Related
Hero guys
I just want to know, is there any way to root and keep getting OTA ?
And what is the best method to root?
Sent from my HTC One_M8 using Tapatalk
ahmadsraj said:
Hero guys
I just want to know, is there any way to root and keep getting OTA ?
And what is the best method to root?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
You still can OTA, even your phone is rooted.
Only their is some tips you need to know:
1. Don't delete or change any files and apps that is build-in on system.
Even you want to delete apps made from telecom operators IS NOT PERMITTED!
2. Recovery need flash back to original version.
For these two tips, you can do OTA even your phone is rooted.
But note that YOU NEED TO ROOT AGAIN every OTA.
missile0407 said:
You still can OTA, even your phone is rooted.
Only their is some tips you need to know:
1. Don't delete any files and apps that is build-in on system.
2. Recovery need flash back to original version.
For these two tips, you can do OTA even your phone is rooted.
But note that YOU NEED TO ROOT AGAIN every OTA.
Click to expand...
Click to collapse
Speaking to point 2:
I recommend not flashing a custom recovery at all. You can boot to TWRP/CWM/Philz from fastboot without flashing, and this leaves your stock recovery intact.
To do this: download your preferred recovery image. Let's say it's called "openrecovery-2.7.0.3-m8.img"
Copy this file to the same folder your "fastboot" executable is in on your computer.
Boot your phone into fastboot and connect it to your computer via USB.
Type in the following on your computer:
Code:
fastboot boot openrecovery-2.7.0.3-m8.img
Now your phone will boot into TWRP without touching your partitions or anything else that might affect OTAs. Apply your root.zip update and reboot!
EDIT: Once you've booted into your custom recovery from fastboot, you can disconnect the USB, so you're not stuck at your PC.
craig0r said:
Speaking to point 2:
I recommend not flashing a custom recovery at all. You can boot to TWRP/CWM/Philz from fastboot without flashing, and this leaves your stock recovery intact.
To do this: download your preferred recovery image. Let's say it's called "openrecovery-2.7.0.3-m8.img"
Copy this file to the same folder your "fastboot" executable is in on your computer.
Boot your phone into fastboot and connect it to your computer via USB.
Type in the following on your computer:
Code:
fastboot boot openrecovery-2.7.0.3-m8.img
Now your phone will boot into TWRP without touching your partitions or anything else that might affect OTAs. Apply your root.zip update and reboot!
EDIT: Once you've booted into your custom recovery from fastboot, you can disconnect the USB, so you're not stuck at your PC.
Click to expand...
Click to collapse
Hello,
I have the same question as the OP. Everything seems to make sense when following this post. My question is even though I will just boot into recovery without ever flashing the recovery am I really able to disconnect my phone from the computer? It seems like the recovery files are actually on the computer so I would need to keep the phone connected while I install the supersu.zip
Thank you for the help
I don't see why you would want to disconnect it but the image should be loaded into ram so I assume it would be safe to disconnect. I have never tried it though :/
exad said:
I don't see why you would want to disconnect it but the image should be loaded into ram so I assume it would be safe to disconnect. I have never tried it though :/
Click to expand...
Click to collapse
Ok I guess I should just leave it connected since I just need to install the supersu.zip file.
Every time an OTA update is applied will I just need to boot into TWRP recover and reinstall the supersu.zip file in order to regain root access?
SouthBayBruin said:
Ok I guess I should just leave it connected since I just need to install the supersu.zip file.
Every time an OTA update is applied will I just need to boot into TWRP recover and reinstall the supersu.zip file in order to regain root access?
Click to expand...
Click to collapse
There's no reason you *can't* leave it plugged in, but yeah, when you run the fastboot command it loads the custom recovery into RAM, and the connection to your computer is doing nothing for you. I give my personal guarantee that it's 100% safe to disconnect after recovery's loaded. But again, if leaving it plugged in makes you more comfortable, it won't hurt.
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
zimilaci said:
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
Click to expand...
Click to collapse
Did you just install the regular supersu file?
I read this thread (http://forum.xda-developers.com/showthread.php?t=2755657) and it seems that if I install the regular supersu root file the OTA update will fail.
Just wondering if you just used the regular files in order to root your phone.
SouthBayBruin said:
Did you just install the regular supersu file?
I read this thread (http://forum.xda-developers.com/showthread.php?t=2755657) and it seems that if I install the regular supersu root file the OTA update will fail.
Just wondering if you just used the regular files in order to root your phone.
Click to expand...
Click to collapse
http://download.chainfire.eu/396/SuperSU
zimilaci said:
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
Click to expand...
Click to collapse
Can you please guide me through the entire process on how to install the OTA update and not lose root, I don't have much knowledge when it comes to flashing into recovery, etc. I do have an HTC One M8 with S-Off. I would be eternally grateful if you could help me out.
KaranNavani said:
Can you please guide me through the entire process on how to install the OTA update and not lose root, I don't have much knowledge when it comes to flashing into recovery, etc. I do have an HTC One M8 with S-Off. I would be eternally grateful if you could help me out.
Click to expand...
Click to collapse
Dude, do the research yourself. I don't know how many more times this has to be said. There's nothing special you have to do, just apply the OTA update when prompted
Hi I m really new to this so excuse me ...
i got many updates by flashing with fastboot prerooted system.img i was on 2.19.40.18 prerooted but i would like to go to a stock no rooted to be able to apply OTA now
I tried an erase of my phone, but i came back to prerooted ...
I tried to install tethered TWRP and to install the.zip from asus download page but it was stuck on updating IFWI .... ( 2.19.40.20 zip file from asus )
What can i do ?
Plz help me
You need to go into the SuperSU settings, scroll to near the bottom and choose "Full unroot."
I did all on this post : http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
I did unroot, flashed all 4 line before but i think my recovery is corrupted, it end in error with the green guy instantly and flashin via fastboot recovery.img isnt doing anybetter ...
I m really stuck ..
i was trying an adb sideload with a stock rom is this a good idea ? i got error protocol fault ...
shinjy87 said:
i was trying an adb sideload with a stock rom is this a good idea ? i got error protocol fault ...
Click to expand...
Click to collapse
Protocol fault is because you don't use latest ADB. Google it.
i successfully did this but now adb is stuck on serving 13 % and on the phone : verifying update package , it stopped like 15 min ago ...
Here's what I did to go from pre-rooted system back to stock.
1. Download the official latest image from Asus http://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
2. Rename the zip to MOFD_SDUPDATE.zip
3. Unroot via SU
4. Uninstall Xposed and modules if you have them busybox etc. (uninstall.bat for xposed it's easy)
5. Copy MOFD_SDUPDATE.zip to an SD card and insert into phone or copy to internal memory
6. Boot into recovery by holding power and volume up
7. If you get dead android press power button and volume up button and release.
8. Auto installs new image
I went this route after unrooting via SU and uninstalling xposed framework still wouldn't let me run OTA updates for some reason. I imagine I did something along the road or removed a system app or something. It wouldn't let me manually sideload or update and would error out halfway through the process. I cleared fastboot cache and even reset the device to no avail. I was on 2.19.40.18. I installed the 2.19.40.20 image then the OTA update to .22 yesterday.
If I root the device again which is likely I'll use method 3 and the rootkit tool.
i will try your way, installing the 22 now.
But i dont remember in recovery the auto installs new image ?
error in recovery trying to update the .22 like you said, i need to put the .20 before the .22 ?
shinjy87 said:
error in recovery trying to update the .22 like you said, i need to put the .20 before the .22 ?
Click to expand...
Click to collapse
I installed the 2.19.40.20 full system image (1.1GB) from Asus yesterday. They didn't have the full image for .22 up but they do now. I was on the .18 pre-rooted image. When you hold power and volume up choose recovery and it should install the MOFD_SDUPDATE.zip automatically (mine did). I had issues trying to manually update the phone from .18 to .20 and .22 via ADB (the patches are like 30MB). It would start the update with the android robot then fail about halfway.
Download the correct system image for your device. The new update is available as a full image now so download the .22 image from Asus and then rename it to MOFD_SDUPDATE.zip. Copy it to an SD card and insert it back into your phone. Phone is powered off so hold power and volume up to get the recovery screen. It will say Normal in a big green arrow. Change it to recovery via the volume buttons then hit power button and it should find and automatically install the MOFD_SDUPDATE.zip image.
FYI this is on a ZE551ML 4GB/64GB US WW firmware based phone. I imagine the other models are the same or very similar.
I wish I could articulate this better. Hopefully someone more knowledgeable comes along and lends a hand.
Hi, want to ask.
Previously i root by using Method 1 (PRE-ROOTED SYSTEM.IMG).
can i use your method to revert to stock rom and root again using Method 3 (1 CLICK ROOT TOOL)?
wlbwlb said:
Hi, want to ask.
Previously i root by using Method 1 (PRE-ROOTED SYSTEM.IMG).
can i use your method to revert to stock rom and root again using Method 3 (1 CLICK ROOT TOOL)?
Click to expand...
Click to collapse
Yes.
Induced_Apathy said:
Yes.
Click to expand...
Click to collapse
Thank, another question. will it wipe all my data?
wlbwlb said:
Thank, another question. will it wipe all my data?
Click to expand...
Click to collapse
Flashing the entire system image you want to wipe everything anyways in this case. If you mean using the one click rootkit (method 3) to root then no it will not.
Yea. I'm hoping someone finds a way to return this to a "never been rooted" device where the OTA actually works.
madmike23 said:
Yea. I'm hoping someone finds a way to return this to a "never been rooted" device where the OTA actually works.
Click to expand...
Click to collapse
Flash the .18 pre-rooted, then don't update SuperSU binary. Take OTAs as needed.
If OTA doesn't show up, download the OTA and adb sideload into stock recovery.
Harfainx said:
Flash the .18 pre-rooted, then don't update SuperSU binary. Take OTAs as needed.
If OTA doesn't show up, download the OTA and adb sideload into stock recovery.
Click to expand...
Click to collapse
I've done that before, with any OTA, it'll give me the error droid when installing. That's when I said screw it, and try to unroot. And now I'm stuck with that error no matter what.
madmike23 said:
I've done that before, with any OTA, it'll give me the error droid when installing. That's when I said screw it, and try to unroot. And now I'm stuck with that error no matter what.
Click to expand...
Click to collapse
What does the recovery log say?
Harfainx said:
What does the recovery log say?
Click to expand...
Click to collapse
Only thing that caught my attention is: Unable to open '/sdcard/MOFD_SDUPDATE.zip': No such file or directory.
This was last attempt unrooted and this morning's OTA
Hi , i got my HTC today i am thinking to root it and install custom rom but i have a question ,if i unlock the bootloader and root it , i will not get updates from HTC server i know that but is there any way i can unroot and look bootloader and get to stock firmware and receive uppdates from HTC ?
and those who have installed custom Rom is there a big advantage ,battery specially ?
pspkid said:
Hi , i got my HTC today i am thinking to root it and install custom rom but i have a question ,if i unlock the bootloader and root it , i will not get updates from HTC server i know that but is there any way i can unroot and look bootloader and get to stock firmware and receive uppdates from HTC ?
and those who have installed custom Rom is there a big advantage ,battery specially ?
Click to expand...
Click to collapse
Custom roms on the 10 (like previous HTC flagships) give you more tweaks, customization and sometimes speed, custom kernels can give better battery, root also give you access to apps like V4A and Titanium Backup.
For official OTA meaning receiving it on your phone from Wifi or mobile data, you have to restore an untouched system image and Boot (meaning stock recovery too) or flash a RUU (but this one will wipe your internal memory).
Though if the Firmware update is your concern, I just learned that you just rip it from the OTA (of your Cid number) Zip, and simply flash it in RUU Mode.
All these methods won't require S-off
You have some posted OTA zips just be sure you have the same Cid
vegetaleb said:
Custom roms on the 10 (like previous HTC flagships) give you more tweaks, customization and sometimes speed, custom kernels can give better battery, root also give you access to apps like V4A and Titanium Backup.
For official OTA meaning receiving it on your phone from Wifi or mobile data, you have to restore an untouched system image and Boot (meaning stock recovery too) or flash a RUU (but this one will wipe your internal memory).
Though if the Firmware update is your concern, I just learned that you just rip it from the OTA (of your Cid number) Zip, and simply flash it in RUU Mode.
All these methods won't require S-off
You have some posted OTA zips just be sure you have the same Cid
Click to expand...
Click to collapse
Thanks but i didnt understand your last point ,see here is my problem i am staying in dubai and i have got only one update 1.30 (around 100MB)i am having auto focus issue , so how can i install OTA update manually ?
When you Unlock Bootloader you wipe everything.
After that you install TWRP via fastboot. Read Only.
Then make a backup of System IMAGE, just in case.
You can Flash systemless Root (from Dev Forum here) and systemless Xposed (if you want to....) and still get OTA Updates!
But... if you now want to install the OTA you have 2 Options.
A: reflash Stock Recovery from a OTA.zip anyone else provided and do a normal OTA, this will update the kernel aka Boot.img in which systemless Root and Xposed are stored. And the Recovery, so you need to reflash TWRP and Root and Xposed again.
B: install the OTA while TWRP is still installed.
This will update System but not included Firmware.zip
You can unpack the OTA.zip and the included Firmware.zip and then manually Flash Boot.img and Radio.img (no need for recovery.img as you want to keep twrp) then reflash Root and Xposed. Now you have about 75% updated.
Or you could try flashfire on Tour rooted phone
Haldi4803 said:
You can unpack the OTA.zip and the included Firmware.zip and then manually Flash Boot.img and Radio.img (no need for recovery.img as you want to keep twrp) then reflash Root and Xposed. Now you have about 75% updated.
Click to expand...
Click to collapse
Why not just flash the entire signed firmware.zip from the ota and be 100% updated? Why unzip it, break the signature, and only flash bits and pieces of it? I'm just not following the logic here.
Because it doesn't Flash in TWRP. I tried
Renaming the whole firmware.zip as 2PS6IMG.zip and putting it on ext_sd and flashing it it Download-mode might work and seems like a way easier Idea, agree on that.
Haldi4803 said:
Because it doesn't Flash in TWRP. I tried
Renaming the whole firmware.zip as 2PS6IMG.zip and putting it on ext_sd and flashing it it Download-mode might work and seems like a way easier Idea, agree on that.
Click to expand...
Click to collapse
Of course firmware doesn't flash in TWRP.
If you're s-on, you have to flash SIGNED firmware in RUU mode. If you're s-off, you can flash signed or unsigned and from download mode or RUU mode. I just don't understand why you're telling people to break the zip signature to flash pieces of it when it's so much easier to flash the entire thing by either:
A) renaming firmware.zip to 2PS6IMG.zip (just rename it, don't open it or you break the signature), placing on external SD, reboot to download mode and let the phone prompt you to flash it
B) boot the phone in RUU mode ("fastboot oem rebootRUU" command from download mode) then flashing with fastboot (fastboot flash zip firmware.zip).
Either of those methods will get you 100% of the updated firmware.
jollywhitefoot said:
Of course firmware doesn't flash in TWRP.
If you're s-on, you have to flash SIGNED firmware in RUU mode. If you're s-off, you can flash signed or unsigned and from download mode or RUU mode. I just don't understand why you're telling people to break the zip signature to flash pieces of it when it's so much easier to flash the entire thing by either:
A) renaming firmware.zip to 2PS6IMG.zip (just rename it, don't open it or you break the signature), placing on external SD, reboot to download mode and let the phone prompt you to flash it
B) boot the phone in RUU mode ("fastboot oem rebootRUU" command from download mode) then flashing with fastboot (fastboot flash zip firmware.zip).
Either of those methods will get you 100% of the updated firmware.
Click to expand...
Click to collapse
thanks for making it simple and clear , what firmware is latest ? i am running now 1.30.401.1 is there any newer available ?
jollywhitefoot said:
Of course firmware doesn't flash in TWRP.
Either of those methods will get you 100% of the updated firmware.
Click to expand...
Click to collapse
The phone doesn't know you have TWRP installed instead of stock recovery.
If You Start the OTA and install it it will Reboot Into twrp and install System then Abort.
I always have to Problem of no computer. So all Fastboot Options are off for me, sorry for mentioning this complicated Update method. Listen to jollywhitefoot he knows the stuff
Yeah, on Sony there were some ways to make Root persist in an OTA.
Does work here as well with Systemless Root as its in Boot.img. but when you Update Kernel it's gone. So I can't patch Boot.img and recovery.img at once
Haldi4803 said:
Yeah, on Sony there were some ways to make Root persist in an OTA.
Does work here as well with Systemless Root as its in Boot.img. but when you Update Kernel it's gone. So I can't patch Boot.img and recovery.img at once
Click to expand...
Click to collapse
If you s-off you can remove stock recovery from the firmware.zip, flash the ota.zip in twrp and flash the modified firmware separately in download mode (or by 2PS6IMG.zip on ext_sd). Otherwise, you have to use the signed firmware from HTC which includes stock recovery, as you know.
So, for s-on, without a computer, to FULLY, 100% update and root, you need:
1) system_image backup with stock recovery and boot
2) external SD card
3) flashable zip with TWRP recovery in it renamed to 2PS6IMG.zip on root of external sd
4) superSU zip
Then:
1) restore stock system_image, boot and recovery
2) reboot to system
3) take OTA
4) reboot to download mode and allow 2PS6IMG.zip (with TWRP in it) to flash
5) reboot to recovery and flash superSU.zip
There may be alternative methods, but this is how I would do it.
jollywhitefoot said:
1) restore stock system_image, boot and recovery
2) reboot to system
3) take OTA
4) reboot to download mode and allow 2PS6IMG.zip (with TWRP in it) to flash
5) reboot to recovery and flash superSU.zip
There may be alternative methods, but this is how I would do it.
Click to expand...
Click to collapse
Is it enough for point 1 to restore only the Stock Recovery
when twrp is always being Read only and systemless Root and Systemless AdAway are installed and no other changes on System?
Best Regards
Thomas
TomF1979 said:
Is it enough for point 1 to restore only the Stock Recovery
when twrp is always being Read only and systemless Root and Systemless AdAway are installed and no other changes on System?
Best Regards
Thomas
Click to expand...
Click to collapse
Yes. And I don't think you ever need stock boot either.
jollywhitefoot said:
Yes. And I don't think you ever need stock boot either.
Click to expand...
Click to collapse
Thanks.
Only one question for point 4,
Must be only the Recovery.img in the zip File or inclusive the Android txt File?
Best Regards
Thomas
TomF1979 said:
Thanks.
Only one question for point 4,
Must be only the Recovery.img in the zip File or inclusive the Android txt File?
Best Regards
Thomas
Click to expand...
Click to collapse
For the zip to be flashable you need the android-info.txt file.
jollywhitefoot said:
If you s-off you can remove stock recovery from the firmware.zip, flash the ota.zip in twrp and flash the modified firmware separately in download mode (or by 2PS6IMG.zip on ext_sd). Otherwise, you have to use the signed firmware from HTC which includes stock recovery, as you know.
So, for s-on, without a computer, to FULLY, 100% update and root, you need:
1) system_image backup with stock recovery and boot
2) external SD card
3) flashable zip with TWRP recovery in it renamed to 2PS6IMG.zip on root of external sd
4) superSU zip
Then:
1) restore stock system_image, boot and recovery
2) reboot to system
3) take OTA
4) reboot to download mode and allow 2PS6IMG.zip (with TWRP in it) to flash
5) reboot to recovery and flash superSU.zip
There may be alternative methods, but this is how I would do it.
Click to expand...
Click to collapse
Thanks!
So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.
Cyber Akuma said:
So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.
Click to expand...
Click to collapse
If you have twrp installed it wont update the firmware only software. You need to flash firmware seperatly with fastboot.
So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?
Cyber Akuma said:
So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?
Click to expand...
Click to collapse
Correct.:good:
Can somebody please explain how to flash the firmware with fastboot?
So I have to flash the OTA with TWRP, afterwards I have to extract the firmware file out of the OTA.zip and flash it with fastboot. But which commands are necessary in fastboot?
To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.
kjjejones42 said:
To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.
Click to expand...
Click to collapse
Thats not true. You flash in ruu mode when S - ON. If your are S - Off you can do it from download mode. I think you are a little confused with that thread. Those firmwares are modified and for S -Off phones only.
yldlj said:
Thats not true. You flash in ruu mode. If soff you can do it from download mode.
Click to expand...
Click to collapse
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?
kjjejones42 said:
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?
Click to expand...
Click to collapse
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.
yldlj said:
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.
Click to expand...
Click to collapse
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery
kjjejones42 said:
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery
Click to expand...
Click to collapse
Correct. Also unmodified boot. But if your flashing unmodified system image, boot and stock recovery you may aswell just boot to android and take the ota.
Anyone has the latest(released Feb 16th) oreo OTA full stock firmware from T-Mobile?
I tried pulling it from a logcat. Was going to fastboot flash it since I can't install it while rooted. Every url I found in the logcat gave me a 405 error though.
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Uzephi said:
Pulling the log through ADB will yield the OTA download link. That's how @joemossjr and I grabbed the Oreo update from nougat for TMO and Sprint.
Click to expand...
Click to collapse
Step by step instructions would be appreciated.
droidgreg said:
Step by step instructions would be appreciated.
Click to expand...
Click to collapse
It's hard to explain. You have to capture the moment the phone grabs the OTA file from Motorola's update website.
Enable developer options
Enable ADB
Plug phone up to a PC that has updated ADB binaries
Open terminal/command prompt
Adb shell
Logcat
After you do that your terminal of choice will start spitting out the log.
Run the system updater.
Download the OTA. At that moment, one of the logs should give you a VERY long URL. That's the download link you're looking for.
Copy and paste into your browser. You should be auto downloading it.
Done
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
I used titanium backup to freeze the update service as it's named in the notification.
charlatan01 said:
I used titanium backup to freeze the update service as it's named in the notification.
Click to expand...
Click to collapse
Thank you. I looked under U for update. I should have searched... It's actually called Motorola Update Services.
joesee said:
Very stupid question, but I have to ask, because Moto is a bit wonky on bootloaders and updates, etc.
I'm currently on OCX27 and I've got the notification to download OCX27.1. I do have an unlocked bootloader and I am rooted with Magisk. Since I have not overwritten the recovery partition, can I take this update? On most other phones I have, I've been able to restore the stock recovery partition, flash the update, and flash TWRP back on, but on this Moto, I chose to boot twrp for loading magisk via adb. Make sense? If I'm not able to take this update, can I shut these update notifications off? They are already off in dev options.
Thanks in advance!
Click to expand...
Click to collapse
You won't be able to update through OTA if you're rooted
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Hi, I am wondering, if I am on ocx 27 do you guys think the 27.1 ota will install in adb sideload as it won't install in ota and I am not rooted. Also, is there a way to extract the bin in the ota?
droidgreg said:
I got another Moto Z2 Force today. Fresh out of the box TMO. Came with the OCX27. I have not yet taken the update. If someone can guide me on how to extract the OTA That'd be helpful. Only thing I am willing to do so far with this new device is unlock the bootloader that's it. I will not root or install TWRP until I can extract the OTA and attempt to fix my other device stuck in an unknown baseband no IMEI state. I got there by attempting to install TWRP and root with Magisk.
Click to expand...
Click to collapse
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
climbhigh77 said:
Did you get your second Z2 rooted and if so did you use magisk v16? I just got a Z2 today that is on the December 1, 2017 security patch, OCX27.1, Android 8.00 and I'd like to root but hesitant. I have already unlocked the bootloader, placed magisk and twrp-3.2.1-1-nash zip(s) in internal storage, and know how to fastboot boot into recovery, I just don't want to brick my new phone. Any help with step by step instructions once I'm in TWRP to flash magisk is greatly appreciated! Do I need to do any of the following: Keep system read only or allow modifications before flashing magisk? wipe data/factory reset, mount storage, wipe cache and dalvik after flashing? Thanks in advance!
Click to expand...
Click to collapse
All you need to do is grab the latest twrp img and zip file from twrp. Should be version 3.2.1-1
Then fastboot boot the img file, then once in twrp you want to flash the zip file, then when that is done reboot back into recovery
Then simply flash Magisk and reboot. Done.
How should I properly Flash Stock Firmware?
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
climbhigh77 said:
New to Moto phones and wondering what the correct method is for reverting to stock? I downloaded the 27.1 Oreo zip from this thread, do I flash it in twrp or should I flash it in adb from the bootloader? I get the following error message in twrp whenever I wipe dalvik/cache, try to install a zip, or do a backup which always says fail. I need a fresh install and re root, etc. Thank you!!
Click to expand...
Click to collapse
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
mattlowry said:
you can not flash with twrp. open the zip and see if there is a "flash-all.bat" file as well as adb and fastboot files. if not then pull them from one of the other flashall zips and add them to 27.1 zip. boot your phone to the bootloader, connect usb cable to your device and pc, then run the .bat file.
Click to expand...
Click to collapse
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
climbhigh77 said:
Factory reset gets the same error message shown in the attached photo. Thanks for the info, unfortunately I'm still a bit confused. Is this the only method to return to stock? I've searched but I'm not finding much and this method is completely new to me. In the past I've used Odin and LG up with my other devices, this is my first motorola. If I wipe internal storage in twrp will that erase the OS and need a new install? I am thinking that may clear up my issues but nervous that the phone won't boot up after that. Thanks and my apologies for my noob questions.
Click to expand...
Click to collapse
unfortunately other than manually fastbooting each img file to your phone this is the only way. check out this https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
BROKEN
droidgreg said:
https://we.tl/B4j816Z2n8
Here's the link to the TMO OCX27.1 OTA firmware if anyone needs it.
Click to expand...
Click to collapse
Please upload again. Thx
sd_N said:
Please upload again. Thx
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=673956719939833411
Here's the official 27.1 firmware. The flashfile.xml has the correct order and commands to flash in fastboot, or search xda for the converter to a flashall.bat.
Sent from my Moto Z (2) using XDA Labs