Hello, I've tried rooting my tablet at first with the sourceforge androidroot thing]. Afterwards I turned on the tablet and the "Android" sign at start up had changed and so did my background,Now I get a system UI error and it restarts every time. Preferabbly I would not like to do a hard reset but I would like to take guides if so, So far nothing I've found on google has helped me.
(I've tried to unroot with SuperoneClick and DoomLord
a500 tablet
DarkLoves said:
Hello, I've tried rooting my tablet at first with the sourceforge androidroot thing]. Afterwards I turned on the tablet and the "Android" sign at start up had changed and so did my background,Now I get a system UI error and it restarts every time. Preferabbly I would not like to do a hard reset but I would like to take guides if so, So far nothing I've found on google has helped me.
(I've tried to unroot with SuperoneClick and DoomLord
Click to expand...
Click to collapse
Which tablet is it? I have an a500 and may be able to help you.
dibblebill said:
Which tablet is it? I have an a500 and may be able to help you.
Click to expand...
Click to collapse
It may be an a500, My tablet is Grey and has the "Acer" on the back. I'm not too sure though. :/
DarkLoves said:
It may be an a500, My tablet is Grey and has the "Acer" on the back. I'm not too sure though. :/
Click to expand...
Click to collapse
Help...please?
Definitely an a500
-bump-
DarkLoves said:
Definitely an a500
-bump-
Click to expand...
Click to collapse
Okay. Which rooting tool did you use? Was it also supposed to install a custom recovery, ROM, etc? I know I'm not on my desktop atm, but i found one for ICS which installed a partition mounter and such.
dibblebill said:
Okay. Which rooting tool did you use? Was it also supposed to install a custom recovery, ROM, etc? I know I'm not on my desktop atm, but i found one for ICS which installed a partition mounter and such.
Click to expand...
Click to collapse
Google "source forge android root" and it should be the first thing that pops up,
I cannot post links yet ;/
DarkLoves said:
Google "source forge android root" and it should be the first thing that pops up,
I cannot post links yet ;/
Click to expand...
Click to collapse
Ah, did find it.
Didn't use that script. Once I'm at my desktop, I can tell you the script I used. Do you have a description of what your boot screen looked like? It could have been the recovery screen.
"Had to run the script manually. After the line files\adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop" and reboot the screen went black after boot android logo. Thought the tablet was bootlooping but this was not the case. Could still connect with adb and USB so after I continued to run all the script file the tablet was booting as expected with root access."
This was posted in the comments on that script. As far as hard reset, I'm not sure, beyond finding something that can push a new recovery or ROM straight to the tablet.
dibblebill said:
Ah, did find it.
Didn't use that script. Once I'm at my desktop, I can tell you the script I used. Do you have a description of what your boot screen looked like? It could have been the recovery screen.
"Had to run the script manually. After the line files\adb shell "echo \"ro.kernel.qemu=1\" > /data/local.prop" and reboot the screen went black after boot android logo. Thought the tablet was bootlooping but this was not the case. Could still connect with adb and USB so after I continued to run all the script file the tablet was booting as expected with root access."
This was posted in the comments on that script. As far as hard reset, I'm not sure, beyond finding something that can push a new recovery or ROM straight to the tablet.
Click to expand...
Click to collapse
"bootlooping"; I might have the same problem this person is having. It seems to be "bootlooping" but as this comment says it might not be the problem.a
DarkLoves said:
"bootlooping"; I might have the same problem this person is having. It seems to be "bootlooping" but as this comment says it might not be the problem.a
Click to expand...
Click to collapse
Try reconnecting it to the computer if you still have the script working, and getting back to that step. Unfortunately, I'm drawing a blank right now on doing a hard reset without OS access.
dibblebill said:
Try reconnecting it to the computer if you still have the script working, and getting back to that step. Unfortunately, I'm drawing a blank right now on doing a hard reset without OS access.
Click to expand...
Click to collapse
Well I still have the script, only thing I would be able to do is to try and re-root it or something, the only option is to press enter for it to root.
DarkLoves said:
Well I still have the script, only thing I would be able to do is to try and re-root it or something, the only option is to press enter for it to root.
Click to expand...
Click to collapse
Try that and leave it connected.
dibblebill said:
Try that and leave it connected.
Click to expand...
Click to collapse
I would have to do it while it was turned off.
DarkLoves said:
I would have to do it while it was turned off.
Click to expand...
Click to collapse
Er, well I dont have to but, I'm not sure if I should turn it on.
Should I do it while its on is the question.
DarkLoves said:
Er, well I dont have to but, I'm not sure if I should turn it on.
Should I do it while its on is the question.
Click to expand...
Click to collapse
I'd say yes. If the tablet's powered off, it can't connect at all. :S
dibblebill said:
I'd say yes. If the tablet's powered off, it can't connect at all. :S
Click to expand...
Click to collapse
Failed to copy files/su to /system/xbin/su' : Read-only file system
rm failed for /data/local.prop No such file or directory
Installing superuser....
failed to copy 'files/superuser.apk' to '/system/;app/superuser.apk' : Read-only file system
It didn't work, uh, Still same problem.
re-edit Everything is alright. Thanks sorry for the trouble.
I'm going to check if its rooted, it should be.
DarkLoves said:
Failed to copy files/su to /system/xbin/su' : Read-only file system
rm failed for /data/local.prop No such file or directory
Installing superuser....
failed to copy 'files/superuser.apk' to '/system/;app/superuser.apk' : Read-only file system
It didn't work, uh, Still same problem.
re-edit Everything is alright. Thanks sorry for the trouble.
I'm going to check if its rooted, it should be.
Click to expand...
Click to collapse
Not Rooted
DarkLoves said:
Not Rooted
Click to expand...
Click to collapse
Okay. I hate to make you wait, but I have to- when I get home today, I'll log onto my desktop PC and check all the rooting tools (I keep every tool for every phone/tablet I root). It'll be about 8-10 hours (I'm at work right now), but I'll get the names of the rooting tools I used. You're on the stock Android 4.0.3 OS, right?
DarkLoves said:
Not Rooted
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1520469
Try this thread. ITs what I used to root.
Did it work?
Related
Hello
I have tried to root my tablet by using bin4ry's but it comes out as shown in attaches images
my tablet is on 4.0.3r1a with kernel#10
anyone has any idea i should do ?
thanks for answering me
Whatever you do, dont use v14 as it has many bugs. Use v13
Sent from my Sony Tablet S using xda app-developers app
I'm having the same issue even though I signed the VpnFaker.apk myself. Stuck without root..
Check out page 3 of the FAQ thread for rooting, I'm having basically the exact same issue, but stifilz is giving me hope that it is rootable, just will take some messing around.
Link: http://forum.xda-developers.com/showthread.php?t=1828107&page=3
jumper62 said:
Whatever you do, dont use v14 as it has many bugs. Use v13
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Yes, I have tried it both V.13 and V.14_2
kandemirb said:
I'm having the same issue even though I signed the VpnFaker.apk myself. Stuck without root..
Click to expand...
Click to collapse
Me, too
DreadPirateDan said:
Check out page 3 of the FAQ thread for rooting, I'm having basically the exact same issue, but stifilz is giving me hope that it is rootable, just will take some messing around.
Link: http://forum.xda-developers.com/showthread.php?t=1828107&page=3
Click to expand...
Click to collapse
Thanks, and Check it out already, so according to the thread mine problems is about VPNFaker.apk right ?
Thanks all of you guys, I will post the result again
golfizz said:
Yes, I have tried it both V.13 and V.14_2
Me, too
Thanks, and Check it out already, so according to the thread mine problems is about VPNFaker.apk right ?
Thanks all of you guys, I will post the result again
Click to expand...
Click to collapse
You followed this.....
Open "ZipSigner 2" on your tablet.
Press the "Input" button and browse /sdcard/VpnFaker_unsign.apk
Press the "Output" button and save it as /sdcard/VpnFaker.apk
Key/mode select "platform"
Press "Sign the file"
Not the picture right?? That confused me when I was doing it (terrible screenshot) LOL
I used V11 and didn’t do anything for VpnFaker.apk.
It was all automatic (almost). Except terminal emulator.
Did you install this to tablet?
When you start script, terminal emulator must show up (on the tablet) and type 2lines by instruction (ignore errors).
Then it’ll work.
Well I've also tried, I think, everything; using different versions of the automated script, doing the process manually, resigning VpnFaker.apk, yet still, no success. I have a Turkish tablet, but had changed it to US using condi's tool before rooting it on HC. Any thoughts?
xdapak said:
I used V11 and didn’t do anything for VpnFaker.apk.
It was all automatic (almost). Except terminal emulator.
Did you install this to tablet?
When you start script, terminal emulator must show up (on the tablet) and type 2lines by instruction (ignore errors).
Then it’ll work.
Click to expand...
Click to collapse
When I finish, it does have a terminal emulator in my tablet, but there is no superuser in it.
stifilz said:
You followed this.....
Open "ZipSigner 2" on your tablet.
Press the "Input" button and browse /sdcard/VpnFaker_unsign.apk
Press the "Output" button and save it as /sdcard/VpnFaker.apk
Key/mode select "platform"
Press "Sign the file"
Not the picture right?? That confused me when I was doing it (terrible screenshot) LOL
Click to expand...
Click to collapse
I have follow your step but I wonder where I have to put a new VpnFaker.apk ? , I mean in bin4ry there is 2 .rar files and one include VpnFaler.apk, so am I have to extract it and replace old VpnFaker.apk with the one I am resign it ? or what I have to do with the new VpnFaker.apk I have resign it ?
@stifilz
I have follow your step in the FAQ thread and also do a VpnFaker.apk thing, and it comes out like it shown in the attached images
still no superuser but it have terminal emulator.
can should I do now ? any ideas ?
thanks
I am lost it should work. Grrr.
I fell your fustration, I have been there.
All I can suggest is factory reset. Then resign vpnfaker then try again. I cant remember exactly how I did it..... but now it works first time every time
stifilz said:
I am lost it should work. Grrr.
I fell your fustration, I have been there.
All I can suggest is factory reset. Then resign vpnfaker then try again. I cant remember exactly how I did it..... but now it works first time every time
Click to expand...
Click to collapse
I already make a factory reset and it still comes out the same ....
really no idea grrrr
Ditto with me to, I have tried to resign the vpnfaker and replace as well multiple times, tried all the automated scripts, reset each time, tried manual way multiple times, no luck.
Sony Tablet S 32GB Wifi US model
golfizz said:
I already make a factory reset and it still comes out the same ....
really no idea grrrr
Click to expand...
Click to collapse
OK Try this.
Do the factory reset and install terminal emulator only (forget the VpnFaker.apk).
Command prompt – type “adb devices”, device number should come up. Leave it open.
If it doesn’t, need to install correct adb driver.
Then run the script and follow instruction. Need to reboot few times till terminal emulator show up (on the tablet) and type 2lines by the instruction (ignore the errors).
Then it’ll work.
jamminjon82 said:
Are you spamming? You joined today and posted the same exact post in 4 different threads
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yeh aye. Coz that tool is crap and didn't work for me! Binarys method is 90% (results may vary)
stifilz said:
Yeh aye. Coz that tool is crap and didn't work for me! Binarys method is 100%
Click to expand...
Click to collapse
Maybe I have done something wrong !!!
Have to redo it again !! Thanks !
binary's method isn't 100% working! i've tried at least 20 times on my tablet s 16gb wifi + 3g and it never worked...
sapphire88 said:
binary's method isn't 100% working! i've tried at least 20 times on my tablet s 16gb wifi + 3g and it never worked...
Click to expand...
Click to collapse
Hmmm weird It has worked for me on 2 nz tabs 16gb no wifi. I will change statement
stifilz said:
Hmmm weird It has worked for me on 2 nz tabs 16gb no wifi. I will change statement
Click to expand...
Click to collapse
Ive tried the manual method, all of the auto scripts 1 - 15, reset factory defaults each time, verified drivers, zinsigner2/vpnfaker resigned, made sure USB Debugging/Unknown Sources, etc, etc, etc, still not working for me.
Sony Tablet S 32GB Wifi US model. 4.0.3 r5
I will try just about anything now, soooooooooooooo frustrated.
mikeblahblah said:
Ive tried the manual method, all of the auto scripts 1 - 15, reset factory defaults each time, verified drivers, zinsigner2/vpnfaker resigned, made sure USB Debugging/Unknown Sources, etc, etc, etc, still not working for me.
Sony Tablet S 32GB Wifi US model. 4.0.3 r5
I will try just about anything now, soooooooooooooo frustrated.
Click to expand...
Click to collapse
And you are US as well. Its not 32gb related for any strange reason??
Try anything hmmm
Try my signed vpn faker....
http://forum.xda-developers.com/showpost.php?p=32780973&postcount=20
Worth a shot
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?
Help! I was using Carlos' unlocking the bootloader guide against my will, because I love stock. And turns out karma has gotten me. For some reason my recovery wasn't installing on V20B, so I flashed back to V20F, factory reset, re-rooted, installed busybox, flashed the artas recovery... And yet my recovery STILL isn't showing up. The boot animation is inverted and the touch screen is still "messed up." I have a backup on my external SD card that I can use if I somehow get recovery functional. It's just the stupid recovery won't work and I need it to work lol. Any help? Please?! By the way, I've done an emergency flash using LG Mobile Support Tool and that didn't work, so I'm still open to suggestions.
I've been very helpful to everyone who's asked me for help, I'd like for others to be the same to me. Thanks to whoever tries
go back into recovery then make a backup in tar format then reboot into recovery and check for your files.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Nathan.7118391 said:
go back into recovery then make a backup in tar format then reboot into recovery and check for your files.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Click to expand...
Click to collapse
I don't have recovery. It won't flash. I have stock V20F without anything but a messed up screen.
Have you tried installing recovery using the L9 recovery installer app?
Also, for the wonky touch screen, it would help a lot if you enabled "Show touches" in the developers options tab~
Creta said:
Have you tried installing recovery using the L9 recovery installer app?
Also, for the wonky touch screen, it would help a lot if you enabled "Show touches" in the developers options tab~
Click to expand...
Click to collapse
That's what I'm using. Full busybox install and it still isn't installing.
You needed to be rooted to get recovery.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Ilxaot said:
That's what I'm using. Full busybox install and it still isn't installing.
Click to expand...
Click to collapse
you need this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&hl=en
I never had a problem with the other, but others have, but this one has worked for everyone.
If you have root, just fix the wonky touch screen the old way (through adb)
kuma82 said:
you need this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&hl=en
I never had a problem with the other, but others have, but this one has worked for everyone.
If you have root, just fix the wonky touch screen the old way (through adb)
Click to expand...
Click to collapse
Can you upload the apk for that? I can't type due to my phone's screen. And how do I do it through ADB? I don't even know how to use ADB, as embarrassing as it sounds. I could never get it to work. But I'm willing to do anything now.
Ilxaot said:
Can you upload the apk for that? I can't type due to my phone's screen. And how do I do it through ADB? I don't even know how to use ADB, as embarrassing as it sounds. I could never get it to work. But I'm willing to do anything now.
Click to expand...
Click to collapse
First fix the touch screen, hold up I'll send you all the info,
Another thing, I hope you already have adb debugging enabled
Wait a min, you have everything you need if you tried to unlock your device
Inside the root lelus folder is the adb
You know, if you go to link for robert busybox on your pc (and sign in) it will send it to your phone, to download
1. Go to the root lelus folder (should be on your c: drive) and open the "stuff" folder
now, hold down the shift key and right click with your mouse, you should see an option, to "open command window here"
This should open a cmd up where the adb is at.
2. Open the cwm_ts_fix_p769.zip and go into the system folder and copy the v6.bin to your external sd
3.now type
adb devices (in the command window)
you should get a number with online status. If you don't it's because adb debugging is not enabled
4. next type
adb shell
su
your phone will ask to enable it, good luck on enabling on the wonky touch screen
okay, type
cat /storage/external_SD/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
note if you put it on the internal storage, type
cat /sdcard/external_SD/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
this will cause the shell to freeze.
so open up a new cmd (hold shift key & and right click inside the stuff folder) and type
adb reboot
hope this helps, if you need a better guide, lol just ask, it will take me awhile though
kuma82 said:
First fix the touch screen, hold up I'll send you all the info,
you have root right?
Click to expand...
Click to collapse
I'll root again right now, I've reflashed so many times lol.
EDIT: I already have root aha. But nothing else.
kuma82 said:
First fix the touch screen, hold up I'll send you all the info,
you have root right?
Another thing, I hope you already have adb debugging enabled
Wait a min, you have everything you need if you tried to unlock your device
Inside the root lelus folder is the adb
You know, if you go to link for robert busybox on your pc (and sign in) it will send it to your phone, to download
Click to expand...
Click to collapse
Sign in as to your Google account and go to the play store.
Sent from my LG-P769 using Tapatalk 4 Beta
kuma82 said:
First fix the touch screen, hold up I'll send you all the info,
you have root right?
Another thing, I hope you already have adb debugging enabled
Wait a min, you have everything you need if you tried to unlock your device
Inside the root lelus folder is the adb
You know, if you go to link for robert busybox on your pc (and sign in) it will send it to your phone, to download
Click to expand...
Click to collapse
I don't have internet connection on my phone lol. We have FIOS and the router password is a WPA and it's like 14 characters long, with like 4 Q's (Near impossible to hit with mirrored touch screen. Trust me. It's a science of its own) I just need the apk, I couldn't find it anywhere. And okay, for the adb, how do i fix it?
Ilxaot said:
I don't have internet connection on my phone lol. We have FIOS and the router password is a WPA and it's like 14 characters long, with like 4 Q's (Near impossible to hit with mirrored touch screen. Trust me. It's a science of its own) I just need the apk, I couldn't find it anywhere. And okay, for the adb, how do i fix it?
Click to expand...
Click to collapse
Here's a direct link to busybox.apk if you still need it.
OMG I don't have internet my WiFi password is too long to type. Is it THAT hard to get an apk?
Creta said:
Here's a direct link to busybox.apk if you still need it.
Click to expand...
Click to collapse
THANK YOU. Now I can try it. I'll keep you updated, thanks for listening and not telling me methods I can't use.
Creta said:
Here's a direct link to busybox.apk if you still need it.
Click to expand...
Click to collapse
Bummer. This isn't the one I needed. NEVER MIND CWM IS WORKING THANK YOU SO MUCH OMG. THANKS TO YOU! Albeit it was really simple, THANKS YOU! God bless your soul, have a great life.
Ilxaot said:
Bummer. This isn't the one I needed. NEVER MIND CWM IS WORKING THANK YOU SO MUCH OMG. THANKS TO YOU! Albeit it was really simple, THANKS YOU! God bless your soul, have a great life.
Click to expand...
Click to collapse
No problem, I just unlocked my boot loader 2 days ago... took me a while cause carlo's video was missing out a lot of things...
Creta said:
No problem, I just unlocked my boot loader 2 days ago... took me a while cause carlo's video was missing out a lot of things...
Click to expand...
Click to collapse
I've got my backup back, but my screen is still mirrored. I'm flashing the touchscreen fix for now, but if this doesn't work I'm at a loss.
EDIT: Yeah, it didn't work. Things are still mirrored.
Ilxaot said:
I've got my backup back, but my screen is still mirrored. I'm flashing the touchscreen fix for now, but if this doesn't work I'm at a loss.
Click to expand...
Click to collapse
TS fix is for the wonky touchscreen, for mirrored, I think you gotta go back to 20D for P769
Creta said:
TS fix is for the wonky touchscreen, for mirrored, I think you gotta go back to 20D for P769
Click to expand...
Click to collapse
So I have to flash again?
Yes, I think I just need to stop trying to mess with this thing.
After using a sideload with a working update for Kindle Fire, the device now boots to the logo, stays the for a while, goes to a blue screen for a while, then shuts off.
What have I done wrong? There's no way for me to get a warranty, this was pre-owned, and I got it from a GameStop.
Alex311360 said:
Yes, I think I just need to stop trying to mess with this thing.
After using a sideload with a working update for Kindle Fire, the device now boots to the logo, stays the for a while, goes to a blue screen for a while, then shuts off.
What have I done wrong? There's no way for me to get a warranty, this was pre-owned, and I got it from a GameStop.
Click to expand...
Click to collapse
If you have root and have not done a factory reset, like I did, than there may be hope.. What version of FireOS did you have?
XxD34THxX said:
If you have root and have not done a factory reset, like I did, than there may be hope.. What version of FireOS did you have?
Click to expand...
Click to collapse
Sadly, I factory resetted. I had 13.3.2.4, and I was trying to get to 2.3.2 so I could get CM-12 and unlock the bootloader. Sadly, this happened.
Something weird is happening though. It stays on the blue screen when plugged in, and it takes ADB commands.
Do I still have hope?
If you still have ADB access, try this: http://forum.xda-developers.com/showthread.php?t=2793253
XxD34THxX said:
If you have root and have not done a factory reset, like I did, than there may be hope.. What version of FireOS did you have?
Click to expand...
Click to collapse
EncryptedCurse said:
If you still have ADB access, try this: http://forum.xda-developers.com/showthread.php?t=2793253
Click to expand...
Click to collapse
It's saying that some commands are denied. I may be screwed. su command does nothing.
Alex311360 said:
It's saying that some commands are denied. I may be screwed. su command does nothing.
Click to expand...
Click to collapse
Are you rooted?
If not, draxie's approach with ghettoroot may work: http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
EncryptedCurse said:
Are you rooted?
If not, draxie's approach with ghettoroot may work: http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
Click to expand...
Click to collapse
EDIT: I forgot that I should have used the code supplied instead of the install.cmd, lol.
Either way, at the point where you push the kindle update, hopefully this works
EDIT2: And now I can't get past pushing because it's denied. How do I get ghettoroot to work outside of adb shell?
Bump, still kinda stuck.
If you're on 3.2.4, then try the old HDX Toolkit to get root since I believe the old method used in this case just does it's job using ADB. Choose the root method for your tablet in in the menu of the toolkit. No need to use the towelroot one, choose option 6 or 7 depending on which tablet you have.
http://forum.xda-developers.com/showthread.php?t=2665683
icedtrip said:
If you're on 3.2.4, then try the old HDX Toolkit to get root since I believe the old method used in this case just does it's job using ADB. Choose the root method for your tablet in in the menu of the toolkit. No need to use the towelroot one, choose option 6 or 7 depending on which tablet you have.
http://forum.xda-developers.com/showthread.php?t=2665683
Click to expand...
Click to collapse
Does not appear to work.
Bump, still in need of help.
Still in need of help. Am I just doomed?
Alex311360 said:
Still in need of help. Am I just doomed?
Click to expand...
Click to collapse
Sorry, mate. I think the lack of recent responses speaks for itself. Some very talented individuals have already weighed in with their suggestions.
Ok, so I actually have some pretty important news. I'm using MobileGo by Wondershare to actually control it.
My screen is blue, however, through the app I'm using, the screen is actually working OK.
What the hell's going on with my screen? It locks normally and everything, except it's just blue.