Help Please! - Desire Q&A, Help & Troubleshooting

Hello,
My device was S-OFF and rooted and was running MIUI-AU ROM and decided to try and revert it to a Stock ROM bog standard etc and ran a TMO RUU, which failed with an error 140.
Problem is I have a blank screen now, with battery out I have tried getting into Fastboot (back button and power) which seems to work as I can run the Android Flasher to try and flash the stock boot from Alpharev, which detects the phone but fails and I know it is there since when you press the power button it vibrates from the Fast boot.
I have tried flashing recoveries and HBoots with the android flasher but am getting nowhere. I do not have a gold card and have tried to set up adb which can't find the device either.
I am hoping some of the incredibly clever people here can help me!
Thanks in advance,
Graham
I did manage to use fastboot commander to get the following, but still have the same issue:-
SPL/hboot version: 0.80.0000.
Radio version: 5.17.05.08.
Main software version: 2.12.110.2.
cid: t-mob005.
cpld: none.
product: bravo.
mid: pb9920000.
security: on.
build-mode: ship.

Hello,
My device was S-OFF and rooted and was running MIUI-AU ROM and decided to try and revert it to a Stock ROM bog standard etc and ran a TMO RUU, which failed with an error 140.
Problem is I have a blank screen now, with battery out I have tried getting into Fastboot (back button and power) which seems to work as I can run the Android Flasher to try and flash the stock boot from Alpharev, which detects the phone but fails and I know it is there since when you press the power button it vibrates from the Fast boot.
I have tried flashing recoveries and HBoots with the android flasher but am getting nowhere. I do not have a gold card and have tried to set up adb which can't find the device either.
I am hoping some of the incredibly clever people here can help me!
Thanks in advance,
Graham
I did manage to use fastboot commander to get the following, but still have the same issue:-
SPL/hboot version: 0.80.0000.
Radio version: 5.17.05.08.
Main software version: 2.12.110.2.
cid: t-mob005.
cpld: none.
product: bravo.
mid: pb9920000.
security: on.
build-mode: ship.[/QUOTE]
see this http://forum.xda-developers.com/showthread.php?t=1363855
this must solve your problem...
If not PM me .. Ill see another option...
and you DON't NEED a GLODCARD for this

It cannot find the device when I get the adb devices, the only way i seem to be able to get adb to work is when I somehow press a combination of buttons to get to recovery. So i end up with a set of numbers in adb followed by the words recovery.
Thanks again,
Graham

Already checked bortak's troubleshooting guide?

I have....Really odd, I have tried the WWE RUU and the T Mobile one, the WWE says it is the wrong Customer ID and the T Mobile one says it is the wrong Bootloader version...

greeham said:
It cannot find the device when I get the adb devices, the only way i seem to be able to get adb to work is when I somehow press a combination of buttons to get to recovery. So i end up with a set of numbers in adb followed by the words recovery.
Thanks again,
Graham
Click to expand...
Click to collapse
you may not have enabled adb at your PC...
BTW there will not be any device list... The message will be like.."List of adb devices attached"
Than you folow the procedure..
enter fastboot commands..

Hi There,
That's exactly what it says when i type adb devices. I have tried a colleagues Desire and adb works fine with his, so I presume there is something else going on?
Thanks,
Graham
I did get into adb when the device is in Recovery but when I try and run fastboot it says '/sbin/sh: fastboot: not found'

greeham said:
Hi There,
That's exactly what it says when i type adb devices. I have tried a colleagues Desire and adb works fine with his, so I presume there is something else going on?
Thanks,
Graham
I did get into adb when the device is in Recovery but when I try and run fastboot it says '/sbin/sh: fastboot: not found'
Click to expand...
Click to collapse
mAY BE YOu have not follwed the whole procedure I wrote in the POST...
Right now the tools folder is missing fastboot.exe file..CHECK it..
2.Download these(http://www.multiupload.com/5ZAPJTFXMM) and put them into C drive in to "C/android sdk/tools" after UNZIPING by 7ZIP...

Hi,
I did follow exactly what you had said and fastboot.exe was in the tools folder but the error is the same...
Thanks,
Graham

greeham said:
Hi,
I did follow exactly what you had said and fastboot.exe was in the tools folder but the error is the same...
Thanks,
Graham
Click to expand...
Click to collapse
Tell me thewhole procedure with EXACT commands..you followed...

Remove battery and place back.
press back and then Power button, phone vibrates.
Plug USB in and then open CMD prompt and attempt adb devices.
Says 'List of adb devices attached' and nothing is listed. If you try anything else it doesn't work since doesn't have device to 'see'.
If I remove battery and place back and power on whilst holding down volume, it vibrates.
I then press volume down button and power button.
if i then adb devices it says '123456789ABCDEF recovery'
I then can adb shell but always has similar errors when trying anything about '/sbin/sh'
Does that help at all?
Thanks again,
Graham

greeham said:
Remove battery and place back.
press back and then Power button, phone vibrates.
Plug USB in and then open CMD prompt and attempt adb devices.
Says 'List of adb devices attached' and nothing is listed. If you try anything else it doesn't work since doesn't have device to 'see'.
If I remove battery and place back and power on whilst holding down volume, it vibrates.
I then press volume down button and power button.
if i then adb devices it says '123456789ABCDEF recovery'
I then can adb shell but always has similar errors when trying anything about '/sbin/sh'
Does that help at all?
Thanks again,
Graham
Click to expand...
Click to collapse
It is not possible that the the phone will not except any command on fastboot...
What are you seeing on your phone screen....oh....you'r missing a thing...
to got to the fastboot mode on your phone..
reboot
press BACK+POWER button..
you currently using volume down+power.. that ends up at the splash screen.. NOT fastboot-Bootloader..
Try this...

The screen is completely blank.
I am pressing back and the power button, I mentioned the volume buttons as I tried that as well.
So, neither works for the fastboot command.

greeham said:
The screen is completely blank.
I am pressing back and the power button, I mentioned the volume buttons as I tried that as well.
So, neither works for the fastboot command.
Click to expand...
Click to collapse
I don't know waht exactly is happening with you... I've never encountered this problem when NOT having anything on screen whille pressing BACK+Power Button...
If this does't solves the problem..
Download the official ruu .. flash it and got to htc...
I am still feeling that you are missing something...may be...
Try this again...if you feel this can help..
I tried this procedure couple of times ... but never got a BLANK SCREEN...

Have tried both the TMO RUU and get a Bootloader is wrong version error and the WWE tells me that the Customer ID is wrong.

greeham said:
Have tried both the TMO RUU and get a Bootloader is wrong version error and the WWE tells me that the Customer ID is wrong.
Click to expand...
Click to collapse
your signature is showing that the PHONE is S-ON....
For all I've written you must have root access...
Have you tried REVOLUTIONARY.IO also for getting S-OFF this time????

Related

[Q] Yep, I made it, fully bricked.

I have a really huge problem. I think my Desire bricked completely.
I don't really know if it was SLCD or a normal Desire, while unrooting due flashing PB99IMG.zip the phone turned black, stopped, done nothing and vibrated once.
Now it doesn't do anything anymore. When I plug it in and boot the phone, windows says 'Android 1.0' ... And nothing more.
Is there any solution out there or is it fully bricked?
Go for warranty.
Rubbish!
Read and follow this thread
http://forum.xda-developers.com/showthread.php?t=831734
In order to help you more you need to give a full account of what you were trying to do and how as well as relevant device info such as were you already rooted, did you try to s-off and anything else that maybe relevant.
Sent with Desire.
Wrong section!
Also as windows recognizer it, it's not bricked(probably wrong ruu and you are slcd bricked so it boots in fastboot, you just cant see it)
Just run the correct ruu through usb.
Also would you like to share which ruu you flashed?
I also don't know why people are running those pb99img.zip things for unrooting =.=
So, um, urm, I forgot to check for SLCD, I know.
I tried this one: RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe
I think this one was the wrong one.
After trying a lot out:
When I hit 'BACK'+'POWER' the windows device-manager says 'Android 1.0' - and then I have three options, I tried, with vol-down and hitting power.
1.) dunno
2.) reboot
3.) reboot to the bootloader
It is still black. I tried with the alpha-rev-pb99img - booting via VOL DOWN and POWER and hitting constantly POWER UP - it seems to do nothing.
fastboot doesn't respond, adb list also no devices...
DarkMio said:
So, um, urm, I forgot to check for SLCD, I know.
I tried this one: RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe
I think this one was the wrong one.
After trying a lot out:
When I hit 'BACK'+'POWER' the windows device-manager says 'Android 1.0' - and then I have three options, I tried, with vol-down and hitting power.
1.) dunno
2.) reboot
3.) reboot to the bootloader
It is still black. I tried with the alpha-rev-pb99img - booting via VOL DOWN and POWER and hitting constantly POWER UP - it seems to do nothing.
fastboot doesn't respond, adb list also no devices...
Click to expand...
Click to collapse
That RUU is way too old. You should have ran the 2.29.405.5 one.
Read this thread: http://forum.xda-developers.com/showthread.php?t=749551
DarkMio said:
fastboot doesn't respond, adb list also no devices...
Click to expand...
Click to collapse
Android 1.0 is ADB driver, download Android SDK from here:
http://developer.android.com/sdk/index.html
This will also install ADB driver.
Nope it's the fastboot driver(not the same as adb)
To solve this just boot using vol-down and connect it to usb. Then run the newest ruu(would be 2.29.405 something) This should flash the newer bootloader with slcd support, and you are back up and running in no time.
Thanks for you help, but anyways, the phone isn't responding, normally.
It only says 'Android 1.0' - and nothing more.
ADB DEVICES doesn't list the phone and FASTBOOT DEVICES neither.
DarkMio said:
Thanks for you help, but anyways, the phone isn't responding, normally.
It only says 'Android 1.0' - and nothing more.
ADB DEVICES doesn't list the phone and FASTBOOT DEVICES neither.
Click to expand...
Click to collapse
Have you tried using a card reader to put the correct 2.29.405.5 PB99IMG.zip on teh root of SD then boot to Hboot (Down+power)?
man in teh device manager on your computer the drivers of your phone are instaled??
Have you now downloaded the latest RUU as suggedyed?
Have you removed the previous PB99IMG.ZIP file from your SDCARD?
Have you gone in to HBOOT and then after some time -VOL once then POWER key to get the phone in to FASTBOOT then run the new RUU?
the thread that I linked you to advises on the very first post how to extract the ROM.ZIP file if you are unable to flash the RUU conventionally.
Sent with Desire.
angusc said:
Have you now downloaded the latest RUU as suggedyed?
Have you removed the previous PB99IMG.ZIP file from your SDCARD?
Have you gone in to HBOOT and then after some time -VOL once then POWER key to get the phone in to FASTBOOT then run the new RUU?
the thread that I linked you to advises on the very first post how to extract the ROM.ZIP file if you are unable to flash the RUU conventionally.
Sent with Desire.
Click to expand...
Click to collapse
yep, alternatively I have a link to the PB99IMG.zip in my toolbox:
http://androidforums.com/desire-all...oads-root-users-updated-18th-june-2011-a.html
theoretically phone when you open or even see it , enter fastboot automatically ,you can revive it , is simply just have the drivers installed
happened to me and I could restore it to life , no panic
rootSU said:
yep, alternatively I have a link to the PB99IMG.zip in my toolbox:
http://androidforums.com/desire-all...oads-root-users-updated-18th-june-2011-a.html
Click to expand...
Click to collapse
So now download this PB99IMG.ZIP from this link, copy to your sdcard and -vol + power button, holding both for about 6 seconds.
Once you have overcome this little learning curve........
1. Make your sdcard in to a GOLD CARD.
2. Go to www.unrevoked.com and follow the Desire how to Root.
3. Go to www.alpharev.nl and download the .iso to get S-OFF.
then you will ask be done within a matter of 30 minutes
Sent with Desire.
try this open android flasher conect your phone to usb cable verify the phone to be open and then select on android flasher hboot select the stock hboot wait 1 or 2 seconds and then open the Ruuand wait and your phone is back to life
my phon is back to normal
DarkMio said:
I have a really huge problem. I think my Desire bricked completely.
I don't really know if it was SLCD or a normal Desire, while unrooting due flashing PB99IMG.zip the phone turned black, stopped, done nothing and vibrated once.
Now it doesn't do anything anymore. When I plug it in and boot the phone, windows says 'Android 1.0' ... And nothing more.
Is there any solution out there or is it fully bricked?
Click to expand...
Click to collapse
So a bit of feedback then please.........did you resolve your LCD Brick?

[Help] Hox Won't Accept Fastboot Commands

I don't know what exactly happened. Today I wanted to upgrade my HOX to JB coming from AOKP to OrDroid. So, I followed the instructions and relocked my bootloader while on fastboot, then it went downhill from there. Phone automatically rebooted into HBOOT and it said that my bootloader was re-locked and below it "Security Warning". Everytime I reboot it always takes me to Fastboot. The weird thing is whenever I try to flash something in fastboot mode the CMD Window just says "Waiting for Device". When I check my phone, I can not move the volume rocker up and down in Fastboot mode while having my phone connected to my PC, but when I disconnect the USB plug, I can move it up and down. When I try to go through the RUU process, it says ERROR 170 and can't find my phone. I am lost as what to do, since I don't know how to get Fastboot to work properly and out of ideas. Please help. Thank you.
http://forum.xda-developers.com/showthread.php?t=1920060
follow this guide to help you its fantastic
I had the same problem when I first tried to flash leedroid 10.4.5. Try installing DroidExplorer.
Worked great for me! let me know if it worked for you:good:
You need to add the ADB paths to your actual windows path.
Right click "Computer" click "Properties" then Click "Advanced System Properties" then go to Envioronment variables and add the paths to adb folders into that, using a ";" to separate each path.
Hope that makes sense, a little hard to textually explain
kotaro_14 said:
I don't know what exactly happened. Today I wanted to upgrade my HOX to JB coming from AOKP to OrDroid. So, I followed the instructions and relocked my bootloader while on fastboot, then it went downhill from there. Phone automatically rebooted into HBOOT and it said that my bootloader was re-locked and below it "Security Warning". Everytime I reboot it always takes me to Fastboot. The weird thing is whenever I try to flash something in fastboot mode the CMD Window just says "Waiting for Device". When I check my phone, I can not move the volume rocker up and down in Fastboot mode while having my phone connected to my PC, but when I disconnect the USB plug, I can move it up and down. When I try to go through the RUU process, it says ERROR 170 and can't find my phone. I am lost as what to do, since I don't know how to get Fastboot to work properly and out of ideas. Please help. Thank you.
Click to expand...
Click to collapse
Unplug your phone
Turn off your phone
turn on your phone
choose fastboot
connect usb[
use fastboot commands /B]
(it's very important that you do it in this order because otherwise the bootloader will think your pc is a storage device and will lag because it will attempt to search for update.zip nowhere)
Use fastboot commands not adb (adb commands almost never work on bootloader)
If that still doesnt work then either the drivers aren't installed properly, otherwise you have to check with repair centers(i dont think its this one)

[Q] Major issues re-rooting

I've been trying to re-root my phone since late last night, and have had nothing but problems. I've searched all over the internet, and tried anything that I thought would apply to my situation in the slightest.
I originally downgraded from 2.3.4 to 2.3.3 and rooted my phone using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1298990
I ran Revolutionary, ClockworkMod, and SuperUser. Everything worked perfect the first time around. Installed the Cyanogenmod 7.2 ROM and Tiamat v1.1.5 kernel. Then I started having issues with my battery, and Cyanogenmod seemed to be increasing the issues. At that time HTC announced they'd be releasing ICS, yada yada yada. I found a stock ROM online, and installed it, and updated as they were released OTA. Having finally gotten a new extended battery, I'd like to re-root & ROM my phone, but I've hit some road blocks.
I currently have the Android Version of 2.3.4 & Software Number of 5.10.605.9
I tried to re-do the entire process that had previously worked for me, but once I used the command hack-vivow.cmd, the phone would boot to the Revolutionary (of HBOOT ?) screen. Command line shows this, and just hangs:
c:\vwhk-12102011-c>fastboot oem rebootRUU
< waiting for device >
Click to expand...
Click to collapse
Phone shows this:
-Revolutionary-
VIVO_W XB SHIP S-OFF RL
HBOOT -6.13.1002
RADIO -1.09.01.1111
eMMC -boot
Click to expand...
Click to collapse
Phone gives me the options of "BOOTLOADER", "REBOOT", "REBOOT BOOTLOADER", & "POWER DOWN". "REBOOT BOOTLOADER" changes "FASTBOOT" briefly to "FASTBOOT USB", but changes back in about 15-20 seconds. When I select "BOOTLOADER", the screen freezes for a few seconds, and it won't let me select any options, "FASTBOOT" changes to "HBOOT", and I get this in green text:
SD Checking
Loading...[PG32DIAG.zip]
No image!
Loading...[PG32DIAG.nbh]
No image or wrong image!
Loading...[PG32IMG.zip]
Click to expand...
Click to collapse
The next screen of green text says "Parsing...[SD ZIP]" followed by 9 things, and I'm only given an option to Update or No/Reboot. No/Reboot reboots my phone into an endless bootloop, until I remove the battery and power back on with Volume Down + Power Button. Update does a reset of my phone, and puts me right back to where I am now. While it is updating there is an error message at the bottom that says "Can not roll back hboot version".
I've tried multiple things to attempt to fix this... I ran the TacoRoot method from here:
http://forum.xda-developers.com/showthread.php?t=1751796
When the 8th line was completed
adb shell /data/local/tacoroot.sh --setup
Click to expand...
Click to collapse
, the phone rebooted, it got stuck in a bootloop.
So that's where I am now. I'm stuck with S-Off, the PG32DIAG/PG32IMG errors, an HBOOT that seems to be far too new of a version, and I haven't found a way to get back to 2.3.3. As you can see I'm a noob. I'm really not sure where I went wrong (other than going back to a stock ROM and allowing it to update). Unfortunately a lot of things are just way over my head, without seeing a step by step process. But I'm just stuck at the moment. If anyone has any ideas on how to fix this, or any ideas of things to try I GREATLY appreciate it.
Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.
Cleanincubus said:
Still looking for an answer, but I've done some more digging.
Would I be correct is assuming that I have to find a way to downgrade hboot (which Revolutionary won't allow) and get S-On, in order to do what I need to do? If so, does anyone know of an accurate way to accomplish this? All I've found are old threads that apparently are no longer relevant for newer Software & hboot updates.
Click to expand...
Click to collapse
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.
gtdtm said:
I am by no means an expert, but my limited understanding would suggest this: try flashing a new recovery like clockworkmod with fastboot. If that is successful you can flash a superuser zip in clockwork. I don't recall the steps to flash the recovery, but I think since you are s-off you should be able to do it fairly easily.
Click to expand...
Click to collapse
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.
Cleanincubus said:
Sorry for my ignorance, I'm trying to understand exactly what you mean. From my very limited knowledge, there might be 2 ways of doing what you're saying.
First, rebooting the phone with Volume Down + Power button, with the the ClockworkMod file placed on the root of my SD card, and renamed PG32IMG.zip. Then selecting Bootloader, and allowing it to Update.
Second would be rebooting the phone (Volume Down + Power), and then "force" the flashboot via command, with the phone connected to the USB cable.
The 1st option I would love to try, if that has a chance of working. The 2nd option though, won't work, because the phone won't respond to any commands via command lines.
The reason I'm not immediately jumping on option #1 for a try, is that I might be on track to get things straightened out, with a possibility of critical failure. I found this thread:
rootzwiki.c om/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
I'm currently using Revolutionary, but apparently Alpharevx is a previous incarnation of that, and some users in that thread claim that it worked for their Revolutionary S-Off phones. So far, I have gotten to the point where I now have Android Froyo/ Android version 2.2.1 (from the same way of doing things as Option #1 above). The rest of that thread is messing with the Bootloader, which I'd rather not risk if I don't have to (I do realize how serious the consequences are). If there's any other way to do it, I'll gladly give it a try, as long as it doesn't put me in a place much worse than I'm at now (bricking my phone by messing with the bootloader certainly would be.)
I apologize for being a pain in the ass, I just want to make sure I understand any recommendations fully before I do something wrong. Clearly I should have done a lot more research before "un-rooting" my phone. Had my original issues not been my battery, I'd still be out of warranty for having S-Off. :laugh: Thank you very much for the response, it is truly appreciated.
Click to expand...
Click to collapse
So with Froyo on there can you get to the stock recovery?
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I think you should be able to do 1B at this little how-to site:
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
Cleanincubus said:
Oh wow, yes I can. I just tried the fastboot clockworkmod flash, but it doesn't seem to be working, or even more likely, I don't know what I'm doing.
I booted the phone with Volume Down + Power, selected "Fastboot", which changed HBOOT to FASTBOOT USB. I used the command prompt and typed "fastboot flash recovery cwm-4.0.1.4-vivow.img". The command prompt stalls at "< waiting for device >" and FASTBOOT USB changed to FASTBOOT. Maybe I just don't know what to do after than. I tried "Recovery", which I thought would have booted ClockworkMod, had it been installed properly.
Click to expand...
Click to collapse
I also just noticed...did you do "fastboot devices" first to make sure it actually recognized your phone? I'm really guessing, but I figured it was worth asking.
Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.
Cleanincubus said:
Yes it does recognize my phone. I think you're exactly right, in the direction you're showing me. I think flashing CWM is the key to getting this all to work.
But I'm getting some strange stuff happening. When I was finally able to select the Fastboot section, I had CWM saved as PG32IMG.zip. I started getting an error (black screen with a little center image of my phone, with a red "!" on it), after rebooting. I had to press Volume Up + Power, which brought me to some kind of Android settings (Wipe Cache, & something about clearing or wiping partition). I selected to just reboot, and the phone rebooted fine. I changed the PG32IMG.zip file back to the Froyo, and I can no longer get past the "Recovery" and forcing to do the Update or Bootloop from declining.
So now I don't know what to do, when it comes to the PG32IMG.zip file. I even just changed the Froyo PG32IMG.zip to a 2.3.3 Gingerbread PG32IMG.zip, so now I'm at the correct ROM for rooting. I changed it because I wasn't sure if being at Froyo was preventing me from doing all of this from the beginning, similar to how the most up to date update did as well.
But back to the PG32IMG.zip, what would be the best thing to do with this situation? Should I change it back to the CWM, and deal with the Android error, while still allowing me to get into FASTBOOT. Or should I just keep it as the GB 2.3.3, as it is now? Can I just delete the PG32IMG.zip file altogether, or is it absolutely necessary? It just keeps trying to update to what the file already is, and prevents me from doing anything else.
I think I'm going to try the CWM.zip renamed to PG32IMG.zip and see if I can get it to work.
Click to expand...
Click to collapse
You shouldn't be flashing romantic zips as PG32IMG. That's what clockwork is for. If get it back to froyo, then go to the HTC recovery and follow the clockwork instructions I linked to. But maybe someone more knowledgeable than I can answer better.
Sent from my ADR6350 using xda app-developers app
After you go onto bootloader and it flashes your IMG you either rename the file on your SD card or delete it from your SD card. You will be able to proceed after that has been done
sent from my incredibly paranoid inc2
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
Your s-off so the hard part is done.
sent from my incredibly paranoid inc2
You're right. The PG32IMG.zip was a problem. I removed them from the SD card's root, and it's working as it should.
Now the issue is the instructions in that link. I can't find any update.zip for the phone anywhere. I also can't find any options in the Recovery for "re-install package". I go to "BOOTLOADER" and then "RECOVERY". The Phone then boots to a small image of my phone with a red "!". I press Volume Up + Power button, and it loads the "Android system recovery <3e>". I have a Yellow error at the bottom stating"
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.
sjpritch25 said:
You need to flash a new recovery. Do you adb setup on your pc? If not, google it and get it setup.
Here is a link to CWM
http://goo.im/devs/aeroevan/cwm/recovery-clockwork-6.0.1.5-vivow.img
Save it to your adroid-tools folder
You will need to navigate to your anroid tools folder in cmd before issuing the commands below
Code:
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img
---------- Post added at 11:55 PM ---------- Previous post was at 11:44 PM ----------
FYI cmd needs to be run as administrator.
Click to expand...
Click to collapse
screenshot for you
The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.
Cleanincubus said:
The version I have has the correct files in the "platform-tools" folder.
I get an error with the "adb remount" command, saying "remount failed: Operation not permitted"
When I use the command "fastboot devices", my phone doesn't show up, and it just skips to the next command line, showing nothing. My phone does say "FASTBOOT" though.
Then when I type "fastboot flash recovery recovery-clockwork-6.0.1.5-vivow.img" it just hangs at "< waiting for device >"
Maybe I didn't set it up the sdk stuff properly? I'll look more stuff up when I get home later tonight. But I figured, I'd at least post this up now, in case this is showing another issue.
Click to expand...
Click to collapse
I don't think it's going to work until you get fastboot devices and adb devices to recognize your phone. I wish I could point you in the right direction, but I'm not very experienced with it.
I'm assuming you have the drivers for our phone installed? Some people have to reboot the pc to get those to recognize the device...
Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.
Cleanincubus said:
Yeah, I'm going to have to do some more digging. ADB device does recognize my phone, at the 6th line on the screen cap I posted. I've restarted the pc multiple times since first trying to get all of this to work.
Click to expand...
Click to collapse
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img
Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2
sjpritch25 said:
First of all make sure you have fastboot.exe in your tools folder
Code:
adb kill-server
adb start-server
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery***.img
Click to expand...
Click to collapse
Yup, it's there.
Did those commands, and it ended in the same result. No errors or "waiting" messages at the flashboot devices command, but it didn't show my device either.
Jasonp0 said:
Make sure you have the drivers and that you delete HTC sync from your computer. If you can get it to boot up into the phone make sure you have android debugging turned on.
sent from my incredibly paranoid inc2
Click to expand...
Click to collapse
Definitely installed driver. I originally tried to install the driver I previously used with my original s-off/root/rom, but it didn't work with Windows 8 (previous PC was WinXP), so I found the correct one for my OS. The "adb devices" command never found my phone, before installing the current driver.
I never installed HTC Sync. Just double checked the "Uninstall or change program" in the Win8 control panel (previously "Add/Remove Programs") to make sure it didn't get installed with out my knowledge, and it's not in there.
If you mean on the phone: "Settings" > "Applications" > "Development" > check box for "USB debugging", then yes. If it's a command of some sort, then no & I don't know how to do it.
I'm also making sure to run these commands by right-clicking the Command Prompt and selecting "Run as administrator", before doing these commands.

[Q] Stuck on HTC Logo, cannot enter hboot

Hi,
I searched a lot withouth luck.
After flashing a kernel my amoled Desire is stuck on the HTC logo.
It is s-off with latest hboot.
The problem is that the volume keys are broken..
So I cannot use power+volume down to enter fastboot or hboot..
From the pc with adb devices I cannot see the device.
Is there a way to recover my poor phone?
Or to enter hboot without
thank you very much for your attention
Use back+power to enter fastboot and select "bootloader"
Thank you very much!
It was so simple, but I didn't know this method, sorry.
After some little problems I manage to restore it. :victory:
I write down the difficulties I found, so if someone has the same issues, he could use that.
After entering fastboot adb could not see the device again.
Fastboot commander 1.51 could, but was unable to write a new rom from a zip.
So I write on the phone a nandroid backup (with fastboot commander).
It booted but was stuck on "Optimizing Applications".
From there adb coul see it.
So I rebooted into recovery with adb, flashed the same nandroid of before from the SD and it booted successfully.
Thank you again!
And thanks to all that keep this device alive and help who need it
HTC desire doesnt boot to OS
RoKKo_TM said:
Hi,
I searched a lot withouth luck.
After flashing a kernel my amoled Desire is stuck on the HTC logo.
It is s-off with latest hboot.
The problem is that the volume keys are broken..
So I cannot use power+volume down to enter fastboot or hboot..
From the pc with adb devices I cannot see the device.
Is there a way to recover my poor phone?
Or to enter hboot without
thank you very much for your attention
Click to expand...
Click to collapse
I too searched for the thread of my problem but couldn't find it.
I was given this Desire and I switched it on, it booted directly to hboot. I thought may be I pressed the volume key unknowingly. But then I tried to reboot it via hboot, I found out that volume keys do not work. So I removed the battery and tried to switch it on again, and it did the same, booted to hboot directly.
It is s-off and does not have any recovery app installed.
What do i do. I really need some help.
P.S. Sorry for my english, and this is my first post/comment in here. I thought this thread somehow matches my problem.
Thanks
Alternative HBoot entry
dreamer8ful said:
I too searched for the thread of my problem but couldn't find it.
I was given this Desire and I switched it on, it booted directly to hboot. I thought may be I pressed the volume key unknowingly. But then I tried to reboot it via hboot, I found out that volume keys do not work. So I removed the battery and tried to switch it on again, and it did the same, booted to hboot directly.
It is s-off and does not have any recovery app installed.
What do i do. I really need some help.
P.S. Sorry for my english, and this is my first post/comment in here. I thought this thread somehow matches my problem.
Thanks
Click to expand...
Click to collapse
Heh guys,
You can enter hboot by holding down the back button then the power button together.
See abaaaabbbb63's reply above
Ps. Thank me if this helps.
But he can enter hboot, so I think the question was different, or I'm wrong?
When you are stuck on hboot, could you see the device with the command "adb devices"?
Have you installed the correct drivers on the pc?
If you haven't got a recovery I think it is not a problem, you can at least flash the original gingerbread ruu.
Have you tried fastboot commander?
Me noob
RoKKo_TM said:
But he can enter hboot, so I think the question was different, or I'm wrong?
When you are stuck on hboot, could you see the device with the command "adb devices"?
Have you installed the correct drivers on the pc?
If you haven't got a recovery I think it is not a problem, you can at least flash the original gingerbread ruu.
Have you tried fastboot commander?
Click to expand...
Click to collapse
Umm... I'm a noob, the lowest one... Honestly I haven't done anything to this device coz I have no idea what to do. I tried googling hoping I would find some helpful infos to start with, but I didn't.
So can you please explain how do I get/do the above things??
The phone has been modified in any way by the previous owner?
First you need to connect the phone with the pc.
From hboot, if you see "fastboot" higlighted, press the power button one time to go into fastboot mode.
I cannot find my exact same drivers, but this should be just fine:
Code:
http://dl.xda-developers.com/attachdl/fe66812c2a4bd7da49a109b357afe420/518cba12/5/6/0/4/1/4/adb_driver_htc.zip
Download also Fastboot:
Code:
http://d-h.st/OFs
Plug the phone in the pc, when it asks for drivers, give it manually the folder that is inside the adb_driver_htc.zip.
It should see now the device from the device manager.
Extract the Fastboot.zip folder in a folder you want. (Like C:\).
With the phone inserted in the pc, open cmd (using the search function over start) and navigate to the directory where you've extracted fastboot.
After type "adb devices" without quotes, and see if it lists a device .
Sorry for my bad guide, hope we could figure it out .
You must understand how to use adb and fastboot, that are the tools we use to interface ourselves with the phone, so if needed the internet is full of little and friendly guides

[Q] Failed remote signature verify fail. Phone stops on fastboot

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.

Categories

Resources