Whenever I try to do the OTA update for Jelly Bean, I get an error message saying that Service is Unvailable, even if I have full reception or Wifi connection. While I realize I can easily update the software using open1your1eyes0 thread, http://forum.xda-developers.com/showthread.php?t=1974114, I'd rather just keep the phone stock for the time being.
Is there a way to overcome this error message? Additionally, for some reason Verizon thinks I'm still using my nexus device and won't reupdate my phone to S3, even though I switched Sims.
I have had the same problem on other phones when i was trying to update. The only solution that i have found to work is a Factory Reset. If you dont want to do that however you can always flash the STOCK update through ODIN and you DO NOT have to root your phone to install the STOCK image. The details are in the link that you posted. Just download #8 it has no root and the stock recovery image.
I activated a new sim and that seemed to do the trick. I'm tempted to root the phone eventually. I've just noticed I've had some GPS and 4G data connection issues after I root my device.
Related
When my G2x was stock unrooted it always failed authentication when checking for an OTA update. I had always assumed this was because I'd done a desktop install of the LG Gingerbread update. After I rooted my phone I tried installing the stock Froyo ROM to test my theory and it still failed.
No problem, I thought, because I'm gonna install CM7. Well now I'm running CM7 and when I go to the section to register the phone for push update notifications I get the message "Registration failed."
Are these two issues connected and what might the problem be?
Once you're rooted, I don't think you can get OTA... when I had my rooted Mytouch 3g I was told to not accept ota or phone might mess up. Plus CM7 is better than stock
kompheak said:
Once you're rooted, I don't think you can get OTA... when I had my rooted Mytouch 3g I was told to not accept ota or phone might mess up. Plus CM7 is better than stock
Click to expand...
Click to collapse
The failed authentication to connect to T-mo's servers was before I rooted. I'm not so concerned about that as I am about the phone failing to register for push notifications of CM updates. The only reason I mentioned the authentication error with T-mo is because I ws wondering if they might be related.
Hi,
I have Samsung Tab 2 7" P3100
Originally had 4.0.4 which worked great.
But got OTA update n upgraded to 4.1.1
& Now it started giving me trouble, Wifi Connection is very unstable.
Connected to Wifi Network keeps popping up every 5 mins.
I cant even install things properly without worrying of it will fail or success.
so i rooted the device and reset the whole thing (Rooted to make a Titatnium Backup n all)
Problem still persists, Still the Wifi Trouble.
Without a Proper Wifi its not even worth having a Tablet.
So my Question is: Can i Push a 4.1.1 ROM from Sammobile on my current 4.1.1 ??
or should i just downgrade it to 4.0.4 & than do a upgrade via Kies rather than OTA update.
( I am thinking something in OTA messed up, so a proper ROM from sammobile might help)
nosdam7 said:
Hi,
I have Samsung Tab 2 7" P3100
Originally had 4.0.4 which worked great.
But got OTA update n upgraded to 4.1.1
& Now it started giving me trouble, Wifi Connection is very unstable.
Connected to Wifi Network keeps popping up every 5 mins.
I cant even install things properly without worrying of it will fail or success.
so i rooted the device and reset the whole thing (Rooted to make a Titatnium Backup n all)
Problem still persists, Still the Wifi Trouble.
Without a Proper Wifi its not even worth having a Tablet.
So my Question is: Can i Push a 4.1.1 ROM from Sammobile on my current 4.1.1 ??
or should i just downgrade it to 4.0.4 & than do a upgrade via Kies rather than OTA update.
( I am thinking something in OTA messed up, so a proper ROM from sammobile might help)
Click to expand...
Click to collapse
Yes, you can trying to download them from sammobile.com and start to installing from odin. Make sure you have backup for your ICS 4.0.4 before replace with JB 4.1.1
Good luck..
rom
what is the best rom?
Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
It all started I guess when I had my phone on CM 10.2 (stable) when the signal would NEVER go past 3x. I thought that was just some error on the phone. The way I flashed the CM 10.2 was some bullcrap because I wasn't getting a certain instruction right where SuperSU/User was playing some Whack-A-Mole game where it would pop in and pop out. Because of all this bullcrap I didn't even think to use EZ Unlock to unlock the bootloader, although I think I didn't see it in the Play Store at the time and some of the Youtube videos I was watching didn't mention it. Eventually all was well though, and although 3x was slow looking back, the ROM was really stable with some minor crashing.
Earlier this past week though, I was tired and clicked away on an update to CM 10.2.1 and then another Cyanogenmod update pops up to the CM 11 snapshot. Just trying to get notifications to go away and I dirty flashed it to CM 11 by the Cyanogenmod updater and got an "Update 7" error when installing it, so I just went back into my downloads folder and re-flashed it to 10.2.1. Being in CM 10.2.1, I wasn't getting anything in terms of reception and later found out the problem was that the SIM wasn't checked under mobile networks in the settings tab, but this had resulted in my phone not getting mobile data past 1x.
Now fast forward to today and I update my CWM because of the "Update 7" error and re-flashed it to CM 11, only to find that there were times that the bars would go up to 5 and the LTE would flair up, but then it would crash down; I messed with both the Global LTE (there was a little more successes in this one in terms of the number of time LTE and better bars popped up, but didn't use it because I was scared to see if I was gonna get charged with Data Roaming) and Regular CDMA LTE (kept having 1x and bars would go up and down...), which is where it's at right now.
Okay, so then I re-flashed it to Verizon's 4.3 (finally Verizon is giving us i535 some love! right?) in an attempt to clean flash it but I had put in the VRALEC bootchain in first and softbricked me out of the recovery partition where it gave me that "Take back to Verizon store" yellow triangle warning and it was stuck for a long time at the Verizon logo until I odin'd a stock recovery 6mb tar and w00t, my phone is back, BUT I still have the same figity signals as the CM 11 and all. At this point though, my triangle count is at 4. Also in this state, my Google Play was acting hell-ish (I also got this in CM 11 too, but didn't care too much for it before); I kept getting this "Error retrieving... [RPC:S-3]" when trying to install apps and I did force stop and clear the info, but it wouldn't work. I've also gotten the RPC:S-7 too. Right now, after my mobile and signal bars being finicky as hell, it's sort of stabilized for 4 minutes (longest it's been ) to 4/5 bars with 4G LTE, but I don't know how long this will stay for.
So being very descriptive and maybe loosing some of you, here's the questions for the tl;dr for the questions.
- How can I get this reception to stabilize? It's never been this bad when my phone was stock around here. (now done with this long blob, the 1x has appeared again!)
- Any other ways on getting that RPC:S-3/S-7 in Google Play Store to go away?
- I'm planning on going to CM 11, once it gets a stable release. Kitkats are too irresistible, pun intended... Can someone please set the stone in how I should go about rooting and unlocking the bootloader? Some of the guides I used months ago were a little outdated, and I'm concerned that the old practices are over with.
Rezey said:
Good evening guys!
Alright so I have this huge mess on my i535 right now where the signal for CDMA (bars) and mobile internet is just total crap.
that the old practices are over with.
Click to expand...
Click to collapse
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
buhohitr said:
As I understood, you flash a stock 4.3 rom? Stock 4.3 rom locked the bootloader so no more CM11 or any custom rom for you unless you need to flash safestrap, but after this you only can flash TW custom rom. OK, now back to your issue. Since you already on factory stock rom, I would do a factory reset, the Odin a full factory 4.3 stock rom again with a PIT file and I think you should be back to normal unless CM10 is really messup your efs (a few people have this issue when flashing CM rom).
Click to expand...
Click to collapse
Hey, thanks for the reply!
A little update; last night I used SUA.exe with Kies drivers which re-flashed it with the factory Verizon's 4.3 and factory reset it, but now my phone will not get any sort of internet bands up and it's stuck on voice roaming which lead me to put my phone on airplane mode so that hidden charges wouldn't sneak up on me. I've even set my Mobile Network options to CDMA-LTE-EVO, but it will not get off of it.
I was just about to go onto one of the other threads and just re-root my phone, until you had told me about the locked bootloader... I'll look more into the safestrap, but this is irritating.
As with the PIT file, do I have to Odin all the VRALEC and other (I've seen a couple of odin to stock and I know rooting requires this) bootchains, to PIT file, and then 4.3? I'm not sure how that step goes... And if it did mess up my efs, what's my next step? I mean I think the i535 might be under warranty, but I'm at 4 triangle counts and I can't get those away unless if I get root permission, but I feel like having a locked bootloader might restrict me from rooting my phone, but I can be just worrying too much...
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Rezey said:
I wanna also put another update that I did flash the phone with a 16gb pit (which my phone is) file I found on another thread, but it still did not do anything. When I did use the pit file I had some security error on my phone which was in ODIN mode the first time and ODIN just kind of stood there, so then I closed it out and did again, to find that the error popped up again, but I ODIN ran through another flash. I had re-partition checked too...
I did a Wipe2 because I couldn't get the Dalvik cache cleared through Samsung's recovery partition, so I'm probably gonna get my phone rooted in the next hour and put another update because with root I'm gonna at least triangle away my phone.
Click to expand...
Click to collapse
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
buhohitr said:
You still don't under stand 4.3 rom. Once you on it the way to go back to stock rom is using full stock 4.3 and pit file. No boot chain, no once click root etc...If you want to root, you need to use saferoot. Let see if you can get back to a normal 4.3 stock with locked boot loader first. Check out this link. http://forum.xda-developers.com/showthread.php?t=2586319 . Just follow it and see if you can get back to a normal phone and there is a link on that thread for you to use saferoot to root.
Click to expand...
Click to collapse
Actually I used the Verizon utility tool from that very thread to clean root back to 4.3 and had Google Play connection error, Voice-roaming only, and no mobile data whatsoever.
I also just did saferoot on my phone and triangle'd away all my counters but yet still nothing. Did I fry my sim card? And with voice roaming always on, won't this put charges on my bill?
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
dwcosby said:
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
Click to expand...
Click to collapse
there have been quite a few people with this same issue. i havent seen any direct fix.
if you are locked, i would suggest you wait it out, or wait for the sbf file to get leaked. there is a way to sideload it, but its risky being locked and no sbf to save you if a problem comes up.
if you are unlocked, there are directions in the General forum to sideload the ota. there is no risk if you are unlocked.
if you are locked, the only thing i would suggest to try is re-flashing the stock 9.30.1 with rsd and see if it will pull the update afterwards. there is no guarantee this will work, but your phone will be 100% clean stock after the flash and give you the best chance to grab the ota if available.
dwcosby said:
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
Click to expand...
Click to collapse
Did you download it and then said to apply it later? If so, are you rooted? If so, hook up your phone to your PC and adb shell into it. Type "su" and hit enter to go into superuser mode.
Navigate to the /cache directory and you should see the OTA .zip file sitting in there. Copy it to your external SD card and then you can load it manually via the recovery.
If you're not rooted, then you won't be able to navigate into the /cache directory. Or, if you didn't have it download when you got the notice (or couldn't download it), then it won't be there.
More update issues
My wife & son both have the HD. My wife checked for the update this morning, said it was ready and proceeded to download. Update did as it was supposed to and when it was done, she had KitKat and that's when things went a bit wonky.
If she has Bluetooth turned on, WiFi connection drops after a few minutes. She googled possible workarounds and none really worked. As long as she is not using BT, WiFi stays up
Has anyone else seen this behavior? She refuses to let me root it and install a custom ROM as I have done on my Samsung GS4 from VZW.
In the mean time, we've told our son not to take the update until
we know more about a possible fix.
zeb carter said:
My wife & son both have the HD. My wife checked for the update this morning, said it was ready and proceeded to download. Update did as it was supposed to and when it was done, she had KitKat and that's when things went a bit wonky.
If she has Bluetooth turned on, WiFi connection drops after a few minutes. She googled possible workarounds and none really worked. As long as she is not using BT, WiFi stays up
Has anyone else seen this behavior? She refuses to let me root it and install a custom ROM as I have done on my Samsung GS4 from VZW.
In the mean time, we've told our son not to take the update until
we know more about a possible fix.
Click to expand...
Click to collapse
Fix was just posted recently. do a factory reset. It sucks, but its the only option.
Factory REst doesn't solve 4.4.2 WIFI issue on Razor MAxx HD
TXKSSnapper said:
Fix was just posted recently. do a factory reset. It sucks, but its the only option.
Click to expand...
Click to collapse
Android V 4.1.2 worked flawlessly since Nov 1023 upgrade. Decided to upgrade to KitKat via OTH. Had WIFI connection issues right away ( inability to obtain IP or lost connection, etc.) This happened with Bluetooth ON or OFF, no difference. The Signal strength was much lower than when on the previous android version and subsequent indicated connection speed was at least 1/2 of what I was getting previously.
Worked with Verizon and Motorola tech support personnel and did multiple factory resets with no improvement.
Since I wanted a factory solution and had insurance on the phone, I ordered a replacement phone. Thankfully, the new phone had 4.1.2 and worked perfectly. WIFI issues are gone.
Conclusion, KitKat is not ready for prime time yet. WIFI bug needs to be worked out before I will upgrade again.
egutwillig said:
Android V 4.1.2 worked flawlessly since Nov 1023 upgrade. Decided to upgrade to KitKat via OTH. Had WIFI connection issues right away ( inability to obtain IP or lost connection, etc.) This happened with Bluetooth ON or OFF, no difference. The Signal strength was much lower than when on the previous android version and subsequent indicated connection speed was at least 1/2 of what I was getting previously.
Worked with Verizon and Motorola tech support personnel and did multiple factory resets with no improvement.
Since I wanted a factory solution and had insurance on the phone, I ordered a replacement phone. Thankfully, the new phone had 4.1.2 and worked perfectly. WIFI issues are gone.
Conclusion, KitKat is not ready for prime time yet. WIFI bug needs to be worked out before I will upgrade again.
Click to expand...
Click to collapse
That's a shame because for me, the FDR fixed the Wifi/Blue-tooth issue as it did for many others. Might have been a hardware issue (faulty radio, etc).
I was able to install the first of the two updates earlier for the 5.1.1 update on my Verizon Galaxy Note Pro 12.2. The second downloads, prompts for install, reboots and begins installing but errors out and reboots back into the OS home screen. The Verizon software update manager shows Failed software update error code 402. I have factory reset my tablet a couple of times and still same issue. I do not have my tablet rooted and no apps disabled.
I downloaded the latest available Samsung firmware md5 file, version VZW-P905VVRUANK1-20141205133604 and tried flashing using Odin 3.07 while in download mode. It starts and after a few seconds, Odin fails and on the tablet screen, I get the error, SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1. I have re-downloaded the firmware along with older versions and still same issue.
I was reading somewhere that my tablet could be "soft bricked" and that is why it will not install the second part of the OTA. As for the Odin/download mode error, I had read that the firmware version I am trying to flash in Odin has an older version of bootloader than my current and Samsung does not let you downgrade the bootloader. I may be wrong on both accounts, which is why I am seeing if anyone else has had this same issue or have any advice on what I can try.
Thanks in advance!
Same here. I unforze all the apps unintstalled SU and factory reset still no dice. VZW repair assistant wont work or smart switch. RA says device firmware not supported and smart switch says im up to date. The first part of the update installed no problem.
dansto82 said:
Same here. I unforze all the apps unintstalled SU and factory reset still no dice. VZW repair assistant wont work or smart switch. RA says device firmware not supported and smart switch says im up to date. The first part of the update installed no problem.
Click to expand...
Click to collapse
I had the exact same issues. Here's what I did with my 4.4.2 Rooted NP. I wiped it completely from within the device, then connected it and to the VZW software and let it do a "Repair". After that, my tablet also said that it was up to date, still on 4.4.2. I let it sit overnight and tried downloading the software update the next morning from the tablet, and it took both of them. My NP is rocking 5.1.1. now, much faster. No root but that's alright for now. By running the repair assistant from VZW, it also got rid of the Unlocked Symbol, which may have prevented the upgrade in the first place.
tdetroit said:
I had the exact same issues. Here's what I did with my 4.4.2 Rooted NP. I wiped it completely from within the device, then connected it and to the VZW software and let it do a "Repair". After that, my tablet also said that it was up to date, still on 4.4.2. I let it sit overnight and tried downloading the software update the next morning from the tablet, and it took both of them. My NP is rocking 5.1.1. now, much faster. No root but that's alright for now. By running the repair assistant from VZW, it also got rid of the Unlocked Symbol, which may have prevented the upgrade in the first place.
Click to expand...
Click to collapse
I was able to get mine to update using ODIN and the firmware file from sammoble. Factory reset on the tablet, factory reset in recovery and finally ODIN worked.
I was having the same problems as the OP listed. Once I decided to live without root and I would be okay with wiping the tablet, I performed exactly what dansto82 said he did and I'm now on 5.1.1.
Now hoping someone comes up with a way to root.
Hey, I have the p905v and it is running 4.4.4, I rooted it with towelroot and it was completely fine. I then tried putting twrp recovery on it the wrong way through flashify and now I don't have a recovery mode and can't update it to 5.1.1. Other than that the tablet runs perfectly fine. Is there a way I can fix it?
Sent from my SM-P905V using XDA Free mobile app