Restore official Firmware after brick - Huawei P20 Lite Questions & Answers

Hello,
I'm really sorry to bother you on this subject but I can't get my P20lite back to the original firmware.
I tried to downgrade my phone with the firmware "Huawei P20 Lite ANE-LX1 ANE-L21 hw eu Anne-L21 8.0.0.150(C432) Firmware 8.0.0 r1 EMUI8.0" but since then I can't do anything. I can only access the erecovry. I can't do a wipe and multi-tool tells me that :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could you please direct me?
Thanks

BenouLM said:
I tried to downgrade my phone with the firmware "Huawei P20 Lite ANE-LX1 ANE-L21 hw eu Anne-L21 8.0.0.150(C432) Firmware 8.0.0 r1 EMUI8.0" but since then I can't do anything.
View attachment 5376427
Click to expand...
Click to collapse
Downgrade from EMUI 9.1 to EMUI 8 is possible through HiSuite only , or, if your bootloader is unloced, through TWRP and HuRupdater.
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:
fastboot oem get-build-number
Click to expand...
Click to collapse
(bootloader) :ANE-LGRP2-OVS 9.1.0.208
OKAY [ 0.016s]
Finished. Total time: 0.016s
Thx for your help
-Alf- said:
fastboot oem get-product-model
Click to expand...
Click to collapse
(bootloader) ANE-LX1
OKAY [ 0.000s]
Finished. Total time: 0.000s
-Alf- said:
fastboot getvar vendorcountry
Click to expand...
Click to collapse
vendorcountry: orange/all
Finished. Total time: 0.016s
-Alf- said:
fastboot oem oeminforead-CUSTOM_VERSION
Click to expand...
Click to collapse
FAILED (remote: 'Read oeminfo failed!')
fastboot: error: Command failed
-Alf- said:
fastboot oem oeminforead-SYSTEM_VERSION
Click to expand...
Click to collapse
(bootloader) :ANE-LX1 8.0.0.155(C109)
OKAY [ 0.007s]
Finished. Total time: 0.009s

BenouLM said:
I tried to downgrade my phone with the firmware "Huawei P20 Lite ANE-LX1 ANE-L21 hw eu Anne-L21 8.0.0.150(C432)
Click to expand...
Click to collapse
If I not mistaken, your region is orange all C109 , for example this one
https://androidhost.ru/TU9
But this is Oreo firmware, at the moment you need flash Pie firmware for region orange all C109 , IMO. Try google it.

-Alf- said:
But this is Oreo firmware, at the moment you need flash Pie firmware for region orange all C109 , IMO. Try google it.
Click to expand...
Click to collapse
Thx but how should i try? what should i write?

Here?

BenouLM said:
Here?
Click to expand...
Click to collapse
I'm not sure, but you can try it.

Nvm

Btw, have you tried update via eRecovery and WiFi? ("download latest version and recovery")

-Alf- said:
Btw, have you tried update via eRecovery and WiFi? ("download latest version and recovery")
Click to expand...
Click to collapse
yes but it crashes

-Alf- said:
Btw, have you tried update via eRecovery and WiFi? ("download latest version and recovery")
Click to expand...
Click to collapse
Thank you for your help. I succeeded in installing the firmware I put above
Now I have another problem, this phone is from a recycling recovery. They wanted to destroy it because the battery was dead. I changed the battery but I'm facing a google ID.
I have to do a bypass, do you have any idea?

BenouLM said:
I have to do a bypass, do you have any idea?
Click to expand...
Click to collapse
Bypass via safe mode should work, but it depends on build number, region etc.
https://frpbypass.net/frp-unlock-huawei-p20-lite-ane-lx1-downgrade-file-via-safe-mode/

-Alf- said:
Bypass via safe mode should work, but it depends on build number, region etc.
https://frpbypass.net/frp-unlock-huawei-p20-lite-ane-lx1-downgrade-file-via-safe-mode/
Click to expand...
Click to collapse
Yes it's works ! thx
Now all I have to do is sim unlock my Galaxy s5 and get the fingerprint reader from my Galaxy A50 and I'll have done the rest of the phone problems (I recycle phones that go to the scrap yard.)
Thanks a lot to you

Related

Failure to install rom Moto Z XT1650-05 Sheridan Chinese.

[SORTED OUT]
By fastboot gives the following error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and rsd lite
Does anyone know how to fix this error?
Looks like you forgot unblock your bootloader.
When I try to unlock the bootloader of this error
Can you solve this error with some command? Because the phone does not turn on.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.017s]
finished. total time: 0.019s
rodrigofvl said:
When I try to unlock the bootloader of this error
Can you solve this error with some command? Because the phone does not turn on.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options.
OKAY [ 0.017s]
finished. total time: 0.019s
Click to expand...
Click to collapse
Check screen while in bootloader. Is there green text "flashing unlock"? Or smth similar.
Try another ROM. My Moto (chinese) flash and boot only on TELUS 25.86-30.
Defaultnickname said:
Check screen while in bootloader. Is there green text "flashing unlock"? Or smth similar.
Try another ROM. My Moto (chinese) flash and boot only on TELUS 25.86-30.
Click to expand...
Click to collapse
this flashing_locked
Can you boot into recovery? Try factory reset through recovery. If there a bootloop, flash recovery, via
Fastboot flash recovery.img
Should work with locked bt and stock recovery.
Defaultnickname said:
Can you boot into recovery? Try factory reset through recovery. If there a bootloop, flash recovery, via
Fastboot flash recovery.img
Should work with locked bt and stock recovery.
Click to expand...
Click to collapse
rodrigofvl said:
Click to expand...
Click to collapse
Look at this thread:
https://forum.xda-developers.com/2015-moto-g/help/updated-moto-3-2015-stuck-bootloop-to-t3485191
did not work
SOLUTION FOR THE PROBLEM
Failure to install rom Moto Z XT1650-05 Sheridan Chinese.
https://forum.xda-developers.com/mo...-xt1650-05-t3695286/post74498676#post74498676
As I did not get able to install another rom or recover the one that was installed because of the blocked bootloader and the OEM lock and without TWRP, I was able to install by the recovery in update by the ADB and installed a modified rom to AOSP and the cellphone called, more by account of some bugs I used the fastboot boot twrp.img thread and I ran the TWRP without installing and changed to the lineageOS and installed GApps. I do not intend to use this rom for much longer until I figure out how to unlock OEM by the developer menu I'm going to stick with it I hope it helps someone. Thank you to everyone who helped me.
Tutorials that help:
https://forum.xda-developers.com/moto-z/how-to/official-moto-z-receiving-7-1-1-update-t3620742/page4
https://forum.xda-developers.com/moto-z/development/recovery-twrp-3-0-3-n1-moto-z-t3547672
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
https://forum.xda-developers.com/moto-z/development/rom-aokp-rom-moto-z-oms-substratum-t3550077
phone doesn't turn on with power button
Defaultnickname said:
Check screen while in bootloader. Is there green text "flashing unlock"? Or smth similar.
Try another ROM. My Moto (chinese) flash and boot only on TELUS 25.86-30.
Click to expand...
Click to collapse
phone doesn't turn on with power button so we can't show it but if it plugs to usb 2 port windows detect as "motorolla ADB interface" in cmd command ,we can detect it as fastboot devices, but we can't do anything because moto z with that condition, it doesn't have any Partitions
is there a problem with no solution ? :angel:
rodrigofvl said:
SOLUTION FOR THE PROBLEM
Failure to install rom Moto Z XT1650-05 Sheridan Chinese.
https://forum.xda-developers.com/mo...-xt1650-05-t3695286/post74498676#post74498676
As I did not get able to install another rom or recover the one that was installed because of the blocked bootloader and the OEM lock and without TWRP, I was able to install by the recovery in update by the ADB and installed a modified rom to AOSP and the cellphone called, more by account of some bugs I used the fastboot boot twrp.img thread and I ran the TWRP without installing and changed to the lineageOS and installed GApps. I do not intend to use this rom for much longer until I figure out how to unlock OEM by the developer menu I'm going to stick with it I hope it helps someone. Thank you to everyone who helped me.
Tutorials that help:
https://forum.xda-developers.com/moto-z/how-to/official-moto-z-receiving-7-1-1-update-t3620742/page4
https://forum.xda-developers.com/moto-z/development/recovery-twrp-3-0-3-n1-moto-z-t3547672
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
https://forum.xda-developers.com/moto-z/development/rom-aokp-rom-moto-z-oms-substratum-t3550077
Click to expand...
Click to collapse
my recovery not working.... its damaged. Do you have any solutions?

Question Fastboot loop, can't seem to find the right thing to flash

Hi, so I successfully installed TWRP from here, everything went well until this point. I flashed a more stable EU rom and then tried to flash Magisk, but when I rebooted it just went to fastboot mode.
Now everytime I try to turn it off or go back into TWRP it just goes to fastboot mode.
I have tried to flash using MiFlash but I can't seem to get the right thing to flash apparently.
When trying to reinstall TWRP
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.498s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.503s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Zelyric said:
View attachment 5448807
Click to expand...
Click to collapse
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
akins0405 said:
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
Click to expand...
Click to collapse
Reading on that post I saw that there are issues with Ryzen powered computers, and I indeed have a Ryzen CPU. Really hopes this helps, thanks for showing me regardless - ill keep you updated!
@akins0405
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try flashing you stock boot img
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
Where do I find that?
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
You have it in fastboot stock rom
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
Try to transfer the rom to the system partition
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
adb doesn't show my device under adb devices but fastboot devices does show it..
MTP also is disabled
Zelyric said:
adb doesn't show my device under adb devices but fastboot devices does show it..
Click to expand...
Click to collapse
Flash in fastboot stock boot img, can you do it
akins0405 said:
Flash in fastboot stock boot img, can you do it
Click to expand...
Click to collapse
fastboot flash b boot.img
Sending 'b' (196608 KB) OKAY [ 4.817s]
Writing 'b' FAILED (remote: '(b_a) No such partition')
fastboot: error: Command failed
nevermind, i understood the partition wrong.
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.558s]
Writing 'boot_a' OKAY [ 0.707s]
Finished. Total time: 6.103s
what now?
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try firstly erasing your recovery partition with fastboot erase recovery
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Zelyric said:
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Click to expand...
Click to collapse
I'm glad you made it, hello

How Unlock UniSOC Bootloader ?

I have a Unisoc UMS512 chipset device.
I can't unlock bootloader.
I do this link : https://forum.hovatek.com/thread-32287.html
But I take this error.
"
downloading 'unlock_message'...
OKAY [ 0.001s]
unlocking bootloader...
FAILED (remote: Unlock bootloader fail.)
finished. total time: 0.101s
"
What should I do ?
Please help me, Thanks
(Sorry my bad english)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UP UP UP. I need a help
I have unlocked my Motorola G20 with Unisoc T700 chipset with fastboot easily - without signature.bin. Then I had to follow instructions on the device to unlock. Try another USB 2.0 port and another cable too.
BASKAN53 said:
I have a Unisoc UMS512 chipset device.
I can't unlock bootloader.
I do this link : https://forum.hovatek.com/thread-32287.html
But I take this error.
"
downloading 'unlock_message'...
OKAY [ 0.001s]
unlocking bootloader...
FAILED (remote: Unlock bootloader fail.)
finished. total time: 0.101s
"
What should I do ?
Please help me, Thanks
(Sorry my bad english)
View attachment 5516217
View attachment 5516219
Click to expand...
Click to collapse
try out my post to see if it helps
Alldocube T803 Smile_1 Bootloader unlock w/ Unisoc T310
All files can be downloaded from the iplay40 tread. MUST use iPlay40 fastboot version or else it will fail using commands. Download install SpreadTrumTools-20200317.apk run command -- adb shell getprop ro.serialno Enter the serial you get from...
forum.xda-developers.com
Thread is up
I have same issue when I try to unlock bootloader of Infinix hot 11 unisoc t610 processor phone ..
Can someone help me out with this...
srinidroid said:
I have same issue when I try to unlock bootloader of Infinix hot 11 unisoc t610 processor phone ..
Can someone help me out with this...
Click to expand...
Click to collapse
I also have this device, did you find anything new aboutt unlocking?
jovisense said:
I also have this device, did you find anything new aboutt unlocking?
Click to expand...
Click to collapse
No :/
BASKAN53 said:
No :/
Click to expand...
Click to collapse
Hm i noticed that the icons on status bar is very close to edge, do u know any workaround?
BASKAN53 said:
UP UP UP. I need a help
Click to expand...
Click to collapse
Robyn_232 said:
I have unlocked my Motorola G20 with Unisoc T700 chipset with fastboot easily - without signature.bin. Then I had to follow instructions on the device to unlock. Try another USB 2.0 port and another cable too.
Click to expand...
Click to collapse
can you tell me pls how you have unlocked the bootloader of your unisoc without signature.bin?
By using fastboot.
fastboot flashing unlock_bootloader
I used this command:-
$ fastboot oem get_identifier_token
And got this in return:-
(bootloader) Identifier token:
(bootloader) 30303231364437303141323630393233
(bootloader) 313041413031424e
OKAY [ 0.022s]
Finished. Total time: 0.023s
What should I do next?
at next forget about what you have done and type: fastboot flashing unlock_bootloader
this is how i did it...
Robyn_232 said:
at next forget about what you have done and type: fastboot flashing unlock_bootloader
this is how i did it...
Click to expand...
Click to collapse
tried that didn't work
enable oem unlocking in developer settings
Robyn_232 said:
enable oem unlocking in developer settings
Click to expand...
Click to collapse
Don't you think I did it?
Got the same problem, seems like private key not working anymore for new devices
vanelizarov said:
Got the same problem, seems like private key not working anymore for new devices
Click to expand...
Click to collapse
What did you try?

ANE-LX3 Bricked Stuck in Bootloader with screen off

If anyone can help me in any way to solve this I would greatly appreciate it.
fastboot oem get-build-number:
ANE-LGRP2-OVS 9.1.0.134
fastboot oem get-product-model:
ANE-LX3
fastboot getvar vendorcountry
vendorcountry: claro/la
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'Read oeminfo failed!')
fastboot: error: Command failed
fastboot oem oeminforead-SYSTEM_VERSION:
ANE-LX3 8.0.0.152(C25CUSTC25D1)
fastboot mode recognizes it, even though the screen is off, and it still works since I flashed twrp and normal pass, but it only boots to fastboot with the screen off
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ozhkavosh said:
If anyone can help me in any way to solve this I would greatly appreciate it.
fastboot oem get-build-number:
ANE-LGRP2-OVS 9.1.0.134
fastboot oem get-product-model:
ANE-LX3
fastboot getvar vendorcountry
vendorcountry: claro/la
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'Read oeminfo failed!')
fastboot: error: Command failed
fastboot oem oeminforead-SYSTEM_VERSION:
ANE-LX3 8.0.0.152(C25CUSTC25D1)
fastboot mode recognizes it, even though the screen is off, and it still works since I flashed twrp and normal pass, but it only boots to fastboot with the screen off
View attachment 5795813
Click to expand...
Click to collapse
it looks like you installed the wrong (global) firmware. And of course, first of all, it was necessary to install TWRP, right? (I hope min. 3.5.9 version ).
Unfortunately, you have a specific regional variant (single SIM ? ). Try asking here:
https://ministryofsolutions.com/202...re-stock-rom-emui9-1-unlocked-bootloader.html
Another option is a rebrand to C432 region dual SIM:
Guide 1
Guide 2
Also you can try DC-phoenix, test-point method & board software etc.
-Alf- said:
it looks like you installed the wrong (global) firmware. And of course, first of all, it was necessary to install TWRP, right? (I hope min. 3.5.9 version ).
Unfortunately, you have a specific regional variant (single SIM ? ). Try asking here:
https://ministryofsolutions.com/202...re-stock-rom-emui9-1-unlocked-bootloader.html
Another option is a rebrand to C432 region dual SIM:
Guide 1
Guide 2
Also you can try DC-phoenix, test-point method & board software etc.
Click to expand...
Click to collapse
the problem is that it only wants to enter fastboot and the screen is still black, the testpoint also works but I don't have the filthy dongle to be able to use that mode, the device appears like this in device manager
Ozhkavosh said:
View attachment 5795917
Click to expand...
Click to collapse
You violated the partition layout. DC-phoenix is your friend, IMO.
Ozhkavosh said:
I don't have the filthy dongle
Click to expand...
Click to collapse
you don't need a dongle
-Alf- said:
You violated the partition layout. DC-phoenix is your friend, IMO.
you don't need a dongle
Click to expand...
Click to collapse
I revived it with testpoint and board software installing a development build that was the only one in that format and the mobile ended up with a rare model HB something. And then I followed guide 1 that you indicated (thank you) and it's already like LX1, but for some reason it asks me for NCK and I lost the imei 2 (maybe it's because a regional version is installed), I'll try to put a global one and incidentally update to 9.1 as it is now at 8.0
Ozhkavosh said:
I'll try to put a global one
Click to expand...
Click to collapse
C432 is a global. Flash service ROM again and do factory reset in stock Recovery (maybe it's because you was on EMUI 9.1, guide 1 is for E 8.0). Or try "Chapter 2", it works for both EMUI version.
Don't try to upgrade to EMUI 9.1 until you have a full working phone with EMUI 8.0, my advice.

[SOLVED] Unlocked P20 Lite (ANE-LX3) TWRP logo bootloop with no eRecovery

Hello!
My goal is to install the last official build of Lineage OS for ANE-LX3 which is version 16 (android 9) that I downloaded from: https://archive.org/details/lineageos20210217 (specifically https://archive.org/download/lineag...lineage-16.0-20210215-nightly-anne-signed.zip)
I did the testpoint method to unlock my bootloader and was trying to follow the Lineage OS guide from here: https://wiki.lineageos.org/devices/anne/install using latest TWRP (3.7.0).
There are issue with the guide, such as mentioning that Volume Down + Power is used to enter fastboot but it's actually Volume Up + Power (as mentioned everywhere in this forum lol) and also to use fastboot flash recovery <recovery_filename>.img but actually one must use fastboot flash recovery_ramdisk <recovery_filename>.img. Also, when I tried to follow the Format Data step, it would always hang after displaying 'done.'. Despite that issue I carried on and it successfully sideloaded the LineageOS zip as per the guide but after rebooting it would not boot into it, it would just hang on the black and orange text screen with 'Your device is booting now...'.
I started deleting more things to try to make it work and I think I deleted too much, because after doing a Advanced Wipe on everything, I started having the TWRP bootloop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Holding Power button to try to turn the unit off only cycles it and boots into TWRP logo screen.
Holding Volumn Up + Power no longer goes into eRecovery, instead it leads to the TWRP logo screen.
TWRP logo screen remains frozen, it does not show the slider nor does any tap or buttons work.
At the TWRP logo, I can see my device with adb as in recovery mode.
Fastboot has no apparent issues, so I tried rewriting TWRP to recovery_ramdisk a bunch of times, which succeeds, but it keeps freezing at the TWRP logo.
Did some searching and found this post which sounded like a similar situation https://forum.xda-developers.com/t/from-locked-bootloader-to-lineage-os-19-0-on-ane-lx3.4414089/ so I tried to follow this guide: https://www.getdroidtips.com/huawei-p20-lite-ane-lx3-firmware/ downloading the android 8 images from there, placing the DLOAD contents (tried both zipped and unzipped) onto an SD card (for example /dload/UPDATE.APP, etc.), however holding Volume Up + Volume Down + Power doesn't appear to do anything, let alone load anything from DLOAD folder.
Have not tried disconnecting the battery yet, more comfortable with a software solution but if that's what it comes down to I can try that.
Any help would be appreciated!
Thank you
Ironsmith9 said:
TWRP (3.7.0).
Click to expand...
Click to collapse
Ironsmith9 said:
Format Data
Click to expand...
Click to collapse
this is a deadly combination on stock EMUI 9 .
It's impossible to install Oreo dload ROM running EMUI 9. The problem is that dload method reguire stock Recovery on EMUI9.
Try command :
fastboot erase userdata
then try to install recovery_ramdisk.
Btw, what is you region? (Cxxx).
-Alf- said:
this is a deadly combination on stock EMUI 9 .
Click to expand...
Click to collapse
oh man what have i done
-Alf- said:
Try command :
fastboot erase userdata
then try to install recovery_ramdisk.
Click to expand...
Click to collapse
this worked!!! thank you!
-Alf- said:
Btw, what is you region? (Cxxx).
Click to expand...
Click to collapse
i'm not sure actually, how do i check this?
Ironsmith9 said:
how do i check this
Click to expand...
Click to collapse
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
Thanks again Alf, here's that info for completeness:
Code:
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-build-number
(bootloader) :ANE-LX3 9.1.0.313(C792E6R1P3)
OKAY [ 0.005s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-product-model
(bootloader) ANE-LX3
OKAY [ 0.003s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot getvar vendorcountry
vendorcountry: cityfone/ca
Finished. Total time: 0.004s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :ANE-LX3-CUST 9.1.0.6(C792)
OKAY [ 0.010s]
Finished. Total time: 0.011s
Ironsmith9 said:
Thanks again Alf, here's that info for completeness:
Code:
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-build-number
(bootloader) :ANE-LX3 9.1.0.313(C792E6R1P3)
OKAY [ 0.005s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem get-product-model
(bootloader) ANE-LX3
OKAY [ 0.003s]
Finished. Total time: 0.005s
c:\Applications\platform-tools_r34.0.3-windows>fastboot getvar vendorcountry
vendorcountry: cityfone/ca
Finished. Total time: 0.004s
c:\Applications\platform-tools_r34.0.3-windows>fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :ANE-LX3-CUST 9.1.0.6(C792)
OKAY [ 0.010s]
Finished. Total time: 0.011s
Click to expand...
Click to collapse
that seems like a problem, not sure if you can find ANE-LX3 C792 9.1 Service ROM for dload method...
Try to update your phone via eRecovery & wi-fi.
-Alf- said:
that seems like a problem, not sure if you can find ANE-LX3 C792 9.1 Service ROM for dload method...
Try to update your phone via eRecovery & wi-fi.
Click to expand...
Click to collapse
Woohoo! LineageOS is installed and booting now!
I wasn't really interested in the dload method. I was just trying to use that to reset everything to some good old state so I can go back into TWRP and try to get LineageOS installed.
What I ended up doing was switching my data partition from f2fs to exFAT which seemed to do the trick for some reason?! It was just a wild guess on my part and I wonder if it'll cause issues in the future (I'll create a new thread if it does). But so far so good!
O.K., midnight here
Ironsmith9 said:
exFAT
Click to expand...
Click to collapse
???? It should be f2fs or ext4 . Install normal TWRP 3.2.0.1 by "gaguga" or "pretoriano80" and perform format data again, be sure you have f2fs format. Imo.
-Alf- said:
???? It should be f2fs or ext4 . Install normal TWRP 3.2.0.1 by "gaguga" or "pretoriano80" and perform format data again, be sure you have f2fs format. Imo.
Click to expand...
Click to collapse
Understood, ok I'll try that out! Thanks Alf!

Categories

Resources