Related
I am looking for guidance this time.....I have a Nexus s I9020 (t mobile version) and a couple weeks ago I don't know what happened really but i may have been messing around with a newer version of clockwork recovery late one night .... then the phone wouldn't boot past the google screen and I couldn't do anything to fix it... I tried to figure things out the next day and this is a list of things i have figured out...
1. in clockwork it can't mount anything....like anything at all pertaining to the internal memory/storage
2. I was tired and irresponsible
3. I tried fastboot just about everything
4. I tried flashing newer/older versions of clock work......nothing worked
5. I have tried downloading and installing roms via adb and fastboot but an error message comes up...
6. now this I know is dumb on my part, but make fun of me as you will... I fastboot locked the device......I know it was stupid because now when I type in fastboot oem unlock it hangs and does nothing after I check unlock on the phone...
I can get into fastboot mode and it says no boot or recovery img?
now if I had access to the internal memory I would def. be able to go back to stock but there in lies the problem what on earth can i do to make this thing a paper weight?
this is what i'm talking about, the bootloader doesn't unlock it just hangs .... any thoughts?
"w w w.youtube.com/watch?v=C4cS0kMj4AI"
Dear forum,
I kind of hesitated to start a thread for my problem, but after a long time I still haven't found a solution. I have contacted HTC (no answer yet), but hope to resolve my problem in meanwhile instead of waiting 1 month+ for a replacement.
I got the -by now familiar- freeze, and after rebooting it would go beyond the HTC logo, then stay stuck in a backlit black screen mode. Tried removing the battery, sim card, sd card etc. Then decided to boot into recovery (vol down + power) which worked, but any option would freeze the phone, like factory reset which I tried first.
Right now, the phone already freezes at the carrier logo, and I can't even get into recovery again (vol down + power). The phone won't respond to the key presses, and eventially boot and freeze at the carrier logo. The weird thing is that before, after a lot of trying and re-inserting the battery, it would eventually boot and work just fine for about 1 in 10 tries.
Does anyone have any ideas what I could try? Any help would be greatly appreciated!
edit: Okay, after a while I finally managed to get into HBoot again! Now what should I do to get my phone resetted/fixed? I guess it's not possible for me to flash another ROM or something as i'm not rooted. Details shown are: S-OFF, HBOOT 98.0002
can you get into recovery from bootloader?
Seems like I now consistently can boot into HBOOT. When I choose recovery, it will reboot, show the carrier logo, show the green logo with circular arrows, and then switch to the phone logo with a red exclamation mark for two seconds. Then, it shuts off. Also, when I tried that just now, it buzzed for like 6 times very fast after turning off.
On the second try, exactly the same happened: red exclamation mark, screen off, +- 6 fast buzzes.
After doing that, it doesn't respond to vol down+power or power at all. After reinserting the battery, I can get back into HBOOT
edit: it didn't want to boot into HBOOT, but now it does again. Anyhow, chosing recovery is still green logo, red logo, screen off and some buzzes. The phone doesn't show up in "adb devices" neither.
Whatever you are going to do; do not root your device as it will void your warrenty.
Is there anything else i can try doing? The situation so far:
-normal boot just stays stuck into carrier logo
-hboot->recovery gives a reboot, green logo, switch to red logo, screen off and +- 6 fast buzzes, then nothing. Needs battery reinsertion to be able to respond to vol down + power again
-hboot->factory reset just freezes on the same screen, no response, needs battery removal
-noshow in adb devices (update: show in fastboot!)
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
maxxur said:
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
Click to expand...
Click to collapse
Slow down maxxur, wait for this quesstion to be out there for long enough for someone to answer it.
Dont go on a battery pulling spree, coz that is the first and most tempting response on a frozen phone. But i hope you know what that can do to this phone...
Give the xda community some time to figure this out. Hold your ground till then. Need to go in to the theatre now. Will get back in the evening and try to figure this out.
Try running the RUU while in the fastboot menu (usb mode). Also my suggestion is not to make the process more complicated by downgrading - just reflash 1.47...
Thanks for the response guys
The RUU I found was 1.37. Could you point me to a 1.47 RUU for the 3UK network?
Also, running that RUU when in Fastboot USB mode is what I tried. The info on the RUU shows that it hangs indefinitely at "rebooting bootloader". That is expected, as when I try to manually reboot bootloader in my fastboot menu, my phone will also freeze.
I'm wondering if running a different recovery image could be of any help? Last night I tried running CWM recovery to see my options, by entering "fastboot boot recovery.img" but i'd get a "remote: not allow" error.
Have not noticed that you are not rooted!
Why don't you try the revolutionary tool? If you have luck it will restore your bootloader if it is broken (keep in mind that is not the best option because it will break you warranty). Then you will just need to flash an eng hboot and run the RUU, or better try some custom ROM
But in my opinion the best option for you is to go for a replacement rather to try yourself, since you dont have any custom software on it it has to be covered by your warranty (probably it is a faulty device to go like this from nothing).
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
maxxur said:
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
Click to expand...
Click to collapse
Of course you can if you are eager to try this. When you run the RUU, even when there is no phone connected there is a folder in your C: drive created (I assume that you are using Windows). Open your Windows Explorer and search for the rom.zip. When you have it copy it somewhere and close the RUU screen. Then if you open the RUU all the *.img files are there. You can try flashing the stock recovery or hboot or whatewer using the fastboot command. But I have to say again the best option for you is to bring the phone for a repair before you end up with something irreversible and void your warranty.
Thanks for keeping me sane on what to do with my problem Mentally, I came to the point where I'd go flash CWM recovery on my phone and try to flash that RUU rom from there, but you helped me get around that thought and now I made arrangements for HTC to come and pick it up. I'll keep you guys posted!
PS: you've got to love our desire s community, it's the best.
Cheered too early
Now HTC suddenly responds that while entering my phone in their warranty service thingy and the phone seemed to be 3G UK branded, they told me they "can't" do repairs for those.
Seriously, HTC is trying to troll me saying the inner hardware could differ between a UK and a Belgian Desire S?? Could this be true in any way?? :/
Maybe some parts are cheaper but with the same parameters...but I thought that when you have a branded phone you should seek your warrancy support from the carrier's office?!?
Sent from my HTC Desire S
Options for solution!
Option 1: Copy rom.zip (from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed) to your sd rename it to PG88IMG.zip and let m boot into hboot.
If option 1 is not ok try option 2.
Option 2: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU then after that run ruu RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.
If option 2 not OK then there is option 3.
Option 3: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU after that run in dos/terminal fastboot flash zip rom.zip (extracted from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed)
Let me know if one of these option worked for you if not I can help you with reflashing your hboot again.
NikMel,
Thank you so much for the tips. Currently I'm trying the first HBOOT + .ZIP method. It detected it, asked me to update and is now showing a pink "Updating" sign. How long should this normally take? I have a strong feeling it simply froze again, and it really turns out to be a hardware problem.
Is that updating next to radio?
If yes it will take realy long so wait!!
Hi guys, this is a friends Nexus S he bricked during an ICS update (official one). I can't get it to work at all. It boots up an android guy with a red triangle and a (!) coming out of his chest. The bootloader is locked (version I9020XXKL1). He's never tried to root beforee
Things I've tried:
Got ADB drivers working
'ADB factory reset oem unlock' gets me a dialog screen on the phone confirming the unlock, then when I confirm, I get: 'FAILED. remote erase: fail'. Tried with serial number (saw a random post mentioning that), but same result.
I tried flashing an IMG file through fastboot with a similar error. the device shows up in getstate and devices, but you can't write to it it seems.
Mentioned to someone at work and he said I should be able to get a stock RUU exe file and you just run the RUU. Similar to a 1 click odin fix, but...not. Cause I can't get into download mode. If I try to go into recovery mode from fast boot, that's when you see the dead android guy with the (!). If I just try and let it boot on its own..it just boot loops. Doesn't turn off/on, but never passes the 'Google' splash screen.
I've searched for the RUU files and can't find them anywhere, at least for a Nexus S. Am I missing something here? Not sure what else to try.
Thanks!
b0vine said:
Hi guys, this is a friends Nexus S he bricked during an ICS update (official one). I can't get it to work at all. It boots up an android guy with a red triangle and a (!) coming out of his chest. The bootloader is locked (version I9020XXKL1). He's never tried to root beforee
Things I've tried:
Got ADB drivers working
'ADB factory reset oem unlock' gets me a dialog screen on the phone confirming the unlock, then when I confirm, I get: 'FAILED. remote erase: fail'. Tried with serial number (saw a random post mentioning that), but same result.
I tried flashing an IMG file through fastboot with a similar error. the device shows up in getstate and devices, but you can't write to it it seems.
Mentioned to someone at work and he said I should be able to get a stock RUU exe file and you just run the RUU. Similar to a 1 click odin fix, but...not. Cause I can't get into download mode. If I try to go into recovery mode from fast boot, that's when you see the dead android guy with the (!). If I just try and let it boot on its own..it just boot loops. Doesn't turn off/on, but never passes the 'Google' splash screen.
I've searched for the RUU files and can't find them anywhere, at least for a Nexus S. Am I missing something here? Not sure what else to try.
Thanks!
Click to expand...
Click to collapse
Firstly is this still under warranty? Since its the offical ICS update. Just tell him to go to his provider and ask for a replacement since it was not the user's fault.
A few questions. Why is he receiving the ICS update now? If this was ages ago when ICS was first released, Google stopped ICS update for a weeks or so since there was some problems.
And if the warranty doesnt work. Id say root it and flash a Recovery.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
It's a few months out of warranty, and no, TELUS won't replace it, he's already tried.
I also can't root it as mentioned. I get to this point in the guide
For Windows:
fastboot oem unlock
And get the ERASE:FAILED error once confirming the unloock.
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?