Develop Bugs

[Q] DHD stuck to hboot, without USB debugging on

Hi guys and gals,
I'm new here, and I'm just recovering my confidence after the video they make noobs sit through. I have also searched related threads, and have around 20 tabs open in Firefox right now. Alas, no solutions found yet so I'm finally going to make my own thread. The problem is as follows:
I have used MIUI v4 for a while, but it was becoming very slow, battery inefficient and not letting my call or send texts. Therefore I went on to flash the Revolution HD 6.3.1 ROM, which I used when I first flashed my DHD and used to be very stable. After having succesfully flashing the ROM and booting, I was flooded with errors of .acore processes, rendering my DHD unusable. Fortunately USB debugging was still on by default. I then went on to use AAHK, thinking I could flash everything back to the situation when I first rooted and flashed my phone.
After taking well over an hour of being non-responsive, my PC (Win 7) froze up and I had to restart. Hoping the AAHK had finished, I unplugged my phone only to discover that it wouldn't do anything other than show the white screen with the HTC logo. At this point I was already starting to sweat, but when I couldn't even get into the bootloader I fell down to my knees letting out a big NOOOO.
I then finally managed to properly hold down the vol- and power buttons, and I was soon basking in the cold white light emanating from the hboot screen. Unfortunately, selecting either RECOVERY or FACTORY RESET leads to the same white HTC screen. FASTBOOT however, does work, and after reading some other threads I have acquainted myself with SDK, adb and fastboot. adb doesn't seem to work, and it also doesn't show any devices when using the 'adb devices' command. 'fastboot devices' does show my phone, and I can use some commands.
Here comes the real tricky bit. I am now trying to flash a recovery or a new ROM using just fastboot, without USB debugging being on as far as I know. I have the PD98IMG-GB2.zip file on my SDcard (done by taking the card out of the phone, and using another phone as a card reader), and also in a C:\Android folder, that also has adb.exe, fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll, as per other instructions in various other threads. I have also used these two commands:
"fastboot erase cache" which got an OKAY.
and
"fastboot oem rebootRUU" which also got an OKAY.
I then tried putting the recovery.img, PD98IMG-GB2.zip and recovery.zip files in my C:\Program Files\Android\android-sdk\platform-tools folder. When using the "fastboot flash recovery recovery.img" command, this got me as far as:
sending 'recovery' <3650 KB>...
OKAY [ 0.607s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 0.609
This leads me to believe that because USB debugging isn't enabled, I can't write to the flash.
Then tried this:
"fastboot update PD98IMG-GB2.zip"
(short wait)
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to acces zipdata in *jibberish*
I'm at a loss as to anything else I might try. The HBOOT still works, and the phone is S-OFF, but I can't seem to flash anything to my phone. I'm hoping some of you gurus here might know something else. My deepest thanks in advance.
EDIT: with Fastboot Commander I made a print of my device:
-----------------------------------.
SPL/hboot version: 0.85.0024.
Radio version: 26.03.02.26_m.
Main software version: 1.32.405.6.
cid: 11111111.
cpld: none.
product: ace.
mid: pd9810000.
security: off.
build-mode: ship.
-----------------------------------.
EDIT 2: After a horrible day of thinking my phone was dead, but still trying to revive it, I have managed to find a solution! In this thread: http://forum.xda-developers.com/showthread.php?p=26844128#post26844128 there was the suggestion to rename PD98IMG-GB2.zip to just PD98IMG.zip. As soon as I did this, copied the file to my SDcard through another phone, and booting into the bootloader, I was asked if I wanted to upgrade. Hell yeah! After a short wait, I now have my phone up and running again, in a very stock configuration!

After going through a similar situation I can definately relate and know exactly how you felt lol. The OMFG what did I just do moment is hard to get past. I am glad all is working good now though! Good luck!

Thanks for the info. It pointed me in the right direction and now my phone is back up and running

Glad to have helped!
**Edit** I feel like a idiot lol please ignore this post

Experiencing same problem, but with S-on
Hi, I'm having same problem with my friends' Incredible S. Without usb debugging I can't do anything.
Will it make sense if I put my PD98IMG.zip file into sd-card and perform steps you did? Only difference is S-on.

NoorBall said:
Hi, I'm having same problem with my friends' Incredible S. Without usb debugging I can't do anything.
Will it make sense if I put my PD98IMG.zip file into sd-card and perform steps you did? Only difference is S-on.
Click to expand...
Click to collapse
If your friend has a Incredible S, then this thread won´t help you much. This is for the Inspire 4G devices. PD98000 is the boot Device ID, and it will be different in your case. Try to find help in the Incredible S forums first. :good:

Same issues - different outcome
Hey everyone, I'm not sure if there is anyone here to help, but it's worth a shot!
I'm having the exact same issues Richard has and I tried the same solutions and they worked, until a point.
I have a HTC Desire (Bravo) EU that is rooted, S-OFF but doesn't have an OS on it. Before it was experiencing a bootloop with a RD2 sound, because of the Leedroid ROM on it. I fixed the loop but now it can't boot.
I have another HTC Desire from home, that one is fully functional. To test out the differences. :highfive:
""Here comes the real tricky bit. I am now trying to flash a recovery or a new ROM using just fastboot, without USB debugging being on as far as I know. I have the PD98IMG-GB2.zip file on my SDcard (done by taking the card out of the phone, and using another phone as a card reader), and also in a C:\Android folder, that also has adb.exe, fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll, as per other instructions in various other threads. I have also used these two commands:
"fastboot erase cache" which got an OKAY.
and
"fastboot oem rebootRUU" which also got an OKAY.
I then tried putting the recovery.img, PD98IMG-GB2.zip and recovery.zip files in my C:\Program Files\Android\android-sdk\platform-tools folder. When using the "fastboot flash recovery recovery.img" command, this got me as far as:
sending 'recovery' <3650 KB>...
OKAY [ 0.607s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 0.609""
-RichardPNL
I did the exact same steps, only the 'PD98IMG-GB2.zip' was called PB99IMG.zip and my recovery WORKED.
After that I could finally load up the HBOOT, and guess what, I did something stupid.
In the phone there is a SD card with a few zip files on it (the PB99IMG.zip(older version), recovery.zip and a LeedroidROM.zip). I booted into the HBOOT and I was sooooooo happy that I could finally do something with the phone. But then it said "Do you want to update using zip blahblahblah", and I was like "No, I ain't touching anything". But when I layed the phone on the table, I accidentally pressed the volume up button and it updated
Since then the phone is bricked, no way to get into recovery, hboot, bootloader or the OS. Fastboot and adb don't work since the phone won't be recognized by the PC's I'm using and doesn't boot further.
Fastboot used to work when the HTC was having a bootloop, which gave me a chance.
Now I only need fastboot to work again with the phone, but I have no idea how!!

If u need help let me know.
---------- Post added at 11:23 PM ---------- Previous post was at 11:20 PM ----------
DenJento said:
Hey everyone, I'm not sure if there is anyone here to help, but it's worth a shot!
I'm having the exact same issues Richard has and I tried the same solutions and they worked, until a point.
I have a HTC Desire (Bravo) EU that is rooted, S-OFF but doesn't have an OS on it. Before it was experiencing a bootloop with a RD2 sound, because of the Leedroid ROM on it. I fixed the loop but now it can't boot.
I have another HTC Desire from home, that one is fully functional. To test out the differences. :highfive:
""Here comes the real tricky bit. I am now trying to flash a recovery or a new ROM using just fastboot, without USB debugging being on as far as I know. I have the PD98IMG-GB2.zip file on my SDcard (done by taking the card out of the phone, and using another phone as a card reader), and also in a C:\Android folder, that also has adb.exe, fastboot.exe, AdbWinApi.dll and AdbWinUsbApi.dll, as per other instructions in various other threads. I have also used these two commands:
"fastboot erase cache" which got an OKAY.
and
"fastboot oem rebootRUU" which also got an OKAY.
I then tried putting the recovery.img, PD98IMG-GB2.zip and recovery.zip files in my C:\Program Files\Android\android-sdk\platform-tools folder. When using the "fastboot flash recovery recovery.img" command, this got me as far as:
sending 'recovery' <3650 KB>...
OKAY [ 0.607s]
writing 'recovery'...
FAILED <remote: not allowed>
finished. total time: 0.609""
-RichardPNL
I did the exact same steps, only the 'PD98IMG-GB2.zip' was called PB99IMG.zip and my recovery WORKED.
After that I could finally load up the HBOOT, and guess what, I did something stupid.
In the phone there is a SD card with a few zip files on it (the PB99IMG.zip(older version), recovery.zip and a LeedroidROM.zip). I booted into the HBOOT and I was sooooooo happy that I could finally do something with the phone. But then it said "Do you want to update using zip blahblahblah", and I was like "No, I ain't touching anything". But when I layed the phone on the table, I accidentally pressed the volume up button and it updated
Since then the phone is bricked, no way to get into recovery, hboot, bootloader or the OS. Fastboot and adb don't work since the phone won't be recognized by the PC's I'm using and doesn't boot further.
Fastboot used to work when the HTC was having a bootloop, which gave me a chance.
Now I only need fastboot to work again with the phone, but I have no idea how!!
Click to expand...
Click to collapse
First of all...update SDK on your PC..ALL VERSIONS...this will help PC see phone via platform tools folder. There u can issue fastboot commands

[Q] Galaxy Nexus i9250 Bricked?

Well, I think I have a big problem with my Nexus phone, I will relate you what happened with it this morning:
I was using Winamp app, listening music and suddenly my phone went crazy and it turned off, after that, it was rebooting again by itself (the image do a little shake), i was waiting to put my pass but it kept rebooting once and over, I had to take out the battery to turn it off. Now that I'm trying to ressurect him via fastboot it throws me this message:
sending 'bootloader' (2038 KB)...
OKAY [ 0.228s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.43s
rebooting into bootloader...
FAILED (command write failed (Too many links))
finished. total time: 0.004s
sending 'radio' (12288 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.640s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.641s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
-----------------------------------------------------------------
getvar:version-bootloader FAILED (command write failed (Unknown error))
finished. total time: 0.706s
Press any key exit...
My phone was takju 4.1.1 and then I flashed 4.1.2 Stock factory image from google (takju), I did it this way:
Downloaded SDK Manager and installed these packages:
1.- Android SDK Tools
2.- Android SDK Platform-Tools
2.- Google USB Driver
I downloaded Galaxy Nexus ToolKit and installed drivers for Nexus Takju 4.1.1.
I downloaded Factory Image "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) ----> 4.1.2 (JZO54K).
I extracted factory image and put all files in the same folder as Platform Tools (android-sdk\platform-tools).
I used "fastboot devices" to check if my pc recognizes my phone and then I executed "flash-all".
When I first did it 2 days ago it worked and I had my phone updated to 4.1.2 but today i tried to do the same (Thinking this will fix it) and it shows me the error that I described above, now I don't know if my phone is bricked, neither if I can make anything to ressurect him from this, I need your help, guys! What can I do?
Thanks in advice!

Too many links sometimes means a bad connection. Try a different USB cable and/or port.
Even a PC reboot can sometimes help in my experience.
Sent from my Galaxy Nexus using xda premium

El Daddy said:
Too many links sometimes means a bad connection. Try a different USB cable and/or port.
Even a PC reboot can sometimes help in my experience.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I just tried changing USB port and it didn't work. I don't have any other USB cable.
Still waiting for another suggestion.

Still needing a hand!
With GNex Toolkil i'm trying to:
1.- Push files into my phone to flash a rom via CWM but it doesn't let me. (I can go into Recovery Mode, that's why I wanna put a rom in the sdcard)
2.- Reboot phone to Android OS it worked only once but as soon as first screen appeared to unlock it the phone freezed and kept rebooting once and over.
3.- Flash stock factory image and it keeps throwing me the same error described above.
I let the phone rebooting once and over and sometimes it tries to upgrade something but as soon as it does the phone reboots again.
The image keeps moving weird.
Please, guys, I need your help.

You should not be using toolkits at this point. They are designed only for properly functioning phones.
As far as I know, "too many links" either indicates that there is a problem with the connection, or a problem with the hardware that is beyond end-user repair capability. Your phone needs to be fixed or replaced by Samsung.

Search for an odin rom and give it a shot
here try this for the GSM nexus
http://forum.xda-developers.com/showthread.php?t=1827685&highlight=odin
if odin didn't detect your device then re-check the drivers are installed correctly if they are then your last hope is omap flash http://forum.xda-developers.com/showthread.php?t=1760787

Also try a different USB port and a different computer...
A few of the "too many links" posts point out that at some point they're able to smell something burnt. At that point you are definitely toast

Bricked = Not turning on no matter what you do.
Bricked is a permanent condition with no recovery method.
You are not bricked, so please don't use that word to describe your situation.
I would recommend flashing via a different computer, and don't use the stupid toolkits.
Manually install the drivers and the android sdk, and use that to flash your device.

DynamicRam said:
Search for an odin rom and give it a shot
here try this for the GSM nexus
http://forum.xda-developers.com/showthread.php?t=1827685&highlight=odin
if odin didn't detect your device then re-check the drivers are installed correctly if they are then your last hope is omap flash http://forum.xda-developers.com/showthread.php?t=1760787
Click to expand...
Click to collapse
I'm gonna try that, I'm downloading files.
cmstlist said:
Also try a different USB port and a different computer...
A few of the "too many links" posts point out that at some point they're able to smell something burnt. At that point you are definitely toast
Click to expand...
Click to collapse
I already did it, same with another pc or usb port.
GldRush98 said:
Bricked = Not turning on no matter what you do.
Bricked is a permanent condition with no recovery method.
You are not bricked, so please don't use that word to describe your situation.
I would recommend flashing via a different computer, and don't use the stupid toolkits.
Manually install the drivers and the android sdk, and use that to flash your device.
Click to expand...
Click to collapse
My first try was with no toolkits, I used flash-all file that makes everything without typing any command, I'm gonna try to unistall drivers and android sdk and install them back.

ernesuat that
LOL! Now i think I'm completely lost, I tried Odin (And I know it was an stupid thing) and it stock at NAND Write Start!! Now I can't even get to bootloader/recovery/download mode, I only see a Phone--Warning Icon--Pc on my Nexus screen. I tried flashing OMAP but nothing happened, same Phone--Warning Icon--Pc.
Thanks for your help, I'll be googling 'till i get tired.

Does your phone still have any warranty on it?

OMAP flash?
Beamed from my Grouper.

cmstlist said:
Does your phone still have any warranty on it?
Click to expand...
Click to collapse
No, it doesn't coz I bought it from Amazon and I'm out of US.
Mach3.2 said:
OMAP flash?
Beamed from my Grouper.
Click to expand...
Click to collapse
I tried OMAP flash, pull out battery, execute OMAP and connect the phone, put battery back and it only shows Phone--Warning Icon--Pc, I, I can't turn it into Download/Recovery/Bootloader mode.

I'm not really sure how odin works, maybe you can try it again?

I can feel your frustration but all these methods are tested and 100% working
if you can still get into odin mode try again and make sure to read all the steps and that the drivers are installed correctly if everything fails then i think it could be a hardware problem
so try
-Odin mode
-Omap flash
-USB Jig to get into odin mode
-Does your PC recognize the phone ??

Mach3.2 said:
I'm not really sure how odin works, maybe you can try it again?
Click to expand...
Click to collapse
DynamicRam said:
I can feel your frustration but all these methods are tested and 100% working
if you can still get into odin mode try again and make sure to read all the steps and that the drivers are installed correctly if everything fails then i think it could be a hardware problem
so try
-Odin mode
-Omap flash
-USB Jig to get into odin mode
-Does your PC recognize the phone ??
Click to expand...
Click to collapse
I can't go into Download Mode (Download and Odin are the same mode). I can't boot it into Bootloader Mode, I can't boot it into Recovery Mode. My pc recognizes the phone, I can't boot it into any mode, all I see as I said is Phone--Warning Icon--Pc.
Odin says added since the first time I plugged it, it still say it and port gets yellow (at Odin window), I try flashing .tar file and it stock in: bootloader.img and then NAND Write Start!!

vermillion66 said:
I tried Odin (And I know it was an stupid thing) and it stock at NAND Write Start!!
Click to expand...
Click to collapse
How long did you wait for it to complete?

Cilraaz said:
How long did you wait for it to complete?
Click to expand...
Click to collapse
30 minutes.

DynamicRam said:
Search for an odin rom and give it a shot
here try this for the GSM nexus
http://forum.xda-developers.com/showthread.php?t=1827685&highlight=odin
if odin didn't detect your device then re-check the drivers are installed correctly if they are then your last hope is omap flash http://forum.xda-developers.com/showthread.php?t=1760787
Click to expand...
Click to collapse
As El Daddy and cmslist mentioned, the "too many links" error usually means a connection problem or hardware problem. Using Odin to flash something when there is either something wrong with the connection or something wrong with the hardware, is never a good idea, as it will corrupt your bootloader.
@OP, If your computer still recognizes your device, then Odin will still be able to flash it, but it still needs a "good" connection. What I would at this point is use OMAP_Flash (which will reflash your bootloader), reboot into fastboot mode, then uninstall whatever drivers you have, make sure your device is plugged int a USB port at the back of your PC, and install 1wayjonny's driver pack. Then proceed to flash each of the images.

efrant said:
As El Daddy and cmslist mentioned, the "too many links" error usually means a connection problem or hardware problem. Using Odin to flash something when there is either something wrong with the connection or something wrong with the hardware, is never a good idea, as it will corrupt your bootloader.
@OP, If your computer still recognizes your device, then Odin will still be able to flash it, but it still needs a "good" connection. What I would at this point is use OMAP_Flash (which will reflash your bootloader), reboot into fastboot mode, then uninstall whatever drivers you have, make sure your device is plugged int a USB port at the back of your PC, and install 1wayjonny's driver pack. Then proceed to flash each of the images.
Click to expand...
Click to collapse
Well, this is interesting, I downloaded a PIT file and flashed it via ODIN and now I can boot it into Bootloader Mode and Download Mode, but when I tried to use fastboot it get stock at the first command:
C:\Users\MyPc\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bootloader bootloader-maguro-primelc03.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.219s]
writing 'bootloader'...
And when I disconnect USB cable and restart the phone it is like dead (It doesn't turn on) so I have to use OMAP Flash and then I'm able to turn it on.
I uninstalled drivers as 1wayjonny's drivers pack post says, All the time I have always used USB ports from the back of my pc.

Bootlooping, adb not recognized, softbricked.

Bootlooping, adb not recognized, softbricked.
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
​
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img​ - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help

Not sure what happened with regards to the update freeze, but we're past that point now. Your next attempt failed because the bootloader is locked, and since you now have no way to enable debugging, you may have no choice other than to try to revert to factory.
Before trying it, issue a: 'fastboot devices' command and make sure your device appears if not you may have to fix your drivers, make sure you get the right image for your device.
https://developers.google.com/android/nexus/images
EDIT: Oh crap, you don't have USB debugging enabled. Try the link anyway, fastboot should still work.

I will give it a go
I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?

rohanjoshi said:
I will give it a try. That being said, I'm not sure what the right image is. On the basis that I bought it in late november and have not touched it till now, what image should I be using?
Click to expand...
Click to collapse
Do you have a camera on the front and back? And is WiFi only? If yes, it is a FLO and you want this one.
Do you have a camera on the front and back? And has LTE and WiFi? If yes, it is a DEB and you want this one.
Based on your initial post, it looks like you have a FLO.

I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.

rohanjoshi said:
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
Click to expand...
Click to collapse
If you wanted the latest you'll want the 4.4.2...aka KitKat, that is what it was trying to update you to before this all happened. If you just want to go back to where you were, use the 4.3, but you will get prompted to update again.
Just keep in mind, runing flash-all as-is wipes everything, BUT, you can open the flash-all script in a text editor and remove the -w and it won't wipe userdata.
...also, if I may suggest, strongly, is if/when this works, and your device is backup, I suggest you unlock the bootloader first (since this wipes all data you might as well do it before you put anything on there), then go in and enable debugging. Now you can root, use adb if something happens again, etc.

rohanjoshi said:
I can confirm its a FLO. I've downloaded the two 4.3 images as well as the 4.4.2 image. I'm not sure which one to use and I'm not sure which one is relevant. I purchased the device in November of 2013 and have not touched it until yesterday.
Click to expand...
Click to collapse
hey did u tried doing a factory reset from the stock recovery?

varuntis1993 said:
hey did u tried doing a factory reset from the stock recovery?
Click to expand...
Click to collapse
do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?
If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.

rohanjoshi said:
do you mean to ask if I've gone into the bootloader and tried the 'system recovery' option?
If so, yes, and then i see a dead android with a red triangle, underneath reads, 'no command'.
Click to expand...
Click to collapse
From there, hold power and press the volume up key, you should get a menu.
http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s

SOLVED
mdamaged said:
From there, hold power and press the volume up key, you should get a menu.
http://www.youtube.com/watch?v=VV1ffMCXRg4&t=4m14s
Click to expand...
Click to collapse
I tried to hard reset it and that didn't seem to get me anywhere, i was still left in a bootloop.
I had asked this same question in a couple other forums and one guy indicated that I should try
Code:
fastboot oem unlock
since the device was locked. That seemed to do the trick. I had previously wiped all drivers off the system and re-installed the drivers. From there, I went through the Nexus Root Toolkit and flashed it with Kit-Kat, everything worked fine. It's currently up and running just fine. I will enable USB Debugging tonight as well.
Thank you for you help! I truly appreciate it.
I think a lot of people who have this problem need to run 'fastboot oem unlock' as their devices are most likely locked like mine was and the NRT will not do anything with the device locked.

rohanjoshi said:
I tried to hard reset it and that didn't seem to get me anywhere, i was still left in a bootloop.
I had asked this same question in a couple other forums and one guy indicated that I should try
Code:
fastboot oem unlock
since the device was locked. That seemed to do the trick. I had previously wiped all drivers off the system and re-installed the drivers. From there, I went through the Nexus Root Toolkit and flashed it with Kit-Kat, everything worked fine. It's currently up and running just fine. I will enable USB Debugging tonight as well.
Thank you for you help! I truly appreciate it.
I think a lot of people who have this problem need to run 'fastboot oem unlock' as their devices are most likely locked like mine was and the NRT will not do anything with the device locked.
Click to expand...
Click to collapse
Actually the very first thing NRT tells you to do is to unlock the bootloader, I assumed you had done this and it failed to unlock, I mentioned the issue in post #2.
Anyways, glad it's sorted.

mdamaged said:
Actually the very first thing NRT tells you to do is to unlock the bootloader, I assumed you had done this and it failed to unlock, I mentioned the issue in post #2.
Anyways, glad it's sorted.
Click to expand...
Click to collapse
No, i understood that. I did not have the correct drivers installed and whenever I ran 'fastbook devices' nothing showed up.
I wiped all google drivers and re-installed one of the recommended packages and everything ran smoothly after that.

Device not detected in Windows.

Hey guys,
I am trying to get my device re-stocked for a warranty repair.
So, I am S-ON, Lollipop (ViperRom) and I used this guide to re-stock.
However, when I got to the RUU zip (401 zip ~1.5gb) flash, I was getting the verification error 12. I googled a bit and found that I needed to flash the 401 firmware pack (~50mb), which I did and it seemed to work ( I repeated the flash command, just to make sure). Afterwards, I did a factory reset and rebooted.
Phone rebooted in ViperRom 4.3 still with baseband 1.25.21....and build number 4.16.401.10.
Now, I re-downloaded the 1.5gb ruu zip to try to flash again, but whatever I do, I cannot get the device to get detected in windows. I did say DETECTED, as I do not even get the device-plugged-in windows sound. This happens both when the device is booted, in the os, and in the bootloader. It says Fastboot, instead of Fastboot USB.
When I an booting to recovery, I am getting the stock recovery, not the TWRP and when booting to bootloader it says on the top Software status: Modified and Relocked.
How can I get the device to get detected again?
Again, I want to return the device for a warranty repair, so I need to remove that Modified text.
EDIT: when I am plugging the device in the computer, I am getting the slow charge notification, but nothing else.

Is Windows seeing the phone in Device Manager?

EddyOS said:
Is Windows seeing the phone in Device Manager?
Click to expand...
Click to collapse
nope, there is no change to the device manager when plug/unpluggin the phone. don't get a sound either.
I tried all my usb ports and 3 cables, same.
it's weird, as I did not remove the phone from the usb after doing all the fastboot/adb commands. so nothing change but the stuff on the phone...it just stopped working after finishing the ruu flash..

And it's the same in all USB ports? If so, try a different cable/PC but worst case scenario your USB port is borked

EddyOS said:
And it's the same in all USB ports? If so, try a different cable/PC but worst case scenario your USB port is borked
Click to expand...
Click to collapse
I tried ALL ports, with 3 cables. all the same.
I don't think all my ports are broken all of a sudden, as I said earlier, I did not remove the phone from the usb after running all the fastboot and adb commands needed to flash the ruu and stuff.
So after running those (while, obviously, the device was being detected), I rebooted, and all of a sudden, the device is not being detected.
Also, the Slow charge notifications pops up when I am pluging it it, and it is charging.

OK, you know what...dunno what the hell was wrong, but I just rebooted the pc, and it all seems to be working ....

@EddyOS
right, so, as I said earlier, I am following the guide to re-stock.
I am at the stage where I need to run the fastboot flash zip ruu.zip (which is the file named 0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_R ... 500021.06G_20.68.4196t.01_F_release_417809_signed.zip downloaded ~ 1.5gb).
I am getting this whenever I am trying to run the command:
Code:
fastboot flash zip ruu.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1536838 KB)...
OKAY [ 66.510s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 122.802s
I followed the guide, so I am Relocked, and S-on

b0gd4n said:
I followed the guide, so I am Relocked, and S-on
Click to expand...
Click to collapse
You don't thoroughly follow the guide.
The guide says you need the htc_fastboot.exe but you're using google's fastboot.exe
Check again item 3. Flash the RUU - clearly stated htc_fastboot flash zip ruu.zip

ckpv5 said:
You don't thoroughly follow the guide.
The guide says you need the htc_fastboot.exe but you're using google's fastboot.exe
Check again item 3. Flash the RUU - clearly stated htc_fastboot flash zip ruu.zip
Click to expand...
Click to collapse
Ah, you're right. I just assumed the attached fastboot was just the same one as google's one, just being attached there for people who don't have fastboot.
So, if I would use the htc_fastboot, it would work?

Should do!

ckpv5 said:
You don't thoroughly follow the guide.
The guide says you need the htc_fastboot.exe but you're using google's fastboot.exe
Check again item 3. Flash the RUU - clearly stated htc_fastboot flash zip ruu.zip
Click to expand...
Click to collapse
EddyOS said:
Should do!
Click to expand...
Click to collapse
Thanks guys. Using htc_fastboot worked.

[Solved] Several (related) problems flashing anything but stock

I have a C6506 that is unlocked, have checked via the service code. Not just unlockable but unlocked. Certain.
I've used both older flashtool64 that worked before (0.9.11.0) on a Surface Pro (windows 10) and newer (0.9.19.10) on a desktop (Windows 10 also).
In both cases I can flash 10.7.a.0.222 for C6506. I also can flash 10.3.a.0.423 on the Surface (did not try on others). It boots, it works, no issues.
I can get in fastboot mode on the phone (blue light), but on the surface with the older Flashtools (and associated drivers) I cannot access the phone at all, just waiting for device.
On the newer flash tools with drivers installed (turned off signing verification) I can get into fastboot and do things like a "getvar version", but I cannot do more complex things like get the unlock status, nor can I flash a boot image (in this case from CM 12.1). It says "Command not allowed" in the write phase. Yes, the phone is unlocked, really, at least it says it is, and I did do an unlock code with legitimate Sony provided codes. And previously rooted using it as unlocked.
I've also tried getting root with a pre-rooted 10.7.a.0.222 -- I can get an older version rooted, put recovery on it, I can do the install of the zip and it completes -- then boot loop. This is using Beta-SuperSU-V2.52.zip and zl-lockeddualrecovery2.8.23-release.combined.zip with PRFCreator. (The recovery is also what I used to do the install). Boot loop. Can't get out of it without a new flash despite power off, resets, etc. Can't get back into recovery either at that point.
I do have the phone working with a non-rooted stock Sony 10.7.A.0.222. As mentioned, flashes fine. I just can't seem to get CM running (can't fastboot the boot image), nor can I get root on the stock sony (boot loop).
I've also tried the fastboot program on the current SDK as well as the one in Flashtools without any difference, still can't flash a boot.img from cm12.1.
I feel like I'm missing something fundamental, like maybe some aspect of running Windows 10 that is interfering (I have no older version currently). I'd suspect CM12.1 but it also is failing with the typical root technique for 5.1.1 stock (i.e. root older version first).
While I am not an active developer, this is not my first round of flashing or updating the phone, though it is my first round in a year or more, certainly since Windows 10.
I realize this is a lot like "nothing is working what could be wrong" and not a very specific question, but wondering if anyone has any suggestions as to whether there might be a common cause here.

I do have one more interesting piece of information that I do not understand.
I downloaded Emma and tried to use it to flash stock just to make sure the image I had was good for stock.
Emma says "this phone is locked". So thinking my last flash re-locked it, I went into flash tools and did this:
U:\AndroidSDK\platform-tools>fastboot oem unlock 0xkey-from-sony
...
OKAY [ 2.969s]
finished. total time: 2.969s
After doing so, Emma STILL says it is locked.
Flash tool however allows me to flash it.
Any clue why Emma would say "locked" when I just finished unlocking it?
In service, configuration it says "Yes" to unlocked, not "no/yes" or any other combination, just "yes".

focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.

ham5 said:
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
Click to expand...
Click to collapse
I will try again tomorrow (need the phone tonight and it takes a while to get stock back up and configured).
Concentrating on fastbook and on my more-working desktop (the tablet definitely has some issue, I think driver related).
I installed the newest Flashtools, and also installed the fastboot and s1 drivers from it (I think that's what they are called). I configured Windows to permit them unsigned and they installed without error.
When I try to do CM12.1, what I did was download their distribution zip, and unzip it and pull out the boot.img file. I then put the phone in fastboot mode, and it worked and was recognized (e.g. "fastboot getvar version" responds).
Going by the instructions for CM12.1, I then tried to do "fastboot flash boot c:\pathwhereitwas\boot.img"
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
As to the locked issue -- after trying this the first time, I thought "maybe the phone has been locked again". So I did the #*#*service*#*# and see it says "yes" for unlocked. But just to be safe, I dug out my 2 year old email from Sony and did another unlock. As to why I did it with the "oem unlock" that's how CM12.1 suggests (https://wiki.cyanogenmod.org/w/Install_CM_for_odin). The first time I typed it, it failed, the second time it said "OK". Tried the flash boot again, same "command not allowed error".
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
I wanted to run CM12.1 as I really don't like that stock has not patched stagefright, plus I hate not having root.
Any suggestions what I may be doing wrong, that fastboot commands sometimes work, but I can't flash the boot file?
Am I flashing the RIGHT boot file? Should I be flashing the CM12.1 recovery image they have on their download page instead? (But the instructions are pretty clear).
I should note that the phone does not appear to have a recovery on it -- booting after flashing stock, and toggling all the volume buttons in any combination is just ignored.

I think your really digging way to deep into this...
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
Click to expand...
Click to collapse
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
Click to expand...
Click to collapse
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked

ham5 said:
I think your really digging way to deep into this...
Click to expand...
Click to collapse
I'd welcome a shorter, simpler path.
ham5 said:
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
Click to expand...
Click to collapse
Perhaps it is purely a sony thing. If, with the phone powered off, you plug it in holding the volume up button you end up in fastboot mode; if you plug it in with the volume down you end up in flash mode.
Flashmode is used by Emma and by Flashtools. Fastboot is used by the Fastboot utility. I'm unclear what happens under the cover, but they are not interchangeable.
ham5 said:
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
Click to expand...
Click to collapse
As I said, I do not know what happens under the covers, but in fastboot mode when you do the "flash boot" it first says it transmitted a file (shows bytes sent, etc) then it does a "write" command itself and it is that write command that fails.
And therein lies my issue trying to flash the boot image -- the write command fails, and I cannot figure out why.
Drivers: I've tried the latest flashtool, and installed the drivers from there. They do install (with signing verification off), and they do connect and see the phone. Some commands work, but this one does not. Could it be the drivers? Certainly, but I do not know what to try to fix them.
Emma: I hate to keep coming back to this, but I do not understand why Emma says my phone is locked, when it clearly appears not to be. I've both re-unlocked it, confirmed it is unlocked with the service menu. But that it thinks it is locked, and the "write" command failure, makes me wonder if there is an issue either in the phone or windows or drivers that makes it act that way. incidentally I've also tried all this with antivirus/firewalls off with no effect.
Locked: just to confirm, in the service menu it says "Root Status" and "unlockable" as "yes". Not "Yes/no". That means it is currently unlocked, correct?
To your first point, I may be over-complicating it. I would welcome some suggestion of other simpler steps. I've done the same google, and don't see real solutions other than "try better drivers", but most threads seem to point to the flashtools drivers, and I've tried those, as well as installing Emma which (presumably) either used those or loaded its own.

Incidentally if this is more appropriate to the Q&A forum, and a moderator is handy, I would appreciate it moving. I placed it here because this relates mostly to the Flashtools drivers and the process of using fastboot.

I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..

ham5 said:
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
Click to expand...
Click to collapse
I've never gotten to CM on this phone so that's moot. I'm doing the service menu from the stock phone. And so far as I can tell the bootloader is unlocked.
I went back to a much older version of Flashtools (0.9.11) that dates from about the time I got the phone, but those drivers do not seem to install on Windows 10 at all.
But I'm not clear whether it is a driver problem, since some fastboot commands work fine.

Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.

ham5 said:
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
Click to expand...
Click to collapse
Yes, in fastboot mode I can do the getvar version. It says 0.5.
I had read the wiki; as mentioned that is why I was trying to flash boot.img.
As requested here is a fastboot session log:
Code:
U:\AndroidSDK\platform-tools>fastboot getvar version
version: 0.5
finished. total time: 0.002s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.340s
U:\AndroidSDK\platform-tools>fastboot flashing get_unlock_ability
...
^C
U:\AndroidSDK\platform-tools>fastboot devices -l
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot devices
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.354s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.353s
As you can see some commands work, some do not. Not sure the get_unlock_ability is even supposed to work as it looks like a late comer to fastboot and the phone is old.
Most articles I find posted about "command not allowed" do not seem to get as far as being able to use fastboot at all, but even if it is a driver issue, not sure what I can do about it, these are the latest drivers.

Ok, I've managed to get this to work. I can tell you what I did, but not why, but in case it helped someone else.
The bootloader showed unlocked, but I ran the flashtool option to unlock it again, then WITHOUT REBOOTING I did the fastboot option to flash the boot.img.
It appears that if you reboot (to stock) in between, it does something that at least makes it appear the bootloader is locked (the service menu shows it NOT locked still).
There's another thread here that implies you need to do it multiple times, but I think the issue is not a need to do it more than once, but a need to make sure that (at least a late version stock) does not get a chance to run, as it appears to do something.
I'm now happily on 12.1. Well, sort of happy, I finally noticed it says it doesn't support the 6506 (as opposed to the 6503) so I might not stay long, but at least I worked out what was wrong. Thanks to those who encouraged me to keep looking.