Related
For some reason I was having problems with activesync, so I uninstalled it and was going to start from scratch. Now every time I reset the phone, it brings me to the bootloader, and I cannot get out of it. It is the standard tri-color screen, and it shows:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
Serial
What the heck is going on here??? It has been working fine ever since I got it and flashed it a month ago. I have a Tilt flashed with the HTC shipped ROM. I was able to hard reset, but after the initial AT&T configuration and restart, bootloader again! HELP me please.
I'm new
I would start by going to the Hermes Wiki cuz they have a good how to unbrick my device section. I read somewhere that holding camera+power and soft resetting with the stylus might work. good luck
So it's bricked? I have done some searching and what I've discovered is that if I can see the bootloader screen than my device is NOT bricked? From what I've seen, bricked means that it is totally unresponsive, and no screens come up whatsoever. I'm confused. Also, how did this happen? The phone was working fine, and nothing has changed...?
All ready try again to flash with original rom?
You mean the Tilt ROM that came with the phone or the HTC shipped ROM that I originally flashed it to?
I really don't understand how this happened. Everything was working fine until today. I've been using this ROM for a month now with no problems.
I will try to re-flash the ROM tonight again - does anyone else have any ideas what might have caused this? Can someone explain to me what bricking is and why it happens? I'm not sure if that is what has happened or not, and I have no idea how to fix it.
More info:
For a split second before it shows the tri-color bootloader, I see a screen that says "No Image File!". It's very quick and I can barely make it out. Does that make any sense?
Also, I have no idea how to reflash since I can't get out of the bootloader screen, and certainly cannot get an activesync connection.
Guys, please help, I'm dyin here.
jackjohnson said:
Also, I have no idea how to reflash since I can't get out of the bootloader screen, and certainly cannot get an activesync connection.
Guys, please help, I'm dyin here.
Click to expand...
Click to collapse
I will try to help you. I'm pretty sure that one of the bootflag bits has flipped. You should connect with MTTY 1.42 (search forum) while your phone is in bootloader. Then type the command readconfig and copy/paste the output here.
Thank you so much jocky - I'm really indebted to you.
Output:
config itemDebugMethod
index0x0, value0x0
config itemKitlIP
index0x1, value0x0
config itemKitlNetMask
index0x2, value0x0
config itemDriverFlag
index0x3, value0x0
config itemDriverLocalZone
index0x4, value0x0
config itemDebugFlag
index0x5, value0x0
config itemPowerSavingDisable
index0x6, value0x0
config itemBootloaderFlags
index0x7, value0x0
config itemRadioDebugFlags
index0x8, value0x0
config itemDriverDisable
index0x9, value0x0
config itemFixedIdleTime
index0xA, value0x0
config itemApSwitch
index0xB, value0x0
config itemConfigDataFlag
index0xFF, value0x434F4E46
Hmm, all normal!
Are you sure the camera button isn't stuck?? Please check that.
Also while in bootloader mode type the command boot and report what happens.
Camera button is definitely not stuck. Seems fine.
Ok, I typed the boot command, and here's what I got:
Cmd>boot
Card inserted
Cmd5 CMD_TIMEOUT
SD 2.0 HC card
SD Init OK
SDFATChkConf: RhOpenFile() failed KAISCONF.txt
OEMIPLInit clear 10MB ext RAM
OEMGetUpdateMode
OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage crc of Mini-Kernel:0xC58C631E
OEMLaunchImage 80000000
Jump to Physical Address 10300000
and then it just hangs there...
Any ideas?
Well that's not good. After doing that, I end up on a solid white screen. Then it repeatedly goes to the bootloader screen, and keeps fading out to pink, then to white very slowly. Looks like the lcd is screwing up. All sorts of crazy colors. This is the craziest thing. After I unplug the usb cable, it just goes back to the bootloader again, and looks fine. What the heck is goin on here?
It looks like a bad flash. Something is checked by the bootloader and it decides to enter bootloader mode instead of booting WinCE kernel.
Have you removed both battery and usb cable? After doing that do a factory reset. I remember I've seen that pof wrote something about typing the boot command when the device is stuck in bootloader mode.
And which image did you flash in order to resolve it?
jockyw2001 said:
It looks like a bad flash. Something is checked by the bootloader and it decides to enter bootloader mode instead of booting WinCE kernel.
Have you removed both battery and usb cable? After doing that do a factory reset. I remember I've seen that pof wrote something about typing the boot command when the device is stuck in bootloader mode.
And which image did you flash in order to resolve it?
Click to expand...
Click to collapse
How could it be a bad flash though - this ROM has been working on my phone for the last month flawlessly? I flashed the stock HTC shipped ROM. It has been working great up until today.
Yea I've tried removing the battery and usb cable. But I can't do a factory reset from the bootloader screen - it just goes right back to the bootloader if I try to do a hard reset. Should I reflash, and if so, how do I do it from the bootloader screen without activesync?
This is really not good. Thank you for all of your help btw.
jackjohnson said:
Should I reflash, and if so, how do I do it from the bootloader screen without activesync?
Click to expand...
Click to collapse
That's easy. Download a ROM from here and run the executable KaiserCustomRUU.exe. That should do the trick. Try and report.
So, if I run KaiserCustomRUU.exe, it will allow me to flash a ROM even though I'm stuck in bootloader? I will give that a try if that's the case. I'll be home in less than an hour to try. I'll report back. Thanks.
Yes, no problem. I've got to leave too, catch u later. Good luck!
Re-flash finished successfully, but I'm still stuck at the same bootloader screen afterwards. Ran the boot command from mtty again, and got something different:
Cmd>boot
Fill RSVD information for block 288 to 309
Storage start sector=0x99C0, total sector=0x11900
Storage start block=636, total block=1124
Total Bad Block in CE: 0
Erase physical block from 924 to 2032
formatstorage Bad block found: 1242
si backup: Erase physical block from 2032 to 2048
Do I have bad internal memory?
Another update. After that lockup, I decided to run the boot command from mtty a second time, and got something different yet again:
*****
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0x99C0, total sector=0x11900
Storage start block=636, total block=1124
Total Bad Block in CE: 0
Erase physical block from 924 to 2032
formatstorage Bad block found: 1242
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
*****
So, it looks like it found and fixed bad blocks? Is that possible?
After this, the OS booted and HTC customizations began installing. When it restarted, I was locked at the bootloader screen again. I ran mtty one more time, and ran boot command again
*****
Cmd>boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
*****
This time I didn't get any errors about bad blocks. So it looks good right? Well, not exactly. It appears I cannot boot unless I run mtty and run the boot command. After it boots, everything seems fine.
Does anyone have any ideas why I can boot through mtty but not through a soft reset?
jackjohnson said:
Does anyone have any ideas why I can boot through mtty but not through a soft reset?
Click to expand...
Click to collapse
Once you're booted into the OS, please check your camera key again. Does the camera start after a gentle click?
Hi!
I need some help. When I reset (soft reset, turn off, hard reset) my Kaiser goes to bootloader screen. The only way to "wake" it is using mtty with "boot" command.
Information on bootloader screen:
KAIS130 MFG
SPL-1.0OliPof
CPLD-8
Serial
And in mtty:
"boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
UserStorageSIPreload --
OSSIReadBack --
OEMIPLInit clear 10MB ext RAM
OEMGetUpdateMode
OEMTranslateBaseAddress 23 80000000 80000000
IPLMSG:0x8:INFO: Loading image ...
IPLMSG:0x9:INFO: Jumping to image...
OEMLaunchImage crc of Mini-Kernel:0xC450BC22
OEMLaunchImage 80000000
Jump to Physical Address 10300000"
Can someone help me?
Thanks!
Try to flash any cooked ROM again....
Cheers
After you run the boot command to restore it, you may need to run HardSPL again to stop it from going into bootloader after every soft reset.
Maybe:
flash original HTC shipped ROM, flash HardSPL and then custom ROM.
This should fix your problem.
hi
Thanks fellows!!
I just tried to flash original HTC shipped ROM, flash HardSPL and then original HTC again. It works for 2 weeks, then the problem is back.
Could you tell a good custom ROM ?
Thanks again!!!
marcelo-cps said:
Thanks fellows!!
I just tried to flash original HTC shipped ROM, flash HardSPL and then original HTC again. It works for 2 weeks, then the problem is back.
Could you tell a good custom ROM ?
Thanks again!!!
Click to expand...
Click to collapse
if you flash original HTC rom, HardSPL changes are gone. again:
1. Flash HTC original ROM
2. flash HardSPL
3. flash CUSTOM ROM not the original one
It works great
Suggestion for a good rom depends on your needs, but try starting with Q-Mobile v1.2 (closest to the original shipped ROM with nice tweaks)
The Activesync does not sync whit Kaiser. The only way I can flash a ROM is starting flash with another Kaiser and change the USB cable when the first on start to flash.
After that, every thing is Ok and i flash the ROM. When Kaiser reset, the bootloader screen back.
In mtty:
"boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0x94C0, total sector=0x11E00
Storage start block=616, total block=1144
Total Bad Block in CE: 0
Erase physical block from 904 to 2032
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++"
Thanks!!
i had to reload the ATT bootloader and send the unit back. i was never able to fix the problem. got a new kaiser, loaded the HardSPL, loaded the same rom and no problems.
i believe its a hardware problem but i'm not expert. that was just my experience.
did it say serial?
I am experienceing a similair problem
sometimes well actaully nearly everyday after nightly charge the audio won't go trough my extusb headset. when I reset I get same 3colored screen with "serial" connection :|
when I plug the headset back in and reset (leaving the headset in) it will go past the 3color screen and boot to wm
and direct the audio trough the headset again.
however when I pull the headset out before wm is loaded it will still have the same problem.
any news?
i'm didn't solve my problem yet...
are you flashing the whole shipped .exe? if so that includes a SPL messing everything up when you do that. flash a shipped rom then hardspl your device then flash just a OS.nb make sure there is no SPL
all,
as in the first post, my kaiser goes to 3 colors boot loader after turning off or any reset.
Nobody seems not reply this thread for more 3 months.
So I guess it is fix.
Can you someone give the feedback ? and maybe confirm the solution ?
thanks a lot.
cheers
Andre
No response so far
So should I conclude that nobody is bother anymore by this issue?
For those interested, I found a way to force the correct boot:
1. remove the battery
2. plug the usb (including extension usb cable)
3. put back the battery
4. start
Then you'll be happy
cheers
Andre
P.S: issues can happen with HardSPL 1 and 3.26
Hi to all,
I have an AT&T TILT HTC 8925,
ROM: 1.57.502.2
RADIO: 1.27.12.11
VE: 22.45.88.07H
Installed the kaiser-HardSPLv1 with no problems.
After this I Flashed (via USB) Q-Mobile_v1.2 ROM, that went perfect. Made a soft reset and then a Hard Reset after this I configured the phone.
After everything was working I made a Radio flash with KAIS Radio Only 1.27.12.17 CustomRUU, all seemed normal until it got to 95%, it suddenly interrupted the update (error 262), and took me to recovery dialog 1-4 steps which I did.
From that moment until know I get the tricolor screen with the following text:
RUUNBHKAIS 1*0
SPL-1.56.0000
CPLD-8
USB
Click to expand...
Click to collapse
And when I try to flash ANY ROM, It gets past the tricolor screen, to a white screen with a percentage bar that gets to 0%, after a minute or so the customRUU screen goes to error 262 and I get to the recovery screen, etc...
I run on WinXP SP2, and have already tried several roms with the same result, with the exception of original ATT RUU_Kaiser_CINGULAR_WWE_.exe, it then gets to 1% and displays error code 294 Invalid Vendor ID.
When I tried the MicroSD method with the rom it gets to the tricolor then the "Loading..." screen, and keeps there (I waited for about 30 min)...
There was no SIM or MicroSD card on the phone at the moment of flashing, and I did dump the original ROM to the 4 raw parts as per instructions.
I live waaay out of the countries with AT&T or HTC servicing routes, so I am stuck with it until I fix it, which I know I can do, and to be honest with myself, can't afford to waste the money spent on this thing.
Until now the best similar thing I found about this was with the hermes unbrick phone thread, and I am not sure this works on the KAISER, but to be honest, I get cold sweats to use any more procedures (without reconfirmation) on this as I have a phone that at least still shows "some" signs of life.
After reading days of threads (my eyes are burning) I know the knowledge is within this site, but I need guidance since I am new to this thing (smartphone flashing) although familiar with computers.
Any kind of help will be very appreciated and valued.
Best Regards.
----------------------
As an update, I solved this thing. Thanks for your help.
After seeing that there was some sort of problem with the boot mode screen not showing the kaiser-HardSPL data, I went in that direction. After some suggestions and much trying I decided to download all / any original roms I found in here for my phone (ATT Tilt) then I worked my way from top to bottom based on the versions of the radio.
The one that solved my problem was 1.5.502.3 Radio 1.27.12.11 although strangely it shows on my phone after the successful flashing. 1.5.502.1
Just out of curiosity I went and installed again kaiser-HardSPLv1 and it gets to this text on tricolor screen:
Kais1*0
SPL-.JumpSPL
CPLD-8
Doing a hard reboot (camera button + soft reset) gives me a different screen:
Kais1*0
SPL - 1.56.0000
CPLD-8
Really don't know if this is normal, and after flashing a cooked rom I had to reinstall it (kaiser-HardSPL).
I have now reflashed QMobile rom and have no problems. Although I didn't flashed again new radios
For flashing the Original rom I did make sure of the following steps in addition to normal ones (Just in case)
1) Disconnected fisically from LAN (Unplugged LAN Cable)
2) Disabled all firewall protections
3) Disabled all antivirus and spyware protections
4) Run RUU original files
5) Pray
Thanks again people
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
I just tried it again (See I am not so scared anymore), and received the same results (Radio upgrade fails on 95%).
I have burned the original ROM back and all is well again!
I also can't get past the same screen and try as I might Activesync won't recognise the phone. When going through the recovery process on Kaiser Custom RUU it says its recovered but then when trying to go through the update it sticks on 0% and then says there are communication problems etc.
On the tricloloured screen it says
KAIS130
SPL-1.81.0000
CPLD-8
Will a hard reset do anything?
Any help much appreciated.
Bump
Now managed to boot via MTTY but power off etc returns me to bootloader screen
Looks to me like you guys have had problems flashing hardspl. Your tri-colour screen should have:
KAIS130 MFG (or Kais 120 etc)
SPL-1.0OliPof
CPLD-8
I don't know about the CPLD number but you MUST have the OliPof SPL. Check this after running hardSPL to make sure that it's there before flashing another ROM.
If you have this but still get trouble flashing, try going to the tri-colour screen and then run the kaiser_RUU.exe to upgrade.
http://forum.xda-developers.com/sho...ked. (One without a radio)
- Flash a radio...
i had the same thing with my MDA Vario 3,but with no success finding the original ROM, since I`m from a small country. I`ve tried to reboot to normal screen via MTTY but it gives me the error: Command error . So - now I`m left with two options: to dump and reconstruct an original ROM from the same type of phone or to find what`s wrong with MTTY.
Anyone had a similar problem, I mean with MTTY and command error???
yes, i`ve searched trough the posts regarding this problem but I didn`t find any saying that MTTY gave this error.
any idea?
THX in advance!
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Martinhdk said:
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Click to expand...
Click to collapse
if you`re reffering to my problem-how can I copy the JumpSPL1.56-KAIS.exe file and execute it from the phone if I can`t boot it normaly,it always stays in tri-color boot screen?
actually, I`ve bricked my phone with that HardSPL procedure.It was the first step for unlocking. I`ve copied the JumpSPL1.56-KAIS.exe file, executed it and then rebooted and tried to flash with the modified ROM from the jockyw2001`s unlocker. it stopped at 95% and now it seems that it is still CID locked and bricked in boot mode. i`ve already said what MTTY gives as an error.
any idea what may be the problem?
like always:the problem is in RTFM
while i was working on my Kaiser i was doing lots of other things on other computers so i`ve skipped the step with flashing the HardSPL,that`s why all went wrong now,as i`m at home i have more time to read the posts and i`ll try with the jockyw2001`s procedure from the MTTY, with the task8 command.
hope it will help,unless the only solution is to dump the same ROM....
i`ll higly apreciate if anyone has a different solution....
will post results
The problem is that I can't flash the phone with anything be that HardSPL or the original Orange ROM or whatever you care to mention because the PC can't communicate with the device via the USB cable after Activesync ceases to operate. As such everything works up until the % progress bars come on both screens and then they stay at 0% before the communication error message appears.
Funny thing is that the phone is communicating with the PC as USB/Serial alternate depending on whether the cable is plugged in or not and the PC recognises the USB device when its plugged in and when Activesync isn't controlling the situation.
I've been stuck like this with a Hermes but not the Kaiser (yet). As far as I'm aware, you don't need activesync running to run a rom upgrade. If you are in bootloader mode (tricolour screen) you can run the upgrade directly with activesync not connected. If hardspl isn't installed then you should flash the original rom, and if you're unlocked then any rom should do.
Also it might be worth trying the SD card method for flashing. But either way I'd use the original rom and then when you get the phone working again keep trying with HardSPL until it's successful - don't flash any other roms without it.
Laubscherc said:
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
Click to expand...
Click to collapse
Thanks for your help.
I did try other "original" rom I got in here http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
The version corresponding my rom is (1.57.502.2 (radio 1.27.12.11)), however I got the error code 294 Invalid Vendor ID after 1%.
I did try the ftp address you mentioned, but I can't login neither anonymously nor with user & psw for xda-developers.
I would like to try the rom you are referring to, please give me another link to download the file.
Best Regards.
Martinhdk said:
http://forum.xda-developers.com/sho...ardware devices list.
Thanks for your help.:)
Click to expand...
Click to collapse
Stuck in Tri color screen
I have been fighting the same issue for several days. Radio gets to 95% and errors. Then hung up in tri color screen. I used MTTY - "set 14 0" command then "boot" command inMTTY to get the phone to boot. I have had to do this a number of times, sometimes more than once per incident. Hope it works for you too. P.S. once you have a successful flash the phone returns to normal operation until then it will go back to tri color screen on reset. I just flashed a startup splash screen to get mine back to normal.
pennco can you expand in further detail on what you actually did with MTTY cause I have the EXACT same problem....
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
boot command from mtty reads:
Cmd>boot
InitDisplay: Display_Chip=1
Fill RSVD information for block 288 to 309
Storage start sector=0xAB80, total sector=0x10740
Storage start block=707, total block=1053
Total Bad Block in CE: 0
Erase physical block from 995 to 2032
formatstorage Bad block found: 1045
si backup: Erase physical block from 2032 to 2048
No card inserted
OSSIPreLoad ++
Try this
Try flashing this ROM and see what happens.
http://www.4shared.com/file/3857459...ULAR_WWE_157_-_Originaly_Shipped_ATT_ROM.html
What does your bootloader screen show?
Please Help!
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Threads merged.
Metzex08 said:
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Some people go to far ahead before figuring out the real issue. Don't **** yourself.
Hold down your power, camera, and insert your stylus then tell us what your bootloader screen displays.
Metzex08 said:
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Click to expand...
Click to collapse
ok post was moved from another thread. sorry. It appears that you do have hardspl installed.
Metzex08 said:
Okay. I tried to flash the OEM rom back to my ATT Tilt. While doing this, somehow my phone entered an unending cycle of soft resets. I can still get to the bootloader, but as soon as I flash a rom, it tries to boot, gets to the first boot screen, then resets. My computer keeps popping up "install drivers for new hardware found".
I tried booting through MTTY, no dice.
My bootloader screen reads:
KAIS1*0 MFG
SPL-1.0.01OliPof
CPLD-8
I tried flashing hardspl. RUU opens and it runs instantly. The phone reboots and the boot loader screen still reads this. I flash a new rom, the bootloader still reads this. I'm at a loss. I've been working on this for 3 hours and I haven't gotten anywhere. I don't have a backup phone, so I have to figure this problem out. I have searched the forums and haven't found anyone with the same problem. Please, anyone who feels they can help, let me know what I can try to fix this problem. Thanks!
Click to expand...
Click to collapse
and your bootloader screen will not change because it does not display the rom version. You have hardspl installed what more do you want?
Did you believe your bootloader screen would change after you flashed a rom?
Damn!!!
Metzex08 said:
Ok, So I had dutty's rom running perfect for about 5 months. Decided I wanted to revert back to the stock ATT rom and play with it. I tried to revert and somewhere along the way, I did a soft reset and it screwed me up. I can still flash roms no problem, but for some reason, when the phone goes to start up, it gets to the first screen of the boot process (white with ATT logo) and then it freezes. After about 10-15 seconds, it automatically soft resets and tries again. So, I can hit the reset button while holding cam and pwr to get to the bootloader. I have tried flashing every rom I have downloaded, and nothing seems to work. I am trying the stock ATT rom as I type this but we will see what happens. That is what I was running when it F'd. I wanted to restore it to stock completely, thought about trying to have it replaced because the hinge is really loose on my handset. Anyway, any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Dude it has been five months since you flashed a rom why bother getting all neurotic and worried For a common situation? I complained to mods because they closed your thread now I look like a douche bag. Thanks.
I had the same problem (continuous reboot) as before, see this thread:
http://forum.xda-developers.com/showthread.php?t=383678
but the problem that I had is because of bad blocks, post your info 8 and maybe I can help
ok, I got the phone to startup, eventually it stopped trying to soft reset. I hit the power button and it turned on. Now, I run jumpspl and it doesn't ever bring up the USB connection, so I can't change the bootloader back to oem. any suggestions?
I used the other version of jumpspl (1.56) and it brought up the USB connection (atleast it says it did). But, when I try to run RUU from the ATT_SPL folder it cannot connect to my phone. MTTY says USB connection is unavailable as well. What should I do?! I want the phone to be able to be sent in for warranty replacement as the hinge seems to keep getting looser and looser. Any ideas? Bootloader still reads the same as before.
Metzex08 said:
I used the other version of jumpspl (1.56) and it brought up the USB connection (atleast it says it did). But, when I try to run RUU from the ATT_SPL folder it cannot connect to my phone. MTTY says USB connection is unavailable as well. What should I do?! I want the phone to be able to be sent in for warranty replacement as the hinge seems to keep getting looser and looser. Any ideas? Bootloader still reads the same as before.
Click to expand...
Click to collapse
If your sending it for warranty replacement via AT&T just put it in the microwave for 2 seconds....problem solved.
I had a StockSpl on my Htc touch pro and I wanted to flash an unsigned Hard-SPL from my MicroSD because I wasn't home and I didn't have the USB cable. After the screen loaded 100% the device restarted I took off the MicroSD and now it keep showing this tri-color screen:
RUUNBH
RAPH100
SPL-1.90.000
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36
Upgrade ROM code error
Please try again
Serial.
(I've also attached a picture)
If i try to flash again from MicroSD the same HSPL it loads until 100% then restart and start to load again until i get the MicroSD card off. Or if i try to flash other StackSPL or any other ROM it stays on Loading on a grey screen.
After I went home I tried to flash the HSPL again from my computer using the USB cable, it start to load 0% then it does nothing. I've tried to flash StockSpl and other ROMs from the computer too but it does the same.
I think i've tried anything but nothing seems to work ... if someone can help me pls ... i've searched the entire forum and there's someone that had almost the same problem here: http://forum.xda-developers.com/showthread.php?t=566796
but noone had any solutions.
You can't flash hard spl off your sd card; it's got to be done through a usb cable.
Just read through the hard spl thread; it's long, but your situation has probably been addressed. I did it almost 3 years ago, so I don't remember the tricks. That's the case with most posters, I'm afraid. Just read the thread.
can u pls tell me which thread?
this one?: http://forum.xda-developers.com/showthread.php?t=410150
or this one?: http://forum.xda-developers.com/showthread.php?t=448008
Either, but read the first one. You can also look in the unlocker thread. Hell, you may just want to buy the unlocker and run that. It will flash hard spl, and the directions may be better.
I just hope they aren't trying to HSPL(hard SPL) a CDMA device :S I've made the mistake to assume the person that was posting in this forum had a GSM device and they really screwed up after a third attempt at flashing HSPL!
Usually if I have a difficult time flashing my Fuze or TP(both GSM), I remove everything to include the battery, connect the USB to an available USB port on the computer then hold the volume down key while connecting the device to the USB cable. Probably not the most friendly way but it certainly will tell you if there is a problem with your USB port/cable or even device!
My htc raphael is GSM
I've tried to hold the volume down button but it's always the same
There's no problem with the cable just that I can't flash anything because I'm stuck with a stock-spl and I can't flash a hard-spl either. When I try to flash something from the computer it starts to flashing with 0% then nothing happends until the RUU gives me the 262 Error. And when i try to flash from my mSD it just stuck with a Loading screen.
Xadow said:
I had a StockSpl on my Htc touch pro and I wanted to flash an unsigned Hard-SPL from my MicroSD because I wasn't home and I didn't have the USB cable. After the screen loaded 100% the device restarted I took off the MicroSD and now it keep showing this tri-color screen:
RUUNBH
RAPH100
SPL-1.90.000
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36
Upgrade ROM code error
Please try again
Serial.
(I've also attached a picture)
If i try to flash again from MicroSD the same HSPL it loads until 100% then restart and start to load again until i get the MicroSD card off. Or if i try to flash other StackSPL or any other ROM it stays on Loading on a grey screen.
After I went home I tried to flash the HSPL again from my computer using the USB cable, it start to load 0% then it does nothing. I've tried to flash StockSpl and other ROMs from the computer too but it does the same.
I think i've tried anything but nothing seems to work ... if someone can help me pls ... i've searched the entire forum and there's someone that had almost the same problem here: http://forum.xda-developers.com/showthread.php?t=566796
but noone had any solutions.
Click to expand...
Click to collapse
Naughty Naughty..
I guess you realise now that you should ALWAYS read read read before modifying your phone in any way.
What EXACT file did you originally flash to your phone via microsd card and where did you get it from?
If you go into the bootloader screen and then connect the usb cable does it show "usb" at the bottom of the screen?
PLEASE STOP TRYING TO FLASH HARDSPL FROM MICROSD AS YOU CANT DO IT. If you could then it would be in my guide..
Mark.
mskip said:
Naughty Naughty..
I guess you realise now that you should ALWAYS read read read before modifying your phone in any way.
What EXACT file did you originally flash to your phone via microsd card and where did you get it from?
If you go into the bootloader screen and then connect the usb cable does it show "usb" at the bottom of the screen?
PLEASE STOP TRYING TO FLASH HARDSPL FROM MICROSD AS YOU CANT DO IT. If you could then it would be in my guide..
Mark.
Click to expand...
Click to collapse
Thanks for replying
Yes ... I did read the part with the SD flashing but i thought it's not a bit deal to flash from mSD since the flashing via activesync is so easy.
Well ... i extracted the RUU_Signed.nbh from the Hard-SPL found HERE and i copied it to the mSD (MicroSD) and renamed it RAPHIMG.nbh.
I restarted my phone holding the volume down button and it started to load until 100% then it restarted and showed the bootloader screen and after a couple of seconds start to flash the HSPL again so after it completed 2 or 3 times of flashing and restarted i took the battery and the mSD off (I DIDN'T TOOK THE BATTERY WHILE IT WAS IN THE PROCESS OF FLASHING). And when i started the phone again without mSD it showed the bootloader screen like it was waiting to get a .nbh file on mSD to start flashing again.
No matter what i do my phone start in bootloader and down it shows "Serial". If i connect the usb it shows "USB".
I tryed to do a hard reset and it seem to work but after it finish and the phone restarts is stuck with the same tri-colour screen.
Sry for trouble and thx again
I guess I missed the part in the OP where you said it was stuck in bootloader. That's not good. I would try flashing the stock raphael rom (assuming you have it). Have you tried that? I dunno, you may be stuck for good.
Xadow said:
Thanks for replying
Yes ... I did read the part with the SD flashing but i thought it's not a bit deal to flash from mSD since the flashing via activesync is so easy.
Well ... i extracted the RUU_Signed.nbh from the Hard-SPL found HERE and i copied it to the mSD (MicroSD) and renamed it RAPHIMG.nbh.
I restarted my phone holding the volume down button and it started to load until 100% then it restarted and showed the bootloader screen and after a couple of seconds start to flash the HSPL again so after it completed 2 or 3 times of flashing and restarted i took the battery and the mSD off (I DIDN'T TOOK THE BATTERY WHILE IT WAS IN THE PROCESS OF FLASHING). And when i started the phone again without mSD it showed the bootloader screen like it was waiting to get a .nbh file on mSD to start flashing again.
No matter what i do my phone start in bootloader and down it shows "Serial". If i connect the usb it shows "USB".
I tryed to do a hard reset and it seem to work but after it finish and the phone restarts is stuck with the same tri-colour screen.
Sry for trouble and thx again
Click to expand...
Click to collapse
As Farmer Ted said your best bet now is to download your ORIGINAL Rom (from your provider) and flash it from your pc with the usb cable attached. The phone had to be in SSPL mode before running the RUU which is why everything was packed in a single exe. You may have corrupted your SPL in which case you have bricked your phone but if you can manage to flash a Stock Rom then the Stock SPL should be reflashed and you can start again with the HardSPL by following the CORRECT instructions and not making up your own lol.
Good luck.
Mark.
When i bought my phone, the first thing i did was to dump the rom. So now i rebuild it from raw and tried to flash but it didn't work so i went to Orange site and i downloaded the official ROM then started to flash and ... IT WORKS
I think that the ROM was corrupted not the SPL, and since the SPL was stock it didn't allow me to flash other ROMs other then the official
Thanks for all guys I couldn't done this without your help
P.S: why did it allowed me to flash the official rom but the hspl not?
It didn't flash the hard spl because you did it all wrong; those rebuilt roms aren't exactly the same as the stock roms, so it's not surprising that wouldn't flash. Good job finding the original shipped one, though.
Now, just read mskip's instructions and you should be good to go. I think the trick is just to enter bootloader, then connect to your pc through the usb cable.