Develop Bugs

New user needs help - nand backup

Hi all, I just rooted my phone using Amon-ra and unrevoked -- latest one. I am trying to do a nand backup so I can flash a kernel onto my phone, but I cant find the option.
When I power into the bootloader, and navigate to recovery. It gives me a red yield sign with an exclamation point. When I press volume up and power, it takes me to the Android system recovery <3e>. I see options to reboot system now (reboots back to main screen), apply sdcard:update.zip (which gives me some error), wipe data/factory reset, wipe cache partition.
I downloaded Rom manager but thats only for clockwork recovery.
What am I doing wrong? What do i need to do?
Thanks for the guidance.

Android with the yellow exclamation is the stock recovery. What happens when you hold vol down & press power?
BTW, this is also Q&A material, not development.

If I push volume down and power, it takes me to the Hboot/Bootloader, whatever that screen is called, where you have option to fastboot, recovery, etc.
Sorry I didnt realize this was development. I have been reading a lot of threads on this so I assumed incorrectly. Please feel free to move it, or I can do it manually.
Thanks again

wasvsdal said:
If I push volume down and power, it takes me to the Hboot/Bootloader, whatever that screen is called, where you have option to fastboot, recovery, etc.
Sorry I didnt realize this was development. I have been reading a lot of threads on this so I assumed incorrectly. Please feel free to move it, or I can do it manually.
Thanks again
Click to expand...
Click to collapse
What do you see at the top of the HBoot screen? S-ON or S-OFF?
Also, what H-Boot version?
Sounds like your Unrevoked didn't take. reboot your phone and try again.

It says
Supersonic EVT2-3 SHIP S-OFF
HBOOT-0.97.0000
MICROP-041F
TOUCH PANEL-ATMEL224_16AB
RADIO-2.15.00.09.01
Aug 19 2010, 14:29:00

Try using ROM Manager to flash Clockwork.
Sent from my PC36100 using XDA App

I was told Amon-RA recovery was the best. I followed the instructions step by step. Even saw the $ change to #. What went wrong? Is there no way for me to create a backup with flashing other things? I mean do I even have a rooted phone? I know the superuser app doesnt have anything in it. Its blank! But I have a superuser app.

wasvsdal said:
It says
Supersonic EVT2-3 SHIP S-OFF
HBOOT-0.97.0000
MICROP-041F
TOUCH PANEL-ATMEL224_16AB
RADIO-2.15.00.09.01
Aug 19 2010, 14:29:00
Click to expand...
Click to collapse
I think you can do one of 2 things:
1. Redo Unrevoked. If you scroll down to Recovery in the Fastboot/Bootloader screen and it takes you to the stock recovery then it didn't flash recovery.
2. Boot into your phone and, making sure USB is turned on in Settings > Applications > Development, use this from Amon-Ra's post
via fastboot
Code:
Copy recovery-RA-evo-v1.8.0.img to a location where fastboot can find it.
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)

Ok just tried doing the above:
Copied that recovery.img file to my sdcard.
Restarted phone into Hboot
Phone checked for PCIMG -> wasnt there
Then went into Fastboot
the following are the options that i have: Bootloader, Reboot, Reboot Bootloader, and power down.
not sure what to do?

Bumping it like im sooo fine.

wasvsdal said:
Bumping it like im sooo fine.
Click to expand...
Click to collapse
ok, go into fastboot. plug into computer. then do what he said. ya. any questions???

[Q] Fix Bootloop with RUU?

Hey guys.
Couldn't find any other posts so I'm hoping I'm not breaking any rules.
Yes, I'm a n00b. Was handed down an old Desire Z still using Froyo and decided to install Cyanogenmod.
My attempted install didn't get past rooting for reasons unbeknownst to me. I used CM's guide: Installing CM for Vision. I got stuck at Rooting the Desire Z.
I followed it to the letter and made it to step 10. Upon reboot the phone reaches "HTC - quietly brilliant" and sounds it's little jingle. Goes black after a while and plays the jingle/logo again. And again. And again. I have to remove the battery to get it quiet again. I can make it to HBOOT and the screen displays (beware verbosity):
Vision PVT ENG S-OFF
HBOOT-0.84.2000 (PC10*****)
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
Sep 8 2010, 15:56:38
HBOOT
<VOL UP> to previous item
<VOL DOWN. to next item
<POWER. to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SYSTEM INFO
IMAGE CRC
I believe the guide I followed installed a custom recovery image. Clockwork Recovery? Accessing RECOVERY results in a quick buzz with HTC logo and a prompt return to FASTBOOT. FACTORY RESET yields the same result. SIMLOCK comes up with "SD init fail !!! Process done, reboot device?" SYSTEM INFO comes up with what the title hints. I'll list if need be. IMAGE CRC comes up with checksums:
hboot: 0x2A125CF4
boot: 0xF7629548
recovery: 0x3921C16D
system: 0xD5CE705B
That's about as far as I can get from concise.
I've downloaded an RUU for it, have the Android SDK and Odin.
I'm not sure if the RUU will fix anything or how to install it. So my question is, how do I get my phone booting again?
Any feedback would be very appreciated.

you used THIS GUIDE? step ten is to check if gfree worked, did it? you didnt need to reboot first to check
anyway looking at your current spl i believe you should be fine, just flash a custom recovery in fastboot - download from CM SITE and check md5
cbc776e7941ebf030e9fa39473d5b6f1
Click to expand...
Click to collapse
then boot into fastboot mode and have phone connected to pc
open a cmd in the location of fastboot.exe and type type
fastboot devices
Click to expand...
Click to collapse
if you see yours then all is good, if not then you need to set up fastboot.exe (odin is only for sammy)
then type
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
and then
fastboot reboot-bootloader
Click to expand...
Click to collapse
once rebooted
adb reboot recovery
Click to expand...
Click to collapse
now youll be in clockwork and flash a rom from there (i suggest looking into 4ext recovery)
oh and for the above to work you need to change name of recovery you downloaded to recover.img, also need to have changed your path in environmental variables or have the image in same folder as fastboot.exe is in

Thanks!
Thanks so much I owe you big-time. And thanks for the quick reply.
I followed your instructions, got Clockwork up, factory reset, got stock firmware back up and flashed Cyanogenmod and it's all running fine now. (I did have to Cyanogenmod twice) I'll be sure to take a look at 4EXT. Thanks again.

[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

[HELP!] HTC One X Problems!!

Hello everyone!! I have for four hours now, tried to fix my newly bought HTC One X. I have bought this phone, softbricked from a friend for £35, as it was a bargain if I could get the phone to work. Here is my problem:
Phone loads directly into Fastboot when you switch it on. I've searched online, followed countless steps, and it says that I need a RUU file that is higher than my current one. If I can get this file, then I am able to charge it using the USB with script in CMD method, and then follow the steps on the RUU file. My current RUU file number is 4.18.401.4
Now I've searched everywhere for a version higher that's compatible. I cannot find one.
So I think I have to go through the S-OFF method. But I can't due to it booting in fastboot.
From what I know about what has happened to the device. My friend wanted to flash custom rom. He did not do a nandroid backup (He forgot) and then tried to flash the rom which was incomplete. This has left him in Fastboot mode.
All I remember is earlier on when I was experimenting, it saying:
HTC__01 something like that. If that helps at all.
Here is all information about the device. Please!! Please help me!!
***Relocked ***
ENDEAVOURU PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013, 18:24:41
Battery level is too low to flash
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN
_________________________________________
This is the first time that I have ever owned a HTC device. Please go friendly on me!! I've only owned Samsungs in the past.

xRapidReload said:
Hello everyone!! I have for four hours now, tried to fix my newly bought HTC One X. I have bought this phone, softbricked from a friend for £35, as it was a bargain if I could get the phone to work. Here is my problem:
Phone loads directly into Fastboot when you switch it on. I've searched online, followed countless steps, and it says that I need a RUU file that is higher than my current one. If I can get this file, then I am able to charge it using the USB with script in CMD method, and then follow the steps on the RUU file. My current RUU file number is 4.18.401.4
Now I've searched everywhere for a version higher that's compatible. I cannot find one.
So I think I have to go through the S-OFF method. But I can't due to it booting in fastboot.
From what I know about what has happened to the device. My friend wanted to flash custom rom. He did not do a nandroid backup (He forgot) and then tried to flash the rom which was incomplete. This has left him in Fastboot mode.
All I remember is earlier on when I was experimenting, it saying:
HTC__01 something like that. If that helps at all.
Here is all information about the device. Please!! Please help me!!
***Relocked ***
ENDEAVOURU PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
Jun 21 2013, 18:24:41
Battery level is too low to flash
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
HBOOT
REBOOT
REBOOT BOOTLOADER
POWER DOWN
_________________________________________
This is the first time that I have ever owned a HTC device. Please go friendly on me!! I've only owned Samsungs in the past.
Click to expand...
Click to collapse
No RUU for this high main version you need just to flash custom recovery, then install the rom and flash the boot.img from rom archive and that is everything and the recovery is diferent for KitKat, JB and Lolipop all the 3 recoverys are different

Thant said:
No RUU for this high main version you need just to flash custom recovery, then install the rom and flash the boot.img from rom archive and that is everything and the recovery is diferent for KitKat, JB and Lolipop all the 3 recoverys are different
Click to expand...
Click to collapse
THANK YOU SO MUCH FOR REPLYING SO FAST! I really wasn't expecting such a fast reply.
So, am I correct in saying.
I find the latest CWM recovery for htc 1x
download it
>>How would I flash it please, through cmd or not, if so, do you have the cmd code by any chance.
Then, I download stock rom from internet, I'm guessing it's going to work similar to the samsungs, I just find any stock rom for the HTC 1 X and it should work fine.
In CWM Recovery, I flash the stock rom as if it were a custom rom.
Wipe Cache
Wipe DavLink
Format
Then flash the boot image and reboot.
I'm guessing that is it and it would work then?
I'm so sorry if I am wrong and you have to explain. This whole S-ON thing and HBOOT is getting to my mind... I'm not used to all this !!
EDIT: i'm not entirely sure what you mean when you say that all three recoveries are different
EDIT2: So when I download the ROM I leave it in the zip folder and just flash like normal. Or do I extract to get the boot.img

xRapidReload said:
THANK YOU SO MUCH FOR REPLYING SO FAST! I really wasn't expecting such a fast reply.
So, am I correct in saying.
I find the latest CWM recovery for htc 1x
download it
>>How would I flash it please, through cmd or not, if so, do you have the cmd code by any chance.
Then, I download stock rom from internet, I'm guessing it's going to work similar to the samsungs, I just find any stock rom for the HTC 1 X and it should work fine.
In CWM Recovery, I flash the stock rom as if it were a custom rom.
Wipe Cache
Wipe DavLink
Format
Then flash the boot image and reboot.
I'm guessing that is it and it would work then?
I'm so sorry if I am wrong and you have to explain. This whole S-ON thing and HBOOT is getting to my mind... I'm not used to all this !!
EDIT: i'm not entirely sure what you mean when you say that all three recoveries are different
EDIT2: So when I download the ROM I leave it in the zip folder and just flash like normal. Or do I extract to get the boot.img
Click to expand...
Click to collapse
You want to install stock JB rom on your phone then:
1. Download Philz recovery 5.15.9 then go in recovery and mount sd card copy your nandroid backup to a folder on the sd card. For flash recovery use command from cmd fastboot flash recovery nameofrecovery.img
2. You are in recovery format data,system cache and dalvik cache then restore your nandroid backup
3. Go in fastboot and flash the boot.img from nandroid backup with the command fastboot flash boot boot.img
4. Reboot and that is

Also you will have to unlock your bootloader again if it is relocked

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!