Related
I've been running a ROM I built from the consolidated kitchen this weekend without any problems. Today I updated the radio to 2.69.11 from the cingular 2.25.11. After the flash the phone froze on the windows mobile screen. After some time I tried to reset the phone and it froze again, a few more tries and it finally boots up. I didn't pull the memory card when I flashed and thought that might have been the problem so I flashed again even though the phone was showing 2.69.11. I don't remember everything after that but it wouldn't boot up and I have tried flashing the original Cingluar ROM & T-mobil 2.26 without any luck.
The phone is stuck in bootloader now and is getting a error code 302 I think it's because the phone doesn't stay on when the USB cable is attached. It gets to about 15% and the phone resets and the error 302 pops up. When connected and not trying to update the phone turns on and off in the bootloader screen. I have pulled the battery, rebooted the laptop, tried using mtty,and pulled the sim. I thought the original problem might have been because I flashed at 52% battery. I put a older battery in after that appeared to have a good charge. Right now I put the phone on charge with the newer battery to see if this helps. I am not sure if it is charging because the orange light is not on, I can't get the phone to stay turned off when plugged into the charger and the bootloader screen is on.
And yes I have been searching for hours for a solution to this problem.
Also looking for a post I read about doing a master reset, I have tried holding the 2 soft keys when turning on, didn't help.
I think this says it all I have tried everything, does anyone anything else to try?
Thanks
UPDATE: went out for a few beers and some food. Not sure it the battery charged (bootloader screen on the whole time it was plugged into the charger)
Tried flashing again with cingular ROM, got about 20% and phone shut off and turned on again in bootloader. Flash gave 302 error again. Tried again and phone reset (on and off) every 5 seconds when connected to laptop with USB.
I'm hopping someone out there has a answer for this problem.
Back from the dead HALLAULA!!!!
This morning I spent more hours searching still didn't out find anything.
I tried mtty again and noticed that I never got to the screen that shows USB>
to enter the command "set 14 0"
I came up with a thought and this is what I did. Created a new ROM, OS only. Thinking it will load faster than any other ROM. It reached 100% in 3 minuets the whole I'm coaching come on baby don't restart and than going (don't know how to explain the feeling) waiting the next 2 minuets to get to finished. But it got there booted fine. I don't know why it stayed on this time and didn't restart, maybe having the battery out all night had something to do with it. After I flashed the Cingular ROM than the original I created and lastly Radio 2.69.11
I hope this helps someone in the future,
i need your help
hi man I had a prophet s200 and give me the same error 302 but, with the diference in my case got 98% adn then stuck in boot screem, please help me if you can...and sorry for my english
Guys,
It may help checking out this thread!
http://forum.xda-developers.com/showthread.php?t=294107
Can you help me out?
How did you create a new ROM - OS only? I'm having the same problem..can you walk me through this?
Thanks
How did you create another ROM (Operating System only)? I'm having the same problem and I have tried for the past 2 weeks - but no luck. Can you walk me through it?
Thanks
I used the consolidated kitchen (sticky at the top of this forum)
Uncheck everything on Build OS.
My problems started from a version of battery status that caused the original problem and not having enough of a charge on my battery.
Make sure you are CID unlocked (if you have a G3) and your battery is charged.
Umm, you can't uncheck everything in build OS or you will have problems, especially if you don't check a tuchflo or non touch flo dll or choose a commanager and probably a few others things. I don't have build OS up in front of me to check. The whole point to this msg is that you can check everything in build OS (besides the ones that say choose only 1) and it will build an OS only rom for you. That's the whole point behind build OS.
You are correct, I was kind of going from memory since I had built the striped down ROM awhile ago.
Greetings,
Im getting a really odd problem with my kaiser. I turned it off yesterday nad connected the charger... the cellphone turned on, but showed me that screen that appears when we are flashing it (4 horizontal bars, red, green, blue, white)... (!!!)
Inside the red bar, I can read:
KAIS130 MFG
SPL-1.0.OlipPof
CPLD-8
Inside the white bar:
Serial
Funny thing is, the phone won´t turn off, I have to remove the battery. After leaving it without the battery for 60 to 120 seconds, I placed the battery again and turned it on... and it booted normally.
Now, most of the time it will boot into the color bars. Any ideas about what is going on ?? Please help... can´t use the phone!
Same thing.....sort of.
I had the same behavior on my Tilt for a while. I did find that if I plugged a usb cable into the phone, or put pressure on the USB port while booting, it would boot normally. It did this for about a week and then started booting normally all the time. The only thing I can think of that I changed that week was upgrading the radio. I upgraded to the 1.64.08.21 radio.
The screen you are seeing is the boot loader screen. When it comes on, does it flash a message real quickly that says something like "image file not found"? That is what mine was doing.
You may also want to check out this thread. http://forum.xda-developers.com/showthread.php?t=344402
StealthNet said:
Greetings,
Im getting a really odd problem with my kaiser. I turned it off yesterday nad connected the charger... the cellphone turned on, but showed me that screen that appears when we are flashing it (4 horizontal bars, red, green, blue, white)... (!!!)
Inside the red bar, I can read:
KAIS130 MFG
SPL-1.0.OlipPof
CPLD-8
Inside the white bar:
Serial
Funny thing is, the phone won´t turn off, I have to remove the battery. After leaving it without the battery for 60 to 120 seconds, I placed the battery again and turned it on... and it booted normally.
Now, most of the time it will boot into the color bars. Any ideas about what is going on ?? Please help... can´t use the phone!
Click to expand...
Click to collapse
You probably have a messed up bootloader, you can fix it. I had this last week. Check the stickys above. The key program to fix it is mtty, make sure read a lot about it.
check the "Flashing your device section"
http://wiki.xda-developers.com/index.php?pagename=KaiserFAQ
that should help
Well... I tried using mtty, but it won´t work. I suppose it will work only on Windows XP machines right ?
I tried in two machines (Vista 64 and Vista 32) wihtout luck.
I tried reverting the ROM back to OEM, including the bootloader. I successfully flashed this one, but Im still getting the 3 color bootloader.
Thing is, it still reads the same
Inside the red bar, I can read:
KAIS130 MFG
SPL-1.0.OlipPof
CPLD-8
Inside the white bar:
Serial
After reading the forums, I found out that I´ll get out of this problem by using MTTY, and that I should simply issue a " boot" command.
Is that right ?
If so, my only problem now is to get a Windows XP machine... because I can´t get MTTY to show an USB option to connect to. Already tried configuring activesync, killing the processes, without success.
Ideas ?
StealthNet said:
Well... I tried using mtty, but it won´t work. I suppose it will work only on Windows XP machines right ?
I tried in two machines (Vista 64 and Vista 32) wihtout luck.
I tried reverting the ROM back to OEM, including the bootloader. I successfully flashed this one, but Im still getting the 3 color bootloader.
Thing is, it still reads the same
Inside the red bar, I can read:
KAIS130 MFG
SPL-1.0.OlipPof
CPLD-8
Inside the white bar:
Serial
After reading the forums, I found out that I´ll get out of this problem by using MTTY, and that I should simply issue a " boot" command.
Is that right ?
If so, my only problem now is to get a Windows XP machine... because I can´t get MTTY to show an USB option to connect to. Already tried configuring activesync, killing the processes, without success.
Ideas ?
Click to expand...
Click to collapse
Yea, you are right, only works on XP. I couldn't get it to work on my Vista Box, had to use my gf XP laptop. goodluck, you should be fine once you find one.
Ok,,, not starting to get worried.
Connected to a MTTY, issued the boot command.
Received this as an outpout:
Cmd>boot
Fill RSVD information for block 288 to 309
Storage start sector=0xA680, total sector=0x10C40
Storage start block=687, total block=1073
Total Bad Block in CE: 0
Erase physical block from 975 to 2032
formatstorage Bad block found: 1658
formatstorage Bad block found: 1659
formatstorage Bad block found: 1918
si backup: Erase physical block from 2032 to 2048
No card inserted
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:0x7EB8DBEB
OEMLaunchImage 80000000
Jump to Physical Address 10300000
Now it boots, the bootloader screen appears rapidly, and it fades to white...
... removed the USB cable, the device turned off. Connected it again and the bootloader appeared again.
Any ideas ?
Since I successfully flashed the way in to the default OEM ROM, and I think my problem is related to the bootloader, I tried flashing HardSPL 3.56.
It flashed, rebooted, and booted nicely into WM 6.1 (default version out from this ROM).
The first automatic customization happened as it was supposed to... and it rebooted... into bootloader argh!!
Removed the battery, waited 120 seconds, boot the phone. Working so far. Now, it has a 50%/50% of getting a bootloader or booting correctly.
Any other ideas ?? Man, tell me about a strange thing...
Since there are more with the same problem, but they are discussing it in another thread from L26, I think it's ok to auto moderate this one
Just to point out that the problem is solved (I think) - read here -> http://forum.xda-developers.com/showthread.php?p=2415437#post2415437
I have an at&t Tilt. I am having a problem with the device automatically powering off during the Windows screen while loading.
To get to where I am at:
1. I followed the instruction to install the HardSPL from HERE. On my bootloader screen, I see:
KAIS1*0 MFG
SPL-1.0.OliPof
CPLD-8
2. Then I did the Sim Unlocker procedures found HERE. After completing step 5, the device rebooted, the AT&T icon displayed, then the screen goes blank and stayed that way.
3. I found the fix for the black screen problem HERE. It was a radio problem, and I needed to update the radio to a compatable radio.
4. My phone worked fine for a day. The next day, my phone just died and when I rebooted, it said critically low battery. After I tried to charge it overnight (with AC adapter charger), it was still critical low battery. Then I tried USB charger for the day, still critical low battery. I figured it was a SPL-Radio conflict.
5. Then it stops getting into Windows altogether. It will power off at the Windows loading screen. I let it charge all day. I suppose that the battery is not dead because it is able to stay on the Tri-Color screen without being plugged in, and it always turns off at the same exact point while loading Windows.
6. I still can get to the tricolor screen. I can see USB when plugged and serial when unplugged.
7. I can flash ROMS, and I will even see the different Windows loading screens (Dutty's screens are different than the AT&T green Windows screens.) I have tried original AT&T and cooked WM6.0 Roms/Radios, WM6.1 Roms/Radios. It still keeps rebooting at the Windows loading screen. I tried the original and cooked roms from HERE.
8. I tried accessing the phone via MTTY and use the "boot" command. I still don't fully understand the boot command and what exactly it does, but from my understanding, it resets the boot loader chip.
9. I would like to update the SPL -- instructions HERE. But since I can't fully boot the phone, I can't actually run the Soft SPL (JumpSPL).
Please... any advice will be greatly appreciated.
Similar Problems/Threads:
1. http://http://forum.xda-developers.com/showthread.php?t=406163
2. http://forum.xda-developers.com/showthread.php?t=409272
Try to charge through the usb port on your computer... I have had a similar issue, but that was full stock and still have the issue. HTC chargers wont work for me but select moto ones will. Does the orange light come on when you connect by USB to your computer?
I have tried charging through the USB port on my computer (as well as AC Adapter). It does show the amber light on top (for both methods), but no matter how long I charge it, it will never get to the fully charged green light.
I haven't tried a different (non HTC) charger, but I will try that next.
Are you sure the SIM card door is locked? My phone reboots on its own during start-up if the SIM door is nor properly locked into place...
I just tested the sim card cover. It will reboot at the same point even if the cover is on of off. However, I do believe the cover is sitting correctly, because if I'm at the white AT&T boot screen and remove the cover, the phone will power off.
have you tried hard-resetting your tilt before and after flashing? I had the same problem before. Try to do a hard reset, flash a stock ROM for your tilt, then hard reset afterwards. If same thing happens again, we'll try another method
Put phone in tricolor mode and connect with MTTY.
Type "info 8" and post output here. I suspect problem is caused by bad sectors in the OS area.
There a few different forums on this same subject, and I had the exact same experience on a brand new kaiser last week and thought it was dead. Yea, your gonna have to do a hard reset holding down the power and camera buttons then clicking the soft reset button to get to tri color bootloader mode before it dies, then plug into pc and reflash the official htc rom. It seems like a one time phenomenom as my Kaiser is running just fine now as I was three seconds away from flushing it down the toilet
jockyw2001 said:
Put phone in tricolor mode and connect with MTTY.
Type "info 8" and post output here. I suspect problem is caused by bad sectors in the OS area.
Click to expand...
Click to collapse
Here is the output after using MTTY:
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_k9k2g08
DEVICE ID=0xAA
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x800
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0x700
Partition[2], type=0x25, start=0xD40, total=0x94C0
Partition[3], type=0x4, start=0xA200, total=0x110C0
CE Total Length(with sector info) = 0x5151000
CE CheckSum Length(without sector info) = 0x5100000
Cmd>
kaalgoosy said:
There a few different forums on this same subject, and I had the exact same experience on a brand new kaiser last week and thought it was dead. Yea, your gonna have to do a hard reset holding down the power and camera buttons then clicking the soft reset button to get to tri color bootloader mode before it dies, then plug into pc and reflash the official htc rom. It seems like a one time phenomenom as my Kaiser is running just fine now as I was three seconds away from flushing it down the toilet
Click to expand...
Click to collapse
I have tried a hard reset before and after flashing the ROM. The method I used was pressing down the two buttons on the front of the phone then soft reset (one above internet button and one above mail button)... then I am prompted with a white screen saying, "This operation will delete all your personal data, and reset all settings to manufacturers default. Press Send to restore manufacturer default, or press other keys to cancel." Please let me know if this method is wrong.
I actually haven't tried the official HTC rom because my phone is originally an AT&T phone. I have tried the official AT&T rom, including the WM6.0 and WM6.1, but I will try the HTC rom now. It won't hurt to try!
UPDATE: After hard reset --> Load official HTC Rom 1.56.405.5 (radio 1.27.12.11) --> hard reset again. Still does the same thing... still rebooting during Windows load. The only difference, no more AT&T screen during bootup... now it's a "smart mobility" message.
jommo said:
I have tried a hard reset before and after flashing the ROM. The method I used was pressing down the two buttons on the front of the phone then soft reset (one above internet button and one above mail button)... then I am prompted with a white screen saying, "This operation will delete all your personal data, and reset all settings to manufacturers default. Press Send to restore manufacturer default, or press other keys to cancel." Please let me know if this method is wrong.
I actually haven't tried the official HTC rom because my phone is originally an AT&T phone. I have tried the official AT&T rom, including the WM6.0 and WM6.1, but I will try the HTC rom now. It won't hurt to try!
UPDATE: After hard reset --> Load official HTC Rom 1.56.405.5 (radio 1.27.12.11) --> hard reset again. Still does the same thing... still rebooting during Windows load. The only difference, no more AT&T screen during bootup... now it's a "smart mobility" message.
Click to expand...
Click to collapse
my OS is writing in bad blocks before that's why it's rebooting over and over again. What I did was use jocky's frankenkaiser (http://forum.xda-developers.com/showthread.php?t=393337). This WIPES OUT ALL DATA IN YOUR KAISER and you need to restore it back again. FOR THIS YOU NEED TO FLASH THE RADIO FROM HELL (get it from here http://forum.xda-developers.com/showthread.php?t=393182) AND AN OLD SPL which you have right now. Read the directions carefully-- it's not that hard but also not for the faint-hearted. Goodluck!
pfcsabre said:
my OS is writing in bad blocks before that's why it's rebooting over and over again. What I did was use jocky's frankenkaiser (http://forum.xda-developers.com/showthread.php?t=393337). This WIPES OUT ALL DATA IN YOUR KAISER and you need to restore it back again. FOR THIS YOU NEED TO FLASH THE RADIO FROM HELL (get it from here http://forum.xda-developers.com/showthread.php?t=393182) AND AN OLD SPL which you have right now. Read the directions carefully-- it's not that hard but also not for the faint-hearted. Goodluck!
Click to expand...
Click to collapse
I know you specifically said to get the radio from hell, but after reading jockey's guide, I got the other radio that GSLEON3 successfully got working with FrankenKaiser. Now I'm stuck because it didn't work out for me. I used radio 1.64.08.21 rather than the actual radio from hell 1.65.17.10. Hopefully GSLEON3 and Jockey will be able to help me with this one.
Can't recall I published FrankenKaiser for radio 1.64.08.21
Here is is:
http://rapidshare.com/files/130939717/FrankenKaiser-V1.9408.zip.html
(follow the readme inside the zip file)
jommo said:
I know you specifically said to get the radio from hell, but after reading jockey's guide, I got the other radio that GSLEON3 successfully got working with FrankenKaiser. Now I'm stuck because it didn't work out for me. I used radio 1.64.08.21 rather than the actual radio from hell 1.65.17.10. Hopefully GSLEON3 and Jockey will be able to help me with this one.
Click to expand...
Click to collapse
ooops... replied to your pm it seems jocky sent you the correct one already. Good luck mate
Losing hope....
Well, I successfully completed the FrankenKaiser process, updated my SPL to reflect:
Security Unlocked
KAIS1*0 MFG
SPL-1.1.JockyW
CPLD-8
I am still getting the power off while Windows loading.
I even tried to load back the original radio from hell (1.65.17.10) and completely ran through the FrankenKaiser process hoping somehow it would fix the problem... but unfortunately, it did not work.
1. Maybe I'll try a few more rom/radio combinations
2. At least I can re-use FrankenKaiser to get back to factory SPL when I attempt to go through the warranty process.
Any other suggestions??? Please let me know.
***Thanks for the help so far Jockey and pfcsabre***
I also have the at&t tilt kaiser version and used the North American Rom update from the HTC website to get it back up. Have you tried getting into tri color bootloader mode by holding the power and camera buttons then clicking the soft reset button then connecting to pc and flash the the official rom? That's what worked for me
also, are you getting any kind of notifications before it shuts down?
kaalgoosy said:
I also have the at&t tilt kaiser version and used the North American Rom update from the HTC website to get it back up. Have you tried getting into tri color bootloader mode by holding the power and camera buttons then clicking the soft reset button then connecting to pc and flash the the official rom? That's what worked for me
Click to expand...
Click to collapse
I have NOT been flashing this way. I have been flashing anytime I get to the tri-color screen, rather than this exact procedure you noted. (Tricolor bootloader--> then soft reset and back to tricolor bootloader) I don't know if this makes a difference or not, but I just tried your method with the rom from the HTC website AT&T Official Rom Download from HTC Website. Still no luck. It still turns off at the Windows screen.
Also, I do not get any kind of notification at all. It always resets before or at the Windows Mobile 6.X screen. I do get a distinctive chime the majority of the time right as it shuts down.
I was having random power down issues as well. This may or may not be the same as your problem, but mine ended up being a hardware issue with the camera itself. My device would suddenly say the camera (actual camera hardware not software) was not recognized and then soon after I would get the chime and then shut down. My only solution was to warranty it. Let's hope I have better luck with a replacement device then a lot of the other storries I have read around here.
Goin' for the warranty...
I want to try the warranty route now. I feel it's hardware at this point because I've already done FrankenKaiser.
Now, my problem lies with returning back to the factory SPL and Rom. I can use FrankenKaiser to UNDO "Security Unlocked" and then use JumpSPL via FrankenKaiser to get back to the factory SPL, but from that point, how do I get back to the original ROM?
Note that I still can't boot into Windows at all, and I will want to flash OEM Rom while I have the OEM SPL. Will the OEM SPL allow flashing back to the OEM Rom, WITHOUT JUMP SPL???
Thanks for your input..
I had posted this in the stickied bootloader thread, but I'm pretty sure I posted to the wrong spot. If a mod wants to move this to another thread then by all means...
My kaiser is doing something I haven't heard of yet. Recently its started to act funny after 6 months of no new software, tinkering, flashing - nothing.
3 days ago I had to restart due to the sound cutting out and I got stopped at the bootloader. After fiddling with it, soft resetting multiple times, taking out the battery (just random low level troubleshooting) it booted into windows. This happened sporadically one or two more times.
I have also noticed that in the last 3 days the phone will suddenly drain to no battery without any warning. I will have 25% battery and be on a call for 20 minutes, then have the phone completely power off. normally, windows alerts me to high heaven with multiple warnings, etc. None - just powered off. After 30+ minutes of recharging in the off state, I powered on... bootloader again.
I hooked it into USB and sent the mtty "boot" command. This worked, it booted straight into windows. Due to my frequent sound problems I figured I'd load on a new radio "just in case" - so I loaded on the eMo radio via the sd card method, and soft reset. Again, bootloader. So I gave it the mtty BOOT command and got into windows... so far so good.
I soft reset just to see what would happen - bootloader.
Now I find myself having to soft reset frequently because the sound will just stop working at random. Of course when I soft reset I get bootloader but just today I found something very interesting: If I plug the phone into USB then simply soft reset it will restart and go right into loading windows. This works from inside windows as well as when I'm stuck at bootloader.
Is this common? My rom is Dutty's 6.1 from April 29. My radio is currently 1.71.09.01.emo. Thanks guys
*edit* now every time I hang up a phone call the earpiece starts making a "TV snow" or "power lines" kind of noise. This of course requires a soft reset which may or may not send me into bootloader. it varies.
I'm no flashing or rom expert by any means but if I were you, I would remove SD card, flash a different hardSPL other than what you're using now, flash a another cooked rom, and another radio. Starting from scratch sounds like the way to go. Good luck ...
I flashed a new SPL (3.29 fixed) and switched from dutty's to hyperdragon III Nov 6. I'm pretty sure this has fixed it.
HI, the problem is that phone dont start, what happens is that when attempting to turn it only shows the Tmobile logo for a few seconds, then turns off and comes back the logo, and definitely off, the LED light dont turns on but displays the logo when power on the cellphone!!!!!!!!!!
I appreciate your help
Step 1:
It could be a problem with the battery - reboot while the charger is connected
and/or let the battery charge fully before turning on the device. Use a different battery if you can get for a try-out.
Step 2:
Remove the SD card, sometimes a faulty card prevents the boot.
Step3:
If the boot does not go to the operating system, then also the settings in the OS may prevent a clean boot. This is very unusual, but you could try to reset the device to the "out of the box" settings (hard reset). You will loose all data and installed programs on the device though in that way.
Step 4:
If the OS is corrupt (how could that happen?) you may want to re-flash the operating system. Take the last available official ROM for that - you will not have to deal with any "special" unlocking stuff. Needless to say that you will also loose everything on the device.
Hi
I have this problem too. T-Mobile SDA Music Edition (Tornado) starts to T-Mobile logo and turn off. I read a lot about it and I think its corrupted after flashing to WM6 (it was'nt my phone). When I write to TeraTerm "info 2" it looks like its CID locked...
Is it enough to return to the original WM5 ROM??
If yes, wher can I find it??
Edit:
I found t-mobile SDA ROM in this post:
http://www.howardforums.com/showthread.php/1035146-SDA-ROM-disappeared-from-HTC-site-Why
but it didn't help:/
Edit:
It works After second flashing SDA alive. First time don't work because battery