Laptop Blue Screen While upgrading (Do i have a New brick?) - 8125, K-JAM, P4300, MDA Vario Software Upgrading

I was flashing my phone which i have done a thousand times, however this time my laptop blue screened at 98%. Now my phone is stuck with the red, green and blue bars. It does however connect to the USB (usb shows up on bottom right).
What can i do now, is the phone shot?
Thx.
Eric

As long as you have the USB in the corner you are good. I would just flash it back to the stock ROM and then go from there.

I can't seem to re-flash i get error 300 when using RUU 2.00.1

kiteOregon said:
I can't seem to re-flash i get error 300 when using RUU 2.00.1
Click to expand...
Click to collapse
Try first to normal routine, take the battery out, wait a sec, put it in again and start.
Connect and if your lucky it will start normal (1%) otherwise flash again.
Normally it should accept the ROM which you had on last.
Don't worry it's not bricked, happened to me at least a dozen time. I have a ASUS Laptop which overheats and shuts down when flashing....

I have removed the battery and reinstalled, then when powered up it did not start over again. Just boots back to the bootloader screen where it displays IPL 2.24 and SPL 2.24. When connected via USB it will show that. I can connect to the phone via MTTY however the set commands dont seem to work and the task commands give me an invalid command error.
Thx.
Eric.

I MTTY to write a known good backup to an sd card from a wizard that was working, i got my phone to boot to the screen that asks to apply image from SD card. After about 30 minutes i get a message that says Sucess. Press any key. When i press any key i go back to the bootloader, when i power off and on i just go to the boot loader. I do notice that my IPL / SPL versions are different.
What's going on here? Is there a way to write the image files used in this process to the SD from windows so i can try a different image? When i try to view the card in windows now it asks to format it.
Eric.

Related

HELP!!!!!!!!!!! pc rebooted during flash!

omg wtf do i do now?! my pc rebooted 31% into the flash.. it blue screened out of no where!
now its stuck on a IPL 2.21 screen!
this happened to me a few times as well. I just re-tried the flash from another machine and it worked fine.
but i cant establish a active-sync connection because the phone wont start it just stays at the 2.21 screen thats red/green/blue/white! omg im about to cry what do i do lol
I have seen the same screen, and have also had the computer blue screen on me probably 3 or 4 times now. When i plugged it into another machine with activesync, i ran the updater and it worked fine.
im trying it right now on 2nd pc still downloading the rom file tho
ok i was able to flash using another computer thank god!
:lol:
Can you post the steps of reflashing the wizard? I've tried a flash on another system, but it still doesn't work...
My steps:
1. Install Active Sync 4.1
2. Connect the wizard on usb
I've tried to downgrade the wizard with wizbackup. wizbackup need to flash IPL/SPL 1.01. The flash was ended without errors. But now the wizard starts and I only see the three colors and the version of IPL/SPL. Then I connect the wizard, Active Sync doesn't get a connection to the phone.
UPDATE:
In another thread I read that the wizard can't be flashed in IPL/SPL 1.01 without an OS. Can anyone verify this information or help me?
UPDATE II:
I finaly found out, that the phone can be restored with an image from the sd-card.
1. Put an image from the system to sd-card with psdwrite.exe
2. Power Off the phone and put in the sd-card
3. Power on the phone holding the camera key
4. Then the bootloader is coming up, press the voice key during 3s
5. The bootloader upgrades your phone from sd-card
Good luck!
that **** happens to me all the time, it always crashes to the boot loader and once its there you can just restart the upgrade no problem. if you need to boot into the boot loader then simply, from a turned off state, hit the wifi button, voice command button and power button, then release the power only and it will boot into the tri colored boot loader. then reinstall your image and soon you will be kickin it with your **** in it once again! booyakasha!
actually now that i think about it that will just go to the hard reset screen. you really just want to stick the stylus in the reset hole if you need to get to boot loader i think. i dont remember off hand.. just mess with it. if you break it just say you got it that way and exchange that ****

Flash Stop at 1% trying to go back to Stock ROM

I have a problem and I've search the forums and search google and I find people with somewhat of the same situation im in... but the methods to fix them don't work.
My problem is,
I have a T-Mobile WING (Herald)
I am flashed on soft SPL with SPL 4.70.Yang
I am ROM flashed to Touch-It WM6.1
I want to flash back to the stock T-Mobile Rom
I run the Stock RUU and it enters the bootloader and at 1% the wing resets
I then get a connection error 260 and the flash will not proceed.
I have tryed restarting my device/computer. unplugging my usb putting in another slot... and still nothing. Any help would be appreciated I'm really unhappy with Touch-It and want to go back to stock and do some customization that way.
you need to extract the .nbh file from the stock rom using 7-zip or winrar on the ruu executable. Make sure you don't extract the spl.nbh file. I think the file you want is something like RUU_signed.nbh
then put it into your HardSPL folder and flash away
Yep. Besides, 4.70.Yang is a HardSPL, not a softspl. If you want the SPL to also return back to stock for warranty issues, then just use USPL along with the tmobile NBH. If not, do what fzzyrn said for the best results.
Got to this thread:http://forum.xda-developers.com/showthread.php?t=421304
Go to post #2 and download the Herald-USPL-beta3
extract the nbh file from your rom and place it in the ruu folder that is located in the flash center folder.
run the utility.
spacemonkey333 said:
Got to this thread:http://forum.xda-developers.com/showthread.php?t=421304
Go to post #2 and download the Herald-USPL-beta3
extract the nbh file from your rom and place it in the ruu folder that is located in the flash center folder.
run the utility.
Click to expand...
Click to collapse
And that links to this.
My T-mobile Dash 620
I HAVE THE SAME PROBLEM . I WAS UPDATIND THE ROM OF MY 620 WITH HTC_S620_WWE_BT_3.66.424.1_4.1.13.44_02.94.90_Ship AND THE PHONE RESTART ADN WHEN THE PROCCESS GOT 25% POP UP A MESSAGE ERROR 260 AND IT WAS RECOMMENDING ME UNPLUG THE USB CABLE AND REMOVE THE BATTERY AND CONNECT IT AGAING SO. I TRIED HARD RESET AND IT DOESNT CONNECT THRU ACTIVESYNC AND ITS STUCK AT THE BOOTLOADER SCREEN (HTC). I TRIED REFLASHING RADIO AND NOTHING WORKS. PLEASE HELP ME. I BROKE MY PHONE.
ROMEROPOLACO said:
I HAVE THE SAME PROBLEM . I WAS UPDATIND THE ROM OF MY 620 WITH HTC_S620_WWE_BT_3.66.424.1_4.1.13.44_02.94.90_Ship AND THE PHONE RESTART ADN WHEN THE PROCCESS GOT 25% POP UP A MESSAGE ERROR 260 AND IT WAS RECOMMENDING ME UNPLUG THE USB CABLE AND REMOVE THE BATTERY AND CONNECT IT AGAING SO. I TRIED HARD RESET AND IT DOESNT CONNECT THRU ACTIVESYNC AND ITS STUCK AT THE BOOTLOADER SCREEN (HTC). I TRIED REFLASHING RADIO AND NOTHING WORKS. PLEASE HELP ME. I BROKE MY PHONE.
Click to expand...
Click to collapse
The S620 is not a herald and every phone is different, so I'm not sure if we could help you out. Does your phone have a HardSPL? Have you used HardSPL before? Even if the activesync icon doesn't start trying to sync it doesn't mean that it's not connected, it just means that it has nothing to sync (since it's in bootloader mode.)
I FIXED
I Did These Steps:
I Turned My Phone Off
I Pressed The Camera Icon Button
I Turned The Phone On (no Loose The Camera Button)
It Got Into Boot Mode
I Plugged To The Usb Cable
I Oppenned The Ruu For My Phone Version
And Wowla Fixed
Thank You Guys For Your Help
The Answer is in a Careful Search
This post is being made to you about... a month too late. But that's because I just got the Wing yesterday and started trying out roms today. Anyway, ran into the same problem earlier today and found the answer in the forums. I've written the following for those who might need all the steps. In your case, read from step 3. Anyway, in case you still have this problem, here's what you do:
1. Hold camera button when pressing the soft reset to get into the bootloader; it should be in red blue green and white. something like that.
2. Connect the usb to the computer and run the stock RUU Utility (this can be found on the official t-mobile website. look under something like support/downloads for the Tmobile Wing)
3. When it hits the 1%, the phone will automatically restart. When it does this, it breaks the connection between the computer and the phone. At that instant, hold the camera button and the soft reset button. Then, when you let go of the reset button, it should go back to boot loader.
4. At this point, the Rom Utility should give you the error. Do not take out the battery as instructed. Just disconnect the usb, reconnect the usb, wait for the computer to recognize it (it should appear in my computer) and then just continue the utility.
Good luck. =)
i had the same problem flashing my P4350 yesterday. tried a lot of different things, the solution for me was:
1. start flashing from the bootloader
2. just to hold the camera button when the phone restarted after 1% (nothing else, no soft reset or anything).
this resulted in the phone restarting in bootloader again, and after that it just resumed upgrading the rom.
koekiemonster said:
i had the same problem flashing my P4350 yesterday. tried a lot of different things, the solution for me was:
1. start flashing from the bootloader
2. just to hold the camera button when the phone restarted after 1% (nothing else, no soft reset or anything).
this resulted in the phone restarting in bootloader again, and after that it just resumed upgrading the rom.
Click to expand...
Click to collapse
This one works for me. Thx!

Stuck on Bootloader (yes i searched.. this is different)

Just going to preface that all of this is off the top of my head since i'm at work and the phones at home.
So my tilt is stuck on the bootloader screen, I never modded it and im using the stock 6.1 rom, I turned it on one day and it was on the tri-color screen. Here's what i've done to try and fix it.
Running the ATT stock 6.1 upgrade over USB: XP and Vista wouldn't even recognize it till I held [ok, power, and the reset button together] first time it errored at 14%, second time it completed at 100%. after restarting it was back at the bootloader screen.
Tried putting the official rom on the SD card: It recognized, and started the upgrade process, went to 100% saying it finished with no errors, rebooted back to the bootloader screen.
mtty: had to hold [ok, power, and the reset button together] to get vista to recognize the device. The command BOOT does not work. Can't remember the other commands off the top of my head, but following the guide I cleared the memory, (NOT the a2 or w/e command that nukes everything) it said it found a few bad blocks and repaired them I think, then I set it to load the OS and not the bootloader..
Attempted to install the stock 6.1 rom, went to 100%... stuck on bootloader after restart.
Any idea what to try from here guys?
Thanks!

Error code

I got a Upgrade ROM code error, please try again.
any ideas on how to get this to go away and return to my phone?
Hard resets dont work
I have tried the other things listed from the other "I bricked my phone"
Unluckily I'm using Vista and currently don't have an XP ready computer to use. I've removed the battery and plugged the USB cable in and I still get the TRI colored screen with no connection to Windows Mobile Device Center
I did notice that with the memory card installed, the TRI colored screen does go away for a second, but goes into a Loading... and that's all the phone does
from my experience tis happened when the hspl didn't flash correctly. my best suggestion would be to try flashing hspl following the instructions for vista, though it may be easier on xp.
btw, the boot looks for an image on the sd card to flash that's why you get the different behaviour.
i'm not sure if it's possible to flash hspl via the sd card only.
Thank you for the advice
I will try and execute that, but im pretty sure it wont work. the phone wont even connect with my computer
?
when trying to connect to your pc, is it in bootload? if not try that (vol down & power same time till boot screen appears). once you connect it should show in the white area the words "usb" after that try running the ruu.
problem solved!
apparently I didn't realize that I was on the stock 1.14.0000 SPL and that I had to flash the stock rom...
I then flashed the stock rom and re-did the SPL to the Olinex one and re-flashed a cooked rom
Thanx for all the input fellas

Please Help Me

So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
tlglegacy said:
So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
Click to expand...
Click to collapse
can you put your phone into bootloader mode (power and vol down together whilst powering on)? be a good idea to remove your sd card first.
cr1960 said:
can you put your phone into bootloader mode (power and vol down together whilst powering on)? be a good idea to remove your sd card first.
Click to expand...
Click to collapse
I can't really manually put it into bootloader mode, but when the phone thinks its charged enough it will start up itself and go into bootloader mode
Does your phone say "RUUNBH" in the top right corner? Have you yanked out your battery then put it back in before charging? Those are the two things I would try. And BTW, in the future you shouldn't create two threads in different parts of the forum.
DaveTheTytnIIGuy said:
Does your phone say "RUUNBH" in the top right corner? Have you yanked out your battery then put it back in before charging? Those are the two things I would try. And BTW, in the future you shouldn't create two threads in different parts of the forum.
Click to expand...
Click to collapse
yea im sorry its just my phones been down for days and its really bugging me and i just want to get this fixed and my phone does say RUUNBH in the top right corner and i have yanked out the battery waited a few seconds for good measure and put it back in before charging...it still just loops into bootloader before dieing and charging again
Phone started up again this is what it says in bootloader
RHOD300 32 M SS-BC RUUNBH in top right
SPL-0.85.Olinex
MicroP(LED) 0x0A
MircroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
then it has some numbers and code error under it with try again
then it says 218,842 calibrated
Okay, the problem is that the RUU flag is set, and the device won't do anything until that is cleared. What you need to do is establish a connection via MTTY. Follow the instructions here about how to connect to your device via MTTY. Once you get an MTTY connection established with your device (it may take awhile, MTTY is quirky like that), simply type
Code:
set 16 0
You may need to manually soft reset the device. Then, I highly recommend flashing to a stock ROM using the microSD card method, before flashing another cooked ROM.
DaveTheTytnIIGuy said:
Okay, the problem is that the RUU flag is set, and the device won't do anything until that is cleared. What you need to do is establish a connection via MTTY. Follow the instructions here about how to connect to your device via MTTY. Once you get an MTTY connection established with your device (it may take awhile, MTTY is quirky like that), simply type
Code:
set 16 0
You may need to manually soft reset the device. Then, I highly recommend flashing to a stock ROM using the microSD card method, before flashing another cooked ROM.
Click to expand...
Click to collapse
hey thanks Dave i plugged in the usb then i waited until my phone was charged enough to switch on and go to bootloader then i opened MTTY the USB port showed up i selected it and it connected no problem i typed in set 16 0 then the device reset and showed the touch pro 2 boot screen then my phone died and started charging...i left it charging overnight and this morning it booted up and started loading the ROM...after it was finished i hard reset it just to be sure and now it's working perfectly thanks very much i appreciate the help
Duplicate thread??
Dude!! you already opened this same thread here, and HERE. Why another??
Closing thread.
Don't do this again.

Categories

Resources