I have seen all the posts about being able to root Lolipop 5.0.1 with Kingroot. When I try this on my phone, it fails over and over. Any suggestions?
I've tried everything I can think of and tried what others have suggested. I can't get the apk or the windows version to work. Personally I'm a bit leary of Kingroot anyway.
Sent from my SCH-I545 using XDA Free mobile app
At least you are not the only one having the problem as I thought I was.
If you're on OF1, I believe Kingroot isnt working currently. OC1 works from experience and people on the forums on the desktop. Check your build number. If on OC1, maybe you didn't turn on USB debugging?
I wish I could say it was something as simple as USB debugging. I'm on OC1 and took the update from 4.4.2 via Kies. That was my fault. My understanding was by doing that or taking the OTA update from Verizon it permenantly locks the bootloader.
I've tried every version of Kingmaster...apk will get to 52% and stop. The only thing I can think of is that I have not clicked the correct buttons on the PC version which is very possible. I have yet to find any English instructions for it. If anyone has them detailed please send.
Thanks
Sent from my SCH-I545 using XDA Free mobile app
real4life72 said:
I wish I could say it was something as simple as USB debugging. I'm on OC1 and took the update from 4.4.2 via Kies. That was my fault. My understanding was by doing that or taking the OTA update from Verizon it permenantly locks the bootloader.
I've tried every version of Kingmaster...apk will get to 52% and stop. The only thing I can think of is that I have not clicked the correct buttons on the PC version which is very possible. I have yet to find any English instructions for it. If anyone has them detailed please send.
Thanks
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
I get the same thing. Kingroot gets to around 50% and then quits. I do feel that nothing is permanent, and with all the savvy techies out there, someone will figure out some sort of exploit. It is unfair for Verizon to lock down their phones to discourage people from switching carriers.
Well, read the EULA..
That said, Kingroot is still hit and miss.on OC1. OF1 came out in the past few weeks so I wouldn't expect anything for atleast a month.
Yep. It's unfortunate. For me, the reason I need to root is that I can't send texts with Tmo Simi a Verizon phone. This only happens on Tmo 4G. When signal drops to 3G or E, I can send text. I thought I would switch the antenna setting to stay on 3G. There is another post about this workaround somewhere on this forum.
Oh well. Maybe I'll find someone to trade me for a Tmobile S4.
Hello, I've tried running the apk of KingRoot on OC1 and it gets to usually 33% before its done so no root here either. I tried to download the desktop version and it won't even come up, so I guess we're stuck for now. I'm like a few others here, I don't fully trust KingRoot so I hope someone way smarter than me can come up with a program to root!
fudplayers said:
Hello, I've tried running the apk of KingRoot on OC1 and it gets to usually 33% before its done so no root here either. I tried to download the desktop version and it won't even come up, so I guess we're stuck for now. I'm like a few others here, I don't fully trust KingRoot so I hope someone way smarter than me can come up with a program to root!
Click to expand...
Click to collapse
I tested on my OC1, KingRoot is working perfectly. I can't root it initially, but after changing another computer it works brilliantly this morning
Lots of people have talked about success with OC1 and Kingroot. Doesn't appear to work with OF1 though.
Sounds great...can you let us know the exact steps? I'll give it another shot. For me I guess since it's not in English I have found it tough.
Thanks
Sent from my SCH-I545 using XDA Free mobile app
real4life72 said:
Sounds great...can you let us know the exact steps? I'll give it another shot. For me I guess since it's not in English I have found it tough.
Thanks
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
I was in the same boat a week or so ago. I had been rooted but had a problem trying to flash another rom. I had to Odin back to stock but when I tried to root again the kingroot app no longer works. This is what worked for me. I went to the kingroot site and let Google translate the home page. You have to download the root installer zip, which to me, was the hardest part. I just used trial and error by clicking on boxes on the installer page until I got it downloaded. If needed I can download it again and post the methods, step by step.
Sent from my Kindle Fire HDX 8.9 using XDA Free mobile app
I'll give it another look. I tried Google Translate but it's still doesn't completely translate. ..at least for me. I just find it odd that there is not at least clear English instructions somewhere. Even if it was just a listing of screen shots.
Sent from my SCH-I545 using XDA Free mobile app
Initially I was having the same issue while using KingRoot. This was what I did to make it work:
1. Uninstall KingRoot, restart your computer
2. Re-download kingroot from kingroot.net, choose " [windows logo] 下载电脑版本 "
3. Install KingRoot, run it
4. Turn on I545 usb debugging, plug in to your computer and you will see kingroot is running.
5. After loading you will see some chinese words 尚未Root。。。。。 or 发现新的root档案 。。。。 etc, click on the green button to start rooting and you will get it done.
6. I successfully have done more than 300pc I545 yesterday, however, sometimes if it keeps on loading without rooting what you need to do is to restart your computer and re-do it again
I can understand chinese, you may show me picture if you need me to translate
I'm going to try that method when I get home from work today. The app doesn't work for me and the desktop I was having issues with but resolved those by uninstalling KingRoot then downloading it again . It ran that time but never rooted, must've ran the desktop version close to 10 times with no luck. The program tried to root, it would run for about 5-10 minutes then it would show a pic of a phone with a red X on the screen, no root.
I think this is the problem...I see no green button when Kingroot loads and I've plugged my phone in.
Sent from my SCH-I545 using XDA Free mobile app
I tried again probably 15 times. Uninstalled,reinstalled,shut down PC several times, it just does not work. I don't know what's going on but I can't get it to root. The desktop version gets to about 60% every time before saying no root. Once again a no go but I am curious to see if anyone else is still being successful at it. I almost thought that maybe Kingroot took down the root for the S4 for some reason, not sure why they'd do that but its a possibility I guess.
Kingroot worked for me...
fudplayers said:
I tried again probably 15 times. Uninstalled,reinstalled,shut down PC several times, it just does not work. I don't know what's going on but I can't get it to root. The desktop version gets to about 60% every time before saying no root. Once again a no go but I am curious to see if anyone else is still being successful at it. I almost thought that maybe Kingroot took down the root for the S4 for some reason, not sure why they'd do that but its a possibility I guess.
Click to expand...
Click to collapse
i got my S4 like 2 months ago with of course lollipop 5.0.1 installed and I had to try rooting via Kingroot several times before the root was successful except now i soft-bricked de-rooting to install an update. I believe i read somewhere to keep trying and it eventually works, i used the PC version of Kingroot. Good luck
smartcellmobile said:
Initially I was having the same issue while using KingRoot. This was what I did to make it work:
1. Uninstall KingRoot, restart your computer
2. Re-download kingroot from kingroot.net, choose " [windows logo] 下载电脑版本 "
3. Install KingRoot, run it
4. Turn on I545 usb debugging, plug in to your computer and you will see kingroot is running.
5. After loading you will see some chinese words 尚未Root。。。。。 or 发现新的root档案 。。。。 etc, click on the green button to start rooting and you will get it done.
6. I successfully have done more than 300pc I545 yesterday, however, sometimes if it keeps on loading without rooting what you need to do is to restart your computer and re-do it again
I can understand chinese, you may show me picture if you need me to translate
Click to expand...
Click to collapse
Hi, I'm having issues with step 5. There isn't any green button that comes up. The first time I run the kingroot after reinstalling it, it shows just a blue button after thinking for several seconds.
(I can't figure out how to attach an image to my post, and apperently links aren't allowed either...) i.imgur.com/8BilQtT.png
After clicking the blue button, it goes to this screen: i.imgur.com/wScf2TT.png
There's a checkmark there, but my phone is not rooted. It did install KrHelper4Pc to my phone though.
Subsequent runs of kingroot (without reinstalling) show this after thinking for several seconds: i.imgur.com/HVmqOLm.png
I've tried this several times and the exact same thing happens each time.
Related
A few days ago I accidentally deleted my messaging app(mms.apk), I looked everywhere for a solution to get it back, I couldn't find anything other than downloading a messaging app for the Android Marketplace, I just decided to restore my phone from the backup I made about ten days ago, I did. Then I decided I just wanted to reset & unroot my phone, I downloaded an unroot file, opened it up using Odin, then started to unroot my phone, a few minutes into the process it said, "Fail!", so I clicked reset and unplugged my phone & tried to boot it, it was stuck at the boot screen for about ten minutes, so then I rerooted it using a root file & Odin, it did it successfully. But now when I turn my phone on it says. "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can acess Odin mode as well, but that's all I can do, Kies can't connect to the phone.
Also, I have to plug unplug the USB a few times before the computer recognizes it.
I need help really bad, I've only had the phone for about two months. D:
Sladdon said:
Yesterday I accidentally deleted my mms.apk, I could not find any solutions to get it back other than downloading a messaging app from the Marketplace, so I restored a backup I made about ten days ago, then I decided that I just wanted to unroot my phone and completely start over, I used Odin and an unroot file to unroot it, about 2 or 3 minutes in it said "Fail!", I attempted to turn on my phone, it was stuck at the startup screen, then I tried it again, same thing, then I rerooted it, and unrooted, and just kept doing that, now when I turn it on it says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." It will not connect to Kies. I can access CWM(I think that's what it is), how can I fix it? I really need help, I'm currently using a Samsung Solstice or something, and it's just horrible.
Thanks.
EDIT: & I have to unplug and plug the USB back into the computer a bunch before it will recognize it(I have the drivers installed).
Click to expand...
Click to collapse
If the phone screen is turning on, it's not bricked.
Try to look for the stock rom
Sent from my HTC Glacier using xda premium
Sladdon said:
then I decided that I just wanted to unroot my phone and completely start over, I used Odin and an unroot file to unroot it, about 2 or 3 minutes in it said "Fail!"
Click to expand...
Click to collapse
May be able to help you but need to know what exactly you flashed that caused Odin to fail. Also need to know what you used to root your phone. And Specifically what the contents of the tar files are for those two packages.
creepyncrawly said:
May be able to help you but need to know what exactly you flashed that caused Odin to fail. Also need to know what you used to root your phone. And Specifically what the contents of the tar files are for those two packages.
Click to expand...
Click to collapse
Any unroot I try to put on it, it doesn't work.
Sladdon said:
Any unroot I try to put on it, it doesn't work.
Click to expand...
Click to collapse
It is impossible to troubleshoot your problem without information. As I said above I may be able to help you but i need to know what exactly you flashed that caused Odin to fail. Also I need to know what you used to root your phone. And Specifically what the contents of the tar files are for those two packages.
That will be a start at least.
creepyncrawly said:
It is impossible to troubleshoot your problem without information. As I said above I may be able to help you but i need to know what exactly you flashed that caused Odin to fail. Also I need to know what you used to root your phone. And Specifically what the contents of the tar files are for those two packages.
That will be a start at least.
Click to expand...
Click to collapse
Alright, but before I tell you that, I don't have USB Debugging on, and I have no way of turning it on through my phone, unless there's a way to turn it on without being able to get on my phone, could this be why the new firmwares, etc. won't install using Odin?
Sladdon said:
Alright, but before I tell you that, I don't have USB Debugging on, and I have no way of turning it on through my phone, unless there's a way to turn it on without being able to get on my phone, could this be why the new firmwares, etc. won't install using Odin?
Click to expand...
Click to collapse
No.
USB Debugging is irrelevant when you are in download mode.
creepyncrawly said:
No.
USB Debugging is irrelevant when you are in download mode.
Click to expand...
Click to collapse
Okay good, but still, nothing seems to work, I need someone to Teamviwer with me.
Sladdon said:
Okay good, but still, nothing seems to work, I need someone to Teamviwer with me.
Click to expand...
Click to collapse
As I told you, I will be happy to try to help you get your phone back. But...
I can't help you if you won't tell me what you have done.
creepyncrawly said:
As I told you, I will be happy to try to help you get your phone back. But...
I can't help you if you won't tell me what you have done.
Click to expand...
Click to collapse
I'm not sure what I used to root it the very first time, I used ATTGalaxyS2Unroot_SGH-i777 http://gyazo.com/41cd5a9600ea4c21b223e1fff7513595 to unroot it(I THINK), I downloaded a few, then it messed up, froze at the startup screen, so I downloaded a root file, once again, I think it was this one, but could have been the other one I downloaded, http://gyazo.com/7412924c18a7bdf386ee2fee57c025d3, here's all the files I have, I didn't use them all, but I have them, http://gyazo.com/a9e126d653d4e29c5da04e505a8e37de.
Hopefully that can help you.
And also, I think I already mentioned it, but I have to unplug and plug back in my phone a bunch before it finally recognizes it, and when it does recognize it every time it installs the driver again as if it were a new device.
EDIT: Here's what it says 90% of the time when I plug it in.. http://gyazo.com/288b9e6a613e5348e91b15482ccbcebf
Im running stock Gingerbread, never been rooted.
What I am looking for is a simple one click method to root the phone for a few minutes so I can make a few tweaks and then unroot it.
Yes, Im aware that I can use the Odin method to root without tripping the flash counter, make my tweaks, and then use another Odin package to unroot it, however, there are a few problems with this, in order to keep this brief, I dont want to go into all the details but suffice it to say, I dont want root constantly enabled, I just want to enable it briefly and I dont want to install CWM so I can reset the flash counter and then (if its even possible) have to re-install the 3e recovery menu EVERY time I need root for something briefly.
Im looking for something along the lines of Super One Click (shortfuse.org) or UnlockRoot (www.unlockroot.com) where I can hit root, the phone reboots, I do what I need to do, hit unroot and the phone reboots unrooted. Both of these tools, needless to say, do NOT work (even tho they are listed as supported devices). Remember also, this is the ATT Note SGH-I717 so when looking thru the device lists supported by other software, make sure to look for the right Note .
i don't think those methods exist like they did with say the Samsung infuse. I used the Odin way, just as easy as super one click...but you mentioned you didn't want to use it so I'm not sure what you can do. Why not just stay rooted? And there is a flash counter reset just so you know
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I used odin super fast and easy
Sent from my SAMSUNG-SGH-I717 using xda premium
Im well aware of how easy the pre-rooted kernel is to flash via Odin, its the unrooting process that is a pain.
I dont want to stay rooted and I dont want to use Odin, the process of reverting back to unrooted is too much of a pain in the ass.
My guess is that there is no easy one click process or it would have been posted already.
Its a shame, one of the huge benefits with Android was how easy it was to gain root to tweak OS level things and then revert back to an unrooted state.
I used SuperOneClick without any issues whatsoever? What, is it not supposed to work or something?
juzz86 said:
I used SuperOneClick without any issues whatsoever? What, is it not supposed to work or something?
Click to expand...
Click to collapse
Erm, ok, Id love to know how you did...
First, what phone do you have (carrier). I am using the ATT Note.
If we are on the same page there, what settings do I need to enable on the phone and/or SuperOneClick?
On my phone, I enabled USB Debugging, in SuperOneClick, I left everything default, I click the Root button and on step 7 a bunch of gobbly gook appears (there is no log created so I cant just copy and paste some of the text) and it just stops. I left it sitting for a few minutes and nothing happened to either the phone or SuperOneClick.
littlewierdo said:
Erm, ok, Id love to know how you did...
First, what phone do you have (carrier). I am using the ATT Note.
If we are on the same page there, what settings do I need to enable on the phone and/or SuperOneClick?
On my phone, I enabled USB Debugging, in SuperOneClick, I left everything default, I click the Root button and on step 7 a bunch of gobbly gook appears (there is no log created so I cant just copy and paste some of the text) and it just stops. I left it sitting for a few minutes and nothing happened to either the phone or SuperOneClick.
Click to expand...
Click to collapse
I have two Notes. The N7000 I rooted using SoC on GB, doing exactly what you've done. The i717 was exactly the same. USB debugging enabled, plugged in and USB not mounted. MY computer is picky about USB ports so I use the same port and cable for every phone.
Grab the latest SoC (my sig has a link) and extract. Install Kies to get the USB drivers, then uninstall Kies and leave the drivers installed. Plug in the phone and let it install. Once it's done, run SoC (not as an administrator), select 'auto' for the exploit and click 'root'.
You'll get the usual 'found a gingerbread', 'sending 149 zerglings' etc. Then it tells you the 'overseer found a path' and after a few more steps reboots with root. Took me all of about 40 seconds.
I use AT&T phones unlocked in Australia, so we are using the same handset. This method doesn't work for ICS, you'll need to flash SU with CWM for that.
Let me know if I can help any more
Yea, unfortunately, it doesnt work for me.
I have the Samsung drivers installed (I know because when I plug in my phone under device manager, it shows my phone as correctly installed and I get a pop up from windows asking me whether I want to open a folder to browse the phones' contents - and Kies sees the phone).
I even tried uninstalling Kies but keeping the driver installed (Windows still asks me whether I want to browse the phone contents).
I also tried removing the sd card, altho this should not affect the process.
When I run SOC, I maximize the window so I can read the text and basically, when it gets to step 7, it sends 149 zerglings, then it waits 40 seconds, then it sends 189 zerglings, waits 40 seconds, then it says that it doesnt have write permissions and asks me whether I have root or not (not in a dialog box but in the text on the right hand side of the screen - I can only assume that it is initially trying to get a shell/temporary root so that it can do what it needs to for a permanent root), then it tries to push some files to the phone and then just completely stops. I let it sit for Id say 10 minutes with no progress.
The only thing that maybe is creating a problem is that the phone seems to be automounting, when I plug in the storage, it doesnt ask me what I want to do, it just mounts the device. I poked around in the settings and couldnt find any setting to disable this but Im not 100% sure this is a problem as the Captivate did the same, when you enabled USB debugging, it would automount the device.
Oh, and when I plug in the USB cable, the notifications bar shows 'MTP Initializing' and a few seconds later, 'MTP Mode'.
And Im using Super One Click version 2.3.3
littlewierdo said:
Im running stock Gingerbread, never been rooted.
What I am looking for is a simple one click method to root the phone for a few minutes so I can make a few tweaks and then unroot it.
Yes, Im aware that I can use the Odin method to root without tripping the flash counter, make my tweaks, and then use another Odin package to unroot it, however, there are a few problems with this, in order to keep this brief, I dont want to go into all the details but suffice it to say, I dont want root constantly enabled, I just want to enable it briefly and I dont want to install CWM so I can reset the flash counter and then (if its even possible) have to re-install the 3e recovery menu EVERY time I need root for something briefly.
Im looking for something along the lines of Super One Click (shortfuse.org) or UnlockRoot (www.unlockroot.com) where I can hit root, the phone reboots, I do what I need to do, hit unroot and the phone reboots unrooted. Both of these tools, needless to say, do NOT work (even tho they are listed as supported devices). Remember also, this is the ATT Note SGH-I717 so when looking thru the device lists supported by other software, make sure to look for the right Note .
Click to expand...
Click to collapse
Did you ever get a working solution to your question? I am in the same position: wanting to temporarily root my phone, do my tweaks and then re-root it so that I can run the POS enterprise mail application that has a policy to check for "root".
I would think that this should be much easier than it seems, but perhaps not
Thanks,
aus
I havent found any solutions yet...
SuperOneClick did not work for me either. I have used it on 3 other phones with no issue so I dunno.
I have tried to root my phone 3 separate times now over the past 3 months. Each time it never works. I have tried the ragaw root method and some root method that goes through the windows .exe, they just dont work. Ragaw will either 1) Freeze before the root me button appears, 2) not recognize phone 3) will sit there saying "starting adb server...". The other .exe method does absolutely nothing besides tell me that adb is not working, daemeon isnt connected, will connect now. Over and over again. Yes I have updated drivers on my computer, yes I have put my phone back to factory settings, My firmware is 2.13.651.1, and I have USB debugging on. I have spent hours combing through threads seeing absolutely nothing. I don't understand why it isnt working as I rooted my old OG Evo like 5 times, no problems. Can someone please help me before I throw my computer and my phone out of a window.
Check out om4 guide don't panic...all phones root
Sent from my EVO using xda premium
---------- Post added at 03:14 AM ---------- Previous post was at 03:12 AM ----------
http://forum.xda-developers.com/showthread.php?p=31102864
Sent from my EVO using xda premium
iHusk said:
I have tried to root my phone 3 separate times now over the past 3 months. Each time it never works. I have tried the ragaw root method and some root method that goes through the windows .exe, they just dont work. Ragaw will either 1) Freeze before the root me button appears, 2) not recognize phone 3) will sit there saying "starting adb server...". The other .exe method does absolutely nothing besides tell me that adb is not working, daemeon isnt connected, will connect now. Over and over again. Yes I have updated drivers on my computer, yes I have put my phone back to factory settings, My firmware is 2.13.651.1, and I have USB debugging on. I have spent hours combing through threads seeing absolutely nothing. I don't understand why it isnt working as I rooted my old OG Evo like 5 times, no problems. Can someone please help me before I throw my computer and my phone out of a window.
Click to expand...
Click to collapse
Do you have Net 4.0 installed that is one of the requirements for Regaw method and I noticed you didn't mention it?
Defenetly not impossible man its android
Sent from my Nexus 7 using Tapatalk 2
bigdaddy619 said:
Do you have Net 4.0 installed that is one of the requirements for Regaw method and I noticed you didn't mention it?
Click to expand...
Click to collapse
Yes Net 4.0 is installed. I followed all of the directions. I can normally figure this stuff out, but this is ridiculous. Dont understand it at all
Heres what it normally does. It goes further sometimes, others it does not. idk what to do.
http://www.youtube.com/watch?v=0T8RBBwgHtk
iHusk said:
Yes Net 4.0 is installed. I followed all of the directions. I can normally figure this stuff out, but this is ridiculous. Dont understand it at all
Heres what it normally does. It goes further sometimes, others it does not. idk what to do.
http://www.youtube.com/watch?v=0T8RBBwgHtk
Click to expand...
Click to collapse
I used this video by qbking77 to root then used the regawmod to get custom recovery good luck
http://www.youtube.com/watch?v=B9pzFqtn6aM&feature=plcp
iHusk said:
I have tried to root my phone 3 separate times now over the past 3 months. Each time it never works. I have tried the ragaw root method and some root method that goes through the windows .exe, they just dont work. Ragaw will either 1) Freeze before the root me button appears, 2) not recognize phone 3) will sit there saying "starting adb server...". The other .exe method does absolutely nothing besides tell me that adb is not working, daemeon isnt connected, will connect now. Over and over again. Yes I have updated drivers on my computer, yes I have put my phone back to factory settings, My firmware is 2.13.651.1, and I have USB debugging on. I have spent hours combing through threads seeing absolutely nothing. I don't understand why it isnt working as I rooted my old OG Evo like 5 times, no problems. Can someone please help me before I throw my computer and my phone out of a window.
Click to expand...
Click to collapse
Did u install adb tools as well? U should make sure your path is set for it properly. Had an issue where adb couldbt see my phone and it was the path.
Try uninstalling everything HTC and all rooting programs including adb toolbox. Make sure u get good downloads and reinstall everything again. It sounds stupid, but if you calm down and just do it I am pretty sure it will root. Believe!
This has been an issue for a lot of people and uninstalling drivers, etc., then deleting them, download & install again solved the problem.
Your phone is rootable. Working on it makes it fun. U learn when u make mistakes, think of it as an opportunity and not a frustrating hassle...
Well... did regaw method at least UNLOCK your bootloader? If so.. why not just fastboot flash a custom recovery (TWRP) and flash a rooted rom? You can flash a stock rooted rom if you're looking to stay pure stock. I think Captain Throwback put one up on the new base and theres one from Haus on the older base.
Hello guys, since the last tutorial I posted was really popular I decided to post another one for my other phone, the LG G2. You don't even need to use any command prompt for this. The only problem is that this is chinese language, so you have to click the exact buttons.
1. Download this file: https://tr.im/64637 <--- HELP ME! OR http://goo.gl/U6Jwaf
2. Install the software, using the installation buttons as you would on any other windows installation.
3. When you have installed it, you will see a green button, press it. Then connect your phone.
4. When the phone is connected the software will recognize the phone and the green button will show "ROOT", click on it.
5. The phone is going to be rooted in some seconds and the process is finished when it will show a tick on the software.
6. The phone will reboot.
7. When it is rebooted, go to google play and download super su.
8. Open super su and it will ask you to update the binaries, and you must click on update, and then normal.
9. A window in chinese will pop up on the phone, this is the screen that allows you to give root permissions to any app. You must click the button on the right.
10. You are done! Root process is complete!
11. This is the most important step. Leave a thanks! If you liked the tutorial, please show it to me!
EXTRA: Video for "visual" learners!
https://www.youtube.com/watch?v=FYE15dugKxk
Post below if you have questions or don't understand.
EDIT: I know you guys might not trust this, but I used it and it worked perfectly. There aren't any problems with this root, and there are no viruses on my PC that I know of. And I regularly scan my PC.
If you want to see my other thread, about 100 people replied and most of them successfully rooted their phone!
I believe that this isn't a virus. If you don't want to use it, don't. But trust me it works and nothing happened to me!
aristide1997 said:
Hello guys, since the last tutorial I posted was really popular I decided to post another one for my other phone, the LG G2. You don't even need to use any command prompt for this. The only problem is that this is chinese language, so you have to click the exact buttons.
1. Download this file: http://goo.gl/Vq5SNs <--- HELP ME! OR http://goo.gl/U6Jwaf
2. Install the software, using the installation buttons as you would on any other windows installation.
3. When you have installed it, you will see a green button, press it. Then connect your phone.
4. When the phone is connected the software will recognize the phone and the green button will show "ROOT", click on it.
5. The phone is going to be rooted in some seconds and the process is finished when it will show a tick on the software.
6. The phone will reboot.
7. When it is rebooted, go to google play and download super su.
8. Open super su and it will ask you to update the binaries, and you must click on update, and then normal.
9. A window in chinese will pop up on the phone, this is the screen that allows you to give root permissions to any app. You must click the button on the right.
10. You are done! Root process is complete!
11. This is the most important step. Leave a thanks! If you liked the tutorial, please show it to me!
EXTRA: Video for "visual" learners!
COMING SOON
Post below if you have questions or don't understand.
Click to expand...
Click to collapse
See This and This
ioroot ftw.
There is no chance in hell of me trusting this.
Sent from my VS980 4G using Tapatalk
I know you guys might not trust this, but I used it and it worked perfectly. There aren't any problems with this root, and there are no viruses on my PC that I know of. And I regularly scan my PC.
If you want to see my other thread, about 100 people replied and most of them successfully rooted their phone!
I believe that this isn't a virus. If you don't want to use it, don't. But trust me it works and nothing happened to me!
Yet. There may be no viruses on your PC, but what if your data has been harvested.
Actually... nevermind.
aristide1997 said:
I know you guys might not trust this, but I used it and it worked perfectly. There aren't any problems with this root, and there are no viruses on my PC that I know of. And I regularly scan my PC.
If you want to see my other thread, about 100 people replied and most of them successfully rooted their phone!
I believe that this isn't a virus. If you don't want to use it, don't. But trust me it works and nothing happened to me!
Click to expand...
Click to collapse
I don't think the issue is that this may be a virus. But, the root process gathers critical phone information (IMEI ans serial number) and sends it back to a server.
eejimen said:
I don't think the issue is that this may be a virus. But, the root process gathers critical phone information (IMEI ans serial number) and sends it back to a server.
Click to expand...
Click to collapse
Yeah may be, I don't think so, nothing bad has happened to my IMEI or Serial. I still think that you can use this, because many thousands have and none have reported anything bad. What if the data being sent was only information for statistical purpose?
I just used it on the latest update d80010q and worked great. Ioroot did not work. Thanks for posting!
ls430cw said:
I just used it on the latest update d80010q and worked great. Ioroot did not work. Thanks for posting!
Click to expand...
Click to collapse
works great thanks
No problem guys!
Just an update on the VROOT/KINGO rooting program.
We have been in contact wit KINGO Software and have received the following response..
Once we received your letter, we realized the seriousness of this whole IMEI issue and we removed it from our code right away.
Click to expand...
Click to collapse
Again this was from KINGO not VROOT.
VROOT has not been in contact with us.
USE THIS SOFTWARE AT YOUR OWN RISK.
I suggest using the newest version of KINGO if no XDA developed method works.
In past versions of both softwares there was XDA dev's work (without credits)
If you use this and find out that someone on the other side of the world has a phone with your IMEI # and your phone no longer works, then you have been warned.
Toledo_JAB said:
Just an update on the VROOT/KINGO rooting program.
We have been in contact wit KINGO Software and have received the following response..
Again this was from KINGO not VROOT.
VROOT has not been in contact with us.
USE THIS SOFTWARE AT YOUR OWN RISK.
I suggest using the newest version of KINGO if no XDA developed method works.
In past versions of both softwares there was XDA dev's work (without credits)
If you use this and find out that someone on the other side of the world has a phone with your IMEI # and your phone no longer works, then you have been warned.
Click to expand...
Click to collapse
I think that VROOT aswell will take it away if we ask them... but anyway I don't really think they are going to do something bad with the IMEIs..
aristide1997 said:
I think that VROOT aswell will take it away if we ask them... but anyway I don't really think they are going to do something bad with the IMEIs..
Click to expand...
Click to collapse
We did ask already
We had contacted both KINGO & VROOT at the same time.
Kingo has been responsive and made the necessary changes to comply with the XDA rules.
We have not heard ANYTHING from VROOT.
At that time both software's were the same (almost identical). We were thinking that they are a part of the same group.
I still recommend that you use a method developed here on XDA, or the newest version of Kingo's software
However it is your choice.
Thanks for the cooperation on this matter,
Toledo_JAB
Toledo_JAB said:
We did ask already
We had contacted both KINGO & VROOT at the same time.
Kingo has been responsive and made the necessary changes to comply with the XDA rules.
We have not heard ANYTHING from VROOT.
At that time both software's were the same (almost identical). We were thinking that they are a part of the same group.
I still recommend that you use a method developed here on XDA, or the newest version of Kingo's software
However it is your choice.
Thanks for the cooperation on this matter,
Toledo_JAB
Click to expand...
Click to collapse
Yes I have noted similiarities within the two websites... I really hope that VROOT proceedes to take the IMEI down aswell... although I really don't think that something bad is going to happen; many people have done it and until now there haven't been reports of IMEI misuse... I could be wrong though they may do it in the future, but for now i think it's safe.
Anyone else tried it?
Why don't people just use towelroot?
- download app from Internet
- install on phone
- start app
- click the button "make it rain"
- finished, you just got root
EDIT: Adding what I did to solve this at the bottom.
Hey everyone. Thanks for your time. I'm new to this forum and in a bit of a panic as this is the first time my phone's been so far gone I couldn't find an easy guide to fixing it. I'm not exactly clueless but I'd say I know enough to get myself in trouble, and this time not enough to get myself out. I'll give you the rundown.
Phone:
SCH-I545
Verizon Galaxy S4
Last stable version of Android was 4.4.2
I wish I had the build numbers or anything but since I was using official tools I didn't take any backup steps
Computer:
Macbook Pro Late 2013
OSX Yosemite 10.10.3
(I also have access to a Windows 7/LinuxMint dual boot machine if needed)
Using OEM USB cable connected directly into the USB on the motherboard.
Until yesterday my S4 was happily running 4.4.2, when I received a notification of a new update. I ran both Verizon updates that came through. The first one finished fine, the second one (the actual Lolipop update) kept failing in the bootloader type screen (Odin mode?). It would look like an android on his back with 'Error!' written out then restart to 4.4.2.
I did a bit of reading and found out that if your phone was rooted and unrooted, it may not take the OTA update. I recalled that I used a one-click style, app-based root a while back, and quickly reverted it because I didn't end up needing root anyway. (I think the logo for the rooter apk was a Greek letter but that's all I remember. It's on my SD card still. If it would be useful I can figure out a way to read the SD card through another phone or adapter or something and figure out the name. I think it was Towelroot but not positive)
So as I researched how to do the update, I read a post that said the Verizon Software Upgrade Assistant would do the job just fine. I figured, since it's a Verizon branded application, I couldn't go wrong. Well, that's where the trouble started.
Everything looked to be going according to plan. The Verizon assistant downloaded the Lollipop update and then began to install it. It booted the phone into what I think is Odin mode and said "Downloading... Do not turn off target!!"
Somewhere in the first third (going by the progress bar) a message popped up on my Mac saying that the phone was unplugged (it wasn't). My phone now displayed a message stating "Software update failed. Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update."
Naturally, I attempted to use the Verizon Software Repair Assistant (seems to be part of the same application as the updater) and to my horror found that every time I plug in my phone, the Verizon app crashes immediately! No matter what I do; plug in the phone then open the app, open the app then plug in the phone, app in update mode, app in repair mode, etc., I cannot get the application to keep running when the phone is attached to my Mac. This might be where I did the most damage to myself... In my attempts to clear the crash issue and get the Verizon app working, I clicked something to the effect of "Forget this device" in the Verizon app and all info about my phone was gone. I'm now thinking that included my chance of repairing the broken update, and Kies needs some code to repair from and I think I lost that with the clear
I have not tried the Verizon application on Windows because I can't find it to download it (the phone itself installs the application when you plug it in, but my phone is fried and can't help me right now.) Luckily my wife also has an S4 so when she get's home, I'll be able to try the Verizon application for Windows and see if that can repair.
What I have tried:
Installing Kies on both Mac and Windows and connecting the phone in both "Software Update Failed" mode by simply powering the device on, and in "Downloading..." mode by holding Vol Dwn while powering the device, then saying yes to the confirmation.
I also tried Odin on Windows following this guide – http://forum.xda-developers.com/showthread.php?t=2301259 and I received a missing PIT error.
I found a PIT file and tried it, with the supplied file from the guide, in Odin, but that ends up disconnecting the phone after a second then ending with an error and reconnecting the phone. It wasn't a very descriptive error but I can get more specifics if needed.
Took it to a Verizon store, wasted thirty minutes of my life, left with the same problem and more anger.
At this point I don't want to do more damage so I would really appreciate some advice on how to approach fixing this.
I'd be happy to take any advice and give any further info. Hopefully one of you guys can help me here.
Thanks again for your time and thanks for anyone that might help!!
–––
RESOLUTION
So I was able to get my phone restored and updated to Lollipop, and thanks to my cloud backups I didn't lose my data!
I think my problem was something with my Mac and Phone not getting along together. I'm not sure if it was the Mac version of the Verizon app or some other factor, what I do know is I'm REALLY lucky I have a Windows machine AND my wife has the same phone.
I needed the Verizon app to repair my phone, but I needed the Verizon app on my PC because the Mac version kept crashing when I'd connect my phone. The only source for the Verizon application is to plug the phone into your computer and install it from the phone, which obviously wasn't an option in this case! Luckily I could use my wife's identical S4 to install the utility onto my PC.
Once I was able to do that, I opened the application on my PC, went into Repair Mode by navigating to the Repair tab on the left then selecting Enter Repair Mode or whatever. Then I connected my phone with a clean boot (no special button presses). It was just displaying the error message which instructed me to use the Verizon Repair utility.
After a few seconds the computer recognized the device and it appeared in the list on the repair utility.
I selected the device in the list (it was the only item in the list) then pressed the 'REPAIR DEVICE' button on the right.
It displayed a warning that 'due to the condition of the device' I would lose all of my personal data and settings. I agreed.
The utility then downloaded the latest firmware (the Lollipop update) and proceeded to install it to my device.
After about 15 minutes I had a factory fresh install of Lollipop ready to go!
BONUS, in the initial setup it remembered my settings and automatically offered to restore from a cloud backup. No data loss!!
Hey skullzarmy,
I may be in a similar situation. I to had root awhile back via Towlroot (i think thats the name), received and OTA update. Afterwards checked root with root checker and said No root but SU was found? I assumed I lost root? Now I downloaded the first OTA this morning and it worked. But the second OTA is failing.
I have factory reset my phone and still no worky.
However, I am in the middle of running the Software Repair Assistant as I read your post. We shall see how it goes. Hopefully it does not blow up.
To run the Software Repair Assistant in Windows just plug your phone is and when the prompt appears click the run option. You can install the assistant from there.
Good luck...
Spyke562 said:
Hey skullzarmy,
I may be in a similar situation. I to had root awhile back via Towlroot (i think thats the name), received and OTA update. Afterwards checked root with root checker and said No root but SU was found? I assumed I lost root? Now I downloaded the first OTA this morning and it worked. But the second OTA is failing.
I have factory reset my phone and still no worky.
However, I am in the middle of running the Software Repair Assistant as I read your post. We shall see how it goes. Hopefully it does not blow up.
To run the Software Repair Assistant in Windows just plug your phone is and when the prompt appears click the run option. You can install the assistant from there.
Good luck...
Click to expand...
Click to collapse
Thanks Spyke, I'm just waiting on my wife to get home with her S4 so I can do just that. It's pretty much my only hope. I'm just hoping it doesn't need that device profile that I deleted from my Mac... Good luck with yours! Let me know how it turns out!
OK, quick update. I was able to get the Verizon application installed on my PC and it was able to connect to the phone. It gave me a message saying due to the condition I would lose my data but it would restore it for me. Of course I went with it, so it's doing its thing now. I'll update with how it goes from here.
Please do...in the middle of my repair/update it BSOD my PC and now i think my phone is jacked
Spyke562 said:
Please do...in the middle of my repair/update it BSOD my PC and now i think my phone is jacked
Click to expand...
Click to collapse
Once I got the phone connected to my PC it was smooth sailing.
At what point did you BSOD? What version of Windows are you running?
Glad to hear you got it working!
I think it BSOD somewhere after 50%.
I am on Windows 8.1
Running it again and its a 93% so far.
Phone stuck on Software Update Failed on boot
Spyke562 said:
Glad to hear you got it working!
I think it BSOD somewhere after 50%.
I am on Windows 8.1
Running it again and its a 93% so far.
Phone stuck on Software Update Failed on boot
Click to expand...
Click to collapse
I ran it on Windows 7. Sounds like you are where I was. I'm hoping it was a fluke and pulls through this time! Fingers crossed for you!
skullzarmy said:
I ran it on Windows 7. Sounds like you are where I was. I'm hoping it was a fluke and pulls through this time! Fingers crossed for you!
Click to expand...
Click to collapse
Hey skullzarmy,
looks like keeping your figners crossed help me. After disconnecting my phone, pulling the battery and re-connecting the repair worked and I am back up and running.
Thanks for your help!
Spyke562 said:
Hey skullzarmy,
looks like keeping your figners crossed help me. After disconnecting my phone, pulling the battery and re-connecting the repair worked and I am back up and running.
Thanks for your help!
Click to expand...
Click to collapse
Great news! Not sure I helped but glad we both got our phones up and running again!