[Q] Rooted S3: How Do I get Verizon Update?? - Verizon Samsung Galaxy S III

I generally don't root my phones but I needed to increase the size of my SD cache so I rooted it.
I have read the threads on what to do if you have rooted and installed a new rom but I only did a portion of this process.
To root the phone, I followed the guide on this forum and completed the following:
Enabled USB Debugging and Unknown Sources (Phone)
Double-clicked "RootDebugfs" on PC with phone connected to computer using OEM USB cable. It ran to completion.
Installed - ez_unlock.apk and rom_manager.apk
At this point SuperUser was supposed to install but it didn't. I downloaded and installed Superuser, updated the Superuser binaries, and I was rooted. I confirmed this with Root Checker.
I never unlocked the phone with Ez-Unlocker
I never used Rom-Manager either.
I did install SD Speed Increase and increased the SD cache size from 128kb to 1024 kb.
Now there is a Verizon update that I should probably get. In the near future I will need to update to Jelly Bean.
What do I need to do to install these Verizon updates?

If you're rooted, stock recovery and not unlocked you can take any OTA but it will break root. But as far as I've seen you can root again.
If you're unlocked with custom recovery you need to flash back to full locked stock and stock recovery to accept OTA.
Sent from my SCH-I535 using xda app-developers app

As long as u have stock recovery then just take the ota and re root. If u don't have stock recovery the gym flash it with ez recovery app. That's how I updated my phone this morning
Sent from my SCH-I535 using xda premium

You could also just wait until someone creates a flashable zip and flash through CWM or TWRP.

Thank you for the replies.
I did not change anything regarding recovery. I only did whats indicated in my initial post.
If I do the OTA update will I just root again using the same process I did initially?
If so, is that just "double-click "RootDebugfs" on PC with phone connected to computer using OEM USB cable and run it to completion."?
I appreciate the support provided and appreciate all responses.

chinook9 said:
Thank you for the replies.
I did not change anything regarding recovery. I only did whats indicated in my initial post.
If I do the OTA update will I just root again using the same process I did initially?
If so, is that just "double-click "RootDebugfs" on PC with phone connected to computer using OEM USB cable and run it to completion."?
I appreciate the support provided and appreciate all responses.
Click to expand...
Click to collapse
Exactly. That's how I did it.
Sent from my SCH-I535 using xda premium

Just be aware that it's not unheard of for the root exploit to get blocked in the new OTA. It doesn't sound like that has happened here, but just FYI. That's part of why the common mantra is to just wait for someone to post a rooted version of the stock rom... or go with a custom rom (shout out to CleanRom here).

ponyboy82 said:
Just be aware that it's not unheard of for the root exploit to get blocked in the new OTA. It doesn't sound like that has happened here, but just FYI. That's part of why the common mantra is to just wait for someone to post a rooted version of the stock rom... or go with a custom rom (shout out to CleanRom here).
Click to expand...
Click to collapse
Yes you are correct about that. Luckily this didn't happen here. I also re locked the bootloader before I accepted the ota
Sent from my XT907 using xda app-developers app

musclehead84 said:
Yes you are correct about that. Luckily this didn't happen here. I also re locked the bootloader before I accepted the ota
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot for the information. I'm sure I can handle that. I'm considering not doing the update and then either waiting for the Verizon update to Jelly Bean or find a Jelly Bean ROM and take that route.
Thanks again.

Related

(SOLVED)[Q] how to tell if phone is already rooted.....

So I just picked up a skyrocket and I went to update OTA and it downloaded the update and when it went to restart to install the update the phone booted into clockwork. I wasnt able to find a thread for this specific device about it so I am asking here now. MOD if there is one please point me in the right direction. I did notice that there is no att bloatware on the device. Thanks.
Terminal editor, type su, press enter, see what happens.
Other clues: presence of Superuser app.
You have a custom recovery also which will need to be ODINed away.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yes, it does have superuser. As far as Terminal editor/ODINed i'll be honest I have no idea what you are talking about. First sammy device that I have had long enough to keep and want to keep. Use to HTC branded devices. But thank you I think it is rooted because of the superuser app.
Questions should be posted in Q&A. Moved.
Side note: I recommend you read a lot before you mess with it. Although this device seems to be very difficult to hardbrick misusing ODIN can lead to one.
Cheers
Go to market download root checker. Run it. If a super user prompt appears, that's a good sign.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
occupational_hazard said:
Go to market download root checker. Run it. If a super user prompt appears, that's a good sign.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Yes it does, superuser prompt comes up. I really would just rather have this back to completly stock running 2.3.6 until the 4.0 update rolls out. Not sure which is better. Rooted or unrooted????? Also am not sure if it has ODIN....I tried to boot into recovery to run ODIN3 and upgrade to 4.0.4 but when trying to power on into bootloader it just vibrates and will not boot until I release the volume up rocker. Other than curiosity the phone works and performs flawlessly. With superuser being installed and after installing titanium I am sure it is rooted. Still not sure what ODIN is (like I said used to the HTC branded phones and never cared about root) Thanks for all the information. Also I am not sure if I will be able to update to 4.0 when the OTA update rolls out, im not concerned about it being rooted or not (have not found a reason to have rooted yet). Anyone know if it can be updated OTA even though it has root?
didozer said:
Yes it does, superuser prompt comes up. I really would just rather have this back to completly stock running 2.3.6 until the 4.0 update rolls out. Not sure which is better. Rooted or unrooted????? Also am not sure if it has ODIN....I tried to boot into recovery to run ODIN3 and upgrade to 4.0.4 but when trying to power on into bootloader it just vibrates and will not boot until I release the volume up rocker. Other than curiosity the phone works and performs flawlessly. With superuser being installed and after installing titanium I am sure it is rooted. Still not sure what ODIN is (like I said used to the HTC branded phones and never cared about root) Thanks for all the information. Also I am not sure if I will be able to update to 4.0 when the OTA update rolls out, im not concerned about it being rooted or not (have not found a reason to have rooted yet). Anyone know if it can be updated OTA even though it has root?
Click to expand...
Click to collapse
Ota will not work with cwm...you need the stock recovery to do an ota......rooted I don't believe matters
Sent from my A500 using Tapatalk
StolenVW said:
Ota will not work with cwm...you need the stock recovery to do an ota......rooted I don't believe matters
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Can I download and install via sd card when the update is available. Only time I have used cwm is on my wifes old eris.
didozer said:
Can I download and install via sd card when the update is available. Only time I have used cwm is on my wifes old eris.
Click to expand...
Click to collapse
You need stock recovery. You need to read the stickies for a few days before you do anything.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Or just keep your phone as is, and wait when ics officially drops, just wait a day and someone will have a flashable zip of it for cwm. Might as well learn the perks of being rooted now and learn your way around the phone
Sent from my SAMSUNG-SGH-I727 using xda premium
Its all set now. Had to figure out the whole Odin thing. Ended up just redoing to software using my computer with a one click method. Can't remember who made it but it was from android central but mad by member on here. So thank you to that mamber Kenny something?? Any was have it flashed to 4.0.4 with no bugs. Everything works perfect and so far battery life is great. I must say that so far I am loving this phone. At first I wasn't sure about going away from my vivid but I can't find any reason to have any regrets. Thanks guys I appriciate your help and input.
can u put solved in ur title

[HOW TO] Root Atrix 2 running on Android GB(2.3.6) / ICS(4.0.4).

This is a method to root Atrix 2 running on Android GB(2.3.6) / ICS(4.0.4).​
EDIT: Last updated on 26th July 2012
WHAT WORKS: Everything including the setting inside superuser which was not working in superuser 3.1
If you use this MOD, then please click on thanks button below.
I have updated this method to latest version of superuser 3.1.3 and su binary 3.1.1 for better compatibility with various Apps.
By following the below instructions you will be rooted in no time. If you have any questions feel free to ask.
Features added in superuser 3.1.3:
1.Temp unroot
2. Ota survival
3. Outdated binary Notification
Method:
1. Enable "USB debugging" in your phone settings
2. Download the attachment Named "Motofail Root (superuser 3.1.3, su binary 3.1.1).zip" to root Android GB(2.3.6)
or Attachment named "ICS_root(superuser 3.1.3 and su binary 3.1.1) .zip" to root Android ICS (4.0.4).
3. Uninstall your old Motorola drivers from PC and install these new drivers.
4. Connect your phone with original USB cable that came with your phone.
5. To root Android GB(2.3.6) click on "Click-To-Root.bat" in the attachment folder or
To root Android ICS(4.0.4) click on "Root.bat" in the attachment folder
6.Your phone will reboot 2-3 times don't remove the USB cable during this process
NOTE: If you are unable to Root even after following the above MOD then perform a Factory restore after OTA update and retry.
Can i root the ics with this?
And my phone is rooted,but can i re-root it?
atrix2 said:
Can i root the ics with this?
And my phone is rooted,but can i re-root it?
Click to expand...
Click to collapse
YES
Thanks for the new update.......
Sent from my GT-S6102 using Tapatalk 2
Please be aware that other A2 users have had issues with Superuser versions higher than 3.0.3.
Sent from my SAMSUNG-SGH-I747 using xda premium
jimbridgman said:
Please be aware that other A2 users have had issues with Superuser versions higher than 3.0.3.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I haven't been having problems, but I always have been using the older motofail exploit then updating the binary from within the app.
lkrasner said:
I haven't been having problems, but I always have been using the older motofail exploit then updating the binary from within the app.
Click to expand...
Click to collapse
I had the issue the other day, on stock 2.3.6, I also saw that alterdlikeness had a similar issue as well. It was updating past the 3.03 on both su and Superuser.
I had issues on my A2 with 3.1 only, and it would just FC and not work. I had to remove and basically re-root, and leave it at 3.0.1.
jimbridgman said:
I had the issue the other day, on stock 2.3.6, I also saw that alterdlikeness had a similar issue as well. It was updating past the 3.03 on both su and Superuser.
I had issues on my A2 with 3.1 only, and it would just FC and not work. I had to remove and basically re-root, and leave it at 3.0.1.
Click to expand...
Click to collapse
hmm. good to know in case it ever happens to me. I guess I will know I am not alone.
I don't know about other variants but it is working on ATT ROM and I have also assisted the same method to one user in India on androidcentral who was on MEART ROM and it even worked for him.
prasannapmv said:
I don't know about other variants but it is working on ATT ROM and I have also assisted the same method to one user in India on androidcentral who was on MEART ROM and it even worked for him.
Click to expand...
Click to collapse
You missed the point I was trying to make to those wanting to update thier binaries for su and superuser.... not new root exploits.
I just want everyone to know there are issues with 3.1... however today an update to 3.1.2 today has been proven to work for those having the issues that both alteredlikness and I have seen with FCs.
Sent from my MB865 using xda premium
On Stock 2.3.6 rooted. The new updates to the Superuser app allow you to update the binary and use the settings now.
Updating thread for superuser 3.1.2 now..
This method works as stated today I was trying to update my su binary but update was not getting successful so I unrooted and rooted back using this method now everything is updated and running smoothly.
About to root my girlfriends phone to eventually install Lithium.
Coming from a AT&T Galaxy S2 so things are a bit different here.
Should I use this method or Jimmy's from this thread? http://forum.xda-developers.com/showthread.php?t=1327741
After that what steps do I need to take to get CWM installed so I can backup and install a new ROM?
Thanks thanks!
seanpr123 said:
About to root my girlfriends phone to eventually install Lithium.
Coming from a AT&T Galaxy S2 so things are a bit different here.
Should I use this method or Jimmy's from this thread? http://forum.xda-developers.com/showthread.php?t=1327741
After that what steps do I need to take to get CWM installed so I can backup and install a new ROM?
Thanks thanks!
Click to expand...
Click to collapse
I think they are the same, except this one has a more updated version of superuser - I think (someone correct me if I'm wrong).
I personally have always used the one in Jimmy's thread and just update the superuser app and binary (and, thanks for reminding me about that post - I never thanked him until today - and due credit to p3droid & JRW 28 of course).
As for CWM recovery, just install the A2 Bootstrap app after being rooted. Use the bootstrap app - top button, OK, bottom button to boot into recovery.
Good luck to you and your girl!
alteredlikeness said:
I think they are the same, except this one has a more updated version of superuser - I think (someone correct me if I'm wrong).
I personally have always used the one in Jimmy's thread and just update the superuser app and binary (and, thanks for reminding me about that post - I never thanked him until today - and due credit to p3droid & JRW 28 of course).
As for CWM recovery, just install the A2 Bootstrap app after being rooted. Use the bootstrap app - top button, OK, bottom button to boot into recovery.
Good luck to you and your girl!
Click to expand...
Click to collapse
Boom, was one setup ahead of you and just finished all that. Currently backing up in CWM and waiting for a painfully slow download of Lithium and we should be jammin. Can't believe how easy it all was actually.
So I assume since this CWM is loaded from an app there's no way to boot into recovery should a bootloop or rom failure happen? Is that something people worry about?
Thanks for your response bud.
seanpr123 said:
Boom, was one setup ahead of you and just finished all that. Currently backing up in CWM and waiting for a painfully slow download of Lithium and we should be jammin. Can't believe how easy it all was actually.
So I assume since this CWM is loaded from an app there's no way to boot into recovery should a bootloop or rom failure happen? Is that something people worry about?
Thanks for your response bud.
Click to expand...
Click to collapse
The cwm on boot feature may already be included in Lithium (edit: yes, it it included - just checked)... if not, you can set that up rather painlessly. And, yes, some of us do worry about that very much so..
Great thanks! worked perfectly for me on the ICS leak (non AT&T A2)
So I am on Atrix Xperia 4 rom and i was wondering if there is any way to re-root my phone to ICS and then flash the ics rom? I really havent seen anyone ask this yet but sorry if I am repeating anyones question.
matt_12tall said:
So I am on Atrix Xperia 4 rom and i was wondering if there is any way to re-root my phone to ICS and then flash the ics rom? I really havent seen anyone ask this yet but sorry if I am repeating anyones question.
Click to expand...
Click to collapse
Are you on the ICS leak already? Are you on AT&T? If you are on the ICS leak and on AT&T there is a way to root it in the leak thread in the General section. I put the files back up today.
If not, I really am not sure, one of the guys on the other leaks might be able to help there.

Ota rootkeeper ???

Has any one perhaps used this app
Essentially ist an app that allows you to back up and restore your root access therefore allowing you to take updates over the air and then afterwards allowing to restore your root. I saw a couple videos on you tube but they were all dated months ago I was wondering if any one had any comments or feedback based on there own experience using this tool cause in theory it sounds pretty awesome
Sent from my SCH-I535 using xda app-developers app
Sent from my SCH-I535 using xda app-developers app
I used it with the most recent jb update on two vzw gs3s. It works as promised. Just make sure your bootloader is still unlocked after the update.
Sent from my SCH-I535 using xda premium
ota rootkeeper
Firealoha said:
I used it with the most recent jb update on two vzw gs3s. It works as promised. Just make sure your bootloader is still unlocked after the update.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
is there any chance you could list the steps you did involving ota rootkeeper....i still have ics 4.0.4, stock rooted unlocked. didnt take the jb update cause i didnt want to lose everything....thanks
Both times I used it I was running CM10 stable and CWM touch 6.0.2.3. I then did a full wipe, restored my stock back up, downloaded voodoo and hit "protect root", and then accepted the OTA. It was that easy.
The first phone I carelessly forgot to re-unlock my bootloader using ez-unlock and when I rebooted I got the dreaded triangle. Learned my lesson with the second one. I remember something about having to answer some ?'s during the reboot process about keeping my custom recovery, but I don't remember exactly what they were. The answers were pretty obvious.
Also, I just tried ez unlock now and it says device status unknown. After the update I remember getting that msg too for some reason. I just locked the bootloader and then unlocked it for good measure, making sure to get the "your bootloader has been successfully unlocked“ msg.
Good luck and lmk how it turns out
Sent from my SCH-I535 using xda premium
So flash or return to stock rooted ics in my case download the app hit protect root and then it says temporary un root then go through the notions of the update and then after it reboots just double check that the boot loader is unlock wit ez unlock before attempting to flash custom roms correct???
Ps after you or I unlocked my boot loader it too says device status unknown so much like you I lock it and then unlock it to be sure
Sent from my SCH-I535 using xda app-developers app
MIKEYSAKZ said:
So flash or return to stock rooted ics in my case download the app hit protect root and then it says temporary un root then go through the notions of the update and then after it reboots just double check that the boot loader is unlock wit ez unlock before attempting to flash custom roms correct???
Ps after you or I unlocked my boot loader it too says device status unknown so much like you I lock it and then unlock it to be sure
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry was to busy watching the Super bowl and didnt have acces to a computer on my last post. Hopefully this is a little easier to follow.
1) Return to stock rooted/unlocked ics (in my case it was the backup I made of my phone straight out of the box)
2) Download the app and when you run it, it should have all but one of the boxes checked (you'll see what I mean when you open the app). Click on "protect root" and the final box should now be checked (indicating that a protected su copy is available)
3) I did not select temp unroot as an option, so I cannot attest to what selecting this will do. Once I selected "protect root", I went and initiated the OTA download. I did this with two gsIII's following the above sequence and had zero problems (well, except for forgetting to re-unclock my bootloader).
4) After the phone has downloaded the update it will ask you if you want to allow CWM (or whatever your recovery is) to install the unsigned.zip - select YES and answer YES to keeping root.
5) Once the phone is done booting up go into ezunlock and re-unlock your bootloader before booting into recovery or rebooting the device.
I think most people will agree that this is kind of a waste of time as their are a number of debloated Stock JB ROMS on this forum that you can flash without having to go through all the hassle of doing all this. I chose to do it as more of a learning tool. This is my first Samsung device having owned and rooted/S-Off''ed two previous HTC devices. I am by no means an expert, but this community has been so helpful to me over the last few years,that I figured it's about time I started spreading the Aloha. Good Luck!

[Q] Installing a Custom Recovery without USB or ROOT?

I'm having a hardware problem with my phone and do not have USB function. it doesn't have anything to do with DRIVERS, CABLES OR COMPUTERS. this we have all ready determined. it is NOT rooted and does NOT have a custom recovery already installed. its a stock Rogers Samsung s2 lte stock ICS (sim unlocked) using bell as a provider. I would like to get JB installed as it is no longer avaible OTA at the moment.
Hmm... I know you can do it without root with Odin, but at requires USB. I would try posting this on your device's forum.
Sent from my SGH-T999 using xda app-developers app
Pennycake said:
Hmm... I know you can do it without root with Odin, but at requires USB. I would try posting this on your device's forum.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
what device are we talking about? if you dont have usb option,you are screwed
I'm not sure it thats a 100% true fallen, if I could root with out usb I could use moblie odin.
its a SGH-i727R fallen, even if I could load Clockworkmod Recovery via stock Recovery menu as a temp then load the official JB rom thats all ready been rooted I'm golden. the only thing I can think of that I got going for me is the facted I don't need root to load a rom.
It is now available as an OTA update again but I have updated to JB still no USB cause the usb port on the S2 Skyrocket is a piece of junk thanks for everyons help.

[Q] KitKat ROM Attempt gone horribly wrong!

So after seeing KitKat in action, I hunted down an Android phone eligible for a KitKat ROM. I traded my iPhone for a Verizon Samsung Galaxy S3 (i535) I got it rooted and CWM on it just fine, and the boot loader unlocked. (or so I thought) Went into recovery and did all the steps to install the ROM, got it installed, along with G-Apps and rebooted. My phone came to a screen saying
"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."
As far as I can tell, the boot loader was not successfully unlocked. So, it's back to stock ROM via Odin, right? :laugh:
NO! All the guides I find say to download an app to reset the binary counter. How do I do that if I have no OS to boot to?
Any Ideas? Did my enticement for KitKat get the best of me?
You shouldn't need triangle away to Odin back to stock. Triangle away would be for if you were trying to take your phone back to Verizon or Samsung for warranty work and didn't want them to know it was previously rooted.
Sent from my SCH-I535 using xda app-developers app
dustin_b said:
You shouldn't need triangle away to Odin back to stock. Triangle away would be for if you were trying to take your phone back to Verizon or Samsung for warranty work and didn't want them to know it was previously rooted.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
jcaauwe said:
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
Click to expand...
Click to collapse
Follow the instructions in section 5 of this guide: http://forum.xda-developers.com/showthread.php?t=1762709. This will get you back to stock and unrooted. Then you will have to do the root unlock processs again.
Sent from my SCH-I535 using xda app-developers app
dustin_b said:
Follow the instructions in section 5 of this guide: http://forum.xda-developers.com/showthread.php?t=1762709. This will get you back to stock and unrooted. Then you will have to do the root unlock processs again.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
and or use the casual all in one tool and follow root, and flash insecure aboot then download Rom manager from google play and install latest CWM
I just had my s3 replaced under warranty. The new one, I used casual to root/unlock, etc. Worked great! I think I let casual install everything then flashed CM from recovery.
Sent from my SCH-I535 using xda app-developers app
jcaauwe said:
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
Click to expand...
Click to collapse
Not sure what you are trying to achieve, but once you get it back to functional and rooted, I would recommend you try out some of the wonderful custom TouchWIz ROMs on the forum here. They have most of if not more features than are in Kit Kat and there are no fully functional Kit Kat ROMSs for the S3 yet. Plus thse ROMs are stable and all your Samsung features will work properly . MORA, Hyperdrive, Synergy, and Jelly "beans" are good examples of excellent ROMs.
So I figured out what went wrong, and I'm still kicking myself for how stupid of problem it was. The reason Odin didn't want to work was because I was using the front USB ports on my system, which are not USB 2.0... I spent 6 hours trying to figure it out. So I hooked it up to a rear USB port, flashed it back to stock ROM, redid the Root, unlocked bootloader (which I didn't do in the first place) and now I'm getting Cyanogenmod on it.
Thanks everyone for the help! I hope anyone else who comes across this who where in the same boat I was can figure it out.
Sometimes it's a user-error.
Fix
jcaauwe said:
So after seeing KitKat in action, I hunted down an Android phone eligible for a KitKat ROM. I traded my iPhone for a Verizon Samsung Galaxy S3 (i535) I got it rooted and CWM on it just fine, and the boot loader unlocked. (or so I thought) Went into recovery and did all the steps to install the ROM, got it installed, along with G-Apps and rebooted. My phone came to a screen saying
"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."
As far as I can tell, the boot loader was not successfully unlocked. So, it's back to stock ROM via Odin, right? :laugh:
NO! All the guides I find say to download an app to reset the binary counter. How do I do that if I have no OS to boot to?
Any Ideas? Did my enticement for KitKat get the best of me?
Click to expand...
Click to collapse
i know you say you are ROOT but why dont you check using ROOT CHECKER download it from the play store its gonna tell you if you are root or not. im using sspencer10 KITKAT 4.4 CM11 and is running pretty smooth why don't you try it out just download the .zip reboot into RECOVERY i preffer you use TWRP (last version) go to whipe>advanced wipe and clear, Dalvik Cache>System>Data>Cache (optional i alwayz check mark Internal storage looking for space and alwayz make a clean flash same as Format Data) make sure you backup everything first using Titatinium Backup go back, then go to Install search for your .zip file on ur SDCard or Internal Storage first select the ROM ADD MORE FILE and add the GAPPS click REBOOT SYSTEM AND ENJOY YOUR NEW KITKAT 4.4 CM11 ON YOUR SGS3.
Don't be scared of Kit Kat! Once u get ur issues figured out and get 4.4 up and running you will see its all worth it!

Categories

Resources