Develop Bugs

[Q] Desire won't boot (now: Radio_v2 failure)

Hi All,
Sorry another n00b making a n00b thread.
I bought a second hand desire very cheap under the understanding that "stopped booting one day" - so first thing first, if it is bricked, so be it.
Currently it only gets as far as the white HTC screen.
Now, when booting with PWR + Vol Down:
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
RADIO-5.17.05.23
Obviously the PO has been playing around given the unlocked bootloader. I can get into fastboot fine. fastboot devices shows the Serial of the device.
So following the Troubleshooting guide here I attempted to flash a Recovery image as per recommendation. It shows sending and writing recovery.img OK, and the two progress bars display on the phone in line with that. However, when rebooting (fastboot oem gencheckpt), I still can't get into recovery - it goes back to the HTC screen again. Same with fastboot reboot-bootloader if it matters.
***EDIT - kept looking on this forum and it seems as if this bootloader would be write protected against RUU updates? So you can probably disregard what was here. I'll keep looking around, but if anyone has advice feel free!
If I'm missing something silly here, feel free to abuse me while you tell me what it is. Just thought I'd check to see if I'm on the right track or I've failed miserably.
Thanks.

Download the HBOOT downgrader from alpharev.nl (and the stock HBOOT, too).
Flash the
1. stock HBOOT,
2. the downgrader
3. then the RUU of your choice (2.3.3/2.2 depends on you).
As you said, you can get to fastboot, it'll work.
You'll get a stock, unrooted device, but you can root it later on.

davebugyi said:
Download the HBOOT downgrader from alpharev.nl(and the stock HBOOT, too).
Flash the
1. stock HBOOT,
2. the downgrader
3. then the RUU of your choice (2.3.3/2.2 depends on you).
As you said, you can get to fastboot, it'll work.
You'll get a stock, unrooted device, but you can root it later on.
Click to expand...
Click to collapse
Thanks for that - I flashed these in this order from fastboot and then rebooted - I can see that it has taken effect due to seeing "AlphaRev Unlock" now, however, can't get the RUU to go - gets to Rebooting to bootloader, phone reboots and gets stuck in a bootloop (I suppose - HTC screen, black screen, and so on). Eventually it gives up and gives [171] USB CONNECTION ERROR. "Reboot Bootloader" from the fastboot menu does the same thing.
I actually have an Atrix so this is not my daily driver, so nothing too urgent, or in fact tragic if it is a hardware issue. I do appreciate any help though all the same!

Hmm - can be the cable, the drivers.
Even some people said, that using win7 64Bit will get you this error.
I'd check first the drivers. Maybe you have USB Brick as well - search the Dev Thread for a fix - basically 2 commands.

I was just reading up on the USB brick actually, as you say doesn't seem like too much effort anyway.
I am using Win 7 x64 in fact... I will copy all the necessaries to a USB stick and use a WinXP box at work just to make sure. Thanks again!

OK, update -
Same result on a WinXP machine trying to flash via RUU.
When I try fastboot oem enableqxdm 0, I get:
partition_read::Too many bad blocks(out of range)
It does say OK after that though?
If I try to flash a mtd0.img via fastboot (I assume I can't use an SD card given I can't boot) with SuperCID as the CID (either hex edited or with the script) I get:
sending 'misc' (640KB) OKAY
writing 'misc' (640KB) ... FAILED (remote: image update error)
It's late here so I'll search more in the morning, but any guidance would be appreciated.

Should I be erasing the misc partition before attempting to flash mtd0.img? If that's where I've gone wrong I'll kick myself, but thought I should confirm before I break the phone more.
Update:
I grabbed the rom.zip from the temp folder, renamed it to PB99IMG put it on a MicroSD and let the phone do its thing. It worked, in that it performed the update, but Radio_v2 failed - so I assume this means either I have a branded handset that has nothing on the outside (how do I check?) or there is a hardware fault?
Of course, I have S-ON now because everything else worked...

radio failure means you're kinda fu*cked IMO... I mean I know a user who kept trying a RUU who eventually undid the radio fail but ermm.. yeah usually it means a real brick

I figured that might be the case. Given the bootloader was already unlocked when I received the phone, one can assume the previous owner actually knew what they were doing and had already tried to fix it and come to the same conclusion.
I'll update the thread if I manage to fix it, but if anyone else stumbles across this due to similar circumstances, looks like you have your answer.
PS: bortak your troubleshooting thread was an amazing help.
Thanks to all!

yeah just try the RUU a couple of times (like 10 or something) and see what happens.. if you're lucky you might get a break..
or what you could do is flash the 2.3.3 RUU, hope it works, and if you do get stuck in splash HTC will cover you warranty!! just tell them you try to upgrade and it broke!

NEED HELP Getting My One X Working Again!!! (Relocked bootloader issue) :(

Ok this is the story.
So I see there is a new custom ROM (HTC One maXimus) with Android 4.1.1 for the One X. I decide to root it.
However the ROM forum tells me that I have to install this 'PJ46IMG.zip' containing the new HBOOT 1.23 in order for JB to run on my phone.
Following the guide, I then start to un-root my One X, first installing the recovery.img file, then re-locking the bootloader using the 'fastboot oem lock' command.
This is the ISSUE!
When I tried installing the RUU version for my One X (I matched the RUU looking at the bootloader menu Radio version), it tells me that my phone is not connected to my laptop (when it clearly is?!).
This is exactly what the bootloader menu says:
*** RELOCKED ***
Endeavoru PVT SHIP S-ON RL
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.90.13
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
My phone even says 'FASTBOOT USB'.
I can't seem to re-boot my phone as it always comes back to the bootloader, plus I get this "developer warning" message as the phone boots.
Also, whenever I try doing a fastboot command on my laptop, it's just stuck on 'waiting for device'.
IM LITERALLY STUCK GUYS! Just hoping there's someone here who knows exactly what to do

try rebooting your pc and bootloader

solution
Jamz442 said:
Ok this is the story.
So I see there is a new custom ROM (HTC One maXimus) with Android 4.1.1 for the One X. I decide to root it.
However the ROM forum tells me that I have to install this 'PJ46IMG.zip' containing the new HBOOT 1.23 in order for JB to run on my phone.
Following the guide, I then start to un-root my One X, first installing the recovery.img file, then re-locking the bootloader using the 'fastboot oem lock' command.
This is the ISSUE!
When I tried installing the RUU version for my One X (I matched the RUU looking at the bootloader menu Radio version), it tells me that my phone is not connected to my laptop (when it clearly is?!).
This is exactly what the bootloader menu says:
*** RELOCKED ***
Endeavoru PVT SHIP S-ON RL
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.90.13
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
My phone even says 'FASTBOOT USB'.
I can't seem to re-boot my phone as it always comes back to the bootloader, plus I get this "developer warning" message as the phone boots.
Also, whenever I try doing a fastboot command on my laptop, it's just stuck on 'waiting for device'.
IM LITERALLY STUCK GUYS! Just hoping there's someone here who knows exactly what to do
Click to expand...
Click to collapse
Hi, I did the exact same thing and faced the same issue. To resolve it, do one thing, just try unlock the bootloader again. And your phone will start working as before. For unlocking the bootloader you will need the Unlock_code.bin file which you used initially to unlock your bootloader. I hope you have the file. I was able to find it in my mailbox. HTC would have sent this file in email.
Let me know if I helped by clicking Thanks

So did you flash the stock boot.img before you relocked the bootloader? And your CID matched the prerequisites right?
For instructions: http://insertcoin-roms.org/2012/10/insertcoin-evolution-one-x-10-0-0-jellybean-and-sense-4-5/

Vcek said:
try rebooting your pc and bootloader
Click to expand...
Click to collapse
Hi,
I tried that but it still didn't work

sun_strings said:
Hi, I did the exact same thing and faced the same issue. To resolve it, do one thing, just try unlock the bootloader again. And your phone will start working as before. For unlocking the bootloader you will need the Unlock_code.bin file which you used initially to unlock your bootloader. I hope you have the file. I was able to find it in my mailbox. HTC would have sent this file in email.
Let me know if I helped by clicking Thanks
Click to expand...
Click to collapse
Hi,
I have found the Unlock_code.bin file, but whenever I try to flash the fastboot command, it is still stuck on 'waiting for device'
What am I doing wrong?

Try a different USB cable or different computer

tomascus said:
So did you flash the stock boot.img before you relocked the bootloader? And your CID matched the prerequisites right?
For instructions:
Click to expand...
Click to collapse
Hi,
Now I think about it, I only flashed the recovery.img
Plus, I did not have time to check the CID, because everytime I enter a command, it is just stuck on 'waiting for device'

You should have checked the CID first before you even started to do anything.
Reinstall a stock RUU and then try to unlock bootloader from there.

Got it working now !!
All I did was use a different computer and re-rooted it! Thanks for all the help guys!

Go to Fastboot
Jamz442 said:
Hi,
I have found the Unlock_code.bin file, but whenever I try to flash the fastboot command, it is still stuck on 'waiting for device'
What am I doing wrong?
Click to expand...
Click to collapse
Are you on fastboot mode. Keep volume down + power button pressed for sometime and your phone will restart in Bootloader modem, you will be HBOOT, use the up and down volume keys to select fastboot, then press power button, your phone will switch to FASTBOOT from HBOOT. When you are in Fastboot mode, try running the command for unlocking.
Let me know if I helped by cliking Thanks

Need massive rooting help

okay so ive tried everything ive read everywhere, htcdev wont work either the command to get a key to put in there site response with an error
This is not my first time working with android devices and rooting, but im at a complete lose.
My phone
::Locked (oow)::
Incrediblec XD SHIP S-ON (obviously i want off so i can flash)
android 2.3.4
v2.15.10.12.20 baseband
kern v2.6.35.13
build v4.08.605.15
hboot 1.02.0000
Unrevoked wont work, super oneclick, anything,
USB debugging is on fastboot off, etc etc
I follow all the gudies i find to a T and nothing seems to work
PLEASE HELP!!!
Email me @ [email protected]

rglabs said:
okay so ive tried everything ive read everywhere, htcdev wont work either the command to get a key to put in there site response with an error
This is not my first time working with android devices and rooting, but im at a complete lose.
My phone
::Locked (oow)::
Incrediblec XD SHIP S-ON (obviously i want off so i can flash)
android 2.3.4
v2.15.10.12.20 baseband
kern v2.6.35.13
build v4.08.605.15
hboot 1.02.0000
Unrevoked wont work, super oneclick, anything,
USB debugging is on fastboot off, etc etc
I follow all the gudies i find to a T and nothing seems to work
PLEASE HELP!!!
Email me @ [email protected]
Click to expand...
Click to collapse
Well the first thing i see is that it says locked (oow) meaning you have had it unlocked before. If you were the one who unlocked it, you should sill have the unlock_code.bin file htc sent you the first time. It will be in the same folder on your pc as fastboot.exe. If you still have the file you can just use fastboot to reapply it.
Code:
fastboot flash unlocktoken unlock_code.bin

[Q] Bell WFS Bootloop ONLY When Not Connected to USB Cable

Hey guys,
So I've spent the last 48 hours raking my head on this one. I'm an intermediate user (Samsung whiz - Ace, i9100, T989, I747, S4 Canada, knowledgeable in HTC's - S-OFF HTC Evo 3D GSM / S-OFF HTC EVO 4G, experience in Experia devices), so I'd say I've done some things, but this one has totally stumped me.
I've successfully:
- Managed to upgrade the HBOOT before unlocking the bootloader (required an RUU update > "PG7611000_Marvel_Hboot_1.08.0099_1.36.666.5.exe"
- Flashed TWRP/CWM (currently running TWRP) using "fastboot oem flash recovery"
- Created a backup of the stock ROM
- Flashed latest version of SuperSU
Now, I restarted the WFS to finalize all my work and hand it back to my friend, but it just bootloops. I do have access to the bootloader still, and always have. I try to load recovery through the bootloader and it bootloops.
Here's the real kicker:
- If I keep the USB cable plugged in, it runs beautifully. Both booting normally into any ROM I've flashed, and to the recovery.
- If I unplug the USB cable when booted into the ROM, it'll run fine until I restart/shut down.
- If I pull the battery and start it up normally, it bootloops. Vibrate, HTC logo, sits for about 5 seconds, goes black, repeat.
Attempts:
- I've tried to create a Gold Card, but the website making the *.img file is down. Tried the other site that just asks for your CID and spits out the *.img file, but neither forward/backward works.
- I've downloaded the only full Bell RUU > "RUU_Marvel_BM_1.36.666.5_Radio_47.10a.35.3030_7.46.36.14M_release_189856_signed.exe", then tried pulling the ROM.zip from the temp folder. It's the only one where the archive appears to be broken. I've tried different download locations and confirmed the md5 matches.
- I've tried just running the Bell RUU thinking that it might work, but it doesn't when it's an older release or equal to the existing one.
- I've tried the latest European RUU > "RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe" and I can pull the ROM.zip, but because the phone is BM___001, it won't allow the flash. I would need a Gold Card, which as I've mentioned is unavailable.
The only thing I haven't done (scared to do so)
- I haven't tried flashing it directly using "Method 3" in This Link because I'm afraid to really brick the device.
Because I can't unzip the Bell RUU (corrupted), I'm afraid to try using even the generic European RUU. Would this even work? There's also this Link which I've checked, but again, I don't think I can even do this one without the Gold Card working.
Leave it to Bell for only having one RUU.
Any thoughts on this very peculiar issue? I've seen a few threads that talk about other HTC devices with this issue, but only an RUU can be performed. And back to the "only-one-Bell-RUU" and "Gold-Card-website-down" issue.
Any help would be greatly appreciated!
Stats:
- Bell HTC Wildfire S (Bell Branded, BM___001)
- Unlocked Bootloader from HTC Dev
- TWRP 2.2.2.0
- Marvellous-Sense-3.5_07.10.13_FIXED
*** UNLOCKED ****
MARVEL PVT SHIP S-ON RL
HBOOT - 1.08.0099
MICROP - 0451
RADIO - 7.46.36.14M
Nov 28 2011, 19:09:21

I'm working from memory, and I'm only going by what you typed, but I'll suggest 2 things for your consideration/research:
I'm unsure how you used, "fastboot oem flash recovery". In my wildfireS (Marvel) the command, "fastboot oem..." doesn't have a flash command option. I'm wondering if this has got you stuck in a bootloader bootloop. You can see the available fastboot [bootloader] commands by hooking up to your PC and in fastboot, type, "fastboot oem ?" without the quotations of course, and it will list the commands. I wonder if you flashed your recovery without that oem in the command line if that might help??? I've always just done straight, "fastboot flash recovery [recovery].img"
The second thing is I've read that either ChainsDD superuser or the superuserSU by Chainfire doesn't play well with TWRP. I don't remember which. Although that's less likely to cause a bootloop, I'm just throwing it out there for consideration.
I'm sorry I can't say anything definitive, but those 2 things came to mind reading your post. Good luck.

[Q] Reverting DHD To Stock RUU?

Hi everyone,
right i have one massive pain in the ass with my Desire HD....
Basically i bought it on ebay it came with the PAC Rom on it... now i want it to be absolute stock no root/no customisation..
so far i have searched high and low on these forums for a solution and found none that work i have also been to shipped-roms.com and tried every single ruu and every single one failed on the signature upgrade?
i have made a gold card although i am now unsure how to actually use it to be able to install a ruu..
i have tried absolutely everything i can think of..... ANY HELP WOULD BE GREAT???
my DHD info.... (from bootloader)
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011, 14:28:19
i believe the out of box android version was Gingerbread 2.3.5.... it also seems i cannot find an RUU for my radio version??
if any one can help me get it to accept a stock ruu i would be very greatfull..
and if i ever solve this problem i will be writing a full tutorial/guide on how to do it just for reference...

Inside 4ndroid said:
Hi everyone,
right i have one massive pain in the ass with my Desire HD....
Basically i bought it on ebay it came with the PAC Rom on it... now i want it to be absolute stock no root/no customisation..
so far i have searched high and low on these forums for a solution and found none that work i have also been to shipped-roms.com and tried every single ruu and every single one failed on the signature upgrade?
i have made a gold card although i am now unsure how to actually use it to be able to install a ruu..
i have tried absolutely everything i can think of..... ANY HELP WOULD BE GREAT???
my DHD info.... (from bootloader)
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011, 14:28:19
i believe the out of box android version was Gingerbread 2.3.5.... it also seems i cannot find an RUU for my radio version??
if any one can help me get it to accept a stock ruu i would be very greatfull..
and if i ever solve this problem i will be writing a full tutorial/guide on how to do it just for reference...
Click to expand...
Click to collapse
First of all you can't run RUU with unlocked bootloader you need to relock it, go to fastboot connect phone to PC and run command:
fastboot oem lock
to relock bootloader.
Then run command:
fastboot getvar cid
to find the cid of your device. when you find it well find the appropriate RUU for you region.
However you can run PB.img from Goldcard without having to find appropriate RUU, but not all SD can be made to it. Go to AAHK2 thread and you will find what manufacturers are supported.

nlooooo said:
First of all you can't run RUU with unlocked bootloader you need to relock it, go to fastboot connect phone to PC and run command:
fastboot oem lock
to relock bootloader.
Then run command:
fastboot getvar cid
to find the cid of your device. when you find it well find the appropriate RUU for you region.
However you can run PB.img from Goldcard without having to find appropriate RUU, but not all SD can be made to it. Go to AAHK2 thread and you will find what manufacturers are supported.
Click to expand...
Click to collapse
I am currently at work but I downloaded the gold card helper app and here's what it gives me
screenshot attatched
if this is no good then I will have to wait until I get home... thanks for your help

Inside 4ndroid said:
I am currently at work but I downloaded the gold card helper app and here's what it gives me
screenshot attatched
if this is no good then I will have to wait until I get home... thanks for your help
Click to expand...
Click to collapse
I think it's better to wait until you get home.

nlooooo said:
I think it's better to wait until you get home.
Click to expand...
Click to collapse
hi again home now
right i have relocked bootloader so now the bootloader screen is same as before but it now says *** RELOCKED ***
and i have run "fastboot getvar cid" which gives an output of "cid: T-MOB005"
i hope this is what you were asking for and you can direct me to a RUU for it...
i await your reply
EDIT: i also tried the RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe
and i get ERROR [131]: CUSTOMER ID ERROR?????
thanks

Inside 4ndroid said:
hi again home now
right i have relocked bootloader so now the bootloader screen is same as before but it now says *** RELOCKED ***
and i have run "fastboot getvar cid" which gives an output of "cid: T-MOB005"
i hope this is what you were asking for and you can direct me to a RUU for it...
i await your reply
EDIT: i also tried the RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe
and i get ERROR [131]: CUSTOMER ID ERROR?????
thanks
Click to expand...
Click to collapse
I'm unable to find appropriate RUU for your phone cause it's for TMobile UK. So Goldcard is the only way. However go to AAHK2 thread to find out which SD card can be used. When you make a gold card extract rom.zip from RUU that you tried, rename it to PD98IMG.zip, put it to the root of your goldcard and reboot phone to bootloader. Use Vol up and down buttons to install.

nlooooo said:
I'm unable to find appropriate RUU for your phone cause it's for TMobile UK. So Goldcard is the only way. However go to AAHK2 thread to find out which SD card can be used. When you make a gold card extract rom.zip from RUU that you tried, rename it to PD98IMG.zip, put it to the root of your goldcard and reboot phone to bootloader. Use Vol up and down buttons to install.
Click to expand...
Click to collapse
ok no problem i will give it a shot later tonight.. i will post my results... oh an i hit thanks
RESULTS: basically i now have a full stock desire hd although i now have no service i cant seem to get it to connect to my network... i followed all your instructions?

flash recovery
I have been through a similar situation before
But I have known the version of ruu for my phone
The key is the error message you have is solved by an easy way
You have to open the ruu u have
And look in the temp folder (%temp%)
For a file named rom.zip
Copy it
Unzip it
Flash boot.img
Recovery.img
System.img files in the fastboot menu
I.e
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
Fastboot flash system system.img
Then try running the ruu again
It should work
Otherwise the gold card will solve it
Keep me updated