This morning I tried to install CyanogenMod 10.2 (stable) for my HTC One S. I followed the instructions over here:
wiki.cyanogenmod.org/w/Install_CM_for_ville
Things were going well, untill this part:
3 Boot to recovery mode on the device by holding With the device powered down, hold the Volume Down and Power buttons until HBOOT appears, then release the buttons. Navigate using the volume keys and select RECOVERY using the Power key..
4 Once the device boots into the ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm your selection, although for some devices the power button is used as a "back" button to go up one level, in which case the home button is used to confirm the selection.
First I had issues with the recovery mode. I got the red exclamation mark/triangle, meaning my HTC was in stock recovery mode. After following these instructions: theandroidroot.com/how-to-install-clockworkmod-custom-recovery-on-htc-one/
I succeeded (with the 6.0.4.6 version of this site: clockworkmod.com/rommanager])
I was also able to get to the CWM recovery mode, but when I tried to install zip from sdcard, the error appeared that sdcard0 was not mounted.
Fastboot is still working, but when I try to copy the zip file again with ADB I get the message that device is not found. With command ADB devices, the attached device list that is returned is empty.
I'm stuck now. I cannot copy the zip file with the ROM to my phone and again I'm having problems to get to CWM recovery mode (phone is in a boot loop with the HTC logo and the red text below when I start recovery mode from HBOOT). What do you recommend?
Just hold the power button for 10 sec and your phone will turn off.Then try again to get in recovery again with power+vol down.
Sent from my HTC One S using Tapatalk
b_ignatov said:
Just hold the power button for 10 sec and your phone will turn off.Then try again to get in recovery again with power+vol down.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Unfortunately that's not helping. I'm getting the screen with HTC logo and following red text:
This build is for development purposes only Do not distribut oustide of HTC without HTC's written permission etc.
After a while, screen turns black. I can go to fastboot/Hboot, but these are my only options apparently.
Hi, I had the same issue in hboot 2.16 because of recovery version (Unable to mount sdcard/adb didn't work and more issues)
Fixed it using openrecovery-twrp-2.6.1.0-ville
Try different versions of CWM/TWRP
Check the forum!!
There is a threat how to flash RUU via fastboot....but be careful if you don not want to brick your device.I'm pretty sure that your problem is well describe somewhere.
Sent from my HTC One S using Tapatalk
Thanks for your replies. Eventually I fixed it (with TWRP) and some searches through this forum. I had to erase all my data, but in the end the internal storage was available again and I flashed the Cyanogenmod succesfully
Can someone report this thread to get moved to q&a. I can't do so on mobile
Sent from my One S using Tapatalk
Thread moved to Q&A and requested.
Ghost
Related
I've got a curly one. I lost super user app so I was doing a restore through EXT4 boot as I have no working volume rocker.
The program got stuck and screen went black.
Upon restart , I get to the HTC screen of death and nothing else.
I cannot hold down volume and power button as volume button is shot.
Is there a way to connect through USB and fire up a recovery screen ?
i've got somewhat of the same issue - due to some water damage, my vol - button does not seem to function anymore. i would like to keep flashing ROMs, but am afraid of getting into a bootloop and not being able to access hboot. is there any way to bypass the vol- power button combo for getting into hboot?
I've got a faulty vol+ button here. No clue why.
ADB reboot recovery
My vol down is starting to go hmm I wonder what the fail rate is ? I smell a design flaw.
Sent from my Inspire 4G using XDA App
Did a lot of reading on ADB recovery ... Installed Android SDK and rebooted into recovery where I was able to do a reinstall off the SD Card.... Happy chap here .... Thanks all
Installing ROM Manager from the market will also allow you to reboot your phone to recovery.
Agoattamer said:
Installing ROM Manager from the market will also allow you to reboot your phone to recovery.
Click to expand...
Click to collapse
Yes but you have to be up and running to use it.
I use 4 ext boot which allows me to use recovery with out the need for a volume control. Just need power, menu and home . buttons.
RickEphraims said:
Yes but you have to be up and running to use it.
I use 4 ext boot which allows me to use recovery with out the need for a volume control. Just need power, menu and home . buttons.
Click to expand...
Click to collapse
4ext is based on cwm. Cwm can use the soft buttons too.
Sent from my Inspire 4G using Tapatalk
Hello all,
my sensation's volume rocker is faulty. By pressing volume down and power on, it will not boot into boot loader thus cannot enter recovery.
I know i can use software to boot into it boot loader but what if I am getting bootloops and unable to boot into rom?
Any ADB commands to make the phone boot into bootloader straight?
I am planning to flash the factory RUU and go claim my warranty after i get my Galaxy nexus..
mgear356 said:
Hello all,
my sensation's volume rocker is faulty. By pressing volume down and power on, it will not boot into boot loader thus cannot enter recovery.
I know i can use software to boot into it boot loader but what if I am getting bootloops and unable to boot into rom?
Any ADB commands to make the phone boot into bootloader straight?
I am planning to flash the factory RUU and go claim my warranty after i get my Galaxy nexus..
Click to expand...
Click to collapse
adb reboot recovery
or
adb reboot bootloader
or plain old
adb reboot
wmoore said:
adb reboot recovery
or
adb reboot bootloader
or plain old
adb reboot
Click to expand...
Click to collapse
thansk for your reply bro. but can this work if i am stuck in a bootloop ( before entering any rom)?
mgear356 said:
thansk for your reply bro. but can this work if i am stuck in a bootloop ( before entering any rom)?
Click to expand...
Click to collapse
Possibly not unless your timing is amazing!
Are you stuck in bootloops now or is this hypothetical?
Please, tell if your volumne rocker is so broken that it cant even turn up/turn down volumne during normal use of phone?
If it's ok, thet I suggest method of booting into recovery which I use (and i had problems to boot before - thought it's vol. rocker):
1. press volume down button and hold it!
2. press power button for 2-3 seconds and then release, still holding the volumne down
3. phone boots into recovery after few seconds.
Hope it might help you.
Decado_PL said:
Please, tell if your volumne rocker is so broken that it cant even turn up/turn down volumne during normal use of phone?
If it's ok, thet I suggest method of booting into recovery which I use (and i had problems to boot before - thought it's vol. rocker):
1. press volume down button and hold it!
2. press power button for 2-3 seconds and then release, still holding the volumne down
3. phone boots into recovery after few seconds.
Hope it might help you.
Click to expand...
Click to collapse
Implying he can't control volume in a bootloop, I seriously hope this guy uses 4EXT touch, or else he needs to replace the rocker.
Can you flash zips from USB fastboot?
Sent from my HTC Sensation using Forum Runner
I understood that he can't enter recovery due to some volume button fault. When you stuck in bootloop only thing you can do is pull out the battery, no keys/buttons are usable - tested myself :/
wmoore said:
Possibly not unless your timing is amazing!
Are you stuck in bootloops now or is this hypothetical?
Click to expand...
Click to collapse
not really hypothetical.. in fact i experienced it earlier..
my volume up/down seems to have a mind of his own and at times i will enter "safe mode"
thereafter it will auto reboot unless i am quick enough to do a factory wipe under settings... it will still boot into safe mode but wont auto reboot.
so after knocking a few times on the volume rocker, i am able to boot into normal mode but the volume rocker isnt working. Pressing it once, will cause to decrease the volume and switch to silent mode.
Decado_PL said:
I understood that he can't enter recovery due to some volume button fault. When you stuck in bootloop only thing you can do is pull out the battery, no keys/buttons are usable - tested myself :/
Click to expand...
Click to collapse
lol this sux man..
I dunno if HTC singapore will honor the warranty cause this is a hardware defect and nothing to do with any rom or unlock..
Even in bootloader mode, press up will cause it to go down or at times up. pressing down may or may not respond.
If you in a boot loop adb should see it for split couple seconds so with the phone connected I would keep trying to do adb reboot recovery
Sent from my HTC Sensation using xda premium
Smokuevo said:
If you in a boot loop adb should see it for split couple seconds so with the phone connected I would keep trying to do adb reboot recovery
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
That's what I thought but it didn't happen when I tried it on mine.
From Fastboot, adb commands also work, provided vol - works while powering on. This sucks dude, sorry.
Sent from my HTC Sensation 4G XE with Beats Audio using xda premium
If you have CWM recovery installed (im not sure about other recoverys), you can connect your phone to your computer when it's off and you will have access to a limited adb provided by CWM. You can then use the command "adb reboot recovery" or "adb reboot bootloader" or whatever to do what you need to do.
Wipe all then cant boot into bootloader
Hi, i'm really sorry to bring back this post,
your fear had become my nightmare in reality.
The volume button was somehow (either physically spoil or is not capture click)
during booting process.
I have completely forgotten about it, and do complete wipe
(select wipe all except sdcard in touch recovery).
So, now the phone is completely clean (without rom)
and i'm unable to trigger bootloader/recovery via pwr/vol down button.
I have try take out battery,leave it for 10min and try press
all those button without casing/rocker;
press & hold vol down, den plug in battery;
and press both vol up & down then only pwr button.
The phone now (i assume) boot normally,
stop at HTC logo because there is no rom inside
(just like normal pc boot pass bios but cant find OS).
ironically, i live at singapore too... haha...
---------- Post added at 10:58 PM ---------- Previous post was at 10:51 PM ----------
I read somewhere that the person use pin to press the button really hard
and it manage to go into bootloader
(but I cant find back that post now)
Searching in forum recommend me to peel off the
volume button cover n use pin to press on it directly
(which I do not dare )
So now I sent it to repair shop,
hopefully that person using either g-box or gmbox
(flash box start with G) and can push RUU inside.
God bless me.
p/s : Sorry I should post in Q&A...
Get the phone off. Pull the battery and re-insert. Open fastboot
Fastboot reboot-bootloader
And if you want to flash a ruu directly:
Fastboot erase cache
Fastboot oem rebootRUU
And then flash the ruu
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk
dexter93 said:
Get the phone off. Pull the battery and re-insert. Open fastboot
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Hi, can you tell me exactly step by step how to open fastboot?
pull out the battery, press vol down (??), reinsert?
fastboot devices go no response after booted and halt at htc logo.
Thank you very much.
Have you tried finding where the rocker lines up with the buttons on the phone, and just used the buttons without the back attached?
Sent from my Sensation using XDA
apow12348 said:
Hi, can you tell me exactly step by step how to open fastboot?
pull out the battery, press vol down (??), reinsert?
fastboot devices go no response after booted and halt at htc logo.
Thank you very much.
Click to expand...
Click to collapse
Did I tell you to power it on?
Just shut it down completely(hence battery pull ) and plug it in USB. Use google to get to know how to use fastboot and try with the commands I wrote above. simple as that
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk
Sensation-al! said:
Have you tried finding where the rocket lines up with the buttons on the phone, and just used the buttons without the back attached?
Click to expand...
Click to collapse
Yup, that is what I did all this while, and no success.
dexter93 said:
Did I tell you to power it on?
Just shut it down completely(hence battery pull ) and plug it in USB. Use google to get to know how to use fastboot and try with the commands I wrote above. simple as that
Click to expand...
Click to collapse
Sorry, I always thought that in order to use fastboot usb you must in bootloader already. Will try to search more. Thank in advance.
RECOVERY AND BOOTLOADER (ubislate 7 by datawind }
hi ,i have an old datawind tablet which runs on andorid froyo with kernel version 2.6.32.6 developer @developer#206
android version 2.2.2
model number NASHOBA NORDICA
can anybody please tell me how to enter bootloader in this particular version and also the rooting methods available
please note that this device lacks any physical volume up or down buttons as well as does not provide any adb support
this is a resistive touchscreen model
processor arm 11 366mhz
with conexant hd co processors
screen resolution 640*800
this device very easily overheats ]
battery lithium ion 2100 mah
i am also unable to play any vidoes on this device
ram 256
this device supports SD CARDS and full sized usb 2.0 ports
no hdmi output also
i any body can help me
please do as so
thanks in advance
I recently flashed a Paranoid ROM (nightly build v1.991, Aug 21) downloaded using GooManager.
All worked fine initially, until recently the power button stopped responding/working.
I tried rebooting the phone by taking the battery out (I did not have to press power button, since it auto-starts), but it did not help.
I could enter the fastboot mode while rebooting by pressing Power button + Volume up button.
However in fastboot mode, the volume rockers (which work everywhere else, eg: recovery) along with power button, were not responding , also "fastboot devices" command did not recognize any device.
Now, to re-flash the Paranoid ROM or a stable ROM, I needed the power button in CW Recovery.
So I was left with a single option of flashing the Touch-CW recovery without fastboot mode.
I managed to do that using Terminal app (the one that opens the shell from the underlying kernel) from the ROM itself.
Now I could flash ROM using the Touch-CW recovery.
I tried re-flashing the Paranoid ROM, flashing a stable CM ROM but none helped.
Latter, I tried various drivers (PDAnet, Samsung, raw adb drivers from Android SDK) and toolkits to get the fastboot mode working but to no avail.
Note: The "adb" commands work correctly when the Nexus S is connected in USB debugging mode.
But no matter what the fastboot mode and the power button do not work!
Please help!
Details of device:
Nexus S, I9023, (SLCD version).
Kernel: 3.0.38-CyanogenMod
Jelly Bean v4.1.1,
Paranoid Android v1.991.
Update 1:
Recently I have updated to paranoid 2.0 (September 7) build. The problem still persists.
Update 2:
Nexus S has been bricked, I suppose!
It now does not start and gives no response to pressing of any combination of the keys(hard and soft).
bitflipster said:
I recently flashed a Paranoid ROM (nightly build v1.991, Aug 21) downloaded using GooManager.
All worked fine initially, until recently the power button stopped responding/working.
I tried rebooting the phone by taking the battery out (I did not have to press power button, since it auto-starts), but it did not help.
I could enter the fastboot mode while rebooting by pressing Power button + Volume up button.
However in fastboot mode, the volume rockers (which work everywhere else, eg: recovery) along with power button, were not responding , also "fastboot devices" command did not recognize any device.
Now, to re-flash the Paranoid ROM or a stable ROM, I needed the power button in CW Recovery.
So I was left with a single option of flashing the Touch-CW recovery without fastboot mode.
I managed to do that using Terminal app (the one that opens the shell from the underlying kernel) from the ROM itself.
Now I could flash ROM using the Touch-CW recovery.
I tried re-flashing the Paranoid ROM, flashing a stable CM ROM but none helped.
Latter, I tried various drivers (PDAnet, Samsung, raw adb drivers from Android SDK) and toolkits to get the fastboot mode working but to no avail.
Note: The "adb" commands work correctly when the Nexus S is connected in USB debugging mode.
But no matter what the fastboot mode and the power button do not work!
Please help!
Details of device:
Nexus S, I9023, (SLCD version).
Kernel: 3.0.38-CyanogenMod
Jelly Bean v4.1.1,
Paranoid Android v1.991.
Click to expand...
Click to collapse
That's normal, because your power button is broken, that has nothing to do with the ROM. If you take a moment and search the web you'll see it's a very common problem for Nexus S.
Send your phone for repair if it's under warranty or if you're ready to afford the repair from Samsung. Otherwise you can fix it yourself if you have experience with small electronics, although I would advise against it.
Thanks for the quick reply. However, I'm able to start the phone in fast boot mode by holding down the power and volume buttons.
Also, any thoughts about the buttons not working in fastboot mode?
Sent from my Nexus S using xda app-developers app
bitflipster said:
Thanks for the quick reply. However, I'm able to start the phone in fast boot mode by holding down the power and volume buttons.
Also, any thoughts about the buttons not working in fastboot mode?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Again, known problem. With a quick search you're able to find answers to these questions.
Whenever the power button breaks, often enough it will stay stuck as pressed in thus activated. Fastboot can only react to one button press at a time thus will act as if the power button was being held. The volume rocker will not be able to work as long as the power button is "held". And since it's broke, it's continually held, so you can't scroll.
You can technically and in practice live with the power button not working. Many people manage to do so.
-From within Android, you can reboot to recovery using either an app or an embedded menu in many custom roms. Using a touch recovery such as CWM 6.0.1.0 or 5.8.0.2 you can use it without any problem.
-To wake up your phone from sleep you can use volume rocker wake embedded in some custom roms.
-To put it to sleep you can use shortcut apps/widgets, a notification bar shortcut, let the timeout do it's work or use a proximity/light sensor app.
Thank you once more.
I am already doing well without the power button, by using volume rocket to switch on the display and touch CW recovery.
To clarify that power button is functional, I tried to enter fast boot mode by only holding down the volume up key, but couldn't enter it as power button was not pressed.
Also the volume rockers work properly in recovery, hence if the power button was continuously being pressed , they would malfunction.
Sent from my Nexus S using xda app-developers app
bitflipster said:
Thank you once more.
I am already doing well without the power button, by using volume rocket to switch on the display and touch CW recovery.
To clarify that power button is functional, I tried to enter fast boot mode by only holding down the volume up key, but couldn't enter it as power button was not pressed.
Also the volume rockers work properly in recovery, hence if the power button was continuously being pressed , they would malfunction.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Does it work properly EVERY time (and I mean that) while in Android?
Fastboot and recovery are different beasts though. I've not heard of problems in recovery when the power button was stuck, unlike fastboot.
It's possible your power button hasn't failed you completely yet. They tend to be flaky at first then one day just out right stop working. Sims22 on these boards has one that works if he smacks his phone a bit, to give you an example.
yeah they work every time as I described.
Actually I'm trying to put back stock ROM in it , with stock kernel and everything else stock.
Sent from my Nexus S using xda app-developers app
I'm also having this issue. I'm able to get into boot loader. But volume cursor doesn't seem to work. It how ever works fine however in another other time.
I want to Odin. Since I restores everything completely to stock. How ever I cannot get into download mode at all. Tried adb. Different apps. And hold volume up/down while plugging USB
Sent from my iPad using Tapatalk
BuLLeT_PrOOf_wAlleTz said:
I'm also having this issue. I'm able to get into boot loader. But volume cursor doesn't seem to work. It how ever works fine however in another other time.
I want to Odin. Since I restores everything completely to stock. How ever I cannot get into download mode at all. Tried adb. Different apps. And hold volume up/down while plugging USB
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I also tried ODIN and Nexus Root Toolkit. But was locked in fast boot mode. Then I pulled off the battery to reboot, and that was the last time the Nexus worked.
I recently opened up the nexus to verify that the power button is functional, it is working correctly.
I guess time for the Samsung service center guys to work on it.
Sent from my Galaxy Nexus using xda app-developers app
Hey guys! I just got a One X from AT&T bought on eBay, although I live in Europe.
I managed to unlock the bootloader by changing the CID to 1111111 etc. (how many 1's?) and it worked fine.
I then ran installed ClockworkMod Touch Recovery for the HTC One X through terminal and it was a success.
I rebooted by holding down the power and volume down, and attempted to boot into recovery. I got a white screen with the HTC logo, and red text underneath saying something like "do not use this without HTCs permission" or something of the sort. The phone then turned off.
NOW I'm trying to boot again into the bootloader (I think that's what it's called, but by turning it off and holding the volume down and power key) and it just doesn't work. I've tried a million times, with different variations of holding down the keys. What happens is the light on the touch keys at the bottom flashes a bunch of times, then it boots normally. Everything works on the phone otherwise.
I tried to do it via fastboot/terminal by issuing the command ./fastboot-mac reboot-bootloader but it just says "waiting for device..." even though it's connected.
Anyone had this problem and found a solution?
Recovery
Clockwork recovery is not supported on the evita. Download goo manager and you should be able TWRP from that. And then you can reboot into TWRP.
I think you flashed CWM for the international (Tegra3 quad core) One X. Install TWRP as previous poster recommended.
There is no version of CWM Touch Recovery that is supported for the AT&T One X. You flashed the international version. Fortunately, you can flash TWRP right over it inside Goo Manager.
Be thankful you didn't flash it inside ROM Manager or you could have bricked your phone. I've seen people do it in the past.
ansedve season
Thanks guys, and glad I didn't brick the phone!
I installed Goo Manager and installed OpenRecovery Script, and managed to attempt to go into recovery, but again got the white HTC screen and something about "development purposes only" in red text.
I think I'm really lost on this one, any help would be great, like a link to a tutorial?
in fastboot run this command "fastboot erase cache", then boot into recovery.
DvineLord said:
in fastboot run this command "fastboot erase cache", then boot into recovery.
Click to expand...
Click to collapse
Don't be too concerned with the blah blah in red writing about development version etc. on the boot screen - you get that boot screen when you unlock the bootloader.
mollysue said:
Thanks guys, and glad I didn't brick the phone!
I installed Goo Manager and installed OpenRecovery Script, and managed to attempt to go into recovery, but again got the white HTC screen and something about "development purposes only" in red text.
I think I'm really lost on this one, any help would be great, like a link to a tutorial?
Click to expand...
Click to collapse
What did you do in recovery? Did you flash anything? Does the phone not boot up now?
Thanks guys for all your help. I guess know I technically know what to do to fix things, thanks to you. The only problem that after probably over 100 failed attempts I cannot boot into recovery. I tried all variations of holding the power and volume down button while restarting, rebooting, turning on/off or up/down sideways but it just boots normally every time.
This means I can't use fastboot etc. I guess unlocking the bootloader and voiding the warranty was for nothing
If you know another way to reboot into bootloader other than the hardware buttons method let me know!
Believe it or not, I think you are just performing the button presses incorrectly, if you can't access the bootloader. Bootloader is probably still intact, otherwise the phone would not be working at all.
1) In Settings>Power, make sure "fast boot" is not checked.
2) Then power the phone off fully, but holding the power button until the power menu comes up, and select "Power off". Wait a minute for the phone to power off completely.
3) Hold down the volume down rocker. DO NOT release it until I tell you to later.
4) Press the power button for 3 seconds, then release. DO NOT release the volume down rocker.
5) Once the white bootloader screen shows up, release the volume down rocker.
Alternately, you can do this:
a) With the phone powered on, hold the power button until the capacitive buttons flash (about 5 seconds).
b) The moment the screen goes black, hold down the volume down rocker, (again, DO NOT release it until the bootloader screen comes up) but release the power button.
The timing for this method is a little trickier, if you press the volume down rocker too late, it will boot normally (or safe mode), and too soon, and it just reduces the ringer volume and the phone stays on. But as long as you press and hold volume down the moment the screen goes black, it will work.
---------- Post added at 10:13 AM ---------- Previous post was at 10:11 AM ----------
But also, I would still not recommend trying to boot into recovery until you have installed the TWRP recovery as mentioned previously on this thread, if you have not done so already. There is no CWM Touch Recovery for this phone, so I'm pretty certain you installed in improper recovery on the phone, and recovery will not function at all.
Alternatively, you can go into Goo Manager and select the "Reboot Recovery" option, which should get you into TWRP
Or from command prompt "adb reboot bootloader" so long as you open your prompt from your adb application folder.
Or alternatively skip the middle man: "adb reboot recovery"
I really think your problem lies with your button pressing -- follow instructions on the previous post and you should be home free.
Well I actually eventually managed it! I think the volume button was a bit stuck because it still takes a few tries to boot into bootloader, but eventually I managed it and am in the TWRP menu right now!
I did a little victory dance when it happened. Thanks again!
I just rooted my One S using this thread: http://forum.xda-developers.com/showthread.php?t=2008440. I flashed Clockworkmod touch recovery and installed the latest CM10 Nightly. I ended up installing the standard Clockworkmod recovery (non touch) through ROM manager once my phone was up and running. Everything on my phone was working great until I let my battery run all the way down to the point my phone shut off. I plugged my phone in and it automatically booted to recovery. I waited a little bit for the phone to charge and selected "reboot system now" from recovery. My phone did not boot and only goes to recovery. When it reboots, it briefly flashes a green stripe twice in the upper third of the screen prior to booting all the way but never shows the HTC screen or anything other than recovery. I tried reflashing the ROM in recovery, formatting every partition in recovery, entering fasboot using ADB, rebooting using ADB, and nothing seems to get my phone to do anything other than boot to recovery. I tried running the latest RUU and it fails (presumably because it can't enter fasboot). I tried pressing and holding volume+, -, and the power button at the same time, I tried holding just the volume down button while holding the power button, but no luck so far.
Is there a way to reflash the recovery from ADB while the phone is in recovery? Is there any other way I can force my phone into fastboot? Can I safely use the method in this thread http://forum.xda-developers.com/showthread.php?t=1990043 to "unbrick" my phone by entering commands via ADB shell while in recovery rather than in terminal emulator? Thanks in advance for all the collective XDA wisdom that I'm sure will help get my phone back up and running.
Hey I had the same problem about a week ago. Are you sure you used the latest the RUU file?
chilaca91 said:
Hey I had the same problem about a week ago. Are you sure you used the latest the RUU file?
Click to expand...
Click to collapse
I'm using RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe. I don't think it would matter which one I used though because it gives me an error that says it can't connect to the phone.
Try holding down the power button for 10 sec and then let go of the power and hold down the volume button. I had to do this a couple of times until I finally got into the bootloader
Sent from my One S using xda app-developers app
chilaca91 said:
Try holding down the power button for 10 sec and then let go of the power and hold down the volume button. I had to do this a couple of times until I finally got into the bootloader
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Amazing! That did the trick. Thanks a ton for that info. I knew it would be something simple.
I also had a similar problem. Seemed to occur only when I had the USB cable plugged into the phone. Once I removed it, I could then get into fastboot. Once I was in fastboot, I simply plugged the USB cable back in, and everything worked flawlessly.
All that crap you got wouldn't have happened if you use TWRP instead of CWM.