Related
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
As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436
What we're your steps exactly? Did you relock your bootloader
a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Does anybody else have some more ideas?
Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?
kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.
Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you
Hi there,
i have a huge problem. As there was no warrenty left for my One S I thought about to change the firmware to CM11.
I have to admit that i don't have any experience in doing such things, but i thought, it couldnt go wrong if i follow a tutorial.
So at first i unlocked the bootloader via HTC website and istalled TWRP 2.7.1 (latest version). Everything went well, I placed the ROM into the phones root directory, started the recovery and then whiped it before choosing install and selected the file. After about 30 seconds the phone reported the step was successful and i pressed reboot. Then there was the HTC starting screen and then a black screen.
After that i had no reaction but the blinking buttons when i press the power button for a longer time. But it changes nothing. No normal boot. No access to fastboot. Only if i connect it to my PC there is an aditional device to see, but whitout any access.
I know I did wrong but i have no idea what or how to fix it. I hope you can help me.
ElDorado1993
Now i found a way to get access to fastboot again, but i dont really know what to do now.
Can you give me an detailed tutorial, for jelly bean or kitkat (dont matter) that is surely working now?
My main problem is that i can't copy my files into the root directory as i cant boot the phone.
Does it show up in computer connected devices?
If it does, download stock kernel and ROM and upload to phone and go into recovery[power +volume up while off] and flash them both kernel first.
Sent from my ZTE_N9511 using XDA Free mobile app
The problem is the phone wasnt ever shown as device on the pc (like a flash drive) since version 4.1 so I allways needed some tricks like airdroid. So i suppose i need adb commands to copy files and i dont have so much experience in doing this.
Do you know how to use adb?You don't need adb I just wanted to know to see if it shows up there and not on computer you simply need to install the drivers.Try holding down all 3 buttons to see if it powers down. Do what it says http://www.technewscentral.co.uk/enter-fastbootbootloader-mode-htc-one/id_7930 if works go into fast boot. Does it say locked or unlocked. If unlocked go herehttps://github.com/koush/UniversalAdbDriver and get the windows installer if your on windows.
Sent from my ZTE_N9511
I now found out how adb and fastboot are working, but the main problem now is, that it says the sdcard cant be mounted. I tried this tutorial http://forum.xda-developers.com/showthread.php?p=25557817#post25850720 but i dont know how to do the first step. Du i need an extra file and where do i get it from and how to use it. As long as i dont get back this access, i couldnt install any OS. I tried also sideload. It was able to copy but cant install because of the missing sdcard access.
I hope you can help me to become my phone running again.
Go here http://m.youtube.com/watch?v=xWmnHwkDrKk but first type adb devices in cmd. If it shows ur HTC type adb shell and and type mount sdcard next to the "#" once it appears although you should be using the fastboot shell not adb commands.adb should only work on a powered on device or you can use fast boot in cmd while phone is in fastboot not recovery(you did say the phone can go into fast boot right?). Just make sure you got the right drivers and both fast boot and adb. You should get Koush's Universal drivers from my previous post since some phones have multiple drivers and MAY cause problems with cmd. Also HTC one S doesn't have expandable storage correct?
Sent from my ZTE_N9511
Wow. Now I incidentally soft bricked my phone again if you would believe it and nothing works this time.
Have you been able to fix?
Sent from my ZTE_N9511
Okay, i forgot to write but adb and fastboot are working on my Mac. I use the Mac because Win 8.1 has the known driver problems.
I tried a lot now, but i recognized maybe the main problem. My phone is still S-ON in bootloader. For sure thats the problem. Do I need to get rid of it and how do I do. The tutorial i used hasn't mentioned this step, maybe the person was still S-OFF.
The first thing i try now is to flash the original recovery, lock the bootloader and execute the original signed RUU to get back the original software first. Im going on holiday on tuesday and it would be a pitty without the phone. When I get it working i will leave it, and thy it again, when I'm back. Otherwise.......****
Use this tutorialhttp://htc-one.wonderhowto.com/how-to/fix-soft-bricked-htc-one-by-flashing-new-rom-via-adb-0154361/unless its the one you used already. From boot loader you were supposed to have gone to fastboot.boot loader has to be unlocked.From fast boot you flash TWRP.IMG which happens to have a special adb side load feature under advanced options. There you upload another ROM and kernel.here is the full list of supported devices as I don't know what variant or carrier you havehttp://teamw.in/twrp_view_all_devicesAlso, a stock kernel is optional but it always seems to fix my problems.
Sent from my ZTE_N9511
Thank you. But I already did it like this. The issue is, than after using sideload successfully the installation fails because of the known "unable to mount storage" text. And i don't know what to do wrong.
Like I already said, my phone is still S-ON, but can this make a difference?
Now i got it to bring the stock ROM running again, and as I'm on holiday for a few days I'm happy it is working again.
But one thing is left. It seems like there is no 3G/HSDPA connection now, only EDGE. I dont know what went wrong. Did you hear about this problem.
By the way, my phone is the standalone version whithout any provider.
Search the forums about edge only. There is a huge thread on this.
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?
Hi everyone. Thanks for your attention
I have a HTC Mini. Today I wasn't able to connect my phone into the wifi. Then, I restarted and afterwards the phone didn't boot at all. It goes only to the bootloader menu. Last two days I was looking for the solution. In the HBOOT menu when I tried to the factory reset it only jumps into the fastboot menu, same thing for the recovery. When I am in the fastboot menu, if I click on reboot, or reboot bootloader it just reboot and the HBOOT menu comes again.
However, my HBOOT menu is locked and when I wanted to try unlock it. following problem happen :
- when I connect the phone to a Mac, Fastboot Devices detect (but only fastboot, ADB devices return nothing) the phone and I could get the token for unlocking procedure, but when I load the the unlock token which sent to me by mail from HTCDEV, nothing happen. it just say everything was successful on Terminal, but nothing shows up on the phone to Confirm unlocking procedure and sometimes it hangs and if I try pushing the token again (the bin file), I receive an error, fail to splash the screen (something like this). However, I already installed the HTC Sync Manager and every other possible driver I could find on the internet.
When I use windows, after installing HTC Sync and all of the drivers several time, still the command for Fastboot devices or ADB Devices return nothing. I don't care about the phone data or anything. I just want to like Flash the whole operating system and everything . thats fine. But nothing is working properly.
Please guide me if you have any idea about this problem.:crying::crying:
It happened to me too. Same sh1t. Camera didn't worked so i decided to restart the phone...from that time same story like yours.
same here, but i have an idea
when i do fastboot getvar all my baseband says N/A indicating corrupt or missing radio rom
the correct radio should be Radio_1.29.40g on mine based on the RUU i have on hand (used before)
RUU attempts to get into different mode and fails
i have been unable to extract the files from the RUU