Database Info

[guide] how to root optimus net p690

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

[ROOT][TOOL]Qemu automated root [09/18/2012]

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!

[Q] Setting up ADB for my Vibrant on Mac OS X

I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.

Ironcheeks said:
I've been following this guide http://forum.xda-developers.com/showthread.php?t=1917237&nocache=1 to set up ADB for my phone and macbook, and when i try the "./adb devices" command to try and ID my device, it isn't working. Ive already downloaded the SDK package from the website, copied and pasted "adb" and "fast boot" into the root of my sdk file in the bundle. I included some snapshots in case I'm inputting the file path incorrectly. Any help would be awesome! My power button stopped working on my phone so I'm trying to set up ADB so i can just adb reboot whenever my phone shuts off or anything like that. The first screenshot is my current file path for the adb and fastboot files and the second is just my attempts at trying the "./adb devices" command.
Click to expand...
Click to collapse
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.

Lgrootnoob said:
First, it's impossible to access your phone's adbd server when it is off.
And adb needs to be in the current folder.
Use ls to see the contents of the folder you are in.
You should try ./adb first.
It's better to boot hirens boot cd.
Then use the tool in my signature.
An even better way to do this is to trust your technolust and take your phone apart and try to identify and fix the problem, or put it back to stock and send it in for warranty.
Click to expand...
Click to collapse
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!

Ironcheeks said:
Thanks for giving such a helpful response what do you mean by adb needs to be in the current folder? and what is Is?
And I'm definitely planning on taking it apart. As soon as i can find a small enough screwdriver somewhere on campus, ill get right on it. Thanks again!
Click to expand...
Click to collapse
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?

Lgrootnoob said:
Your welcome!
I'm happy to help any time.
the . indicates the current folder(directory)
so when you type ./adb
it executes the adb file in . (the current folder)
ls is a command for listing the contents of the current folder. (Just like the dir command on windows)
Before you type ./adb you would want to make sure that adb is in . (The current folder)
Get it?
Click to expand...
Click to collapse
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?

Ironcheeks said:
Ahhh that makes sense.. so when I'm running terminal and since the adb file is in the sdk folder, i should make the command path (cd /Users/..etc) go up to the sdk folder in this case?
Click to expand...
Click to collapse
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery

Ironcheeks said:
Nevermind! got it to work after doing the above^. Thanks again for your help so any helpful adb commands i should know about? all i know is adb reboot and adb reboot recovery
Click to expand...
Click to collapse
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/

Lgrootnoob said:
adb start-server
adb kill-server
adb push file destination
adb pull file destination(>optional)
adb shell (Open a terminal on the device in your pc terminal window)
adb reboot
adb reboot-bootloader(Only useful if your device will stay at the bootloader for fastboot stuff eg: nexus and htc devices)
adb reboot recovery
examples for adb pull would be
adb pull /sdcard/dcim/
adb push doggy.jpg /sdcard/Download/doggy.jpg
There has got to be an adb guide here somewhere on Xda.
If not then go look up some common adb commands.
Have fun with adb.
(I'm anxious to see you fix your phone.)
---------- Post added at 01:48 PM ---------- Previous post was at 01:32 PM ----------
I'm also sure that you know to use the ./ before adb with all of these commands right?
adb guide for windows
Even though its an adb guide for windows, im sure you'll be able to get just as much knowledge from it.
They also might have something on xda university for this stuff.(Which you should totally check out )
http://xda-university.com/
Click to expand...
Click to collapse
Thank you for all your help!

possible bricked Tf300t

Hi there guyz......not a newb....but not a pro.....usually sit back and read........but I was trying to change my recovery from TWRP to CM an some how i think I bricked my tab.....tablet boots to main asus screen......with unlocked in top left and nvidia in lower right......thats it....I cannot shut it down or get into recovery.....any help....thanx in advance !

_shakabra_ said:
Hi there guyz......not a newb....but not a pro.....usually sit back and read........but I was trying to change my recovery from TWRP to CM an some how i think I bricked my tab.....tablet boots to main asus screen......with unlocked in top left and nvidia in lower right......thats it....I cannot shut it down or get into recovery.....any help....thanx in advance !
Click to expand...
Click to collapse
Does it connect to fastboot using the universal naked drivers? If so, try this: http://forum.xda-developers.com/showthread.php?t=2425581

Nope..... It's was stuck on the Asus loading page all day..... Wouldn't shut down or anything........ It is currently dead battery...... I have connected the charger...... But got no charging light on the power button!

i think im having a similar issue. Charged up my tablet since i havent used it in a while. Went to go into recovery and it wont boot. Stuck on ASUS screen. Im on the old boot loader.for 4.1 and i dont know how to upgrade. I can boot back into the rom and use the tablet etc but no recovery.

Help
I am in the strangest situation.
Apparently while trying to upgrade CM 4.3 I flashed the wrong TWRP and checked closely because I love CWM-R
I have lost fastboot capabilities but with using the "adb reboot bootloader" I can get into android 4.3 (no GAPPS).
With any reboot it takes me to the ASUS screen and then directly to TWRP version 2.6.3.0
However nothing seems to work in there. I have used adb to push file to the tablet and when I hit install from the zip nothing happens even though I saw the file, then it disappears. All except system will not let me format etc. ADB does work and at time the TWRP will let me use ADB Sideload.
The problem is getting to install a new TWRP that works and sees a micro SD card. Also I have installed zip files hundreds of times but everything I see for this all I find are blob and img files to down load and have no idea how to make them install when all explain use of the fastboot. I do not believe I am bricked but it ain't good!
Any help greatly appreciated. The problem is getting to install a new TWRP that works and sees a micro SD card.
norm883

_shakabra_ said:
Nope..... It's was stuck on the Asus loading page all day..... Wouldn't shut down or anything........ It is currently dead battery...... I have connected the charger...... But got no charging light on the power button!
Click to expand...
Click to collapse
Asus repair is probably your only option. If it cant charge or boot up, theres nothing I can do.
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
norm883 said:
I am in the strangest situation.
Apparently while trying to upgrade CM 4.3 I flashed the wrong TWRP and checked closely because I love CWM-R
I have lost fastboot capabilities but with using the "adb reboot bootloader" I can get into android 4.3 (no GAPPS).
With any reboot it takes me to the ASUS screen and then directly to TWRP version 2.6.3.0
However nothing seems to work in there. I have used adb to push file to the tablet and when I hit install from the zip nothing happens even though I saw the file, then it disappears. All except system will not let me format etc. ADB does work and at time the TWRP will let me use ADB Sideload.
The problem is getting to install a new TWRP that works and sees a micro SD card. Also I have installed zip files hundreds of times but everything I see for this all I find are blob and img files to down load and have no idea how to make them install when all explain use of the fastboot. I do not believe I am bricked but it ain't good!
Any help greatly appreciated. The problem is getting to install a new TWRP that works and sees a micro SD card.
norm883
Click to expand...
Click to collapse
Have you seen this:
http://forum.xda-developers.com/showthread.php?t=2403674
---------- Post added at 01:56 PM ---------- Previous post was at 01:55 PM ----------
olster said:
i think im having a similar issue. Charged up my tablet since i havent used it in a while. Went to go into recovery and it wont boot. Stuck on ASUS screen. Im on the old boot loader.for 4.1 and i dont know how to upgrade. I can boot back into the rom and use the tablet etc but no recovery.
Click to expand...
Click to collapse
Did you try reflashing the recovery with the correct TWRP verison from fastboot or the tablet in Android?

Follow-up
cmendonc2 said:
Asus repair is probably your only option. If it cant charge or boot up, theres nothing I can do.
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
Have you seen this:
Did you try reflashing the recovery with the correct TWRP verison from fastboot or the tablet in Android?
Click to expand...
Click to collapse
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883

norm883 said:
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883
Click to expand...
Click to collapse
That is very doable, just google it.

norm883 said:
Yes I did see that. It was what got me to the adb possibility. However I am not able to fast boot due to the fact that it goes straight to the TWRP on any start. And the TWRP is dysfunctional. My only choice I can see is going to be terminal emulator and I am not sure of its capabilities.
norm883
Click to expand...
Click to collapse
Try to send "adb reboot-bootloader" command from Your PC. Or You can try "reboot bootloader" command in TWRP terminal.

Have done that, "partial brick"
Graiden05 said:
Try to send "adb reboot-bootloader" command from Your PC. Or You can try "reboot bootloader" command in TWRP terminal.
Click to expand...
Click to collapse
That does work, but the problem is it does not stay. You need to do each time you want to use the table (shut down / reboot etc.). But it does allow me to boot into Android 4.3 but it is only a partial load since GAPPS was never loaded. I can push via ADB but nothing seems to stick! I believe all except /system has a no write or no permission granted. In the Android part (4.3) with Root Explorer I have granted the permissions? It appears that TWRP is both the bootloader (fastboot) and recovery. So any fastboot commands are futile, (waiting for device. I did see somewhere there is an administrative function for fastboot but have not been able to locate in all my readings. Except one persons mention of it to eliminate the waiting for device.
norm883

Partial Brick
If this helps anyone I found in a post:
I used it in Terminal Emulator while in Android 4.3 from (adb reload bootloader)
• # dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
• # dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
• # reboot
This now stops when I reboot or turn off the tablet from going directly to TWRP which basically allows me to do nothing, except pretend to do ADB then on a reboot nothing happened.
norm883

Terminal Emulator in Android 4.3
Can anyone tell me where to read on how to use this?
ADB commands seem much different and really need to know how to push from microSD etc and do not setup.
Files I wanted to push I placed in the same folder as the program on the base of C:\ but do not understand how to map here.
I will read and nice to have examples.
Thanks,
norm883

norm883 said:
Can anyone tell me where to read on how to use this?
ADB commands seem much different and really need to know how to push from microSD etc and do not setup.
Files I wanted to push I placed in the same folder as the program on the base of C:\ but do not understand how to map here.
I will read and nice to have examples.
Thanks,
norm883
Click to expand...
Click to collapse
To push file to tablet microSD through adb:
tablet booted into android
adb push C:\\some_file /Removable/MicroSD/
tablet booted into TWRP(don't remember path for sure)
adb push C:\\some_file /ext_sdcard/
To get file from tablet internal memory:
adb pull /sdcard/some_file C:\\some_path\
or
adb pull /sdcard/some_file -should put file in directory where cmd now.

BAHHH Hummbug
Graiden05 said:
To push file to tablet microSD through adb:
tablet booted into android
adb push C:\\some_file /Removable/MicroSD/
tablet booted into TWRP(don't remember path for sure)
adb push C:\\some_file /ext_sdcard/
To get file from tablet internal memory:
adb pull /sdcard/some_file C:\\some_path\
or
adb pull /sdcard/some_file -should put file in directory where cmd now.
Click to expand...
Click to collapse
All seem to be different say directory does not exists etc Crazy program.
Is it possible that from a corrupt there could be 2 layers here? Because in the recovery mode it tells me that there is not OS installed?
Yet I know I can boot to CM Android 4.3.
Wish I could think of a way to clear and start fresh, but without fastboot I am up the creek.
Thanks,
norm883

[Q] Looking for a way to turn on USB Debugging on phone w/ smashed screen

Hi,
was using this guide online to try to recover and move stuff around in my Nexus5 while it is broken as far as i know this is a LCD problem not a digitiser problem.
http://www.techlife.net/2014/09/access-your-android-device-after-breaking-your-screen.html/
http://forum.xda-developers.com/showthread.php?t=2786395
ran into a problem that I can't turn on USB Debugging on my phone without being able to see what i am pressing.
According to the end of the guide it told me to flash a kernel with USB debugging enabled by default but I am unsure of what this means.
Rooted: No (I dont mind if i have to)
Fastboot: No idea
Installed ADB on computer: Yes

The custom kernel will need to have USB debugging ON by default/on boot. Usually through a custom initrc.

If you manage to get rooted, you could try:
androidscreencast

- Flash TWRP if you haven't already
- boot to recovery
- adb shell
- mount system
- edit build.prop
- reboot
- figure out adbkey.pub stuff
I have gone the same way, but could not get a screen display. It was on my wife's Gnex though. The rest works.
Now to get debian or something installed...ultralow power wireless server.

You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot

joegestes said:
You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
Click to expand...
Click to collapse
OP, try this.

The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.

Bubble-be said:
The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.
Click to expand...
Click to collapse
recoveries have adbd enabled by default. what we're doing here is making the OS have adbd enabled.

Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802

get a USB OTG cable and connect your mouse to your phone

Bubble-be said:
Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802
Click to expand...
Click to collapse
Huh...
Even if display isn't coming on... You can 3bc to fastboot, press down twice (iirc) and press power. wait a few secs, custom recovery should be running.
`adb shell` .. out of android, adb running. profit.

I think the OP is not rooted, nor does he have a custom recovery.
In that case you will need boot temporarily into a custom recovery that will allow root ADB shell access.
Download the TWRP recovery image to you PC.
HERE
For simplicity, rename the file recovery.img
Place the renamed file in your \sdk\platform-tools folder on PC.
Turn off you phone and then hold volume up button while pressing power button to get into fastboot mode.
Then, open a command prompt from within the platform-tools folder and run the following command:
fastboot boot recovery.img
Your phone should reboot into TWRP recovery.
You can then run the ADB commands outlined in my first post to enable usb debugging:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
Best of luck

Bubble-be said:
The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.
Click to expand...
Click to collapse
This is incorrect.
I do not need usb debugging enabled to run ADB shell in custom recovery.
Bubble-be said:
Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802
Click to expand...
Click to collapse
Huh
My post clearly stated via recovery
---------- Post added at 06:31 PM ---------- Previous post was at 06:13 PM ----------
4n3ver said:
get a USB OTG cable and connect your mouse to your phone
Click to expand...
Click to collapse
I've never tried this, but think you need to be rooted and install some hacks to get a mouse
to work via OTG.

Hello again,
Thanks for all the replies so far.
Unfortunately i'm still unable to enable USB debugging.
I'm getting stuck, I have managed to install adb and fast boot using the 15 second thing but am unable to get it to detect via "adb devices" and am currently troubleshooting this step
I can't upload images so i'm just gonna type what it says
Code:
C:\Users\blah> fastboot boot recovery.img
<waiting for device >
^C
C:\Users\blah> adb devices
List of devices attached
C:\Users\blah>
probably something to do with how my adb drivers are installed
Just to clarify my screen is impossible to use as its just coloured lines due to cracks in the LCD screen.
Hopefully all goes well and i'll be able to fastboot TWRP with the instructions you guys have given me.

fuzznuzz said:
Hello again,
Thanks for all the replies so far.
Unfortunately i'm still unable to enable USB debugging.
I'm getting stuck, I have managed to install adb and fast boot using the 15 second thing but am unable to get it to detect via "adb devices" and am currently troubleshooting this step
I
Click to expand...
Click to collapse
Your welcome.
It's probably just simple a driver issue. You will need to look in Device manager on PC while phone is connected.
Download the howto_driver.zip from the "15 seconds ADB Installer thread" and follow the picture tutorial contained in the zip file. This should fix your connectivity issues:good:
---------- Post added at 03:23 AM ---------- Previous post was at 02:58 AM ----------
If it helps, I don't have the "Android Bootloader Interface" driver option. So for me,
selecting "Android Composite ADB Interface" allows me to detect my Nexus5 in both ADB and Fastboot mode.
Keep in mind, my OS Win7 64bit and my 64 bit ADBdriver package may be entirely different than yours.

Okay i'm having some other problems now
can anyone help?

fuzznuzz said:
Okay i'm having some other problems now
can anyone help?
Click to expand...
Click to collapse
Your bootloader is locked.
Sent from my Nexus 5 using XDA Free mobile app

fuzznuzz said:
Okay i'm having some other problems now
can anyone help?
Click to expand...
Click to collapse
Locked bootloader
It is the first question I or anyone replying should have asked you.
Unfortunately, as far as I know, it's game over recovering any user data with
a busted non-viewable LCD, no USB debugging and a locked bootloader.
Unless, you can by some luck, miracle or Power of the Force, pull off using your touchscreen to enable USB debugging.
Then you could use Simple ADB Backup or Holo Backup to get your data.
If not and your data is important enough to you, then replacing the screen would be your last option.
Worth replacing IMHO because your Nexus 5 is still a really great phone with nice specs and plenty of power.
Found one HERE shipped from China for $46.76 or HERE from USA $69.99 from US on ebay.

didn't work
joegestes said:
You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
Click to expand...
Click to collapse
i followed all these steps and adb devices shows nothing while phone is in recovery mode
fastboot devices shows my phone when in fastboot mode
just adb not working
help asap please

halo_95 said:
i followed all these steps and adb devices shows nothing while phone is in recovery mode
fastboot devices shows my phone when in fastboot mode
just adb not working
help asap please
Click to expand...
Click to collapse
Do you have a stock recovery or a custom one?
You'll need to boot a custom recovery, not the stock recovery.
Now that you don't have to install the custom recovery, just boot it.