Related
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Meranico said:
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Click to expand...
Click to collapse
If you can boot to "downloader" use rebranding SW, it will fix everything
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
Thank you so much! My mobile phone is working again! :victory:
Edit: Small problem persists: I cannot use the buttons left and right of the scanner. They do not react.
Edit2: Could fix this. I flashed B120 and the buttons worked again.
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
whats rebranding sw and hoe do i do it as i have the smae problem please help
corey568brown said:
whats rebranding sw and hoe do i do it as i have the smae problem please help
Click to expand...
Click to collapse
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Meranico said:
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Click to expand...
Click to collapse
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
corey568brown said:
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
Click to expand...
Click to collapse
Good to know!
As I had the same problem as you do know: I flashed B120, which does not seem to have the bug with the buttons and upgraded via Firmware Finder to B130 and then to B150.
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
_____________________________________________________________________________________________
UPDATE: The cell phone was completely downloaded. I plugged it into the computer and was able to enter Fastboot mode. So again I have TWRP for OREO.
But I still have a boot loop of "Error MODE". Any idea how to fix it?
TWRP 8 Oreo https://ibb.co/nEn5HS
Error MODE https://ibb.co/mrErrn
Aspiranteh said:
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock oem xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
Sorry bad english.
Click to expand...
Click to collapse
try to flash stock recovery then try force upgrade method.
h30_u10 said:
try to flash stock recovery then try force upgrade method.
Click to expand...
Click to collapse
Edit:
I can flash the recovery stock however, I don't know if in android OREO I can install full firmware through a folder (dload) on the SD card. Is there a similar way as in Nougat and earlier versions of android?
Try to flash your rom with twrp and install magisk before trying to boot into rom. Magisk patch boot.img and remove many security/error check when booting to rom.
rhaavin said:
Try to flash your rom with twrp and install magisk before trying to boot into rom. Magisk patch boot.img and remove many security/error check when booting to rom.
Click to expand...
Click to collapse
I'll give it a try. The problem is that the Rom Oreo I have is not flash for TWRP. I have searched but I still can't find an Oreo ROM that can be flashed by TWRP.
I found this method: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
that I think can work. However, it is for Mate 9, so I have to replace the files with those of Mate 10 lite and rename them as if they were Mate 9. Although I'm not sure what I should extract from Update.app to rename.
If someone could guide me, I'd be very grateful.
If that doesn't work, I will try this other method I found by browsing the forums. [ Chuckles]
https://forum.xda-developers.com/showpost.php?p=75628230&postcount=71
Any contribution is welcome.
Translated with www.DeepL.com/Translator
I stucked on the same or very similar fastboot screen, phones OS was oreo, here is why it happened:
I tried to use command fastboot flash recovery TWRP3.1.1.img
It will always show Failure message.
Then on this kind XDA forum I came to know that the recovery location is changed in oreo to
recovery_ramdisk I flashed with: fastboot flash recovery_ramdisk TWRP3.1.1.img
And thus reached the same fastboot error screen you have posted.
Workaround was: Get the update.app file from the update zip files (I used HWOTA method
to upgrade to Oero when my device was already soft bricked). So used update extractor
to pull out UPDATE.APP file form the biggesst update zip file from HWOTA folder,
but first u have to go to settings and disable header check sum option otherwise it will show error.
So I pulled out the proper stock recovery file named like: recovery_ramdisk.img
I used command: fastboot flash recovery_ramdisk revcovery_ramdiskimg
Now I got the stock recovery that I can use to wipe data and do factory reset.
So if you can come to this point, may be after factory reset you would be able to get it back.
Good luck.
Fix Error (SOLVE)
I can say from experience that the same thing happened to me, and the only thing you have to do is wait until your phone has a 0% charge, leaving the screen turned on with the error.
When that happens, connect the original cable to the PC and connect it in Fasboot mode, unlock the bootloader if you do not have it, then install the firmware of it ... with the HWOTA tool that you will see in one of the posts in this section ... you will have to have the three corresponding files of the same one ... the UPDATE, DATA, DATAPUBLIC and follow the steps in the post of HWOTA ... and you will relive your team.
Greetings ... I hesitate to answer for the difference of time and my work ... Greetings from Panama
Aspiranteh said:
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
_____________________________________________________________________________________________
UPDATE: The cell phone was completely downloaded. I plugged it into the computer and was able to enter Fastboot mode. So again I have TWRP for OREO.
But I still have a boot loop of "Error MODE". Any idea how to fix it?
TWRP 8 Oreo https://ibb.co/nEn5HS
Error MODE https://ibb.co/mrErrn
Click to expand...
Click to collapse
usman400 said:
I stucked on the same or very similar fastboot screen, phones OS was oreo, here is why it happened:
I tried to use command fastboot flash recovery TWRP3.1.1.img
It will always show Failure message.
Then on this kind XDA forum I came to know that the recovery location is changed in oreo to
recovery_ramdisk I flashed with: fastboot flash recovery_ramdisk TWRP3.1.1.img
And thus reached the same fastboot error screen you have posted.
Workaround was: Get the update.app file from the update zip files (I used HWOTA method
to upgrade to Oero when my device was already soft bricked). So used update extractor
to pull out UPDATE.APP file form the biggesst update zip file from HWOTA folder,
but first u have to go to settings and disable header check sum option otherwise it will show error.
So I pulled out the proper stock recovery file named like: recovery_ramdisk.img
I used command: fastboot flash recovery_ramdisk revcovery_ramdiskimg
Now I got the stock recovery that I can use to wipe data and do factory reset.
So if you can come to this point, may be after factory reset you would be able to get it back.
Good luck.
Click to expand...
Click to collapse
I also uploaded to OREO by HWOTA like you, I managed to do it without problems, all functional. Then I don't remember why but I decided to give wipes and that's when my problem started.
Yes, recovery_ramdisk was already in consideration.
I even flashed:
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash kernel kernel.img
fastboot flash system system.img
fastboot reboot
but I can't get it to start just throw that "MODE ERROR" at me, I don't think system is completely installed :/ /
emorenoebultron said:
I can say from experience that the same thing happened to me, and the only thing you have to do is wait until your phone has a 0% charge, leaving the screen turned on with the error.
When that happens, connect the original cable to the PC and connect it in Fasboot mode, unlock the bootloader if you do not have it, then install the firmware of it ... with the HWOTA tool that you will see in one of the posts in this section ... you will have to have the three corresponding files of the same one ... the UPDATE, DATA, DATAPUBLIC and follow the steps in the post of HWOTA ... and you will relive your team.
Greetings ... I hesitate to answer for the difference of time and my work ... Greetings from Panama
Click to expand...
Click to collapse
Yes, I really think this is the solution but it's only posted HWOTA and not HWOTA8 for Mate 10 lite... If there was only one HWOTA8 for our equipment, I'm sure I could fix it .
Aspiranteh said:
I also uploaded to OREO by HWOTA like you, I managed to do it without problems, all functional. Then I don't remember why but I decided to give wipes and that's when my problem started.
Yes, I really think this is the solution but it's only posted HWOTA and not HWOTA8 for Mate 10 lite... If there was only one HWOTA8 for our equipment, I'm sure I could fix it .
Click to expand...
Click to collapse
hmmm since I am all set with Oreo update and its working and I am not a very advanced user in flashing etc.
So am not going to any further thing until proper oreo update comes
But I was thinking at a point, why not go through existing HWOTA script, change the commands where recovery
is referred, (change recovery to recovey_ramdisk in any fastboot command found inside script), then running it to
try luck.
Also I think TWRP for mate 10 lite for Oreo version was made available a few days ago in this forum, search it
usman400 said:
hmmm since I am all set with Oreo update and its working and I am not a very advanced user in flashing etc.
So am not going to any further thing until proper oreo update comes
But I was thinking at a point, why not go through existing HWOTA script, change the commands where recovery
is referred, (change recovery to recovey_ramdisk in any fastboot command found inside script), then running it to
try luck.
Also I think TWRP for mate 10 lite for Oreo version was made available a few days ago in this forum, search it
Click to expand...
Click to collapse
Forgive my ignorance but what would be the script to edit, I downloaded the HWOTA again to modify it but I don't really know which file to modify. :confuso:
** @vovan1982 Hi, excuse me. I saw you post HwOTA for Mate 10 lite, do you know if there are any options for HwOTA8? Thank you very much in advance!
Aspiranteh said:
Forgive my ignorance but what would be the script to edit, I downloaded the HWOTA again to modify it but I don't really know which file to modify. :confuso:
** @vovan1982 Hi, excuse me. I saw you post HwOTA for Mate 10 lite, do you know if there are any options for HwOTA8? Thank you very much in advance!
Click to expand...
Click to collapse
If you can enter to trwp8, I can try to give you my backup of oreo mate 10. The problem for the script is, I think, the recovery push by vovan1982 is not comptatible with the aero installed, and when you are in twrp8, usb cable don't work!
gmbengue said:
If you can enter to trwp8, I can try to give you my backup of oreo mate 10. The problem for the script is, I think, the recovery push by vovan1982 is not comptatible with the aero installed, and when you are in twrp8, usb cable don't work!
Click to expand...
Click to collapse
If I have access to Twrp8, if you could share your backup with me I would be very grateful! :fingers-crossed:
Aspiranteh said:
If I have access to Twrp8, if you could share your backup with me I would be very grateful! :fingers-crossed:
Click to expand...
Click to collapse
I'm in L21. like I see, your model is L03. If you confirm that it's good I'll try to upload it. If someone can help for what to backup. It's too big (ramdisk, kernel, product, product image, cust, cust image,system, vendor, vendor image, version and version image)
gmbengue said:
I'm in L21. like I see, your model is L03. If you confirm that it's good I'll try to upload it. If someone can help for what to backup. It's too big (ramdisk, kernel, product, product image, cust, cust image,system, vendor, vendor image, version and version image)
Click to expand...
Click to collapse
If you please. If that's what you ask in MediaFire, there are 10 GB free to upload to the cloud. I know your help will help someone else at some point. . Thx.
file name is shell inside the folders find it or edit the .bat file to know where is the shell located
but if this is something new 4u then ask some one with little knowledge of MS DOS commands or shell scripts to edit it for u
Aspiranteh said:
If you please. If that's what you ask in MediaFire, there are 10 GB free to upload to the cloud. I know your help will help someone else at some point. . Thx.
Click to expand...
Click to collapse
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Lords, I have news for you. After many attempts I couldn't fix my "ERROR MODE", so I blocked the Bootloader and went to the shop to make my warranty effective... The technician believed my history that the phone was blocked after an update that appeared to me through OTA and will enforce my warranty because the phone presented "Factory Errors"... XD. Well, that's it, I've got my cell phone working again. Thank you all for your help.
gmbengue said:
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Click to expand...
Click to collapse
Maybe if you upload the backup you can help someone else in the future. Thank you very much for your willingness to help me. :good::fingers-crossed:
Urgent ordi 8.0 failed
gmbengue said:
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Click to expand...
Click to collapse
Bonjour
J'ai exactement le même problème.
Tu pourrais me donné le backup de ton mate 10 ton envie , s'il te plait.
Je serrais usurper heureux si tu pouvais m'aider.
Merci d'avance.
Je m'excuser ne parle pas anglais .
Up
RobotGuerrier said:
Bonjour
J'ai exactement le même problème.
Tu pourrais me donné le backup de ton mate 10 ton envie , s'il te plait.
Je serrais usurper heureux si tu pouvais m'aider.
Merci d'avance.
Je m'excuser ne parle pas anglais .
Click to expand...
Click to collapse
XDA Forum rules
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator.
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Arseon said:
So I unlocked bootloader and FRP. Installed magis. It was working, but when i tried to install xposed, it went into a bootloop. Now I'm stuck at eRecovery screen with nothing working. I've done factory reset 10-15 times. Clicking 'Download latest version and recovery' is also not giving anything. Can go to fastboot mode. Went there, saw FRP was locked. Thinking I'll redo the process, I relocked the bootloader. But now the commands aren't working as neither 'allow oem unlock' nor 'usb debugging' is enabled. I can't enable them as phone won't boot up. Any solutions? Please help.
Model ANE-AL00
Click to expand...
Click to collapse
Go to TWRP and restore your system backup.
kilroystyx said:
Go to TWRP and restore your system backup.
Click to expand...
Click to collapse
But I didn't install a custom recovery. So no TWRP
Arseon said:
But I didn't install a custom recovery. So no TWRP
Click to expand...
Click to collapse
So, then try flash same system partition via fastboot.
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
What your build ?
If this phone with OREO or with NOUGAT / Android 8.x or 7.x ?
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Arseon said:
Possibly didn't work because the rom was of a different built. I've an ANE-AL00 8.0.0.131. Any solutions for this fix? Thanks.
Click to expand...
Click to collapse
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
kilroystyx said:
You should try at least flash the system from fullota, the firrmware can be found with Firmware Finder for Huawei
http://pro-teammt.ru/firmware-database/?firmware_model=ANE-AL00C00B131&firmware_page=0
Click to expand...
Click to collapse
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Arseon said:
Yes. I flashed same file only. But not booting up. In DC, it says file writing complete when in fastboot mode. But in upgrade mode, it fails at 5/31 PACKAGE_TYPE.
I'm using update.app from update.zip. Is that what I should be using? Should I use the other zip files(cn, public etc.)? Please help.
Click to expand...
Click to collapse
It seems like you are doing well, but have you read the instructions carefully? They recommend when something fail.
https://www.dc-unlocker.com/huawei-phone-flashing-in-fastboot
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
AND very important : do not relock the bootloader !
ONLY if bootloader 'unlockt' you can self-repair !
JamesBott said:
@Arseon
you write "ANE-AL00 8.0.0.131" - this is not the "full" build : what's your Cxxx ?
on FirmwareFinder i see (example)ANE-AL00C00B133 ( C00 = Country '00'; B133 = Build Counter )
you need the correctly build from your phone !!!
Click to expand...
Click to collapse
Mine is ANE-AL00 8.0.0.131(C675). I used ANE-AL00C00B131 (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2370/g1789/v138744/f1/full/filelist.xml ) to flash
JamesBott said:
you can boot to bootloader ?
your bootloader is unlockt ?
your FRP is unlock ?
Click to expand...
Click to collapse
Sadly no. Both bootloader and frp are locked.
JamesBott said:
you have download your build FULL-Update ?
you have with UpdateExtractor from Update.app (inside Update.zip)
- ramdisk.img
- recovery_ramdisk.img
- system.img
extracted ? The Extractor do automatic for all *.img a *.img.header.
you have copy this 6 files to your ADB-Folder ?
If this all "YES" then boot to bootloader and
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
reboot phone, phone start to eRecovery and Low-Level format "data" and boot to system.
phone start as "new" phone (initial settings)
good : phone work
no good : all data is lost
Click to expand...
Click to collapse
Since bootloader and frp locked, adb commands are not working. Hence I'm using DCPheonix to flash the file. But without luck. It's still botting to eRecovery only
your phone is C675, you flash C00 : no correct
now is inside your phone a 'mix'
i think, you can no self-repair - sorry
@Arseon, my opinion your system partition is a mess due to xposed installation fail.
The solution for this case is restore system partition, it worked for me in the past.
In some cases we can get lucky install a clean system partition even if it is from other region code, because the main differences between regions are located in the other partitions
But what I learning is that system from C00 region don’t follow this standard because at least is missing google apps.
With DCPheonix did with get lucky and flash all files or just the first 4 and stop in the PACKAGE_TYPE?
same situation
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Edit: I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
alvavaca said:
I am in the same situation, can only boot to erecovery. I tried boot fastboot flash 4 files (because i have bootloader and frp unlocked) and dc-unlocker without luck. In both cases pass the flash but phone still not boot, only erecovery. I can get twrp works now following this guide: https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692 but i dont have backups because i do a factory reset and the internal storage is empty. What can i do in twrp? I flash the correctly firmware for my phone ANE-LX3 8.0.0.104(C605), with this file ANE-LX3C605B130 (8.0.0.130) from here: http://pro-teammt.ru/firmware-database/?firmware_model=ANE-LX3&firmware_page=0 . Any other suggestion?
Click to expand...
Click to collapse
This thread can help you a lot => HuRUpdater
kilroystyx said:
This thread can help you a lot => HuRUpdater
Click to expand...
Click to collapse
Thks for your help, I can solve my problem. When I connect my phone in fastboot mode to dc-unlocker it give me an info:
Found Phone : ANE-LX3
Model : Huawei phone in fastboot mode
IMEI : 867903xxxxxxxxxxxx
Serial NR. : KPS7N18xxxxxxxxx
Firmware : ANE-LX3 8.0.0.104(C605
IMEI1:867903032092188
MEID:00000000000000
FB LockState: LOCKED
USER LockState: UNLOCKED
unlocked
Battery state: 3829mv
and with the firmware info I download that version exactly (ANE-LX3 8.0.0.104(C605, found on easy-firmware web page, paid), flash with dc-phoenix, and i got it, the device boots again. Hope it help to anyone, thks. This thing cost me 28 usd, too expensive for unroot a device lol
---------- Post added at 02:08 PM ---------- Previous post was at 02:01 PM ----------
Arseon said:
I tried flashing original firmware using DC-Pheonix. But phone is still in bootloop
Click to expand...
Click to collapse
In pretty sure you are flashing the wrong firmware, try to push your version with dc-unlocker in fastboot and download the excatly matching firmware. Good luck
well, i have all of this+one more tougher stuff..
Well, I tried to install a custom ROM on my P20 Lite (ane-lx1) via TWRP aand when I failed I ended up into a bootloop, but the thing that got me a headache after a full day of forum research is that when I attempted to install the custom ROM the TWRP wanted a .img file, not a .zip file, so I rebooted after I alreday wiped out everything, I made a backup into the phone, BUT I cant access it because.. the TWRP freezes every time at the TeamWin logo.....the only thing that is accessible now its the fastboot&rescue mode and I'm out of juice and desperated...the bootloader is enabled...i think i preety much killed my phoen and my brain trying to get an android stock experience...i really have to get some sleep,well..thank you for your attention, if you have any suggestions that would pick me up from this mess I would be very greatfull, i'll see what i had left to do as soon as i'm able to...for now, have a good night/day/afternoon, whatever side of the world you're from
Edit:
I left the phone all night into bootloobing and after it got FULLY discharged, I dont know exactly how but the TWRP hasn't popped out, instead after this I was able to get into eRecovery and now it is downloading the 146(C432) version. I guess that I got lucky
Mate 10. So, I tried to install the latest EMUI version using HuRUpdater - bad idea. Now, my phone will not boot. I can enter EMUI Recovery Mode but when I try to receive download package, it says it can't be retrieved. I can also enter Fastboot Mode but the problem with that is that under Device Manager, it only gets recognized as, "Android Bootloader Interface."
Please, any help would be greatly appreciated.
edit: So, fastboot DOES work. What files from what version do I flash to return to stock recovery? I don't even know if Pie was actually written to the device or not before the device rebooted and wouldn't boot.
edit again: I have just successfully installed TWRP via fastboot but it hangs at startup screen - is this because it's not compatible with Pi?
So I've tried flashing ramdisk_recovery.img, kernel.img and system.img from the Pi version but I still can't factory reset the phone. It boots back to the white screen with the android dude and says, "Please update system again."
Any help would be appreciated...
Using Multi-Tool, it detects my device in Fastboot mode as still 8.0.0.143. So, I'm trying to flash System, Ramdisk, Cust, Recovery_Ramdisk and Userdata......all succeed, except one - Ramdisk.img. When I manually try to flash Ramdisk.img in command prompt, it also fails, "FAILED (remote: partition length get error)". In Multi-tool, the error is, "the size or path does not match the file system markup."
Please, does anyone have any other suggestions? I've been at this for nearly 12 hours straight.
I assume u have unlocked bootloader and frb unlocked too if both yes u can search in xda for zip file beta downy 0.4
It will help you to downgrade emui 9 to. Emui 8
If u have unlocked bootloader only I guess u need funky huawei to restore ur devise
I hope I did helped u
Thanks for the reply.
My bootloader is unlocked but how do I know if I have unlocked FRP?
And downy tool requires ADB but I can only access Fastboot.
edit: I just checked and my FRP is also unlocked. What now?
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
essen212 said:
Tried Funky Huawei just now, no go. Still get package can't be received error in ERecovery after following all of the instructions. Have emailed them as that's what they suggest doing if it didn't work.
Not sure what else to try to be honest. How the hell does updating my phone from 8.0.0.143 to 9.0.0.159 with HuRUpdate brick my phone? Ffs.
Click to expand...
Click to collapse
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Pretoriano80 said:
Well, it happened because HuRUpdater it's not supported on EMUI 9.0.
Ramdisk fails to flash because even if in fastboot your device is showing as 8.0.0.143, it has EMUI 9's partition layout, so no more ramdisk partition.
Try flashing a firmware with the DLOAD method (search on androidhost.ru for a firmware designed for your device/cust).
Click to expand...
Click to collapse
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
essen212 said:
Damn. Well, that makes perfect sense. A question - do I flash the 9.0.0 version or 8.0.0.143 version?
Click to expand...
Click to collapse
Try with EMUI 9 first, then, if it fails, try Oreo. The most important part is finding a DLOAD firmware for your cust/region.
I've fixed it!
Funky emailed me back and I ended up using a different method on their site which worked like a charm. I couldn't recommend them enough.
Hi, good to hear you got it sorted! Would you mind sharing the details on what you had to do differently with FHC? I'm in the same boat here with a mate 10 pro that died on emui9 and I'm not sure if I should go the FHC way or not...
Thx - David
Hi everybody
I've got a problem...
Downloaded latest OTA update from "xiaomi.eu", agreed to install, the phone then rebooted in to fastboot mode and does nothing else.
Rebooted the phone with adb command "fastboot continue" and this went well...it rebooted the system.
Now every time i restart the phone it reboots in to fastboot mode and i have to "fastboot continue" again.
I am also not able to enter recovery because the phone always enters fastboot mode.
Reinstalled recovery (Twrp-3.4.2B_toco_by.alex.msk1407.img) via ADB succesfully, but when i "fastboot reboot recovery" it reboots back into fastboot.
I'm also not able to boot into EDL mode.
Any solution?
Thanks
"MI NOTE LITE 8GB/128GB" running "MIUI by xiaomi.eu 12.1.1 | Stable 12.1.1.0(RFNMIXM)
Hi, I 'm in the same case, same model, same version.
I investigated and I can provide more details to help the community to look where to get a match to lightning our lanterns.
I downloaded the last OTA from built-in updater then the device was trapped in fastboot loop.
Unable to reboot/boot with adb/fastboot commands, but able to flash, I tried with différents recoveries,whose the last TWRP (testing version) let us discover the "super partition" (need fastbootd implantation to see it) This is the new OTA update partitioning.
We have to set up the proper flags via adb to perform successfully the update , or cancel the update process to retrieve original partitioning (non-updating state).
The commons way to restore recovery/fastboot might don't work, because system/vendor partitions are hidden inside "super partition" so might result of unknown/doesn't exist partition.
I am still seeking (Android dev super partitioning) and I'll be back when I'll discovered more...
EDIT : Doublon ? Another thread is open
https://forum.xda-developers.com/t/...astboot-after-updating-to-android-11.4223957/
EDIT: many users had a similar issue.
Will try with any another GSI rom, downloading...
opposatto said:
Hi, I 'm in the same case, same model, same version, I investigated and I can provide more details to help the community which lantern to pickup.
I downloaded the last OTA from built-in updater then the device was trapped in fastboot loop.
Unable to reboot/boot with adb/fastboot commands, but able to flash, I tried with différents recoveries,whose the last TWRP (testing version) let us discover the "super partition" (need fastbootd implantation to see it) This is the new OTA update partitioning.
We have to set up the proper flags via adb to perform successfully the update , or cancel the update process to retrieve original partitioning (non-updating state).
The commons way to restore recovery/fastboot might don't work, because system/vendor partitions are hidden inside "super partition" so might result of unknown/doesn't exist partition.
I am still seeking (Android dev super partitioning) and I'll be back when I'll discovered more...
EDIT : Doublon ? Another thread is open
https://forum.xda-developers.com/t/...astboot-after-updating-to-android-11.4223957/
Click to expand...
Click to collapse
Thank you. I'll be for updates
salsaecoentros said:
Thank you. I'll be for updates
Click to expand...
Click to collapse
Looking around https://source.android.com/devices/tech/ota/dynamic_partitions/implement
opposatto said:
Looking around https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Click to expand...
Click to collapse
EDIT : so here is the idea, not tried yet:
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Alex msk's twrp is not compatible with android 11. Use orangefox or pitchblack recovery.
Btw i would recommend not upgrading to android 11 at the moment. It has a lot of bugs.
ApexPrime said:
Alex msk's twrp is not compatible with android 11. Use orangefox or pitchblack recovery.
Click to expand...
Click to collapse
So that's the problem....didn't think about that.
Thanks...i Will try one of them and them get back to you.
Thanks
salsaecoentros said:
So that's the problem....didn't think about that.
Thanks...i Will try one of them and them get back to you.
Thanks
Click to expand...
Click to collapse
Hi...
Sorry for the late Replay.
So i did like you said and installed new twrp and...what do you know...ir worked like a charme. No more issues.
Thank you do much.