Related
Currently running version 4.3 stock and i have a problem, my charging port is currently damage so i can't plug it in to the computer to root. Is there some kind of way i can root my device by flashing some kind of custom recovery without using a computer or something. PLEASE HELP ME IF YOU HAVE ANY IDEA HOW I CAN ROOT THIS DEVICE CAUSE I FOUND NOTHING
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
I have tried many methods which do not flash your device ( towelroot, poot,etc ), and I have tried some of the others: Kingo and Odin.
None of these methods work with the Samsung Galaxy S4 Mini ATT running 4.4.2. All of the .apk attempts result in saying " Your device is not currently supported " or just not working. I have made many attempts with Odin, with many different types of files, all of which have ended in saying " Failure ". I really want to root my phone so I can remove all of my bloatware and really use my device. Any help will be appreciated.
May have your service provider, AT&T, prevented the phone from being rooted?
RoyaLKurTx3 said:
May have your service provider, AT&T, prevented the phone from being rooted?
Click to expand...
Click to collapse
I can provide any information to see if my provider has done something to my phone to prevent it from being rooted.
Rooted with king root
I was able to root my at&t s4 mini using king root. I had to do a factory reset so my phone was stock with no software updates.
I just got my G4 Unlocked international H815 model. It's running 5.1 software on ATT. It keeps bugging me trying to OTA software update. Not sure what it's trying to update to exactly, because the only way to see more info is to hit continue with update and there's no turning back from there.
I love this phone unlocked! it didn't have any bloatware I usually root to delete when I get my phone from the carrier. It's got stuff like Wifi hotspot stock and the FM radio and charges over QI instead of Powercrap ... etc.
My question is
if it's already got most of the stuff I root to access, do I let the OTA update happen and risk not being able to root?
not sure what all I'd gain.
I'm wary about rooting because my last phone was the LG G3 and I rooted it and despite me disabling all update processes, it updated itself one day on my way to work and got screwed up so bad I had to force a downgrade and put a rom on it and after a couple days of holding a 600$ paperweight, I finally got it up and running on a rom... still had some bugs but it worked.
I REALLY want to avoid that nightmare with this 3 day old phone.
opinions welcome!
Thanks
Are you saying it's already rooted? If it is, the OTA won't work anyway. You have to unroot and flash the update using LG bridge. but then you can just root it again using the same method. The update doesn't block root. Lots of us have done it. Read the rooting threads.
G4 TweaksBox. One reason to root. ^_^
Adaway, no more adverts in apps. another (big for me) reason to root.
What version are you on now? It's probably only the stagefright fix.
Root...flash TWRP...flash cyanogen 12.1
Install xposed framework and get the YouTube adaway module. That's deffo a reason to ROOT.
Hally79 said:
Root...flash TWRP...flash cyanogen 12.1
Install xposed framework and get the YouTube adaway module. That's deffo a reason to ROOT.
Click to expand...
Click to collapse
You need an unlocked bootloader to flash TWRP / CM.
I'm running stock v10d + root. Works awesomely.
Juzman said:
You need an unlocked bootloader to flash TWRP / CM.
I'm running stock v10d + root. Works awesomely.
Click to expand...
Click to collapse
Yeah the guy said he had unlocked international h815, if he has I was just suggesting flashing CM
That's my DD and it is awesome
Hally79 said:
Yeah the guy said he had unlocked international h815, if he has I was just suggesting flashing CM
That's my DD and it is awesome
Click to expand...
Click to collapse
Yes mine's unlocked, NOT rooted. apparently the update it was trying to do automatically wasn't a big update because it decided it had waited long enough and did it on its own, rebooted and its still at
5.1
I'm still trying to wrap my head around all the terminology and methods of rooting droids- I came from the dark side- I've jailbroken every iphone since the first one they ever produced. My G3 was my first real phone, but like I said, I had it for a couple months stock, rooted it, and almost immediately it went kamikaze OTA update while rooted and went haywire. I limped by with a mediocre rom for another 8 months, until some drunk A Hole destroyed it on Halloween. I may or may not be said A Hole haha
So I guess now my question is, once rooted, am I stuck at 5.1 forever with no security updates, software patches ETC?
and since most people don't have a true unlocked phone, is this process easier to do? I'm probably asking in the wrong forum section now aren't I?
I sure hope at this point if you truly have an unlocked bootloader, that you have the latest MM version 20B installed and have root! - I find that the stock ROM is the best performing and least buggy of any of them (with some minor tweakin)
Unable to Unlock BootLoader. SOS!!!
Hi guys! need a lil help here. I have LG G4 H815. Now this is what's happening :
1. I have tried t install LG drivers a million times but in the device manager, there's always some problem with them during the installation.
2. Therefore, I'm unable to locate my phone using 'adb devices'. I'm stuck on this first step for last 1 week and I have tried every available lg driver on the internet but still the result is same.
3. I'm using Windows 8 Pro.
What's the solution here guys? Your help will highly be appreciated.
you need "disable driver signature verification" to install it
(advanced reboot options from windows)
Still stuck!
skdubg said:
you need "disable driver signature verification" to install it
(advanced reboot options from windows)
Click to expand...
Click to collapse
I did as you said and disabled the driver signature verification at restart. Uninstalled the driver and installed again but still the problem persists.
When I connect the phone, LGE Android phone appears with a yellow question mark in the device manager. When I try to update the driver, it says that
"Windows found driver software for your device but encountered an error while attempting to install it.
MTP USB Device.
The system cannot find the file specified."
Still can't locate the device with adb. Please help me!
However bootloader unlock is not available for the H815P... :/
Sent from my LG-H815 using XDA-Developers mobile app
But...but...
But sir, my phone is H-815, not H-815P.
Please help me where I'm making the mistake. I want to root my phone but nothing is helping me out.
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.