So I had just finished typing a response to a thread, here on xda, when my phone suddenly, all by itself, updated its prl. Only, when it was done, it had changed my prl BACK to 60664. Wired, huh?!
Same thing here. I was surfing the net and by itself the screen turned black and then said updating prl. It then changed from 65000 to 60654.
I just tried updating manually and it said "Your PRL has been updated and changes will be applied now" or whatever it says, but it stayed at 65000.
Hmmm..........
UPDATE:
Now my PRL is the 27392 and stuck on roaming...haha. Will try again...I just want 60664 back! LOL.
UPDATE #2:
Well it said it couldn't update, but then all of the sudden it goes back to 60664....well I got what I wanted...
Related
when fresh released his 2.0d i flashed over to that the first day it was released, now everything was working fine until last night. i woke up in the middle of the night and the phone was on roaming, didnt think anything of it and went back to sleep. i awoke this morning to the phone still on roaming so i took the batter off put it back in, and nothing still roaming. i removed the battery again, and again nothing still roaming. so i went into recovery did a data wipe, then rebooted nothing still roaming, wiped again and installed 2.0d again, and again nothing. i wiped the phone one last time, and flashed over damagedtrev, and again still roaming what are my options besides doing an ruu or is that pretty much my best option.
what does it show as your PRI and PRL? and are you with sprint? Might need to update PRI and PRL...
Mine did the same thing. I had the latest PRL and a PRI of 1.70 and I after about a week of running fine I could not get out of roaming. I went back to stock rom.
prl 27392
pri version it says flipz_01 but i was at 1.70.....
and yes im with sprint
wow ok i did a prl update. and it works now that was stupid thanks!
what happens wen u disable roaming?
yeah prl with sprint should be 60663 for anyone else who runs into this
This happened to me but when I did the PRL update nothing would change so I went and hit it with the RUU and used the kitchen to reroot and it worked the next time. I seriously also broke my phone because I did EVERYTHING to not have to set it back to factory. I did so many NAND and BART backups yet nada worked. NOw im running fresh again and loving it =]
this actually happened to me last night. Couldnt get it out, tried putting in airplane mode and the just stuck. so I restarted the phone, it booted up in airplane mode, turned off airplane mode, and all was good again
Joecrack305 said:
and yes im with sprint
wow ok i did a prl update. and it works now that was stupid thanks!
Click to expand...
Click to collapse
you should update your OP to state the solution.
I got my OTA update today, unfortunately something went wrong. I told it to install now, and the screen with the android and caution symbol showed up. After 10-15 minutes I hit the power button. I wasn't sure if I was supposed to wait for that screen to clear or if that screen wasn't a good sign. Well hitting power took me to recovery and said that there was an error with the install.
What did I do wrong. Was I just supposed to wait longer? I had previously rooted my phone with unrevoked, but was running the stock ROM, should I have unrooted it? Was it some other error?
Any insight into what happened so when the update comes back around I can do it right. Also is there anyway to get the OTA update back, or do I just have to wait patiently again.
jaredkent said:
I got my OTA update today, unfortunately something went wrong. I told it to install now, and the screen with the android and caution symbol showed up. After 10-15 minutes I hit the power button. I wasn't sure if I was supposed to wait for that screen to clear or if that screen wasn't a good sign. Well hitting power took me to recovery and said that there was an error with the install.
What did I do wrong. Was I just supposed to wait longer? I had previously rooted my phone with unrevoked, but was running the stock ROM, should I have unrooted it? Was it some other error?
Any insight into what happened so when the update comes back around I can do it right. Also is there anyway to get the OTA update back, or do I just have to wait patiently again.
Click to expand...
Click to collapse
You can not update a rooted phone. Go to my post on updating 2.2 made easy and you canupdate to 2.2 and reroot the phone. This is the OTA update.
I'm sort of in the same boat. I had rooted with unrevoked and was running cyanogenmod. I reverted back to stock (retaining root). I received the OTA notification, it downloaded and started installing, but showed the <!> with the android.
I thought...ok...I'll return back completely to stock (no root) and now I'm sitting waiting for another OTA notification.
It's been three days now, and still no notification. I've tried checking for updates so many times that I've lost count.
Does anyone know whether or not a failed update gets another OTA notification? -or- why the software shows up-to-date when it's still at 2.1u1?
Thanks
Either take it to Verizon for them to push it onto the phone or use one of the methods here.
fygar66 said:
I'm sort of in the same boat. I had rooted with unrevoked and was running cyanogenmod. I reverted back to stock (retaining root). I received the OTA notification, it downloaded and started installing, but showed the <!> with the android.
I thought...ok...I'll return back completely to stock (no root) and now I'm sitting waiting for another OTA notification.
It's been three days now, and still no notification. I've tried checking for updates so many times that I've lost count.
Does anyone know whether or not a failed update gets another OTA notification? -or- why the software shows up-to-date when it's still at 2.1u1?
Thanks
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/showthread.php?t=771178
I got the OTA notification letting me know an update was available. I ignored it because after reading about all the horror stories here on XDA I didn't want to have a bricked phone. So I went ahead and successfully applied the JI6 update manually using Mini Kies as described on Samsung's website. However, I still get the update notification like before! How do I get rid of it?
I couldn't find a way to get rid of it, so I just ran it and planned on having to redo the update via odin. It applied just fine however.
Interesting. One of my theories is that I could go ahead and apply the OTA but when it downloaded and did a check against the current version it would give up and move along. Do you think that's what happened? How long did the "update" take? Did you notice a new update.zip file or other telltale signs it attempted an update? Were you rooted?
Thanks!
Sean
Just go ahead and do the update, it will download it but won't actually update because it will determine you are on the latest version. Then the message won't appear anymore.
I updated mine via Odin, then click on Update on the OTA notification, and it did not do a full update (much too quick and did not lose root, like I did when I Odin it).
I was bugging out over the same question... but the notification seems to have gone away out of the blue (took between 4 and 5 days).
I may have accidentally missed the 'postpone' button and applied at some point... can't be totally sure... but it's possible the notification will eventually just go away...
anyway it's comforting to hear nothing bad happens =). Thanks for asking the question!
[EDIT]: The icon will deceptively disappear then reappear, apparently. Applied the update this time. It rebooted the phone and appears to have done no damage. Phone is still rooted with RyanZa's OCLF.
It appears mine went away mysteriously as well. I did say postpone 1 day, but it still had the notification in the top with a little clock next to it. When I woke up this morning, it was gone. Thanks for the answers everyone!
I went to do the OTA update today, but my update failed everytime, giving me a exclamation mark upon reboot. Now my phone is rooted and i had the webtop hack. Tried 3 times using OTA, and all failed, so i un did the webtop hack, got rid of the 3 apk files i added, then tried, still failed. Disabled outside apps, still failed. Then i downloaded the update to the sd card, tried that way, still failed.
So then i went to motos website and did the auto upgrade feature, and it took a long time for the program to install, but it finally connected to my phone, then at about 75% it failed, phone shut off, and then locked up. Tried reboot 3 times, never getting past splash screen. Took batt out, then let it sit. About 5 mins into att splash screen, i got a purple blinking light on my phone, then booted up and BAM!!! 2.3!!!
So even tho it said i failed, i have the new software!!! Lets hope it works ok.
Im on sort of the same boat here. I have 1.83 rooted through the GLADROOT after OTA update. i keep getting the exclamation mark upon reboot. After taking battery out and rebooting i still get the update failed message
Took an OTA update this AM in the US, but nothing seemed to change. Switched back to stock recovery, took update, downloaded, installed (no errors), rebooted, message said somethings about a Pre-Install APK, then nothing. Tablet info says I am now up to date, but nothing else seems to have changed.
I'm still on custom kernel (thor's), still on 3.1. I forget the GEN info, but I don't think that changed either.
Was this a pre-update update?
I got the update too.
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Ditto. Used stock recovery and unroot to get it to install. It's Gen 2.
Sent from my ADR6300 using XDA App
Same here, updated with no errors. Didn't lose root and it still says 3.1
With the update to 3.1 they sent out a smaller update a few days earlier. This one may be the same thing.
It's just a small update, about less than 20MB download. But I have no idea what's been changed.
GShyneDM said:
I got the update too.Same thing happaned to me
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Click to expand...
Click to collapse
Same thing happened to me...
System Update
System Update 4.010.13
(14.49MB).
A new system update is available for your device. A network connection is required to download and update your device. You may incur additional charges from your service provider. Thank you for not replacing me with the HP TouchPad.
Click to expand...
Click to collapse
i'm gonna hold off on installing this until i know more of what its all about...
I uploaded the zip in development, I don't think I'm gonna install either...
I also installed the 14MB update today. The tablet was rooted, but otherwise stock. After the update the tablet remains rooted. I have experienced no other issues.
Cheers,
A
I had the same experience as above. So far no issues.
This actually made me worried about the possibility of us to get an update to 3.2 on 8/25. Otherwise, they should just pass this incremental.