Develop Bugs

[Q] Experienced Magic User needs help with Desire (flashing AmonRA) (

hey guys, need some help:
been flashing radios, roms and spls succesfully in the past year on my htc magic.
recently upgraded to the desire and wanted to start flashing here as well.
i can see the device with adb devices (or fastboot devices), so driver must be installed correctly
but when i fastboot flash recovery (AmonRA) it sends ok but then fails writing with the error "fastboot failed (=remote not allowed)".
the desire has froyo sense stock on it and booting into fastboot gives me this info:
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010, 17:52:18
so i have s-off which is good, but why can't i get amonra on the phone?
do i need another hboot? and what about spl?
please someone explain what i'm missing here!
thx,
v.

You could try and use the Android Flasher utility. Makes it easier and I've had no problems with it.

hey, thanx for your answer, and nice prog!
it didn't work though: i booted the phone into fastboot, started the prog and gave it amonra's recovery. it all looked like it worked. the phone also reboots just like it says in the prog. but it still doesn't get the recovery on the phone.
so here's my updated status report, i hope someone can help me out:
i rooted succesfully yesterday (the unrevoked method). the version from their site that you can download now didn't do the trick though, i got the missing CID error that lots of others also get. i searched that problem and found the unrevoked prog in its version 3.2. that one worked. so the phone is rooted and unrevoked also flashed clockwork mod recovery.
i then succesfully flashed a rom (oxygen) and this all works which is nice.
my problem is that i
1.) can't boot into recovery by pressing home + power. i have to fastboot, then choose bootloader, then recovery. this starts clockwork mod.
2.) i can't get amonra to my phone. it won't work via fastboot flash recovery (error mentioned in post #1) or via the program mentioned in post #2.
i'd really like be able to flash recovery and radios via fastboot commands, i'm used to it and i don't like the fact that i get an error when i try this.
what's causing the problem here?
it must also be related to the fact that i couldn't get amonra installed via the program mentioned in post #2.
is it my hboot?
i'm rooted and also s-off.
so what is causing this locked up behavior?
i'd apprecciate any help you can give me,
thx,
v.

Try flashing it from the phone itself.
Place amonra.img in sdcard root directory.
From terminal emulator or over adb type flash_image recovery /sdcard/amonra.img
Then reboot, this can be done from recovery or from android.

already tried that method yesterday (sorry i forgot to mention it).
didn't work either.
i just ran unrevoked again and clicked "custom recovery" and added the amonra recovery. unrevoked ran thru the rooting process and in the end it succesfully flashed amonra. at least i can now use amonra.
but i still can't use any fastboot commands, i always get the "failed (remote: not allowed)" error.
what the hell is going on here?!
greetz,
v.

update:
i flashed a patched hboot from alpharev and this did the trick!
i thought s-off meant i could do all these fastboot commands but i must have been wrong (or some other reason, i don't know).
i downloaded the "PB99IMG_bravo_cm7" zip (because i'm running CM7 at the moment). normally you should flash these via fastboot but as i said this didn't work on my phone so i had to use the alternative method:
"You can also download the corresponding PB99IMG zipfile, put it on your sdcard, and rename it to PB99IMG.zip. Then start the phone in HBOOT mode (VolDown+POWER) to flash the HBOOT without a PC."
now i can finally work with fastboot commands again, no more "failed (remote: not allowed)" errors!
greetz,
v.

Weird. S-Off should allow you to use fastboot commands. Very weird indeed but that's just how it goes sometimes

Having trouble of flashing an hboot other than Alpharev Oxygen

Hi, I've S-Off'd my phone using AlphaRev's ISO.
By default, it comes with an hboot suited for the Oxygen rom.
When I tried to flash the Bravo Stock 1.8 HBOOT using the
fastboot flash hboot bravo_alphaspl.img command, the output claimed everything
went OK, but when I reboot the bootloader, it still says on the top "AlphaRev Oxygen", as if nothing happend.
I also tried the other method, of putting a zip file called PB99IMG.zip which contains the hboot in the root of the sdcard and rebooting to bootloader.
The bootloader claims the device is incorrect :-/, any suggestions ?
Thanks!

Update: Managed to fix it.
Had to create a gold card in order to flash hboot.
The only hboot that worked is the bravo stock.
And the method of flashing was PB99IMG.zip in the root of sdcard and rebooting
to bootloader.

[Q] stuck in hboot

i tried doing a factory reset then I was reading a guide on a similar site about unrooting my phone and downloaded a file called pg32img.zip and put it on my sd card. I booted into hboot on my phone and the only things i can do are reboot/power off and use bootloader which automatically goes to trying to flash the file i put on there but it gives me the error "main version is older" everytime, and kicks me out to the main menu giving me the same options. I cant do anything besides try to reflash the thing or reboot my phone. At the top of the hboot it says "security warning" if thats any help.
tried doing adb devices while my phone was plugged in and it said no devices found.
screen looks like this
***security warning**
VIVO_W XB SHIP S-ON RL
HBOOT-0.97.0000
RADIO-1.09.01.0622
eMMC-boot

Please use the Q&A Forum for questions Thanks
Moving to Q&A

schmoop said:
i tried doing a factory reset then I was reading a guide on a similar site about unrooting my phone and downloaded a file called pg32img.zip and put it on my sd card. I booted into hboot on my phone and the only things i can do are reboot/power off and use bootloader which automatically goes to trying to flash the file i put on there but it gives me the error "main version is older" everytime, and kicks me out to the main menu giving me the same options. I cant do anything besides try to reflash the thing or reboot my phone. At the top of the hboot it says "security warning" if thats any help.
tried doing adb devices while my phone was plugged in and it said no devices found.
screen looks like this
***security warning**
VIVO_W XB SHIP S-ON RL
HBOOT-0.97.0000
RADIO-1.09.01.0622
eMMC-boot
Click to expand...
Click to collapse
First step is to delete the PG32IMG.zip file off of the SD card. If you leave it on, HBOOT will try to install it every time you boot into HBOOT.
The security warning that is now showing indicates that the PG32IMG.zip you tried to flash was an older version that you currently have on your DInc2.
The adb.exe command will only work when the phone is booted normally or booted into recovery mode. It is expected behavior for adb not to work when you are booted into HBOOT mode.

tpbklake said:
First step is to delete the PG32IMG.zip file off of the SD card. If you leave it on, HBOOT will try to install it every time you boot into HBOOT.
The security warning that is now showing indicates that the PG32IMG.zip you tried to flash was an older version that you currently have on your DInc2.
The adb.exe command will only work when the phone is booted normally or booted into recovery mode. It is expected behavior for adb not to work when you are booted into HBOOT mode.
Click to expand...
Click to collapse
+1 to this. Don't fret. Let us know of any other issues.

[Q] HTC Desire Z Stuck on HTC Logo All ADB Command Not Working

Hi
Sorry for my english is bad.
Htc desire Z stuck on HTC Logo Please Help Me
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36.27
All Fasboot Command Working
C:\Android\android-sdk\platform-tools>fastboot devices
SH17DRT00916 fastboot
but all adb command Not Working
C:\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Android\android-sdk\platform-tools>adb shell
error: device not found
I did my card Gold Card SD
PC10IMG.Zip downloaded from shipped-roms site was not installed
What else can I do?

yerin6 said:
Hi
Sorry for my english is bad.
Htc desire Z stuck on HTC Logo Please Help Me
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36.27
All Fasboot Command Working
C:\Android\android-sdk\platform-tools>fastboot devices
SH17DRT00916 fastboot
but all adb command Not Working
C:\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Android\android-sdk\platform-tools>adb shell
error: device not found
I did my card Gold Card SD
PC10IMG.Zip downloaded from shipped-roms site was not installed
What else can I do?
Click to expand...
Click to collapse
I have pretty much the same phone. I've bought it in Austria. Once stopped workig... I can navigate in the bootloader menu, but anything I choose, it freezes. OK, it calculates CRC. No image files, just like my mem card also unreadable with PC. No flashes help. I've downloaded stock RUU. It communicates with the PC says fastboot usb, starts to flash and stops at reboot bootloader and never goes any further....

As your bootloader is S-ON you can't flash custom rom's, adb won't work until the device is past the bootloader and starting up the rom.
Not all sd-cards work properly in Gold mode (it isn't correctly made Golden if your pc wants you to format the sd-card), try another one or format your current one in FAT32 and put the latest PC10IMG.zip (Download one of the .zip files here: http://shipped-roms.com/index.php?category=android&model=Vision rename it to PC10IMG.zip, make sure you don't have extentions hidden in windows for the renaming to be accurate) in the root of it and start the device in the bootloader (holding power and volume down). Then it should flash the PC10IMG.zip as normal.
You can also try to boot into recovery mode and recover your rom from there (as your bootloader is S-ON chances are you've still got stock recovery).
Then, if you still want to, you can try and unlock the bootloader and root your phone.
If the above isn't working for you you can always try to unlock your bootloader via htc (you only need fastboot to work for this). Register at http://htcdev.com/bootloader/ and follow the unlock instructions. After that you should be able to flash a custom recovery like Clockwork mod (http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.1.0-vision.img) and install one of the many ROM's available in the android development section of the Desire Z formums.
You can also try and flash this PC10IMG.zip (http://files.virtuousrom.com/vision/misc/PC10IMG.zip) it contains the correct bootloader (S-OFF hboot), clockworkmod recovery and the latest T-Mobile radio (There's no ROM included in here, you can restart the device in recovery and install a custom ROM).
If this doesn't work, post your problems here, I'll take a look at them and try to help you to get further.

[Q] Why do I have Revolutionary HBOOT?

Hey guys!
I used an RUU to flash my Desire back to the old software (build) version 2.10.405.2. This gave me Android 2.2 (Froyo). I think this is the one that came with my phone (if my memory serves me well). Those who bought it before me had to upgrade from Eclair to get Froyo. I think I had Froyo already.
But why does it say "Revolutionary" and "S-OFF" in my HBOOT menu? Doesn't the RUU flash everything?
Also, when I go into Recovery I get the usual warning triangle icon. So there are no menus, there used to be CWM (clock work mod) with menus.
So the recovery image has been flashed and the ROM image has been flashed? But just not the HBOOT image?
Can I download the HBOOT image only somewhere? And then flash it using Fastboot Commander?

U have to flash alpharev downgrader first then run the ruu, that way it will be completely stock s-on

So I guess I was on the right path then. I mean I just flashed it with what seemed to be the stock HBOOT image. I visited the AlphaRev website and downloaded a file called PB99IMG_stock.zip. This ZIP file includes a file called hboot.img. I used the command prompt to write this file to the phone in fastboot mode.
But all that did is it changed the title in the HBOOT menu from "Revolutionary" to "AlphaRev".
BEFORE;
-Revolutionary-
BRAV PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010,17:52:18
AFTER;
--- AlphaRev ---
BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010,17:52:18
I will try the downgrade image now.
What will the command be?
Code:
fastboot flash hboot bravo_downgrade.img
Is that right?...
And then I will run the RUU? Right? And this will flash the proper stock HBOOT image?

From what i understand you have Stock hboot now (you said you've flashed it)
So yes, now just flash downgrader and run RUU.

How to get back to stock HBOOT image
It worked! Thanks jmcclue! The commands are all the same as for flashing any HBOOT image.
Just for reference, this is how to do it.
Go to AlphaRev website and download the file "bravo_downgrade.img".
Set the phone to fastboot mode.
Connect it to the computer with a USB cable.
Open a command prompt (preferably with elevated privileges).
Navigate to the folder where you saved the "bravo_downgrade.img" file.
Send this command to flash it.
Code:
fastboot flash hboot bravo_downgrade.img
Send this command to reboot.
Code:
fastboot reboot-bootloader
Send this command to erase cache.
Code:
fastboot erase cache
Disconnect the phone from computer.
Select "REBOOT" from the Fastboot menu. Either that, or take out the battery and put it back in.
Boot/start up the phone normally. If you previously took out the battery, put it back in and press the power button.
Connect it to the computer. If it asks you what kind of connection, choose Charge only.
Run the RUU (ROM Utility Update) that includes the HBOOT image. If it includes the HBOOT image the file size should be around 160 MB.
Follow the on-screen instructions to complete the operation.
When done, the phone should reboot and you should have the stock HBOOT image and the stock software version.
Note! Don't remove the cable when you are sending commands to the phone. Only remove it when all commands and operations are performed.
Requirements:
RUU file for your phone.
Android SDK installed.
Java SDK installed.
HTC Sync
(ADB driver for your phone)
I am assuming you already have the SDKs all installed and set up. If not, you will have to do that first.
You will probably also need the HTC Sync installed on the computer. I think this is required for RUU to work properly. I was only receiving ERROR 170 when running the RUU ("phone not connected" or "not found" or whatever), until I installed HTC Sync. You will find it on HTC website or you can find the old version on your original 2 GB microSD card you got with the phone. I personally prefer the old version because the new HTC Sync feels like bloatware and is resource-hungry for no apparent reason (just some flashy graphics).
You may or you may not need the ADB (Android Debug? Bridge) driver for your phone. I have mine, downloaded from XDA Developers forum years ago. It's said that installing HTC Sync will include the proper drivers for ADB and solve the issue with missing driver for "Android 1.0". I didn't find this to be true. I tried different, supposedly HTC drivers only packages, from different web sources, and none of them worked. Except for the one I found on XDA Developers forum. I'm not 100% sure but I think this driver is only needed when the phone is in recovery mode. But it doesn't hurt to install it just as a precaution or at least have it prepared and ready to install.
To get RUU files:
You can either go to the HTC Developer website and try to locate the files there, or you can visit a website like Shipped-ROMs and try locating a "Bravo" or "Desire". Bravo is the codename for Desire. Then you probably want to download the ones that have "WWE" (World Wide English) in the names. These are based on English but have translations to other languages as well. And you want the ones where it says "HTC" in the name, if your phone is not carrier specific and not re-branded. Mine is not.
This is the name of the RUU file I used:
RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe
This gave me Android 2.2 which is what I had on my phone when it was new.
Check:
To verify that you have the proper HBOOT version and that you have S-ON you can show the HBOOT menu (volume down + power button). Here is what it should look like.
AFTER flashing with RUU;
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010,17:52:18
BEFORE flashing with RUU;
AlphaRev Unlock
BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.9999
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010,17:52:18
BEFORE flashing the HBOOT with bravo_downgrade.img;
--- AlphaRev ---
BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30_2
Aug 10 2010,17:52:18

Patched HBOOT images (Revolutionary & Alpha Rev) are protected against downgrades
Hi k3lcior!
If I was on stock HBOOT, then why did it say "Revolutionary" on top of the screen when I hold Volume down and Power button to enter HBOOT menu?
Yes, I did say I flashed it. Or that's what I thought I did. What I meant is I ran the RUU (ROM Utility Update) for build 2.10.405.2. I mentioned the name of the file in the post above. This is a 166 MB file. It's not an OTA update or anything of that nature, like updates of 30 MB or less. So running the RUU (166 MB) should flash everything on the phone, not just parts of it.
RUU file is big because it includes the ROM, the recovery image, and it should also include the HBOOT image. But for some reason when I ran this it only flashed and replaced my ROM image, and the recovery image. It failed to flash and replace my HBOOT image.
I now know why.
Downgrade protection, these HBOOTs cannot be overwritten by an OTA or RUU, unless you flash a downgrader HBOOT first.
Click to expand...
Click to collapse
This is a quote from the AlphaRev website. It's more clear to me now why it didn't work in the first place.
I actually had the "Revolutionary" HBOOT because that's what I used. I used Revolutionary to get S-OFF and root access on Android 2.3.3 on HTC Desire. It of course also installs a custom recovery image (CWM or Clock Work Mod) with "Revolutionary" background and "Revolutionary" printed on HBOOT menu.
So my conclusion is that both "Revolutionary" and "AlphaRev" HBOOT images have this "downgrade protection" feature. That's why running RUU to restore everything to stock version fails to restore the HBOOT image to it's stock version. The HBOOT image on the phone was being protected. That's where the "downgrade image" comes in. You use that to remove the protection first. And then you run the RUU and it will flash everything, including the HBOOT image.
After all, the Revolutionary is a later development based on AlphaRev, and other tools and exploits. So it's not hard to imagine that they share same features. The last time I used AlphaRev and Unrevoked to get root and S-OFF was when I had Android 2.29 (I think it was build 2.29.405.2). I had no problems running the RUU to restore everything back to stock version, including the HBOOT image. But I did not downgrade it that time. I mean I just used the RUU for the same version, as the one that was already on the phone. And of course I didn't use Revolutionary at that time.
So I'm not sure... it's either because of the fact that I used Revolutionary this time (instead of Unrevoked + AlphaRev), or it's because I went from Android 2.3.3 to Android 2.2 (a downgrade), or it's because I was going from HBOOT version 6.93.1002 (came with Revolutionary) to HBOOT version 0.93.0001 which comes with the RUU for (a downgrade).
It may also be that the AlphaRev HBOOT image didn't have the "downgrade protection" until version 1.80. So it's possible that I used some old version of the AlphaRev that didn't have this feature when I rooted and S-OFFed the old Android 2.29.
One of these cases apply, but I'm not sure which one. In either case, I got rid of the custom HBOOT image. It's all back to stock now.

FWIW;
When you visit the AlphaRev website you will see that there is a table with two columns that hold file names and download links. One just says "Download". Th other says "PB99IMG". If you are doing this from a computer, with the phone connected to the computer with a USB cable, then you probably want the files from the column that says "Download".
If you for some reason don't have access to a computer, or you don't know what command prompt is, you don't know how to install the Android SDK so that you can send the fastboot commands... well, whatever the reason may be, then you probably want the files from the column that says "PB99IMG". These are ZIP files that include the same files you will find under "Download", with the addition of some extra files/tools. The idea is to place it on an SD card and let the phone do the rest. It's sort of this "unplugged" and automated way of doing things.
You can also download the corresponding PB99IMG zipfile, put it on your sdcard, and rename it to PB99IMG.zip. Then start the phone in HBOOT mode (VolDown+POWER) to flash the HBOOT without a PC. It is however still necessary to either restore your nandroid, or reflash your ROM after doing this. The partition LAYOUT has changed, the actual data still needs to be 'moved'.
Click to expand...
Click to collapse
I'm not sure how it helps renaming a ZIP file. If the file name is "PB99IMG.zip" (with the zip extension already) how does it help renaming it to... something like "PB99IMG.zip.zip"? Is that what they are saying? That you should add one more zip extension to the end of the file name... or that you should add one if there is no extension. I'm not sure what they mean, but I would go with "PB99IMG.zip".
I have not tried this method myself, but this may be easier to use for some user. Instead of having to install the SDK et al. You may be able to even download the ZIP file right on the phone, without even touching a computer. You just need to have it on the SD card of the phone. And enter the HBOOT menu. I guess there is some Bat file or something inside the ZIP file that automates everything else.

@ OP
glad u got sorted. its good to see that u actually took the time to read and understand what u did, unlike other user who just post problems coz they cant be bothered to read anything and try to understand how things work so :good: to u.
Now about the PB99IMG. Your bootloader will only read PB99IMG it so thats why u have to rename it from PB99IMG_downgrade to PB99IMG. The downgrade part is only there so u know what file it is