Related
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!
hey guys,
ok running out of ideas, nothing is working.
upgraded to radio 1.43 yesterday which went fine. little while later saw phoen had frozen. rebooting showed me the no gsm error...
so i got going, followed all the instructions on the bricking threads without any luck.
its stuck in bootloader. i can flash an OS-only upgrade (been using windows black) which works fine, even LOADS windows when i reboot, but freezes (and gives the no gsm error on boot.)
however ANY other OS i try using, or even trying to upgrade hardspl or the radio gives a communications failure. so for e.g. if i get a radio upgrade, run it when the windows mobile is all up and runing, it'll go through the reboot process but then have a communication error once the status bar of the upgrade shows up (if at all). then when i reboot it only loads the bootloader, and even trying to change this using mtty has no effect - still only bootloader. trying anything from bootloader alone yields nothing.
IPL 1.01
spl 1.40 olipro
would appreciate any help you guys can offer. and yes, i've gone through the wiki and explored all the bricking threads and have not found a solution...
quick update on this: most likely more serious than i thought.
i downloaded the full htc rom upgrade including radio extrom etc etc:
HTC English QTEK_001 2.11.255.1 03/07/07 2.11.255.102 1.38.00.10 32.71.7020.12H 15673.3.3.1 3.3.1 1.11 108 Thread 1,2,3
as found in the wiki. it started upgrading, got to 13% at which point i'm guessing it starts the radio upgrade. at 13% it freezes and there's a communication failure on my pc.
usb cable is secure and intact, i know thats not the issue.
have i busted my rom or what??
Looks like the exact same issues as a number of people here:
http://forum.xda-developers.com/showthread.php?t=309079
Looks like there are enough cases of this from capable users for it to be looked into further? its not like we're all newbies and just mucking about... i've been flashing this device since i got it!
Hey,
Right, so in my great wisdom I managed to drop my TyTN on its face on the kitchen floor one day and since then it just doesn't do GSM.
On boot, it says "No GSM" below the boot logo, and anything to do with GSM (opening the phone app) causes the device to run slow for a little while then return back to normal without launching the phone app or throwing any error message. Its stuck in permanent "flight mode" as it were.
Sending the phone back to the provider, they turned around and said "On inspection it was found that 3rd party software was loaded on the unit and damaged the unit. Unit is returned without repairs done to it."
I was using one of the ROMS from the forums here which worked fine for a few weeks up till the drop. (I do know which one but I'd prefer not to give anyone a bad name where its not called for, so prefer not to mention it directly).
I will say that it was a fairly new release in june.
Also currently have on boot.
IPL-1.04
SPL-1.40.Olipro
Have since tried re-installing version roms which have made no difference at all.
So:
1: is it possible that the updated OS and flashing the radio etc could have cause the problem described?
2: How do I return the phone to its original radio version and a generic (officially supported) WM5?
3: Is there anything I can do from my side to fix the problem?
Many thanks
-RobH
Have you tried flashing the original ROM that it came with... Then you can probably take it back to another warranty shop or to HTC for repair... You can also upgrade to Olipro 2.10, you can search for the files, I'm just to lazy to look for it now... If you can't find let me know, and I'll look for it...
Once you upgrade to Oli 2.10, it may make a difference.. Have you tried flashing the radio...? It could very well be a hardware problem that occurred during that sudden stop on the floor...
I'm not to helpful, sorry...
Rob,
Obviously the fall messed up your TyTN, and HTC now refuses to work on it (read save money) because you are running a non-standard firmware. Well, screw that!
Have a look here to start the downgrading process.
Then, go to Leaf's site and download the AKU3 firmware from the Members section.
Flash it to your TyTN.
Then take it back to a different repair centre (not too sure about your options in Grahamstown) and tell them you dropped it, and now it is not working anymore.
Right so trying to get the original (well an club-imate approved) rom installed so that I can try the repair center again...
Based on this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
Image is HERMIMG_CDL_1.31.305.2_SHIP.nbh
(Extracted frin JASJAM_wwe_1.31.305.2_1.31.305.104_1.21.31.10_ship.exe)
I get the following:
<Gray screen with blue txt>
HERMIMG.nbh -
IPL - OK
BOOTLOADER - OK
SPLASH1 - OK
SPLASH2 - OK
EXTROM - OK
GSM -
OS -
Update in Progress...
</End screen>
And thats where it sits.
Even when trying the recommended usb/HardSPL methods, its gets to about 14% and hangs. I presume due to the GSM module being damaged.
I've also tried .nbh's that only have the GSM stuff, and using the microSD method, it gets about 5% along the progress bar and then halts.
EDIT: I've managed to flash it with an original rom excluding the GSM stuff. Will see what happens at the repair center...
-Rob
Excellent, hope you get it sorted!
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.
I just recently acquired a HTC Touch Dual and really like it but am having a few issues with it. First, I get tskschedule, repllog, and clocknot notification errors. I've noticed a few threads regarding this issue but haven't yet found a solution so any suggestions would be most appreciated. The second problem is that my battery indicator doesn't seem to be working properly, it stays at 90% and doesn't change regardless of how long I use it for. This caused the phone to die on me in the middle of a conversation. So if anyone has an idea on how to fix either of these two issues, that'd be great.
Hard-Reset or flash another ROM (for example Original HTC Shipped 6.1 or one of the custom ROMs which where offered here in your language).
I bought the device used and unlocked off of eBay, will hard-resetting it keep it unlocked? Also, I'm very much a noob to phones and don't have any clue about flashing roms, what are they exactly and how do I do it? Thanks for the quick reply.
Hard-reset = Original state of the installed ROM
For flashing there are lots of tutorials here (I don't know which is your native language, so I can't post links to some ROMs - I have nearly tested all of them ;-)). Best you try flashing first original HTC ROM. Very easy (you said it's already unlocked), just connect the phone to pc via USB and start the flashingtool. After flashing hard-reset to be sure that all settings and files were restored to original state. That's all.
Don't forget to backup contacts, emails and so on before hard-resetting/flashing! Files on storage-card will be ignored, you don't need to backup them!
im from the us, so my native language is english. do you have any suggestions or links for the better flashing tools? after flashing to my original rom, my phone will stay unlocked right? because it doesn't it'll create more problems for me then i am having right now. thanks again
My native lang is German, so don't worry about my English ;-)
Unlocking is easy, just use hardspl and uspl. I have unlocked my phone only once a time and never had problems after or while flashing (done 15 times or more!). Once I killed my phone with a bad Rom (endless boot-sequence), but you can go into bootloader by pressing "Power-Button + Camera-Button + Reset", so you're always able to flash another Rom and/or could unlock the phone again. Nevertheless I can give no guarantee.
First you could try to download from HTC website. You need the serial-no. which can be found after removing the battery. If you have a look at niki upgrading/flashing forum you'll find also links to the original ROMs.
You can also try the latest WWE/english ROMs offered in this forum at the first 1-2 pages. I tried Gullum's TF3D and Lilly's ROM, both are great and have Manilla included (if you don't like it, the old HTC Home plugin is included in HTC Rom), but I prefer german ROMs. The Niki Project Rom didn't work for me (bugs in Outlook and Office Mobile).
All Roms include the flashing tool, it's really easy to use.
thanks buddy, i'll give it a shot and let you know how it goes
do i have to use a sspl before a hardspl? i have a neon and havent yet found a sspl for it yet. how dangerous is it to use a hardspl? im very new at this so thats why i have so many questions. thanks again
For me everything worked without problems. So I can't say how "dangerous" it is. Most users don't have any problems. To be sure get latest ROM from HTC or your provider, so if any problems occur, you're able to flash the original ROM back via bootloader.
As far as I know you only need to hardspl, but I did sspl first and then hardspl.
I think we need to clear up a couple of things and kind of slow down before you brick your phone
Generally, there are 3 types of locking for these phones.
First, there is SIM locking that everyone is familiar with and locks your phone for use on only one network.
Secondly, we have CID locking - which locks the software\firmware on your phone to that supplied by a particular carrier (for example, if your phone is CID locked to AT&T, you can only flash a ROM from AT&T and not HTC or a custom ROM).
Lastly, and least to be concerned about, is Application locking. I've not heard of any of the touch duals being app locked so we can safely ignore this.
I'm guessing that you meant your phone is sim unlocked in which case, I'm 99.9% sure that none of the ROMs that you can flash will change that.
If yours still has the carrier ROM on it, it is most likely still CID locked so you need to get that off first.
Once that's done, you need to HARD SPL installed (the SPL is the bootloader bit, SSPL is just a "software" version of it that can run but doesn't install anything) If you put HARD SPL on, then it is almost impossible to brick and ruin your phone - but until that is on, don't try flashing custom ROMs or radios etc. as you're asking for trouble.
Also, until you have HARD SPL on, be careful about flashing anything - make sure you don't run apps while it's going and shutdown anything that could interfere. Take basic precautions and you should be fine.
But TBH, if you're new to these phones anyway, and the ROM is right for your carrier, I'd leave it as standard - I personally always find something wrong with the cooked ROMs - missing T9 dictionaries \ SMS not working \ MMS not working \ some other detail that was missed, and I always end up going back to either my stock ROM (T-Mob UK WM6) or the HTC Update (WM6.1) but I don't notice the difference if I'm honest.
People say that whatever ROM they have on is the fastest they've ever tried but in my experience (and I'm on my fifth or sixth generation of WM phone) the difference is marginal at best and certainly not worth the trade off of broken features and multiple reboots.
So, my advice is, by all means, have a mess with other ROMs but be careful, get HARD SPL and make sure you have a ROM to go back to.
Oh, and try a hard reset (or Clear Storage from control panel) after syncing everything up to try and fix your current problems
Cheers,
Smiffy.
i was thinking about trying a hard reset prior to flashing a rom. i cant download a rom from htc and am unable to find one from att (my carrier) so as of now, i dont have a rom to fall back on. i bought the phone used and unlocked, so will a hard reset keep it that way (basically, what will a hard reset do exactly)? i am referring to a sim-unlocked state. the centennial wireless splash screen still shows up so im guessing it is still cid locked? do i need to unlock the cid before hard-resetting it? thanks for the help
The hard reset basically wipes and user-related info and returns it to a factory-fresh state - if one ever starts playing up, this is what should be done before you flash a new ROM, and yes, it will still be SIM-unlocked afterwards. It will alos go through the setup routine again as if you just took it out of the box
There are other places to get the HTC rom from - it's actually quite a good one too as it will set up all the data\MMS settings for your carrier too.
If you're not worried about any warranty, then it's good as a fallback though search on here and see what results other people have with AT&T.
CID unlocking is fairly easy if I remember - been a while since I did it and I have a different model than you. Just make sure anything you use is listed as OK for a neon
HTH,
Smiffy.
so i did a hard reset, and there hasn't been a change in the battery issues. so maybe the battery is faulty? would flashing a different rom help or should i just get a new one? thanks again
If the ROM is at fault, then flashing a better ROM would help, yes. If the battery the faulty, then even a ROM that is much more energy efficient would help little, only delaying the inevitable.
how would i know if the the problem is from the rom or the battery? other than trying a new battery that is
aight, so i got the hardspl for the neon. will that cid unlock my phone cause i cant find a cid unlocker for the neon 300. what would happen if i didn't cid unlock my phone before flashing a new rom?
Nothing would happen. Either it refuses to flash on beforehand, or it'd stop at about 1% from the start not touching your existing rom.
Hardspl is indeed the way to cid unlock your phone, as far as I know.
Please Help!
new problem here, my new battery just arrived a couple of days ago. i inserted it in my phone then let it charge before turning it on. my previous problem was that with old battery, the amber light would start blinking but not remain steady and tell me that my battery was very low then eventually turn off. the new battery's amber light was solid and i left it plugged in for 10ish hours because the light never turned green. i finally turned it on, but eventually the same problem arose. i hard-spled it then flashed a new rom which helped for a little while. the light stayed steady and the battery status rose up until 100%, but the light stayed amber. then if there was any shift in pressure on the chord, the light would start blinking and the battery would immediately read 5%. now the new battery isn't any different from the old one. does anyone have a suggestion? it would be greatly appreciated.
Anybody? Help? At the very least would anyone have suggestions of good repair sites? Thanks in advance