Develop Bugs

[Q] i317 lost root after 4.1.2 update

I'm running a rooted stock I317M with nothing modified except for root. I used mrRobinson's thread h t t p :/ / forum.xda-developers.com/showthread.php?t=2004650 as a guide which worked perfectly to keep everything stock (and thus avoid tripping the flash counter) but gave me root. This morning the Canadian carriers began rolling out the 4.1.2 update OTA which failed a few times on my device so I used (GASP!) Kies to do the update. Not sure if it would have mattered OTA or Kies but I have now lost root. Has anyone managed to inject root into a stock image for the I317m yet? It looks like I could go with a custom AT&T I317 build or ADB in and manually install a custom recovery, root etc. but if possible I'm hoping to keep normal device status and not trip the flash counter.

Are you planning on turning your phone in for warranty anytime soon or do you just like the look of "Official" instead of "Modified" on your About Phone settings?

Exact same thing happened for mine, stock rooted Canadian OTA to 4.1.2 failed repeatedly, Had to use Kies as well and lost root. The main reason I wanted root was to switch off fast dormancy since my Canadian carrier doesn't support it and was killing battery. Good news is it stayed switched off.

[email protected] said:
Are you planning on turning your phone in for warranty anytime soon or do you just like the look of "Official" instead of "Modified" on your About Phone settings?
Click to expand...
Click to collapse
Not really. Originally it was just to make sure I'd get the update without issue when it was released. My understanding is that I can always reflash with the stock firmware I have from Sammobile and it will reset the flash counter + set the status back to normal if the need arose but also thought it easier to just unroot, reboot and uninstall SU if possible.

chris19000 said:
Not really. Originally it was just to make sure I'd get the update without issue when it was released. My understanding is that I can always reflash with the stock firmware I have from Sammobile and it will reset the flash counter + set the status back to normal if the need arose but also thought it easier to just unroot, reboot and uninstall SU if possible.
Click to expand...
Click to collapse
Cool.... Honestly, I never worry about tripping the counter unless I need to turn in for replacement/warranty repair. Apparently, this seems to work just fine: http://forum.xda-developers.com/showthread.php?t=2073141&highlight=lost+root

m4runner said:
Exact same thing happened for mine, stock rooted Canadian OTA to 4.1.2 failed repeatedly, Had to use Kies as well and lost root. The main reason I wanted root was to switch off fast dormancy since my Canadian carrier doesn't support it and was killing battery. Good news is it stayed switched off.
Click to expand...
Click to collapse
First time I've actually heard of fast dormancy. My battery life has actually been pretty good and that with fairly varied, heavy use. Have to look more into it. I rooted primarily for backing up (TB), remote file sharing and just plain messing around.

[email protected] said:
Cool.... Honestly, I never worry about tripping the counter unless I need to turn in for replacement/warranty repair. Apparently, this seems to work just fine: http://forum.xda-developers.com/showthread.php?t=2073141&highlight=lost+root
Click to expand...
Click to collapse
Thanks R1K, I looked at that earlier and still might try it after a little more in depth reading if nothing else presents itself. I use the camera fairly extensively and although it looks like the camera is only affected when patching the exploit I have to be a little cautious since I use it for work. Plus the easy unroot/stock return part :good:

m4runner said:
Exact same thing happened for mine, stock rooted Canadian OTA to 4.1.2 failed repeatedly, Had to use Kies as well and lost root. The main reason I wanted root was to switch off fast dormancy since my Canadian carrier doesn't support it and was killing battery. Good news is it stayed switched off.
Click to expand...
Click to collapse
One option which is what I did, was to download the 4.1.2 update from sammobile.
I then used mobile odin to flash it which has the ability to protect root.
So now I am stock rooted on latest firmware device status is normal
---------- Post added at 04:54 PM ---------- Previous post was at 04:42 PM ----------
[email protected] said:
Cool.... Honestly, I never worry about tripping the counter unless I need to turn in for replacement/warranty repair. Apparently, this seems to work just fine: http://forum.xda-developers.com/showthread.php?t=2073141&highlight=lost+root
Click to expand...
Click to collapse
Doubt this will work.
The whole way this gained root was via the exynos exploit.
This firmware I am pretty sure has patched it.
Exynos abuse says no but voodoo app says yes.
I can confirm the exploit is patched in this new firmware so I suspect this will close any holes used by exynos abuse app to root phone.

Canadoc said:
One option which is what I did, was to download the 4.1.2 update from sammobile.
I then used mobile odin to flash it which has the ability to protect root.
So now I am stock rooted on latest firmware device status is normal
---------- Post added at 04:54 PM ---------- Previous post was at 04:42 PM ----------
Doubt this will work.
The whole way this gained root was via the exynos exploit.
This firmware I am pretty sure has patched it.
Exynos abuse says no but voodoo app says yes.
I can confirm the exploit is patched in this new firmware so I suspect this will close any holes used by exynos abuse app to root phone.
Click to expand...
Click to collapse
Thank you Canadoc. Might be the best bet for me too. I did a TB backup just prior to the update so maybe I'll flash back to 4.1.1 with the root injected ROM in odin and then flash the 4.1.2 update from sammobile from mobile odin. Otherwise looks like it might be a custom i317 build for me. CWM sure sounds nice right now

For those trying to get multiveiw update and are rooted.... it is much much easier ti go get the firmware from sammobile.com then flash it with mobile odin with the ever root option.. all done :thumbup:
Sent from my SGH-I317 using xda premium

twanskys204 said:
For those trying to get multiveiw update and are rooted.... it is much much easier ti go get the firmware from sammobile.com then flash it with mobile odin with the ever root option.. all done :thumbup:
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
That's for sure. I'm going to go back to root injected stock 4.1.1 and start from scratch.

chris19000 said:
That's for sure. I'm going to go back to root injected stock 4.1.1 and start from scratch.
Click to expand...
Click to collapse
Worked as planned... more or less. Had to do a factory reset and flash twice to get 4.1.1 to boot but from there installed mobile odin, extracted and flashed from 4.1.2 (from sammobile and copied to external SD) and good to go. Now, if you want to go stock with root and for whatever reason don't want to/can't use mobile odin, head over to this thread http://forum.xda-developers.com/showthread.php?t=2004650&page=26 mrRobinson is working on injecting root into the stock builds.
Cheers.

Which is the better way ?
chris19000 said:
Worked as planned... more or less. Had to do a factory reset and flash twice to get 4.1.1 to boot but from there installed mobile odin, extracted and flashed from 4.1.2 (from sammobile and copied to external SD) and good to go. Now, if you want to go stock with root and for whatever reason don't want to/can't use mobile odin, head over to this thread http://forum.xda-developers.com/showthread.php?t=2004650&page=26 mrRobinson is working on injecting root into the stock builds.
Cheers.
Click to expand...
Click to collapse
I use the Mr. Robinsons thread to stock my device to 4.1.1 but when i did . it always stuck on the Samsung logo after rebooting.
so i have to put my phone in recovery mode and factory restore.
this wasy right now i have root on 4.1.1 .
but i wanna know the best way to update my phone to 4.1.2
becasue i know .. with OTA i will loose my root.
please help.

prashant19p said:
I use the Mr. Robinsons thread to stock my device to 4.1.1 but when i did . it always stuck on the Samsung logo after rebooting.
so i have to put my phone in recovery mode and factory restore.
this wasy right now i have root on 4.1.1 .
but i wanna know the best way to update my phone to 4.1.2
becasue i know .. with OTA i will loose my root.
please help.
Click to expand...
Click to collapse
Hi prashant there are a number of ways you can update OTA without losing root but of the easy ones I can only speak personally about one of them - Mobile Odin - which is what I used. It's a paid app but it gives you the option for EverRoot which maintains root across roms and automatically installs itself and SU in the new rom. Hate to ask, but are you sure you flashed the right rom? He has it listed as the new! Bell rom under January. If you flash that with his directions it should work - that being said though I did have to flash it twice myself to get it to work. One flash with odin, stuck on logo, back to regular recovery, wipe cache, download mode and reflash with odin, worked that time around. By that time I had mobile odin and flashed the regular update without root that way but mobile odin kept my root.

If you're looking to retain or regain root after ota, this is the easiest way imo. Just answered it in this thread.
http://forum.xda-developers.com/showthread.php?t=2156741

Froid said:
If you're looking to retain or regain root after ota, this is the easiest way imo. Just answered it in this thread.
http://forum.xda-developers.com/showthread.php?t=2156741
Click to expand...
Click to collapse
Thanks Froid. SuperSU seemed to work for some folks too if they dropped the dime for the PRO version. I did see some instances where neither worked too though, but not enough details to say why.

all you need to do is just reflash with odin rooted 4.1.1 stock rom then once that is done goto play store and get voodoo ota rootkeeper make backup then temp unroot then get the ota 4.1.2 update when finished goto to ota rootkeeper and restore root works just fine and u keep root.

Question about rooting with odin

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.

[Q] Official 4.3 Upgrade Issues

I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!

phoenix98 said:
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
Click to expand...
Click to collapse
Is not possible for right now, until devs will create a new root app or something like superSU or I don't know ! :crying: Same to me ...

Your Boot loader is probably secured.
Try Root66 image and get back to UVDMD5 Rooted. From there, use Doc Holiday's thread to get 4.3 upgrade.

As it stands, right now if you flashed the official firmware or OTA, you will not be able to Odin flash any previous firmware. Maybe if you were never rooted....
For now though, you shoukd still be able to flash cwm/twrp and flash another rom. you will be limited to the 4.3 modem, but otherwise should be ok to run a 4.1.2 rom.
We are working on it.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2

I had the same problem
I just had this same problem and was lucky enough to fix it!!!!

vTizzle said:
I just had this same problem and was lucky enough to fix it!!!!
Click to expand...
Click to collapse
How/ What did you do you fix it? I'm stuck in a rut :l

I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you

vTizzle said:
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
Click to expand...
Click to collapse
Hm... Interestingly enough it worked! I flashed CWM 6.3.0 though, sent me straight into stock hehe :good::good: Though I'm still curious how long until I can root it

Have you tried the auto root course??
Sent from behind you

Boot recovery, then reboot system. It should ssk if you want to root.
Better yet, flash one of our roms. Or, download the supersu zip file from chainfires thread. (Or in my sig, but its not up to date)
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
There are several ways to root. But if you don't get rid of knox iits almost pointless.

Co-author root didn't work, and nor did Root66

I'm on the same boat
Same here,
Mine was rooted, then
I Updated to Factory 4.3
Same red letters and can't get it back,
I want to 'cause it's unstable and
it has weird partition, "emulated/0"
Any Help Please !!

This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.

DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
If I did softbrick it, is there anyway to restore it?

You can try first wiping just dalvik and cache, then try factory reset.

Other ROMs
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
Thank you Doc , It has been said ..Over and over and over.. OTA 4.3 update means you cannot flash older firmware again! I was one of the lucky that waited and installed you ROM and it has been stable . I placed a few Mods like Apps For 4.3 TW
For those just refused to READ and have NOT done a OTA update to 4.3 Like DocHoliday77 and and many have said .. here goes one more time..
WARNING!!!
If you have NOT updated via the official firmware or OTA update, it is highly recommended that you do NOT do so at this time!
You can still run these roms and gain every advantage, with none of the problems!
There so many other 4.3 ROMs to play with DocHolidays, Sarahai, mrRobinson and now aamir123. . YOu just to READ before run in head first into the OTA.

I have been trying to keep up with all the 4.3 update stuff but its just so hard with 15 different threads and it being updated everyday. I stupidly updated OTA 4.3 before coming on here and reading and it blows! Samsung is stupid for releasing such a unpolished update. But besides the point, I have been having a problem with out going calls, and battery life. When I will press to call someone the call ends instantly and I have to restart phone for it to allow me to call out. Has anyone else had this problem?
Also, are we any closer to getting 4.3 rooted? I know developers are having problems with Knox etc? If not is there anything I can do to make this update better or do I just have to suck it up? Thanks for the help guys.
I alrdy talked to people at samsung and complained beyond belief, but I dont think the out sourced help desk person understood me.

I made it !!
How ?
1. Uninstall KNOX with Titanium.
2. Flash CWM twice (first one failed), Now I have CWM.
3. Download T999UVDMD5 (Deodexed)
4. Flash it via CWM.
5. Voilà !!
Now It has the partition as it comes from Factory !.
It's there a version similar to this one, running on Android 4.3 (Stock Deodexed, Without KNOX) ?

DocHoliday77 said:
You can try first wiping just dalvik and cache, then try factory reset.
Click to expand...
Click to collapse
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?

bentheexo said:
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
Click to expand...
Click to collapse
If you have updated to official 4.3 by any means then don't try to downgrade your boot loader and rom as it may brick device
If you have not taken official update then it depends what is your current boot loader and what rom you are trying to flash
So if you are sure that you haven't gone for official update then you flash dmd5 firmware then try to flash rom
Be sure before doing anything
Sent from my SGH-T999 using Tapatalk

[Q] clockwork mod removal

I rooted my friends S3 ATT with the s3 toolkit v7.0 he now wants me to unroot it so he can take the 4.3 update it have run the unroot and remove zip multiple times ( I even re rooted it and tried removing it again) and it will not remove clockwork mod recovery even though it says it will, it has successfully unrooted it the phone and removed super user and busy box . he does not want to loose all the data on his phone is there another way to remove clock work mod and get him back to the stock recovery so he can take the 4.3 update with out using triangle away ?
thanks

You would need to flash the stock recovery to replace CWM.

audit13 said:
You would need to flash the stock recovery to replace CWM.
Click to expand...
Click to collapse
where do I acquire a stock recovery and is it flashed through oden or through clockwork ?
thanks

I'm not sure where to find the stock recovery as I have never seen one that is flashable via Odin, CWM, or TWRP.
By updating to stock 4.3, the phone will have a bootloader that cannot be downgraded and Knox will be installed.
I personally avoided the 4.3 update because the 4.3 bootloader makes it tough to go back to stock and tripping the knox counter will void the warranty. Also, knox can interfere with root access.

audit13 said:
I'm not sure where to find the stock recovery as I have never seen one that is flashable via Odin, CWM, or TWRP.
By updating to stock 4.3, the phone will have a bootloader that cannot be downgraded and Knox will be installed.
I personally avoided the 4.3 update because the 4.3 bootloader makes it tough to go back to stock and tripping the knox counter will void the warranty. Also, knox can interfere with root access.
Click to expand...
Click to collapse
actually I'm a blind idiot it is an option right in the tool kit i have just reflashed it and all is good
THANK YOU VERY MUCH I could not have fixed this with out your help
(he never used any custom roms and does not mind that his unit will be locked )

iiipm said:
actually I'm a blind idiot it is an option right in the tool kit i have just reflashed it and all is good
THANK YOU VERY MUCH I could not have fixed this with out your help
(he never used any custom roms and does not mind that his unit will be locked )
Click to expand...
Click to collapse
Hey, thanks for the post. I learned something too:good:

Question about downgrading from Kitkat to Jellybean on Galaxy SIII (SGH-I747M)

Before I start I will say iI did check out the search function for more than one hour and felt pretty lost amidst the technical discussion going on. I'm still reading about Android and learning so your help will be greatly appreciated.
I bought a Samsung Galaxy S3 (SGH-I747M) soon after its launch in Canada. It came with Jellybean and after a while I updated it to Kitkat using the "check for updates" area in the phones settings.
My question is basically is out possible to root the device after I updated it. Or is it possible to go back to Jellybean and then root it from Jellybean?
I have tried to flash the stock Jellybean ROM onto it and it just doesn't work at all. Odin loads stuff for 5 seconds and it fails.
Other than going back to Jellybean is there any way to Root my phone if it's on Kitkat now? I'm not concerned about warranty etc due to age of the device and it would be gone already anyways.
Thank You!
SalvelinuxFontinalis

Once you are on KK, you cannot downgrade the bootloader so don't bother trying to downgrade to JB using firmware from sammobile.com. Do this may brick your phone.
Does your phone have a custom recovery? If not, you could try flashing Philz for the d2lte and install supersu from recovery.

audit13 said:
Once you are on KK, you cannot downgrade the bootloader so don't bother trying to downgrade to JB using firmware from sammobile.com. Do this may brick your phone.
Does your phone have a custom recovery? If not, you could try flashing Philz for the d2lte and install supersu from recovery.
Click to expand...
Click to collapse
No it does not. Thanks I'll try that. How do you install super so froom recovery and would i get root access?
Thanks so much!!!

In order to flash supersu, you will need to install a custom recovery onto your phone. Doing this will automatically void your warranty.