Related
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.
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.
me and my sister have the same phone Nexus S but in my boot I see werid sign and her phone the boot is ok. whats the problem?
http://youtu.be/54rRMryRUX0
Is her phone connected to a computer?
Sent from my Nexus S using XDA App
in the video is my phone. i tried to connected her phone to computer and no sign in the boot
d3one said:
me and my sister have the same phone Nexus S but in my boot I see werid sign and her phone the boot is ok. whats the problem?
http://youtu.be/54rRMryRUX0
Click to expand...
Click to collapse
that unlocked padlock mean that your bootloader is unlocked.
Presumably you're talking about the icon at the bottom, that looks like a padlock, then it indicates that your phone (i.e. it's boot-loader) is unlocked. Nothing to worry about... unless you'd like to return your phone to the manufacturer (perhaps to claim warranty) or store, from which you bought it; In which case you'll probably have to have your phone re-locked.
simms22 said:
that unlocked padlock mean that your bootloader is unlocked.
Click to expand...
Click to collapse
what u mean bootloader is unlocked. its good or bad? everyong have that?
its hard to lock it?
d3one said:
what u mean bootloader is unlocked. its good or bad? everyong have that?
its hard to lock it?
Click to expand...
Click to collapse
its good. its like freedom for your phone. it means you can flash a custom recovery and flash custom roms. locking is easy to do.
simms22 said:
its good. its like freedom for your phone. it means you can flash a custom recovery and flash custom roms. locking is easy to do.
Click to expand...
Click to collapse
im sorry but im noob in android
what u mean "it means you can flash a custom recovery and flash custom roms"
d3one said:
im sorry but im noob in android
what u mean "it means you can flash a custom recovery and flash custom roms"
Click to expand...
Click to collapse
Just means you can put customized/modified versions of android, whenever you feel like. This is what makes Google's Android powerful/unique and different from Apple's iOS (for iPhone) and Microsoft's Windows Phone(OS), for example.
I never thought it'd happen to me..
Anyways.
I'm on Virgin Mobile in Canada, just recently unlocked my bootloader and rooted.
The process was bumpy but ultimately successful..ish.
I couldn't actually flash any roms. Not sure if it was because of the bumpy root process,
but every rom would just bootloop and I'd have to restore and deal with HTC Sense.
Great.
I had downloaded a Liquid [somethingorother] ROM from my PC and flashed it, with blind hope.
It was looping, as I half-expected.
I had this crazy idea that my roms were looping because I had neglected to press the "Perm Root" button
on the AIO root tool I had used.
Ecstatic, I rushed up and pressed that button as soon as I could.
The process went off without a hitch, but the next time I tried to boot something odd happened.
Every time I boot the HTC splash screen stating "this is for development purposes only.. etc" pops up.
-the one that would pop up when entering the bootloader - EVERY TIME.
I tried to restore but this splash screen still shows up, then loops on the HTC ONE screen....
AAAAAND that's where I'm at now. I attempted to factory restore from the bootloader, which would
erase my backups and whatnot. I don't know how infamous this issue is but I am unable to mount my storage.
Plenty other people seem to have this issue.
So, is there anything I can do?
You should try to run an RUU, then report back.
Sent from my HTC One S using Xparent Blue Tapatalk 2
invasion2 said:
You should try to run an RUU, then report back.
Sent from my HTC One S using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I'm actually trying to find one now. I haven't been able to find one for Bell/Virgin wild on the interwebs.
I'm trying to find the mysterious RUU section on the painfully slow HTCdev website..
anyone have a link or something?
http://forum.xda-developers.com/showthread.php?t=1543588
Sent from my HTC One S using Xparent Blue Tapatalk 2
The most common reason for ROMs hanging on boot splash or looping is that you failed to fastboot flash the boot image that comes with the ROM.
The good news is if you can detect the phone in your computer, your phone isn't bricked.
That message you mentioned is normal for all of us flashers
I bet you didn't notice the "tampered" flag or you would have freaked out even more
Sent from my HTC One S
I need help please. I flashed the rom following the instructions and my phone boots but the screen remains all black. I hear a sound when it boot and nothing else. I am trying to reach recovery but I haven't been able by holding volume down + power. Any help please?
---------- Post added at 11:08 AM ---------- Previous post was at 10:58 AM ----------
Never mind I got it fixed. It was all because the boot img wasn't in place yet.
Sorry to beat a dead horse but i think i bricked my phone ! I to have a virgin mobile canada HTC One S but i can't find the ruu for virging mobile I Tried bell and it didn't work thus screwing up my phone. please pleaase please i need help I just got this phone yesterday.
lilsammy11 said:
Sorry to beat a dead horse but i think i bricked my phone ! I to have a virgin mobile canada HTC One S but i can't find the ruu for virging mobile I Tried bell and it didn't work thus screwing up my phone. please pleaase please i need help I just got this phone yesterday.
Click to expand...
Click to collapse
your in the wrong section. If you have the one v from virgin mobile, which code name is primo not ville check here http://www.filefactory.com/f/0eafb9c43276c308/ for ruu and section go here for support http://forum.xda-developers.com/forumdisplay.php?f=1551
or here http://htcruu.com/?dir=Primo
puertoblack2003 said:
your in the wrong section. If you have the one v from virgin mobile, which code name is primo not ville check here http://www.filefactory.com/f/0eafb9c43276c308/ for ruu and section go here for support http://forum.xda-developers.com/forumdisplay.php?f=1551
or here http://htcruu.com/?dir=Primo
Click to expand...
Click to collapse
no please help me. I am positive it is a One S I bought it yesterday from Virgin mobile in Canada. It says one s on the box it doesn't have the hump the one v has on the bottom. I am totally lost and don't know what to do The Bell mobility ruu didn't work for it and it seems like a virgin mobile ruu is none existant
lilsammy11 said:
no please help me. I am positive it is a One S I bought it yesterday from Virgin mobile in Canada. It says one s on the box it doesn't have the hump the one v has on the bottom. I am totally lost and don't know what to do The Bell mobility ruu didn't work for it and it seems like a virgin mobile ruu is none existant
Click to expand...
Click to collapse
Does the your computer recognize the one s
Sent from my Galaxy Nexus using xda premium
lilsammy11 said:
no please help me. I am positive it is a One S I bought it yesterday from Virgin mobile in Canada. It says one s on the box it doesn't have the hump the one v has on the bottom. I am totally lost and don't know what to do The Bell mobility ruu didn't work for it and it seems like a virgin mobile ruu is none existant
Click to expand...
Click to collapse
don't know what to tell you if you got it from virgin mobile i just checked there site http://www.virginmobileusa.com/shop/cell-phones/android-phones/ and they selll the V series. did you buy it form there store/site ? or second hand?
soljafree said:
Does the your computer recognize the one s
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes I think It does because I've tried to use the bell ruu about 5 times and it'll start but then I'll get error 155 a little while into it
puertoblack2003 said:
don't know what to tell you if you got it from virgin mobile i just checked there site http://www.virginmobileusa.com/shop/cell-phones/android-phones/ and they selll the V series. did you buy it form there store/site ? or second hand?
Click to expand...
Click to collapse
Try virginmobile.ca . But yes I just wanted to say I really appreciate you guys's help
lilsammy11 said:
Yes I think It does because I've tried to use the bell ruu about 5 times and it'll start but then I'll get error 155 a little while into it
Try virginmobile.ca . But yes I just wanted to say I really appreciate you guys's help
Click to expand...
Click to collapse
ahhhh i see. ok man your DONE!! becasue that error 155 means that your bootloader is unlocked. and to flash the ruu you would have to relock. but you said you're brick nothing happens to your device?
puertoblack2003 said:
ahhhh i see. ok man your DONE!! becasue that error 155 means that your bootloader is unlocked. and to flash the ruu you would have to relock. but you said you're brick nothing happens to your device?
Click to expand...
Click to collapse
ohhhhh that makes sense, and I think I'm bricked. I'm pretty sure I can run adb commands though. maybe I should try oem lock again command again? this is exactly what the top says
***TAMPERED***
***RELOCKED***
*** Security Warning***
I should point out that when I start the ruu the screen actually goes to a black screen with "htc" on it and that's it. and I tried to lock it again via abd and it says its already locked
---------- Post added at 05:27 AM ---------- Previous post was at 05:15 AM ----------
Ok I should also say that when ever I restart phone it goes right into bootloader. I'm guessing because ruu erased everything ? should i maybe unlock boot loader, root, download stock rom and then try rue again?
lilsammy11 said:
ohhhhh that makes sense, and I think I'm bricked. I'm pretty sure I can run adb commands though. maybe I should try oem lock again command again? this is exactly what the top says
***TAMPERED***
***RELOCKED***
*** Security Warning***
I should point out that when I start the ruu the screen actually goes to a black screen with "htc" on it and that's it. and I tried to lock it again via abd and it says its already locked
---------- Post added at 05:27 AM ---------- Previous post was at 05:15 AM ----------
Ok I should also say that when ever I restart phone it goes right into bootloader. I'm guessing because ruu erased everything ? should i maybe unlock boot loader, root, download stock rom and then try rue again?
Click to expand...
Click to collapse
It it says relocked and its not OEM software on there that's y u keep rebooting into boot loader had that happen on a vivid I had. Try reflashing the ruu
Sent from my Galaxy Nexus using xda premium
Man, I never read anything good anywhere in these forums lol. This phone is so awesome as is, I really don't think it is worth the trouble unlocking and rooting and all. Maybe it is cause only the bad gets posted but there seems to be a lot of it. This phone is definitely meant for the normal person who cares nothing about flashing it seems. I would love to be able to just root it for root-required apps, themes and Volume wake and/or slide to wake but it seems to be more trouble than it's worth.
Cyanogenmod 10 makes this phone 10 times the awesome.
soljafree said:
It it says relocked and its not OEM software on there that's y u keep rebooting into boot loader had that happen on a vivid I had. Try reflashing the ruu
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry I don't quite understand, should I try to getting stock back ? Or just continue to try and get the ruu to work ?
LibertyMonger said:
Man, I never read anything good anywhere in these forums lol. This phone is so awesome as is, I really don't think it is worth the trouble unlocking and rooting and all. Maybe it is cause only the bad gets posted but there seems to be a lot of it. This phone is definitely meant for the normal person who cares nothing about flashing it seems. I would love to be able to just root it for root-required apps, themes and Volume wake and/or slide to wake but it seems to be more trouble than it's worth.
Click to expand...
Click to collapse
Yea I found that out to late, I actually screwed up the phone and somehow saved myself by getting on CM10 then I realized how much I love stock and wanted to go back and now i'm here stuck on bootloader -.-
lilsammy11 said:
Sorry I don't quite understand, should I try to getting stock back ? Or just continue to try and get the ruu to work ?
Yea I found that out to late, I actually screwed up the phone and somehow saved myself by getting on CM10 then I realized how much I love stock and wanted to go back and now i'm here stuck on bootloader -.-
Click to expand...
Click to collapse
Unlock your phone again. Change your CID to HTC__001. Then run an unbranded RUU.
Sent from my locked, tampered ville
Hi,
I am new to this forum.
Few days back, I bought a sensation XE on ebay where the seller claims to have run an update and after that, the display backlight wouldn't go on again.
I thought that he screwed up somewhere and I could just flash a lower version and everything would be fine.
But once I got it and entered the bootloader (default one, no root it seems), the light wouldn't go on either. Somewhere I read that this is an indicator that there is a hardware problem which is causing the error since the bootloader is kind of software independant.
Is that right? I just wanted to make sure, before I digg into either way.
Or is it possible that it realy is a software error?
Any advice would be greatly apprechiated
Kindest Regards
Rene
surfer90 said:
Hi,
I am new to this forum.
Few days back, I bought a sensation XE on ebay where the seller claims to have run an update and after that, the display backlight wouldn't go on again.
I thought that he screwed up somewhere and I could just flash a lower version and everything would be fine.
But once I got it and entered the bootloader (default one, no root it seems), the light wouldn't go on either. Somewhere I read that this is an indicator that there is a hardware problem which is causing the error since the bootloader is kind of software independant.
Is that right? I just wanted to make sure, before I digg into either way.
Or is it possible that it realy is a software error?
Any advice would be greatly apprechiated
Kindest Regards
Rene
Click to expand...
Click to collapse
did not get your question try to simplify it and also the details of your phone and wad bootloader shows up is it
shrex said:
did not get your question try to simplify it and also the details of your phone and wad bootloader shows up is it
Click to expand...
Click to collapse
Question is: can this be a software error that could have come from something gone wrong while updating or does this show that it has to be a hardware error?
What I said was that when I enter the bootloader, the backlight isn't on either.
bootloader shows
****LOCKED***
Pyramid PVT SHIP S-ON RL
HBOOT 1.29.0000
RADIO-11.24A.3504.31_M
Open ADSP-v05.6.0.2226.00.0418
eMMC-boot
Noone knows the answer or noone understands the question?
maybe I should rerephrase the question:
If there is no backlight shining in bootloader, can this be caused by a firmware error or does this HAVE to be a hardware error?
surfer90 said:
maybe I should rerephrase the question:
If there is no backlight shining in bootloader, can this be caused by a firmware error or does this HAVE to be a hardware error?
Click to expand...
Click to collapse
do u mean the backlight wch the soft keys have (menu,home,back,search) buttons thos keys?
Not only that, I mean display and button backlight. You can't see anything unless you turn the phone to reflect the sun
Ohh now I got it ... Boot into bootloader n select factory reset but b sure it vll delet all ur data n vll make ur phone as stock
hit thanks if I hve hlped you
sent from HTC sensation using xda premium
Okay i chose factory reset and it didnt give me anything to choose.
Seems like it has finished now.
But still all light is off
surfer90 said:
Okay i chose factory reset and it didnt give me anything to choose.
Seems like it has finished now.
But still all light is off
Click to expand...
Click to collapse
Try flashing a ruu.. Check ruu info guide by kgs1992 in sensation general section.. There instructions to find correct ruu and flashing it were given
Sent from my HTC Sensation using xda premium
okay I did the flash and it was completed without an error. but still the screen has no light.
But (I am not sure whether this happened before) the buttons at the bottom sometimes are iluminated.
So this is a hardware error? or can it still be a software error?
thanks