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
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
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
joaomPT said:
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
Click to expand...
Click to collapse
As you are already familiar with adb and other stuff so will write a short post for you.
To download latest firmware, head to
http://forum.xda-developers.com/hon...tock-firmware-packages-honor-7-t3448747/page1
Google, download and install Huawei update extractor and open UPDATE.APP in it (obtained after extracting firmware).
You can see all the images. Just extract recovery and boot to platform-tools folder.
Meantime, do the unlocking command again, with
Fastboot OEM unlock xxxxxxxxxxxxxxxx
Followed by fastboot reboot
And press and hold the vol down button again until you reboot in bootloader.
Flash the recovery and boot you extracted using
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
(I got a habit of extracting and flashing system and Cust using
Fastboot flash system system.img
Fastboot flash Cust Cust.img
But they are not necessary)
Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again).
Please do report back if it comes to life.
To root, just flash twrp and then use SuperSU 2.62 (no other version) and update it later using play store.
Sent from my PLK-L01 using XDA Labs
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
joaomPT said:
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
Click to expand...
Click to collapse
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
muradulislam said:
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
joaomPT said:
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
Click to expand...
Click to collapse
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
muradulislam said:
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said » version 2.62 «
I cant thank you enough!! Can I pay you a coffee?
Thank you!
joaomPT said:
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said �?�» version 2.62 �?�«
I cant thank you enough!! Can I pay you a coffee?
Thank you!
Click to expand...
Click to collapse
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
You can find him somewhere in this thread
http://forum.xda-developers.com/honor-5x/help/honor-5x-kiw-ul00-boot-loop-t3449554/page1
Decision is yours
muradulislam said:
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
Whichever you like...
Click to expand...
Click to collapse
Alright man, cheers
joaomPT said:
Alright man, cheers
Click to expand...
Click to collapse
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
joaomPT said:
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
Click to expand...
Click to collapse
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
tgergo said:
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
Click to expand...
Click to collapse
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
I'll try... But seems too simple to be true...
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
Hi again,
I'm doing this OS installation now. It starts fine but stucks at 90%, (I'm trying to install the latest stock ROM which can be downloaded from Huawei site, B220 or221). Did you have the same issue? I waited more than half an hour at 90% but did not go on.
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Maybe formatting, Flash stock Android 5 recovery using Honor multitool , and then Flash a Android 5 firmware
Not sure it Will Work without rollback..
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
tgergo said:
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
Click to expand...
Click to collapse
Is this really work? i cant rollback to any version.
Yuaru said:
Is this really work? i cant rollback to any version.
Click to expand...
Click to collapse
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
tgergo said:
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
Click to expand...
Click to collapse
Thanks for the answer. Im gonna try this method. I can't reflash any region rom.
Hi all,
I went ahead and rooted my Mate 10 Pro today - I unlocked my bootloader, installed TWRP and got it running pretty sweet. Then, like a tool - tried installing xposed framework and got myself into a boot loop.
I can get to fastboot, I can get into twrp - but for the life of me don't know how to get a system wipe and fresh format! I've tried flashing LineageOS - but that's stuck on a loading screen and then boot loops after about 10minutes.
What happens is I turn my phone on - see the bootloader message - if I do nothing there's a 50/50 changes Huawei's eRecovery window opens (where if i connect it to the wifi, it fails and gives me the option of reboot or shutdown) or LineageOS boot animation loops for about 10minutes before shutting down.
At this stage, I don't mind what rom i get working - i just want something working and I'm really regretting xposed (I should of googled!).
I really don't want to pay $40 usd - and am happy tinkering around, but would appreciate some solid advice on how I can use TWRP to wipe everything and start again!
I'm also a little confused as to why eRecovery is coming up at all - and why it can't download anything!!!!!
Can someone help me get a phone back?
Thanks!
Yeah, I bootlooped going with xposed too, but I have the Mate 10 (regular) and no TWRP. Can you get to TWRP and simply flash a clean ROM? If not, which I presume is the case, can you get to Fastboot? To try, when you get to the eRecovery window, use the option to shut down your phone. Then press the power button and, while holding it, plus in your USB cable (the other end which should already be attached to your computer). Then go to Mankindtw's thread for flashing ROMs (Mate 10 Flash Oreo one). Basically, you download three zip files from a russian language page with all the latest Huawei ROMs, repackage them within his utility, and then flash them from within his utility. Worked for me.
download update.zip (for your firmware) from http://pro-teammt.ru/firmware-database
Extract update.app from update.zip
Download Huawei Update Extractor (open it and go to settings and disable header check)
Open update.app in Huawei Update Extractor
Extract SYSTEM from update.app using Huawei Update Extractor.
(Not sure if Xposed modifies vendor too, so you might have to extract that as well)
Fastboot flash system system.img
See if it boots now. If not you could try extracting recovery_ramdisk and flash recovery_ramdisk.img to the recovery_ramdisk partition then factory reset from stock recovery.
If it does modify vendor you'd have to flash vendor as well.
Or you could try flashing lineage os system, flash recovery_ramdisk and factory reset from stock recovery (factory reset is needed to get aosp roms running)
If it still fails, use mankindtws HWOTA as described by rogerinnyc above. (link: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814)
Stock rom seems to be installing. TY for your help
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
ChriKn said:
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Click to expand...
Click to collapse
Install this regfix https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
However, you would probably have had problems before too when flashing twrp.
But worth a shot I guess.
Didn't see it said you tried on win 7 too.
And if it worked before on Win 10 it should work without it.
I guess you could push system.img to /data/system.img then tap Install and selectInternal storage, tap on (go up one level) in browser, now you'll be at /. Tap on /data and then on system.img. Flash to 'System Image'.
Edit: I've tested with recovery and that flashes fine from /data/.
please see below;
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Toldorn said:
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Click to expand...
Click to collapse
Boot.img is for Nougat. Oreo uses ramdisk.
Try wiping data in TWRP (Wipe - Format Data).
You can't turn off encryption in TWRP. It's controlled by /vendor/etc/*.fstab (* = kirin970 in this case). (You can temporarily turn off encryption but it re-encrypts after booting if fstab is untouched)
But removing encryption won't fix you bootlooping, and that command you used is for Full disk encryption, we use file based encryption.
You could also try flashing back stock recovery and do factory reset from there.
Edit: Oh, you're the guy who PM'd me
I've reflashed my 'system.img' as before - but im having trouble getting into factory reset menu.
all it ever does is go into e'Recovery instead, which is useless.
Also, my booting image is still a green page of pixels - rather than a huawei logo.
Hi. I have a bla-a09 and need help. can boot into twrp but will not boot.
EDIT: My solution was to have an exFAT formatted SD card with update.app, I had previously only tried on an ext4 formatted card.
Hi everyone!
I've been looking for days for a way to get my Honor 9 working again to no avail.
It started with me trying to install a custom ROM on my EMUI 5.1 Honor9, but when the touch buttons didn't work I decided to go back to stock. This is where the problems started.
FRP and bootloader was unlocked before doing this.
After many different firmware tries I managed to get into stock rom (B130), and apparently it locked FRP again, but since the touch buttons still didn't work I decided to rebrand with B120. Bad idea.
Now my phone has FRP locked, so I can't flash images from fastboot anymore (command not allowed), and no working OS.
I do however have TWRP installed as recovery2/e-recovery, so I can still adb push images and install them via TWRP.
I've looked through every thread on this forum and tried every possible solution I could find (extracting images from update.app, copying update.app to /dload on external sd, different firmware versions etc)
If there is there anyone here that is more experienced than me that can give me any pointers in the right direction, I'd be incredibly grateful!
As far i know there only 3 service repair firmwares publicly available which works the dload way. There nougat and are meant to use from nougat.
Alright, so they won't work for me no matter how hard I try?
What alternatives are left to me?
What's your region and version firmware actually ?
You stated you rebranded ?
What region region service repair firmware did you used ?
Region is EU, I'm not really sure what my original firmware is, but i suspect around B130? I know, I'm an idiot for not checking before I wiped it..
I tried at least, to install the B120 in order to get the capacitive buttons to work, but I'm pretty sure I didn't succeed.
I've been using EU firmware to try and get the phone up and runnin. A few different versions.
have you tried to flash again B130 whit 3 fingers mode?
mmmhhh but maybe you have need stock recevery....
With 3-finger mode you mean stock recovery? (Not twrp or stock eRecovery)
How would I flash this using stock recovery, via update.app method?
When flashing stock recovery to recovery partition it boots straight to twrp (flashed to recovery2) regardless of what buttons I hold. :/
If i flash twrp to recovery and stock eRecovery to recovery2 partition and restart holding vol+ and pwr, I get a screen similar to fastboot screen with "error 2 - could not load"
I'm afraid that if i flash stock both recovery and eRecovery, I have no way of flashing images or restore twrp due to FRP being locked...
Thank you everyone for taking the time to respond, really appreciate it!
not undestrand...
now you have TWRP installed or Stock recovery? phone turn on in system or have a loop? what it is the problem? only FRP blocked?
how you can falsh twrp and stock e-recovery if you have frp blocked?
what is happen when you turn on phone holding Volume + and Power Button WHITOUT ANY USB CABLE CONNECTED?
this is three fingers way:
1) download "stock service B130" from:
https://forum.xda-developers.com/hon...stock-t3696892
2) copy UPDATE.APP and update_STF-L09_hw_eu.app to external SDCARD into /dload folder
turn on the phone holding Volume + and volume - and power ( three fingers way)
if all is good, phone restart in stock recovery and update firmware....
you will have again bootloader and frp blocked after new firmware will be flashed
if you have a twrp installed you can try this method.... but i dont know if it work whit frp locked:
1) download "stock service B130" from:
https://forum.xda-developers.com/hon...stock-t3696892
2) download those 2 file from
https://mega.nz/#F!Y59nFYbJ!fb1f4UpEdgABZ4NhOfu1JQ
3) put all files in HWOTA7 directory on external SD
4)In TWRP find the folder HWOTA7 on the phone SD and from it flash the file "hwota7_update.zip"
he phone will reboot itself into the stock recovery and it will install the firmware.
++++++ Important ! ! ! ++++++
After have installed the firmware, you need to boot into the recovery and make a full Wipe
if all ok, b130 firmware will be flashed.
let me know if you try
First of all, thanks a lot for trying to help me!
I will try this method. I downloaded the HWOTA script, however in the bash script contained in this file, it says:
#!/sbin/sh
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p37
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p34
echo --update_package=/sdcard/HWOTA7/update.zip > /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_data_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_all_hw.zip >> /cache/recovery/command
reboot recovery
Which means that I should have 3 zip files present on the phone in /sdcard/ called update, update_data_public and update_all_hw.
These zip files do not exist in the B130 firmware you linked. What files should I use for this?
I tried running it anyway and got into recovery, however it says "Software install failed! The update package does not exist. Please download the package again."
Alright, that may have thoroughly f**d me. Now TWRP is replaced with stock eRecovery.
I suppose I can put files on the SD card by using my laptop, but then I'd need the correct files. Anyone?
Now you should be able to flash with b130 service Repair files:
http://androidhost.ru/v5
Instructions inside, you will need an sdcard formated to extfat.
I've tried SO many times trying to get this update method to work, but always stuck at 5%, until now!
Seems like exFAT is the key! When formatting the SD card on my laptop with linux, it became formatted as ext4, which was fine to read and write to in twrp, but however stock recovery seems to demand an exFAT partition.
Today I went out and bought an USB SD card reader and formatted with exFAT on my windows machine and lo and behold the update was installed!
I don't know if I'm an idiot for missing this fact or if it is not iterated enough. This solved my issue though!
Thanks a lot, Oslo83 and Angelobiz
miffeltoffel said:
First of all, thanks a lot for trying to help me!
I will try this method. I downloaded the HWOTA script, however in the bash script contained in this file, it says:
#!/sbin/sh
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p37
dd if=/external_sd/HWOTA7/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p34
echo --update_package=/sdcard/HWOTA7/update.zip > /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_data_public.zip >> /cache/recovery/command
echo --update_package=/sdcard/HWOTA7/update_all_hw.zip >> /cache/recovery/command
reboot recovery
Which means that I should have 3 zip files present on the phone in /sdcard/ called update, update_data_public and update_all_hw.
These zip files do not exist in the B130 firmware you linked. What files should I use for this?
Click to expand...
Click to collapse
yes... you have right...i missed somethings:
update.zip same same
update_STF-L09_hw_eu.app have to rename in update_all_hw.zip
update_data_public.zip dont need for restore....
happy that you have solved.
which files have you used?
I used the stock B130 files in the thread that you posted, worked like a charm. As stated, the issue seems to have been that Linux cannot format in exFAT, and stock recovery can only read exFAT.