Develop Bugs

I posted minutes ago another thread with the first part of the Desire issues

I tried unrevoked again as I had clockwork recovery mod on my desire, but it doesn't read my device anymore...trying to install RUU doesn't get me any further either. Maybe I do not have the right version of RUU, or maybe the CID no I got the very first time while creating the gold card wasn't correct, fact is that right now I have the device hooked up on my pc via usb and all I can do is boot in bootloader or recovery mode but thats it.
Trying PB99IMG.zip from sdcard results in CID fail...trying adb from console results in List of devices attached or error: device not found, or at best error remote: not allowed (this happened a while ago when I finally managed to keep adb on for more than a second and I tried pushing the recovery files)...
Oh, one more thing to add to the whole list of surprises...the USB drivers which before having these issues were working just fine, now aren't being recognized by the PC, I installed them manually but the drivers referring to Qualcomm Extra are not to be found even though I used the drivers provided on the forum, the ones provided in the reflashing packages etc etc etc...
BTW I am using W7x64...could this be also a reason why fixing this issue became such a pain in the a**?
Please help!

Another small step to fixing the desire
I found CID HTC_044...what should be the next step?...I can't still use PB99IMG.zip I can't use adb (device not found) only fastboot works for now.

fastboot oem boot error ...FAILED (command write failed Unknown Error)...just after finding HTC_044...where can I get a goldcard just with this CID?
Any help is much appreciated thank you!

Try the Desire forum for a quicker response

Stuck with branded Bootloader 0.80

edit: It finally worked. I cleaned the microsd with diskpart and made a new goldcard, then I flashed a HTC WWE 2.29 Image, with the PB99IMG method. Now Im on bootloader 0.93.00. Back to business (I don't know exactly why the goldcard worked this time, or maybe the goldcard wasnt the problem)
Hello,
I tried to go back to the original state (TMobile germany branded). The phone was S-Off and rooted and I had a cm7 partition table.
At first I just tried to flash over an original T Mobile Rom (RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570a_signed.exe).
Everything worked, and after that I did put the newest OTA Update on the phone. Checking to see what bootloader I have I saw that I was still Security Off. So I flashed a downgrade HBoot from the alpharev page. After that I flashed the same T Mobile Rom again to have an original HBoot.
Somewhere in the middle of the procedure though it stopped and I was stuck in that screen with four triangles on the sides and HTC written in the middle. At first I thought now its totally bricked without hboot, but I was able to reboot into HBoot. Also i can get to fastboot and the standard recovery mode. The current Hboot is 0.80 and S-ON.
Now from there on I tried many things:
- Downgrader from xdadevelopers does not work because one has to be in a working system
- Unrevoked does need a working system
- Tried same TMobile Rom numerous times with the installer on PC (gives bootloader version wrong 140) and as update.zip in recovery mode (signature verification failed)
- Tried RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe and RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865.exe
- I made a goldcard and tried to flash these roms from the goldcard in recovery mode
- Tried to flash the ota update I installed through recovery mode
- Also I tried all of these things with the rom.zip named as PB99IMG.zip in Bootloader
- Fastboot commands do not work, So I should have a locked Bootloader now
- The old root method with goldcard which did not work
- I tried to get into an adb shell in recovery mode with various drivers to get the cid of the sd card to make a new goldcard but the device is listed as offline
I am not really sure why the goldcard does not work, maybe my saved goldcard image got messed up for some reason. Unfortunately I can't get the cid of the phone, because I can't use adb meaning the phone is recognized with "adb devices" but shown as offline.
If there is some other way to get the cid that I have not found as of yet, that might help.
Otherwise I am out of ideas... I hope its not bricked, help is greatly appreciated
edit: official update utility tmobile rom shows that I'm coming from 2.12.110.2 and going to 1.21.110.4 so it seems like the room still exists somehow but cannot boot, bootloader starts and deletes user data, sends data, updates signature=> bootloader version error 140

[Q] problem with ruu

hello guys, i have a problem using RUU to revert my phone back to stock, i searched for a solution on xda forum and google for few hours now but nothing was exacly my problem. i am sorry if i missed vital information, this is my first android phone and i am still trying to learn and understand how it works.
CID 004 primou
i tried 2 different ruu versons for this CID. before using each i did the following steps
flashed boot from archive, flashed recovery from archive, relocked the bootloader.
-http://forum.xda-developers.com/showpost.php?p=30966084&postcount=114
first gave the error 155 due to the HBOOT being of a more recent version than the ruu (not sure if i understood well the error)
http://forum.xda-developers.com/showpost.php?p=30994089&postcount=121
on the second ruu *latest, i did same steps as before, unlocked bootloader, flashed boot, flashed recovery, relocked, but the ruu gives the error 170 ( device not connected) but i am 100% sure it is correctly connected into fastboot because it responds to One_V_All-In-One_Kit and it was recognized by the previous ruu.
i am using windows 8 pro and i have installed the ADB interface using the SDK google driver, this method to be exact http://forum.xda-developers.com/showthread.php?t=2088896

Can you run this script and let us know the result because CID 004 is different from 044.
See this post for the script : http://forum.xda-developers.com/showpost.php?p=36514545&postcount=15
And this post reason for error 170 : http://forum.xda-developers.com/showpost.php?p=36515756&postcount=22

hello, thanks for helping me,
i do not have any USB 3.0 ports on my PC, and the battery is at about 60%
the script you gave me told me this:
C:\Users\Draghici\Desktop\CID_checker_2>call fastboot getvar cid
cid: HTC__044
finished. total time: 0.001s

There is no need to flash boot.img and recovery.img, just a relocked bootloader is needed.
Just follow this step : http://forum.xda-developers.com/showpost.php?p=36515523&postcount=18
Most important is make sure your device is put on fastboot usb mode not hboot usb mode. (Another common error for usb connection problem when flashing RUU)
And use the latest RUU RUU_PRIMO_U_ICS_40A_hTC_Asia_WWE_2.22.707.2_Radio_ 20.76.30.0835U_3831.19.00.120_release_274703_signed.exe

ckpv5 said:
There is no need to flash boot.img and recovery.img, just a relocked bootloader is needed.
Just follow this step : http://forum.xda-developers.com/showpost.php?p=36515523&postcount=18
Most important is make sure your device is put on fastboot usb mode not hboot usb mode. (Another common error for usb connection problem when flashing RUU)
And use the latest RUU RUU_PRIMO_U_ICS_40A_hTC_Asia_WWE_2.22.707.2_Radio_ 20.76.30.0835U_3831.19.00.120_release_274703_signed.exe
Click to expand...
Click to collapse
sure i will do it right now, but i am 100% sure i relocked it correctly, the phone was in fastboot USB (red text) every time, and after each flash of boot/recovery, i relocked it, it told me in pink text in the recovery mode "RELOCKED"
but one more thing to add, when the RUU install failed on my phone screen it told me that the HBOOT version is too recent or something like that

hboot too recent if you flash 2.09 RUU (for hboot 1.17) but your hboot maybe 1.18 (2.22 RUU).
Unless there is a further update that I may missed, what hboot number is written on the bootloader ?

ckpv5 said:
hboot too recent if you flash 2.09 RUU (for hboot 1.17) but your hboot maybe 1.18 (2.22 RUU).
Unless there is a further update that I may missed, what hboot number is written on the bootloader ?
Click to expand...
Click to collapse
i have the 1.18, so i need to use
RUU_PRIMO_U_ICS_40A_hTC_Asia_WWE_2.22.707.2_Radio_20.76.30.0835U_3831.19.00.120_release_274703_signed
the one that gives me the error 170. i have 3 drivers provided by android SDK named
Android ADB Interface
Android Bootloader Interface
Android Composite Interface
each of them work with the 2.09 RUU and with all in one tool but none of them worked on 2.22 RUU.

You need HTC USB driver.
I'm using the driver from this HTC Sync Manager. It works nicely for Win 8 pro.
Install the HTC Sync Manager, it will install the necessary driver and you can remove the HTC Sync Manager later on but keep the driver.
http://www.htc.com/www/software/htc-sync-manager/

ckpv5 said:
You need HTC USB driver.
I'm using the driver from this HTC Sync Manager. It works nicely for Win 8 pro.
Install the HTC Sync Manager, it will install the necessary driver and you can remove the HTC Sync Manager later on but keep the driver.
http://www.htc.com/www/software/htc-sync-manager/
Click to expand...
Click to collapse
sorry for the late rly, I think I got some progress, I did the next steps.
went to device manager and uninstalled google android sdk driver, went to HTC Sync installation folder (I had it installed at first try but it did not pass my mind to show windows the location where it was installed, anyway...) and I installed the windows 7 driver, the windows 8 do not work for some reason, right now I can see the green progress bar on my phone so I guess it worked.
thanks a lot
I will ofc hit the "thanks" button on your posts here.

Yep...that's a good progress... it will be a successful flash

[Q] HTC ONE X stock rom update fail

Hi ALL,
I'm new to Android and I just brought a used HTC ONE X. Previous user updated this phone to JB custom rom. I just wanted to reflash the phone using HTC official RUU. So followed some youtube videos and tried to do it. Some how due my poor knowledge in Android rom details I tried with a wrong RUU. So it went fail and then tried to recover that also failed. Now phone is just boot up to fastboot menu. unfortunately I can't find a sutable RUU too. My phone details are shown below. Please help !!! :crying:
Radio version - 1.1204.105.14
cid - vodap102 (Vodafone UK)
Hboot - 1.12.0000
rom ver - 2.17.161.4
Please help me to find proper RUU.
Thanks !!

I can't find your either but there is another method. First you need to get fastboot commands working ! If you know something about that ?
Install HTC drivers
http://db.tt/gXVxa3Dp
then download these files to your pc
http://db.tt/ldx3qOOU
C:\fastboot\*the files i gave you*
Then open a command prompt inside the fastboot folder on the pc, hold shift and right click inside the folder and choose "open command prompt here" or something similar
Then you put the phone in the bootloader and connect the cable to the pc
Then type
Fastboot devices
It should return a serial of the phone ! Lets start with all this and report back

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