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.
Related
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
pim8181 said:
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
Click to expand...
Click to collapse
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
kilroystyx said:
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
Click to expand...
Click to collapse
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
pim8181 said:
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
Click to expand...
Click to collapse
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
kilroystyx said:
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
Click to expand...
Click to collapse
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
pim8181 said:
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
Click to expand...
Click to collapse
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
pim8181 said:
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
Click to expand...
Click to collapse
No, you are doing right. Can you post the output from fastboot during the installation?
kilroystyx said:
No, you are doing right. Can you post the output from fastboot during the installation?
Click to expand...
Click to collapse
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
pim8181 said:
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
Click to expand...
Click to collapse
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
kilroystyx said:
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
Click to expand...
Click to collapse
It didn't work , maybe I can flash the stock system image from fastboot?
pim8181 said:
It didn't work , maybe I can flash the stock system image from fastboot?
Click to expand...
Click to collapse
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
kilroystyx said:
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
Click to expand...
Click to collapse
I don't know how to get these ones can you explain it to me?
pim8181 said:
I don't know how to get these ones can you explain it to me?
Click to expand...
Click to collapse
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
kilroystyx said:
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
Click to expand...
Click to collapse
It worked, many thanks for your help!
For those that have issues with the programme, I had to uncheck the verify header checksum button in the settings file in order for it to work properly.
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
pim8181 said:
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
Click to expand...
Click to collapse
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
kilroystyx said:
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
Click to expand...
Click to collapse
My TWRP is completely lost and the tool doesn't seem to work, I wiped data cache and dalvik.
When you flash a rom aren't you just supposed to flash the rom itself, when I bricked my phone by installing Xposed I just reflashed the rom it's sytem image and a boot image. How should I do it?
I am new here and this was my first time actually trying any of this. I have my bootloader code, if that helps.
Phone turns on to erecovery mode if powered on normally. Running erecovery downloaded and installed RNE-L21 8.0.0.355(C185). It then asked me to Factory reset, after which it booted back in to erecovery. I can put phone in FASTBOOT&RESCUE MODE by plugging it in to PC and holding power + vol. down.
About Phone
-code
DC-unlocker:
manufacturer - Huawei phones
model - Huawei phone in fastboot mode
Found Phone : RNE-L21
Model : Huawei phone in fastboot mode
IMEI : 868859036054492
Serial NR. : FFY5T18224032295
Firmware : RNE-L21 8.0.0.355(C185
IMEI1:868859036074508
FB LockState: LOCKED
I wanted to downgrade from Oreo to Nougat.
To unlock bootloader, I used Potatonv:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
I installed the TWRP in this post:
TWRP For Mate 10 lite 8.0 Oreo Version For RNE-L21C185
Here is twrp for HUAWEI MATE 10 LITE. Who want? Comment Here. :p
forum.xda-developers.com
I booted in to TWRP with
-code
adb reboot recovery
I made a backup using TWRP but I lost it and couldn't make another one because of some error in TWRP.
I then installed magisk .zip file through TWRP.
The phone would boot in TWRP no matter which option I chose in the Reboot menu of TWRP. Being really impatient, I decided to flash another version of TWRP on recovery partition, with SD card, through TWRP itself. I got this 2nd TWRP from:
How to Install TWRP Recovery and Root Huawei Mate 10 Lite
In this article, we will guide you on how to root Huawei Mate 10 Lite and Install TWRP Recovery.
clickitornot.com
The new TWRP doesn't work and phone does not show bootloader unlocked warning anymore. Upon rebooting after new TWRP, phone showed this error first few times.
I'm not really sure what to do but I figured I'd run some commands that might help someone figure out what I should do.
fastbootoem get-product-model:
(bootloader) RNE-L21
OKAY [ 0.025s]
finished. total time: 0.026s
fastboot getvar vendorcountry:
vendorcountry: hw/meafnaf
finished. total time: 0.025s
fastboot oem get-build-number:
(bootloader) :RNE-L21 8.0.0.355(C185)
OKAY [ 0.026s]
finished. total time: 0.027s
fastboot getvar rescue_enter_recovery:
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.063s
fastboot oem oeminforead-SYSTEM_VERSION:
(bootloader) :RNE-L21 8.0.0.348(C185CUSTC185D1)
OKAY [ 0.031s]
finished. total time: 0.031s
I believe the rom for my phone is
RNE-L21 8.0.0.348(C185CUSTC185D1)I have downloaded it from https://gsmfreehelperteam.blogspot.com/2020/04/rne-l21-800348c185custc185d1-file-by.html but I really don't know what to do with it and I don't want to mess it up any further. Sorry for the long read, any help would be great.
brokenpotato said:
Upon rebooting after new TWRP, phone showed this error first few times.
Click to expand...
Click to collapse
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
brokenpotato said:
I wanted to downgrade from Oreo to Nougat
Click to expand...
Click to collapse
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
-Alf- said:
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
Click to expand...
Click to collapse
"fastboot flash recovery RECOVERY_RAMDISK330.img" gives:
target reported max download size of 471859200 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.055s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.067s
brokenpotato said:
Command not allowed
Click to expand...
Click to collapse
= Locked bootloader or FRP lock
-Alf- said:
= Locked bootloader or FRP lock
Click to expand...
Click to collapse
IT does say "FRP Unlock" in red on fastboot&rescue screen. Should i try fastboot oem unlock?
brokenpotato said:
Should i try fastboot oem unlock?
Click to expand...
Click to collapse
Why not?
Fastboot oem unlock *************** worked, the phone booted up in to android and is working normally. Thank you so much!!
brokenpotato said:
Fastboot oem unlock *************** worked, the phone booted up in to android and is working normally. Thank you so much!!
Click to expand...
Click to collapse
No problem.
-Alf- said:
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
Click to expand...
Click to collapse
When trying to flash the TWRP, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'recovery' (24790 KB)...
OKAY [ 0.794s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.809s
brokenpotato said:
fastboot flash recovery TWRP-oreo-smart.img
Click to expand...
Click to collapse
Read carefully.
brokenpotato said:
When trying to flash the TWRP, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'recovery' (24790 KB)...
OKAY [ 0.794s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.809s
Click to expand...
Click to collapse
Just realized I had to flash twrp on recovery_ramdisk and not on recovery. It works like a charm
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.
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?
Hey,
I recently unlocked my P20 lite with the potatoNV tool. Everything worked fine so far, afterwards I flashed DarkJoker360's TWRP 3.4 and booted into it.
After I tried to flash various Rom's but none of them working (all are stuck on "Your device is booting now").
After reading through various threads about related issues, I stumbled across the necessity to downgrade to EMUI 8.0.126 for a lot of roms to work.
Long story short, I'm trying to recover the stock rom in order to downgrade but it won't work.
what I tried so far:
extracting update.zip and
fastboot flash cust CUST.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash system SYSTEM.img
fastboot flash vbmeta VBMETA.img
didnt work either (same version as is on the phone of course, always stucks at kernel.img --> "image verification error")
twrp flashing stock rom, kernel etc.. not working.
only thing that works is fastboot flash recovery_ramdisk twrp.img and it works fine. anything else just doesnt.
any ideas?
thanks
elgatofeliz said:
Hey,
I recently unlocked my P20 lite with the potatoNV tool. Everything worked fine so far, afterwards I flashed DarkJoker360's TWRP 3.4 and booted into it.
After I tried to flash various Rom's but none of them working (all are stuck on "Your device is booting now").
After reading through various threads about related issues, I stumbled across the necessity to downgrade to EMUI 8.0.126 for a lot of roms to work.
Long story short, I'm trying to recover the stock rom in order to downgrade but it won't work.
what I tried so far:
extracting update.zip and
fastboot flash cust CUST.img
fastboot flash kernel KERNEL.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash system SYSTEM.img
fastboot flash vbmeta VBMETA.img
didnt work either (same version as is on the phone of course, always stucks at kernel.img --> "image verification error")
twrp flashing stock rom, kernel etc.. not working.
only thing that works is fastboot flash recovery_ramdisk twrp.img and it works fine. anything else just doesnt.
any ideas?
thanks
Click to expand...
Click to collapse
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.
Some might fail, so don't worry about it.
Hi Alf,
here's the results (in same order as you posted them):
(bootloader) :ANE-LX1 9.1.0.401(C432E13R1P7)
(bootloader) ANE-LX1
vendorcountry: hw/eu
FAILED (remote: 'The reason of failed input oem_nv_item error!')
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
thank you
elgatofeliz said:
Hi Alf,
here's the results (in same order as you posted them):
(bootloader) :ANE-LX1 9.1.0.401(C432E13R1P7)
(bootloader) ANE-LX1
vendorcountry: hw/eu
FAILED (remote: 'The reason of failed input oem_nv_item error!')
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
thank you
Click to expand...
Click to collapse
Okay, try some of the following:
1. reboot into eRecovery and use option "Download latest version etc."
2. Download Service ROM
flash it using dload mode (the process will lock your BL !)
3. flash TWRP 3.2.1 by pretoriano80 (can be found here
and follow
instructions .
I hope your phone is dual SIM .
somehow the service rom worked after flashing ANE-8 files from here (before it didn't at all)
Custom ROM installation Problems on P20 Lite
Hello developers, I bought a Huawei P20 lite a few days ago after verifing, that lineage is possible to install on those phones. Now, after struggling for 3 days to install lineage, I decided to post here. First some information about my phone...
forum.xda-developers.com
(post No 9)