Dear Folks at XDA,
I would like to ask for you help with my HTC Touch Pro 2. I recently tried to update it to the new AthineOS CHome TF3D WM6.5 Manila ROM v 1.0 and unfortunately I failed.
The problem is that my phone now freezes at the black startup screen with the Touch Pro 2 logo and the red codes at the bottom.
I've flashed the ROM several times before and never got this issue.
Due to the fact that the phone doesn't finish the boot-up and I thus I can't get ActiveSync I'm afraid I messed up my phone for ever.
Please someone tell me I got a way out of this, I'd appreciate it very much.
Greetz,
SjonSjon
umm.... I don't think you can change the firmware just yet on the CDMA version of the phone... if you used a HardSPL that's available in the Rhodium forums then you probably used a GSM specific ROM on your CDMA phone... not sure what to tell you other than making sure you read the CDMA forum before trying something so risky. Best solution, unless someone knows how fix your phone in it's current state, is to toss it under your car and run it over and try to cash in on the insurance.
Problem solved!
Hey guys,
I got my HTC Touch Pro 2 functioning again. Thought I'd post the solution for other people who might encounter the same issue. I don't exactly know what the problem was. I'm assuming a non-compatible ROM or something, but after opening 30 tabs in my browser and reading my eyes out I found that if you put your phone into bootloader mode and connect it through usb to your computer you can flash the ROM without using activesync.
So I turned my phone off, pressed the power and Volume Down button simultaneously and then used the Stock ROM upgrade software from HTC to restore my phone
This solution beats the hell outta "run it over and try to cash in on the insurance" if I say so myself!
Greetz,
SjonSjon
I am glad you have recovered the beautiful device; and thanks for sharing a working solution.
sjonsjon said:
Hey guys,
I got my HTC Touch Pro 2 functioning again. Thought I'd post the solution for other people who might encounter the same issue. I don't exactly know what the problem was. I'm assuming a non-compatible ROM or something, but after opening 30 tabs in my browser and reading my eyes out I found that if you put your phone into bootloader mode and connect it through usb to your computer you can flash the ROM without using activesync.
So I turned my phone off, pressed the power and Volume Down button simultaneously and then used the Stock ROM upgrade software from HTC to restore my phone
This solution beats the hell outta "run it over and try to cash in on the insurance" if I say so myself!
Greetz,
SjonSjon
Click to expand...
Click to collapse
Good job!
big thanks for solution.
You just saved my life!!!
Don't get our hopes up! This is the wrong forum. CDMA TP2s can't be flashed at all yet.
This was a life saver post so a quick bump for anyone that needs it.
I unlocked my CDMA phone, installed a few roms -- decided to go back to my stock rom default (which was Telus) -- reinstalled and bam -- bricked.
Well, technically it's not a brick if you can get back into the bootloader to reflash. So no worries everyone. If everyone reads instructions well enough we should hopefully see zero "real" bricks. Or at most, just enough to only build bbq pit rather than a house.
I think my phone is truly bricked
I was unlocking my phone (the HTC Touch Pro 2 <Verizon>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. Let me know if you need any more information.
my cdma is rebooting endlessley i reflashed stock rom and evorything. it seriously dosnt want to work. its most sadness... i am cashing in on the insurence. but they are going to send me a refurb..
spend 600$ on a phone got inurnce i hope the used one dosnt fail me.
Esazi said:
I was unlocking my phone (the HTC Touch Pro 2 <Verizon>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. Let me know if you need any more information.
Click to expand...
Click to collapse
I did the same exact thing to mt TP2. Same outcome.
We have to learn somehow....
That stinks man. If you did, then your phone is truly bricked. You are going to have to get a replacement or switch to another phone because there is nothing you can do to get it going again. I tried everything possible and eventually just ordered a replacement. I have it now and it's working beautifully, but needless to say I am a little scared away from any more unlocking or flashing for a while.
If you read carefully you dont have to be scared of flashing
I was a noob some time ago but before doing anything I took care of reading and understanding before doing nothing.
lesson learned
By now I have flashed more than 60 times on 3 diferent HTC devices and all were a succes
Hope you get your TP2 working again!
I hope I can get there
Someday I hope to be a flashing expert, but until then I will take it slow and read carefully. Thanks for your encouragement. When I actually get money to pay for the unlock for my TP2, I will let you know how flashing goes.
How do you keep the phone in bootloader? Mine goes right to the press volume instuction screen. Other than that I'm stuck on the black name screen,also my usb will not register in device manager. This was my first try at flashing.
gadgetgirl28 said:
You just saved my life!!!
Click to expand...
Click to collapse
Holy hell, you're not lying. Thanks for coming back to post your solution!
This post saved me at least a few hours of frustration and ever worsening decision making.
So it's totally true???
this situation hasn't solution;
I was unlocking my phone (the HTC Touch Pro 2 <SPRINT>) and I was using a Diamond unlocker (I thought it would be fine), but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, AND PLEASE somebody tell me , that it can be save it
;9
please help
i have the same problem. is there a way to save my phone?
So today i just got my new android back from att after the charger port broke and i thought i would hack it with Gingerbread. well as soon as i installed it i ended up my screen all messed up and blured in funny colors. Well i was able to get the phone into recovery mode to the download screen. I tried installing what was supposed to be fryo 2.2 threw odin and the damn thing froze up and now my phone has the soft brick screan so i tried the one click unbrick but i cant run the program as administrative at my girls house because i dont have the admin password even thought there isnt one. i have been up sense 1am trying to trouble shoot this thing i cant seem to fix it and i have work in 3 hours. can some one please help me with a solution on what i can do. att wont cover another phone.
sorry for the bad grammer
i don't i'll be able to help in this, but for others to help, you need to mention your phone details
Last week I rooted my primary phone, a Samsung Admire with Gingerbread 2.3.4. This was done only after successfully rooting my older LG Optimus T running Fryo. I had no trouble with either phone during the process. However, as of 2 days ago the Admire has had some troubles, namely that the phone function crashes when I press the send key. I get the error message stating “Sorry! The process com.android.phone has stopped unexpectedly. Please try again.” It will receive incoming calls but they cannot be answered and when I try, it crashes
I’ve spent much of the time since researching the problem to find the cause and it’s fix. In doing d\so I have read of multiple causes from screen resolution changes to attempted over clocking, which I have played with. I’ve read that there might be problems with the phones attempting to switch from 2g to 3g too rapidly, something this phone cannot do I believe.
I came to the conclusion, probably erroneously, that I needed to reset it back to factory and then reinstall apps and data out of the backup I made using Titanium Backup prior to the phones troubles. So I did so, doing the three button cocktail I’ve read about here on XDA Forums. After doing this, the problem persists. I’ve read some more becoming more baffled as I went along. So I tried to reroot the phone using one click root, and that was unsuccessful as well, no root. I then read that all I needed to do was to install Superuser from the Market. In attempting this I found my device was no longer recognized by Market and after going through their troubleshooting process it’s still unrecognized, Next I decided, also most likely erroneously to reset the phone again using the three button combo as before. This time I noticed at the bottom of the screen written in yellow, E: File is written: not updated
Also as a side note my phone currently says that there are 133MB available and after the reset(s) my bloat ware has not returned,
So that’s it. I seem to have deleted something that kills the phone app and prevents me from rooting. Other than those two things the phone is working well. However as it sits it’s merely a small Internet tablet with no phone capability. Can anyone help me out with this? And yes, I have read and read and read about it but clearly this is beyond my ability to fix on my own.
Thanks,
Zeke
Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.
Reached said:
Hey, my skill level ranges between beginner and intermediate, but honestly in a situation like that I would odin back to stock. I have an epic 4g, so I have no idea what your download mode is or if you have one or if you have to use quick boot or fast boot? Its one of those. If **** ever hits the fan on me (Thank god it hasn't yet) I would odin to an old stock rom and root it and install a recovery and wipe and flash a ROM. Good luck I hope I helped and didn't sound like too much of a scrub.
Click to expand...
Click to collapse
I will research this Odin you mention as I have no clue as to what it is. Thanks, anyone else care to chime in?
Zeke
I'm not sure you guys can help me here as you seem to deal mostly with phones but I'm hoping, here is my problem.
I have the Pandigital PRD07T20WBL7 the tablet has never been hacked and I have had it for some time now but this morning when I turned it on It got as far as the boot screen and then just sits there, I have tried multiple times to reset it and/or cause it to restore to factory (Holding power and Vol up) I'm honestly not very knowledgeable when it comes to tablets or android systems so I'd love some advice on what I might be able to do to get this one working again, at this point restores or even a workable hack would be welcome. If someone could advise or point me in the right direction I would much appreciate it. BTW I have tried to run the Canadian update to the firmware just to see if I could get it working and it wont go in I get an error from the installer I've attached a screen of the error the updater gives me if thats any help to anyone. I appreciate any help I can get with the problem thank you.
First of all, I want to thank you all for this wonderful webpage/forum - it's very unusual to see such a 'friendly' forum and how willing people are to spend a great amount of time helping others out.
But to my problem, I tried to install Ubuntu tablet OS on Samsung Galaxy note 10.1 (GT-N8010) as it seemed no problem at all. But ever since then I've been stuck in this damn ODIN mode (download mode) - and to be honest I believe I have read and followed the instructions in every single "help thread" about this or similar issue, but however there seems to be NO way I can get my tablet to work normally again.
The device charges perfectly normally, KIES detects it, but it however doesn't seem to be able to recognize what "kind" of device this is. ODIN also (of course :silly: ) detects it, but no matter what help/tutorial/guide I've followed, nothing has worked to fix this. The only screen I can get can be seen on attached picture no. 1. I'm unable to enter recovery mode, but the screen I get when trying to boot to recovery mode can be seen on attached picture no. 2 - which is basically the same as on pic. no. 1, except for these beautiful gray bands/streaks I get all over the screen. No matter what I try, it won't enter recovery mode.
I've gone through this process both on Win 7 and Mac OS X (using Heimdall, Odin and all this stuff - flashing CWM, etc etc, to the tablet). I've even removed the battery twice with no observable success However I sometimes get the message in Odin that everything went all right, as in "passed", but this just keeps the same.
I've, as mentioned before, gone through all the help articles/threads about this or similar issue I can find here, through google and MUCH more so this is my final attempt to recover (or fix) my note 10.1 by asking you guys for help. Does anyone of you sweet sweet guys/girls have ANY idea about what I could do to fix this problem, or is it just hammer time?
Thank you SO much for reading, and ANY advice is appreciated and warmly welcome! And also thanks to all of you for the great knowledge you share in many other posts, I love browsing the forum here!
Kindest regards,
August
And yea, sorry for the bad picture quality, the darn iPad refused to take better shots - or, which is much more likely, I'm a horrible photographer :fingers-crossed: