Database Info

[Q] If your phone is rooted can you still get the ota updates? And One more ?

If the skyrocket is rooted can you still get ota updates? If so How? I am new to this. And also what is the current OTA update?

If its just rooted yes and it'll remove your root if you are on a custom ROM then it'll tell you you have one but it wont download
Sent from my SGH-T989 using Tapatalk

If your phone is rooted when an OTA update is released, you won't be able to download it. Unfortunately one have to be on stock to be able to download it, with bloat included and everything.

It told me I had a update but said server was down then I went back to it today and it says my phone is up to date

From what I understand if you are rooted with stock recovery you can take the ota update. If you are rooted with cwm recovery than you cannot take the ota. The beautiful thing I think is than even if you are rooted with cwm, and an ota releases (that you for some wild reason can't wait to have) its easy as pie to flash back to stock. At that point you should be able to take the ota. Heck maybe even just flashing the stock recovery itself would do the trick.....I dunno
As for current ota, most of us seem to have gotten stuck with 2.3.5. But there were quite a few folks who received the 2.3.6 update.
Sent from my SAMSUNG-SGH-I727 using xda premium

cdshepherd is correct. I was on stock 2.3.5 with stock 3e recovery... and was fully rooted. I was able to take the ATT OTA 2.3.6 update and kept superuser root access.

DoctorQMM said:
cdshepherd is correct. I was on stock 2.3.5 with stock 3e recovery... and was fully rooted. I was able to take the ATT OTA 2.3.6 update and kept superuser root access.
Click to expand...
Click to collapse
+1. I got 2.3.6 and kept root access, too. I'm also on stock recovery.

If you are not SO interrested in OTA
cdshepherd is correct, but, when 2.3.6 came out a few weeks ago, several folks were able to get it posted somewhere as a RAR file. you might look around if you are just dying to have it.. I think it was back around 11/21/2011 when I saw it the first time. About 290mb if I recall correctly.
Good luck!
[SIGPIC][/SIGPIC]

I was rooted and still allowed the OTA update 2.3.6.. and still have root access
Sent from my SAMSUNG-SGH-I727 using XDA App

Ok people heres the deal. To take an ota update you can be rooted but . You need to have stock recovery, and all bloatware intact. It can be frozen but not deleted. And no one knows yet if the 4.0 ota will remove root. 2.3.6 ota did not. So we can hope.

Auto-update warning! Turn off your phone if you are unlocked and rooted stock!!!

I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm

mcduck$ said:
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
Click to expand...
Click to collapse
What ROM were you running? It should have disable OTA's thats why I ask.

Brian Gove said:
What ROM were you running? It should have disable OTA's thats why I ask.
Click to expand...
Click to collapse
The title says rooted stock.

I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...

mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Did you try re-rooting using current methods?

mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2

Zalithian said:
Did you try re-rooting using current methods?
Click to expand...
Click to collapse
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?

mcduck$ said:
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
Click to expand...
Click to collapse
Pretty sure it will just work or fail, but I'd wait for confirmation from someone else first - better safe than sorry.

Can you supply your new Baseband Version number?

I just froze sdm 1.0. I went to the software update and it crashed. I so let's hope that stops the update...
Sent from Land Line using pay phone

epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
I535VRLG7

epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
marcucci217 said:
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was going to play around with flashing different roms eventually, but after upgrading from a decrepit half working ICS flashed Droid X I was just happy to have fully working phone again. Unfortunately I was under the false impression that the jerks at Verizon would have given me the option to accept their so-called upgrade.

Didn't they already remove local search on Verizon? My phone came that way. Of course I didn't stay on stock once we were freed...

rooting with the rootdebugfs tool should still work!

I woke up to a failed update message. Ran the update again to see why it failed and it fails because it reboots into custom recovery. Rooted, unlocked, stock. Just have some apps disabled or frozen.

Can anyone point out where the in the directory the downloaded update zip would go to?
I didn't get an update message but I did check for one it was available for me. So I ticked ok and it downloaded but failed to update as expected because of the custom recovery I have in place.
But I can't find where the zip file download to.
I wanted to try and see if Chainfire's Mobile ODIN Pro would root the updated zip as it claims.

Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller

Yes my laziness allowed verizon to update both of my SGS3 to I535VRLG7. I hope I can reroot when I get a chance later.
I was running stock root on both devices.
Sent from my SCH-I535 using xda premium

Successful OTA Flash using Mobile Odin Pro and Kept Root/Unlocked Status
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Thanks, running a backup now before I try Mobile ODIN Pro. Will update this post:
Edit: Ok, it seems I have a successful flash using Mobile ODIN Pro.
Mobile Odin Pro gave me some Warnings in advance before continuing the Flash.
1) EverRoot may need to remove Google Maps during the flash to free up some space... yadda yadda..
2) The Modem Image on your device does not match the signature check....yadda yadda..
3) 5 out of 499 system files do not match the signature checks in the OTA zip... yadda yadda..
NOTE: I disabled signature checks on both warnings before proceeding.
But you do that AT YOUR OWN RISK!!
From what I gather, Mobile Odin made its own OTA zip from the target file before flashing it
I"ve uploaded some screen shots.
IMPORTANT!
PLEASE RUN A BACK UP before attempting anything risky like this.
ALSO! and VERY IMPORTANT!!
If you are using CWM as your recovery PLEASE PLEASE PLEASE check the size of your backup before proceeding with the update.
It seems CWM is not working properly on my SGSIII because the backup file sizes were only about 22 MB's large.. and thats is SO NOT GOOD!!
I went into GooManager and Flashed TWRP over CWM and ran a backup via TWRP and checked the file size to be in the range of 2.34GB's and thats what it should be (IMO). The only thing that bugs me about both recoveries is the date is 1979-12-31.. and thats definately wrong..
Anyways, my way of checking for root after an OTA is to run Titanium Backup because it always asks for SuperUser Rights before loading.
So all is well with that and checking to see if the Bootloader on my device was still Unlocked with EZ-Unlock said it still was..
Thats all I can think for now..

Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Stock rooted & it tried & failed 2x to do the update and there is nothing in /fota/
I still have root
Second attempt it booted into recovery & I just restarted as it had a fail error

Should I root now or after Jellybean is released by AT&T?

I guess my question is, if I wait to update to jellybean will the method that is available today to root the phone no longer exist? It appears that someone has described a method for me to update to the AT&T version of jellybean once it's available, so that shouldn't be an issue (I hope!).

We won't really know (if they plugged the root exploit hole) until the update goes out, and people try to root. But HTC has killed the previous root method with every AT&T OTA for this device so far. So if I were a betting man, I'd say that the current exploit will not work after updating to JB.
Really, you have nothing to lose if you root now versus after the Jellybean OTA. You can always unroot and accept the OTA later, if you change your mind. Also, if you are rooted and bootloader unlocked, once the AT&T JB OTA rolls out, it will probably be posted in a pre-rooted flashable form within days (maybe even hours) of it being rolled out officially. So you can just flash that on your rooted, BL unlocked device.
But on the other hand, if you accept the OTA and cannot root, you are stuck until a new root exploit is found.

i would root now and wait until a dev gets JB and makes it compatible, because what usually happens when new software or firmware is released is the manufacturers and carriers often patch the vulnerabilities we use to obtain root.

Root it now. There's no telling if a root method for a later version will arrive sooner or later so to be safe I'd do it now. You can flash any jellybean rom you want afterwards.
Sent from my One X using xda app-developers app

One thing that can be said with confidence is that rooting and unlocking is not going to get easier with each update. It may stay the same; it may get a lot harder. So there's no good reason to wait.

I personally haven't had any issues with Viper XL 3.1 (Jellybean), so you could upgrade now if you really wanted to take advantage of some of the features. If you're looking to stay on ICS, Viper XL 2.4 and CleanRom 5.1 are really solid choices.

speaking from experience.
root it now. If you update to jellybean via ota you might run into the problem that I'm currently having. OTA updated my rogers X One then rooted it. Bootloader unlock and root went fine, but when I went to use the penultimate TWRP, the screen wouldn't respond. Had to flash the newest TWRP and that responded to touch. But now when I flash a rom it won't respond to touch. My guess is that something in hboot 2.14 has changed.

veemodz823 said:
root it now. If you update to jellybean via ota you might run into the problem that I'm currently having. OTA updated my rogers X One then rooted it. Bootloader unlock and root went fine, but when I went to use the penultimate TWRP, the screen wouldn't respond. Had to flash the newest TWRP and that responded to touch. But now when I flash a rom it won't respond to touch. My guess is that something in hboot 2.14 has changed.
Click to expand...
Click to collapse
That's true, HTC is almost sure to further mess with hboot, as well as patch the root exploit.
Sent from my HTC One X using xda app-developers app

veemodz823 said:
root it now. If you update to jellybean via ota you might run into the problem that I'm currently having. OTA updated my rogers X One then rooted it. Bootloader unlock and root went fine, but when I went to use the penultimate TWRP, the screen wouldn't respond. Had to flash the newest TWRP and that responded to touch. But now when I flash a rom it won't respond to touch. My guess is that something in hboot 2.14 has changed.
Click to expand...
Click to collapse
redpoint73 said:
That's true, HTC is almost sure to further mess with hboot, as well as patch the root exploit.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Chongodroid flashed the new 2.14 boot and doesn't have an issue.. my guess would be some sort of firmware change/incompatibility

absolutelygrim said:
Chongodroid flashed the new 2.14 boot and doesn't have an issue.. my guess would be some sort of firmware change/incompatibility
Click to expand...
Click to collapse
Which isn't to say that they will even include hboot 2.14 in the AT&T OTA. We seem to get "special" treatment (in a bad way). So I'm betting they will have an even newer hboot for the AT&T update, and f_ck us even more.

I would do it now and never accept any OTA update. My phone came with the 1.14 HBOOT, but after I unlocked the bootloader, I downgraded that using JET and haven't looked back. With an unlocked bootloader and TWRP I am not even sure how they could make the AT&T Jellybean unrootable unless you take the OTA and it screws you with a new HBOOT. My only real advice is to never take an OTA if you plan to root.

Can I take OTA update and keep root?

I am running stock 4.1.2 rooted and froze SDM 1.0 with titanium backup to avoid the constant update reminders.
I am now curious can I accept the updates and keep root somehow?
Is something like OTA root keeper worthwhile?

You can still root but cannot unlock the bootloader. I'd recommend reading the 4.3 sticky thread before taking the ota even if you want to stay stock.
Sent from my d2lte using XDA Premium 4 mobile app

dpeeps74 said:
You can still root but cannot unlock the bootloader. I'd recommend reading the 4.3 sticky thread before taking the ota even if you want to stay stock.
Sent from my d2lte using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you saying that because of the 4.3 issues?
I would rather not mess with the phone but I just got a gear 2 neo and it will not connect. I think this is because of the older android version. The specs on the gear software say it requires 4.2 or higher

scottfarcuz said:
Are you saying that because of the 4.3 issues?
I would rather not mess with the phone but I just got a gear 2 neo and it will not connect. I think this is because of the older android version. The specs on the gear software say it requires 4.2 or higher
Click to expand...
Click to collapse
Ya you need 4.3.
So you have options, since you're have a galaxy gear you're probably going to be running stock TouchWiz, so I would just take the upgrade.
You can root later, but the gear would never work with aosp anyway. Safestrap can make your phone run pretty well with a TouchWiz custom rom if you eventually decide you want one.
Or you can load a custom TouchWiz 4.3 rom right now and see if it connects, then you wouldn't lock your phone down permanently.
Sent from my HTC6525LVW using Tapatalk

Id like to go with a custom rom but don't have a clue what I'm doing.
Thanks for the help

scottfarcuz said:
Id like to go with a custom rom but don't have a clue what I'm doing.
Thanks for the help
Click to expand...
Click to collapse
OK then read the sticky threads in the development section, everything there has guides available for rooting and installing roms, then ask more questions if you have them.
Make sure you're reading the older sticky thread, not the 4.3 one.
Sent from my HTC6525LVW using Tapatalk

I've been unable to even get the OTA to work. It downloads then fails on install.
I have reset the flash counter but thought that was all that would be required to repair/delete before running the OTA update.
Does anyone have a suggestion?
Just to clarify the phone is currently rooted (casual method) on 4.1.2. I never touched the rom or bootloader after rooting i just installed titanium backup and froze all the bloat. Id like to get the OTA even if i lose root.
I reset the flash counter with triangle away and did a batch unfreeze with titanium backup.The OTA downloads then fails on install.

You would probably need to unfreeze everything for the update to work, at least thats what I have heard.
Sent from my SCH-I535 using Tapatalk

scottfarcuz said:
I've been unable to even get the OTA to work. It downloads then fails on install.
I have reset the flash counter but thought that was all that would be required to repair/delete before running the OTA update.
Does anyone have a suggestion?
Just to clarify the phone is currently rooted (casual method) on 4.1.2. I never touched the rom or bootloader after rooting i just installed titanium backup and froze all the bloat. Id like to get the OTA even if i lose root.
I reset the flash counter with triangle away and did a batch unfreeze with titanium backup.The OTA downloads then fails on install.
Click to expand...
Click to collapse
Use this thread to Odin flash 4.3. It's the exact same as taking the Ota.
http://forum.xda-developers.com/showthread.php?t=2586319
I'm sure you already know what taking the update entails, just be absolutely sure it's what you want to do before you flash it. There's no going back.
Sent from my HTC6525LVW using Tapatalk

How to go to stock from 4.1.2

I have gone thru the thread on how to go back to stock however i still have some questions, my s3 had a broken screen for quiet sometime so i am not sure where to start on getting it back to stock or whatever to get me back on the latest firmware. It is rooted on 4.1.2 but i dont know how to check if bootloader was unlocked or not.
If i can just flash a file to get me the latest i can do that as well. It does have TWRP for recovery

aford89 said:
I have gone thru the thread on how to go back to stock however i still have some questions, my s3 had a broken screen for quiet sometime so i am not sure where to start on getting it back to stock or whatever to get me back on the latest firmware. It is rooted on 4.1.2 but i dont know how to check if bootloader was unlocked or not.
If i can just flash a file to get me the latest i can do that as well. It does have TWRP for recovery
Click to expand...
Click to collapse
Its not unlocked by default but the last version of Android you were able to unlock it was on 4.1.2. You can unlock it with casual or ez unlock. If you however unroot it and take the OTA up to 4.4.2 your bootloader will be permanently locked and you will not be able to revert it back
Sent from my Nexus 5

ShapesBlue said:
Its not unlocked by default but the last version of Android you were able to unlock it was on 4.1.2. You can unlock it with casual or ez unlock. If you however unroot it and take the OTA up to 4.4.2 your bootloader will be permanently locked and you will not be able to revert it back
Sent from my Nexus 5
Click to expand...
Click to collapse
I am aware of that, i need to get it back to stock and to the latest version 4.4.x im just not sure how to go about it so i dont brick it. I have odin just looking for the correct stock files to get me the rest of the way and how to use them in what order

Can i just odin straight to 4.4.2? if i am rooted and unlocked on 4.1.2?

aford89 said:
Can i just odin straight to 4.4.2? if i am rooted and unlocked on 4.1.2?
Click to expand...
Click to collapse
You have to unroot first. Once your unrooted you can take the OTA. Just warning you about the bootloader being locked once you take the OTA. As far as straight to 4.4.2 I'm not sure. Never took an OTA on my S3. Start with unrooting first and see where it goes
Sent from my Nexus 5

ShapesBlue said:
You have to unroot first. Once your unrooted you can take the OTA. Just warning you about the bootloader being locked once you take the OTA. As far as straight to 4.4.2 I'm not sure. Never took an OTA on my S3. Start with unrooting first and see where it goes
Sent from my Nexus 5
Click to expand...
Click to collapse
how do i go about unrooting? like i said this phone sat for a LONG time im pretty sure i did it from outlawers method when i first got it
Thanks in advance

aford89 said:
how do i go about unrooting? like i said this phone sat for a LONG time im pretty sure i did it from outlawers method when i first got it
Thanks in advance
Click to expand...
Click to collapse
What SU app do you have on it?
Sent from my Nexus 5

ShapesBlue said:
What SU app do you have on it?
Sent from my Nexus 5
Click to expand...
Click to collapse
the one that looked like a superman shield, i went thru settings and found unroot however its not prompting me for an OTA and when i check it says its up to date. If i just odin the same version thats on there that should be fine right? then it'll start prompting for OTA's?

aford89 said:
the one that looked like a superman shield, i went thru settings and found unroot however its not prompting me for an OTA and when i check it says its up to date. If i just odin the same version thats on there that should be fine right? then it'll start prompting for OTA's?
Click to expand...
Click to collapse
Did you freeze any system apps? That is supersu your speaking of. I'm not completely sure if you can just odin to the newest firmware or not
Sent from my Nexus 5

ShapesBlue said:
Did you freeze any system apps? That is supersu your speaking of. I'm not completely sure if you can just odin to the newest firmware or not
Sent from my Nexus 5
Click to expand...
Click to collapse
No system apps are frozen, i did a factory wipe on it just thru TWRP and its still saying nothing is available

aford89 said:
No system apps are frozen, i did a factory wipe on it just thru TWRP and its still saying nothing is available
Click to expand...
Click to collapse
Then I would say try to Odin back to stock. It should work but don't quote me on that
Sent from my Nexus 5

ShapesBlue said:
Then I would say try to Odin back to stock. It should work but don't quote me on that
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah took the dive and used Odin from 4.1.2 all the way to 4.4.2 and everything worked out fine, was slow to boot and gave me an error but factory recovery wipe fixed that
Thanks for all the replies trying to help