Related
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.
Hello, I have a question
I had on my sensation a custom rom
But i wanted back on a stock rom.
So now, i flashed a PG58IMG,but I have not thought about it that I no longer have root.
I've successfully instaled it, but when I start the mobile phone now I'm just the htc logo and no further.
So guys, anyone can help me with my problem.
I Think he bootloader is broken
I recommend going on youtube to find a solution, just search "how to get back to stock rom" or something like that, i am sure something will pop up, and see where you went wrong, if you did, or google it
Taker18 said:
Hello, I have a question
I had on my sensation a custom rom
But i wanted back on a stock rom.
So now, i flashed a PG58IMG,but I have not thought about it that I no longer have root.
I've successfully instaled it, but when I start the mobile phone now I'm just the htc logo and no further.
So guys, anyone can help me with my problem.
I Think he bootloader is broken
Click to expand...
Click to collapse
A sure way for going back to stock is flashing a RUU. You'll still be s-off and you need to check that the RUU is compatible with your cid.
Sent from my Kindle Fire using Tapatalk
ar4l said:
A sure way for going back to stock is flashing a RUU. You'll still be s-off and you need to check that the RUU is compatible with your cid.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Yea, but i can"t start my Sensation
Taker18 said:
Yea, but i can"t start my Sensation
Click to expand...
Click to collapse
Pull out the battery, insert it, get into bootloader by pressing and holding vol down + power button hold them until you'll get into bootloader. Connect to a computer, change on fastboot mode and You are ready to flash a RUU
ok i dont know what happened.........ive went into twrp recovery many times before!! i went to get in recovery, it wouldnt let me!!! everytime i tried....it would just sit for about 1 and a half seconds then reboot to the htc white screen with the red lettering on the bottom. like it was trying to reboot into the rom. well it wouldnt go to my current rom no matter what!!!! finally held down power untill my soft keys blinked a few times which then eventually got me into my bootloader. from there i tried rebooting into recovery with same results as before! then tried from bootloader mode to reboot into the rom.........no go!!!!!! so finally now i locked bootloader, and am running ruu!!!!! hopefully it boots up ok? ill report back with my findings! anyone see this before?
edit...........got it to boot finally!!!!!! deleted all my files!!!!!! music, pics, everything! luckily i made a backup the other day! still lost some of my files and such! damn it man! this sucks!
Another prime example of why you should always have a backup. Glad you got it unbricked though.
Sent from my HTC One X using xda premium
ECEXCURSION said:
Another prime example of why you should always have a backup. Glad you got it unbricked though.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
me 2!!!! scared me bro!!!!!!! lol!
Ok well now I tried unlocking my bootloader again, it went through fine, but I can't get a custom recovery on here? My bootloader now says
Tampered
Relocked
Any suggestions?
Sent from my HTC One X using Xparent ICS Tapatalk 2
zounduser said:
Ok well now I tried unlocking my bootloader again, it went through fine, but I can't get a custom recovery on here? My bootloader now says
Tampered
Relocked
Any suggestions?
Sent from my HTC One X using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Need to root first??
Sent from my HTC One X using xda app-developers app
zounduser said:
Ok well now I tried unlocking my bootloader again, it went through fine, but I can't get a custom recovery on here? My bootloader now says
Tampered
Relocked
Any suggestions?
Sent from my HTC One X using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
If it says relocked, do you think you unlocked it? I'm just saying, my suggestion would be to not flash a recovery until the bootloader says unlocked. But let's see what others say.
Sent from my HTC One X using Tapatalk 2
SoberGuy said:
If it says relocked, do you think you unlocked it? I'm just saying, my suggestion would be to not flash a recovery until the bootloader says unlocked. But let's see what others say.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
yes i agree as well. however i didnt try pushing the recovery until after i ran the unlock process. im not completely dumb. lol but ya still no go ran the unlock bootloader twice with no luck.
rpomponio said:
Need to root first??
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
im rooted, with super su, as i said the unlock process went through, 2 the point where it says on screen........do you want to unlock bootloader. so basically its not sticking?
edit....after i ran the ruu, bootloader just said relocked. now it says tampered and relocked.
zounduser said:
im rooted, with super su, as i said the unlock process went through, 2 the point where it says on screen........do you want to unlock bootloader. so basically its not sticking?
edit....after i ran the ruu, bootloader just said relocked. now it says tampered and relocked.
Click to expand...
Click to collapse
Re-run the unlock but do not boot to boot loader using adb. Shut the phone off, boot to bootlader by holding vol- then run unlock again. reboot back to bootlader and check. This has been happening a lot, cant explain why but if you boot to bootlader through adb then the unlock doesnt stick a lot of times. Its happened to me on my last two phones. If you werent using ADB and it still didnt stick, just keep trying, it will work. I found the solution in the unlock bootlader thread, after 20+ tries using adb to reboot. It worked first time when i bypassed ADB. i was scared, thought HTC blocked us lol. :fingers-crossed:
nugzo said:
Re-run the unlock but do not boot to boot loader using adb. Shut the phone off, boot to bootlader by holding vol- then run unlock again. reboot back to bootlader and check. This has been happening a lot, cant explain why but if you boot to bootlader through adb then the unlock doesnt stick a lot of times. Its happened to me on my last two phones. If you werent using ADB and it still didnt stick, just keep trying, it will work. I found the solution in the unlock bootlader thread, after 20+ tries using adb to reboot. It worked first time when i bypassed ADB. i was scared, thought HTC blocked us lol. :fingers-crossed:
Click to expand...
Click to collapse
im going to try this right now
Got it!
if i boot to bootloader myself the script wont run it just hangs at restarting adb
Edit......fixed it.
Ok here's the deal. After my little experiance,had a lot of problems! Not sure what happened? But I'm not taking the risk again. I had to ruu again to get to stock, well after puting a new sim in....still fc's! Couldn't do anything with the device. So I took it in and got ANOTHER replacement, they said they have never seen anything like it?! Anyways... Mods please feel free to delete this thread! Thanks.
edit.......just so u all know this all started when trying to flash magnolia rom, i got the status 1 error, so i decided to try from cwmr touch. thats where the problem began!!!!!! so if i were users, i would stick with TWRP recovery!!!!
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
Guys, I really need help. My phone won't turn on after I installed Blackbean. Initially I was running Blackbean then I tried Jellybam then I decided to go back to Blackbean. After I reloaded the software, I've selected to go back to bootloader and then it won't turn on anymore. I am not sure if I bricked the phone coz I didn't do anything wrong. My phone is the unlocked T-Mobile Germany version. If anyone has suggestion please post it here. I will appreciate all the help. Thank you.
mjne_19 said:
Guys, I really need help. My phone won't turn on after I installed Blackbean. Initially I was running Blackbean then I tried Jellybam then I decided to go back to Blackbean. After I reloaded the software, I've selected to go back to bootloader and then it won't turn on anymore. I am not sure if I bricked the phone coz I didn't do anything wrong. My phone is the unlocked T-Mobile Germany version. If anyone has suggestion please post it here. I will appreciate all the help. Thank you.
Click to expand...
Click to collapse
Does your phone boot into recovery? if so then try restore a backup you may have.
fatpanda0 said:
Does your phone boot into recovery? if so then try restore a backup you may have.
Click to expand...
Click to collapse
thanks for the reply. to answer your question no sir. it wont turn on anymore.
So you can't even go into the bootloader? Maybe your battery has run flat, this happened to me once. I just plugged it in for a few minutes and it started up again normally.
Sent from my HTC One S running TrickDroid 4.0
dude you have to flash the kernel ( boot.img)! otherwise it won't boot!
Sent from my One V
But it must boot to bootloader to push the boot file right. How can he do that without getting the phone to turn on?
Sent from my HTC One S using xda app-developers app
fatpanda0 said:
But it must boot to bootloader to push the boot file right. How can he do that without getting the phone to turn on?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ya he just needs to charge it lol.
Darknites said:
Ya he just needs to charge it lol.
Click to expand...
Click to collapse
Plus if he already flashed those roms, would assume he is flashing boot, has low hboot, or using Flash Image GUI--may be wrong--
use the All in one tool kit and get the stock boot.img from kiln, assuming you're able to get into fastboot.