Database Info

[Q] Q. Why my system says up to date but its not???

I have a rooted NS4G with custom kernel Matr1x #5. Im currently on 2.3.4 and have not added any roms or updates. I kept recieving the OTA updates every 1/2 hr. im assuming for the 2.3.5. OTA was 22mb.
I was holding off for a while to not to update but finally gave in. I went to install OTA and my phone turned off and look as tho it was going to update my system. I let 15-20mins go by and I was still at a screen where there was a triangle with an exculmation and the android.
I thought it shouldnt take that long to update so I pulled the battery. I rebooted my phone and it still has 2.3.4 as my android version but when I click on system updates it says my system is up to date which is not the case.
If anyone install this OTA how long did it take for the whole process??
How do I fix this is with my system saying its up to date but clearly its not since im on 2.3.4???
I no longer get the notification to install a OTA. I would like to install an OTA instead of doing it manually.
I still want to be able to receive updates OTA when the are released. Im afraid I messed something up
Any assistance would be greatly appreciated
Thanks

http://forum.xda-developers.com/showthread.php?t=1185812
Flash this in clockworkmod it should update u and u keep root.
Sent from my CM7 powered Nexus S 4g using XDA Premium App

Rooted phone + OTA = fail

You need a stock recovery to install an ota....
Sent from my Nexus S 4G using xda premium

[Q] i9020A - no 4.1.2 ota

So, its been what, four months since 4.1.2 hit the servers? Any idea why my lowly i9020A hasn't gotten her OTA?

Fylk said:
So, its been what, four months since 4.1.2 hit the servers? Any idea why my lowly i9020A hasn't gotten her OTA?
Click to expand...
Click to collapse
Who is your carrier? My impression is that OTAs are determined by the carrier, not Google. My i9020a is with Rogers, and it has gotten it. Also, if you have a custom ROM, OTAs might be turned off. Do you have a custom ROM?

For some reason I have not gotten an OTA since the time of ICS. I am using the i9020A model of Nexus S on AT&T (US).
I have to either manually download the OTA link posted by someone else on XDA or flash the stock image from Google's server.

Try switch your phone into airplane mode>Manage Apps>Google service framework (something like that)>Force stop>Clear data>Switch off airplane mode>Connect to wifi >Settings>About phone>Check whether you get your 4.1.2 ota update or not.
I tried this method twice when I didn't receive my 4.1.1 and 4.1.2 ota updates,and it works.Hope this helps you.
Sent from my Nexus S using xda premium

I have the same problem in my Nexus S. It received the OTA notification but failed in the middle of the installation process. After some reading. I found out that the installation process first checks for the ROM image signature; if it is not the original ROM, it won't proceed.
In my case, I have it rooted and installed a custom ROM. I ended up have to install the upgrade myself. It is quite simple. just search for it and you will find all the instructions.

Stock OTA Update and Checking the Status of your Phone

I'm using the default ROM for my One X and I'd like to update it (I haven't since I got it 6 month ago); do I need to re-lock the bootloader and unroot it before I can use the OTA update? Also it's been a while since I even fiddled with my phones software so I forgot anything else I may have done, is there a way I can check to see what else has been done and if it's safe to update it?
Currently I have:
Android Version: 4.0.3
HTC Sense Version: 4.0
Software Number: 1.73.631.1
HTC SDK API Level: 4.11
HTC Extension Version: HTCExtension_403_1_HA_4

What firmware are u on currently for starters
Sent from my HTC One XL using xda app-developers app

I added the info to the original post

bman3k said:
do I need to re-lock the bootloader and unroot it before I can use the OTA update?
Click to expand...
Click to collapse
Your phone should be factory default before performing OTA updates or results may be unexpected.
Most OTA updates are patch file based and require the files to be exactly what is expected.
There have been known issues with root being detected and the OTA failing.
Rooted phones progressing with an update but root lost after the update.
System files being modified and the OTA failing.
Recovery must be factory; not TWRP or CWM.
CID and MID must suit OTA.
The only modification I would consider safe through all OTA's so far has been SuperCID.

If you have any interest in rooting and flashing custom ROMs, I would suggest rooting and unlocking the bootloader now, while you are on 1.73, and not updating via OTA. The latest 2.20 update will also update your hboot, which plugs the holes by which kernels and radios can be flashed from recovery.

Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms

omario8484 said:
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
Click to expand...
Click to collapse
Agree. If you are already BL unlocked and rooted, why go through the hassle of relocking the BL and returning to stock, just to wait for the OTA?
Just flash a JB ROM, as there are already stock and custom JB ROMs posted in Development.
Plus, until the OTA actually hits, we don't know if it will even be rootable. They have plugged the existing root exploits with every successive AT&T OTA for this phone so far. No reason to think any different for the JB update.
Just flash a JB ROM and stay rooted.

Ya I really like viper xl v3 . Just apply fix listed on op and you should be good to go
Sent from my HTC One XL using xda premium

Stock OTA is not WORTH IT IMO, been there
Reselling the phone is probably the only reason i'd revert to stock.

Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.

bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Ok you're really lucky you didn't just brick your phone.... You want to stay in the att one x forums.... Notice theres a title diff. You're lucky it didn't succesfully flash or your phone would be dead... That's an international one x rom

bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Stick to the ROM's in our forum, I never heard of anything like that ROM for our phone sorry. Lucky you didn't brick it

O damn I feel very stupid now...
Can someone recommend me a JB ROM?
Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Edit: I figured out the Mount function in TWRP, so I know how to add new ROMs now

bman3k said:
O damn I feel very stupid now...
Can someone recommend me a JB ROM? Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Click to expand...
Click to collapse
Try them all, they are all good, the time it takes to ask for other peoples opinions you could have test driven them all yourself.

Are you looking for jb sense?

omario8484 said:
Are you looking for jb sense?
Click to expand...
Click to collapse
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?

bman3k said:
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
Click to expand...
Click to collapse
Funny that you bring titanium up...titanium helps you back up apps it also backs up your app data...and for sms just download something from the market here's one download the app super backup and you can backup your sms

So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.

bman3k said:
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
Click to expand...
Click to collapse
You did a full wipe before hand right?

I did the factory, system, cache and dalvik cache wipes
Edit: I got it to work, not really sure what I did different =/

Verizon OTA Update SIII

I unfroze all the apps I had frozen and tried the OTA and it still failed.
I am rooted with just the stock ROM.
Anything I am missing here?

I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.

No OTA updates will work on a rooted phone. If it somehow does work it will likely break your root privileges

ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Plunkyxda said:
I do not think OTA updates with the carrier is possible on a rooted phone. I know mine would not do OTA updates when it was stock, unlocked, and rooted. It would always fail.
Click to expand...
Click to collapse

You can do a OTA with root but you will just lose it. If you altered some system files it will fail or if you run a custom recovery it will fail.

I've had similar issues, on other devices, with ota updates not working because of root, and more specifically I believe, cwm recovery. Unfortunately I've had to use kies to update.
Sent from my SCH-I535 using xda premium

kendive said:
ok that makes sense.
So did you just not do the update and how do I make it stop trying to update.
I might start running custom roms again. I have not done that in a long time.
Click to expand...
Click to collapse
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.

Yea I agree... I did not really need the OTA and I plan on installing CleanROM 5.6 tmr.
I just froze all that bloat back. I can't stand all that S***T running in the back ground.
Plunkyxda said:
There was no option to update. Verizon pushed the update to my phone twice in the middle of the night without my knowledge or permission. In the mornings I would see the message that the update failed. I didn't want it anyway, and dislike the bloat, so I flashed to a custom ROM after their second attempt. No more OTA updates for me now. That's what happened with me anyway.
Click to expand...
Click to collapse

[Q] OTA Update on rooted GT-I9105P

Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.

boyansky78 said:
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
Click to expand...
Click to collapse
that is because it is a modded firmware

safariking said:
that is because it is a modded firmware
Click to expand...
Click to collapse
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.

boyansky78 said:
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
Click to expand...
Click to collapse
I will say it again
It is not possible to check for updates because the Firmware is modded and not original anymore that's why!!!

Hi "safariking",
In the current situation we have two identically modded FWs, but a different outcome.
It's very nice of you to take the time to answer my question so fully That's why I'd like to thank you for the effort. Herewith I am closing the topic.
Cheers.

No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P

safariking said:
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
Click to expand...
Click to collapse
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:

nickchk said:
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
Click to expand...
Click to collapse
Hi Nick,
Thanks for your reply. You are reading my mind. The issue is really interesting & I think it is worth discussing this.
Safari is right, when he says that FW upgrade OTA for customized ROM is not possible. This is of course true and no one has ever doubted it. This is why when I had the 4.1.2 installed on my G2+ no update was even possible. Droid detects immediately, that the OS has been modified and that you are not running stock ROM.
Okay, so far so good.
Now I have pre-rooted 4.2.2 installed on my phone. When I hit the "Check for update button" it detects that my OS is genuine (although it is not), downloads the whole update package (see screenshot), restarts the phone (part of the update process) and starts installing the update. When the installation reaches 25%, an error message appears saying, that an error has occurred. The phone restarts and loads the "old" OS.
I have tested this a several times and it always hangs on 25%.
The question is NOT why I CAN'T install OTA updates on modified ROM. The question is why I CAN download and install OTA updates on modified ROM.
My suggestion is that:
ROM 1 (4.1.2) had a modified kernel. That's why the OTA updates were not possible.
ROM 2 (4.2.2) is pre-rooted. And I assume it is just stock FW (kernel not modified) with few modifications in the user permissions. This would explain the OTA update and why it reaches download mode and hangs on 25% of the installation.
I hope this brings more clarification to the situation and this would be useful to all members of the forum.
Cheers!:highfive:

I have randomly come across and read posts and topics on this in the other devices' forum.
If I remember correctly, it is the custom recovery, i.e Cwm or twrp that blocks or interrupts the OTA process. 2 reasons why: you'll lose root access if the update went through. Secondly, if a user freezes or uninstalls stock apps like S Voice, Chat On etc, there will be trouble.
There are some ways of allowing an OTA to get pass a custom recovery. I think TWRP has this feature. Again, I stand corrected here lol.
Heard of OTA Root Keeper but no idea how it works
Sent from my GT-I9105 using xda app-developers app