[SOLVED!] How to change to official build? Build 8.0.0.046(070F) EMUI 8.0.0 - Huawei P20 Lite Questions & Answers

Hi guys,
i recently bought a Huawei P20 Lite on ebay. The device they send me has the System Firmware with the Build Number Build 0.0.0.046(070F). Since we all know that the p20 lite supports EMUI 9.1 i wanted to update the Firmware via system update. But no updates available. HiSuite also sais its allready up to date. Latest security patch is March 2018...
I reached out to the official Huawei support and they said to me:
"I have forwarded your ticket with case number SR3202108251214229RK to the specialist department and have already received feedback. Unfortunately, it is not possible for us to send you a software update as a push notification because your device 8.0.0.046(070F) has undergone a software manipulation. The P20 Lite has a custom ROM installed, so unfortunately you will not receive any support, not even from the French support team. I strongly advise you to use your right of withdrawal while you still have time to do so. Unfortunately, I cannot tell you if this is an isolated case with this retailer, but I would not recommend another purchase. "
My Question is: How can i change the Firmware to an official build to get Android 9 on the device.
Things i tried so far:
- Dload method didn't work. "Installation failed"
- HiSuite "allready up to date"
- erecovery doesnt find any official builds to install.
Is it possible to flash an official Firmware via Huawei Multi Download Software? Do i need an unlocked bootloader?
If i go in Bootloader screen it says "Phone locked"
Please help me otherwise i'll send this phone back...
Additional information:
Manufacture information: ANE_LX1_VF
Bootloader Version: Chipset-dallas8.0.0.046(070F)_FASTBOOT
Kernel Version: System 8.0.0.046(070F)_BOOT
Vendor:hw
Country:normal

alexence said:
Hi guys,
i recently bought a Huawei P20 Lite on ebay. The device they send me has the System Firmware with the Build Number Build 0.0.0.046(070F). Since we all know that the p20 lite supports EMUI 9.1 i wanted to update the Firmware via system update. But no updates available. HiSuite also sais its allready up to date. Latest security patch is March 2018...
I reached out to the official Huawei support and they said to me:
"I have forwarded your ticket with case number SR3202108251214229RK to the specialist department and have already received feedback. Unfortunately, it is not possible for us to send you a software update as a push notification because your device 8.0.0.046(070F) has undergone a software manipulation. The P20 Lite has a custom ROM installed, so unfortunately you will not receive any support, not even from the French support team. I strongly advise you to use your right of withdrawal while you still have time to do so. Unfortunately, I cannot tell you if this is an isolated case with this retailer, but I would not recommend another purchase. "
My Question is: How can i change the Firmware to an official build to get Android 9 on the device.
Things i tried so far:
- Dload method didn't work. "Installation failed"
- HiSuite "allready up to date"
- erecovery doesnt find any official builds to install.
Is it possible to flash an official Firmware via Huawei Multi Download Software? Do i need an unlocked bootloader?
If i go in Bootloader screen it says "Phone locked"
Please help me otherwise i'll send this phone back...
Additional information:
Manufacture information: ANE_LX1_VF
Bootloader Version: Chipset-dallas8.0.0.046(070F)_FASTBOOT
Kernel Version: System 8.0.0.046(070F)_BOOT
Vendor:hw
Country:normal
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 results.
alexence said:
Dload method didn't work. "Installation failed"
Click to expand...
Click to collapse
Which firmware?
alexence said:
Is it possible to flash an official Firmware via Huawei Multi Download Software?
Click to expand...
Click to collapse
Nope, it supports Huawei devices running on the Qualcomm Chipset (AFAIK).

{
"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"
}

-Alf- said:
Which firmware?
Click to expand...
Click to collapse
i tried :
- Huawei P20 Lite ANE-LX1 ANE-L21 hw eu Anne-L21 8.0.0.150(C432) Firmware 8.0.0 r1 EMUI8.0 05014YWN [androidhost.ru]
- Huawei P20 Lite ( Nova 3e ) ANE-L21 ANE-L01 hw eu Anne-L01 9.1.0.370(C432E7R1P7T8) Firmware EMUI9.1.0 05014YXU [androidhost.ru]

alexence said:
i tried :
- Huawei P20 Lite ANE-LX1 ANE-L21 hw eu Anne-L21 8.0.0.150(C432) Firmware 8.0.0 r1 EMUI8.0 05014YWN [androidhost.ru]
- Huawei P20 Lite ( Nova 3e ) ANE-L21 ANE-L01 hw eu Anne-L01 9.1.0.370(C432E7R1P7T8) Firmware EMUI9.1.0 05014YXU [androidhost.ru]
Click to expand...
Click to collapse
I'm not sure, but I think your device is a DEMO version
(Region C652 + hw/normal). Someone probably tried to do a rebrand , but unsuccessfully... Is your phone fully functional? What's your security patch date?

-Alf- said:
I'm not sure, but I think your device is a DEMO version
(Region C652 + hw/normal). Someone probably tried to do a rebrand , but unsuccessfully... Is your phone fully functional? What's your security patch date?
Click to expand...
Click to collapse
Which funcions should i check?
So far everything worked fine:
calling, mobile internet, wifi, bluetooth, GPS worked
Security patch date is March 1st 2018

i even did a benchmark with 3DMark and the results are similar to the results from the internet.

alexence said:
Security patch date is March 1st 2018
Click to expand...
Click to collapse
With this patch you should be able to use DC-Unlocker and get bootloader unlock code.
If DC-unlocker will not be able to recognize your phone (due to the current system build 8.0.0.046), try installing the service ROM 8.0.0.142 (C652) using the dload method. Link
Or, try unlock the BL using PotatoNV method.

Okay i'm kinda new to this all...
what will happen "if" i manage to unlock the bootloader?
im downloading the service rom right now.
if you say that the phone is a demo version of it... is it worth all the trouble or shouldn't i just refund it?
it will probably not be possible to refund it after all this alterations, will it?

alexence said:
if you say that the phone is a demo version of it... is it worth all the trouble or shouldn't i just refund it?
Click to expand...
Click to collapse
DEMO devices are fully functional, except the ability to update, it's your choice...
alexence said:
it will probably not be possible to refund it after all this alterations, will it?
Click to expand...
Click to collapse
after all the successful alterations it will work perfectly

-Alf- said:
after all the successful alterations it will work perfectly
Click to expand...
Click to collapse
with an official build and android 9 and recent safety patches?
if you say we can achive this then i will go for it

alexence said:
with an official build and android 9 and recent safety patches?
if you say we can achive this then i will go for it
Click to expand...
Click to collapse
If you manage to unlock the bootloader, no problem.

Allright Bootloader seems to be unlocked now.
Whats the next step?

alexence said:
Allright Bootloader seems to be unlocked now.
Click to expand...
Click to collapse
Are you sure?

well i get the warning message on boot up.
Fastboot says "PHONE Unlocked"

i used DC unlock method

alexence said:
i used DC unlock method
Click to expand...
Click to collapse
Okay, Chapter 1.:
- Downoload oeminfo.img
https://mega.nz/file/U4kjnaYR#RNj3zCLOGFoIO60XbVGBUeiES-pL6iUA1XwRbF4Zo7s
and copy it to SD Card
- Download TWRP
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
and copy it to SD & PC
- Download stock recovery
https://mega.nz/file/04dG0JBb#hEgTk6DMKVDffttHiXGqa_YR_zG5UYwTMEi41KTkZi8
and copy it to SD Card.
- Download Service ROM
https://androidhost.ru/2zMw
Unpack downloaded .zip package, and copy dload folder to the SD Card (without unpacking it! )
In Settings > Developer options enable OEM unlock, so in fastboot mode you will see Phone unlocked FRP unlock.
- In fastboot install TWRP, run
fastboot flash recovery_ramdisk TWRP-oreo-smart.img
fastboot reboot .
- Boot into TWRP and flash it over eRecovery :
-- select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe. Go back, find RECOVERY_RAMDISK-ANE-OREO file , mark Recovery, swipe. Reboot system, when yellow warning appears press and hold Volume Up.
- In TWRP select Install image and flash oeminfo.img file (mark oeminfo, swipe). Go back to main TWRP's menu, select Reboot > Power Off.
- Flash Service ROM using three buttons combo.
THE PROCESS WILL LOCK THE BOOTLOADER AGAIN!

so i did everything as you said. and the last step didnt work :/
there is emui interface "Software install failed!" Imcompatibility with current version. Please download the correct update package.

after the phone rebootet EMUI did a factory reset. bootloader seems to be locked hence there is no warning anymore.
edit: i just checked fastboot. Phone is locked again.

phone in bootloop now

Related

[TOOL][VIEW 10] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Honor View 10 's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Install APKs
Uninstall APKs
Take a Screenshot
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​
I used this on 5T and it did work super.
But i am wondering if this is working for view10 or not... V10 requires a unique code to unlock BL, where do we provide that code here?
Also rooting v10 requires an img to be flashed. Is this tool working?
Anyone tested all these features on View10??
venreddy said:
I used this on 5T and it did work super.
But i am wondering if this is working for view10 or not... V10 requires a unique code to unlock BL, where do we provide that code here?
Also rooting v10 requires an img to be flashed. Is this tool working?
Anyone tested all these features on View10??
Click to expand...
Click to collapse
I have tested it on my honor view 10, to unlock your bootloader you still need of huawei unlock codes, always remember this tool automate process not bypass it (except it is not specified). This tool can't root the phone directly
EDIT: there is a little bug when you try to unlock the bootloader and your phone is in powered on and recognized in adb mode, i'm releasing a new version to fix it at this moment
EDIT 2: update released
mauronofrio said:
I have tested it on my honor view 10, to unlock your bootloader you still need of huawei unlock codes, always remember this tool automate process not bypass it (except it is not specified). This tool can't root the phone directly
EDIT: there is a little bug when you try to unlock the bootloader and your phone is in powered on and recognized in adb mode, i'm releasing a new version to fix it at this moment
EDIT 2: update released
Click to expand...
Click to collapse
Hi
Thanks for excellent tool. I have installed it and watched the videos you posted for OnePlus. You have used SuperSu in case of OnePlus. But for Honor View 10 I want to use Magisk. Can you please let me know the step?
vku369 said:
Hi
Thanks for excellent tool. I have installed it and watched the videos you posted for OnePlus. You have used SuperSu in case of OnePlus. But for Honor View 10 I want to use Magisk. Can you please let me know the step?
Click to expand...
Click to collapse
The videos are not made by me, i found it on youtube and i added the link to tool description. To root your device you need to see this guide: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
mauronofrio said:
The videos are not made by me, i found it on youtube and i added the link to tool description. To root your device you need to see this guide: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
Click to expand...
Click to collapse
Thanks for response. So far I unlocked the boot loader (really easy with your tool one click only thanks for it). For root
how to install Magisk Manager using your tool. Which button to use
1. Recovery flasher
2. Recovery Zip flasher
Bear with me if it sounds naïve this is first time I am trying to root
vku369 said:
Thanks for response. So far I unlocked the boot loader (really easy with your tool one click only thanks for it). For root
how to install Magisk Manager using your tool. Which button to use
1. Recovery flasher
2. Recovery Zip flasher
Bear with me if it sounds naïve this is first time I am trying to root
Click to expand...
Click to collapse
You can't root your phone with this tool, you need to follow that guide
You can installa magisk manager through "apk installer"
Just for info, Files are available for V10 now on firmware finder.
shashank1320 said:
Just for info, Files are available for V10 now on firmware finder.
Click to expand...
Click to collapse
link?
mauronofrio said:
link?
Click to expand...
Click to collapse
On app here it is. Can give you link if want
shashank1320 said:
On app here it is. Can give you link if want
Click to expand...
Click to collapse
The problem is i have the bkl-l04 version and for it there are not stock firmware available so i can't test it for now
just 2 questions - does it work for Honor 10 (not v10)? can I do recovery backup here?
PeterMarkoff said:
just 2 questions - does it work for Honor 10 (not v10)? can I do recovery backup here?
Click to expand...
Click to collapse
Honor 10 is not supported officially, you cant do a recovery backup with this tool
Hi guys.
I'm looking forward for Honor View 10 or Honor 10, and as I'm with Samsung S8, I'm trying to understand if these Honor devices can receive a recovery consol or be rooted in a way that can be restored to stock without being noticed from official assistance in case I'll need to go for an assistance in warranty.
Second, as I'm with Samsung since years, I've always seen to need a recovery consol and a root package to flash (as standard classic methods) for having complete access to phone, while here I read about unlocking and unlocking cuts from Honor (that I'm reading now it seams that they stopped to release easily the code needed), recovery, bootloader and other things that I'm completely lost in reading
I'm not speaking of the strict interest in flashing alternative roms, but at least to have the possibility to clean the phone deeply once in a while manually with SD-Maid, RootExplorer and other apps (maybe you know of more professional...) so for it not to get fat and more fat in time, with the possibility to clean corps and old unused system files without the need of a wipe, so to have a slim internal sd-card as much as I can (specially if I'll go for the Honor 10)
So please explain me a bit of what is this Honor world as I'm really willing to they one even tomorrow!!
Thanks to allall.
Sent from my SM-G950F using Tapatalk
Work this for mate 9...?
PIRATA! said:
Hi guys.
I'm looking forward for Honor View 10 or Honor 10, and as I'm with Samsung S8, I'm trying to understand if these Honor devices can receive a recovery consol or be rooted in a way that can be restored to stock without being noticed from official assistance in case I'll need to go for an assistance in warranty.
Second, as I'm with Samsung since years, I've always seen to need a recovery consol and a root package to flash (as standard classic methods) for having complete access to phone, while here I read about unlocking and unlocking cuts from Honor (that I'm reading now it seams that they stopped to release easily the code needed), recovery, bootloader and other things that I'm completely lost in reading
I'm not speaking of the strict interest in flashing alternative roms, but at least to have the possibility to clean the phone deeply once in a while manually with SD-Maid, RootExplorer and other apps (maybe you know of more professional...) so for it not to get fat and more fat in time, with the possibility to clean corps and old unused system files without the need of a wipe, so to have a slim internal sd-card as much as I can (specially if I'll go for the Honor 10)
So please explain me a bit of what is this Honor world as I'm really willing to they one even tomorrow!!
Thanks to allall.
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
Honor and huawei devices can be unlocked, there are available twrps and you can do what you want. They can be restored to stock.
mataflakitas said:
Work this for mate 9...?
Click to expand...
Click to collapse
Mate 9 is not officially supported, if it has kirin 970 you can try to select honor view 10 and use the tool
Hey buddy, thanks for this amazing tool. I need to know, if there's need of the Bootloader Code for unlocking it on a Honor V10?
Also, if I need to add a phone that's in similar state as this phone (LG Stylus 2 Plus, currently not supported by LG for unlocking with their tool), can I send everything that you may need for making the tool compatible with it?
Thanks in advance!
i tried today on my honor view 10 to unlock bootloader, cant work

[RECOVERY][UNOFFICAL][LINK FIXED] TWRP 3.5.0 for Samsung Galaxy A6+ 2018

Team Win Recovery Project 3.5.0
{
"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"
}
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
How to install:
Coming From Stock:
1. Download This TWRP Release and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
2. Under Developer Options, Tick OEM Unlock. It will tell you to factory reset. Do it.
3. After the phone shuts down, press Vol + & - button and at the same time, insert a usb cable to phone connected to a PC.
4. Check KG Status. If it is Prenormal, reboot the phone and follow this guide : (1) How to bypass KG State and/or RMM state prenormal | XDA Developers Forums (xda-developers.com)
5. Zip the TWRP recovery image to tar format and put in the AP slot of Samsung Odin.
6. Flash and after the phone screen turns off, press vol+ and power button.
7. If there is "Set Warrenty Bit : recovery" text on the top left, success!
8. Format data, flash zip downloaded from above.
9. To boot stock rom, install magisk.
From Other Recovery:
Reboot to recovery and flash this TWRP image as recovery and reboot recovery.
ChangeLog:
2021/3/2 Inital Release
Sources:
Kernel : Junak/android_kernel_custom_a6plte (github.com)
Device Tree: roynatech2544/TWRP_device_samsung_a6plte (github.com)
Recovery Source : TeamWin (github.com)
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
NOTE :
I was developing custom roms for A6+ despite of my computer specs. But my phone's LCD went out and I can't test anymore... And it takes 1 day to build in i5-5200U (2C/4T) CPU and 8GB RAM.. Now I can only build TWRP.​
where is the twrp file ?
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
CRDhani said:
where is the twrp file ?
Click to expand...
Click to collapse
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
Hi,
I'm new here, this method also works with bootloader 6 ? e.g. with the "A605FNXXU6CTH1"
Android 10, UI 2.0, are there any problems with rooting? Magisk or SU?
thanks for your replay
little_beppo said:
Hi,
I'm new here, this method also works with bootloader 6 ? e.g. with the "A605FNXXU6CTH1"
Android 10, UI 2.0, are there any problems with rooting? Magisk or SU?
thanks for your replay
Click to expand...
Click to collapse
yes it works.
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Hello
Is this recovery for android 10?
Hii, I followed a rooting guide before this one, it bricked my phone I had to flash stock rom.. now its back I still want to root it so that I can adopt my sd card as internal.. Can I please have a very clear step by step guide... Please..
I'm using a605fn
okwhateverok said:
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Click to expand...
Click to collapse
I can help with that. I know what it feels like having no TWRP and custom rom. But you still need to test the TWRP. Because I don't have A600FN, and the LCD on my A6+ broke so I don't own a device launched in 2018. OK with testing?
abhisekh010 said:
Hello
Is this recovery for android 10?
Click to expand...
Click to collapse
Yes it is compiled in android 10 tree but recovery doesn't depend on android version..
Naddi2Niic3 said:
Hii, I followed a rooting guide before this one, it bricked my phone I had to flash stock rom.. now its back I still want to root it so that I can adopt my sd card as internal.. Can I please have a very clear step by step guide... Please..
I'm using a605fn
Click to expand...
Click to collapse
PM me
okwhateverok said:
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Click to expand...
Click to collapse
I can help with that. I know what it feels like having no TWRP and custom rom. But you still need to test the TWRP. Because I don't have A600FN, and the LCD on my A6+ broke so I don't own a device launched in 2018. OK with testing?
Thank you for your offer to help develop a recovery for the a600FN. It is about testing and im willing to help but at the moment my device is being used for daily stuff so i cant risk to much....
Any suggestions? Thank you and i will PM any next message.
okwhateverok said:
Thank you for your offer to help develop a recovery for the a600FN. It is about testing and im willing to help but at the moment my device is being used for daily stuff so i cant risk to much....
Any suggestions? Thank you and i will PM any next message.
Click to expand...
Click to collapse
I think it will work...? Because I will use kernel and dt from here. And it's verifyed working. I'm just building for new version
Can you test this?
Thanks, ill hope there will be some users which ow the Galaxy A6 and not using this device as their main phone to be willing to test.
As a IT specialist myself i did try anything to at least help testing for this version of TWRP for our device. I did try to take several rom dumps with professional fabric software and hardware like software dongles but it was impossible to make a full rom dump.
With this said and knowing that a complete data wipe within TWRP is necessary to make the recovery find the internal storage makes it impossible for me to test no matter the fact that the biggest part of this recovery already exist and confirmed working.
I have A600FN and I could test that as soon as my OEM unlock button will be visible (above 10 days passed and still nothing...).
nqnxev said:
I have A600FN and I could test that as soon as my OEM unlock button will be visible (above 10 days passed and still nothing...).
Click to expand...
Click to collapse
I could help with the OEM unlock button. What a waist of time these lost 10 days and still no OEM unlock button while the solution is easy...
Follow guide with screenshots: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
And for those who could test on the A600 the recovery image is already uploaded within this thread thanks to Royna
I've tried that many times (no only that, but many similar guides) - and still nothing. From what I read, Samsung just fixed that "date & time" trick and I have to wait.
Ok that is strange, im on android 10 with One UI version 2.0 and got it working. If im allowed to post this link then the rom could be found here: https://www.sammobile.com/samsung/galaxy-a6/firmware/SM-A600FN/PHN/#SM-A600FN
You should do a clean flash without having the phone connected to the internet, not even once because it will do some synchronization. After the flash just follow the guide which could be found on the xda forum..
Thank you for a hint. Because of that I'm waiting so long already I'll wait till end of week and if things still will be the same then I'll try rom you've proposed. Thanks again.
Royna said:
I think it will work...? Because I will use kernel and dt from here. And it's verifyed working. I'm just building for new version
Can you test this?
Click to expand...
Click to collapse
i flashed that recovery image on my A600FN which has latest android 10 firmware , it caused a bootloop
Adam7336 said:
i flashed that recovery image on my A600FN which has latest android 10 firmware , it caused a bootloop
Click to expand...
Click to collapse
Well because i don't own that device, it is highly experimental. I will try again.

How to downgrade Android 11 to 10

I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to help, but none have worked. I found that Android 10 was good and stable. My question is, how can I downgrade my Moto G Power back to Android 10 easily? Can it be done with Moto's Rescue and Smart Assistant? This rescue utility seems to only want to keep the device on Android 11. Please provide step by step instructions how to do this. Thanks.
Gordster said:
I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to help, but none have worked. I found that Android 10 was good and stable. My question is, how can I downgrade my Moto G Power back to Android 10 easily? Can it be done with Moto's Rescue and Smart Assistant? This rescue utility seems to only want to keep the device on Android 11. Please provide step by step instructions how to do this. Thanks.
Click to expand...
Click to collapse
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First 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
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
sd_shadow said:
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First 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
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
Click to expand...
Click to collapse
Thank you sd_shadow. I appreciate your very detailed response and answer. I will try your methods and hopefully be able to return to Android 10. Android 11 seems to currently have a lot of bugs at least with the Moto G Power phone. Wish I had stayed on Android 10.
sd_shadow said:
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First 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
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
Click to expand...
Click to collapse
Thanks a lot sd_shadow
I tried Flash Option 2 using LMSA. Replaced all the Android 11 ROM files in the default download directory folder with official Android 10 ROM files, and then used the rescue option to flash the Android 10 files to the Moto g Power. Everything worked perfectly. I now have Android 10 back on my phone. I keep getting the notification that there is an Android 11 update available but just have to ignore this. Thanks again for your help.
Gord
HEY im trying to flash stock rom using LMSA manually but a popup says cannot match current firmware ...
Is there somthing i can do to select and flash a downloaded firmware for lolinet?
thanks
darko454 said:
HEY im trying to flash stock rom using LMSA manually but a popup says cannot match current firmware ...
Is there somthing i can do to select and flash a downloaded firmware for lolinet?
thanks
Click to expand...
Click to collapse
Seems that lmsa doesn't work for some software channels, or if the baseband and the channel don't match.
What does getvar all say?
Code:
fastboot getvar all
Curious.
I managed to downgrade, but can't re-lock the bootloader on Android 10 or else it throws this error and will not boot:
{
"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"
}
However, when I reflashed Android 11 and re-locked the bootloader, it boots just fine, without any warnings.
Something, the bootloader itself maybe, must be stuck on 11 and won't let me relock the bootloader when 10 is flashed.
Since I need the bootloader locked so I can pass Playstore security, I guess I'm stuck on Android 11 :\
JackDHopper said:
Curious.
I managed to downgrade, but can't re-lock the bootloader on Android 10 or else it throws this error and will not boot:View attachment 5375851
However, when I reflashed Android 11 and re-locked the bootloader, it boots just fine, without any warnings.
Something, the bootloader itself maybe, must be stuck on 11 and won't let me relock the bootloader when 10 is flashed.
Since I need the bootloader locked so I can pass Playstore security, I guess I'm stuck on Android 11 :\
Click to expand...
Click to collapse
Magisk Hide should be able to hide the bootloader status
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
JackDHopper said:
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
Click to expand...
Click to collapse
It''s a game of cat and mouse, google introduces new security measures, magisk devs get to working a way around it... There is even a module now that lets you pass full safetynet with xposed and microg.
JackDHopper said:
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
Click to expand...
Click to collapse
@JackDHopper. I don't want to brick my Moto G8 Power 2020 running the Havoc 4.8 Android 11 ROM by screwing up a downgrade to Android 10 so I can flash LineageOS 11. So, can you please explain how you did it?
Thanks. Much appreciated.
jhford said:
@JackDHopper. I don't want to brick my Moto G8 Power 2020 running the Havoc 4.8 Android 11 ROM by screwing up a downgrade to Android 10 so I can flash LineageOS 11. So, can you please explain how you did it?
Thanks. Much appreciated.
Click to expand...
Click to collapse
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Beetle84 said:
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Click to expand...
Click to collapse
Beetle84 said:
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Click to expand...
Click to collapse
@Bettle84 thanks for the reply. I'm running TWRP 3.5.0_10-0. I flashed the img files with fastbootd when i initially installed Havoc and when i upgraded to 4.8. So, do you mean that I can flash the LOS ROM in TWRP on top of Havoc without using fastbootd?
Thanks again
jhford said:
@Bettle84 thanks for the reply. I'm running TWRP 3.5.0_10-0. I flashed the img files with fastbootd when i initially installed Havoc and when i upgraded to 4.8. So, do you mean that I can flash the LOS ROM in TWRP on top of Havoc without using fastbootd?
Thanks again
Click to expand...
Click to collapse
Yeah you should be able to
Beetle84 said:
Yeah you should be able to
Click to expand...
Click to collapse
OK. LOS is installed, but I can't find a GAPPS that works. Suggestions?
Thanks
jhford said:
OK. LOS is installed, but I can't find a GAPPS that works. Suggestions?
Thanks
Click to expand...
Click to collapse
No idea, i havent flashed anything on my g8 in a while
does this work with moto g power 2021, android 11 aint working for me either, always get the systen ui has stopped error and certain apps stop working
this is my model number just to make sure
Hi all!! I been trying to downgrade my moto g power 2021 to Android 10 from 11 and I been reading in this thread. At first I tried the second method of flashing that sd_shadow suggested and it seems after 32% a message that says "flash single partian, flash failed" pops up.
Then I tried the first method. I tried making the flashall.bat file and put it in the sdk tools directory as the steps said in the fast boot forum. It didn't work when I double clicked so then I put my supposed firmware zip files (that I got from the lolinet website above) inside the sdk tool directory (unzipped) and Android 10 actually installed. I skipped all the steps after factory reset so I can go into devmode and turn off automatic updates. However when I tried turning on my WiFi, the phone would crash and restart and it would do that everytime it tried to connect to the WiFi. Even after I factory reset my device again the same problem persisted. I managed to use lmsa to go back to 11. What can I do to fix this downgrade issue?
After 1.5 full days of many attempts to downgrade from A11 to A10, fastbootd is the answer! I used Motorola-XML-To-Batch-Script-master with stock firmware from bootloader with nothing but boot loops. went into fastbootd just for the hell of it and ran the bat and boom! back to stock 10!
I go into further details here: https://forum.xda-developers.com/t/how-to-downgrade-android-11-to-10.4283809/post-86614163

General 🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑

***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.***
From the Pixel Images page:
{
"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"
}
This applies to ALL Tensor devices, regardless of whether or not you're rooted!
What this means: Once Android 13 Stable boots, it updates an anti-rollback counter in the device hardware to prevent rolling back the bootloader. This will prevent previous versions of the bootloader from starting.
Why this is a problem: The OTA only updates one slot, then reboots into that slot. It does not update both slots at once. If there is a boot failure after updating to Android 13, the device may attempt to "recycle" back to the old slot. If this other slot has a previous version of the bootloader, the bootloader will not start, rendering the device a brick.
How do I make sure this doesn't happen to me? If you updated via OTA, simply sideload the OTA again. Since you are currently on the Android 13 slot, this will overwrite your old Android 12 slot with the new bootloader.
If you have an unlocked bootloader and prefer to update using the factory image, you can flash the bootloader to both slots:
fastboot flash bootloader --slot=all <bootloader image> It's highly recommended you do this BEFORE updating, but if you didn't, do it as soon as possible.
I've updated several times since the August 2022 update, am I still at risk?
If you've updated via OTA at least once the initial Android 13 update, you should be fine. Instructions to check bootloader versions are further down this post.
The initial Android 13 release bootloader version is slider-1.2-8739948. As long as your bootloader is equal to or higher than this, you should be fine.
What if I was on the Android 13 Beta? Same as above - the beta did not incorporate the anti-rollback, and the beta bootloaders are still considered "old".
Will the new bootloader prevent me from flashing and running Android 12? The short answer is YES, for now. Contrary to what the warning above says, you CAN flash Android 12 on the Android 13 bootloader, and though it will boot, it will not run properly. See this post.
How do I check my current bootloader version?
Spoiler: Use these commands in an ADB command line:
Code:
adb reboot bootloader #Reboots device to bootloader.
fastboot getvar current-slot #Outputs current slot, should also be visible on the device screen: "Boot slot"
fastboot getvar version-bootloader #Outputs current slot's bootloader version, should also be visible on device screen "Bootloader version"
fastboot --set-active=a or b #Use this to switch to the inactive slot - if current slot is A, set to B or vice versa.
fastboot getvar current-slot
fastboot getvar version-bootloader
fastboot --set-active=b or a (set to original slot) #Set active slot back to what it was before. If you started on slot A, make sure you switch back to slot A.
fastboot getvar current-slot
fastboot continue #Commands device to resume boot, same function as selecting "Start" in the bootloader menu.
#So as an example:
fastboot getvar current-sot
>current-slot: a
fastboot getvar version-bootloader
>version-bootloader: slider-1.2-8739948
fastboot --set-active=b
>Setting current slot to 'b'
fastboot getvar version-bootloader
>version-bootloader: slider-1.2-8739948
fastboot --set-active=a
>Setting current slot to 'a'
fastboot continue
I updated with OTA and later sideloaded the update, but my bootloader is unlocked. I'm screwed?
AlphaSteam said:
I updated with OTA and later sideloaded the update, but my bootloader is unlocked. I'm screwed?
Click to expand...
Click to collapse
No. That's is the recommended method according to Google.
"To avoid hitting this state, if you are flashing a Pixel 6, Pixel 6a, or Pixel 6 Pro device with an Android 13 build for the first time, please flash the bootloader partition to the inactive slot after successfully updating and booting into Android 13 at least once. This can be done by following these steps:
Option 1 (recommended): After a successful boot into Android 13 for the first time, sideload the full OTA image corresponding to that build and reboot the device to ensure that both slots have a bootable image."
Can we run A13 system on an A12 bootloader?
Is there any way / anyone / any research on the bootloader code to stop the "fuse" trigger?
Does it break any law in any country that software update secretly activates a hardware trigger that stops the user from using any good old systems?
kylechen said:
Can we run A13 system on an A12 bootloader?
Click to expand...
Click to collapse
Hasn't been tested yet. If you want, you can try by using the same --force argument; just be aware that if it doesn't work, you may need to wipe data.
kylechen said:
Is there any way / anyone / any research on the bootloader code to stop the "fuse" trigger?
Click to expand...
Click to collapse
Don't know, doubt it.
kylechen said:
Does it break any law in any country that software update secretly activates a hardware trigger that stops the user from using any good old systems?
Click to expand...
Click to collapse
This seems like something you could research yourself. I highly doubt it - many OEMs implement some form of anti-rollback on their devices to prevent downgrading to previous firmwares. Samsung is especially notorious for this.
No, and you shouldn't. It has a vulnerability in the Android 12 bootloader.
Android is open source, and that means it is potentially vulnerable to "downgrade attacks." Essentially, an attacker downgrades the software to an older version that has known exploits. This is particularly dangerous in open source software like Android because the act of fixing an exploit reveals it to everyone.
Click to expand...
Click to collapse
I see no reason to downgrade the bootloader, you still can run A12 with the newer bootloader.
Cheers
tom1807 said:
No, and you shouldn't. It has a vulnerability in the Android 12 bootloader.
I see no reason to downgrade the bootloader, you still can run A12 with the newer bootloader.
Cheers
Click to expand...
Click to collapse
Not as a daily driver.
V0latyle said:
Not as a daily driver.
Click to expand...
Click to collapse
Can't comment on this, no idea what would be the side effects.
My active slot is A and has Android 13, I only updated the ootloader to the latest one on slot B but there should be still A12.
Cheers
Tom
tom1807 said:
Can't comment on this, no idea what would be the side effects.
My active slot is A and has Android 13, I only updated the ootloader to the latest one on slot B but there should be still A12.
Cheers
Tom
Click to expand...
Click to collapse
The whole point of this thread is that if only one slot is updated and the device switches/is switched to the Android 12 slot after updating and running Android 13, it will brick.
The side effects of running 12 on the 13 bootloader have been established. See the OP. WebView and DRM Apex constantly crash.
tom1807 said:
Can't comment on this, no idea what would be the side effects.
My active slot is A and has Android 13, I only updated the ootloader to the latest one on slot B but there should be still A12.
Cheers
Tom
Click to expand...
Click to collapse
But if you flash back to A12 using the A13 bootloader you'll have a bunch of apps, webview, browers, etc. crashing.
Which actually makes me wonder about something...
@roirraW "edor" ehT When you were on A12 and flashed the A13 bootloader, did you experience apps crashing or other negative side effects? I don't remember you mentioning so which makes me curious if there is a difference in how well the OS runs when you are on A13 and flash back to A12 with the A13 bootloader vs. being on A12 and flashing the A13 bootloader???
Lughnasadh said:
But if you flash back to A12 using the A13 bootloader you'll have a bunch of apps, webview, browers, etc. crashing.
Which actually makes me wonder about something...
@roirraW "edor" ehT When you were on A12 and flashed the A13 bootloader, did you experience apps crashing or other negative side effects? I don't remember you mentioning so which makes me curious if there is a difference in how well the OS runs when you are on A13 and flash back to A12 with the A13 bootloader vs. being on A12 and flashing the A13 bootloader???
Click to expand...
Click to collapse
I didn't, but I didn't even both trying to launch anything, that I recall. I merely unlocked the phone - I might have swiped right to display "Google Discover" aka whatever it's called now via Nova Companion, and I might've swiped up to check out the app drawer, and swiped down to check out the notifications.
I didn't test texting, chatting, phone calls, web browsing, watching videos, harassing my fellow moderators LOL!, or anything when I had only upgraded the bootloader and still running my original, never upgraded Android 12 (first) July "global" update - 12.1.0 (SQ3A.220705.003, Jul 2022).
roirraW edor ehT said:
harassing my fellow moderators LOL!,
Click to expand...
Click to collapse
Beat you to it bet you won't find the Easter egg
roirraW edor ehT said:
I didn't, but I didn't even both trying to launch anything, that I recall. I merely unlocked the phone - I might have swiped right to display "Google Discover" aka whatever it's called now via Nova Companion, and I might've swiped up to check out the app drawer, and swiped down to check out the notifications.
I didn't test texting, chatting, phone calls, web browsing, watching videos, harassing my fellow moderators LOL!, or anything when I had only upgraded the bootloader and still running my original, never upgraded Android 12 (first) July "global" update - 12.1.0 (SQ3A.220705.003, Jul 2022).
Click to expand...
Click to collapse
Ah, ok. Makes sense now. I had thought you stayed on it for a while and used it. Thanks...
Updating via google pixel flashing website flashes both slots ? Or should i do it manually
Nightf0x_007 said:
Updating via google pixel flashing website flashes both slots ? Or should i do it manually
Click to expand...
Click to collapse
Do you mean Android Flash Tool? If so, no, it doesn't flash to both slots. However, the latest version of the Pixel Flasher does.
Can someone list steps to manually update Google pixel 6?
My phones bootloader is locked.
EDIT : I was just worrying, did manual update VIA sideloading OTA, worked well, now I need to figure out how to update the bootloader.
eagledipesh said:
Can someone list steps to manually update Google pixel 6?
My phones bootloader is locked.
EDIT : I was just worrying, did manual update VIA sideloading OTA, worked well, now I need to figure out how to update the bootloader.
Click to expand...
Click to collapse
Sideload the OTA again. It always installs to the inactive slot.
I've updated by using the factory image (batch-installation), overloaded unblocked.
Can I flash the bootloader to both slots manually again without any issues?
Sui77 said:
I've updated by using the factory image (batch-installation), overloaded unblocked.
Can I flash the bootloader to both slots manually again without any issues?
Click to expand...
Click to collapse
Should be able to, yes.
Thanks for posting this. I manually flashed the OTA update from Google' site and there is no warning listed there (I just double checked to see if it was added since I flashed). I knew you wouldn't be able to roll back to the old bootloader, but I had no idea the recommendation was to flash both bootloaders.
EDIT - actually after looking at the warning on the factory image page (and not seeing it on the OTA image page), I have to wonder if the OTA image flashing process actually flashed both bootloaders. I would think Google would add the same warning to the OTA image site if this was a potential problem.

Ane-Lx3 update emui 9 [half resolved]

Hi, does anyone know how I can flash the base, curt and preload of the p20 lite ane-lx3?
I got them with hisuite proxy but they give me an error when verifying update.
I need it because I can only go back to emui 8 from hi suite emui 9 does not appear, I had downloaded it to unlock the bootloader. I already unlocked them but I want to go back to the most updated emui or at least more than 9.1.0.142 since it still has the app drawer button.
I have seen that the multi tool 8 can be used to flash but I don't understand how to do it.
antonyx2016 said:
how I can flash the base, curt and preload of the p20 lite ane-lx3?
Click to expand...
Click to collapse
this can be done via modified TWRP, HuRupdater 0.4 or Multi-tool if you are running EMUI 9.1.
But these methods are risky when upgrading from 8.0 to 9.1 and are not recommended.
You can safely manually upgrade to 9.1 only by installing the service ROM using the dload method from the SD card.
What is your full build number? (settings > About phone).
Also check your vendor/country information via the Project Menu (*#*#2846579#*#*) and post the result.
Thank you for taking the time to respond, here I leave what you asked for. I would appreciate it if you could explain a little more how to do the process.
{
"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"
}
I thought you were currently on 8.0, sorry. So you can try the methods in my previous post.
For HuRupdater method use TWRP 3.2.1 "Gaguga edition".
Rename all three archives:
base -> update.zip
preload -> update_data_public.zip
cust -> update_all_hw.zip
It works on the P20 Pro, it should also work on the P20 Lite. Be aware that these methods are risky, especially when it comes to choosing the right firmware for your phone!
Personally, I prefer an update via eRecovery & wi-fi, or installing a service ROM via dload.
You can download Service ROM for your phone
Here
The dload process will erase all your data and lock your BL again!
-Alf- said:
I thought you were currently on 8.0, sorry. So you can try the methods in my previous post.
For HuRupdater method use TWRP 3.2.1 "Gaguga edition".
Rename all three archives:
base -> update.zip
preload -> update_data_public.zip
cust -> update_all_hw.zip
It works on the P20 Pro, it should also work on the P20 Lite. Be aware that these methods are risky, especially when it comes to choosing the right firmware for your phone!
Personally, I prefer an update via eRecovery & wi-fi, or installing a service ROM via dload.
You can download Service ROM for your phone
Here
The dload process will erase all your data and lock your BL again!
Click to expand...
Click to collapse
Good brief update: I tried all the stock roms of ane-l23 all with the same result in the case of emui 9 it stays at 9.1.0.046 and in emui 8 8.0.0.046 so far everything is fine after reading several forums here I have found one to see the files with root everything is fine up to here I enter /cust/hw and find two folders (la or latam) and normal. and in special cust only after all the props are fine, that is, it is 5.0.0.20.
Then looking for more information to see where the 8.0.0.046 was, I found it in version.prop. Additionally, enter splash2/cust.log and throw a lot of errors in the following post or answer. I leave you the images to see if we can solve something because the problem that bothers me is not being in emui 8 or 9 but that it is not so stable all that works if when installing any firm again the huawei id does not work first playstore and update hsm core after that everything works either themes etc etc.
but it lags a lot in emui 8 and in emui 9 google maps doesn't work so I don't care if I stay in emui 8 or 9 honestly but I do want the equipment to work correctly. Thank you very much for your willingness and willingness to help.

			
				
antonyx2016 said:
emui 9 it stays at 9.1.0.046 and in emui 8 8.0.0.046
Click to expand...
Click to collapse
It means wrong or incomplete FW. As I said before,
-Alf- said:
service ROM via dload.
You can download Service ROM for your phone
Click to expand...
Click to collapse
-Alf- said:
Here
Click to expand...
Click to collapse
Maybe you are doing something wrong...Follow instructions in ReleaseDoc folder.
antonyx2016 said:
I tried all the stock roms of ane-l23
Click to expand...
Click to collapse
you can only install the service ROM for your region (hw/la)!
But it is possible that with your current build number 9.1.0.046 you will not be able to flash via dload or eRecovery.
-Alf- said:
It means wrong or incomplete FW. As I said before,
Maybe you are doing something wrong...Follow instructions in ReleaseDoc folder.
you can only install the service ROM for your region (hw/la)!
But it is possible that with your current build number 9.1.0.046 you will not be able to flash via dload or eRecovery.
Click to expand...
Click to collapse
Yes I understand that, but what I wanted to say is that I already tried all the c605 firmware that there is, whether it is emui 8 and emui 9, they all install without error but apparently they do not install at all, I don't know if it is cust the oem partition or something like that but whatever the method, it always ends in .046 the only thing I know for sure is that it started to be like that a year ago when I used hisuite to go back and from there I could no longer update after what happened with hisuite I bought the code in dc to unlock the bootloader but I still can't remove the .046 in a few words hisuite screwed my phone xD because it was never rooted or unlocked until after what I told you
Okay, I don't know what the problem is, two last tips from me:
A) follow this method
https://ministryofsolutions.com/202...re-stock-rom-emui9-1-unlocked-bootloader.html
(reliable source)
B) rebrand to global version C432. But this requires downgrading to Oreo, and this is only possible through HiSuite (because there are no files needed for HuRupdater). It could help to get a fully working phone.
It could happen that before using hisuite you had a different region, not hw/la (claro/la etc.) hisuite couldn't recognize it and downgraded your phone to hw/la. Maybe you should try flashing oeminfo C605.
In fastboot mode run commands :
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the result.
If you decide to rebrand, I will give you instructions.
-Alf- said:
If you decide to rebrand, I will give you instructions.
Click to expand...
Click to collapse
If that helps me, ok, I tried option a) it was installed but it is incomplete with the pink background. If doing a rebrand will help me, ok
antonyx2016 said:
with the pink background
Click to expand...
Click to collapse
Now try to flash Service ROM.
Also try enter eRecovery and use option "Download latest version...".
As for rebrand, I can't give you any guarantee.
-Alf- said:
Now try to flash Service ROM.
Also try enter eRecovery and use option "Download latest version...".
As for rebrand, I can't give you any guarantee.
Click to expand...
Click to collapse
I think I achieved it in a while I'll tell you what happened but I'm hopeful something changed with the hisuite proxy
Ok, let me tell you, I managed to install firmware 9.1.0.355. I know it's not the latest and it didn't free me from system component 9.1.0.040 either, but at least now everything works correctly.
I'll tell you what I did in case it helps someone else:
1- I did the point a) that you sent me
2- I kept the pink wallpaper and I went to the proxy hisuite and downloaded the cust, preload and base .355
3- it marked an error when installing in the 1% of hisuite the proxy already warned me that it was going to fail and to cancel
4- cancel it and deactivate the 3 checks of point, cust and preload
5-I put in developer mode and look for the update in hisuite
6- This time I no longer throw any errors and it was completely flashed. I imagine that because of step a) the cust was updated and that is why it allowed the .355 to be installed
7-it was still half incomplete but I went into settings and updated and I got the same .355 version and it was installed correctly in quotes as I said I still have the .40 system but everything works now I imagine that if you keep messing around a bit that way it will I could install the .390 but I'm satisfied with the .355

Categories

Resources