Develop Bugs

[Q] DHD crashed and won't go pass the Bootscreen/ can't navigate it either

Hallo,
just now I was trying to open an app on my DHD but it kept force closing so I decided to Normaly restart it. When I did that it went to the Welcome Logo then got stuck and kept on turning on and Off.
Then I removed the battery and tried again. This time the Bootscreen appeared (I was glad since I could recover a backup version of the RAM) but to my amazement I couldn't navigate through the options. Even the power button didn't work. I tried several times but with the same results.
I was wondering is there a way to restore my mobile from my laptop (USB Debugging?) now after I reached this state?!
How could I solve this?
Any help would be appreciated
UPDATE: I noticed before the Bootscreen loads, there appears some messages quickly before they disappear. I kept on turning my phone on and off to see what they said eventually I came out with this
P98DIAG.ZIP
Image not found
.
.
P98DIAG.NBH
Image not found
.
.
ring any bell?

Reda88 said:
Hallo,
just now I was trying to open an app on my DHD but it kept force closing so I decided to Normaly restart it. When I did that it went to the Welcome Logo then got stuck and kept on turning on and Off.
Then I removed the battery and tried again. This time the Bootscreen appeared (I was glad since I could recover a backup version of the RAM) but to my amazement I couldn't navigate through the options. Even the power button didn't work. I tried several times but with the same results.
I was wondering is there a way to restore my mobile from my laptop (USB Debugging?) now after I reached this state?!
How could I solve this?
Any help would be appreciated
UPDATE: I noticed before the Bootscreen loads, there appears some messages quickly before they disappear. I kept on turning my phone on and off to see what they said eventually I came out with this
P98DIAG.ZIP
Image not found
.
.
P98DIAG.NBH
Image not found
.
.
ring any bell?
Click to expand...
Click to collapse
Can you navigate any menus? If you can't you probably have a volume key hardware issue. If you can, i would just put a p98diag.zip on the root and reflash (use the rooted one).

Sounds like you are booting into bootloader. You need recovery. Pull the battery, then reinsert and hold volume down + hit power. If that doesn't work if you have adb set up on computer, plug it in to computer and use adb reboot recovery.
Sent from my Inspire 4G using XDA

I guess that you have a PD98IMG.zip on sd card.
Remove it or everytime you reboot in bootloader it will ask you to update in a never ending story. Probably this is why all other commands are not working except reboot.
Then reboot bootloader and go to recovery.

No I can't navigate (the weird thing is the power button also dosen't respond) it's like it freezes as soon as it turns on... Could you give me the PD98IMG.zip in a separate link?
I tried reinst the battery while holding the volume + but it didn't work. It vibrated 4 times while the charge light turned green but that was it. It stayed green and the screen was off...
I've always had the volume keys issue even before it went crazy (they do not always respond to my press) but I just installed 3rd party apps as a workaround.
I couldn't find the p98diag.zip anywhere on the SD card (could you give me the path for it?)
I will try to reboot it through my laptop but could someone give me the commands I should write? I'm not that experienced in that field.
Btw I left it for a while before I turned it on again, it went into Safe Mode (no apps no nothing) then I turned it off and after several tries it finally turned on in the normal mode and was almost stable until I restarted it and it went to point 0 again and now I'm stuck with the bootscreen :S
Thanks for your help

Do you have adb set up on your computer? If so then connect phone to laptop. Open command prompt type "adb remount" then "adb reboot recovery"
Sent from my Desire HD using XDA

while looking through the files I used to root my phone when I bought it I found the p98diag.zip. I copied it to my SD Card and wanted to install it. It found it but then it said
Parsing...[SD ZIP]
[1] BOOTLOADER
[2] BOOT
....
but it's been like that for 2 hours now. I tried reinst the battery and pluging in the mobile to my laptop but it didn't recognize it. (I tried the adb and it gave me Device not found" error!
Is it normal for the phone to take long to parse the zip file? what should I do now?

Reda88 said:
while looking through the files I used to root my phone when I bought it I found the p98diag.zip. I copied it to my SD Card and wanted to install it. It found it but then it said
Parsing...[SD ZIP]
[1] BOOTLOADER
[2] BOOT
....
but it's been like that for 2 hours now. I tried reinst the battery and pluging in the mobile to my laptop but it didn't recognize it. (I tried the adb and it gave me Device not found" error!
Is it normal for the phone to take long to parse the zip file? what should I do now?
Click to expand...
Click to collapse
You shouldn't have installed pd98diag. I would suggest either trying to run the ruu to get back to stock, or find the stock rom in pd98img.zip form and place on root of sdcard. Then reroot and start over.
Edit: if you find the stock rooted in pd98img.zip form that should work too and you won't have to reroot.
Edit 2: be sure to remove the pd98diag.zip from your sd card.
Sent from my Desire HD using XDA

bcd420 said:
You shouldn't have installed pd98diag. I would suggest either trying to run the ruu to get back to stock, or find the stock rom in pd98img.zip form and place on root of sdcard. Then reroot and start over.
Edit: if you find the stock rooted in pd98img.zip form that should work too and you won't have to reroot.
Edit 2: be sure to remove the pd98diag.zip from your sd card.
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
Good advice! I still have all the files I used to root (even the RUU)
And you're right I shouldn't have flashed the old pd98img because now my laptop can't recognize my mobile and I can't debug it from the command line (it says Device not found)
Can I still be able to root the img without using my phone? I used this guide to root my phone (http://www.addictivetips.com/mobile/how-to-downgrade-htc-desire-hd-to-root-it-after-ota-update/)
Where can I find the rooted img? and will it be possible for me to upload it here so that someone could root it for me on his device and give it to me rooted?

To boot into recovery
Hold down volume - button (not +) while pressing power button.
Let go of power button but continue pressing down on volume -.
Hey presto ... recovery.
It's a very easy mistake to make, I did it myself a few times when I first got into rooting and flashing ROM's.

lol!
no mate I wish it was like that.

Found this in the inspire section may be helpful. http://forum.xda-developers.com/showthread.php?t=986014
Sent from my Desire HD using XDA

[SOLVED] Think I bricked...

I started off slow, I had my OUYA fully updated, I used the OneClick Recovery, went fine. Then I threw the "RootMyOUYA" apk on it, all went fine. I decided to put Xposed Framework on it, fine, Mod Collection, fine.
I did a Factory Reset just to get a clean slate, I loaded the OUYA back up and logged into my account. I went back into recovery, wiped Cache & Dalvik, flashed StockPlus. It was SUPER delayed and laggy trying to navigate menus. I tried doing a Factory Reset but it did nothing. I went back into recovery and did a data/factory reset, cache, dalvik wipe and now...
I get the OUYA splash screen, background, and then black screen. Nothing. How do I fix this?
If it helps at all, its still recognized under ADB.
EDIT:
HOW TO RECOVER:
This is a hack, an unintended sequence of events that results in recovery mode; what you need to do is crash the startup using sysrq.
For this you'll need a usb keyboard with the sysrq key, this is usually the printscreen button if your keyboard isn't labeled. As the OUYA starts to boot, hold down the alt-sysrq keys and press i, wait a few seconds and then repeat. This key combination is kill-all-tasks; thanks to whoever left this enabled in the kernel. Each time you kill the tasks the init process will restart them, after about 5 or 6 times init will print a warning on the console that one of the processes marked critical has been restarted too many times -- this then triggers an automatic reboot into recovery mode.
Unfortunately it's not always obvious when the ouya is in recovery mode. You might get screen with the ouya logo and a large red exclamation mark, or the screen might be entirely black; usually I got a black screen. Press the home button on the keyboard to bring up the recovery menu; it's actually a toggle so feel free to press the home button repeatedly until you see the menu since the timing isn't otherwise obvious.
Once you get to the recovery menu, the select the second option to update from adb. Download the OTA update from the link at the end of this post, and run the command "adb sideload RC-OUYA-1.0.193-r1_ota.zip" this will reformat the system partition and reinstall the ouya software. You might also want to do a factory reset before rebooting.
Links to download the OTA updates can be found on this xda thread: http://forum.xda-developers.com/showthread.php?t=2266629
Click to expand...
Click to collapse

Now no longer recognized under ADB... Any ideas?

If you are able to connect via ADB during boot you can ADB reboot recovery then flash a rom. If you can not connect via adb try to get to recovery manually. All you have to do is plug in a PC keyboard via USB and restart the ouya. Now press the keys alt + i + sysrq for 4-6 seconds then let go for about half a second and repeat the key press for some time.
It might take you some attempts but eventually recovery should show up.
If you wonder sysrq is print on most keyboards. Now you should be able to adb and flash ROMs.
Gesendet von meinem One X+ mit Tapatalk 4

nchantmnt said:
If you are able to connect via ADB during boot you can ADB reboot recovery then flash a rom. If you can not connect via adb try to get to recovery manually. All you have to do is plug in a PC keyboard via USB and restart the ouya. Now press the keys alt + i + sysrq for 4-6 seconds then let go for about half a second and repeat the key press for some time.
It might take you some attempts but eventually recovery should show up.
If you wonder sysrq is print on most keyboards. Now you should be able to adb and flash ROMs.
Gesendet von meinem One X+ mit Tapatalk 4
Click to expand...
Click to collapse
Yeah I wound up figuring it out. My derpderp-self forgot to put USB Debugging back on after I got everything set up. All is good now! :good:

Samsung Galaxy Tab 3 7 Kids T2105 T-2105 can't access recovery mode

I have three (3) Samsung Galaxy Tab Kids T2105 tablets. All are running the latest firmware, T2105UEAOE1.
None of them will boot into recovery. The tabs work, they will boot normally, and then will boot into Download mode. But they will not boot into recovery.
* If I hold down Power+VolUp+Home, or Power+VolUp, continuously, the Tab turns on, and then, about 5 seconds later, turns back off.
* If I hold down Power+VolUp+Home, or Power+VolUp, and release them when the Samsung Logo appears, the device boots normally.
* If I hold down Power+VolUp+Home, or Power+VolUp, and release Power when the Samsung Logo appears, and then continue to hold VolUp and/or Home, the device sits on the Samsung Logo for 20 seconds, then the screen goes blank for a second, then the logo comes back on and sits for 20 seconds, then the screen goes blank... and this cycle repeats until I release the buttons, at which point the device boots normally.
I have done factory resets (through the normal mode settings menus). I have reflashed the latest firmware with Odin3. Nothing seems to fix this problem.
I've been searching the net for hours for this. I see a number of other people who have reported this problem. But nobody has offered a solution. One person stated that he uses "adb reboot recovery" - which is a fine, if ugly, hack - but the fact remains that, for many people, apparently, Stock Android Recovery is not accessible from the Samsung Galaxy Tab Kids T2105.
Does anyone know of an actual solution for this, to restore recovery functionality to this tablet?

Hello,
I have the same tablet, same problem (no stock recovery). None of the button combinations work, and the logo just keeps repeating. My situations is that my 9 yr old daughter locked herself out and can't remember her lock screen password. It's a totally stock tablet (never been rooted or flashed). Because I can't get into the tablet, I'm not sure what firmware version it has, and it does not have USB debugging enabled.
I tried booting into the stock recovery to do a factory reset (since we can't do it in the Settings). I tried flashing the same firmware you mentioned using Odin. It goes through the motions successfully and reboots. But it boots back to the lock screen and its still "locked" (we still see her personal wall paper) - which tells me the flash is not taking. Even though my Odin set up is fine, it does not work (even though everything passed with green lights). I tried going into Safe Mode to try bypassing the lock screen, but even in Safe Mode it still asks for the password. My thinking was to go into Settings and initiate a new password or do a factory reset.
(BTW - the Safe Mode button combination was different for me. Holding Power + Volume Up did not work. Instead I had to hold Power + Volume Up & Down until the logo showed up. Once the logo disapeared, then I had to let go of the Power button only - but continue holding the Volume Up & Down until it fully booted into Safe Mode).
I tried ADB in order to use a password reset/erase command line. But because the USB debugging is not enabled, ADB doesn't see the tablet. There is no other way to enable it via Odin or ADB. And I can't even sideload any Lock Screen Hack apps becuase the table is not rooted, or not USB debugging enabled, or can't get into recovery to flash an .apk or image.
So I am stuck. Why would Samsung block recovery mode??? I have been trying for more than 8 hours. If anyone can help, me and my 9 yr old daughter will greatly appreciate it. My last attempt will be to try Google Device Manager and see if it can somehow unlocks it. Or try Kies (although everything I have read so far says that these have not worked either).
HELPPPPPPPPPP!!!!!!!
ggee

wfire said:
I have three (3) Samsung Galaxy Tab Kids T2105 tablets. All are running the latest firmware, T2105UEAOE1.
Does anyone know of an actual solution for this, to restore recovery functionality to this tablet?
Click to expand...
Click to collapse
Hello,
I'm not sure which one of these did the trick for me, but I was able to get into recovery mode. I'm not sure if your three tables are rooted or not, but I don't think it matters. Try these two methods:
Method #1:
Technically, I think I just stumbled on to this one after successfully completing Method #2 (below). But it's worth trying it first before moving on to Method #2.
-Hold the Home + Volume Up + Power buttons together at the same time (just like the normal process).
-Now, you will probably need to try this next step a couple of time before you get it right. This is because it happens pretty fast and you need to time it perfectly.
-Notice that when the screen turns on, the actual first thing that happens is that the the screen backlight turns on and glows first. This happens first and a split second later the first Samsung logo flashes.
-You need to let go of all three buttons at the same time as soon as you see the backlight turn on, but before the Samsung logo flashes.
This is the sweet spot, and it happens pretty fast. But once you do it at the right time, the tablet will go black again and then the recovey mode will show up. It works for me every time.
Method #2:
I thought somehow the recovey mode portion of the firmware had become corrupter somehow. So I decided to flash a custom recovery using Odin (since at that time I hadn't stumbled onto Method #1 yet). Make sure to use gr8nole's custom recovery version for the SM-T210 and SM-T210R (these are the equivalent wifi versions of our Kids tablet). His versions have fixed some known bugs that CWM/TWRP have with the wifi version of our tablets. Make sure to download and flash the CWM or TWRP .tar file for Odin (I personally have always liked CWM over TWRP).
Here is his link: http://gr8nole.blogspot.com/
Also mentioned here: http://forum.xda-developers.com/showthread.php?t=2437219
-Make sure you have all the correct USB drivers for the tablet installed on your computer.
-Open Odin and load the .tar file that you downloaded from gr8nole into the PDA or AP slot (depending on your Odin version).
-Let Odin check the m5d verification for successful authorization.
-Once Odin is ready, then boot the tablet into Download Mode (Home + Volume Down + Power button)
-Connect the table to a USB cable that is attached to your computer's main USB port.
-Odin should now recognize that the table it connected to a valid COM port.
-Click <Start> button on Odin and it should flash the costum recovey .tar file pretty quickly.
-The tablet will simultaneously flash a progress bar and start to automatically reboot (also pretty quickly).
-Disconnect the tablet from the USB cable now.
If the tablet does not automatically reboot to the new custom recovery screen, then just power off the tablet completely. Wait 30 seconds, and then boot the table to recovery mode use the Method #1 shown above. You should now be able to go into the new custom recovery mode you flashed with Odin (CMW or TWRP). It should all work now.
From this point you can download and install SuperSU to add root (if you want to).
Let me know if this works for you.
ggee

Nexus 5X dead -- need help -- wont boot

Nexus 5X - was working fine all this while till about yesterday evening.. then suddenly when i causally checked, it was in powered off state.
Normal press of the power button did not work. No response. Pressed Power button for 10 seconds -- google logo appeared...... and that's about it -- it powered off again when OS/Android started to load. (no android boot animation).
Tried to boot to fastboot -> was successfull. Phone stays alive in fastboot mode.
Tried to boot into recovery (I had TWRP). Again, shows google logo and then when TWRP screen shows up - phone shuts down.
Dont think its a power button issue - since in fastboot/bootloader mode, the power button and rest of the buttons work as expected & the phone does not reboot.
Battery is fully charged using official charger.
Further, in fastboot mode, i am able to access/push .img files - so that way, i could push full factory image (with no errors, including userdata) & relock the boot-loader & also install the factory recovery.
I can now get into factory recovery -- but nothing much.
One thing i noted was, while in factory recovery, if i try "Apply update from SDCard" option, it says its unable to mount /sdcard (error).
The phone was purchased directly from google & is under warranty.
Have had nexus 4, nexus 5 without any issues in the past.
This nexus 5x --- has been replaced once in the past due to yellow screen issues ...
Any help/fixes will be appreciated...

arjunprabhu said:
Nexus 5X - was working fine all this while till about yesterday evening.. then suddenly when i causally checked, it was in powered off state.
Normal press of the power button did not work. No response. Pressed Power button for 10 seconds -- google logo appeared...... and that's about it -- it powered off again when OS/Android started to load. (no android boot animation).
Tried to boot to fastboot -> was successfull. Phone stays alive in fastboot mode.
Tried to boot into recovery (I had TWRP). Again, shows google logo and then when TWRP screen shows up - phone shuts down.
Dont think its a power button issue - since in fastboot/bootloader mode, the power button and rest of the buttons work as expected & the phone does not reboot.
Battery is fully charged using official charger.
Further, in fastboot mode, i am able to access/push .img files - so that way, i could push full factory image (with no errors, including userdata) & relock the boot-loader & also install the factory recovery.
I can now get into factory recovery -- but nothing much.
One thing i noted was, while in factory recovery, if i try "Apply update from SDCard" option, it says its unable to mount /sdcard (error).
The phone was purchased directly from google & is under warranty.
Have had nexus 4, nexus 5 without any issues in the past.
This nexus 5x --- has been replaced once in the past due to yellow screen issues ...
Any help/fixes will be appreciated...
Click to expand...
Click to collapse
if you press hold power + volume up you go into download mode. there is a thread with all official MM and N roms, so you should be able to install one and hopefully fix your problem. ofc do a clean install
if that does not work, then you might have more luck with lg flash tool to do a factory reset
if nothing works then imo its hardware problem, but since i am not as good at such stuff as most here i refrain to say so

Giorgos Chatziioannou said:
if you press hold power + volume up you go into download mode. there is a thread with all official MM and N roms, so you should be able to install one and hopefully fix your problem. ofc do a clean install
Click to expand...
Click to collapse
can you please point me to the forum links on how to flash using download mode? -- Nevermind : got the links. will try.

Rooted G7 Play: Forgot pattern lock, can't factory reset either

I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.

veryspecialagent said:
I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.
Click to expand...
Click to collapse
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot

sd_shadow said:
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.

veryspecialagent said:
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.
Click to expand...
Click to collapse
Window 10?

Yeah. It should remember this phone, since I used this computer to root it when I first got it a year and a half ago.
I used a different cable and got it to pick up the phone (as an unknown device) in Windows but NOT ADB, and the phone to realize it was connected (see last line on phone screen) but they're not talking.
If I boot it all the way up, either regular or recovery (root), it doesn't show at all on my computer.
Like I said, I'd be fine with wiping it, but can't even get to that option.

Install the moto drivers. If that doesn't work then make sure your using a usb2 port and not a usb3 port as its a known issue with moto phones.

I just ordered a new OEM cable.
Also ordered an OTG cable to see if I can force it to startup into a different mode that'll allow me to do something with it.
I'll update this thread once I'm able to test them out.

I got a new cable. My USB ports are not labeled, and my Moto drivers reinstalled.
After rebooting to the recovery screen, I plugged it in and apparently I have fastboot. I checked the bootloader logs and it says:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Volume down key pressed
USB connected
Windows doesn't pick up anything connected by USB. I can't restart to get root because then adb doesn't pick up the phone either because of the screenlock preventing me from hitting ok to trust my computer.
I'm asking the following because I can't find answers: Can you delete the screen lock file with the only bridge being fastboot, not adb. How can I do a factory reset if rebooting to recovery is our normal way of turnin gon the device with root access? Or would reflashing something work?
command line commands are a perishable skill and it's been a couple years since I did this stuff.
Thanks in advance.

To recap, I either need to be able to get into the directory to delete the pattern lock, or factory reset the phone.
I've tried the pattern lock 79 times, which means I have to wait 300+ seconds between tries. I think an error is causing that though.
Fastboot is my only option at this point as far as using commands goes. Rebooting recovery just reboots it with root permissions, but neither adb or Windows 10 picks it up. Using a brand new factory cord and tried every USB port on my computer, even the USB-C to USB-C. But I can't find anywhere that shows how to get into the directory using fastboot.
In Device Manager, I've been getting an error with Android ADB Interface (The device cannot start; Code 10). I uninstalled, reinstalled various drivers, killed adb.exe, etc., Still happening.
HOWEVER, Motorola ADB Interface is working just fine and goes away when I unplug my phone, returns when I plug it in. Only when it's in recovery/fastboot mode though.
I got into Safe Mode, but computer won't pick it up.
I can't get into Field Test Mode. I did reboot it into something else. I don't know what, but the screen was off and the home button was illuminated. EDL mode? I don't know. Neither my computer or adb read that anything was attached, and i can't figure out how I did it.
I also tried sideloading some pattern lock removers, but apparently you can't do that in fastboot.
Thoughts?

Just to close this out with a solution: I had forgotten that in order to get to the recovery menu, you have to hold the buttons when you reboot recovery. Didn't realize that until I was rooting my Moto e6.
Factory reset complete. No more pattern lock. Though since I've now tried rooting it 4 times with 4 different images and have not succeeded even though I had root before all this, I wish I could have realized the above and possibly gotten in and deleted the gesture.
Lesson learned.

Hold what buttons? I'm afraid I'm in same spot.

onefstfoknv6 said:
Hold what buttons? I'm afraid I'm in same spot.
Click to expand...
Click to collapse
Volume up button and power button

sd_shadow said:
Volume up button and power button
Click to expand...
Click to collapse
Just found this. Timing is everything apparently.
Press and hold the Volume Down and Power buttons simultaneously until the Android Recovery screen appears.
Press the Volume Down button to navigate to Recovery.
With Recovery displayed, press the Power button.
When you see the 'Droid' with 'No Command,' hold Power and tap Volume Up just once and immediately release both buttons.
Scroll to wipe data/factory reset by pressing the Volume Down button
Press the Power button.
Scroll to YES by pressing the Volume Down button.
Press the Power button.
The 'phone will wipe all contents.
Press the Power button.
The 'phone will now reboot to the initial setup screen.