Related
I would like to root my SPH-L520 so I can flash it to Boost Mobile as a replacement for my long-in-the-tooth TP2. To do this, I followed a guide I found on andromods.com entitled "How to root Sprint Galaxy S4 mini (SPH-L520) running latest software version from OTA" (sorry, I don't have the permissions needed to post the link). My first step was to establish a USB connection between my SPH-L520 and my PC (Windows 7). You use Kies for that, right? Well, Kies would recognize that there was a SPH-L520 connected, but it wouldn't actually connect to it. It just kept saying “connecting” for half an hour. So I shot-off a support request to Samsung asking for the appropriate drivers for my phone (none are listed on the webpage for the device) and Samsung said there aren't any drivers for the SPH-L520. Kies does connect my SPH-L520 and my PC via WiFi, though, so I thought I’d try to go ahead and run the Kingo rooting program. So I enabled Developer Mode (by tapping on “Build Number” several times) and enabled USB Debugging and ran Kingo. Kingo connected but saw my Samsung device as being in “Normal Mode” (I’m guessing it should have said “Developer Mode”?). I went ahead and clicked on the "ROOT" button and my phone failed to root. I tried it several times and it failed every time. Phone stats are below. Any suggestions would be greatly appreciated.
Model number: SPH-L520
Android version: 4.2.2
Baseband version: L520VPUAMK2
Kernel version: 3.4.0-2054908
Build number: JDQ39.L520VPUAMK2
Problems Rooting SPH-L520 with Kies/Kingo
Any suggestions out there on how I can root my SPH-L520?
Problems Rooting SPH-L520 with Kies/Kingo
Anybody?
Problems Rooting SPH-L520 with Kies/Kingo
bump
SPH-L520
I have the s4 mini lte for sprint and rooted the phone with Kingo and didn't have any problems at all. However, I can't find ANY custom roms that are compatible with it due to the phone being fairly new. So yea, I've been impatiently waiting for a custom rom to download. If anyone knows where I can find one that doesn't have a ton of bugs, please let me know. Thanks
Butch31918 said:
I have the s4 mini lte for sprint and rooted the phone with Kingo and didn't have any problems at all. However, I can't find ANY custom roms that are compatible with it due to the phone being fairly new. So yea, I've been impatiently waiting for a custom rom to download. If anyone knows where I can find one that doesn't have a ton of bugs, please let me know. Thanks
Click to expand...
Click to collapse
How did you connect your phone to your computer so you could run Kingo? Did you use Kies or another program? For me, the Kingo program may work fine, but I won't know until I can get Kies to connect.
Problems Rooting SPH-L520 with Kies/Kingo
It finally rooted on the umpteenth try. I believe I disconnected/closed Kies and then ran Kingo and it worked. Now to find a good, easy way to flash it to Boost. Any advice on that would be appreciated.
foncall said:
It finally rooted on the umpteenth try. I believe I disconnected/closed Kies and then ran Kingo and it worked. Now to find a good, easy way to flash it to Boost. Any advice on that would be appreciated.
Click to expand...
Click to collapse
I'd also be really interested in this as well. Well flashing it too anything. I've been searching for HOURS. and have tried to get the MSL with no luck in any shape or form.
Hey guys, new member although I've lurked for a while. I have been searching up and down the last couple of days to find a way to get past KNOX and reroot my device. Me being kinda rustic and not thinking about it, accepted an OTA firmware update a few days ago. Of course I lost root access. What I didn't know about at the time was how big of a problem KNOX had become recently.Well, this firmware update introduced KNOX onto my device. I've heard stories of people being able to use Kingo and Saferoot on 4.2.2 and 4.3 after KNOX. This has not been the case with me, and I'm wondering if anyone has had success with this. Odin doesn't work either. I noticed that write protection is set as yes when in ODIN mode, and I suspect this is KNOX preventing changes to the ROM. As a result I haven't even been able to reflash the stock ROM image I have, whereas I have heard that you can reflash stock ROM's, but can't go backwards as far as version number. Thanks for your help in advance.
HansBlenkers said:
Hey guys, new member although I've lurked for a while. I have been searching up and down the last couple of days to find a way to get past KNOX and reroot my device. Me being kinda rustic and not thinking about it, accepted an OTA firmware update a few days ago. Of course I lost root access. What I didn't know about at the time was how big of a problem KNOX had become recently.Well, this firmware update introduced KNOX onto my device. I've heard stories of people being able to use Kingo and Saferoot on 4.2.2 and 4.3 after KNOX. This has not been the case with me, and I'm wondering if anyone has had success with this. Odin doesn't work either. I noticed that write protection is set as yes when in ODIN mode, and I suspect this is KNOX preventing changes to the ROM. As a result I haven't even been able to reflash the stock ROM image I have, whereas I have heard that you can reflash stock ROM's, but can't go backwards as far as version number. Thanks for your help in advance.
Click to expand...
Click to collapse
Flash anything with ODIN will trip the KNOX. Kingo is basing their root method on Saferoot, just with a GUI to make things simpler. And Saferoot should work with ROM that is before KK (4.4). If your OTA update is 4.4 than Saferoot won't work, since Saferoot is using a vulnerability prior 4.4 version. Does Kingo or Saferoot give any error message?
And just to double check, for both Saferoot or Kingo to work, you need to enable USB ADB and debugging mode.
TNCS said:
Flash anything with ODIN will trip the KNOX. Kingo is basing their root method on Saferoot, just with a GUI to make things simpler. And Saferoot should work with ROM that is before KK (4.4). If your OTA update is 4.4 than Saferoot won't work, since Saferoot is using a vulnerability prior 4.4 version. Does Kingo or Saferoot give any error message?
And just to double check, for both Saferoot or Kingo to work, you need to enable USB ADB and debugging mode.
Click to expand...
Click to collapse
Hey thanks for the reply. I do have USB ADB and debugging turned on. I've also tried reinstalling kies and the USB drivers them selves. I don't really care if an Odin flash trips Knox, as I don't think I have a warranty to worry about. The OTA update brought my firmware upto date , so I'm still on 4.2.2. This means that technically Saferoot or Kingo should work as advertised. This brings me back to the Write Protection set to Yes, and it's the only thing I could see preventing me from rooting my phone.
EDIT: Well I just found out that the Mini USB I use to charge my mouse started shorting other USB devices. Not like short then come back on, it was so bad every port on the computer shut down and I had to restart to get them working again. It was also the cable I was using to plug my phone in. Will update again when I try another cable.
EDIT 2: Just tried with the cable I usually use for charging my phone. No change on Kingo, still get a Root Failed, Need Root error.
HansBlenkers said:
Hey thanks for the reply. I do have USB ADB and debugging turned on. I've also tried reinstalling kies and the USB drivers them selves. I don't really care if an Odin flash trips Knox, as I don't think I have a warranty to worry about. The OTA update brought my firmware upto date , so I'm still on 4.2.2. This means that technically Saferoot or Kingo should work as advertised. This brings me back to the Write Protection set to Yes, and it's the only thing I could see preventing me from rooting my phone.
EDIT: Well I just found out that the Mini USB I use to charge my mouse started shorting other USB devices. Not like short then come back on, it was so bad every port on the computer shut down and I had to restart to get them working again. It was also the cable I was using to plug my phone in. Will update again when I try another cable.
EDIT 2: Just tried with the cable I usually use for charging my phone. No change on Kingo, still get a Root Failed, Need Root error.
Click to expand...
Click to collapse
At this stage I can only suggest to try on a different PC (use don't need Kies, just the Samsung driver will do) with a cable that your are 100% sure it working. If it still not working, my only guess is your network provider enable a looked boot loader in the OTA update you just did (hence the Write Protection flag). If that the case, nothing can be done at this point.
Same Boat
Im in the same boat did realize that KNOX would change so much. I need to reroot so hopefully someone can figure it out without tripping knox.
It fails because of the Security notice....Unauthorized access to a secured area has been blocked. Tap to learn more. If you notice when you check USB debugging, look below at Verify apps via USB. It is checked and grayed out. It isn't checked when USB debugging is off. I don't know how this was circumvented on the S4. But I'm peeved I let the update happen. They conveniently left out any info about security, and I'm tempted to return the phone and get one that hasn't been updated. Figure they weren't forthcoming about what the update contained so I can raise enough stink, get an old phone, download the update, pass it off to someone who can hopefully pull everything but the bootloader and create a tar to flash via odin. If that's possible and someone is willing to do it. If I had another spare line, I'd get another phone to donate for the cause.
I think if we're on Knox we need Odin to Root because anything that gets transferred via USB will be blocked. I even tried rootkeeper, and it was blocked.
The tough part is, unless it's a premium phone, it's not getting the level of dev support we're used to (well I'm used to...haha). Rooting through odin, custom recovery....used to taking it for granted. And with Sprint EOL'ing the phone, it's not really going to gain any momentum, though I did only pay 99 cents for it on a spare line. Kinda ticks me off Samsung has gone this direction when they used to be so dev friendly. Almost enough to make the S4 my last Samsung.
TNCS said:
At this stage I can only suggest to try on a different PC (use don't need Kies, just the Samsung driver will do) with a cable that your are 100% sure it working. If it still not working, my only guess is your network provider enable a looked boot loader in the OTA update you just did (hence the Write Protection flag). If that the case, nothing can be done at this point.
Click to expand...
Click to collapse
the concern is not tripping knox from the bootloader perspective. The problem is the knox security app that can't be removed without root. So for everyone that has OTA updated to NA7, going the odin route to root is the only option as far as I know. I know I don't care about tripping the counter. I just want control back of my phone. And the only way to do that at the moment is to return it for a pre knox version which I'm apt to do at the moment since there is a lack of development, and the ones that are developing don't even have the phone. Kudos to them, but there's not much help once you've updated to NA7. And unfortunately, the update doesn't tell you it's locking down your phone. Then you're stuck in a quandary, because the update also provides updates for Spark, so unless someone does a dump of the download and someone can pick it apart and provide a zip sans Knox, we'll have to deal with a stock phone.
dbpaddler said:
the concern is not tripping knox from the bootloader perspective. The problem is the knox security app that can't be removed without root. So for everyone that has OTA updated to NA7, going the odin route to root is the only option as far as I know. I know I don't care about tripping the counter. I just want control back of my phone. And the only way to do that at the moment is to return it for a pre knox version which I'm apt to do at the moment since there is a lack of development, and the ones that are developing don't even have the phone. Kudos to them, but there's not much help once you've updated to NA7. And unfortunately, the update doesn't tell you it's locking down your phone. Then you're stuck in a quandary, because the update also provides updates for Spark, so unless someone does a dump of the download and someone can pick it apart and provide a zip sans Knox, we'll have to deal with a stock phone.
Click to expand...
Click to collapse
I was (after a good bit of tinkering, and deleting my modem on accident) able to install CWM and flash a CW11 version s0be is currently developing, and it's working pretty well as far as I can tell. Unfortunately, due to the lack of support on this forsaken Sprint device, I haven't been able to find a modem I can flash onto the damned thing to get it working properly again. I don't advise the route I took, firstly because of the effort it took, but I also damned near bricked it about 5 different times, and needed to use a Linux VM. Also, because of the lack of developers on this thing, if you delete your modem and A: don't have a friend (brother in my case, has same phone) you can pull a modem.bin off of and B: don't know how to build that .bin into a working .zip or a flashable tar.md5 you might get stuck with an unusable device at the end of the day. Really, the only thing Knox has done for us is complicate things a hell of a lot more than they need to be. Although, tbh, that might (most likely) have been my stupidity that deleted the modem. In any case, check it (s0be's CM11 development) out, it's coming along nicely. Just be careful with it.
........
thank you very mach
Hello
Specifically, I would like to know if someone has N750 device and successfully rooted his device! The reason I'm doing this thread is because when I had 4.3 android versions, I tried that CF auto root via Odin program and it bricked my phone. Fortunately, I was able to get my original firmware again from a specific site for samsung devices. [Egypt version, because obviously, I live in Egypt]. Now, My device has been updated to 4.4.2 and I have currently the kitkat version without any problems BUT, I want to root my phone in order to use Xpose Framework;
I want the best advice to follow for my device because I do not have the heart to take another chance since I'm not a professional programmer nor a professional developer to deal with such bricks. It was a lucky chance when I had my OS back, but I do not know what would happen in the future.
I tested many one click root softwares on PC and most of them either stuck or tell me 'successfully' without any **** in my phone. Just rebooting like an idiot and nothing happened.
Sorry for my annoying thread. It's my first post here and I hope you guys understand my English well since it's not my Native Language. Apologize another time.
Peace, Ahmed.
Phoenix 1337 said:
Hello
Specifically, I would like to know if someone has N750 device and successfully rooted his device! The reason I'm doing this thread is because when I had 4.3 android versions, I tried that CF auto root via Odin program and it bricked my phone. Fortunately, I was able to get my original firmware again from a specific site for samsung devices. [Egypt version, because obviously, I live in Egypt]. Now, My device has been updated to 4.4.2 and I have currently the kitkat version without any problems BUT, I want to root my phone in order to use Xpose Framework;
I want the best advice to follow for my device because I do not have the heart to take another chance since I'm not a professional programmer nor a professional developer to deal with such bricks. It was a lucky chance when I had my OS back, but I do not know what would happen in the future.
I tested many one click root softwares on PC and most of them either stuck or tell me 'successfully' without any **** in my phone. Just rebooting like an idiot and nothing happened.
Sorry for my annoying thread. It's my first post here and I hope you guys understand my English well since it's not my Native Language. Apologize another time.
Peace, Ahmed.
Click to expand...
Click to collapse
If you flash cf auto root for 4.4.2 base on 4.3, your device is bricked. If you make rooted. Find compatible os and model cf auto root files.
I'm just wondering if it's safe to rollback the firmware on my Galaxy Tab S 10.5" to the previous one or if it causes some sort of conflict.
I want to do so because I've just installed the most recent one (T800ODD1ANK1 - India) and I can't root it using Cf-Autoroot posted here.
Thanks!
What happens when you try to root it?
DUHAsianSKILLZ said:
What happens when you try to root it?
Click to expand...
Click to collapse
Nothing. I did it with Odin and it just reboots to the same old unrooted tablet. All is working fine as usual, but no root.
What botters me the most is that I had Xposed framework installed but now it has no functionality and all the modules I had installed don't work. I would install the previous firmware but I'm afraid of breaking something, with installing older software on top of newer one.
I was able to root the US version of that ROM (T800XXU1ANK1) using CF Auto Root from Chainfire:
http://download.chainfire.eu/473/CF...uto-Root-chagallwifi-chagallwifixx-smt800.zip
Perhaps give that a shot???
I will but the India version has a more recent changelist (which was the reason why I chose to install it).
Thanks in advance.
As I predicted, since the changelist is different (your version has the same as the older one I had, with functioning root, but not with this one), no root.
Does anyone know if it is safe to install a previous version of the software? Like, for example, Cellular South ANK1 (with an older changelist).
Thanks.
Itchiee said:
I was able to root the US version of that ROM (T800XXU1ANK1) using CF Auto Root from Chainfire:
http://download.chainfire.eu/473/CF...uto-Root-chagallwifi-chagallwifixx-smt800.zip
Perhaps give that a shot???
Click to expand...
Click to collapse
I'm having the same issue as the original poster. It says I am rooted, but I'm not because root checker just keeps spinning and there isn't a SU# icon in my apps. I've done this with Odin about a million times before, for some reason on my new T800 (after I updated the software), it doesn't work.
Am I missing a step because I have the same version you have? Extract the file. Load the md5 file into AP. Hit Start. Wait for it to reboot. Right?
Yea root isn't working for me with T800XXU1ANK1. =(
Im assuming you ran Super SU and updated the binaries or whatever it asks, or updated the app in playstore?
Ive done nothing different and root works fine.
I was thinking about another root alternative. I was thinking about downloading the supersu zip and save it to the device or sd card. Then flash twrp recovery with odin, then boot into recovery and flash the supersu zip to get root? Could that work as an alternative since it flashes root in the process?
I just rolled back to T800XXU1ANJ6 and I am rooted.
I just bought a Tab S, and I can't seem to find an answer to a question that relates to this thread. Is there any advantage to updating before rooting?
I can't decide if I should root it now or update the software, and then root. After searching some, it appears that it doesn't matter whether I upgrade or not, but I can't seem to find if there is any advantage to updating it then rooting. Like, is it easier to get the latest firmware that way?
PeterGunz said:
I just bought a Tab S, and I can't seem to find an answer to a question that relates to this thread. Is there any advantage to updating before rooting?
I can't decide if I should root it now or update the software, and then root. After searching some, it appears that it doesn't matter whether I upgrade or not, but I can't seem to find if there is any advantage to updating it then rooting. Like, is it easier to get the latest firmware that way?
Click to expand...
Click to collapse
If i am correct, There should be stock custom roms available that are prerooted so you can flash over. As for an ota update, that is faster than being rooted then flashing lollipop rom.
Anyway we have a lollipop rom already built. Its smooth and most things are working. Its really cool and id rather use this than waiting for samsung to get the latest update out. Do you have the 10.5 in or 8.4 inch?
DUHAsianSKILLZ said:
If i am correct, There should be stock custom roms available that are prerooted so you can flash over. As for an ota update, that is faster than being rooted then flashing lollipop rom.
Anyway we have a lollipop rom already built. Its smooth and most things are working. Its really cool and id rather use this than waiting for samsung to get the latest update out. Do you have the 10.5 in or 8.4 inch?
Click to expand...
Click to collapse
I have the wifi 10.5 inch.
So, you are saying update OTA then root, unless I want to jump to Lollipop (which I do), which in that case it doesn't matter so I should just root and flash a lollipop rom?
Thanks for helping me out.
PeterGunz said:
I have the wifi 10.5 inch.
So, you are saying update OTA then root, unless I want to jump to Lollipop (which I do), which in that case it doesn't matter so I should just root and flash a lollipop rom?
Thanks for helping me out.
Click to expand...
Click to collapse
Up to you If you want to jump to lollipop/CM12, just run flash Cfautoroot( with odin to root) then install twrp and flash the lollipop rom. There is a thread for cm12/lollipop in the development tab s section.
But wait! Rooting trips knox with voids your warranty. Same users has reported getting service from samsung for free of charge from defective units and some had to pay to get defective parts replaced by samsung. 50/50 chance. I took the risk and havent got a hardbrick or anything yet.
Regards
DUHAsianSKILLZ said:
Up to you If you want to jump to lollipop/CM12, just run flash Cfautoroot( with odin to root) then install twrp and flash the lollipop rom. There is a thread for cm12/lollipop in the development tab s section.
But wait! Rooting trips knox with voids your warranty. Same users has reported getting service from samsung for free of charge from defective units and some had to pay to get defective parts replaced by samsung. 50/50 chance. I took the risk and havent got a hardbrick or anything yet.
Regards
Click to expand...
Click to collapse
Thank you for the heads-up. I've rooted all 6 of my android phones that I've had, so I'm not too worried about voiding the watrranty. Judging by your reply it sounds like there are a lot of lemons out there for this device. Mine seems to be running okay, but I just can't take all the lag that I assume comes from TW and bloatware. My HTC One M8 with Lollipop seems faster and smoother than my Tab S at stock. Although after typing the last sentence, I put Nova on there and sped up all the animations and it is definitely light years faster than my One M8 now.
I think the answer to the original post is that the Su binary was installed, but the op didn't download then update Super su after rooting. You wont get full root until you do as there is no app to handle root requests.
Ok, so I recently got my S3 running. It's a temporary phone while I save for a Note 4, but I want to see how it handles Marshmallow and get it fully working on Tracfone's network. The big catch is that my phone's USB port is fairly busted. I can sort of charge with it, but it's flaky. I have no plans to fix it since this phone isn't going to be my primary for long.
I'm wanting to know if it's possible to go from stock to running CyanogenMod 13 nightly without use of ODIN or anything USB.
I believe the first step will be to get TWRP installed. I found a guide that uses Rashr to do this, but I will need to root my phone without USB first. Will Framaroot work on a i747?
Ok, looks like Framaroot doesn't have our i747 listed as a supported device, but I did find this guide that uses Towelroot. I'm going to try that.
http://www.jellydroid.com/2014/07/how-to-root-samsung-galaxy-s-iii-sgh-i747-without-computer/
Welp, ran into a snag with Towelroot, gives me an incompatible error.
Did some searching and found "Towelroot will only work for NE6 firmware on the I747M. The exploit it uses was patched in NF1/NF2.
you can try cf autoroot, or just flash recovery then flash SuperSU." -DocHoliday77
Anyone know any other non-USB rooting options? I believe my firmware is NJ2.
Ok, I have a theory. I'm new to the Android world, but what if we treat my phone like it's bricked and can't use ODIN. Could I use the default recovery to flash the phone over to NE6 stock build, then use Towelroot to root it, then use Flashify or Rashr or something of the like to install TWRP? I know it's a bit of a run around, but it seems like a path forward.
Hm, no. It seems the unbricking process is dependant on ODIN. So I guess if I care enough to do this I need to solder a new port on. :/
The odd thing is that my phone will charge through a "dumb" charger, it's just an older LG charger, but on the smancy Samsung chargers or my PC it won't even try. I suspect it's because the LG charger just provides power while the Samsung ones do some talking first.