Related
I am putting together a quick guide on how to update your Stock ROM, Rooted, custom recovery T-Mo GSIII without having to wipe your phone.
You will need:
- Kies (If your phone has not prompted you to install the OTA yet, Kies will download and attempt to install it for you) (http://org.downloadcenter.samsung.c.../20120809103126135/Kies_2.3.2.12074_13_13.exe)
- ODIN 3.7 (http://forum.xda-developers.com/attachment.php?attachmentid=1270006&stc=1&d=1345396888)
- STOCK T-Mo GSIII recovery.img (I extracted this from the stock ODIN image for T-Mo) (http://forum.xda-developers.com/attachment.php?attachmentid=1269983&stc=1&d=1345396186)
- TWRP or CWM ODIN Flash-able recovery (CWM - http://forum.xda-developers.com/attachment.php?attachmentid=1269979&stc=1&d=1345396186 , TWRP - http://forum.xda-developers.com/attachment.php?attachmentid=1269980&stc=1&d=1345396186)
- Recovery flashable SuperSU root package (http://forum.xda-developers.com/attachment.php?attachmentid=1269984&stc=1&d=1345396186)
SO, place your phone in download mode (Vol Down + Home + Power), and via ODIN, flash the "Stock-Recovery-Image(Working T-Mobile T999).tar" image. ( This is putting the stock recovery back on your phone so the update can install).
When it reboots, either select yes to allow the OTA update to install (if your phone is already aware there is an update) on your phone, OR plug you phone into your PC and allow Kies to prompt you to update your firmware. Select yes and allow the OTA to install.
Once completed, your phone is updated without having to wipe, but you have lost root and customer recovery, so.....
Again, in Download mode, Flash either of the provided ODIN flash-able custom recoveries (TWRP, or CWM) I prefer TWRP
Once that is complete, you can reboot your phone into the new recovery (Vol UP + Home + Power)
Once in recovery, flash the SuperSU.zip package and Voila, all done, Triangle away and you in cool runnings.
Let me know if I need to clarify anything here. It makes sense to me, but then again, I fumbled through it to figure it out and extract the right recoveries and set permissions etc.....
Please hit the thanks button if this helped you in any way
Hans
Nice instructions, but I'm going to wait a few days. I'm want to see if the dev that did the flash and root without tripping the flash counter will do the same for the new firmware. I'm still not too keen on custom recoveries yet even though I backed up my IMEI, so I just want to be rooted. If not, I'll use your guide.:good:
Wildchld already released it.
http://forum.xda-developers.com/showthread.php?t=1838101
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Wildchld already released it.
http://forum.xda-developers.com/showthread.php?t=1838101
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
But with Wildchild's it's a complete ROM (650-700MB), correct? Are you not wiping when you flash his?
Actually I'm not 100% that you need to do a full wipe, but I'm guessing you probably should. Depends on what's different. You can always nabdroid and give it a shot. I will later if I have time.
Anyway, I was more responding to the post above mine about stock with root than to the op. Sorry if shoulda been a little more clear on that.
Sent from my SGH-T999 using xda app-developers app
i might wait. finally got google now and google wallet working and i dont want to mess it up lol
RotaryXperiment7 said:
i might wait. finally got google now and google wallet working and i dont want to mess it up lol
Click to expand...
Click to collapse
What did you have to modify to get them working? Like I said before, I made this little method so you did not have to wipe your phone to get the OTA installed.
The only thing I could see that would cause the OTA to break wallet, or Google now would be that if you have to modify pieces in the /system/ directory that would be overwritten. The only thing I had to do after updating was re-flash my little installer for international boot image, re-remove Carrier IQ as it was added back, and revert the googlesearch.apk to the earlier backed up version (functioning unified search) with titanium. Outside of that I run a pretty tight ship as far as system modifications go outside of root and root privileged programs.
had to edit build pro for wallet
Thanks op, this worked great for me! Updated and rooted again...
Sent from my rooted T-Mo SGS3
I tried several times but couldent unroot my phone. I even tried through the root kit by mskip. I think the problem may be that I got my phone unlocked, not using an unlock code but some other method (all I know about this method is that my phone says"restricted access" for a few seconds upon restarting.)
Any suggestions on how to unroot? Also, if I unroot, will I loose the unlock?
pappuhathi said:
I tried several times but couldent unroot my phone. I even tried through the root kit by mskip. I think the problem may be that I got my phone unlocked, not using an unlock code but some other method (all I know about this method is that my phone says"restricted access" for a few seconds upon restarting.)
Any suggestions on how to unroot? Also, if I unroot, will I loose the unlock?
Click to expand...
Click to collapse
I think the best method to unroot your phone will be to ODIN it back to the stock T-Mobile image. (Overwrites EVERYTHING, probably your unlock as well).
http://forum.xda-developers.com/showthread.php?t=1737855
Above is the link to the stock image.
Apologies, in general, but I feel you may have the wrong thread if your looking to unroot your phone. That is off topic on what is being discussed here.
has anyone tried this and kept google wallet and google now working? Any troubles?
I'm wanting to update but I'm rooted withthose two apps finally up and running.
arts711 said:
has anyone tried this and kept google wallet and google now working? Any troubles?
I'm wanting to update but I'm rooted withthose two apps finally up and running.
Click to expand...
Click to collapse
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us
cybrnook said:
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us
Click to expand...
Click to collapse
So (in case this all doesn't work out) to restore via nandroid, just root and apply right?
cybrnook said:
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us
Click to expand...
Click to collapse
You are correct about build.prop being overwritten.
Sent from my rooted T-Mo SGS3.
If I've helped you, be sure to use the thanks button!
arts711 said:
So (in case this all doesn't work out) to restore via nandroid, just root and apply right?
Click to expand...
Click to collapse
Well if it doesn't work (Which I think it won't), you don't need to worry about restoring root. You just need to flash a custom recovery to revert your nandroid backup. Your root and customization will come back with that.
But with some of the added features that come with the update, I would say don't look back. Upgrade to the latest, then reapply your customization to get wallet and all working again.
IF you have to revert your nandroid back, make sure to do a factory wipe before you revert to your backup.
thanks! i'll give it a shot this weekend once i get more time.
I've used two different versions of Odin and two different T-Mobile stock recoveries (other one is here), and I can't get stock recovery to replace CWM on my GS3. Odin reports that the flash is successful, but when it reboots, ROM Manager still shows me as having latest CWM Touch, and the T-Mo update fails. I'm attempting the update via Kies right now, but I anticipate failure due to CWM still being installed as recovery.
-- I have Cerberus anti-theft installed, but I don't see anything about protecting recovery.
-- I have Busybox installed, but that shouldn't affect recovery.
Any ideas?
EDIT: Interestingly enough, where the OTA update failed, the Kies update went smooth as silk. Now to re-root and remove bloatware!
RaymondPJR said:
Nice instructions, but I'm going to wait a few days. I'm want to see if the dev that did the flash and root without tripping the flash counter will do the same for the new firmware. I'm still not too keen on custom recoveries yet even though I backed up my IMEI, so I just want to be rooted. If not, I'll use your guide.:good:
Click to expand...
Click to collapse
Are you referring to MrRobinson's rooting method? I'm waiting for it too.
Sent from my SGH-T999 using XDA Premium App
Im unable to update. I used Odin to flash the stock recovery, then downloaded the update via settings-> about device-> software update. Installing reboots the phone but then fails and reverts to current state. I can't update through kies also bc it just says "connecting", no errors. I tried uninstalling/reinstalling drivers but kies never completes connecting. Any help?
Sent from my SGH-T999 using xda app-developers app
EDIT: I uninstalled all my samsung drivers and Kies from "Programs and Features" in win7, deleted Samsung folders from HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER. Reinstalled Kies and connected my phone to install the drivers. Kies was stuck in the connecting loop still, so I unmounted my sd card, turned on USB debugging and Kies finally connected and asked to upgrade. Upgrading at this moment.
I can see Android v4.1.1 on System, About, but I totally forget what ROM I flashed. One of the more popular ones, last October or so. How do I tell what is on the phone?
Thanks, and sorry for the dumb question...
Dougmeister said:
I can see Android v4.1.1 on System, About, but I totally forget what ROM I flashed. One of the more popular ones, last October or so. How do I tell what is on the phone?
Thanks, and sorry for the dumb question...
Click to expand...
Click to collapse
Don't you have the rom zip saved? It should say what rom it is. Although you should know what you are flashing.
Sent from my Clean Bean v2.6 Galaxy S3
Dougmeister said:
I can see Android v4.1.1 on System, About, but I totally forget what ROM I flashed. One of the more popular ones, last October or so. How do I tell what is on the phone?
Thanks, and sorry for the dumb question...
Click to expand...
Click to collapse
System settings / build number
Sent from my blue galaxy
miller710 said:
System settings / build number
Click to expand...
Click to collapse
Hmmm. Maybe I never *did* flash anything...
"Build number JRO03L.L710VPBLJ7"
Doesn't that mean plain old Jelly Bean?
I vaguely remember installing Clockwork Mod so I could get JellyBean early.
I guess I want to uninstall Clockwork Mod so I can do OTA updates from Sprint, etc. I found these threads, but they are for Galaxy Tab 2...:
http://forum.xda-developers.com/showthread.php?t=1800175How to Uninstall Clockwork Mod Recovery?[/URL]
[ODIN STOCK ROM] GT-P3113 Stock ROM for Odin flash
But since last fall, I've had to re-install Windows.
So, two questions:
1) Jellybean is standard on Galaxy S3's by now, right?
2) What do I need to install on my PC to uninstall Clockwork Mod Recovery? Odin? Anything else?
Thanks.
Dougmeister said:
Hmmm. Maybe I never *did* flash anything...
"Build number JRO03L.L710VPBLJ7"
Doesn't that mean plain old Jelly Bean?
I vaguely remember installing Clockwork Mod so I could get JellyBean early.
I guess I want to uninstall Clockwork Mod so I can do OTA updates from Sprint, etc. I found these threads, but they are for Galaxy Tab 2...:
http://forum.xda-developers.com/showthread.php?t=1800175How to Uninstall Clockwork Mod Recovery?[/URL]
[ODIN STOCK ROM] GT-P3113 Stock ROM for Odin flash
But since last fall, I've had to re-install Windows.
So, two questions:
1) Jellybean is standard on Galaxy S3's by now, right?
2) What do I need to install on my PC to uninstall Clockwork Mod Recovery? Odin? Anything else?
Thanks.
Click to expand...
Click to collapse
I would suggest searching the Q&A thread for all this. You should read up before you start installing roms or doing any mods to your phone.
Sent from my Freeza MC3 Stock Rooted Galaxy S3
TheSocalGuy79 said:
I would suggest searching the Q&A thread for all this. You should read up before you start installing roms or doing any mods to your phone.
Sent from my Freeza MC3 Stock Rooted Galaxy S3
Click to expand...
Click to collapse
Thanks. Will do.
Dougmeister said:
Hmmm. Maybe I never *did* flash anything...
"Build number JRO03L.L710VPBLJ7"
Doesn't that mean plain old Jelly Bean?
I vaguely remember installing Clockwork Mod so I could get JellyBean early.
I guess I want to uninstall Clockwork Mod so I can do OTA updates from Sprint, etc. I found these threads, but they are for Galaxy Tab 2...:
http://forum.xda-developers.com/showthread.php?t=1800175How to Uninstall Clockwork Mod Recovery?[/URL]
[ODIN STOCK ROM] GT-P3113 Stock ROM for Odin flash
But since last fall, I've had to re-install Windows.
So, two questions:
1) Jellybean is standard on Galaxy S3's by now, right?
2) What do I need to install on my PC to uninstall Clockwork Mod Recovery? Odin? Anything else?
Thanks.
Click to expand...
Click to collapse
Might I interject here? If the only reason you want to go back to stock recovery is to get the OTA updates, I personally don't think you need to. Typically, Freeza has the most up-to-date Stock, Rooted Rom over in his thread. In my case, he usually has it well before I get the OTA notification from Sprint. If you think his thread is daunting to look at, you really only want to flash one of the following (I always remove direct links to the Roms out of respect for the dev's):
freeza said:
[size=+4]Leaked Builds[/size]
MC3 Full ROM (DeOdex): Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMC3 | Mirror (Thanks HashTagHell)
MD5: 8D714F25612D2CA8F103A63DF902E607
[size=+4]Official Software[/size]
FULL ROM:
DeOdex:
Sprint Touchwiz Jelly Bean 4.1.2 L710VPBMB1 | Mirror | Mirror 2 (Not yet active)
MD5: 37E1CCCB3A30959C64DF238D0BD2B23C
Click to expand...
Click to collapse
The MC3 Rom is a leak of a new OTA that might come out soon (or it'll be incorporated in a future OTA). The MB1 Rom is the most current, stock Rom. All you have to do is flash it and you're updated. If you need help with how to flash it, you can look to my post over here. Since you're going from 4.1.1 to 4.1.2, I'd recommend a "clean install" (step 5 in my instructions) just to minimize the chance of Force Closes, but you should be good if you want to do a "dirty flash" (only wipe cache and dalvik cache). If you dirty-flash, though, any and all troubleshooting will boil down to doing a clean install and seeing if the problem persists.
Also, CNexus has written up a really good OTA Guide to help you understand the whole OTA thing more and to recognize your options. You can check out his post over here.
Hope this helps!
Edit: It might also be good to update your Recovery before proceeding. Depending on how old your CWM is, it might be best to get an updated one (with hopefully fewer bugs). Thankfully, Naddict has created updates that are flashable from the Recovery itself. All you have to do is download the one you want (I'm using TWRP 2.5.0.0, but CWM is fine, too) and flash it in your custom Recovery, then reboot into recovery again.
topherk, thanks!
I took your advice and upgraded my ClockworkMod. (I also installed TWRP, which I think overwrote it, but that's another story).
I'm going to go over your post in more detail (hopefully) this weekend.
I tried flashing some different ROMs to see what they were like. I was not impressed, so I went back to stock.
Can you tell me something? If I use TWRP to back up everything, I still need to install GAPPS, right? Then I need to do something with GAPPS and Platinum Backup before I wipe/re-install to keep all/most of my programs/settings, right? Then run GAPPS again after I flash the new ROM?
Dougmeister said:
I took your advice and upgraded my ClockworkMod. (I also installed TWRP, which I think overwrote it, but that's another story).
Click to expand...
Click to collapse
Yeah, you can only have one recovery installed at once. I use TWRP, others use CWM. In my opinion, it shouldn't matter too much. They're both good and as far as I'm aware, the newest of each are relatively bug-free. The only thing is once you have backups for one, you can't restore them with the other. This isn't that big of a deal, but just an FYI.
Dougmeister said:
Can you tell me something? If I use TWRP to back up everything, I still need to install GAPPS, right? Then I need to do something with GAPPS and Platinum Backup before I wipe/re-install to keep all/most of my programs/settings, right? Then run GAPPS again after I flash the new ROM?
Click to expand...
Click to collapse
I'll break your questions here:
As far as I'm aware, all TouchWiz Roms include GAPPS in them by default. Of the flip side, no AOSP Roms will include them. This is because Google has asked dev's to not include them (in a Rom) unless specifically approved by Google. Samsung has gotten that approval for their TW framework, so any Rom based on TW can (and do) include GAPPS. If you're in doubt and the Rom doesn't say, first re-read the thread, as it's a common question. Then you can just flash the Rom without GAPPS and load up your phone. If GAPPS is included, you'll have a play store. If not, then you can just reboot into recovery and install it. Easy as pie.
I believe you mean Titanium Backup (another precious metal). Using TiBk, I actually have an automatic restore done every morning at 3am. Then if I decide to flash a new Rom, I always have an up-to-date backup of my apps. I never restore system apps, as that's just asking for trouble when switching Roms. I always back up my messages and phone log, but nothing that's red in TiBk. And for most apps, you don't have to restore data (only the app). I only restore data for games and apps like Hulu so I don't have to log in again.
Hoep this helps!
Yeah stock based roms will include GAPPS, AOSP roms cant because they arent officially licensed to distribute them...
As for the original question, I think I have it figured out. If you go to /system/build.prop and open that file, the great majority of devs will modify the relevant lines to the name of their custom roms. On cm roms theres a line called "cm.version=", which devs will usually modify that on a CM rom
The name is in there somewhere...could be changed on a couple lines, or on ALL the relevant lines, but it will be changed most of the time
Hope this helps
Is there a way to just directly upgrade Jellybean from 4.1.1 to 4.1.2 without having to re-install (via Gapps?) all of my applications, etc.?
I thought I read that I could unroot, do the OTA upgrade, then root again? I'm reading the OTA guide by CNexus, and 'freezing' the update app seems like a good option, but that just keeps the nag screen away.
Dougmeister said:
Is there a way to just directly upgrade Jellybean from 4.1.1 to 4.1.2 without having to re-install (via Gapps?) all of my applications, etc.?
I thought I read that I could unroot, do the OTA upgrade, then root again? I'm reading the OTA guide by CNexus, and 'freezing' the update app seems like a good option, but that just keeps the nag screen away.
Click to expand...
Click to collapse
All you need to do is follow the guide. You can download the MB1 firmware from freezas thread, and then flash an updated version of your rom. If you are on stock rooted, then you can flash one of freezas plain stock rooted roms over what you have (i would recommend a backup first though)
Just a small correction Gapps strictly refers to Google made apps (maps, play store, books, etc) you usually only flash these when working with AOSP roms. You sound like your talking about Touchwiz roms and thus your not loading all your apps through gapps, because Gapps are already included with Touchwiz roms. What you are referring to is reloading all your apps through Google Play Store and using the Google restore feature.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Yes! I'm talking about:
1) Backing up everything on my Galaxy S3
2) Installing other ROMs (sometimes stock, sometimes AOSP)
(side question: "stock" = "TouchWiz"???)
3) Magically re-installing *all* of my apps in the new ROM by clicking a single button
To do that, I'll need to use the "Google restore" feature?
Dougmeister said:
Yes! I'm talking about:
1) Backing up everything on my Galaxy S3
2) Installing other ROMs (sometimes stock, sometimes AOSP)
(side question: "stock" = "TouchWiz"???)
3) Magically re-installing *all* of my apps in the new ROM by clicking a single button
To do that, I'll need to use the "Google restore" feature?
Click to expand...
Click to collapse
Titanium backup is what I use. Paid version and you dont have to click ok for each app
Sent from my blue galaxy
miller710 said:
Titanium backup is what I use. Paid version and you dont have to click ok for each app
Sent from my blue galaxy
Click to expand...
Click to collapse
You don't have to hit ok for each app when you use google restore the correct way. It automatically reloads your apps on your device. TB is a great also but never restore data it is the root of most issues caused when people use it.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Hi guys,
My beloved S3 is is > 1 year old now.
I was always afraid\skeptical of rooting it as it lead to void warranty
Since it is already > 1 year old and warranty does not come into picture now, I thought why not give it a try now..
I see many S3 users are more than efficient after root.
Should I go for it ?
praddz said:
Hi guys,
My beloved S3 is is > 1 year old now.
I was always afraid\skeptical of rooting it as it lead to void warranty
Since it is already > 1 year old and warranty does not come into picture now, I thought why not give it a try now..
I see many S3 users are more than efficient after root.
Should I go for it ?
Click to expand...
Click to collapse
Yes, unleash your device!! It's easy, and opens up a whole new way to interact with your phone
Sent from my SGH-I747M using xda premium
Yes, root to experience the full capabilities of your phone.
Please be sure to read all guides and FAQs and be familiar with GS3 terminology.
Read tons....i mean TONS!!
Search and reading will be your besfriends.
Root, experiment, enjoy greatness
Root and unleash the chains that bind you.
Take it from a noob, read, read and re-read.
Easier to read about potential problems before they arise than after.:good:
i can has root?
Rooting is a must. I went for root the day i got the phone and went reading up on rooting the S3, roms, etc. before i even got the phone.
first thing i did when i got my s3 in april was root it. and my dad has the same phone i have, and i have to say having mine rooted vs his stock, mine gets so much better battery life. and is just one of the perks of rooting other than overclock and underclock and custom roms and stuff.
...and Sammy phones are fairly fool proof when it comes to rooting and flashing
Yes, it seems like we have many 1 click tools to do this.
I just want to go slow, I want to unlock the boot loader first & then uninstall all the att crap..
that should free up some space n RAM..
Later on I can install custom ROM's and Kernels if need be..
This can be done right...
First thing you should do is make a backup of your stock unmodified system before you remove or erase anything or install roms. And also make a copy of the backup to a second location like a computer.
Sent from my SAMSUNG-SGH-I747
praddz said:
Yes, it seems like we have many 1 click tools to do this.
I just want to go slow, I want to unlock the boot loader first & then uninstall all the att crap..
that should free up some space n RAM..
Later on I can install custom ROM's and Kernels if need be..
This can be done right...
Click to expand...
Click to collapse
S3 doesn't have a locked bootloader. Reality just have to flash a rooted stock firmware in Odin and you are good to go.
Sent from my SGH-I747 using xda premium
stelv said:
First thing you should do is make a backup of your stock unmodified system before you remove or erase anything or install roms. And also make a copy of the backup to a second location like a computer.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
yes,,
1) unlock boot loader
2) take backup of everything using titanium
3) then uninstall all the useless apps which came along with att
4) if required i will flash custom rom and kernel else i will stick with everything stock..
The reason I want to stop at unlocked boot loader is that as of now I already have 4.1.1, and I have read everywhere that 4.1.2 isn't much of a revolution so why flash a custom ROM. People might not agree with this but I tend to think so...
Obviously any suggestions are appreciated....:fingers-crossed:
praddz said:
yes,,
1) unlock boot loader
Obviously any suggestions are appreciated....:fingers-crossed:
Click to expand...
Click to collapse
No
Don't even think about touching anything dealing with bootloaders.
The i747 comes with an unlocked boot loader, the only one that is locked is the Verizon S3.
There have been various bricked S3 by trying to "unlock" something that isnt locked.
Read read read and search and research.
Before you wind up with a paperweight
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
praddz said:
yes,,
1) unlock boot loader
2) take backup of everything using titanium
3) then uninstall all the useless apps which came along with att
4) if required i will flash custom rom and kernel else i will stick with everything stock..
The reason I want to stop at unlocked boot loader is that as of now I already have 4.1.1, and I have read everywhere that 4.1.2 isn't much of a revolution so why flash a custom ROM. People might not agree with this but I tend to think so...
Obviously any suggestions are appreciated....:fingers-crossed:
Click to expand...
Click to collapse
No I am not talking about just backing everything up with titanium backup. I am talking about backing up your stock untouched system with a custom recovery like twrp or clockwork recovery. After root you will most likely have a custom recovery installed like twrp. You can boot into this custom recovery and backup the entire system in its current state, because sometimes when certain system apps are removed you will get force closes and bootloops and the only way to restore your phone is by restoring a backup, flashing a rom or pushing a system to your phone via odin.
Removing stock apps that came with your phone can be risky at times because they are often tied to other systems. Search to see what apps are safe to remove and a system backup is probably good.
http://forum.xda-developers.com/showthread.php?t=1746665
Do not attempt to unlock the bootloader! It is unlocked already. Your proper plan of action should be:
Backup everything possible (MyBackup is what I used)
Root phone (several methods available, choose one)
Install custom recovery. Rom Manager can install CWM for you, while goo manager can install TWRP (I prefer twrp)
Follow instructions for installation off any Rom you download (found in the first post of that Roms thread, usually before you get to the dl link)
Before flashing or attempting any mod, make a back up of everything. And read the directions
Mine is still under warranty and its rooted. Open its can of whoop a**
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
The cool thing for you will be all the awesome tweaks and mods that have out in the last few months because you device is a little elderly. Check out the definitive mod thread in the T-Mobile S3 forum. I forget which thread its in. You can atleast double battery and speed and 20x the customization options. Once you flash a new rom it becomes a habit called flashaholism so be aware. My name is Bubba Fett and I'm a flasaholic.
Finally I did it,, My Galaxy S3 is rooted successfully..
Thanks to you guys & online sources..
-Root is done
-Backup using CWM is taken, a copy is there on Internal Memory, External Memory Card and My Computer
Next step-
-Remove bloatware and free some storage..
-Any idea which is the best stable ROM as of now for 4.2.2
praddz said:
-Any idea which is the best stable ROM as of now for 4.2.2
Click to expand...
Click to collapse
There is no best ROM it all depends on the user. Feel free to try any of them. Just make a Nandroid backup each time before you flash a new one and follow the devs installation instructions. Good luck and have fun!
praddz said:
-Any idea which is the best stable ROM as of now for 4.2.2
Click to expand...
Click to collapse
I've tried Cyanogenmod, PAC, and AOKP in the past week. All three are butter smooth and stable. You will have to cycle the battery a couple of times for it to fit in (I noticed upon initial flash, battery life was terrible).
Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.
Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
Sent from my Nexus 7 using Tapatalk 4
Mine is always rooted, and I get all OTAs.
Sent from my Nexus 7 using xda app-developers app
You just need to have the stock recovery to receive OTAs.
Username invalid said:
You just need to have the stock recovery to receive OTAs.
Click to expand...
Click to collapse
So if I have twrp installed, i won't receive them?
Sent from my Nexus 7 using Tapatalk 4
Takes 10 seconds to reflash the stock recovery.
UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is no longer necessary unless you are using an older version of SuperSU
This post also applies to JSS15Q update.
I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.
Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.
I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)
install UPDATE-SuperSU-v1.55.zip
install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)
reboot
You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.
Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.
If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Sent from my Nexus 7 using xda app-developers app
rmm200 said:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Click to expand...
Click to collapse
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.
Thus it is safest to use stock recovery to flash OTAs.
I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.
I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
It was common on other platforms I've used, but I don't know about here.
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:
If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted
If you are running stock recovery, the update will install automatically as normal
If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use
If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs
Also:
You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)
You can flash factory images instead of the update, without losing data (see other threads for how)
If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it
The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong Hope this helps.
phazerorg said:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically).
Click to expand...
Click to collapse
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.
With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.
You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.
TheAltruistic said:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
Click to expand...
Click to collapse
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
nolook said:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
Click to expand...
Click to collapse
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
Titanium backup is an app, I assume with files he is targeting e. G. Config files.
Sent from my Nexus 7 (2013)
Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
It means don't modify or delete any files in /system
Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)
Adding files is ok.
Alright, so here's my scenario. Hopefully someone can tell me what should happen:
I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.
So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?
Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?
(that last part is just my OCD talking)
phazerorg said:
:
[*]If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
Click to expand...
Click to collapse
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?
So basically what you are saying is this, with my current set up:
1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?
2 - I can just wait for the download to be posted on here, and just install via twrp.
3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.
Correct?
Theoretically it could work. I believe the flash has worked with twrp.
Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.
On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.
Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.
If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?
Then go through and use it to recreate the root\custom recovery again?
I'm sorry i had the wrong links and because of this i had miss information. So i formally apologize by updating with the proper links.
this first method doesn't work with the Sph-L710T or the Sph-L710 on NJ2/NJ3
First method: You can root the stock 4.4.2 ND8/NDC:laugh:
1st. Make sure your on 4.4.2 ND8 or NDC
2nd. Download Towel Root
3rd. Place Towel Root in sdcard or internal storage
4th. With any file manager find and install Towel Root
5th. Open Towel Root and well root
6th. Go to play store and download https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en and also https://play.google.com/store/apps/details?id=stericson.busybox&hl=en let super user update the binary
7th. Flash any recovery you want {personally i went with PhilZ Touch (this was before PhilZ had a root Option)}
8th. Enjoy your rooted stock 4.4.2 ND8/NDC
Down below is one more way too root Stock ND8/NDC/NJ2/NJ3 or NF4/OA3 (L710T) and basically any other update
(link to the almighty ODIN)
Second Method: mostly recommended
1st. Odin flash TWRP
2nd. In Odin choose PDA, PA or AP then select the TWRP Tar you just downloaded
3rd. Make sure Auto reboot is unchecked (also at this time your s3 should be in download mode)
4th. Hit start and let Odin let it finish!!
5th. Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery
6th. now your in TWRP
7th. so to root your stock rom with TWRP flash the following file SuperSU.zip by Chain fire (pro tip. Install any other custom recovery the same way I did for TWRP above if it is in .tar format)
and here is Philz recovery for the D2Lte 6.48.4 ( which you must flash in TWRP)
and here is TWRP that was made specifically for the D2Rephersher/triband/L710T TWRP (which you must flash in a recovery)
Third method Most recent.
Hidyman said:
This is in reference to Samsung Galaxy S3 for Boost Mobile SPH-L710.
Just want to let anyone out there that updated their Boost S3 to L710VPUC0J1 know that you can still root and/or ROM your phone.
Use the instructions to (use Odin to) update the recovery to TWRP first (in the second set of instructions). I had trouble trying to go right to PhilZ Recovery (which I believe is based off of ClockWorkMod). I Had to do the TWRP (twrp-2.8.7.0-d2spr.img.tar) first.
It was the only way to get it to actually accept the recovery, not sure why, maybe because the latest Samsung firmware fixed an exploit or two.
This is an older phone, but it is still a viable one.
I hope this helps someone out there.
It took me a while to figure this quandary out.
As always this WILL flag KNOX, but I'm sure this won't be an issue at this date and time (8/2016).
Click to expand...
Click to collapse
work on ND8 rom? sprint phone?
Tekone said:
work on ND8 rom? sprint phone?
Click to expand...
Click to collapse
i want to say yes but towel root does come with a warning that it might brick your device.....but i want to say yes since most things that can be done to the ND8 can be done to the NDC and also in reverse order.....so try it and report back it will be good to know if it works on both bootloaders
Sprint S3 Android 4.4.2 ND8-It works!
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!
oops
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.
henhun said:
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.
Click to expand...
Click to collapse
ND8 or NDC? have you tried updating your profile/PRL?
6th_Hokage said:
ND8 or NDC? have you tried updating your profile/PRL?
Click to expand...
Click to collapse
Ya know. People keep talking about ND8 and ND___. I have no idea what that means. I know I should be embarrassed.
UPDATE: FIGURED IT OUT, BASEBAND VERSION. GOTCHA. IT IS NDC.
I was JUST coming back to update my post. I DID update the PRL and restarted my phone. That seems to have done the trick. Thank GOD I got my data connection back!! It worked. Even though I found the info somewhere else, thank you so much for the quick reply. PRL update fixes the problem. You're awesome.
I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app
jbnorton0524 said:
I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
many users of basically the same phone report different things with every root method out there. If it worked for you that's great tell other users what you did for it to work and if it didn't work, then ask for help and you will get help; some people don't have success with any method while others do with all of the methods.....my phone falls under every method.....
Successful Towelroot on VM Galaxy S3 4.4.2.NDC
6th_Hokage said:
you can root the stock 4.4.2
first step make sure your on 4.4.2
second step download Towel Root
third step place Towel Root in sdcard or internal storage
fourth step with any file manager find and install Towel Root
fifth step root
sixth step go to play store and download Superuser (Chainfire) and also Busy Box (Stericson) let super user update the binary
seventh step flash any recovery you want personally i went with Philliz Touch
eighth step if you want flash a custom rom now if not enjoy your rooted stock 4.4.2
Click to expand...
Click to collapse
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is usafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave
dave260 said:
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is unsafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave
Click to expand...
Click to collapse
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the binary (<---completely forgot to fix that) you must hit the option normal not TWRP/CWM
churninern said:
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!
Click to expand...
Click to collapse
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.
Darkangels6sic6 said:
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.
Click to expand...
Click to collapse
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Knox Counter and "Device Status"
6th_Hokage said:
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the recovery you must hit the option normal not TWRP/CWM
Click to expand...
Click to collapse
Thanks for your response. I may be over thinking these indicators. All I did was Towelroot, successfully. On the phone, the "About Device, Status" now says CUSTOM (was "Official"). The Knox counter according to app "Phone Info" shows Knox Counter at 0x0. As you said, since the counter is not tripped, should be no problem on warranty. So then Device Status CUSTOM is not a problem? I'm not really worried about warranty at this point, but I think I'll hold off further mods for another 6 moths.
Thanks again for your help!
6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
Thanks. I tried the md8 and mk3 "mk3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all.
I'm guessing maybe I should install twrp. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most md8 Roms want you to odin or flash an md8 base.
Darkangels6sic6 said:
Thanks. I tried the ND8 and MK3 "MK3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all
I'm guessing maybe I should install TWRP. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most ND8 Roms want you to Odin or flash an md8 base.
Click to expand...
Click to collapse
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be
6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
6th_Hokage said:
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be
Click to expand...
Click to collapse
I was afraid you would say that.
Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!
strangelady said:
Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!
Click to expand...
Click to collapse
your welcome strangelady and if you want check out the links in my signature area for other cool stuff
added two more t=root methods