I stuck at T-mobile Logo!! Can't get in to recovery and to the phone.
Can some one help me ?
Had a similar problem. Have you applied the engineering bootloader? Otherwise I think you're stuck. As far as I know you can't flash anything using the stock SPL. I brought mine back within the first 15 days for a new one. http://forum.xda-developers.com/showthread.php?t=453953
hskoon said:
I stuck at T-mobile Logo!! Can't get in to recovery and to the phone.
Can some one help me ?
Click to expand...
Click to collapse
First, try taking out the sim card and booting the phone. I've heard of at least 1 case where that worked .
Second, have you flashed the dev bootloader onto your phone? When you power it on with back+power, do you see a screen with colored bars (stock bootloader, or a white screen with 3 skateboarding androids (dev bootloader)?
If step 1 doesn't work and you don't have a dev bootloader, there's not much you can do, other than return it to t-mobile.
JesusFreke said:
First, try taking out the sim card and booting the phone. I've heard of at least 1 case where that worked .
Second, have you flashed the dev bootloader onto your phone? When you power it on with back+power, do you see a screen with colored bars (stock bootloader, or a white screen with 3 skateboarding androids (dev bootloader)?
If step 1 doesn't work and you don't have a dev bootloader, there's not much you can do, other than return it to t-mobile.
Click to expand...
Click to collapse
I not flash dev bootloader. I power it on with back+power, I see a screen with colored bars (stock bootloader). Then how I want to do for next?
hskoon said:
I not flash dev bootloader. I power it on with back+power, I see a screen with colored bars (stock bootloader). Then how I want to do for next?
Click to expand...
Click to collapse
Did you try taking out the sim and booting?
JesusFreke said:
Did you try taking out the sim and booting?
Click to expand...
Click to collapse
Yes. I did try take out the sim and booting. What I should do anything to flash it from tri color?
Hskoon, I think your stuck buddy. Call t-mobile for replacement.
Stericson said:
Hskoon, I think your stuck buddy. Call t-mobile for replacement.
Click to expand...
Click to collapse
I stay in Malaysia. I did call HTC but they ask me to send it back to T-mobile. I don't know why HTC no support it.
Take the battery out for at least 1 or 2 hours, then try. I have seem this problem with some units, hopefully this will be the only time it happens.
from the stock bootloader screen, can you apply factory settings?
faaque2 said:
from the stock bootloader screen, can you apply factory settings?
Click to expand...
Click to collapse
How to do factory setting from stock bootloader?
sorry
at this time there is no way to fix a phone that has lost its "system image" and only has the 'stock HTC SPL' or "rainbow bootloader" like there was on the older htc WM devices...
Yes thats what the bootloader is made for but the tools and image (dreamimg.nbh, is the name. if they keep the same naming convention as the WM ones.)
bhang
Where I can download dreamimg.nbh?
hskoon said:
Where I can download dreamimg.nbh?
Click to expand...
Click to collapse
hskoon, you cant. its a proprietary file that belongs to HTC.
Related
Hello world
a friend bought a verizon tp2 yesterday (I don't know why because cdma doesn't work in my country ) anyway, this guy open the box, connect the phone and try to upgrade the rom without read anything, in the midle of the rom flashing the phone get stuck and reboot and the phone never turn on again I thought "no problem, I will re-flash it in the tri-colour bootloader", but the phone is dead, no lights, no bootloader, no nothing, but when I connect the phone, windows show a new hardware message "qualcomm CDMA technologies MSM" but nothing happens.
looking the rom used by my friend, is a gsm rom
is totaly bricked ? there is a way to recover the phone?
thanks.
PS: sorry about my english
if you just flashed a custom gsm rom, then you should be fine. if shipped rom, you're f'ed. did you try pulling out the battery for a little bit?
the verizon tp2 is cdma and gsm, so it's usuable in most countries.
razorloves said:
if you just flashed a custom gsm rom, then you should be fine. if shipped rom, you're f'ed. did you try pulling out the battery for a little bit?
the verizon tp2 is cdma and gsm, so it's usuable in most countries.
Click to expand...
Click to collapse
no, it wont wokr even if you used a custom rom, as the phone wasnt meant for gsm roms
yes, I pulled out the battery for a entire night, nothing happen, I can't get the tri-colour screen
there is something like "frankenkaiser" ? or is a paper weight?
if the fone is being recognized just try 2 flash the stock rom it mite just work don't wait 4 the bootloader show up just remove the batt. put it back then press the power and vol. down button and hold it till it comes on if u don't c the bootloader ignore it and attempt 2 flash like normal
aijalon said:
if the fone is being recognized just try 2 flash the stock rom it mite just work don't wait 4 the bootloader show up just remove the batt. put it back then press the power and vol. down button and hold it till it comes on if u don't c the bootloader ignore it and attempt 2 flash like normal
Click to expand...
Click to collapse
the flashing software doesn't recognice the phone "connection error", and the power and vol keys doesn't work either
there is another method to restore the bootloader?
froman said:
the flashing software doesn't recognice the phone "connection error", and the power and vol keys doesn't work either
there is another method to restore the bootloader?
Click to expand...
Click to collapse
No you have a paperwright, does any combination work? does the light atleast come on? was the phone hard spl'd before flashing a custom rom?
djteotancolis said:
No you have a paperwright, does any combination work? does the light atleast come on? was the phone hard spl'd before flashing a custom rom?
Click to expand...
Click to collapse
no lights, no combination work, the only signal of life is the new hardware message, nothing else.
djteotancolis said:
no, it wont wokr even if you used a custom rom, as the phone wasnt meant for gsm roms
Click to expand...
Click to collapse
i didn't say it would work. i said he would be fine because he would be able to put it into bootloader mode and flash a proper rom. Only a gsm radio or wrong hardspl would brick his phone.
razorloves said:
i didn't say it would work. i said he would be fine because he would be able to put it into bootloader mode and flash a proper rom. Only a gsm radio or wrong hardspl would brick his phone.
Click to expand...
Click to collapse
..unless the chef decided to include a radio in their rom. Unlikely, but possible..
indagroove said:
..unless the chef decided to include a radio in their rom. Unlikely, but possible..
Click to expand...
Click to collapse
OP hasnt yet mentioned what exactly did he flash
djteotancolis said:
OP hasnt yet mentioned what exactly did he flash
Click to expand...
Click to collapse
offical htc touch pro 2 rom (GSM)
Hi GUys-
I at one point installed the Energy ROM. I decided I didn't like it and I went back to the stock VZW MR1 update. I realized today that the MR2 update was out so I flashed the phone. It now boots to the white loading screen with the green HTC logo and red text (in bottom left) but it goes no further. What do I do?
Thanks!
hoyadub said:
Hi GUys-
I at one point installed the Energy ROM. I decided I didn't like it and I went back to the stock VZW MR1 update. I realized today that the MR2 update was out so I flashed the phone. It now boots to the white loading screen with the green HTC logo and red text (in bottom left) but it goes no further. What do I do?
Thanks!
Click to expand...
Click to collapse
It sounds like a bad flash. Put it back into the bootloader (reset while holding voldown) and try again.
cajunflavoredbob said:
It sounds like a bad flash. Put it back into the bootloader (reset while holding voldown) and try again.
Click to expand...
Click to collapse
Thanks for the reply. That was my first thought, too. Turns out I never undid the SPL unlock, so when I flashed with stock ROM it was messed up. Relocking SPL made it work just fine.
hoyadub said:
Thanks for the reply. That was my first thought, too. Turns out I never undid the SPL unlock, so when I flashed with stock ROM it was messed up. Relocking SPL made it work just fine.
Click to expand...
Click to collapse
Just for fun, would you please note the steps you followed? Were you able to relock while the ROM was messed up? If not, what did you have to do that allowed you to unlock?
Thanks.
Mike
I had the same problem on my sprint touch pro 2, this has happened to me 2 times now, I used to be able to switch roms daily and now my second phone is a brick.
Yesterday my fiancée performed some updates from the market. Shortly after her phone turned off.
Now when trying to turn it on the phone gets stuck on the white screen with the green HTC logo.
I have tried booting it in to fast mode by turning it on with the volume down button held and then selecting fastboot.
This allowed me to try and flash the O2 ROM back to the phone. It find the software version on the phone (which is slightly newer than the ROM I have downloaded).
The next stage is "Rebooting in to bootloader" this is where it just comes to a stop, the fastboot menu freezes and the phone doesn't do anything.
Does anyone have any ideas? Much appreciated.
Is ur phone rooted or stock? U could try a factory reset...
Sent from my HTC Desire S using XDA Premium App
It's totally stock other than being unlocked.
If I try a Factory Reset from the HBOOT screen it just locks up. Is there another way?
If I try recovery it turns off, comes up with Green arrows in a circle, vibrates 5 or 6 thimes, then does nothing.
Hope your phone will comes up,try to flash ruu
Sent from my HTC Hero using XDA Premium App
zhaominghao said:
Hope your phone will comes up,try to flash ruu
Sent from my HTC Hero using XDA Premium App
Click to expand...
Click to collapse
I've tried to flash the RUU already haven't I? By downloading the O2 ROM.
richard_ha said:
It's totally stock other than being unlocked.
Click to expand...
Click to collapse
When you say unlocked, I'm assuming that you mean network unlocked and not S-OFF (via XTC clip)?
I'm afraid that I'd be tempted to return the device from where you bought it and attempt to get a repair/replacement unit.
Sorry that I was unable to help anymore.
ben_pyett said:
When you say unlocked, I'm assuming that you mean network unlocked and not S-OFF (via XTC clip)?
I'm afraid that I'd be tempted to return the device from where you bought it and attempt to get a repair/replacement unit.
Sorry that I was unable to help anymore.
Click to expand...
Click to collapse
Hi yes, network unlocked and not S-OFF
It seems to be like the bootloader has become corrupt some how.
I'll start making arrangments with HTC, thank you.
If anyone else has any ideas or suggestions let me know.
I checked all the other bricked threads and none have the same problem as me.
My HTC ONE X will not boot and or charge. I cannot get access to the bootloader or recovery.
My HTC ONE X had it's bootloader unlocked via the rogers htc-dev method. I also installed clockwork recovery. It is rooted also but you prob figured that already...
I pulled a bonehead move by flashing the MIUI rom the international one x by changing the update script to flash onto my phone. After it flashed it looked like it worked. When I left recovery and shut the phone off it would not turn back on.
I called AT&T they said they will switch it for me when they get a shipment but I want to keep this phone because the boatloader is unlocked and they might patch the rogers method.
Thanks in advanced.
P.S. I know how to use adb and other tools such as RUU and they did not work.
Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.
Ouch.... Another loss for htc sales
Sent from my HTC One X using xda premium
you cant get to hboot? 0.o
First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras
Reply
equlizer said:
Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.
Click to expand...
Click to collapse
No nothing happens even with the charging adapter plugged in.
kevina90 said:
you cant get to hboot? 0.o
Click to expand...
Click to collapse
Nope
sassafras_ said:
First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras
Click to expand...
Click to collapse
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.
jfn0802 said:
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.
Click to expand...
Click to collapse
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.
gunnyman said:
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.
Click to expand...
Click to collapse
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
jfn0802 said:
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.
Click to expand...
Click to collapse
Where do they have them in stock? I need to replace mine (screen issue) and can't find any around here.
powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+ 1
Sent from my HTC One X using xda premium
powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+2
Honestly, not trying to call you stupid or something, but did you really think it was going to run on this phone when it was meant for another one? The GPU and CPU are completely different...
Anyway, I'm glad AT&T is replacing it for you. Hopefully if someone else bricks the same way then they will be able to get a replacement as well.
so you are smart enough to use adb, an RUU, unlock your bootloader, root, flash roms.......but you aren't smart enough to see the hundreds of posts saying that the international roms don't work on our phones??
lol
Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?
Just pull the batte..... oh
jmattp said:
Just pull the batte..... oh
Click to expand...
Click to collapse
+1 for when I drowned my first one and it was stuck in a boot loop. I know it could have been saved if the battery would have been taken out.
Sent from my HTC One X
modest_mandroid said:
Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?
Click to expand...
Click to collapse
My EVO was unbrickable too, I flashed a rom that was designed for the international version. It only contained system and other basic rom stuff, nothing that was crazy.
No idea why you wouldn't be able to boot into recovery then. I hope all HTC handsets aren't like this..
Sent from my SGH-I897 using XDA
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
reflash
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
thesm4rt1 said:
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
Click to expand...
Click to collapse
I will definitely be trying that. Will be back in a couple of hours and let you know how it went. Thank you!
bbonline said:
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Butters619 said:
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Click to expand...
Click to collapse
I did do the factory wipe.
By the way, I tried what I was told to do and nothing happened. It successfully flashes the boot image and recovery, but when it tries to boot into the recovery, it just freezes in the recovery with the word TEAMWIN and a blue background....No menu or options.... I did try several different ways by downloading and installing several versions of the CWM and TWRP, but no success. Any other suggestions? Will I be stuck with this piece of brick now? Please help.
bbonline said:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Butters619 said:
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Click to expand...
Click to collapse
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
bbonline said:
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
Click to expand...
Click to collapse
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Butters619 said:
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Click to expand...
Click to collapse
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
bbonline said:
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
Click to expand...
Click to collapse
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
Darn.... I just hope I don't have to deal with sending it for any repair. Gave you thanks!
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
But only if they reboot and look, which from what I've seen here, they never seem to do.
iElvis said:
But only if they reboot and look, which from what I've seen here, they never seem to do.
Click to expand...
Click to collapse
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
Butters619 said:
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Click to expand...
Click to collapse
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
trichrome1 said:
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
Click to expand...
Click to collapse
Nope once you unlocked it won't ever say locked again. Just re-locked
gunnyman said:
Nope once you unlocked it won't ever say locked again. Just re-locked
Click to expand...
Click to collapse
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
You should probably double check that. Anybody with an AT&T One X had to have SuperCID to unlock their bootloader so that wouldn't matter. I have unlocked two AT&T One Xs and run the 1.85 RUU on both (one of them a couple times) and I have run the 2.20 RUU on one. every time it says RELOCKED.
Mine did this to when going to 4.5.
I did the following to get back into Recovery.
Use fastboot to flash the boot.img from the cleanrom 4.5 zip.
"fastboot flash boot boot.img"
I then flashed the recovery (TWRP 2.2.1.4 at the moment) again to the phone.
next I erased Cache.
"fastboot erase cache"
I then used the phone itself to reboot the bootloader and went into recovery. It took about 10 minutes but recovery finally booted.
At this point I had no access to anything on the SD card. so I selected mount and mounted the sd card as disk drive to access it through my PC. I was forced to format the drive at this point and loaded a fresh copy of the ROM onto the drive for flashing.
You probably just got a wrong recovery. The recovery on twrp website didn't work for me. The one I downloaded from the development section works fine.
Sent from my One X using xda app-developers app
trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
Screenshots PLS