Ok,
So I recently updated to the stock 4.1.2 image, and I wanted to root because I have always read it was best to have the latest base before rooting. I was able to root using the guides on here, but everything kept force closing and i was unable to do anything with the phone, so i went back to stock because of the problems. What i think was happening was that the rooted image I was using was 4.1.1, and i need 4.1.2.
Could anyone point me to where the 4.1.2 image is that i need to root is so that i can root correctly?
Well, I don't know which method you used before or how you plan on rooting now, but on 4.1.2,
Cf auto root still works.
Casual root still works.
Flashing recovery through Odin then supersu through recovery still works,
I've done them all.
What doesn't work is the No Tripping the flash counter (by flashing the root injected image) root, rooting with motochopper, or the root your phone with your phone root.
You probably know that you need Odin (3.07 preferably) no matter what you do, except I think for Casual;
and also yes you probably flashed a 4.1.1 image over your 4.1.2 data, but a factory reset should have fixed that.
They also have a rooted stock Rom somewhere in the development section if you want it, once you have a custom recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
Related
SGH-T999, stock t999uvdlja
A month or two ago, I followed a rooting instructions thread on here. It had me use odin to flash over a clockwork recovery mod as the first step. It flashed over fine according to odin, but I was never able to enter recovery following the next steps and therefore was not able to root. I can't find the thread anymore.
I realized after the fact that my phone was already on Jellybean, so I presume, maybe wrongly, that the reason the clockwork mod wouldn't work was because it was for the older Ice cream sandwich firmware.
Anyway, now my phone says unable to update because it's modified when I go into settings:about:software updates.
I want to get this error to go away. I have kies and there is now a firmware update in there that I would like to do to see if it fixes a problem with the wifi calling app breaking caller id among other things.
I am afraid that if I try to push this update via kies, it may brick the phone or not work thanks to the clockwork mod problem.
So two questions: 1) how can I un-flash that clockwork mod out of there and make the recovery back to stock so there is no further error or possible warranty issue, and 2) is it safe to do that kies firmware update and if so would that fix the recovery on its own?
Any ideas?
Sent from my SGH-T999 using xda app-developers app
You need to find the stock recovery .tar file and use odin to flash it the same way you flashed the cwm recovery. Then you will probably need to use triangle away to reset the counter.....dont think kies would work if it sees your device is modified but not sure about that.
Use triangle away first to reset your flash counter then odin the completly stock jb from here http://www.androidfilehost.com/?fid=9390169635556426424....this is from docholidays thread for stock odin roms in the sticky section of development. ..this should give you a completely stock phone including recovery.....you will lose your data from this process but your sd card will be fine.
Edit: just realized you dont have root...you need root to use triangle away....so first odin root 66 pre root stock rom....then use triangle away....then odin stock unrooted rom that I linked above.
Sent from my SGH-T999 using xda premium
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Monoclypsus said:
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Click to expand...
Click to collapse
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
ok
topherk said:
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
Click to expand...
Click to collapse
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Monoclypsus said:
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Click to expand...
Click to collapse
Yeah, that same method should work. I personally like the custom recoveries, but understand your desires to leave it at stock recovery (not triggering the flash counter).
Like I mentioned before, Samsung hasn't (and most likely won't) locked their bootloaders, so any rooting method that has worked in the past should work in the future. Just make sure to read the last 3-4 pages of the thread for whatever method you're trying to use to see if there are any issues. I know an earlier version of mskip's toolkit was having issues with JB for a little bit (it's updated now).
Well I'm gonna give it a shot. Ill let you know how it turns out.
Sent from my SPH-L710 using xda app-developers app
Just went with cf autoroot. Worked fine.
Sent from my SPH-L710 using xda app-developers app
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
jkj said:
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
Click to expand...
Click to collapse
I replied to your thread. I hope it works for what you need.
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
eletendre84 said:
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
Click to expand...
Click to collapse
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
mentorkyrom said:
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
Click to expand...
Click to collapse
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
eletendre84 said:
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
Click to expand...
Click to collapse
Tethering is available on CM11 just like it was on 10.2; would strongly recommend latest Philz Touch Recovery over either TWRP or CWM though. Although it is based on CWM, it has proven to be pretty much the superior recovery option for flashing any Android build number, plus it is highly customizable.
Philz Touch Recovery
this is how to downgrade
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
smuther22 said:
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
Click to expand...
Click to collapse
Do you realize that this thread hasn't been used in a couple of months? I would assume the author has no more need of advice based on the inactivity. Also, once Knox is installed, it is on the phone to stay. PERIOD. NO DOWNGRADING POSSIBLE VIA ODIN. Custom ROMs of any build are fine via custom recovery, but any attempt to change the bootloader will trigger Knox and brick the phone. Dangerous info to be posting here, especially since someone else who doesn't know better might try this.
I used KINGO to root my 4.3, it said it rooted, but it didnt. It installed a custom recovery, but doesnt look like root is sticking . I am getting all sorts of app closes now ( you tube, super u, google maps )
Is there a ODIN flashable 4.3 full download? I see only a thread to restore to stock if you have a working flashable recovery...
Any tips???? on getting back to stock
I assume your on a s3? What model?
Sent from my SPH-L710 using XDA Premium 4 mobile app
droodski said:
I used KINGO to root my 4.3, it said it rooted, but it didnt. It installed a custom recovery, but doesnt look like root is sticking . I am getting all sorts of app closes now ( you tube, super u, google maps )
Is there a ODIN flashable 4.3 full download? I see only a thread to restore to stock if you have a working flashable recovery...
Any tips???? on getting back to stock
Click to expand...
Click to collapse
You are posting in the wrong forum, only developers are allowed to post topics here for their releases. You should be asking in the Q&A forum.
Anyways, I am assuming you are here because you have a i747 or i747m and not one of the many other versions of the s3, but make sure before following my instructions, or you might brick your phone. There are several options for getting a stock rooted 4.3 rom, such as downloading a stock image from sammobile installing cf autoroot over your rom, downloading a prerooted rom, using mobileodin to root inject a stock image, etc. forget kingo.
I would recommend using the i747 tools in the android unified toolkit to flash and root your phone since it provides step by step instructions during the semi-automated process, which is helpful for beginners. you can download the toolkit here: http://www.skipsoft.net/?p=1347
Alternatively, you can download a pre-rooted ("root66") odin flashable 4.3 image, and then flash it in odin. i would still recommend using the toolkit alongside that process though. Here are some root66 stock roms: http://forum.xda-developers.com/showthread.php?t=1739426
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
itsfredo said:
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
Click to expand...
Click to collapse
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
The Sickness said:
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
Click to expand...
Click to collapse
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
I don't know if towelroot will root 4.2.2, but it doesn't install a recovery.
Rob
itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
lordcheeto03 said:
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
This.
You really don't need CF Auto Root at all until all you want to do is root the stock rom.
If you want to install a customer rom, use Odin to install a custom recovery and flash whatever you want from there.
lordcheeto03 said:
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Use cf autoroot and flash clockworkmod through Odin. Download rommanager. Download a rom. Hit install rom from SD card. Pick your ROM from downloads.
itsfredo said:
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Click to expand...
Click to collapse
I understand your apprehension, i really do. What I've said to do has worked for me when i got the phone over a year ago, and has worked here recently when i did it again. I'm trying to tell you there is no need for an updated way of doing what you want. If you want root, use CFauto root. Like i said, that method was done specifically for MDB and MDL firmwares, there is no better choice. Newer yeah, but better? Not a chance. Your firmware is equally outdated and it's worked for millions of users without fail.
As far as a custom ROM goes, find one you want to use, put it on your SD card, pick a recovery (CWM, Philz, or TWRP), flash that in Odin, boot to recovery (power+volume up) , do a full wipe (system, data, and cache) select the ROM, and flash. No need to root at all if you want to go straight to a custom ROM.
EDIT: Obviously, you might want to perform a nandroid backup once you flash your recovery... but that's really optional as long as you have the stock Odin-flashable firmware. Totally up to you.
Sent from my SGH-M919 using XDA Premium 4 mobile app