I have a Cingular 2125 which I replaced the ROM with the Imate SP5m one which allows for A2DP... I did that about 4 months ago, and everything worked wonderfully for those several months. Then suddenly yesterday, the phone was responding to my input really slowly, so I did a soft reboot as I hadn't restarted it in awhile. When it started back up, it brought me to the bootloader screen (red, green, and blue screen), and I cannot get out of it... rebooted several times, took out the battery, etc... can only get the bootloader screen.
Is there a way to get back to my phone or did this thing just erase itself?
Many thanks!
SP
I finally got out of it. After about 25 or so reboots, it finally decided it wanted to start up normally.
But now, the joystick is screwed up??? Of the five functions, it only responds to three: up, down, and right. Left, and select (kind of important!) don't work anymore.
Has anyone else experienced this as a software/firmware problem, or should I just assume that this is a hardware failure?
Thanks again.
SP
My guess would be hardware failure, although you could try re-flashing it and see what happens.
Thanks. I figured I'd probably have to go that route, but just wanted to see if this happened to anyone else first.
Off I go to re-flash land!
Yep, hardware is f$^&ed. I just re-flashed to the Qtek 8300 AKU2 ROM as I read that it addressed some joystick issues. Re-flash was successful, but no change in the behavior of the joystick.
Oh well, I was looking for an excuse to get a Tytn anyway.
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]
Hi folks,
I have some new problems but don`t know where they come from.
I have flashed the newest Version of the energy rom and everything was fine. One day my phone falls down and the battery and the cover get lose and the phone gets off. I put the battery in and powered on the phone but the phone stop at the boot screen. I`ve tried serveral thing like Reset, Hard Reset and again took out the battery for some minutes but still it hangs in the boot screen. So I transfered the flash on the SDcard and flashed the rom again. Everything worked great till 2 days later. I was searching something in opera and opera was very slow. I closed opera and tried to open it again but the whole phone freezed. So I reseted it and the phone started boot and showed the Energy Wallpaper and a small white box in the lower left side what is only shown when the phone is started the first time. But the phone freezed again at this point. After reseting the phone again ist hanged again in the boot screen. I flashed the phone again and right now it works fine but I don``t wanna flash my phone every two days.
Is it a hardware failiure caused of the drop or is it a failure of the rom?
maybe post this in the rom thread?
maybe something inside the phone broke when it fell ? This random freezes shouldn't occur. I used Energy Rom 3 for about a week and didn't experience any freezes what so ever.
here's an ideea. Flash a stock rom and see if the problems still persist and if so, you should see your warranty and get your phone fixed.
hope that helped.
you should flash a stock rom then switch bak to nrg and if that doesnt fix it then youll have to get a new phone sorry mate !
Hi folks,
just have to wait 2 weeks for my new Vario IV from T-Mobile. So I have to work 2 weeks with this geek original Rom what is really ugly and slow.
same problem happening to me, except i have not dropped my phone.
should my phone crash whilst using it and i have to soft reset or pull out the battery then the rom will instantly reinstall itself and require me to align the screen again. sometimes i have to hard reset for it to do this.
I have problem flashing my HTC Fuze with the new ROM - I was using EnergyROM 2.0 but failed to flash to 3.0. I am however able to flash it back to the ATT ROM without problem.
Tried from USB flashing and from the microSD card - nothing works at this time???
Not sure what the issue are at this time.
This Energy v3.0 standard is a poor rom for
htc touch diamond p3700
hard spl 1.24
radio 1.00.25.05
Bad points-
have had it on for 30 mins and phone heats up,taskmanager in top right gone and phone freeze,using 89% ram standard , 98%after use,slide lock not working properly after power off, battery draining fast eg down 6% in 5mins,sometimes stert menu doesnt work.
Good Points-
manila is smooth as silk,everything is very responsive,quick,good programs built in,
one rom that could be the best but not for the htc diamond p3700
will read all the posts for problems for fixes
its not true!!!!!!!!!
i am using the same rom,,, and it works perfectly
hiranga said:
i am using the same rom,,, and it works perfectly
Click to expand...
Click to collapse
+1
Best ROM ever tried.