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.
Related
Please help a noob dad with a distraught teenage son who is not as tech savvy as his peers, or his noob dad.
Son and I both have absolutely stock TMo HTC Ones. Mine is fine.
His had all his music on it, and his music was not backed up. (His laptop's hard drive crashed just two weeks ago and he had not gotten around to restoring his music yet. He is not having a good month with tech.)
His phone without warning entered a boot loop. It restarted itself, reached the bootloader/simply brilliant splash page, reached the T Mobile LTE splash page, reached the HTC One Beats Audio splash page, dimmed a bit, went blank, and then restarted the boot sequence. This goes on infinitum, and even after we let the phone battery run down to zero, recharged and started it again.
We can enter the bootloader by pressing volume down and the power key at the point where the screen goes blank after the HTC One Beats Audio splash, and from there we can go to recovery or into fastboot. When in fastboot, the phone can be connected to a computer, where it shows up as an "unspecified" device called Android 1.0. This device does not show up as a storage device - so we don't see the files. It has a driver called MyHTC. The phone screen shows FASTBOOT USB in red, but running adb with the command adb devices doesn't show anything in the device list.
As I said, the phone is absolutely stock - that means it is locked, and never was unlocked. And I understand that unlocking the bootloader to install a custom recovery would wipe the data files, thus defeating the purpose of the exercise.
We won't mind trying a factory reset, or even trying to root the phone, if we can first get to the music and save it. Is there some way to save it?
Now, mind you, two days ago terms like adb, bootloader, Android SDK, custom recovery, etc., were completely foreign to me. These are things I have picked up trying to solve the problem with Google and personal grit. So please bear that in mind when answering.
Is there some way to access the data files on this phone from the bootloader screen or from the recovery screen? If the phone can't be booted up and the phone can't be unlocked without being wiped clean, it seems my son is going to be spending a lot of time and money recreating his music library. Is this true? Have we finally found a situation that Dad can't rescue his offspring from?
Thanks in advance for any ideas...
GenerousDad said:
Please help a noob dad with a distraught teenage son who is not as tech savvy as his peers, or his noob dad.
Son and I both have absolutely stock TMo HTC Ones. Mine is fine.
His had all his music on it, and his music was not backed up. (His laptop's hard drive crashed just two weeks ago and he had not gotten around to restoring his music yet. He is not having a good month with tech.)
His phone without warning entered a boot loop. It restarted itself, reached the bootloader/simply brilliant splash page, reached the T Mobile LTE splash page, reached the HTC One Beats Audio splash page, dimmed a bit, went blank, and then restarted the boot sequence. This goes on infinitum, and even after we let the phone battery run down to zero, recharged and started it again.
We can enter the bootloader by pressing volume down and the power key at the point where the screen goes blank after the HTC One Beats Audio splash, and from there we can go to recovery or into fastboot. When in fastboot, the phone can be connected to a computer, where it shows up as an "unspecified" device called Android 1.0. This device does not show up as a storage device - so we don't see the files. It has a driver called MyHTC. The phone screen shows FASTBOOT USB in red, but running adb with the command adb devices doesn't show anything in the device list.
As I said, the phone is absolutely stock - that means it is locked, and never was unlocked. And I understand that unlocking the bootloader to install a custom recovery would wipe the data files, thus defeating the purpose of the exercise.
We won't mind trying a factory reset, or even trying to root the phone, if we can first get to the music and save it. Is there some way to save it?
Now, mind you, two days ago terms like adb, bootloader, Android SDK, custom recovery, etc., were completely foreign to me. These are things I have picked up trying to solve the problem with Google and personal grit. So please bear that in mind when answering.
Is there some way to access the data files on this phone from the bootloader screen or from the recovery screen? If the phone can't be booted up and the phone can't be unlocked without being wiped clean, it seems my son is going to be spending a lot of time and money recreating his music library. Is this true? Have we finally found a situation that Dad can't rescue his offspring from?
Thanks in advance for any ideas...
Click to expand...
Click to collapse
Very well written question... I'd start with a Fastboot command (entered while the phone is connected to pc and phone screen shows fastboot usb) 'fastboot erase cache.' It will return success, failure, or waiting for device. If it returns success enter 'fastboot reboot.' There is a small possibility this will allow his phone to boot normally.
You are correct that unlocking the boatloader erases the phone although there may be alternative if s-off is possible while the bootloader is locked - anyone? And ADB commands only work when the phone is booted into android or recovery not fastboot. And I have no experience with stock recovery but it might be possible to wipe cache there too.
Sent from my HTC One using Tapatalk
Thanks very much for the reply.
I tried the command 'fastboot erase cache' and it replied with "******* Did you mean to fastboot format this partition?"
Then, without waiting for an answer to that question, it proceeded - it said "erasing cache" and then "OK [0.575s]" and then "finished. Total time 0.575s."
I interpreted that as success, so I proceeded to enter the command "fastboot reboot." The phone rebooted - into the same boot loop I described earlier.
If you (or anyone) thinks that adb will help, I CAN get the phone into recovery mode as well. The phone allows me the option to wipe the cache partition from there (which I did), but a friend of mine (actually, my ophthalmologist as well) suggested I wipe the dalvik cache. Not only do I not know what a dalvik cache is, but I don't see any option for it on the HTC One recovery menu. I also don't know whether wiping the cache partition from the recovery menu is any different than what I did with the fastboot command - but in either event neither one eliminated the boot loop.
Any more ideas for either getting the phone to boot or saving the music so we can factory reset and then restore the music would be appreciated!
make a full adb backup and then unpack the contents
http://androidforums.com/application-development/163138-how-basic-adb-commands.html
http://forum.xda-developers.com/showthread.php?t=1572600
holmesnmanny said:
make a full adb backup and then unpack the contents
http://androidforums.com/application-development/163138-how-basic-adb-commands.html
http://forum.xda-developers.com/showthread.php?t=1572600
Click to expand...
Click to collapse
The only abd access he'll have at this point is for sideloading (Does the stock recovery even do sideload?), which if I am not mistaken, allows only a small subset of abd access (not enough to do the backup).
Would be so much easier if the handset was unlocked. A custom recovery would go a long way to recovering any data from the device... I've never had a device I didn't unlock right away so I'm afraid I can't help much beyond giving my doubts regarding the adb solution...
PhoenixPath said:
The only abd access he'll have at this point is for sideloading (Does the stock recovery even do sideload?), which if I am not mistaken, allows only a small subset of abd access (not enough to do the backup).
Would be so much easier if the handset was unlocked. A custom recovery would go a long way to recovering any data from the device... I've never had a device I didn't unlock right away so I'm afraid I can't help much beyond giving my doubts regarding the adb solution...
Click to expand...
Click to collapse
PhoenixPath, I'm afraid, was right, and we ended up doing a factory reset. My son restored the phone's contents as best he could, making sure to back up this time, and then powered off, but when powering back on the PIN unlock keyboard doesn't come up.
Sigh.
Any ideas? I'll post another thread on this...
Thanks to all who offered ideas.
Did you even try to do what I said or did you just assume I was wrong in full ?
I guess if you're not really interesting in ideas I guess you'll just choose altogether not to try some.
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.
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!
I have a Umidigi Crystal (2/16) and it´s not booting anymore.
How that came is a long story.:crying:
I got the phone, wanted to root it and while I was enabling usb debugging in developer options, I noticed you can root it from there as well.
I have no idea whether thats a Umidigi special or if that was seen on other phones too, basically I had a slider option to enable root access.
After a reboot, SuperSU was installed automatically, root checker, file explorer and rom toolbox worked fine with it but I actually rooted to get Xposed Installer.
That worked very well too, only did I want to have a custom recovery to prepare my phone in case of a bootloop.
So I followed these instructions.
I hadn´t unlocked the bootloader by the time and since the instructions said I would have to unlock it I did that first using these instructions.
Everything worked as expected but from this point on, on the pre-bootanimation picture my screen would say
Code:
Orange State
Your device has been unlocked and can't be trusted
Booting in 5 sec...
As everything else was the same as before, I just ignored it.
Then I moved on to installing TWRP by, again, these instructions.
The process seemed to work but after finishing, I was unable to boot into recovery mode, my phone would just boot into the normal OS(which still worked by the time).
I wanted to get around that by using this app but because of the unlocked bootloader my phone was factory reset
and I had to root again.
I was going for the same way I already did it beforehands and I was asked to reboot again.
After that point, my phone was stuck in the pre-bootanimation screen saying it´s orange state thingy again and would just stay there forever.
I tried installing the stock rom from here ((2/16 - V1.0_20171026)) to get rid of the root setting I enabled.
Now I get the pre-bootanimation screen with the orange state text again and after 5 seconds it keeps the background image but the text disappears.
Thats where it´s stuck for like 3 hours now.
When I press the power key a couple of seconds, that loop starts again, I can´t turn the phone off.
Things I can still do:
•Reboot (holding the power button, still get stuck the same way though)
•Access a PC, the internet, an SD Card and electricity
•Charge the phone
•I still have all the drivers on my PC properly installed
Things I can´t do
•Keep the phone turned completely off
•Boot into fastboot, recovery or normal OS
•Get the PC to recognize my phone (not even the adb)
What I want (if possible in that order):
•Boot into literally any OS
•Use the current OS or any custom rom
•Have root access without the developer option method
•Have TWRP
•Unlocked Bootloader
I know, I ask for a lot but this is the only phone I have right now and I badly need it.
Getting it to boot again is really the primary goal here.
Thanks so much to everyone who tries to help me, it really means a lot
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