Develop Bugs

[Q] OTA update hesitant

Someone flashed me to 4.1.1 and told me not to do the OTA update when I get it and I am unsure his reasoning. I have just received the OTA update and am hesitant to do so cause he told me I shouldn't this is my build.
https://lh6.googleusercontent.com/-Na05R2kBtw8/UH99ptd4xVI/AAAAAAAAB_U/WtzCgehyO34/s512/Screenshot_2012-10-17-20-45-36.png
Please let me know if I should accept the OTA or not I am very noob when it comes to this stuff and thanks

Maybe he rooted your phone too, and didn't want the update to break root.

leppo said:
Maybe he rooted your phone too, and didn't want the update to break root.
Click to expand...
Click to collapse
Is that the only reason not to accept the OTA, he did root it but that can always be redone. If I accept it I wont loose my data saved on my phone will I? I shouldn't I would think

TechnoDork said:
Is that the only reason not to accept the OTA, he did root it but that can always be redone. If I accept it I wont loose my data saved on my phone will I? I shouldn't I would think
Click to expand...
Click to collapse
The update won't install. Its best to just flash a rooted version of said update.
Sent from my Galaxy Nexus using xda premium

Which one would I use?

Rem3Dy said:
The update won't install. Its best to just flash a rooted version of said update.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Root doesn't prevent OTA updates from installing. However, installing the update will unroot the phone unless you use something like CWM which can keep root for you.

RoadHazard said:
Root doesn't prevent OTA updates from installing. However, installing the update will unroot the phone unless you use something like CWM which can keep root for you.
Click to expand...
Click to collapse
I tried the OTA but it shows an android with a Red sign in his belly. So basically I want to get my phone back to where I can get updates straight from Google and I don't need my phone rooted. Is this possible? If so I need instructions lol Much appreciated!

OTA Update 4.1.2 Failing update at 24-26%

The update process fails at 24-26%
I've downloaded 3 times
I am rooted w/Exynos and using OTA Rootkeeper
Thanks

U need to be fully stock.
Sent from my SGH-T889 using Tapatalk 2

Remove SU and OTA Rootkeeper?
Last update was ok with OTA Rootkeeper installed.
I can try.
Sent from my SGH-T889 using xda premium

Use odin/mobile odin to flash this http://forum.xda-developers.com/showthread.php?t=1975560 its prerooted

horr1blek1tten said:
U need to be fully stock.
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Not entirely, I did the OTA update while keeping root using SuperSU Pro and the root saving function. I had a similar failure at 25% when I first tried to update but found it was because I had missed a system app when defrosting. Make sure you've reinstalled/defrosted all the system apps you removed when you debloated.
As you're able to download the OTA update it means you've avoided tripping the flash counter and have been able to maintain the Status:Normal. I rooted originally with the Exynos abuse and have been using SuperSU Pro's root saving function since then to keep root through the OTA updates. It is possible but I will admit it has caused more difficulty then if I went the Mobile Oden or TWRP route.

Crap, I deleted some system apps.
Is there a list for me to compare?

razormy said:
Crap, I deleted some system apps.
Is there a list for me to compare?
Click to expand...
Click to collapse
If you cant figure out what u deleted.just flash again your stuff wont be deleted. Next backup the apps your going to delete. before you do using titanium backup

deeznutz1977 said:
If you cant figure out what u deleted.just flash again your stuff wont be deleted. Next backup the apps your going to delete. before you do using titanium backup
Click to expand...
Click to collapse
I just odined from the link provided.
All is well.
Thanks.

razormy said:
I just odined from the link provided.
All is well.
Thanks.
Click to expand...
Click to collapse
Glad to here it.
I learned several phones back, don't ever accept OTAs. Let other people be the guinea pigs and let the devs figure out what the carrier is patching.

[Q] KitKat 4.4.2 Update fail on rooted Nexus 7 2013 Wifi

Help !!!
I just updated my NEXUS 7 2013 from 4.4 to 4.4.2 but after restarting, the Android version in settings still says 4.4.
I checked for updates again in System Updates menu but my device says the system is up to date.
My device is Nexus 7 2013 32G rooted under TWRP 2.6.3.1 recovery on Super SU root.
I also tried updating manually using TWRP zip update but it failed.
here's the part of the prompt during TWRP update:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/sdcard/Dow...
Hope someone can help me find a solution for this. Thanks!

I auto updated my nexus 7 2013 wifi 32gb with 4.2.2 and there were no problems. I put the device back to stock 4.4 first and unrooted the tablet as well. My suggestion is to get the toolkit and select any version for device then select flash stock and unroot box. I did this and received the ota update the next day. After updating successfully you can root and install custom recovery again if that is what you want. Do not OEM lock the device because every time you unlock it again you will erase all content.
Best of luck
Sent from my Nexus 7 using xda app-developers app

OP: Uninstall stickmount (easiest) or flash the debuggerd in this thread.

Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4

player911 said:
Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4
Click to expand...
Click to collapse
Being rooted is fine. I was rooted just had to uninstall stickmount, and it updated from 4.3 to 4.4.2, I did lose root, but that was easily rectified.

mdamaged said:
Being rooted is fine. I was rooted just had to uninstall stickmount, and it updated from 4.3 to 4.4.2, I did lose root, but that was easily rectified.
Click to expand...
Click to collapse
How did you update? Side-load?

I'm guessing the Stickmount issue is only present on 4.4 because I was on 4.4.1 (Stock Rooted ROM by Scroler) and flashed the OTA I received on device in TWRP and it successfully updated to 4.4.2...and I never lost root ?
Sent from my Nexus 7 using Tapatalk 4

Richieboy67 said:
How did you update? Side-load?
Click to expand...
Click to collapse
Nope, OTA.

thanks
Jleeblanch said:
I'm guessing the Stickmount issue is only present on 4.4 because I was on 4.4.1 (Stock Rooted ROM by Scroler) and flashed the OTA I received on device in TWRP and it successfully updated to 4.4.2...and I never lost root ?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Can you give us the link to the stock rooted rom by scroler?? i can't seem to find it anywhere. thnks alot!

mdamaged said:
Nope, OTA.
Click to expand...
Click to collapse
Cool, I just ran the update myself with no issues. I just changed back to the stock recovery first and ran the ota to 4.4 no problem. I was worried about it though because I had issues when doing my Nexus 4 but it was my fault. At the end in the recovery when it asked if I wanted it to fix root I clicked yes. I should have clicked no and just rerooted using wug or something.
Now I am going to grab the 4.4.2 update. I do not have ota yet for 4.1 or 4.2 on my Nex 7. My Nex 4 though is all set at 4.4.2 and it seems like they really fixed tons of stuff! I can't wait to get that on the 7!!
Thanks:good:

mdamaged said:
OP: Uninstall stickmount (easiest) or flash the debuggerd in this thread.
Click to expand...
Click to collapse
I used to have OTA problems with Stickmount and that damn debuggered file on my 2012 Nexus 7. Never installed it on my flo as a result.
Are you saying that simply uninstalling Stickmount will be sufficient for an OTA to take successfully? Does uninstalling reinstate the previous debuggered file, or must we replace it manually?

mlj11 said:
I used to have OTA problems with Stickmount and that damn debuggered file on my 2012 Nexus 7. Never installed it on my flo as a result.
Are you saying that simply uninstalling Stickmount will be sufficient for an OTA to take successfully? Does uninstalling reinstate the previous debuggered file, or must we replace it manually?
Click to expand...
Click to collapse
Yes. Upon installation, Stickmount makes a backup of debuggerd in the same directory with a bak extension, when uninstalled it renames it to debuggerd, restoring the stock debuggerd, I did not have to put it back manually.

player911 said:
Yea it won't update if your rooted.
-sent from my LG G2 using XDA Premium 4
Click to expand...
Click to collapse
I flashed 4.4.1-> 4.4.2 successfully with twrp on a rooted device but it was just rooted with a modified host file, no other mods.

godutch said:
I flashed 4.4.1-> 4.4.2 successfully with twrp on a rooted device but it was just rooted with a modified host file, no other mods.
Click to expand...
Click to collapse
I thought the issue was to do with OTA updates and and not flashing updates from recovery as this is defeating the purpose of OTA udates.
Sent from my Nexus 7 using xda app-developers app

I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.

vivre said:
I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.
Click to expand...
Click to collapse
You could always just do a full wipe and restore it to factory defaults. That'll do it for sure.
Sent from my Nexus 7 using Tapatalk

dmginc said:
You could always just do a full wipe and restore it to factory defaults. That'll do it for sure.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Anyway to do it without wiping data? :crying:

vivre said:
Anyway to do it without wiping data? :crying:
Click to expand...
Click to collapse
Sorta yeah. But it hurts more than it helps. Wiping is really the best way to go. Or just wait a day or two and see if it comes.
Sent from my Nexus 7 using Tapatalk

vivre said:
I am on 4.3, unlocked and rooted with TWRP recovery.
The 4.42 update notification had been there for a while and I finally decided to take the plunge.....
I ran the update through the notification and my device rebooted into the TWRP custom recovery. Not knowing what to do, I rebooted again and checked the version. Nothing had changed and I am still at 4.3.
However the System Update notification had disappeared. I checked for System Update and it says my device is up-to-date....
How do I get the OTA update again?
What do I have to do to get the update installed on my device?
I have since also uninstalled StickMount.
Click to expand...
Click to collapse
The over the air will not work if you have a custom recovery. You have to flash the update zip with TWRP or whatever custom recovery you are using. You could move the update from "cache" to "storage" if you still had it or just download it to storage and then flash (Install) it with TWRP..

wantabe said:
The over the air will not work if you have a custom recovery. You have to flash the update zip with TWRP or whatever custom recovery you are using. You could move the update from "cache" to "storage" if you still had it or just download it to storage and then flash (Install) it with TWRP..
Click to expand...
Click to collapse
Thanks.
Your method worked.... but only after I uninstalled Xposed Framework ! :good:

[Q] OTA update root??

I'm still using stock unrooted, but I'm wondering if I root my G Pad only without flashing a custom recovery and ROM, will I still be able to update via OTA like usual or I have to unroot first!
Thank you very much in advance!

Fullmetal Jun said:
I'm still using stock unrooted, but I'm wondering if I root my G Pad only without flashing a custom recovery and ROM, will I still be able to update via OTA like usual or I have to unroot first!
Thank you very much in advance!
Click to expand...
Click to collapse
In the past several people have reported problems when taking an OTA update with a rooted G-Pad. Rather than risk it, I have always done a completely clean update with a wipe of the device using the LG Tool Upgrade Recovery with my V500. Once that completes I re-root the device and continue on.

muiriddin said:
In the past several people have reported problems when taking an OTA update with a rooted G-Pad. Rather than risk it, I have always done a completely clean update with a wipe of the device using the LG Tool Upgrade Recovery with my V500. Once that completes I re-root the device and continue on.
Click to expand...
Click to collapse
Even if you don't have a custom recovery installed? Because I saw that some people with root only updated their G Pads ota with no problems with only root removed afterwards! They may have lied however!
I think this ota update with root problem applies to most android phones, right?
Thanks for your help

Fullmetal Jun said:
I'm still using stock unrooted, but I'm wondering if I root my G Pad only without flashing a custom recovery and ROM, will I still be able to update via OTA like usual or I have to unroot first!
Thank you very much in advance!
Click to expand...
Click to collapse
In my case, I have root on stock recovery, and always do the updates via OTA, without any problems, and without losing root after that!
Sent from my LG-V500 using XDA Premium mobile app

Hugo-PT said:
In my case, I have root on stock recovery, and always do the updates via OTA, without any problems, and without losing root after that!
Sent from my LG-V500 using XDA Premium mobile app
Click to expand...
Click to collapse
Excellent, it is good to hear that root without changing recovery could work when taking an OTA update. I was only quoting what I had read, not what I had personally experienced. If it were to fail I would assume you could always use the LG Tool and do an upgrade recovery to reimage the entire tablet.

I did the latest OTA update (while drunk) and it updated fine and I still had root when I woke in a panic the next day wondering if I had soft bricked it.

Tachikoma_kun said:
I did the latest OTA update (while drunk) and it updated fine and I still had root when I woke in a panic the next day wondering if I had soft bricked it.
Click to expand...
Click to collapse
Rock on! Now that's Happy Flashing...

A few months ago my g pad was root and I successful updated it to kitkat via ota update. But recently it showed up another update on the tablet and when I tried update it, it failed giving an error. I think if u are running kitkat and are rooted then ota update won't work.
Sent from my GT-I9505 using XDA Free mobile app

muiriddin said:
Excellent, it is good to hear that root without changing recovery could work when taking an OTA update. I was only quoting what I had read, not what I had personally experienced. If it were to fail I would assume you could always use the LG Tool and do an upgrade recovery to reimage the entire tablet.
Click to expand...
Click to collapse
Thanks for your feedback guys! The G Pad community is awesome! I'm happy I bought this excellent tablet with awesome specs! Nothing can beat its value for money and great design!
I rooted with towelroot and hope I receive future updates! Never thought towelroot would make rooting so easy as with my previous phones, had to do some steps while connected to pc.

Will receive a ZF2, but im lost about root and OTA

Hello guys
I will receive my zf2 on monday, but im kinda lost with the root and OTA. Could you help me with my concerns?
1) I saw that exists 3 methods of root. Each of them has differences about future OTA updates.
NOTE:
If you root via METHOD 1 you can update SuperSu app as well as update binaries but PLEASE DON'T apply any OTA update as the phone WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb...
If you root via METHOD 2 you CAN UPDATE VIA OTA/NO BOOTLOOPS BUT YOU HAVE TO UNROOT FIRST BEFORE APPLYING OTA
If you root via METHOD 3 you CAN UPDATE VIA OTA/NO BOOTLOOPS AND UN-ROOTING BEFORE APPLYING ANY OTA IS NOT NECESSARY.
If I root using method 3, will I have no headache when receveing and installing future OTAs? WIth a rooted phone, will I be able to install them without further bootloops and unrooting before doing it? ( So method 3 is the easiest of them,right?)
2) About the Bloatwares that are pre-installed on zf2, Its safer to freeze them than uninstalling?

up

Root with method 3 is fine, you can OTA.
But, you delete any Bloatware, the ota will fail.

demonntl said:
Root with method 3 is fine, you can OTA.
But, you delete any Bloatware, the ota will fail.
Click to expand...
Click to collapse
Right, at first I used method 3 and uninstalled a lot of bloatware but the next OTA failed because it didn't find files to patch...
Now I still use method 3 but just disabled the app I don't want/use, and OTA work fine, did it 2 times already.

Its safer to update the cellphone, than aplly root, or the inverse?

operatorsof said:
Its safer to update the cellphone, than aplly root, or the inverse?
Click to expand...
Click to collapse
it's always safer to unroot first just in case asus changes something that could cause a bootloop even when using method 3.personally I prefer to unroot, remove busybox and xposed then update.
Sent from my ASUS_Z008 using Tapatalk

luisoman2000 said:
it's always safer to unroot first just in case asus changes something that could cause a bootloop even when using method 3.personally I prefer to unroot, remove busybox and xposed then update.
Sent from my ASUS_Z008 using Tapatalk
Click to expand...
Click to collapse
But my cellphone is new, I didn't update yet. What you suggest?
Sent from my ASUS_Z00AD using Tapatalk

operatorsof said:
But my cellphone is new, I didn't update yet. What you suggest?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
simple, update via ota. after you update to the latest ota you can root.
Sent from my ASUS_Z008 using Tapatalk