After RUU Camera won't work - AT&T, Rogers HTC One X, Telstra One XL

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?

Related

Can you update hboot without updating stock ROM?

Hey guys, I just got 2 HTC Sensation 4Gs off of Craigslist, they are both still running Gingerbread. I want to root and custom rom, but I'm aware that I cannot install newer ICS+ ROMs without updateing the hboot.
My question is, is it easier to HTC Dev Unlock, root, s-off, Super CID, and THEN update the hboot. Or update the phone with the official ICS update (thus also updating the hboot) and THEN HTC Dev Unlock, root, s-off, Super CID?
I've already had experience rooting and s-off(ing) 2 ICS sensations, but don't know if I could do it easier if I don't update them first.
If it is easier to update the hboot after rooting Gingerbread, can you point me in the right direction?
Thanks.
Electriccars said:
Hey guys, I just got 2 HTC Sensation 4Gs off of Craigslist, they are both still running Gingerbread. I want to root and custom rom, but I'm aware that I cannot install newer ICS+ ROMs without updateing the hboot.
My question is, is it easier to HTC Dev Unlock, root, s-off, Super CID, and THEN update the hboot. Or update the phone with the official ICS update (thus also updating the hboot) and THEN HTC Dev Unlock, root, s-off, Super CID?
I've already had experience rooting and s-off(ing) 2 ICS sensations, but don't know if I could do it easier if I don't update them first.
If it is easier to update the hboot after rooting Gingerbread, can you point me in the right direction?
Thanks.
Click to expand...
Click to collapse
Hi,
If you intend to s-off on GB ,then, do NOT go to HTCDEV
S-off using revolutionary.
Look HERE
Everything is listed in order.
Then, update the firmware/radio HERE , using the 3.33 Universal firmware.
Then,install custom ROM.
Thanks! Exactly what I wanted. question though, is the latest 3.33 okay to use on T-Mobile? Or is there a more T-Mobile optimised version I should use?
Sent from my HTC Sensation using Tapatalk 2
Electriccars said:
Thanks! Exactly what I wanted. question though, is the latest 3.33 okay to use on T-Mobile? Or is there a more T-Mobile optimised version I should use?
Sent from my HTC Sensation using Tapatalk 2
Click to expand...
Click to collapse
Hi,
It is the same for all phones.
malybru said:
Hi,
If you intend to s-off on GB ,then, do NOT go to HTCDEV
S-off using revolutionary.
Look HERE
Everything is listed in order.
Then, update the firmware/radio HERE , using the 3.33 Universal firmware.
Then,install custom ROM.
Click to expand...
Click to collapse
It says enter Serial Number on Revolutionary IO. Does it mean the S/N beneath the battery or the IMEI? Both are getting accepted and I'm being given 2 different keys. I'm pretty confident that it means the S/N so that's what i'm going to try. Is that correct?
Electriccars said:
It says enter Serial Number on Revolutionary IO. Does it mean the S/N beneath the battery or the IMEI? Both are getting accepted and I'm being given 2 different keys. I'm pretty confident that it means the S/N so that's what i'm going to try. Is that correct?
Click to expand...
Click to collapse
Hi,
It has been a long while since I did this.
But S/N does stand for serial number.
malybru said:
Hi,
It has been a long while since I did this.
But S/N does stand for serial number.
Click to expand...
Click to collapse
Okay cool. And it doesn't seem to detect my phone. I had the drivers installed already, but no matter what mode the phone is in the Revolutionary.exe isn't finding it. I'm on Windows XP
Maybe I should just update and do it the way I've done before. :-/
Maybe I need an SD in the phone?
Electriccars said:
Okay cool. And it doesn't seem to detect my phone. I had the drivers installed already, but no matter what mode the phone is in the Revolutionary.exe isn't finding it. I'm on Windows XP
Maybe I should just update and do it the way I've done before. :-/
Maybe I need an SD in the phone?
Click to expand...
Click to collapse
Hi,
Yes,you need a sd card.
It is far easier to s-off with revolutionary,so it is worth the effort to find the correct drivers,and re-install them(and reboot the pc)
Also try different usb slots,and a different cable if you have one.
malybru said:
Hi,
Yes,you need a sd card.
It is far easier to s-off with revolutionary,so it is worth the effort to find the correct drivers,and re-install them(and reboot the pc)
Also try different usb slots,and a different cable if you have one.
Click to expand...
Click to collapse
Okay, thanks. I'll also try doing it in Linux Mint. I'll let you know if I need more help.
But one last question. In step one it says:
1. Run the revolutionary Utility you just downloaded from http://revolutionary.io/ and if it has found your device it should read
"Found your Device: HTC Sensation Z710* Applications -> Development)
It doesn't say to plug in the phone, which is a given, or what mode it needs to be in?
THEN it says to do it again but this time plug in the phone, in normal mode, and set it to HTC sync
Electriccars said:
Okay, thanks. I'll also try doing it in Linux Mint. I'll let you know if I need more help.
But one last question. In step one it says:
1. Run the revolutionary Utility you just downloaded from http://revolutionary.io/ and if it has found your device it should read
"Found your Device: HTC Sensation Z710* Applications -> Development)
It doesn't say to plug in the phone, which is a given, or what mode it needs to be in?
THEN it says to do it again but this time plug in the phone, in normal mode, and set it to HTC sync
Click to expand...
Click to collapse
Hi,
Like I said, it has been a while,and I cannot remember how the thing went.
But I do remember no great difficulty following the thread .
Do you run the utility on your pc,then,plug the phone in?
malybru said:
Hi,
Like I said, it has been a while,and I cannot remember how the thing went.
But I do remember no great difficulty following the thread .
Do you run the utility on your pc,then,plug the phone in?
Click to expand...
Click to collapse
No, I plug the phone in and then start the utility. It wouldn't find it though so I uninstalled and re-installed the drivers. But I can't restart my PC right now. In 90 minutes I can though. (watching a live stream with family)
I'll let you know if I get it working, whether through windows or linux.
Ugh, my PC is saying that USBcoinstaller.dll is missing. Any idea how to get it? I can't find it by searching google.
Maybe I have to download the android SDK. Didn't need to before when I rooted my ICS sensation a few months ago. But maybe I have to for gingerbread.
Electriccars said:
Ugh, my PC is saying that USBcoinstaller.dll is missing. Any idea how to get it? I can't find it by searching google.
Maybe I have to download the android SDK. Didn't need to before when I rooted my ICS sensation a few months ago. But maybe I have to for gingerbread.
Click to expand...
Click to collapse
Hi,
As well as installing sdk,have you tried installing the latest HTCSync?
I'm trying that to. Hopefully it'll get it working.
Sent from my HTC Sensation using Tapatalk 2
Okay, I'm having problems. I tried following [GUIDE] (For Noobs) SDK, ADB, and Drivers and now my ADB isn't working!
I tried downloading and installing the recommended SDK zip and it wasn't giving me the files he said it would, then I installed revision 9 and 15 because it said it neded them, they ended up bringing "Platform-tools" which contains another ADB.exe, and it won't let me delete it. I tried installing the latest HTC Sync and it doesn't find my phone. It still gives me the error about USBCoInstaller.dll I am going to reboot my PC but I honestly don't know what I did or how to fix it. Everytime I start any ADB including revolutionary.exe it pops open does a TON of text for a split second and then closes again. Any Suggestions after I reboot?
Edit: actually revolutionary.exe pops open and closes quickly without displaying anything.
My brother fixed it. apparently I want thinking about the fact that HTC sync can't be installed. And the driver wasn't completely installed, which he solved as well. So we're now using revolutionary.
Sent from my HTC Sensation using Tapatalk 2

[Q] Getting Error 170 while trying to RUU to 3.18...what am I doing wrong?

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.

SIM unlock didn't work, factory reset wiped everything, phone doesn't boot.

But wait, there's more.
I just exchanged an Xperia S for this HTC One S in excellent condition. It was already bootloader unloked, has TWRP only that it was sim locked. I tried the unlock.sh script (both from terminal emulator, and root explorer) then manually getting the UN_lock_code and subtracting the reversed 7 digits from the IMEI (with the added one), and even the automated app. The script kept running and never show the unlock code, and the one I got using this method wasn't accepted.
Then I thought I should to a factory reset and try again. So I reboot to bootloader, chose factory reset and now everything is wiped. No OS installed so I can't boot, TWRP won't mount USB storage so I can' flash any other rom.
Please help.
Is this a ville or the ville C2?
From your hbot, it seems like C2
42freelancer said:
Is this a ville or the ville C2?
From your hbot, it seems like C2
Click to expand...
Click to collapse
It is a C2, yes. How does that help me?
edit: Well, some good news is that I managed to be able to mount USB storage from TWRP (a simple FORMAT in windows seems to have fixed it). Any particular rom I should flash before attempting to sim unlock again?
cars ontols
zgomot said:
It is a C2, yes. How does that help me?
edit: Well, some good news is that I managed to be able to mount USB storage from TWRP (a simple FORMAT in windows seems to have fixed it). Any particular rom I should flash before attempting to sim unlock again?
Click to expand...
Click to collapse
Knowing that it is C2 will prevent you from flashing a ROM that isn't compatible with your phone. From experience, I'd go with PAC Rom. It has a ton of features, and should allow you to do anything you want. As far as SIM unlocking, shouldn't you be S-Off first?
And you formatted the phone via Windows? I've never heard of such a thing, never mind it actually fixing a problem.
But if it ain't broke, don't fix it. And your issue seems to be resolved for the most part. Regarding booting, that is.
42freelancer said:
Knowing that it is C2 will prevent you from flashing a ROM that isn't compatible with your phone. From experience, I'd go with PAC Rom. It has a ton of features, and should allow you to do anything you want.
Click to expand...
Click to collapse
How about ViperSC2? Will that do?
42freelancer said:
As far as SIM unlocking, shouldn't you be S-Off first?
Click to expand...
Click to collapse
I'm not sure, tbh, do I? But if I do, that's what I'll do first, however, I don't recall reading anywhere S-OFF being a prerequisite to sim unlocking.
42freelancer said:
And you formatted the phone via Windows? I've never heard of such a thing, never mind it actually fixing a problem.
But if it ain't broke, don't fix it. And your issue seems to be resolved for the most part. Regarding booting, that is.
Click to expand...
Click to collapse
Well yeah... oddly enough... I formatted the phone's internal storage via windows and then I was able to mount it as USB storage from recovery.
further edit: I managed to flash a rom and boot the phone.
For the sake of trying everything, I would s-off first. The easiest way is from stock right after running an RUU, without a custom recovery, No SU or busybox, and a locked bootloader. Moonshine worked for me after trying all the other methods.
I personally love the Viper ROMS. I only wish they would have kept updating the ones for the ONE S and slammed kitkat into it. It would be my daily driver. I use a ville with dirty unicorn 4.4. It's my daily driver.
Awesome that you got it mounted. Maybe that forced the drivers to reinstall properly. Did you check for fastboot and ADB functionality and visibility from the computer? You'll need both of those before attempting s-off.
Sent from my One S using xda app-developers app
---------- Post added at 07:32 PM ---------- Previous post was at 06:59 PM ----------
zgomot said:
How about ViperSC2? Will that do?
I'm not sure, tbh, do I? But if I do, that's what I'll do first, however, I don't recall reading anywhere S-OFF being a prerequisite to sim unlocking.
Well yeah... oddly enough... I formatted the phone's internal storage via windows and then I was able to mount it as USB storage from recovery.
further edit: I managed to flash a rom and boot the phone.
Click to expand...
Click to collapse
Not sure if you saw my last post before this one, I forgot to reply with your quote.
42freelancer said:
For the sake of trying everything, I would s-off first. The easiest way is from stock right after running an RUU, without a custom recovery, No SU or busybox, and a locked bootloader. Moonshine worked for me after trying all the other methods.
I personally love the Viper ROMS. I only wish they would have kept updating the ones for the ONE S and slammed kitkat into it. It would be my daily driver. I use a ville with dirty unicorn 4.4. It's my daily driver.
Awesome that you got it mounted. Maybe that forced the drivers to reinstall properly. Did you check for fastboot and ADB functionality and visibility from the computer? You'll need both of those before attempting s-off.
Sent from my One S using xda app-developers app
---------- Post added at 07:32 PM ---------- Previous post was at 06:59 PM ----------
Not sure if you saw my last post before this one, I forgot to reply with your quote.
Click to expand...
Click to collapse
adb devices lists the phone, however fastboot devices does not... it keeps waiting for device. I tried this fix for windows 8.1 but I can't get it to take the modded drivers. It says it finds them but can't install because the system supposedly cannot find the file.
That seems to be an issue with Windows 8.1. It also seems to be the only OS affecting fastboot. There is a file I used to get all of my drivers working properly, with ADB and fastboot. Fastboot is required with any S-Off attempt. I'll go scope out the file and return here.
---------- Post added at 08:04 PM ---------- Previous post was at 07:59 PM ----------
zgomot said:
adb devices lists the phone, however fastboot devices does not... it keeps waiting for device. I tried this fix for windows 8.1 but I can't get it to take the modded drivers. It says it finds them but can't install because the system supposedly cannot find the file.
Click to expand...
Click to collapse
Try this! This should work: http://forum.xda-developers.com/showthread.php?t=2588979
This is what I used last night to reinstall my drivers with working ADB and Fastboot. It also comes with a picture guide on how to fix the device detection. It's fast, easy, lightweight, and best of all, it works!
Your help is really appreciated.
I already tried this fix as well but I get the same error message. Damn system can't seem to find the file when I am pointing it to it...
I need to get some sleep now, will try more tomorrow.
Tried that and I still can't get fastboot devices to enumerate my device. Pfffft.
zgomot said:
Your help is really appreciated.
I already tried this fix as well but I get the same error message. Damn system can't seem to find the file when I am pointing it to it...
I need to get some sleep now, will try more tomorrow.
Click to expand...
Click to collapse
No sweat. I've got nothing going on later, so I'll do some research for ya! Night
OK, I managed to get fastboot working, but not S-OFF. Moonshine doesn't work, it keeps saying something needs to be fixed and that I need to read, haha funny. Thing is I followed the exact procedure and met all the prerequisites except for being on a stock ROM.
Currently I am running ViperS C2 5.1.0 baseband 16.22.30.03U_16.11.20.24_M, build number 3.19.401.101. I tried a couple RUUs but none worked. Which am I to use? What next?
zgomot said:
OK, I managed to get fastboot working, but not S-OFF. Moonshine doesn't work, it keeps saying something needs to be fixed and that I need to read, haha funny. Thing is I followed the exact procedure and met all the prerequisites except for being on a stock ROM.
Currently I am running ViperS C2 5.1.0 baseband 16.22.30.03U_16.11.20.24_M, build number 3.19.401.101. I tried a couple RUUs but none worked. Which am I to use? What next?
Click to expand...
Click to collapse
What is your carrier and CID? MAybe I have a RUU downloaded. I tend to grab them all. 2tb space, plus tons of cloud storage.
[EDIT] I also posted a thread on how to s-off, if that helps. I'll still look for the appropriate RUU.
http://forum.xda-developers.com/showthread.php?t=2652601
42freelancer said:
What is your carrier and CID? MAybe I have a RUU downloaded. I tend to grab them all. 2tb space, plus tons of cloud storage.
[EDIT] I also posted a thread on how to s-off, if that helps. I'll still look for the appropriate RUU.
http://forum.xda-developers.com/showthread.php?t=2652601
Click to expand...
Click to collapse
CID: HTC__032 And when you ask about my carrier do you mean the one I want to use? It's Vodafone Romania and so far I'm sure the phone works with Orange Romania. Other networks I haven't tried.
zgomot said:
CID: HTC__032 And when you ask about my carrier do you mean the one I want to use? It's Vodafone Romania and so far I'm sure the phone works with Orange Romania. Other networks I haven't tried.
Click to expand...
Click to collapse
I found this repository with some RUU. The last one is the most recent and the closest to your radio version. Reverting flashing this RUU should update your radio to match it. Once stock, you should have the ability to s-off and will have a new kernel. Have you tried flashing the kernel through fastboot?
42freelancer said:
I found this repository with some RUU. The last one is the most recent and the closest to your radio version. Reverting flashing this RUU should update your radio to match it. Once stock, you should have the ability to s-off and will have a new kernel. Have you tried flashing the kernel through fastboot?
Click to expand...
Click to collapse
If you mean this one then I tried that and eventually it gives error 131 CUSTOMER ID ERROR and saying it cannot update my device.
zgomot said:
If you mean this one then I tried that and eventually it gives error 131 CUSTOMER ID ERROR and saying it cannot update my device.
Click to expand...
Click to collapse
Was your bootloader UNLOCKED when you tried that update? Because RUU require that the bootloader be LOCKED before they have the ability to flash.
fastboot oem lock
if you didn't know.
Other than that, I'm at a loss. Until you find the appropriate RUU i guess
42freelancer said:
Was your bootloader UNLOCKED when you tried that update? Because RUU require that the bootloader be LOCKED before they have the ability to flash.
fastboot oem lock
if you didn't know.
Other than that, I'm at a loss. Until you find the appropriate RUU i guess
Click to expand...
Click to collapse
Nope. Bootloader is Relocked.
Now I'm facing another problem. I flashed TWRP via WinDroid HTC ONE S Toolkit and now, when I chose recovery from HBOOT, I get a red triangle with an exclamation mark.
edit: the red triangle was due to flashing TWRP on a locked bootloader. What I plan to do do now is flash this stock rom and try getting S-OFF and eventually sim unlock from there.
*fingers crossed*
further edit: apparently my cid is not supported by this rom.
zgomot said:
Nope. Bootloader is Relocked.
Now I'm facing another problem. I flashed TWRP via WinDroid HTC ONE S Toolkit and now, when I chose recovery from HBOOT, I get a red triangle with an exclamation mark.
edit: the red triangle was due to flashing TWRP on a locked bootloader. What I plan to do do now is flash this stock rom and try getting S-OFF and eventually sim unlock from there.
*fingers crossed*
further edit: apparently my cid is not supported by this rom.
Click to expand...
Click to collapse
You will have to SuperCID then. That requires S-Off most of the time. Back to stock it seems. The RUU hunt continues. I've been looking for you, just to see if I stumble upon it.
[EDIT] http://forum.xda-developers.com/showthread.php?t=2644607 TRY THE FIRST RUU HERE! This one is the same CID as your carrier. it may upgrade your radio and hboot.
42freelancer said:
You will have to SuperCID then. That requires S-Off most of the time. Back to stock it seems. The RUU hunt continues. I've been looking for you, just to see if I stumble upon it.
[EDIT] TRY THE FIRST RUU HERE! This one is the same CID as your carrier. it may upgrade your radio and hboot.
Click to expand...
Click to collapse
PROGRESS!
I managed to get S-OFF. Do I try sim-unlocking now, or is there anything else I have to do first?

[Q] ADB works for my M7, not for my friend's evita?

Hey all,
I'm trying to fix my friend's totally FUBAR'd evita, and I now can get the bootloader and boot to a really screwy CM10, but I can't do adb commands on his evita. But ADB works just fine for my M7. Not sure why this would be the case.
Any idea what's going on?
What exactly are you attempting to do? And what's wrong with the phone?
Sent from my Evita
His SD card was corrupted, so first I used the old Team Nocturnal trick to fix it. The Evita was also getting inexplicably bad reception and running an out of date twrp and CM. I updated his twrp, but his hboot is too old for recent CM builds, so I was trying to get him to s-off (he's hboot 1.14.0001, and from what I read you need to get s-off to update the hboot). I was able to run some commands from fastboot USB, in spite of the fact that adb devices didn't return anything for his phone (did for mine).
But the s-off tool I found requires that I can run commands from within booted android, hence the problem.
My end goal is to get the Evita to a fresh install of CM11, in hopes the the updated software will fix some of the issues he's had with the thing.
Do you have usb debugging turned on on the Evita?
Sent from my Evita
timmaaa said:
Do you have usb debugging turned on on the Evita?
Sent from my Evita
Click to expand...
Click to collapse
Yes I do. I found some threads where people talked about toggling that multiple times before they got it to take, but that didn't work on this device.
You could try uninstalling all drivers from your PC, reinstalling HTC Sync Manager, and connecting only the Evita.
Sent from my Evita

[Q] Cannot soff, devunlock or anything else

Hi guys!
First of all thank you for reading.
I'm probably in my 3rd day lurking around every possible forum and thread looking for an answer to my similar problem but have yet to find one.
I used to have a sensation xe but I kinda smashed the digitizer to bits. before that the was battery swollen and the back case pretty damaged (it survived a 120 kph gps reading of an rc car before going end over end across a parking lot). Meanwhile I got an Htc One, which is superb and I kinda forgot about the old gal.
A few days back I found a guy selling a sensation for spares (the mobo was fried on his) so I just bought that (for 20 euros) and figured all I needed to to was a mobo transplant and then have a nice almost new sensation.
But obviously the digitizer is not calibrated. I found the forum with the tutorial on that but it requires super CID and Soff. Cannot do either of them.
Since the mobo has been replaced the devunlock didn't work. Cannot, for the love of me succeed with the junopunutbear soff with the wire trick. Tried it on a ubuntu live cd, all goes well up until the wire trick. On a side note, I design and build 3d printers for a living, I might be a noob in the android department but that's about it. Even tried an automatic timed relay to do the two wire taps and still nothing. Obviously, it's not working on windows, I found the kgs1992 tool which requires a version of controlbear for windows which I cannot find (found one but it doesn't recognise it when I put it in the tools folder).
tl;dr
Cannot devunlock, cannot soff, nothing. Could I possibly try changing the IMEI so that i can maybe just maybe devunlock it first? I tried putting the mobo back in the old phone, still powered up but didn't recognize the token. I'm pretty much stuck right now.
Any help would be highly appreciated and if you read the whole thing, kudos to you for standing my chatter !
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
rzr86 said:
i sent you a pm
also you can follow this guide which avoids wire trick
http://forum.xda-developers.com/showthread.php?t=2751187
Click to expand...
Click to collapse
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
elktw said:
Hi mate!
Thank you so much for your reply!
Unfortunately, rumrunnes told me to f myself lol, an error about not finding an unsecure kernel I guess, too frustrated to remember what the error was after finally finding a piece of software which seemed to do something.
Will try with the link you sent me and will come back with results!
Click to expand...
Click to collapse
did it tell you to be rooted first?
rzr86 said:
did it tell you to be rooted first?
Click to expand...
Click to collapse
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
elktw said:
That it did, but I was under the assumption (well all the guides I read) that you need to be devunlocked in order to root it. which I can't do. Am I missing something or is this a vicious circle ?
Click to expand...
Click to collapse
just use the temproot.bat file from juopunutbear thread
then run rumrunner again
it is mentioning also in rumrunner thread
Stuck on confirm Unlock bootloader
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
culler said:
Ok, my phone got really messed up with TWRP format bug.
Since then, I have tried RUU, different recoveries and finally got stuck with Relocked, S-ON, no ROM, no ADB on my Sensation.
When i try to unlock via Unlock_code.bit i used earlier i am able to send it via fastboot to phone where it prompts me for a choice Yes/No.
And here is funny part.
I can select No with my power button which reboots my phone and shows white screen with bootloader after it since there is nothing on it.
But, when i press Volume up and select Yes option and Power button to confirm it, nothing happens. Actually it freezes phone and i have nothing else left to do except pulling out battery and booting to bootloader.
Since it is some kind of alive, I'm sure there is some way to revive it but I guess I'm kinda not seeing right steps to unlock it, s-off again, and custom recovery and wait for twrp team or shantur to find a sollution to fix corrupted partitions.
Can you help me with unlocking?
What logs do you need?
Click to expand...
Click to collapse
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
elktw said:
Well, i can certainly try and tell you what I did. Basically listen to the wonderful advice of @rzr86. Assuming you have tried many tools, you probably have the temproot utility. I just used that and Rumrunners, no wire trick no nothing, those were pretty straightforward and I finally managed to soff and supercid it. Afterwards I just installed 4ext recovery and was finally able to install whatever custom rom I wanted.
My problem however is now a different one. Cannot calibrate the touchscreen using the 58diag file. I'm using cgmod11 and if I run the calibration file, it gets stuck in bootloader. Standard RUU and it does nothing at all for the touchscreen. I'm pretty much stuck and out of ideas.
Aaaanyway, try rumrunners with temproot and get back to me with the results !
Click to expand...
Click to collapse
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
culler said:
Did you had access to rom and adb to run Rumrunners utility? I have only access to bootloader and when i try to run it it hangs waiting for ADB.
Also, I'm stuck on unlock bootloader screen so probably have corrupted memory because I can't unlock it. :/
Click to expand...
Click to collapse
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
rzr86 said:
do you have adb/fastboot installed?
did you enable usb debugging mode from settings?
use usb 2.0 ports not 3.0
also what windows OS do you have?
Click to expand...
Click to collapse
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
culler said:
I'm on Windows 8.1 64-bit, but also tried Windows 7 32-bit and Ubuntu 13.04 both 32 and 64bit.
I also tried both USB2.0 and USB3.0 ports.
Like i said, I cant enable USB debugging mode in settings since i don't have ROM now, device is empty, except bootloader without recovery and I can't find way to install since I'm Relocked and S-on.
Click to expand...
Click to collapse
S-OFF requires a working rom so you can't use S-OFF method
with windows 8.1 you will face connectivity issues
type in search box how to set up adb/fastboot in windows 8 but the point is that you don't have enabled usb debugging mode
so i am not sure if you will have any success
by the way what version of TWRP did you flash?
the latest? (2.7.0)
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
culler said:
I was using TWRP 2.7.0.0 which corrupted my partitions so i tried various recoveries to fix the situation without success.
So I tried to RUU and it also failed.
Somewhere along the way of trying to revive my phone, i used fastboot oem lock and now i somehow have S-ON device which is RELOCKED and I have no custom recovery. I can't even access HTC recovery now.
When i try fastboot flash unlocktoken Unlock_code.bin from HTCDev it prompts me with screen to choose YES to unlock or NO to unlock.
When i choose YES with Volume button and press Power button to confirm, device freezes and stays like that forever, or until I remove battery.
Selecting no reboots device and brings me back to bootloader.
*** RELOCKED ***
*** Security Warning ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Mar 2 2012,18:14:34
Click to expand...
Click to collapse
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
rzr86 said:
i thibk you are stuck mate unfortunately
did you try unbricking project or jtag method?
Click to expand...
Click to collapse
I tried unbricking project but it hangs on start with connecting to device or waiting for device.
As I understood, it needs to access ADB which i cant succeed.
I dont have JTAG equipment so it goes to some service to see if they could repair it.
It's such a great device, i don't want to lose it so soon

Categories

Resources