Tilt Flashing Issue, this is a repost - Tilt, TyTN II, MDA Vario III Windows Mobile ROM De

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.

Related

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.

stuck after update failure

Was installing duttys rom when my anti-virus program started. Update failed and since then all I see is the tri-colour screen. Sometimes I can get the rom updater to recognise my TyTNII but it will not continue to upgrade. Any suggestions. Have tried mtty1.42 but it doesn't seem to have a usb port option, have tried hard reset etc with no luck. Any suggestions would be greatly appreciated.
An update, I have tried several rom updates since, most get to the stage where the progress bar is shown and the stop. The HTC update to revert to shipped rom gets to 1% and then tells me that this rom is not suitable for my pda!
How about some more information...
What is your Tytn II - Tilt or HTC?
What Rom was on it before you tried upgrading?
What Radio was on it before you tried upgrading?
What version of Duttys did you try to flash?
Did you upgrade to HardSPL before you tried flashing?
This should enable someone to begin trying to unbrick your phone.
Also DO NOT USE MTTY unless you know what you are doing - it can seriously kill your Tytn if used incorrectly. Wait for GSLEON3 to swing by before trying this - but he's very busy at the moment helping others unbrick their toys so you may have to wait for a while.
If you had an original rom/radio from AT&T or HTC it shouldn't hurt trying to download an original rom and try to flash - preferably using your SD card.
Also, while you're waiting for someone to help, have a good read through the Kaiser Wiki (in my signature) before trying anything else.
what are the steps that u take? let us know if u are missing any
HTC TyTN 11, Was using Q-mobile 1.2 but couldn't install tom tom navigator 6, don't know what radio it was using because i hadn't got that far. Was trying to flash Dutty's 6.1 and I had run jumpspl from device because I got the white screen when I treid to run 1.93 so installed 1.56 to pda and ran it. this worked to insatll Q-mobile this morning.
Hope this helps!
what are the steps that u take? let us know if u are missing any
Try to reset pda keep getting tri-colour, attach usb and usb shows at base of screen. When i try to install rom The problem in my second post occurs. I cannot hard reset device to anything other than the tri-colour
Thanks for your help, I tried one of the roms indicated and it worked! I have spent so much time reading various wikis and downloading files. I'm not entirely sure why it worked this time but I'm not about to ask questions! Thanks again!
OK, now you've got your phone working again, make sure that you get HardSPL installed before you try anymore flashing.
ok i was installing KAIS_Radinly_0.26.07.06_CustomRUU and it froze at 96% and now my phone is bricked!! every time i restart the phone its stuck at the RED GREEN BLUE and WHITE screen.. i tried using mtty but then im not trying to mess my phone up any more. i dont understand how to fix it.. if i download a new ROM and put it on my SD card then how do i read it with my phone? sorry guys, im a noob at this as you can tell..
nm guys. i just ran the new rom and it worked! haha sorry for posting too quick!
okay i have one problem after fixing it. i downloaded the TEST rom for the ATT tilt and now every time i reboot my phone it says 'TEST ONLY. NOT FOR SALE.' how do i get rid of this? when i installed a new rom it still says this and i even tried hard resetting my phone but it did not reset anything to factory settings. it just reloaded the rom that i last had!
xmooglex said:
okay i have one problem after fixing it. i downloaded the TEST rom for the ATT tilt and now every time i reboot my phone it says 'TEST ONLY. NOT FOR SALE.' how do i get rid of this? when i installed a new rom it still says this and i even tried hard resetting my phone but it did not reset anything to factory settings. it just reloaded the rom that i last had!
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=KaiserFAQ
your answer is in there

Suddenly can't flash!

Current Setup :
HardSPL (latest, 3.56 I believe)
Radio: 1.65.29.22 (from Niki or Neon, almost positive it was Niki)
Solace v3.1
Decided I wanted to go back to newest radio, attempted to flash to it; hit a snag at about 78%. Progress didn't update for a while, then to 100%. Update app said there was a flash error, and it did not complete correctly. Device restarted, stuck at bootloader. Re-attempted the flash, same result.
Next, I tried flashing AT&T's latest ROM. Stalled at about 76%, message about having a communication error, walked through the apps troubleshooting steps; it tried (and failed) again.
Tried the latest HTC direct ROM, same result.
Tried to flash the latest HTC via MicroSD card, got 20(ish) percent through, the Radio line then went red and said "RSA Failure". Then that whole process died on me as well.
The only way I can get my device back up to run MTTY to remove the RUU flag. When issuing the "task 8" command to format, it instead reboots the phone. The phone will come up normally after that.
Since I got it back up, I have tried flashing once again, and am getting the same result. Am I just stuck here now?
It's not that I don't like this ROM, I'm just wanting to update the radio. Any ideas what else I might be able to try?
Try using the search function next time before you create a new thread.
If you would tryed you could find this post
Yes, thank you...except that I started my thread saying that the proposed solution was exactly what CAUSED the problem to begin with. I tried to flash to the 1.70.x radio, which is where I got the flash write error.
Anyone else?
Now that you can get it up normally, have you tried going to a stock HTC ROM first, then the new ROM, then the radio? Or HTC, radio, new ROM? I'd probably do it the second way. You said you tried flashing stock before getting it up again, and that you tried flashing after getting it back up, but you didn't state what you've tried flashing after getting it back up.
Since I've gotten it back up, I've tried both OEM and radio only. Both have the same result.
Really at a loss now as to what to try next.
Did you try the 3.29Hard2 SPL? I haven't encountered your issue and wish I could be mroe help here. My only thoughts would be to try a different SPL, or perhaps looking into the ForceUSB issue. Best of luck.

SD Flash stuck at white "Loading..." screen

So, got my self in a bit of trouble today, here's the situation:
- Recently flashed TPC v11 Mega Edition, and had been using it for about a week. Ran across some problems with apps freezing, so I decided I should try to start fresh and reflash a stock ROM.
- Reflashed AT&T Tilt stock ROM (3.57.502.2) via my SD card (my USB is not working, and hasn't in a while).
- Flash seemed like it was going great, but when the phone rebooted the TPC ROM was still there, yet it showed an older radio had been flashed (1.27.14.09)
- Knowing that this wasn't a good situation, I thought I'd try to reflash again via the USB. Began the process, except this time the flash process was now stuck at white "Loading..." screen.
- Thinking it was possibly a issue with my SD Card, I tried reformatting the card with FAT32 and recopying the KAISDIAG.nbh and ROM. Didn't work
- Tried copying a different ROM (TCP V11, a new RADIO, HardSPL 334... didn't work)
Unfortunately, since my USB doesn't work, I don't have an alternative way to flash the device. Surprisingling the TPC v11 ROM and the old RADIO seem to function somewhat, so the device is usable, although it seems as if I'm now stuck with this ROM for good. Also, audio seems not to function now... an unfortunately side effect. I can only assume this is related to the old Radio.
Any ideas as to why my flashing issue might be? ...thanks in advance.
Please consult STICKYs.
Several ways to get around this:
Put the phone into bootloader flash via SD or even computer as dosn't need to sync when in bootloader.
The issue you have with sound is that the stock ROM has a radio so therefore you now have an old radio.
To Flash via SD the ROM file name is KAISIMG.nbh.
Hope this helps any more problems please use a thread already available [Resources] Flashing Your First Kaiser Rom (For Noobs)
Thread closed.

No x7510 ROM flashing for me. Help!

I previously loaded 3.29.xTep_3.00 with hardspl 3.05. It's been running fine, but I wanted to try some different ROMs so downloaded several. None will work. No other versions of hardspl either. no radio upgrades/downgrades either. Everything is fine until I get to the gray load screen with the % of progress. It gets to 1% then bails. PC returns "ERROR [270]: UPDATE ERROR The Image file is corrupted. Please check your update utility." I have tried on 3 different PCs, reformatted flash drive and internal storage, removed all cards.. not sure what else to do. Can't find directions anywhere for MicroSD flash for the x7510 or i'd try it. Only thing odd about my device, besides this, is that the GPS stopped connecting to satellites several months ago (another bummer). Any ideas?
I got this result when I just removed the minisd card and didn't remove the cardadapter. Once I had removed the adapter everything was fine but you have probably done this so... I don't know what to tell you. Second time I flashed I remembered the procedure wrongly and I kept putting the phone into bootloader mode before I flashed I ofcourse got the same lack of result then, once I flashed from windows not bootloader everything was fine.
Thanks teacher1960, I have made sure all cards/sleeves/sims etc are out. Not loading from boot-loader, etc. Sadly, just screwed I guess, when it comes to ROM experimenting. The ROM currently running is the best of all i've tried, so my heart is a-pining, but not destroyed. If anyone knows how to boot from an SD card (I have a 2 MB non-SDHC card that I used to flash my TYTN2 with) I would love to know the steps. Thanks again.
I would try to SPL back to stock-SPL and then start all over again.
As being explained here.
dumbquestion said:
I previously loaded 3.29.xTep_3.00 with hardspl 3.05. It's been running fine, but I wanted to try some different ROMs so downloaded several. None will work. No other versions of hardspl either. no radio upgrades/downgrades either. Everything is fine until I get to the gray load screen with the % of progress. It gets to 1% then bails. PC returns "ERROR [270]: UPDATE ERROR The Image file is corrupted. Please check your update utility." I have tried on 3 different PCs, reformatted flash drive and internal storage, removed all cards.. not sure what else to do. Can't find directions anywhere for MicroSD flash for the x7510 or i'd try it. Only thing odd about my device, besides this, is that the GPS stopped connecting to satellites several months ago (another bummer). Any ideas?
Click to expand...
Click to collapse
Greetings,
i have the x7510 for more than 2 years, may be since i joined xda-developers and since that time i have been trying to upgrade it from 6.1 to any given cooked room. i have tried your roms several times but each time it ends with error. every thing goes smooth till it reaches the tri-color where it shows spl 3.05.0000 then screen goes wight with 1% only then it reboots and on the desktop it gives the following message:
ERROR 270: UPDATE ERROR
the file is corrupted, please check the update file
i remeber i posted several times with no reply
would you please help me to solve this problem, please

Categories

Resources