Related
I was on a call and when I hung up, wanted to unlock.
Push the power button, lights on the 4 bottom buttons come on. Screen stays black, no backlight.
Push the button again, lights go off.
Push again, lights come on, no screen.
etc, etc...
I pulled the battery, and put it back in.
Now it's just sitting here saying HTC, but it doesn't get to the "quietly brilliant" ever. It just sits there forever saying HTC.
The phone is hacked, rooted, ENG S-OFF, was running Android Revolution 4G 5.1.6 or something when this all happened.
I can get into the [vol-] + [power] menu (white BG) and to recovery (black BG), but I'm not sure how to transfer files to the SD card to load a new ROM on without Android.
Can I use ADB to push a file across? If so, how?
Is there anything I should try before I wipe my phone? I'd like to back up my apps and SMSs if possible, but won't break down in tears if I can't.
Edit: I don't really know very much about ADB/Fastboot, but when I type ADB Devices the phone doesn't show up, however if I go into "Fastboot" in the white screen, I can type Fastboot Devices and my phone is listed. I suspect I can somehow push across the Android Revolution 4G ROM zip file and wipe/install it from recovery? I'm not sure how though.
WHile the phone is completely off, press and hold the Volume (down) and the Power off/on button (press the volume down first if that makes it easier ,then the power button).
Then you should get to the Hboot screen (white back), in there you should have the option to go to recovery...
As long as you can get to recovery ,your perfectly safe (even if just the hboot page)...In here you can reinstall a new ROM.
You can do so by going to mounts and storage , and choose mount usb storage (or something; make sure your connected to the PC with the USB)..
Your phone should now be connected to your pc Via your SD card..
Just download a new ROM, and then put it somewhere in your SDcard and after that, choose install zip from SDcard and select the ROM file you just transfered.
ANd unfortunately but, if you cant get passed recovery..I believe there would be no way to back up any phone/internal data .
If he wanted to back up some data as long as he has AR 5.1.6 still he should be able to reflash the rom w/o a full wipe to try and get the phone to boot so he can back up.
Some times it works sometimes it doesn't.
Just boot into hboot , then from there get to recovery. Once in recovery, you should now be able to use adb (if fastboot is working, it should see the phone in recovery).
Now put the rom in the platform tools folder(or whereever your tools/adb is (not sure if your using Linux or windows but this should work with either. Now open a terminal to platform-tools(or like earlier, whereever adb and now the rom are) now -
adb push nameofrom.zip /sdcard
nameofrom.zip has to be exactly what the name of the rom is you put in the location that has adb in it.
It will take a few min. to push the whole rom, when its done flash it.
This is all assuming you don't have adb in your enviorn . path- it can be done a little differently if you have it in your path in windows or Linux, but this way will work either way.
Or use fastboot to flash a new system.img, but you'll have to find one or make one- don't know where.
Di11's method is fine, but pardon me if im mistaken, can't he, since he's able to boot into recovery, plug his cord in>mount usb storage>transfer rom to sdcard>unmount>and wipe data/cache/dalvik/flash rom? it would seem easiest
Ya, sometimes I've noticed in the past when ****s all muffed up it wont wanna mount as USB storage. (Dont know why but it happens)This works every time.
di11igaf said:
Ya, sometimes I've noticed in the past when ****s all muffed up it wont wanna mount as USB storage. (Dont know why but it happens)This works every time.
Click to expand...
Click to collapse
Never had a problem like that, least that i know of lol, my baffled mind forgets to put the rom on my phone since i flash your rom and sense rom's daily, so i always just mount while in recovery after wiping everything.. Anyways, OP report which method you used and how it works.
Hey Guys ,
I think my phone is dead or bricked... ...i have tried to root with the hack-ace and had an issue in the middle of the rooting !!...now my phone can't boot , not even recovery mode , pull the battery, put it back in , nothing happens ..when i plug the usb cable into the computer i have the orange led lighting up but no boot is possible...
have any solution for me ?? it would be highly appreciate !!
thanks
maostar said:
Hey Guys ,
I think my phone is dead or bricked... ...i have tried to root with the hack-ace and had an issue in the middle of the rooting !!...now my phone can't boot , not even recovery mode , pull the battery, put it back in , nothing happens ..when i plug the usb cable into the computer i have the orange led lighting up but no boot is possible...
have any solution for me ?? it would be highly appreciate !!
thanks
Click to expand...
Click to collapse
Go back to the hack kit thread, read the op, towards the bottom it talks about hitting the irc for help. Reeeaaadddd then go there for help.
I got your 10 char right here
Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.
Sapphire18 said:
Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.
Click to expand...
Click to collapse
Em so is the bootloader unlocked? you could try to see if adb is working in fastboot or if it is unlocked I think TWRP lets you use adb.
Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.
Sapphire18 said:
Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.
Click to expand...
Click to collapse
Ok but have you tried adb in fastboot?
adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.
Goatshocker said:
adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.
Click to expand...
Click to collapse
Omg so forgot you can use a mouse so going to do that now for no reason lol.
Darknites said:
Omg so forgot you can use a mouse so going to do that now for no reason lol.
Click to expand...
Click to collapse
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.
Goatshocker said:
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.
Click to expand...
Click to collapse
Cool think I have a play later.
Okay, here is what I got, the OTG cable is not working, that means the phone doesn't have Android 4.1.
The ShareKM application requires installation into the phone, meaning it is out of question too.
I am experimenting with this ADB in fastboot, but I am not really sure how that fastboot command works when I run ADB.exe trough command prompt and list devices, it show me only my other phone in USB debugging, when I run the fastboot.exe and type adb devices it says "waiting for the device", I do not really know how to work with this with a little guide, it shows me some commands there, i tried the one with rebooting into bootloader, but it still says only "waiting for device".
Could you give me a little guide perhaps link to guide what exactly I am supposed to do to run ADB in fastboot?
I am pretty technical type, dont need noobish explanation.
Thank you
Okay, I managed to get into fastboot, I always thought it is something with the fastboot.exe in SDK Platform-tools, well, anyway, I am inside, it says Fastboot USB, but adb still isnt showing the device in the list.
Also there is a big pink ***LOCKED***, that means that bootloader is locked I guess.
Any other ideas how I could backup the files? or any other suggestions?
Thank you
Moving slowly forward, I was being stupid and I was using the ADB command instead fastboot command, when I am in fastboot mode now, well, trough fastboot command now the PC recognizes the phone, altho what is the next step now?
Thanks again
Yeah, the ShareKM app was never really ment for you, it was more of a suggestion to dark sorry if it confused you.
I ran some quick tests, and yeah Im afraid adb is, in fact, not working in bootloader.
What happens if you boot into recovery? Maybe it works there?
What kind of things do you need to save? Is it just like pictures and stuff from the sdcard?
In that case, you could unlock the bootloader (this will wipe the device data, like applications etc) and install TWRP. Im 100% sure ADB works in TWRP without you needing to use the screen.
Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?
Sapphire18 said:
Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?
Click to expand...
Click to collapse
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.
Darknites said:
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.
Click to expand...
Click to collapse
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?
Sapphire18 said:
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?
Click to expand...
Click to collapse
Em did you try scan under select device?
Darknites said:
Em did you try scan under select device?
Click to expand...
Click to collapse
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.
Sapphire18 said:
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.
Click to expand...
Click to collapse
Then I'm out of ideas because unlocking the Bootloader will wipe the sd.
Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)
Goatshocker said:
Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)
Click to expand...
Click to collapse
And I am not throwing any blame either, I am just open to every solution
How would unlocking the bootloader help me? so I could put that TWRP inside and do some magic with it?
For the recovery part, I am not really sure how it is supposed to work, but every picture I googled shows some text
along with the exclamation mark, but the only thing I am getting is exclamation mark, and after a while the phone reboots.
I am guessing the recovery either wont load up, or something is wrong, should I try running ADB while that exclamation mark is shown?
After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.
sinaisinai43 said:
After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.
Click to expand...
Click to collapse
I'm having the same exact issue, except with SlimBean 4.3. My phone is stuck in Fastboot (and says "FASTBOOT - NO BOOT OR RECOVERY IMG") and my phone will charge but can't be detected by *any* computer. I've tried three Windows 7 PCs of different makes and an Ubuntu 13.04 box and three different USB cables that all connect my other phone and my tablet fine - none can see it. (It was connecting fine to PC including being seen by ADB prior to this)
My power button is working, but it is also automatically booting into fastboot on its own when I plug it into the computer. Any of the options (besides "Power Off", which performs as advertised) just brings it back to Fastboot.
When I say can't be detected by a computer, I mean there is no USBDeview device listed and there is no 'connect' or 'disconnect' sound on the PC. ADB can't see it.
Yeah, it's strange. Did you find a solution yet, by chance?
sinaisinai43 said:
Yeah, it's strange. Did you find a solution yet, by chance?
Click to expand...
Click to collapse
Nothing yet. Thinking of buying an phone with a busted screen or something and swapping out the internals... I think it's PROBABLY the NAND chip. What I'm suspecting is that because there are several versions of the Nexus S, we might have used the wrong images. I have no idea if this is correct, but it's the only thing I can think of.
My phone's sticker says i9020 on the inside, but D720 (or whatever) when I look up the EIN.
Just hoping somebody sees this and offers a suggestion... I'm getting ready to buy a refurb and put the 'new' body over it so at least I have a functioning, new-ish phone.
I woke up this morning and my Pixel is dead. Completely unresponsive, can not get into bootloader from the phone.
Any ideas?
I got a replacement ordered through Google, and am using my Nexus 6 for now. It's a little frustrating that they authorize the replacement cost of the phone to process the order when I've got multiple credit cards on file with my Google account (which goes back to when Gmail was invite only) but I'll deal with it.
Just went through this yesterday. Put a hold on my card to replace even though I paid in full for the first one. So now I'm out the cost of 2 and have no phone.
Are you guys still stock?
magnumtripod said:
Are you guys still stock?
Click to expand...
Click to collapse
Yes. Stock. Bootloader unlocking enabled in developer settings but not unlocked. Running the latest OTA.
This is precisely why I always unlock the bootloader immediately after I pull my Nexus (now Pixel) devices from the packaging.
Sorry to hear about the issues. Hope you get your replacements soon.
sn0warmy said:
This is precisely why I always unlock the bootloader immediately after I pull my Nexus (now Pixel) devices from the packaging.
Sorry to hear about the issues. Hope you get your replacements soon.
Click to expand...
Click to collapse
Having the bootloader unlocked would not help in this case, since the phone is completely dead. It will not connect to the computer at all. If I could connect it I could unlock the bootloader through adb and try reinstalling the software. With a complete unresponsive brick, I'm pretty much out of ideas.
atlp99 said:
Having the bootloader unlocked would not help in this case, since the phone is completely dead. It will not connect to the computer at all. If I could connect it I could unlock the bootloader through adb and try reinstalling the software. With a complete unresponsive brick, I'm pretty much out of ideas.
Click to expand...
Click to collapse
Having the bootloader unlocked very well could have helped in this situation, even if the screen won't turn on. There have been a few times that I had phones go completely unresponsive on me and appear to not turn on at all. But following the procedure of booting the phone into the bootloader (power/volume down), allowed me to connect the phone to the computer and communicate with it using fastboot commands. Even with nothing appearing on the phones screen.
This allowed me to fastboot wipe everything and flash a new factory image. The phone booted up just fine afterwards.
Obviously, I can't say with 100% certainty that this would have worked in your case but I've been in your exact situation, more than once, with a phone that was nothing more than a paperweight. Having the bootloader unlocked did solve the problem each time.
sn0warmy said:
Having the bootloader unlocked very well could have helped in this situation, even if the screen won't turn on. There have been a few times that I had phones go completely unresponsive on me and appear to not turn on at all. But following the procedure of booting the phone into the bootloader (power/volume down), allowed me to connect the phone to the computer and communicate with it using fastboot commands. Even with nothing appearing on the phones screen.
This allowed me to fastboot wipe everything and flash a new factory image. The phone booted up just fine afterwards.
Obviously, I can't say with 100% certainty that this would have worked in your case but I've been in your exact situation, more than once, with a phone that was nothing more than a paperweight. Having the bootloader unlocked did solve the problem each time.
Click to expand...
Click to collapse
I didn't say it but I tried that.
The phone doesn't show up at all on the computer. No USB connection at all. If it connected, I could unlock the bootloader through adb and reflash.
atlp99 said:
I didn't say it but I tried that.
The phone doesn't show up at all on the computer. No USB connection at all. If it connected, I could unlock the bootloader through adb and reflash.
Click to expand...
Click to collapse
What? The phone is unresponsive and the screen won't turn on. So there is no way you could unlock the bootloader through ADB because you need the phone's screen functioning in order to check "Yes" for the final prompt of unlocking the bootloader.
With that said, even though the computer doesn't recognize the phone as a USB connection, that doesn't mean it wouldn't communicate with the phone using fastboot commands. Like I said, myself (and many others on this forum) have been in your EXACT situation with a completely unresponsive phone which the computer wouldn't recognize as a connected USB device. However, that didn't stop the computer from recognizing/communicating with the phone via fastboot commands.
It's a moot point now that your replacement is on the way. But I'm still convinced that if your bootloader was unlocked you could have saved the phone.
sn0warmy said:
What? The phone is unresponsive and the screen won't turn on. So there is no way you could unlock the bootloader through ADB because you need the phone's screen functioning in order to check "Yes" for the final prompt of unlocking the boot loader.
With that said, even though the computer doesn't recognize the phone as a USB connection, that that doesn't mean it wouldn't connect to the phone using baseline fastboot commands. Like I said, I've been in your EXACT situation with a completely unresponsive phone and the computer would not prompt me that a new USB device was connected even when the phone was plugged into it. However, that didn't stop the computer from recognizing/communicating with the phone via fastboot commands.
It's a moot point now that your replacement is on the way. But I'm still convinced that if your bootloader was unlocked you could have saved the phone.
Click to expand...
Click to collapse
If it would connect through adb (even if the phone was unresponsive) fastboot OEM unlock would work. I forget off the top of my head what the new command is, but at this point it doesn't respond to that at all.
atlp99 said:
If it would connect through adb (even if the phone was unresponsive) fastboot OEM unlock would work. I forget off the top of my head what the new command is, but at this point it doesn't respond to that at all.
Click to expand...
Click to collapse
"fastboot oem unlock" is just the first part. You still need a responsive phone to unlock the bootloader by hitting 'volume up' and then 'power' as the final step to unlock the bootloader. The computer won't recognize the phone via ADB because the phone is unresponsive and won't power up fully. But just because the computer won't recognize/communicate with the phone via ADB commands, doesn't mean it wouldn't recognize/communicate with it via fastboot commands.
It's pretty common that people have run into an issue where their phone won't recognize ADB commands but still recognizes fast boot commands, especially with bricked phones.
https://www.google.com/search?clien...not+working+but+fastboot+is&ie=UTF-8&oe=UTF-8
I'm telling you, if your bootloader was unlocked, I'd bet money that you would still be able to communicate with your bricked phone using fastboot commands. The inability to communicate with your phone using ADB commands does not negate that.
Possible workaround...
Try holding the power and volume down for 20 seconds no matter what the phone does, or whether you even see anything on the screen, and if you get nothing, then try to do the same with volume up. I have had phones get stuck "in between" modes, for example trying to leave bootloader, recovery, or whatever else, and got stuck on a black screen, when the phone was in fact on. Everyone else's responses here were legit, though. I agree totally on the communicating with the phone via fastboot etc. If you can get it to bootloader even with the screen off, you can flash the entire phone. Of course this means you may lose items saved on the device.
I had this same issue happen...black screen but could hear the phone connect to the computer but fastboot wouldn't work...tried every possible combination oh buttons to get into anything and could...had to replace
http://forum.xda-developers.com/pix...ader-total-t3503963/post69713209#post69713209
Me too.
Well I got the replacement from Google on Wednesday and everything is running fine.
They did send a new phone, in retail packaging with all new chargers and cables. At least it wasn't a refurbished one.
I'm checking out my sister's phone that she dropped and broke the screen. Device boots up, since I can feel the vibration and hear alarms but the screen is dead. Debugging was not enabled, bone stock. I can see it in fastboot, but I'm not sure if there is a specific mode to be in to allow ADB for this device. I've read Downloader mode, which should be 3 spots below where Fastboot drops you, but I get no change. Anyone have a suggestion on how to pull the old data off?
Atemi1337 said:
I'm checking out my sister's phone that she dropped and broke the screen. Device boots up, since I can feel the vibration and hear alarms but the screen is dead. Debugging was not enabled, bone stock. I can see it in fastboot, but I'm not sure if there is a specific mode to be in to allow ADB for this device. I've read Downloader mode, which should be 3 spots below where Fastboot drops you, but I get no change. Anyone have a suggestion on how to pull the old data off?
Click to expand...
Click to collapse
You can only have adb connectivity when booted in the OS and usb debugging must be ON. You must also allow your computer RSA key from your phone at the first attempt to use adb.
adb can also be used form a custom recovery (even with debbug off) but if the phone was still stock it's bootloader is probably locked... Unlocking the bootloader will wipe data (and a working screen is also needed to unlock it).
At this point I think replacing the display would be the only option...
Sorry
alray said:
You can only have adb connectivity when booted in the OS and usb debugging must be ON. You must also allow your computer RSA key from your phone at the first attempt to use adb.
adb can also be used form a custom recovery (even with debbug off) but if the phone was still stock it's bootloader is probably locked... Unlocking the bootloader will wipe data (and a working screen is also needed to unlock it).
Sorry
Click to expand...
Click to collapse
Pretty much confirmed my thought. Thanks for the glance.