Hi guys,
I’m trying to ho from 8.0.0.336 to 8.0.0.321 , i have the stock ROM for RNE-L22 8.0.0.321 and tried to do this via dload but it fails on 37% everytime.
Tried extraxting the following images from upload.app and do fastboot flash CUST.img, recovery.img and system.img, it goes through but on boot it shows the 8.0.0.336
Any thoughts?
Thanks
Rezarz77 said:
it fails on 37% everytime.
Click to expand...
Click to collapse
possible reasons (IMO):
1. phone connected to PC during update
2. corrupted update file on SD card
Rezarz77 said:
CUST.img, recovery.img and system.img
Click to expand...
Click to collapse
+ kernel.img and ramdisk.img
-Alf- said:
possible reasons (IMO):
1. phone connected to PC during update
2. corrupted update file on SD card
+ kernel.img and ramdisk.img
Click to expand...
Click to collapse
Thank for that, i did kernel and ramdisk too, now it goes to e recovery, i tried to clear cache and factory reset but it restarts and again and goes back to erecovery. Tried to flash fastboot and vendor but it says its not allowed, also cant get oem device info -> it says remote not allowed but its unlocked.
Frp and bootlaoder shows unlocked in fastboot mode!
Any other thoughts?
Thanks in advance for helping me out!
Rezarz77 said:
also cant get oem device info -> it says remote not allowed but its unlocked.
Click to expand...
Click to collapse
Try commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
-Alf- said:
Try commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
Click to expand...
Click to collapse
fastboot oem get-build-number
...
(bootloader) :RNE-L22 8.0.0.338(C636)
fastboot oem get-product-model
...
(bootloader) RNE-L22
fastboot getvar vendorcountry
vendorcountry: hw/spcseas
fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: The reason of failed input oem_nv_item error!)
fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :RNE-L22 8.0.0.338(C636CUSTC636D1)
Rezarz77 said:
i have the stock ROM for RNE-L22 8.0.0.321
Click to expand...
Click to collapse
Can you give me a link?
Have you folloved instructions to the letter?
Have you followed the instructions to the letter?
-Alf- said:
Can you give me a link?
Have you folloved instructions to the letter?
Have you followed the instructions to the letter?
Click to expand...
Click to collapse
https://dl.gsm-cloud.com/dl/HUAWEI/alk/Rhone-L22%208.0.0.321%28C636CUSTC636D1%29_Firmware_05014SWC_2.zip
I tried dload method and it failed, so i tried flashing through fastboot, apart from main update.app there is a update_RNE-L22_hw_spcseas.app as well which i'm not to sure what i should do with it.
I'm total noob and first time ever flashing a ROM, I would appreciate if you could point me to a right direction
cheers
Rezarz77 said:
https://dl.gsm-cloud.com/dl/HUAWEI/alk/Rhone-L22%208.0.0.321%28C636CUSTC636D1%29_Firmware_05014SWC_2.zip
I tried dload method and it failed, so i tried flashing through fastboot, apart from main update.app there is a update_RNE-L22_hw_spcseas.app as well which i'm not to sure what i should do with it.
I'm total noob and first time ever flashing a ROM, I would appreciate if you could point me to a right direction
cheers
Click to expand...
Click to collapse
See your P.M.
Related
Hi! As the title stated, my phone is bricked after trying to install custom roms.
My phone is unlocked and it keeps booting to twrp after I wiped system.
I can still access fastboot though.
bigbau said:
Hi! As the title stated, my phone is bricked after trying to install custom roms.
My phone is unlocked and it keeps booting to twrp after I wiped system.
I can still access fastboot though.
Click to expand...
Click to collapse
it is difficult for anyone to help you without relevant information - your build number, EMUI version etc.
You should use the folloving commands in fastboot mode and then post the results:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar version
fastboot getvar vendorcountry
-Alf- said:
it is difficult for anyone to help you without relevant information - your build number, EMUI version etc.
You should use the folloving commands in fastboot mode and then post the results:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar version
fastboot getvar vendorcountry
Click to expand...
Click to collapse
I managed to fix it by using this: https://forum.xda-developers.com/huawei-p20-lite/development/compilation-firmware-flash-emui-8-0-0-t3819642
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
Hello,
- 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:
Hello,
- 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
Hi, thanks for your fast answer!
fastboot oem get-build-number
Code:
(bootloader) :System 8.0.0.046(09B8)
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem get-product-model
Code:
(bootloader) ANE-LX1
OKAY [ 0.011s]
finished. total time: 0.011s
fastboot getvar vendorcountry
Code:
vendorcountry: ti/it
finished. total time: 0.012s
fastboot oem oeminforead-CUSTOM_VERSION
Code:
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.019s
fastboot oem oeminforead-SYSTEM_VERSION
Code:
(bootloader) :ANE-LX1 8.0.0.151(C55)
OKAY [ 0.013s]
finished. total time: 0.014s
I don't know why but the CUSTOM_VERSION reading failed...
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
-Alf- said:
What is (was) your region in your phone build number ? (for example C432, C10, C185...)
Click to expand...
Click to collapse
I think it's C55 , correct me if I'm wrong...
-Alf- said:
according to the results from the fastboot you have a branded phone, maybe a single sim?
Good news is that you are still on A8, bad news is "ti/it ".
Try this :
- Download and flash stock recovery_ramdisk for Oreo
recovery_ramdisk
Use command
fastboot flash recovery_ramdisk (file_name).img
Then try boot into recovery and let me know, thanks.
Click to expand...
Click to collapse
I tried, but doesn't work at all...
-Alf- said:
I think it's C55 , correct me if I'm wrong...
Click to expand...
Click to collapse
Yeah, it is C55. I don't know what to do anymore
andreasaracino said:
I tried, but doesn't work at all...
Yeah, it is C55. I don't know what to do anymore
Click to expand...
Click to collapse
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
andreasaracino said:
Hi everyone.
Yesterday I unlocked the bootloader of my P20 Lite through DC-Unlocked (paid 4 euro) and I rooted it by flashing a patched ramdisk. It was on android 8 because I had to roll back the version to allow DC-Unlocker to get the bootloader code. Anyways, I wanted to upgrade to android 9.0 again but I ran into a major issue. Like an idiot, I tried flashing the update through the TWRP, and so now the phone is hard bricked.
On boot, I get the ERROR MODE screen which gives
Code:
Func NO: 10(recovery image)
Error No: 2(load failed!)
I tried flashing every single .img possible from the UPDATE.APP, but that doesn't do the trick. One thing that I've noticed is that the RAMDISK partition seems to have vanished, because when I try to flash it through fastboot, it gives me
Code:
FAILED (remote: partition length get error)
So I don't actually know how to flash the boot partitions, which is probably the culprit of the issue. I can only flash KERNEL.img but not RAMDISK.IMG.
Oh, and also, as you may have guessed, I can't even boot in recovery anymore.
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Anyone had this experience? Thanks in advance.
Click to expand...
Click to collapse
I did this once to my kiwi (5x) then it went totally blank when i tried flashing an Huawei related system flashing tool. Do not try that.
-Alf- said:
recovery_ramdisk installing using command fastboot flash recovery_ramdisk etc.
was unsuccessful?
Have you tried boot into eRecovery? There's an option in eRecovery "Download latest ....."
Click to expand...
Click to collapse
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
andreasaracino said:
I can't manage to boot in eRecovery, I always get the Func No error...
But the flashing was successful, only it doesn't fix the issue with the recovery.
Click to expand...
Click to collapse
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
-Alf- said:
Okay, try this way out...
- download Service ROM
- unpack, extract from UPDATE.APP files:
CUST.img, RAMDISK.img, SYSTEM.img , RECOVERY_RAMDISK.img using Huawei update extractor, and flash .img files through fastboot. (CUST.img can be found in second UPDATE.APP (update_sd_ANE-L01_hw......zip) folder.
Click to expand...
Click to collapse
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
andreasaracino said:
Now I'm trying to download a FULLOTA-MF which, they say, should unbrick the phone via forced DLOAD method.
Click to expand...
Click to collapse
andreasaracino said:
Thank you very much Alf for your time, but I finally managed to unbrick the phone by dloading the FULLOTA-MF of which I wrote about in OP.
Click to expand...
Click to collapse
then it is not FULLOTA-MF but Service ROM, bro ...okay, it doesn't matter now.
A friend gave me her P20 lite that doesn't boot anymore with the error "verification has failed" and goes into boot loop whatever you do
1) erecovery won't boot
2) hisuite is not supported
3) fastboot works but I can't flash anything cause the bootloader is locked
Is there something I can do to access in any way the sdcard partition at least or only the official service can do it?
That's the main goal here, I would also like to restore the ROM but I guess if I could it will inevitably erase all data.
Thanks to anyone who can help.
More information about your phone is needed - in fastboot mode run commands (use "Minimal ADB and fastboot" tool on PC) :
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.
Some might fail, so don't worry about it.
-sandro- said:
Is there something I can do to access in any way the sdcard partition at least
Click to expand...
Click to collapse
I'm not sure I fully understand your question...do you mean internal storage ?
-sandro- said:
I guess if I could it will inevitably erase all data.
Click to expand...
Click to collapse
Bingo!
Yes the internal storage that is usually called /sdcard, not sure how Huawei calls it, I've never owned a Huawei smartphone
I will post the commands results ASAP, thanks!
Hello - it's been about 10 years since I played with any XDA stuff or custom roms. I have a stock Motorola G Power that bricked itself. It will not boot and recovery mode just gives me "No Command". Only option seems to be factory data reset.
Can anyone suggest a procedure to allow me to either re-install the stock software to get into the phone or recover my data? Sadly I had not backed anything up since last summer.
Should I just try to reflash a stock rom to see if i can get in? Will flashing the rom kill the onboard storage?
Cant find the exact same version either:
SOFIA10/QPMS30.80-63-6-8-5
I found 63-6-8-10 and 63-6-8-3 but not the exact same. Phone is Retail US.
Any help would be appreciated.
Ok found the stock rom that matches 63-6-8-5. Do I just try to flash that back to get back into the phone with my existing data?
Uberhare said:
Ok found the stock rom that matches 63-6-8-5. Do I just try to flash that back to get back into the phone with my existing data?
Click to expand...
Click to collapse
You can try flashing the stock from and just skip the erase userdata step.
The firmware contains a file named flash_file.xml contains the flash commands
You can use Online FlashFile Converter to convert the .XML to simple fastboot commands.
You also should check if getvar is-userspace
Code:
fastboot getvar is-userspace
if yes you need to switch between fastboot and fastbootd
If it's no you don't need to worry about fastbootd
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
You can try flashing the stock from and just skip the erase userdata step.
Click to expand...
Click to collapse
Do I need to unlock the bootloader for flashing an original file?
Uberhare said:
Do I need to unlock the bootloader for flashing an original file?
Click to expand...
Click to collapse
No, you shouldn't need to but it's easier if the bootloader is unlocked.
Unlikely, you can unlock the bootloader now anyways.
Unless you enabled OEM Unlocking in Dev Options already.
If you did enable OEM Unlocking, I would Unlock the bootloader.
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Are the steps any different if the bootloader is locked? You mention it is easier if it is unlocked.
Thank you for the tutorial.
Uberhare said:
Are the steps any different if the bootloader is locked? You mention it is easier if it is unlocked.
Thank you for the tutorial.
Click to expand...
Click to collapse
Easier may not be the right word.
If the bootloader is unlocked, you are less likely to have issues flashing.
ADB devices - does not return any devices, although I can see the phone is connected with the Motorola recovery tool.
fastboot getvar is-userspace returns:
is-userspace: no
Finished. Total time: 0.002s
I found where fastbootd is.
C:\Android>fastboot getvar is-userspace
is-userspace: yes
Finished. Total time: 0.002s
Uberhare said:
ADB devices - does not return any devices, although I can see the phone is connected with the Motorola recovery tool.
Click to expand...
Click to collapse
adb devices will not work if the device is in fastboot mode.
Use fastboot devices when it's in fastboot mode.
sd_shadow said:
adb devices will not work if the device is in fastboot mode.
Use fastboot devices when it's in fastboot mode.
Click to expand...
Click to collapse
adb devices does not show anything in either mode. That is why I looked for fastboot mode. Should I trouble shoot that first?
This is what I want with the erase commands deleted at the end? The erase commands are what will kill my data or is there something else I need to remove?
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase ddr
fastboot oem fb_mode_clear
echo Press any key to restart the phone!
pause
fastboot reboot
exit
Looks like phone doesn't respond to commands in fastbootd only normal.
I successfully ran the batch file, but the phone still doesn't boot. What is my next step? (besides throwing it against the wall!)
Phone accepts all the files for the current version of software, as well as commands to clear some of the labels. So the userdata is still there, I just can't get to it. Can you read these with a jtag like the older phones?
What if I try to roll it forward to Android 11 through the stock roms?
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?