Hi guys,
I need some help with my phone. Few days back I charge my phone after it died as it ran out of battery. I turned it on as I was connecting it to the charger and the white HTC loading screen came on. Left it there to do my own work and came back few hours later to notice that it's still stuck at the same loading screen. Pulled out the battery and tried turning it on again with the same result.
I tried all the methods I could find online to fix it.
The HBoot/Recovery selection only cause it to reboot and get stuck at the same loading screen. Clear Storage is successful but it get stuck again at the same screen after rebooting.
I tried to flash the latest official RUU through the pc at first but error 170 came out and my phone was not detected by the pc.
Then I tried it again with the PB99IMG.zip method with both my current microsd card and my goldcard.
The PB99IMG wasn't detected on my goldcard showing no image found, however it was detected when I place it in my current microsd but the CID incorrect error came up.
I tried the same thing again with few other different RUU.
Examples of the RUU that I had tried:
RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
I even reformatted my goldcard to try again but the PB99IMG still wasn't detected.
Details of my phone is as below:
BRAVO PVT3 SHIP S-ON
HBOOT- 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
It is unbranded Asia WWE SLCD phone. I rooted it a year ago and flashed it to official WWE europe version to catch up with the froyo hype. And I did use back the same goldcard back then to try the PB99IMG method.
Can anybody please help me out?
try boot into fastboot power+back button
Then run in cmd:
Fastboot OEM enableqxdm0
Sent from my HTC Desire using XDA Premium App
kotag82, thanks for your reply.
I did what you told me to but after I entered the command, all I got was this
C:\android-sdk\platform-tools> Fastboot OEM enableqxdm0
. . .
<bootloader> [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
Also when I entered "adb devices" on the cmd prompt, the list of devices attached is empty. Any advice?
try
fastboot devices
as adb doesnt work in fastboot mode
fastboot oem enableqxdm 0
fastboot oem eraseconfig
i sorry mistyped
I did as you advised me to and the following was the result:
C:\android-sdk\platform-tools> fastboot oem enableqxdm 0
. . .
OKAY [ 0.098s]
finished. total time: 0.099s
C:\android-sdk\platform-tools> fastboot oem eraseconfiq
. . .
<bootloader> [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
the eraseconfiq command failed so what should I do now?
config is spelled with a g, not q
sorry for the misspellings on my last post.. I did enter eraseconfig (with the correct spelling) but the same result came out..
C:\android-sdk\platform-tools> fastboot oem eraseconfig
. . .
<bootloader> [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
anything else that I missed?
How many partitions do you have on your gold card? Has it ever worked before?
only 1 partition
yes it's working..i used it to root my phone 2 years ago to flash the european froyo as mentioned in my initial post
Are you able to get another goldcard or create another goldcard with another phone?
Sent from dGB using Transparent XDA App
i have no access to another android-based phones and the current goldcard i am using is the only card that i managed to create a goldcard from
are there any other solutions?
edit: sorry for the double post
anybody else have any ideas? my phone is still stuck at the htc logo
Related
Idk why, the problem resolved it self. I plugged it up to the cable and did nothing. Screen flashed once, then booted into BootLoader.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ok. So I was going back to complete stock using the RUU method from - http://forum.xda-developers.com/showthread.php?t=1705484
I followed everything and got up to locking the bootloader. I got this message when doing
fastboot oem lock
It said
C:\fastboot> fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.359s
C:\fastboot> fastboot reboot-bootloader
< waiting for device >
And now I have a screen with lines, kinda like a dead TV and a blinking led light. Phone won't respond to buttons or commands.
That means u did not connect the phone via USB in fast boot our ur device is not getting detected try installing htc drivers again
Sent from my One V
Hello XDA Programmers and Developers,
I have a big issue with my HTC Desire. Long story short I think I have bricked it
To begin with, I acquired the phone locked to Vodafone UK. After trying to unlock it using HTC Unlock Sim Tool, the software crashed and the phone was restarting at random times. You can watch the video here.
So, following some advice from XDA, I tried to re-install RUU 2.3 Gingerbread Update through the SD Card. For some reason I got a worse problem which was Radio Fail
In order to fix the issue, I tried many different RUUs available in order to get the radio fixed. One of the RUU I used resulted to what is known SLCD brick. As you can understand now, I have now visual feedback now.
In order to fix this, I followed this thread along with this tutorial.
I have created a goldcard and tried all day long to get a WWE RUU run and fix the issue. However I got no results.
Then, I decided to try fastboot and see if the phone is working.
When I run Command I get the follwing results:
1) The device is connected properly:
Code:
C:\android-sdk-windows\tools>fastboot devices
HT091PL00003 fastboot
2) I cannot flash RUU from fastboot:
Code:
C:\android-sdk-windows\tools>fastboot update C:\rom.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
æÙf¸ıÝ´Ñ♫#È╩Á¹Ù■WÎPo±*Uì¬▒á·[▒¡←#òc¼ÿ¢@mUaóQ├«+═^IÕ(F^.↕ƒF,C╗_îü䬲kÿ░Û░û£↨▼♫¤ó♀
bH╗ÓòH+·qÚøµvÞ¾↨ò▲?<´ª█í8úb0<Í╔ÚÈ═║¿µ»gÑvØ╠Ð7tù¿┬Z
ÙÖíÌ´─┐uüL;^Ý3Ö<N²®♦ö"┤uè+║ö┬öµgO¥Å)XX┌u↕▒#Ì iÜøJÅ×R5ıÜ<▓=5ï▲WÂ☺B─┤0º▲Ó©^÷┴JÂn0q
BÓü▓ý☼¯cª°£]'oÿ¥ùO4£g←╔o☼!⌂_LSä¯Ê☻(½j♣&O}bõ,∟♥┘Ä°bT↨╚↔ÒıÌì╬+ð▀»L▀»‗ûjéC▒D#▒¼.)ª♀
*┘♀ƒI*y§À,y²À²©┘±▲|>}À5Z2♦÷^E´ù♀Á╩å3ÆÓÖãÅÌV┬⌂+■5nÕAÔ0~┴½Âq▲←»nl»ÍaîéÝÜW♀█üç+*Ñ*Ö
l/ý§┼x>£i5ız▬♠↑╠ëI∟0½♂±☻·/A╗│T▓ÖÖ±ÜعØÊë│R█zKÁTé■3þ┼▓♫ã▒Ã╔↔η↑ïS2←3Ì^jNÌ^r╦╝$e;k
Ik$├S=I█ì█_Ƶû┐$═ü¤=ãv~rìÛ]&bµÿ╚0C¢d6▼»C*©ziÿ▒░âÕßõÀ╝
vШ¬─©Q_2â│Cg¢À¼©C3ï▒╠ÛHÂü|┐½«♦§§{'
3) This is a bit weird: The list never ends
Code:
C:\android-sdk-windows\tools>fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E
07D944
INFOTAG:Ramdisk OK
4) I can however restart it into bootloader (apparently since I don't have any feedback from the phone or the computer)
Code:
C:\android-sdk-windows\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.016s]
finished. total time: 0.016s
-----
Lastly, I can't update using any RUU since I get ERROR 170 and ERROR 171.
Any help is appreciated.
Did you try the 2.3 GB RUU?
abaaaabbbb63 said:
Did you try the 2.3 GB RUU?
Click to expand...
Click to collapse
Yes, I did try it. However, when I try and run the .exe file through my computer I get error 171.
The exe file guides me up to the point where the installation begins, and it stops working at this point:
"Restarting Bootloader"
"Watining for Bootloader......................"
"Error 171:USB Connection fail"
Click to expand...
Click to collapse
I've been trying for two days and can't make it...
I have a Desire HD with 2.3.5, sw 3.12.207.1 and Sense 3.0 all stock. It isn't branded and it has S-On with H-BooT 2.00.0027
The thing I want to do is install CWM and have the ability after to flash ROMS. As I read I must first unlock the bootloader and then flash CWM correct?
The problem is that when I start the HTCDev instructions I get this:
C:\tools>fastboot oem get_identifier_token
< waiting for device >
...
FAILED (status malformed (1 bytes))
finished. total time: 0.023s
I have HTC Sync, Android SDK, Java. I know that the phone is recognised in windows when working and in fastboot cause it always finds it with either "adb devices" or "fastboot devices". What am I doing wrong?
I tried Easy Ace Root Tool but still the same happens. Some more info if this helps. In the HTCDev steps it says that I should update with the RUU. When I try that (tried them all) I get this: ERROR [191] ROM IS NOT SUPPORTED
Any ideas??
update your hboot with this
www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe
eltarod said:
I've been trying for two days and can't make it...
I have a Desire HD with 2.3.5, sw 3.12.207.1 and Sense 3.0 all stock. It isn't branded and it has S-On with H-BooT 2.00.0027
The thing I want to do is install CWM and have the ability after to flash ROMS. As I read I must first unlock the bootloader and then flash CWM correct?
The problem is that when I start the HTCDev instructions I get this:
C:\tools>fastboot oem get_identifier_token
< waiting for device >
...
FAILED (status malformed (1 bytes))
finished. total time: 0.023s
I have HTC Sync, Android SDK, Java. I know that the phone is recognised in windows when working and in fastboot cause it always finds it with either "adb devices" or "fastboot devices". What am I doing wrong?
I tried Easy Ace Root Tool but still the same happens. Some more info if this helps. In the HTCDev steps it says that I should update with the RUU. When I try that (tried them all) I get this: ERROR [191] ROM IS NOT SUPPORTED
Any ideas??
Click to expand...
Click to collapse
You are in hboot USB plug And not in fastboot usb. And you Need To update your hboot
i am trying to unlock my bootloader on my "T-Mobile G2", the HTC G2 (Vision), using my macbook pro (OS 10.8.5) and the newest version of fastboot (i just downloaded adt-bundle-mac-x86_64-20131030.zip and the files were right there).
on my HTC G2 screen it says FASTBOOT USB all nice and waiting for me...
i am in my platform-tools folder where fastboot lives and i type:
$ ./fastboot oem get_identifier_token
and it says:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
but WHY??? arrrrrgg.
$ fastboot devices
shows the phone is there.
my firmware is Android 2.3.4.
i was just reading that because i have HBOOT 0.82 it wont work... god... so how do i upgrade HBOOT? why is this such a pain?
Hi guys,
Basically I'm in a bit of trouble trying to get my one x back to stock. After running the RUU for my phone, it exited with an error saying that the device suddenly could not be found anymore. After this I tried to run the RUU again but now the error message about the battery level being below 30% came up. Anyway, after this I tried unlocking my phone again to go back to a custom rom and at least have a working phone however I can't do anything through fastboot because no matter what command I type in, it keeps telling me the following:
C:\fastboot>fastboot getvar version-main
getvar:version-main FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
C:\fastboot>fastboot oem readcid
...
FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
I checked the usb connection and the device seems to be recognized:
C:\fastboot>fastboot devices
HT24CW105437 fastboot
Could someone help me as to how to move forward? I also can't seem to charge my phone. I left it on AC charging for about an hour in fastboot mode and tried running the RUU again but the same battery level message came up.
Thank you!
uxyyy
For CID command is:
Fastboot getvar cid
For flashing:
Fastboot flash boot boot.img
Fastboot flash recovery recname.img
Cache clearing:
Fastboot erase cache
Sent from my HTC One X using Tapatalk 2
Hey,
Yeah I know the commands but unfortunately I wasn't kidding when I said I can't do anything via fastboot. :/
Even just trying to get the CID or flashing the boot.img returns:
C:\fastboot>fastboot getvar cid
getvar:cid FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
C:\fastboot>fastboot flash boot boot.img
sending 'boot' (4862 KB)...
FAILED (command write failed (No such file or directory))
finished. total time: 0.001s
So there must be something else that's broken.
Try this..Download fastboot files again,put phone in fastboot..And on fastboot files hold shift and right click and open command prompt here..
Sent from my HTC One X using Tapatalk 2
Still the same problem.
Also, I left my phone to charge overnight and got the green LED to light up however when trying to run the RUU it still tells me that the battery level is below 30%.
Any fastboot commands still return the exact same error message as before. I honestly don't know what I could do atm.