Related
I have attempted everything, I don't remember my B version which doesn't help. I know I was on 5.0.2 and I'm located in the UK.
I'm stuck in infinite boot loop which is happening because I deleted the OS by Accident.
I have attempted to Flash a B330 Version but boot loop. I grabbed the official Update for V5.0.2 Extracted the SYS and the other necessary files to "Unbrick" using the Honor 7 Multi-tool.
When I'm supposed to go to eRecovery I can't go to it. I have removed the cable, HOLDing both Volume Buttons and Power, when the Honor Logo pops up I remove the Power Button and it doesn't go to eRec, it just restarts due to Boot loop.
Does anyone have any suggestions what to do?
Give a shot for "Honor 7 Multi-Tool" that can be found on this Forum, that contain "Unbrick" task what you can use to unbrick your device. And that contains simple tutuorial how to do it.
Give a shot for B180 package with your country, that is FULL patch for 5.0.2 version. When that is done you can upgrade your phone to the B330.
And also for ERecovery, try hold all 3 buttons so long that you reach the recovery menu, you dont need release those buttons until you are on recovery.
kenkae said:
Give a shot for "Honor 7 Multi-Tool" that can be found on this Forum, that contain "Unbrick" task what you can use to unbrick your device. And that contains simple tutuorial how to do it.
Give a shot for B180 package with your country, that is FULL patch for 5.0.2 version. When that is done you can upgrade your phone to the B330.
And also for ERecovery, try hold all 3 buttons so long that you reach the recovery menu, you dont need release those buttons until you are on recovery.
Click to expand...
Click to collapse
thanks for your help,
I have already attempted the unbrick function on H7 Multi-Too but I can't get through to Recovery for some reason after MT is finished with transferring the files to the phone. I'v been holding the 3 buttons for 5 minutes and it just Boot-Loops, I must be doing something wrong.
Regarding how I "Deleted" the system and got into this mess, I used the Advance Wipe function in TWRP and wiped the system by accident. This might be affecting eRecovery?
I'm not sure If I used the B180 Pack or one below. So I'll re-do it and see how it goes.
Galio094 said:
thanks for your help,
I have already attempted the unbrick function on H7 Multi-Too but I can't get through to Recovery for some reason after MT is finished with transferring the files to the phone. I'v been holding the 3 buttons for 5 minutes and it just Boot-Loops, I must be doing something wrong.
Regarding how I "Deleted" the system and got into this mess, I used the Advance Wipe function in TWRP and wiped the system by accident. This might be affecting eRecovery?
I'm not sure If I used the B180 Pack or one below. So I'll re-do it and see how it goes.
Click to expand...
Click to collapse
No that wont effect anything ifyou wipe whole device, because you flash Boot/System/Recovery and other sectors with Multi Tool. So that install's a fresh install there.
Give a shot for that B180 package with correct country for you, flash all sectors with MultiTool and then reboot to recovery. That should work, if not then something goes wrong with flashing.
Heres my Thread from this forum, i think i have done that situation what you have going now.
http://forum.xda-developers.com/honor-7/general/honor-7-premium-stock-images-plk-l01-t3369369
Couldn't find B180, Only B130.
Used Huawei Updater to Extract Files.
and used multi tool's unbrick, Attempted to go to eRecovery no success.
Tried Multi-TOols Reboot to eRecovery no success as it needs USB Debugging.
I'm stuck :'(. Also lost Ability to go back to TWRP
Here is B180 for your Device (United Kingdom): http://www.hihonor.com/uk/support/details/?DOC_ID=77725
Boot your phone to the Fastboot, then flash new TWRP to your device. Shut it down and try boot to the Recovery.
When you have successfully rebooted to the TWRP, create folder what is named to dload inside your SDCard, then put that B180 "Update.app" file inside that folder.
When that step is done, start UpdateExtractor, and take Unbrick files out from that .app file.
Next step will be unbricking with MultiTool, when its done just try reboot your phone first normally to the system, if that works just go: Settings->Update->Local Packet from SDCard.
And your device start updating that B180 packet completely.
After you have updated your phone to B180, download C432B330 packet and just replace that "Update.app" file on your SDCard with that B330 file and repeat previous steps.
The problem was B130 and B180. Before deleting my OS I attempted a ROM Flash from B330 when being on a B180 System (which tells you not to do). So my System froze at B330 I guess. WHen I attempted to Unbrick on B330 it worked, didn't work on B130 or B180.
Though the process itself was correct, was just the package . Thanks
Hi,
Today i received a notification on my L22 to update to Marshmallow (310).
But when it reboots into recovery (stock), it says system update failed.
Note:
I have rooted my phone and installed custom rom before. But i used to get back to stock (both rom and recovery) with a TWRP restore. This has worked with all the previous updates of Lollipop (e.g. 130 to 150), but its not working with Marshmallow.
Can someone please help!!.
Can someone please help. I hope this is a beta version. Actually I had opted for the beta previously.
there are no restoration files zips for MM yet, alternatively, you can flash TWRP back via adb and restore your back up. else, follow the steps in thread below....good luck!
http://forum.xda-developers.com/honor-5x/help/bricked-honor-5x-t3328308
Thank you @nandakalyan @Arobase40 for the information.
I can check with them. But when i tried to login to their community, for some reason, my login credentials weren't recognized.
As an update, I tried the following
I downloaded the lollipop 150 firmware and flashed the BOOT, RECOVERY, SYSTEM and CUST image files. But I received REMOTE: COMMAND NOT ALLOWED error while flashing CUST. I even tried installing the USB/ADB drivers again. Still no luck.
Then i tried the update. Still the same error.
Again i followed step 1, then relocked the bootloader (successfully). But still got the same error. (Because i read somewhere that it could be due to modified firmware)
Looks like some issue with the package. So i might have to get back to them.
I will post the update once i get the update from them. Thank you very much guys.
Arobase40 said:
The CUST image file can't be flashed !
But I saw someone was able to rebuild the /Cust folder and its content but I'm too lazy to do the search...
It's in the Honor 5x thread.
Click to expand...
Click to collapse
That is correct, cust.img can't be flashed through ADB, I have had this issue too.
@mani0608
The only best way is to flash stock recovery, create a dload folder in the root of the sd-card, place the update.app (original firmware file) in it, boot into download mode (power + vol up + vol down) and let the whole factory image be flashed.
nandakalyan said:
That is correct, cust.img can't be flashed through ADB, I have had this issue too.
@mani0608
The only best way is to flash stock recovery, create a dload folder in the root of the sd-card, place the update.app (original firmware file) in it, boot into download mode (power + vol up + vol down) and let the whole factory image be flashed.
Click to expand...
Click to collapse
I followed this and then tried the OTA and voila it worked!!
mani0608 said:
I followed this and then tried the OTA and voila it worked!!
Click to expand...
Click to collapse
Super....congrats! Glad it worked
I was going back to full stock on my 5X, and things must have give sideways... It got stuck in a bootloop (even a stock recovery FDR hangs) and now I fear it might be bricked. I had always figured that if all else fails, I could flash something in fastboot, but that's not even available.
I can get out into the fastboot/rescue mode, and my laptop sees the device plugged in, but fastboot doesn't list it as a device, so I can't issue any commands.
Are there any 'last ditch' methods that might get this thing out of the toilet?
LeoRex said:
I was going back to full stock on my 5X, and things must have give sideways... It got stuck in a bootloop (even a stock recovery FDR hangs) and now I fear it might be bricked. I had always figured that if all else fails, I could flash something in fastboot, but that's not even available.
I can get out into the fastboot/rescue mode, and my laptop sees the device plugged in, but fastboot doesn't list it as a device, so I can't issue any commands.
Are there any 'last ditch' methods that might get this thing out of the toilet?
Click to expand...
Click to collapse
These are instructions I posted for someone else with a L24 you need to adjust the files to your phone L2x
The dload/update.app works, just be patient and follow the instructions I posted.
If you need to restore to Stock B151 use this TWRP backup >> https://www.androidfilehost.com/?fid=24588232905720643
You also need this version of TWRP to restore it >> https://www.androidfilehost.com/?fid=24545070682210514
Fastboot flash TWRP.img
in TWRP go to backup and check only boot.img > make the backup
now extract the b151 backup to your PC and copy it to the phone
their will be a directory named TWRP/BACKUPS/yourserialnumber/put the backup here
Now in TWRP choose Restore choose the backup you just copied over and be sure all the boxes are checked for restore
swipe to restore
be sure B331 dload/update.app are on the sdcard
In TWRP choose Reboot / Power Off
unplug the usb
hold power + volume up + volume down
when you see the first honor screen let go of power and hold the volume buttons till the update starts (be patient it takes a while)
EMUI recovery will load and do the update when it reboots your done
Click to expand...
Click to collapse
Yeah... been here, done this already unfortunately. The update.app is on there... The process actually gets to 5% then it goes and tries to boot, and hangs. That's where I was when I tried to get twrp on there to take a look at the filesystem.
Maybe the update.app file is corrupt/not fully copied. I'll copy it back on the SD and try again tonight.
Usually a very old (stable) release is more advisable if it's Lollipop.
Are you sure you're not running a second instance of ADB? I got that once and had to check windows processes.
Changing usb cable?
LeoRex said:
Yeah... been here, done this already unfortunately. The update.app is on there... The process actually gets to 5% then it goes and tries to boot, and hangs. That's where I was when I tried to get twrp on there to take a look at the filesystem.
Maybe the update.app file is corrupt/not fully copied. I'll copy it back on the SD and try again tonight.
Click to expand...
Click to collapse
So you restored a TWRP backup of the stock System / Boot and Recovery and the Update.APP failed ?
you used the wrong update.app or the wrong backup is the only explanation, as this works 100% of the time
Other option is you have messed up partitions, usually flashed img files from different rom versions.
Well, turns out that the update.app file on the SD was corrupt. I copied it again and the stock update till took over and loaded things properly.
Second issue is a bear... My laptop NP longer can communicate with the phone via fastboot. Based on what I see, it's a driver issue on my laptop... So I gotta figure that out of I want to get TWRP back on there.
LeoRex said:
Well, turns out that the update.app file on the SD was corrupt. I copied it again and the stock update till took over and loaded things properly.
Second issue is a bear... My laptop NP longer can communicate with the phone via fastboot. Based on what I see, it's a driver issue on my laptop... So I gotta figure that out of I want to get TWRP back on there.
Click to expand...
Click to collapse
[emoji3] sorry but you aren't getting any rest are you? Once you fix something you find another thing to fix...
If you use Windows, try and make restore points occasionally so that you can revert to the last fully working point.
Also if you can, see if there's any checksum for the firmware update files. It helps a lot.
Hi guys, i got my H9 yesterday and because i thought i read enough on this forums i wanted to unlock it then install TWRP and install superSU to gain root access and stick with the stock firmware.
Unlocking went perfectly fine,phone booted to OS, than i flashed twrp 3.1.1-1 as advertised here and made a factory reset. Phone was stuck in bootloop for unknown reason.
I made several wipes and somehow managed to check all boxes in the wipe menu which erased the whole OS.
Now i read here that others have the "no OS" problem too but because i still have all unlocked fastboot and twrp i wanted to ask which method is best to flash back the original FW.
Which stock ROM is safe to install? i have european H9 is STF-L09C432B170 the right one for me?
Which method is the best to install it? Copy the 3 zips to internal stoagre via OTG device and install it out of twrp? I read that there is also a force method where users can push vol up, vol down and power simultaneously and enter the huawei install force mode.
I am quite sad that the phone was stuck in bootloop after twrp install and still dont know what caused it. When i install it from twrp there are 3 zips: update, data full public , hw eu. In which order do they have to e installed and is one of them overwriting the TWRP recovery?
Please give me a short hint/procedure, im quite afraid that i cant get my phone back to work and it is brand new. I dont know what caused the unsolvable bootloop.
Best regards and many thanks
Hi.
Check this:
https://forum.xda-developers.com/showpost.php?p=73334439&postcount=1
This help you.
Regards
thanks for the hint but i cant find a solution for me there.
ut this
i copied the 3 .zip files to internal today but TWRP doenst allow me to write them it fails with "write err errno 9"
then i tried to copy the update.pp in DLOAD folder on micro sd but this is not possible because filesize is over 2gb. i tried to format micro sd with twrp to exfat but it till doesnt work. please give me a little hint what to do im completely desperate about the situation.
Today i installed Huawei Multitool and extracted the .img file out of the update.app files, i was able to flash all 4, system, boot, recovery and cust.
Now the rec. menu is back to stock and everything got installed but the phone still isnt booting. i think it is because i missed the userdata.img which i cant find anywhere.
Other users here have the same problem. Is there a firmware package which includes all 5 .img data?
Best regards
i found the official huawei service full repair firmware with all necessary files for unbrick (system, cust, recovery, userdata, boot) flashed them via fastboot but stil device is "hanging" after the warning message that its unlocked. i think it is because i wiped vendor data in twrp but i cant flash vendor.img in fastboot. it is included in the fw package but cant be transfered to phone via fastboot. it stops at part 1/2 because the filesize allowd is around 470mb max but the extracted file has a size of 670. anyone know what to do?
Best regards
You need to go via the Rebrand way with no rebrand. I had the same problem and was trying to use the multitool without success. The oeminfo can be flashed alternatively if it fails during the HWOTA process.
https://forum.xda-developers.com/honor-9/help/how-flash-oeminfo-t3657499
ok i download all the folders with the .bat file. Then i download C432B150 from the czech site and add it to the update folder. Than i rename the 3 files accoding to the manual and run the .bat file but without rebranding right?
Des this tool any different than the HuaweiMultiTool or fastboot with flash command?
Best regards
I treid out HWOTA, the first step installing twrp is successful than i disattach usb cable as described and enter twrp. Then it says in twrp i have to connect again and press enter but then the bat file stops and doenst go on. i dont come to the point where i can choose rebrand or flash firmware.
Whats wrong here?
edit: i saw in the .sh file that the script executes wait_adb but my phone is not entering adb mode as it seems when in main screen of twrp. is this normal or do i have to set it manually in twrp
best regards
I was able to install the B130 now via 3 button recovery. Now im on B130 but cant update elsewhere. Also the 2 capacitive buttons are not working. Bootloader is locked again. Everything is stock and the phone runs great. When i update with the 3 buton method from external sd, which firmware should i use? i tried B150 full OTA but it aborts after 5% with an error. Do i only need to get a small OTA package now?
How can i put my cap. buttons back to work? Too bad only the 3 button method worked to recover the phone.
Best regards and many thanks.
I did the HWOTA with b120 firmware and then used firmware finder to update to b150.
The bug with capacitive buttons is present till Oreo. I use the home button gestures anyways.
Hope it helps.
ok, thats bad but they worked with the initial revision of b130 and b150 when i downloaded it OTA. Is this something like a fuse like.knox at samsung which happens at custom flashing?
Sent from my GT-I9300 using Tapatalk
the HWOTA method doesnt work, the batch file gets stuck after connecting the phone in twrp back to computer. in script it says wait_adb but it is not recognized somehow.
do u know a solution? anotherone here got that problem too.
im very afraid of that, i read here that everything related to twrp 3.1.1-0 and 3.1.1-1 is problematic a lot of people cant boot after installing twrp and can wipe whtever they want the phone never boots fully
whats the difference in the B130/B120 the phone came from huawei and the version flashed via tools? when i got it everything worked
i have this version.
ok so install twrp have frq and bootloader unlocked and then do backup out of recovery? with your file? can you provide download link? is this then a zip file?
I want to solve the thread and how i solved problem.
The B130 service firmware by huawei could be installed via 3 button method, than i was able to go up to the newest B180 via firmwarefinder and DNS method but with not working cap. buttons and flash etc.
Yesterday i installed TWRP 3.1.1-1(temporary) via HWOTA.zip method (ireplaced the older twrp in recovery folder) and successfully installed B120 and got the buttons etc working again. Then installed root and now system works fine and is rooted. My mistake was to install twrp over B130 or B150 which i downloaded OTA at the first day i got the phone. I tested this yesterday to install TWRP along with B150 and unlocked bootloader, infinite bootloop again. With B120 the TWRP 3.1.1-1 works out of the box without any loops.
The 2 trouble solvers where B130 service firmware and HWOTA with B120.
The external SD had to be inserted in card reader on PC because of the large filesize of the B130.
I would recommend to everyone before starting to play with the H9 to move the B130 folders to phone while it is still accessible. When everything bricks like in my case and u still have twrp than you can go to twrp main screen and connect phone to computer to rename the folder with B130 to "dload" and arrange update.app accordingly on PC or in TWRP file manager.
Can i set this topic to [SOLVED] myself?
Best regards
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
this works flawlessly with 3 button method
Hi everyone,
I ran out of ideas with my problem, and could really use some help / advice with this.
Trying to updgrade my STF-L09C432 from B368 to B385 using HuRu updater, something went wrong and now it bootloops after the blue Honor logo.
Fastboot, Huawei eRecovery and TWRP are still working and accessible, my device is bootloader unlocked and says FPR unlock in fastboot mode.
So here's the detailed steps and procedure which I followed:
0) TWRP Backup of System + Data
1) Load three update files (FullOTA) via FF: update.zip (update.zip), update_data_full_public.zip (update_data_full_public.zip), update_full_STF-L09_hw_eu.zip (STF-L09_hw_eu/update_full_STF-L09_hw_eu.zip)
2) Create folder on SD-card with above files and TWRP v0.3 as recovery.img and the HuRu 0.4 zip file. Additionally I've left the HuRu 0.3 in the same folder renamed as HuRUpdater_0.3_old.zip
3) Installed the HuRu 0.4 from TWRP with zip verification disabled (tried before with enabled, but it failed -> call me stupid but I've double checked the checksum with a new download, so I took the risk).
4) the installation log showed warnings about some missing .zip files, but I ignored those as well, as I've never heard of them and didn't have them from FF.
5) rebooted the system and caught the first bootloop
Now I tried myself to fix it the following way, but unsuccessful until now:
1) Flashed TWRP into recovery_ramdisk because I didn't know the right procedure to boot into it
2) Flashed the new B385 versions of KERNEL.img, RAMDISK.img and RECOVERY_RAMDIS.img which I extracted from the UPDATE.APP -> still bootloop
3) Flashed TWRP into recovery_ramdisk again because I still didn't know the right procedure to boot into it
4) Flashed the old B368 versions of KERNEL.img, RAMDISK.img which I extracted from the UPDATE.APP, but not the RECOVERY_RAMDIS.img this time -> still bootloop
5) Then I've managed to boot into TWRP finally, and tried to restore my previous backup as a last resort, but that still didn't resolve my bootloop
Anybody has any idea what I could still try? Maybe I'm missing something obvious, or I'm still to new to this to see what is wrong.
If possible I'd like to keep my data intact, but I could probably extract most of it out of the backup, if nothing else helps.
Thank you very much!
Best regards,
Chris
Nobody has an idea?
Maybe the Seniors on the Honor9, @OldDroid or @zxz0O0?
After I've tried to restore the previous TWRP backup, now also TWRP won't boot anymore, therefore I'm stuck with fastboot or the Huawei stock recoveries...
Schrubbi said:
Nobody has an idea?
Maybe the Seniors on the Honor9, @OldDroid or @zxz0O0?
After I've tried to restore the previous TWRP backup, now also TWRP won't boot anymore, therefore I'm stuck with fastboot or the Huawei stock recoveries...
Click to expand...
Click to collapse
well, aslong as its still unlocked (frp & bl) i'm able to help.
Do you have telegram? if so, send me your username through pm.
Regards
I managed to get into TWRP again when I've installed the latest kernel and recovery images. After that I've realized that I still had Magisk installed and Active.
Uninstalling that solved my bootloop for now.
Unfortunately my backup restore just returned me to the previous version B368 which I already had installed... so lets see what happens if I apply the update again
---------------------
Edit:
Update applied, without magisk installed, still bootloop... At least the way back was quicker this time
Any hints what's going wrong are appreciated!