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
Related
I've got a Nexus S that got screwed up from the 2.3.6 OTA. It can go into fastboot mode and recovery mode but it will not boot into Android. When you try to unlock the bootloader you get the unlock screen, can select yes but when you press power the device just hangs. If you go into download mode you get a screen about unlocking the bootloader. Odin detects the device, retrieves the pit, sends the image you want to flash to the phone and the phone says image verified. Then it just does nothing. Odin just sits there and there is no other feedback on the device. It looks like if the bootloader is locked you cannot flash with Odin either. Or at least if the device goes into the strange unlock bootloader screen instead of the true download mode screen Odin flashes fail. I have searched and searched and cannot find a resolution to this problem. Has anyone figured out why some devices hang when you try to unlock the bootloader and has anyone found a way to work around this problem. I am trying to help a guy out and don't want to give him back his phone telling him there is simply nothing I can do for him. He has a TMO device in Thailand. Samsung service here will only service phones sold in Thailand through authorized channels. Since it has a TMO model number they won't touch it.
push clockwork with fastboot
tylerwatt12 said:
push clockwork with fastboot
Click to expand...
Click to collapse
Can't. Clockwork recovery image is sent to the phone. Then it says failed because bootloader lockaed, use "fastboot oem unlock" to unlock the bootloader. And on the phone it says something like Flash FailedState LOCKEDbootloader.
Without being to unlock the bootloader no image can be flashed. I even tried a stock boot image just for a test and it was rejected in the same manner. With the bootloader being locked down it won't let me flash anything. I would need a stock signed rom with android-info.txt and android-product.txt files. I have yet to find one. I think that would flash the phone.
Odin is a no go also. The images are pushed to the phone, the phone verifies the images and then doesn't flash them due to the bootloader being locked. And in download mode I don't get the shovel guy I get a screen telling me to unlock the bootloader but I am connecting in the manner that Odin can see and talk to the phone. The phone just refuses to flash the images once they are downloaded to it.
same for my nexus s,how to solve it?thx
I'm also having the problems here.
However, I simply cant get fastboot to work. It is continually stuck on 'waiting for device' (since the 2.3.6 OTA update).
I tried to flash an old 2.3.4 stock ROM I had on my SDcard, but recovery wont let me. ClockworkMod also cant be flashed because of the fastboot problem.
Yes, I checked that my drivers are up to date, I've tried using fastboot from both windows 7 and Ubuntu 11.04.
splinter701 said:
I'm also having the problems here.
However, I simply cant get fastboot to work. It is continually stuck on 'waiting for device' (since the 2.3.6 OTA update).
I tried to flash an old 2.3.4 stock ROM I had on my SDcard, but recovery wont let me. ClockworkMod also cant be flashed because of the fastboot problem.
Yes, I checked that my drivers are up to date, I've tried using fastboot from both windows 7 and Ubuntu 11.04.
Click to expand...
Click to collapse
Do you mean getting stuck when you try to unlock the bootloader (fastboot oem unlock) or can you not even get into the bootloader at all.
I can get into the bootloader with "adb reboot-bootloader" or just holding the power and volumeup keys on. However, no fastboot commands work at all. My lock state = unlocked, but even though I have the superuser app installed, I dont have root access.
All the problems started when I foolishly applied the OTA update from 2.3.4 to 2.3.6.
maybe try on another pc?
splinter701 said:
I can get into the bootloader with "adb reboot-bootloader" or just holding the power and volumeup keys on. However, no fastboot commands work at all. My lock state = unlocked, but even though I have the superuser app installed, I dont have root access.
All the problems started when I foolishly applied the OTA update from 2.3.4 to 2.3.6.
Click to expand...
Click to collapse
Reinstall drivers?
Sent from my Nexus S 4G using xda premium
Had the same problem ... but there's a YouTube video where the guy shows how to root any nexus device... here's the link but view from the PC because within the video there's a link saying that this video is old and to click the box within the video screen
Also there should be a link that says Nexussrootnew ... click on it to download and extract it and move it to C drive... within the file Ull have the USB drivers superuser ... recovery. Once moved into C drive open Command Prompt and type:
>cd c:\Nexussrootnew "enter"
>Fastboot Device"s" < Forgot lol
>FastBoot OEM Unlock
Just Follow the step in the video and Ull be fine
"REMEMBER Watch Video Via PC"
http://m.youtube.com/#/watch?deskto...e.com/watch?v=xwe4sWH67dk&v=xwe4sWH67dk&gl=US
Sent from my Nexus S using xda premium
Thanks so much YourMainDude! I usually avoid videos for instructions on this kind of thing, but this one was actually good.
For anyone who comes across this thread again, the tools you need seem to be in the SDK but do not work. The tools that work are at the website of the above video-maker (I cant post links yet, but if you search google for 'nexussrootnew.zip' the first hit should be the website nexusshacks.com)
I'll be installing cyanogenmod I think, since I'd rather that I never again have an OTA update from google.
splinter701 said:
Thanks so much YourMainDude! I usually avoid videos for instructions on this kind of thing, but this one was actually good.
For anyone who comes across this thread again, the tools you need seem to be in the SDK but do not work. The tools that work are at the website of the above video-maker (I cant post links yet, but if you search google for 'nexussrootnew.zip' the first hit should be the website nexusshacks.com)
I'll be installing cyanogenmod I think, since I'd rather that I never again have an OTA update from google.
Click to expand...
Click to collapse
=] your most welcome sir
Sent from my Nexus S using xda premium
YourMainDude said:
Had the same problem ... but there's a YouTube video where the guy shows how to root any nexus device... here's the link but view from the PC because within the video there's a link saying that this video is old and to click the box within the video screen
Also there should be a link that says Nexussrootnew ... click on it to download and extract it and move it to C drive... within the file Ull have the USB drivers superuser ... recovery. Once moved into C drive open Command Prompt and type:
>cd c:\Nexussrootnew "enter"
>Fastboot Device"s" < Forgot lol
>FastBoot OEM Unlock
Just Follow the step in the video and Ull be fine
"REMEMBER Watch Video Via PC"
link
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I tried this but it still requires bootloader to be unlocked so it didn't work. My problem is similar to OP's. My phone appears to offer the bootloader unlock option, but selecting 'yes' to unlock fails to actually unlock. So nothing else works to restore the ROM. Though the phone does accept commands from adb just fine.
Anyway, I'm just posting this in case anyone else has the the same issue w/ bootloader not unlocking.
First of all I apologize if this has been covered, I have been trying to find a solution for 3 days straight. I have a Rogers Wireless HTC One X I managed to unlock bootloader and root as well as having access to TWRP 2.1.8. recovery.
My problem is when I tried to apply the 3 dot removal mod my phone suddenly would not boot past the first screen, and a message would appear for developers use do not distribute but just stay on that screen. I have tried numerous things to no avail. I can boot in recovery and mount sd card from there (but have not found a successful way to restore from within recovery mode) otherwise in fastboot etc. the computer does mount the phone at all. it will not mount as a device properly so I cannot run the RUU and flash to stock.
So I am left with a unmountable and unbootable phone (brick) and have no other ideas on how to fix it if possible. BTW the device does show in device mgr and the computer gives the connect and disconnect alert, but it will not mount. Also, I have read the bootloader has to be relocked to flash back to stock if I relock the phone I cannot access recovery therefore an endless nightmare. Also, within TWRP recovery I try to reboot and it gives an error saying no Android OS found, install a rom or restore from backup (which I have neither) so I have to hold the power and dwn volume button to reboot each time to switch from recovery to fastboot. I think its toast.
Thank you in advance for any responses, I have been up almost 36 hours straight trying to figure this out and the phone is not even a week old. :crying:
There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.
Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.
gunnyman said:
There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.
Click to expand...
Click to collapse
Thank you very much I will look into that today. Fingers crossed!
i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.
stnguyen09 said:
Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.
Click to expand...
Click to collapse
Yes, thank you I have HTC Sync installed and it does not recognize the phone when it is connected either. I will keep searching. Thanks.
ethantarheels123 said:
i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.
Click to expand...
Click to collapse
Yes, I have tried relocking bootloader, it did not help with the phone being recognized by the computer also when I oem lock I cannot access recovery and such. I will have some more time to poke around with it, I have downloaded the RUU utility although it sends back error with device not found. Thanks for your reply, I will keep at it I know the phone can not be bricked, well I am hoping not!
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.
Hello there. I went through the unlock process just fine, but followed some reccomendation to install a new boot.img via Hasoon2000's tool in order to run Viper ROM (downloaded the boot.img from the Viper thread here). Well now my phone is in a boot loop that brings me to the HTC screen with red text saying This build is for..... When I power off it comes right back to that screen and I can't get it to get anywhere else.
Any thoughts? Thank you for any help.
mrwizard65 said:
Hello there. I went through the unlock process just fine, but followed some reccomendation to install a new boot.img via Hasoon2000's tool in order to run Viper ROM (downloaded the boot.img from the Viper thread here). Well now my phone is in a boot loop that brings me to the HTC screen with red text saying This build is for..... When I power off it comes right back to that screen and I can't get it to get anywhere else.
Any thoughts? Thank you for any help.
Click to expand...
Click to collapse
Does your computer recognize the phone being plugged in? If so, run adb reboot recovery. If that doesn't work, try re-running the kit to re-root it.
HTC_Phone said:
Does your computer recognize the phone being plugged in? If so, run adb reboot recovery. If that doesn't work, try re-running the kit to re-root it.
Click to expand...
Click to collapse
I don't believe the computer is recognizing it at all. I'm not hearing the normal "ding" I get when it reboots.
first turn the phone off by holding power button for a longer time, then turn it on by holding both power and volume down buttons for a couple of seconds to enter bootloader
Did you install the Rom? Or just the boot.img?
Sent from my VENOMized HoxL
Alright, so holding down the volume button did get me into the bootloader. I tried the recovery and was able to recover using TWRP, but when I reboot it brings me back to the same HTC screen. So again, now I am able to do things via the bootloader so hopefully there is a next step to fix this.
To answer your question, I did not get to install the ROM, only the boot.img
Thanks for everyones help so far.
So go to twrp and install the Rom
Sent from my VENOMized HoxL
area51avenger said:
So go to twrp and install the Rom
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Ok, went ahead and loaded up Viper 3.2.2 and it seemed to go fine. Rebooted and am at the same HTC logo screen with the "this build is for development....." It will keep rebooting into this screen several times and will hang.
I did get the tampered/unlocked notice on the bootloader before doing all this. Not sure if that makes a difference or not.
Thanks for any additional help.
Did the ROM install correctly? Flash the boot img in adb again.
pOLLYpOCKET said:
Did the ROM install correctly? Flash the boot img in adb again.
Click to expand...
Click to collapse
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.
mrwizard65 said:
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.
Click to expand...
Click to collapse
I thought you wouldn't be able to install RUU if your bootloader is unlocked. But anyway, try this thread instead http://forum.xda-developers.com/showthread.php?t=1732980
I'm glad to report that I was finally able to flash the 3.2.2 Viper ROM. I was having problems unlocking the phone again, but just did it via fastboot command line. Once that was done it was smooth sailing.
I do have a couple of issues with the Viper ROM, but all in all it's fine and I'll post those questions in the Viper thread.
Thanks again for everyones help!
mrwizard65 said:
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.
Click to expand...
Click to collapse
Re-unlocking is a *****. Took me about 80 tries. Reboot phone, reboot pc, keep trying. Eventually it will work. You didn't need to run the ruu.. You may just want to keep the phone in stock state if this seems complex to you.
Sent from my One X using xda app-developers app
go into bootloader manually then plug phone to pc. works first time to unlock.
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?