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
Related
So I need some help. I'm not new to android or adb or anything, just confused with this. Here's some background info:
HTC One S (Cincinnati Bell)
S4 Variant
Unlocked boot loader
Rooted (on stock ROM)
TWRP installed
Hboot 1.14
SuperCID
Problem: tried installing the latest CM10 and also CM10.1 with no success(endless boot animation, and 10.1 gets stuck on the HTC screen). I read I news to flash a boot.IMG to get it to work since I'm not S-off. Where can I find this boot.IMG that needs to be flashed?
Any help is much appreciated! Couldn't find anything from my searches.
Extract it from the ROM zip
HTC_One_S | Xparent_ICS_Blue_Tapatalk 1.06_Hboot_Downgrade | unofficial_4.2.1_AOKP_Feb7 | Komodo_Kernel | S-OFF
Pip513 said:
So I need some help. I'm not new to android or adb or anything, just confused with this. Here's some background info:
HTC One S (Cincinnati Bell)
S4 Variant
Unlocked boot loader
Rooted (on stock ROM)
TWRP installed
Hboot 1.14
SuperCID
Problem: tried installing the latest CM10 and also CM10.1 with no success(endless boot animation, and 10.1 gets stuck on the HTC screen). I read I news to flash a boot.IMG to get it to work since I'm not S-off. Where can I find this boot.IMG that needs to be flashed?
Any help is much appreciated! Couldn't find anything from my searches.
Click to expand...
Click to collapse
If you are able to access TWRP recovery, you should be able to mount your SD card and transfer a new rom onto your phone via your computer(download it onto your computer and transfer it using your USB cable), or if you made a nandroid backup from a point in time when your phone was working, that should do the trick. If you really want to flash a custom boot.img, I recommend using this to flash it.
He already had the ROM installed, he just needs to fastboot the boot.img to get it to boot.
HTC_One_S | Xparent_ICS_Blue_Tapatalk 1.06_Hboot_Downgrade | unofficial_4.2.1_AOKP_Feb7 | Komodo_Kernel | S-OFF
ryanshew said:
Extract it from the ROM zip
Click to expand...
Click to collapse
Yeah, before I went to bed I figured it was was in the ROM. Thank you! I'll have another go at it.
Why is it that the boot.IMG doesn't get flashed properly? Is anyone working on a fix?
Edit: worked perfectly! Thanks guys!
Its because of your hboot. hboot 1.14 and higher dont flash it properly.
Fix for it? Downgrade to a lower hboot, or flash the boot.img from the phone before flashing a new rom with flash image gui, or just live with it.
S-OFF might also remove the need for seperate flash of the boot.img, I havnt bothered looking into it so I dunno...
Right now I'm on CM10, and let's say I want to switch to the 10.1 nightly's. I shouldn't have to flash the boot.IMG for each new nightly since its the same ROM, correct?
Pip513 said:
Right now I'm on CM10, and let's say I want to switch to the 10.1 nightly's. I shouldn't have to flash the boot.IMG for each new nightly since its the same ROM, correct?
Click to expand...
Click to collapse
It depends on which rom you stay with. If you stay on CM10, then you do not have to flash the boot.img everytime you flash a new nightly. But if you go to 10.1, then you will have to flash that boot.img first. If you have S-Off the boot.img will be flashed from TWRP when the rom is flashed, and you wont have to do it from Fastboot. I don't suggest you try to downgrade you Hboot, especially because we have S-Off now. Although some people are finding that they can no longer connect to any signal above Edge/2g after S-Off.
That's why I didn't want to go s-off just yet. I saw some people having trouble with it, and since I've got a different model (Cincinnati Bell version) than the s-off guide has, I decided not to until it was 100% stable. Thanks for the help though guys! As long as I've got to a way to flash roms without too much headache, I'm happy.
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?
Hello,
I recently rooted my one s (s4) using a noob friendly guide from another forum. It was excellently written and got me to root and superuser access in a short amount of time.
Unfortunately in my haste (and stupidity) when it came to flashing a rom on my phone i just choose the top link from the same tutorial, assuming it would be the most popular/recommended one. However unfortunately it was [ROM] CyanogenMod 10 - Official Nightlies. Which i think has screwed my phone, i am stuck in a boot loop with no apparent means to get out. So i tried to do a factory reset and recovery and have also tried to flash another rom onto it but with no success.
So i need to get back to stock, but im struggling to find the RUU file i need, (to be honest i don't really know what i'm looking for) and i was looking for some help and guidance in getting my phone back
thanking you in advance
Zapp
Hi, unless you are S-OFF none of the older T-Mob UK RUUs will work for you as you cannot flash an older RUU than your current version. And unless you have changed your CID from T-MOB005, there are no RUUs with the same version. So you will need to flash CM10 in recovery again, and flash the boot.img as well (in FASTBOOT USB mode straight after it) using the command
fastboot flash boot boot.img
Of course, the boot.img is in the CM10 zip file.
And I would recommend S-OFF'ing, or changing your CID. If a ROM really does get stuck, there will be no RUU for you and that is not a good thing.
Sent from my HTC One S using Tapatalk 2
Thanks for your help, just trying it now, going to s-off and then reinstall cm10
zapp8rannigan said:
Thanks for your help, just trying it now, going to s-off and then reinstall cm10
Click to expand...
Click to collapse
Well, your going to need to get a ROM running first before you can s-off.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
ryanshew said:
Well, your going to need to get a ROM running first before you can s-off.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
Click to expand...
Click to collapse
ah....its not going to work then i was hoping that would be the part of the puzzle i am missing. Is there anything else i can try?
EDIT: actually, i didn't flash the boot.img seperately last time so hopefully thats it..?
OK i'm just installing the stable cyanogen release but its saying no MD5 file found, but it also says it was successful. does this matter?
zapp8rannigan said:
ah....its not going to work then i was hoping that would be the part of the puzzle i am missing. Is there anything else i can try?
EDIT: actually, i didn't flash the boot.img seperately last time so hopefully thats it..?
OK i'm just installing the stable cyanogen release but its saying no MD5 file found, but it also says it was successful. does this matter?
Click to expand...
Click to collapse
Yes, if you didn't flash the boot.img separately then that's most definitely the problem.
MD5 isn't an issue. After you flash it, just make sure you flash the boot.img.
usaff22 said:
Yes, if you didn't flash the boot.img separately then that's most definitely the problem.
MD5 isn't an issue. After you flash it, just make sure you flash the boot.img.
Click to expand...
Click to collapse
THANK YOU SO MUCH CHAPS!
it worked! sorry for being a noob! im so happy now, i can't thank you enough
ok new problem....gapps....
installed from recovery but im back in a ruddy boot loop again.....do i need to do that boot.img thing again???
zapp8rannigan said:
ok new problem....gapps....
installed from recovery but im back in a ruddy boot loop again.....do i need to do that boot.img thing again???
Click to expand...
Click to collapse
Hmm. It shouldn't do that.
You may want to wipe cache, dalvik cache and data in recovery. Then flash CM. Then flash the latest gapps for whichever Android version your CM is. E.g use a different gapps if you were flashing Android 4.2 than if you were flashing 4.1.
Then flash the boot.img in FASTBOOT USB.
Sent from my HTC One S using Tapatalk 2
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