I kinda destroyed my one S, fell out of a truck bed on the highway.....anyways, i just received my new one s thru ups which came preloaded with the JB OTA update direct from TMOUSA. I proceeded to root and gain supercid and s-off but had no success in acheiving s-off or supercid.........all of my back ups and settings and data are for cm10.1 and I am unable to gain full root, I've Ben able to flash CWM and have root permissions but I am unable to flash cm10.1 or any other Roms. Also, I am unable to delete bloatware on the stock Rom using my paid version of titanium back up. Says the uninstall is finished but the bloatware still remains after multiple attempts and re boots.
Has there Ben any progress on overcoming this pesky supercid and s-off lockdown on the JB OTA? Not asking for an ETA, I just haven't Ben able to find anything related to the subject other than "your screwed if you updated to JB thru OTA."
THANKS IN ADVANCED FOR THE HELP AND INFO.
Sent from HTC One S using TapaTalk Beta
Are you fastbooting the boot.img for these roms you are trying to flash? You need to pull it from the ROM zip or it won't boot, same for your nandroids.
Your issue with the bloatware on stock is caused by write protection in the stock boot.img. So flash a custom one.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me
Related
Hello everyone,
This evening I was tired of CM 10 not working properly anymore (play store kept crashing etc.), so i decided that i wanted a new ROM. I chose Viper S 2.2 and there was the point where everything went wrong.
I used to own a HTC Desire with which flashing was very easy, but with the One S I kept seeing that i had to flash a boot.img or something, i hate the SDK so i skipped it. The Viper ROM went OK until after the reboot after the Arosa installer.
It is now stuck at the splash screen and when i try to reflash anything it just gives me a red "Failed" message, with it saying that the zip could not be opened..
I then tried to go extreme and unroot it bij using the RUU but this keeps giving me the 107 error of it not being connected.. It doesnt work in HBOOT or in the splash screen.
Here is the bootloader info:
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.16.31501S.17_2
OpenDSP-v25. 1.0.32.0405
eMMC-boot
and on top of that, in the proces my whole SD-Card was wiped (internal storage)
Anyone any idea what to do? I'm desperate..
Well...all you had to do was flash the boot.img...you can't just skip things that's why it wouldn't boot...no boot.img hence the name..make sense?
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
ryanshew said:
Well...all you had to do was flash the boot.img...you can't just skip things that's why it wouldn't boot...no boot.img hence the name..make sense?
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
Click to expand...
Click to collapse
Well.. the problem already occured when i tried to reflash CM10 ... I know that not flashing the boot image was not my brightest move ever, the problem of not being able to flash anything already occured before even knowing about the thing..
Have you tried flashing a different recovery? Try clock work mod or 2.3.3 of twrp
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
ryanshew said:
Have you tried flashing a different recovery? Try clock work mod or 2.3.3 of twrp
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
Click to expand...
Click to collapse
I am currently on twrp 2.4, i will flash CWM for now and let you know how it goes.
Oh your 2.44 there's your problem. I'm on the latest 2.4.4.0 as well For the OTG support, but If I run into any problems I just immediately flash CWM.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
ryanshew said:
Oh your 2.44 there's your problem. I'm on the latest 2.4.4.0 as well For the OTG support, but If I run into any problems I just immediately flash CWM.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_3.4
Click to expand...
Click to collapse
just flash a new kernel, also my tool flashes .zip files, maybe you should try it, link is in my signature! hope it works!
Nope.. not working, flashed a new custom kernel, CWM, boot.img .. Everything looks fine when installing but when I boot up it keeps getting stuck on the splash screen..
OMG. I don't know why, but it suddenly works.. I threw a CM10 EXPERIMENTAL on my sd and it's booting.. Still not sure on how to flash the Viper though now... Thanks anyway everyone.
cookiejarxxl said:
Still not sure on how to flash the Viper though now...
Click to expand...
Click to collapse
reboot into bootloader -> fastboot
fastboot flash the boot image from the 2.1 rom
reboot into recovery
wipe system, data, cache
flash the 2.1 rom without wiping in aroma
reboot into android
let it sit for a minute or so before unlocking
in the setup, you have to choose your carrier and language. you can skip everything else
reboot into recovery
flash the 2.2 ota
reboot into android
let it sit for a minute or so before unlocking
personalize -> skin or scene, de-select and re-select the default skin
let it sit for another couple minutes
reboot
do your accounts, apps, tweaks, settings, etc..
touch of jobo said:
reboot into bootloader -> fastboot
fastboot flash the boot image from the 2.1 rom
reboot into recovery
wipe system, data, cache
flash the 2.1 rom without wiping in aroma
reboot into android
let it sit for a minute or so before unlocking
in the setup, you have to choose your carrier and language. you can skip everything else
reboot into recovery
flash the 2.2 ota
reboot into android
let it sit for a minute or so before unlocking
personalize -> skin or scene, de-select and re-select the default skin
let it sit for another couple minutes
reboot
do your accounts, apps, tweaks, settings, etc..
Click to expand...
Click to collapse
Thanks alot, I did find that the file keeps giving me a wrong MD5.. I guess it's corrupt, i have downloaded it a million times..
cookiejarxxl said:
Thanks alot, I did find that the file keeps giving me a wrong MD5.. I guess it's corrupt, i have downloaded it a million times..
Click to expand...
Click to collapse
If your recovery complains about signatures on the ota, try toggling signature verification off.
Hi,
I'm running ViperOneS 2.2.0 (Android 4.1.1) and still having the helicopter-glitch. So I contacted HTC support and they told me I should backup all my data and do a hardreset. Will my phone be OK after running the hardreset? Because of custom ROM? I've unlocked via HTCDev and I'm running CWM recovery. Do you think this will fix the issue? Sending it in for repair could end up expensive, because of unlock. Or are there any other ideas for fixing it?
Greets
Sorry I didn't use the helicopter-thread but this does not directly concern the issue itself...
no proper fix till now! we are stuck with it
Seriously HTC!? -.-
Chances for a fix with hardreset? none?
TerrorApple said:
Seriously HTC!? -.-
Chances for a fix with hardreset? none?
Click to expand...
Click to collapse
Doubt it. You could try running an ruu, but other than that...???
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
But whats the difference between RUU with Android 4.1.1 and ViperOneS also running 4.1.1? HTC said the fix was added in Jelly Bean?
RUU , will flash new versions of bootloader , radio etc . The rom is just the system partition , I recommend you to RUU the device then restore your ViperROM
Ruu is like a fresh wipe/reset/clean. Wipe everything and re flash all partitions.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Ok thanks, I'll give that a try. Can someone please post how I exactly do that? First time to flash RUU... Found this: http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html Will that work? And where can I get the RUU I need? It says I should go S-OFF to use any one I want... My phone came with german T-Mobile ROM. And using CWM isn't a problem, right?
Hi
I have a rooted HTC One S with ViperOneS v1.2.1, yesterday I tried to upgrade to the newest update of ViperOneS but it just got stuck in the HTC logo and didn't get any further, then I tried with the same version I had installed and the same issue. Then I tried with another ROM and waited for 45 min and still same issue. A co-worker then told me I might have to SuperCID and S-OFF it ??? But is it really necessary when the phone is rooted and I already have a custom ROM on it ?
I've tried to read several threads on the subject but nothing that really gives me a straight answer
My phone works, cause I'd make a backup, but it is starting to act weird and I wan't to upgrade or try another ROM. :fingers-crossed:
I NEED KNOWLEDGE
Have you tried to flash the boot.img with fastboot from the comandline?
Sent from my One S using xda app-developers app
Also make sure to either use clock work mod or twrp 2.3.3.0 for recovery...nothing newer.
And yeah, you must fastboot the boot.img or it won't boot.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Hello again,
I am attempting to get my phone fully updated and had a few questions regarding the update process.
These are the things that I need done to my phone in order to use $droyd$ cm10.1 instead of the downward slope "official"
SuperCID 1111111
Kernel 3.14 through RUU
S-OFF
It is my understanding that SuperCID is required to S-Off so that order is apparent, but the RUU update and anything else I may be missing I am unsure of.
I am running a TMOUS Ville (S4)
HBOOT 1.09
TWRP v2.4.2
I dont really care about the contents of the phone as its all either cloud based or backed up already.
What is the best course to take to do all that I need?
Am I missing anything vital to this process?
Also, this is the RUU I found doing a search, can someone verify this is the correct/most recent RUU I need :link:
Thanks for any help. Cheers
-pyro
You don't need ruu to soff
Just super cid, then soff
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me
He (apparently) needs to install a RUU to get the latest updates over OTA - otherwise the new 3.4 kernel for AOSP roms won't work (very well).
I'm trying the same thing, (hboot 1.06, s-on, unlocked, TWRP) but i'm pretty confused right now...
1. do i need s-off / stock recovery / something other to install a RUU exe?
2. if i successfully installed a RUU, should i update via OTA? or is it enough to install the latest RUU exe to get the firmware required for the 3.4 kernel?
3. some people mentioned big problems after the OTA update if you have super cid / s-off...... BUT
4. some people mentioned you can't get s-off AFTER you install the latest OTA update
so do we have the choice between not using the 3.4 kernel and not having s-on (therefore having to flashboot boot.img everytime), or am i missing something?
If wont to flash ONLY RUU, just install stock recovery.
If you want to get OTA, chanche super-CID to normal , 'coz YOU CAN FINISH WITH BRICK!!
Hi,
I have a question about reverting back to stock JellyBean 4.1 on a Rogers device. I have tried previous Rogers RUUs and they all fail to install. They fail at the loading hboot portion. I believe I have to revert back to an earlier hboot to flash an earlier Rogers RUU, am I correct? I would like to just install the current RUU but no one seems to have the current one, even AndroidFiles doesn't. They only have an OTA version (OTA_Ville_U_JB_45_S_Rogers_WWE_3.16.631.8_1.11.50.05.28_10.27.50.08L_release_301897nn5lu23br8cg9q7l.zip)
Is there any way I can install the OTA version to get me back to stock or do I have to wait for the RUU to be released? I'm pretty happy using TrickDroid firmware on it but there are still a few bugs and I wanted to go back to stock. Unfortunately I don't have any backup, I got a deal on this phone because the previous owner bricked it and couldn't figure out how to get it working again. It took me many hours but with guidance of these forums, and elsewhere, I was able to get custom firmware on it thankfully! This is my first HTC device and I find them much harder to root/unlock/flash than my previous Samsungs.
S-OFF and supercid and you can run any ruu
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me
and after s-offing supercid and ruu dont forget to revert your cid to the old one before applying an ota.
applying otas with supercid may cause bricks