MT7-L09 - UK model.
I can't remember exactly how this has happened but basically I had a demo version of the device, so flashed it with a TL10 things (Huawei being unclear, I blame them), then reset it a bunch of times because (as expected) things were going wrong. I then Unlocked, rooted etc, and flashed another firmware. The phone reverted to Chinese, called itself JAZZ. I managed to get it back to british, flashed another firmware and everything is OK ish - BUT a factory reset wipes everything and does not theme it like 'out of the box'. There's also a few apps I don't think should be there, like 'Payment UICC'.
I've tried using the unpacker and flashing boot.img, recovery.img, system.img cust.img etc etc, but when I go to factory reset it still has the same issue.
To be honest, I don't even know which the latest UK firmware is - and I don't know if the UK firmware is different toe the EU firmware.
Please help, I'm totally stuck here
re cust fail
I am in the same case as you and so far I have not found solutions;
it would take a backup of the system.
I have the European model.
guys flash appropriate recovery and force flash via adb ..
Simona Simmy said:
guys flash appropriate recovery and force flash via adb ..
Click to expand...
Click to collapse
I have the same problem on the TL10 eu but do not know which and the procedure to do it via adb
not familiar with the commands!!!
edilmacbook30 said:
I have the same problem on the TL10 eu but do not know which and the procedure to do it via adb
not familiar with the commands!!!
Click to expand...
Click to collapse
can u upload pic how that cust fail looks like ? never had this problem..
lorenzw said:
I am in the same case as you and so far I have not found solutions;
it would take a backup of the system.
I have the European model.
Click to expand...
Click to collapse
I don't suppose anyone here with a UK model (L09) Can help me out there at all? Would I be able to do a nandroid restore from someone elses phone?
Simona Simmy said:
guys flash appropriate recovery and force flash via adb ..
Click to expand...
Click to collapse
Ugh - some more help is needed! I have flashed EVERY RECOVERY that works, and you CAN'T just force flash via ADB because it doesn' let you on every partition.
-Where is the 'appropriate recovery' for the L09?
-Where are the latest firmware restore imgs?
HOWEVER, even in the few instances when I WAS able to flash the cust.img (as I said in the OP) it didn't help - it still says 'cust fail' during the factory reset. And then it's wiped and reset, but not 'out of box' - all theming is gone, apps all over the screen, apps I don;t even know if should be there, polaris office not installed etc.
tmorterlaing said:
I don't suppose anyone here with a UK model (L09) Can help me out there at all? Would I be able to do a nandroid restore from someone elses phone?
Ugh - some more help is needed! I have flashed EVERY RECOVERY that works, and you CAN'T just force flash via ADB because it doesn' let you on every partition.
-Where is the 'appropriate recovery' for the T09?
-Where are the latest firmware restore imgs?
HOWEVER, even in the few instances when I WAS able to flash the cust.img (as I said in the OP) it didn't help - it still says 'cust fail' during the factory reset. And then it's wiped and reset, but not 'out of box' - all theming is gone, apps all over the screen, apps I don;t even know if should be there, polaris office not installed etc.
Click to expand...
Click to collapse
man if u search mate 7 forum ull find it ..
https://www.google.com.my/webhp?sou...on=1&espv=2&ie=UTF-8#q=MT7-L09V100R001C00B127
Update: so I downloaded the kindly provided firmware above, and doing a force upgrade gets the 'update' bar all the way to the end, where it just freezes. After about 2 hours I unplugged the phone, and that seems to trigger an 'update failed' message - so that didnt work.
Also th sim card isn't being recognised - which I assume is to do with my baseband? Its currently 21.213.00.00.031
But because I can't flash the modem (see below) I can't seem to do anything about it...
So, I tried to use the extractor, and try to flash each img it extracts from fastboot. I try to fastboot flash:
system: success
cust: success
modem: FAILED (remote: Command not allowed)
boot: success
cache: success
ptable: FAILED (remote: Command not allowed)
fastboot: FAILED (remote: Command not allowed)
recovery: success
userdata: success
When I made it Chinese by accident, is there a chance the partitions where somehow messed up, like resized or something? It's so frustrating that a factory reset doesnt put it how it should, because that means something isn't right... and it also means future updates probably won't work.
Is there anything I can do?
Hi,
I have mt7-l09 french and the same situation (120->chinese->120->cust fail)
No ip calls, also
Tried: extractor, adb, shell commands (rooted)..
@Volgot
Hi, you have a solution ?
yes! and no..
lollipop instalation fixed it, but..
if you go back cust fail do it too )
Related
I tried to downgrade from L29C185B320 to L29C185B200 however I'm now faced with the following:
(Prior to the downgrade I did flash the B320 recovery.img as I was on TWRP before)
On boot, Huawei logo displays then display goes black. Still powered on but not displaying anything
eRecovery is accessible, tried wiping cache but no change, also tried factory reset. The "download latest version and recovery" option isn't possible, "getting package info failed"
Can't access device over ADB as it doesn't detect in "adb devices"
Bootloader is now locked (was unlocked before)
I can "fastboot reboot" but no other command works due to bootloader locked
I can do Vol Up+Down reset but takes me right back to blank screen after installing. I've tried with various update versions (B162, B180, B200, even going back to B320) but its the same result every time.
Afraid I now have a brick, would appreciate any help I can get.
MuPp3t33r said:
I tried to downgrade from L29C185B320 to L29C185B200 however I'm now faced with the following:
(Prior to the downgrade I did flash the B320 recovery.img as I was on TWRP before)
On boot, Huawei logo displays then display goes black. Still powered on but not displaying anything
eRecovery is accessible, tried wiping cache but no change, also tried factory reset. The "download latest version and recovery" option isn't possible, "getting package info failed"
Can't access device over ADB as it doesn't detect in "adb devices"
Bootloader is now locked (was unlocked before)
I can "fastboot reboot" but no other command works due to bootloader locked
I can do Vol Up+Down reset but takes me right back to blank screen after installing. I've tried with various update versions (B162, B180, B200, even going back to B320) but its the same result every time.
Afraid I now have a brick, would appreciate any help I can get.
Click to expand...
Click to collapse
I have same problem...
And cant find any solution for adb commands work again. I don't know where is the problem.Tryed everythink. And nothing. Maybe problem is FRP lock, but in bootloader its nothing showing. Just phone unlocked. I saw many users have this problem.
delete
Same problem
Hi guys,
I'm new here and I have the same problem after my try to downgrade from EMUI5 to EMUI4.1 Mashmallow.
My Phone bootload twice and after my only choice is to use eRecovery taht don't work. I tried to use italian swiss knife nad the other from Asia to unlock the phone but it don't work at all, I got the same message Failed : remote command unaviable, or something like that.
Please can you help me to recover my phone?
Thank you in advance for all your suggestions
lecsolo said:
Hi guys,
I'm new here and I have the same problem after my try to downgrade from EMUI5 to EMUI4.1 Mashmallow.
My Phone bootload twice and after my only choice is to use eRecovery taht don't work. I tried to use italian swiss knife nad the other from Asia to unlock the phone but it don't work at all, I got the same message Failed : remote command unaviable, or something like that.
Please can you help me to recover my phone?
Thank you in advance for all your suggestions
Click to expand...
Click to collapse
Try by dloadl UPDATE.APP (C185B521) from Update.zip.
After re-try rollback
pescixx79 said:
Try by dloadl UPDATE.APP (C185B521) from Update.zip.
After re-try rollback
Click to expand...
Click to collapse
Thank you, is the right update for an EU phone the C185B521?
lecsolo said:
Thank you, is the right update for an EU phone the C185B521?
Click to expand...
Click to collapse
I was on C185B521, flashed Rollback and tryed to downgrade to C185B180. Had ISSUE.
I extracted Update.app from C185B521 zip and Flashed (dload) (had keyboard issue and other not working)
Try to rollback again and alla woked fine.
pescixx79 said:
I was on C185B521, flashed Rollback and tryed to downgrade to C185B180. Had ISSUE.
I extracted Update.app from C185B521 zip and Flashed (dload) (had keyboard issue and other not working)
Try to rollback again and alla woked fine.
Click to expand...
Click to collapse
Ok I will try this, hope it will work on my phone
Thanks for your help
Problem solved this morning I try to boot with vol up and start bouton pressed, when wipe/factory reset appears and selected, then press ok. After that my phone reboot on EMUI 4.1/mashmallow and work fine.
Thank you very much for your help, much appreciated.
r4ason said:
I have same problem...
And cant find any solution for adb commands work again. I don't know where is the problem.Tryed everythink. And nothing. Maybe problem is FRP lock, but in bootloader its nothing showing. Just phone unlocked. I saw many users have this problem.
Click to expand...
Click to collapse
Sigh, that's a pity. I don't think it would be an frp problem in my case as I have my Google account details to login, rather just that it's failing to boot the os partition. What I've gathered from this is that something went wrong with the firmware installation and now that its relocked the bootloader there's no way to push the files into place with adb/fastboot.
Nevertheless, my device is still fairly new so I've sent it back to the supplier, will wait for their response...
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?
Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance
Benfran said:
Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance
Click to expand...
Click to collapse
You can copy the full ota.zip into the root of your storage and can manually install it with system updater.
This update works pretty good here for me. Do you use any magisk modules? Themes for example? Deactivate all and try to install latest ota again.
Benfran said:
Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance
Click to expand...
Click to collapse
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on
Kollachi said:
You can copy the full ota.zip into the root of your storage and can manually install it with system updater.
This update works pretty good here for me. Do you use any magisk modules? Themes for example? Deactivate all and try to install latest ota again.
Click to expand...
Click to collapse
Thanks but I can't do this, as i can't access system settings. Will it work with Oxygen updater app ?
EDIT: Oxygeon updater, also uses system settings...
Qnorsten said:
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on
Click to expand...
Click to collapse
Thanks. Will try this if the above method doesn't work first.
Qnorsten said:
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on
Click to expand...
Click to collapse
Before reflashing i tried to wipe cache from stock recovery, like you mentioned in my other post, but now i'm really screwed i think.
It started correctly the first time, but was stuck on start screen on "starting system" or something like that.... But then suddenly rebooted itself and is now stuck in the boot logo....nothing happening, and unresponsive to my forced restart with keys.
What can i do ?
Thanks
EDIT: Managed to get in fastboot, and started flashing all the .img
But i'm getting some errors with some of them:
Either FAILED (remote: 'Value too large for defined data type') or fastboot: error: boot partition is smaller than boot image (with modem and others)
Benfran said:
Before reflashing i tried to wipe cache from stock recovery, like you mentioned in my other post, but now i'm really screwed i think.
It started correctly the first time, but was stuck on start screen on "starting system" or something like that.... But then suddenly rebooted itself and is now stuck in the boot logo....nothing happening, and unresponsive to my forced restart with keys.
What can i do ?
Thanks
EDIT: Managed to get in fastboot, and started flashing all the .img
But i'm getting some errors with some of them:
Either FAILED (remote: 'Value too large for defined data type') or fastboot: error: boot partition is smaller than boot image (with modem and others)
Click to expand...
Click to collapse
Your command should be something like this
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
and so on
Sorry if I wasn't clear enough about that in my previous post
Qnorsten said:
Your command should be something like this
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
and so on
Sorry if I wasn't clear enough about that in my previous post
Click to expand...
Click to collapse
Oh ok !
I was doing fastboot flash BOOT .... with all of them.
I'll try again now.
Thanks
Benfran said:
Oh ok !
I was doing fastboot flash BOOT .... with all of them.
I'll try again now.
Thanks
Click to expand...
Click to collapse
Any luck?
If not the unbrick msm tools will definitely restore the phone. But also wipe the whole phone
Qnorsten said:
Any luck?
If not the unbrick msm tools will definitely restore the phone. But also wipe the whole phone
Click to expand...
Click to collapse
No luck.
I flashed all the .img and rebooted correctly. As before, everything works fine , except System settings (icon doesn't even appear). So i can't even check what version i have installed...
There was one issue flashing in fastboot though...only with 3 of the .img files :
reserve.img
xbl_config_lp5.img
xbl_lp5.img
With these 3 i got an error, the same one for all 3:
Writing 'reserve' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Any idea as to why i'm getting this error and do you think this is related to the settings error ?
Thank you for all the help !
It finally worked !
I disabled the only magisk module i had active, and again flashed all the .img (still got the same 3 errors as above) and rebooted, and the system settings finally appear.... Although under a weird name.
The settings app is now called "Set data limit".
Also the characters of the clock app name are in Chinese now...
Besides these 2 things, the rest seems to be working fine now with 11.0.6.9
Thanks Qnorsten !
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
Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!