yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] counterfeit187:
I see that you put up a big red warning about formatting /misc... my hero is still dead and I went and bought an epic, but I'd like to fix the Hero if at all possible, ever find a way to recover a phone that has had /misc wiped? For the record, my phone has no recovery on it (formatted that also), no rom (because I was in the process of wiping everything to install a rom), and the update.zip and hercimg.zip options didnt work. bootloader does nothing when I try to boot, it goes straight to a white screen with "HTC" in green letters in the center and stays there forever, if I turn it on with the usb plugged to my PC then it is that same white screen with green HTC in the center but will say "fastboot usb" in red in the top corner (But wont accept any fastboot commands. ADB doesnt recognize the device either.
[Hero CDMA Android Development] s0be:
if you get into fastboot, try pressing volume down to switch to HBOOT (which should check the /sdcard/HERCIMG.zip)
[Hero CDMA Android Development] tomh1979:
Any chance this can be submitted to rom manager for a super easy install.
[Hero CDMA Android Development] jasonmaloney:
ROM Manager already contains the latest version considered stable by Koush (the maintainer of ClockworkMod Recovery). I believe he said the HeroC doesn't need the 3.x line except for the ext4 support.
[Hero CDMA Android Development] tomh1979:
I take it that was the january release version of CWM then, if so ok.
[Hero CDMA Android Development] counterfeit187:
It never actually booted to fastboot mode. While it does say "fastboot usb" in the top left corner, there is no menu and no response to any button presses. HTC is displayed in green letters in the center of the screen. "FASTBOOT USB" AND "htc" are the only things displayed. I'm not actually booting to fastboot, it just says that if I turn the phone on and plug it to pc with USB cable.
[Hero CDMA Android Development] wesssider:
Jason Maloney the pilot? Who joked through an emergency beach landing? :D

Listen to the audio: http://www.nytimes.com/2011/04/06/nyregion/06plane.html
[Hero CDMA Android Development] AjaxBU:
Lol, that guy is going to get the book thrown at him. What a fool, I want to slap this kid and I hope he loses his license(never thought I'd say that).
[Hero CDMA Android Development] jasonmaloney:
Pulled this until the following get done:

Change Ib8565064: Heroc: Remove 'misc' from recovery.fstab

Change I0f935aad: recovery: Prevent the users from doing stupid things.
[Hero CDMA Android Development] il Duce:
good call.
[Hero CDMA Android Development] jasonmaloney:
You guys are going to love this change:

recovery: fix the typo that allowed formatting /misc

This is a great example of the reason I warned in the OP that this was bleeding-edge, untested code.

OP updated with new build to correct this. I HIGHLY recommend flashing this new build to prevent future mishaps!
[Hero CDMA Android Development] jaybob413:
But wait, there's more!

You may also be interested in rolling this in at some point.

Display mount point in title of confirm_selection for format

This will display the partition name in the title string where you are asked to confirm formatting the partition. Fortunately, I have only had this happen to me a couple of times, but I am sure some of you can relate to the sinking feeling you get when you see the message "Formatting /sdcard" being displayed on your screen. Basically, this just changes the title string from "Confirm format?" to "Confirm format? /sdcard".
[Hero CDMA Android Development] hunterd13:
have not done that yet but can see how easy it could be to do.
[Hero CDMA Android Development] il Duce:
hopefully once you get the commit jaybob413 just linked (awesome btw!) merged, you'll change the text color to GREEN :)
[Hero CDMA Android Development] c00ller:
CMW existed for far too long without this
[Hero CDMA Android Development] jasonmaloney:
New build in the OP. Contains the fix for preventing formatting of /misc as was put forth by Cyanogen.
[Hero CDMA Android Development] c00ller:
Could you please add the md5 to the OP?
[Hero CDMA Android Development] il Duce:
Out of curiosity does this also contain the text string fix that jaybob413 linked? I thought the 4/9 build already had the fix for format MISC... Also, your download only seems to work from a computer, which is fine of course but for some who are mobile only users, the links do not work. I intend to DL some stuff tomorrow like this recovery, CM7 final, maybe a nightly, who knows. Thanks again.
[Hero CDMA Android Development] jasonmaloney:
No, this one is straight from cm source.

That was a quick typo fix I made to correct the code that was supposed to exclude formatting misc. Cyanogen submitted a patch that goes one step further and also eliminates formatting recovery from recovery (among other things). This contains that patch.

I'll have to look into this. Something to do with MIME types I think.
[Hero CDMA Android Development] il Duce:
ok thanks for the info. I will wait patiently (or forever lol) for the one with the text string fix. What color is this recovery? I know that's a silly question, and I assume it's orange, but I've never flashed it.
[Hero CDMA Android Development] jasonmaloney:
Orange. You could always log into Gerrit and +1 his patch if you want to see it happen.
[Hero CDMA Android Development] jaybob413:
I have a strange feeling that you are looking for something green. Attached is the Green Lantern version with the fix. ;)
[Hero CDMA Android Development] il Duce:
sweet! Now I have a question for you or really anybody. I now use custom MTD partitions, so I assume the steps I would need to do are as follows:

-change mtdpartmap.txt (if I want)

-nand backup

-power off

-flash GL recovery (from hboot)

-boot recovery (from hboot)

-wipe

-flash firerat 1.5.8 recovery

-wipe again

-reboot recovery

-nand restore

-flash fr boot

-reboot
[Hero CDMA Android Development] c00ller:
Looks correct to me, il Duce
[Hero CDMA Android Development] 24601:
Duce, I think you have to wipe AFTER you flash FR-recovery and before you adb reboot recovery.
[Hero CDMA Android Development] stayclean:
There are instructions in the Firerat's thread.... ;):p
[Hero CDMA Android Development] il Duce:
****ty ****. well, I got all the way to restore so far (it's restoring as I type) - and thanks stayclean, smartass lol. You guys are right, I guess I'll do it all over again, even though I can't imagine it wouldn't work the way I did it. Better safe than sorry I guess. It'll just add another 15 minutes to the process :mad: The good news is, the recovery looks GOOD! thanks jaybob :)
[Hero CDMA Android Development] c00ller:
Woops, my bad for the preemptive confirmation :(
[Hero CDMA Android Development] Drunkpilot:
Yeah, you need to wipe system, cache and data after flashing fr-recovery. It will tell you that once you flash it though. You don't have to adb recovery reboot though. You can do that in the advanced settings. I wipe dalvik as well since it is in advanced as well and reminds me to reboot recovery; I have forgotten and it only lead to more work. I don't know if ra has that option, but CWM does, so no computer needed.
[Hero CDMA Android Development] il Duce:
Yeah thats how I did it, reboot recovery from recovery, no issues. I also edited my post to reflect the proper steps for what I did, thanks all for the help.

sent from a series of tubes.
[Hero CDMA Android Development] mongolx:
Running latest • recovery-clockwork-3.0.2.4-heroc-20110411.img confirmed. Clockwork app in clockwork recovery still shows clockwork recovery 2.5.0.7. Any way of fixing this?
[Hero CDMA Android Development] il Duce:
You mean your recovery screen shows 3.0.2.4 and rom manager shows 2.5.0.7? Ignore rom manager, hell, delete it, it's sorta redundant/useless IMO. If you don't beleive me, tell me what you like about the app/what functions you use from it, and I'll tell you how to do it without the app.
[Hero CDMA Android Development] mongolx:
Duce ;) I think Jason posted somewhere to use the app, can't find link tho!?. Or could be interpretation was wrong. Just trying to emulate the pros. ;). In past I've used it but now I use 3.xxx to backup, restore and wipe.

SuperHero
[Hero CDMA Android Development] GeezyAF:
I agree with Duce, mongolx. If you're having trouble flashing this recovery, just go through fastboot and erase the recovery you're currently using.
[Hero CDMA Android Development] Pyr0TeK:
Hey JM... any chance you can add a HERCIMG.zip to the OP also for the latest 4/11 version so those who would like to flash via hboot?
[Hero CDMA Android Development] 24601:
Here is one for the green lantern version (although to me it looks more like the Green Hornet :)).

*EDIT 4/26/2011* Removed zip. May be improperly compiled HERCIMG.
[Hero CDMA Android Development] Pyr0TeK:
Thanks... coolness.
[Hero CDMA Android Development] Drunkpilot:
I haven't found a way. I had tried putting in different folders, but I didn't want to delete the recovery in there.

I use the manager to save some steps mostly- its a couple of taps. It is not good for flashing if you are using firerat's as it won't flash the fr-boot at the end. Its good for getting back to a 2.5.x recovery in 2 taps. I can't imagine why it would be needed though.
[Hero CDMA Android Development] mongolx:
No trouble at all with recovery its just the app J tickles my finger! Gave it all trying to change app but ooo well…..
[Hero CDMA Android Development] 24601:
When I d/l the green lantern I got the "E: cant' open /cache/recovery/log" and " . . . . last_log" messages. I thought nothing of it until today when I had to nand restore. Of course the restore was garbage. I tried the "rm -rf *" fix but it did not work. Is there any other known fix? Or did I miss something in the d/l process? I went back to 2.5.0.7 and the restore is fine.
[Hero CDMA Android Development] il Duce:
That's weird. I'm using it and nand backup and restore both work (I did that the other day) and I get no errors..... Maybe some missed step with firerat? I say start over, follow the steps I asked about (which are now edited in that post for what I did exactly) a page or two ago. When and where in recovery do you get that error? I can try to duplicate it, also what rm -rf fix are you talking about?
[Hero CDMA Android Development] 24601:
Thx duce. I went back and looked at your post 92, my issue is not with firerat, or at least I don't think so. The "E: can't open /cache/recovery . . . " messages occurred when I first flashed the green lantern. I flashed through Hboot and when the recovery loaded, those two "E:" messages were at the bottom of the screen. They went away as soon as I started to work with the recovery, and they never re-appeared. I flashed a number of items since with no issues. And even created nand backups with no issues. When I nand restored today, howev er, I get multiple fc's and a completely unstable environment. This was my first attempt at a restore with the new recovery. I did a complete RUU (I know, you think I have an ORD problem ;) ) and flashed the recovery again, but no "E:" errors this time, and the restore was still garbage. I reflashed 2.5.0.7 and restored the same backup and it came through fine. I presume there is something within my system that does not like this recovery.

The -rf * fix was found in a G1 thread where others were having the same issues after flashing an earlier recovery. The steps are:

adb remount

adb shell

cd /cache

rm -rf *

Not a biggie, 2.5.0.7 has always worked great for me (and it covers both amend and edify scripts), but the green hornet sure is nice.
[Hero CDMA Android Development] il Duce:
Huh. Weird. Well, I got no errors and restore is all good here :confused: Maybe I have an idea.... I originally flashed regaws s-off and later flashed the end-spl, so my hboot is 1.46.2.xxxxx or something, I doubt that matters but maybe, is yours different? I also made the HERCIMG.zip for the recovery using root expl, and maybe you made on a mac.... maybe that matters? Also my rat settings have a HUGE cache at 95 lol (I'm skeered) and maybe that matters?

EDIT: upon further review, and if my thread stalking has paid off lol, you use a mac and have some weird mac zip maker thingy right? Here is the one I made that works fine for me: http://dl.dropbox.com/u/5669105/HERCIMG.grn3024rec.zip
[Hero CDMA Android Development] 24601:
Thx for spending some time on this. Well, my hboot is 1.47.0000, I have not flashed the eng-spl, perhaps I should. But, I have created and flashed through hboot a number of HERCIMG's created the same way I created the green hornet. Yes, I use a mac, but not any special zip creator. The mac has a compress files feature built in that allows you to "right click" and create zips. Again, used it many times to create and flash HERCIMG's through this bootloader. I'm stumped. I'll see if flashing the 1.46 eng-spl does the trick. Eh, if not, WTH, at least I get to keep flashing ROMS and RUU's. I feel like Jimi Hendrix in upstate New York . . .

*EDIT* Well, that was interesting. Flashed Darch's eng-spl 1.46.2000 and it flashed fine. Booted the phone, splash screen came up for about 2 secs then blinked to the picture of the open box with arrow down for about a half second, then black screen for a second, then back to splash screen. Phone booted fine. Went into bootloader and it still says 1.47.0000. I think I may have bigger issues . . .

*2nd EDIT* I flashed your version and got the same results. Re-flashed 2.5.0.7 and the restore went fine. I'm resigned to the fact I can't use the green hornet :(
[Hero CDMA Android Development] Drunkpilot:
That 1.47.2 almost seems like you melded regaw's and darch's together. I am 1.46.2 and have only had 1 green lantern issue when I tried to restore an nfx backup. I have restored both a 2.5.0.7 backup and GL with no issue though.

Its funny how each phone really is different.
[Hero CDMA Android Development] 24601:
Oops, that was a typo. My bootloader is 1.47.0000. I fixed my earlier post.
[Hero CDMA Android Development] il Duce:
OK, so upon many PMs and further thought, I think the issue with GL cwm 3.0.2.4 and firerat IS incompatible somehow. I have firerat and my original setup was 125 95 (I know that's crazy blah blah whatever) but it all worked well with GL cwm. Yesterday I tried to change my mtdpartmap to 110 50 (I know that's crazy blah blah whatever) but I then got the EXACT error you had been decribing. After booting into the ROM which went fine and all, I could NOT download anything from the market or stock browser, tried the s0be fix 3 times to no avail. In TE the df -h showed /cache was full, so I went and changed mtd AGAIN to 110 75, did NOT recieve the error in recovery, booted fine and downloads worked again with no s0be fix. My conclusion = GL cwm 3.0.2.4 and FR 1.5.8 work together, but only if your /cache is natural, and not pushed via symlink to /data. I still have huge room in /data and LOTS of apps, all works well (even though I'm "wasting" about 10mb - oh well :)).
[Hero CDMA Android Development] 24601:
What's your df -h now say for /cache?
[Hero CDMA Android Development] il Duce:
avail = 75

used = 51.3

To be clear, in an effort to boot properly, I wipe cache and dalvik AFTER restoring the nand and before FR-boot. It used to be somewhere around 65 used.
[Hero CDMA Android Development] 24601:
Thx. So, here's the plan:

1. nand backup

**wipe data, system, cache, boot, dalvik**

2. reflash current 2.5.0.7 to get rid of firerat settings

3. echo "mtd 95 75" > /sdcard/mtdpartmap.txt

**wipe data, system, cache, boot, dalvik**

4. Hboot green lantern 3.0.2.4 (I plan on using the zip you created)

5. Reset firerat

a. wipe data, system, cache, boot, dalvik

b. flash fr recovery

c. wipe data, system, cache, boot, dalvik

d. reboot recovery

e. wipe data, system, cache, boot, dalvik (I know, this is overkill)

6. restore nand backup

7. wipe cache and dalvik

8. fr boot

Does this look right? I want to wipe my current firerat settings before flashing the new recovery because my previous hboot of 3.0.2.4 left me the error messages. I want to have firerat completely removed before flashing green lantern. Also, I use firerat 1.5.7. I doubt that makes a difference.

*EDIT* Added the additional wiping suggested by duce below.
[Hero CDMA Android Development] il Duce:
oops you got a free thanks :) (I'm sure you deserve more) anyway yeah that looks right, except WTF is 5 -

IN POST EDIT: looks like you edited :) nevermind, yeah looks good.

POST POST EDIT: maybe you should wipe wipe after nandroid and before/after you reflash 2.5.0.7 and before you hboot 3.0.2.4? This is assuming you're looking for a healthy dose of overkill lol.
[Hero CDMA Android Development] 24601:
^^^*EDIT* Not sure I got enough TP for all that wiping ;)^^^

Thx. I'll do later tonight and post results for everyone to see.
[Hero CDMA Android Development] il Duce:
@24601 this is weird, I looked in YOUR hboot zip for GL cwm 3.0.2.4 and there is a _MACOSX folder with the full name of the recovery image in it, a _MACOSX file with no file extension, the android-info.txt (which has no file extension?), and the recovery image (recovery-clockwork-3.0.2.4-heroc-04-11-2011.img) is not named correctly, it should be recovery.img :confused::confused::confused: When I make a hboot zip the ONLY thing in there is recovery.img and android-info.txt
[Hero CDMA Android Development] 24601:
Is that the one I posted at 105? If so, I'm gonna remove it until further inquiry.
[Hero CDMA Android Development] il Duce:
Yes.

I assume the missing extensions have something to do with my windows box not reading you mac creations and that's fine. BUT the extra files are weird, and the recovery not being named "recovery.img" is a no-no, which I'm sure you just forgot lol. I can't tell you how many times I've made hboot zips, and either forgot to name the thing I'm flashing right, or forgot to name the zip in uppercase, etc. Prolly a good idea to pull it, I mean it ain't gon' hurt nobody, but it would maybe waste some time trying to flash a non-working zip ;)

EDIT: looks like oldjackbob thanked you for that post, I wonder if he flashed it, because if it worked, either everything I know is a sham, or my work computer is a pile and renames images and creates folders named _MACOSX on it's own ......

/me is confused, and calling for oldjackbob
[Hero CDMA Android Development] dpeeps74:
the recovery doesn't have to be named recovery.img. mine is named recovery-clockwork-3.0.2.4-heroc-04-11-2011.img in my hercimg.zip.
[Hero CDMA Android Development] il Duce:
what !?!?!? ok now I am losing it. Put it up, I wanna try to flash it.
[Hero CDMA Android Development] dpeeps74:
ok, here ya go.
[Hero CDMA Android Development] il Duce:
Ok nevermind me flashing, just realized with firerat that would suck. So you can really flash that? Anybody else flash hboot zips without renaming the image? I coulda swore regaw said the images had to be named the simple way like "system.img" and "recovery.img" and "splash1.nb0" __ I'm confused.

sent from a series of tubes.
[Hero CDMA Android Development] The Fer-Shiz-Nizzle:
I have always thought the same. Anytime I create a new HERCIMG.zip, I follow that same rule (ie rename the .img file to its simple partition name, such as recovery.img)
[Hero CDMA Android Development] oostah:
hay Duce i downloaded the zip and put on sd hbooted it no problems. you can open the zip and see he didnt rename it.

on a another not can a recovery increase you speed/performance.
[Hero CDMA Android Development] il Duce:
Not afaik but a reboot can ;)

sent from a series of tubes.
[Hero CDMA Android Development] Drunkpilot:
I have flashed with more than recovery.img. I think the issue are letters before "recovery" like "GLRecovery" won't work. Bootanimations too. I had tried with the lantern and it didn't work until I dropped the gl.

I need to look back and see the error you guys were talking about. I was getting a larger cache until I wiped dalvik after I had restored my nandroid and it dropped it back to 1.1mb; it was at 2 and said I was full. Sorry if my comments don't pertain to what you were talking about exactly.
[Hero CDMA Android Development] 24601:
Thx, man. On the better safe than sorry route, I pulled the zip in post 105 just in case there's an issue. I try to rename my .img's as "recovery.img", etc., I must have missed on that one. Not sure about all the mac stuff in there. Back when I was routinely making battery mods I was using this same method and had many successful users. So, the mac stuff probably doesn't matter, but you never know.
[Hero CDMA Android Development] il Duce:
Yeah I imagine hboot just ignores the stuff that didn't matter.

@drunk - I can't get gl and rat to like eachother, please share any missed steps or ideas or wisdom, I'd love to figure it out.

sent from a series of tubes.
[Hero CDMA Android Development] 24601:
Here's my results. I followed these steps (with the exception of I moved #3 in front of #1). When I flashed 3.0.2.4 this time I did not get the "E: can't open /cache/recovery . . . " messages I had the first time I tried. On reboot, the splash screen stayed up for at least a minute, and perhaps longer. Boot animation was painfully long but to be expected when wiping dalvik. Then bootlooped. Did not loop on the tick though, spun for a few seconds after the tick. Am gonna try a backup from a few days ago.

*EDIT* Went to an older backup, was able to get past bootloop for about 10 seconds. However, the environment was the same as reported earlier when I first d/l the green hornet. Very unstable, fc's immediately, etc., then after 10-15 seconds sent me back to b/l a couple times, then the phone reset back to splash screen. Went back to 2.5.0.7 and everything booted fine. Again, my hero just doesn't like the green hornet :(
[Hero CDMA Android Development] Drunkpilot:
Duce, let me go back and read so I can get caught up. Is this only an issue with 4/21 or was this with 3/26 too?
[Hero CDMA Android Development] Drunkpilot:
I have gotten the same e: cache issues as well. I think it was working fine because I was working with a nand from 2.5.0.7.

I have actually seen that when on 2.2 as well.

I noticed the error, but it still booted. I ended up doing the df -h and noticing my cache @ 2 instead of 1.1. I went back into recovery and wiped dalvik cache and rebooted and it is back to normal (or 1.1).

You might want to try the fr-removal tool (I think it's version (1.6 that I use and firerat's 1.5.7)

I like to format: boot, system, data, cache, dalvik

Flash fr-removal tool

Format/wipe: system, data, cache, dalvik cache

Reboot recovery (in advanced with wipe dalvik

Flash fr-recovery

Format/wipe: system, data, cache, dalvik cache.

Reboot recovery

flash zip or nand restore

Flash fr-boot

Reboot

See if this helps at all. I did a couple of backups that didn't seem to take and I tried to restore. With 3.0.2.4 greeny and 2.5.0.7. I had some others. I have had issues backing up with all of the cwm 3 series either stopping or corrupt in some way.

The other thing is, 2.x flash amend and edify. You would think it would be the other way around and the 3's would be more versatile.

I will have to fool around a bit more.

I know you don't like rom manager, but it would save you a lot of time to flash a 2.5.x. I keep the GL in a HERCIMG on my SD to go there if I want.
[Hero CDMA Android Development] il Duce:
Thanks for the thoughts. I actually am all setup on GL cwm 3024, was trying to help 24601 get back to it, and oddly it sounds like it's a no go on his device. I'm all good, even though my cache setting is huge. I have like 90mb free and cannot think of what apps I could possibly want to fill it with lol. Thanks again.

@24601 could this recovery be "fatter" than 2507 and maybe your mtd should be 100 75? Nevermind, not only is that illogical, but you're happy with where you're at.
[Hero CDMA Android Development] shortarm:
OP vs GL

Curious to know what the difference is between the OP .img and GL-recovery?

I assumed that the GL was just a green version instead of orange.

But given the Firerat's talk that has GL in the instructions, I started wondering if there is a difference.