Related
As Lg optimus net have not proper section and as it is successor of o1. I think its right place to post this thread.
After searching and trying many forums over 2-3weeks i m able to root my phone successfully. As there is not a single forum here to root this phone i want to make one, to help those searching for this.
i thanks to "g0mezz " whose method for rooting another phone worked for mine too
First of all there are a couple of things that you have to consider before starting to root.
1. Be sure that you have installed the original V20B o v10c version software on rom. I have tested on these two.
2. If you have it installed and tried different methods to root on it do a factory reset before trying this one.
3. Be absolutely sure that you have all the drives installed when working with the phone in USB debugging mode, if not install them.
4. Download SuperOneClickv1.9.5-ShortFuse or later version( i used 1.9.5) , after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the ADB folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. Enable USB Debugging mode (Enter the phone settings menu>Application> Development and tick the USB debugging mode) and then connect phone to pc via usb cable. (DONT PRESS USB STORAGE) .
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices (press enter)(after this command you should see your device id)
adb shell (press enter) (after this command you should see $)
$ echo 1 > /data/local/lge_adb.conf, (press enter)
Do not close the window, live it like that.
8. Start SuperOneClick.exe, leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok and that if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF(DO NOT DISCONNECT CABLE) wait until it will appear in the window again Starting ADB server... after that
b. Turn USB Debugging ON and after this trick it will start rooting.
After this it will ask you to reboot the phone, DO NOT FORGET, and after the reboot click on the SuperUser icon in the phone's menu. it will aks you if you allow or deny it's access. click allow. After this you must connect to the internet via Wireless or a apn, click on the superuser icon again if you exit it, go to settings, scroll down and you will see Su Binary v.XXXX, click on that to update it, than go to market and search the super user app and update it.
Also update busy box.
IF this doesn't work do a factory reset and again repeat these steps.
if this guide works for you do post replies and ...... dont forget to press thanks button
Doesn't seem 2 work. Keeps getting stuck at the point "Running psneuter" and gets stuck. Tried closing debugging and all that but it still gets stuck. Reset it 3 times still no result.
---------- Post added at 02:38 AM ---------- Previous post was at 02:13 AM ----------
Did it!! Yes!! For those who might not be able its very important that in the cmd u write like this:
adb shell (enter)
$ echo 1 > /data/local/lge_adb.conf
Give the exact spaces!! And it worked!!! (Space between echo 1 > /data ... like that)
Chowder93 said:
Doesn't seem 2 work. Keeps getting stuck at the point "Running psneuter" and gets stuck. Tried closing debugging and all that but it still gets stuck. Reset it 3 times still no result.
---------- Post added at 02:38 AM ---------- Previous post was at 02:13 AM ----------
Did it!! Yes!! For those who might not be able its very important that in the cmd u write like this:
adb shell (enter)
$ echo 1 > /data/local/lge_adb.conf
Give the exact spaces!! And it worked!!! (Space between echo 1 > /data ... like that)
Click to expand...
Click to collapse
Yep you have to follow these instruction correctly i have metioned these spaces so .. if u r having problem rooting by this method afrer following these steps correctly then rply.. and also post your rply if u successfully rooted using this....
.
thanks for the guide...i did it...but there is one thing i needed most..this so called tun.ko module to be needed in connecting vpn..is there any one have tried this???
Did u install any custom roms?
Sent from my Optimus Net using XDA Premium.
vicfirth_23 said:
thanks for the guide...i did it...but there is one thing i needed most..this so called tun.ko module to be needed in connecting vpn..is there any one have tried this???
Click to expand...
Click to collapse
no i didnt tried it.....
Chowder93 said:
Did u install any custom roms?
Sent from my Optimus Net using XDA Premium.
Click to expand...
Click to collapse
i didnt find any cw mod recovery for this phone so i didnt tried to install any other rom... but i think cwm recovery of optimus one will also work for this phone... i will try it later on...
I haven't tried installing custom roms in my phone.. some forums said that cfw have stock tun.ko module, a module needed to run the vpn application.
I saw a optimus net CWM installation process.
Sent from my Optimus Net using XDA Premium.
Found it:
http://forum.xda-developers.com/showthread.php?t=1354387
Sent from my Optimus Net using XDA Premium.
still waiting for any feedbacks thanks to TS
LlewoR said:
still waiting for any feedbacks thanks to TS
Click to expand...
Click to collapse
It worked man!! It worked on mine
What exactly is meant by
"Be absolutely sure that you have all the drives installed when working with the phone in USB debugging mode, if not install them."
It means the adb drivers.
is there any development on this like custom rom?im planning to root my phone using this method
is there any development on this like custom rom?im planning to root my phone using this method
Click to expand...
Click to collapse
Yep! There are Custom Roms. I have already flashed one
You Can find em here:-
http://www.androidworld.it/forum/lg-optimus-net-p690-187/
There are only a few but there will be more soon.
thanks for reply mate
thank you sir it works
Did It work??
Chowder93 said:
Did It work??
Click to expand...
Click to collapse
chowder where did you get you custom rom and kernel?maybe you can share it too and its that the best rom for you?thanks in advance
please do keep in touch with this thread hehehe
JCASE HAS DONE IT GUYS:
http://www.forum.lepanlife.com/showthread.php?tid=322
No luck,
I followed the steps, but when I connected the Lepan2 to the computer, it started to find devices, and finally it got this as I show in this graphic:
imageshack.us/f/838/anydatahsusbdevice.jpg (I cannot post links so I place it like that)
So I tried the 'update driver software" for the one with the yellow question mark under "Other Devices" called ANY_DATA HSUSB Device" and none i386 or amd64 work with that device. I don't know why it shows 2 devices, the other as you can see is under "Portable Devices" and it was recognized by Windows 7 64-bit witch is the OS i'm running. Also if I right-click on that "LePanII" device and select 'update driver software' and point to the unzipped files that you posted above, it says that "The device LepanII already has the best windows drivers"
So when I run SuperOneclick, the one you also posted above, the application became "unresponsive' after clicking on "Root"
I checked on windows task manager and there are 2 adb.exe processes running, and the only way I can terminate the Superoneclick app is by terminating those 2 adb.exe processes. I have tried several times and same result, it becomes unresponsive after starting adb server on port 5037
rocketero said:
No luck,
I followed the steps, but when I connected the Lepan2 to the computer, it started to find devices, and finally it got this as I show in this graphic:
imageshack.us/f/838/anydatahsusbdevice.jpg (I cannot post links so I place it like that)
So I tried the 'update driver software" for the one with the yellow question mark under "Other Devices" called ANY_DATA HSUSB Device" and none i386 or amd64 work with that device. I don't know why it shows 2 devices, the other as you can see is under "Portable Devices" and it was recognized by Windows 7 64-bit witch is the OS i'm running. Also if I right-click on that "LePanII" device and select 'update driver software' and point to the unzipped files that you posted above, it says that "The device LepanII already has the best windows drivers"
So when I run SuperOneclick, the one you also posted above, the application became "unresponsive' after clicking on "Root"
I checked on windows task manager and there are 2 adb.exe processes running, and the only way I can terminate the Superoneclick app is by terminating those 2 adb.exe processes. I have tried several times and same result, it becomes unresponsive after starting adb server on port 5037
Click to expand...
Click to collapse
Yep, Bear was having the same issues when he tried. Adam and I have fixed the drivers partially (they are re-uploaded, so re-download them). When you use the re-up'ped drivers and update the AnyData HSUSB Device it will work now and change it to an Android ADB Composite Interface Device.
However, getting ADB working is another story. Adam and myself have been working on Bear's computer remotely and we've done what we can do from there. When we both get our Le Pan II's this week (Tues/Wednesday, respectively), we are going to push forward full speed ahead in Linux to attempt to get ADB to recognize the device.
It's started to look like the drivers that leaked are not for the LP2, which is disappointing to say the least. In order to root it without the drivers, it's gonna take time and patience and we're going to need to find an unpatched exploit in the HC OS by modifying Gingerbreak or Zerg.
I'll keep you updated as it progresses.
Hey,
Could any of you owners of the Le Pan II (TC979) do a dump of the ROM?
(including the drivers, kernel, etc)
It would be GREATLY beneficial to the XDA / RootzWiki HP TouchPad community since it would assist with the development of Ice Cream Sandwich, given how similar, if not identical the hardware on the Le Pan II is to the HP TouchPad.
Thanks.
PresidentMcCain said:
Hey,
Could any of you owners of the Le Pan II (TC979) do a dump of the ROM?
(including the drivers, kernel, etc)
It would be GREATLY beneficial to the XDA / RootzWiki HP TouchPad community since it would assist with the development of Ice Cream Sandwich, given how similar, if not identical the hardware on the Le Pan II is to the HP TouchPad.
Thanks.
Click to expand...
Click to collapse
As soon as we get this thing rooted, I'd be more than happy too
We have no firmware files, just OTA updates - they do not post firmwares, source code, adb drivers or anything on their site. But we'll get it and when we do, I'll get you that info.
dbaybay said:
As soon as we get this thing rooted, I'd be more than happy too
We have no firmware files, just OTA updates - they do not post firmwares, source code, adb drivers or anything on their site. But we'll get it and when we do, I'll get you that info.
Click to expand...
Click to collapse
Maybe this will help you with ADB drivers:
http://rootzwiki.com/topic/15624-how-tocm9-adb-interface-on-usb/
---------- Post added 24th January 2012 at 12:15 AM ---------- Previous post was 23rd January 2012 at 11:50 PM ----------
If you can at least use Root Explorer to zip up some of it, it'd be helpful
(I believe the drivers are .so files in the lib folder under /)
dbaybay said:
Yep, Bear was having the same issues when he tried. Adam and I have fixed the drivers partially (they are re-uploaded, so re-download them). When you use the re-up'ped drivers and update the AnyData HSUSB Device it will work now and change it to an Android ADB Composite Interface Device.
However, getting ADB working is another story. Adam and myself have been working on Bear's computer remotely and we've done what we can do from there. When we both get our Le Pan II's this week (Tues/Wednesday, respectively), we are going to push forward full speed ahead in Linux to attempt to get ADB to recognize the device.
It's started to look like the drivers that leaked are not for the LP2, which is disappointing to say the least. In order to root it without the drivers, it's gonna take time and patience and we're going to need to find an unpatched exploit in the HC OS by modifying Gingerbreak or Zerg.
I'll keep you updated as it progresses.
Click to expand...
Click to collapse
I just downloaded again the link for "Drivers" and I connected the Lepan2 again to the computer and the same problem as before.
Then I checked the "File hashes" for the files "WdfCoInstaller01009.dll" and the other 2 inside the folder "amd64" and the cr32/md5/sha-1 are identical for the ones I had downloaded before and this ones. So where are the new ones you said you re-uploaded ?
About the ROM, I am also interested on obtaining the "original" ROM that came with the LepanII, as I updated the system with a still-in-development that Lepan tech support had uploaded to the server without even first testing it, and now I can not revert back to the original because they have not provided to me in a support-ticket I opened at their website. I don't know much about ROM extracting or management but I could learn a thing or two about it.
WHOOOOOOOOOOOOOOOOOOOO!!!!
I got ADB working on the Le Pan 2!!! Screw Le Pan and their locked down drivers!
I can't get root access yet, but I got a sysdump and am combing through it. Recovery doesn't show the device being plugged in and I can't figure out how to get into fastboot as of yet, but progress is being MADE!
There is not rush, in the mean time I opened a ticket at lepan.supportsync.com to see if they supply me with this driver. who knows I may get lucky.
rocketero said:
There is not rush, in the mean time I opened a ticket at lepan.supportsync.com to see if they supply me with this driver. who knows I may get lucky.
Click to expand...
Click to collapse
Been there, done that. Hopefully you'll have better luck, but their standard reply is to email two people from HQ if you are a developer, which I've also been there and done that. They don't reply. I'm fairly positive that we are on our own considering they didn't release the ADB drivers for the LP1 or LP2 as of yet and no source code for either, either. They are GPL-violators to the MAX. *puke*
We'll get it tho.
dbaybay said:
WHOOOOOOOOOOOOOOOOOOOO!!!!
I got ADB working on the Le Pan 2!!! Screw Le Pan and their locked down drivers!
I can't get root access yet, but I got a sysdump and am combing through it. Recovery doesn't show the device being plugged in and I can't figure out how to get into fastboot as of yet, but progress is being MADE!
Click to expand...
Click to collapse
Can you please upload somewhere zip with content of /system/lib/? One of the major problems community have with porting of ICS to any Qualcomm platform is absense of userspace video drivers (and inability to run hw-acceleration). TC979 seems to have hw-accel enabled in Honeycomb, which is quite close to ICS in this area.
ghuron said:
Can you please upload somewhere zip with content of /system/lib/? One of the major problems community have with porting of ICS to any Qualcomm platform is absense of userspace video drivers (and inability to run hw-acceleration). TC979 seems to have hw-accel enabled in Honeycomb, which is quite close to ICS in this area.
Click to expand...
Click to collapse
As soon as I can get ADB working in recovery or fastboot and have root access, I will be glad to, as I already said before. ADB is working when the device is running normally, but I do not have SU privileges. I can see the list of files, but can't copy, push, pull, or anything as of right now. My project for today is to get ADB working in fastboot so I can get root permissions.
dbaybay said:
As soon as I can get ADB working in recovery or fastboot and have root access, I will be glad to, as I already said before. ADB is working when the device is running normally, but I do not have SU privileges. I can see the list of files, but can't copy, push, pull, or anything as of right now. My project for today is to get ADB working in fastboot so I can get root permissions.
Click to expand...
Click to collapse
I thought adb pull /system/lib/ does not require root
ghuron said:
I thought adb pull /system/lib/ does not require root
Click to expand...
Click to collapse
Nor did I, but I'm getting permission denied for about everything except adb reboot [recovery / bootloader] or 'ls'. SU, Pull, Push, Root, Remount, etc. etc. etc. are giving me "permission denied" or "can't in manufactor mode" errors.
I'm working on getting it to work in Fastboot, but ADB just won't recognize the device in Fastboot no matter what I do. I'm at a loss right now, so any suggestions would be helpful. I'm gonna keep trying different methods to get ADB to work with root permissions.
Code:
$ pull /system/lib c:\users\admin\desktop
pull /system/lib c:\users\admin\desktop
pull: permission denied
$
A list of the contents is the best I can get for you atm - http://pastebin.com/ZqvXqE0Q
Those files are exactly what the HP Touch pad needs
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
are you sure you can't install superuser ?
PresidentMcCain said:
Those files are exactly what the HP Touch pad needs
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
are you sure you can't install superuser ?
Click to expand...
Click to collapse
110% positive.
I have no permissions to do anything except CD into folders and get a list, or reboot into recovery or bootloader. In bootloader ADB and fastboot do not recognize the device and the modified drivers do not work. We are working on it, but no such luck as of yet. As soon as I can gain SU permissions in ADB, I'll get you the files, don't worry.
dbaybay said:
110% positive.
I have no permissions to do anything except CD into folders and get a list, or reboot into recovery or bootloader. In bootloader ADB and fastboot do not recognize the device and the modified drivers do not work. We are working on it, but no such luck as of yet. As soon as I can gain SU permissions in ADB, I'll get you the files, don't worry.
Click to expand...
Click to collapse
just a simple question: how do you get out of bootloader mode? After I did "adb reboot bootloader", I got to a black screen with the text "Fastboot Mode" and then nothing works, not even the power button. Can't access it via USB either. Guess I can wait till the battery runs down, but there should be a simpler way...
Edit: never mind, the reset button worked
anonguy2 said:
just a simple question: how do you get out of bootloader mode? After I did "adb reboot bootloader", I got to a black screen with the text "Fastboot Mode" and then nothing works, not even the power button. Can't access it via USB either. Guess I can wait till the battery runs down, but there should be a simpler way...
Click to expand...
Click to collapse
Try holding power button + home button at same time for 10 seconds.
Bootloader/fastboot are the same thing from my understanding. When I use adb reboot bootloader, it reboots to my fastboot screen. I use the reset button, as you figured out to get out of it.
I need to get adb or fastboot.exe [platform tools] working in fastboot mode and I should have root access but no such luck.
Any Le Pan II users who managed to get the v116 update - did you get an update.zip placed on your SD Card that you can share? If I can get an properly signed update.zip with the stock ROM inside, I can most likely modify it for with SU access built in.
this may be a stupid question, does this app http://www.androidapps.com/finance/apps/299480-root-explorer-file-manager-speed-software give you root access or do you need to have root permission in order to use that app.
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Latest Supported Versions:
v7.1.5
Recent user reported supported version
v7.2.1
Awesome, want to try it when I receive my HD 7 this week...
Wrong thread sorry about that
Works perfectly. Thank you!
Sent from my KFTT using XDA Premium HD app
sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hi sparkym3!
Thanks for your tools!
I love your tools in TF300 and TF700!
One questions about TF300, do you know anything about the APX mode and useful tools in APX mode?
---------- Post added at 06:41 PM ---------- Previous post was at 06:05 PM ----------
sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hello, sparkym3!
Is there some mistake in the tool? Both the step 3 and step 5 are the same...
Code:
Step3:Checking for access...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Code:
Step5:Checking superuser...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
padest.com said:
Hi sparkym3!
Thanks for your tools!
I love your tools in TF300 and TF700!
One questions about TF300, do you know anything about the APX mode and useful tools in APX mode?
---------- Post added at 06:41 PM ---------- Previous post was at 06:05 PM ----------
Hello, sparkym3!
Is there some mistake in the tool? Both the step 3 and step 5 are the same...
Code:
Step3:Checking for access...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Code:
Step5:Checking superuser...
type isroot | adb shell | find "#"
if %errorlevel% == 1 goto NOTROOT
Click to expand...
Click to collapse
Both of those lines are checking for the "#" instead of the "$" to ensure that it has root access.
reverendkjr said:
Both of those lines are checking for the "#" instead of the "$" to ensure that it has root access.
Click to expand...
Click to collapse
Thanks.
I get it.
ADB is unresponsive
androitri said:
Awesome, want to try it when I receive my HD 7 this week...
Click to expand...
Click to collapse
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
Click to expand...
Click to collapse
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse
Interesting, I don't even have that file. I assume it is used to block devices so you could have one plug in for charging and ADB would just ignore it if it is not in the list.
Thanks, sparkym3
After I verified that ADB could see the KFHD7, I ran the 'RootQemu.bat' that was part of what you published. While it took a bit of time (about 1 minute) between reboots, it worked flawlessly. The Kindle Fire HD 7" I have is now rooted. I'll be looking next to replace the launcher, (probably Apex) and scrape the ads off of this.
Pat
Thanks
Thank you so much for this... really makes it easy and fast. However i was worried during the installation haha my device kept rebooting and it warning me to reconnect so i thought i was doing it wrong.
Well it seems that I messed up. Big time.
I got to step 3, and that's where all hell breaks loose. I get message on the cmd window which reads Cannot find specified file, and everything goes downhill from there. There's no more updating whatsoever. But that's not the bad part, I tried messing around with my kindle, and everything is now incredibly slow. The lag is unbearably bad. I'm in process of resetting everything to factory default at this moment.
EDIT: Just reset to factory default, everything is smooth again, but be careful when trying this exploit, things can go wrong!
I'm thinking there was something I did wrong, if this seems unfamiliar I'll list the steps I took in trying to manage everything. But I know you're thinking I did this on impulse, hence my low post count, but I have been lurking the kfhd subforum for a very long time now and have tried my best to educate myself. Sorry.
Vespus said:
I tried messing around with my kindle, and everything is now incredibly slow. The lag is unbearably bad.
Click to expand...
Click to collapse
That’s the result of the entry in /data/local.prop. If you remove that file and reboot, it will fix the lag.
I tried running the tool and it kept getting hung up on step 3, telling me something along the lines of file not found. I was able to root using the manual method though.
nvrmore100 said:
That’s the result of the entry in /data/local.prop. If you remove that file and reboot, it will fix the lag.
Click to expand...
Click to collapse
I suppose my method fixed it regardless
I'm thinking the reason my root backfired is because I wasn't as systematic as I should have been. Rooting my samsung vibrant allowed me to be a little more sloppy since there are backups and flashing is a cinch.
EDIT: This my 3rd time trying to get this thing to work, I get stuck on Step 3 "The system cannot find the file specified."
I really can't see how I'm managing to screw up this badly. Must be something stupid on my part.
EDIT2: Turns out I was using a crumby network directory the whole time, but even still it did not work. Fellows: Put the QemuRoot folder somewhere on your desktop, it's easier there. But after that the prompt would close immediately after step 4, so that took me a while to circumvent. Anyway, I ended up skipping to step 4 to get the superuser to work. I'm fairly sure everything DOES work, but it's hard to test right now.
PMcHargue said:
I picked up the downloads for the Qmenuroot. Installed the ADB drivers referred to in the OP. In my Win7 system's devices manager, I see the ADB driver for the Kindle Fire HD listed as working correctly. Also, the USB driver is in & working, and I can transfer files to/from the kindle. (though I had to re-install the USB driver after I installed the ADB driver)
The problem now is that when I type "ADB devices", it tells me that there are no devices available. Unplug/plug in the USB connection, wait for a bit, "ADB kill-server", "ADB devices" and still no devices available. I have a CMD prompt open in the correct directory. Tried rebooting the kindle, unplug/plug in the USB connector, all kinds of combinations.
I'd like to root this, in anticipation of a JB build for it, (or even ICS) but without ADB, I don't see how.
Has anyone had an issue like this that they have solved? I haven't mastered ADB in any sense, though I've used it to good effect before to un-brick my TF101.
TIA;
Patrick
---------- Post added at 09:35 AM ---------- Previous post was at 08:39 AM ----------
got it. My file,
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse
That's right! I have tested!
This is needed!!!
Thank you for work and contribution.
Thanks for the tip
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
worked!
KF HD has Superuser but no root access
sparkym3 said:
This tool will root your device based on my qemu local.prop root method.
Just download and unzip everything into a directory; then run RootQemu.bat from that directory (if you do not currently have the device drivers for your device, they are attached to this post, please install them, please use them to install your device before attempting the process).
A video with how to do this is available here http://forum.xda-developers.com/showthread.php?p=31728742
Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).
Helpful tip:
Make sure no other Android device is connected to your PC
Click to expand...
Click to collapse
Hi sparkym3
Thanks for all your hard work! I tried it though and it went through all the motions as if it was doing its job, like expected. But at the end of the rooting, I have superuser on the kf HD but no root access! ES explorer and Titanium have no root access. Tried rebooting several times. Still no root access. What could have gone wrong?
Cheers, mate!
A lot of people have questions about using ADB, so I decided to make a very simple guide to some basic ADB operations. This information is available all over XDA, but many people don't seem to like looking through other device threads.
ADB should function in recovery and when the tablet is normally booted.
Install ADB on your PC.
Download the attached ADB_files.zip
Create a folder to hold the ADB files (I will use C:\ADB) and extract the files to that folder.
Download and install the Samsung USB drivers (available HERE), or, install KIES to get the drivers.
On the tablet, go to Settings, Developer Options and enable USB debugging.
Connect the Tablet to your PC via USB cable.
Open a command prompt in your ADB folder. The text at the prompt should read C:\ADB. (You can just click on the Command_Prompt.bat to do this).
Verify ADB is working by typing "adb devices" (and hit ENTER) in the command window. You should see a device number listed for your tablet.
You are now ready to use ADB functions.
I have included in the zip a few .bat files to perform some of the basic commands for you. These commands will output files to your ADB directory.
Below are some of the common commands you can use with ADB for troubleshooting purposes:
- To boot into Download mode:
adb reboot download
- To boot into recovery:
adb reboot recovery
- To reboot:
adb reboot
- To get the last_kmsg (to troubleshoot kernel issues):
adb shell cat /proc/last_kmsg > last_kmsg.txt
- To get the dmesg:
adb shell su -c dmesg > dmesg.txt
- To get the logcat:
adb logcat -v time -d > logcat.log
The first time you use the "su" command, you may need to acknowledge the Superuser request on your tablet in order for the superuser permissions to be granted.
These are some very basic examples of what can be done with ADB, but they are very helpful when troubleshooting many issues. There are MANY other commands for ADB(that can be Googled).
There are also some apps that can do this for you, but I prefer to do these things manually most of the time.
Feel free to post any useful adb commands you use on a regular basis.
HOW TO GET A RECOVERY.LOG
If you are in your custom recovery:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following command:
Code:
adb pull /cache/recovery/*
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.
If you are booted into Android:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following commands:
Code:
adb shell
su
mkdir /storage/sdcard0
cp /cache/recovery /storage/sdcard0/recovery
exit
exit
adb pull /storage/sdcard0/recovery
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.
I have my GT-P5210 (wifi) rooted...
I have not been able to get ADB to work properly once
Wish I I had tried before I rooted this device.
I have tried via WifI & USB = no go.
Anyway no big deal I guess, running 'ES File Explorer' on a rooted device gives me all the power I need.
Just miss the convenience of sending a single APP from PC to Tablet (without cable) to install.
Well ok then..
I finally tried a different version of adb.exe than the one I originally used (was about 400kb), and now it's all working as expected..Yay
Maybe the version I tried was a bit dated ? not even sure where that is now, lol
done too much since, being a new pad owner and all.
Now I am able to make use of "Right Click APK" >> install via Wireless Connection.
No wires, no prompts.
Just wanted to post a follow up in case anyone thought I inferred 'rooting' somehow cost me ADB functionality
Very happy
:good:
(OP get's a +one for making me revisit the issue)
The best and most simple guide
it`s just what you need
Oxyandy said:
I have my GT-P5210 (wifi) rooted...
I have not been able to get ADB to work properly once
Wish I I had tried before I rooted this device.
I have tried via WifI & USB = no go.
Anyway no big deal I guess, running 'ES File Explorer' on a rooted device gives me all the power I need.
Just miss the convenience of sending a single APP from PC to Tablet (without cable) to install.
Click to expand...
Click to collapse
It's extremely easy to get ADB working on a Tab 3 10.1, just make sure USB Debugging is enabled and reboot. Press the bottom button of the Volume key and Power supply key at the same time. Then Samsung Galaxy Tab 3 10.1 will enter hboot mode.
calden74 said:
It's extremely easy to get ADB working on a Tab 3 10.1, just make sure USB Debugging is enabled and reboot. Press the bottom button of the Volume key and Power supply key at the same time. Then Samsung Galaxy Tab 3 10.1 will enter hboot mode.
Click to expand...
Click to collapse
I guess you missed Post #3 just after that one, I have it working no problem, I had to use a different version of ADB.EXE
Cheers and thanks for the kind offer of help
Oxyandy
cant get into recovery
gr8nole said:
A lot of people have questions about using ADB, so I decided to make a very simple guide to some basic ADB operations. This information is available all over XDA, but many people don't seem to like looking through other device threads.
ADB should function in recovery and when the tablet is normally booted.
Install ADB on your PC.
Download the attached ADB_files.zip
Create a folder to hold the ADB files (I will use C:\ADB) and extract the files to that folder.
Download and install the Samsung USB drivers (available HERE), or, install KIES to get the drivers.
On the tablet, go to Settings, Developer Options and enable USB debugging.
Connect the Tablet to your PC via USB cable.
Open a command prompt in your ADB folder. The text at the prompt should read C:\ADB. (You can just click on the Command_Prompt.bat to do this).
Verify ADB is working by typing "adb devices" (and hit ENTER) in the command window. You should see a device number listed for your tablet.
You are now ready to use ADB functions.
I have included in the zip a few .bat files to perform some of the basic commands for you. These commands will output files to your ADB directory.
Below are some of the common commands you can use with ADB for troubleshooting purposes:
- To boot into Download mode:
adb reboot download
- To boot into recovery:
adb reboot recovery
- To reboot:
adb reboot
- To get the last_kmsg (to troubleshoot kernel issues):
adb shell cat /proc/last_kmsg > last_kmsg.txt
- To get the dmesg:
adb shell su -c dmesg > dmesg.txt
- To get the logcat:
adb logcat -v time -d > logcat.log
The first time you use the "su" command, you may need to acknowledge the Superuser request on your tablet in order for the superuser permissions to be granted.
These are some very basic examples of what can be done with ADB, but they are very helpful when troubleshooting many issues. There are MANY other commands for ADB(that can be Googled).
There are also some apps that can do this for you, but I prefer to do these things manually most of the time.
Feel free to post any useful adb commands you use on a regular basis.
HOW TO GET A RECOVERY.LOG
If you are in your custom recovery:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following command:
Code:
adb pull /cache/recovery/*
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.
If you are booted into Android:
Make sure you have adb working on your PC (see above).
Connect your device to PC.
Open a command prompt; then CD to your adb directory.
Type the following commands:
Code:
adb shell
su
mkdir /storage/sdcard0
cp /cache/recovery /storage/sdcard0/recovery
exit
exit
adb pull /storage/sdcard0/recovery
You will get several files in your adb directory (log, last_log, last_log.1...etc)
Send those files to your developer.
Click to expand...
Click to collapse
Hello,
When I try to boot into recovery or when I use the above method to boot into recovery my Tab just goes to the
Samsung
GALAXY Tab3
screen and just hangs there
I can get into download mode but ever since I used oden to do recovery.tar.md5 file I have not been able to go into recovery
Any help would greatly be appreciated...
Thanks...
Tom
misterwright said:
Hello,
When I try to boot into recovery or when I use the above method to boot into recovery my Tab just goes to the
Samsung
GALAXY Tab3
screen and just hangs there
I can get into download mode but ever since I used oden to do recovery.tar.md5 file I have not been able to go into recovery
Any help would greatly be appreciated...
Thanks...
Tom
Click to expand...
Click to collapse
Flash the recovery all over again
Brought to you by SM-T210R
Note: adb is functioning correctly
The Tab just hanges when it should be going into recovery
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
I have done that a few times but will try again
Note: I also cant do a factory reset from within the OS...
Thanks...
Tom
misterwright said:
Note: adb is functioning correctly
The Tab just hanges when it should be going into recovery
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
I have done that a few times but will try again
Note: I also cant do a factory reset from within the OS...
Thanks...
Tom
Click to expand...
Click to collapse
Try to reflash rom, firmware and else
Brought to you by SM-T210R
darn
Ripshock said:
Flash the recovery all over again
Brought to you by SM-T210R
Click to expand...
Click to collapse
Reflashed using oden with the same results = I hold down power vol-up and home until the Samsung GALAXY Tab3 screen appears then I let off the power button and the Samsung GALAXY Tab3 screen just sits there
I have tried holding the home and vol-up keys for over a minute with the same results = the Samsung GALAXY Tab3 screen just sits there even after I release all buttons = I have to do a hard boot but then it loads the UI
Tom
misterwright said:
Reflashed using oden with the same results = I hold down power vol-up and home until the Samsung GALAXY Tab3 screen appears then I let off the power button and the Samsung GALAXY Tab3 screen just sits there
I have tried holding the home and vol-up keys for over a minute with the same results = the Samsung GALAXY Tab3 screen just sits there even after I release all buttons = I have to do a hard boot but then it loads the UI
Tom
Click to expand...
Click to collapse
Ok there is a way to flash a recovery or to check if it is there or not if you use twrp use its file manager but don't forget to mount /system or if you are using cmw u need aroma file manager google that, however the problem is idk where is the location of recovery mod so ask @gr8nole
Moreover have you checked if it is a bad download of recovery ofcourse and try other recoveries
Brought to you by SM-T210R
Ripshock said:
Ok there is a way to flash a recovery or to check if it is there or not if you use twrp use its file manager but don't forget to mount /system or if you are using cmw u need aroma file manager google that, however the problem is idk where is the location of recovery mod so ask @gr8nole
Moreover have you checked if it is a bad download of recovery ofcourse and try other recoveries
Brought to you by SM-T210R
Click to expand...
Click to collapse
It does say MD% verified while in Oden but I was thinking the same thing...
I could really use a link to "known good" firmware and rom and anything else that I need...
Thanks
Tom
misterwright said:
It does say MD% verified while in Oden but I was thinking the same thing...
I could really use a link to "known good" firmware and rom and anything else that I need...
Thanks
Tom
Click to expand...
Click to collapse
Well navigate through the forum
Brought to you by SM-T210R
I meant MD5 verified
but would love to try a different download of a recovery if you know of any...
Thanks
Tom
misterwright said:
I meant MD5 verified
but would love to try a different download of a recovery if you know of any...
Thanks
Tom
Click to expand...
Click to collapse
I already have said navigate through the forum! Amd good luck
Brought to you by SM-T210R
Ripshock said:
I already have said navigate through the forum! Amd good luck
Brought to you by SM-T210R
Click to expand...
Click to collapse
Thanks...
If I find a md5 file that works I will post a link
Tom
this worked THANK YOU gr8nole http://forum.xda-developers.com/showthread.php?t=2433853
misterwright said:
Thanks...
If I find a md5 file that works I will post a link
Tom
Click to expand...
Click to collapse
What version of the Tab 3 do you have?
Sent from my SCH-I605
gr8nole said:
What version of the Tab 3 do you have?
Sent from my SCH-I605
Click to expand...
Click to collapse
SM-T210R
Tom
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
gr8nole said:
What version of the Tab 3 do you have?
Sent from my SCH-I605
Click to expand...
Click to collapse
gr8nole,
I found your CWM v6.0.4.8 and flashed and now everything is great
Thank You so much!!!!!!
Tom
---------- Post added at 02:03 PM ---------- Previous post was at 01:21 PM ----------
Ripshock said:
I already have said navigate through the forum! Amd good luck
Brought to you by SM-T210R
Click to expand...
Click to collapse
I clicked thanks on 5 of your post but, I still wanted to tell you how much I appreciated your help!!!!
Tom
misterwright said:
SM-T210R
Tom
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
gr8nole,
I found your CWM v6.0.4.8 and flashed and now everything is great
Thank You so much!!!!!!
Tom
---------- Post added at 02:03 PM ---------- Previous post was at 01:21 PM ----------
I clicked thanks on 5 of your post but, I still wanted to tell you how much I appreciated your help!!!!
Tom
Click to expand...
Click to collapse
Glad it worked
Brought to you by SM-T210R
Hey guys,
I try to root my OpO with the XDA Toolbox. When I try to install TWRP or other Recovery I get in the cmd the error:
error: cannot open 'C:/Users/Martin/Documents/Opo'
Click to expand...
Click to collapse
I hope someone can help me.
SirMrMartin
My suggestion is to not use any toolkit and follow the step by step guides available on XDA instead.
Look for timmaaa thread in general section
Step 1 backup everything you want to keep
Step 2 is unlock boot loader (which will wipe your phone clean, that's why step 1 is backup everything lol)
Continue from there using the guide
This way you learn proper commands and the method instead of not knowing wtf you're doing and not knowing how to fix things if you come across any problems.
Cheers
---------- Post added at 07:41 PM ---------- Previous post was at 07:37 PM ----------
Also make sure you know where the files are that you downloaded. My suggestion is desktop make a folder called opo and download everything in there
Google and download "15 second adb installer" that will install the required drivers. So this way you just open command window in the folder (hold shift+ctrl+right click > choose open command prompt here) with all your files and don't need to put files in the SDK folder etc.
Forget the toolkit, they're more trouble than they're worth. Plus, you'll gain valuable experience by doing it yourself, experience that you're gonna need when something goes wrong in future. Check out my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471