Related
Hello everyone,
I think this might be my first post here.
Anyways, I have a rather depressing problem. I have my phone rooted running cm 6.1, and when i was about to go to sleep last night, it randomly started to reboot. At first i did not think anything of it because i have had my phone do this several times with cm. But then i became more concerned, it would go into a boot loop at the splash screen (htcEVO4g). Once again, i have had this happen before and i would do a wipe and reinstall the rom, but this time it did not work. I could not get into recovery. I am able to access only the boot loader.
So, i tried to install the stock pc36img. Now when i start my phone, it vibrates 5 times followed by the flashing green led. it also does this when i try to go into recovery. I am still able to get into the bootloader.
i tried doing the ruu thing, and different pc36img
I just got back from the sprint store. After waiting 3 hours, they were not able to fix it. I had told them it was rooted and everything.
If there is no way to fix it, is there at least a way i can turn s-on? That way, i can send it back to sprint.
That is odd. As far as I know, if you used unrevoked forever at any point, the only way to get s on is to flash the unrevoked s on tool, using recovery. But you don't have recovery. If I were you, I would use your computer to format your sd card to fat 32 ( after backing it up, of course) , then put a pc36img on your sd card, and try to flash again using the bootloader. You could also try putting a pc36img of amon ra recovery on your sd card, and flashing that with the bootloader. Maybe you can get recovery back, and flash a rom, or the s on tool. Hope you get it worked out.
Sent from my PC36100 using XDA App
If I were you I would try the newest pc36img.zip and if that does nothing a pc36img.zip of Amon ra. If that doesn't work go to the last link in my sig about splash screens. In that tut I give, I say how to manually run an ruu. Use the pc36img.zip with the fast boot commands from the thread. Hope this helps.
i tried formatting the sc card, and that did not do anything. How can i connect my phone to adb?
marzban123 said:
i tried formatting the sc card, and that did not do anything. How can i connect my phone to adb?
Click to expand...
Click to collapse
Just Download the android SDK and follow the steps. There are some pretty excellent tutorials on XDA and other sites that will walk you through the whole process.
I want to weigh in here for just a moment. There is no way your phone is completely botched, unless it has experienced physical damage (including any overheating). By the way, you running any SBC kernels?
I would look into learning your way around ADB, I think it's a necessary tool for anyone who wants to flash and alter their android phones, unfortunately things have become so easy that many out there haven't had to learn these tools and how to use them.
Seriously, go mess with ADB, I am sure you can get it running again.
Some good info here http://forum.xda-developers.com/showthread.php?t=865204 on using ADB and other methods that may help you.
marzban123 said:
I had told them it was rooted and everything.
Click to expand...
Click to collapse
ouch... they should give you new phone for being honest
ok, so i connect the phone, and in device manager i see "Android Bootloader Interface"
i opened up command prompt, and tried to push a file to the phone and i got this
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Andrew>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb push PC36IMG.zip /sdcard/
error: device not found
C:\android-sdk-windows\tools>
you sure your usb cable is good? id run the RUU to go back to stock & unroot you. then start over from scratch.
i just tried a different cable. No luck
I have already tried a stock ruu, that still does not let me get into recovery or turn s-on
your sorta up ****s creek here if you told sprint you rooted. they probably flagged your account.
is your sd card good? try another, fully formatted for fat32 only. then try the s-on flashable zip. that's all i can think of for you to do. if you need another evo, im sure you can pick one up for cheap on craigslist.
nobody ever took my information
Is there an s-on flashable zip?!?! where can i find it? i have searched before with no luck
first of all, adb doesnt work in bootlaoder. select fastboot, then plug in. you should see fastboot usb come up on the phone. now try using fastboot commands instead. not sure where to download fastboot commands. i have the mac ones if you need them. then do this
with the pc36img.zip ON YOUR COMPUTER:
after flashing s-on tool http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
fastboot oem rebootRUU
you should see a black screen with silver htc lettering
fastboot flash zip pc36img.zip (do this command with the pc36img.zip in the same directory as fastboot)
you should see a green bar appear under htc and a bunch of lines on the comp. make sure it successfully completes, then type:
fastboot reboot
done.
but make triple sure you are s-on first.
thank you very much, that makes things ALOT clearer.
I am still a huge noob to this stuff so i need to ask you some silly questions:
i found out the commands for fastboot in a wiki,
http://wiki.cyanogenmod.com/index.php?title=Fastboot
but i dont really understand how to use them. can someone please give me a little clarification.
well, first check your sdk and see if you have fastboot.exe. i know the mac one doesnt come with it. if you dont google it. if you do, cd to the directory (hold shift and right click in the folder. select open command prompt here) and boot phone into fastboot. make sure it is in fastboot usb mode. then do the commands.
i have the fast boot exe and i am in command prompt.
when i say i am a noob, i really mean it.
for example, when i try a simple command like checking the serial number, i will input
c:\android-sdk-windows\tools>fastboot <-s>
or
c:\android-sdk-windows\tools>fastboot -s
or
c:\android-sdk-windows\tools>fastboot <serial number>
it says
the syntax of the command is incorrect.
i really dont know how to use this stuff
ok forget the last post,
i figured that out
what partition do i want to flash and with what file?
No partition just use the pc36img.zip in ruin more and type fastboot flash zip pc36img.zip.
Sent from my PC36100
C:\android-sdk-windows\tools>fastboot flash zip PC36IMG.zip
sending 'zip' (171727 KB)... OKAY [ 30.475s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 30.477s
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
i researched the "(remote: not allowed)" error message, and everyone says its cause when the phone is set to s-on. However, on my phone it says s-off.
what the heck?
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!
I am in really desperate need of help! I know many see me as a noob and a new user or whatnot but I just had a major accident with my HTC Desire with U.S Cellular. The phone is about 14 months old now but it is working like new still because I take good physical care of it.
Anyways, today I wanted to install a new Rom with Sense 3.0 from my current 2.2 Froyo from RUU. The Thread for the rom I wanted said that the CM7 r2 partition table was recommended and so I went on following the aplharev site were I had to download the CM7 r2 hboot.img (I already had S-Off and Hboot 1.06.0000 with Root)
I went my way booting into Hboot and then Fastboot on my pc. I used Fastboot commander 1.51 and made the flash for the hboot using CM7 r2. This however, is when the problem resulted. After I flashed my Hboot from the previous 1.06.0000
to the new CM7 r2, my phone screen instantly Blacked out. It was as if it died. Then I figured it may be part of the partitioning, so I Deleted my cache, boot, and entire system (I figured that with a nandroid backup, I was invincible... I was very wrong...)
After everything started getting worse, I figured it was time to reverse back to my nandroid. I clicked the "Flash all/Restore Nand" button but instantly I was given:
STARTING FLASH OF NANDROID FILES.
Flashing "boot" - PLEASE WAIT.
"boot" flash FAILURE.
FLASH OF NANDROID FILES FAILURE - "BOOT" FAILURE.
This is were I knew I was... finished... I can't use my phone as the screen is pitch black, the system is deleted because of my "Genius" self, and because the screen is black as if turned off, I can't access the "Recovery" since I am blind of my actions. I tried looking and spending literally 5-6 hours searching forums, downloading, attempting, and of course, failing.
The only thing I CAN ACCESS is Fastboot. When I power my phone, it vibrates with a dead black screen. If i power on with Volume down following power button again, I can access fastboot on my PC.
If anyone out there with a good heart can help me, that would be the best thing ever for me! I feel soo depressed now because this is my everyday phone and now... I am phoneless... The sooner I get help, the better. I need to know the possibilities to fix this issue :0
Additional Info:
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
Nandroid folder found.
Nandroid "boot" file found.
Nandroid "data" file found.
Nandroid "system" file found.
All nandroid files set - Restore button enabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 6.93.9999.
Radio version: 2.15.00.11.16.
Main software version: 2.11.573.5.
cid: utsi_001.
cpld: none.
product: bravoc.
mid: pb9940000.
security: off.
build-mode: ship.
I think Alpharev meant to be for Bravo not Bravoc, flash downgrade reboot fastboot and flash RUU, hope this helps
Sent from my HTC Desire using XDA Premium App
Alright. So how would that be in a step by step situation?
How do I flash the RUU? I'm sorry but I am still a noob learning
Jesus. Why do you cdma users keep doing this?
You're going to be lucky if you haven't bricked your device.
All you can really do is see if you can ruu. Of course, the Rom won't fit in the cm7 so you're going to have to hope your ruu's hboot will be a higher version. If not you'll have to flash the downgrade image first.
Best of luck
Sent from my HTC Desire using Tapatalk
Ok then. I have downloaded the HTC 2.2 Froyo RUU from U.S Cellular linked by HTC website but now how do I flash it? It is an exe file. I am still trying to understand how to do all this :0 I am really sorry for annoying anyone
It runs from a windows pc. Put your phone in Fastboot (from off hold back and press power) connect usb and run ruu
Sent from my HTC Desire using Tapatalk
Alright. I powered on phone into Hboot then fastboot (Windows 7 makes the USB detection sound when fastboot is detected). I am still blind since the black screen shows no image. Anyways, I started off running the "HTC Desire Froyo 2.11.573" RUU that I downloaded from HTC/U.S Cellular website (171Mb) and then I clicked the "Next" screen following up by another "Next" and then the big rectangular box saying "Verifying Information on your Android phone. Please wait..." but after about 30 seconds I get a error:
"ERROR [170]: USB CONNECTION ERROR
This error message will appear when the Android phone is not correctly connected to the host PC. It might be a USB connection problem or a PC USB driver problem. Make sure the Android phone is connected to the host PC correctly and/or check if the PC driver matches the Android phone."
I have Fastboot Commander V.1.51 running and it detects usb just fine as I can display the system info with it, so I don't see how the RUU is not finding the Desire under Fastboot.
So then I flashed the hboot with the "bravo_downgrade.img" from AplhaRev website
like you guys stated and then re approached the situation with the same process. Still keep getting the errors of "ERROR [170]: USB CONNECTION ERROR"
I don't know what to do now... Any additional advice? Am I on the right track? Maybe I'm missing something? If all goes or seems worse, I do have a school friend with the SAME HTC Desire CDMA with U.S Cellular carrier like me. He is updated with Froyo 2.2 and his phone works just as fine as mine once did before my idiot self caused this mess. He however, has no root nor S-Off.
So what can I do now? Gold card attempt maybe? I have not read anything about this but I only heard that it helps recover "bricked" Desire that is SLCD. Another slight problem, I don't know if my Desire is SLCD or not... I know only that it is CDMA *I know, frustrating dealing with a noob like me*.
It sucks not having a phone. 1 day already. I can only have patience until I finally fix my phone with the help of a good heart.
Power to fastboot power and back button..
Will fastboot recognize your phone?
Fastboot devices
If you get long number that is a good sign
You must run RUU or any fastboot command while you are in fastboot mode, not hboot
Should be long number
Sent from my HTC Desire using XDA Premium App
Ok still no go. I ran what you said "fastboot devices" using Fastboot Commander V.1.51 and got the following:
-----------------------------------.
Running fastboot command - PLEASE WAIT.
###Calling fastboot with: devices###
HT0BTHM01381 fastboot
********************************
After I got this, I ran the RUU again, and still getting "ERROR [170]: USB CONNECTION ERROR"
fastboot see your device that is good
extract rom.zip from ruu (see video in step 7 of bortak guide)
then
1 fastboot oem rebootRUU
2 fastboot devices - if you see your htxxxxxxxxxxxx no. then go to step 4
3 if not pull battery out anf boot to fastboot and start from step 1 again
4 fastboot flash zip rom.zip
5 fastboot reboot-bootloader
Alright then. Sorry for late reply. I had an intense amount of much school work to get done from Calculus and other major subjects but I managed to follow your directions and the RUU just won't detect the darn phone! Keep getting USB Error not stop. So I decided to use my brain.
I extracted the ROM from RUU in the "%TEMP%" folder and kept it in "MY Documents". After, I took a deeper look into the Rom using Winrar, and found this file "hboot_8x50_1.06.0000.img". I wondered... Hm.... What if I extract it from Rom, and flash it into my current 6.93.9999 Hboot? So I did.
After, the minute It was flashed, WOLA! I have a working SCREEN AGAIN! I can SEE! Now however, a few things have changed.
SPL/hboot version: 1.06.0000.
Radio version: 2.15.00.11.16.
Main software version: 2.11.573.5.
cid: utsi_001.
cpld: none.
product: bravoc.
mid: pb9940000.
security: on.
build-mode: ship.
My S-ON is back and I have no boot screen what so ever. EX: If I power off phone and back on, it INSTANTLY goes into hboot screen. Doesn't even bother with an "HTC LOGO". *May be because I deleted all the partitions of boot, system, ect.
Moving on, tried running RUU again. Not a single working method! USB ERROR.
Then I tried flashing the "rom.zip" extracted from the RUU using Fastboot Commander but after about 1 minute I get this:
********************************
###Calling fastboot with: flash zip C:\Users\Jona\Downloads\HTC Desire Froyo 2.11.573 ROM\PB99IMG.zip###
sending 'zip' (167226 KB)... OKAY [ 28.390s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 53.580s
********************************
Any idea's what to approach next? I am SUPER happy I can see my screen again, but I must repair what is broken first. Should I take action to "S-OFF" again?
I am trying to think now and here is what I suppose I should/can do.
S-Off then somehow flash Clockwork Mod into Recovery and then from there, Flash back my Nanodroid through Recovery. Would that work? What do you all think?
Why did you flash hboot only? Whole rom flashing via pb99img method not working?
For s-off you need system booted, you can't s-off from fastboot/hboot. Youre booting there because no boot and recovery been flashed. Try to flash it with goldcard via pb99img zip in root of your sdcard?
Sent from my HTC Desire using XDA Premium App
Aww man really? I totally forgot about that... I tried copying the pb99.img on my SD card and now that I can see, attempted waiting in hboot for the files to load but after they did, I't quickly should something like "SD Checking: PB99DIAG.zip"
But then it said
No image file.....
No image file.....
No image file.....
And it returned to hboot.
At this point, I started losing hope. I wanted to cry... What could I do?! No phone for 3 days.... I was a failure...
But then, only then, I took a break and powered off phone. Looked around my shallow apartment and thought, what now...
5 minutes I returned to the phone, took SD card out, blew on it, inserted it back in my Desire, and powered on into Hboot, waited again for the *Miracle* to happen, and WALA! It started loading the zip?!!! WHAT?! NO WAY! Heart pounding I eagerly stared at the phone. "Click Vol + Start Update" I clicked!
Then the 6 steps for updating appeared! 1 = OK 2 = OK
10 minutes later, I booted and back to normal From here, I can S-OFF, Get back Recovery ClockMod, and restore Nandroid. Thanks guys for assisting me well I have never been happier! I shall give you all Thumbs Up and close thread.
Out of curiosity, I should never bother to flash the Hboot EVER again correct? Only GSM phones can do this... So as a CDMA user, I should only flash roms under recovery and leave the hboot radio, recovery, and hboot alone?
Glad to hear that... Take this as warning you can flash anything what you want but only one condition: all stuff MUST be designed for Desire CDMA
Sent from my HTC Desire using XDA Premium App
Alright. I will just stay away from flashing Radio, Hboot. No reason to do so anyways :7 Thanks again!
Sent from my HTC Desire (CDMA)
Definitely as all radios and hboots are gsm and would usually brick your device. You've been very lucky
Sent from my HTC Desire using Tapatalk
I know. I am simply grateful and glad it is over. But hey, I learned soo much more about all this hboot and fastboot because of this. Good experience ^.^ Oh, one final noob Question. How to close the thread as solved? Using XDA Premium app
Sent from my HTC Desire (CDMA)
Jonicraw said:
I know. I am simply grateful and glad it is over. But hey, I learned soo much more about all this hboot and fastboot because of this. Good experience ^.^ Oh, one final noob Question. How to close the thread as solved? Using XDA Premium app
Sent from my HTC Desire (CDMA)
Click to expand...
Click to collapse
Leave it as it maybe somebody will learn from it
Sent from my HTC Desire using XDA Premium App
kotag82 said:
Leave it as it maybe somebody will learn from it
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Yes, however, there is no harm in going to advanced edit on post one and putting [Solved] at the begining of the thread title
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
echoedge said:
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
Click to expand...
Click to collapse
You're going to need to upgrade your device to the latest available RUU version (4.67.651.3), unlock your bootloader with HTCDev, flash a custom recovery, root your device, and then downgrade your misc partition (again). That should normalize your device (if one of the earlier steps doesn't do it).
echoedge said:
Hey everyone.. any help on this would be greatly appreciated, has caused a lot of stress.
The phone was successfully downgraded to hboot 2.10 from hboot 2.18 a while back, s-off was achieved, all things were working perfectly with gingerbread roms and the sort.
I decided I wanted an ICS rom as my main boot-up, but was having difficulties installing it and finding a cooperable kernal/radio to get it to flash..
(looking back this probably wasn't the real issue as to why the ROM wouldn't load, and this base ICS rom that I was drawn to was not at all the one I should have been getting conclusion/direction from)
Anyways, I see now that I was trying to flash an Evo V 4G ICS rom, and in install this rom led me to update an EVO V 4g radio.
This was the rom I was trying to install:
http://androidforums.com/evo-v-4g-a...om-harmonia-3-17-17nov12-ics-sense-3-6-a.html
And in reading up on that lead me to this link
http://androidforums.com/evo-v-4g-all-things-root/648747-update.html
where I flashed the 'OTA_Shooter_ICS_35_S_Sprint_WWE_VM_1.14.652.0-1.13.652.2_release_291083f0wrax77ry0w073p' update.
Soon thereafter I found myself back with S-ON (previously was s-off), with no roms able to install.
I can get adb/sd functionallity in fastboot/hboot and have amonRA 2.3 installed as my recovery that I can get too.
In fact, in amonRA gingerbread roms say they install correctly, and I also have a nandroid backup of 'system' 'restore' 'data' 'cache' 'boot' which I believe I performed before the radio update.
They both say installed/updated correctly (new rom flash/nandroid), but upon rebooting the system, the evo 4G just vibrates 3 times, flashes its LED, and that's it. Blank screen - nothing.
Please, any help on this?
To sum it up:
I flashed the above incompatible radio in attempt to get a rom working which on foresight was for the EVO V 4G instead of the EVO 4G.
Upon doing this my hboot stayed the same (2.10), but it reverted my from S-OFF back to S-ON.
Confusing enough my radio on the hboot menu says '2.15.00.08.08', which is the latest EVO 4G radio according to here:
http://forum.xda-developers.com/showthread.php?t=715485
Hboot 2.10 USB boots fine with vol down + power, have ADB capabilities to it, and recovery boots fine to amonRA.
Much thanks in advance, I really want to get this running again!
Click to expand...
Click to collapse
have you tried running a RUU yet? it should restore your phone back to stock radio hboot system and a few other things
Okay, I will try to get the latest RUU up and running.
I see them listed here
http://wiki.rootzwiki.com/HTC_EVO_4G_Downloads
but all the links are dead -- will look for a mirror right now.
I see there are three different methods for flashing the RUU - an update.zip I can flash in amonRA, a PC36IMG I can flash in hboot and an radio.img file I can do in fastboot adb..
I also find a .exe file
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe
but it's an .exe file?
and they all seem to differentiate in size from a like 10mg PC36IMG to a 220mb version as the .exe is..
so many different choices, what's my best option for the situation
Thanks a bunch for the quick replies!
echoedge said:
Okay, I will try to get the latest RUU up and running.
I see them listed here
http://wiki.rootzwiki.com/HTC_EVO_4G_Downloads
but all the links are dead -- will look for a mirror right now.
I see there are three different methods for flashing the RUU - an update.zip I can flash in amonRA, a PC36IMG I can flash in hboot and an radio.img file I can do in fastboot adb..
I also find a .exe file
RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed.exe
but it's an .exe file?
and they all seem to differentiate in size from a like 10mg PC36IMG to a 220mb version as the .exe is..
so many different choices, what's my best option for the situation
Thanks a bunch for the quick replies!
Click to expand...
Click to collapse
The RUU is run from the PC while you're in fastboot mode. That'll work fine. Or you can use the PC36IMG from here and flash in HBOOT (bootloader).
Cool, thanks.
Okay, I downloaded the .zip and .exe-- ended up using Captain's link to HBoot the RUU by renaming it to PC36IMG.zip
So then booted up in hboot, it detected the PC36IMG -- went through the list.. check, check, check, check, completed and done.
Rebooted the phone, now instead of just a black screen with the 3 vibrations and led flashes, it goes to the "EVO 4G" white screen loader, then 5-10 seconds later, goes blank and does the 3 vibration thing again.
Back to HBoot.
Noticed the only change was the radio oversion now says 2.15.00.11.19 now
So now my next step is to do the HTCDev method I assume?
Fastboot USB'd- phone detected by W7 just fine.
I type in 'fastboot devices' and it detects the phone and gives the serial number, so fastboot seems to be in working order.
I then type in the command 'fastboot oem get_identifier_token'
and am getting the error
C:\Android>fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY [ 0.008s]
finished. total time: 0.008s
Click to expand...
Click to collapse
and seem to be stuck here.. tried re-installing my htc sync, redid the get_identifier_token command and the same error persists.
Any suggestions?
echoedge said:
Cool, thanks.
Okay, I downloaded the .zip and .exe-- ended up using Captain's link to HBoot the RUU by renaming it to PC36IMG.zip
So then booted up in hboot, it detected the PC36IMG -- went through the list.. check, check, check, check, completed and done.
Rebooted the phone, now instead of just a black screen with the 3 vibrations and led flashes, it goes to the "EVO 4G" white screen loader, then 5-10 seconds later, goes blank and does the 3 vibration thing again.
Back to HBoot.
Noticed the only change was the radio oversion now says 2.15.00.11.19 now
So now my next step is to do the HTCDev method I assume?
Fastboot USB'd- phone detected by W7 just fine.
I type in 'fastboot devices' and it detects the phone and gives the serial number, so fastboot seems to be in working order.
I then type in the command 'fastboot oem get_identifier_token'
and am getting the error
and seem to be stuck here.. tried re-installing my htc sync, redid the get_identifier_token command and the same error persists.
Any suggestions?
Click to expand...
Click to collapse
What does your bootloader screen say? S-ON or S-OFF? What are your HBOOT and radio versions? Because it doesn't sound like the zip file finished installing. It should reboot once during the process, and then continue on flashing for around 10 minutes. Did it do that?
Captain_Throwback said:
What does your bootloader screen say? S-ON or S-OFF? What are your HBOOT and radio versions? Because it doesn't sound like the zip file finished installing. It should reboot once during the process, and then continue on flashing for around 10 minutes. Did it do that?
Click to expand...
Click to collapse
Yes, it did that.. went through all the checkmarks with success down to WiMax I believe was the last one.
It did reset once during the process.. I remember because I was confused, didn't know if it turned off or what, then it turned itself back on, continued with the process and installed the rest of it.
The only thing that changed was the radio version from 2.15.00.08.08 to 2.15.00.11.19 after the RUU/Hboot/PCIMG36 img flash.
Bootloader says... I'll type it all out
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010, 12:07:00
Click to expand...
Click to collapse
Should I try re-flashing again using the .exe file, does everything seem right on the bootloader?
Okay, I think I might have put the wrong PC36IMG file directing towards 11.19
(too many files in my Downloads folder )
Lemme try again.. I see the radio version should be 12.19, which is what Captain's link provided
Okay, I used the proper 12.19 PCIMG36 file this time,
now the bootloader says
*** LOCKED (OOW) ***
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.12.19
Dec 21, 2011, 12:50:32
Click to expand...
Click to collapse
Looks like it's back to its original state
I'm assuming it works now, still updating as I type this, will try the token and the other steps to get it back down to 2.10 with s-off and back to where it should be
Thanks for the help guys.
I'll let you know if it works, I'm assuming it will and I know the steps to perform at this stage.
One more question though which got me into this original mess,
do I need to update the kernal/radio/anything in order to get an ICS rom loaded on the Evo 4G?
Or was that issue mute just because I was trying to flash an Evo V 4g/incompatible rom?
Thanks again!!
Okay.. all is going well, but there seems to be something strange going on, don't think it's normal.
After I flashed superuser, I restarted it and it once again went to the black screen with the 3 vibrations.
Took out the battery, put it back in, powered on. Booted to sprint stock.
Enabled USB debugging/disabled Fast Boot.
Then put the USB in, and the notification sound popped up on my computer detecting the phone.. but the phone itself did nothing. It isn't even charging (battery indicator at top stays still).. my settings are set to 'charge only' and 'pop-up and ask me' on connection settings.
Pressed power button, went to restart, and it powered down and again went to black screen with the three vibrations.
Took the battery out, put it back in, turned it on.. went back to sprint stock.
Plugged USB cable in again-- same thing, no pop-up on phone that it's connected, although my computer notifies me that it is.
Tried on two different computers with different USB cables, no luck.
ADB shell doesn't work, no devices found if I try it anyways.
Help
Thanks
echoedge said:
Okay.. all is going well, but there seems to be something strange going on, don't think it's normal.
After I flashed superuser, I restarted it and it once again went to the black screen with the 3 vibrations.
Took out the battery, put it back in, powered on. Booted to sprint stock.
Enabled USB debugging/disabled Fast Boot.
Then put the USB in, and the notification sound popped up on my computer detecting the phone.. but the phone itself did nothing. It isn't even charging (battery indicator at top stays still).. my settings are set to 'charge only' and 'pop-up and ask me' on connection settings.
Pressed power button, went to restart, and it powered down and again went to black screen with the three vibrations.
Took the battery out, put it back in, turned it on.. went back to sprint stock.
Plugged USB cable in again-- same thing, no pop-up on phone that it's connected, although my computer notifies me that it is.
Tried on two different computers with different USB cables, no luck.
ADB shell doesn't work, no devices found if I try it anyways.
Help
Thanks
Click to expand...
Click to collapse
Just as I suspected. Your misc partition is corrupted, causing your sd card to not be recognized, and ADB to be broken. I've been there before, and this is fixable. First, to get your SD card working, you'll need to boot into fastboot (so that your display reads FASTBOOT USB), and from the command prompt on your computer, from the folder where your fastboot.exe resides, type the following command (taken from here - thanks to Calkulin):
Code:
fastboot oem enableqxdm 0
After that completes, boot into recovery. I'd like to check and see if adb will work in recovery - that'll be easier than the alternative, which is flashing a ROM with Wireless ADB enabled, and using those commands to flash the misc partition from the computer. After you get recovery booted, type
Code:
adb devices
at the command prompt and let us know if your device shows up in recovery mode.
Tried going back into hboot.. plugged it in,
was detected, but had to re-install drivers on my w7 machine I noticed.
after i figured out that hboot usb worked, went to recovery, went to restart now.
went to black screen and noticed it is vibrating 5 times now (before it was 3)
took out battery, turned back on, back to sprint stock. still no usb capabilities within the rom.
btw my bootloader now says
** unlocked **
s-on
hboot-2.18.0001
radio-2.15.00.12.19
also,
tried going back into recovery, and re-flashed the superuser file. installed fine.
this time instead of going to 'reboot now' went to shut down.. it shut down fine. I turned it back on, turned on fine.
It only seems to be doing the black-screen and 5 vibrations when I reboot.
Tried plugging it in again to pc, checked settings - nothing.
Am confused now, not sure what's wrong
EDIT:
okay, just read Capt. Throwback's reply AFTER posting this, will give that ago. Thanks CT
Captain_Throwback said:
Just as I suspected. Your misc partition is corrupted, causing your sd card to not be recognized, and ADB to be broken. I've been there before, and this is fixable. First, to get your SD card working, you'll need to boot into fastboot (so that your display reads FASTBOOT USB), and from the command prompt on your computer, from the folder where your fastboot.exe resides, type the following command (taken from here - thanks to Calkulin):
Code:
fastboot oem enableqxdm 0
After that completes, boot into recovery. I'd like to check and see if adb will work in recovery - that'll be easier than the alternative, which is flashing a ROM with Wireless ADB enabled, and using those commands to flash the misc partition from the computer. After you get recovery booted, type
Code:
adb devices
at the command prompt and let us know if your device shows up in recovery mode.
Click to expand...
Click to collapse
I remember having to do that command because my SD card wasn't detected before I flashed the RUU and making this thread.
This is because it was very noticable my SD card wasn't being detected.. any PC36IMG file in hboot wouldn't be detected, and recovery wouldn't mount nor find an sd card. After doing that command above the SD card worked.
But anyways, ADB worked in hboot and I successfully did that command.
ADB did not work in recovery unfortunately.
Are you sure it's an issue of my sd card being detected? My misc partition is probably corrupted I assume which is giving me these errors, but SD card even before doing that above command in hboot and recovery worked fine (was able to browse my sd card/mount it.. flashed superuser on it. I only say that because before when I had to do that command to get the SD working in the beginning of all this the SD card had no access to anything at all, and in recovery would give me a can't mount mnt/mmc*** (or something like that).., that's when I googled the error and found that solution that Calkulin provided.
But i'm not sure.. what are my options now?
echoedge said:
I remember having to do that command because my SD card wasn't detected before I flashed the RUU and making this thread.
This is because it was very noticable my SD card wasn't being detected.. any PC36IMG file in hboot wouldn't be detected, and recovery wouldn't mount nor find an sd card. After doing that command above the SD card worked.
But anyways, ADB worked in hboot and I successfully did that command.
ADB did not work in recovery unfortunately.
Are you sure it's an issue of my sd card being detected? My misc partition is probably corrupted I assume which is giving me these errors, but SD card even before doing that above command in hboot and recovery worked fine (was able to browse my sd card/mount it.. flashed superuser on it. I only say that because before when I had to do that command to get the SD working in the beginning of all this the SD card had no access to anything at all, and in recovery would give me a can't mount mnt/mmc*** (or something like that).., that's when I googled the error and found that solution that Calkulin provided.
But i'm not sure.. what are my options now?
Click to expand...
Click to collapse
You're going to need to flash a ROM with Wireless ADB enabled, or manually use Terminal Emulator to flash the misc partition, as per the instructions in my "Downgrade HBOOT" thread. If you still have the flash_image and mtd-eng.img on your SD card, Terminal might be the easiest way to do it (hopefully it'll let you). If not, we'll have to go the Wireless ADB route, as I did here.
Okay, i'm not sure if it worked or not.
I su'd into terminal and did the commands.
the terminal froze though so I had to take the battery out, but that was after I pressed enter on the three commands..
I noticed in my bootloader it says *** LOCKED ***
and it also says I'm S-OFF..
Now I'm trying to flash over the 11.19 radio PC36IMG.zip but now it seems the bootloader is not detecting my sd card..
I tried the command to get sd working again. That worked okay.
I booted into recovery, and my sd card is mounted and in there I can browse my SD card contents.
But in hboot it tries to detect the PC36IMG.zip and just passes it by.
Did the misc partition commands work properly, what's messing with it now?
I'm still able to ADB/fastboot USB in hboot by the way, it just isn't detecting my PC36IMG file.
Should I try to manually do it, or am I missing something?
Also I booted into the sprint stock rom, plugged in the USB and now that functionality is working fine.. prompts up, charge only, etc.
Seems I'm almost there... :fingers-crossed:
echoedge said:
Okay, i'm not sure if it worked or not.
I su'd into terminal and did the commands.
the terminal froze though so I had to take the battery out, but that was after I pressed enter on the three commands..
I noticed in my bootloader it says *** LOCKED ***
and it also says I'm S-OFF..
Now I'm trying to flash over the 11.19 radio PC36IMG.zip but now it seems the bootloader is not detecting my sd card..
I tried the command to get sd working again. That worked okay.
I booted into recovery, and my sd card is mounted and in there I can browse my SD card contents.
But in hboot it tries to detect the PC36IMG.zip and just passes it by.
Did the misc partition commands work properly, what's messing with it now?
I'm still able to ADB/fastboot USB in hboot by the way, it just isn't detecting my PC36IMG file.
Should I try to manually do it, or am I missing something?
Click to expand...
Click to collapse
If you're back to S-OFF, you might be okay. Try flashing the 4.67 PC36IMG.zip in HBOOT again. After you do that, you should still be S-OFF, if everything is working properly, and hopefully everything else will be working too.
It's also possible that the misc partition flash was incomplete. Since you're now S-OFF, and presumably ADB is working, you should be able to run the commands over USB.
Okay, I had to put in a bigger SD card for it to detect the PC36IMG to detect- installed perfectly.
Also had to reflash amonRA recovery.
I was already S-OFF for whatever reason so yup, after that I was good to go! :good:
Booted to recovery, made a backup, wiped data/factory reset, an flashed an ICS rom. Just booted up, everything is working great
Thanks a bunch everyone (esp Capt. Throwback) for getting this resolved quick and painlessly
Am very relieved to get this working once again as normal, wasn't sure if I would be able
Thanks again!!
Okay, i have a problem with an old phone, I believe its perm bricked, but wanted to check...
It is currently S-ON, and i have no way to turn off, its has no operating system, and the screen does not turn on. however i can turn the phone on, it does vibrate, and i can use fastboot commands.
Anyone got any idea's or shall i bin it?
C:\and\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.80.0000
(bootloader) version-baseband: 4.06.00.02_2
(bootloader) version-cpld: None
(bootloader) version-microp: 051d
(bootloader) version-main: 1.21.405.2
(bootloader) serialno: **************************
(bootloader) imei: ********************
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6175d920
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.006s
C:\and\sdk\platform-tools>
It's not a permanent brick if you can send and receive commands...
Your other posts have been for desire s, are you sure you're posting this in the right place? This is desire (bravo) forum.
If it's definitely a desire, look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
If it's actually a desire s, search over there, although looks like you've tried running an ruu before
eddiehk6 said:
It's not a permanent brick if you can send and receive commands...
Your other posts have been for desire s, are you sure you're posting this in the right place? This is desire (bravo) forum.
If it's definitely a desire, look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
If it's actually a desire s, search over there, although looks like you've tried running an ruu before
Click to expand...
Click to collapse
Yep got the Desire S because i couldn't fix this one years ago.
This is the HTC Desire (Bravo), it was s-off, i tried turning it back to factory settings, IE: S-ON, and a RUU on it, and then it ended up not booting up and the screen stop turning on, i was thinking I may have put the wrong RUU on it, as I believe I was drunk at the time (future warning to all, never flash your phone when drunk!)
When i try to run a RUU, i get errors, normally error with Signature Error. (its a Vodafone locked phone) I have used the RUU for Vodafone UK (latest).
mike989e said:
Yep got the Desire S because i couldn't fix this one years ago.
This is the HTC Desire (Bravo), it was s-off, i tried turning it back to factory settings, IE: S-ON, and a RUU on it, and then it ended up not booting up and the screen stop turning on, i was thinking I may have put the wrong RUU on it, as I believe I was drunk at the time (future warning to all, never flash your phone when drunk!)
When i try to run a RUU, i get errors, normally error with Signature Error. (its a Vodafone locked phone) I have used the RUU for Vodafone UK (latest).
Click to expand...
Click to collapse
sounds like you might have used an SLCD RUU form AMOLED or something like that, which is why you can't see screen.
so can you still get to bootloader screen (turn it off, then vol down + power)? post the output.
are you on a custom hboot?
can you still get into recovery and simply flash another rom just to get it to boot up at least?
you can also try flashing another recovery, recommend 4ext (see my sig), flash it through fastboot, guide if you haven't already set it up. then try to boot into it, full wipe and flash a new rom.
otherwise, if you are looking to get it to s-on and sell it:
look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
Click to expand...
Click to collapse
post the exact output if you're still getting errors. however i'm pretty confident it was never a "permanent brick" and you can get it to boot up
eddiehk6 said:
sounds like you might have used an SLCD RUU form AMOLED or something like that, which is why you can't see screen.
so can you still get to bootloader screen (turn it off, then vol down + power)? post the output.
are you on a custom hboot?
can you still get into recovery and simply flash another rom just to get it to boot up at least?
you can also try flashing another recovery, recommend 4ext (see my sig), flash it through fastboot, guide if you haven't already set it up. then try to boot into it, full wipe and flash a new rom.
otherwise, if you are looking to get it to s-on and sell it:
post the exact output if you're still getting errors. however i'm pretty confident it was never a "permanent brick" and you can get it to boot up
Click to expand...
Click to collapse
Nope the Screen doesn't come on at all, it comes on for a split second as in, the screen powers up, nothing on the display, then stays like that. it does boot to bootloader(fastboot) though by default, don't need to press vol down + power.
screen works though, so its confusing...
Oh also i cannot get to adb only fastboot
mike989e said:
Nope the Screen doesn't come on at all, it comes on for a split second as in, the screen powers up, nothing on the display, then stays like that. it does boot to bootloader(fastboot) though by default, don't need to press vol down + power.
screen works though, so its confusing...
Oh also i cannot get to adb only fastboot
Click to expand...
Click to collapse
almost certain you flashed wrong SLCD RUU for amoled or vice versa like i said. which is why you don't see anything...
(actually i realised you can't flash a recovery because it's now s-on, ignore that bit of previous advice about fastboot commands etc.)
so i believe all you have to do...i'll keep mentioning it until you try it:
look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
Click to expand...
Click to collapse
number 5 on the guide
eddiehk6 said:
almost certain you flashed wrong SLCD RUU for amoled or vice versa like i said. which is why you don't see anything...
(actually i realised you can't flash a recovery because it's now s-on, ignore that bit of previous advice about fastboot commands etc.)
so i believe all you have to do...i'll keep mentioning it until you try it:
number 5 on the guide
Click to expand...
Click to collapse
I get a bootloader version error, code 140 when i try to install lol
mike989e said:
I get a bootloader version error, code 140 when i try to install lol
Click to expand...
Click to collapse
done a bit of research for you, i thought the bootloader 140 error was for trying to install an older version. 2.3.3 GB RUU is the newest, so should work.
found another guide for you. didn't have time to read it all for you, not sure if a goldcard is required, no harm in making one anyway.
i'm still certain it's possible to get your phone working again, just takes some reading
eddiehk6 said:
done a bit of research for you, i thought the bootloader 140 error was for trying to install an older version. 2.3.3 GB RUU is the newest, so should work.
found another guide for you. didn't have time to read it all for you, not sure if a goldcard is required, no harm in making one anyway.
i'm still certain it's possible to get your phone working again, just takes some reading
Click to expand...
Click to collapse
cannot make a goldcard mate, i cannot get to ADB, as device does not boot past fastboot, and even according to that guide you need to boot the device up to use adb.
Thanks for your help though, i think it is dead, think i'll just bin it
mike989e said:
cannot make a goldcard mate, i cannot get to ADB, as device does not boot past fastboot, and even according to that guide you need to boot the device up to use adb.
Click to expand...
Click to collapse
no, you don't need to be booted into the OS:
If you dont have a goldcard, you might try to create one at this point. This may work only for some people. Try to see if Recovery can be booted up. Poweroff phone, then power it on by pressing Vol- and Poweron key, then wait 30sec and press Vol Down and Poweron button again. At this time, phone gets detected in Windows (as shown by the icon in the bottom right of taskbar and a notification sound.
Type:
Code:
adb devices
If this displays a code SH**** after "List of devices", you're in luck. You can issue an adb command and get a CID of your device, following which you can create a goldcard.
Click to expand...
Click to collapse
the goldcard is just very useful to have in case you have this kind of situation.
i'm still very surprised the 2.3.3 RUU doesn't work. another thing you could try is to use the 2.3.3 GB RUU again, but use the PB99IMG.zip method, by extracting the rom.zip from the RUU
Thanks for your help though, i think it is dead, think i'll just bin it
Click to expand...
Click to collapse
as long as you can get to a bootloader screen, it's almost certainly not dead. your symptoms are EXACTLY as that guide states. it's your device, might as well get it working again
a real brick is literally nothing, no response, no LED, nothing. most people who think their device is 'bricked' is never actually bricked.
as long as you get to fastboot no problem. just download the pb99img from the latest 2.3 official upgrade then throught fastboot (back+power) enter in to fastboot RUU update mode then flash the zip with the command fastboot flash zip rom.zip . you dont need even an sd card to do that. just wait to procces to finish then fastboot reboot and your done. first boot takes few minutes longer but you wont have problems.
theres a couple of problems i have, 1 i have no screen, even when i fastboot. so i wont know if it fails, secondly my issues is that the image version number is to high on my phone. hence why i am getting the 140 error. as i have installed a number of roms off here the version number is to high.
off the top of my head, i cannot remember the number, however, on 2.3.3 is got a .17. in it, mine instead of that has .27. which means mine cannot install the standard 2.3.3 software, if i knew how to change the image number to higher than mine, and repackage it i could install it. but i don't know how. as i recall there was a thread about this years ago, but not sure if it was ever solved. i did look for it.
Okay, this is not fixable in my opinion.
Summary:
I have a HTC Desire GMS, I flashed it along time ago, which buggered something! Now the screen does not come on, there is no system installed, and i can only access fastboot from usb.
I cannot use commands like "fastboot oem", It can find the device. I believe this is because the phone is S-ON, and HBOOT is 0.80
My device has a Customer ID of VODAP001 so i assume i need to use a Vodafone ROM
I have tried a number of different versions of ROMs in a few different methods.
RUUS Tried - RUU_Vodafone_UK_2.33.161.2 - RUU HTC_WWE_2.29.405.5 - RUU HTC_WWE_2.09.405.8 - OTA_2.29.405.5
I have tried changing the rom.zip to PD99IMG.zip, but as the screen doesn't work, i do not know what the error is.
When i try to use FASTBOOT to run the ROM, i get a number of different errors, ranging from CUSTOMERID Error to Signature Error.
Installing via RUU i get the same errors as above, or more often than not, i get USB Connection error (i have installed drivers)
So i'm thinking lost course. As i would need a Vodafone UK Customer ID, with a worldwide (405) Signature higher than 1.2x.405.x
Thanks everyone for your help!
mike989e said:
Okay, this is not fixable in my opinion.
Summary:
I have a HTC Desire GMS, I flashed it along time ago, which buggered something! Now the screen does not come on, there is no system installed, and i can only access fastboot from usb.
I cannot use commands like "fastboot oem", It can find the device. I believe this is because the phone is S-ON, and HBOOT is 0.80
My device has a Customer ID of VODAP001 so i assume i need to use a Vodafone ROM
I have tried a number of different versions of ROMs in a few different methods.
RUUS Tried - RUU_Vodafone_UK_2.33.161.2 - RUU HTC_WWE_2.29.405.5 - RUU HTC_WWE_2.09.405.8 - OTA_2.29.405.5
I have tried changing the rom.zip to PD99IMG.zip, but as the screen doesn't work, i do not know what the error is.
When i try to use FASTBOOT to run the ROM, i get a number of different errors, ranging from CUSTOMERID Error to Signature Error.
Installing via RUU i get the same errors as above, or more often than not, i get USB Connection error (i have installed drivers)
So i'm thinking lost course. As i would need a Vodafone UK Customer ID, with a worldwide (405) Signature higher than 1.2x.405.x
Thanks everyone for your help!
Click to expand...
Click to collapse
i'm confused whether the screen comes on at all now. you said previously you could get into bootloader screen, is this still the case?
can you try to get to select recovery, then connect and see if it connects to adb at all as stated in the guide? if so then you're in luck and can create a goldcard. once that's done you should be able to run any SLCD RUU as it will skip the CID check. you need to find some way of communicating via adb. some links are down, so manual method may be another way.
have you read those guides very slowly and tried everything? posting there may also help. droidzone is still active and will be the expert on solving this.
your issue is one of the more difficult to solve, i think it's still possible, goldcard is the key here.
eddiehk6 said:
i'm confused whether the screen comes on at all now. you said previously you could get into bootloader screen, is this still the case?
can you try to get to select recovery, then connect and see if it connects to adb at all as stated in the guide? if so then you're in luck and can create a goldcard. once that's done you should be able to run any SLCD RUU as it will skip the CID check. you need to find some way of communicating via adb. some links are down, so manual method may be another way.
have you read those guides very slowly and tried everything? posting there may also help. droidzone is still active and will be the expert on solving this.
your issue is one of the more difficult to solve, i think it's still possible, goldcard is the key here.
Click to expand...
Click to collapse
Sorry there was some confusion there, the screen does not come on at all, i get to the bootloader as in it loads on the phone, i cannot see it though, and can connect using my pc to use fastboot. i do not believe i cannot get into recovery, as i am not sure where im loading into, it is somewhere that i can use fastboot. yes i have read through them, and thank you for those! and tried everything other than the gold card. will try to do that but as i don't have a screen that works as i installed a SLCD instead of the correct screen firmware i'm not sure how it will help.
mike989e said:
Sorry there was some confusion there, the screen does not come on at all, i get to the bootloader as in it loads on the phone, i cannot see it though, and can connect using my pc to use fastboot. i do not believe i cannot get into recovery, as i am not sure where im loading into, it is somewhere that i can use fastboot. yes i have read through them, and thank you for those! and tried everything other than the gold card. will try to do that but as i don't have a screen that works as i installed a SLCD instead of the correct screen firmware i'm not sure how it will help.
Click to expand...
Click to collapse
i'm still a bit confused as i've never experienced it, only read others. so you can't even see the bootloader screen at all anymore, i thought that still works even in your situation (for clarity it's the white background with BRAVO SHIP S-ON at the top). does it still boot to bootloader screen straight away every time you try to power on normally?
or if you leave it after trying to power it on normally, does it get to boot sound? if so it still installed, you just have no screen. wait a minute until it boots up, then try connecting and see if you can communicate with adb.
at least fastboot is communicating so it's doesn't feel like a lost cause.
if above doesn't work boot to bootloader anyway (vol down + power), wait for a few seconds. then press volume down once, then power to select recovery. then try as before to get it to communicate as stated in the guide. have you tried this?
i haven't read all of it, but i believe you need at least 'adb devices' to work! then goldcard...
eddiehk6 said:
i'm still a bit confused as i've never experienced it, only read others. so you can't even see the bootloader screen at all anymore, i thought that still works even in your situation (for clarity it's the white background with BRAVO SHIP S-ON at the top). does it still boot to bootloader screen straight away every time you try to power on normally?
or if you leave it after trying to power it on normally, does it get to boot sound? if so it still installed, you just have no screen. wait a minute until it boots up, then try connecting and see if you can communicate with adb.
at least fastboot is communicating so it's doesn't feel like a lost cause.
if above doesn't work boot to bootloader anyway (vol down + power), wait for a few seconds. then press volume down once, then power to select recovery. then try as before to get it to communicate as stated in the guide. have you tried this?
i haven't read all of it, but i believe you need at least 'adb devices' to work! then goldcard...
Click to expand...
Click to collapse
Ok, It does not have a white background, the screen simply does not power on at all. (this happened after a flash, no knocks or bangs to the phone. So i don't think the screen is damaged.)
Before, it did have the white background. Yes, i believe it is booting into the bootloader when i try to start up. as thats how i am using Fastboot.
There is nothing in the system folder, "fastboot oem boot" shows nothing. i believe the phone is completely blank other than the HBOOT 0.80
i have tried that, it simply reboots back into bootloader, as i had a 3rd party recovery.
I was returning this to unrooted when this happened.
I cannot get the gold card to work on any of my microsd cards... so i will need to purchase a few to see if i can get it to work!
mike989e said:
Ok, It does not have a white background, the screen simply does not power on at all. (this happened after a flash, no knocks or bangs to the phone. So i don't think the screen is damaged.)
Before, it did have the white background. Yes, i believe it is booting into the bootloader when i try to start up. as thats how i am using Fastboot.
There is nothing in the system folder, "fastboot oem boot" shows nothing. i believe the phone is completely blank other than the HBOOT 0.80
i have tried that, it simply reboots back into bootloader, as i had a 3rd party recovery.
I was returning this to unrooted when this happened.
I cannot get the gold card to work on any of my microsd cards... so i will need to purchase a few to see if i can get it to work!
Click to expand...
Click to collapse
you shouldnt have a custom recovery installed any more, the RUU should overwrite it to stock recovery. you won't be able to do anything with stock recovery per se, but the guide seems to indicate that you may be able to communicate with the device via adb.
still surprised the 2.3.3 RUU didn't work, I thought it's the highest version number so shouldn't have any problem.
I'm running out of ideas tbh, I'd still recommend posting the issue in the droidzone guide, hopefully he'll reply as he'd most likely know how to solve it.