Database Info

why can't i flash any NBD roms?

i have a G4 IPS/SPL 2.25.0001 and i follow all of mun's steps to flash roms and everything usually works fine, i installed the windows titanium rom last night and was loving it but whenever i try to install NBD's roms everything goes fine with the shelltool and when i do a hard reset it freezes at the cingular screen that displays the IPL/GSM info, it's done this three times in a row with 3 different versions of NBD's roms
i'll flash back to titanium but what could be the cause of this?
any help would be appreciated

on my cidlocked g4 whenever i shelltooled NBD from a cingular base rom it would always get stuck at the cingular boot screen. Only way i can get NBD to run is to use shelltools over the wizardlove rom.

pr0naLd said:
on my cidlocked g4 whenever i shelltooled NBD from a cingular base rom it would always get stuck at the cingular boot screen. Only way i can get NBD to run is to use shelltools over the wizardlove rom.
Click to expand...
Click to collapse
i tried from a windows titanium rom and the cingular manufacturer rom, i'll try the wizardlove rom thank you
if anybody feels like answering: why does this make a difference?

yep that did it, the NBD rom worked after i flashed wizardlove first
weird

Wizardloverom is an amazing piece of engineering. Ask anyone how they "saved" their wizard.. 9 times outta 10, wizardloverom.

How long does it take, on average, for you guys to flash the NBD rom? WizardLove almost always goes on in about 8 minutes, but NBD just sits there indefinitely, and I'm dubious about doing a Hard-Reset without confirmation that the flashing procedure is finished.

Yes, it is confirmed that sometimes shelltool doesn't report on flash complete.
Just doing a hard reset after waiting is fine.

unlocked g3 suddenly won't flash TNT

i have a g3 ipl/spl 2.26 completely unlocked device that i have flashed many wm6 roms on in the past. my touchscreen went dead in landscape mode so on a hunch i flashed back to wm5 to try and fix it (which it did). but now i flash the same TNT rom i've flashed a hundred times the same way and everything changes but the OS i tried the boring rom and it changed, but even from there it seems (now) that it's TNT that for some reason won't change the os. any ideas?

which WM5 ROM did you flash back to? was it the official t-mobile ROM?
if not I'd try that first...
if that doesn't work I'd actually take it through the unlocking process again and use that CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM first...the up to t-mobile's offical ROM...then flash to TNT

i flashed back to the latest tmo rom. i'll give what you're talking about a try. as a test i flashed to that one and that's the first one to change the OS. this whole thing caught me by surprise that's for sure.

hope it works for ya...let me know...

update, problem solved! i was using the touchflo rom (love it) and i gave the Professional flavor without the touchflo a try and it worked. all is well.

j3d1n4s7y said:
if that doesn't work I'd actually take it through the unlocking process again and use that CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM first...the up to t-mobile's offical ROM...then flash to TNT
Click to expand...
Click to collapse
hi,
i have the same problem here
what exactly do you mean with "take it through the unlocking process again" should i unlock the wizard again with the service tool (mine is already unlocked and i had 2 different versions of wm6 roms) or just flash the CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM and then the t-mobile one?
p/s before flashing the tnt touchflo i flashed the t-mobile rom, and then while flashing the TNT touchflo i got error on 99%. After that the wizard boots only in boot manager and i can only flash t-mobile rom, the other roms i have tested give back errors (i have not tested the CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE ROM)
Thanks!!!
Regards

i grabbed the latest lokiwiz and used one of the forum stickies as a guide and relocked it and then followed step by step to unlock again. i can't confirm or deny that solved the problem, but it's worth a shot.

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.

upgrade to WM6 close to fail ?

Hello,
First my question :
I'm now thinking about reinstalling official ROM but my question is : should I remove Hard spl and move back to initilial IPL/SPL before loading the WM5 rom.
Then the context:
I'm a newbie and 2 days ago I've tried to upgrade my I-Mate K-Jam to WM6.1.
After having carrefully read several thread and in particular the thread "Wizard Windows Mobile 6 for newbies" i first start to unlock my G4 mobile with HardSpl. This was a great success so I moved on to the next step loading a WM6 ROM. I choose the WizFlo 6.1.1.4 (http://forum.xda-developers.com/showthread.php?t=435228) but this was not a success since my K-Jam was just looping on the splash page/alignment wizard and reboot. I really thought that I had turned my mobile into a brick but was still continuing to investigate and yesterday evening I've learned how to just start the bootloader by pressing the camera button while starting-up. Yepee, 2 a clock this morning, I succeed loading the vanilla version of the TNT rom : http://forum.xda-developers.com/showthread.php?t=388229. Super everything was working fine so I went to bed.
This morning, very proud of what I've done alone I just decided to move from the TNT vanilla version to the professional version. This was a mistake since then I was never able to restart my K-Jam. It just freeze on the TNT splash screen. I've tried to reload several other rom but the TNT splash screen remains and my mobile just continue to freeze.
I'm now thinking about reinstalling official ROM but my question is : should I remove Hard spl and move back to initilial IPL/SPL before loading the WM5 rom.
Thanks in advance for your help

YES!
In order to revert back to official rom,you'll first have to remove HardSPL,otherwise it'll Brick the phone.
Secondly, have you tried a Hard Reset,it might help the phone to start working.Is your battery fully charged ?
After getting the phone HardSPL,there's no reason for any wm6 roms like TNT to stuck up,it might be that the battery is weak or flat.
Get the battery fully charged,try a Hard Reset,otherwise reflash TNT.

Thanks for your answer, I'm not sure about the batterie status. Am i able to refill the battery in bootload mode. or does the official K-jam charger work in my mobile is not yet started.

Almost a week I'm working on my mobile but no sucess yet.
One more question, Is there any special restart or reboot to be performed once the rom load process is complete ?
I've tried to install Loverom or merlin rom but even if the splash page change I never go furher. I'm now considering on moving back to an official ROM. But since I didn't backed up mu rom before all of these update process I'm gone use a download one.
K-JAM_WWE_216901_2169101_020710_ship.exe. This official package install a ROM file and the RUU utility, but how can I check that the rom does not contain IPL nor SPL file.
Is there a way to check rom content before a load. I'm using hardspl and I've read that if I instal a ROM with IPL/SPL i will turn my device into brick.
May be I should also remove hardspl but how can I do this ?

Solved !!
I just notice a format error when hard reset.
Google it and find his thread
http://forum.xda-developers.com/showthread.php?t=428312&highlight=format+error&page=3
Fixed yepeeee.
thanks to all for your help.

Good that you solved it finally, Happy Flashing