Related
As the title says: I'm trying to install the 3.18 RUU for my AT&T HTC One X. I'm currently on an old build of CM10.1 (beautifully maintained by H8rift) and was wanting to try the latest build he posted with the 3.4 Kernel. I am S-Off and Unlocked. I searched the forum (internal search seems to be broken at the moment) and all I keep seeing is mostly go to fastboot THEN run the RUU. Well I'm in fastboot (enabled the menu from within CM...less I just misunderstood that completely). Fastboot shows "Fastboot USB" but the RUU still gives Error 170. What did I do wrong?
Running this on a Windows 8 x64 system, installed HTC Sync Manager (still didn't help). I updated the Android SDK Tools to the latest version. My CID is all 1's (as per the S-Off directions). I'm at a loss here hehe.
Ooh I have TWRP 2.4.1.0. And yes I barely post, just always looking, reading, etc.
Is the USB port you're using 2.0 or 3.0? If it's 3.0 (it should have the USB icon and a little ss) try switching to 2.0. Also, try running RUU while not in fastboot.
RollTribe said:
Is the USB port you're using 2.0 or 3.0? If it's 3.0 (it should have the USB icon and a little ss) try switching to 2.0. Also, try running RUU while not in fastboot.
Click to expand...
Click to collapse
Yup running it on my USB 2.0 ports. Tried my case ports and the motherboard ones, same thing. Also just tried it with the phone booted. No dice. Even using the HTC USB Cable (not like there should be a difference but hey, just in case). Maybe I should threaten the phone...with a hammer. (Nah I'm not that mean).
Turbo Mach 5 said:
Yup running it on my USB 2.0 ports. Tried my case ports and the motherboard ones, same thing. Also just tried it with the phone booted. No dice. Even using the HTC USB Cable (not like there should be a difference but hey, just in case). Maybe I should threaten the phone...with a hammer. (Nah I'm not that mean).
Click to expand...
Click to collapse
Is your phone showing up in adb?
Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.
Turbo Mach 5 said:
Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.
Click to expand...
Click to collapse
Hmm... is your USB debugging on? If yes, try reinstalling the driver.
Turbo Mach 5 said:
Heh had to look it up but after doing it...no just says List of devices attached. Nothing else.
Click to expand...
Click to collapse
It seems to me like a driver issue.
if while in fastboot mode fastboot devices does not show the device, The RUU will not work.
uninstall HTC driver and HTC sync and any other phone software (for samsung or whatever else)
Install latest HTC sync
make sure fastboot devices lists your device, then run the RUU
exad said:
It seems to me like a driver issue.
if while in fastboot mode fastboot devices does not show the device, The RUU will not work.
uninstall HTC driver and HTC sync and any other phone software (for samsung or whatever else)
Install latest HTC sync
make sure fastboot devices lists your device, then run the RUU
Click to expand...
Click to collapse
Roll, yah USB Debugging is on hehe. I even turned it off and back on. Exad: Ok. Uninstalling both HTC Sync and Samsung Kies (have to use that for my brother's Galaxy S2 Skyrocket). Uninstalling both now (might have to also run out of town so reply could be a little late).
Turbo Mach 5 said:
Roll, yah USB Debugging is on hehe. I even turned it off and back on. Exad: Ok. Uninstalling both HTC Sync and Samsung Kies (have to use that for my brother's Galaxy S2 Skyrocket). Uninstalling both now (might have to also run out of town so reply could be a little late).
Click to expand...
Click to collapse
Hey you said you were on Windows 8. You may have to manually install the driver to get it work, that's what I had to do. Or you could use the universal adb driver, but if you're gonna RUU, I'd be safe and use the HTC one.
RollTribe said:
Hey you said you were on Windows 8. You may have to manually install the driver to get it work, that's what I had to do. Or you could use the universal adb driver, but if you're gonna RUU, I'd be safe and use the HTC one.
Click to expand...
Click to collapse
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.
Turbo Mach 5 said:
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.
Click to expand...
Click to collapse
Annd now when I was all set to update to his latest one he posted, H8rift goes and begins posting nightlies and I don't have to downgrade touchpanel firmware! Hahaha (I had downgraded it and was about to install)! Still, thank you guys. I'm back in business!
Dear Turbo Mach 5,
Could you please provide the detailed steps you followed to RUU your ATT HTC One X.
I am also planning to update my ATT HTC One X with 3.18 RUU to use CM 10.2 based roms.
Please provide this information which will help me to start with my device.
1) Whether we need to re-lock the bootloader ? (I have SuperCID and S-Off)
2) After RUU ing whether we need to unclok the boot loader and root the device if we have SuperCID and S-off?
Thanks and Regards,
Sathish.
Turbo Mach 5 said:
Alrite after removing both managers (HTC and Samsung), reinstalling, and then having to turn off debugging then turn it back on...it now sees it
HT25CW****** device (first said offline but I looked at the phone and noticed it was asking for permission).
Time to continue flashing! I think what happened is I had the universal USB drivers but then had to install KIES for my bro so it replaced them. Then installing HTC on top of that made it give up. Thanks you two! I'll post if I have any other strange issues.
Click to expand...
Click to collapse
sathish804 said:
Dear Turbo Mach 5,
Could you please provide the detailed steps you followed to RUU your ATT HTC One X.
I am also planning to update my ATT HTC One X with 3.18 RUU to use CM 10.2 based roms.
Please provide this information which will help me to start with my device.
1) Whether we need to re-lock the bootloader ? (I have SuperCID and S-Off)
2) After RUU ing whether we need to unclok the boot loader and root the device if we have SuperCID and S-off?
Thanks and Regards,
Sathish.
Click to expand...
Click to collapse
You don't need to relock your bootloader to the run the RUU because you have s-off. And your s-off status and unlocked bootloader should survive the RUU process. All you need to do afterwards is flash TWRP recovery again, then you can flash a ROM. Please be aware that cm10.2 is still very alpha and multiple users have reported bricks from running it.
Sent from my Evita
Hi timmaaa,
Thank You very much for the clarification and update on cm 10.2 rom.
I was thinking with RUU my bootloader is going to re-lock even though I have S-off.
Thanks and Regards,
Sathish.
timmaaa said:
You don't need to relock your bootloader to the run the RUU because you have s-off. And your s-off status and unlocked bootloader should survive the RUU process. All you need to do afterwards is flash TWRP recovery again, then you can flash a ROM. Please be aware that cm10.2 is still very alpha and multiple users have reported bricks from running it.
Sent from my Evita
Click to expand...
Click to collapse
Hi,
I'm having trouble using the RUU as well. The problem seems to be getting the usb driver for my oneXL working. every time i plug it into my win7 pc, it goes through this installing drivers process but having clicked on "display details", the "android phone" component of the drivers says "failed". I've tried universal adb driver, and HTC usb driver with and without htc sync installed. the HTC sync manager keeps saying there is an update available for usb driver, even though I uninstalled the driver manager and htc sync.
Have not been able to get adb working, when i recently S_OFF my phone I had to use adb over wifi - but it worked.
Any help greatly appreciated, thanks!
Your post is a bit confusing as to which drivers you actually have installed. Download the latest HTC Sync Manager from the HTC One XL page at HTC.com, install it, connect your phone, drivers will install, uninstall HTC Sync Manager but leave drivers installed. Also, make sure you're using a usb 2.0 port and the HTC cable that came with the phone.
Sent from my Evita
thelloydr said:
Hi,
I'm having trouble using the RUU as well. The problem seems to be getting the usb driver for my oneXL working. every time i plug it into my win7 pc, it goes through this installing drivers process but having clicked on "display details", the "android phone" component of the drivers says "failed". I've tried universal adb driver, and HTC usb driver with and without htc sync installed. the HTC sync manager keeps saying there is an update available for usb driver, even though I uninstalled the driver manager and htc sync.
Have not been able to get adb working, when i recently S_OFF my phone I had to use adb over wifi - but it worked.
Any help greatly appreciated, thanks!
Click to expand...
Click to collapse
Scratch that...
Manually installed drivers and i got it working. Had to manual install twice, after one more error (171 this time), the RUU is applied. CM10.2 here i come!
htc vivid
Freinds My HTC vivid is like dead not able to turn on nor charging and not able to run ruu, its showing unrecognized malfunctioned, did uninstall and install of driver still nothing is happening please help.
biradar said:
Freinds My HTC vivid is like dead not able to turn on nor charging and not able to run ruu, its showing unrecognized malfunctioned, did uninstall and install of driver still nothing is happening please help.
Click to expand...
Click to collapse
You're in the wrong section, this is the HTC One XL section, you need to go here:
http://forum.xda-developers.com/htc-vivid
Just had the same issue trying to manually update my M9 to Nougat. Rebooted to download mode (Volume down & Power from off state) and it worked.
Just yesterday, I was trying to get CM10.1 on my HTC One XL, and all of a sudden, my touchscreen at my dock area just stopped working, i didnt take much notice at that time as I didnt have an OS to boot into yet and i thought it was just a tiny problem. Today when I successfully flashed CM10.1 i then started to realize that my touchscreen there wasn't working. I don't exactly know what the last thing i did was before it happened, as I said i didn't really take notice when it started happening. I tried factory resetting but it didn't work either. Could it be that my touchscreen on that area is spoilt? should i replace the screen???
All help is greatly appreciated
Thanks
The best way to find out whether it's a hardware problem or not is to run an RUU. Boot the stock ROM up directly after running the RUU, if the problem persists it's almost definitely a hardware issue, if your touchscreen works again it was a software problem. Please note: if you have SuperCID (which you probably do) and s-on, running an RUU will brick your phone, so make sure you get s-off first.
Sent from my Evita
timmaaa said:
The best way to find out whether it's a hardware problem or not is to run an RUU. Boot the stock ROM up directly after running the RUU, if the problem persists it's almost definitely a hardware issue, if your touchscreen works again it was a software problem. Please note: if you have SuperCID (which you probably do) and s-on, running an RUU will brick your phone, so make sure you get s-off first.
Sent from my Evita
Click to expand...
Click to collapse
so im s-on, but when i try to change my cid to 11111111, using
>adb shell
>su
>dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
when i type in su it says
/sbin/sh: su: not found
Have you enabled usb debugging and granted it root access in developer settings? Or you could try the hex edit method, but you'll still need su access.
Sent from my Evita
timmaaa said:
Try the hex edit method.
Sent from my Evita
Click to expand...
Click to collapse
thanks for the speedy response. That was the method that i tried, when i type in su, it says
/sbin/sh: su: not found
but im in recovery mode
because i cant turn on usb debugging because i can't click the about phone portion of my screen
timmaaa said:
Have you enabled usb debugging and granted it root access in developer settings? Or you could try the hex edit method, but you'll still need su access.
Sent from my Evita
Click to expand...
Click to collapse
i have now enabled usb debugging and allowed root access for apps and adb. But when i type in adb shell now, it cant detect my device. I have all the necessary drivers installed
So adb has been working previously? Does your screen work fully in TWRP recovery?
Sent from my Evita
timmaaa said:
So adb has been working previously? Does your screen work fully in TWRP recovery?
Sent from my Evita
Click to expand...
Click to collapse
Adb has been working previously in recovery, and yes, my screen works fully in TWRP, exceptthe three buttons below (not the stock htc buttons but the ones in twrp on the screen itself )
Ok, the fact that the problem exists in recovery as well tells me that this is likely a hardware issue.
Sent from my Evita
timmaaa said:
Ok, the fact that the problem exists in recovery as well tells me that this is likely a hardware issue.
Sent from my Evita
Click to expand...
Click to collapse
so i should get my screen replaced???
or can i still just try to run the RUU?
At this point I'm fairly confident that you're looking at a hardware problem. If you want to, you can still try the RUU (as long as you can get s-off first) but I have a feeling it won't really help. It is worth a try though.
Sent from my Evita
timmaaa said:
Have you enabled usb debugging and granted it root access in developer settings? Or you could try the hex edit method, but you'll still need su access.
Sent from my Evita
Click to expand...
Click to collapse
hi again, where do you find the file to hex edit on your computer??? i cant seem to find it.
Thanks again for your help
I really screwed up, I was installing a new OP and was wiping Cache, Dalvik ect... when I accidently wiped my external storage. Well I mounted my SD card and put an OP back on the sd card, installed through TWRP and I'm just stuck in a boot loop. Have tried several differnt OP's and all I get is the boot loop. Can someone please help me correct what I screwed up. Everything is gone, when I look under Android secure there is nothing.
I'm not sure what you mean by OP? Maybe you mean ROM? Anyway you need to give more information, what are your bootloader details?
Sent from my Evita
timmaaa said:
I'm not sure what you mean by OP? Maybe you mean ROM? Anyway you need to give more information, what are your bootloader details?
Sent from my Evita
Click to expand...
Click to collapse
Your correct, I was half asleep when I posted my question. I do mean ROM. What kind of information from the bootloader would you like?
S-off
CID-111111111
HBOOT-1.09.0000
OpenDSP-v34.1.0.45.1219
Well you're s-off, so the boot.img isn't the problem. Which ROMs in particular have you tried installing? What version of TWRP are you using?
Sent from my Evita
timmaaa said:
Well you're s-off, so the boot.img isn't the problem. Which ROMs in particular have you tried installing? What version of TWRP are you using?
Sent from my Evita
Click to expand...
Click to collapse
VenomXL 4.0.0 Sense 5, VenomXL 3.2.7, HatkaXL-evita-v4.7.1. These are all ROM's that I have previously run on my phone. TWRP is v2.3.3.1.
Thank you for your help.
You might need to try running an RUU.
Sent from my Evita
timmaaa said:
You might need to try running an RUU.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaaa are you going for the record of "how many people can you help!" on the Evita forums :silly:
scrappy1959 listen to this guy as he knows what he is talking about! :laugh:
radavs said:
Hey timmaaa are you going for the record of "how many people can you help!" on the Evita forums :silly:
scrappy1959 listen to this guy as he knows what he is talking about! :laugh:
Click to expand...
Click to collapse
Lol I have a lot of spare time on my hands recently, I can't work right now due to health problems so I spend a lot of time on here. I've taken a lot from the XDA community over the years so I feel it's the right thing to do to try to give back and help people where my knowledge permits. I love learning, especially when it comes to Android and I think this is the best place to do it. I think the next step is to actually try to learn how to develop a ROM, but that'll have to wait until I get a new PC.
Sent from my Evita
---------- Post added at 02:37 PM ---------- Previous post was at 02:25 PM ----------
By the way, radavs, it's great to see you throw another Telstra ROM on here for the Aussies :thumbup:
Sent from my Evita
timmaaa said:
You might need to try running an RUU.
Sent from my Evita
Click to expand...
Click to collapse
What would be a good RUU and how would you flash it? I don't want to lose root. Went through to much to achive it.
Root isn't the thing you should be worried about, the unlocked bootloader and custom recovery are what you actually need to flash custom ROMs. All root does is give you administrative access to the root directories on your phone.
You are s-off so it doesn't matter which RUU you use, click the link in my signature and you'll find RUU links in there. Your bootloader will remain unlocked and you will retain your s-off status through the RUU process. You don't "flash" an RUU, it's an exe file so you run it like you would run any other exe program on a pc. An RUU returns your phone to being completely stock, including recovery, so you'll need to flash TWRP again afterwards.
Sent from my Evita
timmaaa said:
I have a lot of spare time on my hands recently, I can't work right now due to health problems so I spend a lot of time on here. I've taken a lot from the XDA community over the years so I feel it's the right thing to do to try to give back and help people where my knowledge permits.
Click to expand...
Click to collapse
I love this attitude, as this is what XDA is all about. Contribute however you can, whenever you can!
timmaaa said:
Root isn't the thing you should be worried about, the unlocked bootloader and custom recovery are what you actually need to flash custom ROMs. All root does is give you administrative access to the root directories on your phone.
You are s-off so it doesn't matter which RUU you use, click the link in my signature and you'll find RUU links in there. Your bootloader will remain unlocked and you will retain your s-off status through the RUU process. You don't "flash" an RUU, it's an exe file so you run it like you would run any other exe program on a pc. An RUU returns your phone to being completely stock, including recovery, so you'll need to flash TWRP again afterwards.
Sent from my Evita
Click to expand...
Click to collapse
Would you be willing to explain the steps of installing the RUU. I think I know, just don't want to screw that up also. Once I get that far I should be fine flashing TWRP.
No worries, it's an exe file so it's pretty easy. Put your phone into fastboot mode and connect it to your pc, then run the RUU exe program, it's as simple as that. Just follow the prompts on the pc, you just need to say ok a couple of times.
Just make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off.
Just make sure you don't disconnect your phone while the RUU is running, sometimes it might look like the process is freezing (it sat on 27% for a while when I did it) but just let it continue, it should be fine.
Sent from my Evita
timmaaa said:
No worries, it's an exe file so it's pretty easy. Put your phone into fastboot mode and connect it to your pc, then run the RUU exe program, it's as simple as that. Just follow the prompts on the pc, you just need to say ok a couple of times.
Just make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off.
Just make sure you don't disconnect your phone while the RUU is running, sometimes it might look like the process is freezing (it sat on 27% for a while when I did it) but just let it continue, it should be fine.
Sent from my Evita
Click to expand...
Click to collapse
Just tried running the RUU and it was not able to connect with my OneXL, it had been so long since I have done any of this I forgot when I was flashing TWRP almost a year ago, both my laptop and desktop were not able to connect to the phone, something to do with the USB ports (Windows 8). However, I have an old laptop with XP that will connect to the phone. I am leaving for work at this point and will not be able to run the RUU until late tonight. I will let you know how it works out. Thanks
scrappy1959 said:
Just tried running the RUU and it was not able to connect with my OneXL, it had been so long since I have done any of this I forgot when I was flashing TWRP almost a year ago, both my laptop and desktop were not able to connect to the phone, something to do with the USB ports (Windows 8). However, I have an old laptop with XP that will connect to the phone. I am leaving for work at this point and will not be able to run the RUU until late tonight. I will let you know how it works out. Thanks
Click to expand...
Click to collapse
Thanks so much timmaaa, got out my old windows xp laptop and the RUU is loading on the phone right now (@29%). For some reason my newer laptop and desktop will not put my phone into Fastboot USB. I think it has something to do with the newer technolgy of the high speed USB. But, soon as I hook up my old XP laptop it picks it up right away and switches into Fastboot USB. It's done, now all I have to do is put TWRP back on the phone and I should be back in business. Thanks
Okay, I ran the new RUU 1.85. I can't seem to get TWRP installed. I downloaded super user# and it says I do not have root. However when I boot into bootloader it says
***UNLOCKED***
EVITA PUT SHIP S-OFF RL
CID-111111111
HBOOT-2.14.0000
S
Didn't think I would need help getting TWRP reinstalled but I do. If you could give me a little more help getting TWRP back on my phone. Thank you
scrappy1959 said:
Okay, I ran the new RUU 1.85. I can't seem to get TWRP installed. I downloaded super user# and it says I do not have root. However when I boot into bootloader it says
***UNLOCKED***
EVITA PUT SHIP S-OFF RL
CID-111111111
HBOOT-2.14.0000
S
Didn't think I would need help getting TWRP reinstalled but I do. If you could give me a little more help getting TWRP back on my phone. Thank you
Click to expand...
Click to collapse
I forgot, the phone is just unlocked. I need to re-ROOT. Thanks for your help.
i've unlocked my att one x got supercid.. and then i decided to change it to htc_405... so... it was the wrong choice! and now i can't get back to supercid, i've tryied all guides on forum but no one works..
from adb shell.. command writes.. device not found.
also installed newest htc drivers but nothing changes.. the hasoon allin1 tool doesnt work and i dont know what to do..hellppp :crying:
Are you s-on or s-off?
Sent from my Evita
timmaaa said:
Are you s-on or s-off?
Sent from my Evita
Click to expand...
Click to collapse
i'm s-on
Wait why did you do that? The cid for at&t one x is cws_001...
Sent from my HTC One X using Tapatalk 4
panda_mode said:
Wait why did you do that? The cid for at&t one x is cws_001...
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
i know but i changed it to recieve eu update.. didn't know that he has other cpu.. so now i cant change it to supercid or the original one..
You're kinda stuck then. To change CID more than once you need s-off, but to get s-off you need SuperCID. You probably should have done some research before you did that.
Sent from my Evita
timmaaa said:
You're kinda stuck then. To change CID more than once you need s-off, but to get s-off you need SuperCID. You probably should have done some research before you did that.
Sent from my Evita
Click to expand...
Click to collapse
so any suggestions? i know that i shloud search more.. i have other one s and i thought it was similar.. but that one is not branded
denny094 said:
so any suggestions? i know that i shloud search more.. i have other one s and i thought it was similar.. but that one is not branded
Click to expand...
Click to collapse
Maybe you can hex edit your mmcblk0p4 and change the cid back to super cid or the AT&T cid. DO MORE RESEARCH ABOUT THIS. I cannot help you step by step because I have not attempted this myself. THIS IS JUST AN IDEA AND MAY BRICK YOUR PHONE. I am not responsible for what will happen of you attempt this.
In the sticky-roll up, there is a thread called "AT&T: Unlocking the bootloader through HTCdev." The title looks irrelevant to your issue, but it has information about hex editing the mmcblk0p4 file
Sent from my HTC One X using Tapatalk 4
panda_mode said:
Maybe you can hex edit your mmcblk0p4 and change the cid back to super cid or the AT&T cid. DO MORE RESEARCH ABOUT THIS. I cannot help you step by step because I have not attempted this myself. THIS IS JUST AN IDEA AND MAY BRICK YOUR PHONE. I am not responsible for what will happen of you attempt this.
In the sticky-roll up, there is a thread called "AT&T: Unlocking the bootloader through HTCdev." The title looks irrelevant to your issue, but it has information about hex editing the mmcblk0p4 file
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
yeah i've seen that one.. but if i try to take that file.. adb says "device not found" so i cant do this one too..
C:\fastboot\adb shell (>enter)
daemon started succesfully*
device not found!
with lastest htc drivers and htc sync... if i could get the mmcblk0p4 file i wont open this thread
Ah I see. Well I can't be much of help then. Sorry
Sent from my HTC One X using Tapatalk 4
denny094 said:
yeah i've seen that one.. but if i try to take that file.. adb says "device not found" so i cant do this one too..
C:\fastboot\adb shell (>enter)
daemon started succesfully*
device not found!
with lastest htc drivers and htc sync... if i could get the mmcblk0p4 file i wont open this thread
Click to expand...
Click to collapse
Ensure that USB debugging is turned on.
Verify that HTC Sync is not running.
Try other cables, USB ports and even other computers.
s79336951 said:
Ensure that USB debugging is turned on.
Verify that HTC Sync is not running.
Try other cables, USB ports and even other computers.
Click to expand...
Click to collapse
i've tried all thoose , 3 pc's (1 with win7 the other win8) always debug mode..(actually the phone is runnin viperx4) ,..on, 2 different calbles and all pc 's usb ports i'm desperate
denny094 said:
i've tried all thoose , 3 pc's (1 with win7 the other win8) always debug mode..(actually the phone is runnin viperx4) ,..on, 2 different calbles and all pc 's usb ports i'm desperate
Click to expand...
Click to collapse
Are you on a Jellybean Sense ROM currently? Does fastboot detect the device? I had a heck of a time getting adb to see the device (but fastboot was working fine), back when the s-off method first came out, while on a Jellybean Sense ROM. I tried any number of the usual fixes, such as different drivers, different USB cords, and a different PC. The only thing that worked is using an old nandroid to go back to ICS, and adb picked up the phone right away. All I can think is that the change to MTP storage somehow messed with the adb connectivity for me (but not for others, I don't know).
BTW, reported to mods to move this thread, as it should be in Q&A.
redpoint73 said:
Are you on a Jellybean Sense ROM currently? Does fastboot detect the device? I had a heck of a time getting adb to see the device (but fastboot was working fine), back when the s-off method first came out, while on a Jellybean Sense ROM. I tried any number of the usual fixes, such as different drivers, different USB cords, and a different PC. The only thing that worked is using an old nandroid to go back to ICS, and adb picked up the phone right away. All I can think is that the change to MTP storage somehow messed with the adb connectivity for me (but not for others, I don't know).
BTW, reported to mods to move this thread, as it should be in Q&A.
Click to expand...
Click to collapse
the device is running viperxl and fastboot its working well..
commands like..dunno...
fastboot oem readcid:
your cid is : HTC_405
so he has no problems..adb yes..
i dont have any ics backup and dont know how to install it..tryied to install ruu (with sense+ and not working)
denny094 said:
the device is running viperxl and fastboot its working well..
commands like..dunno...
fastboot oem readcid:
your cid is : HTC_405
so he has no problems..adb yes..
i dont have any ics backup and dont know how to install it..tryied to install ruu (with sense+ and not working)
Click to expand...
Click to collapse
If you want to get back to ICS to see if adb works: Make a nandroid of your current setup. Then just flash any stock rooted of custom ICS ROM. This is assuming you are still bootloader unlocked.
Of course, I'm not necessarily saying this will work (get adb to work). But it worked for me, and if you are out of options, then its certainly worth a try. If it doesn't work, just restore your nandroid, and you are no worse off.
What is your hboot version?
Also, RUU will not run if the CID is incorrect. So you' ve screwed yourself from running any correct RUU.
redpoint73 said:
If you want to get back to ICS to see if adb works: Make a nandroid of your current setup. Then just flash any stock rooted of custom ICS ROM. This is assuming you are still bootloader unlocked.
Of course, I'm not necessarily saying this will work (get adb to work). But it worked for me, and if you are out of options, then its certainly worth a try. If it doesn't work, just restore your nandroid, and you are no worse off.
What is your hboot version?
Also, RUU will not run if the CID is incorrect. So you' ve screwed yourself from running any correct RUU.
Click to expand...
Click to collapse
uhmm i think the cid problem i solved i've tryied again and adb worked now must be scid.. i'll do s-off.., with all in 1 toolkit or hexeditor?
denny094 said:
uhmm i think the cid problem i solved i've tryied again and adb worked now must be scid.. i'll do s-off.., with all in 1 toolkit or hexeditor?
Click to expand...
Click to collapse
That post is really confusing, your sentence structure and punctuation is all over the place. Can you clear it up a bit and ask again?
Sent from my Evita
Yeah, not sure what was being said there. Did going back to ICS fix the adb issue, or did you find another way? So you have SuperCID now? If so, do the facepalm method to get s-off.
If you are still trying to get SuperCID, I don't think hasoon's all-in-one tool will work. Believe its looking for the AT&T CID (cws__001), so any other CID, it will fail. You'll have to use the hex edit method.
Problem is solved thanks I did s-off but I would like to ask you another question.. I installed clear rom sense 5 but the device has very low signal the radio firmware is 0.24p are there new updates to increase the quality?
Inviato dal mio HTC One S usando Tapatalk 4
I'm not sure which which radio you're referring to there. Have you updated the firmware as suggested in the CR thread?
Sent from my Evita
Hey all,
I used the 318 RUU on my hox. Now the camera wont work, it launches and the app opens but then in closes. If I try to relaunch it a toast pops up and says cant connect to camera.
Unlocked
S-off
11111111
hboot 2.14.0000
0.24p.32.09.06
Would the Super CID or the bootloader effect the camera?
stoopid2001 said:
Hey all,
I used the 318 RUU on my hox. Now the camera wont work, it launches and the app opens but then in closes. If I try to relaunch it a toast pops up and says cant connect to camera.
Unlocked
S-off
11111111
hboot 2.14.0000
0.24p.32.09.06
Would the Super CID or the bootloader effect the camera?
Click to expand...
Click to collapse
No
I would check the MD5 of the RUU if possible. If it's off, redownload and reRUU, if it still happens, it's likely a hardware issue. I think I recall reading a thread a while back with a similar issue that was not in fact hardware related however I cannot recall how it was fixed.
Just re-RUU'd, no dice same issue.
edit-Flashed CFX, camera works fine. This doesn't help with selling it on ebay though!
stoopid2001 said:
Just re-RUU'd, no dice same issue.
edit-Flashed CFX, camera works fine. This doesn't help with selling it on ebay though!
Click to expand...
Click to collapse
What is CFX? I have the same problem and have yet been able to fix.
HOXnoo8 said:
What is CFX? I have the same problem and have yet been able to fix.
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=2426919
My camera won't work on stock (3.18 RUU) but it worked on CM 10.1 before and now it works on CFX.
stoopid2001 said:
forum.xda-developers.com/showthread.php?t=2426919
My camera won't work on stock (3.18 RUU) but it worked on CM 10.1 before and now it works on CFX.
Click to expand...
Click to collapse
I flashed CFX and no dice. I will keep looking. Thanks.
Same problem here guys, camera works sometimes and sometimes just black screen. It works when I erase the camera cache or data but, after one use, the black screen again.
Ale993 said:
Same problem here guys, camera works sometimes and sometimes just black screen. It works when I erase the camera cache or data but, after one use, the black screen again.
Click to expand...
Click to collapse
Its not the "same problem" unless every single detail is exactly the same. Otherwise, you need to tell us the details.
If S-off, did you try to RUU the phone?
Is this the same across different ROMs.
redpoint73 said:
Its not the "same problem" unless every single detail is exactly the same. Otherwise, you need to tell us the details.
If S-off, did you try to RUU the phone?
Is this the same across different ROMs.
Click to expand...
Click to collapse
Yes. I have S-Off. It is the same across different ROMS, Hboots, firmwares, and TWRP. I have been trying to RUU again but cant seem to get my phone to jive with ADB. I know thats a different topic altogether but it is definitely hindering my progress. I've updated SDK, installed the Drivers from HTC Sync, and tried to point device manager to the drivers manually. Still no "Android Composite Device". Even HTC Sync Manager does not recognize the device. Fastboot does not work either. I know that I used to have everything set up correctly because I was able to S-Off, RUU, run adb commands in the past on both of my computers and no problems. Only now. Whats weird, is that android does register in device manager when i am in TWRP. Back to the subject at hand, I am not able to RUU to check if that fixes the camera. RIght now I am on the Stock Telstra NEW 5.08.841.3 UPDATE with root. TWRP 2.6.0. Hboot 2.15.
HOXnoo8 said:
Yes. I have S-Off. It is the same across different ROMS, Hboots, firmwares, and TWRP. I have been trying to RUU again but cant seem to get my phone to jive with ADB. I know thats a different topic altogether but it is definitely hindering my progress. I've updated SDK, installed the Drivers from HTC Sync, and tried to point device manager to the drivers manually. Still no "Android Composite Device". Even HTC Sync Manager does not recognize the device. Fastboot does not work either. I know that I used to have everything set up correctly because I was able to S-Off, RUU, run adb commands in the past on both of my computers and no problems. Only now. Whats weird, is that android does register in device manager when i am in TWRP. Back to the subject at hand, I am not able to RUU to check if that fixes the camera. RIght now I am on the Stock Telstra NEW 5.08.841.3 UPDATE with root. TWRP 2.6.0. Hboot 2.15.
Click to expand...
Click to collapse
You've tried other USB cables and other USB ports? adb connection issues are rather common, but not reading on USB at all (HTC Sync) is a bit more unusual.
redpoint73 said:
You've tried other USB cables and other USB ports? adb connection issues are rather common, but not reading on USB at all (HTC Sync) is a bit more unusual.
Click to expand...
Click to collapse
Yes. I have tried to OEM cable, iFrogz cable (which has always done the job), a cable I purchased from Best Buy, and an LG cable. I used front ports and back ports. Same thing. Its almost as if the last time I RUU's was the last time period that adb was working. I never did do much after that except for custom roms and upgrading to firmware 2.15. But the camera stopped working BEFORE I RUU'd. Thats why I did it in the first place.
I am at the moment trying these things with no sim card. Would that make a difference? I just downloaded new drivers from the General Thread and when I use device manager and uninstall the drivers and then point to my new ones, it says that the drivers are up to date. Still only seeing the phone as an MTP device. Im stuck. I just dont understand how my phone cannot be recognized as an adb device now when just a month ago it was good.
Little help please? Kind of a big deal.
im having the same issue....when i run RUU 3.18 firmware my camera freezes and doesnt work on stock rom. if i run RUU with older firmware i my camera works fine it only does it with 3.18. Anyone find a fix?