Please help, I think I bricked my PPC! :((( - MDA II, XDA II, 2060 Windows Mobile 6 Upgrading

I tried flashing WM6 on my QTEK 2020, but I had the wrong version. I begun the upgrade having it on bootloader and after a while an error about updating radio occured. Now, my PPC powers up, but it gets stuck on the beginning with the "QTEK" logo with the clouds and the blue led that indicates the bluetooth is activated. Neither soft nor hard reset does anything and I can't flash the original rom through bootloader (I can boot the PPC in bootloader).
Does anyone have any idea please?

If you posted this in the Qtek2020 (Himalaya) forum, you might get a quicker response.

Thread moved out of the BA section

Maybe you should try reflashing. Just flashing a new ROM and then just a radio might do the trick.
How did you flash? With the No_ID?
And what were you trying to flash? A BA ROM while you have a HIMA?

OK!
It's ok now! I flashed the WM6 Rom having my PPC on bootloader and everything's fine!

Its very good to hear that..btw which rom did u flash before and what have u flashed now

I really can't remember what the previous rom was, but it was for another brand! It was stupid to flash that one! The one I have now is this:
http://forum.xda-developers.com/showthread.php?t=332945
But I have a problem. The PPC restarts randomly even if I do nothing with it. I haven't overclocked it.

It is not got sign, if your PPC restarts randomly. Better you flash it again.

I flashed again the ROM from "Himalaya Mobile 6" category and the following link:
http://forum.xda-developers.com/showthread.php?t=332945
but my PPC keep restarting and one more thing, WM6 kills my battery! I've got to charge it every day, before I charged it every 3-4 days. Does anyone have any idea what I should do? Can I put WM2003 now?

Hmmm... I'm using the 7c ROM from that page with no problems at all.
Did have some issues with some older apps and the config for TomTom when I switched to WM6, but not anymore.
What do you have installed, and what versions?

I have installed nothing but WM6!

Related

Not a happy bunny...

Well, it seems that my BA finally broke (WM5 anyway). It happened when i was flashing back from a test rom to ivans latest version, i flashed, booted up and got to the wight screen, and stayed there... for 30 minutes. undettered i then tried every WM5 rom i could lay my hands on, but to no avail. in final desperation i downgraded to wm2003se and lo and behold it worked!
Anyone got any idea how to get wm5 working again on my ba?
just reflash back to WM5
thi is a rare bug, which occures, and the fix is downgrade to 2003 and then upgrade to WM5
done that, twice
have u tried to format your extended rom ?
there is topic out there, but show how to do it.
u could give that a try.
reflash everything including radio and ext rom, use radio 1.13, after flashing WM2003 try to flash WM5, please post the result. If this does not work i think it is a bootloader issue, if you can get the same version of boot loader and flash it maybe all will work.I am too scared to mess with bootloader yet.
http://forum.xda-developers.com/viewtopic.php?t=46867
Does anyone have command reference for BA bootloader trough mtty
[curse]
**** **** **** **** **** **** ****
[/curse]
right, i ran the mtty thingy, and reformatted the flash, i then went back to 2003se and storage and extrom were working , but then when i tried to go back to wm5 i kept getting a model id error even though i used xda3nbftool.exe to set the same one as in deveicedata.txt but to no avail, when i gave up to go back to wm2003se i found i couldnt exit bootloader! so i tried connecting again via mtty, it all went fine, ran the commands again etc but still stuck in bootloader. out of desperation i took out the battery, but now to my horror the phone wont even turn back one (yes, i've put the battery back in ). has anyone got a clue how to fix this?
Many thanks in advance....
edit - I just tried a bit of percussive maintanace on it and lo and behold... it began to boot
The only problem now is that the boot screen is f*cked up and i get a model id error whenever i try to upgrade roms (even the official orange shipped extract with no modifications wont run )
http://forum.xda-developers.com/viewtopic.php?t=49611&highlight=model+id+error
@Midget_1990
edit - I just tried a bit of percussive maintanace on it and lo and behold... it began to boot
Click to expand...
Click to collapse
"Percussive Maintenance" rarely fails. Nice term though - I'm sure I'll quote it.
Do post a link to the mtty command reference when you get it.
Cheers
- it just sounds better the 'i threw it at a wall'

Charmer crashed with the new Aku 3.3!

Hello!
I tried to flash my Charmer with the new german Aku 3.3. At first everything seems to be ok, but at 95% it stops and i got the Message: update error- there is an comunication problem! So what can i do? I tried to flash the old rom back but there comes also at 95% a message: invalid command - nfb file cannot be used for your pda!
Please help me !
Greetings Musna!
Ps: can somebody upload a sd image for the mda compact II !
Go to bootloader mode, then try to flash RUU rom (1.x). You can find it on Charmer wiki.
It doesn`t work too, it always stops at 95% has anyone another idea?
did you try hard reset?
Yes i tried hard reset, but it is always in bootloader!
I have also the same problem. Tried to upgrade to version 3.3. Everytime it stops at 80%. I don't know why?! I can repair it with the software and re-run it. But it has the same effect.
Now i will try to downgrade to 2.6 again. I really don't understand what causes the problem. I hope i will get this thing running again....
EDIT: I reflashed the device with the older 2.6 ROM and it is working right now. However I didn't really get why it gets stuck at 80% with 3.3 ?!?!
nitrane said:
I have also the same problem. Tried to upgrade to version 3.3. Everytime it stops at 80%. I don't know why?! I can repair it with the software and re-run it. But it has the same effect.
Now i will try to downgrade to 2.6 again. I really don't understand what causes the problem. I hope i will get this thing running again....
EDIT: I reflashed the device with the older 2.6 ROM and it is working right now. However I didn't really get why it gets stuck at 80% with 3.3 ?!?!
Click to expand...
Click to collapse
The aku3.3 is up to date the bootloader version!!!
IPL and ISP version now is 3.00.
http://www.windowsceportal.hu/forum/viewtopic.php?t=1079
Sorry but i do not speak hungarian. What do you want to tell me ?
I´ve got the same: My charmer is in Bootloader IPL 2.06.0001 SPL 3.08.0001
I can´t downgrade to AKU 2: Please order a newer Version.
Every try to upgrade to AKU 3.3 failed at 95% with Error 326.
Is there any help for my charmer???
oh.**** !!!! I got the same problem with them and my first pda uk rom already empty screen and then i try with my scrond pda German rom it the same problem and now just only show in bootloader screen.Have i ask someone who knowage about this he told me that if SLP in you PDA have chang it be hard to repair.So,I think I lose 2 PDA did I try to flash in T-Mobile Official Rom de that i hope to develop it but i hve to kill 2 Charmer.Who take responsibilities,T-Mobile right ???
Ok no problem you can repair it! At first you have to brand your device with the rom you want to! After 95% the Problem will come again! When it stops you have to go with a reset to bootloader again.When your device is in bootloader you have to install the Radio Rom from this thread:
http://forum.xda-developers.com/showthread.php?t=302768
After that your device will be able to boot again and it should work!- But the Problem during the installation will stay,so you have always to use this way to flash your Mda compact II!
In the new rom there must be a problem with the radio rom and this causes the broken device.
I`m sorry for my bad english but i`m not used to talk very much! So i hope you understand what i mean!
Greetings from Austria Musna!
that link is broken
Then try this one:
ftp://xda:[email protected]/Prophet/Radio_Roms/Prophet_G4_RadioRom_v2.47.11.exe
You can find the radio rom also on the ftp server. Prophet> Radio Roms>Prophet_G4_RadioRom_v2.47.11.exe
You can try different Radio Rom versions, i have flashed the v.247.11 and it worked.
Normaly it should work!
Thank u so much !!! My Charmer secrond PDA come back have life again and it can working.So,my Charmer first PDA UK rom still empty screen and notthing working when i press any button.Who can slove this problem !!
Musna do you have any massage such as msn

Trinity running 6.1 Elegance- totally bricked - please help me!!

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.

Restore from Bootloader?

I tried to upgrade my 8125 using Shelltool earlier this week. I used the tool successfully before and so I was assuming that things would just go well.
Unfortunately, I ended up being stuck on the bootscreen. I can also still go into Bootloader mode and so I figured all I need to do is to download the Wizard Love ROM, go into Bootloader mode and apply the ROM to restore an older version. Well, for some reason the RUU utility keeps telling me about a communication issue even though I already disabled USB in Active Sync and I also killed the program using Task Manager...
What am I missing here? I am hoping that someone can enlighten me...
Thanks,
Jens
For some reason I was finally able to flash my 8125 with the Wizard Love ROM this morning. Flash completed and I was back to an old working ROM.
Unfortunately, when I flashed it with the latest CR86 it flashed fine, but then I am stuck on the Bootloader screen. Already tried it twice and just running it a third time, but I am puzzled...
Any help?
Thanks,
Jens
jstraten said:
For some reason I was finally able to flash my 8125 with the Wizard Love ROM this morning. Flash completed and I was back to an old working ROM.
Unfortunately, when I flashed it with the latest CR86 it flashed fine, but then I am stuck on the Bootloader screen. Already tried it twice and just running it a third time, but I am puzzled...
Any help?
Thanks,
Jens
Click to expand...
Click to collapse
its on its last flashes my friend(or maybe just tire of custom roms)
but just before mine died, it would do that, until i was stuck on the bootloader and the screen would just die, i would have to leave it off then turn on but the same, after that i just left it alone
i could not flash anything on it and i could not see it suffer anymore
i still have it but dont have time to bring it back to life, at least it blinks at me
That's what I was worried about...
Strange thing is I probably only flashed it about 10 times... Very frustrating!
Thanks for your reply!
Hmmm, I just tried the old Wizard Love ROM again and it worked right away.
What am I missing here? I am trying to get to the new CR85 6.5 ROM, but I always end up being stuck on the bootscreen loader. I mean it shows me the HTC screen, but then it goes straight to the bootscreen...
Any suggestions?
I am back in business!
It turned out that flashing back to an older ROM disabled my HardSPL. I guess a case of user error on my end...
Anyhow, I also experienced the fading display mentioned above and I think that's just a sign of a weakening battery. It seems that the phone doesn't charge fast enough over USB in Bootloader mode.
So, if you run into the same problems like me:
- Charge your phone using the charger when you are stuck in Bootloader mode for extended amount of times!!!
- Flash an old provider ROM or Wizard Love ROM
- Re-apply HardSPL if needed
- Upgrade to a newer ROM
Cheers,
Jens

big problem after flashing htc fuze with

i Download the HTC Fuze ROM Update- Version 5.11.502.2 WWE
after i flashed it and booted it, initial setup was taking place... it said it was setting up touchFLO. everything looked good.
until...
it just rebooted!
and it keeps cycling that way. it never gets to load windows.
i have read that other people have been having trouble with touchflo after the update... but now i cant even get windows to load.
ive been trying to find solution all day. about 15 hours. i cant even flash another rom into it. i cannot hard spl. anyone?
Did you install Hard Spl 1.40 before you flash the device ??

Categories

Resources