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?
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.
Hey all, because i dint want to push these older threads... (because a lot forums dont like that for some reasons, not sure if its cool here)
http://forum.xda-developers.com/showthread.php?t=1604658&highlight=stock+kernel
http://forum.xda-developers.com/showthread.php?t=1743496&highlight=stock+kernel
...Im doing a new one:
After unlocking, rooting, and S-OFFing my phone i tried out some roms. They are all not bad (ViperOneS, TrickDroid, CM).
But i wanted to be on stock for now to get used to the phones normal habits and issues before trying out more.
I flashed a stock recovery and installed the newest ruu. Everything worked (with s-off and SuperCID but stock recovery) and im happy with it atm. (Since its rooted and doesnt have an o2 branding anymore...).
But one thing bothers me: Its the kernel.
phone info says:
3.4.10-gae8b65e
[email protected] #1
SMP PREEMPT
When i search it on google: "one s + that kernel", it shows me that people who uses ViperOneS ROM have this one.
I thought when i fully wipe my device or even run a ruu my custom kernel is gone. oO
Cant find the boot_signed.img on google.
Another site has a tutorial how to get those things through the ruu itself:
Rrun the ruu (with admin rights) > start > run > %temp% and there search there for boot_signed_img etc.
But it doesnt work for me. it does not find the boot_signed.img in the complete temp folder.
How can i get back to stock kernel?
Thanks in advance!
That is the stock kernel. It is also the stock kernel which is included with viper.
Ruu brings you completely back to stock, kernel and all.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
aah thats why...
so this means, when i need a stock kernel, for some reason, i can just take the one ViperOneS uses atm?
edit: ah no. this actually contains more than the kernel, right... forget it =)
well, thanks for the answer ^^
turnschuh said:
aah thats why...
so this means, when i need a stock kernel, for some reason, i can just take the one ViperOneS uses atm?
edit: ah no. this actually contains more than the kernel, right... forget it =)
well, thanks for the answer ^^
Click to expand...
Click to collapse
I'm not sure but the ViperOneS boot.img is unsecured (so system partition is writable), so its not 100% stock
turnschuh said:
aah thats why...
so this means, when i need a stock kernel, for some reason, i can just take the one ViperOneS uses atm?
edit: ah no. this actually contains more than the kernel, right... forget it =)
well, thanks for the answer ^^
Click to expand...
Click to collapse
Yes, you can extract the boot.img
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
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
Does anybody know if hboot 2.15 has fastboot restrictions? I am s-off and when I try to flash a radio via fastboot it denyed me access and when I was looking around online some people were relating this to the hboot. So If anybody has anything they would like to share I'd be happy to read it.
Flash them through recovery using the zips in the dev forum.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Thats exactly what I did but It still is throwing that error right when its about to write the img. Could it be the rom?
More likely recovery issue. Change that to lower like 2.3.0 or older.
Sent from my VILLE using xda app-developers app
tylerjholmgren said:
Thats exactly what I did but It still is throwing that error right when its about to write the img. Could it be the rom?
Click to expand...
Click to collapse
I mean, do not use fastboot to flash radios...out don't work, S-OFF or not. Use the radio collection thread in the dev forum. Download the collection zip, then flash it in recovery. and follow the instructions on the screen through the aroma installer.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
On a related note, what are the benefits of having the 2.15 boot over 1.14? Are there any improvements in terms of stability, etc? Before the reason not to upgrade was because of S-ON, but now that we are S-OFF, is it worth upgrading? Thanks!
bombina said:
On a related note, what are the benefits of having the 2.15 boot over 1.14? Are there any improvements in terms of stability, etc? Before the reason not to upgrade was because of S-ON, but now that we are S-OFF, is it worth upgrading? Thanks!
Click to expand...
Click to collapse
If you are s off hboot version doesn't matter
Sent from my HTC One S using xda app-developers app
tylerjholmgren said:
I am s-off and when I try to flash a radio via fastboot it denyed me access [...]
Click to expand...
Click to collapse
You did not by any chance re-lock your bootloader, did you? that would explain why you can't flash.
If you're unlocked and S-Off, you can try the flashable hboot zips in my bootsplash thread. --> http://forum.xda-developers.com/showthread.php?t=1777223 Look at posts #148, #212, #274 there.
But, as k1llacanon points out:
k1llacanon said:
If you are s off hboot version doesn't matter
Click to expand...
Click to collapse
For your radio, have you tried the recovery flashable radio collection by Tecardo? --> http://forum.xda-developers.com/showthread.php?t=1998270
-Jobo
hi. i'm experiencing some troubles with my phone. i was on jb and have downgraded to ics. since then i can't connect my usb flash drive using OTG cable. is there a way to make it work?
It's not powered in ics...you need a "Y" adapter to plug in usb power source. Or you could flash beastmode bricked kernel if your rooted, which will enable self powered USB otg.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
mr_switcher said:
hi. i'm experiencing some troubles with my phone. i was on jb and have downgraded to ics. since then i can't connect my usb flash drive using OTG cable. is there a way to make it work?
Click to expand...
Click to collapse
It only works with JellyBean. And sense 4+
With ICS you need to power the otg for it to work and it could cost like £7 /$10
If you can update to jellybean I would recommend it .
Its a lot easier
If I helped hit me up with a thanks
Hold on... Before getting carried away try flashing beast mode bricked kernel and also download the app usb otg helper. That should do the trick without a y cable
Sent from my HTC One S using Tapatalk 2
Thanks for your replies. So, I tried to flash beastmode kernel, but it won't work. Here's the steps I made:
Unlocked bootloader
Flashed TWRP
Installed the latest beastmode blocked kernel (went through arome installer, it said the kernel is installed)
Cleared cache and dalvik
Reboot... and the settings menu still shows me the default kernel installed(so there was no OTG support).
May be I did something wrong? Kinda noob in flashing this device (used to work with p500 )
Well, you either need to root or flash a custom ROM first (basically, you need root, then if it don't work, is an old trick to flash fusion kernel first, then beastmode.
Remember only to use these, not the new bricked kernel that was just released..that's for JB
http://forum.xda-developers.com/showthread.php?p=31534876
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
ryanshew said:
Well, you either need to root or flash a custom ROM first (basically, you need root, then if it don't work, is an old trick to flash fusion kernel first, then beastmode.
Remember only to use these, not the new bricked kernel that was just released..that's for JB
http://forum.xda-developers.com/showthread.php?p=31534876
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
Click to expand...
Click to collapse
I've already rooted this device. Will try to flash fusion now. (This one, right?http://forum.xda-developers.com/showthread.php?t=1851841)
btw, can anyone tell me how to setup OTG support when i'll install beastmode?
mr_switcher said:
btw, can anyone tell me how to setup OTG support when i'll install beastmode?
Click to expand...
Click to collapse
It'll be working already...for flash drives, etc, use otg helper from play store
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3