yashsingh1/xdaforums huggingface dataset:
[HD2 General] fflakes:
FYI, I just came across this volume tweak, stole from the Touch forums but works perfectly for HD2, I added a bit more info.

As follows:

"If you are willing to do a reg edit

here is a copy of someone else's post I saved

wish I could give "Pete S" more credit

________________________________

Using a registry editor (ie. Rescoe or Total Commander), navigate to HKLM\Software\HTC\VolumeOverlay\3rdPartyAPClass and you will see a list of apps which use the slimvolume control. You have to add keys (new folders) for all the apps you want to add.

Under these keys you have to create a String value containing the Window Classname of the app. You can get these names using a program like FdcSoft Task Manager v3.1 (or I used BSB Tweaks Rotation to see the class, then removed them afterwards).

I've listed a few of the common ones below to save you the time.

Create a Key: "Nitrogen" Create a String Value called “ClassName” with value "CNtgWndMain"

Create a key: "CorePlayer" Create a string value called "ClassName" with value "wCorePlayer"

Create a key: "Opera" Create a string value called "ClassName" with value

"Opera_MainWndClass"

Slacker Radio is "Slacker"

TCPMP is "TCPMP_Win"

And so on. Take care to get caps and lower case correct, and don't include ""s. If you get the window class names wrong, don't worry, it just won't work till you get it right.

The settings take effect immediately, no need to restart.

PS: If you're not confident editing the registry, best not to do it. If you do, take great care, don't accidentally delete any keys!"

Enjoy.
[Droid Eris Android Development] iflip:
ive been using nand backup since eris was rooted. I recently started having this error come up when trying to nand b/u and nand restore. i flashed the fresh rom 2.1 and then i ran into issues. got an error on

my screen:

"Error...Run "nandroid-mobile.sh" via adb!"

everything worked fine up until now.

And i dont think its the rom that did this.

lately, all the latest roms ive been using have been having shutdown issues, requiring battery pulls following shutdown. Im not sure if all the batterypulling broke my amon ra, but im stuck with having to reflash the rom when having issues with it. very time consuming, battery draining, and very annoying. anyone else having this issue or any suggestions??
[Droid Eris Android Development] dmullins80:
Mime has done that too. I've noticed it when my battery was below 15%. Try connecting to a charger or let your battery charge a little bit.

After I did that I had no more problems.
[Droid Eris Android Development] T.C.P:
yea its most likely because your battery is low, charge it a bit then restore
[Droid Eris Android Development] rvpartsguy:
ya it usually does that with a low battery .....

only happened to me once ..... but a very wise man told me this was almost always the cause
[Droid Eris Android Development] iflip:
ive been charged all day. still no luck.. :-(
[Droid Eris Android Development] Magnum72:
I think I had the "Error : run 'nandroid-mobile.sh restore' via adb!" problem before when trying to restore a rom in recovery, but i think it was because of renaming the folder inside the "nandroid" folder on the sd card.
[Droid Eris Android Development] iflip:
i didnt rename anything
[Droid Eris Android Development] t2noob:
quick question what recovery are you using?

I had problems similar to this on CLOCKWORKMOD recovery, to the point where i couldn't flash or restore any nand. I even tried flashing root rom and that also failed. when It tried to write boot and the system in failed and then i had to replace my phone because it wouldn't even boot after trying to flash root rom.
[Droid Eris Android Development] iflip:
using amon ra.

i think im gonna try to reinstall recovery img via adb. any requests to stop me go right ahead.
[Droid Eris Android Development] iflip:
i tried reinstalling recoery img via adb and still nothing!!!! AARRGH!!!
[Droid Eris Android Development] iflip:
Sounds lime my issue js rather unique. Doesnt seem like anyone else had this problem yet. Well i guess for now im .sh out of luck.

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Eris Android Development] paintguy:
I had this problem when the memory on my sd card was almost full. I deleted a bunch of zip files and a bunch of the nand backups and it worked fine. I've also experienced the low power and the invalid rename issue too. hope this helps.
[Droid Eris Android Development] iflip:
That sounds like a solution. Thx. i will trh to free up space on sd. Ive been pretty full for a while tho, but never encountered this msg.

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Eris Android Development] viclabs.303:
nand restore error run nandoid mobile via adb

I just got this error and simply needed to have power plugged in to complete the restore. Hope this helps.
[Droid Eris Android Development] bftb0:
Well, there's two ways to go about solving this type of problem.

One would be to use the built in functionality of the Recovery menu system to copy the recovery log file (/cache/recovery/log) to your SD card and then - oh, I don't know, maybe look at it to see what error messages are in there? Really super-duper users could even just do a "adb shell cat /cache/recovery/log | more" with the recovery console still running, but that presumes a high level of skill (operating a space bar on the keyboard).

The other way would be to ask a bunch of strangers on the internet to speculate about what the problem might be.

I prefer the 2nd way; it's far less efficient, but much more entertaining. Hours of fun, really.

J/K. Have a look at Amon_RA's announcement post for the Eris, where he says:

Always check recovery.log before posting your issues!

bftb0

:)
[Droid Eris Android Development] RogerPodacter:
i am having the same exact problem with my nexus one. the error: run 'nandroid-mobile.sh restore' via adb. i am a new root user and this is my first time attempting to do any nand restores, and i get that error. is it possible i used the newer recorvery which is not compatible with cyanogen 5.0.7 ROM? i just followed all the links on the rooting guide and said to use all latest files.

my battery is 100% and my sd card has 2gb of free space. i'm really at a loss what to do. thanks.
[Droid Eris Android Development] adaneshade:
Verify that there is a folder named nandroid in the root directory of your SDcard. If not, create one. I was having the exact same problem until I did that.
[Droid Eris Android Development] RogerPodacter:
there is definitely a nandroid folder on my sdcard root drive, and inside that folder are 3 backup folders with associated files. i'm going nuts.
[Droid Eris Android Development] vantagejuan:
you can rename the back up files with names starting with "BDS-". You can't rename the folder directly under "nandroid" in your directory. if you do, you will get the "run mobile.sh" error. you will also get this error if your battery is low or you have no storage left. the folder directly under the "nandroid" folder it is your serial number. if you're having issues, just go to the "other" menu and select "send recovery.log to SD card." then go in and search the recovery.log file on your sdcard for "serialno=" right after that there will be a 12 character string of capital letters and numbers directly followed by lower case letters that are useless for this purpose. Create a folder with the same name as that string (capital letters and numbers only, no lower case) and place your previously renamed backups into that folder and voila! you'll be able to restore them.
[Droid Eris Android Development] RogerPodacter:
My issue never got fixed, but I did try a different memory card, copied over my backups, and now they restore fine. And I did rename them to "stockROM" and they restore just fine. So the name does not matter.

I tried formatting the original memory card then copied all the contents back onto it, and still will not work with nand restores. It took me 5 hours to dump my card and reload it, so some files on that card must be screwing something up. Sucks cause now I'm stuck with this small card and with my music on it now It's full, so I have no room to do anything. Wish I could get my main card working with backups.
[Droid Eris Android Development] iflip:
the problem i was having was lack of sufficient storage space on my sd card. I deleted a 600mb movie and was working fine again. if you are maxing out the storage then delete some files. just to be on the safe side, keep at least 2-400 mb free space on the sd.
[Droid Eris Android Development] RogerPodacter:
It wasn't lack of space, I had 2 gb free space on the memory card. It just wouldn't work.
[Droid Eris Android Development] vantagejuan:
Change the name of your folder directly under the "nandroid" folder on your non-functioning SD card to the exact same name as the one on your functioning card. it's your phone's serial number and if that folder's name is at all different from your phone's serial number it won't work. once you rename that folder, put the backup folders (originally named "BDS-whatever") in that folder. that should do the trick. If you can read and write data other than your nandroid backups and restores to the non-functioning card, then there's no reason you shouldn't be able to do backups and restores. it probably just worked on the newer card because nandroid automatically created the appropriately named folder on it.
[Droid Eris Android Development] RogerPodacter:
You don't understand. The name is identical on both cards, I just copied the entire folder over and it suddenly works.

On the non working card, even if I create a brand new backup and DONT change the name, and immediately try to restore that backup, it fails. Original name and all.
[Droid Eris Android Development] vantagejuan:
Hmmm ... it just doesn't add up. If you can read and write to the card and you can access it from your phone, there's no reason it wouldn't be able to backup and restore. And if it works just fine on another card, then it's not a software compatibility issue. Compare the file systems of the two cards and if they're the same (probably FAT32) then you have an anomaly on your hands. If the "working for everything but NAND" card has a different file system, format it to the other card's file system type and see if that works.
[Droid Eris Android Development] cornbreadfarts:
i had this problem.

i did adb shell with phone connected and then tried restore and it restored normally.
[Droid Eris Android Development] RogerPodacter:
It goes even deeper. So first yes I checked both cards and they are both fat32. Then I even emptied the memory card completely, formatted it, and put the files back on the card. And it STILL doesn't work. It's weird cause it has no problem writing the backup to the card, it just won't read the backup.

My only guess is there are some other files on the card that are interfering somehow.
[Droid Eris Android Development] cornbreadfarts:
try hooking the phone up to your pc while in recovery mode. open adb and su, then try restoring. it worked for me.
[Droid Eris Android Development] RogerPodacter:
I tried this too but it didn't work and I can't remember what the error said. I'm a noob though so I don't know if I used the right commands.
[Droid Eris Android Development] korben dallas:
heres my problem, maybe a corrupt partition maybe?? maybe i should reformat card??

Storing the ext2(Apps, Dalvik-cache) contents in the backup folder.

Warning: --ext2 specified but unable to mount the ext2 partition.

Error : Run 'nandroid-mobile.sh' via adb!

I:Set boot command ""

I:Set boot command ""

I:Set boot command ""

Move recovery.log to SD

any ideas?
[Droid Eris Android Development] vantagejuan:
did you store a file with the ext parition? I don't think that ext partitions are supported by this version of amon's recovery. Check that thread to see if they are supported.
[Droid Eris Android Development] korben dallas:
Since I rooted, I've been doing nand + ext backups. Until yesterday I never had a problem, I did just try a plain nand backup and had no problem. So idk
[Desire Android Development] conflipper:
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.ex

New Bravo ROM

RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe

Enjoy

PB99IMG_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.zip

This is an Official HTC ROM

RUU_Bravo_Vodafone_FR_1.21.163.2_Radio_32.37.00.32U_4.06.00.16_2_release_126985_signed.exe

RUU_Bravo_hTC_Asia_India_1.21.720.4_Radio_32.36.00.28U_4.06.00.02_2_release_127705_signed.exe
[Desire Android Development] ruffruff:
Superb ... can't wait to see if there are any new features found on this.
[Desire Android Development] itje:
thx conflipper
[Desire Android Development] ZiCoN:
Is this branded or official?

Can't see this in neither htc.com (dk) nor OTA... Danish user here...
[Desire Android Development] Heppieboeddah:
Looks like the official WWE. Going to flash this one.
[Desire Android Development] K-Hole:
Is anyone has flashed.. Which languages are included? I need German.
[Desire Android Development] ZiCoN:
Let us know as soon as youre done :) (I got the usb etc brick issue, so I'm curious :) )
[Desire Android Development] Heppieboeddah:
Backing up my sd right now. Will start flashing in about 15 minutes...
[Desire Android Development] mactron:
German is included ;) Just flashed it!
[Desire Android Development] fracost:
Italian?????
[Desire Android Development] rdy2go:
Excellent! What is the bootloader version? 0.75? 0.80? newer?
[Desire Android Development] geek78:
0.80 according rom.zip
[Desire Android Development] mactron:
0.80 just checked it.
[Desire Android Development] mrassol:
Flashed it since 20 minutes, don't see anything changed for now ... maybe a little bit faster ...
[Desire Android Development] saquib:
Will we lose root and if yes can it be re-applied ?
[Desire Android Development] fracost:
Italian is included!!!!!!!!!
[Desire Android Development] pina_:
damn, is it possible to downgrade again to the older bootloader-version?
[Desire Android Development] mactron:
No not atm as far as i know!
[Desire Android Development] thomasskals:
is danish included ??
[Desire Android Development] rdy2go:
0.80 can be rooted using Paul's guide
[Droid Eris Android Development] dmullins80:
So, I was looking to try a vanilla Rom. I downloaded the tainted vanilla Rom 1.4. Flashed it. Booted. Like always, the same. It worked great. I notice in the thread that he said he was trying out a2sd. Which I'm a big fan of. Don't know why really, I guess I just like seeing all them mb's. Lol. Anyways , downloaded the terminal from the market. Typed in Su. Got root access. Then typed a2sd check. Said it couldn't find it then said it did find it. Then, my apps disappeared. Went back to.recovery to.reboot. decided to go back we 2.0.1. When I loaded the back up (well) back up. It gave me everything the tainted Rom had.

2 question

How did that happen?

How do I put a2sd to a Rom that doesn't have it?

P.s. be fore I loaded my back up I did a wipe.
[HD Mini ROM Development] conflipper:
New Photon ROM

From May 8 2010

23103 SYS

Contains a few 2015 Packages.

Enjoy

RUU_Photon_HTC_DAN_1.32.403.1_Radio_Signed_32.2803.05.06_0.63.05.36_Ship.exe

RUU_Photon_HTC_WWE_EastEurope_1.32.479.2_Radio_Signed_32.2802.05.06_0.63.05.35_Ship.exe

RUU_Photon_HTC_Europe_1.32.401.2_Radio_Signed_32.2802.05.06_0.63.05.35_Ship.exe

RUU_Photon_HTC_NLD_1.32.404.2_Radio_Signed_32.2802.05.06_0.63.05.35_Ship.exe
[HD Mini ROM Development] Qtek8020User:
Thank you very much for the share :D
[HD Mini ROM Development] conflipper:
I have uploaded the WWE 1.32 has well.

RUU_Photon_HTC_WWE_EastEurope_1.32.479.2_Radio_Signed_32.2802.05.06_0.63.05.35_Ship.exe
[HD Mini ROM Development] Qtek8020User:
Only interrested in the Danish ROM, thank you :)
[HD Mini ROM Development] rigo007:
what are the major update about?
[HD Mini ROM Development] MALmen64:
No SVE version? :P
[HD Mini ROM Development] yuri609:
Hi, does include the EastEurope ROM czech language, please??

Thanks
[HD Mini ROM Development] Wackey:
Thanks!! Great stuf! :)
[HD Mini ROM Development] jmatejka:
It is with English menu and Czech xT9.
[HD Mini ROM Development] robbin7:
Photon is the same as HD Mini ?

Like Touch HD is the same as Blackstone :confused:
[HD Mini ROM Development] Raz0rX:
whats the difference in this ROM to the normal ROM ?

and include the ROM the language German ?

sry for my bad english :)
[HD Mini ROM Development] bakura88:
yeah, im also interested if the Europe ROM has German language included?!

apart from that, i am new to smartphones (i love my HD mini for about 2 weeks now:D). so my question is, do I just have to click the exe file of the ROM to install it? (didnt find any how-to so far for that...)
[HD Mini ROM Development] Chrys3:
Hi guys,

What's the difference between

RUU_Photon_HTC_WWE_EastEurope_1.32.479.2_Radio_Signed_32.2802.05.06_0.63.05.35_Ship.exe

and

RUU_Photon_HTC_Europe_1.32.401.2_Radio_Signed_32.2802.05.06_0.63.05.35_Ship.exe

?

Thanks in advance!
[HD Mini ROM Development] ninnitto:
Europe

RUU_Photon_HTC_Europe_1.32.401.2_Radio_Signed_32.2 802.05.06_0.63.05.35_Ship.exe

Is there the italian language in this rom?
[HD Mini ROM Development] logo123:
ROM the Lithuanian language???
[HD Mini ROM Development] rigo007:
nope. u can just set the location but all the rest is in english.
[HD Mini ROM Development] ninnitto:
is there any rom relased after the 1.07.408.1 (85429) ITA in italian language?
[HD Mini ROM Development] yuri609:
Thx very much friend
[Hero CDMA Android Development] justinisyoung:
would it be more like fastboot boot /sdcard/recovery-RA-.........img?
[Hero CDMA Android Development] imleon:
I tried /sdcard/recovery....img again, faild. Because in this command the image file should be on the PC not on the phone.
[Hero CDMA Android Development] elhead17:
1. Make sure you have the Android SDK installed. Read HERE for more info.

2. Download 4shared.com - online file sharing and storage - download flash_image.zip

3. Download 4shared.com - online file sharing and storage - download recovery-RA-heroc-v1.5.2.img

4. Unzip the first file, and place both in your Android SDK/tools folder.

5. Make sure USB debugging is ON

6. Connect your phone to the PC

7. Open the command window and navigate to the Android-sdk/tools folder on your computer.

8. At the prompt enter the following, one line at a time followed by enter

Code:

adb shell

su

mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

exit

exit

adb push flash_image /system/bin

adb push recovery-RA-heroc-v1.5.2.img /sdcard

adb shell

chmod 0755 /system/bin/flash_image

reboot

9. Your phone will reboot. When it is finished, back at your command window, once again enter

Code:

adb shell

su

cd /sdcard

flash_image recovery recovery-RA-heroc-v1.5.2.img

reboot recovery

10. With any luck, you'll have the recovery image back and can load custom 2.1 based ROMS again.

__________________
[Hero CDMA Android Development] imleon:
Sorry dude, there is NO su file in this released version of RUU.

So you won't run su after adb shell
[Hero CDMA Android Development] obelisk79:
just a question but can you successfully run the testkeys release RUU on your phone?
[Hero CDMA Android Development] pbp776:
I thought with new 2.1 update root access was removed and there was no way workaround to get root access. I might be wrong here.

You might want to try RUU back to 1.56 version and try to gain ROOT access and just flash ROM release by the dev's here which still give us ROOT access.

I'm not sure if it even possible to go back from 2.1 to 1.5 RUU. Maybe some with more knowleadge of RUU can chip in here.

In addition the RUU you flash is same one release by Devs here on their modify ROMs.
[Hero CDMA Android Development] kashb91:
i dont think it is possible to ruu back to 1.5. i think a dev said something about hboot being updated so it needs a new way for root.
[Hero CDMA Android Development] regaw_leinad:
You are correct sir. There's no way to downgrade hboot (without root), just like why you can't run the 1.29 RUU if you ran the 1.56, or yours came with 1.56 on it.
[Hero CDMA Android Development] SupahDave:
F.A.I.L.

10chars
[Hero CDMA Android Development] gunnyman:
aside from people who "accidentally" installed RUU, The push to quickly root this release is probably low priority, first of all this phone is probably end of life, so the chances of it coming out of the factory with 2.1 on it are slim.

2nd I imagine when the Evo gets released this forum will become a ghost town as far as new development is concerned :(
[Hero CDMA Android Development] regaw_leinad:
well, I'll be around here unless someone buys me an EVO :( & :)
[Hero CDMA Android Development] eme82:
It is actually possible to go back to 1.5 even if you used the RUU (well I should say the test RUU). I just did it yesterday so I could take my phone in for service. I'll post how I did it when I'm not mobile. Basically I created an update package to flash the old hboot then used a combination of the 2 main unroot threads. Ended up being able to use the sdcard method after flashing the misc.ing from the other method. I know probably doesn't make sense but I've got it all documented at home.
[Hero CDMA Android Development] Chaid:
I can't WAIT to read how you did this! I have been dying to get back to original HBoot since I ran the first test RUU back in April.
[Hero CDMA Android Development] chuckhriczko:
Well, if we are able to root this Sense 2.1 then theoretically the same root method may work on the Evo, thereby cutting down our wait for a rooted Evo. Just a thought.
[Hero CDMA Android Development] bcnice20:
Very very good point I'm not getting an evo till its rooted anyway
[Hero CDMA Android Development] Kcarpenter:
Possible, but I doubt it.

Chances are it's an entirely different kernel. My guess is the EVO gets a 2.6.30+ Kernel - It's hardware is completely different from ours. QUALCOM doesn't even make our chipset any more.
[Hero CDMA Android Development] zemerick:
I updated to 2.1 using damage sprintupdate2.zip. I want to use wifi-tether now. Where can I find the version I need for this particular build? I looked on wifi-tether website, but it says the 2.1 compatible version is for Nexus One. Is there even a version for Eclair for the Hero?

Would build wireless_tether_2_0_2-pre9.apk for the N1 work?
[Hero CDMA Android Development] gunnyman:
I'm still using pre6 seems to be the one for the Hero.
[Hero CDMA Android Development] richse:
Here's the link: http://code.google.com/p/android-wi...ireless_tether_1_60_htc.apk&can=2&q=HTC+Donut