well this is my last post for the night its 2:30 and I'm tired. I'll be checking up in the morning and maybe bumping my post for more answers.
while installing oprilo's hardsplv7 my computer froze and my phone was stuck on 47% I restart my computer and reset my phone only to find it stuck in the bootloader mode spl 2.03 from the official wm6 from cingular I had on my phone. so I reinstall the cingular 3.57 software onto my phone using the install wizard. it was the only way to unbrick it. when I went to try to download most roms I get the error [240] check update utility. reading the forum it says that code is given when you have a corrupt file.
Now you know my situation here is my question, How the h*** do I totally redo my phone back down to wm5 and spl 1.04 again? or is there another way to fix my semi bricked device? I've read the unbricking page and wasn't finding anything specific to my device.
Try using SD Card flashing
or
starting with phone in bootloader mode, then hook to PC, then start update and select the correct SPL version when prompted.
Crashing while flashing SPL can be a bad thing.
I was wondering about the SD way. its wierd I can flash using sspl with pandora kitchen and it uses the bootloader 1.09, but after its done flashing the new rom and go look at the bootloader screen again its back at 2.03.
I'll try the SD way if that doesn't work, I guess I'm stuck with the highest radio using install method from cingular. although I'd really like 1.50 radio. since I have gsm network over here
Yeah, you're playing with fire whenever you flash the radio. That's where unrecoverable bricking can occur, esp. if you don't have Hard-SPL installed.
Try another PC if you can't do SD flashing... sounds like flakey USB issues to me.
best to set your phone down and don't touch it or the cable until its finished.. also make sure you have a stable machine
Related
I downloaded the Dopod 900 rom, wishing to change my PPC into Traditional Chinese. But after running the no id exe file. It reboot my PPC and said the country ID is not correct.
Afterwards I run the bootloader.exe on JASJAR. And it automactially go to bootloader mode. I'm able to upgrade my PPC rom. But after the cold reboot the system go to bootload mode (ask me to insert serial or USB cable). How can I get PPC work?
you always have to start your device in bootloader mode manually before upgrading.
as you didn't, special bit in the device was set, to start it always in bootloader mode now.
rerun the upgrade with MaUpgradeUtil_noid.exe again. it will fix it.
buzz
I got the same problem after upgrade to a new version complately but always still on bootloader mode,I have rerun the upgrade but still got same problem.Help please.
Reset while holding the power button
xdaIIse said:
I got the same problem after upgrade to a new version complately but always still on bootloader mode,I have rerun the upgrade but still got same problem.Help please.
Click to expand...
Click to collapse
Reflash the Jasjar again. But use the Radio Rom 1.04.02 only. Then do a reset.
Is here nobody who can read?!
Here is the answer how to solve the problem:
http://forum.xda-developers.com/viewtopic.php?t=33191
Or if you're unable to open the link:
make the update w i t h o u t any card (sd-card and sim-card) and you'll see: it works. Maybe you've to run the update twice without changing anything!
Teja
Hi,
I had a similar problem, system and unit both indicated a successful ROM flash but after the reset remained in bootloader mode ("Serial v1.00).
In the end I did a final JasJar ROM flash, then did the radio only ROM flash and after radio done, a reboot worked.
Maybe try the 1.04.02 radio only ROM flash and see if that works.
Note: during the last two ROM flashes I too had removed the SIM and SD cards.
Note: I had removed the SIM and SD cards for a number of ROM flashes prior to that, so I know how you feel finding out that wasn't the quick fix I read. But try all that in combination.
Regards
Michael
most of the time reviving a dead universal is easiest with another rom upgrade of the radio flash.
If your universal boots in usb mode (bootloader), I can confirm your universal is dead. Mostly caused by using an upgrade program that was not made for the universal. For instance using a cracked magician upgrade program to force universal upgrades. In most cases this will get you a dead universal which can easily be repaired by doing an aditional radio rom upgrade (even if you already have that radio upgrade)
Hi,
I can confirm that in the 2 instances of bricking my device (unable to get out of bootloader mode) that the radio only upgrade (1.04.02) got it working again.
I've done this for both the JasJar and Qtek ROMs (currently running Qtek).
My unit is a Dopod 900 originally purchased in Taiwan.
Regards
Michael
i had the same problem with the QTEK of my principal after I upgraded his ROMs.
(after the hard reset, the pocket remained in bootloader mode).
you can solve this problem in a very simple way:
you have to launch the bootloader installation (BL1.01_RUU_UNI_V.1.2.EXE) from the PC (still connected with the PPC through USB) while the PPC is in bootloader mode (on your display you see "USB > Serial 1.01" or something like that).
then you do a SOFT reset and the pocket boot normally.
very simple.
i hope to be helpful to someone.
Yep, i agree with u parallel666killer, it worked by just reinstalling the bootloader (BL1.01_RUU_UNI_V.1.2.EXE).
I've been using Mun_rus's WM6 ROM for quite a while and seeing that PDAVIET's rom was built on a more recent WM6 ROM I decided to flash PDAVIET 2.07.06.PV.
Since then I cannot flash anything on my Trinity, the update utility starts and when the progress bar reaches around 84% half the screen on the Trinity goes funny. The progress bar on the PC reaches the 100% (while the screen on the Trinity goes blank slowly slowly) but upon restarting the device PDAVIET ROM loads up again intact as if I have just done a soft reset!
I've even tried flashing WM5 again but without any success.
Trying to flash Hard-SPL does not work either and I'm running out of ideas now :-( Anyone else has this problem please? I would love to try flashing a ROM with an original IPL SPL but cannot find one. My bootloader currently says IPL 1.5/SPL 9.99.CP.
Yes I am having a similar problem. It starts to flash then stops reboots and on my pc says image fiile corrupted. I have re downloaded and extracted the files but it happens everytime. However. My trinity when it reboots is stuck in the splash screen.
I had a similar problem, though not quite what you're describing. Try removing the Mini SD (storage card) before flashing.
Also, try entering bootloader fisrt before before flashing from PC.
Hope that helps.
i have the same problem...
i get 100% done and than it is still the old one..
Well, I have now sorted it. Go to this link read first post and download and use the unbrick.
http://forum.xda-developers.com/showthread.php?t=308691&highlight=splxploit-windows
I had to run it 3 times but it has worked and now I have flashed a new rom on it and it is working fine now
deniser said:
Well, I have now sorted it. Go to this link read first post and download and use the unbrick.
http://forum.xda-developers.com/showthread.php?t=308691&highlight=splxploit-windows
I had to run it 3 times but it has worked and now I have flashed a new rom on it and it is working fine now
Click to expand...
Click to collapse
I've run the splxploit a couple of times as well. It seems to finish the process succesfully but the problem persists :-( And mine is not stuck on splash screen, the device boots normally, it's just that whatever I flash does not work. Any more ideas please?
I tryed the all i think, read the all forum up and down, started in different ways, but no rom of SSL apply...
What is that!
I am stuck with this rom?
Any of the pro cookers can help with this please? I just need to understand what could be wrong, not necesseraly a solution
capeli said:
I had a similar problem, though not quite what you're describing. Try removing the Mini SD (storage card) before flashing.
Also, try entering bootloader fisrt before before flashing from PC.
Hope that helps.
Click to expand...
Click to collapse
Hey many thanks Removing the miniSD solved my problem I flashed at least a 100 ROMS in my life and never bothered removing the memory card before ... but there you go
hi, i had the same problem. i flashed my trinity with original htc rom and after that when i tried to flash with any other rom it gave me success message after every try but in my phone there was still the same htc rom. i used that : http://forum.xda-developers.com/showthread.php?t=293632 AND IT WORKS. FROM THE MOMENT WHEN I USED THAT FILE I FLASHED MY TRINITY 2 TIMES WITH THE SAME ROMS WHICH DIDN`T WORKED PREVIOUS. you need to copy that file to your trinity and follow the instructions from the readme file. in my case i only opened it ,it started bootloader mode ,i disconected usb and connected it again and started ROMUpdateUtility with rom which i wanted.
interesting... so why does the miniSD card affect the flash?
kta- had you tried running sspl and then flashing during your failed attempts? (just curious)
I have a major issue here. Please bear with me.
I flash my phone to the official 6.1 rom a few months back. Now I recently decided to try a custom rom by NFSFAN. So first thing was to flash the bootloader by IMCokeMan version 0.41. After doing that I flashed the custom rom. Once it booted up my phone kept reboot itself every few seconds or so. It turns out now that it was a battery issue, but I was sure the battery was fine and thought it was simply an incompatibility issue with the rom.
So I then tried to flash the official 6.1 rom back on, but it froze at 44% and then threw a 262 error after a minute or so. I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Then I thought I'd try the NFSFAN's rom again. So I flashed that. Once it successfully finished and started to load it freezes at the Telus splash screen and "No Radio" appears in red on the screen.
So this is where I'm at. I've tried to flash nearly every bootloader I could find and no matter what I do the bootloader always shows "SPL-0.41.coke". I can't flash any official rom including Telus, Bell or Sprint as they each freeze at different spots but consistently at the same spot individually (Telus at 44%, Bell at 30-some%, Sprint at 29%). I can flash custom roms as well as the beta wm6.5 rom but those don't fully load and give the "No Radio" error.
The ONLY rom I can successfully flash is an old 6.0 rom that someone dumped from a telus vogue. But in this rom under "Device Information" the rom is 1.11.661.1 and the radio version field is blank! And I cannot make data connections, as in I cannot connect to the internet, etc.
So my question to anyone that may know is: why am I having these issues with the radio version? How can I get rid of the SPL-0.41.coke bootloader?
And what can I do at this point? Any help from anyone is a thousand times over appreciated!
There's another copy of this thread at PPCGeeks.com:
http://forum.ppcgeeks.com/showthread.php?p=792095#post792095
-Chris
*********** bump-a-doo? *************
eeps! similar issue! did I brick it???
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
cbstryker said:
I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Click to expand...
Click to collapse
I've been reading through the ImCoKeMaN's unlocker sticky (http://forum.ppcgeeks.com/showthread.php?t=20370), and I noticed there is a "VERY IMPORTANT / Warning" referring to the 0.40 rom you used. Here's what it says:
If your carrier did not release a rom and you flash an exe of another carrier with the 0.40 unlocker you won't be able to flash ANY rom until unlocking again (this requires booting into WM)
Click to expand...
Click to collapse
then it points to this: ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe
Hopefully that helps you out.
esskay said:
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
Click to expand...
Click to collapse
hey, I answered this question of yours already over here http://forum.xda-developers.com/showthread.php?p=3526872#post3526872
Detroit Doug
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Viper Matrix Wireless said:
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Click to expand...
Click to collapse
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Detroit_Doug said:
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Click to expand...
Click to collapse
I answered his question on his thread. You forgot one thing though Doug. He doesn't have a radio. He'll need to flash back to stock before he flashes a custom. Doesn't this get frustrating???
I get the colored boot screen then "loading..." then the phone shuts off.
Any ideas on how to fix this?
TW,
Probably your phone is out of energy...
I feel stupid if it is... I'll slip it on the charger for an hour, thanks.
TW,
Battery was close to dead, duh!
However now it won't progress past the white screen "Loading..."
Thoughts or suggestions.
TW,
Flash from windows using custom rru
Making some progress.. Got a link to a good ruu, ATT?
Thanks,
When trying to flash via USB I get the error
"Invalid vendor ID".. then it quits and reboots.
TW,
Did you install hard spl?
Yes, it has hard spl.
Should I update it with a more recent version?
Try with 3.29
The soft SPL is 1.39... I'm getting a communication error now, could it be Windows 7?
I'll try at work in about an hour... thanks.
TW,
Did you follow this guide?
http://forum.xda-developers.com/showthread.php?t=433835
Already had a custom ROM on the phone so SPL should be there correct?
I'm getting error "262 Update Error"..
Tri-color screen shows SPL 1.93.0000
Trying to flash via SD, downloaded Cmonex's HARDSPL 3.29 SD and phone is just hanging at "Loading..."
I installed Android to NAND, will that have some impact on the restoration? Also will the verrsion of Android installed have some impact?
Finally got a ROM to load using the SD method... got the ROM from here:
http://f1ip.net/plug.php?e=index&f=./Downloads/KaiserFiles/Roms/OEMs
Thanks for all the help and suggestions..
TW,
I had 3.29 HardSPL, i used Android on nand for quite some time, after that i decided to flashed back to WinMo to check something out, in one of the guides, it told me to put the kaisimg.nbh and kaisdiag.nbh, (i had flashed back to WInMO several times but never included the Kaisdiag.nbh, since the guide mentioned it i thought it was something good to do)
i used the official WM6.1 and entered bootloader as usual... then my device reset in the middle of flashing...
When i tried again bootloader got stuck at 'Loading...' and the bootloader was now showing 3.34.000
Now i am unable to flash the windows ROM or HardSPL as they all got stuck in the bootloader at 'Loading...' also tried with bootloader in USB mode... nothing
Please help me... thanks in advance
BTW, luckily the android kernel was still functional and i can use it for now...
I posted this in the TyTn General Discussion section but since i got no reply for days, i reposted it here, so sorry in advance for the double thread.
Put the kaiser in boot mode, connect to a pc and flash an original rom from windows. Then reflash hard spl.
l1q1d said:
Put the kaiser in boot mode, connect to a pc and flash an original rom from windows. Then reflash hard spl.
Click to expand...
Click to collapse
Thanks for the reply... i tried this, dont know if i did something wrong but it still got stuck, i used the stock 6.1 asian, it was originally a swedish kaiser so do i need that particular rom?? i will try again...
I tried RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.rar but while it was flashing, it got to 1% on the computer and then the device just resets
It said Error [294]: Invalid vendor ID
the update utility could not be used for your PDA phone on my PC
Finally solved... i went to htc website and downloaded the update using my phones serial number... i successfully flashed back to WinMo using that ROM... now i can use hardspl again... thanks for all the help