Related
So here is what I did... Last night i successfully unlocked my bootloader on my AT&T HTC Onc X and established root. I was running the AT&T RUU_Evita_UL_Cingular_US-1.82.502. I then tried to update this morning to AT&T RUU_Evita_UL_Cingular_US-1.85.502(desktop installer type) it kept giving me errors and would not complete. Like an idiot i tried to flash CleanROM 2.0 -★| 1.85.502.3 | Tweaked! | Stable! | CWM Install! through CWM and it installed successfully but my WIFI would not work at all. So i decided to reload CleanROM DE 1.0 -★| which had worked fin in the past. At the end of the installer it said to do a factory reset and I did. After the reboot is where i noticed my problem. I am stuck on the boot animation screen. Not able to get into the phone at all now. I am able to get back to the bootloader menu.. boot into CWM but unable to reflash the room on the sdcard. It will not mount USB storage. None of the stock desktop installer will recognize my device is plugged in....... ANY SUGGETIONS...or am I screwed....
Is it in a boot loop or is it frozen on the HTC One screen? That happened to me last night but I was able to run the RUU installer. Did you make sure HTC Sync wasn't running, and that you killed adb by using adb kill-server before trying the RUU installer?
Apologies if you've done these things already, I'm just grasping at straws here.
If you can do adb reboot bootloader, you should be able to run the RUU installer from there, no?
it does not show the ONE X boot screen. Its shows i guess what is known as the Galaxy Nexus boot screen that just flashes the colorful boxes over and over the longest i let it go for was like 20 minutes. The RUU installer you talk about, is that the one that you run from ur desktop. If so how do i get it to recognize my device is even plugged in. I have tried it while it is on the boot animation screen and from the bootloader menu. At this point it just seems like I dont have a way to get my computer to detect my device is plugged in. Is there a way to do that from the Bootloader menu?
taterdog2 said:
it does not show the ONE X boot screen. Its shows i guess what is known as the Galaxy Nexus boot screen that just flashes the colorful boxes over and over the longest i let it go for was like 20 minutes. The RUU installer you talk about, is that the one that you run from ur desktop. If so how do i get it to recognize my device is even plugged in. I have tried it while it is on the boot animation screen and from the bootloader menu. At this point it just seems like I dont have a way to get my computer to detect my device is plugged in. Is there a way to do that from the Bootloader menu?
Click to expand...
Click to collapse
If you have adb on your computer (from the Android SDK) and the drivers installed, you should be able to access the device from fastboot (bootloader). RUU will work if you can get your device into fastboot. I'm doing it right now (I wanted to try it before telling you).
Just remember, if you were on an unlocked 1.82 when you borked it, you need to be locked again before you can use RUU. Just use fastboot oem lock from the command prompt.
If you can get to the bootloader screen you are not bricked. Why can't you run the RUU like normal from there? Just re-lock your bootloader first.
Poster above beat me to it while I was taking forever to post.
1. Hold down your Volume Down Button and your power button
2. Wait for the device to turn off and keep holding the combination until you boot into the bootloader (It might take a couple tries, don't give up)
3. Plug your device into your computer via the OEM USB Cable
4. Use the Volume Up/Down keys and the Power button to select the Fastboot Option
5. Wait till the device is recognized (The text on screen where it said Fastboot should become Fastboot USB)
6. Go to the folder where you have fastboot installed and type:
fastboot oem lock
7. Go back to the bootloader and into fastboot when its done with relocking. Make sure the text on the top of the screen says "Relocked" or "Locked" (under the Tampered flag)
8. Run the RUU while in fastboot mode. Use version 1.85.
I sorry for being a NOOB... step 6. Go to the folder where you have fastboot installed and type:
fastboot oem lock...
when you refer to "having fastboot installed" I am taking it that you are not refering to the RUU installer... where do I get this FASTBOOT file from to install?
I think I figured it out... will let yall know in a few minutes
I looks to be that the 1.85 RUU is flashing properly... do I use the same method that I originally used to unlock the bootloader again?
taterdog2 said:
I looks to be that the 1.85 RUU is flashing properly... do I use the same method that I originally used to unlock the bootloader again?
Click to expand...
Click to collapse
Yes. You may need another unlock code. I did, but other people didn't. They just tried several times until it worked.
jmattp said:
Yes. You may need another unlock code. I did, but other people didn't. They just tried several times until it worked.
Click to expand...
Click to collapse
how u get unlock code again....i believe htcdev asking token right...? how do i get token back...? last time i try before one click came up device not found....kinda mess up my adb...? any link to re DL adb or android sdk platform tool again...thanks in ADV
ted77usa said:
how u get unlock code again....i believe htcdev asking token right...? how do i get token back...? last time i try before one click came up device not found....kinda mess up my adb...? any link to re DL adb or android sdk platform tool again...thanks in ADV
Click to expand...
Click to collapse
If you got device not found, you might not have USB Debugging enabled.
I don't think it's possible for something to "mess up" adb. For the Android SDK, just Google it.
When you run the one click CID tool again, just go through it all the exact way you did the first time.
I just spend about four hours on here answering questions and uploading mods. I'm going to take a shower and enjoy the rest of my Saturday. Good luck.
jmattp said:
If you got device not found, you might not have USB Debugging enabled.
I don't think it's possible for something to "mess up" adb. For the Android SDK, just Google it.
When you run the one click CID tool again, just go through it all the exact way you did the first time.
I just spend about four hours on here answering questions and uploading mods. I'm going to take a shower and enjoy the rest of my Saturday. Good luck.
Click to expand...
Click to collapse
so one click unlock bootloader tool work on 1.85 base from designgears that post by Kpenn.....? did u trying using that also...? ENJOY YOUR SAT....HAVE A NICE LONG WEEKEND....HAPPY MEMORIAL DAY...
ted77usa said:
so one click unlock bootloader tool work on 1.85 base from designgears that post by Kpenn.....? did u trying using that also...? ENJOY YOUR SAT....HAVE A NICE LONG WEEKEND....HAPPY MEMORIAL DAY...
Click to expand...
Click to collapse
I think as long as you're relocked, not factory locked (meaning, you unlocked 1.82 and then locked it again) you should be able to use the one click tool again. That's how I did it.
jmattp said:
I think as long as you're relocked, not factory locked (meaning, you unlocked 1.82 and then locked it again) you should be able to use the one click tool again. That's how I did it.
Click to expand...
Click to collapse
assuming it work how u get CWM recovery....are u using one click tool also...? and how u re-root....? are u flashing paulobrien superSU script from recovery?
ted77usa said:
assuming it work how u get CWM recovery....are u using one click tool also...? and how u re-root....? are u flashing paulobrien superSU script from recovery?
Click to expand...
Click to collapse
Once you unlock your bootloader on 1.85 you will not need root to flash CWM Recovery
Ok guys, so here's the problem. my HOX (rogers) is bricked because of what i assume is a bad rom install. I am a noob, I just wanted jellybean and did some things, bricked my phone and here i am. anyone (first person) who is able to un-brick this thing will get $50 in their paypal account WITHIN THE SAME MINUTE - i swear by it. please, i just want my phone back.
So, the steps I took were:
1. downloaded a rom and jb package from http://forum.xda-developers.com/showthread.php?t=1790032
2. transferred the roms onto my computer (am overseas atm, at a coffee shop writing this)
3. did a twrp recovery, transferred the recovery files onto my comp
4. did the factory reset option (wiped data, SD and cache via twrp)
5. rebooted, did transfer of above mentioned files (the rom, jb apps package and recovery of data and system)
6. booted into twrp, flashed the rom and jb apps package (should have rebooted first and then twrp-ed i know)
7. booted; IT WASNT WORKING (i know it was alpha, but i mean constant "phone stopped working" and "messages stopped working?" no one else had that problem...)
8. SO... i said to hell with jellybean and rebooted into twrp, installed the system recovery package i had on twrp (probably where i went wrong...)
9. BIG PROBLEM. the phone won't boot. It's stuck on the HTC logo with just the message "this build is for developer purposes" &c.
10. I go into TWRP and the SD card won't even mount.
I'm on TWRP v2.1.7 atm... and i mean, it really is bricked. I can load into bootloader, and when I plug it into the comp it says fastboot usb instead of fastboot so i know it recognizes being plugged in (maybe it's just recognizing the charge influx?) but when i DO plug it in, it wont show up on my computer as anything. before on jellybean i would try to mount to disk drive and the computer would say something along the lines of driver installation failed or something...
and last resort - would... rogers honor the one-year warranty i have on this? I lost the receipt (stupid i know) but i have the warranty information provided in the box back at home. Rogers still has my customer information and I have many forms of ID to verify that it IS me... and it would be financially beneficial to them to honor the warranty, as if they don't, I'll just cancel my contract and move to another carrier out of spite. The guy that works there probably still does, and should remember me (we had an extended conversation about something i don't quite remember)... what's your two cents on that? Rogers is notorious for being crappy with customer service but eh... worth a shot right?
Anyways... I'd really appreciate it if anyone can give me any information on salvaging this bricked phone. i mean, I said 50 bucks but im willing to negotiate.
Thanks, and I'll be waiting for a speedy reply
The easiest solution would be to download a Rogers RUU from the Evita Shipped Rom thread boot into bootloader then fastboot connect phone then type fastboot devices to make sure it comes up then fastboot oem lock then run the RUU.
Sure you'll have to root and unlock again but you'll get your phone back.
Sent from my HTC One XL
since u r a rogers user u probably a canadian...add me on gtalk..
i will try to help [email protected]
but first.just.to make sure urs is rogers htc one x right not.the international.one.right？
Sent from my HTC One X using xda app-developers app
I once saw sd not mounting. Only fix was to force a shutdown. Hold the power button for 5-10 seconds, you should see the bottom touch buttons flash just prior to it fully turning off.
Push and hold down vol prior to releasing power button and hold while the phone boots.
Hope it boots to recovery again but with sd card access. If not rinse and repeat a few times until it does work.
Personally from fastboot I wouldnt switch to recovery, but instead I would install a ruu.
Sent from my HTC One XL using xda app-developers app
I would try reflashing recovery from fast boot first...and see if you can get back in.
If not fast boot OEM lock and ruu as stated. Certainly not bricked if u have fast boot.
Also if Canadian you can add me on gtalk as well. [email protected] , niceppl you can add me too u lucky soff canuck.
Sent from my One X using xda premium
Fix
First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the RUU without any issues.
Now find your ruu here http://forum.xda-developers.com/showthread.php?t=1671237
Once you've finished upgrading your ruu you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin' (I've heard reports of some people having to type this command two or three times for it to work but it went the first time for me)
Hope this helps ^____^
I bought a HTC One S for T-Mobile USA. Has been working flawlessly. Today I got an OTA and my world is now upside down. I have spent 5 hours trying countless things to get my phone back up to no avail.
my phone stats:
hboot 1.09.0000
radio 0.16.31501s.16_2
open dsp-v28.1.0.32.0504
emmc-boot apr 2 2012,21:08:24
UNLOCKED
TAMPERED
How do I get back to square one and turn this phone back into something usable?
It has something called TWRP 2.1.7 installed on it and I have tried fastboot and a host of other things to remove it. I have even tried the thread on sending your phone back to stock but I can't access RUU because it won't load the driver. I have never rooted this phone nor do I believe USB Debugging was turned on before I accepted the OTA. I can communicate via fastboot in the command shell via a usb cable. The PC wont mound the SD card so I can't copy a new image and reboot this thing on a different rom and then send it back to stock.
I am about ready to throw it away because i can't seem to get a .zip file to it so it will run again (for putting a working build on it). There are no images to boot to. Somehow that got wiped and no backup was done. I don't give a poop if the data is whiped. Its all backed up via dropbox and exchange. I just want it up and running so i can use RUU and send it back to stock.
Any help would be appreciated.
Scuba_Luv said:
I bought a HTC One S for T-Mobile USA. Has been working flawlessly. Today I got an OTA and my world is now upside down. I have spent 5 hours trying countless things to get my phone back up to no avail.
my phone stats:
hboot 1.09.0000
radio 0.16.31501s.16_2
open dsp-v28.1.0.32.0504
emmc-boot apr 2 2012,21:08:24
UNLOCKED
TAMPERED
How do I get back to square one and turn this phone back into something usable?
It has something called TWRP 2.1.7 installed on it and I have tried fastboot and a host of other things to remove it. I have even tried the thread on sending your phone back to stock but I can't access RUU because it won't load the driver. I have never rooted this phone nor do I believe USB Debugging was turned on before I accepted the OTA. I can communicate via fastboot in the command shell via a usb cable. The PC wont mound the SD card so I can't copy a new image and reboot this thing on a different rom and then send it back to stock.
I am about ready to throw it away because i can't seem to get a .zip file to it so it will run again (for putting a working build on it). There are no images to boot to. Somehow that got wiped and no backup was done. I don't give a poop if the data is whiped. Its all backed up via dropbox and exchange. I just want it up and running so i can use RUU and send it back to stock.
Any help would be appreciated.
Click to expand...
Click to collapse
I hate to tell you this but if you never unlocked or rooted your phone, somebody did. Your device is unlocked and running a custom recovery therefore you cannot accept over the air updates and that is your problem. You did not buy your phone that way from T-Mobile so what did you really do to get to this point?
Behold_this said:
I hate to tell you this but if you never unlocked and rooted your phone, somebody did. Your device is unlocked and running a custom recovery therefore you cannot accept over the air updates and that is your problem. You did not buy your phone that way from T-Mobile so what did you really do to get to this point?
Click to expand...
Click to collapse
I never said I bought it as OEM. I also never thought to ask the guy I got it from if he rooted it or unlocked it.
Relocking the boot loader then running an RUU should fix the issue. Once you do that enter the recovery and wipe everything/factory reset.
Then if you are trying to run a custom ROM you should be able to mount your SD card and push one to the phone.
Sent from my HTC One S using xda premium
beats4x said:
Relocking the boot loader then running an RUU should fix the issue. Once you do that enter the recovery and wipe everything/factory reset.
Then if you are trying to run a custom ROM you should be able to mount your SD card and push one to the phone.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Great reply however I am short on knowledge on how to do what you have recommended. I don't know how to relock the boot loader nor can I run RUU because I can't get the driver installed. Any help would be awesome. Thank in advance. Sorry I'm a noob at this.
In the dev section there is an all in one toolkit that will execute the correct scripts for you. Download it, then run it. You may also need the HTC sync drivers installed on your computer.
Once you see that the bootloader is locked run the ruu.
And don't apologize for being a noob, I am too lol. We all need help to get started.
Sent from my HTC One S using xda premium
If you install HTC sync to your pc it should install the driver's you need. Then install the one s tool kit in developers section to relock. Then run ruu.
Also, anything you see in blue text is what you'll need to type, or copy/paste, to avoid any quote confusion.
Files You Need:
T-Mobile USA RUU file (mirror) - it's about 563 mb, and worth saving once you download it.
Extremely Important: If you're on another carrier you'll need a different RUU file - DO NOT try and run this RUU file, it could really screw you up. Go to this link to find the right RUU file.
HTC Drivers (mirror) - You probably already have the drivers installed if you're needing this thread, but just in case...
ADB / Fastboot (mirror) - same as the drivers, but again, just in case...
Initial Setup:
Again, some of this might be redundant as you might already have this setup if you rooted/unlocked.
Install the HTC drivers if you haven't already
Unzip the adbfastboot.zip file to your desktop (anywhere, but I find it easiest to get to it on the desktop for my habits)
Getting into the bootloader (hboot):
If you're stuck in a boot loop, pull the batt... oh wait, we can't do that here. To perform a hard reset, hold down the power button for 10 seconds - in the process you'll see the softkeys start blinking, then it should reset. As soon as it starts to reset, release power, and hold down the volume-down button - hold it until hboot pops up (white screen, colored text).
If you're phone is fully powered off (make sure "fastboot" is disabled - settings > power), hold the volume-down key and while holding it, press and hold power for a few seconds. You can probably release the power button, just make sure you keep holding volume-down - after probably 3-5 seconds (maybe a bit more), hboot should come up.
If the phone is on and you're plugged in to your computer, make sure "usb debugging is enabled" (settings > developer options), shift+right-click the adbfastboot directory on your desktop (or wherever you put it), choose "open command window here", and in the prompt that comes up, input adb reboot bootloader.
Restoring:
Once you're in hboot, make sure you select Fastboot (if you don't see it, you're in Fastboot already). In the command prompt referenced above, input fastboot oem lock. This will relock your bootloader in order to allow the RUU to run. Historically this has been necessary for an RUU to run, but I haven't actually tested it without relocking on the One S, and assumed based on previous HTC devices that this would continue to be the case. Edit: thanks rbrookstx for confirming that re-locking is necessary
Your phone will reboot when it relocks - follow the steps above to get back into hboot.
Once you're back in hboot, make sure you're in Fastboot, and open / run the RUU file. It'll go through some initial prompts, then it should start. It takes about 10-15 minutes, maybe less, depending on your computer.
Once it's done, it'll simply go back into hboot - reboot, and you're good to go.
A couple of notes:
When you unlocked and flashed a custom recovery (if you did that), hboot probably said "tampered with" and when it booted up, it probably had a red message under the "HTC" logo about being a developer only device. That should be gone now. It should boot up clean, and hboot should simply say "relocked", with no tampered message.
Until a better solution comes out, once you unlock the bootloader with HTC's official method, it can never be locked the way it was from the factory. "Relocked" is the best you can do.
Click to expand...
Click to collapse
This is what worked. I had to search the internet for this stuff but the HTC driver, the fast boot and the RUU with a matching or higher radio number all made it work out.
Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?
Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .
As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know
Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk
Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!
nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.
Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2
Hi everyone,
I am trying to help a buddy out and getting his phone working. The phone is not rooted in any way shape or form.
Here are my issues
The phone will not boot into the stock rom. I can get it into the bootloader. Which I went to htcdev. To unlock the bootloader. Followed the steps and was able to get the phone screen to show unlock bootloader. But when I hit yes it reboots and stays on the white htc screen. Then it will keep rebooting. When I go back into bootloader. It still shows the bootloader as being locked? Any suggestions. I haven't flashed anything in about 3 years. But only Samsung things.
This is my set up
Your best bet is to try latest RUU: http://www.htc.com/us/support/htc-one-sv-boost/news/
I tryed that as well. Thinking it is kinda like Odin for samsungs. But as soon as it try to reboot into bootloader. It stays on the white htc screen
The RUU was running completely through and it still not booting?
I will take a picture of the screen. It does not go all the way through. Also I tryed the Ota. Zip. And changed it to PL80IMG and placed it in my SD card. It looked as if it went through and it told me to reboot. But still nothing.
This is what's happening.
Forget the OTA. It won't solve anything for you.
I also think, your bootloader must be locked to run the RUU.
And i think it is your only chance to get the phone back running, because there is no stock rom or backup for boost (as far as i know).
I am OK with rooting it. But in order for me to do it I have to get the bootloader to unlock which I can't seem to do. It does all the motions to unlock. Until the phone reboots
What i have found in this few minutes, Error 171 should be a driver issue.
So, you should make sure that the correct drivers are running (HTC Sync). Maybe another PC could be also a good try.
And you can't root a phone which is not booting into OS. You need a OS.
Is there different drivers I could try besides tc sync. I have tried both computers that I have one has windows 8. The other has windows vista.both have htc sync on them. Also tried a different cable.
If I type in cmd fast boot devices it shows my device being connected. The error shows up while it is waiting for the boot loader to reconnect
Latest should be this.
I will give it a try thank you for helping me. I'm banging my head against the wall for 2 days trying to figure out why nothing is working on this.
Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.
old.splatterhand said:
Its really kinda strange, that bootloader should belocked again after reboot.
But your focus must be the RUU.
Click to expand...
Click to collapse
Yea, my main goal is to get it to boot up. I was hoping it was an easy fix. Like with the Samsung epic I had. Just slap it in with odin and boom. after I couldn't get the RUU to work I figured I would try to root it. but since I can't even get the bootloader to unlock. I am stuck and that's the biggest reason I posted. normally I wouldn't I try to read other post and/or youtube it to find someone with a similar problem.
Quick question. When I go into the RUU can/should be in fastboot?
Yes, you should be in fastboot (USB) mode.
Ok so I downloaded the drivers you recommend. It was different then the ones I had. I also downloaded the RUU from the htc site as well just in case. Will try when I get back home. Thanks again.
So here is what I have. I downloaded driver v4.11.0.001. And installed. Downloaded ruu k2_cl_jb_45_s_sprint_wwe_boost_3.05.653.4......
I went into cmd and type fastboot devices. My device showed up. Ran the ruu. Samething happened. The ruu stops because when the phone reboots. It doesn't reboot to the bootloader.
Also I tried in cmd to get the phone to reboot to bootloader with no luck. Is there any thing else I can try?