LCD on my Moto X 2014 cracked, and it will not boot up into Android. I really just want to get to the storage on the device so just a adb interface would work. The phone has Cyanogenmod + TWRP on it. Booting into TWRP should bring up an adb interface which should be enough. Can anyone specify the exact sequence to get directly into recovery? Maybe a screen shot of the bootloader screen (or a link to one)?
You should be able to issue the following command and then plug the phone into the pc.
Adb wait-for-device reboot recovery
Sent from my XT1095 using Tapatalk
Red_81 said:
You should be able to issue the following command and then plug the phone into the pc.
Adb wait-for-device reboot recovery
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Unfortunately I can't get any adb commands to the device in the first place. The phone would need to boot up properly to do so, or at least get into TWRP, which apparently brings up adb automatically. I assume my options are either to (a) get the phone into TWRP with the volume+power button or to (b) get the phone to boot up properly.
For option (a) I'm just not sure what the button combinations are because I only did it a few times before the phone died.
For option (b) I'm assuming I'd have to replace the screen and input (digitizer) to make it boot properly.
Actually, I'm taking a wild guess, that if I were to physically remove the screen and digitizer it might boot. This is with the assumption that the device is getting some bad signals from the input device (digitizer), but really I have no idea what is going on. The phone initially would boot up just fine after the LCD cracked, but the input would not work. I had the phone off for a day after that, and when I went to turn it back on, the LCD was completely non-functioning. Now the phone just goes into a bootloop when I try to power it up.
Since you said it's in a boot loop, just holding down Volume down while it loops should be enough. Then you can either connect the phone to your PC and send the command 'fastboot reboot recovery', or you can press Volume down once, then Volume up once to boot into TWRP.
Or issue the command I gave you with the phone powered off and the device unplugged. After you issued the command, plug in the phone. It will interrupt the boot process as soon as it sees the device. It's worth the 3 minutes to give it a try.
Sent from my XT1095 using Tapatalk
Alexsp32 said:
Since you said it's in a boot loop, just holding down Volume down while it loops should be enough. Then you can either connect the phone to your PC and send the command 'fastboot reboot recovery', or you can press Volume down once, then Volume up once to boot into TWRP.
Click to expand...
Click to collapse
Thanks, that seems to have worked! (The volume key method)
Red_81 said:
Or issue the command I gave you with the phone powered off and the device unplugged. After you issued the command, plug in the phone. It will interrupt the boot process as soon as it sees the device. It's worth the 3 minutes to give it a try.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I tried it, but it wasn't working Thanks for the idea!
Related
Hello all,
I have a friends sprint hero cdma that was rooted with z4root. He was flashing a mod that changed the text from green to orange and the phone froze. He waited quite a while then decided to hard reset. When he put the battery back in and rebooted the phone and the phone would not boot past white HTC bootlogo. The phone will not boot into recovery and the PC will recognize the phone, but the system will not mount so the ruu will not detect the phone either. HTC sync does not detect the phone being connected either. I am using a program called USBDeview and it shows the driver is there and says it is connected but none of the programs detect its connection. Any ideas?
Thanks in advance. Again this is not my phone and I am not familiar with rooting procedures with this phone, but I see a great learning experience in front of me and love these challenges.
this should be in QnA.
Hold power + vol down. will get you into HBOOT. if you flashed the eng-spl that unlocks fastboot you can erase and flash new. Tutorials are somewhere in this forum.
Sorry for the wrong forum. The phone will not hboot or boot into recovery
If it gets that far, you should be able to run the RUU. It'll restore everything to stock ;-)
Sent from my Epic using XDA App
The phone does not connect all the way for some reason. The RUU does not see device and neither does ADB. In device manger, when the device is connected it is assigned a drive letter and I can right click and go to properties and details and the description says android phone. I am out of ideas. Even when the device is connected and assigned a drive letter I can open file explorer and click on the device and the directory is blank. The SD card does not even show up, but if I take sd and put it in an adapter the sd card is still in tact with everything on it.
Sounds like a driver went haywire try searching the dev section for my thread on how to install adb. I know you have it already but try the diffrent drivers. I would post a link but I'm mobile. Hope it helps
Something.About.Me.U.Dont.Like
Its.Cool.I.Understand.
.AWAH.
Power off
hold vol up and power on
should be in fast boot mode
plug in your USB cable
should now be in fast boot usb mode
run RUU from the computer
RUU should recognise the phone and start installing
I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.
What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.
nordy420 said:
I will try this when I get home. So what would cause the phone to act like this? I have read quite a few threads in my quest to fix this phone and a ton of ppl claim bout the only way to brick the hero is by flashing a GSM vs of a. Zip instead of the cdma version. Is this true? I ask because the phone almost acts like it has been locked out somehow.
Click to expand...
Click to collapse
Yes this is basically true. But if you get the HTC screen, chances are that it is not bricked. I have to ask, did you flash anything like a radio for GSM? If not, then you might need to just let it sit there for an exstended period of time and see if it boots. When I do certain things to my phone, it might take up to 15 minutes to get by the HTC logo screen.
nordy420 said:
What happens when you boot into fastboot mode? I held the buttons but the hero still hangs at the white HTC screen.
Click to expand...
Click to collapse
I wish I could take a screen shot and show you but the phone is not recognised at that point except by the RUU when it is waiting for bootloader. Bootloader is another name for fastboot.
It would be a white screen with green letters and it will say fastboot near the top under the green letters. At the bottom of the screen there will be 3 android characters on skate boards.
This is what you should see. Try again
Important: Make sure the USB is not conected at this time
Power off
Hold volume up, then press the red key (power on)
Fastboot screen comes up
At this point plug in the USB. It will change from Fastboot to Fastboot USB
Run RUU .5 or .6 from the computer
It will get to a point where the install says waiting for bootloader
from there it should start installing
If you can't get to the bootloader screen (fastboot) then I am not sure how to help you
Let me know if it works for you.
Edit: If you are not using ENG SPL or have S-Off read this post. You will need a working knowledge of how to use ADB.
http://forum.xda-developers.com/showthread.php?t=958968
Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.
Thank you for the help by the way. I am not the owner of the phone, I am just more patient than the owner and have nothing to lose if it is screwed lol. http://androidforums.com/sprint-hero-all-things-root/259735-bricked.html. Here is his desperate cry for help after it happened. I own a Droid x and have no idea what he was actually trying to do, but maybe after you read what he did then maybe we can come up with a fix. I agree with you supporters that the phone is not bricked but it is sure being stubborn. Please let me know what ya think. Thanks.
unCoRrUpTeD said:
Usually you are still able to get into fastboot, especially if you see the htc screen. Unless you (not really you) destroy the recovery and/or the misc partitions.Did you do this exactly (some people don't do it exactly) pull the battery, reinsert the battery, holding volume up and while holding volume up press the power (end call) button.
If you did then while the phone is stuck on the HTC screen do ......
Open up a command window. Either cd into your windows-sdk/tools folder or just type in the commands if you have the tools folder set as a global environment.
Code:
adb devices
Does it show you a device is connected? If it does you should be able to flash a new recovery image or at least a system.img to get it back up and running.
Click to expand...
Click to collapse
I will try this when I get home. I did do a battery pull but I did not leave it out very long, but the screen never changed for me, just stayed white with HTC logo in the middle.
Be very sure to disconnect the USB. That was the step I was missing and I could not get it to boot to recovery when it was stuck at the logo. Once the USB was disconnected, took the battery out, put it back in, and held down the home button while pushing the power. That worked! Woot!
Lynne
No luck. The phone will not boot into anything to where a PC will recognize it.
nordy420 said:
No luck. The phone will not boot into anything to where a PC will recognize it.
Click to expand...
Click to collapse
Have you downloaded android commander and gave that a shot? androidcommander.com
android commander recognises the phone when it is at the logo screen. it will see all but the sdcard.
within android commander menu, there is a reboot to bootloader command
Ill try it, and report back
So I messed with android commander a little and could not get it to detect the device. I really think that it is a driver issue. I cannot get the HTC driver to install for the phone. A different driver has been installed for the device and windows will not let me manually install one. I can use the install legacy and the HTC driver is there but it will not correlate with the phone when connected.
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 (WILL ALSO WORK FOR 4.2, just use the correct file that I link to) on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Thank you =) will try
-Google
I hope people actually watch and learn from this tutorial instead of waiting around for some point and click tool powered by unicorn blood and hamsters. It's an excellent tutorial and gets you in touch with your device by using the exact tools Google provided you to use for this exact thing.. Use them, they are invaluable.
This means we can't use the old method of putting update.zip file in the root folder and let the system upgrades by itself.
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
Click to expand...
Click to collapse
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
I've been plugged in to both a charger and the PC. Come on, if I've fired off adb recovery reboot, doesn't that automatically suggest that I'm connected to the computer? I press Power+Volume Up and it does NOT instantly go to the screen it should, but brings up a Google logo and sits there forever.
styckx said:
Insert your USB cable and make sure it's plugged into a charger or PC.. Recovery won't appear unless you are plugged in. It's an odd bug fixed when you update
Click to expand...
Click to collapse
Doesn't work in either case, it just hangs until the hard reboot kicks in.
DirkBelig said:
Terrific video but for one problem: My N7 doesn't seem to want to go into Recovery.
Using adb reboot recovery gets me into the red triangle screen, but pressing Power+VolUp just gets the Google logo and pressing all three buttons just restarts it. Something is screwy and I've wasted about three hours on messing with it. I never get the screen shown at 3:41.
If I cold start it by pressing Power+VolUp+VolDn, it brings up a screen with an Android on its back with the body open and a big green Start pointing to the Power button and arrows next to the volume buttons. In the lower left in white computer type is:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - not defined yet
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - xxxxxxxxxxx
SIGNING - not defined yet
LOCK STATE - LOCKED
Pressing up or down twice brings up Recovery and pressing Power switches to a Google logo and that's the end of the show.
I followed your "How to install the Android SDK, ADB and Fastboot on your PC" video without a hitch (thank you for that one, too) and I have USB debugging turned on (as proven by adb reboot recovery working), so what the heck is going wrong with getting it past the red triangle screen?
EDIT: I'm bone stock, no root.
Click to expand...
Click to collapse
Omega360 said:
I have the same exact same problem, except my bootloader is unlocked. Tried everything I could think of, and it still doesn't go into android recovery.
Click to expand...
Click to collapse
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
ShannonMS81 said:
I had the exact same issues. Turns out, I had to hold my volume button directly in the middle while holding power.
Click to expand...
Click to collapse
THIS WORKED!!!!!!
OMFG!!! I burned the time I was going to watch the making of Prometheus Blu-ray trying to get this stupid thing to work! Where were you hours ago, man?!?!? Thank you!!! Better late than never.
Glad you got it.. BTW.. I did-misread what you said and yes, you would have had a USB cable in. All these posts are running together of people asking for help and having issues. Mah poor brain is getting em all mixed together.
Nexus 7 needs a coffee maker attachment!
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
Great video! I might just be using this in the near future. I plan on waiting for the factory image (I just like having a full install on my devices when possible) instead of using just the zip file (that is if I dont get the update). Although if the update isnt showing up sometime soon then this is going to work for me just fine.
qbking77 said:
Figured this would cut down on threads and questions. I have made a video showing how to manually update to 4.1.2 on your Nexus 7.
http://www.youtube.com/watch?v=PwlXQoAzrBE
Hope this helps.
Click to expand...
Click to collapse
can't enterthe stock recovery since i instaled CWM. removing it would bring the stock back ?
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
While in stock recovery and in the "apply update from adb" screen, type in the command window "adb devices". It should say:
<your device serial number> sideload
If it does not, check the drivers in device manager. You may need to manually install it. I had to on mine.
Cheers qbking77, worked a treat.
First time I pushed using adb & after following your tut life is good. Thanks again!
Ram1500 said:
for some reason its not working for me. im fully stock, no root, locked bootloader. my pc recognizes N7 adb host and goes into recovery, but when i write the command "adb sideload 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip" it doesnt send it and just shows me the help info for adb. any suggestions why?
Thanks in advance
Click to expand...
Click to collapse
You may be using an older version of adb that does not support the sideload command.
Jwoc12 said:
Same issue, when I "adb device" it will sometimes show as "device" and other times as something else (don't recall but not device). I can get into recover via "adb reboot recovery" and then into "update via adb" but when I "adb sideload.....(see above)" it just runs through the different commands as if "sideload" is not an option? Followed the video to a "T" and nothing.....thinking about rooting and doing it the old fashion way but this is the first android device I've had that I've not seen a reason to root right away...maybe should just wait for the OTA?
Click to expand...
Click to collapse
It should say 8sdgfs3JKSDBFkjk3 device or something like that. If it does not, you need to install the the correct driver.
My computer did not recognize my tablet at first. I went to this thread and installed PDAnet which installed the driver.
http://forum.xda-developers.com/showthread.php?t=1809195
I just unlocked the bootloader of the x890 using fastboot. I am not sure if I made a mistake since now the Warning Bootloader Unlocked screen is the only powerup option.
It no longer boots into the fastboot menu. I have tried the pwr+vol_down key combo but it just keeps restarting. Windows 7 recognizes the device but is not listed as a fastboot device to interact with.
On my old phone I could pull the battery, short of waiting for the battery to die and hoping it charges again. Is there an option to force the phone to SHUTDOWN? I think there was an issue with the power down, power up normally, restart, etc. that I tried. I don't think I actually hit power off like I was supposed to.
hopefullyfixed said:
I just unlocked the bootloader of the x890 using fastboot. I am not sure if I made a mistake since now the Warning Bootloader Unlocked screen is the only powerup option.
It no longer boots into the fastboot menu. I have tried the pwr+vol_down key combo but it just keeps restarting. Windows 7 recognizes the device but is not listed as a fastboot device to interact with.
On my old phone I could pull the battery, short of waiting for the battery to die and hoping it charges again. Is there an option to force the phone to SHUTDOWN? I think there was an issue with the power down, power up normally, restart, etc. that I tried. I don't think I actually hit power off like I was supposed to.
Click to expand...
Click to collapse
Do you find the device with 'adb devices'? Cause if so, then you can do: 'adb reboot-bootloader'
No. I can not find the device with adb devices. It lists nothing - same as the fastboot.
dagoban said:
Do you find the device with 'adb devices'? Cause if so, then you can do: 'adb reboot-bootloader'
Click to expand...
Click to collapse
hopefullyfixed said:
No. I can not find the device with adb devices. It lists nothing - same as the fastboot.
Click to expand...
Click to collapse
Your phone probably died by now, do this:
Press Volume down and then attach it to your PC (and do not hit the power button) it should automatically go into the bootloader now.
---------- Post added at 22:42 ---------- Previous post was at 22:41 ----------
If you can't charge your phone anymore, get a factory cable / adapter, then it will boot up using the power from the usb plug
dagoban said:
Your phone probably died by now, do this:
Press Volume down and then attach it to your PC (and do not hit the power button) it should automatically go into the bootloader now.
---------- Post added at 22:42 ---------- Previous post was at 22:41 ----------
If you can't charge your phone anymore, get a factory cable / adapter, then it will boot up using the power from the usb plug
Click to expand...
Click to collapse
So it finally works.
I installed CWM via fastboot, rebooted into CWM and flashed Cynagen mod 11. This gave a Status 7 error which relates to the age of the recovery version.
I switched to the most recent version of TWRP and flashed it with fastboot.
I then installed CM11 and google apps. Phone works great. Thanks.
Here's a longshot as this forum is close to its death, but I was building PA (wanted the old memories) for the Kindle. Fast forward, everything built and it gave me a flashable zip like it should. Upon flashing the zip with TWRP 2.8, I rebooted and now it is just on an infinite loop with the Kindle Fire logo. Not the blue one, but the original one. I am unable to get into anything, not fastboot mode or recovery? Any thoughts or solutions? Thanks!
Edit: I should also mention that the original Kindle Fire logo shows up for a few seconds, then turns off and does it again hence the loop.
When you say you can't get into fastboot or recovery, is that via the device? Have you tried via adb?
Sent from my HTC 10 using XDA Labs
squ89r97 said:
When you say you can't get into fastboot or recovery, is that via the device? Have you tried via adb?
Click to expand...
Click to collapse
ADB is useless at this point - it only works if you're booted into Android or in TWRP and connected to a computer previously authorized for ADB via Android.
OP - did you use a fastboot cable? Also, can you verify the drivers are installed properly? You'll need to disable driver signature enforcement on Windows 8+ before the drivers will successfully install.
Sent from my Amazon Jem using XDA Labs
A hard brick is generally described as a device that won't do anything at all. Since your device is showing the kindle logo on the screen, there may be hope.
Hold the power button until the screen goes blank, than plug in a fastboot cable. If you can boot into fastboot, then you are not bricked. If you can't get it to fully power off, then you may need to disconnect the battery, which I have no clue how to do since I've never taken apart one of these devices.
paulshriner said:
A hard brick is generally described as a device that won't do anything at all. Since your device is showing the kindle logo on the screen, there may be hope.
Hold the power button until the screen goes blank, than plug in a fastboot cable. If you can boot into fastboot, then you are not bricked. If you can't get it to fully power off, then you may need to disconnect the battery, which I have no clue how to do since I've never taken apart one of these devices.
Click to expand...
Click to collapse
If you've got the kindle connected to a computer with working ADB and fastboot, you can also type fastboot -i 0x1949 poweroff to turn it off, if I remember correctly.
Sent from my Amazon Jem using XDA Labs
Hi, so my phone's LCD and glass are broken and there is no display nor is touch working but the phone is on. I don't want to spend any money on it for replacing the LCD. It's on Android 7.0 stock, not rooted and everything stock and Wifi and USB debugging is NOT enabled although there is no lock code on the phone. I need to transfer my data to my pc (and no internal SD files are backed up in my Google account) but when I connect my phone to my PC, it doesn't show any files as i need touch to enable file transfer mode even though it recognized the nexus 6. Now i have 2 questions.
1. How to backup/transfer all my data? (preferably an alternative to the OTG mouse and HDMI solution since i can't find it easily in my country and can't order from amazon/ebay etc to my country).
2. How to reset the phone completely if i want to sell it to someone?
Any help would be highly appreciated on this matter...
yasirrfc said:
Hi, so my phone's LCD and glass are broken and there is no display nor is touch working but the phone is on. I don't want to spend any money on it for replacing the LCD. It's on Android 7.0 stock, not rooted and everything stock and Wifi and USB debugging is NOT enabled although there is no lock code on the phone. I need to transfer my data to my pc (and no internal SD files are backed up in my Google account) but when I connect my phone to my PC, it doesn't show any files as i need touch to enable file transfer mode even though it recognized the nexus 6. Now i have 2 questions.
1. How to backup/transfer all my data? (preferably an alternative to the OTG mouse and HDMI solution since i can't find it easily in my country and can't order from amazon/ebay etc to my country).
2. How to reset the phone completely if i want to sell it to someone?
Any help would be highly appreciated on this matter...
Click to expand...
Click to collapse
Adb pull files from recovery
holeindalip said:
Adb pull files from recovery
Click to expand...
Click to collapse
Hi, thanks for your reply. Can you please explain/guide me a bit on adb pull?
yasirrfc said:
Hi, thanks for your reply. Can you please explain/guide me a bit on adb pull?
Click to expand...
Click to collapse
What files are you needing to get off?
holeindalip said:
What files are you needing to get off?
Click to expand...
Click to collapse
I only need my images and the whatsapp folder. btw i dont have usb debugging enabled and not rooted.
yasirrfc said:
I only need my images and the whatsapp folder. btw i dont have usb debugging enabled and not rooted.
Click to expand...
Click to collapse
Do you have e a custom recovery installed? Bootloader unlocked? Can you see anything onscreen?
holeindalip said:
Do you have e a custom recovery installed? Bootloader unlocked? Can you see anything onscreen?
Click to expand...
Click to collapse
Nope no custom recovery installed. i didn't unlock the bootloader so im guessing its locked. and can't see anything on the screen nor can it recognize touch input as LCD and glass is damaged. is there any way?
yasirrfc said:
Nope no custom recovery installed. i didn't unlock the bootloader so im guessing its locked. and can't see anything on the screen nor can it recognize touch input as LCD and glass is damaged. is there any way?
Click to expand...
Click to collapse
I haven't used adb enough to know whether or not if stock recovery can be used, maybe somebody else can chime in
I hate to say it but your getting them by replacing the screen. Without root or adb debugging you won't even have access to the directory or be able to issue the device any commands.
zelendel said:
I hate to say it but your getting them by replacing the screen. Without root or adb debugging you won't even have access to the directory or be able to issue the device any commands.
Click to expand...
Click to collapse
Can i reset my phone in this condition? If i end up selling it, i want to wipe all the data in it so is that possible in this condition?
yasirrfc said:
Can i reset my phone in this condition? If i end up selling it, i want to wipe all the data in it so is that possible in this condition?
Click to expand...
Click to collapse
Maybe if you have it connected to the device the Android device manager. I disable it myself so can't say for sure. Other then that. No you are not gonna be able to. I really would just replace the screen. Not only will you learn something but you will be able to get all your stuff as well as the sale value will be higher.
bump
zelendel said:
Maybe if you have it connected to the device the Android device manager. I disable it myself so can't say for sure. Other then that. No you are not gonna be able to. I really would just replace the screen. Not only will you learn something but you will be able to get all your stuff as well as the sale value will be higher.
Click to expand...
Click to collapse
is wiping through fastboot an option? like if i enter download mode and wipe through a fastboot command.. don't know the exact steps though..
yasirrfc said:
is wiping through fastboot an option? like if i enter download mode and wipe through a fastboot command.. don't know the exact steps though..
Click to expand...
Click to collapse
If you are wanting to just wipe and sell then yes it is an option
holeindalip said:
If you are wanting to just wipe and sell then yes it is an option
Click to expand...
Click to collapse
ok so i've downloaded a fastboot compilation and i need to use fastbook device to check if nexus 6 is in fastboot mode and fastboot -w to wipe. I tried turning my phone off but i think it doesnt turn off until you press the power off button on the screen, even if you hold the power button longer. so ill let my phone fully discharge so it turns off and then charge it a bit while its off and then try to turn it on in fastboot mode by pressing volume down and power and then enter the commands. seems right?
yasirrfc said:
ok so i've downloaded a fastboot compilation and i need to use fastbook device to check if nexus 6 is in fastboot mode and fastboot -w to wipe. I tried turning my phone off but i think it doesnt turn off until you press the power off button on the screen, even if you hold the power button longer. so ill let my phone fully discharge so it turns off and then charge it a bit while its off and then try to turn it on in fastboot mode by pressing volume down and power and then enter the commands. seems right?
Click to expand...
Click to collapse
Yup, if you plug the phone into PC before booting into fastboot, hold vol- then hit power button,while in your fastboot directory on PC, hold shift and right click mouse button, then click open command prompt from here. Then type: fastboot devices this will then tell you on PC if phone is connected and ready to receive commands. If it returns your phones serial number then proceed with the commands
If you hold power button to reboot phone, as soon as phone vibrates hold the vol- key and it should put you into fastboot mode
holeindalip said:
Yup, if you plug the phone into PC before booting into fastboot, hold vol- then hit power button,while in your fastboot directory on PC, hold shift and right click mouse button, then click open command prompt from here. Then type: fastboot devices this will then tell you on PC if phone is connected and ready to receive commands. If it returns your phones serial number then proceed with the commands
If you hold power button to reboot phone, as soon as phone vibrates hold the vol- key and it should put you into fastboot mode
Click to expand...
Click to collapse
can't seem to boot in fastboot mode. My PC recognizes nexus 6 when its connected in normal mode so i know when its normally on. So i tried holding the power down button for 10 seconds or so and then tried holding the volume down button for several seconds and then connected it to PC but fastboot didn't recognize it neither my PC in general but after a while nexus 6 showed up on my PC which probably meant it rebooted normally without going into fastboot mode. any tips?
yasirrfc said:
can't seem to boot in fastboot mode. My PC recognizes nexus 6 when its connected in normal mode so i know when its normally on. So i tried holding the power down button for 10 seconds or so and then tried holding the volume down button for several seconds and then connected it to PC but fastboot didn't recognize it neither my PC in general but after a while nexus 6 showed up on my PC which probably meant it rebooted normally without going into fastboot mode. any tips?
Click to expand...
Click to collapse
Probably need to install drivers
holeindalip said:
Probably need to install drivers
Click to expand...
Click to collapse
tried installing the drivers twice. no luck...
holeindalip said:
Probably need to install drivers
Click to expand...
Click to collapse
it finally worked but after wiping it said erase successful, but not automatically formatting. cant determine partition type and then it said failed twice. dont know if it wiped it or not so ill leave my phone in fastboot mode for a while. any clues? should i flash a stock image on it or something?