Is there a guide to updating a rooted Google Pixel (XL) to 7.1.1 without losing root or having to wipe data? A google search only came back with info on OTA updates for stock/unrooted Pixels. Thank you!
First make sure you have the latest adb/fastboot.. Flash stock "V" boot(if that's what your current firmware is) .. Reboot to recovery.. Download the ota for O from Google.. Follow the directions there to side load the ota. Reboot back to bootloader . Flash twrp boot image , it will boot into twrp. Then install the supersu zip.. Reboot. If you did it correctly it will still be rooted. First boot takes a little while tho.
kyle4269 said:
Flash stock "V" boot(if that's what your current firmware is) .. Reboot to recovery.. Download the ota for O from Google.. Follow the directions there to side load the ota. Reboot back to bootloader . Flash twrp boot image , it will boot into twrp. Then install the supersu zip.. Reboot. If you did it correctly it will still be rooted. First boot takes a little while tho.
Click to expand...
Click to collapse
Thanks Kyle. I'm actually still on NDE63L, so I guess that's the stock image I would need to flash? Could I just use the SkipSoft Android Toolkit to 'UnRoot' and then sideload the NMF26O OTA?
Also as far as flashing twrp goes, is there anything to be concerned about with this XDA warning for the TWRP alpha2? : "TLDR: It's finally here in alpha form, may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!"
You should be able to just open the flash-all file with WordPad and remove the "-w" and it will not wipe the device when you run flash-all.bat
LotharioRowe said:
Thanks Kyle. I'm actually still on NDE63L, so I guess that's the stock image I would need to flash? Could I just use the SkipSoft Android Toolkit to 'UnRoot' and then sideload the NMF26O OTA?
Also as far as flashing twrp goes, is there anything to be concerned about with this XDA warning for the TWRP alpha2? : "TLDR: It's finally here in alpha form, may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!"
Click to expand...
Click to collapse
I don't think you can go from L to O using the OTA file. But you can use the full factory image.. Just remove the -w and it won't wipe date like the above comment said.. I still had to flash the original boot for the OTA to install, so I'm assuming you'll have to do that to install the factory image.. I could be wrong though. Then just reroot and you're all set.
kyle4269 said:
I don't think you can go from L to O using the OTA file. But you can use the full factory image.. Just remove the -w and it won't wipe date like the above comment said.. I still had to flash the original boot for the OTA to install, so I'm assuming you'll have to do that to install the factory image.. I could be wrong though. Then just reroot and you're all set.
Click to expand...
Click to collapse
DO you know if you can go from J to O using original factory image and flash it?
bturkel said:
DO you know if you can go from J to O using original factory image and flash it?
Click to expand...
Click to collapse
I just did. No worries.
What about if you have changed the build.prop for the tethering hack? Can you still sideload the OTA?
Related
Fixed.
RusherDude said:
If I am on 4.4 stock rooted, with a custom recovery, and stuff modified on /system.. what I do when the update to 4.1.1 comes?
If I don't do nothing, the update will download automatically (which I don't want at all...), then try to patch and fail (I guess it won't even start since it detects that it's not stock system and recovery to flash the update) and it may even loop downloading and failing by what I readed being a bug on some 4.3 roms on the Nexus 4?
So how I should act in the following situations? First make a nandroid then..
a) I wanna flash it asap: I get the ota zip asap its posted and flash it on CWM and hope it goes ok. I may **** up stuff and have to revert to the nandroid, or 1it can go ok and just lose root and the system changes, right?
b) I wanna stay on 4.4 until all the stuff is ported to 4.1.1: It will at some point download the ota (****) by itself and spam me continuously to install it, right? If I wanna stay on 4.4 until all the stuff I use its compatible with 4.1.1, what I got to do to evade the auto-downloading of the ota and the spam about the update?
I don't know.. any way to stop the auto-update from working or so? That would be great!
Thanks in advance.
Click to expand...
Click to collapse
Here is what I just did, and it worked perfectly.
1. Take note of all the mods you installed so you can install them afterwards.
2. Put phone in bootloader mode / fastboot
3. Grab the 4.4 stock image from Google. Extract system.img file from it and flash that through fastboot (without the -w command) (fastboot flash system system.img). Don't worry you won't lose anything if you omit -w. Apps and data are preserved, it just set the \system area back to stock
4. Copy the OTA udpate zip to your phone, flash with TWRP. Since everything is 'back to stock' it should flash fine.
I had to re-root with TWRP after flashing before I rebooted. Everything was good to go. Then reflash your mods.
sonicdeth said:
Here is what I just did, and it worked perfectly.
1. Take note of all the mods you installed so you can install them afterwards.
2. Put phone in bootloader mode / fastboot
3. Grab the 4.4 stock image from Google. Extract system.img file from it and flash that through fastboot (without the -w command) (fastboot flash system system.img). Don't worry you won't lose anything if you omit -w. Apps and data are preserved, it just set the \system area back to stock
4. Copy the OTA udpate zip to your phone, flash with TWRP. Since everything is 'back to stock' it should flash fine.
I had to re-root with TWRP after flashing before I rebooted. Everything was good to go. Then reflash your mods.
Click to expand...
Click to collapse
Ok, that covers the a) situation where I want to flash it asap, thanks! (also note everyone, you got to disable xposed and all mods before flashing the ota)
PS: You can just flash the stock kernel and undo all the system changes, no need to flash the entire 4.4 stock zip.
What about the b) situation?
RusherDude said:
Ok, that covers the a) situation where I want to flash it asap, thanks! (also note everyone, you got to disable xposed and all mods before flashing the ota)
PS: You can just flash the stock kernel and undo all the system changes, no need to flash the entire 4.4 stock zip.
What about the b) situation?
Click to expand...
Click to collapse
Don't know why you'd want to go all the way back to 4.1.1. That's from July '12.
mattjorgs said:
Don't know why you'd want to go all the way back to 4.1.1. That's from July '12.
Click to expand...
Click to collapse
Wut? in the b) situation I just wanna STAY on 4.1 until all the stuff is ported to 4.1.1 (if something needs porting).
RusherDude said:
Wut? in the b) situation I just wanna STAY on 4.1 until all the stuff is ported to 4.1.1 (if something needs porting).
Click to expand...
Click to collapse
You mean 4.4? And 4.4.1? Lol
Sent from my Nexus 5 using Tapatalk
How to update to 4.4.1
I am rooted/bootloader unlocked with TWRP v2.6.3.1. When I try to flash in recovery manually with ota zip, I get a Failed error with error "E: error executing updater binary in zip"
What are step to update for a device like mine??
Cheeze[iT] said:
You mean 4.4? And 4.4.1? Lol
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Omg yea, 4.4 lol, fail haha
I tried to install the new update but on the install screen it says failed to verify and asks if i want to install anyways.
I choose yes and it errors out saying the update is for device "roth" and i have device "thor"
Does ayone know a workaround for this?
Have you messed with any system files or changed out the recovery or anything like that? I assume the Shield is going to look to make sure the system is all intact before allowing the update. Though the fact it says Roth which is a spelling error of Thor seems weird. Mine updated fine...
If you can find the update using root explorer you could delete it and redownload it.
I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk
csos95 said:
I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
OTAs will commonly fail if you install custom recovery. You'll have to wait for someone to make it into a zip that you can run through CWM.
csos95 said:
I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
You probably still have CWM installed, to install an OTA you must first go back to the stock recovery. You can download it from here: http://goo.im/devs/agrabren/shield/original_images/recovery.img
Put that file in your ADB folder
To flash it, connect to usb and enable ADB debugging.
on PC type:
adb reboot bootloader
-Wait to reboot-
fastboot flash recovery recovery.img
-Now you have stock recovery installed-
Reboot the shield normally and install the OTA update, it should work.
Your bootloader is still unlocked, but you don't have root.
To install CWM, just follow the same instructions but replace the stock image with the CWM recovery image. You can download that here: http://goo.im/devs/agrabren/shield/cwm/recovery.img
The shield will be unrooted when you update. To root, simply flash CWM and reboot. CWM will ask you if you want to disable Stock reflashing, and if you want to root.
You may also need to flash the real SU zip from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
For me, I was not able to let the SU app install the binary's alone, (Normal, or CWM method) I had to flash the SU zip.
But the update is smooth, and everything is working. Just no SD write support obviously.
CDeviant said:
You probably still have CWM installed, to install an OTA you must first go back to the stock recovery. You can download it from here: http://goo.im/devs/agrabren/shield/original_images/recovery.img
Put that file in your ADB folder
To flash it, connect to usb and enable ADB debugging.
on PC type:
adb reboot bootloader
-Wait to reboot-
fastboot flash recovery recovery.img
-Now you have stock recovery installed-
Reboot the shield normally and install the OTA update, it should work.
Your bootloader is still unlocked, but you don't have root.
To install CWM, just follow the same instructions but replace the stock image with the CWM recovery image. You can download that here: http://goo.im/devs/agrabren/shield/cwm/recovery.img
The shield will be unrooted when you update. To root, simply flash CWM and reboot. CWM will ask you if you want to disable Stock reflashing, and if you want to root.
You may also need to flash the real SU zip from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
For me, I was not able to let the SU app install the binary's alone, (Normal, or CWM method) I had to flash the SU zip.
But the update is smooth, and everything is working. Just no SD write support obviously.
Click to expand...
Click to collapse
I tried this but it wouldn't download the ota again an I couldn't find where it was. So, I tried going back to stock to update but now it is stuck on the boot screen. I tried downloading a newer factory image from the nvidia website but now all of the windows links are locked behind some developer program that I have to make an account, submit an application, and wait for approval. Do you have any links to a recent factory restore image?
EDIT: I ended up just downloading mint and the linux .sh file to get the factory images.
You can use the root toolbox on this forum to reflash stock and relock and fix it
eric4shay said:
You can use the root toolbox on this forum to reflash stock and relock and fix it
Click to expand...
Click to collapse
That's what I tried before but it didn't work
If some updates please capture the OTA zip that downloads and upload it for us to tear apart.
What steps are you doing on there also email me [email protected] I will be able to respond more quickly
you dont have to
you can just use kwonggers toolkit, and just revert to stock kernel, stock system image, and stock recovery, you don't need to relock bootloader, but you must download the ota's separately, if you don't automatically see them under about shield> updates, then go to application manager>all> and force stop google services framework, then check for the update(it should now show up and download). this is what I have been doing, everytime I want to revert to the stock, most up to date ota, after this, you can reflash cwm recovery, flash the super su.zip and root again!
The ota (for some back assward reason) downloads not to the ota folder but to the cache folder. Anyway uploading the full otq zip now will edit with link when its done
Sent from my SHIELD using Tapatalk
Mechcondrid said:
The ota (for some back assward reason) downloads not to the ota folder but to the cache folder. Anyway uploading the full otq zip now will edit with link when its done
Sent from my SHIELD using Tapatalk
Click to expand...
Click to collapse
That could be more than one reason. But off the top of my head, maybe it's because the OTA folder is userspace, and there might not be enough Storage left on the internal. Cache is a separate partition, Things can even be deleted while running. So basically it insures enough space to download, and the user would never need to delete his own data to make room.
It might be awkward when you're looking for the OTA, but I think it's designed that way with the user in mind. :good:
Well regardless here's the ota file https://drive.google.com/file/d/0B2khjpo7TDP0Y3c0SjNNRWNXT28/edit?usp=sharing
Sent from my SCH-I545 using Tapatalk
Hi everyone. I saw that Google released the factory image for the Nexus 5. I read on a lot of posts that the XDA members usually release a zip file that you just flash on your Nexus 5 through the recovery and it will install the bootanimation and the rom for you. I have no idea where that is. I want the final version of Lollipop and I want to flash it, not wait for the OTA update. Is there already a zip file like this or do I have to wait for some more time? Thank you.
Thread below you lol
Most of the flashing is described by google themselves: https://developers.google.com/android/nexus/images
But do read more about it elsewhere and don't forget to backup everything before you flash, if your bootloader is locked then unlocking it in order to flash the image will wipe your phone.
Sent from my Nexus 5 using XDA Premium 4 mobile app
There's an OTA Zip over there on AndroidPolice.
You can also flash the Factory Image like most of us did.
It'll be like a brand new Nexus.
maxell505 said:
Hi everyone. I saw that Google released the factory image for the Nexus 5. I read on a lot of posts that the XDA members usually release a zip file that you just flash on your Nexus 5 through the recovery and it will install the bootanimation and the rom for you. I have no idea where that is. I want the final version of Lollipop and I want to flash it, not wait for the OTA update. Is there already a zip file like this or do I have to wait for some more time? Thank you.
Click to expand...
Click to collapse
you can go look in the android development section of the nexus 5, there you will find recovery flashable stock and aosp roms. here a flash in recovery stock lollipop rom http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Curiousn00b said:
There's an OTA Zip over there on AndroidPolice.
You can also flash the Factory Image like most of us did.
It'll be like a brand new Nexus.
Click to expand...
Click to collapse
simms22 said:
you can go look in the android development section of the nexus 5, there you will find recovery flashable stock and aosp roms. here a flash in recovery stock lollipop rom http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Click to expand...
Click to collapse
Ok so I have CWM recovery and I have the stock 4.4.4 rom with xposed framework installed. So can I just put the factory image on my nexus 5 and than go on CWM recovery and flash it?
maxell505 said:
Ok so I have CWM recovery and I have the stock 4.4.4 rom with xposed framework installed. So can I just put the factory image on my nexus 5 and than go on CWM recovery and flash it?
Click to expand...
Click to collapse
What I did:
Backed up my files.
Used WUGFrsh to restore the factory image.
Curiousn00b said:
What I did:
Backed up my files.
Used WUGFrsh to restore the factory image.
Click to expand...
Click to collapse
Ok but WUGFrsh is a rooting toolkit and it is only for people who need to root their device. I am looking to just flash the system image onto my device.
maxell505 said:
Ok but WUGFrsh is a rooting toolkit and it is only for people who need to root their device. I am looking to just flash the system image onto my device.
Click to expand...
Click to collapse
So just use fastboot....?
#stayparanoid
maxell505 said:
Ok but WUGFrsh is a rooting toolkit and it is only for people who need to root their device. I am looking to just flash the system image onto my device.
Click to expand...
Click to collapse
Have you seen any of the other options?
Wugfresh Nexus Root Toolkit, contains options to restore completely to stock, flashing recoveries, boot images, you name it.
It's like an organized version for people who don't do fastboot command typings through CMD.
You could always flash the factory image yourself by Google Instructions, or download the OTA file on Android Police. The choice is yours. :/
Curiousn00b said:
What I did:
Backed up my files.
Used WUGFrsh to restore the factory image.
Click to expand...
Click to collapse
Curiousn00b said:
Have you seen any of the other options?
Wugfresh Nexus Root Toolkit, contains options to restore completely to stock, flashing recoveries, boot images, you name it.
It's like an organized version for people who don't do fastboot command typings through CMD.
You could always flash the factory image yourself by Google Instructions, or download the OTA file on Android Police. The choice is yours. :/
Click to expand...
Click to collapse
Ok so using WugFrsh, I have to restore back to complete stock and get the stock recovery also and than I have to flash the system image?
maxell505 said:
Ok so using WugFrsh, I have to restore back to complete stock and get the stock recovery also and than I have to flash the system image?
Click to expand...
Click to collapse
Not exactly.
Download the factory image, and if you want to use Wugfresh, you go to restore to stock, select your own downloaded factory image, insert the MD5 from the Google Page, and it'll guide you through the rest. It's safer to wipe before doing this, but either way, it does it by itself.
Curiousn00b said:
Not exactly.
Download the factory image, and if you want to use Wugfresh, you go to restore to stock, select your own downloaded factory image, insert the MD5 from the Google Page, and it'll guide you through the rest. It's safer to wipe before doing this, but either way, it does it by itself.
Click to expand...
Click to collapse
Ok so I am going to make this clear so I can understand better and not mess up( because I tend to do that A LOT)
*Before I do anything I have to factory reset my device.*
1. Download the factory image from here: https://developers.google.com/android/nexus/images
2. Open WugFresh and click on the "Flash Stock + Unroot" option.
3. I do not understand the MD5 part.
4. WugFresh will guide me through the rest.
P.S: I do want to be rooted when on Lollipop so I can just root again after I install Lollipop right?
maxell505 said:
Ok so I am going to make this clear so I can understand better and not mess up( because I tend to do that A LOT)
*Before I do anything I have to factory reset my device.*
1. Download the factory image from here: https://developers.google.com/android/nexus/images
2. Open WugFresh and click on the "Flash Stock + Unroot" option.
3. I do not understand the MD5 part.
4. WugFresh will guide me through the rest.
P.S: I do want to be rooted when on Lollipop so I can just root again after I install Lollipop right?
Click to expand...
Click to collapse
The MD5 part, next to the " Download " button on the Google page. You see MD5:yadayadayada. In Wugfresh, it'll need the MD5 to confirm the zip.
You can root by installing a custom recovery, flashing SuperSU and a modified kernel.
Curiousn00b said:
Not exactly.
Download the factory image, and if you want to use Wugfresh, you go to restore to stock, select your own downloaded factory image, insert the MD5 from the Google Page, and it'll guide you through the rest. It's safer to wipe before doing this, but either way, it does it by itself.
Click to expand...
Click to collapse
Curiousn00b said:
The MD5 part, next to the " Download " button on the Google page. You see MD5:yadayadayada. In Wugfresh, it'll need the MD5 to confirm the zip.
You can root by installing a custom recovery, flashing SuperSU and a modified kernel.
Click to expand...
Click to collapse
Ok thank you. I just have to factory reset my phone, flash stock and unroot, and insert the MD5. Once I get Lollipop installed, than I root.
maxell505 said:
Ok thank you. I just have to factory reset my phone, flash stock and unroot, and insert the MD5. Once I get Lollipop installed, than I root.
Click to expand...
Click to collapse
It said it is recommended to use force flash mode. Should I say yes to this?
maxell505 said:
It said it is recommended to use force flash mode. Should I say yes to this?
Click to expand...
Click to collapse
I did anyway and it worked! I am setting up Lollipop as I type this. Right now it is activating my cellular service. Hopefully everything works fine!
how exactly do i go about doing this. back in the day root was easy to keep while taking OTA updates but now i'm not so sure about that. Is there a safe way to take the 7.1.1 OTA update and keep root? I'm currently on 7.1 build NDE63V. No i'm not using the Verizon variant as i have Sprint and thus don't need to worry about dealing with Verizon's BS.
If someone can please point me in the direction of some kind of guide in taking OTA while keeping root or unrooting, taking OTA and then re-rooting or something along those lines that would be a great help. I have a few videos showing me how to unroot but that requires me to completely wipe my phone it seems, at least with the guides i've found. And i'd rather avoid that if possible.
silvernirvash said:
how exactly do i go about doing this. back in the day root was easy to keep while taking OTA updates but now i'm not so sure about that. Is there a safe way to take the 7.1.1 OTA update and keep root? I'm currently on 7.1 build NDE63V. No i'm not using the Verizon variant as i have Sprint and thus don't need to worry about dealing with Verizon's BS.
If someone can please point me in the direction of some kind of guide in taking OTA while keeping root or unrooting, taking OTA and then re-rooting or something along those lines that would be a great help. I have a few videos showing me how to unroot but that requires me to completely wipe my phone it seems, at least with the guides i've found. And i'd rather avoid that if possible.
Click to expand...
Click to collapse
Download the newest factory image, extract it all. Right click the flash-all.bat and select edit. Scroll to the -w and delete it. Then boot into bootloader and run the flash-all.bat. Then, fastboot boot TWRP RC2 and then flash the RC2 zip (in TWRP) to keep twrpas your recovery. Then flash the latest supersu in TWRP and reboot.
Deleting the -w stops the flash-all.bat from wiping your device. So when you boot again everything is as it was.
k.s.deviate said:
Download the newest factory image, extract it all. Right click the flash-all.bat and select edit. Scroll to the -w and delete it. Then boot into bootloader and run the flash-all.bat. Then, fastboot boot TWRP RC2 and then flash the RC2 zip (in TWRP) to keep twrpas your recovery. Then flash the latest supersu in TWRP and reboot.
Deleting the -w stops the flash-all.bat from wiping your device. So when you boot again everything is as it was.
Click to expand...
Click to collapse
wouldn't this be the same as taking the ota update? or does the ota lock the bootloader?
Echo2Lincoln said:
wouldn't this be the same as taking the ota update? or does the ota lock the bootloader?
Click to expand...
Click to collapse
Ota does not lock the bootloader, but it will not flash if you have a modified system partition or TWRP recovery. It will simply fail. You could do the above steps with the ota file from Google as well.
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: