Database Develop

pda2k went plank after upgrade need your help

Dear Friends
Good Day To You all …
I have just bought a new pda2k I=mate and I was trying to be a smart person and update its rom and I think I messed up and now I’m getting a blank screen with a word serial on it and USB when I connect the sync cable. And I didn’t make any backup can some one help out im so sad about this thing
Thank you for your help in advance
Regards
Ati

Dont Panic
The first thing is... dont get panic with this.
Just do a soft reset,
put the device in the cradle with active sync on (dont worry of any message that comes on the PC),
double click on the ROM update file
Do the process again.
It will work now!!!

PDA2K upgrade problem
Dear friend,
Thank you for your fast reply yes I checked and did all of this but nothing is happening and always I get an error i tried all that has been posted but nothing happend it checks then it stops error I think 106 maybe I have the wrong update verssion how do I get the proper one ? and looking for any more advice, i'm very unhappy the first day I get it and see what happens.
Thank you all
Warm Regards
Ati

Re: PDA2K upgrade problem
ati said:
Dear friend,
Thank you for your fast reply yes I checked and did all of this but nothing is happening and always I get an error i tried all that has been posted but nothing happend it checks then it stops error I think 106 maybe I have the wrong update verssion how do I get the proper one ? and looking for any more advice, i'm very unhappy the first day I get it and see what happens.
Thank you all
Warm Regards
Ati
Click to expand...
Click to collapse
I dunno why ppl are doing the FIRST day a rom upgrade, firstly u should go over the upgrade posts and get familiar with the updates and how to do them. Sorry to say that mate but u deserved ur punishment.

Well since you can't play with your device try reading wiki.

Help Please ! Won't go past the Splash Screen?

I've been trying to get my old extended rom and new Qtek OS on my Wizard (Vario).
But now it gets stuck in the spash screen (ie the one giving the ROM numbers).
I've tried putting the wizard into bootloader mode and I can flash RUU's but when it resets it still gets stuck on the spash screen and won't go any further !!!????
What can I do ??
Please Help
Cheers
John

I should say that I had flashed using button's ROM RUU_Wizard_1050412_WWE_101_11210_WWE.exe.html
and this worked fine!
I then copied across my T-mobile Extended ROM and again everything seemed OK.
BUT then I tried to restore my new saved OS ROM using aWizard and this caused a freeze on my Wizard. It was after a hard reset that the wizard stopped at the splash screen.
Now of course I'm limited in my options because Activesync won't work until the Wizard has fully booted up.
I have tried setting the Wizard into bootloader mode and tried several ROM's (RUU Installer ones) but every time the correct splash screen comes up with the new ROM numbers but that is as far as it gets.
I also noticed on hard reset that you get the following message
Format FAT partition
Format failed
it then goes to the splash screen as before.
Are there any other things I can try Or will I have to send it back to T-mobile for a replacement??
(It's only 2 months old and I have re-flashed it with the orginal T-mobile ROM - but still won't go past the splash screen!!)
I live in hope
John

I have this EXACT same problem!
I can reflash any ROM but it will not go past the splash screen. Only difference was I wasn't playing with my extended ROM. I flashed the AKU2 QTEK ROM yesterday and have been fine through several soft resets, etc. This last time I was uninstalling phonealarm and after a soft reset I got a "could not find smswakeup.exe" (or something similar) and it's been stuck ever since! I also get the "Format Failed" message. Can anyone help!?

I think I'm going to have to send it back to T-mobile and hope they give me a replacement. Something is wrong, it doesn't seem to make any difference what ROM I used.
I think I'll reload the T-mobile shipped ROM grom the FTP site and send it back - and claim ignorance that it it suddenlt freezed and now won't boot up! - Bummer!!!

Right I've logged a fault and it will be sent back - let's hope T-mobile can't detect it's been unlocked and had several ROM updates - I suspect they will try a ROM update themselves then give up ???
The worrying thing though is that it IS possible to kill your phone with updates - maybe it was when I used aWizard to try and restore a ROM that did it??? I'll be more carefull next time!!

this has just happened to one of the devices im flashing at the moment.... absolulty f**king raging :evil: :evil:
i wish teher was a solution!!? anyone got any ideas?
activesync wont find it, so aWizard wont work.
i can flash between 3 roms without any problems (1.5.x 1.6.x 2.x) but always hangs on the splash screen. i have flashed back to the default rom that it came installed with it so i could just send it back to o2 (only 2 days old!)
i would rather just get it sorted by myself thoough so if anyone has ANY ideas then please let me know.
thank you!

Good luck! after about 3 days of trying different types of firmware, I gave up and sent it to expansys, for repair. And it looks like they've lost the bloody thing now. :evil:

tonym001 said:
Good luck! after about 3 days of trying different types of firmware, I gave up and sent it to expansys, for repair. And it looks like they've lost the bloody thing now. :evil:
Click to expand...
Click to collapse
yup looks like i might have to give up... ohwell, no worries i will just return it back to O2...
looks like one of our sales guys wont be getting a new phone on tuesday :lol:

same problem here.
tryed to write os with awizzard after changing extended_rom.
kills phone.
format failed..
Tryed different os's from win util - failed
upgraded with sd card methode worked.
in short :
you need a working wizzard to make a os dump on sd card.
Connect to wizzard with usbterm or romupdate.exe or simular.
do a rs2all command to dump os to sd card.
stick this card in broken phone.
hold voice comm button while resetting.
On ask press voice comm button again.
it bow restores the sd backup to phone.
saved mine.....
btw sd card backup can be read ad write by pc with util ntrw.exe .
so if you don't have a working dump i can upload one.
just mail me.
grtx , arnold

hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.

FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold

arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.

There is hope
Last week after trying to downgrade to the original Cingular ROM on my 8125 using aWizard I ended up with a device that was close to being a paperweight. At least I thought so until I read and read and finally was able to get it to the bootloader and then plugged in the USB cable and ran the RUU for the new Qtek ROM (2.17). Guess what happened, yeah it worked. To my surprise I had a perfect device after 15 minutes.
For about 3 hours I thought I was a toast. Never will I do that again.

THIS is truly heaven for me !!
I have my O2 XDA MINI S locked on the splash screen .. and i updated some ROMS to it ....BUT IT DOESNT GET THROUGH IT .... please tell me what to do in a little detailed manner .. please so that i can get my phone to work.. there is no warranty on the phone and i stay IN INDIA . SO YOU'LL ARE MY ONLY HOPE .
my email id is - [email protected]
If you have a dump of the O2 XDA MINI S ..please mail it to me
Plese tell me what to do next ? WILL TRULY APPRECIATE HELP

PLEASE SOME ONE ATLEAST MAIL ME the dump of the os SO THAT I CAN TRY THE SD CARD UPGRADING ,.,,, O2 XDA MINI S

Re: There is hope
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.
Thank you so much
my mail : [email protected]
Thanks friend
hellomoto_25 said:
Last week after trying to downgrade to the original Cingular ROM on my 8125 using aWizard I ended up with a device that was close to being a paperweight. At least I thought so until I read and read and finally was able to get it to the bootloader and then plugged in the USB cable and ran the RUU for the new Qtek ROM (2.17). Guess what happened, yeah it worked. To my surprise I had a perfect device after 15 minutes.
For about 3 hours I thought I was a toast. Never will I do that again.
Click to expand...
Click to collapse

Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.
Thank you so much
my mail : [email protected]
Thanks friend
odyseus said:
I've been trying to get my old extended rom and new Qtek OS on my Wizard (Vario).
But now it gets stuck in the spash screen (ie the one giving the ROM numbers).
I've tried putting the wizard into bootloader mode and I can flash RUU's but when it resets it still gets stuck on the spash screen and won't go any further !!!????
What can I do ??
Please Help
Cheers
John
Click to expand...
Click to collapse

stuck on o2 screen helppp
Dear Friend
I have problem that my xda mini s stuck on O2 screen, could you help me step by step.I see alot of post, so complicated
Thank you so much
my mail : [email protected]
Thanks friend
flexchen said:
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
Click to expand...
Click to collapse

how to use bootloader
could you tell me how to use mentioned bootloader for restoring the images? where can I get the software?
Please help
Hendrick
flexchen said:
arnoldl said:
FarSeide said:
hard reset your device and hold your Camera Button prior to starting the wizard back on.
when the device turns back on, you will get the boot screen. Plug in your USB cable and load one of the known ROMS like the second to last iMate ROM.
This will allow you to get past the splash screen.
Click to expand...
Click to collapse
this didn't work for me.
couls flash rom. even splash screen changed to new roms one.
but still stuck at splash...
tried it with about 4 different orgigenal roms
grtx arnold
Click to expand...
Click to collapse
Don't worry, I met the same problem as you before, almost lost my hope, but finally I managed to fix it.
The solution is simple, that is to find an original SD card backup image from your wizard or others, then try to restore it in the bootloader mode. In my case, it said checksum error or sth else after begin restoring, and it gave up. Then I put my wizard into bootloader mode, picked one offical released RUU package, start reflash again. Finnally, I found the wirzrd works again for me after reboot.
I guess the principle is that the SD restore will destroy some import flash data structure before it said wrong, then the RUU package will rebuilt it wholely in the next reflash.
Hope this helpful, and sorry for my bad english.
Click to expand...
Click to collapse

Hi Arnold
My O2 cda mini s get stuck at splash scree, I read your post, still not so understand how to solve it, could you be so kind to write me step by step, and send me some software to solve it. Your help will be so much appreciated.
Hendrick
Email: [email protected]
arnoldl said:
same problem here.
tryed to write os with awizzard after changing extended_rom.
kills phone.
format failed..
Tryed different os's from win util - failed
upgraded with sd card methode worked.
in short :
you need a working wizzard to make a os dump on sd card.
Connect to wizzard with usbterm or romupdate.exe or simular.
do a rs2all command to dump os to sd card.
stick this card in broken phone.
hold voice comm button while resetting.
On ask press voice comm button again.
it bow restores the sd backup to phone.
saved mine.....
btw sd card backup can be read ad write by pc with util ntrw.exe .
so if you don't have a working dump i can upload one.
just mail me.
grtx , arnold
Click to expand...
Click to collapse

How to put Herald in boot loader mode ?

Hello,
I've searched a lot how to put the Herald in the boot loader mode.
Please, help me.
Thank you advance.
LAter edit: i found out: i had to keep pressed the camera button lol

If you searched a lil bit more you'll find that piece of info in herehttp://wiki.xda-developers.com/index.php?pagename=Herald_Resets
in the Wiki herald section

sandibad said:
Hello,
I've searched a lot how to put the Herald in the boot loader mode.
Please, help me.
Thank you advance.
LAter edit: i found out: i had to keep pressed the camera button lol
Click to expand...
Click to collapse
and in nearly everypost about unbricking and flashing.
Pleas read, read, read.
and btw: commmanager + camera + softreset.

Looking for
In fact, i read houdreds of time all the posts... at 5 AM...
Because by Herald was in the "white screen" and i was desperate...loking for solution ...
In fact, I have to wait for the official WM6 because that one didn't worked for me.
Thks for assistance.

papamopps said:
and in nearly everypost about unbricking and flashing.
Pleas read, read, read.
and btw: commmanager + camera + softreset.
Click to expand...
Click to collapse
No need to press comm.button. Just press camera and softreset at once, release the softreset first than camera button. That's all!

nugift said:
No need to press comm.button. Just press camera and softreset at once, release the softreset first than camera button. That's all!
Click to expand...
Click to collapse
OK. Thanks
BTW - my device is unbricked. BUT it was made by repairservice - for warenty. lol.
I´m happy again. Hehe

papamopps said:
OK. Thanks
BTW - my device is unbricked. BUT it was made by repairservice - for warenty. lol.
I´m happy again. Hehe
Click to expand...
Click to collapse
Damn you did not have to pay?? sweet!

Newbie here.....
I have an HTC P4350. During the upgrade, there was a disconnect with my computer to the phone, now I have that colored screen when I start up. I tried the hard and soft reset and also the Boot loader method.
Anyone have any other suggestions?
Do you think if the phone went back to HTC, they would be able to fix it?
Thanks for your help

You should be able to flash the original RUU when you're in bootloader mode ('the three colored screen') and connected to the PC with your USB cable. Worked for me anyways.
Just put your phone in bootloader mode, connect it to your computer and run the RUU.

R_phAn said:
You should be able to flash the original RUU when you're in bootloader mode ('the three colored screen') and connected to the PC with your USB cable. Worked for me anyways.
Just put your phone in bootloader mode, connect it to your computer and run the RUU.
Click to expand...
Click to collapse
The problem is that it won't connect to the computer via activeSync, until that happens the phone cannot be updated.

passmoregas23 said:
The problem is that it won't connect to the computer via activeSync, until that happens the phone cannot be updated.
Click to expand...
Click to collapse
Have you tried it before you said that it would not work? Seriously? When in bootloader mode, the computer doesn't connect via activesync (how could it, there is no operating system on the phone). Get into bootloader mode, connect the phone to the computer (yes, i know activesync doesn't show a connection at this point) and run the stock RUU for your device. If this does not work, then there is something seriously wrong with your device.
I honestly wish people would try things first before claiming that it didnt work, I know i have not posted that much, but that is because i search the forums for the questions i have, rather than wasting the time of the people who are doing all the cooking (for free might i add) and getting on their nerves.

dcmtnbkr said:
Have you tried it before you said that it would not work? Seriously? When in bootloader mode, the computer doesn't connect via activesync (how could it, there is no operating system on the phone). Get into bootloader mode, connect the phone to the computer (yes, i know activesync doesn't show a connection at this point) and run the stock RUU for your device. If this does not work, then there is something seriously wrong with your device.
I honestly wish people would try things first before claiming that it didnt work, I know i have not posted that much, but that is because i search the forums for the questions i have, rather than wasting the time of the people who are doing all the cooking (for free might i add) and getting on their nerves.
Click to expand...
Click to collapse
To add to this, when in bootloader and plugged into your PC, it will say "USB" at the bottom. That's how you know it's connected properly.
If you're having troubles and you're running Vista...
http://www.modaco.com/RUU-Vista-done-u-t252977.html

dcmtnbkr said:
I honestly wish people would try things first before claiming that it didnt work, I know i have not posted that much, but that is because i search the forums for the questions i have, rather than wasting the time of the people who are doing all the cooking (for free might i add) and getting on their nerves.
Click to expand...
Click to collapse
Dude, I have searched for a resolve to my problem, and I do appreciate peoples help. I don't waste time of good Samaritans. I did run the RRU and I received an 260 error, which is another topic which I did research on as well.
I'm going to send the phone back to HTC and let them fix it.

[Walkthrough] How to fix your bricked phone

So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Here's tmobile's ROM.

WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
ivanmmj said:
So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Click to expand...
Click to collapse

papamopps said:
WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
Click to expand...
Click to collapse
I know it has been stated a million times. I'm just tired of the same question being asked over and over again and so here we are...

Too bad it'll be stated a million more times afterwards too.

falconeyez said:
Too bad it'll be stated a million more times afterwards too.
Click to expand...
Click to collapse
If we sticky it and threatened their lives if they don't read it... lol

ivanmmj said:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
Click to expand...
Click to collapse
It will not help!

ASerg said:
It will not help!
Click to expand...
Click to collapse
And we hold their pet's hostage?

ivanmmj said:
And we hold their pet's hostage?
Click to expand...
Click to collapse
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.

falconeyez said:
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.
Click to expand...
Click to collapse
Might work out, I get 10% of the over all sold
Ghostrider

Ghostrider said:
Might work out, I get 10% of the over all sold
Ghostrider
Click to expand...
Click to collapse
Fine, but I get 15% because it's my thread.

The instructions to do this are actually in my newbie thread. Which is a sticky.

TylerC161 said:
The instructions to do this are actually in my newbie thread. Which is a sticky.
Click to expand...
Click to collapse
I know, but most people don't search. I figured, maybe if it says "How to fix your bricked phone" on the title, they might get the idea.
It was actually done mostly as a joke...

help
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang

gumbico said:
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang
Click to expand...
Click to collapse
SPL 4.70.yang!!! your device is HARD-SPL!!
So going back to stockrom--> delete the SPL.nbh from EVERY RUU you are running.
Then it shouldn´t stop......

Big Thanks papa! That did the trick. My Wing is happy once again and running Open Touch. But I still want to give TouchIt another try.

And what if i cant find stock RUU mine came with some arabic keyboard and spl was 1.08 , thanks to Oli he didnt mention that SPL should be 4 or higher , so device is bricked since first Olis release and no way to find this arabic stock RUU.
Any Help ?????
Hitec

If the device had an spl of 1.08 prior to HardSPLing it, then you'll have to bring the device to your nearest repair center. There isn't a way around that. Oli doesn't know everything and that's the risk we take when we try new and experimental things that people create but have no way of testing. But, we live and learn. If it wasn't for that issue, you could always cook your own ROM and if the HardSPL was working, you could've easily flashed any ROM. But the keyboard wouldn't been wrong until you could find someone who had the correct keyboard and you extracted the ROM from it and cooked that keyboard driver into your ROM.

Oh noooo!!
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!

foo_bar_baz said:
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!
Click to expand...
Click to collapse
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.

ivanmmj said:
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.
Click to expand...
Click to collapse
Oh deary me! I am so dead now - I live in Tanzania, East-Africa. My "local" repair center is several hundred thousand miles away across The Big Blue. What exactly do the repair center folks do to fix the device? Perhaps I can soldier out myself with some guidance...
Thank you,
foo_bar_baz.

Please help, I think I bricked my phone :(

Sorry if I shouldn't be writing a new thread about this, but I couldn't find a thread about bad flashes...
I'm a newbie with this, and I think I just bricked my phone after only my second flash I have a Touch Pro 2 (T-Mobile), and I was able to successfully install HardSPL. I even flashed the EnergyROM LEO with no problems. After a few days of playing around, I tried to flash the AthineOS v2.0 ROM, and now my phone won't boot up... it gets stuck in the Touch Pro 2 black screen with the red lettered version numbers at the bottom. I tried rebooting and pulling the battery out, but I have had no success in being able to boot it back up.
Any ideas on how I can fix this? This sucks I've only had the thing for less than a month...

localcall001 said:
Sorry if I shouldn't be writing a new thread about this, but I couldn't find a thread about bad flashes...
I'm a newbie with this, and I think I just bricked my phone after only my second flash I have a Touch Pro 2 (T-Mobile), and I was able to successfully install HardSPL. I even flashed the EnergyROM LEO with no problems. After a few days of playing around, I tried to flash the AthineOS v2.0 ROM, and now my phone won't boot up... it gets stuck in the Touch Pro 2 black screen with the red lettered version numbers at the bottom. I tried rebooting and pulling the battery out, but I have had no success in being able to boot it back up.
Any ideas on how I can fix this? This sucks I've only had the thing for less than a month...
Click to expand...
Click to collapse
hi if you have done the hardspl then try this
to enter Bootloader
Remove the back cover from the phone.
Hold the Volume Down button.
Use the stylus to press the reset hole.
Or if the device was powered off, press the power button whilst holding down the Volume Down button.
you should see serial at the bottom of the three color screen then plug in the usb cable the serial should change to USB then just flash another rom.
i hope this helps you.

Thank you! Thank you! Thank you! Thank you! That worked! That's a really cool recovery feature from HardSPL... you guys really know what you're doing This is such a huge relief...

localcall001 said:
Thank you! Thank you! Thank you! Thank you! That worked! That's a really cool recovery feature from HardSPL... you guys really know what you're doing This is such a huge relief...
Click to expand...
Click to collapse
only to pleased to help I am glad you got your phone back working

localcall001 said:
Thank you! Thank you! Thank you! Thank you! That worked! That's a really cool recovery feature from HardSPL... you guys really know what you're doing This is such a huge relief...
Click to expand...
Click to collapse
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong

b16b said:
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong
Click to expand...
Click to collapse
idd, this is not ROM related, its just unlucky like hell. See the phone as a PC, where blocks need be written. If a block fails or is corrupt, you get these jokes. Its like a BSOD on a Windows PC.

I gotta admit it is great knowing that once you've done a hardspl you are safe as houses as even if you flashed the most currupted ROM, the bootloader will always allow a reflash.
This is way more stable and safe than any other experience I've had of phone flashing.

b16b said:
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong
Click to expand...
Click to collapse
Funny that, your latest ROM was the only one I had problems with - the same problems as the original poster, in fact. I flashed a different ROM fine, re-downloaded your 2.0 and flashed it again, same problem. Hanging on the boot screen.

b16b said:
hehehe finally you found solution.. but my rom does not have any problem.. somethings goes wrong
Click to expand...
Click to collapse
Probably I think I was just unlucky. My fear (while I was panicking) was that your ROM is European based, and since mine came from T-Mobile, it didn't mesh well. I also didn't unlock my phone so that could be also be a problem...

awesome community

localcall001 said:
That's a really cool recovery feature from HardSPL...
Click to expand...
Click to collapse
well..this is a normal recovery feature for stock spl also

Same Issue
I had the same issue with AthineOS v2.0 ROM it gets stuck on Touch Pro 2 logo

wahida76 said:
I had the same issue with AthineOS v2.0 ROM it gets stuck on Touch Pro 2 logo
Click to expand...
Click to collapse
no one have told me that on my thread... only here i found this issue.. and finally how pass the problem?

I had to re-flash a different ROM.
I'm wondering if it's related to the radio version...

what is your version of radio
can't you flash the latest 23060?
i use radio 3.36

I've used 4.49.25.05 and have just got the same result on 4.49.25.17
I'll try flashing 3.44.25.27 (the oldest in the radio thread) and re-flashing your ROM.

Alas, no luck with that one either.
I have no idea why it doesn't seem to work on my Rhodium :/

I'm sorry if I'm hijacking this thread but it's the only one I've found that's even close to having the same issue I have, though I'm still using the stock rom/os.
I was installing winmo msn messenger. It installed fine and reset my tp2 fine. It goes thru the tp2 splash screen, the verizon splash screen and the winmo splash screen. Then it shows owner information and this is where it gets screwed up. Owner info will stay up forever if I dont touch the screen. After touching the screen the only thing left will be the top bar and the rest of the screen stays black. The only things on the top bar are the signal icon (which always has an x), the wifi icon (which seems to be connected fine lol) and either owner info will still be in the upper left or the start menu will be there. Hitting the screen only causes my tp2 to beep.
Nothing I know how to do (which is basically just hard and soft resetting it) works. Verizon can't fix it (didnt think they would be able to) and I can find no drivers (possibly cause I'm still a noob with winmo) to resolve my issue. I'm not even sure how I'd get them on as it wont even sync up to my computer and my computer cannot find its hd. If I could get a rom for the verizon one I think I can figure it out from there with no issues...but htc website sends me to verizon website for support and vice versa. The htc wiki is the closest I've gotten to an answer...but no rom to download. The only OEM roms I can find anywhere aren't for this phone, unless one of those will work? You guys are the experts.
Does anyone know what I can try? Verizon wants me to return it but cannot tell me when I'll get my new one as they are out of stock...again. Please help lol! Thanks for any and all help.

Mr.Clark said:
I've used 4.49.25.05 and have just got the same result on 4.49.25.17
I'll try flashing 3.44.25.27 (the oldest in the radio thread) and re-flashing your ROM.
Click to expand...
Click to collapse
i using this..
*Change the radio to 3.46.25.30 (Hot Fix For GPS Lock)
and also try the latest release of my rom.. (maybe you have bad file bad download)

b16b said:
i using this..
*Change the radio to 3.46.25.30 (Hot Fix For GPS Lock)
and also try the latest release of my rom.. (maybe you have bad file bad download)
Click to expand...
Click to collapse
Sorry, I tried that one as well yesterday. And I've downloaded your ROM a few times too...
Are you still working on the 6.1 ROM? Maybe a new version will just magically start working for me...
EDIT: Tried a fresh 3.46.25.30 and a fresh download of your ROM. Still nothing