I want to update to the latest firmware on my M7, but one of the USB data pins is broken so I'm not able to use fastboot.
What's the best procedure to update it?
I was thinking of using a Guru Reset rom to flash a stock OS and stock recovery, and then OTA update all the way up to Lollipop, which will update my firmware along the way. The only problem with that is that I'll be stuck on stock forever because I won't be able to flash TWRP through terminal without root.
I know that OTA updates use stock recovery to flash the firmware.zip inside the OTA. Is it possible to modify the OTA.zip to just flash the firmware?
thedancingbear said:
I want to update to the latest firmware on my M7, but one of the USB data pins is broken so I'm not able to use fastboot.
What's the best procedure to update it?
I was thinking of using a Guru Reset rom to flash a stock OS and stock recovery, and then OTA update all the way up to Lollipop, which will update my firmware along the way. The only problem with that is that I'll be stuck on stock forever because I won't be able to flash TWRP through terminal without root.
I know that OTA updates use stock recovery to flash the firmware.zip inside the OTA. Is it possible to modify the OTA.zip to just flash the firmware?
Click to expand...
Click to collapse
You can root any htc firmware using the root tool that therootninja provides on his website
Once you do that you can flash the stock recovery img or twrp using flashify and use the terminal functions within twrp
Related
Hello,
I have a Developer Edition (unlocked) with Stock 4.3 at the moment, is rooted and with TWRP 2.6.3.0 custom recovery, my phone is asking me to upgrade to 4.4. My questions are:
- What would be the results of the upgrade?
- It will flash over my custom recovery without problems?
I guess I will loose root and custom recovery but I can flash them again, my main concern is that the OTA will not flash correctly for being rooted and with custom recovery. Thanks a lot for those that know the answer and want to help me.
gustavorod said:
Hello,
I have a Developer Edition (unlocked) with Stock 4.3 at the moment, is rooted and with TWRP 2.6.3.0 custom recovery, my phone is asking me to upgrade to 4.4. My questions are:
- What would be the results of the upgrade?
- It will flash over my custom recovery without problems?
I guess I will loose root and custom recovery but I can flash them again, my main concern is that the OTA will not flash correctly for being rooted and with custom recovery. Thanks a lot for those that know the answer and want to help me.
Click to expand...
Click to collapse
i guess you cant flash official OTA through custom recovery..u need stock recovery to do this
gustavorod said:
Hello,
I have a Developer Edition (unlocked) with Stock 4.3 at the moment, is rooted and with TWRP 2.6.3.0 custom recovery, my phone is asking me to upgrade to 4.4. My questions are:
- What would be the results of the upgrade?
- It will flash over my custom recovery without problems?
I guess I will loose root and custom recovery but I can flash them again, my main concern is that the OTA will not flash correctly for being rooted and with custom recovery. Thanks a lot for those that know the answer and want to help me.
Click to expand...
Click to collapse
Actually, you won't be able to do an OTA update when you've a custom recovery (you shouldn't even get it in the first place, sometimes it comes through), if you try to apply the OTA, you'll boot back to the TWRP recovery.
So, you should either go full stock (recovery & ROM), then do an OTA. Or flash some 4.4 Custom ROM.
By itself the phone alerted me that the OTA download is available and wants to download and flash itself as it did when it upgraded from 4.2.2 to 4.3 so I am not planning to flash through TWRP...
gustavorod said:
By itself the phone alerted me that the OTA download is available and wants to download and flash itself as it did when it upgraded from 4.2.2 to 4.3 so I am not planning to flash through TWRP...
Click to expand...
Click to collapse
it will download OK, but when it reboots to start installing, you'll just see the TWRP screen and nothing is gonna happen; because the OTA expects stock recovery.
Thanks!!!!
I guess I better flash another 4.3 or 4.4 by myself, I just thought the OTA would be better first to upgrade to the latest firmware...
gustavorod said:
I guess I better flash another 4.3 or 4.4 by myself, I just thought the OTA would be better first to upgrade to the latest firmware...
Click to expand...
Click to collapse
you can do two things:
1- get s-off and flash any firmware you want
2- "download & install later" the OTA, once downloaded pull it to your PC, the OTA file will contain a "firmware.zip" which is signed and can be flashed in fastboot ruu mode (you have to issue the flash command twice!!!), which would upgrade your firmware (including hboot, kernal and recovery), but will leave your rom intact
----- because it flashes recovery, you need to reflash custom recovery
----- and, kernel (boot.img) you'll need to reflash the custom one (or dirty install the ROM), otherwise the ROM won't boot up
nkk71 said:
you can do two things:
1- get s-off and flash any firmware you want
2- "download & install later" the OTA, once downloaded pull it to your PC, the OTA file will contain a "firmware.zip" which is signed and can be flashed in fastboot ruu mode (you have to issue the flash command twice!!!), which would upgrade your firmware (including hboot, kernal and recovery), but will leave your rom intact
----- because it flashes recovery, you need to reflash custom recovery
----- and, kernel (boot.img) you'll need to reflash the custom one (or dirty install the ROM), otherwise the ROM won't boot up
Click to expand...
Click to collapse
I've looked around for a CWM compatible version of the Dev Edition + Root, but I'm not finding one. Is anyone aware of a CWM-packaged version that I can flash using CWM on a rooted device? Reverting to stock to pick up the OTA seems like a long way to go
Hi guys!
I've finally received 4.4.4 notification to update my German Moto x!!
I'd like to know one thing before I proceed.. If I update, will I have to root again the phone?
My phone has unlocked bootloader so there is no problem, but right now I'm on holiday and I don't have a pc to root it again..
Thanks a lot!
I have not upgrade to 4.4.4 yet.
I don't think you need to root again
Thanks!
I've read some other user just flashed the stock recovery, installed the ota and flashed back twrp recovery..
Others instead use fwz method
I think I'll wait until I'm home just to be sure I need my phone during the holidays!
daede86 said:
Thanks!
I've read some other user just flashed the stock recovery, installed the ota and flashed back twrp recovery..
Others instead use fwz method
I think I'll wait until I'm home just to be sure I need my phone during the holidays!
Click to expand...
Click to collapse
Hi, i was wondering the same thing. Is there a method for someone to create an update for rooted phones?
Also can you link me to the threads for flashing back to stock and what this fwz is?
thank you
Here you can find some info about FXZ (sorry for my typo)
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
In the same thread you can find the stock recovery, a user posted it. Just search stock recovery in the thread and you'll find it!
I'm not the right person to help you in detail.
I'm not an expert user
In the meantime I froze motorola OTA app to hide the update notification..
Guys, before anyone gets in trouble....there is no FXZ for the german (or any asia/european) Moto X's yet.
The only one released is the Verizon one....so DON'T flash the verizon FXZ.
You need to flash stock recovery back, and if the phone STILL won't take the OTA, also use "mfastboot" to flash system.img from the 4.4.2 FXZ (which IS released for the european/asia models). Afterwards, the OTA should install without fail.
You WILL need to re-flash TWRP no matter which method you use. You will also need to re-root IF you flash the system.img from the 4.4.2 SBF in order to be able to accept the OTA (you only flash system.img from 4.4.2 if the OTA fails after you have flashed stock recovery - it normally means you have modified /system in some way, and restoring the full system.img fixes this issue).
Good Luck - Remember: Don't flash the Verizon 4.4.4 FXZ to your non-Verizon phone. Not a good idea...
If your phone doesn't vary from Stock but rooted, you can get away with flashing stock recovery back on there and taking the OTA. (OTA wont install via custom recovery like TWRP, CWM, etc). And if that is the case, you will retain root. You can optionally flash TWRP back on there.
If you have Xposed installed, it will need to be disabled or removed for the OTA install to work.
It is when you mess with stock files in /System or other folders on the phone.. i.e. remove, rename, etc. files from them, that you may also need to flash system.img and possibly other parts. This is due to verification checks in the OTA zip itself. If you have to flash those parts, you will have to re-root. Not an issue if you have an unlocked bootloader.
Thanks a lot for your help and clarification!!
I knew I wasn't the right person
Guys just to be sure of the right process..
-download the actual sbf of my phone
-extract recovery.img from the sbf
-remove xposed
-flash the recovery with flashify
-take the ota
-flash back twrp recovery
Am I right?!
Thanks a lot
daede86 said:
Guys just to be sure of the right process..
-download the actual sbf of my phone
-extract recovery.img from the sbf
-remove xposed
-flash the recovery with flashify
-take the ota
-flash back twrp recovery
Am I right?!
Thanks a lot
Click to expand...
Click to collapse
IF you do not vary too much from Stock (i.e. didn't remove, rename or replace any "stock" files on your phone), then yes.
Oh, for Xposed, there is a disabler ZIP you can flash from custom recovery located in /storage/emulated/0/Android/data/de.robv.android.xposed.installer (or /SdCard/Android/data/de.robv.android.xposed.installer ) instead of removing it, as sometimes removing it doesn't undo all the changes.
Hello guys ,
I have a question about it. I have M8 Sprint in my hand with 4.4.4.
I recieved OTA Update with Lolipop 4.20.651.10 But can't install because of TWRP.
I want to update this phone. But is there any update version via TWRP ?
Or how i install stock recovery for my phone ? Already tried 5-6 Stock recoveries but non working.
B.R.
gLam16 said:
Hello guys ,
I have a question about it. I have M8 Sprint in my hand with 4.4.4.
I recieved OTA Update with Lolipop 4.20.651.10 But can't install because of TWRP.
I want to update this phone. But is there any update version via TWRP ?
Or how i install stock recovery for my phone ? Already tried 5-6 Stock recoveries but non working.
B.R.
Click to expand...
Click to collapse
did you unlock the bootloader and root? Its not a problem with TWRP. Since you have received the OTA sounds like you didn't do any of the requirements to install TWRP. I would do some research on Unlock Bootloader, ROOT.
schmeggy929 said:
did you unlock the bootloader and root? Its not a problem with TWRP. Since you have received the OTA sounds like you didn't do any of the requirements to install TWRP. I would do some research on Unlock Bootloader, ROOT.
Click to expand...
Click to collapse
Bootloader Unlock , Phone Rooted.
I downloaded the OTA but when is going to be recovery mode TWRP Not allowed to install it.
That's why i need Stock recovery or update file that we can flash from TWRP.
gLam16 said:
Bootloader Unlock , Phone Rooted.
I downloaded the OTA but when is going to be recovery mode TWRP Not allowed to install it.
That's why i need Stock recovery or update file that we can flash from TWRP.
Click to expand...
Click to collapse
TWRP isn't going to let you install the OTA file. You need to update your firmware. Flash lastest TWRP in Hboot or fastboot. I would read this thread here.
http://forum.xda-developers.com/showthread.php?t=2729173
schmeggy929 said:
TWRP isn't going to let you install the OTA file. You need to update your firmware. Flash lastest TWRP in Hboot or fastboot. I would read this thread here.
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
Flash lastest TWRP ? Why i need this i want to update my os to Lolipop. That's what i need. Don't care about ruu or anything.
gLam16 said:
Flash lastest TWRP ? Why i need this i want to update my os to Lolipop. That's what i need. Don't care about ruu or anything.
Click to expand...
Click to collapse
To upgrade you need to flash lastest firmware then ROM of your choice. To make that happen you need updated TWRP. The ruu is your OS and firmware, you better care.
I got an OTA update named OTA_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.35-7.18.531.2_release_450302.zip with size about 180MB.
Did anybody else get it?
I can't apply the update though because I have twrp and the phone is rooted. I was wondering if someone else got the update and applied it successfully on a rooted phone.
devsk said:
I got an OTA update named OTA_M7_UL_L50_SENSE60_MR_TMOUS_7.18.531.35-7.18.531.2_release_450302.zip with size about 180MB.
Did anybody else get it?
Click to expand...
Click to collapse
Should post this question here: http://forum.xda-developers.com/showthread.php?t=2305490
and the answer is probably yes since I don't see why T-mobile USA would push an ota update only to you
7.18.531.35 is the t-mobile US equivalent of 7.17.1540.35 which is the latest version with the stagefright 1.0 vulnerability fixed.
I can't apply the update though because I have twrp and the phone is rooted. I was wondering if someone else got the update and applied it successfully on a rooted phone.
Click to expand...
Click to collapse
You need to be on 100% stock rom including stock recovery to install ota updates. Better to return to stock using a ruu before applying the update imo since many users soft bricked their phones when attempting to install lollipop ota updates on stock rooted phones. If you need the RUU, look in the RUU collection thread, there is a 7.18.531.2 RUU posted there (link in my signature). Don't forget that questions should be posted in the q&a section, not in general. :good:
Thanks for your help. I found the RUU for my version. So, since I need to go back to RUU flash, I will need to re-setup my phone from scratch again just for getting this OTA....sucks!!
I wish they would make it easier to update modified phones. Just overwrite my root changes to /system and destroy my recovery but keep my /data and /sdcard. I can recover from that much faster than doing RUU and set up from scratch!!
So, on m7, isn't there way to flash stock on /system and stock recovery through fastboot and then take the OTA? I have done that on at least Samsung and Moto phones in the past and it worked fine.
So, if I restore system and boot partitions from my backup to stock, can I sideload the OTA ZIP using TWRP?
I should have made a recovery.img from the original stock recovery partition. Do you know if I can find the stock recovery here somewhere?
devsk said:
I wish they would make it easier to update modified phones. Just overwrite my root changes to /system
Click to expand...
Click to collapse
It is, you'll loose root every time you do an ota update.
and destroy my recovery
Click to expand...
Click to collapse
The ota is flashed using the stock recovery, and the stock recovery is also updated in that process.
So, on m7, isn't there way to flash stock on /system and stock recovery through fastboot and then take the OTA? I have done that on at least Samsung and Moto phones in the past and it worked fine.
Click to expand...
Click to collapse
Yes, either using a RUU, or a combination of a stock rom/backup (/system partition) flashed using twrp and then flashing the stock recovery back.
So, if I restore system and boot partitions from my backup to stock, can I sideload the OTA ZIP using TWRP?
Click to expand...
Click to collapse
No, the updater-script will only work with stock recovery
I should have made a recovery.img from the original stock recovery partition.
Click to expand...
Click to collapse
You can't backup the stock recovery directly from the phone (actually yes you can but it requires s-off and its somewhat complicated.
Do you know if I can find the stock recovery here somewhere?
Click to expand...
Click to collapse
already uploaded here:
https://www.androidfilehost.com/?fid=23991606952604831
or you can extract it from the ota update.
It was possible to update a stock rom + rooted phone simply by flashing the stock recovery back in the past (on kitkat roms and eariler) but it looks like its not possible anymore on lollipop updates. So much ppl posted here with the same problem: "Phone is stuck at HTC splash screen after installing update on stock rooted phone". Example here and here
The biggest problem if the ota install fine but the phone is stuck at the booting screen (like in the link above) is that your firmware will be updated to 7.18.531.35 so you won't be able to use the 7.18.531.2 RUU anymore unless you achieve S-OFF or edit your MISC partition.
alray said:
It is, you'll loose root every time you do an ota update.
The ota is flashed using the stock recovery, and the stock recovery is also updated in that process.
Yes, either using a RUU, or a combination of a stock rom/backup (/system partition) flashed using twrp and then flashing the stock recovery back.
No, the updater-script will only work with stock recovery
You can't backup the stock recovery directly from the phone (actually yes you can but it requires s-off and its somewhat complicated.
already uploaded here:
https://www.androidfilehost.com/?fid=23991606952604831
or you can extract it from the ota update.
It was possible to update a stock rom + rooted phone simply by flashing the stock recovery back in the past (on kitkat roms and eariler) but it looks like its not possible anymore on lollipop updates. So much ppl posted here with the same problem: "Phone is stuck at HTC splash screen after installing update on stock rooted phone". Example here and here
The biggest problem if the ota install fine but the phone is stuck at the booting screen (like in the link above) is that your firmware will be updated to 7.18.531.35 so you won't be able to use the 7.18.531.2 RUU anymore unless you achieve S-OFF or edit your MISC partition.
Click to expand...
Click to collapse
Thanks for the great help! I can't thank you enough.
One question: if I do fail to apply the OTA zip after restoring boot, system and recovery to stock, I will still be able to get TWRP back on the recovery through fastboot and restore my full TWRP backup to get a working system back, right? Is there a gotcha in that route?
devsk said:
Thanks for the great help! I can't thank you enough.
One question: if I do fail to apply the OTA zip after restoring boot, system and recovery to stock, I will still be able to get TWRP back on the recovery through fastboot and restore my full TWRP backup to get a working system back, right? Is there a gotcha in that route?
Click to expand...
Click to collapse
yes, even if the ota installation fails, you''ll be able to access fastboot, flash back twrp and restore your twrp nandroid backup. :good:
alray said:
yes, even if the ota installation fails, you''ll be able to access fastboot, flash back twrp and restore your twrp nandroid backup. :good:
Click to expand...
Click to collapse
Awesome!! :good::good:
I just recovered my phone with twrp recovery and the root is now gone so my phone is not currently rooted. And there is an OTA update. But I can't install it. It takes me to tarp recovery. So any help. What if I delete the twrp recovery and then install update?
ameerhamza193 said:
I just recovered my phone with twrp recovery and the root is now gone so my phone is not currently rooted. And there is an OTA update. But I can't install it. It takes me to tarp recovery. So any help. What if I delete the twrp recovery and then install update?
Click to expand...
Click to collapse
You must have stock recovery to install ota update along with an unmodified /system files, unmodified /data/preload files.
return to stock using a RUU before applying the ota is probably the safer way to go now with lollipop updates if you want to avoid a bootloop.