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.
I haven't really been into screwing with my phone but since they finally fixed that bad update, I might try to at least get new system software.
I am still on VRBLK3, I am rooted and pretty sure I unlocked the bootloader last year but can't remember. However when I try to get into the recovery, I get the Samsung logo and a bit of text at the top and then it just shuts down again. So I'm guessing in this case a full ODIN of a new ROM is going to be necessary or can I have a go with just installing a recovery and trying to update?
And since I am back on VRBLK3, do I have to do incremental updates or can I just go with this latest one or a new ROM?
Thanks!
You have use odin back to stock. You don't have to doil incremental updates as all stock firmware are available online.
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?
so i basically updated my phone through kies, (erased everything thru twrp before), but i cant get back to official status, whats going on, kies should have done it, im trying to see if my phone can pick up the official nkd firmware via ota, but it says i did something to my phone, but i don't have root, have stock everything so idk whats going on.
Hey all, need some advice... I recently rooted my phone and found it wasn't for me (way too many apps stopped working). Because of this I tried to unroot the phone, but got stuck in a boot loop and had to recover from scratch.
Anyways, I'm running stock now and the system is back to being rooted. Problem is, I can't seem to update the phone. I'm not getting an error message either. Both Smart Switch and the phone simply say I'm up to date, but I'm on APB7 when I should be able to get APD3.
Is there anyway to fix this? Will I need to factory reset the phone? I'm not sure how to get the phone to recognize an update now.
Same here. I rooted my phone, installed TWRP but battery drain and apps not working properly made me go back to stock. Now I cant get any updates. I flashed APEQ fw yesterday dated June 8 but still dont get the June 17 updates.
I used Smart Switch to do an Emergency Reinstall of the firmware. Had to start over from scratch with my phone... It installed the lastest firmware though.
Been researching as much as I can online and it seems the consensus is simply unrooting the phone does nothing. You have to factory reboot. Tripping Knox won't stop you from getting updates but an unrooted phone that wasn't factory reset still won't get updates. Fun times. Last time I root my phone... Things aren't the same since I last rooted in Android 4.0. Now too many apps and updates etc. check for root and stop working if they detect it.
Luuthian said:
Hey all, need some advice... I recently rooted my phone and found it wasn't for me (way too many apps stopped working). Because of this I tried to unroot the phone, but got stuck in a boot loop and had to recover from scratch.
Anyways, I'm running stock now and the system is back to being rooted. Problem is, I can't seem to update the phone. I'm not getting an error message either. Both Smart Switch and the phone simply say I'm up to date, but I'm on APB7 when I should be able to get APD3.
Is there anyway to fix this? Will I need to factory reset the phone? I'm not sure how to get the phone to recognize an update now.
Click to expand...
Click to collapse
Did you use Odin to flash back to stock?
malek777 said:
Did you use Odin to flash back to stock?
Click to expand...
Click to collapse
I used the Emergency Recovery function of Smart Switch which, from my understanding, is basically the same thing. I know how to use ODIN but it seemed a better idea to go with the official solution. Guess I'll find out if it worked once the June update is available in Canada.