Related
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?
What is the location of the Nexus S Boot image? i.e. On startup the picture with all black that says "Google" on it.
Looking for the location of this image.
Also if anyone knows the method of going about changing it.
All help is appreciated thank you.
I don't believe it's on the /system partition; I looked for it extensively a couple of weeks ago. I'm pretty sure it's in the kernel boot image.
I don't have the skills yet to extract stuff from the bootloader. If you do, that's where you should be looking.
Thank's for the reply. I feared it might be that way. hmmm. Looks like I need to learn a thing or two If I want a custom image
there was another topic about this
and in the SNS it is not a series of PNG images as in the other
AOS phones, instead it's a video clip
AllGamer said:
there was another topic about this
and in the SNS it is not a series of PNG images as in the other
AOS phones, instead it's a video clip
Click to expand...
Click to collapse
He's not talking about the startup animation that you see on a normal boot.
He's talking about the very first bootup screen you see when you turn the phone on; the one that is just the word Google on a black background. This one shows no matter what you're booting into. It's not part of the animation you're referring to. I've opened that and checked, and I posted it in the other thread where a guy was asking for the boot animation, but was actually looking for the Google word one.
distortedloop said:
He's not talking about the startup animation that you see on a normal boot.
He's talking about the very first bootup screen you see when you turn the phone on; the one that is just the word Google on a black background. This one shows no matter what you're booting into. It's not part of the animation you're referring to. I've opened that and checked, and I posted it in the other thread where a guy was asking for the boot animation, but was actually looking for the Google word one.
Click to expand...
Click to collapse
Correct. I have a personal picture I made on my G1 a while back that I wanted to make for my Nexus S, but at the moment, the Team Whiskey splash screen is on it, and I don't much care for it. So I'm looking for a way to change that. The splash image came with the 1.4GHz kernal.
uhhhhhhhh... i'll be interested in the location of that too
to upload my own pic
so distortedloop , mind sharing the location?
i'd like to play around with that too
Had I more knowledge on the subject of building kernels, i'd be more then willing to tackle it, but alas, I have no knowledge on the subject.
Wonder how difficult it is to grasp...I'd like to try building my own kernel.
AllGamer said:
uhhhhhhhh... i'll be interested in the location of that too
to upload my own pic
so distortedloop , mind sharing the location?
i'd like to play around with that too
Click to expand...
Click to collapse
I don't know where in the boot image it is, but I'm 99% certain it's not in the regular ROM space we can get with a file explorer. I asked the famous supercurio what he thought, and he said he's never looked for it but agrees it's probably in the bootloader. He said he'll try to remember to check it out if he remembers.
@SpartusTana - if Team Whiskey's replaced it, they must know the location! Maybe ask them for the location, and/or a rip of it for the guy who's looking for it to port to another phone (in another thread here).
That's a healthy idea. I'll try hoping over to their IRC to see if anyone has the knowledge of it.
Any idea on the guy's name who is working on the port? I'd much like to get in touch with him.
Also, it looks like they're doing this on HTC devices via fastboot.
Personally, I wouldn't muck with it on my phone, but the really intrepid might be willing to read the tutorial here and try it out on our Nexus S...
edit: actually probably won't work, they're mentioning using an "engineering bootloader"...
that's for the info
well, in the worse case scenario, we just need to re-flash the ROM in CW
AllGamer said:
that's for the info
well, in the worse case scenario, we just need to re-flash the ROM in CW
Click to expand...
Click to collapse
If you mess up your bootloader, you might not be able to get into CW, right? That's my fear.
Yah it doesn't appear as though it will work but thank you for looking into it.
@distortedloop You're correct on that. There's no real seperate button combination to bypass the bootloader to get into the recovery. So if the bootloader got screwed up...you'd screw yourself right back. I am wholy against messing with the bootloader haha.
sorry for requesting in this old thread. but is there any progress on this? really want to change that splash...
It is possible I have done it with the second stage Bootloader... The first stage is still google with the unlock.
If you speak Japanese This may be of some help to you.
http://creamsnexus.blogspot.com/2011/02/change-nexus-ss-boot-splash-image.html
Hi,
New to HTC and Android, but just wanted to get your opinion on something.
I got an unlocked HTC Desire S from a Chinese (Hong Kong) supplier via a local middleman. It had all kinds of Chinese bloatware on it, and so I decided to flash a new rom. When I went into About phone > Phone identity to write everything down before flashing, I noticed it has a strange 'Device serial number' of 123456789012. That looks kind of strange. On the box sticker and on the sticker in the battery compartment of the phone, what I see is "S/N: SH1CATJxxxxx". Is there anything fishy going on there?
The default Android 2.3.3 OS seems all right. It has what looks like a default HTC startup splash screen (though I don't know if that makes a difference). I did notice that there wasn't a Power settings entry in settings to change fastboot. I had to pull out the battery to get to the boot screen. Don't know if that's a big deal either. I also noticed it was S-Off to begin with when I installed root.
Does this all seem strange, legit, clone-ish? Are there even Desire S clones/knock-offs/gray models/and the like out there? I don't think so... but still, that is a strange device serial number in the phone software, and even the printed serial numbers on the box and battery compartment seem strange, starting with SH instead of HT.
Would appreciate your thoughts. Thanks.
waterprism said:
Hi,
New to HTC and Android, but just wanted to get your opinion on something.
I got an unlocked HTC Desire S from a Chinese (Hong Kong) supplier via a local middleman. It had all kinds of Chinese bloatware on it, and so I decided to flash a new rom. When I went into About phone > Phone identity to write everything down before flashing, I noticed it has a strange 'Device serial number' of 123456789012. That looks kind of strange. On the box sticker and on the sticker in the battery compartment of the phone, what I see is "S/N: SH1CATJxxxxx". Is there anything fishy going on there?
The default Android 2.3.3 OS seems all right. It has what looks like a default HTC startup splash screen (though I don't know if that makes a difference). I did notice that there wasn't a Power settings entry in settings to change fastboot. I had to pull out the battery to get to the boot screen. Don't know if that's a big deal either. I also noticed it was S-Off to begin with when I installed root.
Does this all seem strange, legit, clone-ish? Are there even Desire S clones/knock-offs/gray models/and the like out there? I don't think so... but still, that is a strange device serial number in the phone software, and even the printed serial numbers on the box and battery compartment seem strange, starting with SH instead of HT.
Would appreciate your thoughts. Thanks.
Click to expand...
Click to collapse
Set up adb and type
adb devices
That'll give you your actual device number. No confusion then...
BTW even my device serial number starts with SH... that's not an indicator of a fake device. Check tour device serial number via adb and if it matches the one on the box... I guess you're good to go.
Beamed from the Dark Side using xda premium.
Through adb, it shows that same 123456789012 number.
so, it's probably just dumb luck that the no. is so Nothing to worry about.
shrome99 said:
so, it's probably just dumb luck that the no. is so Nothing to worry about.
Click to expand...
Click to collapse
Yup. Guess you're just plain lucky!! But then the box belongs to some other phone.how about some pics or screenshots??
Beamed from the Dark Side using xda premium.
waterprism said:
...starting with SH instead of HT...
Click to expand...
Click to collapse
There are different serials for different regions/brands. SH is ok, it is the same for North Africa
I am not aware of a method to change the serial number (never needed such) but I am sure that there is. So if your system is android and your device is solid and nice then this should be a Desire S
Hi. Thanks, everyone.
@enigmaamit, I've posted a few pics and a screenshot. Not sure what kind of screenshot you need. Let me know if you need anything else. Thanks. Also not sure if these pics mean much if funny stuff is going on somewhere. The serial on the box clearly doesn't match the screenshot. And that seal was broken when I opened the package.
@amidabuddha, okay, thanks. But like I said above, and enigma said, the S/N on the box is one thing, the S/N the phone is printing out in the 'Phone identity' screen is totally different.
Appreciate your help.
That 'seal' doesn't look very authentic. There are grammatical mistakes too. And(I just noticed) it says 'SEALED PACKGE' instead of package so there's definitely something wrong.
I hope the phone is genuine.
The device is probably legit, just slightly used by someone else before. I think it's second hand, and the box belongs to another device.
waterprism said:
Hi. Thanks, everyone.
@enigmaamit, I've posted a few pics and a screenshot. Not sure what kind of screenshot you need. Let me know if you need anything else. Thanks. Also not sure if these pics mean much if funny stuff is going on somewhere. The serial on the box clearly doesn't match the screenshot. And that seal was broken when I opened the package.
@amidabuddha, okay, thanks. But like I said above, and enigma said, the S/N on the box is one thing, the S/N the phone is printing out in the 'Phone identity' screen is totally different.
Appreciate your help.
Click to expand...
Click to collapse
Looks legit to me. I wouldn't worry if it was my device.
Lol.... why don't you fool around and use the bar code scanner to scan the bar codes on the box and see where that leads you to!!
I'm starting to enjoy this Scotland yard stuff!!
Beamed from the Dark Side using xda premium.
Thanks, everyone. Guess I'll have to decide on my next step.
I'll do that, enigma. You mean with just a normal downloaded QR code app?
Use this - https://market.android.com/details?...mNvbS5nb29nbGUuenhpbmcuY2xpZW50LmFuZHJvaWQiXQ..
My device was made in Taiwan, not in China as yours!
Well, HTC is based Taiwan, but sometimes companies manufacture stuff in other countries too. It may also be that the packing is fake, which seems most likely at this time.
Also, since it's S-OFF, you should try some custom ROMs, Sense 3.5 is nice. Try Endymion or Virtuous Affinity. If they work, then it should prove that the device is legit. A knock off can't flash a ROM made for this, it's impossible.
Also, in hboot mode, select recovery and tell us what you see. If it's CWM or 4EXT, then it'll prove it's second hand. If you see stock HTC recovery, (red triangle with !) forget your worries
My box looks the same, the only difference is the seal
Sent from my HTC Desire S using xda premium
shrome99 said:
Well, HTC is based Taiwan, but sometimes companies manufacture stuff in other countries too. It may also be that the packing is fake, which seems most likely at this time.
Also, since it's S-OFF, you should try some custom ROMs, Sense 3.5 is nice. Try Endymion or Virtuous Affinity. If they work, then it should prove that the device is legit. A knock off can't flash a ROM made for this, it's impossible.
Also, in hboot mode, select recovery and tell us what you see. If it's CWM or 4EXT, then it'll prove it's second hand. If you see stock HTC recovery, (red triangle with !) forget your worries
Click to expand...
Click to collapse
Hi. Unfortunately, I've already flashed a new rom and so I can't remember what the original recovery was like... I flashed it up to 2.3.5 and Sense 3.0. I'm still new to Androids and didn't really have any misgivings about the phone at that time. It was during the whole process of flashing it, seeing that it was already S-Off, seeing that the serial number was sketchy, etc., that I began to wonder. By the time I was pretty sure something was wrong, I'd already flashed to official 2.3.5 to get rid of the Chinese stuff that I mentioned in my OP.
So, what this tells us is that the phone isn't a knock-off I guess. But I'm pretty sure it's a refurb/second-hand phone (refurb and second-hand are pretty much mutually inclusive here, so bottom line, it's a refurbished second-hand phone).
If not that, it's maybe some kind of development set or something. I came across some Chinese threads out there that have the serial number 0123456789012 mentioned in them. When I did a Google Translate on them, I kind of gleaned that that number can indicate a development or engineering set (or something like that). So it could mean it was used in development and now they're selling them off. Either way, not a new phone.
But the plot thickens when I actually came across a post here at xda that mentions that you can actually change the serial number like this --
Code:
fastboot oem writeserialno HT95XXXXXXXX
Which means these guys could have taken any phone and just wiped the serial number for this serial number.
yup, that seems to be it. It's a second hand phone, and the seller, in order to protect his identity, changed the serial no. The culprit is your supplier or middleman.
CASE CLOSED
One more thing - do you see any sort of hardware issues, that may be caused due to aggressive usage? Like big scratches on the screen or the unibody? If not, then you're just lucky to have gotten an S-OFF device.
shrome99 said:
One more thing - do you see any sort of hardware issues, that may be caused due to aggressive usage? Like big scratches on the screen or the unibody? If not, then you're just lucky to have gotten an S-OFF device.
Click to expand...
Click to collapse
No, not really. Phone works pretty well. Nothing glaring that I can notice, especially now after flashing to a slightly newer version of Android and Sense than the release shipped with. Also, obviously getting rid of that Chinese bloatware helped it a bit. There's a teeny-tiny scratch on the mesh speaker at the top that gets my goat right by the goddamn horns, I have to admit. I also just realized right this second that there's a protector screen on it! I just took it off. I doubt brand new Desire S's ever shipped with a screen protector already attached, if someone could just confirm.
But yeah, I've got it and it's S-Off. As I type that though, I'm pretty sure I'll be taking this further.
i doubt its fake ,i more expect that its a stolen phone with a changes serial number.
you can also check the warranty seal on top of a tiny screw right above the battery compartment.
Hi Guys,
New to flashing the Sensation, though I've done my HD2 a good few times.
Girlfriend just bought a Sensation and I'm eager to flash a decent ROM to it but failing at the first hurdle.
From what I can tell, there is no HBOOT but instead it has uboot (forgive me if this sounds ridiculous).
When I use Power+Volume Down, I do not get a white screen with options and information but instead get a black screen. There's no sign of an HBOOT version, but there is a uboot version number.
If I press Power +Volume Up I am sent to a recovery mode, but I don't think it's CWM.
If I try to use Revolutionary, it finds the phone (in normal mode, not h/u boot) and says that the phone is not supported.
Phone was bought in China but I think it is a Euro model (T Mobile branding on top of phone)
There is a possibility that a ROM has already been flashed onto it - but it sucks, and I want her to get the best from her new phone.
Also, I cannot get the CID or MID number. Tried CID getter, neither of them were on there. Tried terminal emulator, no response from getprop ro.cid or ro.mid.
So even if I wanted to upgrade the firmware, I am unsure which one to use!!
Has anyone run into this sort of situation? Using SuperTool I was able to get root access, which is at least a step in the right direction but I'm not sure how to proceed. Maybe it's already s-off and I can update the firmware and thus get hboot. But if it's not, then I run the risk of ruining it.
If you think I can go ahead and try to install new firmware, without risk of bricking or semi bricking, then I would probably be inclined to go for it.
Looking around here and also on Google, I haven't seen anyone with the same issue, so any help you can give would be very welcome!!
Many thanks in advance,
Mr Al
two possibilities: your sensation is faked or it has been relocked by the sellor which is called "baikamumaji".
Sent from my Sensation using XDA
Thanks for that, although it's slightly bad news!!
I'll see if we can get in touch with the seller and take it from there.
Ok, we've just spoken (online) with the sellers 'tech' guy.
I think pmbldc is right, it's a fake.
Their guy says that it can be flashed, but only using the roms on their forum.
I think it's bull. Currently feeling ripped off and unhappy, but what can I do?!?!
Never buy any more devices from China??? Jus sayin... Sorry you got ripped off bro.. Sucks that that sort of thing happens...
Haha! A little tricky that one, as I live in China!
I've bought lots of electronics over here, both locally branded/produced and international. Lots of successes.
To be fair (grudgingly) this guy was considerably cheaper than everyone else. That old adage of 'if something seems too good to be true, it is' applies very well in this case.
Pretty disgusted with the whole thing, the conversation my girlfriend had with the 'tech' guy was ridiculous. Both she and I work in tech so his usual line of BS didn't work with us.
So now, having decided to be sensible and not buy the HTC One X, we're going to end up spending about the same amount of money anyway!
All we can do is learn from our mistakes, and at least now I know what to look for when buying a Sensation!!!!
True Story, bro
This question has bothered me for a long time. As you guys know, when the bootloader is unlocked, everytime when you boot the device, the warning screen will show up
That screen is quite annoying...
Therefore I use a lot of time searching on Google, many people said it is impossible to remove it...
However, I saw them successfully replaced it on Moto and LG V20 (V20 Guide XDA link)
or something like this V30 Discuss XDA thread
I think maybe we can use the HEX tool to replace the warning screen with original logo sceen...?
But unfortunately, I'm not a developer and still couldn't find out the solution...
Can anyone please help research in how to remove or replaced that annoying screen...? Really appreciate!
UP. I'm also interested to know if it's possible.
AFAIK, there's no way around it. Think of it as a badge of honor.
I hear there's meds that will take away the pain.
Hitting the resume button makes the warning screen go away quicker.
swieder711 said:
Hitting the resume button makes the warning screen go away quicker.
Click to expand...
Click to collapse
Yeah but that's still quite annoying... So I'm thinking if there's a way to get rid of that
MyStyle0714 said:
Yeah but that's still quite annoying... So I'm thinking if there's a way to get rid of that
Click to expand...
Click to collapse
First for a little background on unlocked bootloader warnings. It used to be that the actual graphics files for the initial splash screen were located in their own partition and after you unlocked the bootloader you could flash a new image to that partition of any correctly formated graphic file to display whatever you wanted. Starting with the original Pixels Google moved them into the bootloader itself and I am not aware of any Dev that has or is willing to experiment with altering the bootloader since any error in doing so will hard brick the phone.
Why does it bother you so much? Its not like you need to hide it from the FBI. You should be PROUD...