Hello.
Had a previous problem with my O2 Atom.. It freezes most of the time, when i tried to soft-reset the device.. it freeze at start-up (at the O2 Screen)..
Ive tried reflashing the ROM (both WM5 - Quanta and WM6 - Master Jiggs) via bootloader, but after reflashing the device, it will also still freeze at "Device clean boot".. I've just reflashed my atom (again) and i cant use it no more
Ive managed to go to Diagnostic Mode, All 5 test went well except for the flash test (failed).. Does this mean i have a bricked atom?
Also, Ive already tried removing the battery and putting it back in after 2 days (well, just to be sure..) but still the same problem.
Please help me bring my atom back to life.. no social life here
Thanks!
Alibot
I'm not sure what the exact problem could be but you could always try flashing with a new/empty SD card with just the ROM you want to use and see if that works.
Related
Please has anyone had this problem, I know its old hat now but I just want to have 2003 on the phone, I can load 2002 no worries, works every time without fail but if I load 2003 it always gets stuck at boot up, I have tried a few different roms and all the same problem, I even tried 2003SE over 2002 through activesync and the same problem. I use sd to upgrade and all seems fine until boot up after the rom has finished loading.
I have spent hours searching the internet and nothing.
Any advice would be awesome......
stuck on boot screen
Have you tried just leaving it alone for up to an hour ,i have had a similar problem on my wallaby (O2 XDA) and i left it as i had to go out and when i got back in it was waiting for me to set the screen etc. If you then go into explore on microsft sync and go to the windows\startup folder u can see what programs it is loading that your device doesn't like. If it doesn't solve the problem then at least you have tried
stuck on boot screen
Have you tried just leaving it alone for up to an hour ,i have had a similar problem on my wallaby (O2 XDA) and i left it as i had to go out and when i got back in it was waiting for me to set the screen etc. If you then go into explore on microsft sync and go to the windows\startup folder u can see what programs it is loading that your device doesn't like. If it doesn't solve the problem then at least you have tried
I have left it for two days but yes anything is worth a try. What I can't understand is I had 2003 and 2003se on it about a year ago, then someone borrowed the phone for about a 10months and wrecked it and it wouldn't work so redid the 2002 rom and it worked but I have never been able to get 2003 or 2003se it boot from boot screen, it not my boot loader is it? I have 5.15
Thanks for the help
Well try this
It seems very strange indeed but i have had problems reloading all sorts of roms back into my wallaby,even the original o2 rom wouldnt boot for me and i had to reinstall 2003se ,which worked fine so i have the complete opposite of what you have.I.e. i can put 2003se on it but i cant put 2002 back on :shock: The only other thing i can think of is that maybe its the version of rom that you are trying to install?
Hi all,
Since last friday I'm the happy owner of an S200, until sunday atleast. After a soft-reset, initiated from windows, my device won't boot anymore. It hangs in the red-green-blue bootloader screen (says: IPL 2.09, SPL 2.09). I've tried soft-resets and hard-resets, but the device would consequently keep hanging in the bootloader.
So for the past few days I've been searching the web and just managed to update the ROM. I was expecting that updating the ROM succesfully would mean my device would boot again, but it still keeps hanging in the bootloader (saying IPL 2.09 SPL 2.15 now, so the update did take place).
Does anyone has any idea whats wrong with my phone? Or how to fix this? Please help.
* bump *
I've been searching further and tried to do a SD dump, but I'm getting the message I don't got enough rights to perform a SD dump. This meens my S200 isn't CID unlocked. Is there any way to CID unlock the device without the need of booting into WM?
The solution to your problem
Hello, if you are having bootloader screen right after starting your mobile (prophet) check if your camera button is depressed since i had the similar problem. In my case i had to disassembly the phone in order to fix it. Right after fixing the button it worked fine
hi syzzer,
i really feel with you - why? - i have the exactly same problem. after i tried to upgrade my rom from o2-germany to another one the device isn't starting anymore and hangs in the beautiful-colored bootloader. and now, if i just even want to re-install the same or another rom, doesnt matter which one, the s200 wont start again. i think this is a really unlucky situation for us to stand alone with our weak pda =) hoping for more help, otherwise we have to take up our warranty and try to get it fixed by the store we did buy it (if a rom-update damage is still in warranty )
good luck
budy!
awechris said:
Hello, if you are having bootloader screen right after starting your mobile (prophet) check if your camera button is depressed since i had the similar problem. In my case i had to disassembly the phone in order to fix it. Right after fixing the button it worked fine
Click to expand...
Click to collapse
in my case, the camera button is not pressed in... i truly don't know what to do hopeless? mhm?
greets!
budy!
hello Syzzer
I have the same problem, but i make a soft reset and it works.
Camera but + Com Button + Power
Wait until message appear.
You Get the message : For Hard reset press send
If you choose other key the system boots normaly.
I had already tried all your suggestions, but nothing seemed to work.
About a month ago I bought a Trinity. In the mean while, I forgot I had put my S200 in my bag and carried it around for a month. When I found it a week ago and started pressing random buttons, it suddenly booted and has been working ever since! The problem has gone as mysterious as it came. I can only imagine there was some hardware failure / dirt in my device that caused the trouble and is now gone / moved to some place it does not do harm. Because I already bought a Trinity, I gave the S200 to my brother. He's been using it ever since and did not have any problems. So keep your head up, there's hope!
I m also having the same problem
Now I am having the same problem, no button is pressed, and I can not install the NVID ROM
Actually I can install only a few ROMs, the NVID ROM was working before on my Neo perfectly but, I think it can be because I have changed many ROMs, from a month, actually I have tried different WM6 ROMs and I used NVID ROMs mostly for Step 1.
Now when I install any ROM, it shows a msg some nbf one after 80% or 95%
It can install the pdaviet first step ROM, but now the problem is that it hangs very much and it can not start Wifi, it has stopped working, a few more ROMs i have tried, but the WIFI is completely stopped.
When I press it in communication manager, it will show busy icon for a few seconds and will not start it in end.(I tried it in both WM5 and WM6, same problem, I also tried after soft reset and hard reset, the problem is still there)
Please someone help me out.
hi all,
my jasjar had an error while upgrading to ranju 7.7,
i tried to reset, didn't came back,
hard reset neither,
i went to bootloader mode, i could,
i connected it again to the pc, it showed usb,
i tried to flash to Rom that was working previously it arrives to 7% than stops,
what should i do ...
i tried to flash with official rom, it says that the rom wasn't designed for this model, it has worked before...
please help...
Hi,
if you search in the ranju's thread there's the solution.
You could have the doc corrupted. Simply read the wiki,
you must use mtty to format your device and then reflash the rom you want (with radio rom also).
Had similar problem
upgrading Imate JasJar to Ranju 7.7, only at first it showed as success, then it started behaving funny during customization, then failed to customize, then got stuck on Windows 6.1 green flash screen and eventually refused to budge beyond blue Imate screen with versions info. I tried everything, a few dozens of hard resets returned me to the same problem, removing the battery didn't do much and mtty didn't show USB as available option, so couldn't even use that. I was pretty much stuck solidly and for a while. At my wits end I read that problems like mine are associated with DOC corruption and my JasJar is as good as dead, quite a few people suggested to those who are in the same position to throw their bricked babies away, as there is no economic solution apart from sending it for service where the corrupted chip may be replaced. What do you know, I followed wiki recommendation and entered a boot screen by pressing light power reset, then just flashed back to Ranju 7.6 and my JasJar was brought back to life!!! The update went without a glitch and everything is working fine. I guess I will keep the 7.7 on my O2 and 7.6 on my Imate for now, won't be risking an update anymore on the JasJar, don't think I have much hair left after all the pulling I did trying to bring it back to life. Hope this helps someone in the same predicament
jokove said:
hi all,
my jasjar had an error while upgrading to ranju 7.7,
i tried to reset, didn't came back,
hard reset neither,
i went to bootloader mode, i could,
i connected it again to the pc, it showed usb,
i tried to flash to Rom that was working previously it arrives to 7% than stops,
what should i do ...
i tried to flash with official rom, it says that the rom wasn't designed for this model, it has worked before...
please help...
Click to expand...
Click to collapse
does it turn on at all?
Does the device turn on at all after a hard reset?
Dude, I had a same problem it rectified though, check following of my blog...
http://jay-joshi.spaces.live.com/blog/cns!851D717EDFF14CEC!3258.entry
or
http://buzzdev.net/read.php?40,13307,page=1
Rarest_Kind said:
Dude, I had a same problem it rectified though, check following of my blog...
http://jay-joshi.spaces.live.com/blog/cns!851D717EDFF14CEC!3258.entry
or
http://buzzdev.net/read.php?40,13307,page=1
Click to expand...
Click to collapse
Problem resolved?
Hi!
Please someone can help me?
I have a O2 XDA Exec with a SDHC 8GB...
I'm the second or third user that own this device. Because this, I don't know about roms upgrades with precision, but it's running WM5.
All was work fine... But some days ago, it was stopping in a black screen when I perform a simple soft reset...
I tryed remove the battery, all the cards (include the simcard), but the problem still there...
I tryed a hard reset, but the problem still there...
I tryed all that I know, but the problem still there again...
Trouble details:
The O2 XDA Exec aleatory freeze in a black screen after soft reset.
I persists pressing Reset key with some seconds intervals, untill it (aleatory) turn on the screen and load WM5.
The Bootloader and the HardReset screens comes normaly when calleds.
When I perform a hardreset, immediatly happen an freeze without the new system never was loaded before.
I disassembly the device and test the RESET key... there is no problem.
My big suspect is something corrupt in device's bootloader or other "BIOS" program.
I use many PDAs for a long time (8 years ago), but never see nothing like that...
Seed someone something like this before?
How can I solve this problem?
Can someone help me please?
Thanks a lot.
P.S.lease, excuse my poor english...
wfreed said:
Hi!
Please someone can help me?
I have a O2 XDA Exec with a SDHC 8GB...
I'm the second or third user that own this device. Because this, I don't know about roms upgrades with precision, but it's running WM5.
All was work fine... But some days ago, it was stopping in a black screen when I perform a simple soft reset...
I tryed remove the battery, all the cards (include the simcard), but the problem still there...
I tryed a hard reset, but the problem still there...
I tryed all that I know, but the problem still there again...
Trouble details:
The O2 XDA Exec aleatory freeze in a black screen after soft reset.
I persists pressing Reset key with some seconds intervals, untill it (aleatory) turn on the screen and load WM5.
The Bootloader and the HardReset screens comes normaly when calleds.
When I perform a hardreset, immediatly happen an freeze without the new system never was loaded before.
I disassembly the device and test the RESET key... there is no problem.
My big suspect is something corrupt in device's bootloader or other "BIOS" program.
I use many PDAs for a long time (8 years ago), but never see nothing like that...
Seed someone something like this before?
How can I solve this problem?
Can someone help me please?
Thanks a lot.
P.S.lease, excuse my poor english...
Click to expand...
Click to collapse
Have you tried to install another ROM? with a different Bootloader
Battery?
Check the Wiki, there is a lot of usefull info there
Good luck
Hi, orb3000!
Thanks for your very quick answer!
Are there real chance this solve this kind of trouble?
Suggest someone a good, quick and stable WM5 rom to I try?
Are bootloaders upgradibles without need all rom update??
I'm trying understand what is happen. All we knows no erros are acceptable in ROM (firmware) upgrade... so...
Can someone explain to me how is made the XDA Exec (HTC Universal) boot routine??
Eg: In x86 PCs, first it load the bios, the bios load the setting that said to PC where is HD, the bios load the Master Boot Record with partition table, the partition table said to bios where is the active unitie with FAT, the active FAT said to bios where is the boot file, the bios said to processor load boot file to the ram and execute, etc.
Thanks!
wfreed said:
Hi, orb3000!
Thanks for your very quick answer!
Are there real chance this solve this kind of trouble?
Suggest someone a good, quick and stable WM5 rom to I try?
Are bootloaders upgradibles without need all rom update??
I'm trying understand what is happen. All we knows no erros are acceptable in ROM (firmware) upgrade... so...
Can someone explain to me how is made the XDA Exec (HTC Universal) boot routine??
Eg: In x86 PCs, first it load the bios, the bios load the setting that said to PC where is HD, the bios load the Master Boot Record with partition table, the partition table said to bios where is the active unitie with FAT, the active FAT said to bios where is the boot file, the bios said to processor load boot file to the ram and execute, etc.
Thanks!
Click to expand...
Click to collapse
Hi
here you can find one: http://forum.xda-developers.com/showthread.php?t=409966
The other questions I am no the master, so let´s learn form them
Cheers
Thanks a lot all yours!!
I solve my trouble reflashing my WM5 rom...
I used the Jwrightmcps Crossbow ROM Update 2.12.08 WWE, very fast and very stable WM6 rom! Realy a amazing work by our friend Jwrightmcps!
Including, I want suggest here that all those that still suffering in WM5 (living slowly with crashes, troubles, crashes, more troubles and this poor and slow system), try reflash your HTC with a rom like this... my device reborn!! It was dead more now is alive!!! And much more fast and stable! Before it is slowly my old Jornada 720 (206MHz), but now it realy seems have 520MHz!
Thanks a lot for all.
The link for this excelent work is HERE:
Jwrightmcps Crossbow ROM Update 2.12.08 WWE
(Download the apropriate rom to your device, folow the instructions and EnJoY!! Be HaPpY!!)
This rom don't supports 8GB SDHD cards, but download and Install 2 cabs below and it will support it:
CAB01 - SDHC_DRIVERS_FOR_C550_AND_N560_BY_GreateVK_AND_Fre ePK.cab
CAB02 - Signed_Storage_Settings_App.cab
Special thanks to big_quads for this solution!
Recently, i found a problem with my o2 atom. When i soft-reset my o2 atom, it hangs on that initial blue screen that pops up with the O2 sign on it and will not move beyond that. However, if I reset it for several times, it can start to windows interface successfully sometimes, but it failed for the most times. I have tried to take out the battery and put it back in. But the problem still exists.....
By the way, i did not update my ROM. The ROM is WM5.0 CHT(initial version).
I'll be crazy by this problem
I want to know that this problem is caused by software or hardware and how to solve it ?
Thank u in advance!!!
It is an inherent problem of O2 Roms. Try flashing with a newer ROM. If you would prefer sticking to a XDA Rom, then check out the rom by MWG.