Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.
tparnet said:
Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.
Click to expand...
Click to collapse
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.
svs57 said:
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.
Click to expand...
Click to collapse
Thanks svs57 for the quick reply.
Would you mind elaborating a bit more? I am an IT guy but by no means a developer. When I boot into recovery is the phone supposed to show up in My Computer via MTP or PTP? The phone is not showing up as a device. Or am I supposed to use adb commands to pull the files down?
When I go into recovery and run the "adb devices" command now I get what appears to be a serial number followed by the word "unauthorized". I rebooted and went into recovery mode again this time tried "apply update from ADB". When I try using either the adb push or adb pull I get "error: closed"
Thanks again for the help.
You have to use latest version of adb. Then you can login to phone via adb and find file you want to backup. Then use "adb pull" to get file to PC.
If you have custom recovery you also can make backup you data using recovery.
Also you can flash the same ROM you have without wipe data.
Related
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
sacredsoul said:
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
Click to expand...
Click to collapse
not sure if you found out already but
all you have t do is go to mount and mount what uou need
sacredsoul said:
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
Click to expand...
Click to collapse
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
device manager, right click phone, update drivers, browse computer, let me pick from a list, unclick show compatible hardware, and find LGE or LG and pick the adb driver
Yes, I solved it. Got the drivers fixed.
Fun fact : If your G2 is just getting stuck at boot, turn it off for an over and try again. I stupidly flashed a zip containing a recovery using Flashify and not the boot.img and I got stuck in Fastboot mode or it'd just stuck at the boot animation. I had given up and decided to go back to stock, wiping all my photos. But thankfully the stock flash got stuck because I am using a custom kernal. I turned it off, watched some tv and tried again. Booted right back into the rom. Flashed a proper recovery using adb, got into TWRP, reflashed my rom and didn't lose any data. @autoprime got me through the process via IRC so big kudos to him!
Rooted my N73G with Clockwork back in 12/12 when I bought it, worked fine for a year and change. Last week it wouldnt boot past the glowy X. Tried resetting cache, Dalvik cache, and factory reset options in Recovery Mode. Nothing
Downloaded the SDK as a couple different tutorials instructed. Tried Skipsoft's toolkit. Why does every bloody recovery tutorial tell you "enable USB Debugging in the Settings menu" when you cant bloody well boot to a working OS???????
Needless to say, everything I try deadends at unable to do whatever because USB Debugging isnt enabled. Now it wont even boot into Recovery Mode, stopping at the bootloader.
Wat do?
aeldergoth said:
Rooted my N73G with Clockwork back in 12/12 when I bought it, worked fine for a year and change. Last week it wouldnt boot past the glowy X. Tried resetting cache, Dalvik cache, and factory reset options in Recovery Mode. Nothing
Downloaded the SDK as a couple different tutorials instructed. Tried Skipsoft's toolkit. Why does every bloody recovery tutorial tell you "enable USB Debugging in the Settings menu" when you cant bloody well boot to a working OS???????
Needless to say, everything I try deadends at unable to do whatever because USB Debugging isnt enabled. Now it wont even boot into Recovery Mode, stopping at the bootloader.
Wat do?
Click to expand...
Click to collapse
BETTER DESCRIPTION....
Rooted my N73G with Clockwork back in 12/12 when I bought it, worked fine for a year and change. Last week it wouldnt boot past the glowy X. Tried resetting cache, Dalvik cache, and factory reset options in Recovery Mode. Nothing
Downloaded the SDK as comminus's tutorial instructed. Installed Java Dev Kit and Android SDK. Got to the command line, but under the right directory when I try "adb devices" it doesnt list my tablet.
Tried Skipsoft's toolkit. Why does every bloody recovery tutorial tell you "enable USB Debugging in the Settings menu" when you cant bloody well boot to a working OS???????
Needless to say, everything I try deadends at unable to do whatever because USB Debugging isnt enabled. Now it wont even boot into Recovery Mode, stopping at the bootloader.
Wat do?
If usb debugging was enabled, one might save the important files from the device before flashing it.
Since you boot into the bootloader, you can flash a factory image. I recommend this guide but all of your data will be gone.
Erovia said:
If usb debugging was enabled, one might save the important files from the device before flashing it.
Since you boot into the bootloader, you can flash a factory image. I recommend this guide but all of your data will be gone.
Click to expand...
Click to collapse
From the linked guide (the one I've been using) "Enable usb debugging on your device (found under Settings > Developer Options)
NOTE: Since Android 4.2 the Developer Options are hidden by default."
How can I enable USB Debugging on a tablet that is bricked? Further, the SDK program doesnt see my tablet connected. I hear a little connection tone in windows when I plug it in, but running adb.exe from the command line and using an "adb devices" command shoes a "List of connected devices" that is empty.
Only the Skipsoft toolkit seems to want to even see my tablet, no matter what USB port I try,
There is no need for adb (it is only used to boot into bootloader). What you will need is the fastboot commands in the "Flashing the Factory Image" part, but be carefull to flash the proper image and to the proper partions.
Erovia said:
There is no need for adb (it is only used to boot into bootloader). What you will need is the fastboot commands in the "Flashing the Factory Image" part, but be carefull to flash the proper image and to the proper partions.
Click to expand...
Click to collapse
Sorted. THanks.
Hi, I wanted to return my g2 to stock rom because I didn't like my custom rom, so I followed the lg flash tool guide(tot):http://forum.xda-developers.com/showthread.php?t=2432476
It worked, but it was jelly bean 4.2 instead of Kit kat 4.4, so I tried to install TWRP so that I can install again a custom rom, but when I tried to backup before flashing TWRP, it wrote "backup Failed", I tried again and it wrote it again, but then the phone just stayed on the boot animation for a few seconds and didnt turn on again. After that, again I tried to do the flash tool method just to return to stock rom but now, it just doesn't work, whenever I insert the DLL and TOT file and start the installation, it goes up to 80% extremely quick and just boots up to TWRP without actually installing the stock rom. So now I'm stuck here with TWRP but without a system to boot to and no rom on my sd card to flash.
I really need help here because I have no idea how to continue.
Thanks for any help!
PriStol said:
Hi, I wanted to return my g2 to stock rom because I didn't like my custom rom, so I followed the lg flash tool guide(tot):http://forum.xda-developers.com/showthread.php?t=2432476
It worked, but it was jelly bean 4.2 instead of Kit kat 4.4, so I tried to install TWRP so that I can install again a custom rom, but when I tried to backup before flashing TWRP, it wrote "backup Failed", I tried again and it wrote it again, but then the phone just stayed on the boot animation for a few seconds and didnt turn on again. After that, again I tried to do the flash tool method just to return to stock rom but now, it just doesn't work, whenever I insert the DLL and TOT file and start the installation, it goes up to 80% extremely quick and just boots up to TWRP without actually installing the stock rom. So now I'm stuck here with TWRP but without a system to boot to and no rom on my sd card to flash.
I really need help here because I have no idea how to continue.
Thanks for any help!
Click to expand...
Click to collapse
You could load the zip you want to flash to a USB drive, then connect it to your phone with an OTG cable. TWRP can read from OTG.
Can you get into download mode? (phone off, hold up volume, insert USB cable connected to computer)
thecadman99 said:
You could load the zip you want to flash to a USB drive, then connect it to your phone with an OTG cable. TWRP can read from OTG.
Can you get into download mode? (phone off, hold up volume, insert USB cable connected to computer)
Click to expand...
Click to collapse
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.
PriStol said:
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.
Click to expand...
Click to collapse
Can you get ADB connectivity from within TWRP if you connect your device to the PC?
If so you could do the following command from your computer.
Code:
adb push ROM.zip /sdcard/Download/
Then navigate to your /sdcard/Download folder and flash the ROM.
d00lz said:
Can you get ADB connectivity from within TWRP if you connect your device to the PC?
If so you could do the following command from your computer.
Code:
adb push ROM.zip /sdcard/Download/
Then navigate to your /sdcard/Download folder and flash the ROM.
Click to expand...
Click to collapse
When I try to do ADB sideload on TWRP, it just loads forever and doesn't do anything... So I cant get ADB connectivity.
PriStol said:
When I try to do ADB sideload on TWRP, it just loads forever and doesn't do anything... So I cant get ADB connectivity.
Click to expand...
Click to collapse
TWRP should detect your phone without the need for ADB sideload.
If I boot into TWRP, I can instantly run "adb devices" from the terminal my phone is picked up as a "device".
If I choose ADB Sideload, my TWRP hangs just like yours does, but if I run another "adb devices" command my device shows up in sideload mode, regardless of it hanging.
Conclusion, try running the adb commands without running sideload in the first place.
Edit: Upon reflection, this is most likely because I have created an RSA key between the PC and my phone.
d00lz said:
TWRP should detect your phone without the need for ADB sideload.
If I boot into TWRP, I can instantly run "adb devices" from the terminal my phone is picked up as a "device".
If I choose ADB Sideload, my TWRP hangs just like yours does, but if I run another "adb devices" command my device shows up in sideload mode, regardless of it hanging.
Conclusion, try running the adb commands without running sideload in the first place.
Click to expand...
Click to collapse
It just says error: device not found whenever I do a command.
Please help, I really dont know what to do.
PriStol said:
I just tried to do it through an OTG cable, it said that it flashed successfuly, but when I restarted it just went back to TWRP without booting up the system. Also, when I tried to wipe dalvik and cache, it said "wipe failed.". When I rebooted it said "It seems that the device is not rooted"... I really don't know what to do now And I can get to download mode.
Click to expand...
Click to collapse
Did you wiped absolutely everything before flashing? Do you have previous Nandroid backup you can just flash. Anyway if you connect your phone to PC while in TWRP what does your PC show. Anything?
yanis15 said:
Did you wiped absolutely everything before flashing? Do you have previous Nandroid backup you can just flash. Anyway if you connect your phone to PC while in TWRP what does your PC show. Anything?
Click to expand...
Click to collapse
I tried to wipe but it just wrote "wipe failed". I do have a back up on my computer but for some reason when I try to connect my phone to my computer through an OTG cable, it doesn't find the backup. And my pc doesn't show anything when I connect my phone.
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
any luck?
ahq1216 said:
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
Click to expand...
Click to collapse
different route but im in the same boat. any luck?
I fixed this shortly after. Wanted to avoid returning to stock as. The only option was you and I was on 10d. I had to go back to stock but luckily the recovery method still works.
Hi am looking for custom Rom for my 9020a trek 2 HD device. Seeing on how to install it on a my device that isn't working. Can it be done on laptop or is a SD micro memory card needed. Thanks
Johnlock777 said:
Hi am looking for custom Rom for my 9020a trek 2 HD device. Seeing on how to install it on a my device that isn't working. Can it be done on laptop or is a SD micro memory card needed. Thanks
Click to expand...
Click to collapse
For flashing custom rom you need custom recovery installed on your android or rom package in your android internal storage or in sd card
Ashwinrg said:
For flashing custom rom you need custom recovery installed on your android or rom package in your android internal storage or in sd card
Click to expand...
Click to collapse
Hi thanks for the reply. How is done and can it be done on a device that won't boot up. I cleared the cache and tried factory reset. But doesn't go past the powered by android screen. Says on that screen until it goes off or i hold the home button for ten seconds.
Johnlock777 said:
Hi thanks for the reply. How is done and can it be done on a device that won't boot up. I cleared the cache and tried factory reset. But doesn't go past the powered by android screen. Says on that screen until it goes off or i hold the home button for ten seconds.
Click to expand...
Click to collapse
What did you do to the device before you cleared cache and factory reset, something you did caused this. The best/easiest way to fix it depends on what you did.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
What did you do to the device before you cleared cache and factory reset, something you did caused this. The best/easiest way to fix it depends on what you did.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Was uninstalling apps from twrp manager because since I rooted the device was very slow. I accidentally uninstalled a system file. After it uninstalled froze wouldn't do anything. I hold power button and turned off and been in current state. Won't do anything but stay on the powered by android screen. Does this even after a factory reset roboot device. Am thinking without putting a clockwork mod on device because I can't access googleplay on the device. Custom recovery for installing a custom rom. Nothing I can do to fix the device. I sent the device to manufacturer for repair and sent it back was unrepairable. Even knowing they could of put the stock system on the device. No clue what to do next.
Johnlock777 said:
Was uninstalling apps from twrp manager because since I rooted the device was very slow. I accidentally uninstalled a system file. After it uninstalled froze wouldn't do anything. I hold power button and turned off and been in current state. Won't do anything but stay on the powered by android screen. Does this even after a factory reset roboot device. Am thinking without putting a clockwork mod on device because I can't access googleplay on the device. Custom recovery for installing a custom rom. Nothing I can do to fix the device. I sent the device to manufacturer for repair and sent it back was unrepairable. Even knowing they could of put the stock system on the device. No clue what to do next.
Click to expand...
Click to collapse
Does your PC even recognize the device? Does it show anything device manager?
Have you tried anything by searching for:
"How to unbrick (your model number)"
Have you tried connecting to adb while the device is in bootloop, you may have to create some sort of script to run in adb to echo and interrupt boot cycle while in bootloop to stay connected to adb, if you can get it to accept adb commands, you can try adb pushing copies of the apps you removed or maybe even push a copy of your stock system.img with a dd command, just make absolutely sure that use the correct command to dd the .img to the correct partition(mmcblk0) on your internal sd.
If your device is a fastboot device you can use adb to get to fastboot and flash the device.
There is also the possibility that you can use the stock firmware for your device or a .img dumped from another rooted device like yours to create or pull an .img that can be "burned" to a micro sd card to create a type of "boot disk" that will boot your device from extsdcard and then use that to restore the device. I don't know the software and methods to achieve this on your specific device, I'm just telling you the different tricks that can be used to restore a device.
These are just possibilities.
Droidriven said:
Does your PC even recognize the device? Does it show anything device manager?
Have you tried anything by searching for:
"How to unbrick (your model number)"
Have you tried connecting to adb while the device is in bootloop, you may have to create some sort of script to run in adb to echo and interrupt boot cycle while in bootloop to stay connected to adb, if you can get it to accept adb commands, you can try adb pushing copies of the apps you removed or maybe even push a copy of your stock system.img with a dd command, just make absolutely sure that use the correct command to dd the .img to the correct partition(mmcblk0) on your internal sd.
If your device is a fastboot device you can use adb to get to fastboot and flash the device.
These are just possibilities.
Click to expand...
Click to collapse
It will show on laptop like serial number unavailable but keeps saying USB needs to be debugged but can't because I can't access developer settings on device. I haven't search unbricked with model number. Didn't know what bricked met. I screenshot options with what I have on device. Have no clue on commands and how to do this?
Johnlock777 said:
It will show on laptop like serial number unavailable but keeps saying USB needs to be debugged but can't because I can't access developer settings on device. I haven't search unbricked with model number. Didn't know what bricked met. I screenshot options with what I have on device. Have no clue on commands and how to do this?
Click to expand...
Click to collapse
Do a Google search for:
"USB drivers for (your model number)"
Make sure you get those fully installed.
Then do a Google search for:
"adb/fastboot 15 second installer for windows"
If you have issues getting it installed and working correctly, just do a Google search for:
"How to setup adb/fastboot on windows"
There should be many guides to follow, once you're set up, boot to recovery to the menu in your screenshot, select "reboot bootloader", that will probably boot you to fastboot mode, then connect to PC
Open a cmd prompt, in that terminal type:
fastboot devices
Press enter, if it returns a serial number you're connected, from there you can fastboot flash your stock firmware.
To understand fastboot flashing, do a Google search for:
"How to fastboot flash stock firmware (your model number)"
Droidriven said:
Do a Google search for:
"USB drivers for (your model number)"
Make sure you get those fully installed.
Then do a Google search for:
"adb/fastboot 15 second installer for windows"
If you have issues getting it installed and working correctly, just do a Google search for:
"How to setup adb/fastboot on windows"
There should be many guides to follow, once you're set up, boot to recovery to the menu in your screenshot, select "reboot bootloader", that will probably boot you to fastboot mode, then connect to PC
Open a cmd prompt, in that terminal type:
fastboot devices
Press enter, if it returns a serial number you're connected, from there you can fastboot flash your stock firmware.
To understand fastboot flashing, do a Google search for:
"How to fastboot flash stock firmware (your model number)"
Click to expand...
Click to collapse
I took screenshot of what I get when device is connected to PC. But can't find the USB drivers for this device online. Didn't continue the steps you provided because of that.
You can delete or close thread. With everything I heard there was no hope in fixing the device. So I destroyed it and tossed it. Thanks for advice appreciated it.
A little late now but since I saw that you could boot recovery, so the easy fix would have been using jasminetool with edl to install a custom recovery(twrp ). Once twrp is installed its just simple enough towipe system partition and flash a stock ROM or flash a custom ROM and get it working again. This is a fix For anyone else who messes up there system partition.