I have superCID.
I've relocked the bootloader
I get error 140 when trying to go back to 1.73 from 1.85. What am I missing?
bootloader screen says
Tampered
relocked
security warning
What if you RUU to 1.85, which should get rid of tampered message and then try 1.73?
I've tried that before I'll try it again though
Why do you want stock? Returning this one too? I had a hell of a time with USB drivers. 1.73 and 1.82 worked flawless but 1.85 kept getting errors. Uninstalled drivers and installed htc sync and it worked. If these are the drivers you have installed then search for the naked adb drivers. One of the 2 might fix you up.
nugzo said:
Why do you want stock? Returning this one too? I had a hell of a time with USB drivers. 1.73 and 1.82 worked flawless but 1.85 kept getting errors. Uninstalled drivers and installed htc sync and it worked. If these are the drivers you have installed then search for the naked adb drivers. One of the 2 might fix you up.
Click to expand...
Click to collapse
Sorry, but I just wanted to say I love your avatar. Where did you get it?
Samsung infuse is an animal!!
nugzo said:
Why do you want stock? Returning this one too? I had a hell of a time with USB drivers. 1.73 and 1.82 worked flawless but 1.85 kept getting errors. Uninstalled drivers and installed htc sync and it worked. If these are the drivers you have installed then search for the naked adb drivers. One of the 2 might fix you up.
Click to expand...
Click to collapse
No not returning it. I just want to play with the 1.73 look at the partitions etc.
I installed HTC sync.
looks like going from 1.85 ruu to 1.73 might be working this time. I disabled HTC sync. Something I keep forgetting to do
Have you read the downgrade thread? It does require you to hex edit the mmcblk0p23 file.
nunyabiziz said:
Have you read the downgrade thread? It does require you to hex edit the mmcblk0p23 file.
Click to expand...
Click to collapse
not if you have superCID which I do have.
gunnyman said:
looks like going from 1.85 ruu to 1.73 might be working this time. I disabled HTC sync. Something I keep forgetting to do
Click to expand...
Click to collapse
spoke too soon error 140 again.
look here
http://forum.xda-developers.com/showthread.php?p=26509600.
from my HTC One X using xda premium
I just reread the thread again and I dont see where it said having super cid will excludes you from the hex editing the misc file. I may be not, if so sorry for the misdirection.
nunyabiziz said:
I just reread the thread again and I dont see where it said having super cid will excludes you from the hex editing the misc file. I may be not, if so sorry for the misdirection.
Click to expand...
Click to collapse
superCID is supposed to allow you to install any RUU isn't it?
gunnyman said:
superCID is supposed to allow you to install any RUU isn't it?
Click to expand...
Click to collapse
But there is another check that will fail without the hex edit.
nunyabiziz said:
But there is another check that will fail without the hex edit.
Click to expand...
Click to collapse
ok thanks. I'll try it tomorrow. Getting tired.
gunnyman said:
ok thanks. I'll try it tomorrow. Getting tired.
Click to expand...
Click to collapse
Any luck going to 1.82? I was able to get to that, but I haven't tried to go to 1.73.
Sent from my HTC One X using Tapatalk 2
droidiac13 said:
Any luck going to 1.82? I was able to get to that, but I haven't tried to go to 1.73.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Hadn't tried.
droidiac13 said:
Any luck going to 1.82? I was able to get to that, but I haven't tried to go to 1.73.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Same here. Just relocked and flashed from 1.85 to 1.82 without any problems. No hex edit just super CID. Haven't tried 1.73 though.
Sent from my HTC One X using xda premium
You doing this from fastboot or while the phone was booted into the OS?
Somehow R2 was appended to my software version number. I had previously initiated the RUU while booted up but this was blocking me from restoring as it thought I had a software version newer than the RUU. While in fastboot, no software version is detected and I'd imagine any RUU should work.
nunyabiziz said:
I just reread the thread again and I dont see where it said having super cid will excludes you from the hex editing the misc file. I may be not, if so sorry for the misdirection.
Click to expand...
Click to collapse
I have downgraded to 1.73 without hexedit. Supercid takes care of having to do that. Thats why its calld SUPER cid I think its a driver error. Have you tried the drivers from this thread? http://forum.xda-developers.com/showthread.php?t=1379875
Related
The update to 4.0.4 for the ATT HTC One X has arrived! Unfortunately, everytime I update, everything looks good until it restarts to begin the installation of the update procedure. It gets about a 3rd done before it stops, then shows a red triangle for about a minute and restarts back. Saying that the "update was unsuccessful". What am I doing wrong? I am rooted on 1.85. The bootloader is "relocked". Any suggestions would be great.
niceppl said:
which ruu are u trying to flash...
there isnt a ruu for 2.20 yet...
the patched ruu isnt an ruu....
the signature on it is not correct
the only way u can flash is with s-off
you can get 2.20
by ruu 1.85 then dl and copy the ota .zip someone else extracted put on sdcard
and flash it with stock recovery.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
this
niceppl said:
this
Click to expand...
Click to collapse
Thanks, but I found out the stock recovery in my recently relocked phone was gone. I flashed the RUU the way I was supposed to (1.85) and It turns out, the bootloader became "tampered" again. I have no idea how that happened. But it's all good now. Currently finishing up installing all my apps the old fashioned way since I lost root (eh, didn't need it anyway)
See my posts in the PSA thread in General. I'm rooted on 1.85 but never unlocked. My update failed exactly the same way as yours. Still no luck.
Sent from my HTC One X using XDA Premium HD. In between FCs.
Same here. Must be a root issue.
Sent from my HTC One X using Tapatalk 2
FWIW there's a 2.20 RUU on HTC.com now
If you deleted any system apps then the OTA will fail. You'll need to reinstall them or RUU back to stock before you try to update.
akvtiger said:
Same here. Must be a root issue.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
It is a root issue, rooting my phone changed the filmware version to include "R2" at the end. Not a big thing, but enough to completely f*ck up my phone when it was time to update. No more rooting for me til I gain the courage again... And root is found for 4.0.4.
Sent from my HTC One X using xda app-developers app
_MetalHead_ said:
If you deleted any system apps then the OTA will fail. You'll need to reinstall them or RUU back to stock before you try to update.
Click to expand...
Click to collapse
That must've been another problem. I tried to push google now to my phone, then i found out it sucked and took it off. I thought i put the other file back on, but i guess something went wrong.
gunnyman said:
FWIW there's a 2.20 RUU on HTC.com now
Click to expand...
Click to collapse
I didn't know that. I was looking all over for it yesterday. Thank you.
Sent from my HTC One X using xda app-developers app
Will someone post the correct 1.85 RUU for this phone, or send a link to it? Having a little trouble trying to find it. Or maybe I did?
RUU_Evita_Cingular_US_1.85.502.3_R2_Radio_0.71.32.09.12_10.86.32.08L_release_262092_signed
I'm trying to downgrade via this guide: http://forum.xda-developers.com/showpost.php?p=33914948&postcount=65
Edited the mmcblk0p23 just fine, placed it back on my phone and tried to run the RUU but it says that it wasn't able to run, which leads me to the conclusion it's the wrong RUU.
Any input would be fantastic.
Edit: just tried again and this is the error that I am getting.
Here: http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s
Here: http://forum.xda-developers.com/showthread.php?t=1670238
Or also here: http://forum.xda-developers.com/showthread.php?t=1671237
I believe that since you are editing the version number on your phone, it shouldn't matter what RUU version, as long as the CID is correct (which SuperCID should also render a moot point).
redpoint73 said:
Here: http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s
Here: http://forum.xda-developers.com/showthread.php?t=1670238
Or also here: http://forum.xda-developers.com/showthread.php?t=1671237
I believe that since you are editing the version number on your phone, it shouldn't matter what RUU version, as long as the CID is correct (which SuperCID should also render a moot point).
Click to expand...
Click to collapse
Well, quick on the draw with 3 links... I have the correct one. Now it's just a matter of finding out why it's not working. I'll look at my CID and see what's going on.
Did you reboot into fast boot and relock the boot loader after applying the edit?
Im trying this right now but my hex file is all zeros? Why is this and what should I do to resolve this?
absolutelygrim said:
Did you reboot into fast boot and relock the boot loader after applying the edit?
Click to expand...
Click to collapse
Yeah. Ran the 2.20 RUU just fine
mlaws90 said:
Im trying this right now but my hex file is all zeros? Why is this and what should I do to resolve this?
Click to expand...
Click to collapse
The place you have to edit will be on the right side, You'll find the line 0x0a0 on the left.
Myrder said:
The place you have to edit will be on the right side, You'll find the line 0x0a0 on the left.
Click to expand...
Click to collapse
Screenshot:
Is this all I do?:
mlaws90 said:
Is this all I do?
Click to expand...
Click to collapse
Yeah
Wait, that's your mmcblk0p23? That's wrong, that should have your CID and Clearimage what not above the 0x0a0 line...
Grim, what do?
Myrder said:
Yeah
Wait, that's your mmcblk0p23? That's wrong, that should have your CID and Clearimage what not above the 0x0a0 line...
Grim, what do?
Click to expand...
Click to collapse
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
mlaws90 said:
I only have the unlocked bootloader, not SuperCID, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
Click to expand...
Click to collapse
Oh, that makes sense.. I got the phone two weeks after release, and finally decided to root about 3 weeks ago-ish? so me being dumb I didn't even think to look here before I did the OTA update from AT&T. So I had to do the x factor exploit to get rooted. That might be why yours isn't like mine...? I'm not 100% sure on that one.
mlaws90 said:
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
Click to expand...
Click to collapse
That was the same way mine was. I got the 155 error. Going to run some errands after I get my phone back working again.. and give it another go later.
mlaws90 said:
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day.
Click to expand...
Click to collapse
You can't have an unlocked bootloader without SuperCID on the AT&T branded version. Or possibly another CID besides the AT&T CID, since AT&T's CID is not allowed on HTCDev.com.
Should look like this
absolutelygrim said:
Should look like this
Click to expand...
Click to collapse
But why doesnt mine look like that , can someone upload a mmcblk0p23 for me to use, if that is possible. Mine is all Zeros and I get the 154 or 155 error on RUU.
mlaws90 said:
But why doesnt mine look like that , can someone upload a mmcblk0p23 for me to use, if that is possible. Mine is all Zeros and I get the 154 or 155 error on RUU.
Click to expand...
Click to collapse
Try extracting p23 with your phone plugged into a computer and USB debugging on
I'll give this another go later tonight, If it doesn't work I'll just downgrade my hboot and leave it alone. lol.
Myrder said:
I'll give this another go later tonight, If it doesn't work I'll just downgrade my hboot and leave it alone. lol.
Click to expand...
Click to collapse
I drowngraded hboot, changed main version and then ran the RUU just now with no problems. Weird that it isn't working for you.
mbh87 said:
I drowngraded hboot, changed main version and then ran the RUU just now with no problems. Weird that it isn't working for you.
Click to expand...
Click to collapse
First time I got ahead of myself and didn't save the mmcblk0p23... The next time, idk wtf happened. I'll downgrade hboot in a bit and then try again to see what that will do.
Myrder said:
First time I got ahead of myself and didn't save the mmcblk0p23... The next time, idk wtf happened. I'll downgrade hboot in a bit and then try again to see what that will do.
Click to expand...
Click to collapse
If you tried running it over the top of 2.20 without downgrading hboot then that would be a problem too.
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!
Ok so i need help rooting and unlocking the bootloader for my At&t HTC One X my phone is currently not connected to network (if that makes a difference) So all day i've been trying to unlock the bootloader for my phone through the HTCDev site but i keep getting the error code 160 and MID not allowed. Yes I have made sure that i pasted the characters correctly but still no luck . I'm an extreme noob to this since this is my first smartphone and I'm trying to root it so I can install Jell Bean on my device. If anyone can help me solve this situation it would be extremely appreciated thanks in advance for reading Furthermore, i need a solution in rooting my HTC One X 1.73 Version 4.0.3
Make yourself a cup of coffee and read through the stickies. Att blocked the att one x from being bootloader unlocked through htcdev.com
Sent from my HTC One X using xda app-developers app
exad said:
Make yourself a cup of coffee and read through the stickies. Att blocked the att one x from being bootloader unlocked through htcdev.com
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply, so there is no way that i will be able to put custom Rom on my phone?
Shadane said:
Thanks for the reply, so there is no way that i will be able to put custom Rom on my phone?
Click to expand...
Click to collapse
I never said that
exad said:
I never said that
Click to expand...
Click to collapse
Well that's great news so how will i be able to do it? I've been trying various root methods but can't seem to get my phone rooted
http://forum.xda-developers.com/showthread.php?t=1644167
Sent from my HTC One X using xda app-developers app
exad said:
http://forum.xda-developers.com/showthread.php?t=1644167
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yea man i've done that method numerous amount of times. when i do it "adb server out of date. killing...." and "ADB didn't ACK" comes up alot not sure if that's the reason why it won't let me root
Have you installed the latest HTC Sync Version on your Computer?
If not, install it. Maybe you're just running an old driver for your phone
Kureno7 said:
Have you installed the latest HTC Sync Version on your Computer?
If not, install it. Maybe you're just running an old driver for your phone
Click to expand...
Click to collapse
Yea man i got the latest sync version and i downloaded HTC Drivers and install them as well still no luck
Shadane said:
Yea man i got the latest sync version and i downloaded HTC Drivers and install them as well still no luck
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2197018
Maybe this thread can help you
Shadane said:
Yea man i got the latest sync version and i downloaded HTC Drivers and install them as well still no luck
Click to expand...
Click to collapse
My apologies if this is silly. Do you have adb installed
Sent from my HTC One X using Tapatalk 2
open the task manager, which has adb.exe process and end (kill) that process
Then close your oneclick and re-open it.
That should fix the "ADB server didn't ACK, failed to start daemon" Message.
If that doesn't work you could try installing the lastest android SDK with the latest ADB/fastboot
There's nothing wrong with the rooting procedure. Your lack of technical knowledge is what's holding you back. If you can't troubleshoot issues like this unlocking this phone may not be for you.
I dunno what I did or anything like that. But for some reason the ONLY way I can get adb to recognize my phone is to have HTC sync actually running but minimized. If I exit it from the tray or kill application adb tells me no device found or "waiting for device" indefinitely
Sent from my HTC One X using Tapatalk 2
InflatedTitan said:
I dunno what I did or anything like that. But for some reason the ONLY way I can get adb to recognize my phone is to have HTC sync actually running but minimized. If I exit it from the tray or kill application adb tells me no device found or "waiting for device" indefinitely
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
How bizarre!
Root
exad said:
How bizarre!
Click to expand...
Click to collapse
okay so I uninstalled HTC Syn and killed adb in task manager and when i run the root file everything goes smooth i don't get any errors my phone reboots numerous amount of times but when finished and i go into my apps i don't have "superuser" i even downloaded two different root checkers from the play store however they reported i don't have root do you know how i could fix this problem?
Shadane said:
okay so I uninstalled HTC Syn and killed adb in task manager and when i run the root file everything goes smooth i don't get any errors my phone reboots numerous amount of times but when finished and i go into my apps i don't have "superuser" i even downloaded two different root checkers from the play store however they reported i don't have root do you know how i could fix this problem?
Click to expand...
Click to collapse
Yeah the exploits don't root your phone, They guve temp root to give you supercid so you can unlock the bootloader on HTCDEV. Once your bootloader is unlocked you can flash recovery, after that you can flash su or a rooted rom.
exad said:
Yeah the exploits don't root your phone, They guve temp root to give you supercid so you can unlock the bootloader on HTCDEV. Once your bootloader is unlocked you can flash recovery, after that you can flash su or a rooted rom.
Click to expand...
Click to collapse
Okay i'm a little confused now so this thread http://forum.xda-developers.com/showthread.php?t=1644167 will only give me temp root?
Shadane said:
Okay i'm a little confused now so this thread http://forum.xda-developers.com/showthread.php?t=1644167 will only give me temp root?
Click to expand...
Click to collapse
What software version does your phone have?
keeloc guilty
exad said:
What software version does your phone have?
Click to expand...
Click to collapse
My Android version is 4.0.3 and my software number is 1.73.502.1
Shadane said:
My Android version is 4.0.3 and my software number is 1.73.502.1
Click to expand...
Click to collapse
what's your hboot version in bootloader? I just want to verify.
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