Database Users

Got update on rooted stock with TWRP

Hello,
My wife has a Nexus 4.
I unlocked the bootloader, flashed TWRP, rooted it, and installed busybox.
Yesterday she handed me her phone and it was sitting in TWRP.
She said she got a message saying there was an update and she clicked okay.
I asked her if she saw anything going on but she wasn't paying attention so I didn't know if the update was applied or not.
So... I just rebooted the system from within TWRP.
Looking at her "about phone" it still shows that she is on 4.2.1 and when I check for updates it says she is up to date.
Questions:
What to do now?
Why wasn't the update applied? ... in the past on my Nexus 7 I have done OTA updates with rootkeeper installed and TWRP applied them automatically.
Was the update file deleted from her phone or can I find it somewhere in TWRP and apply it?
Is it like a normal .zip that you install or is it another process?

I'm in the same situation, unsure what to do.
I don't want to have to to do a factory reset for a minor update.
EDIT: Also installing the OTA.ZIP in TWRP fails

Got there in the end:
a) If you want to keep your data & settings and are running the stock rom; only flash boot.img, system.img, and recovery.img (optional) with fastboot.
Here is the JOP40D factory image if you need it. occam-jop40d-factory-ca7602f0.tgz - 327.21 MB
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings

alexroborock said:
Got there in the end:
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings
Click to expand...
Click to collapse
There must be a better way to do this.
That is a huge security risk flashing someone else's untrusted image onto your phone.
What about adb sideload?

You can download the image directly from Google
Sent from my Nexus 4 using Tapatalk 2

You need stock recovery for the ota update to work.
Sent from my Nexus 4 using xda app-developers app

Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.

silverramsrt said:
Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.
Click to expand...
Click to collapse
Did you lose root?

Rizy7 said:
Did you lose root?
Click to expand...
Click to collapse
Yes. The update replaced the recovery_from_boot.p or whatever file and the insecure boot image I had. I just reflashed TWRP, did a factory reset and installed CM anyway.

[Q] OTA update to 4.2.2 problems

My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?

rsipson said:
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
Click to expand...
Click to collapse
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip

You have to restore everything except relocking bootloader ... To be able to update ...when u finish ..just re-root
Sent from my Nexus 7 using xda premium

Same thing happened to me, I had to unroot and then root again after update.
Sent from my HTC Desire S using xda app-developers app

heat361 said:
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
Click to expand...
Click to collapse
Thanks for your post. I tried this using Clockwork and got a very long error message. I will quote part of it.
assert failed_apply_patch_check("/system/bin/debuggerd", "a2323a0c8 and a lot more
This is followed by error in file
I saw something about busybox changing some system files.
Any ideas??

How do I unroot without whipping all data?
Sent from my Nexus 7 using xda app-developers app

Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.

bftb0 said:
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
Click to expand...
Click to collapse
Sorry for being a numpty... can someone put the above into a mini step by step guide for me.. I'm stuggling with the terminology.
I rooted my Nexus and have since forgotten anything techie regarding it. I have StickMount and cannot update to 4.2.2..
How do i flash boot.img and system.img via fastboot, where do i get these files from, what versions etc do i need? And over flash SuperSU root kit?
What is OTA?
Basically, I think i need a newbie guide. I am techie enough to achieve most things normally.. i just don't know the android system at all, and what i did know to be able to root it i have completely forgotten!
Any guidance would be very much appreciated. Cheers.

[XT1032] OTA to 4.4.4 (falcon_umts.EURetail.en.EU)

Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Extra info:
- Received the OTA while being rooted & using custom recovery.
- Can be flashed using PhilZ recovery.
- SuperSU Pro survived the OTA.

Petrovski80 said:
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Click to expand...
Click to collapse
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.

feartheanonymity said:
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
Click to expand...
Click to collapse
It should be. I flashed it using Philz recovery.

feartheanonymity said:
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
Click to expand...
Click to collapse
I had the same problem, TWRP did not take the OTA file properly. Every time it wanted to boot after the install started, it started TWRP and if I restarded the device it went into a bootloop.
So I installed Philz and everything went fine!

It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app

drfr said:
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I copied the zip from /cache and am attempting to install it with the latest Philz.
I get this error in Philz when flashing the zip:
Verifying current system...
"EMMC:boot:10485....................... a0" has unexpected contents.
I restored my stock kernel (was running Faux before). My bootloader is unlocked and I am rooted.
Is it possible to flash directly? Or must I restore stock recovery, flash and reroot?

Is it OK to flash this if I'm already on 4.4.4?

Quark^2 said:
I copied the zip from /cache and am attempting to install it with the latest Philz.
I get this error in Philz when flashing the zip:
Verifying current system...
"EMMC:boot:10485....................... a0" has unexpected contents.
I restored my stock kernel (was running Faux before). My bootloader is unlocked and I am rooted.
Is it possible to flash directly? Or must I restore stock recovery, flash and reroot?
Click to expand...
Click to collapse
You´ve restored wrong kernel. It may be working for you, but it is different from stock. The error says that there is something that is not supposed to be there in the kernel partition.
Nicolae-Daniel said:
Is it OK to flash this if I'm already on 4.4.4?
Click to expand...
Click to collapse
You´re kidding, right?

No.my system is tesco GB.i live in Romania.by flashing this i believe will improve connectivity.
@knizmi what do you think?

Nicolae-Daniel said:
No.my system is tesco GB.i live in Romania.by flashing this i believe will improve connectivity.
@knizmi what do you think?
Click to expand...
Click to collapse
1. You can´t flash this if you are on anything other than en.EU 4.4.2. This is not a complete ROM, but rather an update for a specific ROM version.
2. It is possible reflash your XT1032 with en.EU 4.4.2 firmware and then update it to 4.4.4, but if you don´t know what you are doing, you could brick your device (several people have when they tried to downgrade the bootloader).
3. What improvement in conectivity do you mean? Is the tesco firmware limited in any way? AFAIK it isn´t, so leave it as it is and be happy about a great phone with the latest Android version.

knizmi said:
1. You can´t flash this if you are on anything other than en.EU 4.4.2. This is not a complete ROM, but rather an update for a specific ROM version.
2. It is possible reflash your XT1032 with en.EU 4.4.2 firmware and then update it to 4.4.4, but if you don´t know what you are doing, you could brick your device (several people have when they tried to downgrade the bootloader).
3. What improvement in conectivity do you mean? Is the tesco firmware limited in any way? AFAIK it isn´t, so leave it as it is and be happy about a great phone with the latest Android version.
Click to expand...
Click to collapse
By connectivity I meant signal strength.

My US-Global XT1032 still waiting...

tonyleeloveyou said:
My US-Global XT1032 still waiting...
Click to expand...
Click to collapse
US Global already has 4.4.3. The new kernel and dialer are already there, so don´t expect any improvements besides security patches when we get 4.4.4.

I received the OTA today. Updated without problems. Stock XT1032 8GB Moto G.

drfr said:
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you're still on Stock Recovery and don't want to use Philz, you can try to update the OTA by following the steps in the OP of this Post. I tried a lot of flashing, but in the end only this worked:
http://forum.xda-developers.com/moto-g/general/ota-file-indian-dual-sim-4-4-4-t2810166
Just follow the steps below the text:
REVERT TO STOCK WITHOUT LOSING DATA OR ANYTHING ELSE
Phone is unlocked, rooted and had xposed modules on it

Petrovski80 said:
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Extra info:
- Received the OTA while being rooted & using custom recovery.
- Can be flashed using PhilZ recovery.
- SuperSU Pro survived the OTA.
Click to expand...
Click to collapse
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip

dreezz said:
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
Click to expand...
Click to collapse
So why don´t you revert your build.prop to stock?

dreezz said:
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
Click to expand...
Click to collapse
Knizmi is right. You modified your build.prop file, and an OTA update requires unmodified system files. You can add files to /system without problems however, so the su binary for example isn't an issue.
Sent from my Moto G using Tapatalk

OK, and where do i find a stock build.prop?
i don't know what modifications i have, but can i replace the stock one with my current after flashing? (and do i need to?)

HI! Firstly thanks for share the zip.
I´m using cwm recovery, superSU and xposed. Can I flash the zip directly from the recovery without any change? Will I lose the recovery (coming back to stock recovery) if I succed?
I tried to install the OTA after uninstall xposed and checking the ota survival mode on superSU, but it didn´t work (bootloop).
Thanks in advance.

[SOLVED] Locked Bootloader -- Bootloop. How to save data?

Guys, I'm stuck.
So, I had my Nexus 4 wonderfully running the latest CM11 nightly. Then the Lollipop Factory Image for Nexus 4 came out. My bootloader was unlocked and had TWRP custom recovery. Then in fastboot mode, I flashed the new Lollipop factory images, except the userdata.img. By doing this, I replaced TWRP with stock recovery. Then I restarted the phone.
It stuck in the twirling colorful circles for 2+ hours. I heard it needed 10 minutes or so to fully load Lollipop. But 2 hours? So I then started troubleshooting. One of the first thread I stumbled upon suggested for me to re-lock the bootloader, which I stupidly did. It did not fix the problem. Now I'm stuck!
I'm unable to boot. Stuck in the twirling circles animation for hours.
I have no custom recovery, so I can't load custom ROMs.
I have no unlocked bootloader, so I can't reflash the factory images (or downgrade to stock 4.4.4).
And if I unlock the bootloader, I will lose ALL of my user data, including photos, music, and the Titanium Backups of all my app data, SMS, call logs, etc.
I tried flashing the latest CM11 nightly through ADB sideload within stock recovery, but I get the 'signature verification failed'. Is there a 'signed' ROM I could sideload through stock recovery?
Would ADB sideloading the Nexus 4 Lollipop OTA zip through stock recovery fix this problem? I'm downloading the OTA zip right now.
EDIT: Sideloading the OTA zip did the trick! I'm staring at Android is upgrading... right now. Thanks XDA for the thought process, wouldn't have solved it without posting this thread. Although, please note that at this time, I essentially have Android 5.0 installed, but having bootloop. I can't guarantee that this will work if you bootloop while having custom ROM or Kit Kat installed.
What else I could do to save my data? I'm out of ideas.
EDIT: To save my data, because now I'm able to boot to Lollipop (by flashing official Google Android 5.0 Lollipop OTA zip through stock recovery ADB sideload; see above solution), I'm gonna transfer all the files in storage/emulated/legacy (the internal sdcard) to my PC. I will then unlock the bootloader through fastboot, thus wiping all data on the phone. Then I'll just move everything back from PC to the phone. I should have done this in the first place!
HLEP.

You lost all data as soon as you locked it. Just saying.
Sent from my HTC One_M8 using Tapatalk

Misledz said:
You lost all data as soon as you locked it. Just saying.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
This is untrue. I was unable to boot, but after flashing the OTA zip, I can boot to Lollipop and I still have everything, even my old apps, without needing to reinstall anything. Granted, there are errors here and there (probably due to dirty flash upgrade), but my data is intact.
As I said, I previously had TWRP, CyanogenMod 11, root and unlocked bootloader. Now I have Android 5.0 Lollipop, no root, a locked bootloader and all of my data. I wanted to show you my bootloader screen, but I have no other camera with me. The screenshots below should suffice.
Check attachment for proof.

Ah. I thought you were locked out being unable to boot. Anyways, you can back it up via Holo Backup, might wanna check it out
Sent from my HTC One_M8 using Tapatalk

Misledz said:
Ah. I thought you were locked out being unable to boot. Anyways, you can back it up via Holo Backup, might wanna check it out
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, I was unable to boot. Then, I replaced custom recovery with stock recovery. Then I stupidly locked the bootloader. It's all good now.
I've never heard of Holo Backup before. It seems like the perfect solution for me, as I don't have root right now! And transferring 13GB of files via MTP or Wi-Fi will take ages.
Thanks a lot for the suggestion. I'm giving it a shot.

5.1 Update with TWRP / Unlocked Bootloader

Hello,
Is it possible to update from 5.0 to 5.1 if i have unlocked the bootloader? I also have TWRP. I downloaded the 5.1 update, but when i want to install it the phone reboots and i get into TWRP menu. Is there any way to flash the OTA update without losing my current data on the phone?
Thank you!

Dealing with the same problem here.
IIRC TWRP automatically handled OTA updates in the past but it doesn't seem to be working anymore.

What was the procedure you were using before? You just installed as a normal zip from TWRP ?

For the ota to work you have to be 100% stock system, recovery, and kernel. I'd just flash the system and boot images from 5.1 in fastboot to update.
Sent from my Nexus 5 using XDA Free mobile app

So sad. I will lose all the stuff I have on the device.

tzeus said:
So sad. I will lose all the stuff I have on the device.
Click to expand...
Click to collapse
Not if you just flash the System and Boot images and remove -w from the Flashall.bat command to prevent the wipe instead of using the OTA. If you use the OTA, you will have to be stock as the previous posted stated, which since you are rooted with a custom recovery, would require you to flash the stock image, wiping your device, before you could run the OTA. This is the result of a change in the way Android 5.+ authenticates, which is why it worked previously. It now checks the whole partition, and one byte out of place will abort it.
That said, you can always backup your phone (which is a good thing to do anyway before flashing/upgrading) to prevent data loss.
Edit: Actually, thinking about it, I think Wugs added a No Wipe option to his toolkit, just flash System and Boot images from there is likely easiest for you.

Can i flash 5.1 directly ? And then root and unlock bootloader/flash TWRP again ?

tzeus said:
Can i flash 5.1 directly ? And then root and unlock bootloader/flash TWRP again ?
Click to expand...
Click to collapse
To be clear, you do not need to relock your bootloader. You can just flash 5.1 and then root and install a custom recovery like TWRP again, yes. If you are not familiar, Wug's NRT make this a breeze. Once you get 5.1 installed, just hit root. It will install the latest TWRP version and root/install SuperSU and Busybox for you.

I need to download the whole 5.1 image from Google. And flash just like any other ROM from TWRP ?

tzeus said:
I need to download the whole 5.1 image from Google. And flash just like any other ROM from TWRP ?
Click to expand...
Click to collapse
No, download the image and extract it. See this, http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app