Related
I got the phone offa craigslist.
how can I tell if the phone is already rooted?
Menu > settings > about phone > software > build number if out says release keys at the end it's one of the leaks, if it says test keys you have root. Hope that helps
Sent from my Eris using the XDA mobile application powered by Tapatalk
it says release-keys, but build number 1.17.605.1
the reason I asked is because I am having problems rooting it per the instructions on this website.
this phone recently got sent back to htc for service, and they flashed it to the "latest" rom they said. dunno what that means.
What exactly are you having problems with while rooting?
it says release-keys, but build number 1.17.605.1
the reason I asked is because I am having problems rooting it per the instructions on this website.
this phone recently got sent back to htc for service, and they flashed it to the "latest" rom they said. dunno what that means.
Click to expand...
Click to collapse
Im not sure htc services phones do they?
Sent from my Eris using the XDA mobile application powered by Tapatalk
korben dallas said:
Im not sure htc services phones do they?
Sent from my Eris using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
yes they do ,if u call and have issues with ur phone , they do offer to fix ur phone but not sure for any cost tho , hope this helps
I had audible crackling, and they fixed the speaker, but also reflashed the phone to 1.5, unrooted.
tazzpatriot said:
yes they do ,if u call and have issues with ur phone , they do offer to fix ur phone but not sure for any cost tho , hope this helps
Click to expand...
Click to collapse
shagpal said:
I had audible crackling, and they fixed the speaker, but also reflashed the phone to 1.5, unrooted.
Click to expand...
Click to collapse
view my thread to help you root your phone. the link is the first one in my signature. read threw the thread and make sure you download the full version and the update.
Good to know! Thanks!
ECLIPS3 said:
view my thread to help you root your phone. the link is the first one in my signature. read threw the thread and make sure you download the full version and the update.
Click to expand...
Click to collapse
noob question........my phone says firmware 1.5 build number 1.17.605.1 cl104882 release-key and its flashed to metropcs......if i root my phone and change to 2.1 will i have to reflash to metro........thanks
kingkat186 said:
noob question........my phone says firmware 1.5 build number 1.17.605.1 cl104882 release-key and its flashed to metropcs......if i root my phone and change to 2.1 will i have to reflash to metro........thanks
Click to expand...
Click to collapse
good news is, that you are stock, so you can root your phone.
and yes, chances are you will then have to reflash it to metropcs. but since you already did that once, the next time will be easier. if you do run into trouble, then just ask us in the IRC channel at irc.wastate.net #droideris or #erisroothelp
thanks for your help
jearl75 said:
Menu > settings > about phone > software > build number if out says release keys at the end it's one of the leaks, if it says test keys you have root. Hope that helps.
Click to expand...
Click to collapse
I think I have rooted my phone, but what is "leaks" also my phone has "realease" keys at he end of the build. Superuser app is on my phone and Titanium Backup seems to be working. Just entered, "su" into Terminal and got permission denied. I'm lost.
Additional details:
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
MobileWon said:
I think I have rooted my phone, but what is "leaks" also my phone has "realease" keys at he end of the build. Superuser app is on my phone and Titanium Backup seems to be working. Just entered, "su" into Terminal and got permission denied. I'm lost.
Click to expand...
Click to collapse
Check out this link. I think it might help answer your questions.
Also google theunlockr.com
Bayhill Jacket said:
Check out this link. I think it might help answer your questions.
Also google theunlockr.com
Click to expand...
Click to collapse
The link is not working.
Edit:Nevermind, I managed to find the information on Android Central. So, I'm rooted, but whenever I would do the g free verify I would get an error. Thanks given.
MobileWon said:
The link is not working.
Click to expand...
Click to collapse
I think that he meant this one. Basically, install a terminal app , if one is not already installed, and open it. If you see a "#" prompt, you are rooted. If you see a "$" prompt and then enter the command "su" (and grant permission to the terminal app if you get prompted to by the SuperUser app), if it changes to a "#" you are rooted.
doogald said:
I think that he meant this one. Basically, install a terminal app , if one is not already installed, and open it. If you see a "#" prompt, you are rooted. If you see a "$" prompt and then enter the command "su" (and grant permission to the terminal app if you get prompted to by the SuperUser app), if it changes to a "#" you are rooted.
Click to expand...
Click to collapse
That's the link, thanks doogald. Sorry for the broken one
Thanks guys thats the exact one I used. Maybe I'm doing something wrong when I do the g free verify, but I also wanted to see if I had the cid and sim unlocked.
MobileWon said:
I think I have rooted my phone, but what is "leaks" also my phone has "realease" keys at he end of the build. Superuser app is on my phone and Titanium Backup seems to be working. Just entered, "su" into Terminal and got permission denied. I'm lost.
Click to expand...
Click to collapse
For the Eris, there are at least 5 different ways to "root" your phone, and the most recent & easiest methods (One Click or Dummies) don't even touch the primary OS - they just install a custom recovery boot which allow you to replace the entire OS by flashing a "rooted" OS into place (or, add a root toolkit to the existing "stock" ROM). So, running "su" may not tell you much.
For most rooted ROMs, the "su" terminal/shell program and the Superuser app act as a pair - when any other app requests superuser privileges the first time, the Superuser app will pop up on the screen and ask you whether you want to allow or deny the app requesting root privileges. There will be a check-box on that screen that will allow the Superuser app to remember your choice. If you have ever seen this pop-up, then I suppose you have a rootkit installed correctly.
Note that if you look away from your phone for too long while that pop-up is on screen, the Superuser app will time out - and decide that the requesting app should always be denied.
The Superuser app keeps a list of apps that have previously requested root - start the Superuser app directly from the launcher, and you will see the list. If there is one in there that is erroneously marked as "deny", tap on that entry and select "forget". Then, the next time you start the app in question, keep a lookout for that Superuser app pop-up.
The fact that you get a "permission denied" message when trying "su" from a terminal session means one of two things, either:
- you previously denied access to "su" (or looked away from the screen, and missed the pop-up), or
- your ROM is not correctly rooted.
HTH
PS note that this thread is extremely old - it references methods and techniques which will still work, but are quite a bit more tedious than newer methods. Also, it helps people responding to your inquiry if you mention a few tidbits about your phone : what you have done to the phone,the bootloader version, the (full) kernel version, the "Software #", etc.
MobileWon said:
Thanks guys thats the exact one I used. Maybe I'm doing something wrong when I do the g free verify, but I also wanted to see if I had the cid and sim unlocked.
Click to expand...
Click to collapse
Doesn't SIM Lock only apply to GSM phones?
ok. ive used the one click root... ive used the script root method... downloaded the correct files. but i can't seem to get root.... both methods says i have root and its good to go but no superuser icon and i even tried using the one on the market just incase i need to... nothing still and ive tried over hours and hours... i don't know what else to do... anyone?
Use the fixed superuser posted on these forums.
Sent from my ADR6400L using XDA App
i can't even get root permission to log into cwk. to flash it.
dadsterflip said:
i can't even get root permission to log into cwk. to flash it.
Click to expand...
Click to collapse
i didn't do the one click root, but, in the long root version, and I am sure it is the same, you need to install SU from the market, and then if you do not get SU access right away, reboot the phone a couple times.
If you turn your phone off, and then back on while holding vol down and power, does it say MECH S-OFF at the top? If it still says S-ON or security warning, you didn't root your phone right, if it says S-OFF your rooted, and you just need to get SU working by rebooting a few times.
nosympathy said:
i didn't do the one click root, but, in the long root version, and I am sure it is the same, you need to install SU from the market, and then if you do not get SU access right away, reboot the phone a couple times.
If you turn your phone off, and then back on while holding vol down and power, does it say MECH S-OFF at the top? If it still says S-ON or security warning, you didn't root your phone right, if it says S-OFF your rooted, and you just need to get SU working by rebooting a few times.
Click to expand...
Click to collapse
Hope that works for them. I wonder if fastboot, where it doesnt shut the phone down 100% and suspends the phone in memory, could be an issue or no?
nosympathy said:
i didn't do the one click root, but, in the long root version, and I am sure it is the same, you need to install SU from the market, and then if you do not get SU access right away, reboot the phone a couple times.
If you turn your phone off, and then back on while holding vol down and power, does it say MECH S-OFF at the top? If it still says S-ON or security warning, you didn't root your phone right, if it says S-OFF your rooted, and you just need to get SU working by rebooting a few times.
Click to expand...
Click to collapse
ill redo it and do this. thx
the only problems root wise i ran into (and i did it the adb way) was super user wouldnt initially give rights. I solved this each and everytime by one reboot. (clockwork i didnt have rights) restarted phone superuser came up with the box for me to give cw rights. Then i installed Tit backup form the market. No rights again, a restart and problem solved. Dont know why it was buggy but try that.
is it normal to see. usb device not recognized? while its on the hboot loading the update through? it only says that while its updating the hboot or loading the PG05IMG.zip. otherwise i have all the right drivers for it.
update.... still not luck. i used the script root... at the end i have s-on.... on the first downgrade i have s-off but at the very end of the script to add the other update ppg05img, it turns the s-on back... sooooo whats wrong with it or what am i doing wrong?
if your having that many issues with the quick root method (ill be honest I havent looked at the instructions for it) i really would suggest doing it manually (the method that was first released). I wanted to post the links for you but i dont have enough posts yet to do so. The instructions i used are on droid-life . com. Once your there go to search and type in thunderbolt root. Another one click root method will be the first topic. Go there and youll see two hyperlinks (here) and (here) in the first paragraph.Click the second one and youll see the list of instructions and a link to a video, showing you how to do it. The original video is very fast but once it starts playing it will give you step one and step two links. This video is very helpful and very detailed. Anyway hope that helps.
Any questions leave a post.
update. finally got root... manual way. thx for the help guys.
dadsterflip said:
update. finally got root... manual way. thx for the help guys.
Click to expand...
Click to collapse
no problem man hope i was a help.
dadsterflip said:
update. finally got root... manual way. thx for the help guys.
Click to expand...
Click to collapse
now you can rest easy that in the future if you screw up your tbolt you understand how adb works enough to probably fix it comfortably.
Amen to that.
Sent from my ADR6400L using XDA Premium App
EDIT: Thanks to Steal25 and Ausch30, Your antivirus WILL stop the EXE from running. TURN IT OFF, and obviously back on wants your S-OFF. (thanks from AlphaRev, Unrevoked, and TeamWin)
My Original question...
I for some reason when ever i double click on the Revolutionary exploit, the CMD shows maybe for 4 seconds then ends, and i cant get it open a second time with out re-extracting it.
ADB recognizes my phone.
Ive restarted my CPU
I turned off Firewall.
Still no effect.
This also applies to the drivers exploit and fastboot exploit.
Im running Windows Vista
still no luck ?
is it just insta closing when you click on it or is it waiting for device?
Geeble said:
still no luck ?
is it just inst closing when you click on it or is it waiting for device?
Click to expand...
Click to collapse
nothing man. it opens the cmd, does nothing but read the main title, freezes for 3 seconds and exits
coffeehandle said:
I for some reason when ever i double click on the Revolutionary exploit, the CMD shows maybe for 4 seconds then ends, and i cant get it open a second time with out re-extracting it.
ADB recognizes my phone.
Ive restarted my CPU
I turned off Firewall.
Still no effect.
This also applies to the drivers exploit and fastboot exploit.
Im running Windows Vista
Any suggestions?
Click to expand...
Click to collapse
right click the revolutionary.exe and select run as administrator
ausch30 said:
right click the revolutionary.exe and select run as administrator
Click to expand...
Click to collapse
did that as well
this happened to me also, it seems (atleast for me) norton anti virus didn't like it very much. try shutting off your anti virus and try it again. hope that helps.
have you tried running it from a cmd window ?
start Menu search/run
type cmd
drag file into window press enter
that is if it just keeps closing as soon as you open it.
that is all i got unfortunately .
steal25 said:
this happened to me also, it seems (atleast for me) norton anti virus didn't like it very much. try shutting off your anti virus and try it again. hope that helps.
Click to expand...
Click to collapse
AH didnt think about that. lets see...
steal25 said:
this happened to me also, it seems (atleast for me) norton anti virus didn't like it very much. try shutting off your anti virus and try it again. hope that helps.
Click to expand...
Click to collapse
That was my next suggestion, I had the same issue
Got it to run by turning off Norton. But it wont read my serial code. Is there a way you can copy and paste in a CMD? mine i thought did that but isnt now
My cmd closed trying to install Clockworkmod.....any suggestions?
coffeehandle said:
Got it to run by turning off Norton. But it wont read my serial code. Is there a way you can copy and paste in a CMD? mine i thought did that but isnt now
Click to expand...
Click to collapse
you should be able to, type adb devices and get the s/n again and get a new beta code you may have just written it down wrong.
JOKERx2 said:
My cmd closed trying to install Clockworkmod.....any suggestions?
Click to expand...
Click to collapse
try installing teamwins recovery
put the twrp file in sdk-tools folder
cd into that folder and run the fastboot commands to install it.
JOKERx2 said:
My cmd closed trying to install Clockworkmod.....any suggestions?
Click to expand...
Click to collapse
Mine did the same thing. I told it to install CWM and I didn't quite notice that it had and the command window just closed. I got a little nervous but I just opened the SDK and opened a new CMD window and did adb reboot recovery and I was in CWM recovery
I don't understand one thing people say to uninstall sdk before you root but how would you be able to do adb to check the serial for example without having sdk installed
Sent from my PG86100 using XDA App
iliapiano said:
I don't understand one thing people say to uninstall sdk before you root but how would you be able to do adb to check the serial for example without having sdk installed
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
not sdk, you have to uninstall htc sync.
steal25 said:
not sdk, you have to uninstall htc sync.
Click to expand...
Click to collapse
I didn't and mine worked fine
ausch30 said:
Mine did the same thing. I told it to install CWM and I didn't quite notice that it had and the command window just closed. I got a little nervous but I just opened the SDK and opened a new CMD window and did adb reboot recovery and I was in CWM recovery
Click to expand...
Click to collapse
what i noticed also, don't know if it makes a difference or not, the "y" is capitalized and the "n" is not, like i said don't know if it makes a difference or not, but i caught that and put a capital "y" and everything went smooth.
DONE
steal25 said:
you should be able to, type adb devices and get the s/n again and get a new beta code you may have just written it down wrong.
Click to expand...
Click to collapse
Thanks guys. Ill click the thanks for anyone on my thread =]
steal25 said:
what i noticed also, don't know if it makes a difference or not, the "y" is capitalized and the "n" is not, like i said don't know if it makes a difference or not, but i caught that and put a capital "y" and everything went smooth.
Click to expand...
Click to collapse
The only issue I'm having is when I run adb shell from the command line I get $ instead of #. Anyone know if there something I forgot to do or is this the normal state of this root method at this point? Root apps work, CWM recovery is installed, Superuser app is installed, can't seem to access anything or do much from the command line.
Error Code: 160.
Error Reason: MID Not Allowed.
Wish I had been active enough here to post in development. But ****. Ideas?
You don't need to be able to post in order to read. Just read the stickies in the development section.
joeshmoetogo said:
Error Code: 160.
Error Reason: MID Not Allowed.
Wish I had been active enough here to post in development. But ****. Ideas?
Click to expand...
Click to collapse
Try new automated script and if it fails do factory reset and try again, also follow all instructions it will give you
jose51197 said:
Try new automated script and if it fails do factory reset and try again, also follow all instructions it will give you
Click to expand...
Click to collapse
This was my fourth factory reset with automated script. This time I registered at HTCdev with a different e-mail address and it took my device identifier token. Go figure.
Thanks for all your work and support.
The script didn't seem to get the right code for me. So I just opened another command prompt to get my unlock code manually. Other than that, the whole thing worked perfectly for me. Thanks jose and CaptainRewind.
I have been unable to get past the step where I have to type in:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
I've tried it on Windows XP 32-bit and Windows 7 64-bit and the error doesn't seem to come to an end. The error specifically reads:
link failed No such file or directory
I've tried it with both the automated script and doing it manually on both. I get the device to show up with adb devices, get the restore prompt on the device, but can't seem to go any further. I keep reading the topic and dissecting the automated script trying to find out what I'm not doing, and can't seem to figure it out.
Hesacon said:
I have been unable to get past the step where I have to type in:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
I've tried it on Windows XP 32-bit and Windows 7 64-bit and the error doesn't seem to come to an end. The error specifically reads:
link failed No such file or directory
I've tried it with both the automated script and doing it manually on both. I get the device to show up with adb devices, get the restore prompt on the device, but can't seem to go any further. I keep reading the topic and dissecting the automated script trying to find out what I'm not doing, and can't seem to figure it out.
Click to expand...
Click to collapse
I had the same problem until I realized I had to wait until after this step to accept the restore on my phone.
ceayuso said:
I had the same problem until I realized I had to wait until after this step to accept the restore on my phone.
Click to expand...
Click to collapse
That's just it, this step doesn't seem to end. On both computers I've tried, it goes on for a long time. If I don't give it up, it seems to keep going.
Hesacon said:
That's just it, this step doesn't seem to end. On both computers I've tried, it goes on for a long time. If I don't give it up, it seems to keep going.
Click to expand...
Click to collapse
So when you do this step on your computer, you then go to your phone and accept the restore?
ceayuso said:
So when you do this step on your computer, you then go to your phone and accept the restore?
Click to expand...
Click to collapse
I've accepted the restore while it was looping before, this is what I see with cmd. I've let it go a good 20 minutes now. When I try to restore while it's looping, after reboot with or without adb, I'm still a normal user.
Factory reset your phone. I got the same thing...until I reset mine.
Hesacon said:
I've accepted the restore while it was looping before, this is what I see with cmd. I've let it go a good 20 minutes now. When I try to restore while it's looping, after reboot with or without adb, I'm still a normal user.
Click to expand...
Click to collapse
mine did that too, then i did a second factory reset and made sure the password (restore) was disabled in development section, then ran jose's script and bingo, she worked.
i should say Jose's-Capt Rewind and mdmower's
jose's script seems to have worked, not sure why it wasn't before or why it wasn't manually working, but I've got an unlocked bootloader and I'm rooted! It says s-on on the bootloader still, but superuser and titanium backup seem to be working appropriately.
Thanks guys!
hesacon said:
jose's script seems to have worked, not sure why it wasn't before or why it wasn't manually working, but i've got an unlocked bootloader and i'm rooted! It says s-on on the bootloader still, but superuser and titanium backup seem to be working appropriately.
Thanks guys!
Click to expand...
Click to collapse
glad Your on the go, yipee
Hesacon said:
jose's script seems to have worked, not sure why it wasn't before or why it wasn't manually working, but I've got an unlocked bootloader and I'm rooted! It says s-on on the bootloader still, but superuser and titanium backup seem to be working appropriately.
Thanks guys!
Click to expand...
Click to collapse
I haven't been monitoring this thread subforum until now, but looks like the automated script seems to have helped.
Getting the temproot was all about timing. On the day we found this, it was tough getting the timing just right. The script really helped with that.
Now that you're rooted, the hardest part is over.
Sent from my ADR6410LVW using xda app-developers app
Problems With Automatic Script
CaptainRewind said:
I haven't been monitoring this thread subforum until now, but looks like the automated script seems to have helped.
Getting the temproot was all about timing. On the day we found this, it was tough getting the timing just right. The script really helped with that.
Now that you're rooted, the hardest part is over.
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I'm having a bit of a problem with the automatic script. I make it a few steps in (accept restore, etc). But then it hangs up at "Waiting for Device" and never advances beyond that. On the phone's screen is the Droid Eye. I've tried it a couple times and haven't made it past that stage. I didn't do a factory reset before starting. Would that make a difference? Sorry to post in an old thread. I've been monitoring the Development threads but don't have enough posts to participate. Thanks.
dodgerinNH said:
I'm having a bit of a problem with the automatic script. I make it a few steps in (accept restore, etc). But then it hangs up at "Waiting for Device" and never advances beyond that. On the phone's screen is the Droid Eye. I've tried it a couple times and haven't made it past that stage. I didn't do a factory reset before starting. Would that make a difference. Sorry to post in an old thread. I've been monitoring the Development threads but don't have enough posts to participate. Thanks.
Click to expand...
Click to collapse
Yes you HAVE to factory reset
Okay, just wanted to put this info here for easy reference. Feel free to correct anything I may have wrong.
*Based on my experiences performing the operation on windows 7 x64.
1. Install the LG USB driver for windows found under the software tab from their site here
2. Download and extract the English version of the root optimus g created by fiddy619 from here
3. Set USB debugging on and attach your phone to usb, then put it in MTP/Media Sync mode. Next, open a command prompt and navigate to the "stuff" sub-directory of the extracted file. Run the command "adb devices" to make sure your phone has been detected. Go back to the main directory and run the RootOptimusG.bat file.
4. When prompted on your phone choose restore data. Leave your phone plugged into USB until the program tells you it is finished! Sit back and let the magic happen. Your phone will reboot. Mine acted weird for a few seconds after it rebooted, the buttons at the bottom were going on and off and the screen was flickering. Just be patient and give it a couple minutes if needed.
5. When prompted that all is complete you can disconnect your phone from your computer and open the Play store to get the update for SuperSU
Now you are ready to unlock!
should be a sticky.
Thanks!
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
karelson said:
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
Click to expand...
Click to collapse
well if you have the supersu then it should be rooted. also if you now have it unlocked then it is rooted because i dont think you can unlock unless you root. also please search around the forums about what apps to not remove after root. a lot of people have noted issues after removing google apps.
showstopper03 said:
well if you have the supersu then it should be rooted. also if you now have it unlocked then it is rooted because i dont think you can unlock unless you root. also please search around the forums about what apps to not remove after root. a lot of people have noted issues after removing google apps.
Click to expand...
Click to collapse
Great Thank You.
karelson said:
Great Thank You.
Click to expand...
Click to collapse
actually it looks like V.05 you can uninstall any app without fear of security warnings. Please read all of this link for more info on it.
http://forum.xda-developers.com/showthread.php?t=2001655
Correct, you can just double click the bat file...my steps vary because I included a check to make sure adb is recognizing your device properly.
karelson said:
I followed the thread to root no fiddy619 instructions. I did use MTP.
But instead of Command prompt, I just double clicked the BAT file. and it run without problems, I think.
I have the SuperSU icon on my phone.
How can i make sure it was rooted?
p.s
The unlock also ran without problems.
Click to expand...
Click to collapse
Bumping this back to the top until stickied.
Sent from my LG Optimus G using Tapatalk 2
IrateCustomer said:
Bumping this back to the top until stickied.
Sent from my LG Optimus G using Tapatalk 2
Click to expand...
Click to collapse
Mine is stuck at "Select Restore Data" from my Phone step ... not sure whats going on.
kirdroid said:
Mine is stuck at "Select Restore Data" from my Phone step ... not sure whats going on.
Click to expand...
Click to collapse
I tried unrooting and re-rooting just to test our guides here and I am stuck at this step too. Obviously I can simply flash su in CWM but I wonder why this is happening.
carrett said:
I tried unrooting and re-rooting just to test our guides here and I am stuck at this step too. Obviously I can simply flash su in CWM but I wonder why this is happening.
Click to expand...
Click to collapse
Go to general-developer options- set desktop backup password. Set the password and then use that when you run the script and restore from desktop backup screen shows up.
Sent from my LG-E970 using Tapatalk 2
kirdroid said:
Go to general-developer options- set desktop backup password. Set the password and then use that when you run the script and restore from desktop backup screen shows up.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
If that worked for you, I'm happy for you. I am at this time unable to find a way to unroot and then re-root aside from restoring a backup in CWM or flashing a superuser zip in CWM. This could be because of a "bug" in our rooting script, in SuperSU's un-rooting function, or just an incompatibility between the two. Either way, I think this rooting mechanism works for more virgin LGOGs than not.
worked for me, easy peasy.
When i run the script it gives an error saying that i'm missing backup-restore.apk and /system/bin/ric does not exist. Any ideas as to why this is?
nice. thank you.
aznracer62 said:
When i run the script it gives an error saying that i'm missing backup-restore.apk and /system/bin/ric does not exist. Any ideas as to why this is?
Click to expand...
Click to collapse
That is probably because your phone is not rooted yet. I got that too as I was rooting it. Worked great.
I'm trying to root. USB debugging is on, connected as MTP. Run ADB, run adb-devices, returns an empty screen.
Try to run the script, it tells me "please check setting again"
HALP.
bebop_ said:
I'm trying to root. USB debugging is on, connected as MTP. Run ADB, run adb-devices, returns an empty screen.
Try to run the script, it tells me "please check setting again"
HALP.
Click to expand...
Click to collapse
Also need to allow "unknown sources" in security settings.
adfurgerson said:
Also need to allow "unknown sources" in security settings.
Click to expand...
Click to collapse
I had that checked as well.
bebop_ said:
I had that checked as well.
Click to expand...
Click to collapse
Do you have lg usb drivers installed?