I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
648charlie said:
I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
Click to expand...
Click to collapse
Can you tell us what steps you used to try to root?
What was the status of your phone before you tried to root?
Were you on the most recent update from Verizon? (It was over a year ago.)
I have signed into kies and it says
dawgdoc said:
Can you tell us what steps you used to try to root?
What was the status of your phone before you tried to root?
Were you on the most recent update from Verizon? (It was over a year ago.)
Click to expand...
Click to collapse
s3 was working when I switched to a note 4. I took the verizon service off the phone and it sat in the garage for about a year set at 4.42 installed king root.
when I reset the phone it says king root in shell
pda ne1 phone ne1 csc ne1 vzw both current and latest firm ware I can get a screen with time and be able to go into settings
does the fact that I have no service affect the phone going to the verizon screen?
648charlie said:
s3 was working when I switched to a note 4. I took the verizon service off the phone and it sat in the garage for about a year set at 4.42 installed king root.
when I reset the phone it says king root in shell
pda ne1 phone ne1 csc ne1 vzw both current and latest firm ware I can get a screen with time and be able to go into settings
does the fact that I have no service affect the phone going to the verizon screen?
Click to expand...
Click to collapse
Not having service shouldn't affect it in that way.
I bought a used i535 back in May that was on the stock 4.4.2 rom from a couple that had done no mods to the phone. It had been unused for several months. After receiving it I wiped it and did a factory reset. Following that I rooted with TowelRoot, installed BusyBox, and then SafeStrap. At that point I installed SuperLiteROM and followed that with XPosed. I never put the phone into service but had no issues with installing apps, xposed modules, etc. That is there were no issues until I lent it to a coworker.
I am not familiar with King Root and if it can cause problems. Likewise, I am not familiar with KingoRoot.
I sounds like you are getting to a homescreen since you are seeing a clock widget and can open settings. It could be that your launcher has been compromised. If that is true, the simplest fix may be to reflash the stock NE1 rom. Doing so most likely will cause you to loose root.
@ShapesBlue do you have any other ideas on this?
dawgdoc said:
Not having service shouldn't affect it in that way.
I bought a used i535 back in May that was on the stock 4.4.2 rom from a couple that had done no mods to the phone. It had been unused for several months. After receiving it I wiped it and did a factory reset. Following that I rooted with TowelRoot, installed BusyBox, and then SafeStrap. At that point I installed SuperLiteROM and followed that with XPosed. I never put the phone into service but had no issues with installing apps, xposed modules, etc. That is there were no issues until I lent it to a coworker.
I am not familiar with King Root and if it can cause problems. Likewise, I am not familiar with KingoRoot.
I sounds like you are getting to a homescreen since you are seeing a clock widget and can open settings. It could be that your launcher has been compromised. If that is true, the simplest fix may be to reflash the stock NE1 rom. Doing so most likely will cause you to loose root.
@ShapesBlue do you have any other ideas on this?
Click to expand...
Click to collapse
Yeah, I would say to restore stock firmware but as you know, after 4.3 you have a locked bootloader, this includes the 4.4.2 that you have now, if you flash the stock firmware make sure you flash exactly what you have now or one of the newer stock firmwares, do not try anything older than your 4.4.2, that would be a downgrade and the locked bootloader can't be downgraded or the device will perma-brick. Flashing stock and doing root over again is the simplest solution compared to troubleshooting this issue, more could get messed up if you try too many things.
648charlie said:
I tried to root and it failed now I am trying to get My s3 verison 535 back to original. Unfortunately I no longer have my verizon service for this phone. I have tried to reset it but part way thru the set up it says set up failed.
Then It returns back to the verizon red screen
Any Ideas
thanks John
Click to expand...
Click to collapse
Sent from my SCH-I535 using Tapatalk
got launcher from google apps
Droidriven said:
Yeah, I would say to restore stock firmware but as you know, after 4.3 you have a locked bootloader, this includes the 4.4.2 that you have now, if you flash the stock firmware make sure you flash exactly what you have now or one of the newer stock firmwares, do not try anything older than your 4.4.2, that would be a downgrade and the locked bootloader can't be downgraded or the device will perma-brick. Flashing stock and doing root over again is the simplest solution compared to troubleshooting this issue, more could get messed up if you try too many things.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Loaded launcher from google apps, talked to verizon and they put s3 inservice for 5 minutes and I made a call.
all is well
thank you thank you
John
Related
Hi, my family has multiple Verizon Galaxy SIIIs that were supposed to receive OTA updates about a week ago, but for whatever reason, as I cannot pinpoint the exact cause, none of them will install the update.
Each phone has:
Been rooted, by means of flashing a custom stock ROM through Odin
Had numerous stock applications frozen with Titanium, but we've tried unfreezing all of them prior to trying again with no effect
So I'm assuming it's that the phone's rooted. Is there any way to apply the update manually without unlocking the bootloader (ie. using the stock recovery or Odin to flash the update) and still have the possibility of keeping root?
Yes, the entire updated rom's are available in the development section. The latest being the vrlhd.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
AvataroftheSun said:
Hi, my family has multiple Verizon Galaxy SIIIs that were supposed to receive OTA updates about a week ago, but for whatever reason, as I cannot pinpoint the exact cause, none of them will install the update.
Each phone has:
Been rooted, by means of flashing a custom stock ROM through Odin
Had numerous stock applications frozen with Titanium, but we've tried unfreezing all of them prior to trying again with no effect
So I'm assuming it's that the phone's rooted. Is there any way to apply the update manually without unlocking the bootloader (ie. using the stock recovery or Odin to flash the update) and still have the possibility of keeping root?
Click to expand...
Click to collapse
I had to Odin back to stock and go get a new SIM card from Verizon... Got the OTA instantly after the new sim was put in... It's a known issue
Sent from my SCH-I535 using xda app-developers app
annoyingduck said:
Yes, the entire updated rom's are available in the development section. The latest being the vrlhd.
Click to expand...
Click to collapse
Mm, checked those out, and scrosler says that the bootloader needs to be unlocked, and doesn't provide any other information on how to flash it properly (Odin vs. custom recovery). Though if it's stock, it shouldn't matter...
I odin'd back to root66 and it took the update as soon as i checked for it. (and I dont even live in Verizon coverage)
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
the files that you use to odin with are a different extension (.tar) than what you flash with (.rar)...so you can only use cwm/twrp to use that rooted image. I recommend using odin to get back to stock, then using the root one click method that was recently stickied...that will get you up in running and able to use roms quickly
Yes its possible but first try to install a custom recovery. Download goomanager and then install open recovery script from the menu options. Then you should be able to boot into twrp and flash a new rom
Sent from my XT912 using xda app-developers app
eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
If you are Verizon Stock rooted and have SU and busybox installed without disabling updates, that will occur whenever Verizon rolls out an OTA. if you want the update, ODIN back to stock and take the updates before rooting. If you don;t want updates then find the thread on disable Verizon OTA and that will stop the update request.
I'm currently on 4.0.4 (Canadian version) N8010 and I want to update to 4.1.2 (canadian? not sure if it really makes a difference). I get the notification for the update, but when I select it, it fails, and it also fails with Kies.
When I first got the note I opted for the exynos exploit to root my tablet. I was under the impression that if I disabled root from the app my status would revert back to "non-custom". I've uninstalled exynosabuse and busybox (i think supersu uninstalled with the root disabled) and I've restarted multiple times and waited a few hours. No change. I think I'll try to re-enable root and restore some apps that I froze with titanium backup to see if it reverts back.
The other option I guess would be to get the Canadian rom and flash via Oden. although I think that would wipe by note, which i would like to avoid. I found some links to the canadian rom, but they're down.
Thanks for the help/advice.
Njord0 said:
I'm currently on 4.0.4 (Canadian version) N8010 and I want to update to 4.1.2 (canadian? not sure if it really makes a difference). I get the notification for the update, but when I select it, it fails, and it also fails with Kies.
When I first got the note I opted for the exynos exploit to root my tablet. I was under the impression that if I disabled root from the app my status would revert back to "non-custom". I've uninstalled exynosabuse and busybox (i think supersu uninstalled with the root disabled) and I've restarted multiple times and waited a few hours. No change. I think I'll try to re-enable root and restore some apps that I froze with titanium backup to see if it reverts back.
The other option I guess would be to get the Canadian rom and flash via Oden. although I think that would wipe by note, which i would like to avoid. I found some links to the canadian rom, but they're down.
Thanks for the help/advice.
Click to expand...
Click to collapse
Did you install a custom recovery or do you still have stock recovery installed and can you tell us your ROM's build number.
.
kkretch said:
Did you install a custom recovery or do you still have stock recovery installed and can you tell us your ROM's build number.
.
Click to expand...
Click to collapse
I still have the stock rom, I haven't installed anything custom, just use the exploit for the root access.
Build number: IMM76D.N8010WALG4
Njord0 said:
I still have the stock rom, I haven't installed anything custom, just use the exploit for the root access.
Build number: IMM76D.N8010WALG4
Click to expand...
Click to collapse
Without a stock 4.1.2 firmware for your device it looks like you are going to have to do a factory reset to use Kies.
I think your options are limited..........
Have you considered using a firmware from another country?
You know there is a backup program called Helium that does not need root, you may want to consider using it to backup all of your data and then do a factory reset.
I don't know if I have helped you any............
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
mortified21 said:
Hey guys,
I just got my phone and it updated to 4.4 pretty much out of the box. I still wanted to root so I used a method I found on here (will find if necessary) which is supposed to not trip the KNOX by putting the phone into "Custom Mode." Everything went fine until I tried to use ROM Manager to install CM.
When I boot I get the message "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." I've tried reflashing using Odin, clearing the cache and factory resets, but I get the same error every time.
I'm currently downloading another stock ROM which might work, but I wanted to see if anyone else has had this problem?
Thank you!
Click to expand...
Click to collapse
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
If you have 4.3 stock firmware you can root and that's it, no custom recovery, no custom rom, kernel, nothing, and just a heads up there are like 10 threads where people don't read and have done what you have, you need to flash the Odin 4.3 image for you phone to work again, never take an ota, enjoy your locked down device now
Sent from my SCH-I535 using XDA Premium 4 mobile app
SlimSnoopOS said:
You are permanently stuck on the TW 4.3 OTA because the bootloader is signed with special keys that prevents:
-installing a custom recovery
-flashing custom roms/kernels
-downgrading your software below 4.3
If you can boot into download mode, do this 4.3 soft brick method.
With TW 4.3 OTA, all you can do is root using a tool called: Saferoot.
Click to expand...
Click to collapse
Worked perfectly! Thank you so much!
mortified21 said:
Worked perfectly! Thank you so much!
Click to expand...
Click to collapse
My pleasure but all the thanks is owed to ThePagel, make sure to post your success in his thread. The more people that report their success with that method, then the less fear someone else may have in using that should they suffer the same experiences. :victory::good::good:
If you need any updates on the state of TW 4.3 then keep this discussion thread bookmarked.
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
AURMEND said:
I did the same thing today. The 4.3 update installed by itself!!! So i rooted it using Saferoot,
i installed rom manager, clicked the Install rom from sd card and i got that message. it will repeat that message and it wont boot. So i went into Odin mode and hit the volume down button to restart it. And after that it booted normally.
So basically i am stuck with 4.3? and is there 4.4 out for our phones yet?
also forgot to mention, it says my OS is custom when i first realized it updated.
Click to expand...
Click to collapse
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
buhohitr said:
Once you successfully updated with 4.3, you stuck with 4.3, there is no going back or flash anything and 4.3 is the latest factory rom for now. There's no 4.4 yet for our phone. There is custom 4.4 but only for people who didn't take the 4.3 update. Since they still have unlocked bootloader so they could load any custom rom.
Click to expand...
Click to collapse
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
AURMEND said:
Dang this sucks. I have no idea how it installed automatically then. I was listening to music the whole time. And I was trying to get a custom 4.4 after the update...
Click to expand...
Click to collapse
Yep! sucks big time!!
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.