Database Users

After Flashing a Rom, cannot turn on the device

After flashing this rom : [Rom][WM6.5][27 Aug'09]New Elfin ROM With Latest build 23034 Xip/Sys
The device stay in the 'smart mobility' screen,
I can't even boot it up first time
I can't turn it on so how can flash back other rom?
Can someone tell me what can I do?
Please Help me. thank you

You can use this Unbricker ROM ---> http://forum.xda-developers.com/showthread.php?p=2913636#post2913636. It's the easyest way, without using other WM devices. It worked for me.
You can also use the Elf/Elfin Unbricker (Gold Card) ----> http://forum.xda-developers.com/showthread.php?t=437996. Hadn't tried this one though.
Hope that I helped.

------------------------------------------------------------------------------------------------
A user of this forum, 911sniper, provided us with an HTC test-only ROM:
http://forum.xda-developers.com/show...&postcount=735
Alternate download link:
http://www.neufgiga.com/n/50-17/shar...492127a54134b/
Alternate download link:
http://www.4shared.com/file/82315205/ea440324/RUU.html
IMPORTANT: Read the steps below before flashing!!!!
------------------------------------------------------------------------------------------------
This is a ROM that can potentially overwrite and/or unbrick a device with an original (non-patched) SPL. It has a wildcard for Model ID (ELF0*****) and CID (11111111).
I don't have a bricked Elf but I tested it with an original CID-locked SPL and it overwrote it and flashed a new generic HTC ROM with the following:
IPL 2.11.1002
SPL 2.11.1000 MFG
ROM version: 2.11.0. WWE
ROM date: 08/14/07
Radio: 02.98.90
CE OS 5.2.1620 (Build 18125.0.4.2)
Here are the steps to make it work:
Quote:
Download this ROM from the link above
Two ways to flash:
Rename the file to ELF0IMG.nbh if you want to flash from SD card (you must format the card to FAT32 first)
Put the ROM in a RUU folder that contains the RomUpdateUtility.exe. You must remove any other .NBH files in that folder first.
Start your bricked Elf in bootloader mode (hold down camera button and reset). If you are using the SD card, it should flash right away.
NOTE: If the device flashed successfully but is now stuck at the new boot screen, you are still ok. Now you can flash ANY shipped ROM at the bootloader (if you have an Elfin, flash only an Elfin shipped ROM) and your device will be running again. If you can't flash a shipped ROM after successfully flashing the Unbricker ROM, then make a Gold Card and follow the steps in that thread.
NOTE: If the Unbricker ROM doesn't work then make a Gold Card and use it again on that card.
NOTE:
One thing I noticed is that you cannot use the white screen method (elf-uspl.exe) after you flash this ROM. If you try that, then the message "Not in use" pops up under the penguin. However, you can flash ANY shipped ROM from bootloader after this unbricker ROM has been flashed. From there, you can do white screen method and then flash the Hard-SPL/USPL/cooked ROM.

[Q] In need of some help with install

I've flashed a bunch of WinMo custom ROM's, but this is my first time attempting to install a NAND build. I received my phone back from warranty repairs last week so I'm currently running a stock 3.14 ROM. I've got a stock 1.66 ROM that I'm planning on installing from the SD card to get a SPL that is compatible with HSPL. I want to run a Task29 before I install a NAND Android ROM (MJD's latest build, I'm thinking), but I'm not entirely sure how I should go about this.
This is as far as I've gotten as far as the install procedure goes:
1. Flash the 1.66 ROM through SD card
2. Install HSPL
3. ???
As I said, I want to Task 29 the phone before I install 'droid to make sure everything runs smootly. Can anyone list out the rest of the steps I need to do to and what's the best app to Task29 the phone for me?

Flash a radio 2.08 or above. e.g 2.15.50.14
Only flash 2.xx.50.xx radios btw, if you have a EU hd2. For T-Mo HD2, i'm not sure on the requirements sorry.
Either way, search it up, snoop around the forum, look at stickies, you'll prolly find a guide or something that tells you the radio requirement for T-MO devices.
Then flash MAGLDR, it's done by flashing a regular rom through usb.
Then download your NAND build of choice, and install. Remember to install as an administrator.

Plz read this great guide http://forum.xda-developers.com/showthread.php?t=893948

I don't need to have a WinMo ROM present when I install MAGLDR on the phone, right? I'll be able to install it from the boot loader as long as I have a compatible radio on the phone, correct?
So right now the install goes like this, someone correct me if I'm wrong
1. Flash the 1.66 ROM through SD card
2. Install HSPL
3. Task 29/Install .50 radio
4. Install MAGLDR via boot loader
5. Install a NAND Android ROM via MAGLDR
6. Profit!

novaci said:
I don't need to have a WinMo ROM present when I install MAGLDR on the phone, right? I'll be able to install it from the boot loader as long as I have a compatible radio on the phone, correct?
So right now the install goes like this, someone correct me if I'm wrong
1. Flash the 1.66 ROM through SD card
2. Install HSPL
3. Task 29/Install .50 radio
4. Install MAGLDR via boot loader
5. Install a NAND Android ROM via MAGLDR
6. Profit!
Click to expand...
Click to collapse
Yes, that's correct.
There's a link above, but I found this guide to be very detailed...
http://forum.xda-developers.com/showthread.php?p=11097380
If you have any problems at all, that will help you.
Good luck mate

[Q] Please help!! I may have messed up my MT3G!!

Okay, so I installed a radio version 2.22.27.08 via clockwork recovery on my 32A device when it should be only used on 32B!!!! I wanted to use yoshi's rom and I followed the directions but must have clicked on the wrong one!
I downloaded the old radio (3.22....) and tried to flash it via fastboot (it only comes in a .img file) but it keeps failing on the signature!
Is there anything I can do to downgrade to that radio?
I made a nandroid backup and my phone still works fine with the wrong radio, but I am not able to install another rom that I want!

Give us complete fastboot info

[Q] HTC Magic radio and SPL change

Hi guys. I need some help with my HTC Magic.
I have Magic 32A, (now) with radio 3.22.
I have rooted phone, and installed CyanogenMod, but I am not satisfied. I want to return to stock rom with HTC Sense.
The thing is, I had radio 6.35 but had to flash to 3.22 because of cyanogen mod.
Can I flash it back to 6.35 and put some newer stock rom for HTC Magic? Can flashing back to 6.35 cause some troubles?
Thanks for your time and answers

if the radio is the only thing you needed to change for CM then u can flash it back to 6.35. wipe your CM ofc cause according to your story it's not compatible with radio 6.35.
first determine the type of ROM you want, and then find out what version SPL and radio it requires.
superwipe your CM ROM and then flash your SPL and/or radio to meet your new ROM's requirements. Then flash your new ROM.

If you have hboot 1.33.2010 ENG S-OFF now, you can simply change to [new radio] combo and back too.
Use Fastboot Commander to do that. It has option to change by batch (hboot, radio, custom recovery), so you can do it safe and quickly.
Fastboot Commander: http://forum.xda-developers.com/showthread.php?t=824435
Note: only for Magic 32A (users with MT3G v1.2 with 3.5" audiojack - DON'T flash 6.35 combo)

thank me too

15MB extra RAM for ht-03a using T-Mobile bootloader and radio

Posted by SBS
I flashed the new SPL and radio that also came with the T-Mobile Froyo OTA giving myself an extra 15 MB of RAM. This post attempts to compile the background and links to the knowledge needed to do this safely. Because this is much more complicated than rooting with universal androot, and you can very easily brick your phone, this should not be done if you don't fully understand the process and aren't comfortable using the command line. While I believe someone may have created flashable signed zips for doing this, the recommended way is to use fastboot.
The Benefits
ROM Memory Swap Total (KB) Total (MB)
Stock
97708
0
97708
95
Rooted old SPL/radio
97708
31316
129024
126
Rooted new SPL/radio
112844
31316
144160
141
Without swap, that is an additional 14.8 MB of real memory.
First, a few things you need to know before proceeding:
Perfect Secondary Program Loader
The ht-03a shipped with a "perfect" SPL that does not allow remote fastboot. Therefore, an interim engineering SPL will have to be flashed in order to use fastboot to flash the new SPL (1.33.0013) and radio. The new SPL is also perfect, but a version was modified for the Dream/G1 (1.33.0013d) that allows a few fastboot commands, such as fasboot erase system -w for a complete wipe. Fortunately, 1.33.0013d has been confirmed to also work on the ht-03a, a Google-branded 32B magic.
Even with the modified "d" version of the new SPL, you cannot remote boot a recovery image, flash new splash screens, flash a new recovery image (if for example yours became corrupted). You will have to flash an engineering SPL, do what you must, then reflash 1.33.0013d. Unlike flashing ROMs, flashing SPLs is not 100% risk free.
Amon_RA Recovery Recommended
I'm sure this will probably get some feathers ruffled, but I am leery of clockwork recovery and ROM Manager. As outlined here, this is not the developer's fault but a low memory issue. Perhaps this new SPL and radio will fix that, but the fact remains that there have been a number of instances Dream and Magic users getting stuck with no working recovery. With an Engineering SPL, this is no problem because fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img fixes this, but with a perfect SPL, it will be much more difficult, as in making a goldcard difficult.
Another fact is that I have yet to hear of this ever happening with Amon_RA's recovery, and ezterry at XDA is suggesting to use Amon_RA. However, using Amon_RA means you can't use ROM Manager.
(NOTE: ht-03a users need "G" versions of Amon_RA)
Patched Kernel Required
If you are like me, you never cared about kernels. Yeah, you might have been interested in testing out some of the overclocked kernels but you were perfectly happy to use whatever the developers included with the ROM, which will likely be the most stable way to go but maybe not the fastest. Stability versus bleeding edge. For the time being, those days will be over. All of the cooked ROMs available right now will need a patched kernel that may or may not be included with the ROM.
I have no idea what is the "best" kernel. It will depend on what makes it the best for you.
Required Reading
Start with ezterry's XDA write up with links to the radio and SPL. If this doesn't make sense, stop and read more.
If you don't already have one, read the instructions on flashing an engineering SPL.
The SPL in the above link comes from this list of engineering SPLs.
Finally, you'll want to understand how to flash Amon_RA's recovery because it is less prone to problems than clockwork.
If you plan to use CM 6.1, ezterry's CM Forum post contains a port with the new radio.
Required Environment
Engineering SPL (I am using 1.33.2005. Many others are using 1.33.2009. IIRC, there might be issues with 1.33.2010 and CM, so 2009 is probably best.)
fastboot utility installed on your PC
Android SDK on your PC to allow you to use ADB (Perhaps this is technically not required but at this point of getting into your phone you ought to have it installed.)
What I did
The T-Mobile US Froyo OTA with a cyanogen kernel I've been running lately is by far my favorite ROM due to speed and stability. I've mentioned missing some CyanogenMod features, but when it comes to my phone, stability trumps the bleeding edge. So I 1) did a nandroid backup of my current ROM, 2) updated the SPL and radio, 3) restored the backup, 4) flashed the patched kernel, and 5) picked up where I left off with no loss of data on my phone. The actual work involved for me was about 10 minutes because I already had an engineering SPL and Amon_RA. I spent infinitely more time writing about this than I did actually experiencing it.
So far, all seems fine, but I'll need a bit of time to test. Wifi and GPS are working, and the phone does seem snappier. I haven't had a chance to see how battery life is. There are two choices of radio, 2.22.27.08 or 2.22.28.25. The former came with the OTA. The later is a newer radio. Depends on who you ask and where they live, which is better/faster/easier on the battery. For now I am using 2.22.27.08.
Rebooted to recovery and nandroid backup my current ROM.
Followed ezterry's instructions on XDA
Downloaded all necessary files and checked the MD5 sums against what was published.
dream_2708kit.zip which includes 2.22.27.08 radio and 1.33.0013d SPL
Kernel installer for CM Nightly 271
Mounted my SD card, copied the kernel installer to the root of my SD Card, and rechecked the md5 sum.
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
fastboot erase system -w
fastboot erase boot
Reboot to recovery and restore ROM.
Flash kernel.
Reboot normally.
Pray (actually I used ddms watch all the boot messages)
Play.
New v Old SPL/Radio
HBOOT Radio Context Type Security SPL Maker Fastboot USB
1.33.0006 2.22.19.26I
Stock
Shipping
On
Google
No
1.33.2005 2.22.19.26I
My choice
Engineering
Off
HTC
Yes
1.33.0013d 2.22.27.08
Froyo OTA
Shipping
On
Google
No*
*fastboot erase allowed
Here are the hboot/radio combinations I've had on my ht-03a, beginning with the Docomo stock configuration. After that I used the same radio with an engineering SPL. This was prior to universal androot with no one-click option for 1.6 Donut; An engineering SPL was required to root. Finally, I'm back to a mostly perfect SPL but with an additional 15 MB of real memory.
What most of you will need to do
NOT follow these steps but use them as A Docomo ht-03a SPECIFIC REFERENCE for ezterry's instructions.
If you are unrooted, root your phone and flash a custom recovery. clockwork is fine to start with.
Download and flash an engineering SPL from recovery (e.g., 1.33.2009, though I have been using 1.33.2005). VERIFY MD5 SUM after download and after copying to SD card.
Reboot to fastboot (power + back).
Download Amon_RA recovery (NOTE: that the code in exterry's guide is specific to a dream ht-03a users need a sapphire recovery tagged "G". "cyan" refers to the color scheme, not cyanogen.) VERIFY MD5 SUM!
Using the terminal, cd to the directory with the img file and fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img which assumes you have added fastboot to your path (Instructions for mac/linux here. Windows users on their own.)
Continue as I did.
Restore your previous ROM and flash the "2708" ported kernel of you choice.
Or follow these directions for CM 6.1 after rebooting to recovery.