What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
hey i can help ! which version of twrp are you trying to flash ?
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Venkata Lochan Nune said:
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Click to expand...
Click to collapse
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
My bad , I thought the update website to be huawei's official one(something like update.hicloud and all isn't it?). Well, thanks for the information but I still prefer gsi. It's buttery smooth .
And one more thing, if you follow the youtube video I mentioned, you don't need any gsi. You can get your device back on stock EMUI 5.
King_of_Android said:
hey i can help ! which version of twrp are you trying to flash ?
Click to expand...
Click to collapse
Hey I have a doubt... Will the recoveries we find in twrp official website / app work on EMUI 8? I wanted to try them but I'm afraid I might brick my device again. Getting it back is a hectic thing and I already had to face it thrice. LOL .
King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
lmaohelp said:
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
Click to expand...
Click to collapse
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Venkata Lochan Nune said:
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Click to expand...
Click to collapse
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
lmaohelp said:
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
Click to expand...
Click to collapse
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Venkata Lochan Nune said:
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Click to expand...
Click to collapse
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
lmaohelp said:
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
Click to expand...
Click to collapse
I'm attaching one that works with emui 8 try using it (Remember you have to flash it to recovery_ramdisk).
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
speedson said:
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
Click to expand...
Click to collapse
His problem us with twrp.
He can only access fastboot but isn't able to flash twrp...
Venkata Lochan Nune said:
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
Click to expand...
Click to collapse
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
lmaohelp said:
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
Click to expand...
Click to collapse
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Venkata Lochan Nune said:
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Yup, I tried that as well, and it told me "invalid command"
lmaohelp said:
Yup, I tried that as well, and it told me "invalid command"
Click to expand...
Click to collapse
Well as you said, you partitions must have been really messed up. I have no other ideas except the test point method.
Are you trying anything else?
Ok we have some option that could help you...
Im read in the 4PDA (the russian XDA xD) forum that it should be possible to flash the oeminfo by fastboot command. So just download the HWOTA_BLN_Eng and expand it. Then go to 7 or 8 Folder and there you go to oeminfo folder. There you choose the right one for your Device and local area...for example BLN-L21 (Device) C432 (European Area)
Extract the file to your desktop and rename it to BLN-L21C432.img
--->be sure that you have the right Device driver installed and the right ADB driver for your device to<---
ok now Copy and Paste the BLN-L21C432.img to ADB folder and start command with admin rights
start the phone into fastboot mode
--->bootloader must be unlocked<---
in the command
fastboot flash oeminfo BLN-L21C432.img
wait for the result and it can not hurt to pray a bit in this moment...hihi
if this have success...you type in command
fastboot reboot
wait to the screen you can press 3 seconds Vol+ to go into erecovery....connect to wlan and it should work step by step like it should.
after download and recover the stock rom reboot and go again to erecover by press Vol+ for 3 seconds and now go to the second option...wipe data/factory reset and write yes+enter
in stock recovery wipe Data after that wipe Cache...reboot and wait that system boot the initial boot for first setup.
If this will not working...tell me what honor 6x you have and wich local area you are from and wich firmware you stock had before you doing wronng
good luck bro
solong
speedson
Related
Hello,
After the purchase of my phone i unlocked the bootloader, installed a custom rom of android M, everything went fine, twrp, root, etc.
Few days ago I wanted to give a shot at Nougat. I went through a couple roms but lacking certain functions i needed. I then tried one last stock nougat beta rom (from this link : https://forum.xda-developers.com/honor-8/development/beta-android-7-0-emui-5-l04c567b320-frd-t3529465
This was the worst rom i've encountered. Please don't use it.
Three reasons : No bluetooth, TWRP gone, and no keyboard pre-installed.
Yes. You can only first boot this rom with google voice typing. I'm not joking.
More than that i cannot finish the initial boot of the rom, i get stuck at the "enter your google account" (try to enter yours with google voice...)
I can't even ignore it, it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device".
Anyway, now that I lost TWRP i wanted to flash it back. My bootloader being still unlocked (phone shows "your device has been unlocked and cannot be trusted" at each boot), i went to adb to flash twrp.
I got this message after trying to flash it :
...
FAILED (remote: Command not allowed)
...
I get this message after i try to flash TWRP, update, boot or anything.
I've read that i need to enable oem unlock in the developer settings. Thing is I'm stuck before i can access any parameters.
I even tried Huawei Multi-Tool, with boot, recovery, unbrick, but again, can't flash anything.
tl;dr :
- Nougat 7.0 EMUI 5.0
- Stuck in initial boot
- Only type with google voice
- No TWRP
- FAILED (remote: Command not allowed) error when trying to flash anything
What can I do ?
EDIT : I did manage to enter my google account, but it says that i need to log in with one of the owner's account. I never entered any other account on my phone... Definitely stuck.
This question was already answered a million times before! Just use the search button!
This Honor 8 forum is full of threads created by newly come member that just create a new thread without any use when they could just search for the already answered questions!
Plug in USB to computer, hold down power + volume down until you enter bootloader. Flash recovery system image again, then reboot into recovery and re flash another ROM.
Telperion said:
Plug in USB to computer, hold down power + volume down until you enter bootloader. Flash recovery system image again, then reboot into recovery and re flash another ROM.
Click to expand...
Click to collapse
Even when i'm in fastboot mode I can't flash anything, boot.img, recovery.img, system.img... nothing.
Fastboot mode shows "PHONE Unlocked" "FRP Lock", if that helps.
I tried using the rollback solution shown here https://forum.xda-developers.com/honor-8/help/totally-screwed-honor-8-t3556678/post71033483#post71033483. Intermediate package did apply but the full android 6.0 firmware failed to update.
And yes I've been searching around this forum before posting, but I can't find a post talking about my problem, being unable to access the rom in normal boot, unable to flash anything.
Is there a way to fix the "FAILED (remote: Command not allowed)" error message ? As it is the only think keeping me from doing anything on my phone
Or maybe trick the phone into flashing a rom through recovery (like a rollback but with a random custom rom instead) ?
Hi, did you ever find a fix for this?
Rommco05 said:
Are you missing some stuff from the system?
Click to expand...
Click to collapse
I don't believe so. Why?
Rommco05 said:
You need to install zip data. Which is your model and build number?
Click to expand...
Click to collapse
FRD-L04, and my Build Number is whatever the build number is for the first Nougat Beta from last year haha.
But how would I install zip data if flashing stuff via fastboot isn't working?
Are you referring to the Data Fix.zip? Also, I haven't been able to flash the 6.0 Stock ROM Via ercovery.
---------- Post added at 09:16 AM ---------- Previous post was at 09:14 AM ----------
Rommco05 said:
FRD-L04 US model, right? First beta was maybe B320..?? Via dload
Click to expand...
Click to collapse
Are you referring to the Data Fix.zip? Also, I haven't been able to flash the 6.0 Stock ROM Via ercovery.
Rommco05 said:
FRD-L04 US model, right? First beta was maybe B320..?? Via dload
Click to expand...
Click to collapse
Rommco05 said:
For flash to 6.0 u need rollback packages and full M rom. Is your phone US model? I try send u links if is
Click to expand...
Click to collapse
Yeah I have the US model
Rommco05 said:
First install biggest second small, over dload methodhttp://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v72309/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...09/f1/full/hw/usa/update_data_full_hw_usa.zip
Click to expand...
Click to collapse
Thanks, so what's the install method for this?
Hi everyone, I have the mha-l29 and successfully updated to the latest Oreo for the US version. I then unlocked the bootloader, flashed TWRP, flash Superuser and everything was working fine. I then got an error message while doing a backup in TWRP and foolishly edited a file which caused the system to not boot. I then Flashed the hwoa7 instead of 8 to fix it and now my phone is bricked. The only thing I can do is get into fastboot. Everything else throws an error. Is ee a func no: 11 error. Please see attached pictures. Please let me know how I can fix it. I've already tried reflashing the ramdisk as well as TWRP bet I can't boot into TWRP.
Thanks so much
C:\>fastboot oem lock-state info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.008s]
finished. total time: 0.012s
Do you mean you flashed RECOVERY_nocheck from Nougat to Recovery of Oreo?
If so you should only need to flash recovery_ramdisk.
I guess you could extract ramdisk, recovery_ramdisk and kernel and flash to the partitions of the same name.
See what error it gives after you flash back stock recovery_ramdisk
Thank you for your help ante. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
saw this to late , TWRP caused this i had the same thing earlier and reinstalled different TWRP
seti007 said:
Thank you for your help ante. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
Click to expand...
Click to collapse
DC-Unlockr allowed you to use adb to flash twrp? How were you able to do that exactly?
I was able to flash the entire update package using DC Unlocker. That should have gotten me up fully but it did not. Before using DC unlocker, I was not able to even boot into TW RP or erecovery. I was able to get into fastboot but could not install anything. I did not get any errors in ADB and installations were successful but I could not boot into TWRP. After using DC Unlocker, I went back into fastboot and used ADP to install TW RP. I was then able to boot into TW RP. So the difference that DC unlocker made was that it allowed me to use ADB to successfully install TWRP.
I had the very same issue previously with another device. It was running an old version of TWRP. Regardless of what I flashed, it would give errors, etc.
However, using ADB, I flashed the very latest recovery and voila! Flashed a rom successfully as well as other apps without any issues.
It's always best to use the latest possible recovery to avoid issues with flashing.
Glad you solved your problem
Wirmpolter said:
DC-Unlockr allowed you to use adb to flash twrp? How were you able to do that exactly?
Click to expand...
Click to collapse
Good sir, can you link me to a working twrp? I tried several twrps, but i cant seem to boot into recovery. TIA
marktheripper said:
Good sir, can you link me to a working twrp? I tried several twrps, but i cant seem to boot into recovery. TIA
Click to expand...
Click to collapse
Were you running Android Nougat or Oreo? I've just used the TWRP's found here on the xda forums. However, I didn't use TWRP nor dc-unlockr to fix my issue. Have you tried the hardware button combo of volume up And power to boot into it?
Oreo. I tried using the twrps available, but i cant seem to boot into twrp. It goes directly to error mode. Im using the power + vol up btw.
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone
up
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.
cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.
Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.
Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?
Model: BLN L-24
I am stuck in error mode with
Func NO: 11 (recovery image)
Error NO: 2 (failed load!)
I have tried to re-flash several custom recovery I have used in the past, however none seem to work and end with the same result.
I have also tried flashing the stock recovery2.img from the Update.app for my model, but that also doesn't work and ends with a FAILED (remote: Partition Error)
I have run into troubles before, but I'm stumped with this one, I can at least still boot into fastboot.
Any help would be appreciated.
Hyperweasle said:
Model: BLN L-24
I am stuck in error mode with
Func NO: 11 (recovery image)
Error NO: 2 (failed load!)
I have tried to re-flash several custom recovery I have used in the past, however none seem to work and end with the same result.
I have also tried flashing the stock recovery2.img from the Update.app for my model, but that also doesn't work and ends with a FAILED (remote: Partition Error)
I have run into troubles before, but I'm stumped with this one, I can at least still boot into fastboot.
Any help would be appreciated.
Click to expand...
Click to collapse
What's your Android version. What were you trying to do. What recoveries have you tried and what's the command you're using. I had the same error yesterday because I flashed wrong TWRP. Fixed it by reflashing correct image.
Mannan Qamar said:
What's your Android version. What were you trying to do. What recoveries have you tried and what's the command you're using. I had the same error yesterday because I flashed wrong TWRP. Fixed it by reflashing correct image.
Click to expand...
Click to collapse
The version was Android 8 Oreo
I started out trying to go back to EMUI 8.0 from Open Kirin RROS Beta 2. So I followed this guide https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
I tried the TWRP from download in the guide that was in the HWOTA8_BLN folder along with the TWRP from here https://forum.xda-developers.com/honor-6x/development/rom-emui-8-0-0-honor-6x-dual-sim-t3794079
The command I was using to flash the recoveries I believe is correct also which is the fastboot flash recovery_ramdisk "name of image" command. That command will flash successfully with the custom recoveries, however it will still bring up the error mode despite pressing +vol button.
The stock recoveries I extracted from the update.app file, I downloaded from here: https://pro-teammt.ru/firmware-database/?firmware_model=bln-L24&firmware_page=0. Which are the stock recoveries that end up with the FAILED (remote: Partition Error) Message.
Hyperweasle said:
The version was Android 8 Oreo
I started out trying to go back to EMUI 8.0 from Open Kirin RROS Beta 2. So I followed this guide https://forum.xda-developers.com/honor-6x/how-to/update-bln-l22c675-emui-5-x-x-to-emui-8-t3819317
I tried the TWRP from download in the guide that was in the HWOTA8_BLN folder along with the TWRP from here https://forum.xda-developers.com/honor-6x/development/rom-emui-8-0-0-honor-6x-dual-sim-t3794079
The command I was using to flash the recoveries I believe is correct also which is the fastboot flash recovery_ramdisk "name of image" command. That command will flash successfully with the custom recoveries, however it will still bring up the error mode despite pressing +vol button.
The stock recoveries I extracted from the update.app file, I downloaded from here: https://pro-teammt.ru/firmware-database/?firmware_model=bln-L24&firmware_page=0. Which are the stock recoveries that end up with the FAILED (remote: Partition Error) Message.
Click to expand...
Click to collapse
You tried to use HWOTA 8 to go back to stock? Dude. Use Hurupdater. Now, to fix. First of all search XDA for TWRP for hi6250. You can use Elemental but try this one first. Flash it via PowerShell. Does that give any errors? Now once it's flashed, don't reboot. Disconnect phone from PC and hold Volume Up and Power button simultaneously. You should boot into TWRP. What does bootloader say. Phone Locked or Unlocked? What about FRP? The stock recovery didn't work cause you used the BLN-L24 one which is for EMUI 5. You're on EMUI 8. Try to boot into TWRP
Mannan Qamar said:
You tried to use HWOTA 8 to go back to stock? Dude. Use Hurupdater. Now, to fix. First of all search XDA for TWRP for hi6250. You can use Elemental but try this one first. Flash it via PowerShell. Does that give any errors? Now once it's flashed, don't reboot. Disconnect phone from PC and hold Volume Up and Power button simultaneously. You should boot into TWRP. What does bootloader say. Phone Locked or Unlocked? What about FRP? The stock recovery didn't work cause you used the BLN-L24 one which is for EMUI 5. You're on EMUI 8. Try to boot into TWRP
Click to expand...
Click to collapse
https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959
Ok so I flashed this one with Powershell, and it didn't show up any errors. However I still can't seem to boot into recovery and it continues to show up error mode, even while doing as you say and pressing the vol+ and power in fastboot. Also both FRP and Phone are unlocked
Hyperweasle said:
https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959
Ok so I flashed this one with Powershell, and it didn't show up any errors. However I still can't seem to boot into recovery and it continues to show up error mode, even while doing as you say and pressing the vol+ and power in fastboot. Also both FRP and Phone are unlocked
Click to expand...
Click to collapse
Use Huawei multi tool 8 to unbrick your device it's easier and just use the firmware that you were in before
Hyperweasle said:
https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959
Ok so I flashed this one with Powershell, and it didn't show up any errors. However I still can't seem to boot into recovery and it continues to show up error mode, even while doing as you say and pressing the vol+ and power in fastboot. Also both FRP and Phone are unlocked
Click to expand...
Click to collapse
Try Dload
hamid1999 said:
Use Huawei multi tool 8 to unbrick your device it's easier and just use the firmware that you were in before
Click to expand...
Click to collapse
Mannan Qamar said:
Try Dload
Click to expand...
Click to collapse
I tried both of those things and still couldn't get it working.
dload doesn't pop up and multi tool fails to flash the recovery_ramdisk.img when trying to unbrick it.
I do remember before any of this happened that I was having a problem with my internal storage as I didn't have access to it. All file mangers I tried couldn't access it and showed it up as blank and TWRP showed it with 0mb.
I have a feeling that my internal storage is screwed up and that's why all attempt to flash anything have failed. I may just have face the fact that it's dead.
Hyperweasle said:
I tried both of those things and still couldn't get it working.
dload doesn't pop up and multi tool fails to flash the recovery_ramdisk.img when trying to unbrick it.
I do remember before any of this happened that I was having a problem with my internal storage as I didn't have access to it. All file mangers I tried couldn't access it and showed it up as blank and TWRP showed it with 0mb.
I have a feeling that my internal storage is screwed up and that's why all attempt to flash anything have failed. I may just have face the fact that it's dead.
Click to expand...
Click to collapse
As long as it turns on it isn't dead. Did you try DC unlocker? That often works. Try it and if it fails go to service center and play dumb. Say it happened like this after a update.
Edit. Let it power off. When it turns on hold Volume Up
Under AICP14 i had significant problems with Bluetooth, so I'm back to the latest pie version via erecovery ... all right. Then in preparation for root in TWRP noticed that data is again encrypted. So reset to factory settings via twrp, rebooted into the TWRP3.2.3-3 and formatted data with yes. Thereafter, on the screen was "formatting done," but down the blue animation was still running around, about 10 minutes, apparently hung. Since I could not do anything else, power button long pressed and booted again into the TWRP, but the hangs at the entrance screen, probably clear in the unsuccessful attempt to decrypt data. The Erecovery with the ability to restore the system and the stock recovery is not reachable for me, with everything I've tried. Fastboot is still to reach ... When booting the device will always hang at the inscription "The device is booted" ...has someone an idea? ? Thanks for thinking!
How to restore erecovery? It was pie, latest version installed from erecovery on the device before this crash...
Flash the erecovery partition. Extract the IMG from the update.zip file and flash the same.
shashank1320 said:
Flash the erecovery partition. Extract the IMG from the update.zip file and flash the same.
Click to expand...
Click to collapse
Got an error trying to extract:
borisku said:
Got an error trying to extract:
Click to expand...
Click to collapse
Go to settings and disable checksum or some verification. Dont remember the exact one but its there in setting
shashank1320 said:
Go to settings and disable checksum or some verification. Dont remember the exact one but its there in setting
Click to expand...
Click to collapse
I Managed to extract ERECOVERY_RAMDI.img and ERECOVERY_RAMDI.img header... i also extracted SYSTEM.img/header and RECOVERY_RAMDIS.img/header frum the update.app
Is it correcht to follow this syntax:
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img
to reflash the erecovery? btw. i dont know the exact version of the firmware i installed, it was yesterday i think it had been BKL-L09 (9.0.0.233) C432E4R1P12 , but i cant find that as an update.zip. So i took BKL-L09C432E4R1P8B108-log (9.0.0.108) and extracted the files from there...
borisku said:
I Managed to extract ERECOVERY_RAMDI.img and ERECOVERY_RAMDI.img header... i also extracted SYSTEM.img/header and RECOVERY_RAMDIS.img/header frum the update.app
Is it correcht to follow this syntax:
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img
to reflash the erecovery? btw. i dont know the exact version of the firmware i installed, it was yesterday i think it had been BKL-L09 (9.0.0.233) C432E4R1P12 , but i cant find that as an update.zip. So i took BKL-L09C432E4R1P8B108-log (9.0.0.108) and extracted the files from there...
Click to expand...
Click to collapse
As long as it is pie erecovery, it should work fine. Yes, flash that file.
shashank1320 said:
As long as it is pie erecovery, it should work fine. Yes, flash that file.
Click to expand...
Click to collapse
No success:
sending erecovery_ramdisk (32768KB)
okay [0.707s]
writing 'erecovery_ramdisk
FAILED (remote: command not allowed)
or should i flash to recovery_ramdisk not to Erecovery_ramdisk?
borisku said:
No success:
sending erecovery_ramdisk (32768KB)
okay [0.707s]
writing 'erecovery_ramdisk
FAILED (remote: command not allowed)
Click to expand...
Click to collapse
Is your bootloader still unlocked? There was a guide i posted in v10 section for going back to stock if that's what you are interested.
shashank1320 said:
Is your bootloader still unlocked? There was a guide i posted in v10 section for going back to stock if that's what you are interested.
Click to expand...
Click to collapse
Phone unlocked
FRP unlock
i try to come back to erecovery to install latest Emui 9, and from that point i want to return to AICP14...
@edit: I got it following this post:
https://forum.xda-developers.com/showpost.php?p=78752217&postcount=22
i reached erecovery and i´m installing 9.0.0233 via wifi.... hope it wil run til its completed
The most ****ty problem comes if you want to remove the idiotic encryption via formatting data partition in twrp with the red "yes" ...
Thanks to shashank1320!