Database Info

Stock Rom Odex

Hi
Does anybody know where i can find One S (S4) odex stock roms for tmobile. Basically i can't get ota updates and i think my problem is that my current stock rom is deodex.

none of the develops in the One S community wants to make it.. dont know why....
the closest u get is the nandroid in the dev section.. thats what im running now...

Why not run a RUU from the Shipped ROMs thread in development section

I'd like it too actually. I tried flashing stock recovery and relocking my bootloader, but out still said tampered and still couldn't flash an ruu... I'm hoping getting all stock could help with that.

There are no RUU's for tmobile uk sadly, so i need to super cid my phone to get the international version. Also i dont know how to super cid

I found another version of the RUU for TMOUS so I'll try that in the near future and see what happens.
Because the cramp just won't go away!

Does anybody have a stock nandroid for tmobile UK?
Sent from my HTC One S using xda app-developers app

If you read the posts it says there isn't one. Just to verify I looked and I didn't see one either.
Also, after going into fastboot and flashing stock recovery I did
Code:
fastboot OEM lock
My phone rebooted I did it again and flashed the latest RUU for my phone which was TMOUS 1.84 or something like that.
That seemed to work. Now running android 4.0.4.
_______________________________________
Because the cramp just won't go away!

mylegiscramped said:
If you read the posts it says there isn't one. Just to verify I looked and I didn't see one either.
Also, after going into fastboot and flashing stock recovery I did
Code:
fastboot OEM lock
My phone rebooted I did it again and flashed the latest RUU for my phone which was TMOUS 1.84 or something like that.
That seemed to work. Now running android 4.0.4.
_______________________________________
Because the cramp just won't go away!
Click to expand...
Click to collapse
I'm just curious are you from UK or USA. I supercid my phone yesterday and tried flashing three different ruu's but none of them worked. But then again my bootloader is unlocked so I'm not sure whether locking it will help.
Sent from my HTC One S using xda app-developers app

I'm from us, but please don't hate me i didn't decide to be birthed here
I'm assuming your a tmobile UK user due to your post. I'm not really familiar as to what to do with your situation as I've never dealt with UK RUU Issues. I would assume you probably can't use any of the RUUs from anywhere else. You would think T-Mobile would have an international one out. I would probably not risk damaging your device using other carriers unless someone tells you it works. I don't see why trying a tmous RUU would harm you though. There are two versions of it out a 1.54 and 1.84 I believe. I don't know what effect itll have on your phone though so don't blame me if it bricks if you try.

Ive got a huge problem I supercid my phone last night and after that I couldn't call or text anyone as well as recieve. I even unsupercid my phone and back to the original HTC__001 cid. So can anyone give me a solution. Btw I relocked my bootloader and ran the European RUU and it worked
Sent from my HTC One S using xda app-developers app

Maybe try to run the RUU again? Or a factory reset.
_______________________________________
Because the cramp just won't go away!

No no this happened due to me trying to super cid. I just did the ruu right now. I think I need to flash a radio but not sure how to
Sent from my HTC One S using xda app-developers app

That's possible I suppose. Here is how.
After flashing your device properly, start it up and let everything run a few minutes so the ROM can get settled in, I assume you've done that already.
Next you download the radio image you need, I'm not sure which it is I don't know what your running.
Then reboot to fast boot.
Enter
Code:
fastboot flash radio radio.IMG
Then reboot your phone with
Code:
fastboot reboot
Or you can do it through a menu on the device.
Then you should have your radio set.
Someone please correct if anything is wrong.
_______________________________________
Because the cramp just won't go away!

My hboot version is 1.14.002
Radio-1.06s.50.02.27_2
I'm not sure which radio to flash, so could you please tell me?
P:S I'm on the S4 processor
Sent from my HTC One S using xda app-developers app

I'm not sure which radio you need. This is what I have.
HBOOT-1.14.004
RADIO-1.08ts.50.02.16
I googled quick, but haven't been able to find anything as of yet. Maybe check the wiki?

lonegunman0 said:
My hboot version is 1.14.002
Radio-1.06s.50.02.27_2
I'm not sure which radio to flash, so could you please tell me?
P:S I'm on the S4 processor
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Your not flashing any radio with that HBOOT.
HTC One S

Flash radio
fmedrano1977 said:
Your not flashing any radio with that HBOOT.
HTC One S
Click to expand...
Click to collapse
Are you saying there aren't any radios that i can flash? I'm actually considering sending this back to htc to see if they can fix it but im not sure if they will

lonegunman0 said:
Are you saying there aren't any radios that i can flash? I'm actually considering sending this back to htc to see if they can fix it but im not sure if they will
Click to expand...
Click to collapse
He is saying you CAN'T flash radios, new, old, it doesn't matter. Your hboot does not support it. You are SOL.

[Q] Updated to Jellybean -> Flashed custom ROM -> Have issues

So after having Jellybean updated on my Telstra One XL I decided to much around with recoveries and custom ROMs to see if I could get them running. I realised that this was going to cause issues, but I was fine with mucking around with it.
I unlocked the phone and got a recovery installed and of course the touchscreen didn't work in recovery. So I mucked around with it and managed to get ROMs installed via manual boot.img flashing and manual ROM flashing via:
Code:
adb shell recovery --update_package=/sdcard/rom.zip
My test was with CM10 and it got up and running. The only issue is that touchscreen doesn't work. Which made any progression through the setup phase impossible
If anyone has any clues as to how to get this up and going again I'm all ears.
I tried to use JET to roll back the HBOOT and try to roll back the firmware, but the RUUs wanted none of it.
Thanks in advance,
Anthony

Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135

twistedddx said:
Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135
Click to expand...
Click to collapse
No I didn't, must've missed that. Thanks, I will try that.

Didn't work with any RUU either.
EDIT: Got the RUU installed, thank you very much. I was an idiot and forgot to relock my bootloader again

I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium

Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?

DESERT.TECH said:
I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Not really relevant.
twistedddx said:
Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?
Click to expand...
Click to collapse
RUU_Evita_UL_Telstra_WWE_1.81.841.1_R_Radio_0.17a.32.09.03_2_10.85.32.16L_release_259804_signed.exe
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Tried the unbricking process, but it won't work. Going to get it replaced now.

Antonioffaxii said:
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Click to expand...
Click to collapse
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.

twistedddx said:
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.
Click to expand...
Click to collapse
I couldn't restore it in anyway, I had work so I took it with me and had it replaced.
Now I have one that works again!

[Q] HTC One X AT&T out of options

Hello, I recently received an AT&T One X and the very first thing I did with it was try to root it and all that fun stuff. After a long adventure I couldn't get the HBOOT to upgrade so I had changed the CID to HTC__001 from cws_001 (I couldn't find this CID anywhere, but I swear that's what it said) and then the bootloader was re-locked. There is no OS, there is no recovery, I've tried 10 RUU's from Asia WWE to the UK RUU's and than all the AT&T ones I can find.
Most fastboot commands come back with a "Too many Links" error which I assume is from the bootloader being locked, and I cant change the bootloader's status because the bin file I got is for the supercid.
Please help me, I am usually quite proficient with this type of stuff but I really buried myself in a hole.

Why were you trying to upgrade your hboot..? Anyways.. What hboot do you have now? Is your Cid still htc__001?
Sent from my HTC One X using xda app-developers app

exad said:
Why were you trying to upgrade your hboot..? Anyways.. What hboot do you have now? Is your Cid still htc__001?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Isn't that cid for the international version?
Sent from my HTC One X using xda app-developers app

Re
My HBOOT is 1.14.0002. I tried to upgrade it for all the newer roms and such but thats when I managed to screw everything up. Yes, it is still HTC__001 and that is the international. I've tried several WWE RUU's and all refuse to work giving me various errors..

Yeah no ruu will work because you have an international cid with an at&t phone.
You'll need to htcdev over again and pray it works.
Sent from my HTC One X using xda app-developers app

I already unlocked the bootloader, It just wont let me do anything anymore... All fastboot commands are giving me either unknown errors or too many link errors.
I just dont understand why I cant change the CID anymore! The bootloader is unlocked so i should just be able to use fastboot..

koolgshizman said:
I already unlocked the bootloader, It just wont let me do anything anymore... All fastboot commands are giving me either unknown errors or too many link errors.
I just dont understand why I cant change the CID anymore! The bootloader is unlocked so i should just be able to use fastboot..
Click to expand...
Click to collapse
You can only change the cid once with fastboot oem writecid unless you are s-off
As for fastboot not working. Are you able to flash recovery?
Sent from my HTC One X using xda app-developers app

I managed to put on twrp but I didn't make a nandroids

koolgshizman said:
I managed to put on twrp but I didn't make a nandroids
Click to expand...
Click to collapse
Flash a stock-based ICS rom and then S-OFF, then you can change your cid, or whattever you need to do

Doesn't necessarily need to be ics but yeah you get the idea. After s-off then you can ruu to update your hboot and anything else that gets updates. Bear in mind that on aosp ROMs the touchscreen won't work after you upgrade until you downgrade the touchscreen firmware.
Sent from my HTC One X using xda app-developers app

Don't you still need supercid to s-off? Or is that no longer a requirement?

Never tried with am international or cid from another carrier.. Maybe it'll work? If not he can always hex edit his cid.
Sent from my HTC One X using xda app-developers app

Thank you for the replies, the link to the Hex editing of the CID saved me. I knew that's where the CID was located but I didn't know you could dd it out of the system. By the way, I was having hard times trying to flash CM9 on there and it didn't work, neither did viper roms so I was greatly discouraged. By the way, I have no earthly clue on how to S-OFF the One X so I will probably try to look harder for that. I'm probably going to either RUU to where I was, I believe 2.2 or put on.. some rom that sounds good. Any favorites? Y'all say I can flash ICS to it if I just flash the boot.img first right? I thought that the partition sizes would cause a conflict.. Oh well, I'll give it a try

koolgshizman said:
Thank you for the replies, the link to the Hex editing of the CID saved me. I knew that's where the CID was located but I didn't know you could dd it out of the system. By the way, I was having hard times trying to flash CM9 on there and it didn't work, neither did viper roms so I was greatly discouraged. By the way, I have no earthly clue on how to S-OFF the One X so I will probably try to look harder for that. I'm probably going to either RUU to where I was, I believe 2.2 or put on.. some rom that sounds good. Any favorites? Y'all say I can flash ICS to it if I just flash the boot.img first right? I thought that the partition sizes would cause a conflict.. Oh well, I'll give it a try
Click to expand...
Click to collapse
You should be able to flash any rom so long as you fastboot flash the boot.img ics or jb.

A million thanks, well, I thanked you once, that should suffice. I'm almost set now, for a second I thought the phone would be a goner.

If you can get to bootloader your phone can be saved. Good luck, have fun.
Sent from my HTC One X using xda app-developers app

Yes, CM10.1 is now running, I'm just waiting for my gapps.. thanks again

[Q] Question about 3.4 kernel

Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?

kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
Nope, you'll probably brick doing that.

kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.

RollTribe said:
Nope, you'll probably brick doing that.
Click to expand...
Click to collapse
Yeah i figured it was a long shot, glad i asked first lol. Thanks dude!

pside15 said:
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.
Click to expand...
Click to collapse
Oh I'm sure it's not to bad, but I have no idea how to use fastboot or adb (I've lucked by without having to use either, at least to my knowledge). Plus I don't readily have a windows PC, I just want make sure I know what I'm doing before I even attempt it. I've been looking over gunnyman's adb for noobs (http://forum.xda-developers.com/showthread.php?t=1754018), I'll give it a shot sometime next week when I've worked up the courage. Thanks for the advice!

pside15 said:
There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm.
Click to expand...
Click to collapse
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.

exad said:
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.
Click to expand...
Click to collapse
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2

pside15 said:
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.

exad said:
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.
Click to expand...
Click to collapse
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.

pside15 said:
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.
Click to expand...
Click to collapse
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium

31ken31 said:
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I'm not saying it's that simple and yes, I agree about following the steps. That's why I said I wouldn't even recommend trying the newer ROMs without updating first. I have seen it work though. That's all I'm saying. Maybe those users were ignorant on exactly what they did but I'm just going on what I've read and responded to.

Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app

exad said:
Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Go to my profile and look at my quoted posts or just go back a bit in the Carbon thread. You will see where I quoted someone who was s-on and on the 1.14 hboot that flashed one of the 3.4 nightlies successfully. He was wondering if his phone was going to mess up now. That's the only specific one I remember off the top of my head but I know I've seen others as well. Like I said I'm just going by what I read. They could be completely wrong, lying, or just ignorant noobs. I live on these forums as well and have absolutely no reason to make something like this up.
Sent from my One X using Tapatalk 2

ATT ONE X cid problem. Please 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