hello XDA. I appologize if i am breaking rules but i dont know what else to do with my phone.
I recently bought an AT&T X. it had the 2.20 at&t firmware installed. i managed to root it and supercid it and unlock bootloader. however, ever since then, i cannot update thru RUU. i was updating to 2.14 hboot to get facepalm s-off.
writing zip ...
<bootloader> adopting the signature contained in this image...
<bootloader> zip header checking...
<bootloader> zip info parsing...
FAILED <remote: 99 unknown fail>
i tried downloading the OTA and made sure its AT&T software as i do not have s-off yet. I have flashed stock recovery (i had twrp installed after i rooted and supercid) and navigate to OTA files but i get this.
mount SDCARD failed 1 times
mount SDCARD failed 2 times
mount SDCARD failed 3 times
mount SDCARD failed 4 times
mount SDCARD failed 5 times
i chose apply from phone storage and i get:
invalid operation
rebooting...
also i ran JET and successfully downgraded hboot to 1.09 cuz i read it not all parts of s-on were implemented, so i thought i could obtain s-off that way.
i have searched all over xda and google. i do as much research as i can first.
Whoa, where are you getting your information? Stop what you're doing. Running the jb RUU while s-on and SuperCID is going to brick your phone. You're lucky it's failing.
What makes you think you need to update it to get s-off? Have you attempted the Facepalm procedure yet?
Sent from my Evita
timmaaa said:
Whoa, where are you getting your information? Stop what you're doing. Running the jb RUU while s-on and SuperCID is going to brick your phone. You're lucky it's failing.
What makes you think you need to update it to get s-off? Have you attempted the Facepalm procedure yet?
Sent from my Evita
Click to expand...
Click to collapse
My bad. Wat happened was i successfully rooted while on 2.20 and proceeded to flash the zip indicated by facepalm s-off thread. thats when i started getting the error 99. i checked cid and made sure it was 11111111, which is required by facepalm s-off. now no RUU's work.. i setting the cid back to its original CWS__001 and ran updated RUU but still got the same errors.
i forgot to mention that in the first post. i know RUU while s-off and scid bricks it.
How many times did you try Facepalm, and got error 99? It seems some folks have gotten error 99, and just ran it again.
Bootloader needs to be relocked to run RUU with s-on. Did you relock the bootloader?
redpoint73 said:
How many times did you try Facepalm, and got error 99? It seems some folks have gotten error 99, and just ran it again.
Bootloader needs to be relocked to run RUU with s-on. Did you relock the bootloader?
Click to expand...
Click to collapse
i ran it multiple times. i saw a thread i forgot where to find it. i looked thru pages of different threads and i found one that says if u get error 99 just run it again till it flashes. it never flashed for me. i grew a bit impatient and stopped trying. :cyclops:
i tried relocking once but didnt work. i didnt try too much while relocked ill try again when i get the chance.
hijodedios51206 said:
i ran it multiple times. i saw a thread i forgot where to find it. i looked thru pages of different threads and i found one that says if u get error 99 just run it again till it flashes. it never flashed for me. i grew a bit impatient and stopped trying. :cyclops:
i tried relocking once but didnt work. i didnt try too much while relocked ill try again when i get the chance.
Click to expand...
Click to collapse
There are a couple of solutions to the error 99 problem strewn throughout the Facepalm thread, you can't go through more than a few pages without seeing me mention the solutions. Plus there's another s-off method called Rumrunner that you could have tried. You've kinda taken a step backwards by changing your CID back to stock.
Anyway...
What do you mean you tried relocking but it didn't work? Exactly what didn't work?
timmaaa said:
There are a couple of solutions to the error 99 problem strewn throughout the Facepalm thread, you can't go through more than a few pages without seeing me mention the solutions. Plus there's another s-off method called Rumrunner that you could have tried. You've kinda taken a step backwards by changing your CID back to stock.
Anyway...
What do you mean you tried relocking but it didn't work? Exactly what didn't work?
Click to expand...
Click to collapse
i mean i tried relocking to run RUU but still got error 99. i still have supercid currently. it got to the point i cannot write cid anymore. bootloader simply freezes when i send command to write cid. im not at my computer so ill post cmd's output when i get home. i tried both s-off methods.
hijodedios51206 said:
i tried relocking once but didnt work.
Click to expand...
Click to collapse
The RUU will never run with an unlocked bootloader and S-on. So there is your answer right there.
redpoint73 said:
The RUU will never run with an unlocked bootloader and S-on. So there is your answer right there.
Click to expand...
Click to collapse
alrite ill try it again. ill post the results when i do. thanks.
hijodedios51206 said:
alrite ill try it again. ill post the results when i do. thanks.
Click to expand...
Click to collapse
just be careful of your steps. like the usual supercid + s-on + ruu = brick combo lol
pandasa123 said:
just be careful of your steps. like the usual supercid + s-on + ruu = brick combo lol
Click to expand...
Click to collapse
ill do my best thank u.
hijodedios51206 said:
i mean i tried relocking to run RUU but still got error 99. i still have supercid currently. it got to the point i cannot write cid anymore. bootloader simply freezes when i send command to write cid. im not at my computer so ill post cmd's output when i get home. i tried both s-off methods.
Click to expand...
Click to collapse
hijodedios51206 said:
alrite ill try it again. ill post the results when i do. thanks.
Click to expand...
Click to collapse
You said earlier that you had set the CID
back to stock didn't you? If that isn't the case I'm not sure why you wrote that, you need to provide accurate information otherwise it's almost impossible to help you.
Forget about relocking the bootloader, just find the solution for the error 99 problem in the Facepalm thread and get s-off. It's the easiest solution.
Sent from my Evita
Ok i relocked bootloader and ran RUU and it worked thanks. Facepalm s-off did not work for me again same error 99 so i ran rumrunner's s-off. it worked. as i type i am flashing ruu again to clear the tampered flag. thanks for the help.
Related
First of all: I tried to find some useful info on the web to solve the problem... But if u guys got some useful links -ยป give it to me
Okay. My Ds is on hboot 2... Bootloader is unlocked with htcdev... And s-on...
I am sick of always flashing boot.IMG after flashing a Rom with 4ext... So my question is: is there a way to get s-off to "easily" install Roms without downgrading hboot..?
Sent from my HTC Desire S using XDA
Check this out:
forum.xda-developers.com/newreply.php?do=newreply&p=23771478
Saipro said:
Check this out:
forum.xda-developers.com/newreply.php?do=newreply&p=23771478
Click to expand...
Click to collapse
doesn't really help me, sry...
@rizmdee
Your only option is to downgrade to a older hboot, here a two threads
http://forum.xda-developers.com/showthread.php?t=1399331
http://forum.xda-developers.com/showthread.php?t=1443636
Once downgraded you can s-off with revolutionary, have a look here in section 1.
foX2delta said:
@rizmdee
Your only option is to downgrade to a older hboot, here a two threads
http://forum.xda-developers.com/showthread.php?t=1399331
http://forum.xda-developers.com/showthread.php?t=1443636
Once downgraded you can s-off with revolutionary, have a look here in section 1.
Click to expand...
Click to collapse
how to >without< unlocking with htc dev.... my device is allready unlocked, so i don't really think it will work...?
It will work too. You've got same hboot 2.xxx and are ever s-on with the same firmware . Don't forget to relock your bootloader using fastboot before flashing RUU.
fastboot oem lock
The only difference is that HTC now know you've unlocked your bootloader and can void your warranty if something goes wrong.
Sent from my Desire S using xda
@rizmdee
Just do it already and stop shooting things down. I understand that you are already unlocked, but if you took the time you would see that people that have unlocked have used it, you will only need to "fastboot oem lock" to install the RUU, READ and it will all be clear.
Also if you want to get into the details, then yeah if you are unlocked and have rooted or have a rooted rom, I assume you are, then just jump to changing your misc version cause you already have root #, no need for temp root, but for you I suggest you just follow it cause you will confuse yourself, .
Also just make a goldcard for the hell of it, casue I am unsure if you have a unbraded phone.
@foX2delta:
I tried it before I unlocked with htc-dev and it didn't work... so I#m not really sure
and does it work, if I got allrdy flashed custom rom (primo-s 1.3)? And if not: can i re-unlock with "fastboot oem unlock" ?
EDIT: my device ain't branded... deviceinfo-app says htc-europe...
Thanks a lot pplz... ill try and post again...
foX2delta said:
@rizmdee
Just do it already and stop shooting things down. I understand that you are already unlocked, but if you took the time you would see that people that have unlocked have used it, you will only need to "fastboot oem lock" to install the RUU, READ and it will all be clear.
Also if you want to get into the details, then yeah if you are unlocked and have rooted or have a rooted rom, I assume you are, then just jump to changing your misc version cause you already have root #, no need for temp root, but for you I suggest you just follow it cause you will confuse yourself, .
Also just make a goldcard for the hell of it, casue I am unsure if you have a unbraded phone.
Click to expand...
Click to collapse
misc_version worked...
oem lock worked...
BUT: now im in my bootloader and can't "oem unlock" -> command error!
*** RELOCKED ***
*** SECURITY WARNING ***
my device doesn't boot... PLZ HELP
@rizmdee
Run the 0.98 RUU now.
0.98 ruu? not 1.28 or 1.47?
EDIT: ah sry... doesnt work... error 131
@rizmdee
Yes 1.28 or 1.47
Yip, I told you, MAKE goldcard, remember?
Run the fastboot command "fastboot getvar all" remove yout imei from your post.
You will now have to make a coldcard on your PC (not sure if you can use another phone)
Check here, kashoulis post 11 and you can also check here
but the device is not branded... crappy...
ok ill take a look...
what does getvar all do?
crap: -> cidnum: O2___102
so i cant unlock my bootloader again?
@rizmdee
Yip, see the CID O2__102, means your phone is O2 branded.
I think, not sure though, you can try this RUU. I think, judging by its size/data its a 0.98 hboot (O2_UK_1.31.206.1), but I am pretty sure.
SO give that one a try, if that fails you WILL have to make a goldcard.
foX2delta said:
@rizmdee
Yip, see the CID O2__102, means your phone is O2 branded.
I think, not sure though, you can try this RUU. I think, judging by its size/data its a 0.98 hboot (O2_UK_1.31.206.1), but I am pretty sure.
SO give that one a try, if that fails you WILL have to make a goldcard.
Click to expand...
Click to collapse
Okay i used to "fastboot flash unlocktoken Unlock_code.bin again and now my device is *** UNLOCKED *** again... holy crap i thought i won't get it !
okay... the next time ill try it -> GOLDCARD FIRST!!! thanks a lot foX2delta...
it's just like: holy crap I wanna be s-off xD
I am still sure the above mentioned RUU will downgrade you.
first i need to calm down, my friend
but I still want an s-off-device so I'll try it out next time and post the results
I tried the RUU mentioned above several months ago, and it indeed works for O2-branded DS, which the OP obviously has.
Jack_R1 said:
I tried the RUU mentioned above several months ago, and it indeed works for O2-branded DS, which the OP obviously has.
Click to expand...
Click to collapse
so now u got s-off with that ruu?
Ok, so I installed Cleanrom 6 and flashed Elemental 6.0(I know it's experimental, I should have been prepared for something like this). I went into recovery(CWM) for something and instead of getting into recovery it just showed cwm logo and immediately rebooted to the splash screen and stayed there. I then tried to reboot several times into recovery and the rom, only resulting in the same thing. SOO while in bootloader I decide "hey I'll just run the 2.20 ruu and everything will be ok.". Well, I ran fastboot oem lock and it said it failed but now the bootloader says RELOCKED. Now, having relocked, the RUU program STILL can't detect my phone. Then I realize, I don't have the Unlock_code.bin anymore. So now I'm stuck in bootloader, (somewhat)relocked, and have absolutely no idea what to do next. Oh and I have S-OFF if that helps.
Thanks for taking the time to read that wall of text(hopefully), Does ANYONE have an idea of what I can do next? I sincerely appreciate any help I can get.
Thanks
Ouch. I've done stuff like this, so I'll be nice. This is what happens when something goes wrong and you panic and start trying a lot of stuff without thinking it through.
Does adb devices detect the phone? You should be able to get another unlock token by going back to htcdev, assuming you're still supercid. Try that before running the RUU.
iElvis said:
Ouch. I've done stuff like this, so I'll be nice. This is what happens when something goes wrong and you panic and start trying a lot of stuff without thinking it through.
Does adb devices detect the phone? You should be able to get another unlock token by going back to htcdev, assuming you're still supercid. Try that before running the RUU.
Click to expand...
Click to collapse
Thanks so much for the reply, Yeah I'm still SuperCID and I'll try that. I am supposed to be in bootloader for the RUU to detect my phone, right? and when it "relocked" it said
Code:
C:\ADB>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.938s
Again, sorry. I know this was REALLY dumb. I just panicked. Thanks for taking the time to help.
Are you s-off or not? You can run a ruu not being in bootloader, but once you relock, you can't boot up without running the ruu unless you're s-off.
If you're s-on, proceed very carefully. People with s-on and supercid have bricked running the latest ruu.
iElvis said:
Are you s-off or not? You can run a ruu not being in bootloader, but once you relock, you can't boot up without running the ruu unless you're s-off.
if you're s-on, proceed very carefully. People with s-on and supercid have bricked running the latest ruu.
Click to expand...
Click to collapse
I'm S-OFF. I guess I just got cocky and figured WELL I'M S-OFF SO I'LL JUST TRY EVERYTHING HURR DURR lol. But yeah I'm s-off.
He said he's s-off. So just get a new unlock code from HTC dev and reunlock and reinstall cwm or twrp and flash cleanrom again
Sent from my VENOMized HoxL
jacobas92 said:
I'm S-OFF. I guess I just got cocky and figured WELL I'M S-OFF SO I'LL JUST TRY EVERYTHING HURR DURR lol. But yeah I'm s-off.
Click to expand...
Click to collapse
If you're s-off, you're fine. Just get a new unlock code and you can flash what you want.
iElvis said:
If you're s-off, you're fine. Just get a new unlock code and you can flash what you want.
Click to expand...
Click to collapse
Ok, thanks guys. I REALLY appreciate the help. It's booting fine now. I guess the only problem now is why it won't get past the first 3 seconds into booting to recovery or the rom. I had also flashed multiple versions of TWRP but still had the same problems. I'll just shut it down for an hour or 2 and try again later.
fastboot erase cache
You switched from CWM to TWRP and need to clear the cache.
iElvis said:
fastboot erase cache
You switched from CWM to TWRP and need to clear the cache.
Click to expand...
Click to collapse
AH. Wow. I would hit thanks again but it seems I've hit my limit. I guess the rom wouldn't boot cause I had been undervolting. It's strange, I only undervolted to 825 and it usually only gets unstable around 800. Plus, I was at stock clock speeds. Oh well. Guess I'll be trying flars bulletproof kernel. lol I NEED s2w.
Thanks again for all the help. You guys are awesome.:good:
jacobas92 said:
AH. Wow. I would hit thanks again but it seems I've hit my limit. I guess the rom wouldn't boot cause I had been undervolting. It's strange, I only undervolted to 825 and it usually only gets unstable around 800. Plus, I was at stock clock speeds. Oh well. Guess I'll be trying flars bulletproof kernel. lol I NEED s2w.
Thanks again for all the help. You guys are awesome.:good:
Click to expand...
Click to collapse
My phone doesn't like undervolting at all. Bulletproof is a great way to go.
Sent from my HTC One XL
area51avenger said:
He said he's s-off. So just get a new unlock code from HTC dev and reunlock and reinstall cwm or twrp and flash cleanrom again
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
If he's s-off he doesn't need to relock or unlock bootloader right? At least I didn't when I ruu'd back to stock while s-off.
Sent from my Elemental Venomized S-off HTC One XL
majortaylor said:
If he's s-off he doesn't need to relock or unlock bootloader right? At least I didn't when I ruu'd back to stock while s-off.
Sent from my Elemental Venomized S-off HTC One XL
Click to expand...
Click to collapse
Its all good now they helped me. But to answer your question, I do know that even with s-off there are a few if not all fastboot commands that write to certain partitions that require an unlocked bootloader (at least from my experience).
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Bump
Sent from my One S using XDA Premium 4 mobile app
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
bump
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.
Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.
pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!
So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks
pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755
[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.
hello everyone, android user and my device s-off in the first year I want to do but how to do it without the support of htcdev? Is there a program available? When I unlock my device also has root? Am I going to root sturdy at the same time to s-off? I just want to get rid of device applications that official. 5 4.2.2 installed on my device, this device can sense it possible to root for?
Thank you.
I think you're confused as to what s-off is and unlocking is, they're two entirely different things. You don't use htcdev to get s-off. You use htcdev to unlock your bootloader, and no you cannot unlock your bootloader without htcdev. Unlocking your bootloader doesn't give you root, after unlocking the bootloader you must install a custom recovery and then you can gain root. After gaining root you can get SuperCID and then you can get s-off. If all you want to do is remove some system apps, then you'll just need to unlock the bootloader, install a custom recovery, and install root.
Sent from my Evita
You don't need s-off to delete bloatware (pre-installed apps). Just use HTCDev.com to unlock the bootloader. Then install custom recovery, then either flash SU or a rooted ROM to get root.
The process to s-off is simple (see Facepalm method in the Original Android Development subforum). However, it requires SuperCID. Since the CID is protected on Sense 5, you will not be able to SuperCID (and therefore S-off).
But as already mentioned, you don't need S-off to root and delete bloatware.
I'm at a loss and somewhat confused.
I read in one place that I need to s-off to update my radio, but in order to do that I need super-cid.
so I'm trying to change my cid from ROGER001 to 11111111.
Now I'm reading that I can s-off without super-cid? All I'd like to do is update my radio and kernel so my phone stops losing signal and stops rebooting. I should also mention that I already went to htcdev and unlocked my bootloader.
What I see in fastboot:
TAMPERED
UNLOCKED
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Viper Xl 4.2.0(amazing Rom btw)
HTC Sense 5.0
I have tried the script, it failed, manual method, that failed.
manual method gets me this result after I fastboot oem readcid(ok), fastboot oem writecid 11111111
... INFO elite_init_sd, SD card already power on
INFOsdhw_7xxx_open: id=0
INFO[SD_HW_ERR] SD: No device attached
INFO902910 902E20
FAILED (status read failed (No such file or directory))
I'd like to resolve this as my signal stops, and device reboots randomly.
telaphoneguy said:
Now I'm reading that I can s-off without super-cid?
Click to expand...
Click to collapse
Nope, wherever you read that, its completely incorrect.
It says right in the s-off method instructions, in big bold print that SuperCID is required: http://forum.xda-developers.com/showthread.php?t=2155071
If you are having trouble with s-off, the other solution to random reboots on Sense 5 is to install the Beastmode kernel.
Release the hounds!!
Sent from my One X using XDA Premium 4 mobile app
KungFuCracka94 said:
Release the hounds!!
Click to expand...
Click to collapse
I actually started to type "as mentioned in a bazillion different places" after my Beastmode statement in the previous reply. But I decided to be nice!
I checked out this link again: http://forum.xda-developers.com/showthread.php?t=1952038
i still get an error, it fails on step 6 with message [-] Failed.
I'll give beastmode another shot, i've tried it before, no success.
telaphoneguy said:
I checked out this link again: http://forum.xda-developers.com/showthread.php?t=1952038
i still get an error, it fails on step 6 with message [-] Failed.
I'll give beastmode another shot, i've tried it before, no success.
Click to expand...
Click to collapse
The x-factor exploit fails since its looking for the AT&T CID. For other CIDs, you need to edit it manually using the hex edit method.
If you have trouble with installing Beastmode, I think some folks have had to install Beastmode 2.0 before installing 3.5.
After many attempts, boot loops beastmode reloaded 3.5 finally took.
So now I need to ask if I need s-off, i've done everything except upgrade my radio.
I'll only update my radio if the antenna drops keeps dropping out.
Well, radio went out, no reboots yet, I'll see what else I can try.
no i want to only rooting device, this video help me ? cause title for htc one."but my device hox"
www.youtube.com/watch?v=kJYAS2KN17Y&list=WL2E6DAD3D0702FB02
No it won't work, it's not for this phone. Only ever use guides specifically for this device or you could brick it. As I've already told you, you absolutely cannot root this device without unlocking the bootloader through htcdev first. I'm not sure why you're still searching for ways to do it, they do not exist. There's no point in coming here for advice if you don't even listen to the answers you're given.
Sent from my Evita
timmaaa said:
I think you're confused as to what s-off is and unlocking is, they're two entirely different things. You don't use htcdev to get s-off. You use htcdev to unlock your bootloader, and no you cannot unlock your bootloader without htcdev. Unlocking your bootloader doesn't give you root, after unlocking the bootloader you must install a custom recovery and then you can gain root. After gaining root you can get SuperCID and then you can get s-off. If all you want to do is remove some system apps, then you'll just need to unlock the bootloader, install a custom recovery, and install root.
Sent from my Evita
Click to expand...
Click to collapse
Tnx so much if i think rooting need to s-off but you say "thats two entirely different" .. then why people use to s-off? for change rom ? and i find this video for root its working for my hox ? or only working htc one.. https://www.youtube.com/watch?v=kJYAS2KN17Y&list=WL2E6DAD3D0702FB02 again tnx. sorry for english
timmaaa said:
No it won't work, it's not for this phone. Only ever use guides specifically for this device or you could brick it. As I've already told you, you absolutely cannot root this device without unlocking the bootloader through htcdev first. I'm not sure why you're still searching for ways to do it, they do not exist. There's no point in coming here for advice if you don't even listen to the answers you're given.
Sent from my Evita
Click to expand...
Click to collapse
some people say me "when using htcdev for unlock your warranty get void" thats true ?
Absolutely nowhere within this forum does it say you need s-off to root, because you don't. I've already told you that. I can't view that video for some reason but unless it specifically says it's for the Evita don't use it. All you need is in the Everything Evita link in my signature, do not get information anywhere else, XDA is the only place you need to look.
As I've already told you, if you want to root you need to unlock your bootloader and install a custom recovery first. In the link I mentioned there are guides on how to do this, you need to follow the guide that pertains to your current firmware version.
Sent from my Evita
timmaaa said:
No it won't work, it's not for this phone. Only ever use guides specifically for this device or you could brick it. As I've already told you, you absolutely cannot root this device without unlocking the bootloader through htcdev first. I'm not sure why you're still searching for ways to do it, they do not exist. There's no point in coming here for advice if you don't even listen to the answers you're given.
Sent from my Evita
Click to expand...
Click to collapse
timmaaa said:
Absolutely nowhere within this forum does it say you need s-off to root, because you don't. I've already told you that. I can't view that video for some reason but unless it specifically says it's for the Evita don't use it. All you need is in the Everything Evita link in my signature, do not get information anywhere else, XDA is the only place you need to look.
As I've already told you, if you want to root you need to unlock your bootloader and install a custom recovery first. In the link I mentioned there are guides on how to do this, you need to follow the guide that pertains to your current firmware version.
Sent from my Evita
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1732980 i searched someone info for s-off "s-off, hboot and radio flash only happens if I need to make" sorry i ask much question cause im noob; then give me root link for sense 4.3.3 and hasoon2000's working for me ?
What are your bootloader details?
Sent from my Evita
Cid: htc_m27; Softwarenumber:4.18.401.2 , radio: .51204.167.31 hboot: 1.72.0000 s-on RL htc one x
You're not even in the right forum, this is the HTC One XL / at&t One X (Evita) forum. You need to ask in the HTC One X forum. They're different phones.
Sent from my Evita
As the subject says, how can I completely get rid of 4ext? I've uninstalled it from my phone, but any time I boot into recovery, 4ext still starts up. At a loss as to what to do.
Dan33185 said:
As the subject says, how can I completely get rid of 4ext? I've uninstalled it from my phone, but any time I boot into recovery, 4ext still starts up. At a loss as to what to do.
Click to expand...
Click to collapse
only with stock rom(RUU.exe) you can get rid of 4ext recovery
it restores stock recovery
rzr86 said:
only with stock rom(RUU.exe) you can get rid of 4ext recovery
it restores stock recovery
Click to expand...
Click to collapse
Actually u can use fastboot commands.
Type -
fastboot erase recovery
EDIT: @op, i must ad tho it erases the recovery completely, and if u want stock then only the ruu like rzr86 says can do it.
I in the process of trying to do a RUU recovery, but I'm not sure which one to use. All I can find are ones for Europe or Asia, I am in the US.
Dan33185 said:
I in the process of trying to do a RUU recovery, but I'm not sure which one to use. All I can find are ones for Europe or Asia, I am in the US.
Click to expand...
Click to collapse
what firmware do you have and what cid
are you on S-OFF or S-ON?
3.33.401.6, S-Off. Not sure what CID or how to find it. I think I've found the right one, downloading this one now:
Official RUU-Pyramid-ICS-hTC-Europe-3.33.401.5 RUU-Pyramid-ICS-hTC-Europe-3.33.401.6-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-266171 signed.exe
From here: http://htc.vi8.info/Stock-RUU/
Already tried a different one and got an error message saying it couldn't install, hopefully this one gives me better luck.
Dan33185 said:
3.33.401.6, S-Off. Not sure what CID or how to find it. I think I've found the right one, downloading this one now:
Official RUU-Pyramid-ICS-hTC-Europe-3.33.401.5 RUU-Pyramid-ICS-hTC-Europe-3.33.401.6-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-266171 signed.exe
From here: http://htc.vi8.info/Stock-RUU/
Already tried a different one and got an error message saying it couldn't install, hopefully this one gives me better luck.
Click to expand...
Click to collapse
besides that you can use also the last one
by the way since you are on S-OFF if you have supercid you can use any ruu.exe you want
for cid you can check with fastboot getvar cid
Alright, it says TMOB010
Dan33185 said:
Alright, it says TMOB010
Click to expand...
Click to collapse
probably it won't work the ruu.exe you chose
if you will face any error try this one
http://shipped-roms.com/download.ph...0U_11.23.3504.07_M2_release_256085_signed.zip
otherwise change your cid to supercid and use whatever ruu you want
I changed my CIP to Super CID and it's now 11111111. Theoretically, I should now be able to use any RUU and get back to stock, correct?
Dan33185 said:
I changed my CIP to Super CID and it's now 11111111. Theoretically, I should now be able to use any RUU and get back to stock, correct?
Click to expand...
Click to collapse
correct:good:
Success! Thanks for all the help, really appreciated!