Related
I cant believe this....I had no issues all day upgrading the ROM...until my PC overheated and shut off at 57%...
now when my phone starts up I see the 3 bars and it sais USB in the bottom left...but active sync is not connecting!
help!
what 3 bars?
a Red Blue Green Bars color?..
If that so.. you are too lucky..
I read a little more on the wiki:
Type 2a: When the phone boots, it goes directly to bootloader mode (tri-color screen)
This is what I have right now...I can't seem to get active sync to connect...although at the bottom of the screen it has "USB"
I have tried using mtty and dont think its diong anything...
Just stay in the bootloader (tri-color screen) and make sure the "USB" is shown in your device screen..
The reflash.. even if its not sync/connected.. just reflash the ROM..
Everything will be fine..
wow....i think it may actually work....that was SCARY.
nice to know the good ole button flash works when all others fail
I just want to make a clarification..
You are just flashing your device and when the upgrade process is on 57% your computer suddenly shutoff? and the upgrade was cut..
What happened next? did you reset the device then went to tri-color screen? or you just force bootloader mode it?
Yeah pretty much exactly what you said. I literally got up for a second to get some water, came back and saw the telltale sign that my pc had just shut itself off (the screen was black except for the standard boot junk that shows up).
So I look at my device (8125) and it was locked at 57% and was not responsive. I figured that the flash util probably wouldn't continue after the computer started back up (and besides, the device wasn't alive anymore) so I rolled the dice and unplugged the USB and took out the battery. When I put the battery back in and hit the power button, it went straight to the bootloader (the tri color screen).
- By the way - ive got the button image on here now - workin like a champ...
tnx for the explanation..
have fun!!..
thanks for the quick reply - i thought i was completely stuck but the button flash seemed to take care of everything. Makes me almost think that bricking this thing is near impossible... >
Yup!.. that also my conclusion.. its impossible to brick.. thats why i ask for your clarification..
What is this "button flash"? I am stuck in RGB boot mode with no activesync connection. I have read til my eyes crossed, but can not fix my 8125 (G3)!
Please advise.
How about more information? On your bootloader (Rainbow screen) what does it show the IPL / SPL to be? What were you trying to do when you got into this situation? What happened when you were flashing? Is your device a G3 or G4?
Safest thing for you to do right now is to flash your carrier's rom onto the phone (an official shipped ROM). With your phone in the bootload, just run the ROM and it will install (DO NOT RUN A CUSTOM ROM AT THIS POINT SINCE YOU HAVEN"T TOLD US ANY OTHER INFORMATION).
G3 8125
ipl/spl 2.25
Was trying to use faria's latest rom...got stuck at 99% for almost one hour, so I rebooted computer and discon'd the wizard. Now it will boot to rainbow screen and will not connect via activesync (so I can't utilize any other roms to get back to square one).
ActiveSync will NOT connect when you are at the boot loader. As long as you see USB in the bottom left of your phone (above the left soft key) then you can flash your original Cingular ROM and be good to go again.
brick, brick, brick
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
I need help....
Hunter6 said:
It happend to me too with faria´s new crossbow rom:
the device freezed at 99% and I reseted it then....nothing happend- bootloader mode: red green blue + usb... but no chance to flash ANYTHING... always the same message:ERROR (260) update error, no connection to the device...???
I tried the O2-mini s update, and the faria rom, no chance just a brick
Click to expand...
Click to collapse
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Go get a copy of your carrier's official ROM (not a custom one, but an official one from your carrier.). Then with the phone at the boot loader (Rainbow screen) and the USB cord plugged, in, run the official ROM. If that doesn't work, then get a copy of the Wizard Love rom and flash it (You'll need to find links around here for it, or pull it via PirateBay). You may also want to reboot the PC you are running on and remove your SD card (if you have one) just to remove variables that can play in to all of this.
Good luck
mfrazzz said:
Why did you reset it??? All roms freeze. The screen that is flashing the ROM even says it can take up to 10 mins. If you don't get an error onthe PC then DON'T stop the flashing process.
Click to expand...
Click to collapse
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
-----
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Thanks!
brick, brick, brick
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help
entdiablo said:
Ten minutes is understandable, but mine stalled for about an hour at the 99% mark. Even my PC would not respond. Is that normal for a rom upgrade?
Click to expand...
Click to collapse
No, that sounds like your pc locked up or something (I'd blame windows on that one )
I was finally able to reset my 8125 to the Cingular ROM. Not sure why I couldn't do it on my PC, but after moving over to my wife's PC I did not have any problems.
Click to expand...
Click to collapse
Glad to hear you got it going. Good luck and be careful out there!
Hunter6 said:
o.k. boys, now it is a nice little crossbow brick from faria.....and I can make telefon-calls with my brick.
thanks a lot for your help
Click to expand...
Click to collapse
Sorry, I may be missing your humor or sarcasm... Are you saying its dead (if so, give more details about what it does or doesn't do, IPL/SPL it shows (if it turns on), etc... If its now working, then congrats!
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"
Ok, so today I tried to flash my Rom with the official att 6.1 rom from HTC. I got it to finally start flashing after about ten tries but when it reached about 13% it gave me an error 276 I think. I tried the recovery method suggested by removing the battery for 3 seconds and reseting the device but now my device isn't recognized in windows and I can't run the upgrade file anymore.
It just goes to the bootloader screen with "KAIS1*0" on the top, then "SPL-3.02.000" below that, and "CPLD-8" below that. At the very bottom it shows USB but my computer doesn't recognize the device. I've tried hard reseting it and it just goes back to the bootloader screen.
Is there any way I can get my Kaiser back or am I screwed?? All this waiting for 6.1 and now my phone is dead. What a load of crap.
Just re start the ruu and let it sit for a minute when that happens, it will start again by itself. Almost shat myself when it happened to me.
First of all, relax. Your phone is not bricked. Do a little looking around the forums and you will resolve this.
I am too lazy to search for him but is the 3.02 SPL compatible with the 6.1 ROM?
I can't restart the Ruu because I can't get a usb connection to my phone. The bootloader goes into usb mode but my computer does not see the phone. The Ruu says it cannot detect the phone either.
Isn't there a way this guy can re-flash using a MicroSD card?
MineralGray02K said:
Isn't there a way this guy can re-flash using a MicroSD card?
Click to expand...
Click to collapse
I'm not sure if the OEM SPL has the ability to flash from card like the Hard SPLs.
To test put the Carrier ROM (Download from the Wiki) on to the root of the MicroSD Card and call it KAISIMG.NBH. Turn on the Phone with the Camera Button Held Down. It should try and flash the ROM then. If that doesn't work, I have a thread and wiki page all about getting stuck on the bootloader, check my Sig for more info.
Hope this helps.
Dave
rodavery said:
Ok, so today I tried to flash my Rom with the official att 6.1 rom from HTC. I got it to finally start flashing after about ten tries but when it reached about 13% it gave me an error 276 I think. I tried the recovery method suggested by removing the battery for 3 seconds and reseting the device but now my device isn't recognized in windows and I can't run the upgrade file anymore.
It just goes to the bootloader screen with "KAIS1*0" on the top, then "SPL-3.02.000" below that, and "CPLD-8" below that. At the very bottom it shows USB but my computer doesn't recognize the device. I've tried hard reseting it and it just goes back to the bootloader screen.
Is there any way I can get my Kaiser back or am I screwed?? All this waiting for 6.1 and now my phone is dead. What a load of crap.
Click to expand...
Click to collapse
run this while phone is hooked up to computer stuck in bootloader.
Sweet Jesus
Ok, I tried the tri-color fix from nufsaid. It didn't work b/c it couldn't open a usb port or didn't see the phone or something. Then I tried putting the rom on my microSD card.
And *SHAZAM* there it was. DaveShaw you are a god to me now. It said the update was successful but I'm still stuck in the bootloader. It used to work if I would plug it into the wasll charger and reset it but that isn't working now. My computer still doesn't recognize it so Mtty or anything still doesn't work.
Ok, I left my tilt on the tri-color screen all night long to run down the battery. When I woke up I tried to power it on and I got the familiar ATT flash screen but when I plugged it into the AC power it went straight into the bootloader.
I don't know what's worse, bootloader or red light of death, I just experienced the red light, called att and got a new phone sent out in 12 hours! What SPL does your phone show? they might exchange if it's not 'voided'
ok, I finally got it to load the windows. If the battery has a high charge or is charging resetting won't get out of the bootloader. If I let the battery run down to almost nothing, wait a little while with it out, then try it again it will turn on. my spl is now 3.56.0000.
Finally
I finally got it out of the bootloader. I'm never going to reset my phone again. It's gonna suck if it freezes. Thanks for all the help.
rodavery said:
I finally got it out of the bootloader. I'm never going to reset my phone again. It's gonna suck if it freezes. Thanks for all the help.
Click to expand...
Click to collapse
Glad your back up and running. There are two new hard SPL's be cmonex (they are mentioned in the link in my sig) that make it less likley for you to get stuck at the bootloader. You could try those?
Ta
Dave
Im about to flash my ROM from original 1.56 to Duttys new, but when i enter bootloader the white loadingscreen gets stuck in my face. Nothing happens and i need to remove the battery to shut down device. Anyone? Freakin frustratin´.
Before I flashed my first rom, I read wiki.xda-developers.com to make sure I understood what I was doing, and used the search button, instead of risking turning my phone into a paper weight.
Since then, Crackwhore has written a very helpful post at the top of this forum about how to use HSPL and USPL to allow you to flash roms.
yeah i know all that. not my first time flashing a phone but the first time it got stuck loading the bootloader. and specially when i´ve only used the HTC update.
darfor said:
Im about to flash my ROM from original 1.56 to Duttys new, but when i enter bootloader the white loadingscreen gets stuck in my face. Nothing happens and i need to remove the battery to shut down device. Anyone? Freakin frustratin´.
Click to expand...
Click to collapse
you mean you couldn't get to boot loader page?
So you already have HSPL 1.56 installed (or have SPL1.54 and used USPL)?
If you have HSPL you could try renaming the .nbh file to blacimg.nbh and copying it to the SD card and entering bootloader
Same problem here. Stuck in bootloader mode. Loading progress indicator never moves beyond 0%. Have always used the card method (blacimg.nbh), but this time it doesn't work and nothing flashes. No matter what I do the system goes to tricolour bootloader screen and says ROM update error. Have tried 3 microSD cards, all in working order, so this isn't the problem. The full problem description is here. Help!
AFW said:
Same problem here. Stuck in bootloader mode. Loading progress indicator never moves beyond 0%. Have always used the card method (blacimg.nbh), but this time it doesn't work and nothing flashes. No matter what I do the system goes to tricolour bootloader screen and says ROM update error. Have tried 3 microSD cards, all in working order, so this isn't the problem. The full problem description is here. Help!
Click to expand...
Click to collapse
try dnloading the rom again amd try.
the file might be corrupt
Have tried that many times. File is not corrupt. I'm getting really worried this is now a brick...
OK, if you can get phone into bootloader, it is not bricked
What does your SPL say in bootloader? Do you get any errors when trying to flash rom? Are you using USPL or HSPL? If USPL, you have to use it before every flash to new rom or radio. If HSPL, are you using correct version?
Was on Dutty's 3.9 XT, but decided to revert to standard WWE 1.56. I flashed the Std 1.56 ROM successfuly, and then tried to restore the ship SPL 1.54 using the card flash method. This failed, and now I'm stuck on the bootlader screen forever.
No matter what I do the THD always goes to bootloader (red-green-blue-white screen), with following text:
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
Upgrade ROM code error
Please try again
USB
Click to expand...
Click to collapse
When I start blac_uspl.exe (USPL 2.5), a window flashes (Vista64) for a split second and then nothing else happens. The Vista64 system's USBs work with THD and have been used to sync over past few months.
When I try to run HSPLWrapper_Blackstone_156OliNex.exe and step through the preliminary screens, the Verify that you want to update ROM version screen has the From Image Version as blank and the To Image Version as 1.56.Olinex. When I click to commit the flash the THD screen switches to white with a progress indicator that always stays at 0% until it times out. Recovery does nothing and the same thing always happens. Using Vista64. .Net installed and fine. I can't use the card method (BLACIMG.NBH) - the system also stays on "Loading .... 0%" and nothing else happens.
When I try to flash anything (have tried HSPL1.56, Dutty's 3.9 ROM, stock 1.54 spl) using the card method, the system says "Loading . . ." and hangs there forever without a progress indicator showing.
Your SPL says 1.54.0000. When you try and run USPL.exe have you remembered to disable your antivirus?
Have you tried usb method instead of card for flashing rom?
I know you have said that youi have used usb for syncing, but when in bootloader does it change from 'serial' to 'usb' when you connect HD to PC?
Fallen Spartan - I want to thank you for taking the time to help me resolve this problem. Very much appreciated!
1. Yes, anti-virus disabled and indeed removed from the PC.
2. Yes, have tried the USB method at least 20 times.
3. Yes, the bootloader changes from Serial to USB. It then goes to the progress indicator screen and hangs on 0%. The progress indicator on the RUU on PC also stays at 0% and eventually times out. I've gone through the Recovery routine at least 20 times, with no luck.
When I try to run SSPL-Manual-TouchHD.exe it says "not a valid Win32 application".
I'm a bit perplexed by this.
You have obviously successfully flashed Duttys V3.9 so drivers are fine, you know how to use USPL, both flashing methods (SD card and usb/pc), disabled anti-virus, phone in bootloader.
Have you tried to reflash 1.56 rom or possibly performing a hard reset before trying to use USPL or HSPL. I doubt this would make a difference though.
Have you tried cRaCKwHoRe's USPL GUI v 2.5 Application?
You don't get any code errors?? I'm struggling to find a solution here.
Yes, this is most vexing. I've flashed innumerable times before and never had an issue. I suspect the SPL is fine, but somehow the actual WM ROM image is corrupted. Will now try to load Std 1.56 ROM image again...
Success! The 3rd attempt at reflashing stock 1.56 ROM worked. I don't know why the system bombed out before. Perhaps one of those inexplicable brain farts..
Anyway, all seems to be fine now. Fallen Spartan, you have my endless gratitude for at least responding. Let me know if you need accommodation at next year's FIFA World Cup in South Africa (though I'm a rugby fan).
AFW said:
Success! The 3rd attempt at reflashing stock 1.56 ROM worked. I don't know why the system bombed out before. Perhaps one of those inexplicable brain farts..
Anyway, all seems to be fine now. Fallen Spartan, you have my endless gratitude for at least responding. Let me know if you need accommodation at next year's FIFA World Cup in South Africa.
Click to expand...
Click to collapse
No accomodation required, just glad you got it sorted
Im still stuck. When i installed HSPLWrapper_Blackstone_156OliNex my screen changed colors but would go back to normal when i would turn the screen off and back on so i didnt see it as a problem. I installed the EnergyROM BLACKSTONE 20090608 Standard an tried to go back stock using RUU_BlackStone_HTC_WWE_1.14.405.0_Radio_52.49a.25.26_1.09.25.14_Ship but it gets to 1% then says this update utility cannot be used for you PDA phone. Please check your update utlity.
Then the phone boots up and at the black smart mobility screen in the bottom corner it says
R 1.09.25.14
G 52.49A.25.26U
D 1.14. 21010
the phone boots up with the funny colors again and goes to align screen but it keeps staying there even after i align it.
The bootloader screen says
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
USB
Am i tryin to install the wrong stock ROM. I purchased the HD from phonesource-usa if that helps also
can anybody help me at all
Adamsville: perhaps you're stuck in bootloader mode because the WM ROM image flashed on your system has become corrupted or disabled, ie the only thing the system can boot into is the bootloader.
Try flashing a new compatible WM ROM image and see if that works.
AdamsvillE said:
Im still stuck. When i installed HSPLWrapper_Blackstone_156OliNex my screen changed colors but would go back to normal when i would turn the screen off and back on so i didnt see it as a problem. I installed the EnergyROM BLACKSTONE 20090608 Standard an tried to go back stock using RUU_BlackStone_HTC_WWE_1.14.405.0_Radio_52.49a.25.26_1.09.25.14_Ship but it gets to 1% then says this update utility cannot be used for you PDA phone. Please check your update utlity.
Then the phone boots up and at the black smart mobility screen in the bottom corner it says
R 1.09.25.14
G 52.49A.25.26U
D 1.14. 21010
the phone boots up with the funny colors again and goes to align screen but it keeps staying there even after i align it.
The bootloader screen says
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
USB
Am i tryin to install the wrong stock ROM. I purchased the HD from phonesource-usa if that helps also
Click to expand...
Click to collapse
a hardreset followed by a 1.54 base rom will solve all ur probs.
or lower spl to 1.14 cos ur stock rom is a 1.14 base as suggested by th name..
cheers
this morning, I restarted my x1 because it was awfully slow this morning. so after I restarted it, it stayed at the sony ericsson splash screen for long time and didn't do anything. I tried to reinstall the rom through SD and it didn't work. Then I hardspl-ed it and tried to reinstall one of my old kovsimg.nbh in it, then now....it won't even turn on!!!
Did I brick my x1??? HOW IN THE WORLD CAN I FIX IT?
my battery is fully charged btw. PLEASE HELP. THIS IS URGENT!!!!!!
I've checked on different forum guides on here and none of which seem to be having what I am looking for.
UPDATE: i just plugged in my phone to the computer and then it popped out a notice on my computer saying that the device is not recognized. "the device is malfunctioned and does not recognize it."
@[email protected]" so what am I to do? do I return it to the store and get them to fix it or is it better just to give it up?
Have you tried a hard reset?
I have, but still no reaction...
I am guessing the x1 is still safe in a sense since the red light is still on.
Can you put it in booloader mode? If so, what version of the spl do you have?
the Phone won't even turn on. no possible way to get into bootloader. when you say spl as in hardspl and also softspl. i'm not quite sure. i just found it on this forum in the latest forum updates.
asian_boi said:
the Phone won't even turn on. no possible way to get into bootloader. when you say spl as in hardspl and also softspl. i'm not quite sure. i just found it on this forum in the latest forum updates.
Click to expand...
Click to collapse
Have you tried taking the battery out for ten seconds, put the battery back in, then hold the power and volume down keys until you see the tri color screen. Does this work?
yes. I've done that.
the phone still can't be turned on.
need help too
i just tried to Hard SPL my phone, and now i'm on the bootloader screen
showing KOVS110
SPL-0.72.OliNex
Micro P1 -787
Micro P2 -707
and it says continue to upgrade ROM please wait. i've been waiting for for a long time. it stucked there. i take off the battery for few second and put it back it shows the same screen again. And i need to use MTTY to boot it to get into window mobile. i was trying to Hard SPL the NEW ORIGINAL X1 ROMS INCLUDING R3xxxxx update 1.10.2009. and i can't upgrade it. everytime i restart my phone it goes back to the bootloader screen and freezed there. then i need to use MTTY to boot it and bring it alive again. can anyone help me out with this? pls