Database Info

Dutty 6.1 + 1.64.08.21 = Brick?

Hey folks -
I upgraded my ATT Tilt to DUtty's 6.1 today (first time flashing).
Anyway, after sound wasn't working I read up on the radio information and decided to go with 1.64.08.21 based upon what some folks said worked for them in various posts.
To flash the ROM, I am using JumpSPL1.56-KAIS.exe loaded onto the device.
Dutty's worked fine, but the radio made it to 99% then hung. I waited for 3-4 minutes and nothing happened, but the flashing tool said it lost connection. I followed the recover steps including a hard reboot (and went to the tree color screen with "serial" at the bottom), but now each try just hangs at 0% when trying to install the radio ROM.
What do I do?
Thanks,
Tom

pearsth said:
Hey folks -
I upgraded my ATT Tilt to DUtty's 6.1 today (first time flashing).
Anyway, after sound wasn't working I read up on the radio information and decided to go with 1.64.08.21 based upon what some folks said worked for them in various posts.
To flash the ROM, I am using JumpSPL1.56-KAIS.exe loaded onto the device.
Dutty's worked fine, but the radio made it to 99% then hung. I waited for 3-4 minutes and nothing happened, but the flashing tool said it lost connection. I followed the recover steps including a hard reboot (and went to the tree color screen with "serial" at the bottom), but now each try just hangs at 0% when trying to install the radio ROM.
What do I do?
Thanks,
Tom
Click to expand...
Click to collapse
from what i understand you cant flash a radio with the jumpspl. why not install hardspl and be done with it. it's a one time thing.

DELETED... Above is better^^

pearsth said:
Hey folks -
I upgraded my ATT Tilt to DUtty's 6.1 today (first time flashing).
Anyway, after sound wasn't working I read up on the radio information and decided to go with 1.64.08.21 based upon what some folks said worked for them in various posts.
To flash the ROM, I am using JumpSPL1.56-KAIS.exe loaded onto the device.
Dutty's worked fine, but the radio made it to 99% then hung. I waited for 3-4 minutes and nothing happened, but the flashing tool said it lost connection. I followed the recover steps including a hard reboot (and went to the tree color screen with "serial" at the bottom), but now each try just hangs at 0% when trying to install the radio ROM.
What do I do?
Thanks,
Tom
Click to expand...
Click to collapse
1.) Disable USB connections in activesync.
2.) Put your phone into the tri-color screen.
3.) Flash the original shipped ROM.

Something i learned this past week from another poster, that had a problem. U can't JumpSPL a radio Rom.
Try flashing a 6.0 rom and see from there. I assume you couldn't Hard SSPL your device? if this is not the case then your better off doing that

I tried hardspl and it didn't work - constant white screen.
Thanks for the tip on original ROM, trying that now.
Tom

pearsth said:
I tried hardspl and it didn't work - constant white screen.
Thanks for the tip on original ROM, trying that now.
Tom
Click to expand...
Click to collapse
did you try the hrdspl, white screen solved thread?
http://forum.xda-developers.com/showthread.php?t=354061
jocky made it so you can flash hardspl from what I understand.
you can also try this to get hardspl on your device.
http://forum.xda-developers.com/showthread.php?t=361236

Does this mean I need to avoid flashing at all if I cannot use hardspl?

avoid flashing radio, but try the links that tater posted and see if it solves your problem.

Thanks, everyone...just got back to ATT stock rom and all is well again. Will try the links posted above!
Tom

pearsth said:
Thanks, everyone...just got back to ATT stock rom and all is well again. Will try the links posted above!
Tom
Click to expand...
Click to collapse
just be careful to follow the instructions to the letter. Good luck.

Just finished re-doing everything. I was confused regarding the fact that JumpSPL didn't replace HardSPL, it just helped getting it working.
Just finished reinstalling ditty and the same radio version and all is working great.
Now off to figure out how to play with TouchFlo and Cube.
Thanks!!!

pearsth said:
Just finished re-doing everything. I was confused regarding the fact that JumpSPL didn't replace HardSPL, it just helped getting it working.
Just finished reinstalling ditty and the same radio version and all is working great.
Now off to figure out how to play with TouchFlo and Cube.
Thanks!!!
Click to expand...
Click to collapse
very welcome. glad to see you back up and running.

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?

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).

tmac said:
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).
Click to expand...
Click to collapse
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

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

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.

hchavarria said:
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?
Click to expand...
Click to collapse
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.

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.

Please tell me you installed hardspl first?

Soft Reset Looping - Dead Kaiser
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

P1Tater said:
Please tell me you installed hardspl first?
Click to expand...
Click to collapse
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.

I guess you have also tried going to the tri-color screen and re-flashing as well as a HR or MTTY command

tmac said:
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.
Click to expand...
Click to collapse
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.

P1Tater said:
I guess you have also tried going to the tri-color screen and re-flashing as well as a HR or MTTY command
Click to expand...
Click to collapse
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.

AvinashDhaniraj said:
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.
Click to expand...
Click to collapse
I was actually replying to P1, hence the reason I quoted him. So, I don't take offense to anything you said.

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.

P1Tater said:
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.
Click to expand...
Click to collapse
Not offended at all... I am appreciative of the suggestions.

Not-so N00B dumb question

I've been flashing new ROMS on an 8525 for a couple of years now, but I'm new to the 8925.
I've been reading a lot, I think I understand the relation between SPL and the ROMs now, but I'm still puzzled.
I keep getting a lot of cruft left behind from prior ROMs and don't know how to get rid of it. for example about three ROMs ago, I flashed the "Mobile Vista" from ansar. Now I still get his Today theme, and there are still a lot of apps installed that read "ansar..."
I've tried removing the battery before flashing, making sure the SPL version is OK with the ROM doing hard resets - nothing seems to let this device start from a "clean slate".
I'm trying to find a ROM I can be happy with, which is why I'm trying so many, but I can't fairly evaluate aon one ROM if I don't know what I've really got installed.
TIA
Walt

I've never heard of anything like that happening Are you sure it is the today theme, or just the boot splash? That would be most likely.
As far as the programs, maybe most of them are from ansar? Which ROM are you using right now?

I just flashed the PDA Corner latest version (15) and it seems to be behaving now. Prior ROMS I tried this morning included Athine, Garmin and Phoenix.
Prior to flashing PDA Corner, I did an "Erase memory" (hard reset from software) and removed the battery for about 10 minutes. Maybe that's what did it. I agree, I've never seen anything like this before, I always thought that flashing the ROM reased everything, but then I started reading about SPL on the Kaiser somehow being more than just a bootloader so I got concerned.
And yes, it was the Today screen including clock, wallpaper, etc. The splash screen on bootup actually did change to the one corresponding to the new ROM.
Thanks.
Walt

When flashing a new ROM, when you get to the "Tap screen to begin" do you perform a Hard Reset?
If not, I suggest you start doing now.
Also, merschle (ex-moderator and Artemis cook) recommended flashing a ROM twice with a Hard Reset in between. I don't do this, but it just might help
Ta
Dave

Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs

Billun said:
Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
Click to expand...
Click to collapse
I hard reset three times then I flash an OEM ROM, then I hard reset three more times to be sure. I know it's anal, but it works for me.

I don't know how you're flashing try the SD Card method.
It's safer and more reliable.
The SPL & Rom have closer relationship than on your older device.
A sign of have the wrong SPL or needing to change to another SPL is freezing. If you notice your device is freezing or non-responsive, flash the recommended SPL by the chef.
Don't worry any, I was the same when I upgraded from the Wizard...gotta learn all over again.

Tilt Flashing Issue, this is a repost

Hey Guys,
First off this is a re-post, me old thread was closed, I am sorry for reopening but I am still having this issue. DaveShaw and smokestack76 had posted. Dave thank you for your reply but I have been through the noob flash guide and many many many other threads and it does not resolve my issue.
I'm not new to flashing and roms, I have flashed at least 100 times and have done some cooking. Had the random stuck in bootloader that wouldn't resolve itself today (using 3.29) Loaded kaisdiagsd.nbh and flashed stock att rom. (probably should have gone right for the spl patch but I was frustrated and needed my phone) Boot loader is now v3.65
Flashed fine, reboot, same issue. Phone will now only load the stock 6.1 att rom from the micro sd. kaisdiagsd.nbh is stuck on loading as for all other roms. I can occassionally get the os to load using mtty. From there tried jumpspl and it would not connect via usb at all.
I have tried flashing spl from the sd and yes spl image was KAISIMG.nbh and KAISDIAG.nbh was on there as well. Card is formatted fat32. HardSPL would start, read the file and get stuck on loading.
When in the stock 6.1 os I get the old unrecognized usb device in both xp and vista.
Is there anything else I can do to reflash spl? All i can think of is trying the task 2a, wiping everything and trying to flash from diag but I don't even want to try that route without something solid in place.
The phone is 2 years old, upgrading when the touch pro 2 hits att in aug sept or whenever it is released, but I need my phone.
I have gone through many many many posts. I'm stuck. Any help would be appreciated.
I have the stock 6.1 att rom up right now but I would like to resolve the issue.
__________________

finally finally got the patched version of 3.29 flashed. I will let you guys know how it goes from here. I am on a different computer at work.

Success!
I started from complete scratch and a fresh brain and was able to get everything going.
After I got the os back up i was able to start jumpspl and get it to connect via usb. Then only the force usb on 3.29 patch would work. After that repaired active sync and I was ready to go. Thanks smokestack79 for the late night help last night. I was out of it and frustrated. Seems like she's got a little more life in her after all.

[Resolved] Getting stuck on go go go

Hi,
Alright, im totally new to this; I'm trying to run Android on my HD2...
So, All guides I found kind of talked about the same things:
1, Flash phone with HSPL3
2. Flash phone with Radio 2.15.50.40
3. Flash magldr v.1.13
4. Download a NAND ROM -- I was first trying with Cope's Cyanogen Rom, kept getting stuck on GO GO GO! (in magldr) after a while I actually got it to work, but couldn't get data to work, the first time I restarted the phone it got stuck again....
Then I flashed official tmobile wm, got rid of magldr, and started all over, but this time I tried flashing MDJ's Cyanogen Rom, however after resolving several previous issues i got stuck on GO GO GO! again...
also, I have tried with both magldr v 1.11 and 1.13
-------------------
Is there something wrong with the previous steps I took? Any suggestions?
There is another thing that was always wrong with my phone which might be causing this problem; ever since I got it it would sometimes get stuck on the first purple "stay together" screen and not want to move... Even after I restart the screen would persist, and the only solution was to let it 'chill' for a while before attempting to turn on again...[It got stuck even when I flashed the wm to get rid of mangldr]
So any suggestions on how could I get Android running ???
Thanks

Never mind....
It seems to have fixed itself!!! THIS IS GREAT!!! Skyfire, one bus away!!!!
Thanks to all for this awsome forum and for the great roms!!!!

xzpx said:
Hi,
Alright, im totally new to this; I'm trying to run Android on my HD2...
So, All guides I found kind of talked about the same things:
1, Flash phone with HSPL3
2. Flash phone with Radio 2.15.50.40
3. Flash magldr v.1.13
4. Download a NAND ROM -- I was first trying with Cope's Cyanogen Rom, kept getting stuck on GO GO GO! (in magldr) after a while I actually got it to work, but couldn't get data to work, the first time I restarted the phone it got stuck again....
Then I flashed official tmobile wm, got rid of magldr, and started all over, but this time I tried flashing MDJ's Cyanogen Rom, however after resolving several previous issues i got stuck on GO GO GO! again...
also, I have tried with both magldr v 1.11 and 1.13
-------------------
Is there something wrong with the previous steps I took? Any suggestions?
There is another thing that was always wrong with my phone which might be causing this problem; ever since I got it it would sometimes get stuck on the first purple "stay together" screen and not want to move... Even after I restart the screen would persist, and the only solution was to let it 'chill' for a while before attempting to turn on again...[It got stuck even when I flashed the wm to get rid of mangldr]
So any suggestions on how could I get Android running ???
Thanks
Click to expand...
Click to collapse
Hi, Can you please tell me how do you fix your data to work? On my HD2 everthing iworks fine except data using phone connection ( Data works fine on wifi). Please let me know how to fix this or send me a link for your android ROM. I am using Flash phone with HSPL2.08
2. Flash magldr v.1.13. Anroid version 2.2. I dont know the radio version i am using.
Thanks in advance. Mathew