Related
I'm currently on a HYDRO ROM 4.1 and want to update to the newest bootloader and JB. I downloaded the latest ROM from ASUS but when I try to flash it via TWRP it just says failed before anything gets started. What steps to I have to take from where I am to get the latest and greatest?
Bagel Bear said:
I'm currently on a HYDRO ROM 4.1 and want to update to the newest bootloader and JB. I downloaded the latest ROM from ASUS but when I try to flash it via TWRP it just says failed before anything gets started. What steps to I have to take from where I am to get the latest and greatest?
Click to expand...
Click to collapse
Did u try using fastboot to flash it? Also dont forget to extract the ROM from the downloaded zip file.
I did not realize the ROM .zip file was inside the .zip file...
Thank you installing now. After that I just have to flash an updated recovery and then install an custom ROM, correct. You've been a great help.
Now TWRP says Successful but it didn't take but a couple of minutes and the log says "E:Unable to mount '/staging'
I assume it failed for some reason.
Bagel Bear said:
Now TWRP says Successful but it didn't take but a couple of minutes and the log says "E:Unable to mount '/staging'
I assume it failed for some reason.
Click to expand...
Click to collapse
Did you install the -42 TWRP since you are now on the 4.2 boootloader?
Ah I see. It did actually install the latest bootloader. I installed the latest TWRP but it seems that it can't see files from various partitions. I guess it can't mount them or something so I can't installed a custom ROM from my micro sd or anything. Any help for this problem?
Bagel Bear said:
Ah I see. It did actually install the latest bootloader. I installed the latest TWRP but it seems that it can't see files from various partitions. I guess it can't mount them or something so I can't installed a custom ROM from my micro sd or anything. Any help for this problem?
Click to expand...
Click to collapse
Did you mount the correct partition in the settings of TWRP. Try unmounting and then remounting what you need.
Even the log on TWRP says it is unable to mount anything on startup. When I try to exit TWRP it says that I am not rooted and prompts me if it can root for me. Can I do it this way?
Anyone know anything about this?
Bump
I successfully rooted and achieved an unlocked bootloader with S-OFF on my Verizon HTC One M8 and also flashed TWRP 2.7.0.2. I downloaded a rom (without an SD card). I booted into recovery and i made a backup (not noticing that one of the lines read "unable to mount '/system". I then wiped and attempted to flash the rom only to find out that i can't find it in my file system. So i put the rom on an SD card and mounted it and tried to flash it, i get this message:
E: Unable to mount '/system'
E: Unable to open zip file.
Error Flashing zip '/external_sd/Roms?ViperOneM*_1.2.0.zip'
Updating partition details...
E: Unable to mount '/system'
So i'm stuck with a boot loader, an unmountable file system, and unable to flash a rom.
I've tried Fix permissions, I've tried mounting the "system" but all that mounts is 'cache' 'data' and 'micro SDcard'.
I hope my nerves are getting the best of me and i can't see something that's right in front of me!
Edit: Flashed CWM Recovery. Trying to install ROM from SD Card results in "Installation Aborted". When i try to side load it hangs at 81%.
Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.
dsEVOlve said:
Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.
Click to expand...
Click to collapse
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!
First of all you aren't bricked. Have you tried using side load to flash the ROM? Try flashing another recovery too.
Sent from my HTC6525LVW using Tapatalk
SimplyNando said:
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!
Click to expand...
Click to collapse
The above suggestion to try and Sideload the ROM install is a good idea. Basically, put the ROM zip file in your platform-tools folder of adb. Then boot to TWRP recovery, choose "sideload" and then issue the command "adb sideload [filename.zip]" (Instructions are found HERE.)
If that doesn't work, have you tried flashing Clockwork Recovery? You may have better luck with that in regards to mounts and/or flashing the ROM...
There's always USB OTG as well
Sent from my HTC6525LVW using Tapatalk
I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?
WorldOfJohnboy said:
I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?
Click to expand...
Click to collapse
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.
SimplyNando said:
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.
Click to expand...
Click to collapse
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.
123421342 said:
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.
Click to expand...
Click to collapse
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??
SimplyNando said:
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??
Click to expand...
Click to collapse
no because it is not a flashable zip. Factory image or RUU means the bootloader will literally write the partition. Recovery will mount the partition and write information to it. It cannot create the partition itself which I think is your issue.
Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.
bakemcbride21 said:
Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.
Click to expand...
Click to collapse
Yep. You have a bad download. Download a new ROM on your computer...boot to recovery and do a adb sideload or push
Sent from my HTC One M8
Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...
WorldOfJohnboy said:
Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...
Click to expand...
Click to collapse
Kernel runs inside the rom and the system becomes writeable in the ROM so that won't do anything. I'm pretty convinced he is missing the partition.
Sent from my HTC6525LVW using Tapatalk
Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?
jerico9 said:
Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?
Click to expand...
Click to collapse
did you try formatting internal yet?
Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion
jerico9 said:
Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion
Click to expand...
Click to collapse
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.
dottat said:
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.
Click to expand...
Click to collapse
I mean the device memory was low, so couldn't flash as no room on the device
DISCLAIMER: I AM NOT LIABLE TO ANY DAMAGE THAT HAPPENS TO YOUR DEVICE BECAUSE OF DOING ANYTHING WRONG.
MOTO G4 PLUS [XT1643]
This is for those who had flashed a custom kernel on their stock ROM and now want to revert to stock.
REQUIREMENTS:
1. TWRP 3.0.3-n2 by @Shreps .
https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
This one is more updated/maintained than the official 3.0.2 version.
2. 7Zip Compression Utility:
Download and install on your PC. I use this as it gives the maximum ultra level compression. See Downloads below.
PROCEDURE:
1. Download and extract the TWRP.7z using 7Zip.
2. Place the TWRP folder it in the root directory of your INTERNAL STORAGE.
2. Just reboot TWRP once and choose Restore and then choose this: athene_93-14_boot
3. Swipe to restore.
NOTE: As a general recommendation for all zip installations and backup/restore using twrp, Wipe Cache and ART Cache before you Reboot to System.
4. You're DONE
DOWNLOADS:
Google Drive Link for the file:
https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
7-ZIP Download Link:
http://www.7-zip.org/download.html
IF YOU WANT ENTIRE STOCK ROM ( TWRP BACKUP) VISIT THIS THREAD BY @Greekgodmerwyn .
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-moto-g4-plus-npj25-93-14-t3544601
HIT LIKE IF I HELPED YOU! :fingers-crossed: :good:
Hey I need the file bit it is in bin so give a alternative link
Can i install this to xt1644 retus?
Dont know bro I just want the 1643 one
dedik46 said:
Can i install this to xt1644 retus?
Click to expand...
Click to collapse
Not tried. Make additional backups and try. :good:
https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
Not Found
Error 404
Please re-upload.
nextheart said:
https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
Not Found
Error 404
Please re-upload.
Click to expand...
Click to collapse
Oh wait. Try this, @nextheart
https://www.androidfilehost.com/?fid=745425885120722570
@tywinlannister7 Thanks for quick reply.
As far as I can understand, this file should be flashed (restored) after restoring my TWRP back up of nougat stock rom taken in January-2017. Currently I am on RR-MM.
Shall I able to take OTA then?
nextheart said:
@tywinlannister7 Thanks for quick reply.
As far as I can understand, this file should be flashed (restored) after restoring my TWRP back up of nougat stock rom taken in January-2017. Currently I am on RR-MM.
Shall I able to take OTA then?
Click to expand...
Click to collapse
For OTA updates to work, you'd need a stock recovery on your device too; TWRP is a no go. Once you've restored your TWRP backup of your Nougat stock ROM (which hopefully may have the stock boot still), you can flash the stock recovery linked here https://forum.xda-developers.com/moto-g4-plus/how-to/how-to-ota-rooting-nougat-npj-25-93-14-t3601747
I imagine the easiest option is to flash the recovery in fastboot (same as you did with TWRP) using 'fastboot flash recovery recovery.img', then rebooting into recovery.
I think, though I've not tried it with a stock recovery, that you should be able to flash the recovery image in TWRP:
tap Install in the TWRP menu
Select 'install image's
Find your stock recovery image and select
Choose recovery as the image type
Flash and reboot to recovery.
Then, provided your system has a stock kernel, no modifications to your system and a stock recovery (bootloader doesn't matter), you should be able to update via OTA.
@echo92 Thanks for detailed guide.
I had flashed SuperSU on Nougat stock ROM, so stock boot might be affected. Am I right?
In short, I want to sell the device, so I want to return to stock.
nextheart said:
@echo92 Thanks for detailed guide.
I had flashed SuperSU on Nougat stock ROM, so stock boot might be affected. Am I right?
In short, I want to sell the device, so I want to return to stock.
Click to expand...
Click to collapse
You could have directly flashed the latest March 1 Security firmware via fastboot and lock your bootloader too.
tywinlannister7 said:
You could have directly flashed the latest March 1 Security firmware via fastboot and lock your bootloader too.
Click to expand...
Click to collapse
Thank you for pointing out.
Will I lose my IMEI or WIFI MAK or any thing else by fastboot method? Because I have read that some users are losing such things by fastboot method.
nextheart said:
Thank you for pointing out.
Will I lose my IMEI or WIFI MAK or any thing else by fastboot method? Because I have read that some users are losing such things by fastboot method.
Click to expand...
Click to collapse
Shouldn't create any such issues. Anyways, you can make an entire backup of the fsg and other partitions in twrp.
Yes, your data will be wiped though.
I have HTC one a9 with build number 1.58.709.1. Rooted and unlocked bootload and have twrp. Never flash any roms.
I want to remove every thing that prevent ota to be installed.
I think twrp will cause problem for ota. So how can I remove it an have stock recovery?
The ruu is not available for x.xxx.709.x in web. But I find ota matching my build number. Is that help?
ghasemi.hussein said:
I have HTC one a9 with build number 1.58.709.1. Rooted and unlocked bootload and have twrp. Never flash any roms.
I want to remove every thing that prevent ota to be installed.
I think twrp will cause problem for ota. So how can I remove it an have stock recovery?
The ruu is not available for x.xxx.709.x in web. But I find ota matching my build number. Is that help?
Click to expand...
Click to collapse
Yes, you can extract the recovery.img using this tool.
CSnowRules said:
Yes, you can extract the recovery.img using this tool.
Click to expand...
Click to collapse
Thanks.
I will do that. Then what should I do with it? Flash it?
And I remember that after installing twrp I had format my internal storage to make it decrypted. How can I undo that?
ghasemi.hussein said:
Thanks.
I will do that. Then what should I do with it? Flash it?
And I remember that after installing twrp I had format my internal storage to make it decrypted. How can I undo that?
Click to expand...
Click to collapse
Yes, you can flash the extracted recovery image via recovery.
For encryption, if you do the OTA update and let it reboot stock, it will automatically encrypt your data. Obviously, first boot might take a long time. If you interrupt it, you will lose your data.
CSnowRules said:
Yes, you can flash the extracted recovery image via recovery.
For encryption, if you do the OTA update and let it reboot stock, it will automatically encrypt your data. Obviously, first boot might take a long time. If you interrupt it, you will lose your data.
Click to expand...
Click to collapse
After restoring stock recovery, I need to unroot and lock boot loader for getting ota?
ghasemi.hussein said:
After restoring stock recovery, I need to unroot and lock boot loader for getting ota?
Click to expand...
Click to collapse
To manually install an OTA, definitely not. All you need is the stock recovery, a COMPLETELY untouched system (never mounted r/w), and the correct ota.zip.
CSnowRules said:
To manually install an OTA, definitely not. All you need is the stock recovery, a COMPLETELY untouched system (never mounted r/w), and the correct ota.zip.
Click to expand...
Click to collapse
Is there a way to check if system modified or not?
I read before that some ota are patches asn some of them are complete os. They said only when you want to install patches you need untouched system partition.
The next ota will be android 7. So it format every partitions and modified system cannot make any problem.
Is it correct?
No, the Nougat OTA (for US unlocked at least) patched the existing system partition.
The easiest way to check is to attempt to install the OTA with the stock recovery. It will tell you.
If I were you, I'd flash stock recovery and system from your current RUU, then OTA update.
Another option is to just install the RUU. That will revert your phone to completely stock, wipe your data, and allow you to start fresh.
CSnowRules said:
No, the Nougat OTA (for US unlocked at least) patched the existing system partition.
The easiest way to check is to attempt to install the OTA with the stock recovery. It will tell you.
If I were you, I'd flash stock recovery and system from your current RUU, then OTA update.
Another option is to just install the RUU. That will revert your phone to completely stock, wipe your data, and allow you to start fresh.
Click to expand...
Click to collapse
That's the problem. There is no ruu available for my build number (1.58.709.1.). I just find an ota with this bluid number. The ota did not contain a system.img.
ghasemi.hussein said:
That's the problem. There is no ruu available for my build number (1.58.709.1.). I just find an ota with this bluid number. The ota did not contain a system.img.
Click to expand...
Click to collapse
Did you flash the stock recovery and attempt to install the OTA?
If so, what is the result?
CSnowRules said:
Did you flash the stock recovery and attempt to install the OTA?
If so, what is the result?
Click to expand...
Click to collapse
Yes. I flash stock recovery. then I try to side load the ota to phone. Adb did not recognize device in boot loader or recovery. I don't know why. I use 15 sec Adb installer. It said it installs drivers.
Update: I notice that in bootloader on top of screen there is writing: "software status: official".
Does that mean system partition is untouched?
If your stock recovery has a menu, you can copy the OTA.zip to your phone or sdcard and install from there.
It said system partition has mounted r/w.
What can I do now? There is no ruu with my build number in web. I think s-off is my only way to get android 7? Or maybe htc publish ruu for all regions this time?
If I found system partition backup of my build number in web, is restoring it help?
update:if previous ota (1.56.709.70) has system image in it can i flash that sysem.img?
and do i have to install twrp again to be able to flash system.img?
ghasemi.hussein said:
It said system partition has mounted r/w.
What can I do now? There is no ruu with my build number in web. I think s-off is my only way to get android 7? Or maybe htc publish ruu for all regions this time?
If I found system partition backup of my build number in web, is restoring it help?
update:if previous ota (1.56.709.70) has system image in it can i flash that sysem.img?
and do i have to install twrp again to be able to flash system.img?
Click to expand...
Click to collapse
System backups found online can be unreliable for OTA updates. Here's what I suggest:
Install TWRP to your phone, and backup your current boot and system to an external sd. Be sure that the 1.58.709.1 ota.zip is located on your external sd as well.
Extract the system image from 1.56.709.70 RUU, place it on your external sd card as well, and flash it in TWRP.
Reboot to stock recovery and install the 1.58.709.1 ota. It should verify the 1.56.709.70 system and patch it.
That should complete successfully. When it reboots, it will take a long time since it will encrypt data by default.
You will then be 1.58.709.1 stock and be able to take OTA updates.
If something doesn't complete successfully, stop and post the log here.
CSnowRules said:
System backups found online can be unreliable for OTA updates. Here's what I suggest:
Install TWRP to your phone, and backup your current boot and system to an external sd. Be sure that the 1.58.709.1 ota.zip is located on your external sd as well.
Extract the system image from 1.56.709.70 RUU, place it on your external sd card as well, and flash it in TWRP.
Reboot to stock recovery and install the 1.58.709.1 ota. It should verify the 1.56.709.70 system and patch it.
That should complete successfully. When it reboots, it will take a long time since it will encrypt data by default.
You will then be 1.58.709.1 stock and be able to take OTA updates.
If something doesn't complete successfully, stop and post the log here.
Click to expand...
Click to collapse
Unfortunately the latest ruu for Taiwan is 1.27.709.x for android 6.0.0. I download 1.56.709.70 ota. It doesn't contain system image too. 1.56 was first update if android 6.0.1 and 1.27 was latest build of android 6.0. I think system image of 1.27 is same as 1.5x updates.
I want to try your way in 1.27.
Ok, that MIGHT work with system images only. 1.2x boot and recovery images will not boot on 1.5x firmware.
CSnowRules said:
Ok, that MIGHT work with system images only. 1.2x boot and recovery images will not boot on 1.5x firmware.
Click to expand...
Click to collapse
this is what i do step by step:
1. flash twrp
2. backup system and boot partition
3. flash system image from 1.27
4. flash stock recovery
5. try to install 1.56 ota. unsuccessful. see image 1.
6. try to install 1.58 ota. unsuccessful. see image 2.
7. boot to system. it got stuck in bootloop.
8. install twrp and restore system and boot backup.
9. boot to system and it booted successfully.
what else can i do?
ghasemi.hussein said:
this is what i do step by step:
1. flash twrp
2. backup system and boot partition
3. flash system image from 1.27
4. flash stock recovery
5. try to install 1.56 ota. unsuccessful. see image 1.
6. try to install 1.58 ota. unsuccessful. see image 2.
7. boot to system. it got stuck in bootloop.
8. install twrp and restore system and boot backup.
9. boot to system and it booted successfully.
what else can i do?
Click to expand...
Click to collapse
Did you swipe to allow system to be mounted r/w in TWRP? If you did, that could be the problem.
If not, you can attempt to use the system backups that you can download. You may have the same result, though.
Have you tried using HTC sync manager from download mode? Sometimes that will RUU your phone. Your data would be wiped though.
CSnowRules said:
Did you swipe to allow system to be mounted r/w in TWRP? If you did, that could be the problem.
If not, you can attempt to use the system backups that you can download. You may have the same result, though.
Have you tried using HTC sync manager from download mode? Sometimes that will RUU your phone. Your data would be wiped though.
Click to expand...
Click to collapse
Yes. I allow twrp to mount system as r/w because without this twrp cannot flash system.img.
I don't understand last paragraph. Will you please explain more?
ghasemi.hussein said:
Yes. I allow twrp to mount system as r/w because without this twrp cannot flash system.img.
I don't understand last paragraph. Will you please explain more?
Click to expand...
Click to collapse
TWRP can flash the image without mounting system r/w. That is most likely what is breaking your OTA. Once the system is mounted r/w, it breaks dm-verity, even if you make no modifications.
You should start over and not allow system to be mounted r/w.
HTC sync manager can RUU most modern devices if you connect them in download mode with the software open.
It can be downloaded from HTC's website. I normally wouldn't recommend it since it usually interferes with fastboot and adb if it is installed.
Hello guys
I unlocked the bootloader and root my phone but it's not full root because it's Read only and I can't uninstall any system apps and the only thing I get is to freeze those app and because of this I want to go back to stuck
But I couldn't do that no matter what:crying::crying:
I try Upade.app in dload folder on both internal and sd card but I get error when I want to initiate the update
So please if any one knows a cretin way to go back to stuck, do tell
does Sp Flash tool works with this phone or not ???
badboy_6120 said:
Hello guys
I unlocked the bootloader and root my phone but it's not full root because it's Read only and I can't uninstall any system apps and the only thing I get is to freeze those app and because of this I want to go back to stuck
But I couldn't do that no matter what:crying::crying:
I try Upade.app in dload folder on both internal and sd card but I get error when I want to initiate the update
So please if any one knows a cretin way to go back to stuck, do tell
does Sp Flash tool works with this phone or not ???
Click to expand...
Click to collapse
try to reroot using the method from this thread https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
you need to flash your stock boot.img thru twrp to remove the superuser you use previously before proceed using superRoot or SuperSU from that thread. and try to look for your stock boot.img maybe you can find it in this thread https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
Good Luck.
eddmecha said:
try to reroot using the method from this thread https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
you need to flash your stock boot.img thru twrp to remove the superuser you use previously before proceed using superRoot or SuperSU from that thread. and try to look for your stock boot.img maybe you can find it in this thread https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
Good Luck.
Click to expand...
Click to collapse
thanks for your reply
any Idea how to get back to stuck firmwork ???
badboy_6120 said:
thanks for your reply
any Idea how to get back to stuck firmwork ???
Click to expand...
Click to collapse
Flash back stock boot and you'll be back to stock, as long as you didn't modify any of the other partitions (/system, /vendor, /product). And flash back recovery using adb.
Get stock boot by downloading your firmware from http://hwmt.ru/oth/HWFF/info/view.php?find_model=mha
Then download Huawei Update Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Open it up and open update.app which you extracted from update.zip. Right click on BOOT and extract, same with recovery.
Flash back boot using twrp and 'fastboot flash recovery recovery.img' to flash back stock boot.
ante0 said:
Flash back stock boot and you'll be back to stock, as long as you didn't modify any of the other partitions (/system, /vendor, /product). And flash back recovery using adb.
Get stock boot by downloading your firmware from http://hwmt.ru/oth/HWFF/info/view.php?find_model=mha
Then download Huawei Update Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Open it up and open update.app which you extracted from update.zip. Right click on BOOT and extract, same with recovery.
Flash back boot using twrp and 'fastboot flash recovery recovery.img' to flash back stock boot.
Click to expand...
Click to collapse
I did that but I still don't see "system update" in settings and still getting error while applying new update and can not apply any theme and still have that ridiculous screen that apeared after unlocking bootloader
I mean any way like flashing a new firmware with a tool like SP Flash Tool
badboy_6120 said:
I did that but I still don't see "system update" in settings and still getting error while applying new update and can not apply any theme and still have that ridiculous screen that apeared after unlocking bootloader
I mean any way like flashing a new firmware with a tool like SP Flash Tool
Click to expand...
Click to collapse
You will have to flash back hw and public zips for your build. There's a folder (hw_init) in /data/ that gets wiped when you format data, it contain apps (system update for example) and the theme engine.
So you will have to flash back TWRP again and decrypt again if you went back to stock, else you won't be able to flash the zips. After that you can flash back stock boot and recovery, and you *should* be able to update via OTA.
Here's a little guide for getting HW and public for your build: https://forum.xda-developers.com/showpost.php?p=71302827&postcount=627
Also, question: What update are you trying to apply? It might just be that it's not approved by Huawei yet, and that makes it impossible to install using Firmware Finder.
And if you're trying the Dload method, it won't work. Only 2 offline firmwares have been released.
Edit: I should learn to read. So you're trying Dload? Yeah, that won't work.
I guess you could install your current full firmware using Firmware Finder, but for that you'd still need to flash back HW and Public so you can actually see the System Update button.
And that means flashing back TWRP, and flashing to /data requires decrypting, so you'd have to do that as well.
ante0 said:
You will have to flash back hw and public zips for your build. There's a folder (hw_init) in /data/ that gets wiped when you format data, it contain apps (system update for example) and the theme engine.
So you will have to flash back TWRP again and decrypt again if you went back to stock, else you won't be able to flash the zips. After that you can flash back stock boot and recovery, and you *should* be able to update via OTA.
Here's a little guide for getting HW and public for your build: https://forum.xda-developers.com/showpost.php?p=71302827&postcount=627
Also, question: What update are you trying to apply? It might just be that it's not approved by Huawei yet, and that makes it impossible to install using Firmware Finder.
And if you're trying the Dload method, it won't work. Only 2 offline firmwares have been released.
Edit: I should learn to read. So you're trying Dload? Yeah, that won't work.
I guess you could install your current full firmware using Firmware Finder, but for that you'd still need to flash back HW and Public so you can actually see the System Update button.
And that means flashing back TWRP, and flashing to /data requires decrypting, so you'd have to do that as well.
Click to expand...
Click to collapse
My Stuck rom is MHA-L29C185B110 and since I didn't find this one I extracted the boot.img from MHA-L29C185B126 and used it
I also download the public and Hw zip for MHA-L29C185B126 rom and flash those
When I boot up the camera Icon is gone as for Settings
but the update option is now avalible in settings and it suggest build 156 but when I hit quick update it gives me a popup that says Download failed
any Idea ???
badboy_6120 said:
My Stuck rom is MHA-L29C185B110 and since I didn't find this one I extracted the boot.img from MHA-L29C185B126 and used it
I also download the public and Hw zip for MHA-L29C185B126 rom and flash those
When I boot up the camera Icon is gone as for Settings
but the update option is now avalible in settings and it suggest build 156 but when I hit quick update it gives me a popup that says Download failed
any Idea ???
Click to expand...
Click to collapse
You have to flash public first than hw_data not the opposite.
gm007 said:
You have to flash public first than hw_data not the opposite.
Click to expand...
Click to collapse
I used this method that our friend suggest in post 2
UNLOCK YOUR BOOTLOADER
02-FLASH TWRP 3.0.2-2 (thanks to @Tkkg1994) using ADB
03-Boot into TWRP (HOLD VOL up + POWER)
03(a)-Backup your Boot thru TWRP into your ext SD or OTG(optional)
04-Format Data in TWRP
05-Flash superRoot.zip (thanks to @ante0 for this)
06-Flash Public_data.zip if you are on build L29C636 u can use THIS
07-Flash Full_HW_data.zip(you will get error 7 but it still went thru)if you are on build L29C636 u can use THIS
***how to obtain files for step 6&7 Read THIS thanks to @gm007
08-Boot into system (setup ur phone)
09-Install PHH superuser from playstore.
badboy_6120 said:
I used this method that our friend suggest in post 2
UNLOCK YOUR BOOTLOADER
02-FLASH TWRP 3.0.2-2 (thanks to @Tkkg1994) using ADB
03-Boot into TWRP (HOLD VOL up + POWER)
03(a)-Backup your Boot thru TWRP into your ext SD or OTG(optional)
04-Format Data in TWRP
05-Flash superRoot.zip (thanks to @ante0 for this)
06-Flash Public_data.zip if you are on build L29C636 u can use THIS
07-Flash Full_HW_data.zip(you will get error 7 but it still went thru)if you are on build L29C636 u can use THIS
***how to obtain files for step 6&7 Read THIS thanks to @gm007
08-Boot into system (setup ur phone)
09-Install PHH superuser from playstore.
Click to expand...
Click to collapse
Hi there,
I am having similar issues, but the THIS in your post is just text? I am a novice to the Mate 9 and am trying to get my system update back It failed when I tried to go to B136 via FF
Use this https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page36
Rebrand to c636 it will be easier for you to go back to stock anytime,and faster update.
gm007 said:
Use this https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page36
Rebrand to c636 it will be easier for you to go back to stock anytime,and faster update.
Click to expand...
Click to collapse
Thanks for that. Do I have to do a full wipe if coming from a MHA-L09C34B122?
gm007 said:
Use this https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656/page36
Rebrand to c636 it will be easier for you to go back to stock anytime,and faster update.
Click to expand...
Click to collapse
Thanks man, It really worked:good::good:
I'm running on Stuck Rom again :victory::victory: