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
Related
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,
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
These days, as I'm more onto porting,development and testing of ROMs, just wanna be sure with the possibilities for a BRICK. Plz help me out guys!!
Just don't mess around with low-level stuff like partitions, hboot, radio and stuff like that. Also, porting a ROM incorrectly could mess up your main board if the device that you are porting from has much higher/lower CPU/GPU frequencies than this device.
vatsaman said:
just wanna be sure with the possibilities for a BRICK.
Click to expand...
Click to collapse
Ways to brick that I know of:
* Turning S-On after you flashed a modified hboot, or flashing an modified hboot while S-On (which you can actually do on 1.06 and 1.09. don't.)
* Taking certain recent OTAs while on SuperCID (you need it to gain S-Off but I suggest to change to HTC__001 afterwards.)
There have been reports of devices in qhsusbdload mode after completely draining the battery. But not for a while I think.
usaff22 said:
Just don't mess around with low-level stuff like partitions, hboot, radio and stuff like that. Also, porting a ROM incorrectly could mess up your main board if the device that you are porting from has much higher/lower CPU/GPU frequencies than this device.
Click to expand...
Click to collapse
Thanks a lot for the info. Another clarification.. Are the files related to hboot, radio and partitions are included in the ROM zips ?? If yeah please name the folder, so that I'll get my hands cleaned up while working with them :victory:
vatsaman said:
Thanks a lot for the info. Another clarification.. Are the files related to hboot, radio and partitions are included in the ROM zips ?? If yeah please name the folder, so that I'll get my hands cleaned up while working with them :victory:
Click to expand...
Click to collapse
No, they are in firmware.zip, not in the rom.zip itself.
usaff22 said:
No, they are in firmware.zip, not in the rom.zip itself.
Click to expand...
Click to collapse
So we won't be dealing with firmware.zip while porting the ROM ??
vatsaman said:
So we won't be dealing with firmware.zip while porting the ROM ??
Click to expand...
Click to collapse
Nope
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me
I can't get a valid rom into my phone, and it currently has no ROM, but can get to boot loader, and fastboot. Please help me get it usable again.
I went to obtain S-Off on my One S (older phone, got it before the S-Off was available). aka, I was getting real tired of flashing CM Roms and having to use Fastboot to flash boot.img.
I selected the moonshine S-Off tool, and reviewed the directions.
Directions said you need stock, so I re-locked the boot loader, grabbed the Telus RUU.zip and tried to flash the phone to stock using Hansoon's All-in-one kit v4.0 for the One S. It came back and said: "FAILED (remote: 12 signature verify fail)"
The RUU filename is: OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip
At this point I still had TWRP installed, so I tried to unlock and restore CyanogenMod from a nandroid backup to no avail. It said it couldn't mount several partitions.
Per another thread about that specific error I, flashed the recovery.img from the ruu zip file (it was already unlocked from the last step), relocked and retried. Got the same error.
I've attached a screenshot of the fastboot screen hoping that will provide useful info.
Any help is appreciated, and I'm happy to provide more info as needed as well.
That is not an ruu, it's an OTA.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
ryanshew said:
That is not an ruu, it's an OTA.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
Click to expand...
Click to collapse
Thanks for the clarification. The .exe version returned an "unknown error" ... I missed that step in the description above. The RUU filename was: RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe, and was flashed with the device re-locked.
DouglasK said:
Thanks for the clarification. The .exe version returned an "unknown error" ... I missed that step in the description above. The RUU filename was: RUU_Ville_U_TELUS_WWE_1.70.661.1_Radio_0.16.31501S.02_10.18.31501S.08L_release_254554_signed.exe, and was flashed with the device re-locked.
Click to expand...
Click to collapse
That is too old, you have to use a version the same or higher than your current
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
Ok. Next question, where do I get one that is recent enough?
Douglas
Sent from my Nexus 7 using XDA Premium HD app
DouglasK said:
Ok. Next question, where do I get one that is recent enough?
Douglas
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I think your going about this all wrong. First, you are on a low enough firmware for facepalm s-off. Moonshine cannot even be run with your firmware even if you upgraded it.
What you need to do is super cid, then use facepalm s-off method.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
ryanshew said:
I think your going about this all wrong. First, you are on a low enough firmware for facepalm s-off. Moonshine cannot even be run with your firmware even if you upgraded it.
What you need to do is super cid, then use facepalm s-off method.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+
Click to expand...
Click to collapse
Ok, I'll do that. Do you have a link to a recommended SuperCID method? Normally I'd search and pick one, but I've well... not had the best weekend at that.
Also, once I've got it S-Off, then I can install an RUU or OTA of choice without issue?
~~Douglas
DouglasK said:
Ok, I'll do that. Do you have a link to a recommended SuperCID method? Normally I'd search and pick one, but I've well... not had the best weekend at that.
Also, once I've got it S-Off, then I can install an RUU or OTA of choice without issue?
~~Douglas
Click to expand...
Click to collapse
There only is one. It's in the one s dev section titled "Super CID 11111111" and I'm sure they linked to it from the facepalm thread as it is a prerequisite.
hTConeS | SoFF | DarKSeNsE | BuLLetprOOf
Dark Sense 5 Theme Updates+Tweaks
Inverted Sense 4+