Hi all,
Hoping someone could help me. My Dopod has been freezing on start-up and after doing countless hard resets i am stuck at the Windows Mobile splash screen!
I have connected it to my PC, but as Windows Mobile hasn't loaded, ActiveSync can't pick-up my Dopod. This means i cannot update or completely re-flash. Is there a way to do this without ActiveSync?
I am now stuck with a Dopod i cannot use. I have no idea what to do.
can you flash using SD card? have a search, im pretty sure that will work.
Or go through the Bricked thread
Are you sure you're doing hard resets and not soft resets? Generally when a freeze occurs, you would soft-reset.
If you have indeed been doing hard-resets, then you most likely have a hardware issue and there's not much anyone here can do to help that.
Have you updated your ROM in the past? If these freezes started after an update, then it may be a bad update, so you could either try flashing from microSD as suggested above, or boot into the bootloader as per instructions in the wiki and flash from there.
Thanks for your replies guys!
I have tried all that. My son knocked my usb cable from my Dopod whilst it was updating my ROM ... that was the cause of my Dopod current 'brick' state!
My bootloader is SPL-1.09, but i have noticed from here that the Dopod ROM that i require (for Hutchinson '3' - Australia) uses bootloader SPL-1.06. Is it true that i cannot down-grade from 1.09 to 1.06?
I ask this question as i get "Invalid Vendor ID" attempting to flash my Dopod with that ROM. When i don't get that, i get communication errors (Update Error) when attempting to run Hard-SPL-V7.
What could i be doing wrong?
Hey guys,
Think i have worked out that my CID is corrupt, therefore i can't flash any ROM even if i wanted to. I used mtty and after a bit of searching in this thread (http://forum.xda-developers.com/archive/index.php/t-291336.html) i found that the 'info 2' result i got (HTCSF kEØ(HTCE) meant my CID was corrupt.
Hopefully i haven't voided my warranty as i haven't attempted to flash any 3rd party ROMS, only the one on the Dopod website that was accidently stopped when my son tripped over the usb cable.
We shall soon find out!
Hello everyone here:
I have bought a Cinglar 8525 about 3 month ago. Because enthusiasm of flashing rom, I start to flash rom one week after the purchase.
I flashed the hard spl v7,and flashed new OS rom image.
During the flashing, nothing special happened.
After two months usage, one time a software stopped responding, I thought it might be network failure or something like that and simply reset the device,then the nightmare began.
The device boot into bootloader automaticlly without the pressing of OK and Power button.I tried to reset the device by push the reset pin but it does not work, the device always boot into bootloader, after a few step of tring, it turns out the device maybe dead and I pull off the battery to make the device totally shut off, then install the battery again, and leave the device black screen.
After some time, I reset the device again , it boot into the OS this time. After some configuration that need reset , I reset the device ,but again ,it boot into bootloader.
So my device is very unstable now, even "fragile". Boot, maybe into OS, maybe into bootloader.
Can someone explain this? Or help me solve it?
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
You're running wm6.1, aren't you? Try wm 6 as its more stable or if you wanna stick with 6.1 try PDAViets roms (19701 or 19900). They're english though....
Please note the "unstable" I mentioned is not something like halt frequently,application auto close up,etc.It's the bootloader stuff.
But I thought the problem might be irrevelant to the OS version, the "crash" occur first time when I use a ROM of wm6.0 and "crash" second time when I use a ROM of wm6.1
do some reading on wm6.1, it causes stuff like what you are describing....
After deep search in my brain, the "crash" might be occured during two version of ROM and both with wm6.1 .
Can you provide some link describing this problem of wm6.1 ? I just wondering if it is my device hardware failure or not.Or due to my some improper operation during ROM flashing process. Thank you.
Use the search function. There are a heap of threads... Some people recommend flashing a stock rom THEN flashing the wm6.1 of choice. This DOES seem to fix the problem.. Cheers...
yinx said:
some addional information:
I have flashed using card-flash method with the Manufacture Traditional Chinese Version( I came from China and the phone is origionally unlocked and I have hardspl v7 on it ).
After the flash ,the device can boot into OS this first time I reset the device, but after second reset,it still goes into the bootloader.
After a long time, I plan to flash one of the cooked ROM when I purchase the device, and ready to return the device the the seller to sort it out. But after this flash, the device just RETURN to normal ! I think it maybe back in normal and I have no execuse to return the device.So I start to use it normally.
After half a month of usage , the "bootloader mode" came again,similar steps to last time it "crash" ( device halt, reset, boot into bootloader ).
May someone diagnose this?
Click to expand...
Click to collapse
Please note this, I have done it before, I 'll do some search work.
Is there some evidence or something that the 6.1 rom of 19701 kernel has solved this problem ? I really like the thread function in SMS message in 6.1 so I want to stick in wm6.1 .
I have honestly only had problems with th 19919/19202 versions of wm 6.1. Tried 19900 with no problem and REALLY liked the speed. 19213 is SLIGHTLY faster and again no problems. Try ne of these if you MUST have wm6.1. The stability seems to get better and better as the chefs progress up the versions. Cheers...
Untill now I can't get my phone out of bootloader, I've flashed many ROMs including manufacture shipped ROM, but the phone still remain in one screen.Wondering if it can work out. Frustrated....
Start from 9:00 this morning I kept flashing my phone with different version of ROM, try to get out the bootloader,but still not working.
After a reset of frustrating "not working", I put down the phone,and do some other job,when I came back,I have transfered another ROM to the microSD and ready to flash the ROM.Before flash I thought "may I reset the phone again? may be the bootloader will go away", then I reset the phone as normal, after a while , the splash screen appear! I enter the OS, thinking the bootloader problem has go away. But when I complete some setting and reset the phone again, the phone finally fall in bootloader again.
So what ......
check for bad blocks using MTTY.... On upgrading section.
Cheers...
This I also have tried out. But I see no bad block on it, and I even do a forcibly fix to the NAND and with no avail.
I have sent the phone to a service center, it is said they might going to change a chip on the phone.
Wish my phone good luck.
Hi guys,
Recently I updated my XDA Orbit with the new WM6.1 Diamondish ROM. Everything went great until I tried to install the Oops 6.1 ROM. Before trying to install the Oops ROM I tried to unlock the CID just in case (with your Artemis_USPL tool)... Half way through the setup screen displayed an error saying "Connection error... Please check the USB connection...". Just to clarify I never managed to install the Oops file.
Then I tried to install the original XDA WM6 ROM but with no luck as I got the same error again. Then I tried to start the bootloader manually (by pressing the voice recorder button along with the Reset one) and instead of the usuall 3 colour screen I got a blank white one. Afterwards the phone froze and I had to reset it so that I can use it again.
I did a small search on your website but because I wasn't able to find another similar case I decided to start a new thread.
Currently my phone works perfectly fine with my previous Diamondish ROM, but I seems that I can't install anything else.
Could it be a corrupted bootloader? If so, how can I fix it?
Any help will be much appreciated.
Thanks in andance!!!
Take out your MicroSD card and then try and flash
You were right! Once I got my memory card off my phone, the bootloader started as usual. Cheers mate!!!
Alright, I've searched everywhere and can't seem to find a solution to this. I have a Cingular 8125 running a ROM with IPL/SPL 2.25. I then proceed to unlock it as I have down with so many in the past, and when I try to downgrade the ROM, the ROM utility update never went completely through. It told me to restore it, so I did what it said (take out battery, reconnect, etc...) and know all I ever get when I turn it on is the bootscreen with IPL/SPL 2.25.
I have tried reflashing the Button ROM many times to no avail. The only thing I can think of doing is reflashing the stock ROM with 2.25, but of course that link on the wiki is dead.
Anyone have a solution to this or at least the original ROM I need? Thanks!
Edit: Finally found an updated ROM on the internet and flashed that one, which worked. Mod Please close. Thanks
I tried to do a factory reset on my A500 and ended up getting a "Unrecoverable bootloader error (0x19000008)" error. I read various threads and ended up at this very helpful thread and tried to flash an update but didn't get anything to work after trying several and then decided to flash a new ROM and the third version I tried seemed to take but now I get a password prompt from something that looks like the screenlock screen. I tried as many generic factory passwords as I could think of but can't get past the screen. Any hints as to what to do? I may try flashing a different version of the ROM to see that helps but I thought I would ask here first. If you're curious, the ROM file I used was Acer_A500_7.006.03_COM_GEN1.