Related
First off, the original thread is here: http://forum.xda-developers.com/showthread.php?t=1950232
It looks like some users are having an issue with the following results:
1. Unable to boot into Fastboot - HAS SINCE BEEN FIXED
2. Unable to wipe/flash from CWM
3. Unable to wipe /cache or /data
We aren't sure if this is a hardware issue or a software issue, but we are trying to figure it out.
I am running Epinter CM10 (from early september), and I hadn't flashed a new version of the rom since then. A couple days ago my phone started giving me a bunch of errors (application crashes) so I decided to update to the latest version and wipe. After wiping, and flashing, I rebooted and everything looked the same. All my applications were still on lancher and all my texts were there. So it clearly didnt work, when I went back into CWM I tried wiping specific partitions manually and found there were errors when trying to format /data and /cache. Trying to reboot into Fastboot it gets stuck at "starting fastboot protocol support", and never is detectable from command prompt.
My first question - Are there any ways to wipe the Atrix outside of CWM and Fastboot? Would flashing a SBF from RSD do anything? (I am already rooted which you probably knew from the fact im running epinter CM10)
Has anyone found themselves in this situation and found a fix?
Thanks for your help.
Firstly, questions go to the Q&A section.
Secondly, I've faced this issue a few weeks ago where nothing happens when I wipe everything and flash a new ROM. But miraculously my restore worked and then everything went smooth after that. I came from Epinter's CM10 as well, I restored to Maxblur I think. Now on MROM, flashing still works.
If you have the time and are desperate to flash something, you can try to SBF back to your previous firmware. Only problem is, you might need to wipe you phone using... fastboot.
I'm not sure though, it might be a hardware issue.. Besides, my digitizer is failing and my wifi disables and locks itself every now and then...
Edit: Reading you post in that other thread, you mentioned that your phone went into "starting USB protocol". Do you have the correct drivers loaded on your computer? Have you tried reinstalling CWM or another recovery?
Sent from that Atrix.
Thank you for your reply. The reason I moved it here was that some others had this issue with epinter and it straddled the lines of Dev and Q&A, and there wasn't much exposure on the Q&A forum and it seemed that others using epinter were having this issue.
1. I will try a restore and report back on if that worked (I tried restoring before which resulted in a failure when it gets to /data)
2. I will double check fastboot is properly installed.
3. I will also try flashing the CWM non-touch version
**Edit**
Update to item 1:
I tried restoring a backup on CWM and got the following log:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
Error while formatting /data!
boot in fastboot your atrix. power on + vol down, then when show fastboot press vol up. then in windows cmd write this commands.
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (reboot to recovery)
Flash ROM.
if doesnt work try with moto-fastboot program and moto-fastboot commands, mine atrix worked fine
try installing another recovery i get this same error its work for me
I got fastboot working, and this is the error I get when trying to wipe:
fastboot -w
erasing 'userdata'...
OKAY [ 1.021s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 0.333s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.018s]
finished. total time: 1.403s
***Update
Well, after wiping twice, I rebooted the phone... and all my icons are still there, my phone still has my text messages and calls and all the applications. So something is not working right.
sjbayer3 said:
I got fastboot working, and this is the error I get when trying to wipe:
fastboot -w
erasing 'userdata'...
OKAY [ 1.021s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 0.333s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.018s]
finished. total time: 1.403s
***Update
Well, after wiping twice, I rebooted the phone... and all my icons are still there, my phone still has my text messages and calls and all the applications. So something is not working right.
Click to expand...
Click to collapse
I always thought we needed to use moto-fastboot, not just fastboot.
I also used romracers recovery and then Th3Bill's Full_Wipe flashable wipe tool to recover from a similar situation.
Good luck.
Okay.
I found moto-fastboot, and using that STILL nothing gets wiped.
I tried flashing the non-touch recovery, and well it shows everything success... but when I open recovery its still the touch recovery.
It just seems like something is locking me out from doing any wipe or flash to my phone, I am just baffelled that nothing has worked so far.
Trying to format from fastboot and I got this output, type ".FAILED ()" certainly doesn't sound good.
C:\Users\ofsstbay>fastboot format userdata
formatting 'userdata' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.014s
C:\Users\ofsstbay>fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.012s
C:\Users\ofsstbay>fastboot format system
formatting 'system' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.010s
In addition, when I flash recovery:
C:\Users\ofsstbay\Desktop>fastboot flash recovery recovery-clockwork-5.0.2.0-oly
mpus.img
sending 'recovery' (4824 KB)...
OKAY [ 0.280s]
writing 'recovery'...
OKAY [ 0.125s]
finished. total time: 0.415s
On the phone screen it says:
Flashing partition recovery
Flashing StorMgr partition: SOS
Belongs in Q&A. I closed other one since this has more replies. There aren't any exceptions for organization on the forums. Please do not post questions in Development even if they "straddle the lines." Thanks!
Same issue here! I was on uriels awezome rom when it happened. I've tried fastboot, and even rsd lite wiping everything at once, individually to no avail.
Well I even tried going through the originaly root unlock and recovery flash and still didn't do anything. None of my backups work either still
any one figure this out yet??? I can't think of anything else to try myself.
is it possible that the internal sd is corrupted and possible the data partition as well?
I was thinking the internal card was corrupt as well.
Is this something that can be removed and replaced or is it built into the board?
i looked that up. I saw a different phone where it is removable but not necessarily replaceable. I know there is a way to use the sd card as the internal but the directions are above me. I wish some devs were reading this thread. Doesn't seem like it's got enough interest from the people who could really help.
Be nice if we knew what caused this. I don't know what the three of us could have done to cause these problems. I have scoured google for answers and ways to repartition and tried so many things and I am giving up.
Hi guys,
So, I'll start by saying I haven't seen this problem before. And, if I had to venture a guess, I'd say your hardware is borked (not being able to format is a big clue).
But, there are some things to discuss and try before you use your devices as paperweights.
First, no one has mentioned the OS and version of your PCs. You must have the correct version of fastboot running with the correct drivers.
Second, fastboot and moto-fastboot are nearly identical, so don't expect different results. The only noteworthy difference is that moto-fastboot can handle large images like system and webtop.
Third, I recommend avoiding touch recoveries. The best ones are still sketchy and it is very easy to do things accidentally. There is a reason that button CWM makes you scroll through 10 "no" before you get to "yes".
__________________
Please do the following:
1) Ensure that you are in fact running the correct version of fastboot with the correct drivers for your PC. Be 100% certain.
2) Enter fastboot mode and do "fastboot devices" (no quotes) and make sure your device is recognized.
3) If your device is properly recognized, try this:
a) "fastboot erase cache"
b) "fastboot erase userdata"
c) "fastboot erase boot"
d) "fastboot erase system"
e) "fastboot reboot"
After fastboot reboot does your device boot to OS, or stay on the boot logo? If your device stays on the boot logo, you wiped your OS (which is good).
Next install the most recent CWM button recovery.
If that works, flash a stable ROM. Nothing experimental - try a stock GB ROM (fruit cake, NottachTrix, etc.) or CM7 and see how things go.
There is some useful fastboot information available here.
I went through the steps as you asked...thank you for helping out by the way. I issued all the fastboot commands and said they were completed but it booted back up to the same rom that I had before I started. I downloaded and installed the drivers again based on your link on another thread.
edit: Oh yeah and I'm running windows 7.
upndwn4par said:
First, no one has mentioned the OS and version of your PCs. You must have the correct version of fastboot running with the correct drivers.
Second, fastboot and moto-fastboot are nearly identical, so don't expect different results. The only noteworthy difference is that moto-fastboot can handle large images like system and webtop.
There is some useful fastboot information available here.
Click to expand...
Click to collapse
Thank you for your response, that link lists drivers 5.1.0_64bit, but I have 5.4.0_64bit. Are you saying we should be running the older version?
Thanks for the help!
**Edit**
So I went through the steps with both the 5.1.0 and 5.4.0 drivers and neither actually wiped the cache/userdata/boot/system.
boonemeat said:
I went through the steps as you asked...thank you for helping out by the way. I issued all the fastboot commands and said they were completed but it booted back up to the same rom that I had before I started. I downloaded and installed the drivers again based on your link on another thread.
edit: Oh yeah and I'm running windows 7.
Click to expand...
Click to collapse
sjbayer3 said:
Thank you for your response, that link lists drivers 5.1.0_64bit, but I have 5.4.0_64bit. Are you saying we should be running the older version?
Thanks for the help!
**Edit**
So I went through the steps with both the 5.1.0 and 5.4.0 drivers and neither actually wiped the cache/userdata/boot/system.
Click to expand...
Click to collapse
No. A newer version is fine, as long as you are using the correct drivers.
______________
What Recovery were you both using? I think one of you mentioned touch CWM.
______________
Have either of you tried Th3Bill's wiping tools? (I use them all the time)
Another way to install recovery would be via ROM Manager.
The title basically describes my problem, essentially I some how managed to completely filled up my internal storage and now my phone will not start. I did try formatting but it give me error make_ext4fs failed on /dev/block/etc etc
Any clue on what I should do?
S-OFF HBOOT 1.93.0002
Mobilicity Stock ICS Rooted
4EXT Recovery
dpsi said:
The title basically describes my problem, essentially I some how managed to completely filled up my internal storage and now my phone will not start. I did try formatting but it give me error make_ext4fs failed on /dev/block/etc etc
Any clue on what I should do?
Click to expand...
Click to collapse
Did you try boot into recovery & delete unwanted data?
dpsi said:
The title basically describes my problem, essentially I some how managed to completely filled up my internal storage and now my phone will not start. I did try formatting but it give me error make_ext4fs failed on /dev/block/etc etc
Any clue on what I should do?
Click to expand...
Click to collapse
I'm going to list the following commands you should do. I assume that you know how to use Fastboot and the like and already have the drivers set up. If not, there are threads out there that explain in detail on how to do that.
Ensure the battery is fully charged before doing anything
Take out the battery and reinsert it. Hold the Vol Down button and press power button. This will take you into bootloader mode. Use the Volume Up/Down buttons in the bootloader mode to boot into FASTBOOT mode. You will know if you're in the fastboot mode when you see the text "FASTBOOT" highlighted in RED. If you see the text "BOOTLOADER" highlighted in BLUE, you are NOT in fastboot mode.
After you have entered fastboot mode, plug in the usb cable. The highlighted "Fastboot" text should change into "Fastboot USB". After that, open the command prompt. You should have had the fastboot drivers set up before starting this.
Input the following commands EXACTLY (including their respective case):
fastboot erase cache
fastboot erase system -w
After that's done, reboot into recovery and re-install your ROM of choice. NOTE: Upon doing those fastboot commands, you will lose all of your data and your ROM on the phone.
crazykas said:
Did you try boot into recovery & delete unwanted data?
Click to expand...
Click to collapse
If formatting won't work, how do you think I can delete files?
Keylogger_0 said:
fastboot erase cache
fastboot erase system -w
Click to expand...
Click to collapse
Code:
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.000s
Any other ideas?
dpsi said:
If formatting won't work, how do you think I can delete files?
Code:
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.000s
Any other ideas?
Click to expand...
Click to collapse
Run this tool http://forum.xda-developers.com/showthread.php?t=1762936
Take note that this installs a tmobile ruu so you need supercid. Be sure to follow instructions.
Sent from my Amaze using xda app-developers app
Keylogger_0 said:
Run this tool http://forum.xda-developers.com/showthread.php?t=1762936
Take note that this installs a tmobile ruu so you need supercid. Be sure to follow instructions.
Sent from my Amaze using xda app-developers app
Click to expand...
Click to collapse
That did it, thanks.
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.
C:\Android>fastboot devices
317251cf fastboot
C:\Android>fastboot erase data
erasing 'data'...
FAILED (remote: Check device console.)
finished. total time: 0.004s
Hello,
I want to erase data because i can't do this unbrick method (https://forum.xda-developers.com/one...lus-6-t3796665)
despite that it worked before.
(and the Msm recovery don't work)
this problem appeared after many successful uses of the method mentioned above. The problem appeared after wanting to install an older rom on my OP6 for downgrade the play services
I am desperate, I searched for hours and hours on the internet so if a little genius goes through, a little help would not be refused
Awehweh said:
C:\Android>fastboot devices
317251cf fastboot
C:\Android>fastboot erase data
erasing 'data'...
FAILED (remote: Check device console.)
finished. total time: 0.004s
Hello,
I want to erase data because i can't do this unbrick method (https://forum.xda-developers.com/one...lus-6-t3796665)
despite that it worked before.
(and the Msm recovery don't work)
this problem appeared after many successful uses of the method mentioned above. The problem appeared after wanting to install an older rom on my OP6 for downgrade the play services
I am desperate, I searched for hours and hours on the internet so if a little genius goes through, a little help would not be refused
Click to expand...
Click to collapse
Flash a compatible recovery first by dv minimal tools from PC to phone,in fastboot mode,if you cannot enter in twrp
Sent from my LEX820 using Tapatalk
bilausdaniel said:
Flash a compatible recovery first by dv minimal tools from PC to phone,in fastboot mode,if you cannot enter in twrp
Sent from my LEX820 using Tapatalk
Click to expand...
Click to collapse
it dont work, its possible to have recovery stock ?
Awehweh said:
it dont work, its possible to have recovery stock ?
Click to expand...
Click to collapse
Don't know about stock twrp...ask in telegram group.but you tried latest official twrp to flash it by adb in fasboot mode?press volume up and power both time 15 seconds,
Sent from my LEX820 using Tapatalk
bilausdaniel said:
Don't know about stock twrp...ask in telegram group.but you tried latest official twrp to flash it by adb in fasboot mode?press volume up and power both time 15 seconds,
Sent from my LEX820 using Tapatalk
Click to expand...
Click to collapse
yes i already did it
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?