Database Info

Major problem - tf101 bricked

I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)

need more info
what model number do you have, what can you get into, what cant you get into etc

lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.

You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf

baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.

What is the serial number of your tf?
Hopefully it's one that's nvflash compatible

baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90

i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.

I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.

gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?

The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?

roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?

If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.

gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?

joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.

In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??

gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.

Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.

gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...

Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision

With JB installed: CWM Recovery causes a hang when I try to load into it.

Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Edit: Forgot to also ask, am I just an idiot?

badfontkeming said:
Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Click to expand...
Click to collapse
I have the same issue, no fix yet.

untermensch said:
I have the same issue, no fix yet.
Click to expand...
Click to collapse
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.

I have the exact same problem so I right there with ya
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.

badfontkeming said:
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.
Click to expand...
Click to collapse
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.

EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
I've noticed the same issue, it exists with the latest TWRP flashed via fastboot as well.
The problem with flashing via the terminal is that we don't have root yet, and need a recovery to get it. Looks like the only option is to wait for a fix.

EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
Yeah... the issue is, the reason I'm trying to flash CWM is so I can get root.

krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?

sparky28000 said:
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?
Click to expand...
Click to collapse
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265

krhainos said:
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265
Click to expand...
Click to collapse
Now there is atleast 3 people since I bricked mine also

krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
just curious how are you able to get in APX mode it seems I cant even do that

Drgravy said:
just curious how are you able to get in APX mode it seems I cant even do that
Click to expand...
Click to collapse
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.

krhainos said:
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.
Click to expand...
Click to collapse
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient

Drgravy said:
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient
Click to expand...
Click to collapse
I used the reset hole in place of the power button when fiddling with button combinations. Hold down VOL+, and poke the reset hole with a paperclip and that'll get you in APX mode -- not like it does any of us any good.

I thought I had bricked mine...
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim

I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.

jdeatsch said:
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim
Click to expand...
Click to collapse
Not working for me at all...

untermensch said:
I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.
Click to expand...
Click to collapse
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
---------- Post added at 10:46 PM ---------- Previous post was at 10:40 PM ----------
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse
Weird. When I try to edit this post, I only get 3/4 of the quote and none of my actual post to edit. Anyway...
Just wanted to clarify: not asking for directions. If the file is what I think it is, I know what I'm doing. I just want to know that the file is what I think it is.

It is the Jelly Bean recovery kernel and the ClockWorkMod ramdisk repacked with mkbootimg, then blobpack,
then I added the "-SIGNED-BY-SIGNBLOB-" header with a hex editor. it seems like ADB does not work but I
was able to root with an update.zip
I installed this with fastboot and erased and re-flashed 4 time's before posting to make sure
it would not cause instant brick.
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse

LG-P870 LG Escape: How to root, KDZ and other info

Seeing as there isn't a section for the LG P870/LG Escape I'm going to try and get as much info condensed into one thread for now.
Not even sure how popular this phone is but, hopefully this will be of some use to someone.
KDZ:
I know this isn't posted anywhere so here is the v10f KDZ from LG. It is the latest firmware as of 11/6/2012:
http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP870/AATTBK/P87010f_00/P87010f_00.kdz
If you don't know how to flash a KDZ I will make a guide here soon. V10f is rootable using the method below as is v10c
Download Mode:
To get into download mode turn off your phone, press and hold the vol+ and vol- keys, with those held down insert the USB cable while continuing to hold down the keys. After a few seconds phone will enter download mode automatically.
Rooting:
I was able to root my phone that has v10c on it using this tool:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
I used 1.6 of the root script but some say that 1.2 works better for them. I would try 1.6 if that doesn't work try 1.2 if it fails the first time run it a second time and it should work.

Thanks! My wife just got this. I was able to root and update and retain root with OTA rootkeeper. Was looking for a kdz just in case. If there's enough interest i will see if i can port TWRP so we can cook up some custom roms.

I am definitely interested in custom roms, I have this device. Its not bad considering the price and what you get. 1494 on geekbench too! Pretty decent!
---------- Post added at 07:49 PM ---------- Previous post was at 07:44 PM ----------

Thanks for the effort

Aye guys I'm new into rooting and android in general, but I don't really understand how to root this phone. Kinda been looking around for a while and I was wondering if you can write some sort of guide. As of now I'm pretty lost the other threads aren't giving me any general information on exactly how to root the LG P870 or androids in general.
-Thanks
Btw I understand what exactly what rooting does to your device and the purpose of rooting, its just exactly how to root the device.

Well first things first do you have the android SDK installed on your computer

cyclejim said:
Well first things first do you have the android SDK installed on your computer
Click to expand...
Click to collapse
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Urabewe said:
Rooting:
I was able to root my phone that has v10c on it using this tool:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
I used 1.6 of the root script but some say that 1.2 works better for them. I would try 1.6 if that doesn't work try 1.2 if it fails the first time run it a second time and it should work.
Click to expand...
Click to collapse

He
GHazard said:
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Click to expand...
Click to collapse
Download the zip and unzip it to your desktop. Go into your phone's settings and go to developers options. Turn on USB debugging. Go back to settings and go to security. Turn on unknown sources. Now plug your phone in and run the .bat file that you just unzipped. Follow the commands on the and that should be it. Good luck!

Thanks for the effort

GHazard said:
Alright now what lol.
As of now I have Eclipse with android sdk installed on it and the newest version of java. Whats next, and spefically whats a KDZ and what is he talking about here:
Click to expand...
Click to collapse
KDZ is the LG format for ROMs which is the built in read only memory that hold the instructions for the phone to run the hardware and features.
But I just rooted my phone with a combination of the above files, and it didnt go exactly as I hoped. First I ran the v1.2 batch file linked above, (the 1.6 batch file archive is invalid and doesnt extract properly. It seemed like it ran properly, i did the restore (no data destructive you shouldnt lost any data) but I didnt have root when completed. Then I tried the v17 of the original thread which can be found here http://forum.xda-developers.com/showthread.php?t=1886460
That one also ran but failed at the end saying something about me not having root on the phone.
I than ran the v1.2 batch file not once, but twice in a row. The second time I found my phone operating in "emulator mode" in other words, it was running laggy as hell and very slow. I then ran the V17 batch file from the link above, and boom it worked. So as you can see it wasnt typical, but I think if you dont have success with the 1.2 the first time, run it again, if it still didnt work, try running v17 like i did. I now have root and my phone is working fine.

Basically, I got the Escape then got the Nexus7 and have been involved in that. Really haven't been doing much with the Escape. I will be looking into more for everyone and hopefully get a custom recovery at the very least. Then at that point we can start thinking about rom. Until then we are stuck with what we have. I will get more info for everyone , till then this is what we have. If you think you can help go for it. If not sorry but this is the best info there is for our phone . I will positively without a doubt post any new info here so if that's what you are looking for this is the right place until then, thank you and you are welcome.
Sent from my Nexus 7 using xda premium

Markyzz said:
He
Download the zip and unzip it to your desktop. Go into your phone's settings and go to developers options. Turn on USB debugging. Go back to settings and go to security. Turn on unknown sources. Now plug your phone in and run the .bat file that you just unzipped. Follow the commands on the and that should be it. Good luck!
Click to expand...
Click to collapse
So when I run the .bat file do I just run it in cmd? I'm kinda knew at this lol.
Also does my phone have to be in download mode?
Sorry for the inconvenience but where exactly do I run the .bat file?
-Thanks
One more thing I never downloaded a .zip or .rar file.. Could you please leave me a link?

Rooted
Thanks people I guess I just needed time to figure it out lol. I ran it in cmd twice(1.2v) but not right after each other and the second time it worked thanks guys.
Well. I tried to install beats audio but now it won't even load up just boot loops when it gets to at&t...

Bricked
Great the first bricked lg p870 lol, anyone know how to fix this. Or is it just a brick?

Sorry for the repititive posts, but so far I have gotten my device to read by my computer. The only thing is I can see it in the Device manager but it never shows up in my computer. It also picks the phone up in cmd, is there sometype of command I can run to flash the device and put it back to normal?

GHazard said:
Sorry for the repititive posts, but so far I have gotten my device to read by my computer. The only thing is I can see it in the Device manager but it never shows up in my computer. It also picks the phone up in cmd, is there sometype of command I can run to flash the device and put it back to normal?
Click to expand...
Click to collapse
No command. You need to flash the kdz using lg flash tool.
Sent from my MB886 using xda premium

Markyzz said:
No command. You need to flash the kdz using lg flash tool.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Is their a guide on how to flash the device using the kdz flash tool? I mean my phone won't turn on though. It goes into the lg logo then just goes black (the back light is still on).

K I have all the tools but
I downloaded every tool from this thread
But in the PDF guides it says to put the phone in Upgrade mode by removing the SIM, battery and SDC(Micro sd card?) so I did that. Then insert the usb while holding the Volume Up button. All that happens on my phone is the home keys on the bottom just flash. And my phone doesn't connect to my computer either.

My Notes on LG P870
Ok I have fixed my device, well twice now. It seems whenever you try to change any file within the root it restarts, then boot loops. I tried too change a font using Rom Toolbox, it restarted then boot looped. I rooted the device using the 1.2v script once, but this time I'll try 1.7v and see if I can change fonts etc.
Are any of you guys having any problem with this?
If you do, and you are soft bricked just:
Download UPK 3.7.1
Then open up LG /mobile Update
Click Install Drivers(Make sure your phone is not connected) Choose your phone and carrier
Let that finish(Gonna take awhile you have to install all of them)
Then click Install updates...Done

Worked
Posting confirmation for an LG Escape (p870). 10f rooted using the tools linked in first post. Used version 1.2 to start and had to use the version 17 of the other rooting kit to finalize like another user encountered as well. Thanks will be given if they haven't been yet.

[Q] Ultra-newbie: Help! tf3oot stuck bootloading; locked & unrooted.

Progress circles keep circling til battery dies. Coldboot didn't work. (Although Asus said I shouldn't try android icon.)
Don't want to wipe data if I don't have to because I was in the middle of backing up data when it got stuck (can I connect it to my 2 1/2 yr. old laptop to copy files I need?)
Have all updates except last one two weeks ago. Not under warranty.

hi
Try to connect it to PC when you turn it on..if your computer recognized it...other wise no way to copy data as far as i know..(I am also not a PRO).
For your tablet to boot again i think go into recovery and then wipe everything and it ll re format your tablet then it should be in factory condition.
If this dosent works try my guide see the first posts in here u ll find it!!..
Hope u ll recover it!

You should be able to pull some files, but I don't think you'd be able to get your app data back. The same thing happened to me not too long ago unfortunately and in the end I did end up having to wipe the data. You could try flashing a .blob file. Here's the thread I made, there's good advice in there:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.

Can't Find adb download link
UndisputedGuy said:
You should be able to pull some files, but I don't think you'd be able to get your app data back. The same thing happened to me not too long ago unfortunately and in the end I did end up having to wipe the data. You could try flashing a .blob file. Here's the thread I made, there's good advice in there:
http://forum.xda-developers.com/showthread.php?t=2253834
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Spent 45 min trying to find adb download link (without whole sdk if possible). Where is it.
Did you flash a .blob file?
Like your motto

pjspener said:
Spent 45 min trying to find adb download link (without whole sdk if possible). Where is it.
Did you flash a .blob file?
Like your motto
Click to expand...
Click to collapse
I did flash a .blob file but it didn't work for me. I downloaded the whole Android SDK as mentioned in the guides on the forum
And thanks
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.

How to find Link to sdk with adb
UndisputedGuy said:
I did flash a .blob file but it didn't work for me. I downloaded the whole Android SDK as mentioned in the guides on the forum
And thanks
Sent from my R800i using xda-developers app.
It's nice to be important, but it's more important to be nice.
Click to expand...
Click to collapse
Forgive my ignorance. That link didnt lead me to an sdk with adb in the directories, which sdk do I use?
Also, I cant figure out how to get a list of the guides on this forum or all forums.
Thanks!

If you want to use ADB to try and pull your files, then download the Android SDK from here:
http://developer.android.com/sdk/index.html
You can search on Google for guides on how to use it and try asking if you get stuck
This guide should help you in using Fastboot commands (Method 2):
http://forum.xda-developers.com/showthread.php?t=2187982
While it does say it's for Unlocked Bootloaders, it works on Locked Bootloaders too if I'm not mistaken. The way I saw it when I did it was that I had nothing to lose and it did seem to complete the command just fine although it didn't work after that and I had to wipe the data.

adb devices command didnt work
UndisputedGuy said:
If you want to use ADB to try and pull your files, then download the Android SDK from here:
http://developer.android.com/sdk/index.html
You can search on Google for guides on how to use it and try asking if you get stuck
This guide should help you in using Fastboot commands (Method 2):
http://forum.xda-developers.com/showthread.php?t=2187982
While it does say it's for Unlocked Bootloaders, it works on Locked Bootloaders too if I'm not mistaken. The way I saw it when I did it was that I had nothing to lose and it did seem to complete the command just fine although it didn't work after that and I had to wipe the data.
Click to expand...
Click to collapse
"adb devices" didn't work for me either, how did you make it work? I'm in the same place you were.
Also are there separate adb drivers?
Thanks

Rooted, stock ROM, but can't install 4.4.2 OTA with CWM

Every time I try to flash the OTA update, it first asks me if I want to install the untrusted zip, which doesn't make much sense, because why would an OTA be untrusted?
Then, during the installation, it aborts for some reason. After that it asks if I want to fix root.
I have no idea why any of this is happening, but I can't install the update because of it. What should I do?
Sent from my Nexus 5 using Tapatalk

There should be a reason in recovery why it failed. We'd need to know it before we can help
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

For me at least (I didn't start this thread), it fails because Roboto-Bold.ttf contains unexpected content.
I don't recall ever changing Roboto-Bold.ttf, so I have no idea what about it is unexpected.

CarpeNivem said:
For me at least (I didn't start this thread), it fails because Roboto-Bold.ttf contains unexpected content.
I don't recall ever changing Roboto-Bold.ttf, so I have no idea what about it is unexpected.
Click to expand...
Click to collapse
It's a non standard font installed by something. If you have anything non standard on your phone the ota will fail

Thank you. I understood that.
What I meant to say is, how do I correct it? Where can I find a copy of Roboto-Bold.ttf that the update will be "expecting"?
And then, if/when it complains about another file being unexpected, where did I find THAT? etc, etc.

CarpeNivem said:
Thank you. I understood that.
What I meant to say is, how do I correct it? Where can I find a copy of Roboto-Bold.ttf that the update will be "expecting"?
And then, if/when it complains about another file being unexpected, where did I find THAT? etc, etc.
Click to expand...
Click to collapse
You need to read this http://forum.xda-developers.com/showthread.php?p=47369234. Basically you need to flash the stock system.img

Those instructions include "attach phone to computer while phone is in fastboot mode".
However, when I do that, when I attach my phone to the computer while in fastboot mode, my Nexus 5 is NOT SHOWN when I type "adb devices" OR "fastboot devices".
When my phone is in recovery mode, and I type "adb devices", then it IS shown. Additionally, if my phone is fully booted up as normal, if I type "adb devices", it IS shown then too.
But if there are things which need to be done from the computer at the command prompt (and it seems that there are) while the phone is in fastboot mode, well, I cannot do those things, as my device doesn't seem to recognized at all while in that mode.

CarpeNivem said:
Those instructions include "attach phone to computer while phone is in fastboot mode".
However, when I do that, when I attach my phone to the computer while in fastboot mode, my Nexus 5 is NOT SHOWN when I type "adb devices" OR "fastboot devices".
When my phone is in recovery mode, and I type "adb devices", then it IS shown. Additionally, if my phone is fully booted up as normal, if I type "adb devices", it IS shown then too.
But if there are things which need to be done from the computer at the command prompt (and it seems that there are) while the phone is in fastboot mode, well, I cannot do those things, as my device doesn't seem to recognized at all while in that mode.
Click to expand...
Click to collapse
Google tool adb fastboot drivers xda. Use that to get the drivers working with fastboot

jd1639 said:
You need to read this http://forum.xda-developers.com/showthread.php?p=47369234. Basically you need to flash the stock system.img
Click to expand...
Click to collapse
Will that do anything to root access?
Sent from my Nexus 5 using Tapatalk

kehlan said:
Will that do anything to root access?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
After taking the ota you'll have to re-root

I think it's finally happening. I think I'm finally done. I'm successfully running 4.4.2 on my rooted Nexus 5. Thank you so much for the help (especially since this isn't even my thread; it just had a title which aligned perfectly to my problem, so hopefully the OP was helped along the way also).
To recap, for future use other visitors to this thread...
1. I tried to apply the 4.4.2 update using an OTA.zip file I found elsewhere on the Internet. This is easy. You've probably already done this.
2. I was told "build.prop" contained unexpected content.
3. I remembered that I had changed the DPI, so I changed that back from my personal 420 to the default 480. This resolved the previous error message.
4. I tried again, but this time was told Roboto-Bold.ttf contained unexpected content. I have no idea why that was.
5. I followed SOME of the instructions on this page: http://forum.xda-developers.com/showthread.php?t=2513701
Specifically, from the "Method 2" section, I did the "fastboot flash system C:/image-hammerhead-krt16m/system.img" and "fastboot flash boot C:/image-hammerhead-krt16m/boot.img" commands. That's ALL I DID from the "type these commands" section of those instructions. Doing that, I did NOT lose data! (well, none that I've yet noticed, at least)
6. I tried AGAIN to flash the OTA.zip file from Clockworkmod Recovery. This time it finally worked!
7. I checked Settings > About Phone, and I'm running 4.4.2 now!
8. I'm having trouble changing the DPI back to 420. I'm probably not rooted anymore. I'll have to go do that again. No big deal. Everything else seems fine.
...along the way, I needed to install drivers, for which I tried so many things, I don't even remember anymore what was the best method. I think using "ADB Manager.exe" from within my ADB folder was best. I also, at one point, had to change my USB device type from MTP to PTP. That was done on the phone, by swiping down the notification area.
Ugh, I wish I remembered everything, so I could spell it out as directly and clearly as I would've appreciated it be this morning, but I've seriously done so much recently that I know I'm missing certain steps, and I feel really bad for anyone having problems. There are so many instructions on the Internet that say, "Do this, and then this will happen," but they never explain what to do if that DOESN'T happen. And now here I am, not being any better than any of them. Sorry. Good luck.

Glad you got it working