Hi im new here and i need help :^;
Have a huawei mate 9 (dual sim, unlocked bootloader) and accidentally wiped the system partition through twrp (custom for huawei mate 9 through xda so not all functions work)
tried:
- fastboot flashing system.img, boot.img and revovery.img from update.zip (MHA-L29C432B176) from "techora"
--- this ended up as a boot loop
- flashing the update.zip through twrp but i got an error message for unknown command (probably because update.zip is not made for twrp)
- using dload/UPDATE.APP using ext sd card after flashing recovery.img but nothing happened, cant access internal storage so cant move the dload folder there
- hisuite system recovery but rejected my phone because it is unlocked ... tried to relock phone but still got rejected
please help ;^;
Thanks
Got it working but not optimal
how i got it working with fastboot and twrp:
flashed romaur1.5 along with system.img from a MHA-L29C636XXX full update zip
the boot img from that was a bit messed so flashed KangVIP custom rom boot.img (dont flash the whole rom there tons of chinese bloat) ---- i probably didnt need to flash the romaur, just system.img and boot.img
that fixed everthing kinda. the os booted fine but there was a messed keyboard (google voice keyboard that didnt work) so i skipped everthing and installed a google keyboard apk, then went into Settings to redo the startup things i didnt do. The other problem is that my phone is permenantly rooted with SuperSU, cant uninstall or update through the app :/ factory resetting didnt remove the root (after flashing the stock recovery.img from update.app)
Thats all..
henry931 said:
how i got it working with fastboot and twrp:
flashed romaur1.5 along with system.img from a MHA-L29C636XXX full update zip
the boot img from that was a bit messed so flashed KangVIP custom rom boot.img (dont flash the whole rom there tons of chinese bloat) ---- i probably didnt need to flash the romaur, just system.img and boot.img
that fixed everthing kinda. the os booted fine but there was a messed keyboard (google voice keyboard that didnt work) so i skipped everthing and installed a google keyboard apk, then went into Settings to redo the startup things i didnt do. The other problem is that my phone is permenantly rooted with SuperSU, cant uninstall or update through the app :/ factory resetting didnt remove the root (after flashing the stock recovery.img from update.app)
Thats all..
Click to expand...
Click to collapse
SuperSU is in boot.img so you'd have to restore that to get rid of root.
You could use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
To get back to your old version or get to B190. Backing up /data is recommended if you're decrypted, or backup using titanium or similar. (that's if you want to unlock bootloader again after it's done, since it does a factory reset.)
Or you could try flashing system.img directly in twrp, to the /system partition. Youd have to flash your boot.img for B176 for this though.
ante0 said:
SuperSU is in boot.img so you'd have to restore that to get rid of root.
You could use this: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
To get back to your old version or get to B190. Backing up /data is recommended if you're decrypted, or backup using titanium or similar. (that's if you want to unlock bootloader again after it's done, since it does a factory reset.)
Or you could try flashing system.img directly in twrp, to the /system partition. Youd have to flash your boot.img for B176 for this though.
Click to expand...
Click to collapse
I've tried that, and it doesnt work for me, going to try different boot.img from another post on xda
lol that didnt work because my system image was too old, i flashed a newer version of supersu and it installed systemless and uninstalled my old one
You could have just downloaded your update.zip, taken out update.app, extracted system.img and made a flashable zip.
Powerlated said:
You could have just downloaded your update.zip, taken out update.app, extracted system.img and made a flashable zip.
Click to expand...
Click to collapse
cant be bothered, id rather just flash through fastboot
Related
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
theoden144 said:
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
Click to expand...
Click to collapse
To solve this, you could get phone into Fastboot and flash Dottat's RUU for the M8 - he made several versions.
For sure, add HTC_Fastboot.exe to your ADB folder and use it, NOT regular fastboot.
It will overwrite your previous recovery with stock and fix your phone. Then later, you could flash TWRP 2.8.7 thru Fastboot.
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
cntryby429 said:
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
Click to expand...
Click to collapse
I would flash firmware or ruu, if indeed he flashed recovery to wrong partition, that partition needs the correct one which firmware wlil do, and ruu will 100% do.
Personally I'd run ruu, go to stock recovery and run a factory reset.
theoden144 said:
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
Click to expand...
Click to collapse
Gotta use ADB and HTC_Fastboot.exe
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
theoden144 said:
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
Click to expand...
Click to collapse
Twrp manager is not a safe way to flash recovery because they aren't flashing by block name yet. They are still hard-coded to block number. The partitions have changed during ota already...so the app does hose things up a bit.
Sent from my Nexus 6 using Tapatalk
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Martynhsmith said:
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Click to expand...
Click to collapse
I've come across this today (my OPO was rooted and I had TWRP installed), I was able to install the OTA via returning the OPO back to an unrooted stock build. You can easily do this via getting the 'Fastboot' zipped version of your current .....1NO build.
Once you have this, you only need to fastboot flash the following: - boot.img, recovery.img and system.img
After flashing just these three images, yes you'll loose root but you'll be able to OTA update to the ......2QL build via the normal phone method - hten if you want, you could then reflash a TWRP recovery and re-install a supersu.zip
One thing I forgot to add, which maybe helpful to others as it took me a moment to realise, both boot.img and recovery.img flash without issue, but due to it's size to flash the large system.img you'll probably need to brake it down into flashable chunks, notice the change in fastboot commands: -
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot -S 512M flash system system.img
Martynhsmith said:
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Click to expand...
Click to collapse
OTAs can only be flashed through stock recovery..applicable to all devices
Hello,
on the same subject, I am looking for explanations on how to create twrp flashable files for ota updates. Do you know where I could find any resources?
Thx
I had the same issue while installing the incremental update (I got root and TWRP); I solved it simply installing the signed zip of ...2QL version which was pulled out yesterday afternoon. My only concern was about root that could be wipe away with the new installation, so I directly installed SuperSU via zip. Everything works fine till now
Sent from my A0001
Hi!
This morning I updated supersu binaries via CWM, beacuse "normal" upgrade didn't work.
Now the phone is stucked with the boot logo animation.... I tried to clear the dalvik cache, but I don't understand very well what is going on...
I neither know if the un-brick procedures applies to me, because I didn't ugpraded the EMUI
Any ideas?
Thanks in advance and sorry for my poor english
Follow this procedure to get your phone back to stock:
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
NOTE: If the manual flashing doesn't works or you get any errors, then first try only the force update method, i.e Putting the UPDATE.APP from which you extracted the files in dload folder of your external SDCARD and pressing Vol UP + Vol DOWN + Power button simultaneously after switching off your phone.
Thank you.
Is there no other way to "revert" SuperSU changes?
I guess something went wrong with that. I have same problem, but I did not update SuperSU, i just installed it and choose to clear dalvik cache.
atarifreak said:
Thank you.
Is there no other way to "revert" SuperSU changes?
I guess something went wrong with that. I have same problem, but I did not update SuperSU, i just installed it and choose to clear dalvik cache.
Click to expand...
Click to collapse
Install an older version of SuperSU, like 2.51 or 2.62.
Don´t clean cache or Dalvik after install.
It might do a couple or reboots, just wait.
atarifreak said:
Thank you.
Is there no other way to "revert" SuperSU changes?
I guess something went wrong with that. I have same problem, but I did not update SuperSU, i just installed it and choose to clear dalvik cache.
Click to expand...
Click to collapse
If you have a twrp backup restore only system. Or maybe try flashing only system img from fastboot. Worked for me.
goldfinv said:
If you have a twrp backup restore only system. Or maybe try flashing only system img from fastboot. Worked for me.
Click to expand...
Click to collapse
Thank you.
older SuperSU does not work. I think it iss because of Android 6.
I need some sort of boot.img patching...
I reflashed system.img from huawai extract and all fine (except of rooting...)
Okay cool. I rooted by flashing SU 2.47 and was able to update from play store. Which I don't recommend. Just root and stick to that SU version
well, rooting without working supersu.zip - flash would be great, but I dont get it with Android 6.
no Problem with Android 5.1
And I dont want to use some strange chinese tool (that does not support honor 6 plus any more).
So you got Android 6 and root with Honor 6plus?
Hi guys i was trying to install a custom rom on my mate 9 (MHA-L29C432-156)so i followed the instructions ; unlocked the bootloader; then installed twrp 3.1.0-0; on twrp formated data; then full wiped and try to install AurRom from SD; but get a message that zip file is corrupted; so I tried with S.H.I.E.L.D ROM and it flashed , but then when boot goes to eRecovery, and give me 3 options download latest version and recovery; reboot and shutdown. So now I cant boot the phone, when I restarted, followed same steps , format data, full wipe and trying to installing again but getting a message about all zip files of the roms are corrupted; then i try to restore backup; and same again get the huawei logo, then the android logo , phone restarts and eRecovery again.
Please someone HELP, I use this phone for my work...........!!!!!!!!!
How did you full wipe?
Also try with Twrp 3.0.2-2
Here:www.androidfilehost.com/?fid=745425885120697579
dannytgt said:
on twrp formated data
Click to expand...
Click to collapse
Something went wrong here. You can run 'adb logcat' to see the crash details while starting.
If you have a backup on twrp then restore to get phone working. You may need to flash the public and hw-data zips afterwards though.
If you don't have a backup then you could try flashing the C636 off line firmware and then use firmware finder to go back to your original firmware
Sent from my MHA-L09 using XDA-Developers Legacy app
you may just flash the modified recovery ( See Guide subforum ) ) to bypass the update certification and authorization and reflash an original firmware. your stored files will be lost anyway in most cases.
I would bet superuser ( shield ) and SuperSU ( Aurom) messed your boot image. Both are incompatible to each other and, afaik both are incompatible to twrp 3.1.
Flash TWRP 3.0.2.2, reboot to recovery again to change version, flash the rom ( f.e. shield rom), boot once up, reboot to recovery and THEN you may flash twrp 3.1
Thanks all of you guys, I've solved the problem, it seems that's something related to the sd card, I've formated the sd and transfer the files trough another phone and then put the sd on the mate 9, I follow the steps as followed before and works successfully, now I'm on AurRom and 182 firmware.
I know, i know there's plenty of resources over the net already and I already spent 10+ hrs on this.
I bricked my phone when SuperSU prompts me to install su binary. And it got me into bootloop.
Tried https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 but failed at 61%
Tried the backup oem file method but TWRP kept saying permission denied when trying to backup
Couldn't find a way to import dload+Update.app file into internal storage without actually booting up the phone first. I didn't knew the exact directory for internal storage so I couldn't copy it from OTG
Bootloader Unlocked, Rooted(before recovery), using TWRP.
I wanna go back to clean stock firmware
Any helps would be appreciated.
ADDED: ITS ORIGINALLY OREO
Any luck? I have the same problem here ..
Still have unlocked bootloader & know the firmware version you were on?
Right. Go to Firmware Finder. Download the FullOTA version of it.
Get one of the firmware extractor utilities. You're going to want SYSTEM, KERNEL, RAMDISK, and RECOVERY_RAMDISK (or RECOVERY_RAMDIS, depending on the extractor).
Get into fastboot mode.
Flash those 4 items to the partitions named the same.
Reboot into recovery - you're now in an EMUI recovery. Factory reset.
Reboot.
You should be back to stock with an unlocked bootloader. If you've gone poking around with root or whatnot and might have modified one of the other partitions, don't relock your device - it won't boot. Instead, hwota8 or a NoCheck stock recovery are probably the way you'd want to go. (To be honest, I haven't used either. If I want to get back to full stock knowing it's not modified, I usually do a downgrade flash to Nougat through HiSuite and then upgrade again.)
irony_delerium said:
Still have unlocked bootloader & know the firmware version you were on?
Right. Go to Firmware Finder. Download the FullOTA version of it.
Get one of the firmware extractor utilities. You're going to want SYSTEM, KERNEL, RAMDISK, and RECOVERY_RAMDISK (or RECOVERY_RAMDIS, depending on the extractor).
Get into fastboot mode.
Flash those 4 items to the partitions named the same.
Reboot into recovery - you're now in an EMUI recovery. Factory reset.
Reboot.
You should be back to stock with an unlocked bootloader. If you've gone poking around with root or whatnot and might have modified one of the other partitions, don't relock your device - it won't boot. Instead, hwota8 or a NoCheck stock recovery are probably the way you'd want to go. (To be honest, I haven't used either. If I want to get back to full stock knowing it's not modified, I usually do a downgrade flash to Nougat through HiSuite and then upgrade again.)
Click to expand...
Click to collapse
Data reset/factory reset not working !!
hussam_qashu said:
Data reset/factory reset not working !!
Click to expand...
Click to collapse
Try this one: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
And use this TWRP with it (won't work otherwise, most likely): https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353
(Also, that TWRP has decryption support so you can backup /data.)
Search and download your fw from http://pro-teammt.ru/firmware-database/
You'll want Update.zip, update_data_full_public.zip and the hw data zip. (Make sure it's actually for your phone, e.g. check region cust)
Rename update_data_full_public.zip to update_data_public.zip, rename hw data zip to update_all_hw.zip.
Put update zips and HuRupdater zip in the same folder on your sdcard/internal memory, flash HuRupdater with TWRP.
i have a question, im on mha l29 dual sim version with stock oreo magisk and twrp (368 update) how can i revert back to clean oreo? so i can get the updates normally. thanks !!
ante0 said:
Try this one: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
And use this TWRP with it (won't work otherwise, most likely): https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3783353
(Also, that TWRP has decryption support so you can backup /data.)
Search and download your fw from http://pro-teammt.ru/firmware-database/
You'll want Update.zip, update_data_full_public.zip and the hw data zip. (Make sure it's actually for your phone, e.g. check region cust)
Rename update_data_full_public.zip to update_data_public.zip, rename hw data zip to update_all_hw.zip.
Put update zips and HuRupdater zip in the same folder on your sdcard/internal memory, flash HuRupdater with TWRP.
Click to expand...
Click to collapse
that recovery wont work for me, only work twrp from pretoriano80 3.2.1-0, i got a mate 9 MHA-L29 dual sim...
edit:
well aparently theres 2, i dont get it, but when the recovery boot and show the logo of pretoriano, that version doesnt works, but when boot and show the classic twrp logo with pretoriano80 letters in red works...
so, if you flash recovery with fastboot and reboot recovery for the first time doesnt works, but if you reboot in recovery from twrp will show another version ...???? and works. sorry for my english
Colicablb said:
that recovery wont work for me, only work twrp from pretoriano80 3.2.1-0, i got a mate 9 MHA-L29 dual sim...
edit:
well aparently theres 2, i dont get it, but when the recovery boot and show the logo of pretoriano, that version doesnt works, but when boot and show the classic twrp logo with pretoriano80 letters in red works...
so, if you flash recovery with fastboot and reboot recovery for the first time doesnt works, but if you reboot in recovery from twrp will show another version ...???? and works. sorry for my english
Click to expand...
Click to collapse
That is weird, considering that he only made one TWRP for Mate 9