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.
Hello
I wanted to speed up the TF201 with the help of the Kernel Adjutor. Something went wrong and after a series of frustrated attempts the only thing I get after starting the TF 201 are
- the ASUS /nvidia screen with the message "the device is unlocked"
- 4 penguins with a text "3.xxxxx message length: 9" (xxxxx being random numbers)
- the blue "teamwin" screen.
I cannot get into any other screen by pressing the volume up or down.
In June 2017 I have installed KatKiss 7.1 v023 following your tutorial. I have also made the backup recommended there.
How do I have to proceed to get the TF201 back to normal ?
Thank you very much for your help.
SwissJames
You might have to bring it back using a PC/Laptop along with Minimal ADB and Fastboot, you would have to wipe it and in the process loss everything.
Is your back-up on an external media like the micro SD or SD card?
NP
Hello Nektopoli
Thanks for your support.
backup files "bricksafe.img", "factory-config.img" and "unlock-token.img" are on the PC.
I still have the original files on micro SD from the upgrade to Android 7.1 Nougat as described in the tutorial.
After much research and many unsuccessful tries, it seems that I get lucky with lj50036's post: https://forum.xda-developers.com/showthread.php?t=2538028. After following his instructions it I was able to boot into fastboot.
At the step "fastboot -w" I got stuck: erasing cache "Command write failed <unknown error>"
So I closed the terminal and opened a new one (as described).
"fastboot erase boot" failed again "Command write failed <unknown error>"
Restarting the PC fixed the issue.
I managed to get the other steps done as well.
Now the tablet is working again with Android 4.1.1.
Next I'll upgrade it back to 7.1
Regards
SwissJames
swissjames said:
Hello Nektopoli
Thanks for your support.
backup files "bricksafe.img", "factory-config.img" and "unlock-token.img" are on the PC.
I still have the original files on micro SD from the upgrade to Android 7.1 Nougat as described in the tutorial.
After much research and many unsuccessful tries, it seems that I get lucky with lj50036's post: https://forum.xda-developers.com/showthread.php?t=2538028. After following his instructions it I was able to boot into fastboot.
At the step "fastboot -w" I got stuck: erasing cache "Command write failed <unknown error>"
So I closed the terminal and opened a new one (as described).
"fastboot erase boot" failed again "Command write failed <unknown error>"
Restarting the PC fixed the issue.
I managed to get the other steps done as well.
Now the tablet is working again with Android 4.1.1.
Next I'll upgrade it back to 7.1
Regards
SwissJames
Click to expand...
Click to collapse
Have you updated the bootloader to 10.6.1.27.1 and installed the TWRP recovery console?
NP
No, not yet. As I flashed the tab with the official ASUS firmware, everything has gone. Bootloader is 10.4.2.18 and the TWRP recovery console is gone. (RCK ends up with a "dead" android...). I'll follow the latest version of the tutorial https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237 to upgrade the tab.
Can you access the tablet via a computer/laptop using and ADB fastboot program like "Minimal ADB and Fastboot" https://forum.xda-developers.com/showthread.php?t=2317790
If you can, you could manually wipe the tablet, and flash JB Bootloader 10.6.1.27.1 and TWRP 2.5, then update the TWRP and install 7.1
NP
I almost got through the guide till chapter 8. Trying to install the open_gaaps-arm 7.1 pico I got the error msg "insufficient storage space available in System partition". The error log is attached.
Maybe you have an idea what I could delete on the System partition (and how). I have tried e.g. to get rid of the gmail account, but without success.
You should wipe the system partition before flashing the ROM, SuperSU and GAPPs using TWRP when you flash a new ROM
Alternatively, if you're using a PC and Fastboot to install the ROM
the: [fastboot erase system] command will wipe the system, but I don't think it will change the System partition to F2FS
NP
I have wiped all partitions before proceeding.
The size of my "system" partition after wiping is 503 MB (8 MB used) with ext4 (510 / 116 MB used with f2f). So I opted for the ext4-variant as described in the guide.
After installing KatKiss-7.1_TF201_026.zip, 433 MB are used in "system"
After installing SuperSU-v2.82.zip, 440 MB are used in "system".
So there is not enough space left for open_gaaps-arm-7.1_pico.zip with about 125 MB unzipped.
Is there a way to increase the size of the "system" partition ? (there is enough space left in the "data" partition where I could take some...)
Or do you see other options ?
Can you get back into the recovery console?
NP
yes I think so.
By pressing power and volume - I got to the selection screen and chose RCK. Now I am in TWRP again.
When you boot into the fastboot screen, the one with the RCK icon you should see the bootloader version at the top of the screen, what version is your tablet on?
this is what mine looks like
NP
it says
<1.00 e> released by "ww_epad-10.4.2.15-20120917" A03
sj
I checked the configuration of the bootloader before I began with the upgrade from 4.1. It said 10.4.2.18-20112122...
sj
What version TWRP do you have working now?
Ok, with the working TWRP you can flash the new Bootloader v10.6.1.21.1 found here;
https://androidfilehost.com/?fid=23060877490002899
This will also install TWRP 2.5 at this point we don't want to install any thing else. Once you are on the correct bootloader and TWRP 2.5 you will need to update TWRP in two steps. First to TWRP 2.8.5.1 and then to TWRP 3.1.0-1 once you have a working TWRP you can wipe the TF and flash the 7.1.2 ROM.
NP
As you suggested I downloaded the zipped file and put it on the pc and on the sd-card.
Swiped it with the twrp 3.1.0-1 from the sd-card
looked ok. Requested reboot.
The blue line appeared. It took no time at all to complete.
Now the I am on the asus-screen
reboot to get to see the version. still 10.4.2.15 with twrp 3.1.0-1
next try: installing the bootloader with cmd.exe
typed on pc: "adb devices"
response:
"list of devices attached"
"015d0787774bf603 recovery"
typed: "adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard" (the one I got from the site you indicated)
response: "1325 KB/s" etc -> looks as transferred to sdcard
on tab: "installing files.."
"done..."
"now please restart..."
"updating partition details..."
"...done"
reboot to get to see the version.
screen says
"OS will cold boot in 10 seconds if no input is detected"
"booting recovery kernel image"
Version is still 10.4.2.15 with twrp 3.1.0-1
That is so bizarre that it wont update the bootloader or downgrade the TWRP.
One way to fix this is to do a FULL "adb wipe"
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
This will wipe the complete table back to nothing.
Then:> adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard
This should get you on the correct bootloader and TWRP, after this boot into fastboot to confirm you're on the correct bootloader then flash 3.1.0-1
NP
I did what you suggested and erased all the files ->worked well.
Then "adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard" -> got an error: "device not found"
I restarted the tab and then clicked on the USB-symbol.
"adb devices" showed an empty list of devices attached.
"fastboot -i 0x0b05 flash recovery flatline_TF201.img" gave "OKAY" and "writing recovery"
Bootloader is still 10.4.2.15
On the tab I am now on Flatline CWM Recovery v1.0RC1
TWRP is gone.
"adb devices" shows "0123456789ABCDEF recovery"
again "adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard" success ! Data were copied.
reboot. Bootloader is still on 10.4.2.15
nBootloader should now be in the /sdcard
next intent:
"fastboot -i 0x0b05 flash recovery flatline_TF201.img" gave "OKAY" and "writing recovery"
restart, then to RCK - flatline CWM recovery
install zip from sdcard -> no files found
got in advanced - wheelie - I accept the above statement - flash androidRoot BL power off
-> blue progress line is almost empty. then progress line disappears, ASUS screen shows up.
In Flatline recovery tried "install zip from sdcard" - "choose zip from sdcard".
only "- AndroidRoot/" is shown. (no nHairyBean_Bootloader_TWRP2.5.zip). So no way of installing the nHairyBean_Bootloader-
On one hand, it seems that I am able to establish a connection between the PC and the tab when in RCK, but when in USB, the connection seems not possible.
Hmmm...
Maybe I am missing something basic in this whole thing that keeps me from progressing.
What if I use the backup-files and try to go back to the initial configuration of the TF201 ? Or are there other options with the CWM-Recovery ?
Regards sj
That sounds like the best idea, going back to the stock ROM, they can be found here; https://www.asus.com/Tablets/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/
Download the version for you region install and see if you can get back to stock.
NP
I downloaded the file you indicated. Now how do I get it into use ?
I cannot get into APX-mode
the only program working in the tab seems to be the flatline CWM Recovery v1.0RC1.
I tried to send the zip-file with "adb sideload <filename>" Error: failed to write data 'protocol fault <no status>'
I copied the zip-file to the external sd-card, but do not see how I can access it. The sd-card mentioned on screen ("Apply update from .zip file on SD card")seems to be an internal storage.
Hi,
I have unlocked bootloader, installed TWRP recovery, flashed image "AospExtended" and started the device w/o issues.
Then I enabled device encryption, entered the password and the device started to reboot.
However it did not reach the phase where the password must be entered.
Instead, it ends up in a boot loop where the display shows "Kindle" and then reboots.
I can boot into both fastboot and recovery.
But even after deleting everything in TWRP and installing "AospExtended" image again, the boot loop is still there.
How can I fix this?
c.monty said:
Hi,
I have unlocked bootloader, installed TWRP recovery, flashed image "AospExtended" and started the device w/o issues.
Then I enabled device encryption, entered the password and the device started to reboot.
However it did not reach the phase where the password must be entered.
Instead, it ends up in a boot loop where the display shows "Kindle" and then reboots.
I can boot into both fastboot and recovery.
But even after deleting everything in TWRP and installing "AospExtended" image again, the boot loop is still there.
How can I fix this?
Click to expand...
Click to collapse
Yeah, encryption is not supported. You will need to format (vs. simply wipe) the system and/or data partitions. There was a recent discussion that addresses the commands needed. I will try to scare up a link and add to this post (check for updates).
Edit: This post should supply what you need; be sure to whap the 'thanks' button for @draxie if it solves your problem.
I boot into recovery, but then there's an issue with adb shell:
Code:
[email protected]:~/Hardware/Amazon/thor$ adb shell su -c "make_ext4fs /dev/block/mmcblk0p23"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Could I format this partition in fastboot, too?
Or in TWRP?
In recovery I tried to fix the bootloop issue by deleting/formating any partition.
Then, when I plugin the device to USB, I can only transfer data via file manager, means adb is not working.
Any file can be copied over to device (using file manager) and installed in TWRP.
A fool with a tool...
c.monty said:
Code:
error: device unauthorized.
Click to expand...
Click to collapse
Right... if you bothered checking that thread
for *all* the relevant messages, you would've
realized that the person with the encryption
problem had rolled back to Lineage 13; so, adb
with TWRP was not an issue for them...
Luckily, for you, that's not actually necessary.
c.monty said:
Could I format this partition in fastboot, too?
Click to expand...
Click to collapse
Probably not, although you could try
Code:
fastboot -i 0x1949 erase userdata
and hope that AEX does the right thing
and formats the partition as required.
c.monty said:
Or in TWRP?
Click to expand...
Click to collapse
Yes, of course, you can, but I'd prefer
that you tried the fastboot method first
and report back if that worked (since
that's simpler and would be helpful
for others stuck in the same place).
Code:
[email protected]:~$ fastboot -i 0x1949 erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.085s]
finished. total time: 0.085s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.320s
Reboot is successfull.
THX
Hi, on this phone there was a Lineage 16 9.0, but for a problem I had to reset everything and miflash the rom again mido_global_images_V10.2.3.0.NCFMIXM_20190128.0000.00_7.0_global. It was to put the Gcam. Now I'm trying to start over and get the recovery twrp, but it always fails.
I've tried with Fastboot Tool and with platform-tools, but it always fails.
At the command 'fastboot devices' sees the phone, instead at the command 'fastboot flash recovery recovery.img' sees the recovery ok, but when it has to write it says 'FAILED (remote: 'Partition flashing is not allowed')'
How do I solve it?
Unlock bootloader after flashing MIUI stock ROM.
After that again attempt to install TWRP.
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?