It is a G3 device and not unlocked and I used something that probably was never meant to be used in a wizard.
RUU_Prodigy_1070302_103_10703102_CMCC_CHS_Ship.exe
really stupid I know, now it is not powering on.
is there any way to recover from this?
lol no kidding it isnt meant for a wizard.. don't you see it says PRODIGY ..
Try taking your battery out for a little while..then put it back in and try booting into bootloader mode by holding the camera button for a couple seconds then press the power button while still holding the camera button... if you get a screen that has 3 colors flash the device with Wizard_Love or an official cingular ROM
I will try that, how long is little while? I will try leaving it for more that 5 min. In many sites prodigy is presented to be the same with wizard, so I probably [email protected]#$ it up..
I bricked my Hermes before and I left the batter out for about 10 seconds and put it back in and the power LED came on.
update:
took out the battery and then put the charger in.
three coreor creen came up with IPS/SPL versions and a RUU message in top right corner... Now?
is your phone CID unlocked?
go to www.htcamerica.net/support/8125/software-downloads.html and download that ROM and flash that to your device....
you can flash the above rom regardless if ur CID unlocked or not. it's the official ROM
it is not unlocked, I tried to update to the original version but it gives an error message and then it returns back to the 3 color screen.
What does the RUU mean in the top right corner? Now it does not power off. When I press power it shuts down and then comes up again in that screen. this happens only when I have the charger plugged in. Is there a chance that the battery is dead?
ok .. find wizard_love rom in this forum somewhere and try flashing that.. your phone isn't bricked it's saveable... first off, you CAN NOT flash a custom rom to your phone if it is NOT UNLOCKED.
Find Wizard_love rom and flash that.
now it is back to the original cingular 2.25 rom. After 2nd time it managed to install it. And I am back to my previous problematic situation...
http://forum.xda-developers.com/showthread.php?t=310853&page=4
Thanks for the information, by the way if you are aware of any way to get out of the situation I am now, you would be more than welcomed to help..
Thanks!!
I hope someone can help here or point me to a post with steps to fix this.
I decided to do a ROM update on 8125 like device (Does not say Cingular or HTC etc. on the cover) But when started said QTek.
I installed the T-Mobile ROM update MDA_software_update_226102_22610105_022511.exe
Now the device starts then shuts down and then strats again then shuts down again. Sometime it makes it all the way to the start menu but most of the time it restarts during booting.
When it does make it to the start menu. The device reboots with in 30 seconds of clicking here and there.
Thanks,
You may be using the update not for your ROM...
Try to hard reset your device by pressing CommManager+VoiceCommand+reset (Release reset while still holding the other two buttons), then press Call button when prompted.
I have tried that many times but no help.
Phone boots
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
Windows Mobile
Reboots
Phone seems to me stuck in loop.
If I take out the battery
Give it a little rest.
Then it boots like normal but as soon as you click here and there the phone auto reboots.
Thanks,
I think you better try if the phone still reboot if it is in bootloader mode (Camera + reset). If so, then it is a hardware fault and software repair should not make any change.
If it stays in bootloader mode without reboot, then maybe the updater placed a bad ROM dump in your flash. Visit the unlocking forum, view the unlocking sticky and follow the instruction to use Button's 1.05 ROM to unlock CID, then flash another ROM.
No phone is not in a boot mode.
I did install the boot 1.05
CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe
Then install the
MDA_software_update_226102_22610105_022511.exe
But the phone just keeps rebooting.
Does anyone from where I can download and install the
early release of Cingular 8125.
Thanks,
CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe
This ROM is used for CID unlock only, it is NOT a Cingular stock ROM, and you should upgrade to other ROM for day-to-day use because the IPL and SPL is far too old.
Read the how to flash a rom sticky, then read all of the stickies you can find about how to flash a ROM. Read the wiki.
Read, read, read. All of the instructions are available - you just need to take some time and read them.
kegobeer said:
Read the how to flash a rom sticky, then read all of the stickies you can find about how to flash a ROM. Read the wiki.
Read, read, read. All of the instructions are available - you just need to take some time and read them.
Click to expand...
Click to collapse
This may help, the exact same thing happened to me with my touch pro, I thought it was corrupt rom or somthing, however after looking into every aspect of this and trying everything I found the fault. It was my left hand battery pin in the back of the phone, it was bent at a lower angle to its two other friends. I carfully levelled them all out and raised them slightly and the phone was instantly cured. Try it I hope it sorts you out.
I would also suspect a bad battery issue. If you have not recently messed with the pins, I would right off suspect the battery. You must be ultra careful when bending any pins. I would first replace the battery. I had a battery that was up to 100% then dropped right off to 0 as soon as I attempted to make a call. Also it is common for the chargers to go bad. I had a wall charger that actually seemed to drain the battery overnight. I replace it with the battery and problem solved. Try batteries plus it is a chain store and they will have your battery and charger. Good luck. And one last thing try and charge with a wall charger or usb most of the time. It is much better on your battery then a car charger.
I have a Wizard 200 and I tried to unlock it, I loaded the Love rom and that worked, but CID locked I then loaded 1.05 rom and when it finished I just got the splash screen, so I removed the battery and now it will not power up and there is no led display even for power, I am sure there is some charge in the battery as it was 75% when I was loading the rom.
Now I have no display and no power in, nothing, is this truly a brick?
Gazoo22 said:
I have a Wizard 200 and I tried to unlock it, I loaded the Love rom and that worked, but CID locked I then loaded 1.05 rom and when it finished I just got the splash screen, so I removed the battery and now it will not power up and there is no led display even for power, I am sure there is some charge in the battery as it was 75% when I was loading the rom.
Now I have no display and no power in, nothing, is this truly a brick?
Click to expand...
Click to collapse
YES, that's what we call a bricked phone; when it does same as a brick: NOTHING.
I'm guessing you have a G4 and tried to apply procedures meant for G3.
My advise (and only thing possible now) is to get another battery or charge yours on another phone and see if it lights up...
I tried the plug and unplug with no battery process and I get a red light flashing, but nothing more then that, I am guessing I can't post a boot because of the wrong rom loading (it said prodigy for new version when I loaded the rom) Does anyone now of a way to re-write, access, or reprogram the chip, in a jtag type connection, any service that i can pay for to revive this thing.
one other thing if someone can help me, CAn I take a G3 and make it a G4 with a rom upgrade?
I swear I seen 2.21 for IPL/SPL and OS sytem(it was a lock O2 xda mini s) when I started the process and the next screen said it was 2.21.0001 for IPL/SPL with OS 2.26( I used the LOVE rom and the loader was in Italian, that worked fine but the CID was still locked, so I loaded the last rom and ended up with IPL 1.05 and SPL 2.21.0001 I forget what OS it was last loaded with.
Gazoo22 said:
I tried the plug and unplug with no battery process and I get a red light flashing, but nothing more then that, I am guessing I can't post a boot because of the wrong rom loading (it said prodigy for new version when I loaded the rom) Does anyone now of a way to re-write, access, or reprogram the chip, in a jtag type connection, any service that i can pay for to revive this thing.
one other thing if someone can help me, CAn I take a G3 and make it a G4 with a rom upgrade?
I swear I seen 2.21 for IPL/SPL and OS sytem(it was a lock O2 xda mini s) when I started the process and the next screen said it was 2.21.0001 for IPL/SPL with OS 2.26( I used the LOVE rom and the loader was in Italian, that worked fine but the CID was still locked, so I loaded the last rom and ended up with IPL 1.05 and SPL 2.21.0001 I forget what OS it was last loaded with.
Click to expand...
Click to collapse
No,you cannot make a G3 device to a G4 device with a Rom upgrade.They are entirely made of different DOC chips with different Bootloaders.You cannot flash a G3 Rom unto a G4 device which contains IPL/SPL in it.cuz a G3 has IPL/SPL 1.xx or 2.xx bootloaders and a G4 device has 2.xx.xxx1 bootloaders.A Rom containing 1.xx bootloaders if flashed to a G4 device will Brick the device.This has been Warned many a times on the forum.That's exactly what you did.You flashed a Rom with containing IPL/SPL 1.xx (wizard_love_rom and Button's Rom)
It's clearly visible from the SPL 2.21.0001 which you have posted,that you had a G4 device.It's wrong to say that it was actually with a IPL/SPL 2.21 in the begining and with flashing it changed to SPL 2.21.0001,cuz both the roms which you flashed only have IPL/SPL 1.xx or 2.xx, they will always downgrade to 1.xx,it cannot make it 2.xx.xxx1.
Take mestrini's advise and try to charge or get a fully charged battery to make the phone start and try to go into bootloader screen,if it's able to get into bootloader mode than there are chances of it's revival,by flashing the official carrier's rom from the bootloader,ok
good luck
Ok, thanks for the reply and correcting and pointing me in the right direction, my battery says 3.57 volts on a meter, any idea what a fully chargered battery should read on a meter, not sure how i am going to charge the battery but I will try to find a way.
Gazoo22 said:
Ok, thanks for the reply and correcting and pointing me in the right direction, my battery says 3.57 volts on a meter, any idea what a fully chargered battery should read on a meter, not sure how i am going to charge the battery but I will try to find a way.
Click to expand...
Click to collapse
If i remember correctly from my Nokia days a battery would not wake the phone below 3.2v and would not allow to charge below 2.4 (not sure though) but wouldn't also never reach the 5v when fully charged
So i'm guessing that your battery has enough 'juice' to fire up a 'good' bootloader. Sorry to tell you this but either make up some story with the repair center or sell the housing and other parts to get some money back...
Gazoo22 said:
Ok, thanks for the reply and correcting and pointing me in the right direction, my battery says 3.57 volts on a meter, any idea what a fully chargered battery should read on a meter, not sure how i am going to charge the battery but I will try to find a way.
Click to expand...
Click to collapse
Sry,it's not my field ,I don't know what a fully charged battery shud read on a volt meter,better ask some person who got experience with it,
Ya I think the battery has the power to boot the sytem, it is reading 3.66 when I measured again and my xda IIi reads 4 volts after a full charge, so I think it is down to a corrupt boot loader and I have yet to see anyway to program it like I do with jtag on satellite boxes, I had backed up what i could before flashing but no way to put it back in.
I have just got this Wizard and am having difficulties getting past the first screen: I Have unlocked before and should know the answer to this question. But the annoying thing is that the ugraders do upgrade to 100% and go to FINISH.
The unit then boots to the initial beer mug screen, the red markings appear and the whole unit stops. It is showing an IPL of 1.01 (which I have never heard of before), an SPL of 2.26, a GSM of 01.12.10 and now an OS of 1.5.4.2. No amount of soft booting will get me past this screen and all I can do else is to upgrade to some different ROM and it loads fully and then wont get past THAT splash screen, when it wont of course activate ActiveSync because presumably the ROM OS isnt loading past the splash screen.
I can of course get to the three coloured screen and try again and this result repeats itself.
I should add that PDA Update Utility 2.00.1 gives an error message 300, 'get newer update utility' which seems to make no sense as this is 3.08
licensedtoquill said:
I have just got this Wizard and am having difficulties getting past the first screen: I Have unlocked before and should know the answer to this question. But the annoying thing is that the ugraders do upgrade to 100% and go to FINISH.
The unit then boots to the initial beer mug screen, the red markings appear and the whole unit stops. It is showing an IPL of 1.01 (which I have never heard of before), an SPL of 2.26, a GSM of 01.12.10 and now an OS of 1.5.4.2. No amount of soft booting will get me past this screen and all I can do else is to upgrade to some different ROM and it loads fully and then wont get past THAT splash screen, when it wont of course activate ActiveSync because presumably the ROM OS isnt loading past the splash screen.
I can of course get to the three coloured screen and try again and this result repeats itself.
Click to expand...
Click to collapse
What was the ipl/spl...? before you flashed button's rom 1.05 ? and which carrier's Rom was loaded ?
you got ipl 1.01 due to flashing button's rom but your spl remained 2.26,try to flash button's rom a couple of times more,sometimes it takes a lot more than one flash to load up button's rom,or try a hard reset.
secondly,download official carrier's rom and as you say you can get into bootloaders,flash it.
Disconnect your phone from the usb cable,disable any Firewall and Anti virus and reboot your Pc.
1. Make sure your phone is not Connected to the PC and remove the dummy card or SD/MMC card
2. On your Desktop PC, open Microsoft ActiveSync, then go to File >Connection Settings >Remove the Selection from “Allow USB Connection with this desktop computer”
3. Reconnect your phone to the Desktop PC using the USB Cradle and the Charger MUST be Connected to the Cradle (Don’t Bluetooth for the Upgrade)
4. When you see usb appear at the bottom of bootloader screen
5. Run the Upgrade again and it will work fine without any problems.
While upgrading, the ActiveSync program will not go on, however the upgrade is running.
What do you mean by 'I should add that PDA Update Utility 2.00.1 gives an error message 300, 'get newer update utility' which seems to make no sense as this is 3.08',did you upgraded to ipl/spl 3.08 before flashing button's rom 1.05 ?
good luck
I've tried some of that: Now I'll do it properly
OK I will follow your instructions: Just a few points. Firstly I didnt realise that when it says Button's ROM has loaded properly, you might still have to try loading it again a few times.
Secondly I did try loading the manufacturer's ROM and it gave the same result: Loaded fully, went to FINISH. After 100%, wouldn't get past initial splash screen on reset.
Thirdly the reason I was doing the upgrade which failed with that error message was because I just didn't recognise the IPL of 1.anything. So as I had heard that the SPL/IPL was some type of bootloader, I thought that the reason it wouldnt in effect boot was because I was trying to load an advanced ROM with a dinosaur boot loader. So I was trying to load IPL/SPL 3.08 to try the ROM flash again. This seems to have been a red herring. I am reasonably sure that the IPL/SPLs were the same as they are at present before I loaded Button's ROM
Lastly I can do all of this with a vanilla computer I have lying around somewhere onto which I can load ActiveSync 4.5 so I will try that.
I hope this is of some use to users who have this problem
Here's where I am stuck now: Reloading button ROM numerous times did nothing. Same problem. Gets stuck at splash screen. Tried loading T-Mobile ROM. Went successfully to 100% then prompted to FINISH. Same problem. Gets stuck at splash screen. All soft reboots result in same. Holding down all three buttons while pressing the power button seems to result in a black screen with "Press SEND to restore factory defaults, Other keys to quit" Pressing SEND (I presume they mean CALL?) gives a very quick report something like 'Formating FAT32 partition Formatting failed' followed by t-mobile splash screen for a few seconds and then IPL 2.26 SPL 2.26 GSM 02.25.11 and OS 2.26.10.2, so that flash did take successfully and then the screen hangs!
Then I noticed that Vippie tells you that you have to re-run lokiwiz after flashing the Button ROM, which raises the question: how do you do that after Button hasnt actually run it's course after the successful flash? (besides this, which unlock do you run? There seem to be about four options. So presumably you have to assume it is the full CID unlock)
Then I ran the Button again and of course it completed (this time going red at a more normal 98% rather than the 85% as last time, flashing blue quickly and then going red again before going to 100% at red and then turning blue again) and of course it then gets stuck at splash screen as soon as the red info crops up. But as I had received a successful flash report, I re-booted, ran Lokiwiz again and tried to CID unlock again. Naturally lokiwiz gets stuck at the unlock DOS screen when trying to unlock with the Button splash screen stuck on the Wizard (which is a bit Vippie doesnt tell you on his instructions page).
So I Controlled-C to stop the non-running lokiwiz and tried Wizard_Love ROM from the tri-coloured screen, with the IPL of 1.01 and an SPL of 2.26 just to show me that the most recent flash had worked: Which returned the (italian) error 300 message, old utility and of course no activity on the Wizard.
With the tri-coloured screen, plugging the Wizard in again and seeing the USB appear on the Wizard to make sure the computer sees the device, I ran lokiwiz again and saw no activity on the device, just an inactive tri-coloured screen along with a (after about an hour of this) non-working CID unlock program.
Does anyone have any idea what could be causing any or all of this or are these symptoms a bit egregious/
licensedtoquill said:
Here's where I am stuck now: Reloading button ROM numerous times did nothing. Same problem. Gets stuck at splash screen. Tried loading T-Mobile ROM. Went successfully to 100% then prompted to FINISH. Same problem. Gets stuck at splash screen. All soft reboots result in same. Holding down all three buttons while pressing the power button seems to result in a black screen with "Press SEND to restore factory defaults, Other keys to quit" Pressing SEND (I presume they mean CALL?) gives a very quick report something like 'Formating FAT32 partition Formatting failed' followed by t-mobile splash screen for a few seconds and then IPL 2.26 SPL 2.26 GSM 02.25.11 and OS 2.26.10.2, so that flash did take successfully and then the screen hangs!
Then I noticed that Vippie tells you that you have to re-run lokiwiz after flashing the Button ROM, which raises the question: how do you do that after Button hasnt actually run it's course after the successful flash? (besides this, which unlock do you run? There seem to be about four options. So presumably you have to assume it is the full CID unlock)
Then I ran the Button again and of course it completed (this time going red at a more normal 98% rather than the 85% as last time, flashing blue quickly and then going red again before going to 100% at red and then turning blue again) and of course it then gets stuck at splash screen as soon as the red info crops up. But as I had received a successful flash report, I re-booted, ran Lokiwiz again and tried to CID unlock again. Naturally lokiwiz gets stuck at the unlock DOS screen when trying to unlock with the Button splash screen stuck on the Wizard (which is a bit Vippie doesnt tell you on his instructions page).
So I Controlled-C to stop the non-running lokiwiz and tried Wizard_Love ROM from the tri-coloured screen, with the IPL of 1.01 and an SPL of 2.26 just to show me that the most recent flash had worked: Which returned the (italian) error 300 message, old utility and of course no activity on the Wizard.
With the tri-coloured screen, plugging the Wizard in again and seeing the USB appear on the Wizard to make sure the computer sees the device, I ran lokiwiz again and saw no activity on the device, just an inactive tri-coloured screen along with a (after about an hour of this) non-working CID unlock program.
Does anyone have any idea what could be causing any or all of this or are these symptoms a bit egregious/
Click to expand...
Click to collapse
First of all,let me advise you that lokiwiz02b tool never works in bootloader mode (tri color screen),to work it has to have a working OS on your phone,therefore using lokiwiz again and again will not work and is of no use,untill and unless your able to flash button's rom 1.05 successfully and it loads up correctly and the phone is in working condition,also downgrading to IPL/SPL 1.xx,lokiwiz will not operate.
Vippe said to rerun the lokiwiz in this sense that if you ever again downgrade to IPL/SPL 1.xx by flashing button's rom.as if you have upgraded to a wm6 Rom with ipl/spl 2.xx or 3.xx and you flash back again button's rom 1.05,than only to rerun the lokiwiz.but if you are able to flash button's rom 1.05 and load up sucessfully to OS and get the device unlocked,than there's no need to go back to ipl/spl 1.05 as your phone will be permanently unlocked.
regarding Error 'Formating FAT32 partition Formatting failed'
well to my understanding and knowledge,it does not pertain to any Rom flashing errors,it's mostly related to sdcard/mini-sd problems,Are you having any sdcard/mini-sd card in your phone,then remove it before flashing cuz it has been seen that sdcard/mini-sd card create problems while flashing.If the sdcard/mini-sd card requires format,it usually get splash screen stuck up or won't let bootloader mode stuck.
So, try to flash button's rom a couple of more times or as sometimes it gives problems then download and try xda_minis_Launch Rom :- http://rapidshare.com/files/43423464/Xda_MiniS_LaunchROM_v154102.exe
and the third option is of course try to flash the official carrier's rom,good luck
Not sure I have simplified enough
Many thanks for the note: To restate the problem, no ROM I flash can get me past the initial splash screen and I am not using any SD card at all.
Every ROM flashes successfully. It always then gives me it's SPL/IPL report on the initial splash screen but none of them get past that first splash screen. All they do is to load the splash screen (whether it is the beer mug or the T-Mobile one) and then tell me what versions I am running in red and then all stop.
Actually I thought that there wasnt much point in re-running the unlock program of whatever type if it was unlocked already but that was how I interpreted Vippie's advice if you had somehow got back to a 1.xx IPL. Now I see that was incorrect. I have tried so many times to reflash Button ROM and seen it complete fully and even close the utility that I am beginning to wonder whether it IS worthwhile trying numerous times again. So I will now try to flash the http://rapidshare.com/files/43423464/Xda_MiniS_LaunchROM_v154102.exe as you suggest.
By the way, I don't ever seem to be able to get the computer to see the device so as to flash it when any OS is loaded (obviously because none of them load after the soft resets after their flashes). it SEEMS to me that I can only get ROMs to re-flash from the three colour screen? But even trying to get a stable T-Mobile ROM onto the machine seems to work this way and as I say usually completes to 'FINISH' and then doesn't get me past the splash screen again. Curiously this device doesn't seem to mind being flashed in tri-colour mode!!
In first splash screen mode with the Button beer mug showing, and with the red text showing an IPL of 1.01,, an SPL of 2.26, GSM or 01.12.10 and an OS of 1.5.4.2 all I get now when I try to flash the T-Mobile ROM is an error 274 or error 260 telling me that although I can see the green light lit on the Wizard telling me that the device IS connected to the computer and the battery IS fully charged, there is no connection between the computer and the Wizard! Actually flashing Xda_MiniS_LaunchROM_v154102 now does the same thing: I should try rebooting and possibly [grasping at straws here] moving the flash directory from the desktop to the root of C:
update
Just to update this, I did flash the mini-ROM Xda_MiniS_LaunchROM_v154102 and it did complete successfully from the tricolour screen (going red at 85% and then at 98% as well) and then completing and closing the utility
And now stops yet again at the Button beer mug after reading the parameters (which are the same)
Sorry to repost yet again
I have now flashed the manufacturers ROM and it took successfully from the tricolour screen and the unit now boots to the T-Mobile initial splash screen where it yet again stops completely after telling me that it is now at spl/ipl 2.26
licensedtoquill said:
I have just got this Wizard and am having difficulties getting past the first screen: I Have unlocked before and should know the answer to this question. But the annoying thing is that the ugraders do upgrade to 100% and go to FINISH.
The unit then boots to the initial beer mug screen, the red markings appear and the whole unit stops. It is showing an IPL of 1.01 (which I have never heard of before), an SPL of 2.26, a GSM of 01.12.10 and now an OS of 1.5.4.2. No amount of soft booting will get me past this screen and all I can do else is to upgrade to some different ROM and it loads fully and then wont get past THAT splash screen, when it wont of course activate ActiveSync because presumably the ROM OS isnt loading past the splash screen.
I can of course get to the three coloured screen and try again and this result repeats itself.
Click to expand...
Click to collapse
The issues began right after a ROM downgrade from IPL/SPL 2.25.001 using the button 1.05 ROM. After 100% complete the phone got stuck on the beer mug. I waited 5-10 minutes before doing a soft reboot. Now the phone won't turn on it all.
No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second. I think this is just the screen and LED discharging.
I thought it may be a battery issue even though the batter was at 90% before the firmware upgrade. I tried jumping the battery by wiring a 9 volt to the + and - ports on the HTC battery for between 1 and 5 seconds without any luck. I do not have a multimeter to verify, but I think the battery is good. I tried swapping my battery with a co-workers. His phone turned on, mine did not.
At this point I'm pretty sure I bricked it but want to confirm before I move on to my next toy.
Thanks!
Pity no one seems to know the answer to this judging by the number of page views!
lou2ser said:
I'm having similar issues. I got to the beer mug screen and waited 5-10 minutes before doing a soft reset. Now I can't even get the phone to power on. No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second.
Any ideas?
EDIT: I've done some reading and it looks like it may be a dead battery. I'll try jumping it tonight and will report back.
Click to expand...
Click to collapse
At the moment the Consumer Product Safety Commission is looking into the general question of battery malfunction on these Wizards: T-Mobile seem to know all about it as they have instructions to try to sell customers new units when problems with batteries or battery overheating are reported; if customers don't respond positively, they are instructed to read endless scripts to you and keep you on the phone for as long as possible and hope that sooner or later you will go away.
Did yours overheat before dying? Some element of reseting the device may be called for: I found that with a working unit I have, (not the one with the frozen screen problem) if you simply put another charged battery in it, the Wizard may spring to life. But don't expect T-Mobile to assist you with this, they are in denial about this problem. One suspects Cingular may react the same way, I have never had any experience with them.
Nevertheless this does appear to be a real problem here judging by the number of page views and the lack of suggestions by any moderators?
lou2ser said:
I'm having similar issues. I got to the beer mug screen and waited 5-10 minutes before doing a soft reset. Now I can't even get the phone to power on. No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second.
Any ideas?
EDIT: I've done some reading and it looks like it may be a dead battery. I'll try jumping it tonight and will report back.
Click to expand...
Click to collapse
what is the data of your phone like IPL/SPL...?,is it a G3 or G4 device,if it's a G3 then it might be your battery problem,either you did not had a full charged battery when you flashed the Rom or may be it's a faulty battery,but did have any previous problems of this battery,before in normal working or before you flashed ?
secondly the most important,If you have G4 device and you flashed a G3 Rom with IPL/SPL 1.05,well....... man you got a Bricked Phone.
There may be another problem, - People dont like answering hardware problems here?
No, read the thread: But I may have a bricked device and not know it. No one has suggested this yet. The device cannot be seen by the computer. If I go to the bootloader screen and then connect the USB cable, I can flash the ROM successfully.
Nobody seems to know why this should be. This flashing changes the splash screen, ROM and the SPL/IPL.
But I can never get past the first splash screen. After the red data is displayed, the unit freezes. Although I always do this with a fully charged battery, lately the unit doesn't seem to want to charge itself.
Can you still flash your device?
licensedtoquill said:
No, read the thread: But I may have a bricked device and not know it. No one has suggested this yet. The device cannot be seen by the computer. If I go to the bootloader screen and then connect the USB cable, I can flash the ROM successfully.
Nobody seems to know why this should be. This flashing changes the splash screen, ROM and the SPL/IPL.
But I can never get past the first splash screen. After the red data is displayed, the unit freezes. Although I always do this with a fully charged battery, lately the unit doesn't seem to want to charge itself.
Can you still flash your device?
Click to expand...
Click to collapse
As long as your phone gets into bootloaders(tri color screen),it's not 'Bricked',be rest assured of this,ok
Secondly until and unless you have working OS on your phone,it'll not be recognized by the computer,as it cannot establish connectivity through Activesync.Activesync will only detect your phone in a normal working status,so in present status,your phone doesn't bootup normally into working OS and it only goes into bootloaders,it will never be detected by the Activesync and thus your computer.
The only test to verify the connectivity of your phone with computer at present is that when you attach your phone with the USB cable to the PC and there appears small usb at the bottom of the bootloader screen,that means your phone has established connectivity with PC.
It's a 'catch 22' situation,where your bootloaders are not accepting any Rom flash and the only way is to get your phone start working normal and unlock it ,for that it's required to downgrade to ipl/spl 1.xx,or the other option is to flash the official rom to bring it back to it's default status and then try to downgrade to ipl/spl 1.xx and unlock it.
Well,as you say it's not charging that cud be a major hindrance in flashing,cuz it's recommended to have atleast 70% charged battery before starting any flash,if it does not retain charge during a flash and does not have enough juice left to complete the flash then the flash will not complete,it's a bad flash and phone usually stuck up at the bootloader screen,this cud also be the problem ,you are not getting a full proper flash.
Try to fully charge your battery and then try to flash,if it's not charging,than check your charger or the usb plug of the charger,it might not be having a good connection with the mini usb port of your phone,wiggle it a bit and see if it starts to charge,secondly,it cud also be the mini usb port of your phone which might be malfunctioning,anyway verify and rectify the problem.if it's the usb plug of the charger,get a new charger,but if it's the mini usb port,than I'm afraid you'll have to get it repaired or replaced,
good luck
zabardast_1 said:
what is the data of your phone like IPL/SPL...?,is it a G3 or G4 device,if it's a G3 then it might be your battery problem,either you did not had a full charged battery when you flashed the Rom or may be it's a faulty battery,but did have any previous problems of this battery,before in normal working or before you flashed ?
secondly the most important,If you have G4 device and you flashed a G3 Rom with IPL/SPL 1.05,well....... man you got a Bricked Phone.
Click to expand...
Click to collapse
Here's my updated post:
The issues began right after a ROM downgrade from IPL/SPL 2.25.001 using the button 1.05 ROM. After 100% complete the phone got stuck on the beer mug. I waited 5-10 minutes before doing a soft reboot. Now the phone won't turn on it all.
No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second. I think this is just the screen and LED discharging.
I thought it may be a battery issue even though the batter was at 90% before the firmware upgrade. I tried jumping the battery by wiring a 9 volt to the + and - ports on the HTC battery for between 1 and 5 seconds without any luck. I do not have a multimeter to verify, but I think the battery is good. I tried swapping my battery with a co-workers. His phone turned on, mine did not.
At this point I'm pretty sure I bricked it but want to confirm before I move on to my next toy.
Thanks!
lou2ser said:
Here's my updated post:
The issues began right after a ROM downgrade from IPL/SPL 2.25.001 using the button 1.05 ROM. After 100% complete the phone got stuck on the beer mug. I waited 5-10 minutes before doing a soft reboot. Now the phone won't turn on it all.
No LEDS when charging via USB, no activity on the PC. When I pull the battery I get an amber LED and a white screen for a fraction of a second. I think this is just the screen and LED discharging.
I thought it may be a battery issue even though the batter was at 90% before the firmware upgrade. I tried jumping the battery by wiring a 9 volt to the + and - ports on the HTC battery for between 1 and 5 seconds without any luck. I do not have a multimeter to verify, but I think the battery is good. I tried swapping my battery with a co-workers. His phone turned on, mine did not.
At this point I'm pretty sure I bricked it but want to confirm before I move on to my next toy.
Thanks!
Click to expand...
Click to collapse
hmmm,are you sure it's IPL/SPL 2.25.001 (two '0') and not 2.25.0001(three'0') ?
well if it's 2.25.001,it'a G3 device and I find no reason that it cud brick like this,but if it has 2.25.0001,than it's a G4 device,than it's pretty well known that by flashing a G3 Rom will definitely Brick it.
secondly,First fully charge the battery,somehow,even you can do this by your friend's phone than try to force your phone into boot loader mode.Power off the phone completely,not stand-by but completely power off,and take out the battery for about one minute and insert it again.....Hold down the camera button and while keeping it holding down push down the power on button,as normally you power on the phone,The phone will start up,keep holding down the camera button till your phone gets into bootloader mode(multicolor screen),if it goes into bootloader mode,that means it's not "Bricked"
I'm pretty sure. I wrote it down before staring the update process.
Not sure if this matters:
GSM: 2.25.11.1
OS: 2.25.1.1
Am I describing what a bricked phone looks like? Any other ideas on how to revive it?
This was a replacement from ATT under warranty from an 8125 that had a bad touchscreen. It broke the 1st day and I'm sure I can get another replacement but I want to make sure they aren't going to find a way to power it up and see the hacked firmware.
lou2ser said:
I'm pretty sure. I wrote it down before staring the update process.
Not sure if this matters:
GSM: 2.25.11.1
OS: 2.25.1.1
Am I describing what a bricked phone looks like? Any other ideas on how to revive it?
This was a replacement from ATT under warranty from an 8125 that had a bad touchscreen. It broke the 1st day and I'm sure I can get another replacement but I want to make sure they aren't going to find a way to power it up and see the hacked firmware.
Click to expand...
Click to collapse
GSM 2.25.11.1 and OS 2.25.1.1 are the Radio version and windows Rom version which were installed on your phone before.they are not IPL/SPL bootloaders,it can only be verified if a device is a G3 or G4 by bootloader IPL/SPL data.
well,usually when you flash a rom,it replaces the IPL/SPL of the phone,as your phone does not show even the bootloader mode,its difficult to say,if the ipl/spl has been repladed or not.
So if it still has the initial bootloaders IPL/SPL,which were uploaded by the vendors,than there's no problem for replacement,as you can always say that,it never started again,BUT !!!,if during the flashing of Button's Rom 1.05,it has replaced the IPL/SPL than I'm really sorry,it won't be easy to explain and get away that the device was not fiddled with and you won't get a warranty replacement
zabardast_1 said:
GSM 2.25.11.1 and OS 2.25.1.1 are the Radio version and windows Rom version which were installed on your phone before.they are not IPL/SPL bootloaders,it can only be verified if a device is a G3 or G4 by bootloader IPL/SPL data.
well,usually when you flash a rom,it replaces the IPL/SPL of the phone,as your phone does not show even the bootloader mode,its difficult to say,if the ipl/spl has been repladed or not.
So if it still has the initial bootloaders IPL/SPL,which were uploaded by the vendors,than there's no problem for replacement,as you can always say that,it never started again,BUT !!!,if during the flashing of Button's Rom 1.05,it has replaced the IPL/SPL than I'm really sorry,it won't be easy to explain and get away that the device was not fiddled with and you won't get a warranty replacement
Click to expand...
Click to collapse
The GMS and OS versions were recorded before any update was done. As of right now the phone does nothing whatsoever. I just want to make sure there's not a magic button the technician can push to see my tampering.
Again, thanks for your help.
lou2ser said:
The GMS and OS versions were recorded before any update was done. As of right now the phone does nothing whatsoever. I just want to make sure there's not a magic button the technician can push to see my tampering.
Again, thanks for your help.
Click to expand...
Click to collapse
wee.this you know yourself that they are the manufacturers,technicians and have all the gadgets,knowledge and means to find out.lol
why don't you atleast try the 'Force bootloader' once,let's check it out.huh !
Try this.First fully charge the battery,somehow,even you can do this by your friend's phone than try to force your phone into boot loader mode.Power off the phone completely,not stand-by but completely power off,and take out the battery for about one minute and insert it again.....Hold down the camera button and while keeping it holding down push down the power on button,as normally you power on the phone,The phone will start up,keep holding down the camera button till your phone gets into bootloader mode(multicolor screen),if it goes into bootloader mode,that means it's not "Bricked"
Hi all,
I recently got a G4 T-Mobile MDA and flashed it with Molski's WM6 ROM http://forum.xda-developers.com/showthread.php?t=412845.
I did this by using the instructions at http://forum.xda-developers.com/showthread.php?t=394218
Everything went fine and my Wizard was happily upgraded and all was fine.
Unfortunately, I had an active syunc failure and had to soft-reset the Wizard. It would then boot up, tell me the IPL/SPL, etc. and then hang at the splash screen. I cannot hard-reset the phone, and I can enter the bootloader.
From what I can tell, I need to downgrade to the carrier ROM, and that should see me right. As I didn't unlock my phone with HardSPL (only SoftPSL, can I just:
Fully Charge Wizard
Reflash carrier ROM using the same instructions I used
Enter bootloader
Fully charge the Wizard
Follow the instructions (using softSPL and the update utility) I used origionally to flash the carrier ROM
I then should be back where I started and I can re-flash Molski's in.
Is this the correct proceedure?
As I SoftSPL flashed my Wizard, do I need to revert back to the carrier ROM or can I try to reflash Molski's to see if that corrects the problem?
I am sorry to be a pain and ask this, I have read alot and am pretty sure I need to do this. I have read in the forum a few times that if you aren't sure, ask. I hope this is OK.
Thinking of using the T-Mobile ROM in http://forum.xda-developers.com/showthread.php?t=342744
Thanks all!
Note:
IPL/SPL 2.21.0001
GSM 02.07.10
OS 11.0.0.1
Well,as you upgraded with SoftSPL,no patched IPL/SPL was flashed and the original official Bootloaders are booting the device,therefore,there's no need to flash the official rom using SoftSPL,it can be flashed directly without any problem.
Secondly,it won't charge in Bootloaders (IPL/SPL) and untill and unless there's a working OS on the phone,so try to charge the battery through other means,like with a friends phone or buy a cradle.
As you are already in Bootloaders,coz your phone boots up and stuck at Bootloaders,you can flash any rom in this mode,but you can always enter into Bootloaders by pressing Camera button and soft reset together simultaneously.
Yes! you can still reflash any custom rom using SoftSPL,even this Molski's WM6 ROM in this situation wiyhout any hassel.
Nopes,its not neccesary to first flash official carrier's rom and than flash any custom rom,you can still flash to any custom build through SoftSPL.
BTW!!! why don't you try a Hard Reset,it may clear the stuck up and load into working OS,you can Hard Reset by Comm Manager button + Voice Command button + Soft Reset with stylus,it'll hard reset and reboot,check if this works out,otherwise go as above.
Thanks zabardast_1.
I did try to hard-reset but it wouldn't work. However, something interesting happened. When the issue occured, I had about 30% batter power, I think. I left the phone on charge with the USB wall charger (light went orange up top so I knew it was charging) after trying everything I could think of knowing I needed to charge it to re-flash it.
I came back to the phone about an hour later and tried a hard-reset again, and it worked!! I know for sure I used the correct hard-reset method when I was attempting to fix it earlier - but... questioning myself now.
Does anyone know if you need to have a certain charge to allow a hard reset? Seems unlikely.
Thanks for the information anyway - I was wanting to clarify this in anyway, just incase I did have something more permanent go wrong.
Thanks
jason
Its a built in safety feature in the wizard to cut off all the operations if battery charge goes below 30%,it for protection of the lithium battery in the phones,otherwise it dies quickly.So always try to keep it charged above 50% and never let it to fully discharge itself.