I tried to update my athena to the dopod wwe rom after using the asukal switcher to change the UI from dutch to english.
It is sim unlocked, but not cid unlocked. Result was connection error, and white screen of death!
Almost panicked but went through all sorts of resets and always returned to "Loading........". The bootloader screen never stayed on for me to try another flash through usb! I left it on that screen for about 15 minutes and eventually the real bootloader screen came up A soft reset then brought me to normal boot up, and my device re-started again. I had formatted the microdrive in my desperation, so I now have to restore a backup.
I thought I would share this with the adventurous ones here. If it happens to you DO NOT REMOVE THE BATTERY. Just keep it in and let it return to the bootloader screen, and then do a soft-reset.
Happy holidays from sunny Africa until next week
Whoa... real adventure, bot glad to hear your Athena is OK..
Thanks for sharing your experience
A symbolic event
Yikes, that was scary for a bit. Your circulation must have had more exercise than a 100 meter run. Sounds like your pda did the easter story on you!
Watch out for the Hippo's in Africa
O
optigrouch said:
Watch out for the Hippo's in Africa
O
Click to expand...
Click to collapse
I have one for a pet
victoradjei said:
I tried to update my athena to the dopod wwe rom after using the asukal switcher to change the UI from dutch to english.
It is sim unlocked, but not cid unlocked. Result was connection error, and white screen of death!
Almost panicked but went through all sorts of resets and always returned to "Loading........". The bootloader screen never stayed on for me to try another flash through usb! I left it on that screen for about 15 minutes and eventually the real bootloader screen came up A soft reset then brought me to normal boot up, and my device re-started again. I had formatted the microdrive in my desperation, so I now have to restore a backup.
I thought I would share this with the adventurous ones here. If it happens to you DO NOT REMOVE THE BATTERY. Just keep it in and let it return to the bootloader screen, and then do a soft-reset.
hi
i did soft reset few times but still in bootloader mod..can anybody pls help?
thanks
Click to expand...
Click to collapse
use mtty.type "set 14 0" and press enter..
hdubli said:
use mtty.type "set 14 0" and press enter..
Click to expand...
Click to collapse
i think i stuck in the Flash ROM utility..tried mtty.type "set 14 0" already but still couldn`t get out...
try this )))))))))))))))
I think you are not stuck in bootloader, I think you are stuck in the Flash
ROM utility which has colors and not just the Dopod logo with a black scree.
If this is the case, here it is what I did to solve this:
I downloaded ruu_athena_dopodasia_wwe_1.24.707.3_105_6275_1.32.
00.10_108_ship, which you already did.
Decompiled the RUU_signed.nbh contained inside
ruu_athena_dopodasia_wwe_1.24.707.3_105_6275_1.32. 00.10_108_ship with
dutty's good NBH tool found at: http://forum.xda-
developers.com/showthread.php?t=296316 then I created a new RUU_signed.nbh
with the same files but it didn't allowed me to insert some items like the
SIRFBootLoader.nb and some others, so I started executed the
ROMUpdateUtility.exe again and it stopped again at 1% but with a different
error "Corrupted ROM Image" and suddenly! My device was taken out of the
Flash Utility to see the bootloader screen again! Wow! What a relief!
Click to expand...
Click to collapse
Related
Dear All,
I've tried to upgrade to ROM Hermes_1.18.416.1_1.18.416.101_1.14.00.10_WWE_Ship
and unluckly cable loosen and I reset the phone.
Since it's in the middle and can't success enter the Windows Mobile,
but the bootloader was updated to 1.06.
Now I can't flash any ROM either
HER_DopodAsia_1237074_1060010_WWE_SHIP or the new one.
The tools on "imei check" even can't recognize my phone.
Any one can help me on this issue, please?
Thanks in advance.
Try the steps here, let us know the results:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
If you don't fix it with the proposed solutions attach USB Monitor capture in text format as explained in the bootom of the page.
I have the same issue, and sent it to service, and now I have the phone back and they could not fix it, so got no radio or imei number, so none of the FAQ will work for me.
So I have an expensive paper weight.
Hi,
ME TOO!!
I recently had a power cut (yes, a lights off power cut!) that killed my PC half wat through installing the Cingular English CWS__001 1.34.502.1 09/21/06 ?? 1.16.00.00 32.53.7018.01H 14955.2.3.0 ROM onto my SPV 3100.
Now SPV 3100 will boot to the ROM I was running prior to the upgrade but I can't use the telephone. I'm also not able to rerun the upgrade as it got far enough through the process to upgrade my bootloader to 1.06 - therefor rendering me unable to load another ROM.
Before the crash I was using the Imate ROM as below and M3100 was sim unlocked and running on o2 3G
i-mate English CDL__001 1.20.305.3 07/21/06 1.20.305.104 1.07.03.10 32.41.7010.02H 14955.2.3.0 1.04
I have also tried imei without any joy.
the PDA part of my M3100 still works but the phone is dead. I have been told that if you can get the latest radio installed then you satnd a chance of the phone part working.
We need a hack to get bootloader 1.4 back on the phones.
Please help.
Thanks
My one now is a photo frame which one show "HTC" or "Windows Mobile",
at least your one is a PDA.
There are nothing in "info 2" and so nothing can be flash into it.
Is it possible to have something written CID and IMEI to phone in mtty
and let the flash rom success?
i am in the same situation like yhlee. Pof, i have reply your pm and ready to upload the result file to FTP. where should i upload to?
Thanks
oh i forgot to say, mine is even worst. as soon as i turn on the unit. it will go right into bootloader without press any button.
The USB Log is too large (around 2MB)
and can't upload, any suggestion?
Thanks.
rnc1688 said:
oh i forgot to say, mine is even worst. as soon as i turn on the unit. it will go right into bootloader without press any button.
Click to expand...
Click to collapse
This can be fixed by bootloader commands 'set 14 0' and 'task 8', will reboot your device and boot into OS again (but no GSM yet!)
yhlee said:
The USB Log is too large (around 2MB)
and can't upload, any suggestion?
Click to expand...
Click to collapse
Upload it to xda-developers ftp:
ftp://xdaupload:[email protected]/Uploads/Hermes/
USER: xdaupload
PASS: xda
POF, file have been uploaded, file name= rnc1688
Thanks
'set 14 0' and 'task 8' didn't work
@rnc1688: It starts the flashing process, but you get a "CID not allow (255)" error because your CID is corrupted and you are in bootloader 1.06.
Is not booting WM5 after "set 14 0" in mtty.exe? If it's not booting WM5 you'll not be able to flash bootloader 1.04 and bypass CID checking.
so i guess my unit is bricked now.
I've upload the file which named yhlee.txt.
However, I'm going to send the unit for service.
Hope they can fix.
Any way to make it show the bootloader screen on start-up
everytime?
"set 14 1" doesn't work after push the RESET button.
Thanks.
@yhlee: U're getting exactly the same error as rnc1688. Device in bootloader 1.06 which has corrupted CID, however you say you can go into OS, so it would be possible for you to downgrade the bootloader so it does not enforce CID checking.
yhlee said:
Any way to make it show the bootloader screen on start-up everytime? "set 14 1" doesn't work after push the RESET button.
Click to expand...
Click to collapse
Try "set 1e 1" and then "set 14 1", you'll boot stright into bootloader.
@rnc1688: If you want to go WM5 try this:
"set 1e 1" and then "set 14 0", you should be able to boot stright into OS.
no luck either
grrr!!!... command "set 14 [0|1]" is working fine in 1.04 here to switch boot into WM5 or boot in bootloader mode... probably different in 1.06??? I don't have a 1.06 now to test
Mine one is just showing "Windows Mobile" but stuck there,
but seems rnc1688 one is a PDA but my one is nothing.
I've sent to distributor for service.
Thanks you pof.
yhlee said:
I've sent to distributor for service.
Click to expand...
Click to collapse
Let me know when they fix it... i'm curious about if they will fix it with 1.06 or they will downgrade to 1.04 first.
I got a correct message back from the service company, and they will not fix a bootloader 1.06 unless the original rom has been release with it, I was told that is HTC policy on this.
Hi guys, I have some experience with rom flashing, and I did it today as usual - flashed HTC 1.35 ... Update stopped at 1%. I tried everything I could to finish the update (It wasn't my first time ). Now, after restart TyTn is flashing with LCD (black & white) & camera led. I can't do anything, even turn it off. Seems like a problem with bootloader. What should I try before i send it for repairing? Do you have any experience with T-Mobile UK? I'm the legal owner of PDA, but I don't have any receipt. Should I contact seller (ebayer) or post it to T-Mob straight away?
Thanks in advance, Jack.
Anyone please?
Check out the wiki for Tytn upgrade problems
I also had this problem, upgrade stopped at 1%....Left it for an hour and no progress. Had to stop update, which then left me at the boot loader screen (tri-color) screen. Tried Hard reset as mentioned above, no luck, still stuck in boot loader, tried to reload rom..got error 262 upgrade error
I had just run the unlocker and set device to super CID, and thought maybe that was my problem, but it wasn't
Luckily the wiki had the answer
Problem 4: Device is stuck in bootloader mode (tri-color screen)
>Disable ActiveSync: connections -- settings -- uncheck "Allow USB Connections"
Remove the battery, put it back in, connect the USB cable, power on the unit (this should allow the USB port to be opened again)
Wait a minute or two, if you get a message that device cannot be recognized just close and ignore it
Open
mtty.exe and select "USB" from the dialog box, then hit Ok.
You should see a white screen, hit enter and you should see a prompt like this: "USB>"
Type set 14 0 (do not copy and paste!!!) and hit enter
Soft reset with stylus
OS ROM and radio version should be back and OS functional, the unit isn't a BRICK anymore!
I had to reload the rom. step 8 did nothing, but return me to bootloader. This time the rom upgrade took about 45 minutes to complete. Weird, but it worked...This is first time in at least 4 rom upgrades with this device and at least 50 other rom upgrades that I ever encountered any issues.
POF...Thanks for the great wiki
http://wiki.xda-developers.com/index...ame=HTC_Hermes
Unfortunately, when it hanged on 1% connection was totally lost. Everytime I tried to run rom upgrade/unlocker/spl downgrader is said no connection. Now I don't have bootloader screen, only flashing LCD & camera diode. Any suggestions?
If you can't get the bootloader running then a service center will be the only solution I think.
Has anybody found the solution to this problem, my phone is doing the same thing. Can't get it into bootloader and screen & camera flash just blinks? I tried everything but to no avail.
Hi mate, have you done anything special or it goes bricked "without help"? I I still haven't put it to RMA because there's no T-Mobile in Republic of Ireland and I'm 2 lazy to go to Belfast
jackass_ass said:
Hi mate, have you done anything special or it goes bricked "without help"? I I still haven't put it to RMA because there's no T-Mobile in Republic of Ireland and I'm 2 lazy to go to Belfast
Click to expand...
Click to collapse
It's bricked trying to update it!!! If i could just get it to the bootloader, i can probably revive it but can't do anything. Can't access USB or nothing, I'll guess I'll send it off to a repair center.
Are there any good repair centers in the US???
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up.
Now, the phone is dead completely. I can''t even enter bootloader mode.
Is there a possible way that I can still save it??
Help!!!!
Have I bricked my device? Help plz
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up. Can't remember exactly, but like some address can't find error.
Now, the phone is dead completely. I can''t even enter bootloader mode. Only when I take out the battery and plug in the charger cable the red light comes on. I looked the upgrade problem page, my symptom doesn't match any.
Is there a possible way that I can still save it??
Help!!!!
I had something similiar happen a little while back. What I did was pull the battery out and leave it out for a while, maybe a few minutes. I then put the battery back in and held the two side buttons and hit the reset button to put me into bootloader mode. I then cabled it to my computer and flashed a new OS via mutty. That got my phone back and operational.
@float. Nuh, it didn't work on my brick. Prob i will have to take it back to Tmobile if they kind enough to repair the no warranty phone i bought on ebay.
Sorry to have opened a new thread, I was so desperate.
Plz delelte it.
how exactly did you try to update the radio using mtty?
I download the 1.27 shipped radio rom. P.S. It seemed to be a german version, not sure whether that caused the disaster.
Using NBHextract to get the single GSM.NB file, then in MTTY, typed
USB> task 32
USB> lnb GSM.NB
Before flashing, just had it upgraded to the HTC AKU3.3 OS rom only. The old version radio rom version before flashing was 1.18.
Maybe the order i flash is wrong. I flashed OS first then the radio rom.
just guessing
ok, you loaded the radio rom code where os.nb should go. That may have caused mega bad blocks in flash. Can you even get bootloader mode if you reset using Wiki directions to obtain Tri-color bootloader?
Yes. I have tried many ways wiki suggests. Such as removing the battery leaving it more than half an hour and plugging it to the usb cable without battery. still can't get to the tri-color bootloader mode. Basically, I just can't turn on the phone.
If you connect it to the computer, can it communicate w/the PC? If you hear the windows tones try opening up mtty and see if you can communicate.
i'm stuck in the same place
for me it happened during extrom flash
Try removing the battery for a bit (a few minutes, maybe half an hour). Then, put the battery back in but don't plug the usb cable in. After that, hold the two side buttons as if you're trying to get it to go into the bootloader. Hit the reset button a few times with your stylus and see if that gets you to the bootloader. That's what worked for me.
tried that
tried removing battery and connecting usb
nothing helps
is there a place that fixes tytn in belgium ?
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
diffda said:
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
Click to expand...
Click to collapse
well your not supercid... your still locked to qtek
Look here and unlock your phone before doing any flashing!
http://forum.xda-developers.com/showthread.php?t=295751
to late i ve done that tow day's ago , now the only way to make my phone back to life, PB + KITL method i think
god bless KITL
Hey everyone,
i am so upset and lost; words cannot describe it.
So i installed WM6 black shadow and everything was working except for SMS and MMS. So i am like ok i can live with that for a day till custel' rom will come out. SO i decided to upgrade the radio to 1.43 and boom here is where the problem started, No GSM on boot up. Phone doesn't boot up. I tried install 1.40 over again, still nothing. No i tried upgrade the the rom itself, i tired custel 2.5 and nothing and i tried the new Cingular rom, still same problem. the roms flash all the way. I read the wiki, and saw the mtty.exe thing but that doesn't work for me either. I am really lost and don't know what to do.
Specs
cingular 8525
hardspl v7 cid and sim unlocked.
PLEASE HELP
4.13?? 4.10??
Where did you download these radios from??
or do you mean 1.41 or 1.43??
Yeah thats what i meant, 1.40 and 1.43 sorry. You can see how upset i am.
Thanks Again
Well, if your phone turnes on .. it's not a brick.. lol .. it IS fixable... When you turn the phone on does it go RIGHT to the 3 colored screen?
@dan5.5
You need to read the unbricking thread about this, all the info you need is there.
http://forum.xda-developers.com/showthread.php?t=286755
If you are superCID I don't see how flashing a radio could have messed up your phone.. that's weird.
mrvanx said:
@dan5.5
You need to read the unbricking thread about this, all the info you need is there.
http://forum.xda-developers.com/showthread.php?t=286755
Click to expand...
Click to collapse
I read everything there and nothing seems to be working for me. I woudnt post for nothing. i dont want to be annoying.
OK im going to repost what ive said on 4wm:
We need to check if your Radio BL is functional, firstly leave HardSPL v7 on there and connect to the bootloader via mtty (il assume you know how to do this).
Issue the following commands and tell us the results please:
1) checkimage (this shows the CRC checksums of each component...id expect the radio image to show a timeout....
2) info 2 (This will verify that your CID is intact)
3) info 8 (does a bad block check)
Once youve done this, flash SPL 1.10.oli to the device and once again connect up to mtty.
4) 'rtask a' this will enter the radio bootloader you will see "Enter Radio Bootloader" or something to that effect
from now on when you type the text does NOT appear on the mtty screen.
5) 'rversion' this should return your radio bootloader version...now unfortunatly if you see nothing...you radio BL is dead and sorry your device is royally bricked. If you get something returned back onto the screen (most probably containing the text '0108') then your radio BL is fine.
Click to expand...
Click to collapse
do as instructed in that text, post your results here.
I cant falsh spl 1.10 oli. it gives me the 260 error.
the 260 error is not connected via USB right? .. weird... have you tried taking your battery out for a couple minutes, then booting into BL mode? sounds weird but this worked for me when I didnt flash hardSPL firsl..
hey mrvanx's
I can't downgrade the hardspl to 1.10, anyhelp.
I cant active sync, the phone doesnt boot up.
Is there anyway to aviod having to respond on the phone.
hey,
i can get the phone to boot up into windows and then it freezes within a couple min. what should i do. Still no gsm message and no phone. thanks
Dan
OK, so let's try and get you to a working state - I've bricked mine a couple of times and it can be quite heart-stopping, eh?
The first thing I would do is re-download radio 1.43, just incase your current one is damaged somehow.
Secondly, download Black Shadow - I know it's not the ROM you ultimately want but the aim here is to get you working again and we can move forward from there.
First, boot up into BootLoader mode (hold down the OK button on the left side of the phone and the power button and then press the reset button on the bottom, just in case you didn't know
You should come to the three colour screen and it should be reading IPL-1.04 and SPL-2.10.Olipro. If it isn't, stop here and post what it does say.
If it everything is OK at this point, when you plug your phone into your computer, it should change to USB at the bottom. Just wait for the Found New Hardware prompts to clear on your PC and then flash the black rom - choose the hardspl option in the flash program.
Once that has finished and it is at the "tap screen to set up windows..." bit, put it back into bootloader mode as above and flash the radio.
This should hopefully give you a running phone again as I know this combination works OK as I am currently using it.
Fingers crossed, don't panic, and let us know what the results are
Cheers,
Smiffy.
Nothing is working, can some please help me. Is there anyt way i can restore the spl to the original one so i can send the phone back, i just got it like 2 weeks ago. thanks
Also i have a bad block thats what i think makes the phone freeze after i boot it up.
How can i get around this, thats seems to be the biggest problem.
Hey everyone, let me give you more info.
I can fully flash any rom and and radio,
phone will boot up like 1 out of 10 times and then freezes and thats it.
i have a bad block number 6. I have hard spl v7 installed before the phone got screwed up. I cant downgrader the spl to a lower one to check if radio stack is screwed up. Can someone please help me, if you need to ask me more info feel free.
I have a wizard 8125! i sim unlocked it earlier and began the process to soft-spl with the tmobile rom found here:http://forum.xda-developers.com/showthread.php?t=353237... well shelltool stated that it would take more than 15 minutes and i fell asleep! when i awoke my laptop had turned off and also my phone! phone now freezes at cingular splash screen, is capable or bottloader mode though! IPL/SPL are are 2.XX.XXX1 too!! PLEASE HELP!!
koolkidcrankdat said:
I have a wizard 8125! i sim unlocked it earlier and began the process to soft-spl with the tmobile rom found here:http://forum.xda-developers.com/showthread.php?t=353237... well shelltool stated that it would take more than 15 minutes and i fell asleep! when i awoke my laptop had turned off and also my phone! phone now freezes at cingular splash screen, is capable or bottloader mode though! IPL/SPL are are 2.XX.XXX1 too!! PLEASE HELP!!
Click to expand...
Click to collapse
wow did i have many spelling and grammatical errors!!LOL ...but uh... i re flashed it with wizardlove and then boring tmobile wing rom!! works great!
If you can make it to the Cingular splash screen, you should be ok. Did you hard-reset your phone after the shelltool?
CoasterMaster said:
If you can make it to the Cingular splash screen, you should be ok. Did you hard-reset your phone after the shelltool?
Click to expand...
Click to collapse
I have the same problem and yes I reset after shelltool. Now its stuck in the bootloader screen and every rom I try gives me a different error. From invalid file to phone not detected, etc. What do I do?
For anyone who gets stuck and is readin this post. If your CID unlocked and your SPL say 2.XXOlip just find and load the "wizard love rom". That rom saves people from all kinds of problems. Once you have it loaded the phone will boot up normally (you will see like some cartoons people in water on the splash screen) and you can then load other roms. In my case I loaded BlackDiamond 3.1.