Hi,
So I busted the screen/digitizer on my N6. Phone will still ring and give notifications but screen is dead.
With no way to take the phone out of charge only mode and access it via USB, is there any kind of work around to recover my files on the phone without resorting to buying a new digitizer/screen for $150(already got a replacement phone). I'm comfortable enough with computers and doing cmd functions, I just have no idea how to tackle this.
dahak7 said:
Hi,
So I busted the screen/digitizer on my N6. Phone will still ring and give notifications but screen is dead.
With no way to take the phone out of charge only mode and access it via USB, is there any kind of work around to recover my files on the phone without resorting to buying a new digitizer/screen for $150(already got a replacement phone). I'm comfortable enough with computers and doing cmd functions, I just have no idea how to tackle this.
Click to expand...
Click to collapse
Do you have TWRP recovery installed? Booting to TWRP should give you access to internal storage.
Is ADB enabled in developer menu (which itself would have had to been enabled). If so, the obvious answer would be to reboot to bootloader and use adb pull.
If nether of those options, then *maybe* you can use a technique where TWRP is booted on the PC. I'm on the road, so I can't test that for you.
Nope no TWRP, not even rooted and I didn't set up developer mode. Learned my lesson and have that all set up on my 6p, guessing I might be screwed.
Thanks so much for taking the time to try and help me out.
dahak7 said:
Nope no TWRP, not even rooted and I didn't set up developer mode. Learned my lesson and have that all set up on my 6p, guessing I might be screwed.
Thanks so much for taking the time to try and help me out.
Click to expand...
Click to collapse
I'm not so sure I'd give up quite yet. The booting twrp on your PC might work. requires USB debugging enabled.
Do you have tasker? Maybe we could create an auto task. requires usb access which you don't have.
That's what I get for spitballing before coffee.
So, unless your bootloader is already unlocked and you can fastboot flash twrp, you're stuck. I'm sure you're aware, unlocking the bootloader now would wipe your data you're trying to recover.
Related
Hey everyone ^^
Hoping I can find some help here, else it'll be another phone consumed by the bricking plague
I recently tried to flash the latest CM from sourceforge, but the flashing process was interrupted (Powercut FFS). So the phone's stuck at the bootscreen. Normally, it'd be a case of rebooting into download mode and retrying, but....
My home key is buggered, it had a disagreement with some rain. Again, normally it'd be fine. Just use ADB to get into recovery/download, but...
The bad flash has made the phone unable to be recognized. Unsure whether it fails before it initializes USB, but it just won't be picked up on either ADB or Odin.
It's not all bad, I can still see the first Galaxy S bootscreen (The first one being the static, unflashey one).
TL;DR: Phone is buggered, unable to use "conventional" methods to access download mode, bootloader is still intact.
Could somebody please give some advice on this situation? It'd really help me out! Not keen on getting a new phone just yet
Cheers,
Morgan ^^
use JIG mate
http://forum.xda-developers.com/showthread.php?t=819551
thanks to TheBeano.
Yeah, I was looking into that. Unfortunately it'd take a few weeks for the parts to get here (No places like RadioShack etc) and this phone needs to be working ASAP (Usual story, right? ). Short of taking a knife to the AC adapter and hoping that I can find a 300K resistor, I'm at a loss as to what to do...
And now, this is even more interesting. Out of curiosity I decided to try to install my phone's drivers manually (For some reason Windows wasn't picking them up). The ADB drivers installed without any problems and I can now issue commands via ADB
The bad news is, well... Apparently most of the system stuff is missing. No /System/Bin directory at all (The only thing in /System is Lost+Found). Which, obviously, is bad. I tried issuing "reboot recovery" and "reboot download" which both worked, except the phone quickly flashed a white/blue line across the screen and restarted.
Is there any way to restore functionality through ADB? Can I push files to the /System/Bin directory (And all other missing things...)? If so, where would I get the files?
Hi, I have a rooted HTC One running the Google Play Edition ROM (first rooted device) but I stupidly hit the 4.3 OTA update when I got the notification. Apparently this is a big no-no, but I didn't know any better and now my phone can't get past HTC's splash screen. I can still enter bootloader and recovery (CWM 6.0.3.2) but that's about it.
I don't have a ROM on the internal memory, so can't just revert to the previous 4.2.2 and because I can't enter the phone's settings to turn on USB Debugging. The phone does not show up in Windows Explorer, nor in 'adb devices' when I do the usual thing on Command Prompt. The phone shows up in Device Manager under Android USB Devices as 'My HTC' but again, no device will appear in Command Prompt, otherwise I'd adb push a new ROM onto the phone.
I've tried clearing cache, dalvik and so on with zero luck. It's causing me all sorts of grief and I've been pulling out my hair since yesterday. I've heard that an OTG micro-USB cable might help by loading a ROM onto a flash card, but I'm looking at a few days delivery (at least) and would like to get this problem sorted ASAP. If you can help, I'll name my firstborn after you.
Strand0410 said:
Hi, I have a rooted HTC One running the Google Play Edition ROM (first rooted device) but I stupidly hit the 4.3 OTA update when I got the notification. Apparently this is a big no-no, but I didn't know any better and now my phone can't get past HTC's splash screen. I can still enter bootloader and recovery (CWM 6.0.3.2) but that's about it.
I don't have a ROM on the internal memory, so can't just revert to the previous 4.2.2 and because I can't enter the phone's settings to turn on USB Debugging. The phone does not show up in Windows Explorer, nor in 'adb devices' when I do the usual thing on Command Prompt. The phone shows up in Device Manager under Android USB Devices as 'My HTC' but again, no device will appear in Command Prompt, otherwise I'd adb push a new ROM onto the phone.
I've tried clearing cache, dalvik and so on with zero luck. It's causing me all sorts of grief and I've been pulling out my hair since yesterday. I've heard that an OTG micro-USB cable might help by loading a ROM onto a flash card, but I'm looking at a few days delivery (at least) and would like to get this problem sorted ASAP. If you can help, I'll name my firstborn after you.
Click to expand...
Click to collapse
I think an RUU for your carrier will do the trick. There are a lot of RUU's posted in the HTC One forums in the various sections, search and find the one for your phone/carrier. Pretty sure that will do the trick!
dgtiii said:
I think an RUU for your carrier will do the trick. There are a lot of RUU's posted in the HTC One forums in the various sections, search and find the one for your phone/carrier. Pretty sure that will do the trick!
Click to expand...
Click to collapse
Hi, I've read up on this option but apparently it unroots my phone and basically returns it to factory settings. This will be my last choice. Thankfully all my photos from a recent trip have been backed up to Dropbox/Drive, but I'd need to root again and jump through all the hoops. I simply want a way to get a new ROM onto the phone to flash it, but neither of my computers are recognising the phone in recovery, with USB debugging off.
Strand0410 said:
Hi, I've read up on this option but apparently it unroots my phone and basically returns it to factory settings. This will be my last choice. Thankfully all my photos from a recent trip have been backed up to Dropbox/Drive, but I'd need to root again and jump through all the hoops. I simply want a way to get a new ROM onto the phone to flash it, but neither of my computers are recognising the phone in recovery, with USB debugging off.
Click to expand...
Click to collapse
Dude, have you a phone that won't get past the splash screen, and you're worried about losing data? If you could get a computer to see the phone, you could push a rom to it in ADB and then sideload it in recovery. If you can't, I think you're left with an RUU I'm afraid.
Strand0410 said:
Hi, I've read up on this option but apparently it unroots my phone and basically returns it to factory settings. This will be my last choice. Thankfully all my photos from a recent trip have been backed up to Dropbox/Drive, but I'd need to root again and jump through all the hoops. I simply want a way to get a new ROM onto the phone to flash it, but neither of my computers are recognising the phone in recovery, with USB debugging off.
Click to expand...
Click to collapse
You can just root/unlock/s-off it after, you've come this far already so you should be familiar with the short process
Flash a ROM using an OTG cable if you have one.
AllAboutTheCore said:
Flash a ROM using an OTG cable if you have one.
Click to expand...
Click to collapse
Cheers for the info guys. I think I'll wait till Monday to buy an OTG cable, fingers crossed this will work. In hindsight, I should have kept some ROM on the phone memory or left debugging on. At least now I'll know not to do an OTA update on a rooted phone.
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Marco2G said:
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Click to expand...
Click to collapse
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
danarama said:
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
Click to expand...
Click to collapse
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Marco2G said:
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Click to expand...
Click to collapse
Haha, no worries. Sometimes it is hard to see the wood for the trees.
Hi guys,
I just broke my phone's screen & digitizer, it's all black except for a few lines at the top of the screen, and I've used screenshots (viewed on windows) to verify touch is doomed as well.
I need to enable usb debugging to mirror the phone to windows, but I'm unfortunately not in any town area for a few days to buy and try a otg cable with mouse. I think there's a way to enable usb debug through abd, but I'm no expert on this, please help...
My phone's bootloader is unlocked, it's rooted, TWRP, can't remember exactly if it's on 4.4.2 or 4.4.4.
I know adb works with it, but I haven't use adb since 2 or 3 years back.
I can copy photos, videos, and audio recs through windows, but there are contacts and certain app data with my notes which I don't know how to retrieve / can't find through windows.
Can anyone help me out? Much appreciated if you could give step by step guide.
Thanks in advance....
adb needs usb debugging enabled, that's why its called Android Debugging Bridge.
Not much you can do, unless you van somehow navigate to developer options and tick the option + confirmation dialog.
Anyway, maybe someone else got a better idea
thanks liveroy, i'll try to get a otg cable later
Pretty much you can do if you have unlock bootloader, flashing twrp will give you adb by default.. Many more things you can do in fast boot
cilix said:
thanks liveroy, i'll try to get a otg cable later
Click to expand...
Click to collapse
Salik, thanks for informing, but unfortunately, my phone's battery is out and it doesn't seem to charge anymore. So, I'm now just patiently waiting for my X Play to arrive, and give it more protection At least it comforts me when I can't get back my two years worth of notes :silly:
Salik Iqbal said:
Pretty much you can do if you have unlock bootloader, flashing twrp will give you adb by default.. Many more things you can do in fast boot
Click to expand...
Click to collapse
Hey Guys,
My phone's screen got broken a few months ago. I remember I tried to recover the data from the phone but I hadn't enabled USB debugging prior getting it broken and had a really hard time trying to find a solution. I indeed realised that I can flash a Custom Recovery through Fastboot mode (I can access them, even without a screen. Intuitively and thanks to adb.) in order to log into the Custom Recovery and then be able to perform adb commands to pull out the data from internal memory. It seemed fair, but I just couldn't get it to work, given the fact that I also had no visuals of what I was doing, even though I followed correct steps. My question and help I need from you, is:
- Has anyone stumbled upon such inconvenience, and if yes how did it turn out?
- Could someone please tell me if its even possible to execute adb commands through a Custom Recovery in this phone, and which recovery would that be? (a redirection link/download .img file would be very appreciated)
- Recall my memory by telling me the basics of going to fastboot and after flashing the Custom Recovery, going into the CR from there. (Since I have no screen and its been quite a while, I don't remember the commands, button combinations of this phone). A video representation example would be greatly appreciated.
I really do not have a lot of time now, and I want to get the data back from the phone, precious photos and memories, and I can't have the luxury of time getting through the process alone with no proper guidance, so any help would be very appreciated.
Thank you!