Hi there!
Ever since my first upgrade to Bepe 0.73 I'm having problems flashing new ROMs. The P3600 is properly connected and recognised by the updater. The flashing process begins and seems to finish successfully. However, upon restart of the phone I'm still presented with the old ROM in exactly the state I left it.
I have no idea what's going wrong here. By mere chance one of my many upgrade attempts to Bepe 0.75 succeeded yesterday (no idea why). I do however still experience the same problem when trying to update to v0.76.
I also tried flashing the original (German) HTC-ROM - equally unsuccessfully but with the distinction that at 13% progress the display freezes and fades to black. The flashing process does however seem to finish successfully.
I'd be very grateful if someone could point me in the right direction as to what could cause this problem and how it might be resolved.
Thanks a lot!
could you give your bootloader details? (ipl + spl)
IPL-0.50
SPL-1.30.Olipro
Here's another thing I just experienced: when entering the Bootloader manually, the display again freezes and slowly fades to black. What the heck is going on here?
solving my own problem:
the above described behaviour is due to my miniSD-card still in the slot. if removed, upgrading works flawlessly.
Related
Hello,
I believe I have a real 'tough' scenario:
My BA (WM2003) was running normally till yesterday where it simply 'froze'. I tried restarting it, (soft and hard) and it kept stalling on the (IMate) splash screen and didn't proceed to WM. I left it to battery drain completely.
I came to work this morning, and literally tried everything:
Standard Upgrade using the Imate original exe (PDA2k_WWE_14000_176_11200). doesn't recognize the phone anymore.
Tried the MaUpgradeUT_noID with the nbf files (radio, ms and nk). In all cases the upgrade starts and gets interrupted in the middle with a 'weird' error and the BA display fades as the signal led goes RED (constant, no blink). I have to take the battery out, back in.
Tried the mtty set 14 0 / task 28 sequence with no result. (The info commands return a garbled sequence which makes me assume that my bootloader got corrupted).
Any advice would be appreciated.
Thanks a lot.
W.
wzaatar
Read in another post that you got no reply on this one.
Well it seems like nobody can come up with anything that would make more sense than what you have done.
My wording is when everyting else falis go back to the original rom and start from fresh.
If you can't flash an original rom in the ship.exe or the extract form you need to send it in.
Does your device react to hard reset ?? at least you should get a boot screen.
Have you tried Bootloader mode?
I know that this is a really stupid idea.. but have you tried putting it in bootloader mode, and then trying to upgrade? Or maybe throw a WM5 rom on there, and downgrade again! Worth a try until you send it in!
Thanks for the replies guys, I really appreciate the help.
I figured out that I had two distinctive problems:
1. The constant red led light, after a lot of research, it turned out that the battery was defective. Changing it solved the problem.
2. Now, I am able to flash the ROM (Tried it a couple times so far) with the orginal or another one. It flashes correctly, but only if I use the NoID flash program, else it will return a MODEL ID error. And when I reboot it, it stays stuch on the 'Imate' or the bootscreen and I don't get the WM to load (As if it freezes)...
3. I don't think I can upgrade to WM5 as I need to shrink the EXTROM size? Can this be done through some 'task' or other command in mtty for example?
Thanks for your suggestions.
Cheers,
Wadih.
Firstly, let me say that I scoured the forums and the internet in general for information before starting a thread. Finally, I came to the conclusion that I needed to start a thread.
I bought a PDA2K from a friend who upgraded to a newer phone. It worked great, was MUCH better than my craptastic PPC4100 from Audiovox. Then it started crashing. Just freezing at random times. It got worse and worse.
Finally, someone suggested the ROM was corrupted and that a flash to the newest firmware, replacing the bad information, would solve the problem.
So, I downloaded the latest firmware (PDA2k_WWE_14000_176_11200), followed the instructions, and began the flash.
When analysing my device, there was a blank spot next to the extended ROM information, which confirmed the theory that the extended ROM was corrupted.
I initiated the flash, and it completed the first stage of the flash sucessfully. Then the problems began. The phone went blank. I left it alone, but nothing happened. So I killed the flash and pulled the battery. When I replaced the battery, the standard bootloader pulled up (Serial 2.07).
After reading for a bit, I decided that I wasn't SOL. So I docked it again, and got a 'USB Device not Recognized' error. I ran the flash anyways, but it never progressed past the 'analysing your device' screen. So, I disconnected it, hard reset it, and docked it again. This time, when I docked it, it switched to (USB 2.07), and windows recognized it as Microsoft USB Sync. I thought I was in luck.
Yea, right. Same thing, the flash program does not progress past 'analysing your device.'
So... am I SOL? What do I do?
I think I went to this problem before, I remember that I solved it by downloading the upgrade from wiki
http://wiki.xda-developers.com/index.php?pagename=BA_Upgrades
try downloading the rom from wiki and try upgrading again. if it doesn't work, upgrade without extended rom. once its done unlock extended rom by extended rom unlocker software and remove all contents in it and then run upgrade again.
There is a problem with my MDA: It continually flashes the volume/ringer control on the screen with the circle with the loudspeaker and mic turned off. This flashes every second or two and when it flashes, prevents pretty much anything else from working or command from executing.
I had a very old TMobile software version on it. I down loaded a much newer version from TMobile in an attempt to get rid of this problem before upgrading to XDA firmware: (The whole thing is very out of warranty)
The upgrade went successfully but the flashing volume / ringer control still flashes.
Does anyone know what this means or if upgrading to XDA will get rid of this problem (or exacerbate it!)
Has anyone noticed IF there is a problem with Puttenham's "Step 17"?
I got around my nerves about upgrading this G3 with a hardware problem in place and appear to be encountering a severe problem with Step 17 which is that it says it is "Your Choice" to go to a 3.08 SPL/IPL. Nowhere however does it say which later ROMs you can apply if you DO choose to go with the 3.08. I applied this to correct what I thought was the hardware issue (reinstalling the T-Mobile ROM at SPL 2.26 didn’t seem to cure it) and the 3.08 did install properly and cured the hardware problem.
I tried different ROMs because I cant seem to understand how to use VoIP or which ROM will let me use this 'feature' or which ROM has this feature built it as some say they have deliberately taken it out.
Suddenly I am getting error messages telling me that the unit needs a later ROM revision to install perfectly.
(WizardLove was the first to do this: It executes in Italian and as I mentioned, just tells me that it needs a later version to work)
So I reflashed with the Molski ROM which is the only one which seems to be around and the flash worked up until 94%. At that stage the progress bar turned to red and there was an error message telling me that I can recover and try again. I did this a few times and SEEM to have bricked my Wizard (When the Molski upgrade failed, attempts to chkdsk, reboot, delete all temp files etc failed). The unit will now only boot to the three-colour screen? Further attempts to flash seem to see and read the device and tell me either that there is no ROM on it and would I like to upgrade? Followed by this unexplained 'USE LATER ROM'. (There may be a problem with installing the T-Mobile ROM on an unlocked Wizard with a 3.08 IPL/SPL However it has to be said that Molski is, still, the only ROM which runs and it inevitably stops at the same position, the 94% mark when the MDA progress bar goes red, the unit shuts down, the upgrade process thinks about it for a while and ultimately reports ERROR [302] UPDATE ERROR)
Alternatively they (for example ROM Update Utility 2.00.1) tell me that there is no communication between the PC and the Wizard. Actually ActiveSync 4.5 does show no connection between the device and the PC, which I suppose I would expect if the Molski ROM failed to complete? Device Manager seems OK with the unit being in place though? And I cant believe this is important as there obviously IS connection between the computer and the PDA
Easymob said he would let users have a path to a ROM they could use but no where is it set out which ROMs you can use of the ones you actually CAN find?
I have also tried the Xelencin ROM which initially tells me that it cant see the PDA. Then it admits that it can and tries to unlock the CID (which surely must be already unlocked by now if I have upgraded to the later SPL??)
I am not sure I have a totally bricked unit, - The Xelencin T-Mobile ROM MUST be doing something because it does successfully run the RAPI unlock and after a few error messages telling me it can't access the MDA, reports DONE! But then it tries to run Machinagod's HTC Wizard Unlocker and gets stuck. It shouldnt get stuck at this step as I must already BE unlocked! It should pass this step.
I can hear hdd movement (not churning) but the program doesn’t progress past this step. Ultimately this carries on for hours and the Wizard shuts down I presume when the battery fails as the charge function doesn’t seem to work in ROM upgrade three colour screen mode. Plugging the charger in now doesnt seem to do anything
Again as the program was built for the 2.26 SPL, I still cant figure out whether these available ROMs should run on the 3.08 which I followed in the STEP 17.
MEANWHILE BACK AT THE RANCH: Is there a more obvious answer to why Molski always fails at precisely the same 94% position?
Hi all,
I have been visiting these forums for 2 years now and have downloaded some great tools and ROMs to enhance my Trinity, however something all of a sudden has gone very wrong!
I upgraded to WM6.1 Elegance edition about 3/4 months ago, CID unlocked the phone about a month ago and everything has been working like a dream.
However just today, I attempted to turn the volume down on my phone during a meeting (I always forget to normally!) and there was no display. After few battery resets, again no display. It starts up, loads the the Elegance splash screens and then hangs on the screen before when the OS should appear.
My decision was to flash the ROM again. I cant flash using Activesync as it wont pick up on the hung screen, so I started the bootloader and got as far as 1% of the flash and it will restart. So I tried the SD Card method when resulted in a "loading" screen appearing for a few seconds and then it goes back to the standard bootloader and displayed a 00068002 error.
I am out of ideas, I hear mtty.exe is a good program for this kind of thing, but what I want to know is if this is fixable or if I should give up!
I have been working on this since 2pm today none stop!
Can any of you guys give me any suggestions please?!?!?
Kind regards,
Jonathan
Should be a cinch
Did you SPL the Phone before flashing roms?
If you put the phone into the bootloader mode The RGB screen and kill of activesync you should be able to run one of the flash update programs.
If I have flashing problems its usually Active sync so I kill it then run the flash program.
I've got a sneaky suspision your battery might be causing the problem.
Hi there, thanks for the reply. As I was new to upgrading I havent used SPL on the phone before flashing the ROMS. I did use an unlock tool recently as i wanted to try a different network SIM to see if it worked when I was in South America, so the phone is unlocked to all networks. Are you saying if I SPL now it should sort the problem out? If so how do I do this withour ActiveSync working - can you use SD?
Another thing I failed to mention was that when I start an upgrade and it follows all the steps, it doesnt say the current ROM on the screen where you press update ROM. It just gives the name of the new ROM and the current one is left blank.
I have disabled Active Sync before attempting the update. It seems to go through fine and then the phone restarts wafter 1% of the update.
What makes you think it is the battery? I am happy to spend under 20 pound on ebay if you think it will fix the issue!
try unbrick.bat.......my trinity was also stuck.......unbrick.bat save my day....
The same happened to me several time....I could not find a solution other than this one:
1. Flash the official HTC ROM.
2. Flash the required ROM then.
it works for my TrinTy.
Hi,
I've recently upgraded to the latest radio ROM, no problems there (but it did cause a hard-reset). Now I'm trying to flash FInixNOver's latest ROM. The problem: I run ROMUpdateUtility, the device enteres bootloader mode and... nothing! No flashing, no errors, no nothing. The upgrade fails and I'm stuck in bootloader mode. The weird thing is... soft reset works and I can boot the (already installed) ROM just fine.
Any ideas...?
Thanks!
In which phase are you stuck? some bootloaders leave my trinity with the screen with the colored bands, and then refuse to continue. I launch them again (with some anxiety) and everything continues correctly. I had this probably 20 times and never a problem - but i don't understand why. It is probably a timing matter....
I'm stuck in the three-colour screen. A soft reset boots up the device properly, but it does not flash. However, I've successfully managed to flash by using the SD card method.
i always get stuck, as i was saying, in the three color screen. The windows bootloader complains it cannot continue, i simply relaunch the windows bootloader without doing anything on the trinity. Actually, i doubt it has some relation with the bepe's kitchen, since it didn't happen with NetDrg french rom....but i have exactly the same problem with the present (great) tnyynt roms...good anyway you had solved your problem somehow. it also could depend on the Hard-SPL version you are using.
Yeah, I thought the SPL could be the cause.
However, knowing that the SD card method works is reassuring.
Thanks.
my hard-spl comes from olipro:
http://forum.xda-developers.com/showthread.php?t=299659
Regards,
I had the exact same issue, i re-installed my Olipro Hard SPL v3.2 (if you are running a 3600i be sure to get the specific version).
Tried flash once again, all was fine!
Other thought, it has happened to me, when it is in the bootloader, tri-colour, just run the upgrade again. i had that with some ROMs.
I tried that many times, it didn't work.
Thanks for the reply, though.