Related
Hi,
I have a huge problem.. I just wanted to install a new ROM on my MDA Vario
and during the update process I accidentaly knocked the phone of my desk.
Causing the USB to unplug and crash the update.
The Vario now stops booting @ the red, green and blue screen..
Hard reset didn't work and Windows won't recognize the phone when I plug in the USB cord..
Eerrrr.. HELP!
Can I fix this? If yes; HOW?!
The red/green/blue screen is a good sign, when you plug in your USB cable, you should see a USB icon on the bottom of your Wizard's screen. At this point, run the RUU for the ROM again from your PC. This re-flashing should fix it.
If the icon doesn't appear, check to see that the fall didn't break the phone's USB connector. If it did, send it for repair.
The next step would be to reboot your PC, and remove the battery from your phone for 5 minutes or so. Then try to reconnect again, and see if that works (To display the aforementioned icon).
Good luck!
omg dude..
I could kiss you right now.. Before your reply, I tried the same thing already (without the reboot) but that didn't work..
The USB icon did show up on my Wizard's screen, but Windows didn't recognize a USB device, so there was no
way of re-running the RUU to continue/retry the upgrade..
Obviously Windows had a lot of 'update' programs still running in memory..
And I couldn't 'kill' them.. So I reboot my PC, plug in the USB connector and YES! it's updating!!
The phone didn't fall on the USB connector.. It sort of bungee-jumped of my desk
Phew.. man I'm reliefed You just made my day!
Good to hear that you fixed your phone, Darkone.
I recently bricked a Cingular 8125 using an update from Cingular's website. Turns out my phone was a G4 and the ROM update was for G3 phones (Cingular neglected to state this information. I got my replacement phone in the mail, it's a refurbished G3 phone with a messed up, sticky keyboard. My bricked G4b(brand new, in immaculate condition) is stuck in boot loader mode(RGB screen), but I've tried about 6 different G4 ROMs and it appears that there is no way in hell it's coming back from the dead. I think my mistake was not CID unlocking it prior to the ROM upgrade. Glad your upgrade/bricking story had a happier ending
So am I gumbydude.. So am I..
I'm sorry to hear your phone is bricked beyond repair..
But isn't it possible for Cingular to fix your bricked one?
They caused the problem in the first place, they didn't inform you in any way that the ROM was for G3 phones..
I wouldn't agree to use a refurbished, sticky G3 phone if it's their fault you bricked your brand new G4b in the first place..
gumbydude said:
Good to hear that you fixed your phone, Darkone.
I recently bricked a Cingular 8125 using an update from Cingular's website. Turns out my phone was a G4 and the ROM update was for G3 phones (Cingular neglected to state this information. I got my replacement phone in the mail, it's a refurbished G3 phone with a messed up, sticky keyboard. My bricked G4b(brand new, in immaculate condition) is stuck in boot loader mode(RGB screen), but I've tried about 6 different G4 ROMs and it appears that there is no way in hell it's coming back from the dead. I think my mistake was not CID unlocking it prior to the ROM upgrade. Glad your upgrade/bricking story had a happier ending
Click to expand...
Click to collapse
First, if you get the RGB Screen that is the bootloader so your phone IS NOT BRICKED!
Second, the Cingular 2.25 Rom works with both G3 & G4 devices, it contains two complete bootloaders.
Third, you do not need to CID Unlock your device to flash an official Cingular Rom onto a Cingular 8125/8100.
Fourth, you should return the replacement device telling Cingular Returns that it is not in acceptable condition.
Fifth, download the Cingular 2.25 Rom from here: http://www.htcamerica.net/support/8125/software-downloads.html
Well, my problem is kind of similar, so I won't post a new threead, but write in this one instead.
So, what's the story... I upgraded my G3 Wizard to PDAVIET's v4 WM6 ROM and it worked like a charm. Changed the default boot logo with a custom one and after a while I tried to flash again with the same ROM (because I had restored backup from Windows Mobile 5 and had been experiencing a few bugs; however, I had done hard reset before this flashing) - it stuck at 2%; I waited 10 minutes and reset the device, saw the bootloader, pluged the USB and started the flasher - It didn't see my phone is connected to the computer. It turned out that when I plug the USB cable, the device hangs, so if I pull it out, it won't give any indication and the display will still read "USB". So, there is no way to access my phone and reflash it, nevertheless it can go in bootloader mode (however, no LED or keys are flashing) - it will just hang upon connecting the USB cable... Tried to remove the battery for a while and it still hangs just the same way...
Does anyone think there is a way to repair the device and what advice would give me to try to work the problem out?
I have just been trying to upgrade my Wizard, I have done this many times before, I tried but failed with a few ROM's and last I tried Molski's latest, now, it is just dead, after I try a hard reset, I get the red blue green screen for a few seconds, I even see it connecting to the USB and then the screen just goes black.
Pleas help with anything
Sounds to me you're battery could be empty/dead
It was full last night, so I do not think this is the problem
It was full last night, so I do not think this is the problem
Try another battery and see.
And keep us posted
I agree, it sounds like your battery is drained. And since it goes to the boot loader, that means your battery will not charge on your phone. You'll have to borrow a battery that is charged, or get someone to charge your battery.
azmerlin said:
It was full last night, so I do not think this is the problem
Click to expand...
Click to collapse
What state did you leave the phone in over night? Was the battery removed, or was the phone fully off..?
Interesting. I seem to have a similar problem. I only get the boot loader screen.
But i can establish a USB connection and update my phone. It will go all the way to 100%. Then the phone will switch off and start new. But instead of loading the OS it goes automatically into the boot loader screen.
Any idea what went wrong here?
lingley said:
Interesting. I seem to have a similar problem. I only get the boot loader screen.
But i can establish a USB connection and update my phone. It will go all the way to 100%. Then the phone will switch off and start new. But instead of loading the OS it goes automatically into the boot loader screen.
Any idea what went wrong here?
Click to expand...
Click to collapse
Since you haven't told us what you were trying to do when this started, what rom you tried flashing, and what your current IPL / SPL are and whether this is a G3 or G4, no, we don't have any ideas on what is wrong .
Read and follow this:
http://forum.xda-developers.com/showthread.php?t=298613
I would suggest you try flashing your carrier's latest official rom to get a working device back.
Bricked
If install IPL 3.08 in G4, exist solution or not
One thing to add : if the battery is really low, then it will likely not charge or respond via USB. It is necessary to use the wall charger in this case. It must have something to do with the amount of charging current that can be delivered to a flat battery.
luisprieto said:
If install IPL 3.08 in G4, exist solution or not
Click to expand...
Click to collapse
I'm not sure if you are asking a question or what. But if you try to install IPL/SPL 3.08 on a G4 device, your device will be bricked (ie: dead). I did see where someone in the Wizard forum said they were able to do a JTAG recovery and get their G4 back.
mfrazzz said:
Since you haven't told us what you were trying to do when this started, what rom you tried flashing, and what your current IPL / SPL are and whether this is a G3 or G4, no, we don't have any ideas on what is wrong .
Read and follow this:
http://forum.xda-developers.com/showthread.php?t=298613
I would suggest you try flashing your carrier's latest official rom to get a working device back.
Click to expand...
Click to collapse
You are right, sorry.
I used to have Aserg3.12 Rom on my device (G4). It worked well for at least two months. Suddenly the phone crashed in the middle of a call and didnt react anymore. Hard Reset nothing worked.
I got somehow the Boot Loader Screen back and downgraded to the original rom (QTEK novid, 220734, 2207114). Problem was whilst it finished the upload process until 100% and restarted the phone, it got stuck at the OS loading page. After 1 minute the screen started losing its colour and turned white. If I soft or hard reset the same happens, it turns white at the OS loading page.
At some point I got through miraculously, it started up and everything was fine. I charged it, upgraded to smart1 wm6 v2 and everything seemed to work. However again some 10 minutes into a call, the phone crashed and back to square one. Downgrade to old rom, got again stuck at OS loading screen etc.
I then put it over night on the charger. The orange charging LED was blinking in 5-10 sec intervals. In the morning it was red. I started the phone again interestingly got through and got it running. Battery was fully charged. But again: 10 min into a call, the phone crashed. And trying to reboot I get to the OS loading screen, then it turns white. I put it back on the charger LED is blinking, guess I have to wait again for some hours.
Thanks for any help or suggestion,
forgot that:
IPL 2.15.0001
SPL 2.20.0001
Aserg3.12? smart1 wm6? Are you sure you've got a wizard? Aren't those prophet roms?
It had been going so well, until 9 months later...today. This morning I noticed my battery low (12%), and I thought I'd charge it when I got to work. However it never made it to work - when I went to charge it the back light was on and it was frozen. Thought nothing of it, plugged in the charger, hit the reset button and... nothing. So battery out, back in - press the power light and all I get is the solid green light, no screen, no activity, nothing.
The charging light isn't on either when it is charging, yet the battery shows good charge (tried it on a friends). I'm guessing it's dead, any other takers? I'll ring Vodafone tomorrow, but I'm running with a Duty rom. Hopefully as it looks terminal it should be ok, fingers crossed??
Same thing happened to me just now. WTF? I didn't even do anything. Just totally dead with green light only on. I've tried everything. Pull battery, connect USB, charger, took out SIM, took out memory card, even tried with another new battery, nothing at all. and I just got this phone as replacement last week.
You are stuck in OEMSBL. I can help, but it will be later or tomorrow.
Tell me your ROM, SPL Version, Radio Version, & device model number as well as typey, i.e. Tilt, TYTNII, etc...
HMMMM seems we have a new problem here
Hi Guys
Guess this is now new problem with tytn ii had my phone repaired a couple of weeks ago. technician said something about 3 bad block in the CE was responsible for the TRI color boot screen i used to get.
He said that he formated the phone and reloaded all "firmware".
Prior to sending it in i had Confused Stu Vista Mobile 1.3 running on the phone. Also had OLIPRO 1.0 as the sspl
Tried Frankenkaiser but the phone will not complete step 7 keeps showing that it is an unknown USB device, once i replug the USB cable.
Loaded all the Qualicom Drivers for the Phone as well.
GSLEO3 you and JockeyW are "GOD'S" when it comes to these issues.
Please grace me with your knowledge.
Running Confused Stu Vista Mobile 1.3
Radio 1.65.14.06
wolffie02 said:
Tried Frankenkaiser but the phone will not complete step 7 keeps showing that it is an unknown USB device, once i replug the USB cable.
Loaded all the Qualicom Drivers for the Phone as well.
Click to expand...
Click to collapse
why did you even try frankenkaiser? you only need to use it if you have no SPL (and only if you have the radio from hell).
anyway, to everyone in this thread... if the device still causes the PC to load the qualcomm drivers, when plugged in, then you can recover it, though usually need to use another program as frankenkaiser is currently only compiled for specific radio versions.
Sorta Dead with solid green light
I am in the same boat ... I mistakenly flashed a non-Kaiser radio ( 1.65.28.25 ) and then thought I was reading a Kaiser page about ho to fix it and I ran a `2a`. Ooops on me.
I cannot get tricolor bootloader ... tried hard-reset ( two soft keys and reset ), and Camera-reset, but nothing is working.
What does work:
-bong when connected to PC
-mtty connects - but no `CMD>` prompt.
-able to issue `setboot` - and get back "ARM9BootMode:1".
I've read all the posts and it seems like without the bootloader, I am stuck.
This is an ATT Tilt/8925.
Any and ALL suggestions much appreciated.
seems i have such a problem
the kaiser shows only solid green led. nothing else
doesnt enter tricolor
when i plug it to usb, device manager shows first Qualcomm device and then finds several new devices such as Data Interface
device is AT&T Tilt 8925, original rom version, radio and spl are unknown
who can help me?
cmonex said:
anyway, to everyone in this thread... if the device still causes the PC to load the qualcomm drivers, when plugged in, then you can recover it, though usually need to use another program
Click to expand...
Click to collapse
what program?
I took battery out to change SIM card and now it won't start.
I get text "Touch Diamond" on the black screen and when it comes to Radio version etc. (red text i corner) it restarts!?!
I tried hard reset but it doesn't help.
Plz help I need my baby back!
Tnx
Try this
I found solution for this problem. If your diamond won't boot go to bootloader mode and upgrade your radio hxxp://modmydiamond.info/index.php?option=com_content&task=view&id=15&Itemid=26 and after that your dimond worked fine without loosing data.
or
forum.xda-developers.com/showthread.php?p=5514067#post5514067
I have the same problem. After a lockup when trying to get the internet sharing to work the phone just keeps rebooting.
I tried to flash a new radi version (from bootloader mode). Everything went OK, but the phone still won't start.
Whats next step? Hard reset?
i have the same problem - i believe it´s battery related
Try leaving your device off for a bit and pull the battery. Then re-insert the battery and plug your device into the ac adapter/charger and charge it for at least 30min. Then turn it back on and see if it continues. Like the previous poster said, you could have a bad battery. Otherwise, flash the shipped rom and then see if it still does it. Then flash back to your custom rom.
Hello All Expertz,
My 02 xdaIIs was dead while upgrading ROM.It was struck at 23 % and i was forced to disconnect.Now it is not showing any screesn even in full charged battery.I soft reseted but not working ITS DEAD.Can anyone pls help????
Thanks in Advance
MT
Milesht said:
Hello All Expertz,
My 02 xdaIIs was dead while upgrading ROM.It was struck at 23 % and i was forced to disconnect.Now it is not showing any screesn even in full charged battery.I soft reseted but not working ITS DEAD.Can anyone pls help????
Thanks in Advance
MT
Click to expand...
Click to collapse
Can you put it in bootloader mode? (white screen with the word "Serial" or USB and "v2.0x")
No..not able to put in bootloader mode.i tried to put in by pressing power+record+soft reset nothing happened.Only response i get is when i put in cradle for charging it shows a red light.pls help
in that case you should remove the battery and charge it in the back of the cradle (needs AC power supply, usb alone doesn't work). it might also show red at first, meaning the battery is completely dead now, but shortly after that, it will turn orange. if, during the charging process, it should turn red again, your battery is probably broken. maybe the battery dying was the reason your upgrade failed in the first place. i had a similar issue when i first tried upgrading in vista several years ago (before i came here). i removed the device from the cradle and it was still in bootloader mode. normally you should let the device stay in bootloader mode and just start flashing again. i didn't do it and neither did you, so all you can do is try everything to get it into bootloader mode again.
try everything you can do with the device at the moment:
- insert the battery, try bootloader
- reset, try bootloader
- power+reset, try bootloader
- battery out, battery in again...
eventually you will get the device back into bootloader mode and can try flashing it again. but before the next attempt to flash it, you should find out, what caused the error in your last upgrade to make sure, it does not happen again.
Milesht said:
No..not able to put in bootloader mode.i tried to put in by pressing power+record+soft reset nothing happened.Only response i get is when i put in cradle for charging it shows a red light.pls help
Click to expand...
Click to collapse
Chef is correct. The battery will not charge if it is on the device. Luckily for us, the BA cradle has the charging slot in the back for the "extra" battery. I would (regardless if it is dead or not) just buy a new battery on e-bay (they are dirt cheap nowadays) simply to rule out the possibility of the battery being dead, which as chef suggested might be the reason for the failure (especially if you cannot turn on the device).
Tony,
It worked lot of thanks.
1.Removed battery charged it.
2.Done hard reset(power+softreset)
3.Tried bootloader.IT WORKED .....
4.Flashed it with old stable wm6.1 rom.
IInd case.Finding the root cause.
After flashing I put that back again to the cradle.Then problem began BA went OFF.
Then I softreset and put again to the cradle before OS boots up Tried 3 times same result to make sure its cradle prob.
I take out frm the cradle
softreset the BA to boot.Now another problem.ITS not booting it reaches the FOUR COLOR SCREEN WITH RoM DETAILS then it FADES OUT with some markings(horizintal lines) here and there.
I waited for few minutes removed battery.Put it again then pressed power button got same results.
On the second attempt while locking the battery switch (pressing it up) That old RED LIGHT glows up.Then I pressed it down to unlock and removed battery.Then I tried again
This time it boots up and everything came to normal.(My HEART BEAT WENT DOWN) Thanked GOD.. And ofcourse you Tony.
Meanwhile I had given a small blow at the cradle and put my sweet Angel to cradle its working fine Now.
SO AM NOT SURE WHO IS THE real CULPRIT.. Battery,battery switch,or cradle?..
egzthunder,
I think battery is ok because I am getting the same backup just it was before..
So big THANKS to u two of you.
( I write this post frm my BA ) ;-)
Regards
Milesh James
egzthunder1 said:
Can you put it in bootloader mode? (white screen with the word "Serial" or USB and "v2.0x")
Click to expand...
Click to collapse
Hello,
I am facing the same problem on my xda iis showed on the screen only " Serial/USB v2.06"
I am really appreciated if you and someone can help me to solve the problem.
Many thanks for your kindness.
please don't double post, there was really no need to bump the other thread, since it is incredibly outdated and not helpful at all. being stuck at the serial v2.07 screen, the bootloader, you should try starting over from the very beginning, using the guide in my signature (if you are a windows xp user).