Hello all!
In an effort to try and help Boost Mobile users out, I have put together a stock restore guide for the Moto E 2015. There are other versions of a stock firmware guide, but those are for GSM and others not using CDMA. Here you will find steps to restore your Boost Mobile Moto E!
First off, I am NOT responsible for damaging your phone or any user error. USE THIS GUIDE AT YOUR OWN RISK!
If you are here reading this guide, you have either bricked your device or just want to go back to the stock firmware. If you are using a custom recovery such as TWRP, any saved nandroid backups will be lost if saved on internal storage. This will factory load 5.0.2 Lollipop fresh out of the box the day you got your phone!
Firstly, you will need ABD and Fastboot and Motorola Device Manager. You can download Motorola Device Manager directly from here.
I have attached ABD and Fastboot to this post for download.
To use ABD and Fastboot, you will need to make a new folder and extract the zip to the new folder and name it fastboot. From there, you will need to launch a command window from that folder. The easiest way to do this is to to have that folder selected and Shift/right click and "Open command window here". From there, if you have done this right, you will have a command prompt window ready to go!
After you have setup your new folder with ABD and Fastboot, you are ready to load the stock firmware to your Moto E! Download link is here
After you have downloaded your stock firmware, double check to make sure you have XT1526_Updated_SURNIA_BOOST_5.0.2_LXI22.50-14.6_cid9_subsidy-DEFAULT_CFC.xml.zip
Extract the contents of the file you downloaded to the folder where you put your ABD and Fastboot in.
Once you have everything ready to go, power down your phone and put it in bootloader mode. Hold power and volume down for a few seconds and you are there. Attach your USB cable from your PC to the phone and be ready to load several lines of code. Flash these codes in order. Copy and paste if you like in to your command prompt, one line at a time!
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem config carrier
fastboot oem fb_mode_clear
Once you have done this, restart your phone and wait a few minutes for the boot sequence to start. If you have done this right, your phone will be factory fresh with the stock firmware on it!
If I was able to help out, hit thanks! :good:
This is my first guide and I had to look everywhere to find out how to do this for Boost variants, and hopefully it is ok for everyone to use!
EDIT: I updated the download link. Sorry about that.
Will this relock bootloader?
crazynapkinman said:
Will this relock bootloader?
Click to expand...
Click to collapse
No. There are certain steps to relock the bootloader, but it does no good now. You can still OTA with an unlocked bootloader, but as far as factory warranty goes, its void as soon as you unlock it. The only reason you would ever want to relock it is if you were giving the phone to someone who didn't know anything about rooting our phones.... it just doesn't do any good.
Thanks. I may try this, but not until after I flash cyanogen 12. That won't be until they get LTE working on CDMA Boost Mobile variant.
Also, why do you need to have Motorola Device Manager?
crazynapkinman said:
Thanks. I may try this, but not until after I flash cyanogen 12. That won't be until they get LTE working on CDMA Boost Mobile variant.
Also, why do you need to have Motorola Device Manager?
Click to expand...
Click to collapse
Motorola Device Manager installs all the drivers you need for the phone.
Thank you
imprint89 said:
Motorola Device Manager installs all the drivers you need for the phone.
Click to expand...
Click to collapse
Thank you I finally got my Moto e back to stock with twrp and root with SuperSu which Borks my cameras. LOL. The only thing I had to do different I had to use MFastboot and there is a 1 click installer to do it with.
I really appreciate you looking out.
Joe
joex55 said:
Thank you I finally got my Moto e back to stock with twrp and root with SuperSu which Borks my cameras. LOL. The only thing I had to do different I had to use MFastboot and there is a 1 click installer to do it with.
I really appreciate you looking out.
Joe
Click to expand...
Click to collapse
Glad I could help out!
Hey, this forum looks really helpful, but unfortunately the stock firmware zip link isn't working for me. Is there any other place that you might suggest getting it from? I do have two of the same phone if it's possible to retrieve the firmware from another one, but I wiped my first one which is why I'm here in the first place. Thanks!
*EDIT: Hey, no worries, I found another file of the same type, but I can't post the link yet. (Follow the Moto E 2015 thread to general to "| Read Before You Flash | Unlock | Restore | Stock Firmware |," follow the link there, and find the other, newer, XT1526 file.) I just installed the drivers, got the minimal adb/fastboot zip, and followed the commands given above. Thanks for your help, everything is fixed now, even my service is back!
Will you provide the link when you can?
I could use a link as well :|
Sitting ducks until i can flash stock back on.
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
NateAC said:
Hey, this forum looks really helpful, but unfortunately the stock firmware zip link isn't working for me. Is there any other place that you might suggest getting it from? I do have two of the same phone if it's possible to retrieve the firmware from another one, but I wiped my first one which is why I'm here in the first place. Thanks!
*EDIT: Hey, no worries, I found another file of the same type, but I can't post the link yet. (Follow the Moto E 2015 thread to general to "| Read Before You Flash | Unlock | Restore | Stock Firmware |," follow the link there, and find the other, newer, XT1526 file.) I just installed the drivers, got the minimal adb/fastboot zip, and followed the commands given above. Thanks for your help, everything is fixed now, even my service is back!
Click to expand...
Click to collapse
is there any way you could pm me a link to a working xt1526 rom?
Download link is updated.
Does this remove account information and installed apps? Do you have to activate phone with Boost again or no?
Nevermind. I just went for it and the answer is Yes, it removes accounts and installed apps.
And No, you do not have to re-register with Boost Mobile. Full system restore.
Confirm working for Boost Mobile XT1526 CDMA LTE.
Thanks so much for this thread. You're going to save SO many devices!
After flashing this my stock recovery gives me a dead android (on it's back with red triangle) How can I get stock recovery back? Can I flash stick recovery via adb?
Edit: So after further Googling, my understanding is that the red triangle android is supposed to be there... but I've tried all the suggested button presses to get the actual menu to appear. I'm trying to get the menu on the Moto E 2015 CDMA LTE Boost Mobile.
Can someone tell me the actual button combination to get the stock recovery menu to appear?
Edit: OMFG! People are so stupid... I'm going to make my own youtube video and post it for our phones.... All of the guides were wrong!
To enter recovery menu (after android with red triangle is displayed) press and hold power for 3 seconds, then tap the volume up once.
I will post a video on how to do this for moto e 2015 CDMA XT1526. Hope this helps anyone else who was confused/concerned about their stock recovery partition not working after flashing back to pure stock.
Edit: Here's the video of how to access the contextual menu of Recovery on the Moto E 2015 4G LTE CDMA Boost Mobile variant (XT1526)
http://youtu.be/gffx5CN9wF4
Help with Fastboot Errors
There are errors when running some of these commands on my phone the rest of the commands seem to run fine. Hope to resolve or confirm they are simply to be ignored. I would like to confirm all partitions are re-written factory for troubleshooting purposes. Thanks.. These are the only errors...
Windows 8.1
Fastboot download from this post.
Driver Motorola ADB interface v2.0.2.0 - If in question please confirm this or post directly to drivers that I can manually install to know I'm running. The MOTO software install hides everything so I'm just not sure what it's doing exactly.
D:\ADB>fastboot erase D:\ADB\XT1526\modemst1
erasing 'D:\ADB\XT1526\modemst1'...
(bootloader) Invalid partition name D:\ADB\XT1526\modemst1
FAILED (remote failure)
finished. total time: 0.016s
D:\ADB>fastboot erase D:\ADB\XT1526\modemst2
erasing 'D:\ADB\XT1526\modemst2'...
(bootloader) Invalid partition name D:\ADB\XT1526\modemst2
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot erase D:\ADB\XT1526\cache
erasing 'D:\ADB\XT1526\cache'...
(bootloader) Invalid partition name D:\ADB\XT1526\cache
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot erase D:\ADB\XT1526\userdata
erasing 'D:\ADB\XT1526\userdata'...
(bootloader) Invalid partition name D:\ADB\XT1526\userdata
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot oem config D:\ADB\XT1526\carrier
...
(bootloader) Not allowed command
FAILED (remote failure)
finished. total time: 0.016s
Hmmm. I followed this exact guide and it worked flawlessly
deansouth8 said:
There are errors when running some of these commands on my phone the rest of the commands seem to run fine. Hope to resolve or confirm they are simply to be ignored. I would like to confirm all partitions are re-written factory for troubleshooting purposes. Thanks.. These are the only errors...
Windows 8.1
Fastboot download from this post.
Driver Motorola ADB interface v2.0.2.0 - If in question please confirm this or post directly to drivers that I can manually install to know I'm running. The MOTO software install hides everything so I'm just not sure what it's doing exactly.
D:\ADB>fastboot erase D:\ADB\XT1526\modemst1
erasing 'D:\ADB\XT1526\modemst1'...
(bootloader) Invalid partition name D:\ADB\XT1526\modemst1
FAILED (remote failure)
finished. total time: 0.016s
D:\ADB>fastboot erase D:\ADB\XT1526\modemst2
erasing 'D:\ADB\XT1526\modemst2'...
(bootloader) Invalid partition name D:\ADB\XT1526\modemst2
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot erase D:\ADB\XT1526\cache
erasing 'D:\ADB\XT1526\cache'...
(bootloader) Invalid partition name D:\ADB\XT1526\cache
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot erase D:\ADB\XT1526\userdata
erasing 'D:\ADB\XT1526\userdata'...
(bootloader) Invalid partition name D:\ADB\XT1526\userdata
FAILED (remote failure)
finished. total time: 0.000s
D:\ADB>fastboot oem config D:\ADB\XT1526\carrier
...
(bootloader) Not allowed command
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
You're entering the commands incorrectly. For example, the first command in your example should be "fastboot erase modemst1", not "fastboot erase D:\ADB\XT1526\modemst1". Enter the commands as shown in the first post of this thread.
Brainfart bigtime. Thanks for the catch. I'm going to get the tire pump for a refill.
If you do this after updating to 5.1 ota will the phone still work correctly?
Meaning you will be back to stock recovery, stock system, stock firmware, and Android 5.1 OS?
Question?
imprint89 said:
No. There are certain steps to relock the bootloader, but it does no good now. You can still OTA with an unlocked bootloader, but as far as factory warranty goes, its void as soon as you unlock it. The only reason you would ever want to relock it is if you were giving the phone to someone who didn't know anything about rooting our phones.... it just doesn't do any good.
Click to expand...
Click to collapse
Can i just put the lock bootloader command first,then put the rest of the commands or is this not digitally signed
Help: XT1511 bricked
Hello, my XT1511 has been bricked, had installed CM12.1 and TWRP but the error information to be going to an external hard drive via a laptop with ubuntu mate is present. My terminal only presents the logo of the brand and enter fastboot, have tried to follow the steps but I get errors that you can not write to the device, the debug options and OEM you were disabled so the OEM unlock does not work how I can get my device?
Regards.
Related
I downloaded CWM for Moto G from clockworkmod's rom manager site. My intent was to backup the entire phone, including the ISP's ROM, before rooting or even unlocking the bootloader. I didn't know whether I could avoid unlocking the bootloader, but I was going try backing up without flashing to the device to see if it would let me. I put the phone in fastboot mode by holding down the power button and volume-down for 10 seconds. Then I issued the following from the command line (I'm using cygwin's bash shell, and the directory containing fastboot is in $PATH):
$fastboot boot recovery-clockwork-6.0.4.7-falcon.img
downloading 'boot.img'...
OKAY [ 0.310s]
booting...
FAILED (remote failure)
finished. total time: 0.313s
Is this the symptom of not having unlocked the bootloader?
P.S. I want to back up the phone rather than get an ISP's stock from online.
BUMP.
Anyone?
my1stSmartPhone said:
I downloaded CWM for Moto G from clockworkmod's rom manager site. My intent was to backup the entire phone, including the ISP's ROM, before rooting or even unlocking the bootloader. I didn't know whether I could avoid unlocking the bootloader, but I was going try backing up without flashing to the device to see if it would let me. I put the phone in fastboot mode by holding down the power button and volume-down for 10 seconds. Then I issued the following from the command line (I'm using cygwin's bash shell, and the directory containing fastboot is in $PATH):
$fastboot boot recovery-clockwork-6.0.4.7-falcon.img
downloading 'boot.img'...
OKAY [ 0.310s]
booting...
FAILED (remote failure)
finished. total time: 0.313s
Is this the symptom of not having unlocked the bootloader?
P.S. I want to back up the phone rather than get an ISP's stock from online.
Click to expand...
Click to collapse
Yes, an unlocked bootloader is a requirement for being able to install a custom recovery on those phones, and most every Android device with a few exceptions. Keep in mind that unlocking the bootloader will reset the phone as well.
Sent from my A0001 using XDA Premium 4 mobile app
es0tericcha0s said:
Yes, an unlocked bootloader is a requirement for being able to install a custom recovery on those phones, and most every Android device with a few exceptions. Keep in mind that unlocking the bootloader will reset the phone as well.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, es0tericcha0s. I think I need to clarify: For the backup, I just want to "soft" boot CWM, I don't want to flash it to the phone. I want to back up the phone in its entirety with as little modification to it as possible. Is this possible without unlocking the bootloader?
my1stSmartPhone said:
Thanks, es0tericcha0s. I think I need to clarify: For the backup, I just want to "soft" boot CWM, I don't want to flash it to the phone. I want to back up the phone in its entirety with as little modification to it as possible. Is this possible without unlocking the bootloader?
Click to expand...
Click to collapse
I'm not sure if you need the bootloaders unlocked to just fastboot boot recovery, but I would think you still would need to. It'll either work or just reboot the phone normally so very little risk of anything bad happening were you to try it. From a couple threads I found, the ability to do that also depends on which bootloader you have (4.3 or 4.4.2) and the recovery img as well.
es0tericcha0s said:
I'm not sure if you need the bootloaders unlocked to just fastboot boot recovery, but I would think you still would need to. It'll either work or just reboot the phone normally so very little risk of anything bad happening were you to try it. From a couple threads I found, the ability to do that also depends on which bootloader you have (4.3 or 4.4.2) and the recovery img as well.
Click to expand...
Click to collapse
Interesting. It neither soft boots to the img file nor does it reboot. It simply fails.
> $fastboot boot recovery-clockwork-6.0.4.7-falcon.img
> downloading 'boot.img'...
> OKAY [ 0.310s]
> booting...
> FAILED (remote failure)
> finished. total time: 0.313s
How does one find the bootloader version? Turning off the device and holding Power + VolumeDown for 10 seconds leads to a "fastboot" mode, which has a version number that is very different from the bootloader versions that you cited:
> AP Fastboot Flash Mode (S)
> 41.13(*) (sha-7dc8e78, 2014-06-1616:33:29)
The image I'm trying to soft boot is recovery-clockwork-6.0.4.7-falcon.img.
my1stSmartPhone said:
Interesting. It neither soft boots to the img file nor does it reboot. It simply fails.
> $fastboot boot recovery-clockwork-6.0.4.7-falcon.img
> downloading 'boot.img'...
> OKAY [ 0.310s]
> booting...
> FAILED (remote failure)
> finished. total time: 0.313s
How does one find the bootloader version? Turning off the device and holding Power + VolumeDown for 10 seconds leads to a "fastboot" mode, which has a version number that is very different from the bootloader versions that you cited:
> AP Fastboot Flash Mode (S)
> 41.13(*) (sha-7dc8e78, 2014-06-1616:33:29)
The image I'm trying to soft boot is recovery-clockwork-6.0.4.7-falcon.img.
Click to expand...
Click to collapse
You'll know which bootloader you're on by which update you're on. 4.3 or 4.4.2, but I just don't think it'll work without unlocking the bootloader regardless. You realize that besides wiping the data (which you can back up most of it other ways anyway...)that unlocking the bootloader makes no other changes to the operating system so if you were to do that and and then, once you perform a nandroid backup, you'll have a copy of an unaltered OS?
es0tericcha0s said:
You'll know which bootloader you're on by which update you're on. 4.3 or 4.4.2, but I just don't think it'll work without unlocking the bootloader regardless. You realize that besides wiping the data (which you can back up most of it other ways anyway...)that unlocking the bootloader makes no other changes to the operating system so if you were to do that and and then, once you perform a nandroid backup, you'll have a copy of an unaltered OS?
Click to expand...
Click to collapse
I'm on 4.4.4.
I suspected that the OS is not changed by unlocking the bootloader. I just wanted to delay the warranty-voiding step of unlocking the bootloader until as far along the process as possible, in case I got cold feet after doing the full backup of the entire phone. Looks like I can't delay it until after the backup. Ah well, it's only a $150 phone.
Funny, though, the error indicates that it's downloading boot.img. Almost as if it was interpreting the 1st parameter as the boot image instead of a fastboot command. That's now how fastboot is suppose to work.
my1stSmartPhone said:
I'm on 4.4.4.
I suspected that the OS is not changed by unlocking the bootloader. I just wanted to delay the warranty-voiding step of unlocking the bootloader until as far along the process as possible, in case I got cold feet after doing the full backup of the entire phone. Looks like I can't delay it until after the backup. Ah well, it's only a $150 phone.
Funny, though, the error indicates that it's downloading boot.img. Almost as if it was interpreting the 1st parameter as the boot image instead of a fastboot command. That's now how fastboot is suppose to work.
Click to expand...
Click to collapse
Might try it with the Motorola fastboot files: mfastboot
http://forum.xda-developers.com/attachment.php?attachmentid=2427667&d=1385958280
same commands, just do "mfastboot" vs "fastboot"
But the "downloading...." part is not uncommon. Found references in various threads.
Looks like mfastboot doesn't work either. Same results. Next step: Unlock bootloader.....
Afternote: It worked! At the shell on the PC:
> $ fastboot oem unlock FLRPKG3ZYPCPLOBYXY3T
> ...
> (bootloader) Unlock code = FLRPKG3ZYPCPLOBYXY3T
> (bootloader) Unlock completed! Wait to reboot
> FAILED (status read failed (Too many links))
> finished. total time: 20.842s
The device rebooted into fastboot mode with the following details:
> <...snip...>
> Device is unlocked. Status Code: 3
> <...snip...>
> Fastboot Reason: UTAG *flashfail* configured as fastboot
> USB connected
I'm not too worried about the "status read failed" because others have encountered it [google "Rooting my Moto E out of the box (step by step)"]. Also, I'm not going to worry about the "UTAG *flashfail*" message just yet.
UNFORTUNATELY...
...booting CWM without flashing to the Moto G does not work:
> $ fastboot.exe boot recovery-clockwork-6.0.4.7-falcon.img
> downloading 'boot.img'...
> OKAY [ 0.300s]
> booting...
> OKAY [ 0.240s]
> finished. total time: 0.540s
The device simply boots up as normal.
hello I try everything and cant make my phone to work, I'm asking to somebody if can help me to upload a moto e 2nd gen. XT1526 SPRINT Backup, I made my backup and save it in a different sd card but for some reason, it wipe it and delete everything on the memory
Are you asking for someone to link you to the ROM you need? I'm not following you.
Mdkcheatz said:
Are you asking for someone to link you to the ROM you need? I'm not following you.
Click to expand...
Click to collapse
sorry, I didn't be to explicit, yea Im asking to somebody to link me a rom or a nandroid backup or a twrp backup of the moto e tx1526 cdma sprint, because I already try almost all of the roms and non of them still working for me, and I delete accidently my own backup.
or probably still not release some sprint rom's?
I didn't find your specific ROM yet but there were XT1526 ROMs which may help from this note I made for myself back when I needed mine... Its possible that a similar ROM may work for you. Just make sure you are using GSM version if you are GSM and vice versa: Installing incompatible firmware can lead to hard bricking.
Do not rely on these links to last. Some are already down.
RETUS = Retail US
TMO = T-Mobile
This is the only source of leaked Moto E Firmware. Some Links are down. The XT1527 TMO (T-Mobile subsidy) version works but it may lock only to Tmobile. I assume you can flash to any of those carriers to inherit their subsidy.
FileFactory
Flashing a compatible ROM will not:
Mess up Fastboot
Lock bootloader (it is possible to lock it, however, locking* the bootloader could screw up your last chance of restore.
Flash a compatible ROM will:
Overwrite Recovery (easily reflashed)
Remove Root (easily reflash)
Reset everything to near factory settings.
Fix Baseband
To reflash ROM:
I've put together some commands that are needed to flash the rom files. Copy and save as [any_file_name].bat
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Save .bat file to the same directory as the rom files.
Have Fastboot installed.
Have Moto Drivers installed.
Boot Moto into Fastboot mode
Load terminal and confirm connection to device. (Type "fastboot devices")
$cd into a folder with extracted .xml files.
In terminal, type [name_you_gave_file].bat and it should automatically start flashing the rom files.
Reboot phone and it should be* restored.
---------- Post added at 12:28 AM ---------- Previous post was at 12:26 AM ----------
Sorry the link didn't parse:
http://www.filefactory.com/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=2
Try one of these three XT1526 ROMS (actually 2: the boost subsidy version won't help you obviously)
Good luck!
luzbel3821 said:
sorry, I didn't be to explicit, yea Im asking to somebody to link me a rom or a nandroid backup or a twrp backup of the moto e tx1526 cdma sprint, because I already try almost all of the roms and non of them still working for me, and I delete accidently my own backup.
or probably still not release some sprint rom's?
Click to expand...
Click to collapse
Hi, did you manage to solve your issue? I am also in the same boat, looking forsprint moto e stock 5.1 firmware or comatible. Didyou have any success?
dreckgos said:
Hi, did you manage to solve your issue? I am also in the same boat, looking forsprint moto e stock 5.1 firmware or comatible. Didyou have any success?
Click to expand...
Click to collapse
rom for sprint didn't come out yet, but this rom work perfect on sprint network http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
its on the last post by Mdkcheatz, just follow the instruccions
luzbel3821 said:
rom for sprint didn't come out yet, but this rom work perfect on sprint network http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
its on the last post by Mdkcheatz, just follow the instruccions
Click to expand...
Click to collapse
Hm, I tried the 5.1 boost ROM from the same site, but I got a bootloop if only flashing system and hang on boot if following the full process....
dreckgos said:
Hm, I tried the 5.1 boost ROM from the same site, but I got a bootloop if only flashing system and hang on boot if following the full process....
Click to expand...
Click to collapse
Huh, I tried again and this time it worked. The problem was that previously I used a script to flash and it did not include a fastboot invocation for the last piece of the system image.
Yea that does to me too, but don't use BOOST 5.1 instead use Boost 5.0.2 and once you started it will ask you on your phone to OTA upgrade
dreckgos said:
Huh, I tried again and this time it worked. The problem was that previously I used a script to flash and it did not include a fastboot invocation for the last piece of the system image.
Click to expand...
Click to collapse
but no luck for me getting this message, any solution?
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.358s
alshanu said:
but no luck for me getting this message, any solution?
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.358s
Click to expand...
Click to collapse
Did you make sure to unlock your bootloader?
Also, you shouldn't bump a year-old topic.
xtermmin said:
Did you make sure to unlock your bootloader?
Also, you shouldn't bump a year-old topic.
Click to expand...
Click to collapse
Ya I gave up. Thank you
Long story short, I tried to flash new rom on my Mt2-L02 mate2 and failed and its bootlooping (at Huawei Ascend screen and keep rebooting) now. using the SDcard udload to load new rom don't work either. I cannot go into recovery, or boot into system.
My phone is bootloader unlocked, so I tried to flash (extract from a rom) boot.img, recovery.img and is ok but when flashing system.img, it stucked in writing 'system'... for long time.... so I tried fastboot erase system -w and get FAILED (remote: Command not allowed)... why is it so? my phone is already unlocked. I tried unlock again and flash the system.img, same problem.
So... I'm screwed?
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
kimtyson said:
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
Click to expand...
Click to collapse
Only have 1 pc, yes, I'm flashing MT2-L02 ROM, tried alot of version but discovered only these version rom (b408, b603, b606, b607) able to write the system.img, original out of box android version for my phone is 4.4.2. but still bootlooping after flashing boot.img, recovery.img and system.img. I think only custom recovery can save now, but there is none for this model... or maybe there is no hope for my phone? Maybe my phone got some system modified lock so that I'm not able to erase using flashboot?
C:\adb>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
C:\adb>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
If I'm able to erase those, I'm might solved the bootlooping problem..
Try using this thread as reference, http://forum.xda-developers.com/asc...to-fix-soft-bricked-phone-using-twrp-t2886630. It's for a different model so just use your stock ROM in place of the L03 ROM. I'm not sure how to help beyond that. There has to be a way to return to stock on the L02.
Maybe this message is late, pls try following
http://pan.baidu.com/s/1dDpc4eP
http://www.huaweirom.com/rom/mate2/2619.html
usb flash instructions:
http://www.huaweirom.com/guide/2621.html
You may need to use google translate since all the info is in Chinese
Basically they are saying you should use B117 if B4xx not working.
Hi,
I followed this article -> phandroid DOT com/2014/11/05/how-to-root-nexus-9/ (Sorry, new account, can't link) to the letter, and everything seemed to go well, until the last step where I ran "fastboot reboot" which returned "error: device not found" I thought nothing of this as there was a reboot option on the devices screen, so I rebooted, I get the google logo, followed by the four orbs, then it says "Optimising app x of 99" once this is done, its back to the orbs again and it just repeats.
I tried restoring to factory defaults from the recovery menu, that did nothing, then sometime after I noticed I actually cant turn the device off any more, if I hold the power button it turns off, but reboots instantly. I tried going through the steps again, but no luck, the only change was that I didn't have the error at the end, and the first Optimising dialogue said 104 apps, not 99, but all the rest afterwards have said 99.
I'm not sure what do do from here, any advice?
Here's my cmd output:
Code:
## First attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot bootloader
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
...
(bootloader) ability is 1
(bootloader) RUU_frame_buffer_enable_flag=0
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Unlock device successfully!
OKAY [ 23.489s]
finished. total time: 23.489s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot nexus9\inject.img
downloading 'boot.img'...
OKAY [ 0.783s]
booting...
OKAY [ 0.156s]
finished. total time: 0.939s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot nexus9\patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.541s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.798s]
finished. total time: 1.339s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
## Second attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
< waiting for device >
...
(bootloader) ability is 1
(bootloader) Device stete is unlock already
OKAY [ 0.141s]
finished. total time: 0.141s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
downloading 'boot.img'...
OKAY [ 0.749s]
booting...
OKAY [ 0.158s]
finished. total time: 0.908s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.539s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.787s]
finished. total time: 1.326s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot reboot
rebooting...
finished. total time: 0.066s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Try returning to stock and trying again. See method 2 of this, http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 9 using XDA Free mobile app
That root method is for the old 5.0 Android; it doesn't work anymore with 5.1.1. Go back to stock using jd1639's link, then run Chainfire's Auto-root and you should be good to go. Link is here: https://download.chainfire.eu/595/CF-Root/CF-Auto-Root/CF-Auto-Root-flounder-volantis-nexus9.zip. There's supposedly an update coming in the next week or so to fix the stagefright vulnerability, make sure you do NOT take it in case it does weird things that could cause you to lose root.
(I know it says Volantis and not flounder but the Nexus 9 is known by both names, just to keep things confusing)
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
TheShryke said:
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
Click to expand...
Click to collapse
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
bynarie said:
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
Click to expand...
Click to collapse
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
bynarie said:
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
Click to expand...
Click to collapse
Just take notice that this will wipe everything on your device, so make a backup first.
dictionary said:
Just take notice that this will wipe everything on your device, so make a backup first.
Click to expand...
Click to collapse
cobyman7035 said:
...
Click to expand...
Click to collapse
Yes, my apologies... I forgot to mention this. You will definitely want to pull any pictures or other files you might want to keep from the /sdcard partition. Or anything else because ALL DATA WILL BE WIPED.
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU? do i need to wipe dalvik or cache?
im installing that huge android SDK studio setup into my laptop for prep
cobyman7035 said:
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU?
Click to expand...
Click to collapse
Here > https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
ok i just unlocked my bootloader....so i rebooted in android again...i have to go back and enable usb debugging and developers again?
---------- Post added at 10:16 AM ---------- Previous post was at 10:01 AM ----------
when i typ adb reboot fastboot. ...my n9 reboots into the android o.s and NOT into fastboot?
---------- Post added at 10:23 AM ---------- Previous post was at 10:16 AM ----------
nm i installed and flash twrp and SU! i didn't do a dalvik cache wipe...is that ok? booting in android o/s again to setup!
my next step is to go unencrypted... don't wanna setup too many apps cuz its just gonna be all deleted again
Hello guys...
So, without going too much into details of how I idiotically f-ed up pretty much everything... I just want to say that I've already lost about 12 hours reading through the forum trying to solve the problem and to understand how everything works, and by what I understood... I bricked the phone?
Firstly, I managed to unlock the bootloader with the HCU Client (Phone unlocked, FRP unlocked). At some points I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
I've tried hard but never managed to boot any of the Custom ROMs available, especially the LineageOS 16 which I wanted but later on, through a specific TWRP which gave an error information that it's meant for Hisilicon, and not for Kirin SoC...
I also had no idea when I was booting into recovery, and when into erecovery, because I flashed TWRP over both of them... I have really no idea what was the last thing to happen, but now it seems as if I can't boot into eRecovery anymore, and whatever I try flashing to the recovery_ramdisk over Fastboot, I just always get the same error when trying to boot into recovery
Error! Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Now I'm also having an issue because my battery has drained and it doesn't seem to turn on without it being connected to the charger or a PC.
Is there anything that I can do to make it work with any Custom ROM?
returnedinformation said:
I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
Click to expand...
Click to collapse
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
-Alf- said:
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
As I said before
-Alf- said:
some people posting nonsense here.
Click to expand...
Click to collapse
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
I see. Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons:
1. Bootloader isnt "fully" unlocked, please check with the unlocking guide/service provider (if unlock was a paid service)
2. Bootloader is in "retail" mode, not a "service" mode. Some manufacturers do not intend for bootloader to be unlocked, and ship the devices with a restricted "retail" version that blocks certain commands.
also, why is your fastboot sending the "boot.img" while the command had " twrp img" as a payload?
I take it the bootloader still lets you use the "flash" command? If true, flash TWRP temporarily by "fastboot flash boot twrp.img", restart teh phone using the recovery menu keycombo
returnedinformation said:
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
Click to expand...
Click to collapse
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Totesnochill said:
Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons
Click to expand...
Click to collapse
No, there is only one reason - on Huawei devices we do not have a "boot" partition since Android 7.
-Alf- said:
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Click to expand...
Click to collapse
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Personally i had a xiaomi poco f2 pro 6/128 and then i bought another same model phone but 8/256 from a fellow who almost bricked his phone..it was just blinking, when i restarted the phone, it went straight into blinking whenever i tried to boot into recovery, and it wouldnt boot into system anyway cos there was nothing there. so i figured it was stuck in recovery loop.
i was fortunate that i was able to hook up to it using my pc...then using command prompt, i was able to switch to fastboot mode..then i tried downloading and flashing different twrps, over 10 different twrps, and finally one worked..then it was smooth sailing from then on..and presto, that became my daily use phone.
returnedinformation said:
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
Click to expand...
Click to collapse
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
flashgordon65 said:
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Click to expand...
Click to collapse
-Alf- said:
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
Click to expand...
Click to collapse
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
returnedinformation said:
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
Click to expand...
Click to collapse
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
-Alf- said:
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
Click to expand...
Click to collapse
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
Sorry!
fastboot erase userdata
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
returnedinformation said:
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
Click to expand...
Click to collapse
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
-Alf- said:
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
Click to expand...
Click to collapse
I've tried both, they give me the same error.
After I flash the recovery I can't really reboot straight into recovery because of the issue with the battery... somehow I gotta hold the Volume UP key, while catching exact moment when I can unplug USB after the low battery status page passes, and before Huawei logo appears...
After unlocking the phone I flashed TWRP over either recovery or erecovery (idk anymore)... then I probably installed Pixel Experience 13 ROM (https://github.com/ponces/treble_build_pe/releases)
And after that... I tried too many things I can't even remember anymore.
returnedinformation said:
then I probably installed Pixel Experience 13 ROM
Click to expand...
Click to collapse
Under EMUI 8 ??? Which TWRP?