[HOWTO][GUIDE] Root & Backup of almost EVERY mt65xx based Device - Android Q&A, Help & Troubleshooting

THIS WILL ONLY WORK WITH DEVICES USING EMMC PARTITION LAYOUT!
otherwise flashtool cannot properly readback needed files wich will cause a bricked device. for rooting mt6573 or mt6575 without emmc partition layout,
refere to this method by rua1: http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
You need to upload the needed files to your Computer using the Read Page Only feature.
ALSO, MAKE SURE YOUR DON'T TRY THAT ON AN ALCATEL (OR SIMILAR) DEVICE, INDICATOR HERE IS A CUSTPACK PARTITION IN SCATTERFILE.
those devices have mt65xx, but have a totally different partition strukture. You can try this tutorial, BUT IF YOU BRICK YOUR DEVICE; I CANNOT HELP YOU OUT!!!
since a lot of devices have different hardware - e.g. Display or Camera - making a Backup of your device should have highest priority. Flashing a wrong ROM can brick your phone!!
What is needed:
VCOM Driver, thx to n2k1
ADB, thx to n2k1
MTK Droid Tools V2.46
If you wan't to use the newest Versionof MTK Droid Tools, refere to here:
http://forum.xda-developers.com/showthread.php?p=38337401#post38337401
also, you can buy Master Shifu rua1 a coffee for his great tool!
Support for the newest Version of Droid Tools is NOT given in this thread! I personally don't use his tool so if something unexpected happens, its not my fault.
SP Flashtool V3.1224 for mt6589, newer flashtool is needed!!! if there are some problems with reading back or flashing the device, newer flashtool is needed.
Install the needed drivers. installing VCOM drivers might take a while, because it will show up just a few seconds while connecting the phone(off).
and now the Step-by-Step tutorial to backup your boot.img, recovery.img and system.img for rooting.
1. enable USB-debugging under Settings-Development->USB debugging
2. phone should now get recognized as "Android Phone - Android Composite ADB Interface" -> if this is a Unknown Device, you should install the ADB drivers.
3.Open MTK Droid Tools
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Connect device to USB (USB Debugging has to be enabled)
5. Device informations has been loaded, Press on "Blocks Map"
We'll need to find the lines bootimg, recovery and Android. We'll need to write down Start-adress(Scatter) and the Size for every line.
(i made a screenshot, writing down isn't necessary.)
In MY Case, this is:
bootimg: 00F88000 size: 00600000
recovery: 01588000 size: 00600000
Android: 026E8000 size: 31900000
6. Now we'll need to click on "Create Scatter File" and you can save it as "MT6577_Android_scatter_emmc.txt"
7. You can Close MTK Droid Tools now.
8. Now we need to open SP Flash Tool and we need to load the scatter file.
9. Now we'll need to click on "Read Back" in the top of SP Flash Tool.
Click on "ADD" 3 Times, we will create "ROM_0", "ROM_1" and "ROM_2".
10. Doubleclick on "ROM_0", and select a place to save it, e.g. C:/N9770_backup/ and rename it to"boot.img"
11. now it will ask you for the Start Adress and lengh for bootimg, we wrote down earlier.
this is in my case: Start Address: 0x00F88000; Lenght: 0x00600000. the first "0x" MUST remain at its place!
12. the same thing you'll need to do for "recovery" and "android".
13. disconnect, shut down and remove the battery of your Device.
13. Now we'll need to click on "Read Back", insert your battery and connect your device to USB. (VCOM driver is needed now, you'll need to install it before getting to the next steps)
14. if this were correct, a red bar should appear on the bottom of SP Flash Tool. you'll need to wait until the green ring appears.
15.Flash Tool now read back the 3 files. system.img isn't that important, but boot.img and recovery.img should be around 6 MB. if the file is smaller or bigger, the length is different to my device or there was a failure while reading back your firmware. So make sure, that at least recovery or boot.img has the right size!!
16. Back to droid tools. reconnect your device to USB , debugging should be enabled, too. switch to "root, backup, recovery" tab in MTK Droid Tools.
select "to choose the boot.img" and press on "Recovery and boot". select your backup boot.img and recovery,img. MTK droid tools will patch boot.img, so you obtain permanent shellroot.
(optional) a window will pop-up and ask you, if you want to install CWM-r. i cannot tell you if that will work, but you can try it, since you backed up your recovery before. )
(optional) a window will pop-up and ask you for the name of your device(you connected it before starting droidtools, so this should not ask you for the name). you can just press enter or you can enter a name for your device.
17. Droid Tools should have modified the boot.img. "--a task is complete--" text should show up in the right of droidtools.
18. Back to Flashtool
You'll need to load the Scatter (like in Step 8)
select boot.img and recovery.img. make sure you select the modified files. (.../Droidtools/recovery/boot.img and recovery.img)
only boot and recovery should be selected!!
19.disconnect, shout down and remove the battery of your device. press on "Download", a window will show up that you have not selected all images. you can press on "OK".
20. insert the battery and connect your device to USB. Flash process should start and if it worked, green ring will appear.
21. Back to DroidTools. device needs to be connected and debugging enabled. switch to "root, backup, recovery" again and press on "SuperUser". this will push superuser, SU binary and busybox to your device.
22. Your Device is rooted now. you can make a Full backup with Droid Tools now.
thx to n2k1 and tommy0815 for the needed files and the original tutorial!!
if i helped you, don't forget to press on "thanks"

reserved for future updates

Testing on my Acer Z120 MT6575 base, I hope this will work, feedback later *fingers crossed*
FEEDBACK:
It totally worked, My Acer z120 is now rooted.
(optional) a window will pop-up and ask you, if you want to install CWM-r. i cannot tell you if that will work, but you can try it, since you backed up your recovery before.
Click to expand...
Click to collapse
Do not use CWM, it will cause your phone not to boot properly, that is my experience on my phone.
Thanks!

yeah never tested it though, thx for the reply!

Re: [HOWTO][GUIDE] Root & Backup of almost EVERY MT65xx based Device
is there anyone here who tried to follow this thread and successfully rooted his android phone?lenovo s720 user here.waiting for more positive feedbacks.

Will this method work on a Vodafone Smart III (975N) probably with 6575?

Guys, this will work on every mt65xx device, if you installed all drivers sucessfully .this whole thing basically changes a value in Boot.IMG To obtain permanent root in the shell. This is the same on EVERY mt65xx based smartphone. Basically you are rooted now. Just needs To push busybox, su and superuser To your device. Thos whole thing seems complex, but you make a backup oft your modified files before modifiing. I never Had device this tutorial was not working every mt6575, 6577 and 6589 should work without an problem. Mt6573 can be a Problem because oft their YAFFS partition strukture.

Chrizzly92 said:
Guys, this will work on every device, if you installed all drivers sucessfully .this whole thing basically changes a value in Boot.IMG To obtain permanent root in the shell. This is the same on EVERY mt65xx based smartphone. Basically you are rooted now. Just needs To push busybox, su and superuser To your device. Thos whole thing seems complex, but you make a backup oft your modified files before modifiing. I never Had device this tutorial was not working every mt6575, 6577 and 6589 should work without an problem. Mt6573 can be a Problem because oft their YAFFS partition strukture.
Click to expand...
Click to collapse
Thanks, I will try!
Sent from my Samsung I9300 with tapatalk4

thank you for this :thumbup:
Sent from my PICOpad GEW using xda app-developers app

dbius said:
Will this method work on a Vodafone Smart III (975N) probably with 6575?
Click to expand...
Click to collapse
Yes, i rooted my vodafone 975N with this method (CWM recovery working) :good:

Gynekolog said:
Yes, i rooted my vodafone 975N with this method :good:
Click to expand...
Click to collapse
:good: That sounds great! Thx man for the informations!
Edit:
Now i tried to root the phone. Everything is went fine till phase nr.19. At this point when the flashtool tried to write back the modified boot.img and recovery.img it gave back me the attached error window.
What should be the problem? I went through the steps with doublecheck and everything was fine till that point. I tried this step two or three times more, but every time gave me this error message.
What should I do now? If it helps I can upload the log folder content here.

Make sure the scatterfile is correct and the files should not be bigger than 6 MB. Flash tool tells you that you need to flash a full image cause the scatter is different from you phone.
Sent from my Star N9770 using xda app-developers app

Chrizzly92 said:
Make sure the scatterfile is correct and the files should not be bigger than 6 MB. Flash tool tells you that you need to flash a full image cause the scatter is different from you phone.
Sent from my Star N9770 using xda app-developers app
Click to expand...
Click to collapse
!EDIT!
Thanks for your answer!
Tonight I found a newer version for flash tool (v3.1304.0.119). Using that version rooting the phone was successful, so thanks, finally it worked.

VCOM Ports
Gynekolog said:
Yes, i rooted my vodafone 975N with this method :good:
Click to expand...
Click to collapse
I still cant root my device. I think its the VCOM ports, because i cant flash
When i click "Read Back" the device is not there..
Can you help me?
Thanks!

This will be very helpful. I have a china phone running on MT6577. I've successfully installed a ported V970 ROM to ZA-985 (which is compatible to my unit in terms of hardware and appearance). I wanna try porting a JB V970 Lewa OS ROM to Kata i1 (identical to ZA-985).

dbius said:
!EDIT!
Thanks for your answer!
Tonight I found a newer version for flash tool (v3.1304.0.119). Using that version rooting the phone was successful, so thanks, finally it worked.
Click to expand...
Click to collapse
thx for your reply, i updated Post #1 , that for mt6589 newer flashtool is required nad sumtimes youll need to play with them. this is because the widely spread devices, they are not the same and sometimes big differences in partitionlayout, SoC revision and so on.
@verntechguy: after rooting, make sure you get a full backup of your device using mtk droid tools. porting lewa is not that hard, but you maybe need to try different platforms to port from. you can refere to here, master shifu yuweng made a pretty good tutorial abut porting Roms.
@Beirajunior: is your device recognized as "mt65xx preloader" when connection to USB? (phone should be off) if not, you can try pressing VOL Up or down while connecting to USB. for flashing, VCOM port 1-16 should be assigned to the drivers.
6

Chrizzly92 said:
thx for your reply, i updated Post #1 , that for mt6589 newer flashtool is required nad sumtimes youll need to play with them. this is because the widely spread devices, they are not the same and sometimes big differences in partitionlayout, SoC revision and so on.
@verntechguy: after rooting, make sure you get a full backup of your device using mtk droid tools. porting lewa is not that hard, but you maybe need to try different platforms to port from. you can refere to here, master shifu yuweng made a pretty good tutorial abut porting Roms.
@Beirajunior: is your device recognized as "mt65xx preloader" when connection to USB? (phone should be off) if not, you can try pressing VOL Up or down while connecting to USB. for flashing, VCOM port 1-16 should be assigned to the drivers.
6
Click to expand...
Click to collapse
Can you help me by team viewer ? :x i still cant do the flash..and the phone is reconized as "mt65xx preloader" but after a while he disconect.
My email is: [email protected]
I appreciate any help.
Cheers

no, i cannot help you via teamviewer, my internet connection is too slow, cause i`m on tethering. some additional infos will be helpfull. device? mt6573,75,77,89?
if the device gets found, everything should work. you`ll need to assing the VCOM ports. just look in the driver settings or google it. i`m sure there is some kind of tutorial for it. also, trying another PC or OS will help, too. alot of guys have problems with that, just switching to XP or so will mostly help without tweaking the drivers.
device should be disconnected and battery should not be inserted. now press readback in flashtool, insert battery and connect the device to USB. now phone should be found by flashtool. if not, like i said, check VCOM ports.

Chrizzly92 said:
no, i cannot help you via teamviewer, my internet connection is too slow, cause i`m on tethering. some additional infos will be helpfull. device? mt6573,75,77,89?
if the device gets found, everything should work. you`ll need to assing the VCOM ports. just look in the driver settings or google it. i`m sure there is some kind of tutorial for it. also, trying another PC or OS will help, too. alot of guys have problems with that, just switching to XP or so will mostly help without tweaking the drivers.
device should be disconnected and battery should not be inserted. now press readback in flashtool, insert battery and connect the device to USB. now phone should be found by flashtool. if not, like i said, check VCOM ports.
Click to expand...
Click to collapse
Hi,
Im already done, but im receiving this error when i try to modified the backuped files (boot and recovery) on MTK Droid Root.I sai no to similar CWM, and i get this error:
"--- ERROR :Boot unthe public mailing list [email protected]"
" --- task is complete ---"
What do you suggest ?
Cheers!

what SoC? mt6573?

Related

USB\VID_1F3A&PID_EFE8 x64 driver

hello guys;
i am in a bit of trouble on win7 x64.
i am trying to flash my tablet with a new rom via livesuitepack 1.7 but the driver which comes with the livesuite doesn't do the trick.
the complete id of the device in device manager is "USB\VID_1F3A&PID_EFE8". and i am wondering if anyone has or know where could i find the suitable driver for that id.
thanks a lot
xgeek
xgeek.cub said:
hello guys;
i am in a bit of trouble on win7 x64.
i am trying to flash my tablet with a new rom via livesuitepack 1.7 but the driver which comes with the livesuite doesn't do the trick.
the complete id of the device in device manager is "USB\VID_1F3A&PID_EFE8". and i am wondering if anyone has or know where could i find the suitable driver for that id.
thanks a lot
xgeek
Click to expand...
Click to collapse
I'm curious what tablet you have and if you'd have any progress. I recently got a Craig CMP741e and was trying to see if I could get into the bootloader. Now it's stuck with a blank screen and shows the same device when plugged in. Seems to be unresponsive, and it looks like it won't boot up normally unless I take it apart and cut power or let the battery drain.
Hello,
It seems that you messed up your bootloader.
The problem you replied to was about the Freelander PD60 (a chinese tablet) 's device driver. The driver to use and flash a rom to it.
I suggest you go and find your latest rom for your device and flash your tablet with it.
Sent from my SXZ-PDX0-03 using Tapatalk HD
Your device should be off and you should press volume - and connect your tablet to the pc.
Install the driver and use live suite to flash new rom into.
If you need any specific let me know.
If the is a driver issue, let me know to give you a link for my driver. If the hardware id is the same you could use that.
Sent from my SXZ-PDX0-03 using Tapatalk HD
Thanks
I'm facing exactly the same issue with Windows 8 (x64) although it worked with Windows 7.
Gesendet von meinem HTC Wildfire S A510e mit Tapatalk 4 BETA
djolivier said:
I'm facing exactly the same issue with Windows 8 (x64) although it worked with Windows 7.
Gesendet von meinem HTC Wildfire S A510e mit Tapatalk 4 BETA
Click to expand...
Click to collapse
As far as I know there is no driver for win8 64bit edition. But there may be a driver for that if you could find LiveSuit 1.9 from your vendor.
you are the one
xgeek.cub said:
Your device should be off and you should press volume - and connect your tablet to the pc.
Install the driver and use live suite to flash new rom into.
Sent from my SXZ-PDX0-03 using Tapatalk HD
Click to expand...
Click to collapse
DUDE DUDE DUEEEEEEEEEEEEEEEE . God bless you soooo hard. you saved my tablet after 4 days hard research in google, to find a solution .How to thank you ! i give you 5 stars.
I could not find any solution to get into Fastboot & boot loader, and the worst was i did install CMBook 10 and i got stuck on "encryption unsuccess" . no access to "Clock Work"
NOW I AM IN .... thanks alot for your solution.
driver request
xgeek.cub said:
Your device should be off and you should press volume - and connect your tablet to the pc.
Install the driver and use live suite to flash new rom into.
If you need any specific let me know.
If the is a driver issue, let me know to give you a link for my driver. If the hardware id is the same you could use that.
Sent from my SXZ-PDX0-03 using Tapatalk HD
Click to expand...
Click to collapse
could you please provide that same driver, i effed up my bootloader to
tablet AT792HC (great tab but support is close to none)
also i am trying to find a custom recovery that might worth with this one, it has an allwinner a20 chipset with dual Mali 400 gpu
i would greatly apreciate any help
reply
seventh_burn said:
could you please provide that same driver, i effed up my bootloader to
tablet AT792HC (great tab but support is close to none)
also i am trying to find a custom recovery that might worth with this one, it has an allwinner a20 chipset with dual Mali 400 gpu
i would greatly apreciate any help
Click to expand...
Click to collapse
Hello, no worries, Now you options are not limited, you can even use suasage script instead of Livesuit. But I recommend livesuite. The latest version that I know is livesuit 1.11 and you can get it from softpedia. But it would be better if you coukd get the kates version of livesuit for your own tablet. From the manufacturer website.
I will post a series of livesuits here also for all of us.
In terms of ROM, ask aroud. You could found yours or relatively similar Roms. But bebcareful don't flase just any rom. That may damage you device.
now that was fast o.o
xgeek.cub said:
Hello, no worries, Now you options are not limited, you can even use suasage script instead of Livesuit. But I recommend livesuite. The latest version that I know is livesuit 1.11 and you can get it from softpedia. But it would be better if you coukd get the kates version of livesuit for your own tablet. From the manufacturer website.
I will post a series of livesuits here also for all of us.
In terms of ROM, ask aroud. You could found yours or relatively similar Roms. But bebcareful don't flase just any rom. That may damage you device.
Click to expand...
Click to collapse
right now i just want to get the device running again hahahaha (and if luck may see fit.. root the damn thing LOL)
think you could help me out.? i won my self a MASIVE fail trying to mess with a device i just recently purchased T.T
reply
seventh_burn said:
right now i just want to get the device running again hahahaha (and if luck may see fit.. root the damn thing LOL)
think you could help me out.? i won my self a MASIVE fail trying to mess with a device i just recently purchased T.T
Click to expand...
Click to collapse
Sure, give me your device exact specs like make and model , inch, memory, hard, cpu and gpu ... , and I give you list of Roms if I found any.
Then after you booted your device, I tell you how to root it.
Don't worry
device info
xgeek.cub said:
Sure, give me your device exact specs like make and model , inch, memory, hard, cpu and gpu ... , and I give you list of Roms if I found any.
Then after you booted your device, I tell you how to root it.
Don't worry
Click to expand...
Click to collapse
Aikun AT792HC
Allwinner dual Core Arm Cortex A7 1.2 ghz
ram 1gb ddr3
flash memory 8gb
screentype capacitive multitouch
screensize 7.85inch panel 1024x768 pixels
camera front 0.3 mpx back 2.0mp
cant get it past android screen
although got the driver running ( i was thinking of trying to flash a custom recovery to see if i can solve the issue but no idea as to where to look, this since finding a stock rom for this is very unlikely)
Forget about any custom job right now, when we flash your device again . And when it boots I will tell you how to go for custom rom as you have that option and they are afew custom roms out there. Again they should match your device.
Wait for next post
gpu info update
seventh_burn said:
Aikun AT792HC
Allwinner dual Core Arm Cortex A7 1.2 ghz
ram 1gb ddr3
flash memory 8gb
screentype capacitive multitouch
screensize 7.85inch panel 1024x768 pixels
camera front 0.3 mpx back 2.0mp
cant get it past android screen
although got the driver running ( i was thinking of trying to flash a custom recovery to see if i can solve the issue but no idea as to where to look, this since finding a stock rom for this is very unlikely)
Click to expand...
Click to collapse
pardon, GPU if im not mistaken it has mali 400 (dual stated but not confirmed)
Firmware in case its needed
seventh_burn said:
pardon, GPU if im not mistaken it has mali 400 (dual stated but not confirmed)
Click to expand...
Click to collapse
http://aikun.com.mx/support/AT792HC/ here is the link to the firmware and phoenixsuite that was used to restore my device, now all im missing is a good rom for it
thank you for your awesome support and if you could point me to a good rom and recovery i would be very thankfull!
Firmware = ROM
First of all hello;
You are so lucky that you found your (STOCK, Native, Factory ...) ROM or Firmware.
For your and all the other chinese tables the ROM is the file with .img extension.
http://aikun.com.mx/support/AT792HC/MVTA-007.img
As it seems Aikun prefers the PhoenixSuit For Flashing ROM. But no worries you still could use LiveSuit if you want to.
So first i will explain the process with Phoenix Suit. Then I will EXPLAIN THE SAME PROCESS with LiveSuit ( YOU SHOULD TRY ONLY ONE of them).
I urgently recommend that you use a Fresh Window Installation. (Either 7 or 8 or XP). if you previously installed android ADB driver or other android related drivers, You may run into trouble. At least remove all the android related drivers and softwares and restart you computer.
1. Install PhoenixSuit. It will install the android USB Driver too. If it asks you that the driver has no valid signature you should press install it any way. IF not do the following:
If you encounter the driver problem like thee image below (Google android driver NOT INSTALLED) or you see your android device with red(x) or yellow (!) on it in windows device manager. Follow these Steps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(This problem happened in windows 8 64bit)
Press end and continue installation of PhoenixSuit .
After that press the update to see if there is a new version available. if yes download and install the new version too.
Again in installation you receive the error message again , dont worry .
Press end and continue installation of PhoenixSuit .
After finish the installation , go to the google site and download the Android SDK ( choose the correct version x32 or x64 for your system ).
Ok now run the android sdk in your computer after finish you can see what have installed.
Go to folder of android sdk and find the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.)
2. From this folder COPY all files EXCEPT the "source.properties"
3. Now go to the PhoenixSuit folder C:\Program Files (x86)\AllWinnertech\PhoenixSuit. [boot disk for me are C:]
Go to folder Drivers ---> C:\Program Files (x86)\AllWinnertech\PhoenixSuit\Drivers .
Now enter to folder ADB_Driver --> C:\Program Files (x86)\AllWinnertech\PhoenixSuit\Drivers\ADB_Driver
And press Paste and REPLACE the contents in the folder (Paste the contents previously copied in step 2 )
4. Go back in folder C:\Program Files (x86)\AllWinnertech\PhoenixSuit .
5. find the file "PhoenixDrvInstall.exe"
6. Now run ( as administrator ) the "PhoenixDrvInstall.exe"
AND VOILA
HowTo install ROM:
FIRST POWER OFF YOU TABLET
1. press Volume -- key and then connect the tablet to PC via usb cable.
2. If you asked to install the driver you do. If you asked that the driver has not been SIGNED you press install it anyway. (or something like that)
3. After the driver(s) is installed; disconnect your table from the PC.
4. Press volume + key and then connect the tablet to PC via usb cable. If you are asked to install the driver again you do
5. Go to PhoenixSuit and select the .img file and press ok to install the ROM.
6. Accept the mandatory Foramt.
epic win!
xgeek.cub said:
First of all hello;
You are so lucky that you found your (STOCK, Native, Factory ...) ROM or Firmware.
For your and all the other chinese tables the ROM is the file with .img extension.
http://aikun.com.mx/support/AT792HC/MVTA-007.img
As it seems Aikun prefers the PhoenixSuit For Flashing ROM. But no worries you still could use LiveSuit if you want to.
So first i will explain the process with Phoenix Suit. Then I will EXPLAIN THE SAME PROCESS with LiveSuit ( YOU SHOULD TRY ONLY ONE of them).
I urgently recommend that you use a Fresh Window Installation. (Either 7 or 8 or XP). if you previously installed android ADB driver or other android related drivers, You may run into trouble. At least remove all the android related drivers and softwares and restart you computer.
1. Install PhoenixSuit. It will install the android USB Driver too. If it asks you that the driver has no valid signature you should press install it any way. IF not do the following:
If you encounter the driver problem like thee image below (Google android driver NOT INSTALLED) or you see your android device with red(x) or yellow (!) on it in windows device manager. Follow these Steps.
(This problem happened in windows 8 64bit)
Press end and continue installation of PhoenixSuit .
After that press the update to see if there is a new version available. if yes download and install the new version too.
Again in installation you receive the error message again , dont worry .
Press end and continue installation of PhoenixSuit .
After finish the installation , go to the google site and download the Android SDK ( choose the correct version x32 or x64 for your system ).
Ok now run the android sdk in your computer after finish you can see what have installed.
Go to folder of android sdk and find the USB driver folder. (The Google USB Driver is located in <sdk>\extras\google\usb_driver\.)
2. From this folder COPY all files EXCEPT the "source.properties"
3. Now go to the PhoenixSuit folder C:\Program Files (x86)\AllWinnertech\PhoenixSuit. [boot disk for me are C:]
Go to folder Drivers ---> C:\Program Files (x86)\AllWinnertech\PhoenixSuit\Drivers .
Now enter to folder ADB_Driver --> C:\Program Files (x86)\AllWinnertech\PhoenixSuit\Drivers\ADB_Driver
And press Paste and REPLACE the contents in the folder (Paste the contents previously copied in step 2 )
4. Go back in folder C:\Program Files (x86)\AllWinnertech\PhoenixSuit .
5. find the file "PhoenixDrvInstall.exe"
6. Now run ( as administrator ) the "PhoenixDrvInstall.exe"
AND VOILA
HowTo install ROM:
FIRST POWER OFF YOU TABLET
1. press Volume -- key and then connect the tablet to PC via usb cable.
2. If you asked to install the driver you do. If you asked that the driver has not been SIGNED you press install it anyway. (or something like that)
3. After the driver(s) is installed; disconnect your table from the PC.
4. Press volume + key and then connect the tablet to PC via usb cable. If you are asked to install the driver again you do
5. Go to PhoenixSuit and select the .img file and press ok to install the ROM.
6. Accept the mandatory Foramt.
Click to expand...
Click to collapse
This won so hard that chuck norris gave it kudos... Now all im missing is a custom rom so i can take advantage of this tablet's specs T.T
Flashing tablet by the use of LIVESUIT
DO ONE OF 2 OPTIONS LIVESUIT OR THE POST BEFORE.
First get the latest version of livesuit from XDA.
Then unpack it.
Click on the livesuit icon (blue and white cubic icon). It will automatically goes to system tray.
By doing so it installs the basic driver package that comes with it.
Now shutdown your tablet
Attach one end of the usb cable to it
Press volume - and hold
Then connect another end of usb cable to the PC.
The window will pop up asking for the location of the device driver.
Address it to where you unpack LiveSuit.
In the Livesuit directory there is a folder named driver. Choose it. (Inside is seprate set of drivers for 32 and 64 bit drivers)
Now click install driver.
Disconnect the usb cable.
Press volume + hold it and connect to PC.
Now when the driver installed, livesuit starts the flashing process by automatically asking for ". img" file. Choose it
You are asked to format the driver. Press yes.
Do not disconnect the usb cable while the process is going on.
For now I dont think any custom rom is available for your device but as the time goes by this will change.
First try to root this rom and go from there.
The next step would be platinum packup pro
Then dolphin browser and a MX video player pro

[Q] LG E455F Optimus L5 II Dual: Hang on "LGSetupWizard"

Good morning.
I got a problem yesterday with my LG L5 II Dual phone: I caught my sisters pressing any buttons on it and when I saw what they did, there was an Android image on it. Now, every time I try to boot it, it cannot finish the initial setup, saying "Unfortunately, LGSetupWizard stopped."
I've rooted this phone some time ago, but the root seems to have no effect now. For instance, I deleted the following apps:
- Facebook
- Twittter
- All of "TIM" resources ("TIM Recarga, TIM Música, TIM this, TIM that"); "TIM" is the mobile operator of my phone.
I tried to follow the steps described in this post: "[Tutorial] Flashing KDZ on LG L5 II (E455/E460) and other LG phones", but I can't get my phone detected under "Download Mode", what I accessed using (Vol Up) + (Vol Down) keys while booting the phone. Unfortunately, it couldn't be detected in any workaround provided by this guide.
When connected under "Download Mode", I see a device called "LGE AndroidNet USB Modem" under "Modems" category on Windows Device Manager. It seems to be the only mode my phone could be detected under this mode.
Playing around with it, I could access a "Recovery Mode" by (Vol Up) + (Quick Access) keys while booting up the phone. I tried to get some info about it and I could, at least, use it with ADB. But I have read-only access, not read-write anymore. Searching more trying to get an answer to "ADB Force Root Mode", I got some things to notice, like the file "default.prop" under the phone's root system.
This "default.prop" shows the following 6 first lines:
Code:
ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=0
persist.sys.usb.config=charge_only
persist.service.acm.enable=0
which means, I think, the phone now isn't configured for USB debugging neither for system write permission.
What can I do to, at least, try to delete some files on it, specifically the 4 setup wizard ones, located at "/system/app/" under the names "LGSetupWizard_JB.apk", "LGSetupWizard_JB.odex", "SetupWizard.apk" and "SetupWizard.odex", since these are the ones which I'm dealing with?
Ah. I tried on computers running Windows 8.1 and Windows XP SP3. No luck.
(edit: 2014-04-02, 23:16 UTC -03:00)
I've playing around with ADB trying to run it with another mode. I don't know if this can help, but sending the phone to recovery mode using ADB
Code:
adb reboot recovery
I get an Android lying with a red triangle sign over it... Still searching for a procedure or an answer to fix the phone, but still with no luck.
[Solved] Guide to solve this kind of problem
After looking for a while on how to fix the problem either by trying to run an ADB shell as root either by flashin the ROM, I could figure another way to flash the original "TIM" rom for my phone instead of the one described on the topic "[Tutorial] Flashing KDZ on LG L5 II (E455/E460) and other LG phones". Here's the way out:
1. Downloading firmware KDZ Flash ROM
First, you have to download the original KDZ ROM for your phone. It can be found at the link below:
LG Optimus L5 II Firmware List
The ones for Brazilian users are described in the page. For TIM users, I suggest using firmware 33 BTM/TIM(BRAZIL), size 599.09 MiB.
Since my phone was sold by TIM, I can't tell about another mobile operators, like Claro, Oi, and VIVO.
2. Extracting a binary file from the KDZ Flash ROM
After that, you will need to extract the KDZ file using LGExtractor (and not DZExtractor).
You can download it from here as an autoextractor file: <4shared>. It will extract itself to C:\RecoverE455\Extract.
Put your KDZ file on an easy access folder. I will assume you will use C:\RecoverE455\ROM for this.
Launch an Administrator command line prompt, and run this command:
Code:
C:\RecoverE455\Extract\LGExtractor -kdz C:\RecoverE455\ROM\<KDZ-ROM-FileName>.kdz
Again, I assume you will put evertything under C:\RecoverE455.
Now, you have a cabinet (CAB) file in the same folder of your KDZ ROM. Extract it directly and you will get some structure similar to this:
DLL (folder)
LGE... (binary rom)
LGUP... (dll file)
3. Getting a most recent version of LGFlashTool
After this procedure, you will have to download LGFlashTool in order to flash you newly extracted BINARY rom.
You can download it from here as an autoextractor file: <4shared>. It will extract itself to C:\RecoverE455\Flasher.
Run the Setup program attached within it and it will install itself under the folder C:\LG\LGFlashTool. Overwrite the file MegaLock.dll under this folder with the one you just extracted in C:\RecoverE455\Flasher.
4. Install the correct LG Support Drivers for your E455 phone
Instead of installing the most recent version of LG Drivers provided by LG, you will install the following ones:
LG United Mobile Driver 3.8.1
LG Windows Mobile 1.0
LG SmartPhone DUN Modem Driver 1.0
They are packaged and you can download them from here as an autoextractor file: <4shared>. It will extract itself to C:\RecoverE455\Drivers. Install them in the order described above then restart your computer.
5. Put your phone under Download Mode
To do this, turn off your phone either directly either removing and reinserting the battery.
Plug the phone - WHILE TURNED OFF - on your computer by the USB cable.
Hold (Vol Up) + (Vol Down) and turn on the phone. Keep holding (Vol Up) + (Vol Down) until you see the line "==>Download mode" in bottom of the screen. If it doesn't appear, try until you get this.
6. Configuring your computer to flash under USB download mode
After plugging your device under Download Mode, open Windows Device Manager and search for some LGE AndroidNet USB Serial Port (COM##):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it is not (COM41), you must set it to port (COM41). Set properties of the serial port, select tab "Port Settings", then click "Advanced":
Here, select (COM41) for COM number port.
7. Launch LGFlashTool and flashing
Open your newly modified LGFlashTool (yes, the one you downloaded here and replaced some DLL). It immediately will ask for your BINARY rom and a DLL:
Click the "..." button and select the LGUP***.DLL in the same folder as your .BIN file you extracted in step 2.
Click the "Add" button immediately below (side S/W box), then select the LGE***.BIN you extracted in step 2.
Click OK.
Click the serial port button --
--, and let this dialog be equal as this one, with only "16 ports\Port 1 ~ Port 16\1" marked:
And now click the forward button --
.
It will display READY on box with port COM41.
Disconnect your phone, turn it off, then turn it on under Download Mode as described on step 5.
If you manage to turn it on Download Mode without connecting to your computer, plug it back to the computer.
It will begin flashing by itself. No action needed.
DO NOT DISCONNECT YOUR PHONE. I DON'T KNOW WHAT MAY HAPPEN IF YOU DO SO, BUT PROBABLY YOU WILL BREAK DEFINITIVELY YOUR DEVICE.
After all, your phone will restart with all its original configuration and LGFlashTool will display an error. After you manage to finish LGSetupWizard on the phone, you may close everything.
Man, you are a HERO.
I was having trouble debranding and updating my phone, but with your tutorial, it was EASY! Now I have a debranded and updated phone (V10K).
MANY MANY MANY THANKS!!!
Again, I assume you will put evertything under C:\RecoverE455.
Now, you have a cabinet (CAB) file in the same folder of your KDZ ROM. Extract it directly and you will get some structure similar to this:
DLL (folder)
LGE... (binary rom)
LGUP... (dll file)
i couldn't find these, i've done instructions carefully ... help me pleasee !!! :crying:
reresatria said:
Again, I assume you will put evertything under C:\RecoverE455.
Now, you have a cabinet (CAB) file in the same folder of your KDZ ROM. Extract it directly and you will get some structure similar to this:
DLL (folder)
LGE... (binary rom)
LGUP... (dll file)
i couldn't find these, i've done instructions carefully ... help me pleasee !!! :crying:
Click to expand...
Click to collapse
solved :laugh: , just doin' little mistake ... thanks man for tutorial
Hi! I'm here again!
I'm trying to do everything again, but now in my new phone, a D685 (LG G Pro Lite Dual).
But, when I connect it in download mode, FlashTool give me an error just after "USB Connection established". No description of the error, just a "F0000002"...
You know how to solve this?
LG 455 IMEI Problem
Hi,
I flash my phone following this instructions a month ago, all gone ok but yesterday both sims come into negative band and i discover IMEIS changed. I try to rewrite imeis from back label under batteries by all the ways i know, but none works. The AT command method via engineer menu or Putty console responds OK but doesnt change anything; same thing with MTKTools.
The las chance, i think, its by meta mode imei an sn change tools, like Maui META or SN_STATION, but i cant enter the phone in meta mode or cant find the correct drivers; every times programs fail attemping to connect to phone...
Please if some know some clues make me know!!!!
niconiconico111 said:
Hi,
I flash my phone following this instructions a month ago, all gone ok but yesterday both sims come into negative band and i discover IMEIS changed. I try to rewrite imeis from back label under batteries by all the ways i know, but none works. The AT command method via engineer menu or Putty console responds OK but doesnt change anything; same thing with MTKTools.
The las chance, i think, its by meta mode imei an sn change tools, like Maui META or SN_STATION, but i cant enter the phone in meta mode or cant find the correct drivers; every times programs fail attemping to connect to phone...
Please if some know some clues make me know!!!!
Click to expand...
Click to collapse
The AT commands worked for me. In putty, be sure to get "IMEI changed" as response, and check the number. If I remember, the IMEI is comma seppareted.
[SOLVED]
romulocarlos said:
The AT commands worked for me. In putty, be sure to get "IMEI changed" as response, and check the number. If I remember, the IMEI is comma seppareted.
Click to expand...
Click to collapse
Hi, thanks for the reply!
Yes, finally the solution was simple, instead of using AT+EGMR command I use AT%IMEI=, that worked!!
can u solve it ?
romulocarlos said:
Hi! I'm here again!
I'm trying to do everything again, but now in my new phone, a D685 (LG G Pro Lite Dual).
But, when I connect it in download mode, FlashTool give me an error just after "USB Connection established". No description of the error, just a "F0000002"...
You know how to solve this?
Click to expand...
Click to collapse
hii, how about this problem ? have you solved it ? can u tell me how do it ... i've got same problem,
reresatria said:
hii, how about this problem ? have you solved it ? can u tell me how do it ... i've got same problem,
Click to expand...
Click to collapse
FlashTool can't work with this phone. Instead, search here on XDA about flashing KDZ larger than 1Gb. Is an offline method.
help
romulocarlos said:
FlashTool can't work with this phone. Instead, search here on XDA about flashing KDZ larger than 1Gb. Is an offline method.
Click to expand...
Click to collapse
thx for reply, i'm using L5 II E455 before i've tried your method about twice and it's work, but since i restart my phone and got an android laying with a red triangle over it, i can't flashing again, it got problem error F0000002 ...
goo(dot)gl/R43Jmj if you don't mind click the url
reresatria said:
thx for reply, i'm using L5 II E455 before i've tried your method about twice and it's work, but since i restart my phone and got an android laying with a red triangle over it, i can't flashing again, it got problem error F0000002 ...
goo(dot)gl/R43Jmj if you don't mind click the url
Click to expand...
Click to collapse
I'm sorry, I make a mistake. My answer above was for another thread.
This method works with E455, just check the drivers and everything else again, and if possible, use a clean computer.
Again, sorry for my mistake.
still can't
romulocarlos said:
I'm sorry, I make a mistake. My answer above was for another thread.
This method works with E455, just check the drivers and everything else again, and if possible, use a clean computer.
Again, sorry for my mistake.
Click to expand...
Click to collapse
still i can't flash my phone,
Thank you very much, I could not recover the phone all the time, the update always stuck to 4%. When this has helped me! Just when I launched the BAT extractor, it deleted all the contents of the parent folder.

Asus Zenfone C bootloop

I tried to flash latest rom from Asus website to my new Zenfone C because it had a weird issue, it came the user interface in taiwanesse, but when trying to change to english, it stayed in taiwanesse, so I wasnt able to setup it in first place.
Then, it came to my mind to flash the latest rom, and I used this guide in absence of a Zenfone C guide for flashing:
http://en.zenfoneasus.com/zenfone-recovering-returning-stock-rom-downgrade-clean-update-guide/
I did all the steps listed there first, and then tried the steps but with the red marked steps, flashing the dnx and ifwi also, no result.
The problem is that now im stuck in a bootloop, and cant advance from there, the Asus logo stays there forever.
What happened during flashing is this:
When I sideloaded the update.zip containing latest rom from Asus website, it said:
-Installing update
-Device image SKU: ww
OTA image SKU: WW
and suddenly after that it restarted, showed a huge Intel Inside logo that I never saw and then went to the dead android image. After waiting a while, the phone restarts, this time only showing the Asus logo with the Intel Inside logo beneath it (not the Intel Inside logo only that I mentioned earlier), and stays there forever.
I dont know what else to do, I dont know if Im doing something wrong.
Were you ever able to fix the problem?
No, until now, no
Sent from my Nexus 5 using Tapatalk
Solved!!!
Hey Spartan!
I was searching online about nexus 5 to buy one but I found something else randomly in an Indonesian blog and was able fix my phone! Hardly took about 15 minutes
I will be posting the solution soon... I hope you are still in need?
kkdevta said:
Hey Spartan!
I was searching online about nexus 5 to buy one but I found something else randomly in an Indonesian blog and was able fix my phone! Hardly took about 15 minutes
I will be posting the solution soon... I hope you are still in need?
Click to expand...
Click to collapse
I still need the fix man, I will really appreciate the posting of the solution! thanks in advance!
Sent from my Nexus 5 using Tapatalk
The Fix!
First Download: -
USB Drivers: http://www.asus.com/in/Phones/ZenFone_C_ZC451CG/HelpDesk_Download/
Asus Flash Tool v1.0.0.11: https://drive.google.com/file/d/0B7cZB2l2IKlKMENKUWlVaHJ3ZHM/view
Signed Rom zip image: https://drive.google.com/file/d/0B__oiYlSY-brdHFWMy1OWXNrajg/view
The Process: -
Get your phone to boot into fastboot mode by pressing [vol -] button and power button simultaneously for few seconds.
Connect to your PC and install USB drivers if not done already. The phone should show up as an "ASUS Android Composite ADB Interface" in the Device Manager.
Now, open ASUS Flash Tool :-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It should detect your phone with serial number and blue orb in front of it.
Select your phone model i.e. ZC451CG
Choose if you want to wipe data or not. I chose "Wipe Data" since I had everything backedup on asus web storage.
Click that box icon and browse for the signed zip image file you downloaded earlier.
Select your device on the ASUS flash Tool by clicking on the serial number like shown in the picture below.
( It had me scratch my head after one failed attempt because I didn't select it the first time! :silly
Click on the green start button, be patient, stay calm and cross your fingers. This could take 10-20minutes or so.:fingers-crossed:
If everything went well your phone should bootup to the welcome screen like the day 1 you got it.
Now, the zip image is quite old so after the initial setup the phone would prompt you with lots of system and app updates. Go with it and enjoy! :victory:
Lastly, don't be shy of pressing that " :good:Thanks! " button if this post helped you.
Thanks man, I will try tonight. Do you know if this works under Windows 8.1 64bits??. I see the screenshots are from windows 7.
Spartan Legionnaire said:
Thanks man, I will try tonight. Do you know if this works under Windows 8.1 64bits??. I see the screenshots are from windows 7.
Click to expand...
Click to collapse
Hopefully it should, I did it on a Windows 7 Professional 64 bit machine.
The USB drivers you download has Windows 8 drivers in it. I think that's all that is needed.
Yeah, I will try it then, and report back, thanks again.
Sent from my Nexus 5 using Tapatalk
kkdevta said:
First Download: -
USB Drivers: http://www.asus.com/in/Phones/ZenFone_C_ZC451CG/HelpDesk_Download/
Asus Flash Tool v1.0.0.11: https://drive.google.com/file/d/0B7cZB2l2IKlKMENKUWlVaHJ3ZHM/view
Signed Rom zip image: https://drive.google.com/file/d/0B__oiYlSY-brdHFWMy1OWXNrajg/view
The Process: -
Get your phone to boot into fastboot mode by pressing [vol -] button and power button simultaneously for few seconds.
Connect to your PC and install USB drivers if not done already. The phone should show up as an "ASUS Android Composite ADB Interface" in the Device Manager.
Now, open ASUS Flash Tool :-
It should detect your phone with serial number and blue orb in front of it.
Select your phone model i.e. ZC451CG
Choose if you want to wipe data or not. I chose "Wipe Data" since I had everything backedup on asus web storage.
Click that box icon and browse for the signed zip image file you downloaded earlier.
Select your device on the ASUS flash Tool by clicking on the serial number like shown in the picture below.
( It had me scratch my head after one failed attempt because I didn't select it the first time! :silly
Click on the green start button, be patient, stay calm and cross your fingers. This could take 10-20minutes or so.:fingers-crossed:
If everything went well your phone should bootup to the welcome screen like the day 1 you got it.
Now, the zip image is quite old so after the initial setup the phone would prompt you with lots of system and app updates. Go with it and enjoy! :victory:
Lastly, don't be shy of pressing that " :good:Thanks! " button if this post helped you.
Click to expand...
Click to collapse
IT WORKEEEED!!!! I dont know how to thank you man!. Thank you so much, I was going to give up on this device!. Its working really well.
The only thing I came into trouble, was to install the USB drivers included in the Asus Flash Tool. I did the following (on Windows 8.1 64bits):
I disabled driver signature check first on windows.
I went to the USB drivers folder inside the ASUS Flash tool folder on Program Files.
I went here C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller\devcon\x64
On that folder, there is a program called devcon.exe, right click on it, and select properties.
On compatibility tab select Run as Administrator, click ok.
After this, reinstall USB drivers by going to C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller and here execute install_drivers.bat
Thats it, the phone now should be recognized by the Asus Flash Tool.
I always failed when downloading Signed Rom zip image.. Someone please provide mirror... Thanks
Tjecing said:
I always failed when downloading Signed Rom zip image.. Someone please provide mirror... Thanks
Click to expand...
Click to collapse
Use a download manager like "free download manager" or something. I am on a slow network to re-upload it else where.
kkdevta said:
Use a download manager like "free download manager" or something. I am on a slow network to re-upload it else where.
Click to expand...
Click to collapse
I don't know how to thank You.. But thanks a lot you safe my days..
Can any one plz give me the link of any custom recovery for asus zenfone c.....i badly need it plz help me...thnks in advance.....plz give me..and tell me how to flash it.....
do you know where i can find the correct .raw file for asus zenfone 5 A501CG ? i use lollipop, i dont know if that's matter =s
Anyone help me When I press volume- and power, it can't enter to fastboot. And when I plug the cable, the flash tool can't detect it
Sent from my Mi 4i using XDA Free mobile app
hello brother...can you help me...
my zenfone 5 a500cg has been softrick and bootloop to...
if i'm turn on my phone
logo asus and then usb logo and then dead again...
i can't log into fastboot(power on+vol up)..
but i can log into cwm philz...
i try flash via adb sideload but always error bla bla bla tmp/updated.zip
if i try other ROM always like this ( please upgrade to image 4.3 first)
i try xftsk but always windriver error( i am use notebook win7)
i try asus flashtool with .raw zip rom but my serial number error just 12345678abcdef...
if i click start always device not detect...
help me bro
disappear3896 said:
Anyone help me When I press volume- and power, it can't enter to fastboot. And when I plug the cable, the flash tool can't detect it
Click to expand...
Click to collapse
power and volume up (+)
Spartan Legionnaire said:
IT WORKEEEED!!!! I dont know how to thank you man!. Thank you so much, I was going to give up on this device!. Its working really well.
The only thing I came into trouble, was to install the USB drivers included in the Asus Flash Tool. I did the following (on Windows 8.1 64bits):
I disabled driver signature check first on windows.
I went to the USB drivers folder inside the ASUS Flash tool folder on Program Files.
I went here C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller\devcon\x64
On that folder, there is a program called devcon.exe, right click on it, and select properties.
On compatibility tab select Run as Administrator, click ok.
After this, reinstall USB drivers by going to C:\Program Files (x86)\ASUS\ASUS Flash Tool\Driver\USBDriverInstaller and here execute install_drivers.bat
Thats it, the phone now should be recognized by the Asus Flash Tool.
Click to expand...
Click to collapse
First and foremost, follow Spartan about how to deal with the driver install error. Read above. Second, those are the links for the raw images:
ww_A500CG_3.23.40.60_20150630.raw and many other phones. It was posted by thanhthuy. 500CG Lollipop: https://mega.nz/#!jwBDUKzJ!x3VD9VJrMe0CBs353DVnXlHr2dHQXepjcqtrR0gQDdU
500CG kitkat:
https://mega.co.nz/#!H8YkyLba!4Ye52JKAjzogGRVvCx2r9XoJIhou_uY3z6YH1xBges8
400CG 6.6.3 - https://mega.co.nz/#!HoRRnLCL!CV-iCMEUgRd_LwDc4QgNkevxKIGOKtFGDYrytt59EVE
400CG 7.3.3 - https://mega.co.nz/#!G8hRwYqR!Eu_l6r_6QSbhjID-MtYQU3v0q0voQ0GYkFeayy-3MFI
451CG: https://mega.co.nz/#!794U1TpT!rermqclZOpPKcYZY8z2YezUkQE-MWjYJgqyKMUAjYDo
600cg Kitkat: https://mega.co.nz/#!S1wlnYhC!doCPvf7ukeEFStcJPgqaEViE5oiHb_hpGSGnIh3n1IQ
Here for 600cg lollipop: https://mega.co.nz/#!3p4wBQAY!KUx26zaGdCBU6CGa4g68zT_iX9NxmIQCUvHiolfa_Oo
ZE550ML Lollipop 40.23 : https://mega.co.nz/#!HgBSySZA!EOxpsmPvHgCfl-9jUVRAv624Uq9LG4uvxuN83j6-P-k
ZE550ML Lollipop 40.40: https://mega.co.nz/#!P4RmXIwb!-xrDe8AYXdprZgUG4Ehs8fLNHhrdKpXdmaV3FBWPC_0
ZE551ML Lollipop: https://mega.co.nz/#!i4JRAQDR!9DzxtSd1oxDuCV6oc0rEhm-1sF4SA-94YPG9fLVw_lw
Source using Google cache (Vietnamese): http://webcache.googleusercontent.com/search?q=cache:w5AS-N1JrAoJ:zenphoneviet.com/threads/all-zen-stock-rom-firmware-kk-l-update-hang-tuan-chay-bang-asus-flash-tool.7066/+&cd=1
---------- Post added at 07:31 AM ---------- Previous post was at 07:29 AM ----------
Those raw files are extremely difficult to find so if you pretend to have any of those phones i recommend to download. It works easily if you have fastboot. If you only have adb i did not saw working but i am trying.
---------- Post added at 07:38 AM ---------- Previous post was at 07:31 AM ----------
If you try to do that under adb they give a serial number mistake.
4 days trying to solve this bootloop using adb. At least one person here saved his phone with the raw links i found using google webcache in this vietnamese link so it was worth it. Looks like i will need to lose 40 days sending to Asus in Sao Paulo. What a hell folks, those asus firmwares are really crap. Set a great hardware for set poor software.
why my phone does not give any reaction when press power button+vol
I had same problem but different situation....I tried to make an experiment by changing systemui and I had done it with a wrong step .lucky I make a backup and tried to recover it.
But Things get worst when it failed to backupbang now my phone get stuck to Asus logo.I tried to follow the method that your all give in this thread but I can go to fastbootode with it must press power button+col down button.
CAN ANYBODY HELP ME WITH THIS PROBLEM
Sorry for my bad English
And I'm a newbie and try to learn something from pro

SP Flash Tool error "STATUS_DA_HASH_MISMATCH"

Hey everyone,
I think my non-rooted phone is stuck in a bootloop (device keeps connecting and disconnecting after every few seconds while connected to the PC via USB). I searched for a way to get a clean ROM install on it using SP Flash Tool (found a guide on GetDroidTips), but whenever the SP Flash Tool starts downloading, it gives me "STATUS_DA_HASH_MISMATCH" error. Does anybody know what might be causing this and what the error itself might mean?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Model: Cubot Power
Error code solution?
madis121 said:
Hey everyone,
I think my non-rooted phone is stuck in a bootloop (device keeps connecting and disconnecting after every few seconds while connected to the PC via USB). I searched for a way to get a clean ROM install on it using SP Flash Tool (found a guide on GetDroidTips), but whenever the SP Flash Tool starts downloading, it gives me "STATUS_DA_HASH_MISMATCH" error. Does anybody know what might be causing this and what the error itself might mean?
Model: Cubot Power
Click to expand...
Click to collapse
Did you find a solution to this? All generic solutions don't seem to work.
Thedonqt said:
Did you find a solution to this? All generic solutions don't seem to work.
Click to expand...
Click to collapse
Hi , i thing that firmware is wrong maybe is for the same device but for example your device has 16GB internal memory but another device with same model has 8 gb of internal storage and that way this error come up.
So what you can try here is :
1. Find Global version for your device with latest firmware if you can find.
2. Put your phone in to the charge for about 2-3 hours to make sure that battery is charged.
3. Uninstall all drivers for your device by using USBDeview (scroll down for download links)
https://www.nirsoft.net/utils/usb_devices_view.html
To uninstall your drivers for device just open the tool , find the your driver for device , right click on it and click on uninstall.
4. Reset COM Ports , and once you reset reboot your PC .
To do that see this post : https://superuser.com/questions/408976/how-do-i-clean-up-com-ports-in-use
5. Reset Windows Defender status to default.
Here you have one example: https://www.youtube.com/watch?v=5t6ES_Py8lU
6. Disable antivirus or malware protection temporary.
7. Try to use old version of SP Flash Tool like one of v5.1xxx .
For example :
https://spflashtools.com/windows/sp-flash-tool-v5-1452
or
https://spflashtools.com/windows/sp-flash-tool-v5-1548
or try with latest version:
https://spflashtools.com/windows/sp-flash-tool-v5-1904
10. Run SP Flash tool with Administrator.
11. Make sure to have this checked inside SP flash options:
-Open Sp Flash tool , go to Options :
Connection - USB ( check USB speed to "High speed" , Battery to "auto detect")
Download - Check "DA DL All with Checksum" and also "Storage checksum" if you have those.
12. Try to just hold Power button while is flashing , once is finish release the power button.
13. Try to flash with disabled driver signature.
To do that follow this post:
https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
14. If the problem is still there , try on another PC or with another version of System (Windows) ....
Good Luck
Teddy Lo said:
Hi , i thing that firmware is wrong maybe is for the same device but for example your device has 16GB internal memory but another device with same model has 8 gb of internal storage and that way this error come up.
So what you can try here is :
1. Find Global version for your device with latest firmware if you can find.
2. Put your phone in to the charge for about 2-3 hours to make sure that battery is charged.
3. Uninstall all drivers for your device by using USBDeview (scroll down for download links)
https://www.nirsoft.net/utils/usb_devices_view.html
To uninstall your drivers for device just open the tool , find the your driver for device , right click on it and click on uninstall.
4. Reset COM Ports , and once you reset reboot your PC .
To do that see this post : https://superuser.com/questions/408976/how-do-i-clean-up-com-ports-in-use
5. Reset Windows Defender status to default.
Here you have one example: https://www.youtube.com/watch?v=5t6ES_Py8lU
6. Disable antivirus or malware protection temporary.
7. Try to use old version of SP Flash Tool like one of v5.1xxx .
For example :
https://spflashtools.com/windows/sp-flash-tool-v5-1452
or
https://spflashtools.com/windows/sp-flash-tool-v5-1548
or try with latest version:
https://spflashtools.com/windows/sp-flash-tool-v5-1904
10. Run SP Flash tool with Administrator.
11. Make sure to have this checked inside SP flash options:
-Open Sp Flash tool , go to Options :
Connection - USB ( check USB speed to "High speed" , Battery to "auto detect")
Download - Check "DA DL All with Checksum" and also "Storage checksum" if you have those.
12. Try to just hold Power button while is flashing , once is finish release the power button.
13. Try to flash with disabled driver signature.
To do that follow this post:
https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
14. If the problem is still there , try on another PC or with another version of System (Windows) ....
Good Luck
Click to expand...
Click to collapse
Massive thank you for taking the time to reply . I was about to jump straight to finding windows 7. I'd done most of those but haven't done vthe usbdeview or couple of hers. I'll try it all in sequence later and let others know :good:
UPDATE
TOK so an update. The problem is still happening after all the steps. I've tested on a windows 8 machine and the same error code is appearing. I'll try it on 7 later though.
As some backstory to mine is my phone entered a bootloop on Friday. It was running low on storage, about 8gb free of 128gb, during the bootloop I tried the power+volume keys to "battery pull" it which rebooted the phone back to normal. Shortly after the screen appeared low-res (like it was a much older screen) and then shut off and hasn't been on since.
The red LED shows when powering, with no screen activity, the phone connects to the computer and is read as a mediatek device. Holding the power down button for around 15 seconds with the device plugged into a wall charger makes the red LED go off then back on (not a flashing led though), and when doing the same while plugged in to a pc it connects like it was just plugged in.
My phone is a Umidigi S2 Pro (only one model for it instead of different size memories etc), the firmwares have been the official ones from the Umidigi S2 Pro roms page including the other tools which is where I flashed the stock Nougat ROM from last year so those should be fine (I'll post links if that's allowed on XDA-developers?). For some stupid reason Umidigi allowed a 3rd party to develop a UmiOS version of Android and used Efuse to restrict it's rooting ability, however this didn't stop the flashing of the 2 update ROMS before.
The code displayed in SP flash tools is M6575D if that's a known trouble one?
Hm , strange maybe the image files from stock firmwares is larger or small and sp flash tool can't verify hach ...
this :
Try with this version of SP Flash tool: https://spflashtools.com/windows/sp-flash-tool-v5-1828 also use checksum from stockfirmware . And make sure that all is checked inside SP Flash tool .
But this way do like this:
- Run SP Flash Tool with Administrator.
- Load full firmware inside SP Flash tool.
- Set Option " Download Only " check just preloader and click Start .
- Now connect your phone with USB 2 ports and see what is happening .
- If the flash is done load now full firmware again and uncheck just preloader.
Let me know if you got fixed .
Good Luck
ERROR: STATUS_STOR_EXHAUST (0xC003001D)
ERROR: STATUS_STOR_EXHAUST (0xC003001D)
The storage in your device has reached end of life, please change to use new device to do operations.
ANY SOLUTION TO THIS???? TRYING TO FLASH TECNO CAMON CX.....
- Set Option " Download Only " just check preloader and click Start .
I learned something new, after investigating this is done to flash the preloader, and fix
STATUS_DA_HASH_MISMATCH​It gives that error because the preloader is flooded/bricked. there is an incorrect hash code/mismatching code between the Brom , preloader in the scatter, and the DA.
After properly unlocking SLA, DAA(Being in Brom mode), fixing the preloader, using the right DA, right Scatter file, this code should match, and the error disappears.
(Flashing the rest of the Rom without preloader becomes possible on the 2nd run)
Thank you for teaching @Teddy Lo
This error wont exist in the future, won't be relevant. But it teaches us about the function of preloader, super data, data, and hash codes.
jdd1996 said:
STATUS_DA_HASH_MISMATCH​It gives that error because the preloader is flooded/bricked. there is an incorrect hash code/mismatching code between the Brom , preloader in the scatter, and the DA.
Click to expand...
Click to collapse
Thank you. After many hours of trying to find a fix, this has helped me. It worked on SP_Flash_Tool_v5.2032_Win.

Moto G8 Power lite Any method to unlock the bootloader ??

there is a method to unlock the bootloader of this device. researched and found nothing about it
therafael1910 said:
there is a method to unlock the bootloader of this device. researched and found nothing about it
Click to expand...
Click to collapse
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
And
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
It's not possible to unlock the bootloader on the G8 power lite, only the G8/G8 power.
aryanhington said:
It's not possible to unlock the bootloader on the G8 power lite, only the G8/G8 power.
Click to expand...
Click to collapse
Says who? This is blackjack/XT2055?
sd_shadow said:
Says who? This is blackjack/XT2055?
Click to expand...
Click to collapse
I can confirm that it's not possible on the XT2055-1 running Mediatek MT6765 SoC
Did anyone try this? Can someone confirm if this works for you?
link
or folllowed this
read my post
aryanhington said:
read my post
Click to expand...
Click to collapse
It is easily possible, stop spreading BS
It cannot be done using fastboot but it is certainly possible using the Realtek VCOM USB protocol
Rooting Moto G8 Power Lite
Does anyone know where I can find a decent guide to rooting the G8 Power Lite (if one exists - I know it's only been out a few months)? I've had a Google around and looked on this forum and on reddit but I can't find anything. I haven't done...
forum.xda-developers.com
This video sums it up well
Essentially you need to:
1. download MTKCLIENT from github, works best on Linux IMHO but Windows works too - on Windows you need additional USB drivers and MTK Drivers, which i attached. Use PIP to install the requirements by going into the MTKCLIENT directory and typing into CMD/Terminal: python3 pip install -r requirements.txt
2. Copy the G8 power Lite specific script to the root folder of the MTKCLIENT
3. Open up the phone, remove the plastic covering the cameras and motherboard. Unplug the battery. Short these two pins either by soldering them together or just using something metal - this is only necessary during the flash and then should be removed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Plug in usb cable to the phone but dont connect it to the pc yet. Start the program either by CD-ing to the MTKCLIENT directory and running it via CLI (on Linux: python3 mtk w proinfo,seccfg proinfo.bin,seccfg.bin, (only use this in case you wiped the bootloader in order to reflash it, the actual unlocking is done by using this generic command: python mtk da seccfg unlock) or doubleclicking the desbloq_bootloader.bat on Windows (which again contains the first command, which should only be used if the bootloader is corrupted or so, unlock using second command from terminal) . Then short the two pins, keep them shorted and connect the USB cable to the PC. You should see a bunch of code scroling, it will automatically close/end.
5. Unplug USB, remove short circuit from two pins, plug in battery, turn on phone, you should see lines of text during the boot like this:
Bootloader unlocked. Now the only use is ROOT, no custom ROMs or Recoveries available as its vastly different from normal G8 power, which has a Snapdragon CPU and totally different screen.
You'll also get a big "CARRIER INVALID" message on the home screen. I tried relocking the bootloader to fix it, but that put the phone into red state and I had to reflash the bootloader using the above mentioned command. On another note, when I trial and error-ed the unlocking process, I first used the bootloader reflash command (which effectively invalidated it) so that may be the sole cause of the invalid message and not the unlocking itself (as the message appeared after reflashing and before unlocking). If anyone tries this, just use python mtk da seccfg unlock and report back.
FakedKetchup said:
It is easily possible, stop spreading BS
It cannot be done using fastboot but it is certainly possible using the Realtek VCOM USB protocol
Rooting Moto G8 Power Lite
Does anyone know where I can find a decent guide to rooting the G8 Power Lite (if one exists - I know it's only been out a few months)? I've had a Google around and looked on this forum and on reddit but I can't find anything. I haven't done...
forum.xda-developers.com
This video sums it up well
Essentially you need to:
1. download MTKCLIENT from github, works best on Linux IMHO but Windows works too - on Windows you need additional USB drivers and MTK Drivers, which i attached. Use PIP to install the requirements by going into the MTKCLIENT directory and typing into CMD/Terminal: python3 pip install -r requirements.txt
2. Copy the G8 power Lite specific script to the root folder of the MTKCLIENT
3. Open up the phone, remove the plastic covering the cameras and motherboard. Unplug the battery. Short these two pins either by soldering them together or just using something metal - this is only necessary during the flash and then should be removed.
View attachment 5889467
4. Plug in usb cable to the phone but dont connect it to the pc yet. Start the program either by CD-ing to the MTKCLIENT directory and running it via CLI (on Linux: python3 mtk w proinfo,seccfg proinfo.bin,seccfg.bin, If it wont unlock using the custom G8 script, just run this generic command: python mtk da seccfg unlock) or doubleclicking the desbloq_bootloader.bat on Windows. Then short the two pins, keep them shorted and connect the USB cable to the PC. You should see a bunch of code scroling, it will automatically close/end.
5. Unplug USB, remove short circuit from two pins, plug in battery, turn on phone, you should see lines of text during the boot like this:
View attachment 5889471
Bootloader unlocked. Now the only use is ROOT, no custom ROMs or Recoveries available as its vastly different from normal G8 power, which has a Snapdragon CPU and totally different screen. You'll also get a big "CARRIER INVALID" message on the home screen, so after you ROOT make sure to relock the bootloader using the same method but the command is python3 mtk da seccfg lock
Click to expand...
Click to collapse
please can you kindly elaborate how you got proinfo.bin and seccfg.bin in the first place? also do you know if it uses any of the payload.bin files which are included with the mtkclient program?
aryanhington said:
please can you kindly elaborate how you got proinfo.bin and seccfg.bin in the first place? also do you know if it uses any of the payload.bin files which are included with the mtkclient program?
Click to expand...
Click to collapse
I have no idea where the files are from, I found them on the net but you know, it works so who cares
These files should work for some models of the Lite G8 as there are the UK models and a few more with the same name. I'm from Slovakia so these didn't work for me, but a generic MTK command python mtk da seccfg unlock did it just fine and I checked it's in fact unlocked by typing fasboot getvar all, and also the fact that on every boot there is a visible text saying that the bootloader is unlocked. It also shows that in developer options.
FakedKetchup said:
I have no idea where the files are from, I found them on the net but you know, it works so who cares
These files should work for some models of the Lite G8 as there are the UK models and a few more with the same name. I'm from Slovakia so these didn't work for me, but a generic MTK command python mtk da seccfg unlock did it just fine and I checked it's in fact unlocked by typing fasboot getvar all, and also the fact that on every boot there is a visible text saying that the bootloader is unlocked. It also shows that in developer options.
Click to expand...
Click to collapse
do you mean the file you attached bootloader_g8powerlite.zip , you dont know where desbloq_bootloader.bat, proinfo.bin , seccfg.bin are from? because they are not mentioned on https://github.com/bkerler/mtkclient
FakedKetchup said:
I have no idea where the files are from, I found them on the net but you know, it works so who cares
These files should work for some models of the Lite G8 as there are the UK models and a few more with the same name. I'm from Slovakia so these didn't work for me, but a generic MTK command python mtk da seccfg unlock did it just fine and I checked it's in fact unlocked by typing fasboot getvar all, and also the fact that on every boot there is a visible text saying that the bootloader is unlocked. It also shows that in developer options.
Click to expand...
Click to collapse
also how is the scatter file used ? i see you attached it but no mention on how its used
aryanhington said:
also how is the scatter file used ? i see you attached it but no mention on how its used
Click to expand...
Click to collapse
1. as i said i dont know, i found the files in the video description
2. scatter file is a useful file for flashing stuff like bootloaders though SP-Flash-Tools. I ripped it from the stock rom which i also just downloaded from the internet. I haven't tried flashing anything yet but it seems the scayyer file (and thus the MTK chip) deosnt allow flashing a nev recovery/bootloader/rom anything really. Need to check again later and play with it a bit more
FakedKetchup said:
1. as i said i dont know, i found the files in the video description
2. scatter file is a useful file for flashing stuff like bootloaders though SP-Flash-Tools. I ripped it from the stock rom which i also just downloaded from the internet. I haven't tried flashing anything yet but it seems the scayyer file (and thus the MTK chip) deosnt allow flashing a nev recovery/bootloader/rom anything really. Need to check again later and play with it a bit more
Click to expand...
Click to collapse
please can you post which error message you get? in theory you should be able to flash anything after the bootloader is unlocked, unless there is some secure boot or verity which is still enabled, which would need to be toggled off. i think you may have the wrong scatter file in that case
aryanhington said:
please can you post which error message you get? in theory you should be able to flash anything after the bootloader is unlocked, unless there is some secure boot or verity which is still enabled, which would need to be toggled off. i think you may have the wrong scatter file in that case
Click to expand...
Click to collapse
Yes i think there is another video on his channel showing that before flashing you need to once again short the 2 pins and execute another program, then flash using SP Tools. There is no error, but when i load up the scatter file, it shows bunch of partitions, none of which are named boot/recovery/bootloader etc. so i don't know if its actually possible. Also I recommend doing all this on Linux, much less hassle, but you will need to compile libpng-12 in order for SP Tools to work. On Ubuntu there should be a binary package in the repos but i used Debian and the package is not supported since release 16.04 so...
according to his channel, you can root it. He uses something called Avenger Box which i assume is some flahing hardware, but we can use SP Flash tools just fine
First, backup NVRAM using SP flash tools in the Readback section
Click ADD NEW and save it to a location on your PC
Then open up your scatter file and look for partition called NVRAM, see the lines "LINEAR START ADRESS", as well as PARTITION SIZE, enter these values to the readback popup menu as such:
(the values on the picture are not real)
Press OK, plug in your device with the shorted pins, press Readback ICON and see if its successful. I am not sure if disabling the protection is needed for readback, will attempt tomorrow.
Tutorial video or a generic guide
Then you can take advice from this video although he isn't using SP Tools so its not a step by step kind of thing. Also for some reason he refuses to share the unlock protection scripts as he is "running a business" by rooting these phones, what a clown , ill try to DM him and see if he shares it or whatever. Ill try to find a way to root it via SP but its a hit or miss.
Edit: Found the script on this exact website:
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
So on some phones you hold downa volume button to flash but in our case we most likely need to short the 2 pins again
aryanhington said:
please can you post which error message you get? in theory you should be able to flash anything after the bootloader is unlocked, unless there is some secure boot or verity which is still enabled, which would need to be toggled off.
Click to expand...
Click to collapse
FakedKetchup said:
Yes i think there is another video on his channel showing that before flashing you need to once again short the 2 pins and execute another program, then flash using SP Tools. There is no error, but when i load up the scatter file, it shows bunch of partitions, none of which are named boot/recovery/bootloader etc. so i don't know if its actually possible. Also I recommend doing all this on Linux, much less hassle, but you will need to compile libpng-12 in order for SP Tools to work. On Ubuntu there should be a binary package in the repos but i used Debian and the package is not supported since release 16.04 so...
View attachment 5891625
according to his channel, you can root it. He uses something called Avenger Box which i assume is some flahing hardware, but we can use SP Flash tools just fine
First, backup NVRAM using SP flash tools in the Readback section
View attachment 5891651
Click ADD NEW and save it to a location on your PC
Then open up your scatter file and look for lines "LINEAR START ADRESS", as well as PARTITION SIZE, enter these values to the readback popum menu as such:
View attachment 5891667
Press OK, plug in your device, press Readback ICON and see if its successful. I am not sure if disabling the protection is needed for readback, will attempt tomorrow.
Tutorial video
Then you can take advice from this video although he isn't using SP Tools so its not a step by step kind of thing. Also for some reason he refuses to share the unlock protection scripts as he is "running a business" by rooting these phones, what a clown , ill try to DM him and see if he shares it or whatever. Ill try to find a way to root it via SP but its a hit or miss.
Edit: Found the script on this exact website:
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com
So on some phones you hold downa volume button to flash but in our case we most likely need to short the 2 pins again
Click to expand...
Click to collapse
in regards to not seeing the recovery partition etc on sp flash tool, its because the scatter file you have used doesnt contain those partitions. I can help you do a full readback of the rom via sp flash tool and create a proper scatter file for your device, because that one you used is most likely incomplete or for another device.
also you lost me at the part regarding libpng-12 , thats only used to render png files . you can come on libera.chat irc and i have created a channel called #motog8powerlite if you need help as its easier to communicate on there
aryanhington said:
in regards to not seeing the recovery partition etc on sp flash tool, its because the scatter file you have used doesnt contain those partitions. I can help you do a full readback of the rom via sp flash tool and create a proper scatter file for your device, because that one you used is most likely incomplete or for another device.
also you lost me at the part regarding libpng-12 , thats only used to render png files
Click to expand...
Click to collapse
libpng-12 is a dependency of the program, probably for the Welcome tab which is made out of pictures instead of a mark language elements...
In regards to the recovery partitions, i found out it is because on devices with A/B partitions, the recovery is merged into the boot.img file. Im not aware of any custom recoveries made for it.
Patching it for root is as straightforward as installing older version of Magisk App on any android phone, copying the stock boot.img anywhere on the device, then patching the file from the app and flashing using SP Tools.
I patched the boot.img from the stock rom. I also managed to successfully execute the bypass script. It used to throw out Missing Default Config error, but i found the default config on github (exploits-collection; attachments) and used that just fine - copy the contents of the archive into the root folder of the bypass utility:
So, in order to unblock the protection, one needs to SOLDER the two pins, any other method was extremely unreliable. On Windows, install LIBUSB drivers from the attached file or from sorceforge. Do it in such a way that you run the installer and you'll get to this popup:
then click next
and youll see bunch of devices. Now plug in the phone with unplugged battery and shorted pins, then wait till a new device pops up, could be called MTK Device or anything like that. You select it and install the libusb library to it. Unplug the phone.
CD into the Bypass Utility folder via CMD/Terminal and run as root: python3 main.py, but install the requirements beforehand (sudo) pip install pyusb pyserial json5 ( running the program as root, the dependencies may not carry over so install them as root as well)
If you did everything right, you should see a prompt saying "Waiting for device"
Then you keep the 2 pins shorted and plug in the phone, if all goes right you should see this output:
On linux, you need a custom patched kernel, either get the patch or get a prepatched kernel or live boot a FireOS iso.
from the README file:
## Usage on Linux
Skip steps 1-2 after first usage
To use this you need [FireISO](https://github.com/amonet-kamakiri/fireiso/releases) or [this patch](https://github.com/amonet-kamakiri/kamakiri/blob/master/kernel.patch) for your kernel
Prebuilt kernels for various distros are available [here](https://github.com/amonet-kamakiri/prebuilt-kernels)
1. Install python
2. Install pyusb, pyserial, json5 as root with command:
```
pip install pyusb pyserial json5
```
3. Run this command as root and connect your powered off phone with volume+ button, you should get "Protection disabled" at the end
```
./main.py
```
4. After that, without disconnecting phone, run SP Flash Tool in UART Connection mode
Click to expand...
Click to collapse
As long as you keep the phone plugged in, the protection is off, however i found myself often needing to re-run the script before each action that utilizes the bootrom.
Using the mentioned scatter file throws out errors. I tried to first remove the protection and then immediately run the NVRAM readback but it failed
Full guide https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
I tried to make my own scatter file by using MTK Droid Tools, but this utility only supports MTK65xx and below CPUs, so it isnt possible in our case. I also tried a generic MTK6765 scatter but that didn't work either. Without the scatter file, the tool doesn't kow where to write the boot.img and thus its a dead end. I'll try to do this on a different PC see if anything changes but i highly suspect its just a wrong scatter file. I got it from this allegedly stock rom.
What i stumbled across is this mirror site, where basically every ROM this device ever had is uploaded, so i think ill start there.
HUGE EDIT:
Accidentally i didnt load up the scatter file from the ROM directory but instead from a different location, tus it didnt load all the other necessary parts. It seems like you have to flash everything, not just one part like recovery or bootloader. Or maybe you can flash a single thing and that is what the square checkboxes are for lol
Thus i can happily announce that i successfully flashed the boot.img, after which Root Checker wstill reported NON-ROOT. I installed MAGISK APP once again and it asked me to reboot to finalize, then it rebooted, i entered the Magisk app and rooted directly from the app. -and the phone is rooted !
Technically it could be possible to flash a custom ROM using this exact tool, although i can only imagine few of the hardware actually working without manually fixing ACPI etc.
It is certainly one of the most difficult root procedures, but nothing unusual in the world of reverse engineering
FakedKetchup said:
libpng-12 is a dependency of the program, probably for the Welcome tab which is made out of pictures instead of a mark language elements...
In regards to the recovery partitions, i found out it is because on devices with A/B partitions, the recovery is merged into the boot.img file. Im not aware of any custom recoveries made for it.
Patching it for root is as straightforward as installing older version of Magisk App on any android phone, copying the stock boot.img anywhere on the device, then patching the file from the app and flashing using SP Tools.
I patched the boot.img from the stock rom. I also managed to successfully execute the bypass script. It used to throw out Missing Default Config error, but i found the default config on github (exploits-collection; attachments) and used that just fine - copy the contents of the archive into the root folder of the bypass utility:
View attachment 5892949
So, in order to unblock the protection, one needs to SOLDER the two pins, any other method was extremely unreliable. On Windows, install LIBUSB drivers from the attached file or from sorceforge. Do it in such a way that you run the installer and you'll get to this popup:
View attachment 5892951
then click next
View attachment 5892953
and youll see bunch of devices. Now plug in the phone with unplugged battery and shorted pins, then wait till a new device pops up, could be called MTK Device or anything like that. You select it and install the libusb library to it. Unplug the phone.
CD into the Bypass Utility folder via CMD/Terminal and run as root: python3 main.py, but install the requirements beforehand (sudo) pip install pyusb pyserial json5 ( running the program as root, the dependencies may not carry over so install them as root as well)
If you did everything right, you should see a prompt saying "Waiting for device"
Then you keep the 2 pins shorted and plug in the phone, if all goes right you should see this output:
View attachment 5892965
On linux, you need a custom patched kernel, either get the patch or get a prepatched kernel or live boot a FireOS iso.
from the README file:
As long as you keep the phone plugged in, the protection is off, however i found myself often needing to re-run the script before each action that utilizes the bootrom.
Using the mentioned scatter file throws out errors. I tried to first remove the protection and then immediately run the NVRAM readback but it failed
View attachment 5892981
Full guide https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
I tried to make my own scatter file by using MTK Droid Tools, but this utility only supports MTK65xx and below CPUs, so it isnt possible in our case. I also tried a generic MTK6765 scatter but that didn't work either. Without the scatter file, the tool doesn't kow where to write the boot.img and thus its a dead end. I'll try to do this on a different PC see if anything changes but i highly suspect its just a wrong scatter file. I got it from this allegedly stock rom.
What i stumbled across is this mirror site, where basically every ROM this device ever had is uploaded, so i think ill start there.
HUGE EDIT:
Accidentally i didnt load up the scatter file from the ROM directory but instead from a different location, tus it didnt load all the other necessary parts. It seems like you have to flash everything, not just one part like recovery or bootloader. Or maybe you can flash a single thing and that is what the square checkboxes are for lol
View attachment 5893083
Thus i can happily announce that i successfully flashed the boot.img, after which Root Checker wstill reported NON-ROOT. I installed MAGISK APP once again and it asked me to reboot to finalize, then it rebooted, i entered the Magisk app and rooted directly from the app. -and the phone is rooted !
Technically it could be possible to flash a custom ROM using this exact tool, although i can only imagine few of the hardware actually working without manually fixing ACPI etc.
It is certainly one of the most difficult root procedures, but nothing unusual in the world of reverse engineering
Click to expand...
Click to collapse
please can you elaborate why you're using exploits_collection-master as before you mentioned you were using mtkclient-main? also do you know why a patched kernel is required on linux?
Not sure but without them it throws out errors, I looked up the error and found a GitHub page which was referenced to the mtkclient - it essentially needs a default config and I supplied that, the file contains configurations for many APUs which are listed in the readme file
Patched kernel I assume is necessary for the bootrom exploit, again if you took few minutes to check the links I mentioned it's all there on GitHub. The kernel needs a way to communicate with the MTK protocol, on Windows there is the VCOM Driver and LIBUSB wizard, on Linux you need to apply the driver to the kernel manually or download a prepatched one.
Hope I proved my point that it's indeed possible to root it and unlock the bootloader, it took me dozens of hours so least you could do is go ahead and edit all the messages where you confidently said it isn't and link this forum there.

Categories

Resources