Hello, I have a motoE 2 LTE (XT1514 Surnia) that originally had Android 5.0.2, but it went to motorola for repair and came back with 6.0. Despite the upgrade, the bootloader screen still showed "software status: official".
The I have unlocked the bootloader, installed TRWP and used it to flash supersu. The log says the process was successful but I checked with the app root checker that it was not.
Then I wanted to go back with the stock ROM. I downloaded the XT1514_SURNIA_RETBR_DS_6.0_MPI24.65-39_cid12_subsidy-DEFAULT_CFC.xml ROM from this link I found on xda-developers and flashed it with RSD Lite. The system works but the bootloader screen now says "software status: modified"; before this process I made a backup using TWRP but after restoring the bakcup image the message still didn't change back to "software status: official".
I thought maybe I need to install the original Android (5.02) and then upgrade it to 6.0, so I downloaded the XT1514_SURNIA_RETBR_DS_5.0.2_LXI22.50-53.8_cid12_subsidy-DEFAULT_CFC.xml ROM from the same link. The problem is I get a failure message when I try to flash the 5.0.2 image
Code:
# mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.125s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.570s
I did try with RSD Lite too, but I get the same message. I've read somewhere you can't dowgrade stock firmware, is the the problem here ? There is any workaround ?
My final objective is to have stock firmware with android 6.0 installed and the bootloader message saying it is official. I appreciate any help =)
ps. Even after flasingh the stock ROM there still a folder called supersu on the root folder. How is this possible ?
This is the log of RSD Lite flashing the stock image with android 6.0
Code:
28/16 05:39:10 The FlashLog key is turned off.
09/28/16 05:39:10 Multi upgrade started for 1 phones
09/28/16 05:39:10 [Device ID: 0] 1/20 getvar max-sparse-size
09/28/16 05:39:10 [Device ID: 0] 2/20 oem fb_mode_set
09/28/16 05:39:10 [Device ID: 0] 3/20 flash partition "gpt.bin"
09/28/16 05:39:11 [Device ID: 0] 4/20 flash bootloader "bootloader.img"
09/28/16 05:39:12 [Device ID: 0] 5/20 flash logo "logo.bin"
09/28/16 05:39:12 [Device ID: 0] 6/20 flash boot "boot.img"
09/28/16 05:39:15 [Device ID: 0] 7/20 flash recovery "recovery.img"
09/28/16 05:39:18 [Device ID: 0] 8/20 flash system "system.img_sparsechunk.0"
09/28/16 05:39:42 [Device ID: 0] 9/20 flash system "system.img_sparsechunk.1"
09/28/16 05:40:03 [Device ID: 0] 10/20 flash system "system.img_sparsechunk.2"
09/28/16 05:40:22 [Device ID: 0] 11/20 flash system "system.img_sparsechunk.3"
09/28/16 05:40:42 [Device ID: 0] 12/20 flash system "system.img_sparsechunk.4"
09/28/16 05:40:49 [Device ID: 0] 13/20 flash modem "NON-HLOS.bin"
09/28/16 05:40:54 [Device ID: 0] 14/20 erase modemst1
09/28/16 05:40:54 [Device ID: 0] 15/20 erase modemst2
09/28/16 05:40:54 [Device ID: 0] 16/20 flash fsg "fsg.mbn"
09/28/16 05:40:54 [Device ID: 0] 17/20 erase carrier
09/28/16 05:40:55 [Device ID: 0] 18/20 erase cache
09/28/16 05:40:55 [Device ID: 0] 19/20 erase userdata
09/28/16 05:40:57 [Device ID: 0] 20/20 oem fb_mode_clear
09/28/16 05:40:57 [Device ID: 0] reboot
09/28/16 05:40:57 CMultiFlashFlex::RebootPhone, waiting for phone to disconnect, status=2, state=0.
09/28/16 05:40:58 Removal, interface=28(0x0), device id=1636460.
09/28/16 05:40:58 CMultiFlashFlex::RebootPhone, waiting for phone to connect, status=3, state=4.
09/28/16 05:48:08 00002de8 Phone.cpp 1571 0 ERROR Waiting for phone's handle is setted successfully after restart [430000 ms] completion. failed
09/28/16 05:48:08 CMultiFlashFlex::RebootPhone, unable to wait for phone, status=3, state=4.
09/28/16 05:48:08 [Device ID: 0] Please manually power up this phone.
09/28/16 05:55:18 00002de8 Phone.cpp 3974 -1 ERROR CPhone::WaitForPhone timed out. Iteration-1
09/28/16 05:55:18 [Device ID: 0] Please manually power up this phone.
09/28/16 06:02:28 00002de8 Phone.cpp 3974 -1 ERROR CPhone::WaitForPhone timed out. Iteration-2
09/28/16 06:02:28 [Device ID: 0] Please manually power up this phone.
09/28/16 06:08:36 Arrival, interface=36(0x0), device id=1636460.
09/28/16 06:08:36 [Device ID: 0] Waiting for others to finish current operation.
09/28/16 06:08:36 Arrival, interface=20(0x0), device id=1636460.
09/28/16 06:08:36 Arrival, interface=19(0x0), device id=1636460.
09/28/16 06:08:36 The FlashLog key is turned off.
09/28/16 06:08:36 FlashLog file is turned off.
09/28/16 06:08:36 Multi upgrade finished.
you can install the stock mm firmware without any issues, but cant keep the status as official. Coz ive flashed the firmware multiple times and have had the status to be modified and not official.
ASKdroid said:
you can install the stock mm firmware without any issues, but cant keep the status as official. Coz ive flashed the firmware multiple times and have had the status to be modified and not official.
Click to expand...
Click to collapse
Hi, ASKdroid, thanks for answering, I thought this might be how it works, but I've seem videos of people rainstalling stock and the message did change back to official. Check this one at times 1:10 and 11:20
Related
I have a Droid RAZR XT912 that was working perfectly. I bought it and did a factory wipe inside the phone settings. Rebooted phone only to get stuck at the "Droid" sign. Was running 4.1.2, no rooting ever, and stock recovery. Basically stock everything. So far I've done:
1. Factory Reset In Recovery
2. Matt's Utility Factory Reset to Jelly Bean with Wipe Of Data in Fastboot Mode
3. RSD Lite Flash in Fastboot Mode of version cdma_spyder_9.8.2O-72_VZW-16_1ff.xml
4. Matt's Utility for Factory Reset then the BLUR version of OTA flash in stock recovery.
5. Continuous wiping of data and cache between all of these points.[/B][/B]
Nothing produces anything other than it to freeze at the same point in it's boot. Right at the white lettered "Droid" screen. Please help me! I know it's not hardware because the phone worked find until I factory reset it. Thank you in advance!
RSD Lite Logs for the .165 Flash
Here are my most recent RSD Lite logs for the cdma_spyder_9.8.2O-72_VZW-16-5_cfc.xml flash.
07/27/14 10:53:17 Multi upgrade started for 1 phones
07/27/14 10:53:17 [Device ID: 0] 1/24 flash cdt.bin "cdt.bin_signed"
07/27/14 10:53:18 [Device ID: 0] 2/24 reboot-bootloader
07/27/14 10:53:25 [Device ID: 0] 3/24 flash emstorage "emstorage.img"
07/27/14 10:53:27 [Device ID: 0] 4/24 reboot-bootloader
07/27/14 10:53:34 [Device ID: 0] 5/24 flash mbm "allow-mbmloader-flashing-mbm.bin"
07/27/14 10:53:35 [Device ID: 0] 6/24 reboot-bootloader
07/27/14 10:53:41 [Device ID: 0] 7/24 flash mbmloader "mbmloader.bin"
07/27/14 10:53:41 [Device ID: 0] 8/24 flash mbm "mbm.bin"
07/27/14 10:53:42 [Device ID: 0] 9/24 oem fb_mode_set
07/27/14 10:53:43 [Device ID: 0] 10/24 reboot-bootloader
07/27/14 10:53:47 [Device ID: 0] 11/24 flash motoboot "motoboot.img"
07/27/14 10:53:50 [Device ID: 0] 12/24 reboot-bootloader
07/27/14 10:53:57 [Device ID: 0] 13/24 erase cache
07/27/14 10:53:57 [Device ID: 0] 14/24 erase userdata
07/27/14 10:53:59 [Device ID: 0] 15/24 erase userdata
07/27/14 10:54:00 [Device ID: 0] 16/24 flash logo.bin "logo.bin"
07/27/14 10:54:01 [Device ID: 0] 17/24 flash devtree "device_tree.bin"
07/27/14 10:54:02 [Device ID: 0] 18/24 flash system "system.img"
07/27/14 10:55:50 [Device ID: 0] 19/24 flash boot "boot.img"
07/27/14 10:55:54 [Device ID: 0] 20/24 flash recovery "recovery.img"
07/27/14 10:55:57 [Device ID: 0] 21/24 flash cdrom "cdrom"
07/27/14 10:56:35 [Device ID: 0] 22/24 flash preinstall "preinstall.img"
07/27/14 10:58:13 [Device ID: 0] 23/24 flash radio "radio.img"
07/27/14 10:58:18 [Device ID: 0] 24/24 oem fb_mode_clear
07/27/14 10:58:18 [Device ID: 0] reboot
Did you ever get a resolve from these jokers?
Same thing for me, did you ever get a resolve from all these idiots at these forums? I don't see one, but could you remember what you did to get it back or did you trash it? Thanks, I am going nuts trying to figure this out presently.
[email protected] if you could let me know. Thanks.
Speakeasys said:
I have a Droid RAZR XT912 that was working perfectly. I bought it and did a factory wipe inside the phone settings. Rebooted phone only to get stuck at the "Droid" sign. Was running 4.1.2, no rooting ever, and stock recovery. Basically stock everything. So far I've done:
1. Factory Reset In Recovery
2. Matt's Utility Factory Reset to Jelly Bean with Wipe Of Data in Fastboot Mode
3. RSD Lite Flash in Fastboot Mode of version cdma_spyder_9.8.2O-72_VZW-16_1ff.xml
4. Matt's Utility for Factory Reset then the BLUR version of OTA flash in stock recovery.
5. Continuous wiping of data and cache between all of these points.[/B][/B]
Nothing produces anything other than it to freeze at the same point in it's boot. Right at the white lettered "Droid" screen. Please help me! I know it's not hardware because the phone worked find until I factory reset it. Thank you in advance!
Click to expand...
Click to collapse
Hello everybody. (sorry for my writing mistakes )
XT910 with stock firmware: http://savepic.org/6550017.png
IMEI - EMEA region
Worked fine.
But then...
Through BMM installed - LiquidSmooth KitKat (http://forum.xda-developers.com/showthread.php?t=2782971)
and then
"SPYDERIRD_U.01.6.7.3-94_SPI-328_04.11.01P_0A.74_ASIA_RETAIL_HKTW_CFC_HWp2b_SIGNED.xml.zip"
(I do not know why. It was not me. But I want to help restore the phone.)
When the process is finished (Successfully О_о), the phone no longer worked.
Now:
Normally mode, Recovery - not working:
Invalid Flash Mode (S) (Boot Failure)
0A.77
To return to normal mode - first press power key to poser down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X004E)
Invalid CG OTV (CG: system)
What we tried to install (AP Fastboot - RSDLite 6.1.5):
- SPYDERIRD_U.01.6.7.3-94_SPI-328_04.11.01P_0A.74_AUSTRALIA_NZ_CFC_HWp2b_SIGNED.xml.zip
- SPYDERIRD_U.01.6.7.3-94_SPI-328_04.11.01P_0A.74_AUSTRALIA_OPTUS_CFC_HWp2b_SIGNED.xml.zip
- SPYDERIRD_U.01.6.7.3-94_SPI-328_04.11.01P_0A.74_MEA_RETAIL_CFC_HWp2b_SIGNED.xml.zip
- SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSO2DE_HWp2b_Service1FF_fastboot.xml.zip
- SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml.zip
- 673.94.324.XT910.AsiaRetail.en.03.xml.
- 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RTFE1007.0R_USASPDRJBRTFR_P013_A014_p2b_S1FF_fb_CFC.xml.zip (Retail FR)
- 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b57374ab5a_p2b_S1FF_fb_CFC.xml.zip (Retail GB)
Always:
11/28/14 11:48:56 [Device ID: 0] 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin"
11/28/14 11:48:56 [Device ID: 0] 2/19 reboot-bootloader
11/28/14 11:49:00 [Device ID: 0] 3/19 flash mbmloader "mbmloader.bin"
11/28/14 11:49:01 [Device ID: 0] 4/19 flash mbm "mbm.bin"
11/28/14 11:49:02 [Device ID: 0] 5/19 reboot-bootloader
11/28/14 11:49:06 [Device ID: 0] 6/19 flash cdt.bin "cdt.bin_signed"
11/28/14 11:49:06 ERROR: 6/19 flash cdt.bin "cdt.bin_signed" -> Phone returned FAIL. - on device ID 0.
11/28/14 11:49:06 [Device ID: 0] 6/19 flash cdt.bin "cdt.bin_signed" -> Phone returned FAIL.
11/28/14 11:49:06 ERROR: Failed flashing process. - on device ID 0.
This metod:
1-download cdt.bin ( http://www.mediafire.com/?ua1nj6ds6r0vtue )
2-download fastboot files ( http://dfiles.eu/files/bih3tmg7b )
3-restart your phone in to bootloader ( fastboot ) mode
4-connect your phone via usb cable
5-open cmd.exe in your pc an go to fastboot files
6-flash cdt.bin via this command -------------------------------------- fastboot flash cdt.bin cdt.bin
7-restart your phone in to stock recovery
8-do triple wipe and restart your phone
Nothing helps! Can you help? What can we do?
Thanks for help...
No one has any ideas?
that's interesting: tried to remove CID and failed, because: (see picture)
Code:
Erasing CID ... INFOCommand Restricted
Wrong command?
And:
Code:
CID:5
XT910S ?
Why can not we delete CID?
Thanks for "help".
Mission completed.
Thread is closed.
did u manage to fix your i have the same problem with you please some one should help,i just want to get my phone back to normal, i have the same firmware with u
jamil1982 said:
did u manage to fix your i have the same problem with you please some one should help,i just want to get my phone back to normal, i have the same firmware with u
Click to expand...
Click to collapse
This is my script for FastBoot (0A:77 Bootloader and for XT910S)
Warning! This will remove your CID!
Use this method only when all other methods have failed.
https :// yadi .sk/d/M2EmR9HKdA3pF
unpack RAR: in C:/MyRecover/
Connect your phone (AP Fastboot mode) to PC.
Run MyRecoverV1.bat
done.
After that, you can install any firmware (RSDLite 6.1.5)
reccomend: Britain Retail 4.1.2 : https :// yadi .sk/d/zcq12jT5d44mu
After finish all task whitout errors, reboot cellphone, press Volume up, volume down and Power, and selet "BP Tools"
Get Root
Install BMM 0.3.4
Now your phone loaded automatically (without BP TOOLS)
VasyaAgPro said:
This is my script for FastBoot (0A:77 Bootloader and for XT910S)
Warning! This will remove your CID!
Use this method only when all other methods have failed.
https :// yadi .sk/d/M2EmR9HKdA3pF
unpack RAR: in C:/MyRecover/
Connect your phone (AP Fastboot mode) to PC.
Run MyRecoverV1.bat
done.
After that, you can install any firmware (RSDLite 6.1.5)
reccomend: Britain Retail 4.1.2 : https :// yadi .sk/d/zcq12jT5d44mu
After finish all task whitout errors, reboot cellphone, press Volume up, volume down and Power, and selet "BP Tools"
Get Root
Install BMM 0.3.4
Now your phone loaded automatically (without BP TOOLS)
Click to expand...
Click to collapse
Downloading Right now thank You i will give u feed back:good:
after running my MyRecoverV1.bat see what i got
---------------------------------------------------------------
Delete CID for kwyjibo jr by Vasya
---------------------------------------------------------------
Press any key to continue . . .
---------------------------------------------------------------
getvar:all FAILED (remote: unsupported command)
finished. total time: 0.008s
getvar:all FAILED (remote: unsupported command)
---------------------------------------------------------------
0A3BEC240400A007 fastboot
0A3BEC240400A007 fastboot
CID delete:
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
finished. total time: 0.010s
sending 'mbm' (512 KB)... OKAY [ 0.089s]
writing 'mbm'... OKAY [ 0.486s]
sending 'mbm' (512 KB)... OKAY [ 0.089s]
writing 'mbm'... OKAY [ 0.507s]
finished. total time: 0.596s
rebooting into bootloader... OKAY [ 0.007s]
finished. total time: 0.008s
< waiting for device >
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
finished. total time: 0.011s
rebooting into bootloader... OKAY [ 0.008s]
finished. total time: 0.009s
< waiting for device >
sending 'mbm' (512 KB)... OKAY [ 0.102s]
writing 'mbm'... OKAY [ 0.489s]
sending 'mbm' (512 KB)... OKAY [ 0.103s]
writing 'mbm'... OKAY [ 0.483s]
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
finished. total time: 0.010s
rebooting into bootloader... OKAY [ 0.007s]
< waiting for device >
sending 'mbm' (512 KB)... OKAY [ 0.102s]
writing 'mbm'... OKAY [ 0.488s]
finished. total time: 0.592s
sending 'mbm' (512 KB)... OKAY [ 0.090s]
writing 'mbm'... OKAY [ 0.508s]
finished. total time: 0.599s
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
erasing 'cid'... INFOCommand restricted
FAILED (remote: )
finished. total time: 0.010s
rebooting into bootloader... OKAY [ 0.006s]
finished. total time: 0.007s
< waiting for device >
cid: 5
finished. total time: 0.018s
Press any key to continue . . .
any help please?
this is what my phone is showing
jamil1982 said:
this is what my phone is showing
Click to expand...
Click to collapse
CID not erased, for 0A:74 BootLoader try to use:
http://forum.xda-developers.com/showthread.php?t=2372614
If you want to check, removed CID or not:
Just see on last line in MyRecoverV1:
Code:
< waiting for device >
[COLOR="Red"]cid: 5[/COLOR]
finished. total time: 0.018s
When CID : DEAD - you win
If another thread not helps you:
Run MyRecoverV2 and MyRecoverV3 and again V1
it should help.
VasyaAgPro said:
CID not erased, for 0A:74 BootLoader try to use:
http://forum.xda-developers.com/showthread.php?t=2372614
If you want to check, removed CID or not:
Just see on last line in MyRecoverV1:
Code:
< waiting for device >
[COLOR="Red"]cid: 5[/COLOR]
finished. total time: 0.018s
When CID : DEAD - you win
If another thread not helps you:
Run MyRecoverV2 and MyRecoverV3 and again V1
it should help.
Click to expand...
Click to collapse
thanks i will check the link please can u give me the easy way on how to make a motorola factory cable? i have some factory cables that came with my polar 3 box whenever i connect the cable from my phone to the system the phone show white led light and my system doesnt recognize the phone so i dont know if the phone is charging or not and im afraid of loosing the power battery,but with normal cable my system recognize it but the white led light doesnt show, thank you once again
---------- Post added at 09:14 AM ---------- Previous post was at 08:45 AM ----------
strange i run all the bat but it give me the same
cid: 5
jamil1982 said:
thanks i will check the link please can u give me the easy way on how to make a motorola factory cable? i have some factory cables that came with my polar 3 box whenever i connect the cable from my phone to the system the phone show white led light and my system doesnt recognize the phone so i dont know if the phone is charging or not and im afraid of loosing the power battery,but with normal cable my system recognize it but the white led light doesnt show, thank you once again
Click to expand...
Click to collapse
Only one way for factory cable: (see picture)
jamil1982 said:
strange i run all the bat but it give me the same
cid: 5
Click to expand...
Click to collapse
Now run MyrecoverV2 and V3, then V1 for check.
VasyaAgPro said:
Only one way for factory cable: (see picture)
Now run MyrecoverV2 and V3, then V1 for check.
Click to expand...
Click to collapse
I run the V2 and V3 then Run the V1 again it showed the same thing, but I noticed its like the number has change from 0a.74 to 0A.74 and now its Showing 0A.75
jamil1982 said:
I run the V2 and V3 then Run the V1 again it showed the same thing, but I noticed its like the number has change from 0a.74 to 0A.74 and now its Showing 0A.75
Click to expand...
Click to collapse
hmm...
now - run all .bat files - V1, then 2, then 3 (after 3 NOT run again 1 !)
and finally "info.bat. (https :// yadi .sk/d/HdYWqS1gdAhfr)
Put info.bat to "MyRecovery" dir and run.
Log insert here.
VasyaAgPro said:
hmm...
now - run all .bat files - V1, then 2, then 3 (after 3 NOT run again 1 !)
and finally "info.bat. (https :// yadi .sk/d/HdYWqS1gdAhfr)
Put info.bat to "MyRecovery" dir and run.
Log insert here.
Click to expand...
Click to collapse
OHHH MY G You are Genius :good: after running Myrecover1 again it deleted the cid everything went smooth and the number on my Ap fastboot display 0A.77 then i run this 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b57374ab5a_p2b_S1FF_fb_CFC.xml.zip, it run perfect without any error:laugh: then my phone restart showing Costumer error. Contact Resseller, the i off it and on it to boot menu then select Bp Tools, my phone restart, its time for me to get rid of the Costumer error. Contact Resseller if u can provide me the link i will be very greatfull thanks for everything:good::good::good:
Im rooted using this method http://forum.xda-developers.com/showthread.php?t=2298408 then install BMM Everything went ok only the Costumer error. Contact Resseller but im ok like this thank you so much
xt910 bricked and cant find firmware
Hi,
I also have xt910 razr maxx and i bricked it after installing some kind of custom rom app.
I want to flash stock firmware but all the links on internet are broken. I guess I need this one:
SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_ Service1FF_fastboot.xml.zip
Can aybody help me with a working link of this file pls, its kinda urgent.
Thanks.
VasyaAgPro said:
No one has any ideas?
that's interesting: tried to remove CID and failed, because: (see picture)
Code:
Erasing CID ... INFOCommand Restricted
Wrong command?
And:
Code:
CID:5
XT910S ?
Why can not we delete CID?
Click to expand...
Click to collapse
Hey all, yesterday I only flashed 4.4.4 Kitkat in my phone (previously running custom 5.1.1).
(PS also received 3 5.0.2 updates as I was on soak test)
Anyways, the problem I am facing is that:
MY logo.bin is getting flashed, but still showing "Warning bootloader unlocked"
WHY?
I must mention here that I didnot flash gpt.bin and motoboot.img..... Do these files have anything to do with it?
Please help.
Maybe because your bootloader is still unlocked so the unlocked bootloader must have replaced the logo.bin if though you flashed it
Sent from my condor using Tapatalk
Moto E XT1022 soft bricked ad USB debugging is not enabled
[/B]
Faiz Syed said:
Maybe because your bootloader is still unlocked so the unlocked bootloader must have replaced the logo.bin if though you flashed it
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Dear Faiz, I have soft bricked my moto e 1st gen (XT1022) India dual sim variant after I tried to flash android 5.1 from 5.0.2. While flashing I copied the 13MB (small bug fix) Condor zipfile ad everything went fine, however I forgot to disconnect the USB cable after pasting the 13 mb zip file and the phone got stuck in bootloop. It throws up the error "E: Can't mount /cache/recovery/last_install and E: Can't open /dev/block/platform/msm_sdcc.1/
Now I have not enabled USB debugging previously and the device is not getting detected in ADB cmd. But in mfastboot cmd I can see the device, but there I cannot flash as it is not able to clear cache or data or anything. Oh also, during trying to reset my phone i tried to unlock the bootloader and now the bootloader is unlocked.
How to recover my phone back to normal? Please guide.
UjRock said:
[/B]
Dear Faiz, I have soft bricked my moto e 1st gen (XT1022) India dual sim variant after I tried to flash android 5.1 from 5.0.2. While flashing I copied the 13MB (small bug fix) Condor zipfile ad everything went fine, however I forgot to disconnect the USB cable after pasting the 13 mb zip file and the phone got stuck in bootloop. It throws up the error "E: Can't mount /cache/recovery/last_install and E: Can't open /dev/block/platform/msm_sdcc.1/
Now I have not enabled USB debugging previously and the device is not getting detected in ADB cmd. But in mfastboot cmd I can see the device, but there I cannot flash as it is not able to clear cache or data or anything. Oh also, during trying to reset my phone i tried to unlock the bootloader and now the bootloader is unlocked.
How to recover my phone back to normal? Please guide.
Click to expand...
Click to collapse
It looks like you did something wrong while flashing and the gpt(partition tables) may have got corrupted thats why it shows it cant mount cache partition or open dev/block directory files...what exact error does it show after entering the commands in fastboot?
Sent from my condor using Tapatalk
Moto E XT1022 soft bricked ad USB debugging is not enabled
Faiz Syed said:
It looks like you did something wrong while flashing and the gpt(partition tables) may have got corrupted thats why it shows it cant mount cache partition or open dev/block directory files...what exact error does it show after entering the commands in fastboot?
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick response Faiz, please find the screenshot of the errors when I try to flash from SD card and the mfastboot cmd.
These are the commands in the install ROM .bat file;
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
pause
mfastboot.exe reboot
This is what i get in mfastboot cm whe i run the istall ROM .bat file;
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash partition gpt.b
in
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.491s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash motoboot motobo
ot.img
target max-sparse-size: 256MB
error: cannot load 'motoboot.img': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (527 KB)...
OKAY [ 0.062s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 5.077s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
error: cannot load 'boot.img': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash recovery recove
ry.img
target max-sparse-size: 256MB
error: cannot load 'recovery.img': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash system system.i
mg_sparsechunk.0
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.0': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash system system.i
mg_sparsechunk.1
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.1': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash system system.i
mg_sparsechunk.2
target max-sparse-size: 256MB
error: cannot load 'system.img_sparsechunk.2': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash modem NON-HLOS.
bin
target max-sparse-size: 256MB
error: cannot load 'NON-HLOS.bin': No error
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase modemst1
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.039s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase modemst2
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.028s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (648 KB)...
OKAY [ 0.094s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 5.135s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase cache
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.025s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot.exe erase userdata
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 5.025s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>pause
Press any key to continue . . .
Screenshot of SD card flash;
After looking at the command failures,from my own experience,your emmc(storage chip) may have got corrupted,the bootloader cant make any changes in the partitions neither can it write a new gpt to the storage...try this command(it wipes data,system and cache)..see if it works or what error it shows,corrupted emmc is not a good thing,could be a brick.
Fastboot erase system -w
Sent from my condor using Tapatalk
Faiz Syed said:
It looks like you did something wrong while flashing and the gpt(partition tables) may have got corrupted thats why it shows it cant mount cache partition or open dev/block directory files...what exact error does it show after entering the commands in fastboot?
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Faiz Syed said:
After looking at the command failures,from my own experience,your emmc(storage chip) may have got corrupted,the bootloader cant make any changes in the partitions neither can it write a new gpt to the storage...try this command(it wipes data,system and cache)..see if it works or what error it shows,corrupted emmc is not a good thing,could be a brick.
Fastboot erase system -w
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
I tried, but it failed nevertheless.
This is what it returned:
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mfastboot devices
ZX1B33CH8Z fastboot
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>Fastboot erase system -w
'Fastboot' is not recognized as an internal or external command,
operable program or batch file.
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>mFastboot erase system -w
erasing 'system'...
(bootloader) Erase allowed in unlocked state
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 9.930s
D:\Utorrent Downloads\Chrome Dwlds\Mfastboot>
The problem is I do not have a proper service centre here and as per customer experiences, they have been asked to replace the motherboard. Now that is as goo as buying a new handset. Please Faiz, let me know if this is solvable or I have to simply shut down the handset and buy a new one?
Sure the emmc got corrupted and it cant be fixed,and its embedded on the motherboard so it cant be replaced either..the only solution would be to replace the motherboard,or say goodbye and buy a new phone...motherboard should cost around 2k and our device value in the market is around 2.5-3k so its not feasible..your choice.
Sent from my condor using Tapatalk
Moto E XT1022 soft bricked ad USB debugging is not enabled
Faiz Syed said:
Sure the emmc got corrupted and it cant be fixed,and its embedded on the motherboard so it cant be replaced either..the only solution would be to replace the motherboard,or say goodbye and buy a new phone...motherboard should cost around 2k and our device value in the market is around 2.5-3k so its not feasible..your choice.
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Thank you very much Faiz, you were helpful in providing quick answers. I very much appreciate your time and effort. I'll buy a new phone as that seems to be a more doable option here.
You have a good day ahead!
Faiz Syed said:
Maybe because your bootloader is still unlocked so the unlocked bootloader must have replaced the logo.bin if though you flashed it
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
I'll try relocking.
Hi everyone!
Just wanted to share some steps in case you brick your Realme.
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY DAMAGES
Some prerequisites you will need:
mtkclient + python
spft (sp flash tool)
ofp extractor
Your stock rom in OFP format.
Step 1. Download all of the things mentioned above.
Step 1a. Make sure your device is turned off. DO NOT PLUG IT IN.
Step 2. Install mtkclient using the guide on GitHub.
Step 3. Run
Bash:
$ py mtk payload
in your terminal.
Step 3a. When it says ***waiting for device*** hold both volume buttons and plug in your device.
This will enter BROM mode.
Step 4. Extract and open ofp extractor and extract your ofp.
Step 5. Open SPFT and click DOWNLOAD ONLY (do not I MEAN DO NOT PRESS FORMAT ALL.)
Step 6. In scatter, look for your scatter file. It should be (MTxxxxScatter.txt etc) Then select it.
Step 7. Select your auth file if you have one.
Step 8. Press Download and if the progress bar starts going the flash is going. DO NOT UNPLUG.
Step 9. Reboot after it says 'Download Ok'
Step 10. Enjoy your unbricked device!
NOTE In most cases the rom will be for android 10. Update if required through OZIP.
I cannot download with SPFlash. Error 0xC0060001. I'm sure that I have done all steps correctly including this tutorial:
Realme 7 Unbrick
Of corse I'm doing everything with Realme 7 5G RMX2111EU.
I had problems with disabling protection as follows but I think it finally succeeded.
1. bypass_utility-v.1.4.2 gives error
Code:
[2022-05-10 22:53:51.684562] Waiting for device
[2022-05-10 22:53:59.780976] Found port = COM4
[2022-05-10 22:53:59.921376] Device hw code: 0x996
[2022-05-10 22:53:59.921376] Device hw sub code: 0x8a00
[2022-05-10 22:53:59.921376] Device hw version: 0xca00
[2022-05-10 22:53:59.921376] Device sw version: 0x0
[2022-05-10 22:53:59.921376] Device secure boot: True
[2022-05-10 22:53:59.921376] Device serial link authorization: False
[2022-05-10 22:53:59.921376] Device download agent authorization: True
[2022-05-10 22:53:59.921376] Disabling watchdog timer
[2022-05-10 22:53:59.936976] Disabling protection
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win
error: A device attached to the system is not functioning.\r\n\n'
[2022-05-10 22:54:01.028978] Payload did not reply
Press any key to continue . . .
2. mtk-client gives error:
Code:
....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
3. MTK Meta Utility v37 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
DriverName : MediaTek USB Port_V1633
DriverPath : usb\vid_0e8d&pid_0003\5&278a3c80&0&2
DriverID : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
InfPath : oem28.inf
ProviderName : MediaTek Inc.
Connecting to BootROM......
● Chipset MT6853
● Identifier Dimensity 720/800U 5G
● Info 8A00_CA00_0000_Mouton
● MEID:3EFFEA531AB22A57AB0240D8421E92B4
● SecCFG SBC+SDA
Disable BRom protection...
MTK Auth Disable(SLA/DAA) success!
now you can use SP Flash Tool or any MTK Tool
4. MTK Auth Byoass Tool v6.0.0.1 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
Sync with bootrom started...
● Chipset MT6853:Dimensity 720/800U 5G
● Code Mouton
● Hw Sub 8A00
● HW Ver CA00
● SW Ver 0000
● SecCFG SBC+SDA
Disable brom protection.
Bypass Payload ACK = 0xa1a2a3a4
MTK Secure Boot Bypasss success!
now you can use SP Flash Tool or any MTK Tool
czaroslaw said:
I cannot download with SPFlash. Error 0xC0060001. I'm sure that I have done all steps correctly including this tutorial:
Realme 7 Unbrick
Of corse I'm doing everything with Realme 7 5G RMX2111EU.
I had problems with disabling protection as follows but I think it finally succeeded.
1. bypass_utility-v.1.4.2 gives error
Code:
[2022-05-10 22:53:51.684562] Waiting for device
[2022-05-10 22:53:59.780976] Found port = COM4
[2022-05-10 22:53:59.921376] Device hw code: 0x996
[2022-05-10 22:53:59.921376] Device hw sub code: 0x8a00
[2022-05-10 22:53:59.921376] Device hw version: 0xca00
[2022-05-10 22:53:59.921376] Device sw version: 0x0
[2022-05-10 22:53:59.921376] Device secure boot: True
[2022-05-10 22:53:59.921376] Device serial link authorization: False
[2022-05-10 22:53:59.921376] Device download agent authorization: True
[2022-05-10 22:53:59.921376] Disabling watchdog timer
[2022-05-10 22:53:59.936976] Disabling protection
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win
error: A device attached to the system is not functioning.\r\n\n'
[2022-05-10 22:54:01.028978] Payload did not reply
Press any key to continue . . .
2. mtk-client gives error:
Code:
....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
3. MTK Meta Utility v37 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
DriverName : MediaTek USB Port_V1633
DriverPath : usb\vid_0e8d&pid_0003\5&278a3c80&0&2
DriverID : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
InfPath : oem28.inf
ProviderName : MediaTek Inc.
Connecting to BootROM......
● Chipset MT6853
● Identifier Dimensity 720/800U 5G
● Info 8A00_CA00_0000_Mouton
● MEID:3EFFEA531AB22A57AB0240D8421E92B4
● SecCFG SBC+SDA
Disable BRom protection...
MTK Auth Disable(SLA/DAA) success!
now you can use SP Flash Tool or any MTK Tool
4. MTK Auth Byoass Tool v6.0.0.1 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
Sync with bootrom started...
● Chipset MT6853:Dimensity 720/800U 5G
● Code Mouton
● Hw Sub 8A00
● HW Ver CA00
● SW Ver 0000
● SecCFG SBC+SDA
Disable brom protection.
Bypass Payload ACK = 0xa1a2a3a4
MTK Secure Boot Bypasss success!
now you can use SP Flash Tool or any MYKI Tool
Click to expand...
Click to collapse
What more.info about the error code do you have? Also are you on windows because spft buggy on linux
BROM ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
Windows 7
SP_Flash_Tool_v5.2208_Win
czaroslaw said:
BROM ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
Windows 7
SP_Flash_Tool_v5.2208_Win
Click to expand...
Click to collapse
Then you haven't bypassed brom, try mtkclient again and don't unplug your device
Mtk client gives error: Preloader - [LIB]: ←[31mStatus: Handshake failed
Install mtk drivers and Libusb, also pyserial
All above mentioned was installed. I tried different pack from droidwin and I get this:
Code:
Port - Device detected :)
Preloader - CPU: MT6853(Dimensity 720 5G)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0xa
Preloader - Disabling Watchdog...
Preloader - HW code: 0x996
Preloader - Target config: 0xe5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: 3EFFEA531AB22A57AB0240D8421E92B4
Preloader - SOC_ID: DAA82CB9D5E03916132A0BE2A479C0CC0FFD2B10
1E00173F9EA9FCB44C88FC8E
PLTools - Loading payload from mt6853_payload.bin, 0x264 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
Kamakiri - Done sending payload...
PLTools - Successfully sent payload: D:\Apk\MTK Bypass Tools\mtkclient-main\mtkc
lient\payloads\mt6853_payload.bin
Be sure to use in SPFT, in connection check USB full speed, and in general settings, uncheck the options Check LIB DA Match and Storage Life Cycle Check.
If this doesn't work, try to flash only preloader firstly, and then flash the rest, upload some screenshot if the error persists.
That means it worked
Ok. Bootloader is unlocked but now I have dm-verity corrupted.
I cannot enter recovery mode. Some error flashes on screen and immediately reboot. I cannot even read this. I have found that it might be:
the serial is not matched
fastboot_unlock_verify failed
I cannot enter fastboot mode. It gives:
Orange state
The device is unlocked and cannot be trusted
and then restarts
Normal boot gives:
dm_varity corruption
Your device is corrupted
It won't be trusted and may not work properly
Press power button to continue
Then pressing power button boots into system correctly and the phone is working.
How to get rid of these errors? How to recover access to recovery and fastboot mode? Should I flash some partitions again from stock formware?
Should I install PBRP using mtkclient as in this guide?
Install TWRP Recovery without using Fastboot Mode [MediaTek]
And then should I root it using patched Magisk as follows?
Root MediaTek Devices without using Fastboot Mode [via MTK Client]
There is some info about patched version of Magisk for MTK devices. Should I use it?
do
Code:
fastboot flash --disable-verity --disable-verification vbmeta {your vbmeta.img}
czaroslaw said:
Ok. Bootloader is unlocked but now I have dm-verity corrupted.
I cannot enter recovery mode. Some error flashes on screen and immediately reboot. I cannot even read this. I have found that it might be:
the serial is not matched
fastboot_unlock_verify failed
I cannot enter fastboot mode. It gives:
Orange state
The device is unlocked and cannot be trusted
and then restarts
Normal boot gives:
dm_varity corruption
Your device is corrupted
It won't be trusted and may not work properly
Press power button to continue
Then pressing power button boots into system correctly and the phone is working.
How to get rid of these errors? How to recover access to recovery and fastboot mode? Should I flash some partitions again from stock formware?
Should I install PBRP using mtkclient as in this guide?
Install TWRP Recovery without using Fastboot Mode [MediaTek]
And then should I root it using patched Magisk as follows?
Root MediaTek Devices without using Fastboot Mode [via MTK Client]
There is some info about patched version of Magisk for MTK devices. Should I use it?
Click to expand...
Click to collapse
If it says DM-verity error, reflash with spft and on mtkclient, relock BL by using
Code:
Py mtk da seccfg lock
I cannot enter fastboot mode so I cannot use fastboot flash.
Second advice: I do not want to lock bootloader.
If you are able to boot to stock, do ADB reboot fastboot
Does not work. It gives the same as VolUP+PWR. Orange state message and reboot.
I cannot enter fastboot in any way.
Should I flash something in brom mode? Recovery partition? Something else to get rid of dm_varity?
Reflash firmware then try, idk this hasn't happened to me
Also send the link of the firmware U got
I have RMX2111_11_C.11. Updated via OTA. I cannot find such version firmware file.
The newest I found is:
RMX2111GDPR_11_C.09 EDL mode
czaroslaw said:
I have RMX2111_11_C.11. Updated via OTA. I cannot find such version firmware file.
The newest I found is:
RMX2111GDPR_11_C.09 EDL mode
Click to expand...
Click to collapse
Relock bootloader and try using this to reunlock bl
Hello I got Cat s52 phone and it is restarting all the time and getting this error "your device has failed verification and may not work properly"
I will appreciate any help! Thanks in advance!
xDaemon said:
Hello I got Cat s52 phone and it is restarting all the time and getting this error "your device has failed verification and may not work properly"
I will appreciate any help! Thanks in advance!
Click to expand...
Click to collapse
If you have a warranty and you have not made any modifications to the firmware, please contact support.
If there is no warranty or you have modified the firmware, then follow the steps described below.
1. Install mtkclient (or use live dvd).
2. Make a backup of all partitions.
3. Find the firmware dump.The dump can be found here or here. Also I can make dump from my device if needed.
(Only firmware from first link tested by me).
4. Flash the partitions you need (it may be enough to flash only the boot partition).
More detailed instructions how dump and flash are on the mtkclient page.
Lesosek said:
If you have a warranty and you have not made any modifications to the firmware, please contact support.
If there is no warranty or you have modified the firmware, then follow the steps described below.
1. Install mtkclient (or use live dvd).
2. Make a backup of all partitions.
3. Find the firmware dump.The dump can be found here or here. Also I can make dump from my device if needed.
(Only firmware from first link tested by me).
4. Flash the partitions you need (it may be enough to flash only the boot partition).
More detailed instructions how dump and flash are on the mtkclient page.
Click to expand...
Click to collapse
Spoiler
C:\Users\Admin\mtkclient>PYTHON mtk_gui
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
.....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Port - Hint:
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
...........
Port - Hint:
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
...........
Port - Hint:
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
Port - Device detected
Preloader - CPU: MT6765/MT8768t(Helio P35/G35)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0x25
Preloader - Disabling Watchdog...
Preloader - HW code: 0x766
Preloader - Target config: 0xe5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: 921E4FBF578455DEEC50F9EBA448BD88
Preloader - SOC_ID: 0240DFE71E5D62B444C450A856A7E8C3A5B6C2A94C1F9C7EFDA8A7838803CD98
Preloader - Status: Waiting for PreLoader VCOM, please connect mobile
Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Port - Device detected
Preloader - CPU: MT6765/MT8768t(Helio P35/G35)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0x25
Preloader - Disabling Watchdog...
Preloader - HW code: 0x766
Preloader - Target config: 0xe5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: 921E4FBF578455DEEC50F9EBA448BD88
Preloader - SOC_ID: 0240DFE71E5D62B444C450A856A7E8C3A5B6C2A94C1F9C7EFDA8A7838803CD98
Port - Device detected
DAXFlash - Uploading xflash stage 1 from MTK_AllInOne_DA_5.2152.bin
xflashext - Patching da1 ...
xflashext
xflashext - [LIB]: ←[33mError on patching da1 version check...←[0m
xflashext - Patching da2 ...
DAXFlash - Successfully uploaded stage 1, jumping ..
Preloader - Jumping to 0x200000
Preloader - Jumping to 0x200000: ok.
DAXFlash - Successfully received DA sync
DeviceClass - USBError(5, 'Input/Output Error')
None
Traceback (most recent call last):
File "C:\Users\Admin\mtkclient\mtkclient\gui\toolkit.py", line 113, in run
self.function(self, self.parameters)
File "C:\Users\Admin\mtkclient\mtk_gui", line 87, in getDevInfo
mtkClass = da_handler.configure_da(mtkClass, preloader=None)
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_da_cmd.py", line 112, in configure_da
if not mtk.daloader.upload_da(preloader=preloader):
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_daloader.py", line 209, in upload_da
return self.da.upload_da()
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_daxflash.py", line 1143, in upload_da
connagent = self.get_connection_agent()
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_daxflash.py", line 383, in get_connection_agent
res = self.send_devctrl(self.Cmd.GET_CONNECTION_AGENT)
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_daxflash.py", line 267, in send_devctrl
status[0] = self.status()
File "C:\Users\Admin\mtkclient\mtkclient\Library\mtk_daxflash.py", line 215, in status
magic, datatype, length = unpack("<III", hdr)
struct.error: unpack requires a buffer of 12 bytes
Thats is the longest way which i can go . . . . .
xDaemon said:
Thats is the longest way which i can go . . . . .
Click to expand...
Click to collapse
It's most likely an installation or incompatibility issue. The python version must be 3.9. requirements,drivers,usbdk must be installed. If the problem cannot be solved, you can use LiveDVD where all the necessary software is preinstalled.
Lesosek said:
It's most likely an installation or incompatibility issue. The python version must be 3.9. requirements,drivers,usbdk must be installed. If the problem cannot be solved, you can use LiveDVD where all the necessary software is preinstalled.
Click to expand...
Click to collapse
I tried with LiveDVD but it is not recognized, can you make some guide with commands for LiveDVD if you have time, Please! I am real noob with Linux.
And the phone is restarting every 5 seconds, I have to press all 3 buttons and hold them but after some time I hear sound from connecting and disconnecting USB . . . .
Sorry for wasting your time!
xDaemon said:
I tried with LiveDVD but it is not recognized, can you make some guide with commands for LiveDVD if you have time, Please! I am real noob with Linux.
And the phone is restarting every 5 seconds, I have to press all 3 buttons and hold them but after some time I hear sound from connecting and disconnecting USB . . . .
Sorry for wasting your time!
Click to expand...
Click to collapse
Latest LiveDVD has user interface for MTKClient.
Lesosek said:
Latest LiveDVD has user interface for MTKClient.
Click to expand...
Click to collapse
I know, but when i click on it does nothing . . . . .
xDaemon said:
I know, but when i click on it does nothing . . . . .
Click to expand...
Click to collapse
"python mtk" command should print list of commands with description
Code:
MTK Flash/Exploit Client V1.52 (c) B.Kerler 2018-2021
-----------------------------------
Available commands are:
printgpt: Print GPT Table information
gpt: Save gpt table to given directory
r: Read flash to filename
rl: Read all partitions from flash to a directory
rf: Read whole flash to file
rs: Read sectors starting at start_sector to filename
ro: Read flash starting at offset to filename
w: Write partition from filename
wf: Write flash from filename
wl: Write partitions from directory path to flash
wo: Write flash starting at offset from filename
e: Erase partition
es: Erase partition with sector count
footer: Read crypto footer from flash
reset: Send mtk reset command
dumpbrom: Try to dump the bootrom
dumppreloader: Try to dump the preloader
payload: Run a specific kamakiri / da payload, if no filename is given, generic patcher is used
crash: Try to crash the preloader
brute: Bruteforce the kamakiri var1
gettargetconfig: Get target config (sbc, daa, etc.)
peek: Read memory in patched preloader mode
stage: Run stage2 payload via boot rom mode (kamakiri)
plstage: Run stage2 payload via preloader mode (send_da)
xflash: Run da xflash special commands
You can solve your problem using these commands:
"python mtk rl <dump directory name>" - dump all partitions, you shold have free 64GB, process may take few hours
"python mtk printgpt" - partition list
"python mtk r <partition name> <path to file>" - dump partition to file
"python mtk w <partition name> <path to file>" - write partition from file
"python mtk e <partition name>" - erase partition
Also you have to be careful with write or erase commands so a backup of all partitions should be done!