Database Develop

Deleted My HTC Wizard Radio Rom

I was tryin to update the radio rom on my MDA and i i was usin the RUU and i guess i did somethin wrong cause now thers a X where the active sync is and a exclamation point where my reception bar is, also wen i go to about device i dont see the radio rom where the others ones are listed. So i downloaded the universal radio gsm exe but it doesnt recogize my device even thought it pluged in my microsoft active sync does recognize it either. and now its runs extremly slow, could someone give me some insite to wat i have done wrong and how i can fix it,
Thanks klawdlan
PS i am runin the orginal firm that came wit my mda US-Tmobile

The radio for the Universal will not work in the Wizard.

so what should i do to fix my prob

Download a Radio Rom (as an example you could try the Cingular 2.25 Radio Rom) for the Wizard on the XDA FTP

my pc is nto recognize it after i deleted the radio firm, even wen i plug in the wall charger thers no indication thats its chargin.

Can you get in bootloader mode by pressing the camera button (and hold it) and then doing a soft-reset?
If you get the tri-color screen, THEN try to update the Radio Rom, if that doesn't work, then you are in deep **** I guess!

yea i can get to that screen

Then go into that screen and flash the Radio Rom!
The Radio Rom is located here: ftp://xda:[email protected]/Wizard/Radio_Roms/wizard_radio version-2.25.zip
Good luck.

how will i get the rom to the pda if it wont even recognize it in microsoft synce, i cant even browse the device wen i go to my computer?

Listen carefully!!
- Connect your device via the cable to your PC.
- Get your device in the bootloader (tricolor-screen) mode.
- Unzip the zip file with the Radio Rom
- Go into to folder you unzipped it in
- Doubleclick the .exe file and follow instructions on your screen!
Good luck!
p.s. You flash Roms from your PC to your device, you dont flash Roms "on the device itself".
p.s.2 Maybe it will be smart to do a hard-reset afterwards (because your device is very very slow, look at my post in this topic on how to do a hard-reset http://forum.xda-developers.com/viewtopic.php?t=56145&highlight= ).

i did everythin u said word for word wen ruu was runin this came up
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and i continued and in about device it doesnt show a radio rom

Just continue!!
Just press Next or Continue until it starts flashing or gives an error!

i did and i still get no radio rom in the end

Dont pay attention whats on your screen.
You can end up with 2 things:
1) You get an error and the update failed.
2) The flashing begins and you will get a message when it's done!
Molski

i get the message that its done and that i flashed, but in im in wm5 and i go to systems about device i still dont see a radio rom

Then grab a Full Rom from here: ftp://xda:[email protected]/Wizard/Roms
And flash the Full Rom the same way I decribed for flashing only your Radio Rom.
Good luck pal !
p.s. When you turn on your device, don't you see a Radio Rom (GSM version number in your top-left corner?

alright ima try it now, thanks

PRAISE BE UNTO molski FOR HE HAS HELPED ME FIX MY FONE, thanks man i got a hang of this update thing now, learned mucho mucho i would make a new thread in ur honor if it were proper forum edicate

It's never wrong to thank someone (especially me in a new thread haha)
I'm glad your phone is working again that and you learned how to do things like flashing your Wizard!
And now you can play around with it....you know what to do if something goes wrong
Regards,
Molski.

I bricked my phone.

I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?

Babyche43 said:
I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Click to expand...
Click to collapse
lol......its gone....call tmobile and tell them your phone said it had an update and you said to update it and that you left it there for a while and when you came back it wouldn't get past that.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just another brick in the wall.

How did you mix up the ordering of the files? Sounds like you know which should come first...

Oh well. Thanks for the advice. I just call T-mobile and they are going to send me a new phone and give me a loaner phone until the new one arrives. Great.

I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.

Babyche43 said:
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Click to expand...
Click to collapse
You don't need to reroot the phone to go to a hero ROM from another modded rom. You only need to flash the newest radio and then the special SPL (in that order)

Babyche43 said:
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Click to expand...
Click to collapse
Yessir the ol gut feeling.

that's the worst when you ****ed up and there is nothing that you can do to stop it. well unless you are like me and don't care and just do it anyway

Diceman4 said:
You don't need to reroot the phone to go to a hero ROM from another modded rom. You only need to flash the newest radio and then the special SPL (in that order)
Click to expand...
Click to collapse
I know but something happen when I went from a Cyanogen mod too a Drizzy hero rom to were it would work and kept boot looping (if that is a word) so since I don't know that much about flashing roms and all that I figured I would just start over and just install the hero rom from the beginning and that's were I installed the wrong update.

Babyche43 said:
I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Click to expand...
Click to collapse
How would you know if you bricked your G1?will it be stuck in a certain logo it'll be stuck at?

will it be stuck in a certain logo it'll be stuck at?
hahahahahahaha yes. The very first one.

you will know your phone is bricked by the fact that it no longer wants to cuddle with you when your press power, or when it no longer gets in the mood when you press home and power, and you know all hope is lost and you will never get to the g-spot on your g1 when camera and power no longer does anything.
yes all the answers are in there lol

Oh Boy What Did I Do(Went from 1.5 to Android Dev 1 on 1.6)

Hey, so I tried rooting my phone and I followed the steps very specifically from these topics
First I did this and it worked properly
http://forum.xda-developers.com/showthread.php?t=558301
I was at 1.33.2005 at this point and 1.5
Then I followed the instructions in the topic "ROgers, heres your real root", specifically from the very last post on page 60
http://forum.xda-developers.com/showthread.php?t=544654&page=60
It booted to Cynogen v1.4 + JF
However instead of installing "signed-dream_devphone_userdebug-ota-14721.zip" first, I installed the Cynogen rom first)(4.2.11.1), then when I rebooted, it got stuck on the Rogers, so I booted up in Recovery mode again, this time with the "signed-dream_devphone_userdebug-ota-14721.zip" on the sd, and I installed that, then I installed the 4.2.11.1 again
I restarted, and it got stuck on the Rogers screen
So I booted up in recovery mode again and I did an entire clearing and erasing of all data (I think equivalent to a format)
I booted up my HTC Rogers Dream again, and now Im on 1.6....And my model is Android Dev Phone 1...and my kernel was 3.something before and its now 2.6.29
Ugh I just wanted to root the thing and have Cynogen running
Does anyone know the appropriate steps to fix my problem?

Cyanogenmod 4.2.11.1 IS firmware 1.6. And that is the correct kernel version too.

So...in essence I DID....root it? hahaha

Your "about phone" screen should look somewhat similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mine does not have a MOD VERSION category
everything else is identical except
Build Number which says
dream_devphone-userdebug 1.6 DRC83
14721 test-keys

And my model number says Android Dev Phone 1

chinkpak said:
And my model number says Android Dev Phone 1
Click to expand...
Click to collapse
That means you rebooted after flashing the HTC ADP 1.6 rom...Which is not the correct thing to do
The Base rom can be found in enom's thread, then flash the cyan rom but first we need to get you suited up with Amon_Ra.

Oh boy...say what hahaha

So how do I get back to square 1 here?

chinkpak said:
So how do I get back to square 1 here?
Click to expand...
Click to collapse
Press
Cam+power
Then put what it says.
I think that rom takes your root away but i havent tried flashing it alone.
If your recovery image is still there you can:
0.get Amon_RA http://forum.xda-developers.com/showthread.php?t=566669
1.Wipe
2.Flash this base rom
http://forum.xda-developers.com/showthread.php?t=538456
3.Flash cyan after that w/o rebooting
4.reboot

chinkpak said:
So how do I get back to square 1 here?
Click to expand...
Click to collapse
here
http://forum.xda-developers.com/showthread.php?p=4677631#post4677631
aces method wont work because the recovery is replaced on boot..at least im pretty sure it is

Hmm that didn't work?
It says device is not found when I typed in adb remount
I should mention I cleared everything off my SD card, its totally blank, sort of lost as to where I am :S

I have nothing installed on my mem card right now and I have no backup recovery progs installed, Im just starting fresh, heres my stats
Model number
ANDROID Dev Phone 1
Firmware
1.6
Baseband Version
62.50s.20.17H_2.22.19.26I
Kernel Version
2.6.29-00479-g3c7df37
[email protected] #19
Build Number
dream_devphone-userdebug 1.6 DRC83
14721 test-keys
Also when I boot(holding Camera)
It says
DREAM PVT 32B ENG S-OFF
HBOOT- 1.33.2005 (DREA21000)
CPLD-4
RADIO - 2.22.19.26I
APR 20 2009, 15:30:43
Hope thats helpful haha
Oh I'm also on a ROGERS DREAM, I dont think the TMobile tuts are helpin

reboot into recovery (home+ power) and reflash cm 4.2.11.1 and see what happens.

I get the triangle with the exclaimation mark when I do that :S

chinkpak said:
I get the triangle with the exclaimation mark when I do that :S
Click to expand...
Click to collapse
have you tried pressing alt+L?

reroot use this method
http://androidcommunity.com/forums/f12/rooting-your-g1-made-easy-11825/
I have done this what you are experiencing on pupose one time.

I didnt know about Alt+L
But anyways, I pressed Alt+L and tried to apply sdcard:update.zip(4.2.11.1), but it aborted installation for what reason I don't know
As for that link, my RC is 83? Which one would I use RC30 file or 8? I'm from Canada btw, using a Rogers phone, will using the american RC30 work?

Oh man, what happened I follwed the first step from this topic
http://androidcommunity.com/forums/f12/rooting-your-g1-made-easy-11825/
I used the RC30 file, and now my phone says T-Mobile and I can't get past google activation and it says im on roaming wtf...

Oh man, Im panicking here can someone help me
I've even lost the little skateboarding fellows at the bottom
I can't get past the google activation screen(no data/3g)
Im on T-Mobile...I should be on Rogers
Ahh mann

Absolutely bricked?

Story, in key point format:
-Just moved, no internet at home yet (in fact I've been using tether since I only check e-mail and use FB anyway)
-At cafe... Already closed, but they agreed to let me stay about 5 minutes past closing time, no time to search. NO N00B/"SEARCH FIRST" COMMENTS PLEASE.
-Don't have any old phones
-Just got a new girlfriend and didn't think much about emergency expenses and spent most of my $ on wine n' dine with her (but at least I got some worthy "dessert", but that's another story).
-Just lost my job a week after meeting her (I stayed up all night, eventually gave into a "food coma" [see above] and came into work late) LOLOL... Woulda had a new phone budget if I was around for another 2 weeks, but noooo....
Anyway:
-Tried to install CM5 onto G1
-Installed it with the CM bootloader (or something like that, it had an orange font)
-Downgraded to RC29, successfully loaded AMON_RA
-Installed DangerSPL, rebooted per the instructions
-Stuck on the boot screen for almost exactly half an hour (5 mins after 8PM until 8:30PM), said "WTF" and pulled battery out
-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work (although when you push end+trackball the blue light turns on, whatever that means)
With that in mind, what should I do? Any hope?

Hmm well Im not an expert like most of these other guys by ANY means, but in my experience I've learned that removing the battery during a percieved "hangup" is a sure fire way to brick a G1. Trust me Ive done it, not fun.
If you can make it to the recovery screen somehow, theres still hope. On the Cyanogen Wiki, I believe theres a type of method for reflashing a rom, by booting while holding the camera button. I would recommend researching that.

Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.

You forgot to flash a compatible radio!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

BoomBoomPOW said:
You forgot to flash a compatible radio!
Click to expand...
Click to collapse
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.

DAMNITS!! I only read the "steps" portion of the instructions on the Cyanogen Wiki, which didn't even include the "radio" portion of the equation (I edited it just to avoid other people having the same problems).
lbcoder said:
Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.
Click to expand...
Click to collapse
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Acecalibur said:
...by booting while holding the camera button. I would recommend researching that.
Click to expand...
Click to collapse
"-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work"
lbcoder said:
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.
Click to expand...
Click to collapse
Well, I was (somewhat) following the steps of the Cyanogen wiki.

EdWaRdW818 said:
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Click to expand...
Click to collapse
Your information is wrong. There's no baking, there's no removing chips. There is just interfacing with the board. If you're handy with a soldering iron, its a cakewalk.
Well, I was (somewhat) following the steps of the Cyanogen wiki.
Click to expand...
Click to collapse
Finding all your information in one location? What makes you think that your SINGLE SOURCE of information was accurate or correct? For all you know, it was written with the INTENTION of screwing you up.

[Q] HTC HD7 keeps booting in Data Transfer screen

Hello, guys.
First of all, I'm a little new to phone-modding, so please bear with me.
I have one HTC HD7 (PD29***) with HSPL3.1.2250.
Whenever I turn it on, it goes directly to a black screen with a picture of a cellphone, an USB cable and a computer, and an arrow pointing the USB Cable to the computer (I believe it's the USB Host mode)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there any way to fix this? Any way to try to push a rom through the USB connection?
Can anyone provide a backup file that I can try to restore?
Thank you!

Easy!
It's a stuck camera button, just do a minor disassembly to release it...

faustolg said:
It's a stuck camera button, just do a minor disassembly to release it...
Click to expand...
Click to collapse
Thanks for the reply!
Just dissassembled pretty much the whole cellphone. I even turned it on while disassembled, but I keep getting this.
Also, I can feel the camera button "clicking" in a normal way when I press it!
Any other possible ideas? Can I upload a rom when the phone is in this state to test it?
My USB Boot screen works normally, I can even install bootloaders without trouble. Transcript to it is here:
Code:
PD29*** SS-BC (4K)
HSPL3.1.2250.0(119314)
CotullaHSPL 0x07
TOUCH S1(v1.8,#1624)
SD UNKNOWN 2
Partition Info-v211v413

stephenkall said:
Thanks for the reply!
Just dissassembled pretty much the whole cellphone. I even turned it on while disassembled, but I keep getting this.
Also, I can feel the camera button "clicking" in a normal way when I press it!
Any other possible ideas? Can I upload a rom when the phone is in this state to test it?
My USB Boot screen works normally, I can even install bootloaders without trouble. Transcript to it is here:
Code:
PD29*** SS-BC (4K)
HSPL3.1.2250.0(119314)
CotullaHSPL 0x07
TOUCH S1(v1.8,#1624)
SD UNKNOWN 2
Partition Info-v211v413
Click to expand...
Click to collapse
I just tried the Y-Cable, but my cellphone keeps saying "No Image File"!

goldcard method is not the solution...
i's the camera button, if it's not clicking it's damaged...
The RUU file on the goldcard must be called SCHUIMG (uppercase) and you must use a 1GB card (it works better sometimes).
Good luck!

faustolg said:
i's the camera button, if it's not clicking it's damaged...
The RUU file on the goldcard must be called SCHUIMG (uppercase) and you must use a 1GB card (it works better sometimes).
Good luck!
Click to expand...
Click to collapse
The RUU worked as a charm with a 1GB card, I was trying with a 8GB but didn't work.
Case is solved and my Schubert is now with WP7.8!
Thank you guys!