brick fixed brick again, SPL troubles - G1 Q&A, Help & Troubleshooting

Y does my phone brick everytime i try to flash SPL? i know to do radio 1st, the SPL 2nd, then reboot, but when i reboot, it brick, this happened 5 times in a row, just today alone

It's not a brick if you can flash the radio and spl again. After flashing the spl you have to flash a new ROM because the spl removes the ROM.

make sure you flash the right spl for the right device, i flashed hard-spl to my 2nd gen dream and had a brick, 2005 spl worked on the replacement device

Fingerlickin said:
It's not a brick if you can flash the radio and spl again. After flashing the spl you have to flash a new ROM because the spl removes the ROM.
Click to expand...
Click to collapse
no believe me it was bricked, i couldnt do anythin, i just know how to fixed a bricked G1 thats all, but thanx 4 the info, i will try it now

djet229 said:
no believe me it was bricked, i couldnt do anythin, i just know how to fixed a bricked G1 thats all, but thanx 4 the info, i will try it now
Click to expand...
Click to collapse
Would you like to share how to fix a brick, there are many that would love this information.

Fix bricked g1
david1171 said:
Would you like to share how to fix a brick, there are many that would love this information.
Click to expand...
Click to collapse
all u have to do is unroot, have a spare SD card, format it 2 FAT32 just like in the beginning, then place the dream.nbh file on the root of the SD, the start the phone inn bootloader(u guys know this stuff) then when its done, u will have lost root access, but will still have a working G1 and can always reroot

djet229 said:
all u have to do is unroot, have a spare SD card, format it 2 FAT32 just like in the beginning, then place the dream.nbh file on the root of the SD, the start the phone inn bootloader(u guys know this stuff) then when its done, u will have lost root access, but will still have a working G1 and can always reroot
Click to expand...
Click to collapse
If you can get into the bootloader the phone is not bricked. Your terminology is incorrect. What you have is known as a soft brick.

rdfry said:
If you can get into the bootloader the phone is not bricked. Your terminology is incorrect. What you have is known as a soft brick.
Click to expand...
Click to collapse
Is that also known as a whiskey brick? HAHA

djet229 said:
all u have to do is unroot, have a spare SD card, format it 2 FAT32 just like in the beginning, then place the dream.nbh file on the root of the SD, the start the phone inn bootloader(u guys know this stuff) then when its done, u will have lost root access, but will still have a working G1 and can always reroot
Click to expand...
Click to collapse
The brick we are referencing is where the phone will not get into bootloader or recovery.

ummm... aren't you supposed to install a ROM after you upgrade your SPL? BTW, don't tell us you know what a brick is and then show that your phone is not bricked... I'm pretty sure if there was a fix for the brick it would be big news.

{
"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"
}

I had a brick, I held down the power button and the phone turned off and I could not get it to turn back on by holding the camera or home buttons. I finally found that the way to unbrick the phone was to hold down the power button and voila' it worked great
By the way I killed another G1, damn screen died out
***** and complained to t-mobile and got no where's with them, then I found the execitive custumer's relations # within 10 minutes they had me able to go get a brand new one at a store

gridlock32404 said:
I had a brick, I held down the power button and the phone turned off and I could not get it to turn back on by holding the camera or home buttons. I finally found that the way to unbrick the phone was to hold down the power button and voila' it worked great
By the way I killed another G1, damn screen died out
***** and complained to t-mobile and got no where's with them, then I found the execitive custumer's relations # within 10 minutes they had me able to go get a brand new one at a store
Click to expand...
Click to collapse
whoa i need that number

hjlow said:
make sure you flash the right spl for the right device, i flashed hard-spl to my 2nd gen dream and had a brick, 2005 spl worked on the replacement device
Click to expand...
Click to collapse
somebody can explain what is that ?? which device can I install hard SPL ?

I would like some clarification too... Last night I tried rooting my Rogers HTC Dream with the step-by-step guide using CyanoGen Mod, but on the very last step (Where it should have booted back into normalcy), it just stayed at the Rogers logo forever.
I don't think it's entirely bricked as I can get into the SPL thing (That's where you can do 'Fastboot USB', right?). I'm not sure how to get it back to normal though, I tried doing 'fastboot boot recovery.img' while the phone is in the Fastboot usb screen, and it reboots but it just sits at the Rogers logo again.
Is this thing bricked, or do I have options?

Okay, I did some more reading and now i understand a bit better...
What I have access to is the Bootloader, but I can't seem to get into the SPL. What steps do I need to take to get it back to working condition? I have a Rogers HTC Dream and I must have messed up when trying to apply the Cyanogen ROM

Holy Crap! A way to fix a Brick????!!!!!!!WOW!!!!!!!!
Hey if there's a way to fix a brick let me know cuz WOW! I would have gotten further with the last G1 I sent back to T-Mobile if I could have fixed it myself! Check your statements as you pertain it to being "BRICKED." BRICKED is not going past the T-Mobile G1 screen or not starting up at all! These newbies need to get it right! WOW! This one did give me a GREAT laugh today! This just made my day better now that I've had a good laugh!

can you get into recovery after the spl? home+power

jonzina said:
somebody can explain what is that ?? which device can I install hard SPL ?
Click to expand...
Click to collapse
Only the t-mobile g1/ADP1
rogers from canada will brick
use 1.33.2005 for rogers. its safe on that phone
the spl is the bootloader (well just think of it as the same)
in command prompt, when you type
Code:
fastboot devices
can you see your phone?
Also, if you booted off of the HTC recovery rom, your actual recovery is being replaced on each boot.
Search for the
"flash_image not found" thread in this section and look at sleepy_sanchez's method to remove the script that replaces the recovery.
EDIT
fastboot erase recovery
fastboot flash recovery *name of recovery*
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
try that
making sure the images are in the same folder as the fastboot
if that doesnt work, try
http://forum.xda-developers.com/showthread.php?p=4677631#post4677631

Related

I think I bricked him :(

Something screwed up today after installing that ApptoSD application from the market and I had to downgrade to RC29 again. That was all fine.
Now I was in the process of upgrading to CM 4.0.4. I already installed the old HardSPL, and realized I needed to install the 'new' one. I did this, and upon reboot my phone is stuck at the G1 screen.
Home+Power and Camera+Power do absolutely nothing.
Am I ****ed? This sucks.
jackaz said:
Something screwed up today after installing that ApptoSD application from the market and I had to downgrade to RC29 again. That was all fine.
Now I was in the process of upgrading to CM 4.0.4. I already installed the old HardSPL, and realized I needed to install the 'new' one. I did this, and upon reboot my phone is stuck at the G1 screen.
Home+Power and Camera+Power do absolutely nothing.
Am I ****ed? This sucks.
Click to expand...
Click to collapse
Yes, its gone. You need to install the radio update before the SPL update. Don't know why you would install the update that kills so many phones without reading up on it...
for the record: cm4.0.4 and all cyanogen mods do not require the DangerSPL, hardspl works fine.
Wow you get a big ol' F for not doing your homework and thinking that you needed the newest thing, good job screwing yourself
Just like everyone else said your toast. I was first thinking why would you need to go back to rc29 because of an apps2sd issue or really any issue, you should have just reflashed a rom. Second (like the others said) you didn't need the new spl.
{
"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"
}
WTB - spare batt and batt cover!
Whoa, didn't need to jump down my throat - I already flashed the new radio after HardSPL, but I suppose it doesn't matter anyway.
The phone bricked after installing that app, and upon restart it was stuck at the G1 screen, I had to leave the office so I reflashed to RC29 (as it was the only ROM I had on my laptop) while I was on the road (so no internet access) because I desperately needed my phone for a job I was attending. When I got back to the office I must have mixed up my update.zip files somewhere in the process.
Thanks for the help from the people that weren't dicks about it, at the end of the day it's only a phone. Time for a shiny new one.
It is pretty common knowledge that the DangerSPL will not work with older radio versions BUT I believe flashing RC29 downgrades your radio to an earlier version, therefore bricking your phone. If you decide to use DangerSPL or Haykuro's SPL (the same I think) in the future, make sure you flash HardSPL BEFORE restoring to RC29.
I would play the stupid card with TMO and see if they will send you a new one.
And if you don't already, use Cyanogen's 1.4 Recovery. You can backup and restore via Nandroid from the recovery image so you can have a working version on your SD card at all times and not need a computer to access it.
Just for my own knowledge,
A phone with the hard spl can be safely downgraded back to rc29 (if you needed to send it back to tmo for instance) correct?
It's the danger spl that can brick your system if you downgrade to earlier radio right?
dcorrea said:
Just for my own knowledge,
A phone with the hard spl can be safely downgraded back to rc29 (if you needed to send it back to tmo for instance) correct?
It's the danger spl that can brick your system if you downgrade to earlier radio right?
Click to expand...
Click to collapse
Correct......
downgrading by using rc also downgrades the radio and spl, does not matter what spl you are using. it takes it back. you will not brick by using the rc dreaimg.nbh
r4d14n7 said:
It is pretty common knowledge that the DangerSPL will not work with older radio versions BUT I believe flashing RC29 downgrades your radio to an earlier version, therefore bricking your phone. If you decide to use DangerSPL or Haykuro's SPL (the same I think) in the future, make sure you flash HardSPL BEFORE restoring to RC29.
I would play the stupid card with TMO and see if they will send you a new one.
And if you don't already, use Cyanogen's 1.4 Recovery. You can backup and restore via Nandroid from the recovery image so you can have a working version on your SD card at all times and not need a computer to access it.
Click to expand...
Click to collapse
Thanks for that information.
I'd play the stupid card but I'm guessing that being in Australia makes that pretty difficult eh?
hey you guys have an awesome prime minister
He gave use all $900 just for the fun of it. Great guy.
I guess I can try contacting HTC and see if they'll repair it, I'm expecting to pay for it but i guess it's better than paying for a new phone.
i was talking about his policies, like telling everyone that this is our country and that we will not bend over backwards to appese you and if you don't like it then get the **** out. we need someone like that guy here instead of ass kissing obama
sorry small rant
yeah you could call htc
Haha I know you were
I've got in contact with the repair center in my area and they're going to 'get back to me'.

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

desperate plea for help

if anyone here who lives in Toronto ON that can fix my HTC rogers dream , please let me know im willing to pay in beer or straight cash, long story short
i get htc dream with 1.5 , i want to update to 1.6, my friend makes recovery image and puts on nandroid v2.2 and at bottom it says " build: cyanogenMod V1.4 + JF", console doesnt work, and he tried flashing via the update.zip , and since then its never gotten past the rogers splash screen. on the camera+power menu it shows the following
DREAM PVT 32B SHIP S-ON d
HBOOT -1.33.0009 (DREA21000)
CPLD-4
RADIO -3.22.20.17
May 12 2009 , 17:05:58
HBOOT
<SEND> fastboot mode
me and Ace 42 spent the last 2 days trying to fix this problem, we tried updating the "dreaimg.nbh " or w.e its called file and then we tried loading rogers htc dream roms found on this website, and it still wouldnt boot... im fearing the worst , as i cant get into console, the screen goes from
{
"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"
}
to just the black background with the android logo and the writing " build cyanogenMod v1.4 + JF" and its unresponsive, only way is to pull battery,
also now the fastboot menu says
DREAM PVT 32B ENG S-OFF
HBOOT -1.33.2005 (DREA21000)
CPLD-4
RADIO-3.22.20.17
APR 20, 2009 15:30:43
HBOOT
<SEND> fastboot mode
also the icons on the bottom are skateboards with the little green android guys ( before and after hboot changed)...
ok so now ace42 told me he thinks the only option left is to flash the radio, but he said theres a 50/50 chance it might permanently brick the phone since its downgrading ( i think i dont exactly remember what he said) ill get him to chime in here and say his side of this whole situation.
honestly i just want android 1.5 back, no fancy custom stuff, OR android 1.6 and as long as it works normally ill be quite happy and never touch this updating fiasco every again....
Looks to me like you flashed the danger SPL without updating to the 26I radio. I am pretty sure you own a paperweight.
please.. i dont want to hear that
ummm
you are gunna have to do this
http://forum.xda-developers.com/showthread.php?t=491350&highlight=stock+firmware
then after you do that, just either go to your settings and search for updates or root and get a CM rom
After re-reading you post, I am really not positive. I didn't notice you were using a rogers phone. The radio might be different. Hopefully someone with a rogers phone can confirm their radio with yours.
do you have another nandroid backup? if so... when you press camera+power, go into fastboot mode and fastboot flash system.img...etc, if not use fastboot to flash another update.zip
So after checking out some sigs from other Rogers users...they have the 26I radio with the 1.33.2005 SPL...so yea...I fear the worst for you. Good luck tho.
nandroid backup of the OS when the phone was working?? no i accidentally pressed the backup choice and it overwrote the original recovery with a nonworking rom
sockpuppet4 said:
So after checking out some sigs from other Rogers users...they have the 26I radio with the 1.33.2005 SPL...so yea...I fear the worst for you. Good luck tho.
Click to expand...
Click to collapse
, this is a ******* nightmare.. i dont have money for a new phone and i needed this phone for work...
cant i update or change SPL then change radio?
wait, my radio didnt change at all from the beginning to right now???
just the SPL... :|
32adream said:
, this is a ******* nightmare.. i dont have money for a new phone and i needed this phone for work...
cant i update or change SPL then change radio?
wait, my radio didnt change at all from the beginning to right now???
just the SPL... :|
Click to expand...
Click to collapse
Sorry man, it happens. Good luck to you. Maybe try and brick it all the way and get your warranty fix.
cant.. bought it second hand...
*checked spl & radio versions
*attempted to flash cyan mod
*tried micro hero
*tried regular rogers build by enomther
*console but was unable to acess
*was gonna try to flash dreaimg-rc29 but it contains older radio
ok so you can get into recovery and fastboot?
yes i can get into recovery and fastboot.
lol... chill.. this is NOT an spl brick. Sounds like your recovery image could be corrupt from a bad flash, but that's perfectly fixable. You know how to use fastboot from your pc, right? If not there are plenty of guides around here.. use fastboot to flash either cyanogen's recovery or amon_ra's.. from there, follow instructions to install CM 4.2 here: http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_Versions
Just don't flash that old radio.. thats not a 50/50 chance of brick, that's 100% cast-iron brick.
ITT: n00bs scaring n00bs.
ace42 helped me alot, i dont think he is a noob
ok from what you said, im gonna need step by step instructions on how to access fastboot from my pc. :| goldenarmz do you have gmail chat or msn??
I can't do a live chat atm, but I'm feeling helpful so I'll try to talk you through it here.. I'm just reading up on the rogers dream rooting process to try and see where you're at.
While you wait, download and indstall the android 1.6 sdk from here:
http://developer.android.com/sdk/index.html
http://developer.android.com/sdk/installing.html
You don't need to download eclipse or set up the adt, just get the SDK installed with the tools path defined.
I'm assuming you're on windows btw?
yep, windows xp
OK I think I can see where you've gone wrong. You need to have the rom you want to flash on your sdcard (im assuming its still there from your earlier tries), and you need to download givemeroot.zip to your pc:
http://www.stevebirstok.com/android/givemeroot.zip
Let me know when you've got the SDK installed and we can proceed..
i was on the other computer, im doing all this from my laptop since the usb ports are right in front of me, i actually do have the sdk, and i dont think i have the rom i want . i just want a plain android 1.6 thats optimized for the htc dream. and now its updating the sdk

Touch pro2 stuck at tricolor bootloader screen

OK i tried getting help at the hardspl thread but just getting a generic answer.
I was wondering if there is anyone who can point me in the right direction or hold my hand so to say with step by step instruction on possibly fixing the problem i currently have.
here is what i had performed to get to where i am at right now.
I had my phone hardspl. been flashing different roms then stayed with one. then today my phone wasnt able to activesync and the usb wasnt being recognized so i wasnt able to activesync, or use phone as a disk drive or internet sharing but the phone would still charge through usb. i called tmobile they are sending me a phone ill get it in about a week in the meantime i need to make this one back to stock.
So i downloaded and flashed the tmobile stock rom which i found here....http://forum.xda-developers.com/showthread.php?t=550975 after that was installed.
I then downloaded the tmobile splash screen which was provided in a link found here... http://forum.xda-developers.com/showpost.php?p=4592520&postcount=163
i then downgraded the radio.
after doing all that all what was left was to change the hardspl to relock to spl. well being that my usbport was not being detected by computer to use activesync being that your phone needs to be synced in order to use the rhodiumsplrelocker.exe program. so i ran the program and when the files showed up from the program i took the RUU_signed.nbh file and moved it into another folder and renamed it to rhodimg.nbh and placed on my memory card thinking this would relock the phone using the sd card loader method..
I ran it and then the phone frooze. it rebooted and when it did this is what shows up
When i try to put the stock rom image file back on my memory card as i was told to do... after the first screen with the tricolor it then goes into a second screen with the words loading and thats it...i let it run like this for 20minutes and there was no change. heres what that screen looks like
is there anyone who may help me i would appreciate it greatly. ill be willing to make a donation to you for a solution that really works.
Connect to your device via MTTY (delete the NBH on your SD for good measure), and in the MTTY terminal, simply type this command:
Code:
[FONT=Courier New][B]set 16 0[/B][/FONT]
After that, it should boot back to Windows Mobile just fine. Good luck
DaveTheTytnIIGuy said:
Connect to your device via MTTY (delete the NBH on your SD for good measure), and in the MTTY terminal, simply type this command:
Code:
[FONT=Courier New][B]set 16 0[/B][/FONT]
After that, it should boot back to Windows Mobile just fine. Good luck
Click to expand...
Click to collapse
can you send me the mtty program or send me a link or direct me to where i can get this mtty program much appreciated
edit: i tried mtty program and its not working. the program needs to access the usb port on phone. the first problem i was having was that the computer was no longer to read the usb port on phone due to a problem with the usb hardware. so any fix that may require a usb to computer connection may not work...if theres a way to put a file on the memory card that would work to fix or to have it boot to windows without going into the loader all the time that would help.
I just looked at the pictures in the first post, and that SPL is the shipping SPL, and not HardSPL. Therefore, it doesn't matter if the phone boots or not, since you've made everything stock, and they have nothing on you. You can just say that your phone started doing this and you don't know why, and if you play dumb, they'll have no reason to suspect otherwise.
you need to find a computer with a working usb port. Mtty is your best way out of this. It's a pretty simple problem that you have actually. mtty can be quirky so don't give up!
Sleuth255 said:
you need to find a computer with a working usb port. Mtty is your best way out of this. It's a pretty simple problem that you have actually. mtty can be quirky so don't give up!
Click to expand...
Click to collapse
I have the same problem and the issue isn't our computer is the actual MINI USB port on the phone that no longer works
Um, i hate to tell you, but that same thing happened to me. I got it all back to stock, called HTC , sent it in for repair, they kept it for 45 freeking days. I just got it back. Cost $20.
Good luck. I tried everything before sending it in. Nothing worked.
Im just wondering if sending it to T-mobile that way would cause a charge to me
usb not working
ok this is for everyone who has tried to help and i really do appreciate it. but one thing people seem to keep forgetting about is you have to remember the USB PORT on the phone has MALFUNCTIONED meaning it doesnt work anymore. So for those of you who have come up with try using MTTY program...well the thing is you need to have a working USB in order for that to even work. so as i have mentioned before is there any program out there that would help by trying some rebooting program you can install on the memory card or what would really help is if the people who made the hardspl and the splrelocker would make a splrelocker program that can all be run off of the memory card with no need for the USB port because if and when that usb port is no longer working and you need to return for warranty reasons then it would be a great help being you can still relock the spl even with a non working usb port.
ok, so everybody started out not being able to activesync due to a malfunctioning mini-USB port.
If this was the case, how was anyone able to downgrade the spl in preparation for a return.... which normally requires a working MiniUSB connection?
Are you absolutely sure this isn't the (more common) PnP-doesn't-recognize-the-port issue?
usb problem
Sleuth255 said:
ok, so everybody started out not being able to activesync due to a malfunctioning mini-USB port.
If this was the case, how was anyone able to downgrade the spl in preparation for a return.... which normally requires a working MiniUSB connection?
Click to expand...
Click to collapse
when i first received the phone ... yes the usb port was functioning well and i was able to hardspl my phone... and everytime i would flash a rom i would put the rhodimg.nbh file on the root of my memory card and do the hold volume button down and hit the reset button allowing me to boot to the tricolor screen without the need for activesync or usb to flash a rom. during the use and life of my phone the usb port malfunctioned maybe from wear and tear who knows...so even with the usb dying im still able to flash roms to my phone through the memory card which i could use a memory card reader to put the rhodimg.nbh file onto and then put memory card into phone and reboot the phone while holding down the voldown button still letting me access the bootloader screen without the need for usb. so my thing is if a problem develops during this process how do you fix it when the usb no longer works.
So your SPL isn't downgraded then? That would make sense given the problem you cite. I'm hoping you say that it is because that means there's still hope b/c I don't know of a way to do the downgrade from SD. The only way you can communicate with the BL is through the USB port afaik.
Sleuth255 said:
So your SPL isn't downgraded then? That would make sense given the problem you cite. I'm hoping you say that it is because that means there's still hope b/c I don't know of a way to do the downgrade from SD. The only way you can communicate with the BL is through the USB port afaik.
Click to expand...
Click to collapse
Correct me if im wrong, the screen where he is stuck (See screenshot post #1), looks like original SPL? If so, how can T-Mobile even notice it has been reflashed? What im trying to say is, if he just play dumb, he should get warrantee just fine, since it looks all original to me.
good point... looks like yours is one option. Still perplexing how the downgrade could have occurred with a bad miniUSB port... There are some real quirks getting mtty to connect. Some of them had to do with getting USB active on the BL screen... I haven't used the utility since I had my TyTN in the days before soft/hardSPL however.
not sure where you ended up with this, but I ran across the following thread and thought about your problem:
http://forum.xda-developers.com/showthread.php?t=540290
It shows the many things that are needed for successful USB tri-color connect with mtty.
Sleuth255 said:
not sure where you ended up with this, but I ran across the following thread and thought about your problem:
http://forum.xda-developers.com/showthread.php?t=540290
It shows the many things that are needed for successful USB tri-color connect with mtty.
Click to expand...
Click to collapse
i have same problem
my touch pro 2 stuck at tricolor bootloader screen
and i have mtty1.42 soft
what i do or how i can slove my problem
plz help
B.R.
mobitec said:
i have same problem
my touch pro 2 stuck at tricolor bootloader screen
and i have mtty1.42 soft
what i do or how i can slove my problem
plz help
B.R.
Click to expand...
Click to collapse
what is the SPL version?
cmonex said:
what is the SPL version?
Click to expand...
Click to collapse
{
"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"
}
check plz
thx
plz any help
????
mobitec said:
plz any help
????
Click to expand...
Click to collapse
wow that was a big photo...
ok, well, do you have a GSM tp2? or a CDMA/GSM one? because it says RHOD500 modelid on the screen but I'm not convinced that you actually have a CDMA worldphone...
if you are not sure, then tell me what carrier the device is from, that'll give me a hint if it's GSM or CDMA/GSM.

[Q] Stuck in cyclic restart after Radio ROM upgrade!?!

Hi, i am from Turkey,
I have a Touch Diamond (Diam100) bought from Norway. I just loaded a new radio ROM onto my phone (I am security unlocked and sim unlocked and hard SPL'd, thanks to Olinex!) and everything looked to work fine, the status bar got to 100% and the phone rebooted as usual after a new ROM load
However - it is completely stuck in a cyclic reboot. I get the HTC startup screen and then it just reboots again and again. I tried a hard reset and got the confirmation message that it was restored OK, press volume up to boot. However it does the same reboot again and again
I tried some thing like that:
*Try to install "RUU_Diamond_HTC_NOR_1.93.409.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship" stock rom, but it freezes at %13
*Try to install stock radio rom "Diamond_Radio_1.00.25.05" bu it freezes at %95!
*Try to install stock spl, everything looked to work fine, the status bar got to 100% and the phone rebooted as usual after a new ROM load but the problem seems again!
i can install cooked roms, but after restart this problem happens again and again!
Can you help me please? I love my phone very much.. (
(sorry for my poor english)
Hi, try MTTY your phone. log in to use search in these fora and find "The definitive MTTY thread". It's a bit of...homework to do but will get you out of this.Your issue is caused by certain undeleted items which remain after a rom flash as far as i've learned.I hadn't have to do it until after several ROM flashes but guess sooner or later everybody faces it.Well it's time you did it too...
Cheers
[email protected] said:
Hi, try MTTY your phone. log in to use search in these fora and find "The definitive MTTY thread". It's a bit of...homework to do but will get you out of this.Your issue is caused by certain undeleted items which remain after a rom flash as far as i've learned.I hadn't have to do it until after several ROM flashes but guess sooner or later everybody faces it.Well it's time you did it too...
Cheers
Click to expand...
Click to collapse
hi, i tried it step by step. but nothing happens
Hi,
Dude, that's frustrating, however as i understand it's a stock SPL you've presently got on your phone, right? I don't know which SPL version you've had before but just in case, try to update to HSPL version 1,93. Then try flashing a ROM you like.If problems persist MTTY your phone again after having upgraded HSPL.
And a word of advice based on own experience: Not all radios are compatible with all ROMs and vice versa...
Hope you're soon going to get this right,
Regards from Greece
merinos said:
Hi, i am from Turkey,
I have a Touch Diamond (Diam100) bought from Norway. I just loaded a new radio ROM onto my phone (I am security unlocked and sim unlocked and hard SPL'd, thanks to Olinex!) and everything looked to work fine, the status bar got to 100% and the phone rebooted as usual after a new ROM load
However - it is completely stuck in a cyclic reboot. I get the HTC startup screen and then it just reboots again and again. I tried a hard reset and got the confirmation message that it was restored OK, press volume up to boot. However it does the same reboot again and again
I tried some thing like that:
*Try to install "RUU_Diamond_HTC_NOR_1.93.409.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship" stock rom, but it freezes at %13
*Try to install stock radio rom "Diamond_Radio_1.00.25.05" bu it freezes at %95!
*Try to install stock spl, everything looked to work fine, the status bar got to 100% and the phone rebooted as usual after a new ROM load but the problem seems again!
i can install cooked roms, but after restart this problem happens again and again!
Can you help me please? I love my phone very much.. (
(sorry for my poor english)
Click to expand...
Click to collapse
before you upgrade the radio, whether it has been unlock device with the XDA Unlock Application ..? try to hard reset your device after that make sure the device go to the boot loader (3 colors screen) and reflash with the official ROM!! then unlock the device and immediately you can do to upgrade the radio (at the time of upgrading the radio make sure the SIM card removed)
[email protected] said:
Hi,
Dude, that's frustrating, however as i understand it's a stock SPL you've presently got on your phone, right? I don't know which SPL version you've had before but just in case, try to update to HSPL version 1,93. Then try flashing a ROM you like.If problems persist MTTY your phone again after having upgraded HSPL.
And a word of advice based on own experience: Not all radios are compatible with all ROMs and vice versa...
Hope you're soon going to get this right,
Regards from Greece
Click to expand...
Click to collapse
hi, i can not change the hspl, i tried again and again, but nothing changed.
(hspl olinex 1.93 signed and unsigned versions)
i tried to change the hspl to stock spl, installation was going and everything was ok (%100 inst.) but after restart, spl 1.40 olinex in bootloader mode again!
i don't know how can i change this 1.40 spl. i think the main problem is spl and radio rom.
{
"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"
}
Hakim Rahman said:
before you upgrade the radio, whether it has been unlock device with the XDA Unlock Application ..? try to hard reset your device after that make sure the device go to the boot loader (3 colors screen) and reflash with the official ROM!! then unlock the device and immediately you can do to upgrade the radio (at the time of upgrading the radio make sure the SIM card removed)
Click to expand...
Click to collapse
hi, my device is security unlocked, and hspl version is olinex 1.40.
i can not acsess to os, it just stay in the touch diamond screen .
thanks for the solution.
merinos said:
hi, my device is security unlocked, and hspl version is olinex 1.40.
i can not acsess to os, it just stay in the touch diamond screen .
thanks for the solution.
Click to expand...
Click to collapse
you have to do is to Hard Reset your device and reFlash

Categories

Resources