So, after messing around with trying to root the S3 via adb scripts for a while, trying to get fastboot working, I came across several sources that the S3, and Samsung altogether, does not use fastboot. (I didn't know this, as I've never owned a Samsung phone before.)
Considering the lack of fastboot, is there anyway to adb push the su and busybox binaries and root the phone via adb scripts? I've tried, but as you all are aware, I'm sure, the adb remount script is a forbidden operation.
I have a Virgin Mobile (VM) S3, same model number SPH-L710. The reason I want to root via ADB is to avoid tripping the flash counter, as ODIN is required for every root method, and I'm not sure if Triangle Away is compatible with the VM bootloader. I am also reluctant to use CF-Autoroot from XDA, as it contains a Sprint boot.img, and I don't want to mess up my phone.
Any help would be appreciated.
Try this
http://forum.xda-developers.com/showthread.php?t=2252248
Yes, in s4 forums but it has worked for a large large range of Qualcomm devices
CNexus said:
Try this
http://forum.xda-developers.com/showthread.php?t=2252248
Yes, in s4 forums but it has worked for a large large range of Qualcomm devices
Click to expand...
Click to collapse
Thank you very much for this. What's the likelihood of bricking my phone if this exploit doesn't work? After looking at the run script, I know it's just pushing the binaries to temp directories. But, I already replaced my phone under store warranty once, and won't be able to do it twice.
Higgs_Boson said:
Thank you very much for this. What's the likelihood of bricking my phone if this exploit doesn't work? After looking at the run script, I know it's just pushing the binaries to temp directories. But, I already replaced my phone under store warranty once, and won't be able to do it twice.
Click to expand...
Click to collapse
None. If it fails, nothing bad will happen
Speaking from experience here
CNexus said:
None. If it fails, nothing bad will happen
Speaking from experience here
Click to expand...
Click to collapse
I guess I'll join the club. Exploit failed. There was a minor incremental update to the VM S3 recently. Maybe, they patched that loophole?
VM is Sprint there should be no difference. You can flash a costom recovery then just flash the team epic root file. It's not going to touch your bootloader or anything. Triangle away should work spot on for the VM device as well.
Remember search is your best friend, Have a great day!
edfunkycold said:
VM is Sprint there should be no difference. You can flash a costom recovery then just flash the team epic root file. It's not going to touch your bootloader or anything. Triangle away should work spot on for the VM device as well.
Remember search is your best friend, Have a great day!
Click to expand...
Click to collapse
Thank you for your reply. I would have searched, but I didn't really know where to begin. But, your reply has me pondering... If I have the stock recovery.img, can I flash via odin after unrooting and triangle away to restore to stock?
Again, sorry for adding clutter.
EDIT: Kind of answered my own question in a sense, as the mere flash of stock recovery via ODIN would trip flash counter... conundrum.
Would odin trip or brick anything with 4.2.2?
Would odin trip or brick anything with 4.2.2? Now?? Know there has been some issues with KNOX, My son's phone just cracked, and he cant use the screen and I want to wipe/install factory rom before I sell it.
Related
Ok so here goes a long but detailed read. I am writing this in hopes other fido users searching may find this thread and avoid future questions. Phone came with the TW 4.1.1 from fido and is fully stock.
Brand new S3 Galaxy from Fido (same as rogers) i747M Phone is great but the rooting bug has caught me.
1. I plan to root the device fairly shortly and install a non touchwiz variant. I will be following "High on Android's" Technique. detailed in this youtube video.
Is that method correct for my phone?
or should I be following something different? I just noticed Mr. Robinson posted the Fido TAR with root injected already on it. Does this make any difference? Links to TAR file are here
2. Now assuming I get everything up and running. What is the deal with "Triangleaway" and flash counters? From my understanding, Samsung has a counter installed that ensures they keep an eye on voided warranties due to flashing. Sure thats fine but lets talk about what we can do.
From what I gather, Triangle away will sort me out and get rid of the counters and put them back to zero in case I need to send my phone in for warranty. Is this correct?
Most of the triangle away info I read is for pre 4.1.1 confirmations hence why I ask.
3. Now lets assume I have flashed thephone and I am running CM 10 beautiful. Oh no power button breaks. What will be the required steps to get my phone back to 'stock" to send to Samsung. Will this even be possible to send it in without a worry? I cant seem to find steps online for this.
4. A lot of guides talk about the importance of backing up. Sure sounds great but they dont seem to give detailed instructions. What are the most important things I should backup before, during and after rooting my phone in case I brick it or anything goes wrong? Again any link or detailed explanations would be great.
Sorry for being so exhaustive in my questions. I like to learn it all so I can help other afterwards but also structured the thread so its easy to search for future users.
Happy new year everyone!
sspikey said:
1. I plan to root the device fairly shortly and install a non touchwiz variant. I will be following "High on Android's" Technique. detailed in this youtube video.
Is that method correct for my phone?
or should I be following something different? I just noticed Mr. Robinson posted the Fido TAR with root injected already on it. Does this make any difference? Links to TAR file are here
2. Now assuming I get everything up and running. What is the deal with "Triangleaway" and flash counters? From my understanding, Samsung has a counter installed that ensures they keep an eye on voided warranties due to flashing. Sure thats fine but lets talk about what we can do.
From what I gather, Triangle away will sort me out and get rid of the counters and put them back to zero in case I need to send my phone in for warranty. Is this correct?
Most of the triangle away info I read is for pre 4.1.1 confirmations hence why I ask.
Click to expand...
Click to collapse
I'm going to answer these two questions together, because they're interrelated.
There's no one single root method that's more "correct" than any of the others. The key difference between the end result of most of the methods is whether the flash counter has been tripped, which occurs (under circumstances where you're coming from ICS) if you use Odin to flash something other than a stock image (untouched or rooted as in Mr_Robinson's case). You can also trip the flash counter if you have the Jelly Bean boot loader and boot into a non-stock recovery image.
Thus, if you want to avoid tripping the counter for as long as possible, you want to use a method for rooting that doesn't trip the counter, such as the Mr_Robinson method.
If you're going to flash a custom recovery after working from stock JB, you'll probably end up tripping the flash counter the moment you boot into it, in which case (assuming your phone is still rooted) you could use Triangle Away to reset said flash counter.
sspikey said:
3. Now lets assume I have flashed thephone and I am running CM 10 beautiful. Oh no power button breaks. What will be the required steps to get my phone back to 'stock" to send to Samsung. Will this even be possible to send it in without a worry? I cant seem to find steps online for this.
Click to expand...
Click to collapse
I'd do the following:
Triangle Away, if the flash counter isn't 0;
Boot into download mode;
Flash a normal stock image from here; [*]Boot into stock recovery and wipe data/cache; [*]Boot phone as normal.
sspikey said:
4. A lot of guides talk about the importance of backing up. Sure sounds great but they dont seem to give detailed instructions. What are the most important things I should backup before, during and after rooting my phone in case I brick it or anything goes wrong? Again any link or detailed explanations would be great.
Click to expand...
Click to collapse
There are two major approaches you can take here, and using both of them responsibly is probably a good idea.
Titanium Backup, usable if your device is rooted, can back up all of your application data and some system settings; it's great for transferring data between ROMs and/or between devices altogether (I've done both). Most people I know of only use it for the former, as trying to restore system data with TiBu usually causes bizarre and unpredictable effects (with a few exceptions, such as text message data).
With a custom recovery, you can make what's called a "nandroid" backup, which is a complete image of your current ROM and userland data; it's most useful when you want to make a restore point of sorts for if you're, say, flashing experimental ROM images or other things you don't expect to work very well.
Hope this is of help.
smelenchuk said:
I'm going to answer these two questions together, because they're interrelated.
There's no one single root method that's more "correct" than any of the others. The key difference between the end result of most of the methods is whether the flash counter has been tripped, which occurs (under circumstances where you're coming from ICS) if you use Odin to flash something other than a stock image (untouched or rooted as in Mr_Robinson's case). You can also trip the flash counter if you have the Jelly Bean boot loader and boot into a non-stock recovery image.
Thus, if you want to avoid tripping the counter for as long as possible, you want to use a method for rooting that doesn't trip the counter, such as the Mr_Robinson method.
If you're going to flash a custom recovery after working from stock JB, you'll probably end up tripping the flash counter the moment you boot into it, in which case (assuming your phone is still rooted) you could use Triangle Away to reset said flash counter.
Click to expand...
Click to collapse
It seems the flash counter is a lot less worrysome to me now that you indicated I can always go back to a stock rom and return it for warranty regardless if it has a counter or not. Now I wonder why people even worry about tripping it.
I'd do the following:
Triangle Away, if the flash counter isn't 0;
Boot into download mode;
Flash a normal stock image from here; [*]Boot into stock recovery and wipe data/cache; [*]Boot phone as normal.
Click to expand...
Click to collapse
So Sounds to me like I should not worry about flashing and warranty correct? There will always be a method to go back to my phone in order to deal with warranty if something physical goes wrong? Any guide you could point me towards for this? I found this http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-canadian-galaxy-s3-sgh-i747m-stock-roms/
but it doesnt mention any fido files (understandable since its new)
There are two major approaches you can take here, and using both of them responsibly is probably a good idea.
Titanium Backup, usable if your device is rooted, can back up all of your application data and some system settings; it's great for transferring data between ROMs and/or between devices altogether (I've done both). Most people I know of only use it for the former, as trying to restore system data with TiBu usually causes bizarre and unpredictable effects (with a few exceptions, such as text message data).
With a custom recovery, you can make what's called a "nandroid" backup, which is a complete image of your current ROM and userland data; it's most useful when you want to make a restore point of sorts for if you're, say, flashing experimental ROM images or other things you don't expect to work very well.
Hope this is of help.
Click to expand...
Click to collapse
These two forms of backup I am use to and have used extensively on my nexus S. What I am worried about is more deep "system" type backups people do. is there any for this phone I should do through odin or Kies?
Edit: almost forgot to say thank you!
How come the root66_FMC_I747MVLDLK4.7z download link keep saying searching for mirror, please wait? Waited for 1 hr, no links. Refresh, no links.
thats odd I tried it yesterday and it worked
send a PM to the thread starter he will put up a new mirror I guess
1. Since the Galaxy S III became available as a Boost variant, there’s been an increasing amount of questions, issues, and requests for builds. I have collaborated with the powers that be, and it was determined that it might be a good idea to start a Boost only thread. This thread is dedicated to anything and everything Boost Galaxy S III related.
2. I will update and bump and sticky and edit and whatever else needs to be done the best that I can, but it is open and available to all. This is YOUR thread, just as much as it is mine. I encourage folks to ask questions, post relevant links, tutorials, helpful hints, and anything else they come across while tinkering with their new phone that may help others related to the Boost S3.
3. First and foremost, as always is the disclaimer. We are all responsible for our own actions. I am not responsible for what you do to your phone, so please do not flame me or anyone else in this thread if you do something that potentially fries your device.
4. If you post a link to something flashable, either through Odin, CWM, Heimdall, TWRP, etc, please test it on your own phone first or have someone test it before you do so. If it works, and will benefit someone, feel free to include it. I will most likely PM the dev and ask to put it in the OP.
5. And finally, please be courteous and respectful. We are all here to learn from one another, and do not need sarcasm, unkindness, flaming, or disrespect, of any kind. Thank you and enjoy.
Stock Unrooted OTA Odin Tar
This is the official, stock, right out of the box, Boost MD7. This will unroot your device, and take everything back to the way it was when you got it. Please thank the OP, Smith058, over at AF (link to OP at the bottom), since he was so gracious to let me post it here, and to let me use it to cook up something good for you folks More to come on that one! The only issue I’ve noticed on this build is there’s no boot up sound. But it flashed modem, stock recovery, put the device status back to “normal” and made the “custom” in Odin mode back to “official.” This should come in handy if you need to send it back for repair, or just want to start anew. The coming zip (once it’s uploaded) has working sound.
Stock MD7 Odin Tar Link https://mega.co.nz/#!ARkXGZCS!RITkIjvPnT51c6nyDdFvE2Z4oBNQt0PTcKnCGWuavdo
Link to Smith058’s OP(be sure to give him a shout out!)
http://androidforums.com/boost-mobile-galaxy-s3-all-things-root/753772-odin-backup-sph-l710_md7-stock.html
Stock OTA MG2 Tar:
http://www.androidfilehost.com/?fid=23212708291678209
Flashing Instructions:
1. Download and Install Odin to your PC
2. Download the ROM to your computer, and remember where you put it
3. Boot your phone into download(Odin) mode by pressing volume down, home button, and power button simultaneously
4. Once in Odin mode, connect your phone to your PC
5. Once the “COM” block turns blue, click the PDA button, and navigate to the ROM tar.
6. As a habit, I uncheck the F. Reset Time and Auto Reboot boxes as well
7. Click Start. When it’s done, pull the battery.
8. Reinsert battery, boot up, and profit
Links to Boost ROMs
Stock Rooted MD7 Flashable Zip -http://forum.xda-developers.com/showthread.php?t=2478888
Stock Unrooted MD7 Flashable Zip - http://forum.xda-developers.com/showthread.php?p=46367914#post46367914
Stock Rooted, Deodexed MG2 Zip - http://forum.xda-developers.com/showthread.php?p=47537971
One more, just to be on the safe side
jdsingle76 said:
The only issue I’ve noticed on this build is there’s no boot up sound. The coming zip (once it’s uploaded) has working sound.
Click to expand...
Click to collapse
My phone is running a rooted version of the stock MG2 ROM. While it has the Boost startup splash "4G" screen, I don't think there ever was a sound component.
Also - If I recall correctly, some custom ROMs labelled as compatible with the Sprint Galaxy S3 will cause us to LOSE 4G SERVICE, because they do not have the Boost-specific APN settings in them, and changing APN settings on Jellybean ROMs is (apparently) not possible as it was on Ice Cream Sandwich ROMs. So beware, and make sure that any ROMs that you want to flash will not kill your 4G!
SweetBearCub said:
My phone is running a rooted version of the stock MG2 ROM. While it has the Boost startup splash "4G" screen, I don't think there ever was a sound component.
Also - If I recall correctly, some custom ROMs labelled as compatible with the Sprint Galaxy S3 will cause us to LOSE 4G SERVICE, because they do not have the Boost-specific APN settings in them, and changing APN settings on Jellybean ROMs is (apparently) not possible as it was on Ice Cream Sandwich ROMs. So beware, and make sure that any ROMs that you want to flash will not kill your 4G!
Click to expand...
Click to collapse
I think it was an issue with the Tar, because when I built the flashable zips, they not only had the Boost animation, but the sound component as well. And I have seen around that some Sprint ROMs will cause issues with 4g. I know that it is possible to get into change the "guts" of your phone if you have your MSL by with JB Touchwiz ROMs by dialing ##3282# from your phone's dialer. However, for some reason, with the zip I just built, it's not cooperating. I'm going to swap out secphone.apk later today, from another stock build, and see if that fixes the issue. But thanks for the heads up. That's what this thread is all about.
I've been prompted for a system update... safe?
beneliezer said:
I've been prompted for a system update... safe?
Click to expand...
Click to collapse
If you flashed the rooted one, chances are it won't let you update, but give it a try. Additionally, if you have custom recovery, which you had to in order to flash the zip, it most likely won't let you update it either. It's an Android Software update, not a firmware. I would try it, and I'm sure it will fail, but at least you won't get prompted anymore for software updates But yes, it is safe to try.
jdsingle76 said:
If you flashed the rooted one, chances are it won't let you update, but give it a try. Additionally, if you have custom recovery, which you had to in order to flash the zip, it most likely won't let you update it either. It's an Android Software update, not a firmware. I would try it, and I'm sure it will fail, but at least you won't get prompted anymore for software updates But yes, it is safe to try.
Click to expand...
Click to collapse
jdsingle76 is correct. It won't hurt anything, it just won't work. If you accept the update, your phone will reboot into recovery, process for a few seconds, and fail with an error. However in my experience, that will not stop the software update prompts from re-occurring. If I recall, the best way to stop them was to use something like Titanium Backup and freeze something having to do with 'OTACERTS'. It's been a while, so my info may be out-of-date on that front.
can someone please reupload the stock SPH-L710 odin tar file else where before I brick my phone accidentally, its not letting me use recovery. The root method i used did not work correctly, now my phone is now working properly and i just want to get back to stock to try a different method for rooting, i need this odin file please!
nickdagreat said:
can someone please reupload the stock SPH-L710 odin tar file else where before I brick my phone accidentally, its not letting me use recovery. The root method i used did not work correctly, now my phone is now working properly and i just want to get back to stock to try a different method for rooting, i need this odin file please!
Click to expand...
Click to collapse
http://androidforums.com/boost-mob...backup-sph-l710_md7-stock-3.html#post6238089
Post #106
smith058 said:
http://androidforums.com/boost-mob...backup-sph-l710_md7-stock-3.html#post6238089
Post #106
Click to expand...
Click to collapse
Good to see ya bro. Thanks for throwing that up there. Just noticed the dropbox link was broken for too much traffic. I have the MG2 tar from Kies as well. This weekend if I get time I'll throw both of them in AFH and/or dev-host. Hope all's well, thanks for helping out!
J
Guys, i know this post is a little bit old, but i was wondering if I could flash this file with the Sprint Version (same one, SPH-L710) I know this will not harm my phone but I just want to make sure. is it safe?
erick1457 said:
Guys, i know this post is a little bit old, but i was wondering if I could flash this file with the Sprint Version (same one, SPH-L710) I know this will not harm my phone but I just want to make sure. is it safe?
Click to expand...
Click to collapse
What file from this op are you referring to? But to answer your question, yes, you can flash ant sprint file to the boost variant, and vice versa, you just might have to change apn, mmsc, stuff like that, to get mms to work.
Sent from my SPH-L710 using Tapatalk
Boost Stock 4.3
jdsingle76 said:
What file from this op are you referring to? But to answer your question, yes, you can flash ant sprint file to the boost variant, and vice versa, you just might have to change apn, mmsc, stuff like that, to get mms to work.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Thanks to all of u guys out there especially jdsingle76, Can anyone help with untouched Stock BoostMobile S3 4.3.tar ODIN ROM, i would be glad for any help in this regard, Meanwhile are we seeing Kitkat for BM S3? , Again is there a chance we can be KNOX free again in our lives?
alemosman said:
Thanks to all of u guys out there especially jdsingle76, Can anyone help with untouched Stock BoostMobile S3 4.3.tar ODIN ROM, i would be glad for any help in this regard, Meanwhile are we seeing Kitkat for BM S3? , Again is there a chance we can be KNOX free again in our lives?
Click to expand...
Click to collapse
I have not gotten my hands on a 4.3 Odin tar yet. If you do remember it'll have Knox, and I think Knox is here to stay. Ice heard rumors about Kit Kat for this phone but nothing's come out yet. Thanks for the support!
Sent from my SPH-L710 using Tapatalk
jdsingle76 said:
I have not gotten my hands on a 4.3 Odin tar yet. If you do remember it'll have Knox, and I think Knox is here to stay. Ice heard rumors about Kit Kat for this phone but nothing's come out yet. Thanks for the support!
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Thank you Jdsingle76, Boost Mobile are doing a hell of a job there keeping the 4.3 Odin tar under their sleeves.
Are your enjoying my build
Sent from my SPH-L710 using Tapatalk
knox scares me
knox bootloader scares me soo much that am still running stock unrooted, am afraid when i void my warrant i might not be able to upgrade to kitkat if it ever comes out
alemosman said:
knox bootloader scares me soo much that am still running stock unrooted, am afraid when i void my warrant i might not be able to upgrade to kitkat if it ever comes out
Click to expand...
Click to collapse
Don't fret. .. If kitkat comes out there will definitely be a custom rom made with it that you will be able to flash. With root you will have many more options than you ever will with stock.
Hey Guys,
I have read a burch of different threads about my problem and nothing has seemed to help or it was too advanced for me to understand. So here it is:
I tried to root my S3 and at first Oden 307 said the root failed, then i was able to try a different file and it said pass. but now when it boots up it gets stuck on the samsung galaxy s3 screen. I can still get into download mode and recovery mode. I have already tried the factory reset in recovery mode. Please help I have only had this phone a month. At this point I dont even care rooted or not I just want my phone back lol
Thanks for any help
+rep
garrett.burn said:
Hey Guys,
I have read a burch of different threads about my problem and nothing has seemed to help or it was too advanced for me to understand. So here it is:
I tried to root my S3 and at first Oden 307 said the root failed, then i was able to try a different file and it said pass. but now when it boots up it gets stuck on the samsung galaxy s3 screen. I can still get into download mode and recovery mode. I have already tried the factory reset in recovery mode. Please help I have only had this phone a month. At this point I dont even care rooted or not I just want my phone back lol
Thanks for any help
+rep
Click to expand...
Click to collapse
First you need to tell us which build you were on, and then what build did you try flashing...
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
BIGSAMDA1st, can I call you "Sam?" Your post count would indicate you've got more experience than I do so I thought I'd ask: aren't all the Sprint S3s on the MK3 build by default? Or are there inconsistencies within the Sprint-branded line of S3s?
Oh man. At least you've still got access to the download console. Can you also access the recovery console? Also, sounds like you're new to rooting (I could be wrong, just going on your comment about certain techniques being too advanced for you to wrap your head around). If you're new, you really picked both one hell of a time and one hell of a phone to cut your teeth on. Samsung's official 4.3 update (which, for all I know, is shipped standard now) comes with the KNOX bootloader which is, in certain situations, basically a bomb designed to ruin your week... and your phone. In particular, it has a REALLY nasty reaction to attempts at downgrading to the old (and much happier) bootloader. It also seems to really hate the older versions of TriangleAway (might hate the new one too, for all I know. I won't touch it anymore). It has other ways to make you hate life as well, but those are two big ones.
How to tell if you have the KNOX bootloader: Did you install the official OTA update to 4.3? If so, you've got the bomb. Did your phone come with 4.3 right out of the box? If so, you've probably got the bomb. Are you still unsure? Look in your Download console for red text that says something like "Warranty Void Bit" or anything that mentions KNOX. If so, you guessed it, you've got the bomb.
If you have the Warranty Void thing listed, then check to see: is it a 0, or is it a 1? If it's a zero, don't do anything else with trying to flash your ROM or root the device until we try some things in your Recovery Console (assuming it's also accessible). Once that flag is tripped, there's no going back... Not a huge deal if it's just a personal device, assuming you're not still under warranty... If you are, well, don't trip that bugger if you can avoid it.
FallenZen said:
BIGSAMDA1st, can I call you "Sam?" Your post count would indicate you've got more experience than I do so I thought I'd ask: aren't all the Sprint S3s on the MK3 build by default? Or are there inconsistencies within the Sprint-branded line of S3s?
Oh man. At least you've still got access to the download console. Can you also access the recovery console? Also, sounds like you're new to rooting (I could be wrong, just going on your comment about certain techniques being too advanced for you to wrap your head around). If you're new, you really picked both one hell of a time and one hell of a phone to cut your teeth on. Samsung's official 4.3 update (which, for all I know, is shipped standard now) comes with the KNOX bootloader which is, in certain situations, basically a bomb designed to ruin your week... and your phone. In particular, it has a REALLY nasty reaction to attempts at downgrading to the old (and much happier) bootloader. It also seems to really hate the older versions of TriangleAway (might hate the new one too, for all I know. I won't touch it anymore). It has other ways to make you hate life as well, but those are two big ones.
How to tell if you have the KNOX bootloader: Did you install the official OTA update to 4.3? If so, you've got the bomb. Did your phone come with 4.3 right out of the box? If so, you've probably got the bomb. Are you still unsure? Look in your Download console for red text that says something like "Warranty Void Bit" or anything that mentions KNOX. If so, you guessed it, you've got the bomb.
If you have the Warranty Void thing listed, then check to see: is it a 0, or is it a 1? If it's a zero, don't do anything else with trying to flash your ROM or root the device until we try some things in your Recovery Console (assuming it's also accessible). Once that flag is tripped, there's no going back... Not a huge deal if it's just a personal device, assuming you're not still under warranty... If you are, well, don't trip that bugger if you can avoid it.
Click to expand...
Click to collapse
First thing is THANK YOU and as i am a noob, where is the +rep button for you? Second and maybe you could help with this, since I posted this I was able to flash back to the official 4.3 :/ so I got my phone back but made my life harder in the process...I got clockwork recovery working and I was able to flash KNOX app remover .zip and I flashed team epic v5..it said everything was installed I rebooted and Im stll not rooted..Supersu says something about not having binary something another and root checker says I dont have root access. According to the step by step I followed I should be rooted :/ Any advise other than nex time dont upgrade to 4.3? lol
-Thanks Bro
BIGSAMDA1ST said:
First you need to tell us which build you were on, and then what build did you try flashing...
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
Im not quite sure what you are looking for but it says "Build Number JSS15J.L10VPUCMK3" And its a GS3 4.3 Model SPH-L710
Thanks for the reply
Hey mate,
I'm not familiar with the method of rooting 4.3 that you used. I'm glad to hear you got around the soft brick though! As far as running a rooted 4.3, I can tell you that what I wound up using was CNexus's pre-rooted ROM and the various fixes (s)he's compiled here:
http://forum.xda-developers.com/showthread.php?t=2541900
I've also shared my personal installation notes as well as hosted the files that worked for me on my Google Drive. That information is here:
http://forum.xda-developers.com/showthread.php?t=2560478&page=3
You shouldn't need the files I've got hosted on my Drive though... The ones CNexus has assembled in that thread should work just fine (that's where I got most of them, after all).
I cannot speak to whether or not any of the steps in my notes will trip your KNOX Warranty Void bit since I tripped mine (and damn near hard-bricked my phone) before I even knew what the KNOX bootloader was, let alone that Samsung had gone ahead and installed it for me.
I hope that helps.
-Zen
IM new to this and im not the brightest canyon in the box .
Ive read a bunch of tutorials ,downloaded odin , then after install cwm or team with odin which I have done . Even after installing when I goto recovery its still the normal stock recovery. when reading up on cwm they says your phone needs to be rooted for it to work. yet all of the forums and tutorials I have read say you need cwm or team to be able to install the supersu.zip.to root your phone.
This oxymoron in my mind makes me want to shoot myself in the head with the proverbial bullet.
blazingsun said:
IM new to this and im not the brightest canyon in the box .
Ive read a bunch of tutorials ,downloaded odin , then after install cwm or team with odin which I have done . Even after installing when I goto recovery its still the normal stock recovery. when reading up on cwm they says your phone needs to be rooted for it to work. yet all of the forums and tutorials I have read say you need cwm or team to be able to install the supersu.zip.to root your phone.
This oxymoron in my mind makes me want to shoot myself in the head with the proverbial bullet.
Click to expand...
Click to collapse
That's because c.w.m. needs root access to work properly. You need first to root your phone and then install the recovery. Try out the vroot chinese rooting toolkit, works on many devices.
I have tried vroot & kingo both says unsupported device
Man that looks like a tough phone to root but after a lot of research I found this:
http://honai-android.blogspot.ca/2013/09/how-to-root-galaxy-mega-63-lte-canadian.html?m=1
Try at your own risk but it does seem to work
Sent from my C5303 using xda app-developers app
Its looks promising however where I'm getting confuse is the part where all these tutorials say that you need to install the recovery first to be able to root your device. but on the other hand the recovery wont install properly unless your phone is rooted first.
To me this is turning into a real what came first the chicken or the egg .
blazingsun said:
Its looks promising however where I'm getting confuse is the part where all these tutorials say that you need to install the recovery first to be able to root your device. but on the other hand the recovery wont install properly unless your phone is rooted first.
To me this is turning into a real what came first the chicken or the egg .
Click to expand...
Click to collapse
As far as I know, installing a recovery before rooting ends up with a useless recovery. The recovery needs root access so it can work properly (e.g. installing custom roms).
To clear up a bit of confusion here you do not need root to install cwm through fastboot or Odin. That being said if you attempt to use cwm to flash a custom ROM without root it will fail as you do not have the permission to edit the system. This root method works by installing cwm through Odin without root then using cwm to flash a root patch thus giving you root permissions. It will not work on the american variant ( thank verision) but works on other variants.
Sent from my C5303 using xda app-developers app
After about a day of reading forum after forum I found a solution , probably wasn't the easiest method but it worked. I flashed a custom kernel then after that I was able to flash team recovery and boot the root file.
However the down side to this was I lost the ability to use wifi and screen capture. so now I have another problem to fix and like 80% of the noobs out their I didn't back up anything and to top it off this was my wife phone. ;= )
So the solution to this is two methods, either flash another custom kernel or find the stock modem for your phone, both are normally easy to come by unless you have a galaxy mega 6.3 i527m such as myself. However after 4 redbulls and a half of cup of coffee I found this.
http://forum.xda-developers.com/showthread.php?t=2461203&page=29
On this page the user name starmaster10 whip up a customer kernel ,modem to fix this issue.
so if you get stuck in a similar mess the key to recovery your wifi is make sure your modem baseband version match or flash a customer kernel.
The lesson to this story is happy wife happy life SO BACK YOUR PHONE BEFORE YOU START MESSING AROUND.
Thanks for everyone help
If you flashed a custom kernel then you bootloader must have been unlocked so you could have just adb pushed the su binary
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
yeah I had a feeling their was a simpler to do it. However I learnt how to trouble shoot some problems I may be able to help some other poor smuck with
lol well said
For myself it was knowing a little enough to cause damage
I upgraded to 4.4.2 on my TMobile Galaxy S4. I did this Via KIES. Afterwards, I tried to root - and this is where things seemed to go wrong.
I used ODIN 3.185, and used T-Mobile_OUDHS-Recovery-jfltetmo and then installed ROOT_M919UVUAMDL.
Since then, I have the
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Message at boot, and the Samsung Galaxy S4 logo.
I tried to use Odin to put over the top CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar
I tried also to use the SD card to update again to what I think is the stock firmware from here: http://forum.xda-developers.com/showpost.php?p=50977575&postcount=49&nocache=1&z=9496224221703208
When doing an update, there were a couple of errors - but it went through. However, on reboot the same error.
Any help would be extremely appreciated.
My next try is to do the unroot steps from this post: http://forum.xda-developers.com/showthread.php?t=2335109
But hopefully someone can give some more advice before I wipe the whole thing.
Since it's a work in progress, I figure I will post as I go along.
I downloaded the 1.5gb TMB-M919UVUFNB4-20140314115123 file from the unroot link above. I then used Odin to install it... and was able to stop at step 9 - before doing the data wipe/factory restore. I can now get my phone to boot.
I am feeling so good - that I'll try to root again.
Rooted, and SuperSU instaled - all is well to this point...
Since I was fairly freaked out, hopefully this helps someone down the line (or me - since I'm fast to forget).
You tripped the Knox flag. That's all that happened. It won't affect your ability to use the phone. You didn't do anything wrong. it's normal when you root a Knox protected device.
I ran into the same issue as you on my TMobile Samsung Galaxy S4 and I wanted to say thanks for this post! It helped me get my phone restored back to the way it was and thankfully I didn't lose anything! Thanks so much!
Was wondering however.....how did you get it to root successfully after this?
I used this guide to try to root my phone
http://www.androidrootz.com/2013/05/how-root-cwm-recovery-on-galaxy-s4-gt.html
Did you use another set of steps?
Thanks in advance!
0verfiend said:
Since it's a work in progress, I figure I will post as I go along.
I downloaded the 1.5gb TMB-M919UVUFNB4-20140314115123 file from the unroot link above. I then used Odin to install it... and was able to stop at step 9 - before doing the data wipe/factory restore. I can now get my phone to boot.
I am feeling so good - that I'll try to root again.
Click to expand...
Click to collapse
anoshwadia said:
I ran into the same issue as you on my TMobile Samsung Galaxy S4 and I wanted to say thanks for this post! It helped me get my phone restored back to the way it was and thankfully I didn't lose anything! Thanks so much!
Was wondering however.....how did you get it to root successfully after this?
I used this guide to try to root my phone
http://www.androidrootz.com/2013/05/how-root-cwm-recovery-on-galaxy-s4-gt.html
Did you use another set of steps?
Thanks in advance!
Click to expand...
Click to collapse
That procedure is so old and outdated, you should really pay attention to what you read and the sites you visit.. Everything you need is here on XDA.. Use cf-auto root to root the phone, do whatever you want afterwards..
Sent from my SGH-M919 using Tapatalk
Appreciate the response. I should have mentioned that I did start off at XDA. I used this thread
http://forum.xda-developers.com/showthread.php?t=2335109
....and it led me to use that link in my previous post. I figured since it was under the forums for my device and had been stickied, it would work fine. I didn't see anyone else on that thread report the issue I ran into, possibly because it worked prior to an update I had from Tmobile.
I will try your suggestions with cf-auto root. Thanks again for the help!
serio22 said:
That procedure is so old and outdated, you should really pay attention to what you read and the sites you visit.. Everything you need is here on XDA.. Use cf-auto root to root the phone, do whatever you want afterwards..
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Skipjacks said:
You tripped the Knox flag. That's all that happened. It won't affect your ability to use the phone. You didn't do anything wrong. it's normal when you root a Knox protected device.
Click to expand...
Click to collapse
Hi, is there a way to get rid of it?
I'm rooted and have TWRP 2.8 no problems, also I'm on Insanity V11 ROM, but those lines are too ugly :crying::crying::crying:
Railius said:
Hi, is there a way to get rid of it?
I'm rooted and have TWRP 2.8 no problems, also I'm on Insanity V11 ROM, but those lines are too ugly :crying::crying::crying:
Click to expand...
Click to collapse
Flash unmodified stock kernel