Hi, Guest! Login / Register




Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

[Still Unresolved] Having trouble getting tools to work with MT6735 device

#21

Thank you admin,
I believe Miracle Box can do it.
Aerieana_Did you Tick Usb Cable?
Secondly Why don't you consider USBdeveiw to uninstall and then reinstall your MTK drivers.
Try Read info first before any other operation.
Miracle is one of the Boxes that supports this Newer Mtk which most don't so,try concentrate well on Miracle.

Sent from my TECNO 8H using Tapatalk


Reply
#22
(This post was last modified: 06-14-2016, 10:27 PM by mensa. )
(06-14-2016, 07:56 PM)Aerieana Wrote: I've tried v2.5.3 just now also, it did exactly the same as v2.5.3d, detects it, gives the same errors as in my attached image a few posts ago, and clicking Blocks Map also shows the same as before.
I meant v2.4.3 and not v2.5.3. I believe that is what I wrote yea it is v2.4.3
Reply
#23
(06-14-2016, 10:09 PM)major.b2b100 Wrote: Thank you admin,
I believe Miracle Box can do it.
Aerieana_Did you Tick Usb Cable?
Secondly Why don't you consider USBdeveiw to uninstall and then reinstall your MTK drivers.
Try Read info first before any other operation.
Miracle is one of the Boxes that supports this Newer Mtk which most don't so,try concentrate well on Miracle.

Sent from my TECNO 8H using Tapatalk
Yes, USB cable was ticked in Miracle Box. I'll try USBdeview tomorrow.



(06-14-2016, 10:17 PM)mensa Wrote:
(06-14-2016, 07:56 PM)Aerieana Wrote: I've tried v2.5.3 just now also, it did exactly the same as v2.5.3d, detects it, gives the same errors as in my attached image a few posts ago, and clicking Blocks Map also shows the same as before.
I meant v2.4.3 and not v2.5.3. I believe that is what I wrote yea it is v2.4.3

I'll give it a try but I don't have high hopes. Seems my SoC is just too "new" or not common enough to be properly supported by tools yet.

----

A slightly different subject; I have a .kdz file for my phone model, taken from LG's servers, and I used a program to extract it. The resulting files are .bin though, not .img like I was expecting. Can .bin files still be used somehow to create/port a custom recovery?
Reply
#24
(06-14-2016, 11:52 PM)Aerieana Wrote: I'll give it a try but I don't have high hopes. Seems my SoC is just too "new" or not common enough to be properly supported by tools yet.

----

A slightly different subject; I have a .kdz file for my phone model, taken from LG's servers, and I used a program to extract it. The resulting files are .bin though, not .img like I was expecting. Can .bin files still be used somehow to create/port a custom recovery?
I suppose so)))) what are the sizes?
Reply
#25
(06-15-2016, 12:13 AM)mensa Wrote:
(06-14-2016, 11:52 PM)Aerieana Wrote: I'll give it a try but I don't have high hopes. Seems my SoC is just too "new" or not common enough to be properly supported by tools yet.

----

A slightly different subject; I have a .kdz file for my phone model, taken from LG's servers, and I used a program to extract it. The resulting files are .bin though, not .img like I was expecting. Can .bin files still be used somehow to create/port a custom recovery?
I suppose so)))) what are the sizes?

The Boot.bin is 11MB, and the Recovery.bin is 12MB. Do those sizes seem about right?
Reply
#26
(06-15-2016, 12:58 AM)Aerieana Wrote:
(06-15-2016, 12:13 AM)mensa Wrote:
(06-14-2016, 11:52 PM)Aerieana Wrote: I'll give it a try but I don't have high hopes. Seems my SoC is just too "new" or not common enough to be properly supported by tools yet.

----

A slightly different subject; I have a .kdz file for my phone model, taken from LG's servers, and I used a program to extract it. The resulting files are .bin though, not .img like I was expecting. Can .bin files still be used somehow to create/port a custom recovery?
I suppose so)))) what are the sizes?

The Boot.bin is 11MB, and the Recovery.bin is 12MB. Do those sizes seem about right?




The CPU is advanced that even mobileuncle can not tweak the imei.
Attach the screeshot of the file for better understanding.
Reply
#27
(This post was last modified: 06-15-2016, 10:49 AM by mensa. )
The Boot.bin is 11MB, and the Recovery.bin is 12MB. Do those sizes seem about right?
[/quote]

Yea they surely are. I believe flashing through sp flash tool, you will have to rename them ".img".are you sure they are really for your phone? Cos the boot especially; if not patched for your phone, flashing with it could brick your phone.

About the backup through mtk v2.4.3; don't even try to tackle it cos it will never work. I just realised my phone is of the same CPU as yours. It's MT6753, 64-bit Abate cos it will never backup the stock rom; not even the imei.
I have been trying the miracle box as well but going through the something as you. Even connecting tecno p5 with CPU MT6572 to it is not detected. I wonder if the fault is with miracle box or something.

About backup, I have been able to root my phone using kingroot v4.6.5! This one did the work when any other root tool have failed. You can try that to root your phone.

Sent from my Infinix NOTE 2 using Hovatek mobile
Reply
#28
Good but still consider you have some of the files in disc image format.
Reply
#29
(This post was last modified: 06-15-2016, 10:47 AM by matybazz. )
(06-15-2016, 12:58 AM)Aerieana Wrote: A slightly different subject; I have a .kdz file for my phone model, taken from LG's servers, and I used a program to extract it. The resulting files are .bin though, not .img like I was expecting. Can .bin files still be used somehow to create/port a custom recovery?

(06-15-2016, 12:58 AM)Aerieana Wrote: The Boot.bin is 11MB, and the Recovery.bin is 12MB. Do those sizes seem about right?

If its in kdz format then its not for spflashtool.. . You sbould try get a firmware with scatter file cause it seems your phone is a LG clone
Reply
#30
(06-15-2016, 10:25 AM)major.b2b100 Wrote:
(06-15-2016, 12:58 AM)Aerieana Wrote: The Boot.bin is 11MB, and the Recovery.bin is 12MB. Do those sizes seem about right?


The CPU is advanced that even mobileuncle can not tweak the imei.
Attach the screeshot of the file for better understanding.

I got the .kdz from here http://www.mylgphones.com/lg-k8-4g-k350n...0n10b.html, and the download link is from LG's servers (http://csmgdl.lgmobile.com)

(06-15-2016, 10:29 AM)mensa Wrote: Yea they surely are. I believe flashing through sp flash tool, you will have to rename them ".img".are you sure they are really for your phone? Cos the boot especially; if not patched for your phone, flashing with it could brick your phone.

Yes, it's for the LG K8 K350N, which is the European version (that has MTK chips, the US K8s have Qualcomm). My phone has the English ROM as I'm from the UK.

(06-15-2016, 10:42 AM)matybazz Wrote: If its in kdz format then its not for spflashtool.. . You sbould try get a firmware with scatter file cause it seems your phone is a LG clone

I already know that .kdz isn't for SPFlashTool, it's for LG's own official tool for backup and restore. I can't get or make a scatter file as I've said before, since the tools to retrieve or make one don't want to work with the SoC my phone has.

My phone is not an LG clone either, I bought it directly from the O2 UK network.

Attached Files
.png   extracted bin files.png (Size: 45.22 KB / Downloads: 6)
.png   Screenshot_2016-06-15-11-53-19.png (Size: 68.59 KB / Downloads: 5)
.png   Screenshot_2016-06-15-11-53-35.png (Size: 58.36 KB / Downloads: 6)
Reply










Users browsing this thread:
1 Guest(s)