Right. I bought this phone (second hand, flashed with shifu 4.2 ROM {I have no clue what this means}) and it worked perfectly. It didn't come with a sim, so I went out and bought two. An O2 and an Orange one. The O2 one had problem's activating, so I placed in the Orange one. The phone somehow screwed up, saying iLockV2.exe is corrupt/could not be found. So, I contacted the seller, he told me to do a hard reset, which I done. The phone worked fine from there.
This afternoon, the phone froze, so I took out the battery and put it back in. The same problem occurred with the iLockV2.exe thing above; so I tried to do another hard reset, it didn't work. After that, I was stuck at the HTC screen where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
.
I then took out the battery again, and the same thing happened. So I took out the battery once more, and when I pushed the power button it wouldn't turn on. So, I took the battery out and left it for about 4 hours, and put it back in, but now, I'm still stuck at the HTC boot screen (same code as above).
What do I do to make my phone work again?
koglaa said:
Right. I bought this phone (second hand, flashed with shifu 4.2 ROM {I have no clue what this means}) and it worked perfectly. It didn't come with a sim, so I went out and bought two. An O2 and an Orange one. The O2 one had problem's activating, so I placed in the Orange one. The phone somehow screwed up, saying iLockV2.exe is corrupt/could not be found. So, I contacted the seller, he told me to do a hard reset, which I done. The phone worked fine from there.
This afternoon, the phone froze, so I took out the battery and put it back in. The same problem occurred with the iLockV2.exe thing above; so I tried to do another hard reset, it didn't work. After that, I was stuck at the HTC screen where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
.
I then took out the battery again, and the same thing happened. So I took out the battery once more, and when I pushed the power button it wouldn't turn on. So, I took the battery out and left it for about 4 hours, and put it back in, but now, I'm still stuck at the HTC boot screen (same code as above).
What do I do to make my phone work again?
Click to expand...
Click to collapse
First of all, stop taking out the battery when the phone is on because that really screws up the files. You are doing more harm than good there.
Try a series of soft resets to try and fix it. If that doesn't work, try a series of hard resets to solve the problem.
If no luck there, go into bootloader ( tri color screen ), hold in power and camera button at same time while doing a soft reset. The try flashing a stock Orange rom ( found in the wiki ) Then re-flash with shifu rom.
Not letting me hard reset, so I'm just going to reflash (Y). I hope I do this right :\
EDIT:
My computer can't read my phone when connected via usb D:
koglaa said:
Not letting me hard reset, so I'm just going to reflash (Y). I hope I do this right :\
EDIT:
My computer can't read my phone when connected via usb D:
Click to expand...
Click to collapse
What does the phone do when you try to hard reset ?
When you put your phone into bootloader what does the screen say . When in bootloader, does the bottom of the screen change from serial to usb when you plug it in to your pc ?
denco7 said:
What does the phone do when you try to hard reset ?
When you put your phone into bootloader what does the screen say . When in bootloader, does the bottom of the screen change from serial to usb when you plug it in to your pc ?
Click to expand...
Click to collapse
The phone just soft reset's when I try to hard reset.
And yes, it does change from serial to usb when I plug it into my computer
Seem's like I was doing the hard reset wrong. Same thing is still happeneing, not getting past the part where it says:
Code:
R 1.71.09.01
G 25.75.40.02.
D 3.34.shifu
EDIT:
After 20 or so hard resets, I've moved onto the boot-loader, then it took about 5 minute's to load to the main OS. I think everything is sorted out now. Thanks
omg, this is getting really annoying now. The phone keeps on crashing at random interval's and can only be recovered by hard resetting :\
Well if it keeps happening try a different ROM just make sure you follow F.A.Q for ROM your flashing.
The thing that it's saying is corrupted is S2U2 and to me sounds like it just can't find the .lnk in Windows StartUp.
Flash OEM Rom before the new one and if you have 2GB or smaller SD Card flash using the SD Card method.
stylez said:
Well if it keeps happening try a different ROM just make sure you follow F.A.Q for ROM your flashing.
The thing that it's saying is corrupted is S2U2 and to me sounds like it just can't find the .lnk in Windows StartUp.
Click to expand...
Click to collapse
It happen's when the phone freeze's and I soft reset it :\
koglaa said:
It happen's when the phone freeze's and I soft reset it :\
Click to expand...
Click to collapse
I'd go with what Philux-X says "to which is why i said F.A.Q" try and flash a stock ROM prior to flashing custom so as to clear nand.
The corruption due to stalling sounds pretty normal as the phone does not get to shut down via the usual method.
stylez said:
I'd go with what Philux-X says "to which is why i said F.A.Q" try and flash a stock ROM prior to flashing custom so as to clear nand.
The corruption due to stalling sounds pretty normal as the phone does not get to shut down via the usual method.
Click to expand...
Click to collapse
I'll do that next time it crashes .
Thanks for all your help guys
Related
I've been trying to get my old extended rom and new Qtek OS on my Wizard (Vario).
But now it gets stuck in the spash screen (ie the one giving the ROM numbers).
I've tried putting the wizard into bootloader mode and I can flash RUU's but when it resets it still gets stuck on the spash screen and won't go any further !!!????
What can I do ??
Please Help
Cheers
John
I should say that I had flashed using button's ROM RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
and this worked fine!
I then copied across my T-mobile Extended ROM and again everything seemed OK.
BUT then I tried to restore my new saved OS ROM using aWizard and this caused a freeze on my Wizard. It was after a hard reset that the wizard stopped at the splash screen.
Now of course I'm limited in my options because Activesync won't work until the Wizard has fully booted up.
I have tried setting the Wizard into bootloader mode and tried several ROM's (RUU Installer ones) but every time the correct splash screen comes up with the new ROM numbers but that is as far as it gets.
I also noticed on hard reset that you get the following message
Format FAT partition
Format failed
it then goes to the splash screen as before.
Are there any other things I can try Or will I have to send it back to T-mobile for a replacement??
(It's only 2 months old and I have re-flashed it with the orginal T-mobile ROM - but still won't go past the splash screen!!)
I live in hope
John
I have this EXACT same problem!
I can reflash any ROM but it will not go past the splash screen. Only difference was I wasn't playing with my extended ROM. I flashed the AKU2 QTEK ROM yesterday and have been fine through several soft resets, etc. This last time I was uninstalling phonealarm and after a soft reset I got a "could not find smswakeup.exe" (or something similar) and it's been stuck ever since! I also get the "Format Failed" message. Can anyone help!?
I think I'm going to have to send it back to T-mobile and hope they give me a replacement. Something is wrong, it doesn't seem to make any difference what ROM I used.
I think I'll reload the T-mobile shipped ROM grom the FTP site and send it back - and claim ignorance that it it suddenlt freezed and now won't boot up! - Bummer!!!
Right I've logged a fault and it will be sent back - let's hope T-mobile can't detect it's been unlocked and had several ROM updates - I suspect they will try a ROM update themselves then give up ???
The worrying thing though is that it IS possible to kill your phone with updates - maybe it was when I used aWizard to try and restore a ROM that did it??? I'll be more carefull next time!!
this has just happened to one of the devices im flashing at the moment.... absolulty f**king raging :evil: :evil:
i wish teher was a solution!!? anyone got any ideas?
activesync wont find it, so aWizard wont work.
i can flash between 3 roms without any problems (1.5.x 1.6.x 2.x) but always hangs on the splash screen. i have flashed back to the default rom that it came installed with it so i could just send it back to o2 (only 2 days old!)
i would rather just get it sorted by myself thoough so if anyone has ANY ideas then please let me know.
thank you!
Good luck! after about 3 days of trying different types of firmware, I gave up and sent it to expansys, for repair. And it looks like they've lost the bloody thing now. :evil:
tonym001 said:
Good luck! after about 3 days of trying different types of firmware, I gave up and sent it to expansys, for repair. And it looks like they've lost the bloody thing now. :evil:
Click to expand...
Click to collapse
yup looks like i might have to give up... ohwell, no worries i will just return it back to O2...
looks like one of our sales guys wont be getting a new phone on tuesday :lol:
same problem here.
tryed to write os with awizzard after changing extended_rom.
kills phone.
format failed..
Tryed different os's from win util - failed
upgraded with sd card methode worked.
in short :
you need a working wizzard to make a os dump on sd card.
Connect to wizzard with usbterm or romupdate.exe or simular.
do a rs2all command to dump os to sd card.
stick this card in broken phone.
hold voice comm button while resetting.
On ask press voice comm button again.
it bow restores the sd backup to phone.
saved mine.....
btw sd card backup can be read ad write by pc with util ntrw.exe .
so if you don't have a working dump i can upload one.
just mail me.
grtx , arnold
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
There is hope
Last week after trying to downgrade to the original Cingular ROM on my 8125 using aWizard I ended up with a device that was close to being a paperweight. At least I thought so until I read and read and finally was able to get it to the bootloader and then plugged in the USB cable and ran the RUU for the new Qtek ROM (2.17). Guess what happened, yeah it worked. To my surprise I had a perfect device after 15 minutes.
For about 3 hours I thought I was a toast. Never will I do that again.
THIS is truly heaven for me !!
I have my O2 XDA MINI S locked on the splash screen .. and i updated some ROMS to it ....BUT IT DOESNT GET THROUGH IT .... please tell me what to do in a little detailed manner .. please so that i can get my phone to work.. there is no warranty on the phone and i stay IN INDIA . SO YOU'LL ARE MY ONLY HOPE .
my email id is - [email protected]
If you have a dump of the O2 XDA MINI S ..please mail it to me
Plese tell me what to do next ? WILL TRULY APPRECIATE HELP
PLEASE SOME ONE ATLEAST MAIL ME the dump of the os SO THAT I CAN TRY THE SD CARD UPGRADING ,.,,, O2 XDA MINI S
Re: There is hope
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.
Thank you so much
my mail : [email protected]
Thanks friend
hellomoto_25 said:
Last week after trying to downgrade to the original Cingular ROM on my 8125 using aWizard I ended up with a device that was close to being a paperweight. At least I thought so until I read and read and finally was able to get it to the bootloader and then plugged in the USB cable and ran the RUU for the new Qtek ROM (2.17). Guess what happened, yeah it worked. To my surprise I had a perfect device after 15 minutes.
For about 3 hours I thought I was a toast. Never will I do that again.
Click to expand...
Click to collapse
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.
Thank you so much
my mail : [email protected]
Thanks friend
odyseus said:
I've been trying to get my old extended rom and new Qtek OS on my Wizard (Vario).
But now it gets stuck in the spash screen (ie the one giving the ROM numbers).
I've tried putting the wizard into bootloader mode and I can flash RUU's but when it resets it still gets stuck on the spash screen and won't go any further !!!????
What can I do ??
Please Help
Cheers
John
Click to expand...
Click to collapse
stuck on o2 screen helppp
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.I see alot of post, so complicated
Thank you so much
my mail : [email protected]
Thanks friend
flexchen said:
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
Click to expand...
Click to collapse
how to use bootloader
could you tell me how to use mentioned bootloader for restoring the images? where can I get the software?
Please help
Hendrick
flexchen said:
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
Click to expand...
Click to collapse
Hi Arnold
My O2 cda mini s get stuck at splash scree, I read your post, still not so understand how to solve it, could you be so kind to write me step by step, and send me some software to solve it. Your help will be so much appreciated.
Hendrick
Email: [email protected]
arnoldl said:
same problem here.
tryed to write os with awizzard after changing extended_rom.
kills phone.
format failed..
Tryed different os's from win util - failed
upgraded with sd card methode worked.
in short :
you need a working wizzard to make a os dump on sd card.
Connect to wizzard with usbterm or romupdate.exe or simular.
do a rs2all command to dump os to sd card.
stick this card in broken phone.
hold voice comm button while resetting.
On ask press voice comm button again.
it bow restores the sd backup to phone.
saved mine.....
btw sd card backup can be read ad write by pc with util ntrw.exe .
so if you don't have a working dump i can upload one.
just mail me.
grtx , arnold
Click to expand...
Click to collapse
I cant believe this....I had no issues all day upgrading the ROM...until my PC overheated and shut off at 57%...
now when my phone starts up I see the 3 bars and it sais USB in the bottom left...but active sync is not connecting!
help!
what 3 bars?
a Red Blue Green Bars color?..
If that so.. you are too lucky..
I read a little more on the wiki:
Type 2a: When the phone boots, it goes directly to bootloader mode (tri-color screen)
This is what I have right now...I can't seem to get active sync to connect...although at the bottom of the screen it has "USB"
I have tried using mtty and dont think its diong anything...
Just stay in the bootloader (tri-color screen) and make sure the "USB" is shown in your device screen..
The reflash.. even if its not sync/connected.. just reflash the ROM..
Everything will be fine..
wow....i think it may actually work....that was SCARY.
nice to know the good ole button flash works when all others fail
I just want to make a clarification..
You are just flashing your device and when the upgrade process is on 57% your computer suddenly shutoff? and the upgrade was cut..
What happened next? did you reset the device then went to tri-color screen? or you just force bootloader mode it?
Yeah pretty much exactly what you said. I literally got up for a second to get some water, came back and saw the telltale sign that my pc had just shut itself off (the screen was black except for the standard boot junk that shows up).
So I look at my device (8125) and it was locked at 57% and was not responsive. I figured that the flash util probably wouldn't continue after the computer started back up (and besides, the device wasn't alive anymore) so I rolled the dice and unplugged the USB and took out the battery. When I put the battery back in and hit the power button, it went straight to the bootloader (the tri color screen).
- By the way - ive got the button image on here now - workin like a champ...
tnx for the explanation..
have fun!!..
thanks for the quick reply - i thought i was completely stuck but the button flash seemed to take care of everything. Makes me almost think that bricking this thing is near impossible... >
Yup!.. that also my conclusion.. its impossible to brick.. thats why i ask for your clarification..
What is this "button flash"? I am stuck in RGB boot mode with no activesync connection. I have read til my eyes crossed, but can not fix my 8125 (G3)!
Please advise.
How about more information? On your bootloader (Rainbow screen) what does it show the IPL / SPL to be? What were you trying to do when you got into this situation? What happened when you were flashing? Is your device a G3 or G4?
Safest thing for you to do right now is to flash your carrier's rom onto the phone (an official shipped ROM). With your phone in the bootload, just run the ROM and it will install (DO NOT RUN A CUSTOM ROM AT THIS POINT SINCE YOU HAVEN"T TOLD US ANY OTHER INFORMATION).
G3 8125
ipl/spl 2.25
Was trying to use faria's latest rom...got stuck at 99% for almost one hour, so I rebooted computer and discon'd the wizard. Now it will boot to rainbow screen and will not connect via activesync (so I can't utilize any other roms to get back to square one).
ActiveSync will NOT connect when you are at the boot loader. As long as you see USB in the bottom left of your phone (above the left soft key) then you can flash your original Cingular ROM and be good to go again.
brick, brick, brick
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
I need help....
Hunter6 said:
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
Click to expand...
Click to collapse
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Go get a copy of your carrier's official ROM (not a custom one, but an official one from your carrier.). Then with the phone at the boot loader (Rainbow screen) and the USB cord plugged, in, run the official ROM. If that doesn't work, then get a copy of the Wizard Love rom and flash it (You'll need to find links around here for it, or pull it via PirateBay). You may also want to reboot the PC you are running on and remove your SD card (if you have one) just to remove variables that can play in to all of this.
Good luck
mfrazzz said:
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Click to expand...
Click to collapse
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
-----
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Thanks!
brick, brick, brick
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help
entdiablo said:
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
Click to expand...
Click to collapse
No, that sounds like your pc locked up or something (I'd blame windows on that one )
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Click to expand...
Click to collapse
Glad to hear you got it going. Good luck and be careful out there!
Hunter6 said:
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help
Click to expand...
Click to collapse
Sorry, I may be missing your humor or sarcasm... Are you saying its dead (if so, give more details about what it does or doesn't do, IPL/SPL it shows (if it turns on), etc... If its now working, then congrats!
I've got a weird one. Yesterday, my phone was running fine (I've had Dutty's rom on it for about 4months), I lost sound and needed a reboot. I rebooted and immediately got the RGBW bootloader screen. Successive reboots gave me this. I removed my flash card and tried again - was able to get in the O.S. but I still had no sound, so I rebooted again. Now I can't seem to get past the bootloader.
I'm probably going to try a reflash of the ROM, but I'm curious if there is another option since I'd rather not lose my data.
Any thoughts?
--Edit--
Bootloader screen says:
"KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8"
Bottom says: "Serial"
dude i am sorry to inform you but without an os back up is impossible
*just a thought - try removing SC Card and Sim Card and Remove Battery for some time then put everything back and try.. but most likely.. dont put lots of hope on this..
KyleK29 said:
I've got a weird one. Yesterday, my phone was running fine (I've had Dutty's rom on it for about 4months), I lost sound and needed a reboot. I rebooted and immediately got the RGBW bootloader screen. Successive reboots gave me this. I removed my flash card and tried again - was able to get in the O.S. but I still had no sound, so I rebooted again. Now I can't seem to get past the bootloader.
I'm probably going to try a reflash of the ROM, but I'm curious if there is another option since I'd rather not lose my data.
Any thoughts?
--Edit--
Bootloader screen says:
"KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8"
Bottom says: "Serial"
Click to expand...
Click to collapse
jahrami said:
dude i am sorry to inform you but without an os back up is impossible
*just a thought - try removing SC Card and Sim Card and Remove Battery for some time then put everything back and try.. but most likely.. dont put lots of hope on this..
Click to expand...
Click to collapse
Well, it's not a total loss. I have a backup of my settings from about 3 months ago and all my PIM data from 2 nights ago. I was just hoping to be able to recover most of it.
Thanks for the idea though, no luck. Here's hoping the new flash will work!
So I added the newest version of Dutty's - phone took it fine. I installed some apps, rebooted multiple times, worked for like 30minutes. Rebooted after installing one of the apps asked me to, and BLAM .. bootloader.
Would it be reasonable to assume that the ROM in this thing might be hosed?
Interesting I had the EXACT same issue yesterday with a the Default ATT ROM.. I was going to try Duttys since Its already wiped
Ransom342 said:
Interesting I had the EXACT same issue yesterday with a the Default ATT ROM.. I was going to try Duttys since Its already wiped
Click to expand...
Click to collapse
Yeah, mine seems to be fubar'd. I tried flashing Dutty's ROM again, it took the flash, rebooted, and immediately gave me the bootloader again with a blank image.
*edit*
Tried again with a different ROM. It got to the loading screen for the OS, as soon as I rebooted it went back to the bootloader with a blank OS.
Looks like my ROM is fubared. I think my warranty is up, or coming up very soon. Does HardSPL void it? Because I'd assume that is the only thing they can tell was done.
of course hard spl will void ur warranty but if u can revert to orgininal spl
http://forum.xda-developers.com/showthread.php?t=335568
KyleK29 said:
Does HardSPL void it? Because I'd assume that is the only thing they can tell was done.
Click to expand...
Click to collapse
Same issue - Semi Fix
Hi Kyle,
I started having the same exact problem three weeks ago (it is now Sep.18.2008). I've got no sound coming from my phone, and when I reboot I get the bootloader screen.
my FIX: Plug the phone into it's usb cable, and have it plugged into a source (computer, power jack, etc).
When I reset my phone with it plugged into the usb cable, it finds the rom and loads up perfectly. But when I reset without it, I get the bootloader. I still have not figured out why it is doing this. CAVEAT: this only works with my usb cable plugged into the power outlet of MY CAR. I know...it's weird...but that's what's working for me. When plugged into the computer I still only get the bootloader - it works in the car only. But I suggest you try your car, computer, and a wall outlet if you have one for usb and see what works for you. I find that I rarely reset my phone anyway, but it's just annoying when I do.
I hope this message hasn't found you too late :S Cheers
May anyone can help me ?
Kaiser 100 (TILT 8925) during Flashing, the battery was discharged. Now it does not join, the green light diode only burns at power ON attempt.
The computer defines it on USB as Flash device, but the driver from ActiveSynch do not approach.
How to restore it ?
What buttons for input in Flash mode (tricolor) ?
BR !
Ok, so today I tried to flash my Rom with the official att 6.1 rom from HTC. I got it to finally start flashing after about ten tries but when it reached about 13% it gave me an error 276 I think. I tried the recovery method suggested by removing the battery for 3 seconds and reseting the device but now my device isn't recognized in windows and I can't run the upgrade file anymore.
It just goes to the bootloader screen with "KAIS1*0" on the top, then "SPL-3.02.000" below that, and "CPLD-8" below that. At the very bottom it shows USB but my computer doesn't recognize the device. I've tried hard reseting it and it just goes back to the bootloader screen.
Is there any way I can get my Kaiser back or am I screwed?? All this waiting for 6.1 and now my phone is dead. What a load of crap.
Just re start the ruu and let it sit for a minute when that happens, it will start again by itself. Almost shat myself when it happened to me.
First of all, relax. Your phone is not bricked. Do a little looking around the forums and you will resolve this.
I am too lazy to search for him but is the 3.02 SPL compatible with the 6.1 ROM?
I can't restart the Ruu because I can't get a usb connection to my phone. The bootloader goes into usb mode but my computer does not see the phone. The Ruu says it cannot detect the phone either.
Isn't there a way this guy can re-flash using a MicroSD card?
MineralGray02K said:
Isn't there a way this guy can re-flash using a MicroSD card?
Click to expand...
Click to collapse
I'm not sure if the OEM SPL has the ability to flash from card like the Hard SPLs.
To test put the Carrier ROM (Download from the Wiki) on to the root of the MicroSD Card and call it KAISIMG.NBH. Turn on the Phone with the Camera Button Held Down. It should try and flash the ROM then. If that doesn't work, I have a thread and wiki page all about getting stuck on the bootloader, check my Sig for more info.
Hope this helps.
Dave
rodavery said:
Ok, so today I tried to flash my Rom with the official att 6.1 rom from HTC. I got it to finally start flashing after about ten tries but when it reached about 13% it gave me an error 276 I think. I tried the recovery method suggested by removing the battery for 3 seconds and reseting the device but now my device isn't recognized in windows and I can't run the upgrade file anymore.
It just goes to the bootloader screen with "KAIS1*0" on the top, then "SPL-3.02.000" below that, and "CPLD-8" below that. At the very bottom it shows USB but my computer doesn't recognize the device. I've tried hard reseting it and it just goes back to the bootloader screen.
Is there any way I can get my Kaiser back or am I screwed?? All this waiting for 6.1 and now my phone is dead. What a load of crap.
Click to expand...
Click to collapse
run this while phone is hooked up to computer stuck in bootloader.
Sweet Jesus
Ok, I tried the tri-color fix from nufsaid. It didn't work b/c it couldn't open a usb port or didn't see the phone or something. Then I tried putting the rom on my microSD card.
And *SHAZAM* there it was. DaveShaw you are a god to me now. It said the update was successful but I'm still stuck in the bootloader. It used to work if I would plug it into the wasll charger and reset it but that isn't working now. My computer still doesn't recognize it so Mtty or anything still doesn't work.
Ok, I left my tilt on the tri-color screen all night long to run down the battery. When I woke up I tried to power it on and I got the familiar ATT flash screen but when I plugged it into the AC power it went straight into the bootloader.
I don't know what's worse, bootloader or red light of death, I just experienced the red light, called att and got a new phone sent out in 12 hours! What SPL does your phone show? they might exchange if it's not 'voided'
ok, I finally got it to load the windows. If the battery has a high charge or is charging resetting won't get out of the bootloader. If I let the battery run down to almost nothing, wait a little while with it out, then try it again it will turn on. my spl is now 3.56.0000.
Finally
I finally got it out of the bootloader. I'm never going to reset my phone again. It's gonna suck if it freezes. Thanks for all the help.
rodavery said:
I finally got it out of the bootloader. I'm never going to reset my phone again. It's gonna suck if it freezes. Thanks for all the help.
Click to expand...
Click to collapse
Glad your back up and running. There are two new hard SPL's be cmonex (they are mentioned in the link in my sig) that make it less likley for you to get stuck at the bootloader. You could try those?
Ta
Dave
I've been waiting for hours for someone to help me and I searched and searched, I can't find any help!!! I have to go to work soon and I've been on this screen since 7:30AM EST!
Looks like I'm stuck at the boot loader screen and it goes back to it when I do a soft rest. I can't do a hard reset since I can't turn off the phone.
I think it's the bootloader screen.
Says RUUNBH on the top right corner and the screen is red, green, blue and white which these codes or whatever.
Took the battery out for a few and it went right back to that same screen.
Can someone help me bring back my Rhodium to stock???
EDIT: I might of posted this in the wrong section. Should this be in Rhodium General?
*UPDATE*
ark666 found the stock rom for T-Mobile HTC TP2 and I did a flash to get it back! Thank you so much ark666!!!
Flash stock rom.
I have no idea on how to do that, I searched how-to's but I can't find any full instructions or where to get the stock rom for T-Mobile HTC TP2.
This is the worse ever!!! Somebody please!!!
Isn't this the best site for things like this?
Try a manual hard reset? The instructions should be in your manual.
It says while the phone is off to HOLD SEND/END key with the power until the message comes up. The phone wont turn off unless I take out the battery for me to do a hard reset.
EDIT: I took the battery out then put it back in. The phone is now off, I hold the buttons and did the hard reset. It went right back to the boot loader screen.
hi,
what happend after you hard reset the device?
regards,
twisted
Asked me to press the VOL UP button to reboot. I did and it went right back to the boot loader screen. A flash happened on the screen when I try a soft reset and it says really quickly!..."NO IMG FILE" then it goes back to the 4 color screen.
EDIT: Image below on how my screen is since 7:30 AM EST!!!
on some device, active the RUU, connect it to PC & press soft reset button (the one in side the battery cover).
don't know if it help, just try that
good luck
Thanks for the reply, but that was the first thing I tried. Looks like I will have to go to work with no phone! This is crazy on how this can't be resolved.
Looks like you've basically erased the flash I'd say...
If you can get the t-mobile image, then try flashing that back to the device... If you connect a usb cable to your device, at the bottom, where it says serial it'll change to usb...
Or, if you have a goldcard, maybe try installing another image. But I'd say you're best to install the t-mobile image if you can get one?!
Ok so where can I get an image that will work on my phone? I also will need instructions on how to do it properly.
HeavyComponent said:
Ok so where can I get an image that will work on my phone? I also will need instructions on how to do it properly.
Click to expand...
Click to collapse
Where are you from? Can you find the rom on your tmobile site?
Or, creat a goldcard, copy the RHODIMG.nbh into the root of the card and try flashing that...?
As far as I know, your device is not bricked, you simply need your original supplier rom...
I replied to the PM (basically do set 16 0 command in mtty)
but I see your photo now - you have 0.85.1000 SPL? that's mfg SPL so if "set 16 0" did not help (you didn't describe what you did to the phone when this happened), you can just take any official rhodium ROM and flash it
sorry if I misread your photo... quite blurry
Ok that's my main problem that I've been having. Where can I get an official Rhodium ROM and how do I do a flash? I've been searching all morning.
And yes 0.85.1000, that's what it says on the screen.
I tried to this ROM...Link: http://forum.xda-developers.com/showthread.php?t=548546
Did the goldcard, but I think I did it wrong. I added the RHODIMG to the SD then tried to update my TP2. That's when I got an error saying it's not for PDA and how I need to update my utility.
I got the steps to do the goldcard correctly, I just want to take another shot at updating this ROM.
lovelldr said:
Looks like you've basically erased the flash I'd say...
If you can get the t-mobile image, then try flashing that back to the device... If you connect a usb cable to your device, at the bottom, where it says serial it'll change to usb...
Or, if you have a goldcard, maybe try installing another image. But I'd say you're best to install the t-mobile image if you can get one?!
Click to expand...
Click to collapse
hard reset doesn't erase the OS image.
HeavyComponent said:
Ok that's my main problem that I've been having. Where can I get an official Rhodium ROM and how do I do a flash? I've been searching all morning.
Click to expand...
Click to collapse
see my PM first, maybe set 16 0 will be enough.
is your SPL version really 0.85.1000? how did you get this phone? what happened when it got stuck on bootloader screen?
as for flashing, see xdadev wiki on rhodium.
Ok, will try what you PMed me. Brb!
It says 0.85.1000 on the screen so I guess so and I got it from T-Mobile. Ordered it through Customer Service.
post #15 has been updated to let you know what I was trying to do.
HeavyComponent said:
Ok, will try what you PMed me. Brb!
It says 0.85.1000 on the screen so I guess so and I got it from T-Mobile. Ordered it through Customer Service.
post #15 has been updated to let you know what I was trying to do.
Click to expand...
Click to collapse
then the set 16 0 will work just fine
weird the rom didn't work though
I have just flashed the 6.5 rom which you flashed
It does change the spl to 0.85 and i have the exact the sameimage which you have shotted during the flash process. But the process of this rom's flashing has two stage, it will restart after first 10% and show up the image which you shotted and upload, and continue afterwards. i guess ur goldcard has the problem so it stops and stucked there. Try other sign roms would be a better solution.