[Q] Music file recovery - phone in boot loop - T-Mobile HTC One (M7)

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.

Related

[Q] Can't access recovery nor reset to factory settings on rooted device

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

NEED! Help on How to pull files using ADB from Recovery Mode !!

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!

*URGENT* HELP! File pulling with ADB

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.

Motorola Electrify M won't boot. Any ideas?

My wife was using her phone (completely stock, no mods whatsoever) and it started shutting down processes (contacts, calendar, etc). She held the power button down to manually shutdown and then rebooted shortly after. The next day, it started to do it again, so she did the same thing only this time it stuck on the "M" logo screen. When she brought it home, I held the power & vol down buttons in for 2 minutes and the phone began to reboot but still stuck on the "M" logo screen.
I began searching vigorously online for a solution and have tried everything. **NOTE** - I am completely unsure what version of software the phone was running before this happened. The first thing I tried was RSD Lite with the JB Stock file from Team US Cellular. The flashing fails during certain lines of the .XML file. I took suggestions from other users to delete the lines it fails on and let the file continue the flash. Once it reboots, it is still stuck on the "M" logo screen. I then tried all the other stock firmware files I could and the same result each time.
Next, I tried using ADB and Fastboot tools. My PC recognizes the phone when plugged in and running command "adb devices" shows the phone listed, but whenever I try to run a pull or other command, I get error:closed. I've tried all the solutions of making sure ADB files are updated, running the list of commands to get the daemon connection reset, etc. I can't push/pull anything using adb. I tried using mFastboot with no luck either.
I tried the above steps over and over for 3 days straight, hoping I missed something simple. My final option was to boot into Recovery Mode and run Wipe Data/Factory Reset. When I select that option, about 3 lines of command begin to run and the phone reboots and goes back to being stuck on the "M" logo screen. The command lines and reboot literally happen within 2 seconds. That tells me Factory Reset is corrupted, but I'm not 100% at this point.
Does anyone have any insight on if there is anything I can do at this point? It wouldn't be such a big deal to lose the phone, but we have pics/videos of our 2 year old that we never got backed up at home or in the cloud and they're very important to us. Unfortunately, the phone did not have and SD card. I'm honestly out of ideas at this point and have never felt so defeated.
I got brave and decided to just unlock the phone and attempt to install TWRP on it and that doesn't even work. It says it flashed it, but whenever I choose Recovery, it never boots to TWRP. It continues to use the stock recovery screen. I'm assuming this thing is just completely done for?

Bricked Lg V10 Need Help!

I was on my phone when suddenly it just booted off for no reason, weird right? So now it just stays on the "LG" boot up screen and now do anything. I've tried everything and done everything right (as far as I know) before I get into that let me tell you what my device can do as of now:
Devices DOES have fastboot oem unlock done
Phone was rooted as well and working perfectly (or so I thought until this happened)
ADB doesn't seem to work, but fastboot when connected to the computer does.
Ex: ADB devices (blank)
but fastboot devices (shows phone connected)
I've tried rebooting into recovery (Power + down) doesn't do anything, however, {Power + down} then finger off power then {Power + down} again takes me to "factory reset" option, if done so the phone just hangs and removing battery on way to take it back to fastboot on pc, or bootloop again.
I've done the following steps using [LG-H901] Stock .img Files (Boot, System, and Recovery)
Code:
fastboot flash system system.img
then
fastboot flash boot boot.img
and finally
fastboot flash recovery recovery.img
I've tried booting the phone and still gets me stuck on bootloop, and doing the same {Power + down} gets to the same "factory reset" option only then freezes my phone if I agree to do so.
Is there something I've done wrong or incorrect? I will provide as much info as requested.
Thanks guys!
Update: Phone booted up to lockscreen after finishing "Android is starting..." procedures, then kept bootlooping and it is now doing "Android is starting.." procedures again. I'll keep it updated if it keeps doing so or anything of the sort.
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Double0EK said:
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Click to expand...
Click to collapse
This is the weirdest thing, phone worked for a bit then shuts off and does the same thing. all files and everyhing was in tact. ANy main reason behind this? I am desperate not to delete everything because i have important photos on there that were still there when it re-started again right now.
So to recap: At the moment doing the {factory reset} got me as far as using phone for like 2 minutes before ****ting out and sending me on a bootloop yet again.
Important Questions:
On all my other devices I am able to connect via usb and read devices, but on this phone I get the message when connecting to my computer "LGE Android MTP Device: Failed" whats this about?
Is there any way to save internal photo album images other than getting this to boot up and pray it stays on long enough to transfer data?
UPDATE 2: Phone has booted up and not froze (yet)? Testing to see if it will keep working so far so good. Unfortunately all my **** was deleted which bummed me out, would have honestly prefered to lose a $600 phone than all the family, friend, ext photos I had on my phone I made the huge mistake of saving to internal memory and never backing up. Smh.
Update 3: Phone is back at it again with the bootloop. I have no idea what is wrong, I've repeated the steps twice and phone doesn't seem to let up. It's fine until I hit that restart or shutdown button then it goes into bootloop heaven. I'm guessing this phone is done for? On an unrelated note it did fall on me, but worked fine afterwards, it was just sudden when it started doing this. Unless anyone has more suggestions I'd be glad to hear them. As of right now, this phone is toast.
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Double0EK said:
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Click to expand...
Click to collapse
I am thinking the warranty route. Is there anything specific I should do before doing so? I hear having "fastboot oem unlock" {Bootloader Unlocked} voids the warranty. Is this true that you might know of? Either way thanks I appreciate the information.
Sorry so late..
But you can try to fastboot oem lock it.

Categories

Resources