Develop Bugs

[Q] White HTC screen after .. [RESOLVED]

Hi all,
I need a little help here. I have an European DesireZ (stock 2.2/1.34).
I've followed ianmcquinn's guide which is basically doing a temp root using visionary (I used r14) and then using gfree to get perm root. I did that with no visible issues and I also flashed an ENG hboot while I was there, then I rebooted.
Now, when my DesireZ boots, I get a while screen with the green HTC logo and nothing else. I can get into hboot fine:
Code:
VISION PVT ENG S-OFF
HBOOT-0.76.20000
MICROP-0425
RADIO-26.03.02.26_M
System Info says:
Code:
SN-HT0Axxxx
...
OS Ver.-1.34.405.5
CID-11111111
eMMC-unknown 2223MB 4554751 Sectors
I can get into stock recovery (Black screen with a red /!\) then using VOL-UP + Power get into the menu.
I've done a factory reset, wiped all caches and data with no result. Also did a Factory reset from hboot. There seems to be a progress bar there but I don't see it filling in.
On the windows side, I see the android 1.0 device while in hboot and the adb devices while in recovery but "adb devices" gives me my S/N followed by offline.
Tried swaping cables too.
Any hints on what may have gone wrong and what I could try next?
I figured if I could flash Clockwork recovery 3 using hboot I could flash a GB rom and might fix it ...
Thanks in advance, DouD

The red triangle that you are getting is the stock recovery what you need to do is
flashing a clockworkmod recovery as you said
so get the recovery image and put it in your adb folder (tools)
navigate to that folder and type this command "fastboot flash recovery <name of the file>.img "
after that on your phone go to recovery and flash the rom if you already have it on your sd card. if not you can download the rom put it in your adb folder and type this command "adb push < rom name> sdcard/ " obviously you dont need to type <>
and please be careful only flash recovery 3 and above if you are planning to install CM7 otherwise get the 2.5.1.3 recovery and you should be fine.

Hey bahmanxda,
Brilliant, that worked.
As adb wasn't too happy about my device to be listed offline, I was holding back from doing the fastboot sequence, it appears that it worked perfectly and I'm now running CM7 - 17.
Thanks a lot

Glad to see you got it all working properly again!
Not sure what happened to cause your issue though. Had you tried any other rooting methods before? Did you make sure none of the options were selected in Visionary when you did the temproot?

ianmcquinn said:
Glad to see you got it all working properly again!
Not sure what happened to cause your issue though. Had you tried any other rooting methods before? Did you make sure none of the options were selected in Visionary when you did the temproot?
Click to expand...
Click to collapse
Hi Ian,
that was the/my first attempt on that Desire Z.
Nothing was checked in Visionary, made sure of that. I tapped temproot, it did it's attempting thing, then came back to the menu and I pressed the home hey so I could start the Terminal Emulator.
At that point I think HTC Sense crashed because I had the white screen with the HTC logo on it and it slowly loaded my home screen. I was like meh, and started the Terminal Emulator and typed su, got the elevation request and a success, proceeded with the rest of the steps.
Then I rebooted (long press on power button, selected 'Restart') the device vibrated twice for a second or two then I got into hboot (I was pressing Vol Down). I admired the versions and checksums for a minute and selected reboot in the fastboot menu and got the white HTC ever since.
Once I did the fastboot and loaded CWm 3 I attempted a NANDroid backup and got a "E:failed to mount /system (invalid argument)" error (tried CWm 2.5, ditto).
At that point I just flashed a new rom and everything went fine.
I think I might have broken something by pressing VolDown while restarting?? Anyhow the scripts worked great and I don't think anything went wrong there. Someone else with an 1.34 EU DesireZ should give it a try, just to make sure.
Thanks for the scripts and guide Ian, they really simplified the whole process and even when you know adb and the long way it's great having a nice bundle like that.
DouD

Help please!!!!!

hello ppl long time whit out visiting my favorite place, but now i really need help, some of my friends just bought a EVO, but every time that he try to turn it on, the phone show the splash scree (htc evo bla bla bla) and than star to looping back never pass from that scree, so how i can fix this isuue, thanks in advance

is the phone rooted? if not take it back to sprint! if its rooted try wiping everything and flashing a rom

Is your friend's phone rooted? Check to see if he or she can get to the bootloader menu. With the phone turned completely off, simultaneously press the DOWN volume button and the power button until the phone starts. After a short pause, a few lines of text should flash across the screen. After that, he or she will be given options on the left side of the screen.
posting & replying via the XDA Premium app.

it looks that is not rooted, only had fastboot, recovery, clear storage, simlock n hboot usb, also i can not go in recovery way to flash rom cause start to looping

At the top of the bootloader screen, you will see either "S-ON" or "S-OFF". If it displays "S-ON" then the EVO needs to be rooted. Your friend should still be able to download and flash one of the RUU roms from HERE. Make sure he chooses the one that coincides with his HBoot. The hboot version can also be viewed in the bootloader menu. In regard to the RUU roms, the exe versions are run from within Windows and the zip version are flashed via the bootloader. If using the zip version, rename the file to PC36IMG.zip.
posting & replying via the XDA Premium app.

my bad the phone is root it show me s-off, could i flash sprint lovers rom the once that should go by hboot

Sorry for the delayed response. I was driving home. Anyway, if you cannot get into recovery, you will need to reflash a recovery. Click on the name "amon_RA" in my signature to download its PC36IMG.zip or click HERE and place it on the root of your SD Card. Make sure that no other file with that name is on the root of your card. Afterwards, power off and then boot into the bootloader. After a short pause, the bootloader should auto-detect the file and prompt you to install. Follow the easyy prompts to install. Installation takes less than 10 seconds. Afterwards, go to your new recovery and flash whatever rom you want. Now, in regard to your question about the Sprint Lover's rom, if there is a version flashable via the bootloader, then yes, it *should* work for you.
posting & replying via the XDA Premium app.

i flash ra recovery but when i try go on it the phone start to bootlooping again,f#ck

Turn off your device and remove the SD card. Afterwards, reboot into the bootloader and then select recovery and see if it will allow you.
posting & replying via the XDA Premium app.

no, still looping hate this phone lol

Okay, do you have a backup of your SD card? If so, reformat and/or re-partition your card. Re-flash amon_RA and try getting into the recovery again. Are you certain you are still "S-OFF"?
posting & replying via the XDA Premium app.

Sounds like you have the same problem a lot of people are having, where you can't get past the White EVO screen.
I can't find the link, but I did save a walk through that someone wrote. It takes some work, but this does apparently work.
You will need to use ADB for this
"Okay, I don't claim to know this will work for your phone nor do I claim it won't ruin your phone. That said if you decide to continue with the instructions below I can not be held liable for any negative/undesireable effects. I don't think you will get any symptoms worse than the dreaded bootloop that has inevitably led you here, but I could be wrong.
I will include almost everything needed to complete the steps that brought my Evo back after writing a complete NV list from an HTC Mogul. (accidentally)
You will need to download the following:
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe
http://shipped-roms.com/download.ph....651.1_Radio_1.39.00.04.26_release_171253.exe
EVO_Softbrick.zip (extract to C:\)
http://www.4shared.com/file/VlJ9mpJR/EVO_Softbrick.html
The zip contains the Adb and fastboot files that you'll need as well as the PC36IMG.zip that you need to flash from the sdcard.
1.Turn Evo on while holding the volume down button. Verify it boots into bootloader. Pull battery.
2.Format sdcard to FAT32 and copy PC36IMG.zip to it, insert card into phone and reboot into bootloader.
This is where the phone should find the .zip and flash the new spoofed Hboot, After the phone reboots it will show as
Hboot version 2.10 this is fine. Time to verify fastboot commands are working.
3.While in bootloader select fastboot by pressing down on the volume button and pressing the power button to select.
4.Plug phone into your computer and cancel any driver installs, open device manager and look for "Android 1.0"
This is where you should double click on "Android 1.0" and choose Update Driver>Browse my computer>Let me pick.
Highlight "Show All Devices" and select Next, Now choose "Have Disk".
5.Navigate to the "Driver" folder in my zip and select androidusb.INF.
Now verify that it installs and shows "My HTC".
Time to start fasboot.
6.Start cmd prompt, just copy the commands (without quotes) below into the window:
"cd C:\EVO\ADB"
"fastboot devices"
Verify that it shows your device.
Now send following commands
(I think all commands should work but some may not be allowed, I refuse to format my Evo just to test it though)
"fastboot erase nv"
"fastboot erase userdata"
"fastboot erase system"
"fastboot erase recovery"
"fastboot erase microp"
"fastboot erase boot"
"fastboot erase radio"
"fastboot flash nv nv.img"
Assuming all has been successful thus far then run the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe.
That should be it. Hopefully your phone boots up. Enjoy.
These steps worked for my friend 1justformail as well, Modified Hboot was created by thefredelement.
"

[TROUBLESHOOTING]/!\ Root | S-OFF | Flashing | RUU | Bootloop | Brick | Resources /!\

Welcome to the HTC Desire (Bravo) Troubleshooting Guide
by bortak
DISCLAIMER: I'm not responsible for anyone bricking their phones. By using this tutorial and any of it's content you accept that you may be flashing system critical aspects of your mobile device, and things can go wrong. By using this guide you agree to put your phone at risk in the hope of fixing it, and you take full responsibility.​
Click to expand...
Click to collapse
BEFORE YOU BEGIN:
1. No. Your phone is not bricked (Touch wood)
2. Make a goldcard. You need it. (Check goldcard section for help)
3. Set up ADB (android de-bug bridge), it's useful when things go wrong.
4. RUU's are DANGEROUS to your phones well-being. Only use them when you absolutely have to.
5. This will help you understand if your phone is "bricked"​
Click to expand...
Click to collapse
IF YOU ARE RESTORING FOR WARRANTY PURPOSES DO NOT USE THE WWE RUU (USE 2.3 GB RUU INSTEAD)​
Click to expand...
Click to collapse
Find your issue here. Then find the corresponding number
NO BRAINER: IF IT'S NOT A DESIRE, USE GUIDE AT OWN RISK.
CONTENTS:
[1]: BOOT PROBLEMS
- stuck on HTC screen/ splash screen
- stuck in bootloop
[2]: ADVANCED BOOT PROBLEMS
- stuck on splash screen with no recovery with S-OFF
- stuck on splash screen with no recovery with S-ON
[3]: S-OFF'ING PROBLEMS
- Bootloader too old for revolutionary
--- upgrading the Bootloader
--- using different software to S-OFF
- installing correct drivers
[4]: RUU PROBLEMS
- stuck on black /!\ screen after RUU failure S-OFF
- stuck on black /!\ screen after RUU failure S-ON
[5]: SLCD BRICK
- black screen after RUU on SLCD phone
[6]: RUU PROBLEMS CONT'D/ GOLDCARDS
- RUU does not run due to CID error
[7]: RUU WITHOUT USB CONNECTION
- Extracting the rom.zip from a RUU (PB99IMG.zip)
- Restoring to stock/ using RUU without USB connection/ connection error
[8]: S-OFF AFTER RUU
- Alpharev write protection explained
- how to S-ON
[9]: DEEP SLEEP
- Rough deep sleep issue cause explained
- "Fix" for deep sleep issue (not waking up after putting phone to "sleep")
[10]: FLASHING CUSTOM RECOVERY
- how to flash a custom recovery using different methods
- Different recoveries available
- PVT4 devices/ ERASESIZE 40000
[11]: ROOT WITHOUT USB CONNECTION/ USB BRICK
- How to root without connecting to USB
[12]: FLASHING SPLASH SCREEN
- How to make a viable splash screen
- Different methods of flashing a splash screen
- Stock HTC splash screen download
[13]: RECOVERY CAN'T MOUNT SD-CARD
- How to remount the SD-Card with fastboot commands
- Troubleshooting fastboot
[14]FLASHING HBOOT/SPL
- How to flash custom HBOOT/SPL
[15]EASIEST ROOT METHOD
- Easiest way to root your phone for Hboot's 1.02 and below
#: RESOURCES
- Useful links/ tools/ resources/ downloads
- Software to help with android e.g. Flashing tools etc.
- RUU'S
- Recoveries
- Radios
- External tutorials
- Drivers​
Click to expand...
Click to collapse

You may find that much of this thread repeats, so it requires you to be patient and pay close attention!
[1]
Click to expand...
Click to collapse
BOOT PROBLEMS
"I just flashed a new ROM, and I get a bootloop.. Help!"*
"I just flashed a new ROM, and it just stays on the HTC screen"
"My phone randomly rebooted itself and now it won't boot"
*This is a fairly common problem, and is solved very easily.
Possible causes of bootloops/ phone stuck on HTC Screen:
- You are S-OFF, and you have not got the correct partition table that is required for the ROM.
- Some ROM's require an SD-EXT partition, you either have not got this or have not done it correctly.
- For whatever reason, the ROM did not install properly.
To fix a bootloop/ stuck on HTC Screen:
[STEP1]- do a battery pull to power off the device (as this is the only way to do so when stuck in a bootloop)
[STEP2]- hold the VOLUME DOWN button and the POWER button to boot into the bootloader
[STEP3]- use the VOLUME UP/DOWN buttons to navigate, and POWER to select. Navigate to RECOVERY.
[STEP4]- select "mounts & storage" and then select the following options
[STEP5]- format boot
[STEP6]- format system
[STEP7]- format data
[STEP8]- format cache
[STEP9]- format sd-ext (IF YOU HAVE IT)
[IF YOU HAVE A BACKUP]
[STEP10a]- go back to the main menu, select "back up & restore", select "restore" and restore the latest working backup.
[IF YOU DO NOT HAVE A BACKUP]
[STEP10b]- go back to the main menu, select "install zip from sdcard", then "choose zip from sdcard", and flash a ROM which you KNOW works.
If you have none, try my failsafe: CyanogenMod
- reboot system now
#PHONE STILL DOESN'T BOOT#
[IF YOU USED YOUR BACKUP, OR A ROM THAT IS NOT CYANOGENMOD]
- Repeat the process, and flash cyanogenmod instead of restoring a backup or a different ROM.
[IF YOU ARE USING A RECOVERY THAT IS NOT CLOCKWORKMOD 2.5.0.7]
- Download Clockworkmod 2.5.0.7.zip and place it in your sdcard.
- boot into recovery, select "install zip from sdcard", then "choose zip from sdcard" and choose "recovery-clockwork-2.5.0.7-bravo.zip"
- repeat [1] from [STEP4] onwards
Click to expand...
Click to collapse
​
[2]
Click to expand...
Click to collapse
ADVANCED BOOT PROBLEMS
S-OFF
"I'm S-OFF, I can't boot recovery and my phone doesn't boot"
For one reason or another, your recovery image is corrupted and when you try to boot into recovery, all you get is the HTC screen
and your phone doesn't boot. It is relatively simple to fix, and there is more than one way to go about doing this. All you need to do,
is to flash a new recovery image.
Possible causes
- I have no idea, however if somebody has an explanation then feel free to PM me.
Repairing recovery, booting phone:
NOTE: If you have a PVT4 Device, go to "Flashing custom recovery". If you are unsure, check just to be safe.
#METHOD 1#
Method One uses Android Flasher to flash the recovery image.
[STEP1]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
[STEP2]- Download Android Flasher
[STEP3]- Download the recovery image. Put it in a place you can remember.
[STEP4]- Run android flasher, tick "Recovery", and press "Begin"
[STEP5]- Browse to where you downloaded the recovery image, select it, and press "open"
[STEP6]- repeat [1] from [STEP4] onwards
#METHOD 2#
Method two uses cmd and requires Android SDK to be set up.
[STEP1]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
[STEP2]- Download the recovery image. Rename it to "recovery.img" for simplicity, and place it in the following directory:
Code:
C:\
[STEP3]- then in cmd type the following commands
Code:
cd c:\android-sdk\tools
fastboot flash recovery c:\recovery.img
fastboot oem gencheckpt [COLOR="Silver"](this command boots you into recovery, ignore the feedback from cmd)[/COLOR]
[STEP4]- repeat [1] from [STEP4] onwards
S-ON
"I'm S-ON, I can't boot recovery, and my phone doesn't boot "
This is a bit of a worse situation, as you cannot flash system critical parts such as the recovery image and just restore a backup.
This unfortunately means that you will lose all of your data when you attempt to fix the phone.
[STEP1]- Make sure that you have a goldcard. If not, create one from the tutorial.
[STEP2]- Battery pull. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
[STEP3]- Download the latest WWE RUU from here
[STEP4]- Run the RUU and wait for completion WARNING: DO NOT, BY ANY CIRCUMSTANCES INTERRUPT THE PROCESS -
THIS WILL MORE THAN LIKELY END UP WITH A BRICKED PHONE - NOT EVEN IF GOD HIMSELF TELLS YOU TO DO SO, OR IF THE US PRESIDENT THREATENS YOU WITH
THERMO-NUCLEAR WAR
[STEP5]- Once the phone is booted, you are now returned completely to stock. You will need to re-root again, and I'd recommend S-OFF
Click to expand...
Click to collapse
[3]
Click to expand...
Click to collapse
S-OFF'ing PROBLEMS
"I tried to S-OFF using revolutionary, but it didn't work"
Possible causes:
- Your Bootloader version is too old. Revolutionary works with 0.93.0001 and 1.02.0001
- You didn't install the relevant drivers
- HTC Sync is interfering with the process
- You have a custom ROM installed -ONLY USE THE STOCK HTC ROM
[STEP1]- Check bootloader version. Power-off, hold VOLUME DOWN and POWER.
YOUR BOOTLOADER VERSION IS NOT 0.93.0001 or 1.02.0001
[OPTION1]- Use Alpharev instead
[OPTION2]- Use a RUU to upgrade to the 2.2 Froyo RUU which gets you to 0.93.001 bootloader version - Follow from S-ON [STEP1]
The latest is gingerbread 2.3.3 however I DO NOT recommend using it.
YOU DID NOT INSTALL THE RELEVANT DRIVERS/ HTC SYNC IS INTERFERING
[STEP1]- Disable or un-install HTC Sync
[STEP2]- Try Again
#DIDN'T WORK?#
[STEP1]- Download and install these drivers
[STEP2]- Follow this guide
[STEP3]- Try again
#DIDN'T WORK?#
[STEP1]- give up on this guide, do some research, start a thread in Q&A if needs be. As a last resort try the IRC client for live support..
Click to expand...
Click to collapse
​
[4]
Click to expand...
Click to collapse
RUU PROBLEMS
"I tried using a RUU, but it failed, and now my phone is stuck on a black HTC Screen with /!\ In every corner!"
Possible Causes:
- You were S-OFF and you flashed a custom bootloader from alpharev
- You didn't check the MD5 Sums before proceeding, and the download may have been corrupted.
- You tried using the wrong RUU
Fixing your problem
Your phone is stuck in RUU mode. RUU mode is like fastboot mode, and can still receive fastboot commands, therefore it can be easily "fixed".
It helps to have a goldcard for this problem, so that you can use any RUU you want.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
S-ON
If you're S-ON it eliminates the possibility of you having a custom bootloader, and the only possibility now is that the RUU was corrupted or you
used the wrong RUU for your device. Therefore, for this process you need a goldcard.
[STEP1]- Create the goldcard from the tutorial
[STEP1]- Use the WWE RUU
NOTE: If you are restoring for warranty purposes, unless you bought an unbranded phone, using
the WWE RUU will VOID YOUR WARRANTY, and you should use the 2.3.3 RUU (link available from #resources)
Click to expand...
Click to collapse
[5]
Click to expand...
Click to collapse
SLCD BRICK (BLACK SCREEN AFTER RUU)
"I restored my phone using a RUU, the process finished and my device is detected by my PC, but my screen is black and does not turn on"
Cause:
- The RUU you flashed is incompatible with your SLCD Device, and was made for the AMOLED Desire
Solution:
[STEP0]- My guess is that because you got yourself to this STEP already, the RUU you used was not for your phone so you already have a goldcard.
[STEP1]- Download the WWE RUU
[STEP2]- Boot into fastboot mode (battery pull since you can't see, hold BACK and POWER. Wait about 10 seconds to be sure)
[STEP3]- Plug phone in via USB and run the RUU
Click to expand...
Click to collapse
[6]
Click to expand...
Click to collapse
RUU PROBLEMS CONT'D/ GOLDCARDS
"My phone isn't functioning properly, and I need to use a RUU,however when I try I get a CID error"
Possible causes:
- You are just using the wrong RUU for your phone. If you have a branded device e.g. on Vodafone, you need to download the latest Vodafone RUU.
- For an unexpected reason, your phone is giving you a CID error, even with an unbranded device [note: the "fix" to this is the logical steps one would take in order
to try and solve the problem, however it has not yet been tested and it is not 100% guaranteed to work for you]
Solution:
The obvious solution to this problem is the goldcard. A goldcard makes the device ignore the CID and effectively enables you to run any RUU without any hiccups.
[STEP1]- Follow this tutorial to create a goldcard
[STEP2]- Insert the goldcard into the device, and re-try the RUU process
Phone doesn't boot so can't get CID like in tutorial
- use this and copy the CID without spaces or commas. Follow the tutorial from further stage.
#DIDN'T WORK?#
- it IS possible you made a mistake in the goldcard process. Follow the tutorial carefully, and try again
#DIDN'T WORK?#
- not all sd-cards will work as goldcards, if you have a spare sd-card lying around try that, or read around some forums for what sd-card definitely works in the process.
The sd-card I use for my goldcard is a Sandisk 8GB Mobile Ultra Class 6 (NOTE: This does not mean I am telling you to buy it, I'm just simply stating that it works.)
#DIDN'T WORK?#
- for now, that's all I can think of. Anyone who has any more ideas feel free to PM me.
Click to expand...
Click to collapse
[7]
Click to expand...
Click to collapse
RUU WITHOUT USB CONNECTION
"My USB port is broken and I need to use a RUU to return my phone to stock. How do I do it?"
"I need to use a RUU because my phone is "broken" but I have no access to a PC"
RUU without USB:
IF YOU'RE S-ON, START FROM [PHASE2]. S-OFF CONTINUE FROM [PHASE1]
[PHASE1]- Because you're S-OFF, the custom SPL (hboot) has write protection, a RUU will not overwrite it and only restore the system, data etc.
[P1/STEP2]- Download the Alpharev Downgrader PB99IMG (MD5: 6c482ccfa6b7093de4ee1a5804ccbdfc - check MD5 matches with MD5 checker, link below)
[P1/STEP3]- Rename it from "PB99IMG_downgrade" to just "PB99IMG.zip" (careful with file xtensions on windows 7)
[P1/STEP4]- put the file in the ROOT of your sd-card (not in any file or folder) and boot into bootloader (poweroff, hold VOLUME DOWN and POWER).
After a few seconds, you will be prompted to update bootloader. Select Yes. DO NOT INTERRUPT THE PROCESS, OR YOU WILL BRICK YOUR PHONE. Wait for it to finish,
reboot and then continue.
[PHASE2]- we need to extract rom.zip from the RUU. If your phone is branded Orange, you will need a goldcard because Orange didn't release any RUU's.. The bastards
[P2/STEP1]- Run the RUU (BUT DO NOT PLUG IN YOUR PHONE OR CONTINUE), move it to the side as it cannot be minimised.
[P2/STEP2]- go to start menu, and use the "run" feature. Type in %temp%
[P2/STEP3]- select "date modified" to "today" (to make it easier to find). There are should now be 2 folders with long names of random characters.
[P2/STEP4]- search the folders for rom.zip and extract it to the desktop.
[P2/STEP5]- Rename the rom.zip to PB99IMG.zip (if on windows 7 and you have hidden file extensions, only make the name PB99IMG,
otherwise it will be PB99IMG.zip.zip - because windows is retarded sometimes)
[PHASE3]- now we need to actually use the RUU
[P3/STEP1]- put the file in the ROOT of your sd-card (not in any file or folder) and boot into bootloader (poweroff, hold VOLUME DOWN and POWER).
After a few seconds, you will be prompted to update bootloader. Select Yes. DO NOT INTERRUPT THE PROCESS, OR YOU WILL BRICK YOUR PHONE.
[P3/STEP2]- Once the process is finished, you will now be S-ON and unrooted with the stock system.
Click to expand...
Click to collapse
​
[8]
Click to expand...
Click to collapse
STILL S-OFF AFTER RUU
"I want to return my phone for warranty, I used a RUU but I'm still S-OFF"
Cause:
- Alpharev's Hboots are write protected, so that they can not be overwritten by a RUU
HOW TO S-ON
METHOD 1#
[STEP1]- Visit Alpharev and download the "Downgrader"
[STEP2]- Flash the downgrader over fastboot. This can be done with Android Flasher, cmd, or fastboot commander (Note: android flasher is the
only program that does not require third party software such as Android SDK or Java JDK)
[STEP3]- You should now notice the title on the bootloader screen is "Alpharev Unlock", run the RUU again and you will have S-ON'd your device.
#METHOD 2#
[STEP1]- Instead of running the RUU again, and putting your phone at risk once more, you can simply upgrade just the bootloader manually,
with the PB99IMG.zip method.
[PHASE1]- we need to extract rom.zip from the RUU.
[P1/STEP1]- Run the RUU (BUT DO NOT PLUG IN YOUR PHONE OR CONTINUE), move it to the side as it cannot be minimised.
[P1/STEP2]- go to start menu, and use the "run" feature. Type in %temp%
[P1/STEP3]- select "date modified" to "today" (to make it easier to find). There are should now be 2 folders with long names of random characters.
[P1/STEP4]- search the folders for rom.zip and extract it to the desktop.
[P1/STEP5]- delete everything EXCEPT "hboot_8x50_0.93.0001_20100810.nb0" and "android-info.txt"
[P1/STEP6]- rename the zip to PB99IMG.zip (make sure it is not PB99IMG.zip.zip)
[PHASE2]- now we need to update the bootloader
[P2/STEP1]- put the file in the ROOT of your sd-card (not in any file or folder) and boot into bootloader (poweroff, hold VOLUME DOWN and POWER).
After a few seconds, you will be prompted to update bootloader. Select Yes. DO NOT INTERRUPT THE PROCESS, OR YOU WILL BRICK YOUR PHONE.
[P2/STEP2]- Once the process is finished, you will now be S-ON.
Click to expand...
Click to collapse
[9]
Click to expand...
Click to collapse
DESIRE DEEP SLEEP ISSUE
"I put my Desire on standby, and now the screen won't turn back on!"
Causes:
- Your phones network not being able to connect to a certain network type (Hard to explain)
Fixing Deep Sleep
[STEP1]- Enter dialpad
[STEP2]- type *#*#4636#*#*
[STEP3]- Go to "phone information
[STEP4]- Change "preferred network type" to GSM only, or CDMA only
Side effects
- your phone will only be able to connect to either HSDPA, 3G or 2G (depending on what you pick), therefore if a certain area is not covered by that network.. you will not have data
Click to expand...
Click to collapse
[10]
Click to expand...
Click to collapse
FLASHING CUSTOM RECOVERY
"I'm using clockworkmod, but I want a different recovery"
"My recovery is damaged and won't let me flash"
As said above, you either want to flash a different recovery to test out it's different features, or perhaps you read that one is better than the next,
so you want a different one. Or your recovery is damaged, and you need to re-flash a different recovery image.
FLASHING RECOVERY
In order to flash recovery, you need to be S-OFF
[STEP1]- S-OFF using revolutionary - if you have any problems go to S-OFF'ing problems, [STEP1]
[STEP2]- Download the recovery image that you have chosen. If you have not chosen one, then I recommend Amon Ra's Recovery
#METHOD 1#
Method One uses Android Flasher to flash the recovery image.
[STEP1]- Poweroff. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
[STEP2]- Download Android Flasher
[STEP3]- Download the recovery image of your choice. Put it in a place you can remember.
[STEP4]- Run android flasher, tick "Recovery", and press "Begin"
[STEP5]- Browse to where you downloaded the recovery image, select it, and press "open"
[STEP6]- Wait for the process to complete.
#METHOD 2#
Method two uses cmd and requires Android SDK to be set up.
[STEP1]- Poweroff. Hold the BACK button and the POWER button to boot into FASTBOOT mode.
[STEP2]- Download the recovery image of your choice. Rename it to "recovery.img" for simplicity, and place it in the following directory:
Code:
C:\
[STEP3]- then in cmd type the following commands
Code:
cd c:\android-sdk\tools
fastboot flash recovery c:\recovery.img
fastboot oem gencheckpt [COLOR="Silver"](this command boots you into recovery, ignore the feedback from cmd)[/COLOR]
*Recovery CAN be flashed using unrevoked, however I haven't personally done this and I'd just recommend S-OFF
PVT4 DEVICES
If you're device is PVT4/ erasezie 40 000 deivce (You can check in bootloader, first line will say Bravo PVT1/2/3/4 SHIP S-OFF/ON)
or by entering the following command in terminal emulator (available in android market):
Code:
su
cat /proc/mtd
You CANNOT use clockworkmod 2.X.X.X because it is incompatible, I recommend using Amon Ra's Recovery as I know it works.
Click to expand...
Click to collapse
[11]
Click to expand...
Click to collapse
ROOT WITHOUT USB CONNECTION
#NOTES: MUST BE BOOTED INTO ROM, ONLY TESTED ON FROYO AND S-OFF - MAY WORK WITH OTHER SOFTWARE #
"I can't connect via usb, but I want to root"
Possible Reasons:
- You are unrooted and you have a usb brick
- you do not have access to a PC/ Mac
- some other strange reason
How to root without USB connection
This process uses temproot and ROM manager to flash recovery. You will only be fully rooted once you flash a rooted ROM.
[STEP1]- Download visionary. Put in on your sd-card
[STEP2]- If you have not got one already, download a file manager (Astro file manager works fine)
[STEP3]- Using the file manager, find Visionary and install it.
[STEP4]- Run visionary, and select TEMPROOT NOW - wait about 30 seconds
[STEP5]- Go to market, and download superuser, then update the binary if needed
[STEP6]- Download ROM Manager, run it, and select "flash recovery"
[STEP7]- Download a custom ROM if you have not done so already, and flash it via recovery.
Click to expand...
Click to collapse
[12]FLASHING SPLASH SCREEN
"I have a branded Desire and want to get rid of the UGLY splash screen"
"I want to use a custom splash image instead of the HTC logo"
How to flash custom splash
#METHOD1#
Method one uses Android Flasher
[STEP1]- If you haven't got it already, download Android Flasher
[STEP2]- Get a 480x800 .bmp image as your desired splash screen
[STEP3]- boot into fastboot (poweroff, hold BACK and POWER) and run Android Flasher
[STEP4]- choose splash, choose the .bmp image and flash the flash the splash
#METHOD2#
Method two uses cmd, and for this you need a .img (also covered in the tut). It also needs Android SDK set up
[STEP1]- Download nbimg.exe and unzip it into C:\
[STEP2]- Get a 480x800 .bmp image as your desired splash screen, rename it to splash1.bmp and put it in C:\
[STEP3]- open cmd and type:
Code:
cd\
nbimg -F splash1.bmp
[STEP4]- you will now have a file called splash1.bmp.nb - rename it to splash1.img
[STEP5]- boot into fastboot (poweroff, hold BACK & POWER)
[STEP6]- in cmd type the following:
Code:
cd c:\android-sdk\tools
fastboot flash splash1 c:\splash1.img
fastboot reboot
Stock Splash screen
- Stock splash screen can be downloaded here. Procedure for changing remains the same.
Click to expand...
Click to collapse

[13]
Click to expand...
Click to collapse
RECOVERY CAN'T MOUNT SD-CARD
I flashed a new recovery, and now my phone doesn't recognise my sd-card. I get the following error:
Code:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
HOW TO MOUNT SD-CARD
[STEP1]- Firstly, you will need Android-SDK (If you don't already have it)
[STEP2]- Boot into fastboot mode (Poweroff, hold BACK & POWER)
[STEP3]- Open command prompt (cmd) and type the following command
Code:
cd\ C:\android-sdk-windows\tools
fastboot oem enableqxdm 0
fastboot oem eraseconfig
ERROR: AdbWinApi.dll IS MISSING
[STEP1]- Go to: C:\android-sdk-windows\tools
[STEP2]- Copy "fastboot.exe
[STEP3]- Go to C:\android-sdk-windows\platform-tools
[STEP4]- Paste fastboot.exe here
[STEP5]- type the following NOTE: THE DIRECTORY IS DIFFERENT HERE TO BEFORE
Code:
cd\ C:\android-sdk-windows\platform-tools
fastboot oem enableqxdm 0
fastboot oem eraseconfig
ERROR: 'fastboot' is not recognized as an internal or external command,
operable program or batch file.
CAUSE:
When you downloaded the Android-SDK installer, it installed the the SDK in a different directory, try using:
Windows 32Bit
Code:
cd\ C:\program files\android-sdk-windows\platform-tools
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Windows 64Bit
Code:
cd C:\program files (x86)\android-sdk-windows\platform-tools
fastboot oem enableqxdm 0
fastboot oem eraseconfig
STILL DOESN'T WORK
Try:
- Different recovery
- Different SD-Card
Possible Reasons
- Your recovery is damaged
- Your SD-Card is dead
- you forgot to insert your sd-card and you're doing all this needlessly?
Click to expand...
Click to collapse
[14]
Click to expand...
Click to collapse
FLASHING HBOOT/SPL
in order to flash a hboot/spl, you need to be s-off
[STEP1]- s-off using revolutionary - if you have any problems go to s-off'ing problems, [STEP1]
[STEP2]- download the hboot image that you have chosen.
#METHOD 1#
method one uses android flasher to flash the hboot/spl image.
[STEP1]- poweroff. Hold the back button and the power button to boot into fastboot mode.
[STEP2]- download android flasher
[STEP3]- download the hboot image that suits your rom. Put it in a place you can remember.
[STEP3.5]- Check the MD5 with tool provided to minimise chances of bricking your phone.
[STEP4]- run android flasher, tick "hboot", and press "begin"
[STEP5]- browse to where you downloaded the hboot image, select it, and press "open"
[STEP6]- wait for the process to complete.
#METHOD 2#
method two uses cmd and requires android sdk to be set up.
[STEP1]- poweroff. Hold the back button and the power button to boot into fastboot mode.
[STEP2]- download the recovery image of your choice. Rename it to "hboot.img" for simplicity, and place it in the following directory:
Code:
c:\
[STEP3]- then in cmd type the following commands
[STEP3.5]- Check the MD5 with tool provided to minimise chances of bricking your phone.
Code:
cd c:\android-sdk\tools
fastboot flash hboot c:\hboot.img
fastboot clear cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
[15]
Click to expand...
Click to collapse
Easiest Root Method
- The easiest root method for the HTC Desire
[STEP1]- Check Hboot version. Poweroff, and hold Volume Down & Power (it's the number after "HBOOT". Examples are 0.75xxxxx, 0.83xxxxx, 0.93xxxxx, 1.02xxxxx)
REVOLUTIONARY
[REVOLUTIONARY]- If your HBOOT version is 0.93 or above (NOTE: Version 1.03 is NOT supported) then continue, if it is below then use the Alpharev method.
[REVOLUTIONARY][STEP1]- Go to revolutionary.io and go to the "Downloads" section, Pick your operating system, choose device as HTC Desire, and choose your HBOOT version (you should already know this from STEP1). Then enter your serial number, it can be found in "about phone" or behind the battery.
[REVOLUTIONARY][STEP2]- Read the documentation page and download these fastboot drivers.
[REVOLUTIONARY][STEP3]- Make sure HTC Sync is disabled, if you have it installed on your PC. Plug your phone in via USB and make sure USB debugging is turned ON (settings> applications)
[REVOLUTIONARY][STEP4]- Extract all of the tools from the revolutionary.zip file and run revolutionary.exe. A CMD window should pop up and show you the progress (See [3] for how it should look like).
[REVOLUTIONARY][STEP5]- When the process is almost finished, it will prompt you to flash a custom recovery, type YES or Y. Follow tutorial number [10] if you would like to flash a different recovery - This is optional and not required if you decide to flash recovery during the revolutionary process.
[REVOLUTIONARY][STEP6]- Download superuser.zip (mirror), put it anywhere on your sd-card (preferably in a path you can remember). Boot into recovery by holding Volume Down & Power (You will see lines of green text flash, this is normal), then using the volume keys to navigate to RECOVERY, and use POWER to select. The phone will now boot into recovery.
[REVOLUTIONARY][STEP7]- Once you are in recovery, use the trackball (if it's broken then use volume keys) to navigate to "install zip from sd-card > choose zip from sd-card > #directory where you put superuser.zip# > superuser.zip > yes"
[REVOLUTIONARY][STEP8]- After the process is finished, reboot, and your phone will now be rooted.
ALPHAREV
[ALPHAREV]- If your HBOOT is 0.93 or below (For version 0.93, you can use revolutionary or alpharev. revolutionary is significantly easier/ quicker), then use this method.
[ALPHAREV][STEP1]- Go to Alpharev.nl and read the page carefully. Download the reflash utility and burn it to a CD.
[ALPHAREV][STEP2]- Reboot your PC, change the boot order for CD/DVD and boot the alpharev disk. Make sure USB debugging is turned ON (settings>applications) and plug it in via USB. Then follow the onscreen instructions.
ALPHAREV][STEP3]- When the process is almost finished, it will prompt you to flash a custom recovery, type YES or Y. Follow tutorial number [10] if you would like to flash a different recovery - This is optional and not required if you decide to flash recovery during the revolutionary process.
[ALPHAREV][STEP4]- Download superuser.zip (mirror), put it anywhere on your sd-card (preferably in a path you can remember). Boot into recovery by holding Volume Down & Power (You will see lines of green text flash, this is normal), then using the volume keys to navigate to RECOVERY, and use POWER to select. The phone will now boot into recovery.
[ALPHAREV][STEP5]- Once you are in recovery, use the trackball (if it's broken then use volume keys) to navigate to "install zip from sd-card > choose zip from sd-card > #directory where you put superuser.zip# > superuser.zip > yes"
[ALPHAREV][STEP6]- After the process is finished, reboot, and your phone will now be rooted.
Click to expand...
Click to collapse
#RESOURCES
Click to expand...
Click to collapse
These are some useful links to and resources you may find... useful.
Tutorials:
- ADB & Fastboot by MatDroid (A+)
- ADB by Droidzone (A+)
- Goldcard tutorial
- ADB and Fastboot for windows by rootSU (A++)
- ADB Help 1, 2
- Creating your own Bootanimation by MatDroid
- 1.03 Hboot downgrade
Tools:
- Android Commander
- Android Flasher
- fastboot commander (Awesome <3)
- Android SDK (adb & fastboot)
- Alpharev 1.8 (S-OFF & SPL's) / Revolutionary (S-OFF & Drivers)
- RevSkills Goldcard generator
- Hboot drivers (need for Unrevoked)
- Java JDK (need for android-sdk, fastboot commander etc.)
- RUU's (Factory ROM's to return phone back to stock i.e. unroot, S-ON*) / WWE RUU in case shipped-roms is dead / Android 2.3.3 RUU
- Visionary - Froyo temproot
Recoveries:
- Ra Desire
- Clockworkmod 2.5.0.7
- Clockworkmod 5.0.2.0
- RMD Recovery (USB Brick Fix)
- 4EXT Recovery/ 4EXT Touch > Recommended, better to use 4EXT Recovery Control from Play Store.
Radios/ RILs: WARNING: EXPERIENCED USERS ONLY
- Radios
- RILs
ANY MORE HELPFUL TOOLS/ LINKS GIVE ME A SHOUT!
Click to expand...
Click to collapse
These are probably not up to date:​

Sticky
Sent from my HTC Desire using XDA App

Very nice thread! Thanks for your work!
Btw I found a little mistake:
STILL S-OFF AFTER RUU
"I want to return my phone for warranty, I used a RUU but I'm still S-ON"
Think it should say "still S-OFF"

boelze said:
Very nice thread! Thanks for your work!
Btw I found a little mistake:
STILL S-OFF AFTER RUU
"I want to return my phone for warranty, I used a RUU but I'm still S-ON"
Think it should say "still S-OFF"
Click to expand...
Click to collapse
Thanks but... you HAD to say it in front of everybody didn't you?

bortak said:
Thanks but... you HAD to say it in front of everybody didn't you?
Click to expand...
Click to collapse
YES!
But you can delete this posts anyways as they are not useful to anyone

Updated 27/09/11
Added video

So, I am a bit of a noob, but does this work with gsm and cdma phones? My CDMA desire won't boot into recovery and so I can't flash a new rom. I downloaded a fresh recovery onto my computer, and was hoping this would let me flash it onto my phone so that i can change to a different rom.

lafonjef said:
So, I am a bit of a noob, but does this work with gsm and cdma phones? My CDMA desire won't boot into recovery and so I can't flash a new rom. I downloaded a fresh recovery onto my computer, and was hoping this would let me flash it onto my phone so that i can change to a different rom.
Click to expand...
Click to collapse
Good question, personally I have never dealt with CDMA Desires so I wouldn't want to give you the wrong advice.. You can try this guide and see if it works for you.. because I have no idea, sorry. Just remember - if the method in the guide breaks your phone in any way, shape or form - I am NOT taking any responsibility.

Made this a Sticky for you and i must say Very Good Work
Nice one

lufc said:
Made this a Sticky for you and i must say Very Good Work
Nice one
Click to expand...
Click to collapse
Thanks Andrew!

lufc said:
Made this a Sticky for you and i must say Very Good Work
Nice one
Click to expand...
Click to collapse
sweeet I'll add the vids and stuff to eventually.. I'm in college at the mo but I next week is free so might see it then

Looking good.
Sent from my HTC Desire using XDA App

Hi. I recently used the camera app to take some pictures. After that, I locked my phone. When I tried to unlock it, the screen remains black. I decided remove and put back the battery. After I did that, the phone still does not turn on. I connected the phone to the charger, the LED does not light up. Is my phone bricked? I did not flash/install anything, I was just using the camera app. I hope anyone could reply as soon as possible. Thanks.
_________________________
Htc Desire
Hboot version: 6.93 (cm7r2)
Rom: Cyanogenmod 7.0.3
S-off: Yes (Using revolutionary)
Recovery: Clockworkmod v5.0.2.0
Rooted using: unrevoked
Radio: unsure (its the latest)

PreScoper said:
Hi. I recently used the camera app to take some pictures. After that, I locked my phone. When I tried to unlock it, the screen remains black. I decided remove and put back the battery. After I did that, the phone still does not turn on. I connected the phone to the charger, the LED does not light up. Is my phone bricked? I did not flash/install anything, I was just using the camera app. I hope anyone could reply as soon as possible. Thanks.
Click to expand...
Click to collapse
well, the fact that your phone doesn't turn on and the LED does not light up on charge suggests to me that your phone is dead. Happened to mine too (exact same symptoms, don't know what cause). It will be covered by HTC, just give them a call.

bortak said:
well, the fact that your phone doesn't turn on and the LED does not light up on charge suggests to me that your phone is dead. Happened to mine too (exact same symptoms, don't know what cause). It will be covered by HTC, just give them a call.
Click to expand...
Click to collapse
I haved s-offed my phone and I know that going s-off will void the warranty. Is there a way to go s-on again while the phone is dead?

PreScoper said:
I haved s-offed my phone and I know that going s-off will void the warranty. Is there a way to go s-on again while the phone is dead?
Click to expand...
Click to collapse
I thought it'd have been pretty obvious that due to your phone being dead, they won't be able to tell. Don't worry about it.

If anyone can help, I'm a little inexperienced with android OS
I'd like to use the usb menu of sense 3, but more like miui. If you know a program that allows me to share the internet from phone to computer and vice versa would be a good alternative. Thanks in advance

krufeee said:
If anyone can help, I'm a little inexperienced with android OS
I'd like to use the usb menu of sense 3, but more like miui. If you know a program that allows me to share the internet from phone to computer and vice versa would be a good alternative. Thanks in advance
Click to expand...
Click to collapse
if you're using MIUI go to options and go to "USB tethering"

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

Can't Enter CWM Recovery After Rooting HTC G2

Can't enter CWM recovery after rooting HTC G2
I rooted my HTC G2 and want to upgrade ROM.
However, I can't get into ClockworkMod Recovery mode. When I boot the phone using Power + Home + VolDown I get this screen:
i.imgur.com/h7MjBT0.jpg
(Since I'm too new to embed images these are the HTTP URLs)
But pressing VolDown does nothing. After a few seconds it moves itself along to this screen:
i.imgur.com/3kNbdsR.jpg
And finally back to this screen.
i.imgur.com/Nvgr5o7.jpg
Any ideas what is wrong, or what I need to do to get into CWM recovery so I can install the ROM zip from the sdcard? (Or is there another method I can use to load the ROM and gapps?)

dbooksta said:
I rooted my HTC G2 and want to upgrade ROM.
However, I can't get into ClockworkMod Recovery mode. When I boot the phone using Power + Home + VolDown I get this screen:
i.imgur.com/h7MjBT0.jpg
(Since I'm too new to embed images these are the HTTP URLs)
But pressing VolDown does nothing. After a few seconds it moves itself along to this screen:
i.imgur.com/3kNbdsR.jpg
And finally back to this screen.
i.imgur.com/Nvgr5o7.jpg
Any ideas what is wrong, or what I need to do to get into CWM recovery so I can install the ROM zip from the sdcard? (Or is there another method I can use to load the ROM and gapps?)
Click to expand...
Click to collapse
You need to remove the PC10IMG.zip from your SD card, after that you will be able to get into recovery

That does indeed allow me to select Recovery, but that boots me to this screen:
i.imgur.com/e2H7hTi.jpg
What's going wrong now?

dbooksta said:
That does indeed allow me to select Recovery, but that boots me to this screen:
i.imgur.com/e2H7hTi.jpg
What's going wrong now?
Click to expand...
Click to collapse
Been a while so I can't say for sure, but I believe that is stock recovery
Take a look here
http://forum.xda-developers.com/showthread.php?t=2348266
You will find links to various recovery options as well as a fastboot guide to flash the image
Pretty much just download appropriate recovery and flash it like
fastboot flash recovery nameofrecovery.img

Well I can get the fastboot to recognize the phone, but whether I try to "fastboot flash" an "hboot x.img" or a "recovery x.img" I get
Code:
FAILED (remote: not allowed)
Which appears to be due to the fact that no Cyanogen recovery is available for the vision-compatible builds!
I have no trouble getting that "recovery screen" I showed in the previous message, but I don't understand how to get anything to actually recover.
So I have this kernel (AndromadusMod) that I want to install, but I'm so confused...

dbooksta said:
Well I can get the fastboot to recognize the phone, but whether I try to "fastboot flash" an "hboot x.img" or a "recovery x.img" I get
Which appears to be due to the fact that no Cyanogen recovery is available for the vision-compatible builds!
I have no trouble getting that "recovery screen" I showed in the previous message, but I don't understand how to get anything to actually recover.
So I have this kernel (AndromadusMod) that I want to install, but I'm so confused...
Click to expand...
Click to collapse
Boot into bootloader and write down all info on that screen, with this I should be able to help further

demkantor said:
Boot into bootloader and write down all info on that screen, with this I should be able to help further
Click to expand...
Click to collapse
Initial boot into ClockworkMod (i.e., Power + Vol Down + TouchPad):
Code:
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
SEP 2 2010, 17:50:38
HBOOT USB PLUG
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
If I select FASTBOOT from that screen then I get
Code:
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
SEP 2 2010, 17:50:38
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
At this point if I run "fastboot devices" from the attached computer I get "SH12SRT203241 fastboot".

dbooksta said:
Initial boot into ClockworkMod (i.e., Power + Vol Down + TouchPad):
If I select FASTBOOT from that screen then I get
At this point if I run "fastboot devices" from the attached computer I get "SH12SRT203241 fastboot".
Click to expand...
Click to collapse
So right now you do have security flags removed but still a stock bootloader so you can't flash with fastboot
...I'm having troubles with links right now (using an experimental version of xda app) so I'm going to just paste in a quote from an old thread where I was helping someone in a similar situation
demkantor said:
um, md5sum is just well a sum, it is a unique algorithm to make sure the file downloaded matches (complete/ no corruption)
you can flash just the Hboot, but it also makes no difference if you were to flash the same firmware over the same firmware. so you don't need to bother extracting anything. ill post when I get home,
~make nandroid in recovery
~download
~check md5sum
~name PC10IMG.zip
~put on SDcard
~boot to Hboot
~let it run, it will reboot halfway (needs to cycle emmc)
~let it finish
~reboot to recovery (via adb)
~reformat all in recovery
~remove PC10IMG.zip from SD
~restore nandroid and reboot to OS
EDIT:
DROPBOX LINK ill upload to op when i get a minute but for know here is this
md5 for g2:
md5 for dz:
*thanks again to nipqer for pointing out my obvious mistakes creating these!
EDIT:
Not sure if i made this clear earlier - flashing firmware using any method is potentially
dangerous. Although very unlikely if you follow these steps I'm still throwing out the waring.
If at all possible it is still best to use fastboot to flash these as an error will be given
to you and you can fix your issue before you reboot and make things permanent.
The above is also dangerous without having true radio s-off, if you are not sure
if you have true s-off - follow these steps:
download THIS COPY OF GFREE md5sum:
now unzip it and open a command where gfree is on computer - have phone plugged
in, debugging on and screen unlocked (after you type "su" you need to grant superuser permissions.)
Now type:
If this is your output, you are in good shape!
@CID: 11111111 means you have superCID (able to flash all software once locked out of)
@SIMLOCK= 00 means you're sim-unlocked (able to use any carrier's sim card)
@secu_flag: 0 this means your radio is S-OFF (This is the important info needed!)
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
---------- Post added at 07:14 AM ---------- Previous post was at 07:11 AM ----------
...looks like it didn't post the links when I quoted.... Check out the fastboot thread from the link I sent earlier... This is post #30 there and those links are still active
If you need help let me know and when I get to a PC I'll link you better

I tried to follow your post, but when I tried su I got "su: permission denied". Proceeding anyway and running gfree_verify I get:
Error: could not open modem device: /dev/smd0
Error: verify could not initialize device!
Click to expand...
Click to collapse
Per your recommendation here I also wanted to try switching to 4ext, but when I ran fastboot erase recovery I got:
erasing 'recovery'...
FAILED (remote: not allowed)
Click to expand...
Click to collapse

Flash the custom PC10IMG.zip I made, the link is in that post #30
Do this like before, put on root of sdcard
When its done you will have an engineering bootloader and 4ext recovery
Then just be sure to remove it off SD in order to get into recovery to flash ROM of choice

That is a great image, and 4ext is a great recovery!
However after I reformatted and restored the AndromadusMod.zip the phone just boot cycles to the "htc" screen.
Attached is a current screenshot of the hboot System Info. Should I give up, or am I close?

You have the g2 engineering bootloader now, but the dz one is needed for most ROMs above ICS as it has a larger system partition, do the same thing you did but this time flash the dzPC10IMG.zip from the post I linked you, then ROM and gapps

I think there's something wrong with that dz bootloader: It only ever offers to update [SD ZIP]. I have to physically remove the sdcard and delete the PCIMG10.zip after it runs its install cycle in order to get into recovery; it's impossible to get it to startup in any other mode that allows sdcard access.
After I do delete the PCIMG10.zip, reformat all but sdcard, and install the ROM (which appears to "succeed" suspiciously quickly) I get the boot loop problem again and have to pull the battery to get back into hboot....

Sounds like a bad download, check the md5sum to make sure its good

Yes, MD5 matches that given in the post.

Maybe I misunderstood, so when when flashing the PC10IMG.zip through bootloader it works and changes your bootloader and then you remove the file off sdcard and you are able to get to recovery?
If that all is working then you are in good shape, try another ROM/gapps
Try a gingerbread ROM just to make sure you can get up and running.

Correct. So I just re-wiped and installed this Gingerbread kernel: http://elite-force.eu/elitemod/MOD_EliteKernel_120319.zip
It took a "reasonable" amount of time for 4ext to install that one.
But now it's doing the same boot cycling as before, though much faster than on the JellyBean kernel I previously tried ?
Is there a known stable kernel I should be trying? Maybe I'm as bad at choosing kernels as I am at choosing women....

Haha,
Well a kernel alone won't help, you will need a kernel and a ROM (and probably gapps too)
Try cyanX, its a ROM I put together a few years back, its gingerbread based but has a lot of ICS and jb features back ported to it
Once we know that is working then move on to newer ones

Ah ha: that does help! Putting a JB ROM on did the trick. For some reason in all my reading I didn't get the message that the ROM isn't part of the kernel....
Thank you for all your help!