I cannot get JB still. I bought the phone from rogers and just use it on Telus.
Always when I try it gets stuck on bootloop.
Could I just borrow somebodies sim from rogers or fido and let them get the OTA?
not really sure how to get JB. Nothing has worked so far.
The OTA has absolutely nothing to do with what SIM you have in your device.
martonikaj said:
The OTA has absolutely nothing to do with what SIM you have in your device.
Click to expand...
Click to collapse
then howcome it won't let me update my phone?
I've tried roms, I've tried stock.
Not sure what's holding me back.
Mackie011 said:
then howcome it won't let me update my phone?
I've tried roms, I've tried stock.
Not sure what's holding me back.
Click to expand...
Click to collapse
If the OTA update bootloops your stock phone, you've likely changed something (knowingly or unknowingly) that's causing a conflict when the update applies. Also, you haven't indicated how you're trying to update.
What do you mean you've tried ROMs? That'll have nothing to do with OTA updates. Custom ROMs are a completely different path.
martonikaj said:
If the OTA update bootloops your stock phone, you've likely changed something (knowingly or unknowingly) that's causing a conflict when the update applies. Also, you haven't indicated how you're trying to update.
What do you mean you've tried ROMs? That'll have nothing to do with OTA updates. Custom ROMs are a completely different path.
Click to expand...
Click to collapse
Okay so at first I had paranoid android running fine and I had AOKP.
When JB was released I tried to just try a new rom but it would always go to the boot screen and just sit there forever.
I gave up and decided to factory reset everything completely and just went back to stock to try to get the over the air update. It constantly pops up, every 5 minutes. Update available! This has been happening for a long time I just decided I will use 4.0.4 for now because I couldn't figure out what I did wrong or what I was missing.
And that is pretty much where I am at right now.
Not really sure how to make it work.
Mackie011 said:
Okay so at first I had paranoid android running fine and I had AOKP.
When JB was released I tried to just try a new rom but it would always go to the boot screen and just sit there forever.
Click to expand...
Click to collapse
Likely didn't wipe properly, chose the wrong ROM, or tried to switch between ROM makers unsuccessfully.
I gave up and decided to factory reset everything completely and just went back to stock to try to get the over the air update. It constantly pops up, every 5 minutes. Update available! This has been happening for a long time I just decided I will use 4.0.4 for now because I couldn't figure out what I did wrong or what I was missing.
Click to expand...
Click to collapse
When you flashed back to stock it didn't flash properly, or missed part (like recovery, bootloader or radio), so the OTA won't install properly.
If you want stock 4.1.1, just flash it completely. Stop trying to mess with an OTA.
This is the only guide I'd recommend: http://forum.xda-developers.com/showthread.php?t=1626895
Factory images... including 4.1.1 are right here: https://developers.google.com/android/nexus/images
As well, some have reported issues trying to flash JB if they had an old bootloader. Make sure you flash the LC03 bootloader before trying to flash a JB ROM. (It's already part of the guide mentioned above.)
Sent from my Galaxy Nexus using Tapatalk 2
Related
My phone has been prompting me to install 4.0.4 update as of late. I was running a stock 4.0.4 flash w/ root and about 2 weeks after installing it via CWM it prompted me to install. The installation failed so I yanked the battery and it successfully booted back into the phone. After this it won't prompt again until after the phone is rebooted again.
I just flashed to the 4.1 Jelly Bean release figuring that would alleviate the problem and it still exists. My phone is constantly telling me to update the phone (even though now a 4.0.4 "upgrade" would infact me a downgrade). This is driving me crazy...is there any way to stop this from happening?
DKNUCKLES said:
My phone has been prompting me to install 4.0.4 update as of late. I was running a stock 4.0.4 flash w/ root and about 2 weeks after installing it via CWM it prompted me to install. The installation failed so I yanked the battery and it successfully booted back into the phone. After this it won't prompt again until after the phone is rebooted again.
I just flashed to the 4.1 Jelly Bean release figuring that would alleviate the problem and it still exists. My phone is constantly telling me to update the phone (even though now a 4.0.4 "upgrade" would infact me a downgrade). This is driving me crazy...is there any way to stop this from happening?
Click to expand...
Click to collapse
Let me guess, you are running a custom ROM?
This will fix it: edit the line that starts with ro.build.fingerprint in your build.prop file to read like this:
ro.build.fingerprint=google/takju/maguro:4.1/JRN84D/392829:user/release-keys
I wish I could say I was talented enough to create my own ROM, however I'm just flashing ROMS from the forums here.
The Jelly Bean ROM i just flashed is the one located HERE
DKNUCKLES said:
I wish I could say I was talented enough to create my own ROM, however I'm just flashing ROMS from the forums here.
The Jelly Bean ROM i just flashed is the one located HERE
Click to expand...
Click to collapse
By custom, I meant NON-stock, like that one. Do what I posted above.
No love I'm afraid. That's actually what's already in the ro.build.fingerprint...
Any other suggestions?
DKNUCKLES said:
No love I'm afraid. That's actually what's already in the ro.build.fingerprint...
Any other suggestions?
Click to expand...
Click to collapse
Hmmm. Strange. That used to fix it for older versions. Anyway, maybe re-flash Jelly Bean, and use the stock ROM this time: http://tinyurl.com/JRN84D
I cleared the data in the Google Services Framework, restarted the phone and the notification has not popped up since.
I'm headed to NYC tonight and will have little access to the internet but I will report back.
Thank you for your help efrant!
Clearing the data from the Google Services Framework seems to have done the trick. Almost a week and no prompts to install an update.
For a while now I've been getting system updates but they've always failed during application (ie the red exclamation icon after reboot). This wasn't bothering me too much but now that Sprint has finally decided to roll out Jellybean I'm trying to figure out what the issue is. I've never rooted the phone (although I nearly did yesterday before hearing the news re:Sprint). I've gone so far as backing up everything on my phone and doing a factory reset and I still have this happening. Does anyone have any possible idea what might be wrong or what I could check to see what is wrong, like an error log or something similar. The build is IMM76D if that helps.
becktionary said:
For a while now I've been getting system updates but they've always failed during application (ie the red exclamation icon after reboot). This wasn't bothering me too much but now that Sprint has finally decided to roll out Jellybean I'm trying to figure out what the issue is. I've never rooted the phone (although I nearly did yesterday before hearing the news re:Sprint). I've gone so far as backing up everything on my phone and doing a factory reset and I still have this happening. Does anyone have any possible idea what might be wrong or what I could check to see what is wrong, like an error log or something similar. The build is IMM76D if that helps.
Click to expand...
Click to collapse
That is the stock recovery image. You are probably seeing it because you have something that is not stock (i.e., something that you change), whether it be a radio, a kernel, or a system file. If you remember what you change, change it back. Otherwise flash everything back to stock.
efrant said:
That is the stock recovery image. You are probably seeing it because you have something that is not stock (i.e., something that you change), whether it be a radio, a kernel, or a system file. If you remember what you change, change it back. Otherwise flash everything back to stock.
Click to expand...
Click to collapse
Ok, since then I had rooted my phone but decided to reverse it. I've since used WugFresh's Nexus Root Toolkit to flash back to stock, unroot and lock the phone.
Even after doing all of that I'm still getting the same stock recovery image. I haven't done anything since flashing it back to the stock image aside from setting up my google account on it.
Even when returning to stock you likely didn't flash all parts of the image, so you're missing something like the proper bootloader, radio, or recovery for that specific build. This is another great example of why toolkits are a bad idea. You have no idea what you've flashed.
op, go and ask your question in that toolkit thread
Sent from my i9250
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
I really hope someone helps with this, because oddly enough, I just had the exact same problem!
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I suggest you should go check out the Sprint Samsung s3 forum under the Android development section the check out for the stock rom, try using the 1 click Odin or check out in there the proper way to restore your device, then continue reading the forums to check out when or how is the proper way to apply that update it could be that its bugged or that your device lost some permissions so best way to solve it should be to restore it to its original state.
Sent from my SPH-D710 using xda app-developers app
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
You cant install an OTA update unless you have the official stock rom and the stock recovery because custom recoveries will install it and I believe im correct when I say that to flash an OTA update you have to odin to stock and then do the update.
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Most custom touchwiz roms will allow updates, but you have to flash stick recovery 1st. The 157mb update is for mb1. You could just change your build prop to get the notification nag to go away
sent from my GS3 using XDA app
If you're on stock rooted with no apps removed, do what I did. Plug phone into odin, flash stock recovery, update, flash custom after update done, re root, done.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
tazfanatic said:
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
Click to expand...
Click to collapse
Yup, if you just wanna make it go away, go into your build.prop and change all instances of "LJ7" (or "MA6" ) to "MB1"
CNexus said:
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Click to expand...
Click to collapse
That's all I do. Once an update comes out I just head over to Freezas page and update my rom. Stock look and feel with the root in place.
Sent from my stock rooted Galaxy S3
Any update on this? I have the same issue.
Thanks
coderaja said:
Any update on this? I have the same issue.
Thanks
Click to expand...
Click to collapse
There's several ways to fix this issue posted on the other page. Use one of them.
D
So my OTA installed successfully to 4.3 I also managed to root it perfectly fine and reboot with everything working correctly.
However for some reason I decided to fiddle with system/app mover, moved a few samsong and AT&T application to be user ones instead of system and rebooted. The phone starts booting and freezes in the middle displaying the ATT logo, I tried factory resetting which didn't help.
Is there a way for me to re-install 4.3 or whatever else that works. I don't think this is considered 'bricking' and I'm hesitent about using odin with 4.0.4 ROMs since I heard 'downgrading' will brick the phone.
morps said:
So my OTA installed successfully to 4.3 I also managed to root it perfectly fine and reboot with everything working correctly.
However for some reason I decided to fiddle with system/app mover, moved a few samsong and AT&T application to be user ones instead of system and rebooted. The phone starts booting and freezes in the middle displaying the ATT logo, I tried factory resetting which didn't help.
Is there a way for me to re-install 4.3 or whatever else that works. I don't think this is considered 'bricking' and I'm hesitent about using odin with 4.0.4 ROMs since I heard 'downgrading' will brick the phone.
Click to expand...
Click to collapse
If you have custom recovery you can flash another 4.3 rom.
are you sure it is stuck 4.3 takes a long time to boot up after a factory reset (mine took about 4 minutes??? after I installed 4.3 the first time and about 3 the second time I installed it.)
Thanks, I flashed the ROM from http://forum.xda-developers.com/showthread.php?t=2540998 which seems to have worked. I'm wondering if there is anyway to go to stock (ie. the original AT&T one, but apparently it's not available anywhere just as an OTA).
morps said:
Thanks, I flashed the ROM from http://forum.xda-developers.com/showthread.php?t=2540998 which seems to have worked. I'm wondering if there is anyway to go to stock (ie. the original AT&T one, but apparently it's not available anywhere just as an OTA).
Click to expand...
Click to collapse
That's the same one I have I like it. That's as close to stock you're going to get.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Ok, so I am not to sure exactley what I did. I accidental hit unroot in CWM. I have a recent titanium backup, but i suppose that will do me no good. I lost superuser permission to operate Titanium anyway. Also CMW as the app is useless to me now. I can boot into it using the volume down, home power option, but i can not get to anything there to restore it.
Do i need to re-root, or what direction should I be going in? All I am looking for is someone to point me in the proper direction, I feel horrible asking this here, as I normally know what I am doing.
Thanks for your help.
I am back to stock. Not rooted or anything, so there is one problem solved. I would like to OTA update, but it is saying i am up to date, and i am pretty sure 4.1.2 is not up to date. Oh well, im half way there.... i think...
sully42 said:
I am back to stock. Not rooted or anything, so there is one problem solved. I would like to OTA update, but it is saying i am up to date, and i am pretty sure 4.1.2 is not up to date. Oh well, im half way there.... i think...
Click to expand...
Click to collapse
You have options, OTA to 4.3 (just advance time/date 24 hours or whatever time it says to check again) You will have a locked bootloader and Knox *****ing at you if you install root.
Or you can flash this through ODIN or CWM, You get root and 4.3
http://forum.xda-developers.com/showthread.php?t=2589891
dicksteele said:
You have options, OTA to 4.3 (just advance time/date 24 hours or whatever time it says to check again) You will have a locked bootloader and Knox *****ing at you if you install root.
Or you can flash this through ODIN or CWM, You get root and 4.3
http://forum.xda-developers.com/showthread.php?t=2589891
Click to expand...
Click to collapse
Thanks! I got it to OTA to 4.3,I did not think about changing the clock, I ended up booting to CWM and factory resetting, then rebooted and it poped up with in 30 seconds that there was a software update.
I think I will flash that threw oden later. I was mostly freaking out because my phone was stuck between rooted, and not rooted. All sorts of apps where tweeking out on me. 4.3 is nice, but way to much junk installed by ATT.
cell carriers are the worst kind of people.
sully42 said:
Thanks! I got it to OTA to 4.3,I did not think about changing the clock, I ended up booting to CWM and factory resetting, then rebooted and it poped up with in 30 seconds that there was a software update.
I think I will flash that threw oden later. I was mostly freaking out because my phone was stuck between rooted, and not rooted. All sorts of apps where tweeking out on me. 4.3 is nice, but way to much junk installed by ATT.
cell carriers are the worst kind of people.
Click to expand...
Click to collapse
No worries. This just came out yesterday.
http://forum.xda-developers.com/showthread.php?t=2659569
A little of the crap removed. I'm running it, pretty smooth.