Develop Bugs

[Q] Desire stuck on boot logo

Hi
I brought a rooted desire a month ago and 2 nights ago it restarted its self and now is stuck on the boot logo. Fastboot and Recovery both go to HTC boot screen and hang there too.
I have tried taking the battery out and leaving it.
I have tried removing the SD card and booting it.
Also from what i can tell usb debugging is disabled in the phone settings...
I Wont try and pretend that i know what i'm doing here i rather out of my depth trying to sort this out so please bear with me,
i'm using windows xp (x32)
Thank you for your time and patience
EDIT: I think it has a rooted froyo rom on there also. (version unknown)

Chuck_Neus said:
Hi
I brought a rooted desire a month ago and 2 nights ago it restarted its self and now is stuck on the boot logo. Fastboot and Recovery both go to HTC boot screen and hang there too.
I have tried taking the battery out and leaving it.
I have tried removing the SD card and booting it.
Also from what i can tell usb debugging is disabled in the phone settings...
I Wont try and pretend that i know what i'm doing here i rather out of my depth trying to sort this out so please bear with me,
i'm using windows xp (x32)
Thank you for your time and patience
EDIT: I think it has a rooted froyo rom on there also. (version unknown)
Click to expand...
Click to collapse
Not sure if there is an easier solution..But, have you tried unrooting with a RUU?

i haven't tried, can i unroot without a Goldcard?

Chuck_Neus said:
i haven't tried, can i unroot without a Goldcard?
Click to expand...
Click to collapse
Only if you have an unbranded Desire.
But..you try the following in Recovery..It may be stuck in a loop and yet communicate with the pc..
Get into recovery (with an sdcard inside), and issue the following command from your PC (You must have the sdk installed and must be the Tools folder:
Code:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid>c:\goldcard.txt
start c:\goldcard.txt
A text file opens up with a code. If it does you can make a goldcard now. Use the goldcard tool.
Two options to try solving your problem:
METHOD 1
If goldcard can be created ok, then you may proceed with flashing the RUU. Be careful to use the newest version on shipped-Roms. Older ones can brick your device if it's SLCD. We'll use Method 1 as last resort. Try Method2 first.
Note:
Before you try this out, CREATE A GOLDCARD EVEN IF YOU THINK YOUR DEVICE IS UNBRANDED.
Flashing an RUU always has the potential to softbrick your device. Recovering may be difficult unless you have a goldcard and extensively know some advanced methods to unbrick the device/or willing to research it
METHOD2: FLASHING CLOCKWORKMOD DIRECTLY WITH FASTBOOT (Will work only on rooted ROM. Will need goldcard if branded)
Since your current recovery is corrupted, you can try flashing the Clockworkmod again from Fastboot. In fact, it may be safer to try this option first rather than unrooting.
Download the latest image for Clockworkmod recovery
Rename the ClockworkMod Recovery Image to simply recovery.img.
Boot into the bootloader mode.
Turn the phone off.
Insert goldcard
Press the back button & power at the same, until you are booted into bootloader mode.
Connect the phone to the computer.
On the computer, open the command prompt/terminal & navigate to the Android SDK Tools folder.
Issue the following command:
Code:
fastboot flash recovery recovery.img

Try Method2 and tell me if it worked for you.

method 2 didnt work
Code:
flash recovery recovery.img
sending 'recovery' (4216 KB)... OKAY [ 0.578s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.045s

Chuck_Neus said:
method 2 didnt work
Code:
flash recovery recovery.img
sending 'recovery' (4216 KB)... OKAY [ 0.578s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.045s
Click to expand...
Click to collapse
Your goldcard must be inside the device. Try again with goldcard? Did you get the CID for goldcard creation. Follow Method 1 till creation of goldcard. Dont run the RUU though

Use the goldcard tool to make it simpler.

Tried Following method 1 but all i get is access denied... Could this be down to USB Debugging not being on?

Chuck_Neus said:
Tried Following method 1 but all i get is access denied... Could this be down to USB Debugging not being on?
Click to expand...
Click to collapse
At what point?
Dont run the RUU. Just issue the code I've written:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid>c:\goldcard.txt
start c:\goldcard.txt
Try this from Fastboot and from the stuck recovery screen. What does the textfile display>?

Note that your USB device must get recognized within Windows. After the device is notified as connected in Windows (notification icon and a sound in the PC), To check, type this command and see if it shows a code (the serial of device)"
Code:
adb devices

when i type adb devices it says "list of devices attached" and that's it. Could there be a driver problem or something more sinister?

Chuck_Neus said:
when i type adb devices it says "list of devices attached" and that's it. Could there be a driver problem or something more sinister?
Click to expand...
Click to collapse
Your device is not interacting with adb. You could try the following:
Code:
Fastboot devices
If this one works, it's a problem with only adb. More sinister if that is so. Try to boot into Fastboot, Recovery and Simple Boot (See my thread here, and read the part which tells you how to boot into each), and try the adb devices command in each. If it works in any one, get the CID and proceed with goldcard.
If you cant get the CID, you cant get the goldcard. Two solutions exist-1.Use the correct updated RUU and flash to stock. 2.Use Teppic74's guide to downgrade (Search XDA for it) and then flash a lower RUU for your device.
Note that without a goldcard, only the appropriate RUU will work.

fastboot devices gives
Code:
HT05SPL07600 fastboot

Problem with only adb then. See my post and the other thread..

Thank you for your time and help. I sure hope this works

problem fixed unrooted back to stock.

[Q] Unrooted Device Stuck in Bootloop

Hi guys,
My phone (GSM yakjuzs) was stuck in bootloop ages ago. Still can't find a solution to this. It was running 4.0.2, unrooted. At first the bootloop went all the way through Google splashscreen. After plenty of mucking around, now it couldn't pass through Google logo.
I tried to flash the phone with 4.0.4 to no available. It kept saying 'Sending bootloader: failed (status read: failed)' or 'Sending bootloader: failed (remote: write fail)'.
I'm wondering if actually the device has to be rooted first in order to flash a phone. How could I root it if it's already stuck in bootloop?
PS: I tried flashing using mskip's tool, wug's etc. The pc detected the phone in fastboot mode. I could see the numbers.
Any help is appreciated. Thanks a lot.

If your bootloader is still locked, you won't be able to flash. Keep in mind that to flash the 4.0.4 update manually using fastboot, you need to unlock the bootloader. Doing so will wipe data/factory reset the phone causing you to lose everything in your internal storage.
Command to unlock the bootloader - fastboot oem unlock
follow link below for instructions on flashing a stock image.
http://forum.xda-developers.com/showthread.php?t=1366806
the guide specifies up to ICL53F, you can actually use the commands he states in the guide but replace the file names with those of the stock IMM76I image directly from google. Location of stock google images (yakju) https://developers.google.com/android/nexus/images
I hope this helps you in some way.

I forgot to say I had already unlocked the bootloader. However it's still unrooted if it does matter.
Thanks for posting the link though.

It shouldn't matter if you're unrooted. If you try the commands in one of the links I sent, it should work.

Okay, will try this later and I'll get back to you. Thanks a lot.

Hi racerklm,
I tried your method and it failed.
When I entered the first command, the result was as follows:
Sending bootloader ......... OKAY
writing bootloader ......... Failed (remote: write fail)
I just don't get what this means. Does anyone know what this is about? Any help is really appreciated.

Are you on a GSM or CDMA gnex? Just to clarify things. If you're on a GSM version the below applies to you.
Did you download the Superboot zip from the first thread i linked you? You need to extract both the r4-galaxynexus-gsm-superboot.zip and the IMM76I.zip you downloaded from google.
Look for the following files inside the IMM76I.zip you downloaded from google and transfer them to the same directory as fastboot.
bootloader-maguro-primela03.img
radio-maguro-i9250xxla2.img
image-yakju-imm76i.zip
Once that's done, do the following commands (taken from thread I linked you).
fastboot-windows flash bootloader bootloader-maguro-primela03.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-maguro-i9250xxla2.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-yakju-imm76i.zip
if you're on mac or linux just replace "windows" in the commands with "linux" or "mac"

I'm using a GSM model. I did download the superboot zip and the stock google image.zip and extracted all of their files into the same folder.
I have also already typed the first fastboot command. However those words came up again. The very exact words when I tried to fix the device using mskip's and wug's tool. I also tried using two other Windows PC and one Mac PC to no avail. Haven't tried linux since I don't have one.
Your posts are very informative, I thank you a lot for that. However it just didn't work in my case. I've read plenty of similar threads. Their devices could get back to normal. Mine doesn't. I don't know why. Hence, I really wonder what 'remote: write fail' means.

Sorry that there's nothing I can do to help you solve this problem. Have you tried just running the last command? fastboot-windows -w update image-yakju-imm76i.zip? If somehow you can get that flashed, it should boot up normally.

I tried that just now and this came up:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: xxxxxxxxxxxxxxxxx
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (4148 KB)... OKAY
writing 'boot'... FAILED (status read failed (Too many open files in system))
Long time ago I could get into recovery mode and playing around with the device. I wonder if I accidentally unmount the sd? Now I could no longer get into recovery mode. When I select recovery, it would just go to the Google logo with lock image at the bottom.

hmm try flash clockwork recovery and see if that works?

If it's refusing to flash valid files from fastboot, you may just have a hardware defect. Relock the bootloader and if you can still produce the bootloop symptoms, take it for warranty.

I can boot into CWM but not flash it. Is there anything else I could do before sending it in for warranty/fixing?

most likely then it's a hardware defect. best to take it in for warranty work.

wsoelivan said:
I can boot into CWM but not flash it. Is there anything else I could do before sending it in for warranty/fixing?
Click to expand...
Click to collapse
The first thing I would try is to change USB cables.
Next I would try changing USB ports on your PC. Use the ones at the back, not the front.
If that still doesn't work, and you have CWM installed, you could always flash back to stock while booted in CWM (assuming your PC sees your device when booted in CWM).

Crazy as it sounds, you may also want to check your USB cable.
When I worked as Swype's tester, I flashed perhaps hundreds of ROMs across many different devices. In particular I remember having a similar problem with a particular prereleased device, and swapping the USB cable seemingly fixed the problem on more than one occasion. I studied EE in school, and I never could explain why this was a problem or why this would fix it.
Sent from my Galaxy Nexus using XDA

efrant said:
The first thing I would try is to change USB cables.
Next I would try changing USB ports on your PC. Use the ones at the back, not the front.
If that still doesn't work, and you have CWM installed, you could always flash back to stock while booted in CWM (assuming your PC sees your device when booted in CWM).
Click to expand...
Click to collapse
I have already tried 3 different USB cables and all ports in my PC. But, I'm gonna give it one more try for the last time.
I don't have CWM installed, I could only boot it from mskip's tools.
Chinpokomon said:
Crazy as it sounds, you may also want to check your USB cable.
When I worked as Swype's tester, I flashed perhaps hundreds of ROMs across many different devices. In particular I remember having a similar problem with a particular prereleased device, and swapping the USB cable seemingly fixed the problem on more than one occasion. I studied EE in school, and I never could explain why this was a problem or why this would fix it.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
At first I was using two Blackberry's USB cables and it didn't work. Then I read in the forum suggesting to use the original cable. I became very hopeful and suddenly grabbed the USB cable came with the phone.
However, as I said before, I might probably try this method one more time. I'm gonna install a linux OS first and try again before sending it in.
On the other hand, I've tried another method of flashing using ODIN mode. Not surprised at all, it still didn't work.

Need help updating to JB on HTC One X (HBOOT 0.43) [SOLVED]

Hey all, I dont usually post questions, cause I usually am able to find all my answers, but this time i really hit a stump. not sure if its just cause my case is unique.
I have a HTC__622 (so JB compatible), with HBOOT 0.43 running Android Revolution 9.7.2, and im looking to upgrade to JB. However, despite many guides and tutorials, I can't seem to get past updating my HBOOT. Let me list out what I've done (I was following http://forum.xda-developers.com/showthread.php?t=1660807, following method 2/3, cause i haven't cooked a rom since windows mobile LOL)
1-downloaded "RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.29.708.15_Radio_2.1204.122.17_release_268338_signed" (my original one was 1.29.708.2)
2-extracted rom.zip from the RUU, and copied over boot-signed.img, system.img, recovery-signed.img
3-flashed boot-signed.img, and recovery-signed.img. system.img failed.
4-relocked bootloader
5-this is where i get stuck, the RUU cannot detect my phone in fastboot mode and so I cant run the RUU.exe.
anyone got any ideas as to why i can't run RUU.exe from my comp while my phone is in fastboot mode? thanks in advance!

I have no idea what you are doing. To install an RUU:
fastboot oem lock
Run RUU.
All this extracting and flashing is madness.
When you boot into bootloader, what does it say on the screen?

BenPope said:
I have no idea what you are doing. To install an RUU:
fastboot oem lock
Run RUU.
All this extracting and flashing is madness.
When you boot into bootloader, what does it say on the screen?
Click to expand...
Click to collapse
I can relock but I can't boot back into my rom. im stuck in the bootloader. The RUU only detects my phone from normal phone mode.
The first lines on the screen are relocked, security warning, and then my hboot info.
Sent from my HTC One X using xda premium

I have done it yesterday and opend a thread http://forum.xda-developers.com/showthread.php?t=2048646
Only relock stay in fastboot mode and run ruu with admin rights... Than the setup will so the rest for u
Sent from my HTC One X using xda app-developers app

ngy said:
I can relock but I can't boot back into my rom. im stuck in the bootloader. The RUU only detects my phone from normal phone mode.
Click to expand...
Click to collapse
What error do you get in fastboot mode?

zottel1993 said:
I have done it yesterday and opend a thread http://forum.xda-developers.com/showthread.php?t=2048646
Only relock stay in fastboot mode and run ruu with admin rights... Than the setup will so the rest for u
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks man, i've looked at that thread though, i dont see what i'm missing. how did you run the ruu in fastboot mode?
BenPope said:
What error do you get in fastboot mode?
Click to expand...
Click to collapse
the error i get is the ruu cannot detect the phone through usb (while phone is in fastboot mode). and i cannot run the ruu while phone is in normal mode because i can't boot in normal mode when i lock my bootloader.

Does the phone say fastboot USB when you have it in fastboot/bootloader
Then try fastboot devices first to see if your serial comes up ! If it does you can run the ruu.exe from the pc with admin rights.....
Should do the trick

Ok I would try to do everything from the beginning.
To make it easier and faster you can use the script form that thread:
http://forum.xda-developers.com/showthread.php?t=1924003&highlight=jbfwflasher
Then you don't need to install RUU.
Remember to place in the folder boot.img from the rom which you want to flash later.
Have a good fun

Follow this it might give you an idea where to start and what to do
http://forum.xda-developers.com/showthread.php?t=2018040
say thanks if i helped you

MarcelHofs said:
Does the phone say fastboot USB when you have it in fastboot/bootloader
Then try fastboot devices first to see if your serial comes up ! If it does you can run the ruu.exe from the pc with admin rights.....
Should do the trick
Click to expand...
Click to collapse
i already have, i always fastboot devices first to check to make sure my device is connected. on my phone it does say fastboot usb, and i can run fastboot commands on it. and i've ran RUU.exe with admin rights, but still does not detect the phone and gives me a usb connection error.
mrdelook said:
Ok I would try to do everything from the beginning.
To make it easier and faster you can use the script form that thread:
http://forum.xda-developers.com/showthread.php?t=1924003&highlight=jbfwflasher
Then you don't need to install RUU.
Remember to place in the folder boot.img from the rom which you want to flash later.
Have a good fun
Click to expand...
Click to collapse
au contraire, i also have tried using this tool, but if you look carefully, its meant for hboot versions higher than 0.43, which i have. it just points me to download an RUU.exe for my phone (which I already have)
Onexed said:
Follow this it might give you an idea where to start and what to do
http://forum.xda-developers.com/showthread.php?t=2018040
say thanks if i helped you
Click to expand...
Click to collapse
hmm, so you're saying I just need to flash firmware.zip (for my HTC__622 of course), to get the hboot 1.36? i'll give that a shot and report back.
--update 1--
alright so after trying to just flash the new hboot 1.36 (from firmware.zip), i am met with this:
E:\Utilities\Android\One X\JBFWTOOL20>fastboot flash zip firmware-622.zip
sending 'zip' (12875 KB)...
OKAY [ 1.647s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 3.130s
how did you flash it and make it work?
--update 2--
I must've downloaded the wrong (or renamed the wrong) firmware.zip file, i just redownloaded and bam everything works. thanks a lot onexed, that did help. basically, even if you're on 0.43, just flash the firmware.zip for your phone, and get onto a newer hboot, and all is well. thanks!

Welcome i'm glad it worked out for you enjoy jellybean

[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.

Htc 10 EU version. *Unlocked* *S-ON* bricked?

Hi guys,
So i run into this problem this morning that my phone wont charge at all. Did a reboot and got stuck there somehow.
Some time ago i flashed TWRP recovery and Unlock the bootloader. Everything went ok, but had the red text under HTC logo every time i was booting up.
Now i can access the bootloader by pressing VolUp + VolDn + Power buttons but that's it.
If i try to Boot into Download Mode to use fastboot (as far as i know this way it can be used) it goes back to the boot-loop. Same happens with Boot to Recovery. Also ADB and Fastboot won't show it at all.
Even when i select Power Down it goes into boot-loop.
So far i've tried on a Linux machine without any luck. I'll try on a Windows but i suspect the same result.
Linux can't see it at all on the USB interface (only for a really short period of time when is looping, like half a second. not enough to adb or fastboot)
It got bricked? Just like that? Any way to flash anything on it? Like a recovery or the stock ROM.
Hope you can help me guys. Thanks

Update:
I've just installed on Windows the HTC 10 Drivers and ADB, Fastboot tools.
The device is shown in Device Manager as "My HTC 10" and its listed in "fastboot devices".
The Recovery is still unreachable and if I try to reflash the recovery i get this error message.
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (53680 KB)...
OKAY [ 1.336s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.392s
I have to say that first time i did this it went smooth without errors and i was S-ON the entire time. Do you have any ideas? Please.

I believe you need to use htc_fastboot.exe rather than the stock fastboot.exe. Google is your friend for finding it, then do the exact same command but with htc_fastboot rather than fastboot.
so: htc_fastboot flash recovery twrp....

Same result with that tool.
And for some reason even the "getvar all" through fastboot or htc_fastboot i can't get any info on imei, cid, mid.

iakelclaudiu said:
Same result with that tool.
And for some reason even the "getvar all" through fastboot or htc_fastboot i can't get any info on imei, cid, mid.
Click to expand...
Click to collapse
You need to be in download mode

iakelclaudiu said:
Same result with that tool.
And for some reason even the "getvar all" through fastboot or htc_fastboot i can't get any info on imei, cid, mid.
Click to expand...
Click to collapse
Try fastboot oem reboot-download when in bootloader to see if it'll boot to download using fastboot commands.
Sent from my HTC U11 using XDA Labs

That was the first thing i've tried. I know that in download mode i can run fastboot to flash recovery and so on. But this unit at this point wont let me get into download mode, neither recovery mode. Even by selecting it on the bootloader screen or fastbooting the commands.
I've found a post (gotta search it) that had kind of the same issue, a soft brick unit and somehow he managed to bringing it back to life. By unpacking a RUU rom.zip achive and fastboot flash each partition.
Or i'm stupid enough but by rom.zip file is full of zips (zip1,zip2 and so on) not recovery.zip / boot.zip / radio.zip and so on.
Gotta find that topic to quote it.

iakelclaudiu said:
That was the first thing i've tried. I know that in download mode i can run fastboot to flash recovery and so on. But this unit at this point wont let me get into download mode, neither recovery mode. Even by selecting it on the bootloader screen or fastbooting the commands.
I've found a post (gotta search it) that had kind of the same issue, a soft brick unit and somehow he managed to bringing it back to life. By unpacking a RUU rom.zip achive and fastboot flash each partition.
Or i'm stupid enough but by rom.zip file is full of zips (zip1,zip2 and so on) not recovery.zip / boot.zip / radio.zip and so on.
Gotta find that topic to quote it.
Click to expand...
Click to collapse
Hi, do you finded any solutions?

iakelclaudiu said:
That was the first thing i've tried. I know that in download mode i can run fastboot to flash recovery and so on. But this unit at this point wont let me get into download mode, neither recovery mode. Even by selecting it on the bootloader screen or fastbooting the commands.
I've found a post (gotta search it) that had kind of the same issue, a soft brick unit and somehow he managed to bringing it back to life. By unpacking a RUU rom.zip achive and fastboot flash each partition.
Or i'm stupid enough but by rom.zip file is full of zips (zip1,zip2 and so on) not recovery.zip / boot.zip / radio.zip and so on.
Gotta find that topic to quote it.
Click to expand...
Click to collapse
Try to search for the HTC Decrypt Tool here. You'll find the thread which will help to decrypt the RUU and receive the images needed to flash.
On thebother hand you got to be in download mode to flash them. If you're not able to reach it, I guess it's a case for a professional repair.
Sent from my HTC U11 using XDA Labs