LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
whitechameleon said:
LG Escape running 4.1.2
here is the progression of events:
1. rooted device
2. root seemed successful and no malfunctions
3. backed up all apps and system data with Titanium backup
4. the lg escape has no way to unlock the bootloader, so I tried various other methods. one of which was entering recovery mode via terminal commands. this is basically a hard reset, and it wiped all my data
5. I restored all my apps and data from my external sd card with titanium
My best guess is this is where something went wrong
6. upon restoration it prompted me to reboot the device
7. reboot passes manufacturer logo, but resets when AT$T logo appears
8. as stated earlier, there is no way to enter recovery mode during boot.
9. there is a hard reset during boot, but mine will not work, as it requires touching buttons which do not seem to be active in my stage of the boot sequence
so, I understand this does NOT mean my phone is bricked, but I don't know how else to get it to boot back up, or what is even causing the boot loop, as I DO NOT HAVE ANY CUSTOM ROMS flashed. any help here is very appreciated!
EDIT: so I have attempted to use adb on my pc to reboot into recovery from there, but it occurred to me that while I was in recovery the first time, I never checked "usb debugging". as a result my adb console commands cant even see my device. any way to turn on usb debugging while locked in a boot loop?
also, I can get it to enter download mode. I was hoping I could just reflash the firmware to it without needing to enable usb debugging, but have no clue how to do that while locked out of the phone.
I realize this is a very specialized set of questions, but it is necessary to ask here as the most people will see it. im open to any ideas
Click to expand...
Click to collapse
i have now tried to flash the firmware while in download mode using a less than legitimately obtained lg R&D tool. however, i need V10F_00.kdz and i am facing a bit of censorship. any kind soul willing to host this file on dropbox or similar so i can download it?
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
J2270A said:
Usually devices have a button combination to press when powering on to get into different modes. Maybe try searching for the button combination of your phone on Google? Try ' lg escape button recovery ' ?
Click to expand...
Click to collapse
believe me i have. the only combo i can get to is download mode. there is a combo for a hard reset, but my touch buttons arent active during boot.
Related
Hello,
I own an Android tablet KO PARA1 FULL and experiencing a strange problem. This is a chinese atm7029 quadcore tablet (16gb, 1gb ram, without bluetooth, only wifi, bu supports 3g dongle), running android 4.1.1 nad 3.4.0+ kernel, which came prerooted. After some time I've decided to install backup programs on in to make a full backup of the device for the case something would go wrong, and after some trying I descovered, that there is something like recovery for that purposes which seemed a good solution for me. I decided to install CWM, which I managed to install without problems and made some backups on my device. Everything was fine, I did some factory resets through the time, some restoring processes from my previously backup states of the device, was always able to activate CWM recovery menu through Reboot to recovery or through combination of Volume down a Power button...
Until last saturday. I was normaly surfing the internet, reading mails and afterwords I powered my tablet off (it is draining battery in sleep mode, but its another story..). After a while wanted again to write a mail, so I powered it on. In that momet seemed the screen too dirty for me and I tried to cleen it little bit throug the bootup process. Unfortunately I obvious confused the system with it and after boot it was not responding properly. I did not wait enough and after a while powered it off with power key pressed for a long time, to make a new boot.
But when I powered it on again, it stayed stuck in boot logo and did not boot at all. I've tried a copple of times to boot it again with no cuccess, stayed stuck in boot logo for more then 10 min...
Afterwards I decided to make it boot up with the help of computer. I downloaded adb and drivers and somehow managed to make it boot up. I thing I was too excited to see it boot up again, that during boot up process I desconected my device from computer...
My worries were reliesed and I thought it would be a good idea to make a restore from backup to prevent some strange behaviour, so wanted to boot into recovery, but nothing had happened. After some repeated clicks on Boot into recovery button, as well as app called rebooter with nothing happening, I decided to try it out through button combination. It has not worked as well Next try was to reset to factory settings. But when I go through the menu, I can click on reset to factory settings button, seeing warning that I will lost ma data, then I can push the button to make it happen, but nothing is happening. I see only the screen with the button, can touch it 100 times and the tablet stays on, fully funcional. making no factory reset as it done before.
I did a lot of reading and searching, but have not find answer for my problem. I flashed recovery images from my backups (using flashify, flash gordon, adb shell, terminal emulator), from all previously functional states of the device. I refleshed the CWM recovery downloaded from the internet for my chipset, which previously did the job just perfect, with no success...
I am still not able to reach recovery menu. For me it seems like the bootloader would be locked, but I did not find the answer how to unlock it without to be able to start in some recovery state to use fastboot command to unlock it.
Otherwise, my device is functional, still rooted, i can use it without any other problems. But not be able to do recovery from my backups, even do a factory reset.
How can I restore my access to recovery mode? Is it somehow possible?
Hopfully it is not too much information (tryied to follow the intructions and wrote everything I thought would be important to know about) and you will not be bothered to read all my story and pull me out of my darkness with helpfull suggestion.
Thanks a lot in advance
Steve
The phone was working fine until the battery was empty. I tried to charge it and turn it on, but it's stuck at the Samsung logo splash screen. Holding the power button only restarts the device, so to turn it off I'll have to take the battery out. I don't know how to fix this, and if a factory reset is the only option, I need to backup my data first which I currently don't know how to either (without accessing the OS).
I've got to the Android System Recovery 3e menu and tried clearing cache, which did not help. The option to do a factory reset is also there, but I need to backup my data first, and I don't even know if this will fix the problem.
I'm also able to enter download mode.
When connected to my PC it detects an unknown device named 'samsung_android", and it shows up in adb. I've tried doing a backup through adb, but it wanted me to unlock the screen to accept the backup, which I could not, because I'm stuck at the splash screen.
Is there anything I can do to save my data? Anything through adb? Install root (never done this before)?
dinho10r said:
The phone was working fine until the battery was empty. I tried to charge it and turn it on, but it's stuck at the Samsung logo splash screen. Holding the power button only restarts the device, so to turn it off I'll have to take the battery out. I don't know how to fix this, and if a factory reset is the only option, I need to backup my data first which I currently don't know how to either (without accessing the OS).
I've got to the Android System Recovery 3e menu and tried clearing cache, which did not help. The option to do a factory reset is also there, but I need to backup my data first, and I don't even know if this will fix the problem.
I'm also able to enter download mode.
When connected to my PC it detects an unknown device named 'samsung_android", and it shows up in adb. I've tried doing a backup through adb, but it wanted me to unlock the screen to accept the backup, which I could not, because I'm stuck at the splash screen.
Is there anything I can do to save my data? Anything through adb? Install root (never done this before)?
Click to expand...
Click to collapse
Hey mate, can you get into the recovery mode? Try flashing the TWRP recovery and boot by pressing power button + home button + volume up and find an option to mount your USB storage via USB cable and see if your phone's folder tree is available from the Windows Explorer and hopefully you can backup your data by then. Just make sure you have all the drivers ready.
Hope that helps.
cglegion said:
Hey mate, can you get into the recovery mode? Try flashing the TWRP recovery and boot by pressing power button + home button + volume up and find an option to mount your USB storage via USB cable and see if your phone's folder tree is available from the Windows Explorer and hopefully you can backup your data by then. Just make sure you have all the drivers ready.
Hope that helps.
Click to expand...
Click to collapse
Yeah, I can get into recovery mode. But how do I get the TWRP to my phone? Do I have to put it on my external memory card and then load it from there?
And I could only find it for a S2 Exhilarate SGH-i577 device. Does it matter if my phone is a S2 GT-I9100?
I've never rooted my phone earlier. Is a root necessary to flash a ROM?
dinho10r said:
Yeah, I can get into recovery mode. But how do I get the TWRP to my phone? Do I have to put it on my external memory card and then load it from there?
And I could only find it for a S2 Exhilarate SGH-i577 device. Does it matter if my phone is a S2 GT-I9100?
I've never rooted my phone earlier. Is a root necessary to flash a ROM?
Click to expand...
Click to collapse
Correct. Put the TWRP zip on your external and flash it normally via recovery mode such as CWM not the android 3e recovery. Or find an odin flashable zip for yoyr device.
I am very sure there is one for I9100 because I ran into the exact same problem before and managed to figure it out. You just have to search for it can't give you a link because I'm on mobile now.
You need to root your phone in order to install a new recovery such as TWRP/CWM or even flash new kernel and ROM.
Good luck.
Hi, I'm completely new on all this mobile/android stuff, also sorry my poor English.
Out of nothing my phone bricked and I just wanted to recover my files from the internal storage.
Why I've tried so far: to install a custom recovery using Odin. Installation process were OK, I guess, judging by Odin and phone messages (on phone download mode you can read "custom binary download: YES (3 counts)". That's 3 because I've tried twrp-2.8.6.1-i9300 (tar) twice and recovery-clockwork-touch-6.0.4.4-i9300 (tar) once.
Where I'm stuck: I cannot see the options to access these recoveries form the recovery mode, just the already existing options (reboot, apply update, ...).
Thanks you for any help!
Vinicius
First of all flash chainfire auto-root. You can download it from here: https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
Then try again to flash TWRP. If it will go ok, you can copy from recovery data from internal storage to sd card
Hi There,
I am in a similar predicament.
I have a Galaxy S3 (purchased in 2012) and a few weeks ago, the phone started to automatically switch off (when I locked it) and I would have to hold the power button for about 15-30 seconds for it to switch back on.
I checked the power button(to see if it was broken and pressing down all the time) but it seemed to be fine as whenever I pulled the battery, the phone would NOT come on unless I held the power button.
About 1 week ago when i tried to turn my phone on, with the power button, but it would get stuck on the samsung logo screen (it was frozen, not looping).
I was still able to enter both recovery and download mode. So I tried wiping the cache but it did nothing.
Then I tired flashing the ROM with ODIN and it passed but it also did nothing (tried flashing multiple times all with "PASS" as well as wiping the data cache in conjuction with the flashing but to no avail).
Tried flashing it again with BL and it also passed, but now whenever I try to enter Recovery Mode or Turn the phone ON it would display a White Scrambled Screen which probably means eMMC failure.
How do I retrieve the information on the phone ?
N.B;
- I do not care about fixing the phone, only want the information
-I cannot enter Recovery Mode, BUT I can enter download mode.
-When I connect S3 to PC it is detected (In Device Manager it states "Samsung Mobile USB CDC Composite Device")
-I did have my phone password protected before this happened using the Pattern Password (you have a 3x3 Dot grid in which you can use to draw a line(s) which will function as a password)
-My phone is an S3 GT-I9300
-Never interfered with the ROM or software on the phone before this (was running the official android software from Samsung which I believe was Android Version 4.3).
-I am not very versed with computer programming so please use simple words to help me
As previously stated. flash cf-autoroot and then flash twrp, both via odin. Then you should be able to access twrp (hold home and vol+/- (cant remember which, opposite from download mode) and press power once.
If you can get to twrp you can use its built in file manager to move your data to an sd card.
If no twrp its what is technically known as f*cked.
I wish I stole my HTC M9.
shivadow said:
As previously stated. flash cf-autoroot and then flash twrp, both via odin. Then you should be able to access twrp (hold home and vol+/- (cant remember which, opposite from download mode) and press power once.
If you can get to twrp you can use its built in file manager to move your data to an sd card.
If no twrp its what is technically known as f*cked.
I wish I stole my HTC M9.
Click to expand...
Click to collapse
Hi,
Thanks for the reply.
How would I flash cf-autoroot and thenflash twrp (I have no clue what this means lol).
Also what is twrp?
bossman111 said:
Hi,
Thanks for the reply.
How would I flash cf-autoroot and thenflash twrp (I have no clue what this means lol).
Also what is twrp?
Click to expand...
Click to collapse
Short and sweet: TWRP is a popular recovery system; cf-autoroot is the preferred method for rooting some samsung devices by member Chainfire
I could lay out all that here again in detail, but it's safe to say you are better off in the long run if read up on that stuff by yourself...
Check the excellent threads I linked in my signature! Trust me, it's not as complicated as it seems.
To start off, I suffered, what seems to be a common problem, of the fingerprint unlock on Samsung Galaxy S6 Edge randomly being unable to recognise my fingerprint. Followed by my back-up password not being accepted. Unfortunately, I turned off my data and wifi before the phone locked so the problem doesn't seem to be able to resolve itself unless I Factory Reset the phone.
This i am happy to do as long as I can find some way to retrieve the media files from the phone (just pictures and videos). I read up and watched some videos where some people were able to use ADB through Recovery Mode or Field Test mode, and pull the files from the phone. These people however were using older models of Android phones but I decided to read numerous pages etc and go ahead and try.
I set up everything (I believe) i needed on my Mac Book pro in order to use the Adb Terminal. However when I tried to connect my phone Adb couldn't detect my device. I then decided (after reading somewhere to do so) to press "Apply update using ADB" on the Recovery menu. Again, Adb did not detect my device.
i left this screen up on my phone which resulted in "dm-verity verification failed..." appearing at the bottom of the screen. It then switched back to the Recovery menu and continues to show "dm-verity verification failed..." at the base of the screen. Now when I try and power up the phone normally, the start up screen just repeatedly flashes and it goes no further than that.
Im not completely brain dead when it comes to this stuff but I obviously don't fully understand what I am doing, So Im wondering if there is a genius out there who, even after what I've done, can help me pull the files from my phone before I have to Factory Reset!
The problem is, that you don't have the ability to use adb pull through the stock recovery. This kind of thing can only be done via a custom recovery like TWRP, CWM, or Philz. Now that it's not booting, pretty much the only thing to try is to install a custom recovery and boot directly into it before it tries to restart. Make sure you find one for the correct variant of your phone. If yours is a VZW or ATT version, you're in trouble because they don't have custom recoveries like that for them.
Hello. I have tried to install a custom recovery (TWRP) on my Samsung Galaxy Tab A 8.0" (SM-T290) today, however, it has not exactly gone to plan. I will run over exactly what I did, and what troubleshooting steps I have taken so far.
I downloaded this version of ODIN: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I unlocked the bootloader through the bootloader menu and enabled USB debugging after the tablet had turned on.
I downloaded and used the latest .md5.tar TWRP file from here: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
ODIN Successfully flashed TWRP and the device rebooted. I attempted to get straight into the recovery by holding volume up, however, the screen remained black.
The tablet now cannot boot into recovery, download mode, etc, and only the backlight of the screen turns on. The tablet does eventually "boot up" and give the little vibration, at which point my computer recognises it, but I cannot see any files on the tablet. I can also see the tablet with ADB using the command "adb devices", however it tells me the tablet is "unauthorized", meaning I cannot use any ADB commands to attempt to reboot into recovery, download mode, etc.
I have tried disconnecting the battery and just powering on with the cable to no avail. I am assuming the device is fully bricked at this point, however, I would be appreciative if any possible solutions could be suggested, and if where I went wrong can be pointed out so I do not make the same mistake in the future.
Thanks in advance.
It's always risky to apply mods.
To get rid off of all mods you applied re-flash tablet's Stock ROM.
If this doesn't work for you then take it to authorized service center and let them try to fix it.
jwoegerbauer said:
take it to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
They never fix anything. The only thing they do is charge you an absurd price and replace the motherboard or the entire tablet.
I'm on the same boat. Tablet can't get into download mode, just shows "This device has unauthorized software on it and is locked". Tried all possible button combinations to no avail.
SmiffyJ said:
Hello. I have tried to install a custom recovery (TWRP) on my Samsung Galaxy Tab A 8.0" (SM-T290) today, however, it has not exactly gone to plan. I will run over exactly what I did, and what troubleshooting steps I have taken so far.
I downloaded this version of ODIN: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
I unlocked the bootloader through the bootloader menu and enabled USB debugging after the tablet had turned on.
I downloaded and used the latest .md5.tar TWRP file from here: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
ODIN Successfully flashed TWRP and the device rebooted. I attempted to get straight into the recovery by holding volume up, however, the screen remained black.
The tablet now cannot boot into recovery, download mode, etc, and only the backlight of the screen turns on. The tablet does eventually "boot up" and give the little vibration, at which point my computer recognises it, but I cannot see any files on the tablet. I can also see the tablet with ADB using the command "adb devices", however it tells me the tablet is "unauthorized", meaning I cannot use any ADB commands to attempt to reboot into recovery, download mode, etc.
I have tried disconnecting the battery and just powering on with the cable to no avail. I am assuming the device is fully bricked at this point, however, I would be appreciative if any possible solutions could be suggested, and if where I went wrong can be pointed out so I do not make the same mistake in the future.
Thanks in advance.
Click to expand...
Click to collapse
Hi,
I have the exact same problem, did you manage to recover the tab?
Thanks heaps