It was a driver issue as stated below.
I am going to assist with all my knowledge, hopefully, someone which is way more knowledgeable will glance here as well.
As per your concern on ODIN, I believe it's a mobile drivers issue, you need the sufficient samsung drivers to run and flash with ODIN with success.
If you have the drivers and want to root, your glide will be downgraded to 2.3.5 for the pre-rooted ROMs are on that firmware version and the available methods of rooting so far is only available for flashing those pre-rooted stock ROMs. There is also a method flashing only the insecure.so file but it is too technical for me to perform and explain.
I downloaded and installed the samsung drivers and they appeared to be the same as what windows auto installs for the device, i'll try xp next...
Any updates on this?
nothing so far, I definitely have a different recovery screen than those in videos, so i'm wondering if they didn't patch the software in a way that blocks ODIN access but doesn't undo root if it's already happened...
my desktop wasn't reading the right drivers, and i had to roll back the drivers on my laptop to get the new (correct) drivers to install, all is good now, i'm CIQ free!
Related
Hi, I just bought my SIII 2 weeks ago and I heard that there is a process just like jailbreaking on the iPhone called rooting. I just switched from apple because it sucked and gave me no freedom (not to mention I love widgets). So I want to root my phone but for some reason, my Windows Vista won't recognize it (yes, I already installed the drivers and reinstalled them). So how can I root my phone without connecting it to the computer. I can connect to Kies via Wi-fi. Also, what does rooting do to your phone. I am a Java programmer, so I don't think it will be too complex for me. Would the root remain once the Jelly Bean 4.1 update came to the Galaxy SIII?
1. What does rooting do?
2. How can I root my phone without connecting to the computer
3. Would the root stay if I updated to Jelly Bean?
http://forum.xda-developers.com/showthread.php?t=1746665
easiest way..to root etc,, but again gotta be connected to ur pc,,. also try and re-install the drivers and use the usb cable that came with the phone..
As far as I know. u need a pc to root etc..
and never take a ota update while rooted.. etc.. just wait til a rooted version of said update is released then flash it...
No one can tell ya how to do these things.. like everything else research and read,, is the best way.. to learn,, plus im sure there are a million youtube how to vids also... I have been rooting androids since the htc hero.. and never once had a brick.. same for flashing roms in the old days of windows mobile.. go slow and read and you should be ok...
http://forum.xda-developers.com/showthread.php?t=1739426
[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
That forum gives you a step by step guide how to root your.. there's a program called Odin that you need but you'll see all that when you read it.. everything is in the first few posts as far as how to do it..
Rooting gives you access to the root folders of the phone.. it allows for removal of bloatware, overclocking/underclocking, undervolting etc..
It also allows you to run custom ROMs.. I've been running a jelly bean ROM for weeks now.
As far as ota updates you would actually have to download them now if you change the recovery (which is required for flashing ROMs) if you leave the stock recovery you should be OK to still receive ota updates..
Most people on here root for performance reasons (better performance, battery battery life) but many also root to use custom ROMs that are enhanced over the stock ones or to get the newest OS faster than waiting for your carrier to release it. Some roms are called aokp/aosp which is basically stock android with no touchwiz its what you would get on a nexus device from Google.. on this phone however aokp/aosp will remove alot of the stock functionality such as swipe for a screen shot, smart stay, direct call, etc.. there are apps that imitate the lost features but rarely are they as fluid and properly functioning as the stock features built into the device..
But with that said to each their own. Make sure you read and read and read what your doing or you can end up with a nice $600 paper weight that is now void of a warranty.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I rooted my phone using the method outlined in this thread here:
http://forum.xda-developers.com/showthread.php?t=1771687
I used odin to flash the 4.1.2 T-Mobile image and I stopped at the part that said "If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE" because I only wanted root so I could fix the keyboard bug (keyboard would revert to stock one after resets).
So my question is, can I update to 4.3 via the OTA update that is in the About Device > Software Update section in the phone? Looking elsewhere the official instructions say that the phone should not be rooted before updating. If so, can I get rid of the root in order to update? (As far as I know, the keyboard bug doesn't exist in 4.3 anyway so I don't think I need the root anymore). If not, how can I update to 4.3?
Lastly, and somewhat unrelated, can I use the factory data reset in the Back up and reset section of the settings? Previously in my experience with roms, this would lead to a boot loop but I'm not sure if that is the case with this so-called rooted stock rom.
Thanks in advance.
You can use OTA RootKeeper to temporarily disable Root so that you will receive the update. Or you could also visit the Root66 thread you have linked. There you will see Rooted version of the 4.3 update.
Having said that, You will want to Research the consequences of the 4.3 Stock update. In particular you wish to research the consequences of CIQ, KNOX and the new EFuse Bootloader.
I am by no means an expert but I figure I just did this so it may help you out. I updated my phone to 4.3 accidentally on purpose and then I decided to root my phone like the next day. I used Mr Robinson's method and then used his third method to download the ROM manager and install CWM Recovery and then I put Cyanogen on it. I have not had any issues except the app Trailer Addict doesn't work with it but that is not a big issue. I have everything else that I wanted and more. I don't care about the flash counter since I am not under warranty. Oh and you can use Titanium Backup to back up your apps. I didn't do this the first time so I had to back up from Kies 3 by dragging files onto my SD card and not all worked. I hope I helped a little.
I recently had my LG G2 stolen from me and have had to go back to the trust p930. I am using bell variant in canada and its on GB 2.3.5. I cannot for the life of me figure out how to root it. I can't update it with B2Cappsetup because everytime I try to open that it says "Need to connect to internet". My drivers are always "not found even though I've downloaded LG mobile unite drivers from their site and OTA updates say I have latest verion. Sigh. Anyone able to tell a half baked noob how to achieve root and CWM/TWRP in the easiest way known? WOuld be a huge help
butthurtlocker said:
I recently had my LG G2 stolen from me and have had to go back to the trust p930. I am using bell variant in canada and its on GB 2.3.5. I cannot for the life of me figure out how to root it. I can't update it with B2Cappsetup because everytime I try to open that it says "Need to connect to internet". My drivers are always "not found even though I've downloaded LG mobile unite drivers from their site and OTA updates say I have latest verion. Sigh. Anyone able to tell a half baked noob how to achieve root and CWM/TWRP in the easiest way known? WOuld be a huge help
Click to expand...
Click to collapse
In order to root it you have to have the drivers installed so try installing the drivers on another pc or try to figure the problem. If you just want it rooted and nothing more (Custom ROM, Recovery, or Kernel), then use Bi4nary's root. If you want a custom ROM, Recovery, or Kernel, then you have to 'Unbrick' and I would suggest you use hereric's method. Both of them work perfectly
Truepeace said:
In order to root it you have to have the drivers installed so try installing the drivers on another pc or try to figure the problem. If you just want it rooted and nothing more (Custom ROM, Recovery, or Kernel), then use Bi4nary's root. If you want a custom ROM, Recovery, or Kernel, then you have to 'Unbrick' and I would suggest you use hereric's method. Both of them work perfectly
Click to expand...
Click to collapse
SO I couldn't just root with something easy like superoneclick then Just download TWRP from goo manager and flash roms through that? I HAVE to do that long complicated guide? I definetly am too noob to follow that, I can't even open Bc2appsetup for some reason let alone the rest of it!
Superoneclick will work to root this phone. As others have experienced, it takes one shot or multiple tries to get it rooted. IRC, I had to also install the Android SDK package before it got rooted.
BUT, if you just bought that phone as used it might be already rooted so check that first before you waste your time.
butthurtlocker said:
SO I couldn't just root with something easy like superoneclick then Just download TWRP from goo manager and flash roms through that? I HAVE to do that long complicated guide? I definetly am too noob to follow that, I can't even open Bc2appsetup for some reason let alone the rest of it!
Click to expand...
Click to collapse
Oh yes I guess superoneclick will work for gingerbread. I personnally had ICS.
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
Samsung Galaxy SIII SGH-I747M Build No. KOT49H.I747MVLUFOB3 Android Ver. 4.4.2 Kernel Ver. 3.4.0-1784548
Have backed up personal files but not system, yet.
Phone unlocked from Rogers (Canada) carrier and rooted using Kingo App.
Have installed Root checker, Rom Manager, Busy Box, Super Su and have downloaded the firmware[ I747MVLUFOB3_I747MOYAFOB3_RWC.zip. ] to have on hand.
I rooted the phone because everything I had read to date [which may not have been enough] told me rooting was necessary. Would like to install a more up to date android than 4.4.2, possibly 5.0 or 6.0. Also, to get rid of Apps I never use. Because I see so much in my reading about Cyanogenmod, I thought I would start with 12 and go from there.
Have been trying to follow steps at the link for https wiki cyanogenmod org/w/d2att_Info which I believe is the correct one for my model number, which has led me to the link at https wiki cyanogenmod org/w/Install_CM_for_d2lte where it tells me that:
Rooting the stock firmware is neither recommended nor necessary
Click to expand...
Click to collapse
Firstly, I am just wondering,
1a] since I still have the original firmware installed, could I just unroot with the same Kingo App I used to root the phone?
1b] Would/Can I still use Rom Manager to do my system backup?
Secondly, if it is not too technical an explanation, why is it that the Rogers(Canada) i747m does not need nor is it recommended to be rooted? It almost sounds as if it already is or maybe rogers firmware is weak and easily hacked?
Thirdly, just a comment on my part, as interesting and good as this whole process is, it seems that rooting and installing new firmware can be a bit of a Pandora's box and the people who are developing things to do so are very diligent and creative.
I am still determined to make this happen with my i747m and am thankful for people on this forum and others to advise me.
To install a custom rom, you need to install a custom recovery to install the custom rom.
Rooting gives you access to the rom system files, similar to gaining administrative privilege on a Windows or Mac machine.
Rooting is not required before installing a custom recovery or custom rom.
I have never heard that that the Rogers i747m should not be rooted. For security and stability purposes, rooting any phone is not recommended by many people.
I am not familiar with the program that was used to root the phone but each program usually has an option to unroot.
I am not 100% certain as I haven't used a rom manager in years but I don't think the option to create nandroid exists.