Tilt Bricked? - Tilt, TyTN II, MDA Vario III Windows Mobile ROM De

Possibly the fastest phone brick in history... I did everything wrong...
AT&T Tilt, Windows Vista host machine
I ran the SSPL, NOT the Hard-SPL...
16% thru it failed
Rebooted, tri color screen, but not the same extact screen I had seen after running the SSPL on my Tilt.
Hard Reset, said yes take me to factory settings, back to same tricolor screen
Plugged it into a XP box, drivers installed, plugged in USB (it shows USB connection on the screen) Activesync of course wont go green
Loaded both the Kraiser rom and the Cingular rom, both fail at 1% and reboot the device and same invalid device ID..
Any ideas, aside from I'm a r-tard?

I ran the Hard-SPL on my HTC and it worked as it should. I'd say give that a shot, THEN try flashing the ROM of your choice.
-Mc

Problem is, when I run hard spl it expects activesync to be running, but in bootloader mode AS doesnt connect so Hardspl wont load =/

- Disable activesync usb connections
- Connect to bootloader with mtty and type the following commands to know your CID and Model ID:
Code:
Cmd>task 32
Cmd>info 2
Cmd>getdevinfo
Paste the output here, and also tell me which SPL version you have on your device.
Also, does the tri-color shows "RUURUN" or similar in the screen?
You should flash a ROM matching your CID to fix it.

Cmd>task 32
No card inserted
Level = FF
Cmd>info 2
HTCSCWS__001Ùü¤HHTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1*00CS_0HTCE
Cmd>
Device screen says
RUUNBH
KAIS1*0
SPL-1.56.0000
CPLD-8

Flash this ROM, should bring it back to life.

I'm leeching it now, 40% done, also FYI, I've posted on the Official ROM forum new links to most utilities and ROMs hosted on my servers off the rapidshare, to share free of charge.

Ahh, life saver =) Thanks, I'll be sure to add that rom to my list of full Kraiser roms on my web server, now to correctly flash it back with the HTC rom.
Thanks!

Same problem as TS. Bigger problem ... does anyone have the Dutch ROM?
Tnx!

I got the same problem as Palmore. After 16%, stuck, then bricked. I am downloading the ROM pointed by POF (thanks man!!) hopefully will unbrick it. Now, how do we get the HTC Kaiser ROM on this thing? Anyone?

It's on my phone. Tell me how do dump it and I ll send it to you.
Wouter
Lukstra said:
Same problem as TS. Bigger problem ... does anyone have the Dutch ROM?
Tnx!
Click to expand...
Click to collapse

ludovich said:
I got the same problem as Palmore. After 16%, stuck, then bricked. I am downloading the ROM pointed by POF (thanks man!!) hopefully will unbrick it. Now, how do we get the HTC Kaiser ROM on this thing? Anyone?
Click to expand...
Click to collapse
Run the Hard-SPL utility on your PC, and follow the instructions (sticky on this forum)
It will allow you to flash any ROM after that, I've flashed the AT&T Rom, the HTC rom and back and forth, pulling cabs out of the AT&T rom for the items I like (IM utility etc)

Palmore said:
Possibly the fastest phone brick in history... I did everything wrong...
AT&T Tilt, Windows Vista host machine
I ran the SSPL, NOT the Hard-SPL...
16% thru it failed
Rebooted, tri color screen, but not the same extact screen I had seen after running the SSPL on my Tilt.
Hard Reset, said yes take me to factory settings, back to same tricolor screen
Plugged it into a XP box, drivers installed, plugged in USB (it shows USB connection on the screen) Activesync of course wont go green
Loaded both the Kraiser rom and the Cingular rom, both fail at 1% and reboot the device and same invalid device ID..
Any ideas, aside from I'm a r-tard?
Click to expand...
Click to collapse
If you are a r-tard, it must be catching - same situation here at 16% and 1% now......

andydempsey said:
If you are a r-tard, it must be catching - same situation here at 16% and 1% now......
Click to expand...
Click to collapse
LIFE SAFVER

nispen said:
It's on my phone. Tell me how do dump it and I ll send it to you.
Wouter
Click to expand...
Click to collapse
Hi Wouter,
I bought a new Kaiser today (yes now I have two of them ).
I will see if I can dump the Dutch ROM myself and see what happens next.
Thanks for your help anywhy!
- Lucas

Bricked
Ok, so here is my situation. I have a Tilt and Vista.
I ran HardSPL and I am at the tri-color screen. I have:
KAIS1*0
SPL-1.JumpSPL
CPLD-8
USB (in the middle of the screen)
I tried disconnecting and reconnecting it several times. I cant get HardSPL to run again (it hangs at the first section looking for ActiveSync) I tried restarting Vista several times. I can NOT turn off my device, as holding down the power button does not appear to work.
I have tried just running a couple of .exe roms (AKU 0.7.0 ROMS) and I get the connection error [264]. I cant re-establish my ActiveSync connection. In device Manager I have Microsoft USB Sync for the mobile device, but I cant get ActiveSync (Mobility Center) to see it.
I have tried opening MTTY to run "boot" but it says USB Port Can NOT be opened.
I just need some direction here, as it seems like everything hinges on my ActiveSync connection. I have been up and down the Wikis for Hermes and all the similar ones, and I think I am SOL.
I WILL GLADLY DONATE if thats what it takes for someone to help me. Thanks guys, I cant wait for my HTC Rom to work.

Vista Problem.
First off, i had the same problem as you so i just found an XP box to use.
Second, even with XP i still managed to **** up because i did not read the directions all the way through. This device is totally different so make sure you read all the directions.
If you have no access to an XP machine then u can just "obtain" a copy of XP and dual boot just for flashing your device.
If you have no idea what I am saying then read some more. the hermes forums have some great information when it comes to flashing via Vista.

For all you guys that just saved between $300.00-$500.00. How about sending POF like %5 or %10 of what he just saved you...
I'm just sayin'
Later, Lew

Have you installed the XP activesync drivers under Vista? The Hermes Wiki mentions somewhere how to do that.
Jabbs19 said:
Ok, so here is my situation. I have a Tilt and Vista.
I ran HardSPL and I am at the tri-color screen. I have:
KAIS1*0
SPL-1.JumpSPL
CPLD-8
USB (in the middle of the screen)
I tried disconnecting and reconnecting it several times. I cant get HardSPL to run again (it hangs at the first section looking for ActiveSync) I tried restarting Vista several times. I can NOT turn off my device, as holding down the power button does not appear to work.
I have tried just running a couple of .exe roms (AKU 0.7.0 ROMS) and I get the connection error [264]. I cant re-establish my ActiveSync connection. In device Manager I have Microsoft USB Sync for the mobile device, but I cant get ActiveSync (Mobility Center) to see it.
I have tried opening MTTY to run "boot" but it says USB Port Can NOT be opened.
I just need some direction here, as it seems like everything hinges on my ActiveSync connection. I have been up and down the Wikis for Hermes and all the similar ones, and I think I am SOL.
I WILL GLADLY DONATE if thats what it takes for someone to help me. Thanks guys, I cant wait for my HTC Rom to work.
Click to expand...
Click to collapse

Best Forum Ever
I
I got it working. I had to pull the battery out of the phone to get it out of bootloadr, it was just plain stuck. Then, in Vista, I needed to F8, disable driver enforcement, I replaced the wceusbh.inf in device manager, and relaunched HardSPL and there she was! Now for the BigStorage.
Thanks to all that helped, I will be donating pof for sure

Related

Prophet stuck in bootloader HELP!

1st off I DID use the search button.... 2nd HELPPP ME!!!
Waaah :'( I have a most intriguing problem I was running pdaviet 4.0.0.6 Touch for almost 2 weeks now without a single glitch.. the phone fell on my carpet and went to bootloader screen and eversince then it has never recovered I tried a hard reset it didn't work when I was pressing the send button it did nothing I did some forum searches and tried putting back the nvid RUU and it said that the update was succesfull and the progress bar on the phone moved accordingly but it went back to the bootloader screen ... then I tried pdaviet temp rom that was in the package still no go I can tell it works somehow because the USB lights up in the bottom left when I plug the usb cable and the progress bar that moves, but I'm getting desperate IPL and SPL info is in my sig...
same same... but i dropped mine before flashing the new PDAVIET touch rom.. still went fine..
now, it still flashes... RUU says its successful.. but PDA just reboots back to bootloader..
i can charge my phone fine in bootloader.. i can see the USB come on when i connect it to my computer.. other than that, can't do anything...
i've tried everything the past 2 days.. looks like i'll have to send it back to dopod.. will let u guys know what happens... probably something got damaged..
struck at bootloader
I tried WM6 (4.0.0.6 touch) from WM5 AKU 2.2 but it failed in between with some write message,which was bit strange as I didn't touch any key on laptop during that time and no program was being run at that time. (I am using VISTA Home premium). I got my phone into bootloader but it does not connect to my laptop...so cant upgrade back to AKU 2.2. In Windows Mobile Device Center, I cant see my device connected. So is it particular to Vista or my phone got bricked?
I am yet to try on Windows XP, which I have to arrange.
Please advise.
i had the sam problem.i installed this : try to install the 2.20 nvid rom
just go into bootloader mode-you dont need active sync connection and start the upgrade-search for 2.20 nvid rom download it and recover your device
charliess said:
i had the sam problem.i installed this : try to install the 2.20 nvid rom
just go into bootloader mode-you dont need active sync connection and start the upgrade-search for 2.20 nvid rom download it and recover your device
Click to expand...
Click to collapse
I tried the same but when I run ROMUpdateUtility_No_VenderID, I get a message 'Update Error, 260' which tells further that PDA is not connected to laptop., although it is very much connected. However LED on PDA does not blink as well.
When I plug in this phone to Wall adaptor, LED does show up.
'USB' appears at Bottom Left corner of PDA when connected to laptop and certainly its getting recognised by Vista as it starts installing Driver as soon as this is connected to laptop.
Please suggest.
I am stuck in the same situation, although I have a G3, running 2.20 on IPL & SPL
Working now
I tried on XP (I was trying on vista before)..I had to install Active Sync as it was not installed on that PC, then run RUU update for AKU 2.2 and update was successfull. Now will try Touch 4.0.0.6 again but this time on XP.
Hope this time I wont have any problems.

Help, Help, HTC Touch Diamond nearly dead

I have an ex-Vodafone, sim unlocked HTC touch diamond and it won't turn on. All I can do is bring it into the tri-colour screen/bootloader. When plugged into my computer the phone screen goes from serial to usb, but thats as far as it gets. Communication with activesync is no longer possible. I have no idea what to try now, I've gone as far as my non-technical mind will go ! help
I'm in the UK. Phone info;
Duttys V2.7 RC2 WWE - 27/10/08
Radio 1.08.25.08
P3700
Bootloader screen reads;
DIAM 100 MFG 64M
SPL 1.40 Olinex
MicroP- Diam (LED) v11
PSOC - Diam STAGE_PVT v0x30
Welcome to forums
Please have a deep read here:
http://wiki.xda-developers.com/index.php?pagename=HTC_Diamond
You´ll find all needed to do a succesfull reflash.
Good luck,
no comms with activesync
thanks for the link. have read the info on flashing my device but my phone no longer communicates with activesync. Is it bricked ? Phone won't go beyond initial 'vodafone' startup screen. i don't know what to do now.
which os in computer do you use ??? if in tri-color boot loader, pc only recognized the HTC driver device, but Activesync won't show the connect. You understand what i mean? Go Flash yourself your device with successfully, I will pretty sure that your device doesn't brick.
yes correct you can run the RUU wrapper while the phone is in the boot loader and itll still flash the rom
i use windows xp home sp2, i don't understand the flash process and can't get further than the tri-colour screen. I think i need a very simple step by step walkthrough if I'm to get any further !
ok
down load the rom of your choice and exract it
in the folder there should be a file called ruu_signed.nbh and a exe file called RUU wrapper or something like that if it doesnt come with the RUU wrapper it should be able to be downloaded from a stickied thread at the top of the diamond rom forum
then u need to connect ur phone to the pc while its in the boot screen the click on the ruu wrapper in the file on the pc and it should install on ur phone
hi, i downloaded the ruu, then connect my phone in boot screen, start the install, it asks me to make an activesync connection. activesync no longer finds my phone so no connection is made. i got this close, what now ? thanks for the help !
Done it finally
after many dime bar moments and weeks of annoyance the touch diamond finally came back to life. expecting this phone to actually work as advertised turned out to be a bridge too far. cheers for the help.

Dash3G (Maple): SSPL, HardSPL and original SPL by JockyW

Attached you find all you need to flash cooked ROMs on your Dash3G (Maple).
The sspl/hardspl are confirmed to work fine on the HTC Maple platform (Dash3G, SNAP S520, SNAP S521). Any phone that says MAPL1XX under the battery should work just fine with the sspl and hardspl. This has been tested by oOkBa yesterday night. His cooked roms flash extremely fast and he noticed no problems except for the splash screens. Apparently HTC changed the format slightly. Should be easy to tackle and has nothing to do with the sspl/hardspl.
Now for the bad news ... It will not work on the HTC Cedar platform (GSM/CDMA, HTC Ozone XV6175, Verizon). Running the sspl on an Ozone will definitely brick it. Also the HTC Willow platform (SNAP S511, Sprint) is not supported. Please see this post for more info and how you can help.
There are 2 packages both contain a SSPL, HardSPL, patched ROM updater and the original Maple SPL. The first package is based on SPL 1.17 (tested by oOkBa) and the second is based on SPL 1.19 (tested by Gawain1986)
Instructions:
1. remove SD and SIM cards (don't forget otherwise the sspl is likely not to work!!)
2. connect your device to your pc with a USB cable and wait until it is synced
3. extract the file "Dash3G HardSPL by JockyW.zip" and execute "auto.bat"
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "1.17.hard")
5. if you have difficulties to install 1.17 then try 1.19
6. to test the sspl and the hardspl you can flash the attached splash.nbh
Once the HardSPL is installed on your device you can flash any Maple cooked or original ROM.
Have fun,
JockyW
Excellent work!! JockyW is the man! Please donate to a great cause! This now opens the door to amazing possibilities! Thank you thank you!!
ookba said:
Excellent work!! JockyW is the man! Please donate to a great cause! This now opens the door to amazing possibilities! Thank you thank you!!
Click to expand...
Click to collapse
couldnt of said it better myself..
oo..
my Snap 526 is MAPL110..
should i gib it a shot?
but i need a plan b in case something goes wrong.. any idea how to hard reset the snap with the scrollball?
I have the same mapple, ithink it's ok.
before running this file, do we have to dump the rom? and do we have to use the spl backup kit berfore?
(sorry for all these questions)
First of all, there's really no need to run this yet until there are custom ROMS to flash. If you want to simply test or prep, go for it. I can confirm it works in a MAPL100 so I don't see why any other device with MAPL1XX should be an issue. I will build some factory ROMS as well as some custom cooks in the next days for you guys to play with and test.
see i dont think alot of the new people understand the process.
the spl does nothing more than ENABLE ur device for a rom, thats it!
nothing fantastic, its not a completely diff o.s. on ur device..just preps it for whats to come.
what happend with my device today was a fluke!
i was testing and working at the same time..i could have missed a step, one of my work programs on my laptop could have set something off..i dunno.
Bricking usually isnt a part of getting a SPL for a device..just ALOT of testing. SO now is the another part of the process..the waiting process. Waiting for a rom cooker to successfully establish something, test it, and release it.
in this game..u need patience.
So I;ve been trying this and it seems something is going wrong...
Ik run auto.bat, JumpSPL gets copied and started, the device screen goes black, and when I reconnect the USB cable to get the "Smartphone Sync" driver working, my Windows 7 install tells me that there is something wrong with the USB device.
It will then refuse to use any driver I try to add to the device.
Any thoughts?
PS. It's a SNAP S521 (MAPL110)
EDIT: Windows XP x64 has the same problem.
Gawain1986 said:
Ik run auto.bat, JumpSPL gets copied and started, the device screen goes black, and when I reconnect the USB cable to get the "Smartphone Sync" driver working, my Windows 7 install tells me that there is something wrong with the USB device.
Click to expand...
Click to collapse
First, this has not yet been tested on Win7. Second, it should not be necessary to unplug and replug the cable. Try again and just wait a minute or so to allow Win7 to install the driver. Other thing you can do to make sure the driver is already installed is to put the phone in bootloader mode and connect it by usb cable.
ps: it is normal the display turns dark after running the sspl
ok, i understand there are 3 steps. but I would like to know how to do the first one:
dumping my rom.
First I entered the bootload by holding the volume down button and turning the device on...
It said:
Code:
MAPL110
SPL-1.19.0000
MicroP-Maple (LED) v6
ENGID 0x2
PCBID 0x80
PanelInfo 15-0x2
I connected it to the computer and it recognised the Qualcomm phone immediately and settled on the HTC USB Sync driver.
Then I restarted the phone and connected it again, ran auto.bat... it ran SSPL again and I waited.
So after I tried waiting for 5 minutes, WIndows 7 did not see a new device, it stayed with it's normal RNDIS driver.
So I took the plunge and ran the RUU, which told me it could not connect to the phone.
I unplugged the phone and replugged it and it said there was an error regarding the USB device.
Can it be that because my SPL version is higher than the HardSPL or SSPL, that it's getting into conflict with itself?
Hi,
First thanx for your hard working.
I got some trouble when trying to install the Hard SPL.
My SNAP from france, S521 Mapl100 under the Battery; Just HTC no operator
I launched the auto.bat
The device display turned dark and tri-color bootloader screen said "1.19.hard
The flashing process start and stuck at 0%
Unplugged the USB and the phone restart well.
Is this Hard SPL
Enter bootloader. If you see "1.17.Hard" the HardSPL is succesfully installed and you can flash any cooked and official roms in the near future.
Fabtwone said:
Hi,
First thanx for your hard working.
I got some trouble when trying to install the Hard SPL.
My SNAP from france, S521 Mapl100 under the Battery; Just HTC no operator
I launched the auto.bat
The device display turned dark and tri-color bootloader screen said "1.19.hard
The flashing process start and stuck at 0%
Unplugged the USB and the phone restart well.
Is this Hard SPL
Click to expand...
Click to collapse
Gawain1986 said:
Can it be that because my SPL version is higher than the HardSPL or SSPL, that it's getting into conflict with itself?
Click to expand...
Click to collapse
Please first try it on WinXP before we draw wrong conclusions.
Good work jocky - nice to see you about again
Thread Stuck.
Dave
jockyw2001 said:
Please first try it on WinXP before we draw wrong conclusions.
Click to expand...
Click to collapse
Did that immediately after I posted... it just keeps telling me the USB device is "malfunctioning" somehow...
Gawain1986 said:
Did that immediately after I posted... it just keeps telling me the USB device is "malfunctioning" somehow...
Click to expand...
Click to collapse
Ok, if there are similar problems i can try to build a sspl based on 1.19
Please dump it and attach (see first post for the link to the dump kit)
To anyone who has problems, please look up your current SPL version.
(press volume down and power on).
Is there anyone who succesfully flashed the HardSPL where the old SPL version was 1.18.00 or higher?
jockyw2001 said:
Ok, if there are similar problems i can try to build a sspl based on 1.19
Please dump it and attach (see first post for the link to the dump kit)
Click to expand...
Click to collapse
Here you go...
http://www.mediafire.com/?sharekey=cb564520d236e90090a82c7bb0fad7ade04e75f6e8ebb871
Gawain1986 said:
Here you go...
http://www.mediafire.com/?sharekey=cb564520d236e90090a82c7bb0fad7ade04e75f6e8ebb871
Click to expand...
Click to collapse
Try the attached sspl which is based on your v1.19 SPL.
Run sspl.bat (preferrably in XP)
I'm sorry, but the new 1.19 SSPL is not working either. The phone stays in the black screen and both Windows XP x64 and Windows 7 x86 keep telling me the USB device is malfunctioning.
I have had some experience with unlocking my previous Tornado, VOX, Kaiser and X1 and I'm pretty sure I need to see a tri-color scren when invoking JumpSPL.
So maybe that's the problem?

Possibly being a very blonde female :'( HALP!

I'm normally good with stuff like this ^_^
Not today though
I promise, I followed the instructions to the letter, trying to install WM 6.5 on my phone (S710). I did the USPL thing first, then basically did the exact same thing with the files I got from the WM6.5 "Official v1.0" thread. Is that the right version of WM 6.5?? I'm a bit lost. So I feel like I did the USPL stage twice.
Now here's where things get weird.
When I get to the RUU stage, ready to install - activesync stops recognizing the phone. Says it's not connected. The RUU however sees the phone, but shows blank for the current installation. I press 'update' and both the phone and the RUU go to 100% in about 2 seconds (so obviously it's not doing much).
I reboot the phone and it's like nothing ever happened. Back to my crappy version of windows (infested with my stinky network's own software).
Have I given enough info? What am I doing wrong? Should I start again from the beginning? If so which files should I have and like I said :'( what am I doing wrong?
Epic love and hugs to anybody that can help
x
i've had a problem similar with this. make sure the uspl is done properly. and you must run SDA_ApplicationUnlock.exe first. then uspl: uspl_116_jockyw.bat, after all done, phone will have black screen, run ROMUpdateUtility.exe from uspl folder. (the tutorial is in the archive of uspl). aftel all that install new rom. i have wm6.5 official v1.0 too, work fine.
oh, you may try to start flashing from bootloader(turn off phone, keep the camera button pushed, and insert usb cable)
fuggerboo said:
I'm normally good with stuff like this ^_^
Not today though
Click to expand...
Click to collapse
MS has added "exchanced ...." checkbox in USB to PC connection - just disable it (uncheck).
when checked - works only with synce on linux but not with activesync on XP
m32

[Q] Connection Error

dear all,
first at all: I´m completely new here, so hello.
I finished reading the Wiki twice, also the guide from 'mskip' (Flashing your First GSM Raphael Rom (For Noobs)). very good and sounds very easy.
now I downloaded this file: RaphaelHardSPL-Unsigned_190_1_3
when I´m trying to flash, it results in a "error 202: connection". could the windows mobile device manager be a reason, because here is just an explanation with activesync. as I use win7 64bit, activesync will not run.
I also checked lots of posts here, but did not get a right answer which could lead to a solution.
btw I have the "MDA Vario IV"-version.
greetings, tris
EDIT:
Update: Now I downloaded "TAEL ROM v6.28244 RC2".
Connected mobile to PC, waited until it is connected via 'windows mobile device manager'.
Proceeded with the update (my image is 1.69.111.6) until the screen turned black and a progress bar is shown (0%). now error 262 appeared. have to unplug USB cable, reinstall battery and restart. old system is still working. what am I doing wrong? btw, same error on my laptop with win7 32bit with fresh installed 'windows mobile device manager'.
EDIT2: okay, and same on my other laptop with winXP and activesync.
You need to flash hard spl before doing anything else. Try putting the phone into bootloader (hold volume down, then soft reset), then connect it to your PC once it's in the tricolor screen and run the hard spl exe.
After that, just flash roms off your sd card. Make sure it's FAT 32 format, rename the ruu_signed.nbh to RAPHIMG.nbh, put it on the sd card root, and then go into bootloader and follow the instructions.
volume down and reset done. phone switched to tricolor screen. then I started 'RaphaelHardSPL-Unsigned_190_1_3', phone switched to gey screen with progress bar. 30 seconds later after 0% progress: error 262 appeared
EDIT: also when trying to update via bootloader, my image (1.69.111.6) will be left blank, I can´t see the version number which is currently installed.
I just hope you have a GSM TP/RAPH...
RAPH300 -> "T-Mobile MDA Vario IV"
but why do you ask? do I have the wrong software?
Just hear of those bad incidents with CDMA phones and GSM ROMs is all...
What does it display on the bottom of the screen when you boot into the tricolor screen/bootloader before you connect it to your PC and then after?
first serial, later USB
oh my god! *facepalm* okay for all the noobs out there: look at your phone. if you use HardSPL for the first time, you have a short timeframe to confirm "unsigned access to bootloader" via touchscreen. if you don´t do so, you will result in connection error 202 / 262.
thank you all, it works

Categories

Resources