Hey All!
I have a Sony Xperia Z1, which although advertised as waterproof, somehow got water damage after a day at the waterpark, even though all the flaps were perfectly closed and the phone even had a case that covered the whole back and sides of the phone.
After a few days of letting the phone dry out, now I'm able to connect it to my laptop, but only in fastboot mode as the phone won't boot up and I can't turn on USB Debugging to try and do something via ADB. Anyway, the bottom line is that I need to recover the files from my phone. I read about pulling files out through ADB, but I have no idea if it's possible to somehow acces the phone memory through Fastboot mode or at least switching to ADB using fastboot. The phone has insurance so I don't really care about the hardware, I just want my photos and files(which I realise I was an idiot for not backing up regularly).
Please help!
P.S. The phone isn't and has never been rooted.
Try here: http://forum.xda-developers.com/showthread.php?t=1849170
Thanks. I read everything but unfortunately the information found on that page and the links provided there doesn't help in my situation. From what I read there, the solutions include wiping all the data off the phone, which is exactly what I don't want to do. I would just need to somehow switch from the current Fastboot mode(blue light) to ADB, so that I can use the "pull" cmd and download my files from the phone.
Sorry to hear mate. Perhaps you find some ideas here:
http://forum.xda-developers.com/showthread.php?t=2229250
Thank you. I tried those solutions last night, I managed to enter flash mode, flashed only the system files, without wiping the data, everything was succesful, but unfortunately there was no change in my phone's state. Still no response when trying to power it up, still no ADB access. I'm starting to think that my data can't be recovered in the phone's current state
If you can get flashmode and flash system files succesfully and without errors you could also try to flash whole ftf of your device and wipe everything else but data.
Related
I have an HTC One M7 on T-Mobile, v4.4.3, with a locked bootloader and no root access (never got around to rooting). So the phone is basically completely untouched from a developer standpoint. I had previously accessed the developer options and I'm pretty sure I left USB debugging checked although not 100% positive.
The past few days my phone has been randomly rebooting, and then today I randomly found it in a state of apparent upgrading even though there are no new OTA updates (I checked yesterday). Then it was "optimizing apps" and going through all of them. Then it rebooted and ever since that point it has been stuck on the HTC ONE logo and will not boot to the home screen. I'm able to access the bootloader (HBOOT 1.57). I'm also able to access the stock recovery, from which I wiped the partition cache and rebooted with no success.
I have a ton of pics and videos from the first year of my son's life on the phone and stupidly did not back them up. I really want to avoid doing a factory reset if possible. Is there any way to recover these files?
I installed minimal ADB and fastboot. From within fastboot on the phone, I can see my device when typing "fastboot devices" in the command prompt. However, it does not list any devices when I enter "adb devices" in the command prompt, regardless of whether my phone is in the bootloader, fastboot, recovery, or stuck on the logo screen. I reinstalled updated HTC drivers and also tried with a universal ADB driver. I've tried multiple usb cables and all USB 2.0 ports, using Windows 7. While in fastboot, when I connect my phone to PC via usb cable, the computer makes the typical sound that it does when a USB device is connected and unconnected, however no drive/mount shows up.
All I want to do is find my device somehow on the PC and extract my photos and videos. I was hoping to use "adb pull" to do this but it just won't find my device. At this point, unlocking the bootloader and installing a custom recovery will wipe all data anyway, correct? Is there any way that I can recover my data in this situation?
Any help would be greatly appreciated since I'm at a complete loss and losing this data would be terrible. Thanks so much in advance!
mac12383 said:
I have an HTC One M7 on T-Mobile, v4.4.3, with a locked bootloader and no root access (never got around to rooting). So the phone is basically completely untouched from a developer standpoint. I had previously accessed the developer options and I'm pretty sure I left USB debugging checked although not 100% positive.
The past few days my phone has been randomly rebooting, and then today I randomly found it in a state of apparent upgrading even though there are no new OTA updates (I checked yesterday). Then it was "optimizing apps" and going through all of them. Then it rebooted and ever since that point it has been stuck on the HTC ONE logo and will not boot to the home screen. I'm able to access the bootloader (HBOOT 1.57). I'm also able to access the stock recovery, from which I wiped the partition cache and rebooted with no success.
I have a ton of pics and videos from the first year of my son's life on the phone and stupidly did not back them up. I really want to avoid doing a factory reset if possible. Is there any way to recover these files?
I installed minimal ADB and fastboot. From within fastboot on the phone, I can see my device when typing "fastboot devices" in the command prompt. However, it does not list any devices when I enter "adb devices" in the command prompt, regardless of whether my phone is in the bootloader, fastboot, recovery, or stuck on the logo screen. I reinstalled updated HTC drivers and also tried with a universal ADB driver. I've tried multiple usb cables and all USB 2.0 ports, using Windows 7. While in fastboot, when I connect my phone to PC via usb cable, the computer makes the typical sound that it does when a USB device is connected and unconnected, however no drive/mount shows up.
All I want to do is find my device somehow on the PC and extract my photos and videos. I was hoping to use "adb pull" to do this but it just won't find my device. At this point, unlocking the bootloader and installing a custom recovery will wipe all data anyway, correct? Is there any way that I can recover my data in this situation?
Any help would be greatly appreciated since I'm at a complete loss and losing this data would be terrible. Thanks so much in advance!
Click to expand...
Click to collapse
unfortunately, you need a booted rom or a custom recovery to use adb commands, so you can't pull your files from the bootloader or from the stock recovery. You already wiped cache and tried to reboot... Not much you can do except maybe to try reflashing the firmware and see if your phone can boot. Can you post the output of "fastboot getvar all" except imei and serialno?
alray said:
unfortunately, you need a booted rom or a custom recovery to use adb commands, so you can't pull your files from the bootloader or from the stock recovery. You already wiped cache and tried to reboot... Not much you can do except maybe to try reflashing the firmware and see if your phone can boot. Can you post the output of "fastboot getvar all" except imei and serialno?
Click to expand...
Click to collapse
Thanks for the quick reply. Here's the info.
Would reflashing firmware require the bootloader to be unlocked? It wouldn't wipe my data?
mac12383 said:
Thanks for the quick reply. Here's the info.
Would reflashing firmware require the bootloader to be unlocked? It wouldn't wipe my data?
Click to expand...
Click to collapse
no with s-on, bootloader must be locked to flash firmware.
What you could try is to download the 6.10.531.9 RUU and extract the firmware.zip and flash it to your phone.
Firmware.zip must be in the same folder where adb and fastboot are then open a command prompt (minimal adb/fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fasboot reboot
If this doesn't work I think theres nothing we can do (to access your files) At least you can restore your phone using the complete RUU
alray said:
no with s-on, bootloader must be locked to flash firmware.
What you could try is to download the 6.10.531.9 RUU and extract the firmware.zip and flash it to your phone.
Firmware.zip must be in the same folder where adb and fastboot are then open a command prompt (minimal adb/fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fasboot reboot
If this doesn't work I think theres nothing we can do (to access your files) At least you can restore your phone using the complete RUU
Click to expand...
Click to collapse
Thanks, I'll give that a try soon, probably tomorrow, and let you know how it goes. Appreciate the help
mac12383 said:
Thanks, I'll give that a try soon, probably tomorrow, and let you know how it goes. Appreciate the help
Click to expand...
Click to collapse
I flashed it successfully, but unfortunately the phone still did not boot to the home screen. I'll hold off on wiping everything for a little longer in case anyone has any other ideas. Thanks for the help!
HTC and T-Mobile were of no help, as suspected. I guess I just find it strange that there's NO WAY to recover data from a soft bricked phone. If I was some big-time criminal who was arrested by the FBI and my phone was seized in this condition, their analysts would have no way of getting into my phone and recovering the data? Maybe I just watch too many crime shows, I don't know...but that seems a bit unbelievable. Is there no way to (carefully) take it apart and access the hard drive in some other way? I'm desperate...
mac12383 said:
HTC and T-Mobile were of no help, as suspected. I guess I just find it strange that there's NO WAY to recover data from a soft bricked phone. If I was some big-time criminal who was arrested by the FBI and my phone was seized in this condition, their analysts would have no way of getting into my phone and recovering the data?
Click to expand...
Click to collapse
Yes they would disassemble the phone, de-solder the emmc chip and extract its data which is not an easy task...
Maybe I just watch too many crime shows, I don't know...but that seems a bit unbelievable. Is there no way to (carefully) take it apart and access the hard drive in some other way? I'm desperate...
Click to expand...
Click to collapse
There is no hard drive in your phone, its a memory chip (emmc). It is soldered to the main board and can't be removed by the user.
see the chip highlighted in orange? This is where your data is stored.
If you can't boot to the OS, your bootloader is still locked, and you have already tried to erase cache and reflashed the firmware, afaik, there's nothing more you can try
alray said:
Yes they would disassemble the phone, de-solder the emmc chip and extract its data which is not an easy task...
There is no hard drive in your phone, its a memory chip (emmc). It is soldered to the main board and can't be removed by the user.
see the chip highlighted in orange? This is where your data is stored.
If you can't boot to the OS, your bootloader is still locked, and you have already tried to erase cache and reflashed the firmware, afaik, there's nothing more you can try
Click to expand...
Click to collapse
I was afraid of that. Thanks for all your help though
Hi all,
A few years ago (well when the devices has pretty much just come out), I ran a mod which i found on the XDA website that allowed me to root my partners Xperia T (LT30P),
Everything has been fine until recently, where I've wanted to upgrade the ROM on the phone, but this is where i'm having some major problems.!
Essentially I cant get the phone to boot into either Flash mode (green LED) or Fastboot mode (Blue LED). I've tried the volume down and then connecting the USB cable to my PC (on which the correct drivers are installed via Flashtool). and also the volume up for Fastboot. Neither work. Unsure if the phone has an unlocked bootloader or if that matters (im a Samsung man and used to working with that, so all the Xperia modding is totally new to me... :/
So far ive tried the following:
-Volume down key and plugging into USB port - Result: Phone remains switched off.
-Volume up key pressed in and then plugging into USB port. - Result: Phone remains switched off
-Enabled USB debugging and attempted to boot the phone into flash mode via ADB (Flashtool option). Phone simply reboots.
-Attempted inbuilt software update - Update downloads, but fails at 25% approx when it reboots and attempts the install.
-PC companion equally unsuccessful on my PC, as cant enable flash mode.
I'm totally at a loss at how to flash a fresh complete build (using a ftf file) to the phone without access to flash mode or fastboot mode. Anyone got any idea or know of any tools that might allow me to to completely rebuild the phone so all partitions are present and correct?
One idea i had was to flash a recovery to the phone using FlashR or alike, but cant seem to get it to work either. Flashr looks to install the twrp recovery, but when i attempt to reboot into recovery via Flashr or Rom Manager (another tool i use but not sure if useable on xperia phones?), the phone simply reboots. SOunds like a damaged or wiped partition perhaps?
Anyhoo , any ideas would be welcome guys! Too good a phone to just leave in the drawer
Cheers
Craig.
Cant you flash a boot.img (maybe from cm11 or something) with inbuilt recovery? You can use this for flashing
Ok, I've started writing this reply and lost everything near the end, started freaking out, calmed down and decided to do it again, cause I know what it's like to have a phone that's not behaving as it should. So here goes the shorter-ish version cause I really can't type everything again...
Make sure your volume buttons are working at all (I mean when the phone is booted). They work? good, procced. They don't? we can bypass that, but you, should get them fixed.
Got to this thread and download the latest build of the ROM http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-12-neo-s-homebuilds-t2984988
Extract the boot.img file from the zip and copy it to the root of your external micro sdcard, NOT IN A FOLDER. If you don't have an sdcard, put in on the internal storage, again, not in a folder.
Root your phone if you haven't. There are plenty of threads on that here on xda
Download an app called Terminal Emulator from the Play Store
Open the app and type su into the prompt.
Grant the app superuser/root access
The following step is the dangerous one where you can seriously break your phone forever. I'm not responsible for anything you mess up. You alone chose to do this
Run the following command in the terminal (be sure that the $ at the end of the line changed to a # (That means you're in root shell, but it's not important))
If you don't have an external sdcard type sdcard0 instead of sdcard1
Code:
dd if=/storage/sdcard1/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/Kernel
Connect the phone to a PC with fastboot drivers installed
Next execute this command and your phone should now boot into fastboot
Code:
reboot bootloader
If a blue LED lights up, you can happily continue flashing kernels and ROMs, if not report back and I'll see if I can help you
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
crstephenson said:
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
Click to expand...
Click to collapse
No and it probably never will be. It's hardcoded on the chip. If your phone is bought with a contract binding or it's limited to a single provider, then chances are that you will never be able to unlock the bootloader and flash kernels. It could be that you not being able to get into fastboot is because it's restricted on the device itself [citation needed]. In that case you're screwed and can pretty much forget the whole custom kernel thing. Only ROMs for locked bootloaders
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.
I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!
ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk
hello,
It's worst scenario I could imagine, My sisters Xperia Z1 dropped on street floor and crashed almost 70% of the screen,
touch is working on the remain area, she left the device for a while, and now she need some contacts, sms, pics from it, she forgot the pattern, and forgot the google mail associated !!.
I tried many ways described in many sites to remove the pattern without removing stored data, but the way ends at USB debugging OFF on the device,
please any one can lead my to how to unlock it ?
and in worst case if we can reset the device totally , how to do that? and can we use some app to recover data?
any help would be so appreciated.
thanks
A.H.A
engali555 said:
hello,
It's worst scenario I could imagine, My sisters Xperia Z1 dropped on street floor and crashed almost 70% of the screen,
touch is working on the remain area, she left the device for a while, and now she need some contacts, sms, pics from it, she forgot the pattern, and forgot the google mail associated !!.
I tried many ways described in many sites to remove the pattern without removing stored data, but the way ends at USB debugging OFF on the device,
please any one can lead my to how to unlock it ?
and in worst case if we can reset the device totally , how to do that? and can we use some app to recover data?
any help would be so appreciated.
thanks
A.H.A
Click to expand...
Click to collapse
If she has recovery, you should be able to start recovery and from there you can connect the phone to computer and have access to internal card. If there is no recovery and bootloader is unlocked, fastboot TWRP and do the same. If bootloader is locked, and there is a google account prompt, I doubt you'd be able to get to data. But google the options...
Hello,
I'm Afraid there is no recovery available ,
as I check about fastboot TWRP recovery, it needs first the device to be rooted and "Enabled USB debugging " ; means need the device to be opened and rooted and Enabled USB debugging !.
any idea please ?
unlock bootloader using fastboot mode via flashtool, then fastboot flash twrp.
then boot into recovery and attach your device to pc.
links that might help are below
twrp recovery
how to unlock bootloader
how to flash with adb fastboot
If you don't have anything particulary worth saving on it, then just flash a fresh rom with flashtool.
team_div said:
unlock bootloader using fastboot mode via flashtool, then fastboot flash twrp.
then boot into recovery and attach your device to pc.
links that might help are below
twrp recovery
how to unlock bootloader
how to flash with adb fastboot
Click to expand...
Click to collapse
IGnoTon said:
If you don't have anything particulary worth saving on it, then just flash a fresh rom with flashtool.
Click to expand...
Click to collapse
thanks for replies,
my first problem is FLASHTOOL which is "EMMA" , it dosn't work at all, it always says: "unable to connect to the network" , ... while I really have a network connection working fine !!.
what to do please?
engali555 said:
thanks for replies,
my first problem is FLASHTOOL which is "EMMA" , it dosn't work at all, it always says: "unable to connect to the network" , ... while I really have a network connection working fine !!.
what to do please?
Click to expand...
Click to collapse
ok, get this one:
http://www.flashtool.net/index.php
it works like a charm. And it has firmware downloader built in.
after unlocking the bootloader and installing TWRP, you want to delete the file password.key in /data/system/ using this:
forum.xda-developers.com/showthread.php?t=1646108
then it should be unlocked. good luck.
History of the issue at hand:
I was running a new rom that was marshmallow based. It was running fine but lost root privileges so I attempted to boot into recovery and install the stable version of SuperSU for the device. I wiped the dalvik and cache and rebooted through TWRP recovery and the system went into a bootloop. Solution: Read XDA forums to find a way to fix the device. Went on ebay and bought a fastboot cable, waited 3 weeks, cable comes in and gets me to fastboot mode, but I am running Windows 10, creating a new problem. Solution: Partition the HDD on my computer and install Windows 7 Professional. This now fixed the driver issue. Plugged in the cable, with the new drivers installed and voila - Fastboot mode.
Seems pretty easy right? Wrong. After trying several utilites, I still cannot seem to get the Kindle to get out of the current situation it is in.
The device was rooted with the 2nd bootloader added over 2 years ago. Every ROM I have ran has been successful. Every time a new ROM was used or tried a backup was done and the device wiped properly before install. I made sure that every ROM was for my specific device (Tate).
Here is what I can do:
If I power on the Kindle, it briefly shows the logo, then the fastboot logo and goes blank
If I power on the Kindle by plugging in the factory cable and quickly entering any command (it is already typed) like "fastboot erase cache" the system will remain in fastboot with the fastboot logo on the screen. My sdk does recognize the device and states it is in fastboot.
From here I have no idea where to go. I can type any command I like, such as erase cache, recovery, system or any multitude of things and the command prompt takes it time to show the device is working on the command. However, the device remains unresponsive and has the same issues when attempting to reboot. When flashing anything the target size of the device remains unchanged at 1006632960 bytes, which seems to tell me that device is receiving the command but not writing anything to the device. This probably also means that anything that is on the device causing it to continuously bootloop or fail is not being erased or properly formatted.
All I have is fastboot and time. Time to scratch my head and wonder if the device is truly and totally bricked. i am under the assumption that if I have a working fastboot that I should be able to at least accomplish something. Even if it means reverting it to bare bones stock and starting the whole process over. I will be happy to answer any questions you all have regarding the system via here or PM.
Please assist this old man and thank you in advance for your time.
Give it a try
While I wasn't in the same weird brick scenario as you. My device would show up on my pc as fastboot and or regular adb. But, I would get no video. The solution which I have no idea why worked was to pop the back cover off. Then disconnect the battery from the mobo. Wait a few seconds. Connect it back to the mobo. After that video showed back up. Then proceeded on my way.
Not sure if what I did will help you. But. Then again I didn't think simply disconnecting the battery and reconnecting it would solve video issues.
You definitely do have a weird brick scenario. Good Luck!