Related
Hi all,
Hope someone can help, I have a desire HD that has some issues.
Long story short the phone was acting up and was flashed with a non official ROM. It was working originally but after about a week it started acting up, with apps force closing, phone crashing altogether etc.
I am trying to get the phone back to a state that Vodafone in Australia will be able to warranty the phone in.
The current situation is that when the phone turns on, it'll load straight to the bootloader/hboot. Recovery mode does not work - it dumps you in to fastboot menu and fails to load.
System restore from boot menu does not work either, and there is no rom at all so USB debugging is a no go, and there appears to be no way to flash the ROM.
Any ideas? Any help would be greatly appreciated.
Thanks
Sent from my GT-P7100 using XDA App
Use adb / fastboot to push a new recovery to the phone (I hope you left USB debugging enabled).
Sent from my Ericsson T39m
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Sent from my GT-P7100 using XDA App
CrystalCastle said:
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Sent from my GT-P7100 using XDA App
Click to expand...
Click to collapse
ooh i tested it in my DHD and don´t works...how can be possible that don´t works adb parameters, but fastboot commander works perfectly??
maybe we have anything that works badly in our PC´s.. i´m in it...
ei crystal!! has you tested with FASTBOOT COMMANDER? if you download it you can flash a new recovery from this tool... its intuitive...
you only must to download the tool
download the recovery (lastest CWM in the DHD android development forum)
put the file in the paragraph that says "RECOVERY:not file set" and then push FLASH IT"".maybe you enjoy...
remember to put your device into boot loader
CrystalCastle said:
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Click to expand...
Click to collapse
How did you check to see if adb shell can see the device?
Run an pb98.img from the bootlaoder
Sent from my Motorola Startac running Atari 2600 software!
Mr_JMM said:
How did you check to see if adb shell can see the device?
Click to expand...
Click to collapse
adb get-state
result:
unknown
Code:
adb devices
But this does depend on you having previously ticked USB Debugging option before you had all these problems (no way to check now without being able to boot the phone).
If this fails you may have to try the previous suggestion of putting a PD98IMG on your sdcard then going into fastboot on the phone.
Mr_JMM said:
But this does depend on you having previously ticked USB Debugging option before you had all these problems (no way to check now without being able to boot the phone).
If this fails you may have to try the previous suggestion of putting a PD98IMG on your sdcard then going into fastboot on the phone.
Click to expand...
Click to collapse
Currently there is no Rom on the Phone. Just put PD98IMG.zip on the SD card which seems to be updating. Does it normally take a while to Update all the Sections?
Can take anything from 5 to 20+ minutes.
Seems to be taking ages to even get past [1]. Is that normal? Hasn't done anything. It says "Updating" yet I'm still yet to see it get past "[1] BOOTLOADER"
Just to confirm...
1. Turn phone off
2. Put PD98IMG file onto ROOT of sd card
3. Use vol- and power button to get to Fastboot
4. Scroll and select Bootloader (HBOOT)
(might automatically do last step when you boot phone)
Phone will show a message to say it is looking for the file then unpack it and install.
Mr_JMM said:
Just to confirm...
1. Turn phone off
2. Put PD98IMG file onto ROOT of sd card
3. Use vol- and power button to get to Fastboot
4. Scroll and select Bootloader (HBOOT)
(might automatically do last step when you boot phone)
Phone will show a message to say it is looking for the file then unpack it and install.
Click to expand...
Click to collapse
Confirmed dude. Doesn't seem to be doing much though. It has been stuck on "updating BOOTLOADER". It has trying to update it for more then 30mins now
It has a big list of 12 things it wants to update however it hasn't moved past the first file "BOOTLOADER" in over 30mins.
Did you confirm the MD5HASH of the file before putting it on the card?
Could you put a link to where you got the file from please?
http://forum.xda-developers.com/showthread.php?t=905003
Thank you.
Are you still connected to the PC? If so disconnect and try again.
Did you confirm the MD5HASH?
Have you got another SD card you can try? If not, reformat the current one and put the PD98IMG file on it again and try again.
The Device fails to even turn on now dude. Thanks anyway man
!!!???!!!
Damn. Do you just get the orange flashing light when you try to turn the phone on?
Take out SD Card and try.
If nothing works the bright side is you can send it to HTC and say "I woke up, turned it on and it's dead". Chances are they'll never be able to tell how it happened.
Many people did this when the Clockwork recovery bug bricked loads of phones.
Sorry but stay positive. Always a sliver lining.
Thank you
thanks for your great guidance to get back to recovery. I followed your tips and made it.
thanks a lot once again.
SERGI.3210 said:
ooh i tested it in my DHD and don´t works...how can be possible that don´t works adb parameters, but fastboot commander works perfectly??
maybe we have anything that works badly in our PC´s.. i´m in it...
ei crystal!! has you tested with FASTBOOT COMMANDER? if you download it you can flash a new recovery from this tool... its intuitive...
you only must to download the tool
download the recovery (lastest CWM in the DHD android development forum)
put the file in the paragraph that says "RECOVERY:not file set" and then push FLASH IT"".maybe you enjoy...
remember to put your device into boot loader
Click to expand...
Click to collapse
Hi to all
I have a big problem. My HTC Desire HD is now "dead". So, everything is working normally, just fine, on JellyTime, but this afternoon everything get broken. Suddenly, after the boot animation is finished, nothing happens, the screen is "black". The phone works, because when I connect USB to the computer sound. I can not get into Recovery (Home + Volume Down), can not do anything. I tried to remove the battery, but it does not help. I tried with adb, but there is "error: device not found". So I installed the drivers, asking me activate USB Debugging on the phone, and I can not access the phone.
Do you have any idea how to access recovery mode and install the new ROM?
Please help!
Thanks in advance.
just turn on your device with press volume down + power to get into the bootloader..then from there you can select recovery
JJeamy said:
just turn on your device with press volume down + power to get into the bootloader..then from there you can select recovery
Click to expand...
Click to collapse
I try, but I can't. :crying:
SkipperRi said:
I try, but I can't. :crying:
Click to expand...
Click to collapse
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
JJeamy said:
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
Click to expand...
Click to collapse
I finally managed this problem. I pulled off the battery over the night, and this morning I can booted into the recovery. So, I installed new ROM, all my apps, and now I performed backup to the my PC.
Thanks for help!
Regards.
Again same problem. For few hours everything seems fine, but just now my HTC has "blank" screen... Nothing to do. Again, I can't go to Recovery, nothing... What's going on with this phone?!?!
JJeamy said:
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
Click to expand...
Click to collapse
How to do this? And, if I do that, will be my phone still rooted after that?
SkipperRi said:
How to do this? And, if I do that, will be my phone still rooted after that?
Click to expand...
Click to collapse
no..you will lost it
what the state of your phone bootloader..?
unlocked or locked or nothing ?
s-on or s-off ?
hboot - ???
n your phone still can't go to bootloader with press volume down + power..?, is that the new rom you've already installed earlier..already by default it had enabled usb debugging under system settings..?
JJeamy said:
no..you will lost it
what the state of your phone bootloader..?
unlocked or locked or nothing ?
s-on or s-off ?
hboot - ???
n your phone still can't go to bootloader with press volume down + power..?, is that the new rom you've already installed earlier..already by default it had enabled usb debugging under system settings..?
Click to expand...
Click to collapse
No, I can't go to bootloader with volume down+power. About state of phone... S-off, that's I know. The ROM is installed earlier, but today I perform full wipe, and then installed ROM again, not backup/recovery, but fresh install. USB debugging is, as far I know, disabled... What should I do?
SkipperRi said:
No, I can't go to bootloader with volume down+power. About state of phone... S-off, that's I know. The ROM is installed earlier, but today I perform full wipe, and then installed ROM again, not backup/recovery, but fresh install. USB debugging is, as far I know, disabled... What should I do?
Click to expand...
Click to collapse
did you already try it adb is connected or not..?, just try first with "adb devices" (while the phone is on booting and had a black screen)
anyway why your phone can't go into bootloader by pressing volume down + power..?, is that already broken with your volume rocker..?
what happen if your pull out the battery first just a few minutes..then put in back again..and try it again pressing volume down+power..
JJeamy said:
did you already try it adb is connected or not..?, just try first with "adb devices" (while the phone is on booting and had a black screen)
anyway why your phone can't go into bootloader by pressing volume down + power..?, is that already broken with your volume rocker..?
what happen if your pull out the battery first just a few minutes..then put in back again..and try it again pressing volume down+power..
Click to expand...
Click to collapse
I don't know why can't go into bootloader with volumeD+power... I pulled battery, but everything is same. Can you please explain to me how can I try with adb?
Thank you so much for help!
SkipperRi said:
I don't know why can't go into bootloader with volumeD+power... I pulled battery, but everything is same. Can you please explain to me how can I try with adb?
Thank you so much for help!
Click to expand...
Click to collapse
i assume that you already had SDK/ADT or adb.exe and fastboot.exe on your PC.. if not just downloading from here..
and already had installing the latest HTC driver on your PC..
firstly your let the phone is boot like normal..then after you see the black screen..try connecting it to your pc..
then open your SDK folder (place of adb and fastboot.exe) then run cmd and source to your adb folder.. example : if your adb folder is in "C:/android tools/" then you must change source to that folder with typing "cd C:\android tools", now you ready to used it..don't closed it..just let it open
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
if your phone is detected..then you had prompt after that is your phone serial number that on list of attached devices
if success connected..then you can typing "adb reboot-bootloader" or "adb reboot recovery" (all command w/o quote)
JJeamy said:
i assume that you already had SDK/ADT or adb.exe and fastboot.exe on your PC..
firstly your let the phone is boot like normal..then after you see the black screen..try connecting it to your pc..
then open your SDK folder (place of adb and fastboot.exe) then run cmd and source to your adb folder.. example : if your adb folder is in "C:/android tools/" then you must change source to that folder with typing "cd C:\android tools", now you ready to used it..don't closed it..just let it open
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
if your phone is detected..then you had prompt after that is your phone serial number that on list of attached devices
if success connected..then you can typing "adb reboot-bootloader" or "adb reboot recovery" (all command w/o quote)
Click to expand...
Click to collapse
Thank you so much! I'll go and try right now and let you know what's going on.
JJeamy said:
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
(all command w/o quote)
Click to expand...
Click to collapse
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
SkipperRi said:
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
Click to expand...
Click to collapse
wel on my windows 8 i also get that blank line whre the serial number from the device should be but in my case its connected 'cause i can push files and to adb commands with it.
try to do adb reboot-bootloader and see if if does that
lexuz said:
wel on my windows 8 i also get that blank line whre the serial number from the device should be but in my case its connected 'cause i can push files and to adb commands with it.
try to do adb reboot-bootloader and see if if does that
Click to expand...
Click to collapse
Hm, I'm also on Windows 8, when I try command: adb reboot recovery then I get error: device not found.
But, when I connect/disconnect phone via USB there is a sound that detect connection...
SkipperRi said:
Hm, I'm also on Windows 8, when I try command: adb reboot recovery then I get error: device not found.
But, when I connect/disconnect phone via USB there is a sound that detect connection...
Click to expand...
Click to collapse
sorry can't help you more its up to the gurus here, try the thread ace think tank here on the forum
SkipperRi said:
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
Click to expand...
Click to collapse
you sure that your pc already had latest HTC driver right and support with your OS..?
if so..maybe that's the usb debugging is not already active on your phone indeed..
because what i know is that just had two option to access your phone again:
1. with your volume down+power to access bootloader of your phone..and you can do it everything from there..
2. with adb command on android home of your phone..
while both option that is doesn't work..i'm sorry..i don't know more how the way to access your bootloader again beside the two way above..
anyway maybe you can try it again like the first way you success go into bootloader with pull out the battery over few hours like before..
and when you've already success flashing new rom again..don't forget firstly to enable it usb debugging from system settings..and connect as charge mode only..
and don't forget to disable fast boot mode too from system settings if you using sense rom
lexuz said:
sorry can't help you more its up to the gurus here, try the thread ace think tank here on the forum
Click to expand...
Click to collapse
Thank you anyway...
JJeamy said:
you sure that your pc already had latest HTC driver right and support with your OS..?
if so..maybe that's the usb debugging is not already active on your phone indeed..
because what i know is that just had two option to access your phone again:
1. with your volume down+power to access bootloader of your phone..and you can do it everything from there..
2. with adb command on android home of your phone..
while both option that is doesn't work..i'm sorry..i don't know more how the way to access your bootloader again beside the two way above..
anyway maybe you can try it again like the first way you success go into bootloader with pull out the battery over few hours like before..
and when you've already success flashing new rom again..don't forget firstly to enable it usb debugging from system settings..and connect as charge mode only..
and don't forget to disable fast boot mode too from system settings if you using sense rom
Click to expand...
Click to collapse
Yes, I have valid drivers, because before this disaster it was possible to connect phone with PC without any problems.
Have you any idea why the phone go "dead" after few hours working just perfect? Hardware or ROM related issue, what do you think?
I pulled battery out just now, for tommorow morning I giving up, maybe I'll be lucky and again I can with volume down + power booting into Recovery Mode.
Thank you, my friend!
P.S. Do you have any suggestion for some stable and good ROM?
SkipperRi said:
Thank you anyway...
Yes, I have valid drivers, because before this disaster it was possible to connect phone with PC without any problems.
Have you any idea why the phone go "dead" after few hours working just perfect? Hardware or ROM related issue, what do you think?
I pulled battery out just now, for tommorow morning I giving up, maybe I'll be lucky and again I can with volume down + power booting into Recovery Mode.
Thank you, my friend!
P.S. Do you have any suggestion for some stable and good ROM?
Click to expand...
Click to collapse
i'm not sure about that..until now..what i see is still software related..but i don't know what software exactly had the problem is..
can be from the recovery that you had installed the rom..or else..
to make sure what exactly is.. you must return the phone to the stock..stock bootloader, stock rom and stock recovery too..all back to the stock..with flashing stock RUU while your phone back in normal condition..
you know the forum rule is doesn't give any permission to all member for compare the rom..
Hello all,
My unlocked (for a long time) Nexus 7 stopped responding so I turned it off and on and now it won't go beyond the google screen.I have tried connect it to my computer but windows doesn't see it as a device (usually does) so I can't run any adb commands.
I pressed power + volume down until the menu appears but nothing I select helps. I have left it for hours after selecting 'recovery mode' from that menu and still no joy. I have left the battery completely empty then changed it up again and it still won't get beyond that Google screen.
Does anyone please know anything else I can try?
standardman said:
Hello all,
My unlocked (for a long time) Nexus 7 stopped responding so I turned it off and on and now it won't go beyond the google screen.I have tried connect it to my computer but windows doesn't see it as a device (usually does) so I can't run any adb commands.
I pressed power + volume down until the menu appears but nothing I select helps. I have left it for hours after selecting 'recovery mode' from that menu and still no joy. I have left the battery completely empty then changed it up again and it still won't get beyond that Google screen.
Does anyone please know anything else I can try?
Click to expand...
Click to collapse
Does your computer recognize your N7 when it's booted into the bootloader (aka fastboot mode)?
charesa39 said:
Does your computer recognize your N7 when it's booted into the bootloader (aka fastboot mode)?
Click to expand...
Click to collapse
That's the menu with the start/recovery/power off options isn't it? It doesn't detect it at that point either, I'm afraid.
standardman said:
That's the menu with the start/recovery/power off options isn't it? It doesn't detect it at that point either, I'm afraid.
Click to expand...
Click to collapse
Well, if you've already unlocked it in the past, you should still have the drivers on your computer. You need to select the correct drivers, and it should detect it. Once you've done that, you can confirm this by using the "fastboot devices" cmd to make sure your device shows up in fastboot mode.
charesa39 said:
Well, if you've already unlocked it in the past, you should still have the drivers on your computer. You need to select the correct drivers, and it should detect it. Once you've done that, you can confirm this by using the "fastboot devices" cmd to make sure your device shows up in fastboot mode.
Click to expand...
Click to collapse
Thanks for the reply.
Sorry I'm not exactly sure how to do that. Will they just be files on my PC, what should they be called?
If it helps, I used the nexus root toolkit to root mine.
standardman said:
Thanks for the reply.
Sorry I'm not exactly sure how to do that. Will they just be files on my PC, what should they be called?
If it helps, I used the nexus root toolkit to root mine.
Click to expand...
Click to collapse
Give this a try: http://forum.xda-developers.com/showthread.php?t=2588979. Once you have the correct drivers installed, it should detect it in fastboot mode.
charesa39 said:
Give this a try: http://forum.xda-developers.com/showthread.php?t=2588979. Once you have the correct drivers installed, it should detect it in fastboot mode.
Click to expand...
Click to collapse
Thanks again!
Ok, so it didn't detect so I rebooted the device a few times while connected to USB and it appeared, did some windows instally drivers stuff then the DEVICE booted. Unfortunately the touchscreen wasn't working (happens fairly often) so I rebooted and now it won't get beyond the google screen again and windows isn't detecting it again.
So close!
standardman said:
Thanks again!
Ok, so it didn't detect so I rebooted the device a few times while connected to USB and it appeared, did some windows instally drivers stuff then the DEVICE booted. Unfortunately the touchscreen wasn't working (happens fairly often) so I rebooted and now it won't get beyond the google screen again and windows isn't detecting it again.
So close!
Click to expand...
Click to collapse
Well, if it detected it, then you should have the correct drivers. Boot into the bootloader by holding Power + Volume Down. Plug in your device. Open a command window in the folder where your adb/fastboot was installed. The easiest way to do that is to navigate to that folder (default location should be something like C:/android-sdk/platform-tools) and hold SHIFT on your keyboard and right click. The drop down menu should have an option to open a command window in that location. Type "fastboot devices" (obviously, without the quotation marks), and you should see the serial number for you device pop up. That's when you know you can then use fastboot commands successfully.
charesa39 said:
Well, if it detected it, then you should have the correct drivers. Boot into the bootloader by holding Power + Volume Down. Plug in your device. Open a command window in the folder where your adb/fastboot was installed. The easiest way to do that is to navigate to that folder (default location should be something like C:/android-sdk/platform-tools) and hold SHIFT on your keyboard and right click. The drop down menu should have an option to open a command window in that location. Type "fastboot devices" (obviously, without the quotation marks), and you should see the serial number for you device pop up. That's when you know you can then use fastboot commands successfully.
Click to expand...
Click to collapse
Great, that worked, it output my serial number. Now we know we can use those commands, what's next please?
standardman said:
Great, that worked, it output my serial number. Now we know we can use those commands, what's next please?
Click to expand...
Click to collapse
Good. The easiest thing to do to try to recover without wiping your data would be to format the cache. Sometimes, your issue can be caused by a corrupted cache partition. So type "fastboot erase cache" and hit enter. Let it do it's thing. Then, type "fastboot format cache" and hit enter. Let it do it's thing again. Then, on your Nexus 7, select "reboot" and see if it boots into the Android OS.
charesa39 said:
Good. The easiest thing to do to try to recover without wiping your data would be to format the cache. Sometimes, your issue can be caused by a corrupted cache partition. So type "fastboot erase cache" and hit enter. Let it do it's thing. Then, type "fastboot format cache" and hit enter. Let it do it's thing again. Then, on your Nexus 7, select "reboot" and see if it boots into the Android OS.
Click to expand...
Click to collapse
Hooray! This is looking waay more positive! I can nowe boot my device but still have that touchscreen issue (I tend to do this stuff until it sort itself out).
Thank you so much for all your help. Just in case I can't get the damn touchscreen working. How would I use command line to factory reset this thing please?
standardman said:
Hooray! This is looking waay more positive! I can nowe boot my device but still have that touchscreen issue (I tend to do this stuff until it sort itself out).
Thank you so much for all your help. Just in case I can't get the damn touchscreen working. How would I use command line to factory reset this thing please?
Click to expand...
Click to collapse
Great! Well, except for those touch issues... To flash the factory image, check out the OP in this thread over in the Nexus 5 forums: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Although it's for the N5, the procedure is pretty much exactly the same for the N7 (2013) (and Nexus 10 for that matter). Just make sure you have the correct factory image for your device. Basically, after you download the factory image, you have to extract the folder inside the zip. Then, open the command window there, and type "flash-all.bat" (assuming you're using a Windows PC). IMPORTANT: After everything is done running, boot back into the bootloader and boot into recovery. Select "wipe data/factory data reset." After that's done, just reboot and you're good to go.
charesa39 said:
Great! Well, except for those touch issues... To flash the factory image, check out the OP in this thread over in the Nexus 5 forums: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Although it's for the N5, the procedure is pretty much exactly the same for the N7 (2013) (and Nexus 10 for that matter). Just make sure you have the correct factory image for your device. Basically, after you download the factory image, you have to extract the folder inside the zip. Then, open the command window there, and type "flash-all.bat" (assuming you're using a Windows PC). IMPORTANT: After everything is done running, boot back into the bootloader and boot into recovery. Select "wipe data/factory data reset." After that's done, just reboot and you're good to go.
Click to expand...
Click to collapse
Thank you once. Honestly, I feel like I found a saint on the internet :highfive:
standardman said:
Thank you once. Honestly, I feel like I found a saint on the internet :highfive:
Click to expand...
Click to collapse
Haha! I don't know about all that. Just glad I could help. :highfive: Hope it all works our for you. :good:
I have a 2013 Nexus 7 wifi tablet, bootloader locked, with USB debugging disabled. It decided mid-activity that all it would like to do in life is display the "Google" image on the boot up screen.
I can access the bootloader so I tried doing the standard wipe in recovery mode but that did not work.
Investigated Wugfresh's Nexus Root Toolkit. Drivers (Windows 7) are installed but under Step 4 of the Full Driver Configuration guide it is unable to find the device as an ADB device, even though the device does show up on my Device Manager (but only as bootloader interface, not ADB). Tried to use the unlock feature anyway but on the tablet it just gets stuck on the "unlock bootloader" screen after trying to run the unlock tool (choosing "yes" by pressing the up volume button to scroll to the yes option, followed by the power button to select it).
My questions based on this are simple:
1) Can I unlock this device without having USB debugging enabled? If so, how?
2) Can I restore to factory stock settings without having USB debugging enabled (and not using recovery mode on the device itself, as that does not work)? If so, how?
All of the tools I have seen thus far require that USB debugging be enabled on the device. Since I can't actually boot up the device, there is no way to make this happen. I don't really care about any of the data on the device, I just want it to function again to avoid buying a new one.
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
nhizzat said:
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
Click to expand...
Click to collapse
I believe this also requires that USB Debugging be enabled. I would paste links but the forum prevents me from doing so since I just signed up.
If I am incorrect in thinking that USB Debugging must be enabled for this to work, then please let me know. All I really need is clear instructions on how to hard reset the device without USB debugging enabled. Unlocking just seems to be a prerequisite for that in most of the tutorials I have found so far.
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
skrypj said:
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
Click to expand...
Click to collapse
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Bugnerd said:
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Click to expand...
Click to collapse
Couple of things:
1. You may also have a driver issue, I was playing with this the other day on both my Nexus 5 and Nexus 7. My nexus 5 worked fine, but later that day when i tried my nexus 7 I had troubles with my PC recognizing the N7 in fastboot mode. It would be fine in ADB and would reboot, but then the computer would freak out when it saw the fastboot device. Sometimes it would kinda work, sometimes the N7 would freeze on the bootloader screen or fail to flash during the process. It even locked my PC at one point. I completely uninstalled(per the Step 1 instructions in Wug's) all Android associated drivers(Samsung, LG, Asus, whatever. Kill them all) on the PC and reinstalled and it solved the issues. It sounds like maybe your PC is failing to flash properly like mine was.
2. Not sure if you tried this yet but; go to Options Menu>Flash Stock Tab>Check "Enable 'Force Flash Mode' . . . " Then try to flash stock + unroot again with the soft-bricked option selected. This basically makes Wug's ignore the check process at the beginning of the flash. I had to do this for both my N5 and N7.
Keep in mind, you will lose EVERYTHING on your N7 if you unroot and flash, including your internal storage.
Yeah, it does not seem to want to do the unroot + flash even with the override of checks. It seems unlocking is really a prerequisite for that tool (according to the text that appears as it proceeds), and unlocking appears to require the USB debugging. If it really can be unlocked without that, then it is not cooperating and just getting stuck on the unlocking screen. I expect it is now a very expensive paperweight.
All of this nonsense just over a year since I bought it, of course.
Try it with another computer, another USB cable...
I'm in the same boat, can't get it to unlock so it's essentially dead now
I've tried original and a G3 usb cord and nothing, front and rear USB ports, just will not unlock, almost to the point of sending it on and paying to get it fixed if possible , will try another computer first
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Az-one786 said:
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Click to expand...
Click to collapse
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
skrypj said:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Click to expand...
Click to collapse
I looked into this a week or so ago and I think I determined that it would also require the USB debugging to be on (at least from the tutorials). Do you have any recommendations of tutorials on this process? Screwing around with this stuff is not really my bag.
Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
Click to expand...
Click to collapse
Ok.., Your have no choice by now, you'll need to find a working driver for your PC to get recognize your tablet when on fastboot mode..
I've got this issues before when I want to update my tab using toolkit...
My PC can recognized my tab as adb devices, but when it's reboot to check fastboot status it fail to detect my device is on fastboot mode..
But maybe I'm so lucky that day, Moboginie notification has pop-up and it's has searching and found the driver and fix it itself ...
Then i try again and this time it's has no problem at all till now... I still can access my storage using Moboginie but until now window explorer still fail to recognized my N7...
It's so weird isn't it ...
Try Moborobo
Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
Click to expand...
Click to collapse
After the recovery screen with "sick" Andy, did it automatically begin to reboot? If not, you know that it's very tricky with the power+vol up button (sometimes I think it's power+both volume buttons that works) to access that screen in recovery (the one past sick Andy). Sometimes I've tried five or six times. I have twrp so I can't check it out right now.
As far as adb/fastboot drivers set up to run any commands, I thought they were required. I'm not certain about USB debugging. It seems you've tried with your device in fastboot and running Cmd (fastboot oem unlock) from your fast boot directory. Do you get a device code when you enter [fastboot devices] while in that directory? If not, your N7 will not accept fastboot commands.
Sent from my Nexus 7 using Tapatalk
hey everyone! new to the forum. needed help bad.
i have been running CM 10.2.0 for awhile now, pretty much since it was released without any issues. yesterday for whatever reason while surfing the net my phone restarted. now it keeps restarting every 15-20 secs. my main concern at this point is saving my photos before i reset my phone and start from scratch. any ideas as to how to back up photos?
some notes on my rebooting condition.:
phone keeps rebooting even when booted up in safe mode.
-in safe mode i do have more time before it reboots itself
phone does not reboot itself when in bootloader mode or recovery mode
i tried to back up to sdcard while in recovery mode but it fails when it tries to back up data. i also tried using nexus root toolkit but to no avail.
any help would be much appreciated. feels weird to not have a phone.lol. thanks in advance
lilzed_747 said:
hey everyone! new to the forum. needed help bad.
i have been running CM 10.2.0 for awhile now, pretty much since it was released without any issues. yesterday for whatever reason while surfing the net my phone restarted. now it keeps restarting every 15-20 secs. my main concern at this point is saving my photos before i reset my phone and start from scratch. any ideas as to how to back up photos?
some notes on my rebooting condition.:
phone keeps rebooting even when booted up in safe mode.
-in safe mode i do have more time before it reboots itself
phone does not reboot itself when in bootloader mode or recovery mode
i tried to back up to sdcard while in recovery mode but it fails when it tries to back up data. i also tried using nexus root toolkit but to no avail.
any help would be much appreciated. feels weird to not have a phone.lol. thanks in advance
Click to expand...
Click to collapse
Hate when a rom just goes bad for some reason.. Could you supply the error messages you get when your backup fails? I'm guessing it might have to do with file names having weird symbols. Also you might want to backup different folders of your sdcard at a time to avoid failure; i.e., "adb pull /sdcard/Download <some_directory_on_computer>".
7175 said:
Hate when a rom just goes bad for some reason.. Could you supply the error messages you get when your backup fails? I'm guessing it might have to do with file names having weird symbols. Also you might want to backup different folders of your sdcard at a time to avoid failure; i.e., "adb pull /sdcard/Download <some_directory_on_computer>".
Click to expand...
Click to collapse
thanks for the reply. system backup finishes then it goes to back up data. after while it says that there's an error making backup image of /data
is it possible to just to use command prompt to just pull my pictures? would it just be adb pull /sdcard/dcim <some directory>?
also for some reason i am unable to communicate with my phone using adb prompts. yesterday i typed in adb devices and my phones serial number would come up as connected. today under "list of devices" its just blank....not sure what to do.
UPDATE: i was able to get my pictures off of my phone. i launched CMD through the nexus toolkit and it seemed to detect my phone.
i flashed my phone back to stock using the toolkit. for some reason after everything was said and done my phone wasnt actually set back to stock. my phone still has all my apps etc. it still restarts every few seconds.
i tried a couple force flashes using the toolkit again but still same phone. nothing has changed or been fixed. not really sure what my next plan of attack should be. any guidance is very much appreciated.
lilzed_747 said:
UPDATE: i was able to get my pictures off of my phone. i launched CMD through the nexus toolkit and it seemed to detect my phone.
i flashed my phone back to stock using the toolkit. for some reason after everything was said and done my phone wasnt actually set back to stock. my phone still has all my apps etc. it still restarts every few seconds.
i tried a couple force flashes using the toolkit again but still same phone. nothing has changed or been fixed. not really sure what my next plan of attack should be. any guidance is very much appreciated.
Click to expand...
Click to collapse
Glad to hear you got your pictures off. As far as wiping your phone. If you got everything off your sdcard that you want, you can do a fastboot wipe.
-press volume up + volume down + power to get to fastboot mode
-connect the phone to your computer and enter in the command window "fastboot devices" to see if it's connected
-enter "fastboot -w" to do a full erasure of the phone's /data partition
Then use nexus toolkit, recovery, or fastboot to flash a new rom from there. This has saved me in the past in a similar situation. Definitely make sure you have everything off your sdcard you want to keep before trying this though.
7175 said:
Glad to hear you got your pictures off. As far as wiping your phone. If you got everything off your sdcard that you want, you can do a fastboot wipe.
-press volume up + volume down + power to get to fastboot mode
-connect the phone to your computer and enter in the command window "fastboot devices" to see if it's connected
-enter "fastboot -w" to do a full erasure of the phone's /data partition
Then use nexus toolkit, recovery, or fastboot to flash a new rom from there. This has saved me in the past in a similar situation. Definitely make sure you have everything off your sdcard you want to keep before trying this though.
Click to expand...
Click to collapse
thanks so much for the help so far. unfortunately everything you have told me so far has not worked.lol. i followed the steps like u said but the phone just stays on the "google" screen after i install a stock rom. left for 2.5 hours in hopes of it doing its thing.lol. had to pull battery and start it up. nothing changed, phone still restarts i also tried using toolkit to flash stock + unroot (both in bricked mode and normal mode), flashed zip stock images and installing in recovery mode. i also used CMD to push stock images to my phone and installing but still nothing.
i also followed the instructions extactly on this forum http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1
all of the steps successfully completed but after a reboot my phone was left unchanged.
i may have screwed up my description of the problem earlier. the phone restarts after my phone stop responding/freezes. i also find that there almost always is a program that stops working. i find handcent sms is having the most errors. tried to uninstall but phone freezes. tried in fastboot/adb but nothing happens.
thanks again for the help so far.