yashsingh1/xdaforums huggingface dataset:
[Hero, G2 Touch Q&A, Help & Troubleshooting] btdag:
Did you flash using the exe? You shouldn't have any leftover data. Might be worth formatting the sd card as well.
[Hero, G2 Touch Q&A, Help & Troubleshooting] pulser_g2:
The solution is now confirmed to work, and stickied on the dev forum :)
[Hero, G2 Touch Q&A, Help & Troubleshooting] akuma24:
i downloaded version 1.5 from modaco forum, when rebooting the phone, the ra hero 1.5.2 recovery image is still showing, tried flashing again to no avail, any suggestions?

p.s. flashed via update.zip
[Hero, G2 Touch Q&A, Help & Troubleshooting] akuma24:
flashed the .exe and that seems to have done the trick, thanks for all your help, muchas gracias
[HD2 General] romskii:
Ever tought about trying to get iOS oder meego or some over os on the hd2? i know this is very very difficult or not possible.

But what do you think?
[HD2 General] Spl4tt:
xD... iOS rofl..

we can be happy that we get android now :3
[HD2 General] willgill:
Seems strange to want to shoehorn on a limited, locked-down iOS.
[Motorola Droid and Milestone Q&A, Help & Troublesh] kaiya215:
Can we get a recovery image from you..... god I miss my amonra recovery from my mt3g and droideris
[Windows Mobile Software Development] appelflap:
warning: this tool is for flashaholics. The ones who know all risks of flashing roms and like to live in the fast lane :)

Note for HD2-users: Although this version can be also used for the HD2, you may like this version more (the HD2 version doesn't require that you provide a "preflash" .nbh file - see further).

- Description:

FlashaholicRUU (FRUU) is a customized version of the HTC Rom Update utility that will simplify the rom update proces by:

1. performing a task29 before updating a rom

2. allowing the user to navigate through the dialog windows without having to check checkboxes (s)he has seen a gazillion times before.

3. allowing the user to use only the keyboard to go through the dialog boxes (enter -> next window, esc -> quit fruu)

- Prerequisite

Task 29 is performed by flashing a .nbh file before the (custom) rom file. Because the tool is meant to be general applicable for all devices you need to provide this "pre flashable" .nbh file yourself. In principle you can use any .nbh file for this. To speed up this first step though it is recommended to use a radio for your own device or better yet, a .nbh file containing only the splashscreen for your device. Rename this file (radio, splashscreen ) preflash.nbh and put it in a directory together with your custom rom file (may have any name as long as it has an .nbh extension) and the general_FlashaholicRUU.exe. Make sure there aren't any other files in the directory.

For the rest follow the instructions described in the section Usage

- Usage:

(Thanks to mskip for writing this brief but comprehensive manual)

- Video:

Video of the app on a computer of a fellow flashaholic: http://www.youtube.com/watch?v=hn3pGbW-vag. Thank you claub. Keep on flashin' :)

- Note to chefs:

You can pack FRUU with your Roms. You can even customize FRUU for your Rom series. For example you can use your own images, text, info etc. I have written some general instructions about customizing the RUU here. (Notice that in FRUU ModelID.fig is used for the first task29 step and RUU.fig is used for the second step. The dialogs for the first step are part of RUUResource.dll. Dialogs for the second step you will find in CustomizedRomResource.dll. Instead of the setup.bat and setup.vbs I mentioned in the aforementioned post I used the files run.bat and run.vbs. For exra information you can PM me)

- Donations:

Thank you!

Thanks to: doloop (for his non-mtty task 29 tool)

---------

Note: this tool should work for any (newer) htc device. Nevertheless make sure that your bootloader will support task 29 and that experiments with mtty task 29 has positive results for your device (look at the development section for your device forum)

Devices on which this tool is reported to work:

Happy flashing :)
[Windows Mobile Software Development] Petulinek:
Not Radio.nbh? Isnt it typo?
[Windows Mobile Software Development] appelflap:
Yes, it is a typo. Should be radio.nbh
[Windows Mobile Software Development] core7x:
sure need to test.

what diff between task 32, task 29 and task 28

im on blackstone, so that using only task 29
[Windows Mobile Software Development] appelflap:
task 28 hard resets the device. It is the default task executed by the shipped romupdateutiliy (RUU). Custom RUU's one find here on xda have replaced task 28 with a task 32 (security level check). That way you can use the custom ruu to flash a radio or a bootscreen. You don't want a hard reset after that :)

Task 29 formats the device.

It should work on the blackstone. From what I've read the bootloader supports those commands. As far as I know those commands are also supported by the bootloader of other newer HTC devices as well.

Make sure you have HSPL installed. (or how it is called for your platform)

-----

(BTW for anyone who like to experiment with the above util, you can extract the exe and examine run.bat ...

If the RUU's in this package don't work use the RUU for your device. Open it with a hexeditor. search for "task" and change the digits "28" behind it to "29" and save it as "Task29.exe". Do the same again, but now change "28" to "32" and save it as RomUpdateUtil.exe. )
[Windows Mobile Software Development] core7x:
clear, will do that:p
[Windows Mobile Software Development] appelflap:
You naughty boy... naughty naughty naughty :mad:
[Windows Mobile Software Development] core7x:
joke only, by the way. im flasholic rom person.:o
[Windows Mobile Software Development] appelflap:
I kinda hoped that you noticed the ironic undertone of my reply ;)
[Windows Mobile Software Development] gguruusa:
OK, this sounds like a bad idea taken even further.

Hard reset reloads nvram and ram from flash. Radio and bootscreen are in flash, so a hard reset will do nothing to them.

Unless HD2 is different from all other HTC devices (I seriously doubt it, but do not know), stock ruu should flash radio and bootscreens found in custom roms just fine. This makes sense, of course, because carriers don't release different ruu's just because radio update or bootsplash are included in .nbh.

As to erasing flash before flashing....what a waste of time. I can imagine almost no case where this would be beneficial, and it certainly is wasteful in 99.99% of cases. Why would you want to degrade memory 2x as fast (or more) on a routine basis? Flashing RARELY (like never) fails to overwrite, and when it does, it won't help you to have 0's where it fails.
[Windows Mobile Software Development] appelflap:
Not when you just want to update your radio without updating or resetting the os

If i don't do a format before flashing a new rom - time has shown me this again and again - i get some serious battery drain problems. Of couse I like to pass this step... but..

and with respect to your other advice, this is a tool for flashaholics you know. I don't think flashaholics worry very much about the memory of a device they use for 1-2 years max. :-)
[Windows Mobile Software Development] ephestione:
I totally quote appelflap on this one.

I've never ever had battery drain problems with my flashes, the very first time I had those is when I attempted at flashing just a new radio radio keepin the rom and the data. Before thatm, flashing a new radio always was done when flashing a whole new rom, and after a task29 anyway.

After that "radio only" flash, hell ensued, as no matter the radios I changed thinking it was the radio version's fault, I was getting up to 16% drain overnight, and anyway not lower than 12%, against a normal 4-5%, with a standby drain of 20mA and more, against a normal of 4-7mA.

Next thing I did, task 29 + radio + rom and now I'm getting a whopping 3% drain overnight with my current rom combo, never went so low.
[Windows Mobile Software Development] resqman:
Tested this morning on a Raphael (ATT Fuze). Worked well. Task 29, radio flashed and ROM flashed. No problems at all.

Also tested with a Rhodium(ATT Tilt2). Same results.

Makes ROM flashing much faster. Now if there was just someway of not having to press the down volume button at the end of task 29 it would be perfect.

Good work Appelflap!!!
[Windows Mobile Software Development] appelflap:
Thanks for testing! I think you helped a whole lot of flashaholics :D

BTW: If you have a original nbh file of the first bootscreen of your device(-s) you can use that instead of a radio ... For now, (till I uploaded a new version) just rename the bootscreen to radio.nbh and put it in the folder from where FlashaholicsRUU is run. Flashing a bootscreen in the first task 29 step is so much faster.

EDIT: about putting the device back in bootloader after the first task 29 step: if I only knew the bootloader command for it I could make it work without any problems. So if anybody has any idea, please let me know, I can hexedit the RUU to execute this command right after task 29 is performed.
[Windows Mobile Software Development] resqman:
Might it be possible to have it check for the existence of a radio.nbh file and if it doesn't exist skip that? I know it is handled by a batch file so there must be a way around it.

I flash a lot of ROMs but I rarely flash radio or bootscreen
[Windows Mobile Software Development] appelflap:
The bootscreen or radio is needed in step 1. Task 29 is performed after flashing one of these. I will look for another solution when my HD2 is repaired.
[Windows Mobile Software Development] resqman:
I have performed task29 on both Fuze and TP2 without having to flash a radio.

From the task29 section of the Rhodium forum:

Obviously I am missing something here:confused:
[Windows Mobile Software Development] appelflap:
Thanks for your feedback! This was exactly the feedback that I was looking for.

The task29 tool from the rhodium forum flashes a ruu_signed.nbh that is specifically brewed for the rhodium. Indeed flashing this file doesn't touch anything.

Problem is I can't use such device specific files for a universal flashing tool. That's why I use radio nbh. So that I'm sure that the tool runs task 29 with a nbh file that is accepted by the device that is flashed.

The ruu_signed.nbh that task29 uses for the rhodium is 8.5 mb large. This will take more time to flash than a bootscreen (which is 0.7mb) but less than a radio (which is > 10 mb). May I suggest to use this tool with a bootscreen nbh it is soooo much faster.

Anyway when I get my device back I will look if I can brew a small nbh file that doesn't change the bootscreen or radio. I will target it to different devices and wrap it up for each specific device.

Again, thanks for your input.

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

Edit: I've attached the nbh file that is used by the rhodium task29 tool. Use this one instead of a radio. It doesn't alter you radio nor your bootscreen. Although the file is named radio.nbh it isn't a radio (the current test tool need that filename). You can try this for your rhodium.
[Windows Mobile Software Development] resqman:
I understand now. It's not really a big deal for me to flash a radio. It would be a lot of work for you to have to create a signed ruu for every device.

Thanks
[Windows Mobile Software Development] hav0c:
Thanks!!!!
[Windows Mobile Software Development] resqman:
Just flashed my Rhodium again (NRGZ28 is prolific). Once again flawless and fast. 6 minutes from start to final boot.
[Windows Mobile Software Development] Mhyst:
Way awesome!

Worked perfectly on my Fuze. Just had to be sure to hold the volume down key and press reset to start the bootloader to get the rom to flash (I was staring at the AT&T splash screen like a retard until I decided to try this, lol). Perhaps adding this step to the instructions would help the noobies (or other retards like me)?
[Windows Mobile Software Development] malatest:
Works on Diamond. Fantastic!

Very Thanks
[Windows Mobile Software Development] appelflap:
Thanks for reporting back. I think the tool is ready to go out of beta. The results give me enough confindence that it will run on practical any (newer) HTC device.

Thanks again for testing.
[Windows Mobile Software Development] appelflap:
There will be a more elaborate guide for using the tool when I "release" it. Thanks for testing.
[Windows Mobile Software Development] appelflap:
Update: released a first version of FRUU. See first post for details.
[Windows Mobile Software Development] Ohamn:
Flashaholic doesn't work for Topaz

Hi there appelflap!

I just tried your interesting custom RUU!

I followed your instructions but got an error message when reaching 11% when flashing the radio NBH file. See attached screenshot.

And yes, I used the "general_FlashaholicRUU, not the HD2 version!!! ;)

Any suggestions from you appelflap!? :confused:

// Ohamn
[Windows Mobile Software Development] resqman:
Did you rename the radio.nbh preflash.nbh? Just wondering
[Windows Mobile Software Development] NLS:
This happened to me because of a not-so-good USB extension cable. I switched cables and it worked.
[Windows Mobile Software Development] Ohamn:
Hi there Resqman!

I did rename the radio nbh to preflash.

The only files present in the folder are the preflash and the Topaimg file together with the FRUU.

I will try to run the FRUU as administrator later today and see if that helps.

//Ohamn
[Windows Mobile Software Development] Ohamn:
Still doesn't work for Topaz??

Hi again appelflap!

This afternoon I tried to run the FRUU as administrator and still got the same error.

I even tried to change USB port from front to rear on my computer to see if that helped, but it didn't work either.

The preflash jumps to eleven percent at once and then it stops and after two, three seconds the phone disconnects from the computer and the phone screen goes black. The phone then reboots and the error message previously posted appears on the computer screen.

It would be sweet to get this to work for my Topaz as well!

Any ideas!?

// Ohamn
[Windows Mobile Software Development] appelflap:
Just speculation, but it seems that you don't use a radio.nbh that is compiled for your device. Could that be possible? Do you have HSPL installed?

The most pragmatic way is to try a radio.nbh rom and flash it with a custom RUU. If that works it should work also with this utility.
[Windows Mobile Software Development] Ohamn:
Aha......

Hi appelflap!

The radio nbh I used was the one you supplied in post 18.

And, of course it's for the Rhodium (if I had bothered to read!!:rolleyes:).

What a noob thing to do!

I will try a Topaz radio and get back to you!

// Ohamn
[Windows Mobile Software Development] Ohamn:
Yep, that did it....

..... of course!!! :o

When I used a Topaz radio it went like a charm!

I'm now running NTGZ28 ROM from the 30 of July and got myself a task29 done in the process!!! :D

Thanks for sending me in the right direction appelflap.

Even though I made a fool of myself!! :o

I guess that it's safe to say that your app works for the Topaz as well then!? ;)

// Ohamn
[Windows Mobile Software Development] appelflap:
Thanks for testing. I surely will add the Topaz to the list of devices FRUU works on.

BTW If you can find an original first splash bootscreen nbh you can speed up the first step. One day I will collect some bootscreen for some devices in the first post.

In the meantime, if someone finds the original splash bootscreen for his/her device, please post it in this thread. Thanks.

(some threads about customizing the first bootscreen:

* for the Diamond:

* for the Touch Pro 2 or Rhodium: http://xdaforums.com/showthread.php?t=576703 )
[Windows Mobile Software Development] goldlocke:
thank you appelflap! :D
[Windows Mobile Software Development] Nirak:
I once had a Diamond with no button activity at all, i somehow managed to fire it up again and wanted to perform the 'good ol' mtty' to be sure there where no software flaws that caused this.

I found out that in mtty utility, if i start with command 'set 14 1' (instead of 14 0) the device ends up in bootloader (after performing task 29 and task 8) instead of making a regular restart. That way i could also flash a stockROM.

I'm not a pro concerning this kinda stuff, but it may help.

(Off course it turned out a hardware issue, both connectors were ripped off the Diamonds flex board)
[Windows Mobile Software Development] Pumpiron579:
Just used this to flash a rom on my Diamond, Worked Great. Nice work. :cool:
[Desire General] jannen:
Anyone has this? Desire is mostly blizzfast, but sometimes when I open a contact widget it takes 4-5 secs to open up, same goes with the agenda. Not the end of the world but frustrating sometimes.
[Desire General] tifosi256:
Happens to me too. Contact opening is especially slow.

I'm hoping that when we get Froyo, the JIT will make the delay go away. Until then, I think we're just going to have to be patient.
[Desire General] jannen:
Bit irritating really, but all in all Desire is fast. Had another play with Iphone 4 where opening all apps or returning back to home screen had annoying delay. A second or so aybe but in the long run irritates. Maybe was something with that particular handset.

Just wonder where that delay on Desire comes from, i dont have masive amount of contacts or agenda entries...!
[JASJAR, XDA Exec, MDA Pro General] davecoolz:
I play worms games several hours and then my universal hangs everytime it enters standby mode. I have flashed roms and doesn't work. But it wont hang if I connect my charger to my uni. So it lost its mobility now.

Do you know whats the problem? Could you help me?

Thanks..
[JASJAR, XDA Exec, MDA Pro General] orb3000:
Try with a new battery
[Motorola Milestone Android Development] Coburn64:
G'day.

So, I got my motorola milestone and I followed the Milestone Root thread, which I followed and downloaded the required SBF files to flash the exploit recovery (so I can actually get root). However, when flashing, it will say "Erasing Flash Memory: 99%" and then it'll go "Uploading new data. 0%" and just hang on that. I pulled out the USB connection after about 15 minutes of it being stuck on it, and I didn't get a brick. Android still boots, but I'll possibly be without a recovery image for a little while!

Android is still booting. HOWEVER, I don't have any recovery image as it was successfully nuked by RSD Lite. The milestone will not flash the Exploit recovery, that's all!

So, I need some help.

Bootloader Version: 90.78

Firmware Version: 2.1-update1

Firmware Config Version: GAS_EMEA_USASHLS00RTINT_P016

Baseband Version: 3GSMEPU91A_U_91.07_56I

Baseband Config Version: UCASHLSMR2EMEAB1B806D.0R

Build Number: SHOLS_U2_02.36.0
[Motorola Milestone Android Development] een625:
Hi,

You know what, I got the exact same phone as yours and I spent hours trying to work it out, and I got mine rooted finally.

First of all, you can't downgrade your bootloader, but what you can do is to make your bootloader vulnerable.

You need to use a special vulnerable recovery that is made especially for 90.78

Google vulnerable_recovery_only_RAMDLD90_78 and use that file instead to downgrade the recovery.

Afterwards it's smooth sailing, but remember, afterwards, to enter recovery mode as our bootloader is 90.78, everytime the guide mentions up/camera button, just replace with hold x then power up until you get exclamation mark, then hold volume up, and press camera button.

Good luck
[Motorola Milestone Android Development] Coburn64:
Thanks een625, I just fixed the problem. Thanks bro!
[Motorola Milestone Android Development] kabaldan:
You can always find the latest vulnerable recovery sbf here:

android.doshaska.net/rootable
[Motorola Milestone Android Development] een625:
No worries mate... Glad I can help
[Motorola Milestone Android Development] daxie:
I have the same problem as the OP and did the procedure you detailed using the vulnerable_recovery_only_RAMDLD90_78 sbf on RSD, still no dice. I even tried the open recovery method which didn't work too and ended with the "E: EOCD Marker occurs after start of EOCD E: Signature verification failed" error.

After searching the forums all over the web, I see that I may have to apply a stock motorola sbf from the company site before the vulnerable recovery SBF, but reluctant to do it as I see that I will wipe everything and start afresh. I am not sure of which official SBF (service/non-service) to apply and the required version to allow rooting.

Need help!

Bootloader Version: 90.78

Firmware Version: 2.1-update1

Firmware Config Version: GAS_EMEA_USASHLS00RTINT_P016

Baseband Version: 3GSMEPU91A_U_91.07_56I

Baseband Config Version: UCASHLSMR2EMEAB1B806D.0R

Build Number: SHOLS_U2_02.36.0
[Motorola Milestone Android Development] een625:
Hi,

Can you tell me the steps you take one by one...

These are the steps I take:

h t t p://xdaforums.com/showthread.php?t=696359

openrecovery is run AFTER you flash a vulnerable recovery on the device...

Remember on 90.78 the vulnerability is patched, which is why you need to make the 90.78 bootloader vulnerable again.

You can't downgrade it, the only thing to do is flash with the vulnerable version

Only after you flash it, you can run open recovery...
[Motorola Milestone Android Development] kabaldan:
daxie:

Have you read the second point of "Possible issues you may encounter"?

here: http://android.doshaska.net/rootable
[Motorola Milestone Android Development] daxie:
thanks guys, i finally did it, kabaldan's solution finally did it!

but have one final doubt, after i successfully rooted it, when i tried getting to Open Recovery (had the Open Recovery update.zip on the sd card root folder), I couldn't and I got the same "E:EOCD marker occurs after start of EOCD E:signature verification failed" error. What does this mean and does this mean that I am not completely rooted?
[Motorola Milestone Android Development] kabaldan:
See the updated information about the recovery checking caused by OTA being applied in the past and how to avoid it:

http://android.doshaska.net/rootable
[Motorola Milestone Android Development] k_myk:
I just want to say: Nadlabak, you are a good guy:) I really appreciate your work:)

Sorry for OT.

Cheers!
[General Topics] anonymous-x:
I'm thinking I'll get the Vibrant in a couple hours & I plan to use the sim between the HD2 & the Vibrant. Then I'll update the HD2 w/Android & learn the HD2 in its own ways & still use the Vibrant as a personal.

The sad part the Vibrant is not UMA capable, so no wi-fi calls from this one either. :(

The 8520 the 9700 & the E73 are the only phones TMO allows to have UMA allowances. This does not make me happy.

If Sprnt & TMO join new possibilities will arise but you know how that is, its something else thats off in the future so if we want, we have to choose from what is available today.

a/b/g/n has nothing to do with the concept to allow wi-fi calling, this is another lesson I have learned the hard way with my individual learning to try & understand this developing technology.

I am a runt here, in this fantastic site of genius & ever thankful to all those that share & teach. I will be slightly quite, hoping that one day the phone I need will be made : they can, they could but they won't.

Thank you XDA, you help us withstand this corporate tease.
[Touch Diamond2, Pure Android Development] coolbluesea:
Thank ReWind402 first, bate2 v2 work well on my phone, in fact, this is the only one XDAndroid able to work well in my phone.

I have two tips for all of the V2 Players:

1, XDAndroid default is English, if you want to become Chinese or other languages but not in the list, you can install a software called "Morelocale", then you can choose any language supported by Android.

2, try the zoom in and zoom out "BAR" in the screen below, you will find interesting things.

If you find some tips, please write in below to share to everyone.;)