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.
Related
Update:
I was able to use this method to root the new ICS update. The thread has been edited accordingly.
----------------------------------------------
I was unable to find a single thread that detailed how to root the stock T-Mobile Springboard firmware and keep the boot and recovery partitions intact to allow future updates, so I have consolidated information from other threads and posts, as well as adding a little myself. Full credit goes to the users and thread OP's referenced in the post links below.
The usual warnings apply: Under no circumstances should anyone do this to their device. You are likely to brick your device and render it completey unusable. In addition, you will void your warantee with T-Mobile. So you will have an out-of-warantee brick instead of a nice, functional tablet. Turn back now while there is still time.
Before you begin, I obviously did this to my device without any problems. My device is running full stock T-Mobile Springboard firmware with the following:
Android version: 4.0.3
Baseband version: 314007
Kernel version: 3.0.8
Build number: S7-303uV100R002C201B035
I do not know if it will work on a device with any other version of the firmware. The following also assumes that you have fastboot and ADB installed and functional on your computer.
In describing how to boot into fastboot and recovery modes below, the description of the volume buttons is how they are while in portrait mode in Honeycomb....as this is where I first used this method. In other words, the volume button closer to the power button is volume up and the other volume button is volume down.
1. Download the CWM Recovery image from this post:
http://forum.xda-developers.com/showpost.php?p=23601045&postcount=7
2. Download CWM-SuperSU-v0.95.zip from this post:
http://forum.xda-developers.com/showpost.php?p=27678611&postcount=22
3. Copy the CWM-SuperSU-v0.95.zip file to an sdcard and put the card in your device.
4. Flash the CWM recovery image to your first recovery partition ONLY:
a.) Boot into fastboot by powering down the device and starting it back up by pressing the
volume up and power buttons at the same time. After the device vibrates, release the
power button but keep holding the volume button until it is booted into fastboot.
b.) Once in fastboot, flash the recovery image:
Code:
fastboot flash recovery recovery5.5.0.4.img
5. Press and hold the power key for 10 seconds to reboot the device. It will boot into the
T-mobile firmware.
6. Power down the device in the usual fashion.
7. Boot into recovery by starting the device back up by pressing the volume down and power
buttons at the same time. After the device vibrates, release the power button but keep
holding the volume button until it is booted into CWM Recovery.
8. Choose 'install zip from sdcard' -> 'choose zip from sdcard', then select the
CWM-SuperSU-v0.95.zip file you put on your sdcard above, then confirm installation.
9. Go back to the main menu and select 'reboot system now'. It will boot into the T-Mobile
firmware.
10. Shut the device down again in the usual fashion, then restart normally and boot into the
T-Mobile firmware again.
11. Now you need to get your stock recovery partition back and get rid of CWM recovery.
There are two copies of the stock recovery- one on each 'recovery' and 'recovery2'. You can
get back to stock recovery by extracting an image from 'recovery2' and flashing it back to
'recovery'. The following (using adb from your computer) will dump the image from recovery2
to your sdcard:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/mnt/sdcard2/recovery.img
12. Take the sd card out of your device and copy this file back to your computer, then flash the
first recovery partition with this image as in step 4b above, but with your new recovery.img file.
You are now rooted and your recovery partitions are returned to stock.
Once you are rooted, if you would like to remove some of the T-Mobile bloatware note that the apk files are not in the usual location (/system/app). I found them tucked away in the following directory:
/data/cust/app
Of course, you will need an app like Root Explorer to get to them and delete them...or you can just use adb. I deleted several of the apk files in that directory, rebooted, and everything is working just fine...with less bloatware.
Also, be aware that any changes you make will be permanent. I tried hard reseting the device through the usual android settings menu security method, and I kept root and all of my deleted bloatware was still gone after it finished and rebooted. There does not appear to be a way to get all of your stock stuff back once you start deleting things...so make backups of files before you delete them in case removing them causes unexpected consequences.
Just to add another bit of information - a list of what I believe are the internal partitions and their locations appears below. I got this from the output from 'cat /proc/partitions' and 'mount', as well as further inspection of the stock recovery image that I extracted from my device. As we don't have a functional CWM Recovery, and I am not sure that I would use any version that was built for the Mediapad (i.e. non-Springboard) for backup and restoring, this list should give Springboard users a way to back up their devices. Using the 'dd' command as in the coding box at the bottom of the OP for each of the paritions should result in a partition image stored out on the sdcard. Fastboot then should be able to flash these 'backed up' images back to the device as in step 4b of the OP...with the correct partition names and backup files substituted of course. I did do this for the recovery partition as I detailed in the OP, but have not tried it for the rest of the partitions.
Code:
/misc emmc /dev/block/mmcblk0p14
/vrcb emmc /dev/block/mmcblk0p16
/recovery emmc /dev/block/mmcblk0p17
/recovery2 emmc /dev/block/mmcblk0p18
/boot emmc /dev/block/mmcblk0p19
/system ext4 /dev/block/mmcblk0p20
/cache ext4 /dev/block/mmcblk0p22
/cust ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p27
/tmpdata ext4 /dev/block/mmcblk0p23
/persist ext4 /dev/block/mmcblk0p21
/tombstones ext4 /dev/block/mmcblk0p24
/firmware ext4 /dev/block/mmcblk0p1
Thanks
Many ty's for this.
Thanks you help me rooted my Springboard. Have you try the MediaPad Phone app can we use the tablet for calling? :good:
Do I have to do step 11 ?
Sent from my SpringBoard using XDA Premium App
---------- Post added at 06:11 PM ---------- Previous post was at 05:49 PM ----------
robkaos said:
Do I have to do step 11 ?
Sent from my SpringBoard using XDA Premium App
Click to expand...
Click to collapse
Also can I do it without PC?
Sent from my SpringBoard using XDA Premium App
Can I use the recovery image from the update that is still on my sd card,what is the difference between the I've springboard .rar, and the su files
Sent from my SpringBoard using XDA Premium App
robkaos said:
Do I have to do step 11 ?
......
Also can I do it without PC?
Click to expand...
Click to collapse
If you do not return your recovery partition to stock, then you will not be able to install future firmware updates from T-Mobile as their updates rely on the stock recovery. So no, you don't have to return your recovery partition to stock, but if you don't you will not be able to install future T-Mobile updates. As far as doing this without a computer - you can use a terminal emulator on your Springboard to create the recovery image from 'recovery2'....the commands should be the same. However, you need to fastboot flash that image back to 'recovery', which you must do from your computer with your device in fastboot mode.
robkaos said:
Can I use the recovery image from the update that is still on my sd card....
Click to expand...
Click to collapse
Yes, if you extract the recovery image from the official T-Mobile update package, you can use this image to flash 'recovery' back to stock when you are done.
Some people have reported that they are unable to boot into CWM recovery if it is flashed only to 'recovery' and not also to 'recovery2'. It is my experience that the device seems to alternate which recovery partition it boots into when you sequentially boot it into recovery mode. When I have CWM on 'recovery' and the stock recovery on 'recovery2', my device will boot into CWM every other time I boot into recovery mode. The other times it boots into the stock recovery. If you can't get CWM recovery to appear when you boot into recovery mode, you could do things a bit different than the instructions. Extract the stock recovery image from the official T-Mobile update package. Store this away on your computer. Then, instead of only flashing 'recovery' with CWM recovery, also flash 'recovery2'. Once you are done rooting the device, use your stored image of the stock recovery to flash 'recovery' and 'recovery2' back to stock.
Originally, I used this method to root Honeycomb. I did not have the T-Mobile update package for Honeycomb and so could not simply extract the stock recovery image from that package. You cannot use the 'dd' command as in step 11 above until you are rooted to dump the image of 'recovery2'. So, without a copy of the update package I could not get an image of my recovery partition without already being rooted. But to root, I have to overwrite my recovery partition with CWM recovery, thereby making it impossible to dump a copy of the stock recovery as I had wiped it out and replaced it with CWM. The solution was to only flash one of the recovery partitions and keep the other one as a backup until the device was rooted and the image could then be extracted.
robkaos said:
...what is the difference between the I've springboard .rar, and the su files
Click to expand...
Click to collapse
Not sure what you are asking here...please clarify.
I haVe found two different root files one su zip and the other is for media pad orange Tahiti ,andspringbord .rar which is the difference?there is not a one click Method like motor defy? My phone wasn't such a problem
Sent from my SpringBoard using XDA Premium App
robkaos said:
I haVe found two different root files one su zip and the other is for media pad orange Tahiti ,andspringbord .rar which is the difference?
Click to expand...
Click to collapse
I don't know about the root files for the Mediapad. I know there is a package that contains the su files and a Windows-based command file that contains a string of adb commands that is supposed to work to root both the Mediapad and the Springboard. I think what you are talking about can be found at either one of these locations:
http://www.modaco.com/topic/354579-...-mediapad-t-mobile-springboard-orange-tahiti/
http://www.gamefront.com/files/22185176/Huawei+MediaPad+ROOT+ICS+Android+4.0.x.rar
I tried to use this, and got a 'premission denied' fail pretty early on. I run Linux on my desktop, so perhaps this works under Windows with the specific Springboard drivers and interface software installed, but it sure does not work in Linux. I came up with my method (or rather consolidated the information for 'my' method from multiple other sources) as a result of having this root method fail for me.
robkaos said:
...there is not a one click Method like motor defy? My phone wasn't such a problem
Click to expand...
Click to collapse
If the files that I linked above work for you, then this is going to be about as close to a 'one-click' method as you can get. Unless you modified it, your Motorola Defy is running Android 2.1 (Eclair). This version of Android can be rooted pretty much just by yelling 'ROOT!' at your phone. There is even an app in the market that can be installed and run on an Android v2.1 device that provides a one-click root without the use of a computer. All of the exploits that were used for these one-click root methods were patched in Android v3+. Pretty much every device needs its own unique root method now, and the only way it is a one-click method is if someone has constructed a command script to execute all of the needed commands for you, as in the linked packages above.
xdajunkman said:
Also, be aware that any changes you make will be permanent. I tried hard reseting the device through the usual android settings menu security method, and I kept root and all of my deleted bloatware was still gone after it finished and rebooted. There does not appear to be a way to get all of your stock stuff back once you start deleting things...so make backups of files before you delete them in case removing them causes unexpected consequences.
Click to expand...
Click to collapse
Just to point out - now that the Springboard ICS update is out, and the zip has been captured and archived - there is a backup of complete stock ICS available. Every single partition is in there including system and cust. So worst case scenario if you bork it by zapping the wrong file in system or cust, you can reflash that partition from the bootloader.
Thanks for the clarification
Sent from my SpringBoard using XDA Premium App
cmstlist said:
Just to point out - now that the Springboard ICS update is out, and the zip has been captured and archived - there is a backup of complete stock ICS available. Every single partition is in there including system and cust. So worst case scenario if you bork it by zapping the wrong file in system or cust, you can reflash that partition from the bootloader.
Click to expand...
Click to collapse
You are, of course, correct. That statement of mine is now outdated...you can delete things to your hearts desire. If you mess something up, just reflash the firmware and start over.
Just finished rooting my MediaPad from t-mobile. I had to install into recovery one and two so now I have no original recovery but I don't really care, I've got the latest Android Ice Cream update beforehand. What usefull apps with root access do I need now? I've got ad free and ROM Toolbox. Was there a phone app that I could use now?
Failed updates and can't recover - PLEASE HELP!
xdajunkman said:
You are, of course, correct. That statement of mine is now outdated...you can delete things to your hearts desire. If you mess something up, just reflash the firmware and start over.
Click to expand...
Click to collapse
Well, unfortunately, I've messed things up. Here's what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
Any and all help would be immensely appreciated! How can I get back to some sort of working ROM? Please!
Thanks!
knightpawn said:
Well, unfortunately, I've messed things up. Here's what happened:
1) I received the OTA update and everything went fine with upgrading the my T-mobile Springboard tab to ICS 4.0.3
2) I then got brave and went ahead with rooting and installing SU using the technique described in "Root Stock T-Mobile Springboard" by xdajunkman. That worked fine and I was able to get CWM recovery installed.
3) I then tried to install the [ROM][ICS] [Unofficial] Root-ready Huawei/Springboard International ROM and downloaded the dload folder to my SDCard, etc. I tried using the dload folder with the ulmt.cfg file in it and that failed with a "Installation aborted" message. I then removed that file and tried to go into CWM and tried "Install from zip" approach. Same thing...installation aborted message.
4) So, then I did the next stupid thing...in CWM, I formatted my /system, /data, and /cache. That was a big mistake! I now have officially bricked by tab.
5) I tried to get rid of CWM recovery by extracting the recovery.img file from the stock rom zip file. I fastboot flashed that to the recovery and recovery2 partitions. I then thought, let me try extracting the update.zip from the stock rom zip and put that on the root of my sdcard and tried to install that. No go...it just says, update failed with a big red "FAIL" message in the center.
Any and all help would be immensely appreciated! How can I get back to some sort of working ROM? Please!
Thanks!
Click to expand...
Click to collapse
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Any particular locations for the other files via fastboot?
cmstlist said:
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Click to expand...
Click to collapse
Wow! Thanks for the help! I unfortunately, don't have my other computer that has the proper drivers installed to recognize the tablet and to run fastboot on. So, I'll try the fix you are suggesting once I get home today. However, in the meantime, I had some questions with regard to where I should flash the other files.
I understand that recovery.img should go to the recovery and recovery2 partitions.
What about the others? Does boot.img go to a particular partition? Effectively, what would the command line look like? (eg fastboot flash boot boot.img?)
Sorry about the newbie questions. I've installed a number of custom ROMs on phones using CWM, but this is a strange beast.
With regard to your question of whether it boots, well, kind of...it does boot to the T-mobile Springboard screen, then it sits there. I will let it sit for 20-30 minutes and see what happens. Will report back...for sure!
Thanks a ton!
[UPDATE]
So, I had a chance to install the TWRP recovery with the CM10 ROM. I loaded the CM10 ROM with the TWRP which installed successfully. I turned the tablet on and let it sit there for about 10 minutes and sure enough, CM10 runs just fine. However, I did notice that I cannot receive any calls. I am able to make calls, but when someone dials my number, it just goes straight to voicemail.
So, now, I'm wondering, if I can get the stock ICS with International ROM running so that I can try to use this thing as a phone, data and texting tab. I'll try what you suggested when I get home as mentioned earlier.
CM10 has too many problems, why would you want to use it?
cmstlist said:
OK so you blanked system, screwed up data and possibly recovery. Cache shouldn't be an issue. Everything else is probably fine.
So from the Springboard ICS update zip, you'll want to flash each of the following from fastboot:
- stock recovery.img to recovery and recovery2
- boot.img just in case that got buggered up
- cust.img
- system.img.ext4
- userdata.img.ext4 (this will probably blank your internal storage but you probably already did that in the process because CWM doesn't know the difference)
At this point, does it boot? If it looks like it might be bootlooping on the animation, give it a good 20-30 minutes before you pronounce that it's not working. Wiping pretty much anything other than cache with CWM is a huge nono... it doesn't work right and it buggers a lot of things up.
Click to expand...
Click to collapse
That worked for me. After playing with vold.fstab I had rendered my Springboard unusable (got the encryption was unsuccessful screen!).
I really wanted to switch the apps installation path to the external sd card but did not succeed.
What am I doing wrong
I have not been able to root my springboard at all. It will go to a black screen that says enter fastboot and it just stays there. When I type to flash the recovery it says it cannot load it. I have adb and fastboot installed...could it be a driver issue? I now know that I am in the correct screen, just can't get this thing rooted. any help would be appreciated thanks.
Well I feel quite stupid. But figured out where I went wrong and for the love of God got my Springboard rooted. *whew*
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 just make my mobile unlock(KIW-TL00C01), I have tried
1. extract the image of UPDATE.app from B228 and fastboot flash (failure)
https://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
2. using e-recovery(internal recovery), put firmware zip file(B228) in dload directory in SDcard, inform failed at 5%,
if you put that file in root directory of SDcard, it would stop at 5%.
3. install the 3rd part firmware from TWRP recovery(installed, but reboot would make the touch screen support in all the place, and boot loops)
I have tried install a different firmware through the adb when the touch screen is broken.
I use the following command, I didn't find a one could work.
Code:
recovery --update_package=/external_sd/firmware.zip
The one thing I could do to is put the UPDATE.app of B430 into dload, and retry the method 2 or my mobile is complete brick.
I wonder does the Huawei update the signature or firmware of TrustZone?
I don't know anything I could do to make it work.
if you want to downgrade, you first have to dload the rollback package, then the actual firmware
the rollback package
Click to expand...
Click to collapse
Oh I don't know that before, but where could I get that?
hizukiayaka said:
I just make my mobile unlock, I have tried
1. extract the image of UPDATE.app from B228 and fastboot flash (failure)
https://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
2. using e-recovery(internal recovery), put firmware zip file(B228) in dload directory in SDcard, inform failed at 5%,
if you put that file in root directory of SDcard, it would stop at 5%.
3. install the 3rd part firmware from TWRP recovery(installed, but reboot would make the touch screen support in all the place, and boot loops)
I have tried install a different firmware through the adb when the touch screen is broken.
I use the following command, I didn't find a one could work.
Code:
recovery --update_package=/external_sd/firmware.zip
The one thing I could do to is put the UPDATE.app of B430 into dload, and retry the method 2 or my mobile is complete brick.
I wonder does the Huawei update the signature or firmware of TrustZone?
I don't know anything I could do to make it work.
Click to expand...
Click to collapse
where are you getting your files ? what is the Full version of your phone KIW-TL00C00 or KIW-TL00C01 or KIW-TL00HC00 ?
you must use the exact version for your phone.
the only useful info on the Honor 7 link you posted is how to flash from dload
nowhere did you say you put update.app in dload folder on ext_sdcard and flash with power + volume up and volume down
First determine the correct file for your phone and then flash it correctly
clsA said:
where are you getting your files ? what is the Full version of your phone KIW-TL00C00 or KIW-TL00C01 or KIW-TL00HC00 ?
you must use the exact version for your phone.
the only useful info on the Honor 7 link you posted is how to flash from dload
nowhere did you say you put update.app in dload folder on ext_sdcard and flash with power + volume up and volume down
First determine the correct file for your phone and then flash it correctly
Click to expand...
Click to collapse
I tried to use the match file, but failed in rollback, it would always inform me that system update failed.
hizukiayaka said:
I tried to use the match file, but failed in rollback, it would always inform me that system update failed.
Click to expand...
Click to collapse
Follow this : https://forum.xda-developers.com/honor-5x/how-to/guide-entering-fastboot-using-key-t3400869
After you entered fastboot, flash twrp, then restart to recovery and copy stock firmware to sdcard.
Even if it fails, you can hold VOL+ button during startup to enter eRecovery, where you can revert to stock using nothing but wireless LAN
P/S : I'm also stuck at bootloops trying to install lineage and mokee, please post a guide if you have done it successfully
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
I've bricked my phone and am in need of help!
What I've done:
Unlocked bootloader with a code from DC-Unlocker then using minimal ADB and Fastboot to unlock
Flashed TWRP 3.1.1
Installed Magisk
Took TWRP backup - but I was unable to backup Data (I believe this was due to encryption - recovery.log shwed errors initially on Bluedorid files)
Wiped data with TWPR to try and do a factory reset
This is where my problems started and now I cant restore boot with TWPR the error is "No such file or directory"
I can ADB pull my recovery.log which says
Read info file, restore size is 12444160
Restoring 6 partitions...
Total restore size is 4512MB
I:Restore filename is: /external_sd/TWRP/BACKUPS/L5NDU17B18000539/Stock V7 2018-06-23--16-58-45/boot.emmc.win
I:Restore file system is: 'emmc'.
I:Restore file system is: 'emmc'.
Restoring Boot...
Error opening: '' (No such file or directory)
I can restore OEM recovery and do a factory reset but it hangs at 99%
power down then it goes back to factory reset and goes to 100% - message "Reset Successful!"
but... then it gets stuck in a boot loop
I've tried downloading other stock ROMS and extracting and flashing images via fastboot (Boot, cust, product, recovery, system, vendor, version)
I've tried Huawei Multi-tool but I lack the Userdata.img disk image
I've tried flashing Resurrection Remix N v5.8.5 For Honor 9 (STF) but without success, although the TWRP install says it is successful and the vendor.img flashes fine.
I've tried extracting UPDATE.app files and putting them in sd_card/dload and then 3 button resetting
I've tried the above in external_sd/dload (not sure why - desperation)
I've tried looking on as many threads as I can find on XDA but with no luck
I can always get to fastboot, flash TWRP or OEM recovery, I can also run ADB commands via Putty (in command line they display strangely)
Any suggestions would be greatly appreciated! I am at a loss an quite frustrated, and have been working on this for maybe 15 hours now.:crying:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Fixed!
Thank you, I think I even saw this thread but for some reason did not download the file, also the exfat formatting tip was excellent. I owe you a beer!
Can I always use this method to go back if I totally destroy things again even If I update to Oreo?
oslo83 said:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Click to expand...
Click to collapse
Unfortunatly, there only nougat 'service repair firmware' available publicly as far I know.
So, for now, you can only use this when on nougat.
When on oreo, you should use HuRUpdater with oreo's Twrp.
Or if you're oreo device is really messed badly, a paying app called DC-Phoenix then HuRUpdater.