View Full Version : Stuck On Boot Screen
Ok, I really have read existing threads related to similar problems, but I am completely stuck on the boot screen (not bootloader screen) with my Tilt.
I flashed Dutty's 6.1 ROM last week and all had been working fine until last night. The phone was stuck with screen lock (screen nor buttons would respond). So, I performed soft reset and it just stopped at 'smart mobility' boot screen. I then performed hard reset, and again it just stopped and hung at 'smart mobility' screen.
This morning I got into the bootloader screen (power + camera + reset) and flashed original ROM (well, new officiall AT&T ROM released last month). Original ROM flashed successfully, but it now hangs on AT&T boot screen. I have tried hardspl, and flashing multiple ROMs, which all complete successfully, but it always hangs at the boot screen.
Thoughts?
P1Tater
03-03-2008, 08:08 PM
what radio are u using?
Well, with Dutty's I was using 1.64.08.21 that came with the ROM... When I flashed to the stock AT&T ROM, I used the radio included with it as well (1.27.14.09).
P1Tater
03-03-2008, 08:35 PM
Well, with Dutty's I was using 1.64.08.21 that came with the ROM... When I flashed to the stock AT&T ROM, I used the radio included with it as well (1.27.14.09).
Dutty's didn't come with a radio.
Well, I was using 1.64.08.21.. Right now, I have the stock ROM flashed with 1.27.14.09
hchavarria
03-03-2008, 08:40 PM
I have a similar problem. I flashed alex rom yesturday then I flashed back to OEM to test something then today I flashed back to alex cube rom and it said flash was successful but when I did a hard reset during the "Tap screen to begin" my phone go stuck in the AT&T inital logo. I tried connecting to USB to reflash but USB won't detect the phone. I have hard reset, removed battery, and no avail. Does this mean I bricked my phone?
To clarify, I have been doing these for some time and also had and 8125 previously, so I understand the flashing process. I also understand that there are only certain radios that work with WM 6.1 and 6.0. This doesn't appear to be a radio incompatibility issue. As I mentioned, I was using Dutty's 6.1 ROM just fine for several days before this happened. I had been using Sleuth's 6.1 prior to that.
Tim
GSLEON3
03-03-2008, 09:16 PM
You always should re-flash the radio AFTER flashing the ROM. Pt yuor device into boot loader (hold camera, power & reset button). Reflash the Radio. If that doesn't work PM me & I'll walk you thru looking for bad memory blocks.
GSLEON3
03-03-2008, 09:20 PM
I have a similar problem. I flashed alex rom yesturday then I flashed back to OEM to test something then today I flashed back to alex cube rom and it said flash was successful but when I did a hard reset during the "Tap screen to begin" my phone go stuck in the AT&T inital logo. I tried connecting to USB to reflash but USB won't detect the phone. I have hard reset, removed battery, and no avail. Does this mean I bricked my phone?
NO, it does not mean brick. It means you may want to try another USB port, check the activesync connection settings, & possibly reflash using the SD card.
Edit: After looking at your MTTY feedback, & confering with a few of the Gods, I have to unfortunately tell you that your NAND chip appears to be damaged beyond flushing. The blocks can't even be erased, & that's the problem. When you reflash the blocks have previous ROM data still stored & because of the NAND damage they cannot be overwritten. Return under MFG warranty is all you can do. (Believe me, I really hate saying this & even got confirmation from Pof & Jocky) :( Sorry Guy.
hchavarria
04-03-2008, 08:33 PM
My 30-day return policy date is tomorrow so I went to the AT&T store today and they swapped it out with a new device. They mentioned next time I have to ship it.
Could this have happened because of to much flashing? Or was this possibly an already existing defect?
I got a new one shipped to my overnight. There was obviously something wrong with it, as I tried everything under the sun. Flashed new ROM, then flashed new radio, flashed original ROM, etc. Everything gets stuck on the boot screen. At one point yesterday, I left it at the boot screen for a couple hours and it finally booted up, but then locked up again once it did. Then next time I reset, it got stuck on the boot screen again.
P1Tater
04-03-2008, 09:55 PM
Please tell me you installed hardspl first?
AvinashDhaniraj
04-03-2008, 10:50 PM
Hi all,
I have been flashing/testing many roms for a number of years now. I particularly enjoyed Jasjamming in my Tytn I days. Now...
Great work seen by many developers.
When I first got my Kaiser, i tried HardSPL, and had "white screen" issue, I then followed instructions on "white screen" thread....copied cab to kaiser....ran cab from kaiser..........eventually was able to flash to a new/ different ROM
However, I recently flashed my Kaiser and after using it for 6-7 hours after flash, it soft reset itself. It continued to keep soft reseting itself without geting to boot screen. It kept reading "smart mobility" and it would reset, vibrate, reset, vibrate, reset.......
I tried EVERYTHING - remove battery, flash back to original ROM, change radio (bootloader worked in safe mode - holding down camera button), but to no avail.
I then tried MTTY, and no go with this too. I eventually had to give my phone back in to HTC.
The question I ask is what is the cause of this? Is it excessive flashing? Is is HardSPL? Any comments/ suggestions would be welcomed...
Many thanks
Please tell me you installed hardspl first?
If you are asking me that question, the answer is yes I did run hardspl. As I mentioned, I have been doing this for long enough that I know what I am doing. I also mentioned that I was successfully running Sleuth's 6.1 for a month or two before switching to Dutty's new 6.1. I was only running Dutty's for a few days before all of this happened.
There is definitely something wrong.. if I let it sit long enough, it will eventually boot. It will work for a few minutes, and then lock up again. Once I reset, it sits on the boot screen for a couple hours again. I have flashed several different ROMs and Radios to get different results, but the results are always the same.. It hangs at the boot screen.
P1Tater
04-03-2008, 11:26 PM
I guess you have also tried going to the tri-color screen and re-flashing as well as a HR or MTTY command
AvinashDhaniraj
04-03-2008, 11:28 PM
If you are asking me that question, the answer is yes I did run hardspl. As I mentioned, I have been doing this for long enough that I know what I am doing. I also mentioned that I was successfully running Sleuth's 6.1 for a month or two before switching to Dutty's new 6.1. I was only running Dutty's for a few days before all of this happened.
There is definitely something wrong.. if I let it sit long enough, it will eventually boot. It will work for a few minutes, and then lock up again. Once I reset, it sits on the boot screen for a couple hours again. I have flashed several different ROMs and Radios to get different results, but the results are always the same.. It hangs at the boot screen.
Please don't take offence to my probing, as my questions weren't directly directed to you. All I am saying is that we need to understand what is the actual cause of this problem, or we all will be "flashing in the dark", and fearing that this problem could be imminent every time we flash in the future.
Many thanks.
I guess you have also tried going to the tri-color screen and re-flashing as well as a HR or MTTY command
P1 - Since I can't get the phone to boot completely (well, except for waiting several hours), the only way that I have been flashing different ROMs is from the tri-color screen. Regardless of what ROM or Radio I try, it still just hangs at the boot screen. The only thing I haven't tried was MTTY.
Please don't take offence to my probing, as my questions weren't directly directed to you. All I am saying is that we need to understand what is the actual cause of this problem, or we all will be "flashing in the dark", and fearing that this problem could be imminent every time we flash in the future.
Many thanks.
I was actually replying to P1, hence the reason I quoted him. ;) So, I don't take offense to anything you said.
P1Tater
04-03-2008, 11:48 PM
Well, I hope your not getting offended to my questions? I am just trying to cover all of the simple fixes first since those have been the majority of the things that fix "Most" people's issues. I suggest getting in touch with GSLeon3. He has a pretty good handle on what goes on in flashing and all of the fixes.
Well, I hope your not getting offended to my questions? I am just trying to cover all of the simple fixes first since those have been the majority of the things that fix "Most" people's issues. I suggest getting in touch with GSLeon3. He has a pretty good handle on what goes on in flashing and all of the fixes.
Not offended at all... I am appreciative of the suggestions.
GSLEON3
05-03-2008, 01:01 AM
As always, here to help. If the flashes aren't fixing your issue, I suggest finding out what the problem is. It will take you about ten minutes & I can probably tell you whether it can be saved or not. Maybe you're scared because of what I had to tel hchavaria, but I assure you that I've helped save 10 devices to every one that I have to give up on. ;)
d_nosko
14-04-2008, 02:25 PM
All,
I am totally new to flashing but I got the same issue with my Tytn II today. I got the device from eBay and assume it was flashed before it arrived. I had it running for more than half a year now until this morning when I soft-reset it myself. And it now hangs at the "Smart Mobility" screen showing me the versions of R. G. and D. (whatever that screen is called).
My question is: Is there any way for me to bring the device back to life? I can reflash whater is needed, please give me guidance.
In case if this helps:
R: 1.27.12.11
G: 22.45.88.07H
D: 1.56.00.00
svcglobal
14-04-2008, 03:16 PM
I do not want to be pessimist and please do not be offended but, erratic software problems, when that software is probed to be good due thousand of flashing well succeeded, point us to a hardware failure. A fault single bit in the memory boot area can do exactly the issues posted in this thread.
Flashing an EEPROM, yes, can stress a defective chip causing it total failure. However, a healthy one can be reflashed "ad eternum" without any problem.
There are many other hardware faults (RLOD) on the Kaiser due the high grade of integration necessary to put a medium computer power (Wi-Fi, GPS, Bluethoot, 3G, cameras) in such so little space.
So, IMMO for this kind of problem the best is ask for a replacement and move on. There will be not any software solution for a hardware failure.
GSLEON3
14-04-2008, 10:26 PM
All,
I am totally new to flashing but I got the same issue with my Tytn II today. I got the device from eBay and assume it was flashed before it arrived. I had it running for more than half a year now until this morning when I soft-reset it myself. And it now hangs at the "Smart Mobility" screen showing me the versions of R. G. and D. (whatever that screen is called).
My question is: Is there any way for me to bring the device back to life? I can reflash whater is needed, please give me guidance.
In case if this helps:
R: 1.27.12.11
G: 22.45.88.07H
D: 1.56.00.00
First thing, this could be a hardware problem, but that is not as likely as it being a rom/data problem. First thing, hold down the camera button & the power button at the same time. While still holding camera & power buttons, depress the reset tab with the stylus & keep holding all three until the tri-color boot scrren pops up.
When you get to the BL screen, write down everything it shows & PM the info to me. I can probably get it going for you.
d_nosko
15-04-2008, 02:41 PM
First thing, this could be a hardware problem, but that is not as likely as it being a rom/data problem. First thing, hold down the camera button & the power button at the same time. While still holding camera & power buttons, depress the reset tab with the stylus & keep holding all three until the tri-color boot scrren pops up.
When you get to the BL screen, write down everything it shows & PM the info to me. I can probably get it going for you.
Gsleon3,
Thanks for your help!
I have managed to hard reset the phone and not it seems working now. Of course, all the data I had is lost. Another lesson learned on backing up :-)
All the best!
First thing, this could be a hardware problem, but that is not as likely as it being a rom/data problem. First thing, hold down the camera button & the power button at the same time. While still holding camera & power buttons, depress the reset tab with the stylus & keep holding all three until the tri-color boot scrren pops up.
When you get to the BL screen, write down everything it shows & PM the info to me. I can probably get it going for you.
Hi GSLEON3,
I have the same problem (hangs at AT&T screen and says RGD values), I held the buttons down and got to the BL screen and this is what my tri-color screen says.....
KAIS1*0
SPL-1.0.OliPof
CPLD-8
(and in the bottom white area says "Serial")
Please tell me if there's an easy, non-painful way to fix my tilt.
I have not tried hard-resetting, I'm trying to avoid that.
EDIT: I hard reset my phone, everythings fine now.
If you're wondering how I got into this whole mess I was trying to change my Sip Keyboard to the Diamond Qwerty thats like 4mb and takes everyone like 5min to install. so i have been using duttys from early april and deleted the orig pcm that was cooked in and installed diamond, but couldn't get diamond to work and installed sip change and something called default im then soft reset, didn't help, kept soft resetting, and boom.... FU<K3T!!!!
2ND EDIT: The very last thing I installed before my Tilt took a $#!T was "Keyboard_Cert".
ibre34
03-06-2008, 07:35 PM
Yesterday tilt got stuck at the "Smart Mobility" screen and refuse to boot.
I tried hard reseting and removing the battery but it didn't work
I managed to go to 3-color screen and reflash my tilt to 6.1 official but no avail.
This morning I removed the battery again and... WOW... my tilt is working again
This was the most strange thing ever... now I am afraid this would happend to me again...
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.