Earlier today my ATT Tilt was having trouble synching to my office system; it would charge, but it would not be recognized by Active Sync. I had been planning to flash the new HardSPL tonight anyway, so I thought I'd check different cables on the home system while I looked to update the SPL.
When I got it home, none of the cables or other systems would change the basic problem: the unit would charge, but the device would not be recognized. I tried soft resetting it, but that did not help. I thought I'd try taking the battery out, then try a hard reset.
After taking the battery out, the system went straight to the tricolor boot loader, with "serial" underneath. The micro SD card it had in it wasn't formatted for FAT32 and didn't have an image on it, so it just stuck there.
I removed the microSD card.
I then tried plugging in the USB cable (which does change the screen from serial to USB), but attempting to flash a ROM still fails, as the USB connection still seems to be dead for that. Hard reset does not change this; it goes straight to tricolor.
It didn't seem to be charging on the usb or on the charger (no yellow light), so I also I removed the battery so as not to waste any remaining charge.
My current theory is to get another SD card in the morning, format it with FAT32 and see if it will flash a rom. Any other, better ideas?
Since I had the (v1) HardSPL on it with one of Dutty's ROMs, I am a
bit afraid to send it in for warranty replacement repair, at least until
I can restore it. But if I can't get anything to it, it's going to be a bear
to get through the diagnostic update to restore the original rom.
If I am missing anything obvious to try here, I'll glad take the noob points, but I'm stuck for better ideas.
Thanks for any thoughts.
Mtty doesn't work
Meant to mention that mtty.exe doesn't work through USB.
No Joy with sd card, hmm
So, I re-formatted the SD card, put an image on it, and it was recognized. It loaded the radio and OS, gave a success message and stayed on the white screen. I did a soft-reset, according to the "Flashing with SD cards" instructions, and it returned me to the boot loader and offered to re-run the install. I did that (why not, I guess?), and it did the same thing.
This had been Hard SPL'ed, but I'm trying a return to the stock ATT rom now. Any other thoughts much appreciated.
<edited>Same thing happens with the stock ATT rom. If I load it via SD card, it reports success, but a reset returns to the tri-color screen if the SD card is taken out and to the "loading" screen if it is not.
Hey there,
It seems I have a similar problem as you. A few days ago, I wanted to install this rom:
http://forum.xda-developers.com/showthread.php?t=392245
There was a hardSPL with it. Copied it to my device, ran it (went into tricolor mode, so that's good). From there, I wanted it to flash it, but my laptop didn't recognize my Kaiser anymore. Soft-resetted the thing, went back into windows mobile.. good. Bu from that point, my laptop didn't recognize my Kaiser anymore, it just charges the damn thing..
EDIT:
Laptop now recognizes my phone.. when updating, the screen freezes on the white screen with the percentage bar (how many % is done flashing the romd)
damn.
moos said:
Hey there,
But from that point, my laptop didn't recognize my Kaiser anymore, it just charges the damn thing..
EDIT:
Laptop now recognizes my phone.. when updating, the screen freezes on the white screen with the percentage bar (how many % is done flashing the romd)
damn.
Click to expand...
Click to collapse
That does sound bad, too. When you were getting the tri-color screen were you still showing the old SPL or the new one?
And what, if anything, changed when the Laptop went from charging to not recognizing the phone?
I have had some issues with getting usb to recognize in the tricolor screen. In my latest spl flash, it took about five trys to get it to work, you have to be persistent some times.
Anyways the steps to get it recognized are as follows:
1. I plugged the phone in, (with the os booted, you can't do this obviously) and waited for activesync.
2. Went into bootloader mode, in the tricolor screen it said I had USB, but I was never able to flash.
3. Disconnect the usb while in tricolor, and wait about 15 sec and plug it back in.
4. I waited for about a minute, the tricolor screen never showed USB on it again, however it worked.
Im hoping that will help you a bit, just try to unplug and plug the usb back in. Good luck.
edit: is it showing olipro 1.00 or similar in the tricolor screen? That would be HardSPL if it is.
Use task Manager to make sure that there is not a current session of activesync running on device before plugging in. If there is kill it & try again.
I have recently had very good luck in helping others with this situation, but it is a detailed process best done over IM & takes at least 45 minutes to an hour to complete. I have a bit of a reputation for saving Kaisers. At any rate, try a few of the suggestions above, then if all else fails PM me & I'll see when I have some time.
Speaking_On said:
That does sound bad, too. When you were getting the tri-color screen were you still showing the old SPL or the new one?
And what, if anything, changed when the Laptop went from charging to not recognizing the phone?
Click to expand...
Click to collapse
At this point, the tricolor screen is showin the following:
KAIS130
SPL-1.JUMPSPL
CPLD-8
I already got my laptop to recognize my phone, just gave it a reset. I'll update as soon as my phone is over 50% of charge.
i had the same problem with my usb port...
I have just been flashing roms from microSD but I am stuck with radio from hell with no way to change it without usb connection
i also wanted to flash a new spl but have read that it is not recommended to do so from sd card.
not sure if its a hardware or software problem, in either case, it is a problem with the phone, i have tried it on many different computers with many different cables and i also tested my brothers tilt which is detected by each computer immediately.
rcm_rx7 said:
4. I waited for about a minute, the tricolor screen never showed USB on it again, however it worked.
Im hoping that will help you a bit, just try to unplug and plug the usb back in. Good luck.
edit: is it showing olipro 1.00 or similar in the tricolor screen? That would be HardSPL if it is.
Click to expand...
Click to collapse
Thanks for your message. The phone is showing olipro (I had flashed it with HardSPL before all this started; I was getting ready to update it to the new HardSPL for WM6.1 ROMs). I've tried a couple of different cables and the usb seems truly gone. I have had problems with it being a bit sensitive in the past, so I think the pins have just shorted at this point.
All else has failed...
GSLEON3 said:
Use task Manager to make sure that there is not a current session of activesync running on device before plugging in. If there is kill it & try again.
I have recently had very good luck in helping others with this situation, but it is a detailed process best done over IM & takes at least 45 minutes to an hour to complete. I have a bit of a reputation for saving Kaisers. At any rate, try a few of the suggestions above, then if all else fails PM me & I'll see when I have some time.
Click to expand...
Click to collapse
Thanks for the message. There aren't two activesync sessions running on the XP system, and there are none on the phone (as it is stuck in bootloader, there is no way to get to its task manager).
After calling in to ATT and finding a fairly knowledgable tech (Ben, no last name given), it sounds like the original problem was that the mini usb slots has bent pins which caused a short. Somehow, when I removed and re-installed the battery, that short went from preventing a synch to toasting the OS. My first Tilt had a red-light of death on first charge, so I pretty much believe that something in the electronics connecting the usb/charger and battery is delicate on Kaisers.
They're going to send out a warranty replacement tomorrow, and the RMA packaging for returning this unit. I guess I'll just cross my fingers that they don't boot it and notice that it isn't a stock SPL. Given that it's being written up as a hardware issue (as it is), hopefully they won't.
What could they do after you get the new one? Charge you for it? Guess you never know with ATT.
Since your sending it back anyways, why not try to flash the SPL from the microSD? You might be able to revert it back to the stock ATT spl, then no worries right!
I think I got it..
This is what I did. I followed the following steps from the first post:
http://forum.xda-developers.com/showthread.php?t=354061
Then I did the same thing, but I used the rom I wanted to flash. Now the first time it got stuck @ 17%.. but on the second time, I succesfully flashed my rom. Hope this helps!
Theoretically, yes
rcm_rx7 said:
What could they do after you get the new one? Charge you for it? Guess you never know with ATT.
Since your sending it back anyways, why not try to flash the SPL from the microSD? You might be able to revert it back to the stock ATT spl, then no worries right!
Click to expand...
Click to collapse
I did try flashing the SPL from the microSD, several times and using the stock ATT SPL was one of the choices. It reverted back to tri-color boot mode.
Theoretically, yes, they could demand payment. I've heard of them doing that if a customer said that a unit hadn't been wet, but they found that it had when they did diagnostics. Down from that, they could terminate the warranty or shut off service. Now that T-mobile is getting higher speed, that's not the threat it once was, but still.
The battery is now also empty (since it had no way of charging), so I am hoping they won't even bother.
Glad to hear it!
moos said:
This is what I did. I followed the following steps from the first post:
http://forum.xda-developers.com/showthread.php?t=354061
Then I did the same thing, but I used the rom I wanted to flash. Now the first time it got stuck @ 17%.. but on the second time, I succesfully flashed my rom. Hope this helps!
Click to expand...
Click to collapse
Glad to hear it worked for you! I couldn't get my system even close to that functional to get there, but it's good to know that you were able to get through.
kaiser usb dead
I have the same prblem as your USB is gone cannot move from tricolor screen. Cannot even flash from sd card. Check my signature for the link of my thread it explains everything that happened to it.
hello,
i'm interssested to buy it. can you send me your mail at [email protected]
Related
As i said on the title,suddenly i couldn't recharge my Universal anymore,yes i've tried with a brend new official battery as well but everything was in vain.As soon as i plug my charge to my Universal it appear a Red Led and after 3 min or so the led turn off and so the battery.
How can i fix this problem?!
Is there any chance?!
Is it really dead like that?!
Please HHHHHHHEEEEEEEEELLLLLLLPPPPPPPPPPPPPPPPPPP!!!!!!!!!!!!!!!!
If the battery is really brand new, then I guess the connectors might be damaged or the internal power buses might be broken somewhere. Have you dropped your device recently? Or did anything that might explain broken connectors or internal buses?
Nothing happened to my device and never felt down,it just happened suddenly!Now if i won't be able to fix this by myself this means a finger in da a.. cuz my warranty is expired!DAAAAAAAAMN
tetsuokaneda said:
Nothing happened to my device and never felt down,it just happened suddenly!Now if i won't be able to fix this by myself this means a finger in da a.. cuz my warranty is expired!DAAAAAAAAMN
Click to expand...
Click to collapse
It can be a software error. Have you tried hard resetting or installing another ROM?
tnyynt said:
It can be a software error. Have you tried hard resetting or installing another ROM?
Click to expand...
Click to collapse
That's the point!!!
I was trying to update to WM6 but something went wrong and stucked in boot load screen!Then my battery died but when i've tried to charged again i had that problem!!!
tetsuokaneda said:
That's the point!!!
I was trying to update to WM6 but something went wrong and stucked in boot load screen!Then my battery died but when i've tried to charged again i had that problem!!!
Click to expand...
Click to collapse
Your battery is fine, unfortunately your device broke
Unless you have a lot of specialized equipment at home, and the proper qualifications, there's no way in hell you can fix this. I'm sticking with my diagnosis, that either the power routing circuit broke down, or a power bus inside the device.
Really, your best off taking it back to the store, and paying for the repair. Either that, or buying a new phone, and selling this one for spares...
Sorry mate...
mzalan said:
Unless you have a lot of specialized equipment at home, and the proper qualifications, there's no way in hell you can fix this. I'm sticking with my diagnosis, that either the power routing circuit broke down, or a power bus inside the device.
Really, your best off taking it back to the store, and paying for the repair. Either that, or buying a new phone, and selling this one for spares...
Sorry mate...
Click to expand...
Click to collapse
I wanna die!!!I'm completely Fu.. up!!!
What a terrible news!I can't believe it!!!!
If i'll bring my phone to the assistant i'm gonna pay alot of money,at least 200.00 euro!!!!
similar problem
i had the exact same thing happen to my EXEC when i got 2 new batteries for it. One was a standard sized, pretty much the same as the stock one that came with the phone and one was a much larger capacity one that needs an extra cover for the back.
Id been using the device for ages on this huge battery and the charge said 100% constantly. then the device turned itself off and it wouldnt come back on. upon connecting the charger the LED was red, so i thought the battery was dead. I left it on charge over night and when i tried again the next morning it was fine.
this happens everytime with this battery, it just needs a much longer charge than the standard one, and doesnt register properly on the default OS, i havent tried it on my recent upgrade to one of the midget roms.
so try leaving it on charge over night or for a very long time. if all else fails just get a new battery.
That might reset the battery back to life, but I wouldn't exactly count on that. A battery with a broken monitor circuitry is pretty hard to reset.
My last hope,i'm gonna leave charging my phone for a day and then see what happend....I'm desperate
Permanent red light...
I had this problem, I put the phone on charge but forgot to put a battery in - spare phone... It wouldn't work no matter what I did , until I reformatted the DOC by following the steps in the WIKI.
wtpelzer said:
I had this problem, I put the phone on charge but forgot to put a battery in - spare phone... It wouldn't work no matter what I did , until I reformatted the DOC by following the steps in the WIKI.
Click to expand...
Click to collapse
Could u post it please?!
Took a while but here it is...
I did the task 28 55aa command in MTTY which should reformat the DOC alternatively you could reload the bootloader using the link below...
MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual.
If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself go to http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52
This link gives full instructions :
http://forum.xda-developers.com/showthread.php?t=289325&highlight=task+28+55aa
Hope this helps.
Same Problem, Led Indicator Always red
Hi,
We have the same situation, my jasjar just died in my hands, im reading a txt messages then al of the sudden it hangs, so what i did is reset it but it didnt power on, i removed the battery then after 10mins i put it back but then no power,then i charged it but it didnt power on too and the led indicator is always red, they say that if the indicator is red it means that there is no battery or the battery is missing but i check it thoroughly,the battery is perfectly place on the back of jasjer, i even tried to enter to bootloader but it cant. If anyone knows how can i revive my jasjar pls pls let us know....Thank you so much.
So sad till now there's no single solution.....
wtpelzer said:
I did the task 28 55aa command in MTTY which should reformat the DOC alternatively you could reload the bootloader using the link below...
MTTY with "task 28 55aa", "set 14 0", "set 14 9, "set 14 10" and "set 14 20" as described. bootloader screen may be replaced with a blank one, boot it on bootloader mode by "Backlight+Power+Reset"
http://wiki.xda-developers.com/index.php?pagename=Universal_Resets
now upgrade as usual.
If you stuck on the bootloader again after upgrading, try to upgrade the bootloader itself go to http://forum.xda-developers.com/showpost.php?p=1255206&postcount=52
This link gives full instructions :
http://forum.xda-developers.com/showthread.php?t=289325&highlight=task+28+55aa
Hope this helps.
Click to expand...
Click to collapse
Exactly if my Jasjar is completely dead how can i connect via usb and then use mtty?!
I'm losing my hope to bring it back to live!
have same problem - can do nothing, still waiting
but there is one thing - led flashes once, when i put the charger into the device - but it does nor light, nor flashes - exactly nothing happens
If your device is dead...
Well just to answer the question, if the battery is dead and you can't charge it because of a red LED. I suggest you buy a standalone charger from ebay and charge the battery or get someone else to charge it for you. Then follow the steps as I stated in my previous post...
wtpelzer said:
Well just to answer the question, if the battery is dead and you can't charge it because of a red LED. I suggest you buy a standalone charger from ebay and charge the battery or get someone else to charge it for you. Then follow the steps as I stated in my previous post...
Click to expand...
Click to collapse
The point is that the device is dead and that is why the constant red light. I have a device that is stuck on the splash screen (no solution in sight) and another that fell down and broke. The one that fell down does not power on. If you put a charged battery ang plug in the charger nothing happens, no light comes on, but if you put a discharged battery the red light comes on. I have a third Uni that I accidentally flashed with a BA rom. It is behaving exactly like the broken uni, it does not turn on, does not go into bootloader and the red light comes on when I plug in the charger with a discharged battery in it.
For some things, there's just no cure...
Okay I understand where you're coming from but essentially what you need to do, under normal circumstances, is connect it to your PC, which if the device is working at all the PC will detect it but not connect... In the case of two of your Uni's I don't think this will help - the dropped one and the BA ROM failure. The one with the Red LED, which has stopped working could be a component failure on the board or it could be a Corrupt DOC table. Now to get back to how you'd go about fixing it if it is a corrupt DOC table, when you connect it to the PC and the PC detects it you disable ActiveSync and start MTTY it should give you the option of connecting to the USB port, when it does this if you get a prompt the problem should be fixable because MTTY can "talk" to the device... As for the other's try this method and if it doesn't work sell them for parts or canabalise the one for parts for the other...
Hey guys...I recently upgraded my SDA to WM6 without any problems using Kar Hoe's guide. The only thing I noticed was that I couldn't connect to the internet via GPRS/EDGE (only WIFI). So I found a radio ROM last night and forgot to format BINFS before I installed it. It said it was successful of course but now I'm stuck in the bootloader. Here's the horrible part: The phone goes in USB mode for the bootloader, but won't connect to ActiveSync so I can't reflash it or anything! I really liked this phone and can't really afford another one at this time. I'd appreciate any help I can get.
Thanks. I'll be working until 5 but will check back after that!
p.s.: When I installed WM6 previously, I DID app unlock it and make it SuperCID.
-velcro
try mtty and and kar hoe`s guide
to Profy_X
Thanks for the quick response! I've downloaded mtty (similar to Tera Term huh?). Is it possible to copy the ROM image to the mini SD card in order to flash it? I have the original one for my phone and I tried copying the NBF file to the card via a card reader I have by Vakoss but windows won't recognize it. (due to its format right?)
I know I have too many questions but I need my phone. http://forum.xda-developers.com/images/smilies/confused.gif
Thanks again!
I have the same problem and really looking for a solution.
The phone enters bootloader mode after pressing the camera button and inserting the usb cable. However activesync or anything else does not recognize the device. mtty and teraterm cannot connect to the device.
When I hard reset or turn off/on the phone, it keeps resetting itself after a couple seconds of booting.
Any ideas what I can try?
I fixed it...
I tried everything! I ended up extracting this fileTor_TMOUS_10140_191916_10900_SHIP.exe with winrar and running the RomUpdateUtility. Even though ActiveSync wasn't working I went through with it. It randomly worked though! So then I just followed Kar Hoe's guide for installing wm6. Now the only thing is that it will turn off randomly unless it's plugged in. And it's not the battery though. lol 0_o
To Burkay: If mtty or teraterm can't recognize your phone then the only thing you can do is copy the original ROM to your memory card and then flash it directly from the phone through bootloader....or at least that's the only way I can see since USB's out.
After an unsuccessful rom flash, phone always stuck to bootloader screen, it happened 2 or 3 times on my phone. In these cases ActiveSync couldnot recognized my phone (thru USB). But I always successfully reflash my phone just running RomUpdateUtility connecting thru USB. How come so complex in your cases, I just wonder
unforsakenrule said:
To Burkay: If mtty or teraterm can't recognize your phone then the only thing you can do is copy the original ROM to your memory card and then flash it directly from the phone through bootloader....or at least that's the only way I can see since USB's out.
Click to expand...
Click to collapse
I agree. I just don't know how to flash from an SDCard. Do you have a tutorial?
burkay said:
I agree. I just don't know how to flash from an SDCard. Do you have a tutorial?
Click to expand...
Click to collapse
I don't...but if I find one I'll def let you know
thacen said:
After an unsuccessful rom flash, phone always stuck to bootloader screen, it happened 2 or 3 times on my phone. In these cases ActiveSync couldnot recognized my phone (thru USB). But I always successfully reflash my phone just running RomUpdateUtility connecting thru USB. How come so complex in your cases, I just wonder
Click to expand...
Click to collapse
Well...It might just be my battery after all (current surge or something). Because I tried 2 different wm6.1 roms and now am using Nitro's wm6 rom, and the same thing would happen on all of them (but less on Nitro's). It looks like if I do something demanding then it turns off after a minute or so. And there's no warning at all. It seems to try to turn back on, but fails. After that, the only way to start it is if I plug in the charger.
I'm going to order another battery from ebay and we'll see what happens I guess.
I hope it works!
@unforsakenrule: When i flashed, normally it takes hardly 10min, how your battery discharge so quickly. I tried most of rom found here now I stick to Kamikadze's 6.1 pro, it is quite cool and I don't want to back to STD.
Sometimes, flashing did not success and I tried again but I am always sure to be fully charged before start. If it stuck in bootloader charging is not easy. I sometimes use some crude method on my other phone, just connecting terminals of charger to battery directly using some wires, but it is really dangerous
thacen said:
@unforsakenrule: When i flashed, normally it takes hardly 10min, how your battery discharge so quickly. I tried most of rom found here now I stick to Kamikadze's 6.1 pro, it is quite cool and I don't want to back to STD.
Sometimes, flashing did not success and I tried again but I am always sure to be fully charged before start. If it stuck in bootloader charging is not easy. I sometimes use some crude method on my other phone, just connecting terminals of charger to battery directly using some wires, but it is really dangerous
Click to expand...
Click to collapse
That's pretty hardcore man! I'll try that ROM out and see what happens. In the meantime, I'm still waiting for a battery I bout on ebay. Thanks!
I received my new battery today~
No more problems since I got my new battery. The old one was a Sanyo and apparently had issues. The new one's a Celxpert. I'm now running wm6.1 Pro and it IS tight. Thanks for your responses guys!
-unforsakenrule
I have read and read and read. I have "bricked" my phone in the past and fixed it. I have used, tested, and flashed many roms from this site (Thanks to all cooks for their work!) but I still consider myself somewhat 'new' to troubleshooting.
I woke up this morning to make some important phone calls today and as luck would have it, my phone was stalled again. It's been doing that for a few weeks now. My last flash was Open Touch 5.0 UL I believe (either that or 5.2 biggy) and it has been working great except for the occasional freeze.
The problem is now it won't boot up after it froze this morning. Just sits at the boot screen
So I've tried my other methods of fixing it...
Except this morning nothing is working. I have tried flashing with Orig. T-mobile ruu, tried SD flashing with the RUU_signed.nbh, tried restarting the computer, phone, removing battery and sim... NOTHING! When trying the sd flash (which I've never done before today, it reads and tells me to push the down button but then goes to bootloader screen and just sits there. With the RUU I'm getting err 300 but I'm using the SAME RUU (4.10...) that I've used in the past to reflash my phone AND tried the new one (4.26...)
Possible problem: Does it matter what kind of usb cable you use? I don't have the normal one I use as I am not home but I figured usb is usb...
I've read about it being a motherboard issue, how common is this?
I've read somethings about MTTY, would this apply to me??
Please help, anyone who has any suggestion, I'll try it!!
Stats:
IPL 4.10.0002
SPL 4.10.0000
NOT hard-spl'd
Wing w/ Open Touch Project 5.0 or 5.2
By The Way...
I decided to post this in this section as well because it pertains to a problem with Open Touch 5.0 or 5.2 as it is directly related to my problem.
Since you are not hardspl, did you try to go to the bootloader and then flash the original Tmo stock rom from there?
Yes I did, all I am getting is an error 300... I wonder if it my usb cable though cause I'm using one that is meant for a TV to CPU device. (it's a little thicker than my other cable which is at home unfortunatly)
To be honest, I've tried two different Tmo stock rom's and I can't even get it past 0% before getting the 300 error. Even though one of the two I've used before for this situation, the 4.10
epicphotoeye said:
Yes I did, all I am getting is an error 300... I wonder if it my usb cable though cause I'm using one that is meant for a TV to CPU device. (it's a little thicker than my other cable which is at home unfortunatly)
To be honest, I've tried two different Tmo stock rom's and I can't even get it past 0% before getting the 300 error. Even though one of the two I've used before for this situation, the 4.10
Click to expand...
Click to collapse
Have you tried your regular wing USB?
Sometimes the metal inside the USB varies in number even if they have the same size..
Hi I had the same problem after flashing the phone of a collegue of mine.
After reading forum after forum I found the goldcard method.
It is found here: http://forum.xda-developers.com/showthread.php?t=417930
It is a bit tricky to get it working but eventually it did work. And the phone is up and running again.
good luck..
PM me if you are having problems.
this happened to me.im new at this so i was jus lookin around in the phone and i found that when you install opt 7.5 biggy it changes me from tmobile to at&t and i changed it back and my phone worked with no problems.
Alright, I've had a Kaiser for about a year and a half, and I just got a new one through warranty return, as my old one has a LCD issue.
So this one has the most recent AT&T Rom included, which has HTC Home. I was unaware that they came with that now, which is cool.
Although I don't really like AT&T's roms. But the first thing I was going to do was flash Hard SPL 3.29. (Which I had before) I do all the steps, and everything go fine, until I run KaiserCustomRUU.exe, I can go through the process, and it gets to the progress bar. Then the phone also shows the progress bar, but it never exceeds 0%.
Eventually the RUU gives me a Error 262 Update Error.
I can unplug and reset and nothing has been affected and the device boots up properly. But I cannot seem to get Hard SPL 3.29 installed.
Then I tried a daring attempt, and just flash a new ROM without hardspl. The same thing occurs.
My bootloader reads:
KAIS1*0
SPL-3.56.0000
CPLD-8
I've been searching xda with no avail. I've tried every idea i've had, and no luck.
Anybody know the trick to this?
Thanks
when it says unplug the USB connection...dont unplug the cable going into the phone..unplug the actual usb cord from the computer and replug it in...not the cord going into the phone
ATT software you say ?
If its an actual tilt, you've got to use the Jump-SPL to flash Hard-SPL more than likely. Once Hard-SPL enabled its free sailing for the most part
Oh I know how to do the HardSPL.
Cause I did it on my previous Tilt, and it was easy as pie.
This one is just being a troublemaker and being a jerk to me haha.
But I know to use JumpSPL and everything. It's all worked before, and now it just won't go past 0%.
I really need some help with this one.
No matter what I do it will not go past 0%
I downgraded to WM6.0, thinking maybe its something with 6.1.
Still no help, even HardSPL1.0 won't install. I have no idea what is wrong with my phone =/
After the longest time, and hassle, I did it on my older PC with Xp, and it worked perfectly.
I guess Vista was just being a jerk
My Fuze was running PROven ROM 2.2 and various others before that fine, Hard-SPL and everything done correctly.
Now the device will not turn on with the power button, however i CAN get to the BootLoader and the HardReset Screen, i've tried hard-resseting and re-flashing with multiple roms- they say its succeful and then i still CAN'T power on
please anyone help if you can, thanks in advance
try flashing the stock rom
tried that..
i did, both the SD card and the USB method- no luck :/
says flash was successful- still won't boot up...
remove the sd card then try restarting it
i've tried that also, no luck
Plug in your phone via USB to your computer and boot into the tricolored bootloader screen without your SD Card. It should say USB at the bottom.
Download and run stock AT&T ROM (Assuming you have an AT&T branded phone since you said Fuze): http://rapidshare.com/files/157242627/RUU_Raphael_Cingular_US_.exe
This should install your original shipped package.
Now if you still get a black screen, at this point, remove your SIM Card and reset your phone.
nothing
thanks for the link, tried it, yet again, no luck.....
is the back light on but the screen is black or does the phone look completely dead with no back light? Plug in your AC adapter and see if the light fades in and out to indicate charging.
I know this might sound retarded but have you tried pressing the reset button on the bottom of your phone?
I'm sure you tried so try this step. Pull out the battery and let the phone sit there for a good 2 minutes then try reflashing to your stock ROM.
If you still have a black screen, pull out the battery again for another 2 minutes, put it back in but this time plug in your phone using the AC adapter and just charge the phone for a few minutes then try turning your phone on.
thanks
thanks variablex, however i cannot try your last step because i had already given up and used my warranty by the time you posted it, i will be receiving a new fuze in the mail soon - would've rather not used it yet and tried more steps but now its too late :-\
thanks anyways though