This thread is for information of those who are NEWBIE’S like me and are struck by a syndrome which is between complete bricked Atom Exec and Semi bricked one (not described by anyone as yet). First of all the symptoms, my Atom Exec during a ROM upgrade stuck at Update Screen. No matter what I did, including ‘pressing the camera and soft reset key’ or ‘removing battery and while pressing camera and reset key replacing the battery again’, for going in bootloader my Atom Exec remained on Updating Screen (of death). On attaching it through USB it would go in the upgrade processes after starting the ‘Device Software Update Utility.exe’. However on reaching ExtendedROM updation it would stop and give an error ‘ExtendedRom upgrade Fail’ like this one http://forum.xda-developers.com/sho...Atom+Exec+always+at+update+screen#post1025943
Then I also went through the bricked test as told in Wiki by removing the battery for at least 1 minute and then replace it while observing the LED lights. if the LED blinks once upon battery insertion it is semi dead. But in my case it did not even blink. then I went for diagnostic test process by pressing the camera and record buttons, and soft resetting at the same time. The diagnostic results were:
Sdram test : OK
Display test: OK
Keyboard test: Fail
Flash test: Fail
Serial test: OK .
The first thing I did was search the complete forums (as ordered by our great seniors specially homer285 who is always ready to strike) and the result at the end I got was to ‘GET MY ATOM REPLACED OR REPAIRED’ as it was bricked.
Then I got an idea and got hold of the original O2 ROM ‘Xda-AtomExec-ENG-20060614_R060428N_EX0028.exe’ and extracted all its files to ‘C:\WINDOWS\Temp’ directory. Afterwards replaced ‘Device Software Update Utility.exe’ with the one from Chartreux’s ‘ATOM_EXEC_WM6_AKU0.7b_20071216A3WWE_6MBPP.7z’. After attaching the USB I started the upgrade and instead of ‘ALL’ I selected ‘OS+EBoot’ only by pressing tab key and down arrow key. And VIOLA my Atom Exec started rebooting in the normal mode after upgrading. However, it stopped at the Windows screen while booting. Afterwards I applied the great Jiggs formula of semi-dead bootloader explained here http://forum.xda-developers.com/showthread.php?p=1534132&highlight=To+get+back+to+the+bootloader%2C+do+this+exactly+in+chronological+order#post1534132
And now my Atom Exec is again dancing to the tunes.
Man am I happy and hope it helps some one else like me.
Great one thanks it saved my Atom Exec
bro i saw that u hae atom exec rom to wm6 and the touchflo version. can i have i full copy of that and a full detail instruction to upgrade it, becuase i just bough the phone and im damn worry to upgrad, cause scared spoilt the phone, or facing any error then i die. thanks man
claven86 u can get fresh copy alongwith instructions here http://forum.xda-developers.com/showthread.php?t=352622
For detailed instructions on the different issues of upgrading to WM6 read in detail here http://forum.xda-developers.com/showthread.php?t=352221 and in here http://forum.xda-developers.com/showthread.php?t=333165 and also remember:-
Upgrade Procedure:NEVER ATTEMPT TO UPDATE YOUR DEVICE USING SD CARD FLASHING!!!
1. Unzip the file into c:\windows\temp
2. Connect device to PC under Windows XP using USB cable
3. Make sure all the files inside c:\windows\temp
4. Run the Device Software Update Utility.exe
5. Follow on-screen procedure
I'd love to say it worked for me too...... But it didn't :-(
Mine's an Atom, I'm running Windows XP.
I've successfully run the Charteaux DSUU with the files from an original WM5 ROM through through the OS + Eboot option.
Then on re-trying to upgrade it hangs at the Entended ROM again. Gives the error MOT Sync Fail 0x2b, and the xxxxxx's get as far as P...in please. I'm waiting on average 40 minutes each go. Same spot, every time, regardless of what rom's used :-(
Any idea's for me to try?
Cheers,
How many stages are there? Its stage 5 its hanging at. I'm wondering if I can try upgrading the radio separately...
I think u cannot do the radio only with ‘Device Software Update Utility.exe’. However, you can upgrade just the os+mot. Please read the complete Wiki on the subject as urs is an Atom and there is little difference in upgrading/Un-bricking a device.
hey there been a member for sometime and have tried to search for a solution to my problem and am abit confused.
and sorry if its such a newb question (dont burn me for it)
i have an o2 atom exec (using RC3 rom with touchflo) and yesterday i /soft reseted/ the phone because it was acting funny, after the reset it would be stuck at the startup screen and would not load past that the whole day, so i waited and re-tried in the evening.. the same thing occured... i was at the time able to load into bootloader (MN2) but then could do nothing else.. so i searched throughout the forums and found a post by 'chartreux' http://forum.xda-developers.com/showthread.php?p=1684559&highlight=EBOOT.NB0 but had not read the entire post and proceeded to load (mn1) onto my phone via mini sd card and it worked, my phone was working again, it performed a hard reset and restored it to factory settings (ie: calendar, msgs, contacts, software all gone) and phone is working normally again... since it has done this i wanted to update to 'wm6.1 atom exec rom' just to be up-to-date and have synced it via activesync and have run "DSUU" but my phone just restarts and loads the current rom i have installed! and just repeats everytime i have tried (have tried atleast 50 times)
so my main question.. is my bootloader dead? i know my phones not bricked since its still working perfectly im just not able to upgrade my ROM but can still do everything else (such as browse through files, run programs, make calls)
and last of all.. can anybody please help?! as i am at the point running the phone over with my car!
and once again am sorry for the stupid question.. =/ and thanks for hearing me out!
cheers!
stylistik said:
hey there been a member for sometime and have tried to search for a solution to my problem and am abit confused.
and sorry if its such a newb question (dont burn me for it)
i have an o2 atom exec (using RC3 rom with touchflo) and yesterday i /soft reseted/ the phone because it was acting funny, after the reset it would be stuck at the startup screen and would not load past that the whole day, so i waited and re-tried in the evening.. the same thing occured... i was at the time able to load into bootloader (MN2) but then could do nothing else.. so i searched throughout the forums and found a post by 'chartreux' http://forum.xda-developers.com/showthread.php?p=1684559&highlight=EBOOT.NB0 but had not read the entire post and proceeded to load (mn1) onto my phone via mini sd card and it worked, my phone was working again, it performed a hard reset and restored it to factory settings (ie: calendar, msgs, contacts, software all gone) and phone is working normally again... since it has done this i wanted to update to 'wm6.1 atom exec rom' just to be up-to-date and have synced it via activesync and have run "DSUU" but my phone just restarts and loads the current rom i have installed! and just repeats everytime i have tried (have tried atleast 50 times)
so my main question.. is my bootloader dead? i know my phones not bricked since its still working perfectly im just not able to upgrade my ROM but can still do everything else (such as browse through files, run programs, make calls)
and last of all.. can anybody please help?! as i am at the point running the phone over with my car!
and once again am sorry for the stupid question.. =/ and thanks for hearing me out!
cheers!
Click to expand...
Click to collapse
what version of your bootloader now? MN2 or MN1? if still MN1 please read again the thread to update your bootloader to MN2 (since your device is ATOM EXEC).
and after done, please check when you run DSUU, see on the left bottom whether have a drop down box or not? if yes then choose "ALL"
hope this can help to solve your problem.
hey! thanks for the reply mate!
but im not sure i cant check the version of my bootloader...
wont let me get into it by pressing camera+SR or camera+off button..
just boots straight into the operating system.
and, as for the DSUU it just restarts the phone after i choose all, and goes through to the today screen on the phone, and as for the DSUU update its stays at the screen which shows "The current software is now being updated from your device."
followed by an error appearing after a few minutes showing " No download target was found!!" even though my atomexec is synced
which is then followed by the "connection error" screen.
please help.. this is seriously pissing me off...
stylistik said:
hey! thanks for the reply mate!
but im not sure i cant check the version of my bootloader...
wont let me get into it by pressing camera+SR or camera+off button..
just boots straight into the operating system.
and, as for the DSUU it just restarts the phone after i choose all, and goes through to the today screen on the phone, and as for the DSUU update its stays at the screen which shows "The current software is now being updated from your device."
followed by an error appearing after a few minutes showing " No download target was found!!" even though my atomexec is synced
which is then followed by the "connection error" screen.
please help.. this is seriously pissing me off...
Click to expand...
Click to collapse
try to downgrade again your bootloader to MN1 (please do it step by step). as long you can secure your bootloader, hopefully you can resolved your problem.
remember to upgrade again to MN2 once you able to downgrade to MN1 before try flashing to wm6.1.
good luck.
still cant access bootloader.. even when trying DSUU it just boots straight into the operating system, when trying to update and also i tried the MN1 bootloader again and tried to get into it... still nothing.. it just resets, i tried it with my 4GB mini sd, 2gb msd, and a 64mb mini sd.. could not get into it... sigh...
Ok try a deep breath and read all the posts on dead boatloaders and other upgrading problem posts through and through. Then try to change ur USB cable and what system are u using i.e XP or Vista????
thankyou kindly, for the suggestions i have been reading through alot of posts and tried alot but.. nothing so far.. i guess its not too bad since its stuck on windows mobile 6 with abusalzas rom..
im just annoyed i cannot upgrade to the latest 'rom' and since my phone 'had' to perform a hard reset why not update so yeh.. and i am using windows xp for my computers os.
Did u change the USB cable mate, once I had to do it and the interesting thing is that the same USB cable was working perfectly for other things but causing problems when connecting to my Atom Exec.
yeh tried it with my old v3 cable didnt work has the same outcomes.. sigh.. i might try that dead bootloader hardware and software recovery from this post by Alex_Beda & 1stMASTER
http://forum.xda-developers.com/showthread.php?t=336278
what you think?
although my phone doesn't resemble there symptoms list.. as it still works and everything just cant get into the damn bootloader.. :/ when done manually and when trying to upgrade..
Did u read this mate ?????
http://forum.xda-developers.com/showthread.php?t=358442
You just try the DSUU with upgrade "OS" only and not "ALL".
alright cheers buddy! ill try it out and i hope it works!!
bahh.. didnt work =( just restarted my phone and gave me a connection error screen on my computer....
Actually i have the same problem, i tried to get into the bootloader by press and hold camera + reset button it just restart and load the WM
Dead atom exec
My atom exec having problem ( dead ), so after press camera reset sw my atom can booting normaly but touch screen function only for entering password and then touch screen not response anymore. I check the system information by touch the button (manualy) but IMEI not ready and Radio not ready.
Pls someone can help us.
o2 atom bootloader
hello
my o2 atom bootloader screen mn1 dignostic manger screen remains after rom flashing .i tried flashig orginl rom and pedvit rom but bootloader screen comes again .not starting my mobile please help
Hi, I`m having some serious issues when trying to flash my HERMES. As far as I can tell, it is SIM Unlocked, but not sure if it`s CID unlocked. it`s SPL-1.06, and I can't seem to get it to install HARDSPL. I have tried, and tried and tried and tried. I've tried flashing VIA SD-CARD, but it just says "LOADING" and displays a number at the top, then goes back to the bootloader screen.
When I am flashing via the wizard, it'll go into the bootloader screen, and the wizard will fail saying it cannot connect "CONNECTION ERROR"...
I am at my wits ends, and cannot figure this out for the life of me. I have had 3 TYTN's now, and this one has gotten the better of me. I was able to flash both of my other TYTN's, but unfortunately I got the WSD, and cannot repair them, they are both beyond my technical knowledge of repairs...
PLEASE PLEASE PLEASE PLEASE PLEASE help....
Trying so hard to get this done...
Copied the .nbh (ren to hermimg.nbh) to my SDCARD and reset into bootloader, as I said, it just came up "LOADING" then back to bootloader....
I'd rip my hair out if I had any..
any help would be appreciated..
***UPDATE - I don't know what the hell happened, but suddenly, this bugger is letting me flash VIA SD. It's a damned miracle!
Just out of the blue, it asked me to flash via SD in the bootloader. Thank goodness! After 3 hours, I finally got it working..
Cheers all!
if you need more info, just ask, I will provide all I can....
need help ,during the upgrade it was around 15% that the upgrade utility show the error that device cannot connect.
my device is bricked now
IT is not KITL enabled
IPL 1.01
SPL 2.03
my device freezed at loading screen .
Now ,when i tried to rom upgrade in bootloader mode , using any ruu (ruuwraper,.....) it only shows 1% and my device reboots and ....
Edit/Delete Message
TVincent0621 said:
need help ,during the upgrade it was around 15% that the upgrade utility show the error that device cannot connect.
my device is bricked now
IT is not KITL enabled
IPL 1.01
SPL 2.03
my device freezed at loading screen .
Now ,when i tried to rom upgrade in bootloader mode , using any ruu (ruuwraper,.....) it only shows 1% and my device reboots and ....
Edit/Delete Message
Click to expand...
Click to collapse
Okay, when you're in the "bootloader" method, have you renamed the file that you're trying to flash "HERMIMG.NBH".
also, try to use the "stripped" AT&T ROM first, see if that'll help correct the issue.
Did you flash that first before you attempted to flash a different ROM on your Hermes? I've read in many different posts that it is highly suggested to flash that first then flash your ROM to your Hermes.
Should always flash via SD-Card, not recommending flashing via USB Wizard.
Try the "stripped" rom first, on a formatted (FAT32) microSD card, and see if that helps.
Cheers
i have download the "stripped" AT&T ROM ,it also the same ,when using USB method ,it stuck at 1% and my devide reboot .
when using SD card method ,it show (loading ...) about 2 second ,then it will back to tri-color mode there .
TVincent0621 said:
i have download the "stripped" AT&T ROM ,it also the same ,when using USB method ,it stuck at 1% and my devide reboot .
when using SD card method ,it show (loading ...) about 2 second ,then it will back to tri-color mode there .
Click to expand...
Click to collapse
I had that exact same problem.
I noticed that I hadn't named the file properly.
It's HERMIMG.NBH I kept putting in HERMING.NBH. It's kind of funny, but it's an easy mistake. When you boot with the "HERMIMG.NBH" it should flash. I used the HARDSPL V7, which can be downloaded at http://forum.xda-developers.com/showthread.php?t=296722, which is a "sticky" for this forum. Try flashing that one. Also, double check your .nbh file, make sure it's HERM IMG not HERM ING
That was the problem I was having too, it would just show "LOADING" and a bunch of numbers then drop to the bootloader... Then all of a sudden... "POOF" it worked, after I double checked the file and noticed my spelling error.
Now, if you have that fixed and still getting the error, it might be something else. I'm not sure how to exactly fix that, but as I said, mine was just a minor spelling error.. The exact spelling that I have, don't know if it is case sensitive, is "HERMIMG.nbh"
if it is case sensitive, that could also be a minor issue.
try it, if it works, then bingo, you're back in business, if not, then I'm not sure how else to fix it.
Cheers!
>.< ,now i type correct word "HERMIMG" ,it shown loading ... and (00068002) on the top of loading ... ,now it ,have better improvement ,it show loading ... for about 5 second only jump back to tri-color there ,izit this is the normal procedure ?
TVincent0621 said:
>.< ,now i type correct word "HERMIMG" ,it shown loading ... and (00068002) on the top of loading ... ,now it ,have better improvement ,it show loading ... for about 5 second only jump back to tri-color there ,izit this is the normal procedure ?
Click to expand...
Click to collapse
Okay, we're getting there. But still a long way off from it working as it should.
Okay, do you know if your phone is HARDSPL?
If you haven't already HARDSPL your phone, you should download that and try to flash that onto your phone.
Also sounds like it isn't SUPERCID. You'll have to CID unlock your phone, which is a good possibility as to why it isn't accepting other ROMS.
If your phone responds to the flash wizard when you download a ROM then get the SUPERCID and try to flash that one first, then move on to the HARDSPL.
For the SUPERCID, and my previous post has the HARDSPL.
At least the situation is improving, and your phone is starting to respond.
We'll get it working!
The HARDSPL you have to follow most of the "manual" installation instructions, and copy, then rename the "HermesUnlocker_v3a.nbh" file.
Try to flash that file, and we'll see if we can get it going.
Cheers
i think my phone not yet HARDSPL ,can you guide me to do this ?
i search the web ,it show me to here "http://forum.xda-developers.com/showthread.php?t=296722" izit correct ?
and also superCiD:
1. Unrar RUU_HERM_Unlock_v3a.exe
2. Unrar RUU_Inside.exe
3. Empty (erase the contents) of your microSD card from the Windows Mobile file explorer
or format it from your computer using a card reader (in some cases format doesn't work).
4. Rename HermesUnlocker_v3a.nbh to HERMIMG.nbh and copy it to the FAT32 formatted microSD card.
5. Insert microSD card on your phone
6. Transfer SSPL/SSPL-HERM.exe to your phone and run it
7. Confirm flashing on screen by pressing the power button.
how i wana do the step 6 ,my phone is stuck now ,i cant log in at all >< ,but i try step 1-5 ,it also shown the 00068002
TVincent0621 said:
i think my phone not yet HARDSPL ,can you guide me to do this ?
i search the web ,it show me to here "http://forum.xda-developers.com/showthread.php?t=296722" izit correct ?
and also superCiD:
1. Unrar RUU_HERM_Unlock_v3a.exe
2. Unrar RUU_Inside.exe
3. Empty (erase the contents) of your microSD card from the Windows Mobile file explorer
or format it from your computer using a card reader (in some cases format doesn't work).
4. Rename HermesUnlocker_v3a.nbh to HERMIMG.nbh and copy it to the FAT32 formatted microSD card.
5. Insert microSD card on your phone
6. Transfer SSPL/SSPL-HERM.exe to your phone and run it
7. Confirm flashing on screen by pressing the power button.
how i wana do the step 6 ,my phone is stuck now ,i cant log in at all >< ,but i try step 1-5 ,it also shown the 00068002
Click to expand...
Click to collapse
Attached is the HARDSPL file, already named "HERMIMG.nbh, which you just need to copy onto your SD-CARD.
When those are successful you will be able to flash any rom you want (provided it is as Hermes ROM)....
But as of right now, your phone is NOT bricked. It just currently has no ROM on it.
Have you tried to HARD-RESET your phone?
That's the two soft keys at the bottom of the phone, above the SEND and about the END keys.
Press and hold BOTH of those, then press the "RESET" button on the bottom of the phone. That'll hard-reset the phone.
I'm not saying to do that, just asking if you've tried that option yet.
Good luck, let me know how it's going.
Cheers!
my problem has solve now ,i try to install original rom for the phone ,it work ^^ ,thank for your help ,nice to meet you my friend from oversea .
Now i afraid to change any new rom >.<,can you guide me the best way to upgrade the rom ?so that i wont face the same problem and also brick my phone .
TVincent0621 said:
my problem has solve now ,i try to install original rom for the phone ,it work ^^ ,thank for your help ,nice to meet you my friend from oversea .
Now i afraid to change any new rom >.<,can you guide me the best way to upgrade the rom ?so that i wont face the same problem and also brick my phone .
Click to expand...
Click to collapse
Glad the problem was solved, and very happy to help!
Absolutely I can.
First thing is first, we have to SUPERCID unlock your phone, and we have to HARDSPL your phone.
Run the HARDSPL first, because the wizard will actually temporarily superCID your phone, so that you can install the HARDSPL, which will help prevent you from ever bricking your phone.
with your phone plugged in for activesync, you have to run the "autounlocker.bat" file in the SUPERCID. What this will do is make your phone accept other custom ROMS, whether it is from another carrier, or one of the ROMS that someone has developed on here.
After this, I would highly suggest, that if you ever flash your phone again with another ROM, do it the "SD-CARD" way. I'd only use the wizard to flash the HARDSPL and the SUPERCID.
Let me know how it goes.
Cheers!
Hehe ,My friend ,i had flash my phone with WM6.5 rom ,my device was Dopod838pro ,it is old device ,for my opinion WM6.5 not so suitable for my device ,but WM6.5 look amazing >.<
heh! Nice! Well sounds like your phone is now back amongst the living! That's good news! Hope you have many years of enjoyment with your phone!
Glad to have been of help for you!
Cheers
heh! Nice! Well sounds like your phone is now back amongst the living! That's good news! Hope you have many years of enjoyment with your phone!
Glad to have been of help for you!
Cheers
Do you have any must have application suggest me to install it ?
the memory for this new rom is low ,it decrease so fast ,with HTC clean ram i use ,it also the same ,it just save less then 1MB of ram ><
TVincent0621 said:
Do you have any must have application suggest me to install it ?
the memory for this new rom is low ,it decrease so fast ,with HTC clean ram i use ,it also the same ,it just save less then 1MB of ram ><
Click to expand...
Click to collapse
Unfortunately, no, I don't. You'd have to get a Vanilla, or a "lite/ultralite" rom. That's about the best I can suggest, unfortunately with the hermes, it does have a smaller ROM size, and limited RAM compared to the new, more up-to-date modern phones, like the 8925(Kaiser), or the new Tilt 2..
Cheers
TVincent0621 said:
Do you have any must have application suggest me to install it ?
the memory for this new rom is low ,it decrease so fast ,with HTC clean ram i use ,it also the same ,it just save less then 1MB of ram ><
Click to expand...
Click to collapse
Unfortunately, no, I don't. You'd have to get a Vanilla, or a "lite/ultralite" rom. That's about the best I can suggest, unfortunately with the hermes, it does have a smaller ROM size, and limited RAM compared to the new, more up-to-date modern phones, like the 8925(Kaiser), or the new Tilt 2..
Cheers
use the [Easy Hard-Spl v7 beta v0.1] by qwasde2
it,s really usefull i tryed it,s by me
it,s for win XP and vista and se7en users
i,am not joking here is the link
http://forum.xda-developers.com/showthread.php?p=5136858#post5136858
Hope you dont mind me reviving this thread as I also need your help
I tried flashing the MrDSL's WM6.5 ROM to my Hermes. Of course I followed the direction, I have Hard SPL (ever since Schaps rom) and stripped ATT flashed first.
However when I started flashing this rom, when I reached about 5% on the progress bar, I keep on getting Error. I followed the Recovery Steps and luckily I get the Tri-color mode and the process says Recovery successful. I then proceeded with the flashing but still getting errors, then recovery, then continue, then error again. Its been 10th try now.
Finally I canceled the update but I can only get the tri-color screen. Tried to Softreset as well as Hardreset but no go....my screen only gives me the Tri-color mode.
Any advice please....
thank you very much...
EDIT.....
problem solved sorry for that post.
what I did was:
1. flashed again the stripped ATT ROM....success!
2. flashed again MrDSL's WM6.5 titanium ROM (titanium)....success!
Dopod 838 Pro working again!
thanks again!!!
Bootloader shows but phone won't flash
Hey everyone,
I'm not new to
flashing my Hermes.
I'm just having an
issue I've never ran
into and can't figure
out. I would
appreciate some
assistance.
The strangest thing
is happening to me
while attempting to
flash from my
storage card. I put
the phone in
bootloader mode
and it takes
(IPL-1.04 /
SPL-2.10.olipro).
Then on the bottom
Serial shows and it
never goes to the
next step and ask
me do I want to
flash the new image.
I put the att original
on the 2gb storage
card over and over
and over and
renamed it
HERMIMG.nbh over
and over and over
and just am
flabbergasted. The
phone is not bricked,
it just refuses to
flash again.
Does anyone here
have any solutions
or suggestions?
PS - I have
formatted the card
to fat32 and I have
checked it for errors.
The HERMIMG.nbh
file is on the root of
the storage card.
I dug up my old Atom Life since the HTC HD2 is in for repairs. But when I was going to flash it to a less buggy ROM something happened, and now it's stuck in DSUU mode. I can flash any ROM from the MINI-SDCard, extended and regular rom. But it doesn't help one bit, it boots to DSUU mode.
I can connect to it in bootloader mode with USB, but I get a model ID error with every ROM I try. Even if I flash the same ROM/Ext ROM first from the Mini SD and then try to flash again from USB I get that model ID error. Weird stuff... Anybody got a god idea to how I can fix this?
Mastiff said:
I dug up my old Atom Life since the HTC HD2 is in for repairs. But when I was going to flash it to a less buggy ROM something happened, and now it's stuck in DSUU mode. I can flash any ROM from the MINI-SDCard, extended and regular rom. But it doesn't help one bit, it boots to DSUU mode.
I can connect to it in bootloader mode with USB, but I get a model ID error with every ROM I try. Even if I flash the same ROM/Ext ROM first from the Mini SD and then try to flash again from USB I get that model ID error. Weird stuff... Anybody got a god idea to how I can fix this?
Click to expand...
Click to collapse
Maybe the file was corrupted, try downloading the ROM again or another WM6.5 ROM for Atom Life. Hope this helps.
Thanks for trying to help, but like I say in the first post I can flash any ROM from the SD Card and it still boots to DSUU mode. So I have tried that.
try to disconnect everything and remove the battery. Let the remaining set for about 5 minutes.
Then reinstall the battery and try to upgrade again. This time it happened to pass through.
Sorry, but I've tried that. I even left it for a couple of days without power this weekend, and it still didn't help.
I have the same problem.
anyone help please!
Doesn't seem like there is any help. My Atom is put away in a drawer.
the only thing you should try is :
clean your record button, actually for some device, i found stuck hardware key. if they stuck at important key such as "recorder" on atom life, this will always keep you booting to boot loader mode...
diassemble your device carefully and just spray any contact cleaner while pushing your broken key repeatidily or if you have correct tools and part, replace it...
if the problem still persist, then the only suspect is your NAND FLASH on the device actually broken/corrupt/have some damage sector... and nothing you can do about it...
or maybe someone can reformat it?
In case anybody stumbles over this thread some day I finally made it work again by removing both the USB and SD card. Then I was able to use up and down and enter on the D-pad to choose "Boot OS" and strangely enough it worked! I'm not sure if that is because I had already flashed 5-6 different ROMs from the SD card, but no matter it's working now. Talk about tricky device!