Database Info

[Q] Question on Flashing a Rom

Hello, recently i've just rooted my htc one s, s4. I stalled for a bit and had the 4.0.4 update already, so currently I have root access with the stock firmware. I'm looking through the rom list and the viper One s room caught my eye. So my question is, are there any prerequisite requirements before i flash this rom. Sorry for such a ridiculous question, but i havn't flashed a rom since the G1 and I remember having to flash certain kernels for certain roms. I still haven't messed with the kernel yet so that's stock too.
_________________________________________________________
My One S is s4 t-mobile, TWRP recovery, obtained root access with the All in One Toolkit v3.0 by hasoon2000. firmware is stock update 4.0.4 and everything else is just stock. so all i did was root

Just follow the instructions in the Viper Thread.
Since you have it rooted (and I assume a working recovery) you should already have all tools needed (fastboot etc).

On the Working Recovery, I would recommend installing TWRP. Best recovery atm for rom flashing. Get it thru the Goo Manager App on PlayStore. Just open Goo Manager then open Menu and tap on Install OpenScript Recovery.
Read OP pages carefully and scan the threads of the rom you want to flash. Depending on your hboot version, you may have to fastboot boot.img right after flashing rom. If at or above .13. Or, get Flash Image GUI from PlayStore and it will do it for you.
On CM roms there are some other quirks with radio etc, so some pre-study would be advised as well as nandroiding and backing up sdcard first. Put both backups on PC for extra safety.
Good Luck--

rugmankc said:
On the Working Recovery, I would recommend installing TWRP. Best recovery atm for rom flashing. Get it thru the Goo Manager App on PlayStore. Just open Goo Manager then open Menu and tap on Install OpenScript Recovery.
Read OP pages carefully and scan the threads of the rom you want to flash. Depending on your hboot version, you may have to fastboot boot.img right after flashing rom. If at or above .13. Or, get Flash Image GUI from PlayStore and it will do it for you.
On CM roms there are some other quirks with radio etc, so some pre-study would be advised as well as nandroiding and backing up sdcard first. Put both backups on PC for extra safety.
Good Luck--
Click to expand...
Click to collapse
Thanks! i went ahead and flashed viper rom and after reading a bit i noticed that i had hboot .14 so it broke my wifi . I'm still currently searching info and came across that i need linux to downgrade, which i don't have . do you know any other method? or roms beside trickdroid 7 that support the hboot version and allow wifi?

On .14 the items I mentioned will apply on all roms
Not sure on wifi, i use mostly cm roms atm

Im on Hboot .14, and wifi works fine for me on viperS

there is a wifi partition zip floating around for wifi issues. didn't pay much attn to it as i have no issues--maybe a search, or someone will post it

[Q] One S C2 / S3 Not compleating ROM flash?? Bricked?

Hey all, been a member here for years but dont post offten. Normally able to get the info i need from other posts but this time i am stuck Just wondering if anyone has had the same issue flashing a One S C2 with the S3 CPU that im having now. It was stuck with 4.0.3 with hboot 2.09.001, raido 16.05.2.24_M and CID OPTUS001...
Last night i dev unlocked it via the HTC site and flashed TWRP 2.4.4.0 recovery. Tried to put on luxandroidROM v4 but it failed part way through ROM install. The progess bar just got to a point and stopped?? I noticed i had a hboot that was too old for the JB ROM so tried BackToBasics v3 (ICS) ROM but that did the same thing...
Thinking it was maybe just a issue with the ROMs, i tried TrickDroid 6 and CM10 Unofficial build but that was doing the exact same thing... Tried redownloading all the ROMs and looking into SupoerCID but as other with the S3 CPU have reported, it all appears to have worked but does not change the CID Oddly enough when i was in ADB Shell while the phone was sitting on the TWRP recovery mode the SU command was not working. Relevent?
I'm now thinking the issue is the phone is not getting permissions to write the ROMs but have no idea how to correct this. I made sure TWRP has all sections mounted (not sure if this is needed as i normally use CWM) but didn't help.
TWRP keeps saying device isnt rooted when i go to reboot it but fails to root when i tell it to on exit. I have manually flashed SuperSU through TWRP and tried fixing permissions. Tried full factory wipe, Bulletproof-S3-1.3 Kernal and SuperSU again. Still nothing.
Not able to find a RUU for the OPTUS001 CID. Tried extracted version of RUU_VILLEC2_U_ICS_40_hTC_Asia_WWE_1.11.707.112_Radio_16.12.20.02U_16.05.20.16_M2 with CID changed in texts files but it still saied with carrier ID issue
This would be the first time i think i have bricked a phone Does anyone have any suggestions? At this point i would be happy for a nandroid backup to go back to sock and just like with 4.0.3

$40 reward to whoever provides me the info i need to fix this

On the s4 versions of TWRP newer than 2.4.0.0 have issues. I'm not sure if they affect the c2 version but I shouldn't hurt to try an older version.
Sent from my HTC One S using xda app-developers app

TWRP 2.4.4.0 has known bugs. Downgrade to 2.3.3.0 or 2.3.3.7.
And remember to open (BUT NOT EXTRACT) the .zip and to copy and paste the boot.img into your fastboot working environment and manually flash it with this command:
fastboot flash boot boot.img
Then try to flash the ROM that you got the boot.img from. This should work.
Sent from my One S using xda premium

Managed to get this working, figured i would post in case anyone else runs in this issue.
Tried multiple versions of TWRP and no matter what one i tried the roms were unable to write to the stoage. Had to format the phone storage using boot cd - I used GParted through a virtual to do so.
Once that was done TWRP 2.4.4.0 worked fine to flash rom. Still stuck with 4.0.3 with hboot 2.09.001 due to the optus CID but phone is atleast alive. Thanks all for the input

[Q] PAC-man ROM not booting anymore

hi,
so as i can not post in the android development subforum i'll have to try it here..
I have: HOS with TWRP 2.4.4.0 (goo manager) with HBOOT 2.15 (S-ON) running PAC-man ROM 22.1 (the newest update)
also i have bubba v4 installed and everything was working really perfectly. (s2w and some kernel tuner settings)
yesterday i played a bit with UI settings, nothing that i thought would stop my device from booting..
today i woke up, the battery was empty so i plugged in, turned on and left, after a while i came back and it was still at the boot
animation (PAC is loading...).
now i have tried to reflash bubba, PAC (cache+dalvik wipe) and the boot.img via fastboot. still it is stuck on that loading screen.
now i'd really like to use this rom with the bubba kernel.
any clues how i could get it out of this boot cycle?
thanks
-t.

2.4.4.0 is kinda crap in certain things. Flashing roms is one of them. Please use 2.3.3.0 as this will work.

why do you think that twrp version is the problem?
flashing this rom with 2.4.4 has worked well, so flashing over the same ROM with it shouldn't be problem...?
when flashing or wiping everything seems to work normally.
also, i am not sure how to downgrade twrp!?
best,
-t.
edit: okay i found out, fastboot flash recovery .. should work. i'll let you know if it works afterwards *fingers crossed*
edit2: reflashing the ROM it takes much longer (maybe thats good?) i just hope it finishes at some point...
edit3: okay, so re-flashing with twrp 2.3.3.0 did'nt work either, it is still stuck at the "PAC loading..." stage
(yes, i flashed the boot.img too)
any more clues?
finally i had this phone set up just the way i wanted, it was perfect and then this. why couldn't it just keep working
makes me sad, i want to use my phone damnit

okay, so i flashed and wiped and flashed and wiped a few times, system, cache, dalvik whatever, suddenly it started working... i also flashed some different kernels (as i thought some bubba stuff might still be there)
soo IDK what it was but now it works again, thank god..
maybe its worth mentioning that i flashed an older PAC rom (v22.0.1_20130324-230044) though i am not sure if that was the problem...

Sorry, I was off for some time from this forum.
If your bootloader version is > 1.09 you'll have to flash the kernel separately due to some restrictions in the higher bootloader versions.
If e.g. you flashed boot.img only from the 'bubba.zip' you're missing some of the modules needed for working coming with that flashable zip. Just have a look inside the zip file and you'll see some different content besides the boot.img. So you need to flash the complete zip file (to get the modules) and separately again the boot.img (to get the kernel itself).
The point about 2.4.4.0 / 2.5.0.0 is, that some installer scripts for some roms don't work as they should.
:good:

Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Well nevermind I guess I learned something from this little action that cost me most of my precious Saturday...
Also I now tried flashing twisted 3 and bulletproof kernel neither of them worked for pac rom, maybe someone could explain to me which kernel works for which rom? I thought they are completely interchangeable as long as they are compatible to the hardware..
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Well, appreciate the help.
Best,
#t.
Sent from my One S using xda app-developers app harhar

Bulletproof is for sense
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2

Aha okay, I thought sense is like any app running ontop of any kernel...alright.
Sent from my One S using xda app-developers app

tehtomi said:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Click to expand...
Click to collapse
Usually the installer script should set the right permissions already. Nah, modules shouldn't go lost this way ( system/lib/modules/*.ko).
tehtomi said:
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Click to expand...
Click to collapse
In short: boot.img = kernel
It's stored in an own partition (block) on the phone, That's why you have to use 'fastboot flash boot boot.img'. Same for radio: 'fastboot flash radio radio.img' and so on. The bootloader will load them first from this block. But search Google if you'd like to know more. lol
Usually there is a boot.img file in any rom.zip that can be extracted and flashed also it's supposed to be flashed with the rest of rom.zip in one go. Blame htc for their bootloaders which prevent you from this. That's why we talk about htc's half assed bootloader unlock.
To come to an end: There are sense based roms, AOSP and AOKP based roms. Whereas AOSP and AOKP based kernels could be interchangeable, sense based kernels are only compatible to htcs sense UI. That's why you can't mix them up with all the roms out there. Sense is deeply integrated into kernel.

[RESOLVED] Updating HBoot

Hi, I'm trying to update my HBoot to 2.13 or 2.15 so I can install the nightly CM11 builds. However, I'm not certain on the steps, so am hoping someone can clear things up for me.
This is the guide I've been looking at:
http://forum.xda-developers.com/showthread.php?t=2501542
At the top he says to find the correct RUU, then links to RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe for HTC Europe.
Am I able to just use that one? My original RUU is RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe, but I can't find a JB version of that.
Looking on http://www.androidruu.com/?developer=Ville, I can't see any RUUs for JB with Radio_0.16.315.
I don't want to download and try and use the wrong thing, so could someone just confirm whether I can/can't use the HTC Europe RUU, and if not, if there's anyway I can update the HBoot to run CM11?
Thank you.

zodac01 said:
Hi, I'm trying to update my HBoot to 2.13 or 2.15 so I can install the nightly CM11 builds. However, I'm not certain on the steps, so am hoping someone can clear things up for me.
This is the guide I've been looking at:
http://forum.xda-developers.com/showthread.php?t=2501542
At the top he says to find the correct RUU, then links to RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe for HTC Europe.
Am I able to just use that one? My original RUU is RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed.exe, but I can't find a JB version of that.
Looking on http://www.androidruu.com/?developer=Ville, I can't see any RUUs for JB with Radio_0.16.315.
I don't want to download and try and use the wrong thing, so could someone just confirm whether I can/can't use the HTC Europe RUU, and if not, if there's anyway I can update the HBoot to run CM11?
Thank you.
Click to expand...
Click to collapse
No! As the OP has said in his thread, you have to use the correct RUU that matches your CID. So yeah you cant use the Europe RUU.
And if your bootloader is still locked and you are S-ON, i suggest you try to find an OTA for JB.
Because THERE IS NO RUU for JB. HTC did not release any RUU for JB as they pretty well understood OTA did serve their purpose.
So if you can confirm your existing HBOOT version here, that would be great to those who can help. Else please provide your CID. (You can use CID getter which is downloadable from PlayStore)

ayyu3m said:
No! As the OP has said in his thread, you have to use the correct RUU that matches your CID. So yeah you cant use the Europe RUU.
And if your bootloader is still locked and you are S-ON, i suggest you try to find an OTA for JB.
Because THERE IS NO RUU for JB. HTC did not release any RUU for JB as they pretty well understood OTA did serve their purpose.
So if you can confirm your existing HBOOT version here, that would be great to those who can help. Else please provide your CID. (You can use CID getter which is downloadable from PlayStore)
Click to expand...
Click to collapse
Ha, a nice strong "no". Thank you for that - good thing I came here to check first then.
Ok, first things first, I've tried updating using the OTA, but it doesn't install. I'm using TWRP v2.6. I could get the error code, but I think I read somewhere that you can't (or shouldn't) install OTA with custom bootloaders? I was hoping to use CM if possible anyway, so hopefully shouldn't have to worry about that (unless that's the way to update the HBoot...)
As for the other info, my HBoot is v1.13 and my CID is O2___01.

807 94346552
Anyone with any information?

zodac01 said:
Anyone with any information?
Click to expand...
Click to collapse
Have you tried to S-OFF your device? If you don't want to do that, why can't you run the O2 RUU then use the system update to get to the higher android version? You have to re-lock the bootloader etc.. as detailed in that guide.

rosswhite said:
Have you tried to S-OFF your device? If you don't want to do that, why can't you run the O2 RUU then use the system update to get to the higher android version? You have to re-lock the bootloader etc.. as detailed in that guide.
Click to expand...
Click to collapse
I tried doing that - I installed the O2 RUU, and then tried to install the update, but it wouldn't work in TWRP. So I locked the bootloader (using fastboot oem lock), but trying to install the update just sends me to the stock HTC bootloader, and doesn't install anything. Is there something else I need to do to install the OTA update?

zodac01 said:
I tried doing that - I installed the O2 RUU, and then tried to install the update, but it wouldn't work in TWRP. So I locked the bootloader (using fastboot oem lock), but trying to install the update just sends me to the stock HTC bootloader, and doesn't install anything. Is there something else I need to do to install the OTA update?
Click to expand...
Click to collapse
The O2 RUU should revert the phone completely to stock and put the stock HTC recovery on the phone so TWRP should not even be installed at this point. Just to trying to understand what you are doing: you install the RUU, once it has booted go to Settings>About>Software Updates>Check Now. It will will find an update then choose to install it. Are you saying from here the phone just reboots to the bootloader and doesn't install the update?

rosswhite said:
The O2 RUU should revert the phone completely to stock and put the stock HTC recovery on the phone so TWRP should not even be installed at this point. Just to trying to understand what you are doing: you install the RUU, once it has booted go to Settings>About>Software Updates>Check Now. It will will find an update then choose to install it. Are you saying from here the phone just reboots to the bootloader and doesn't install the update?
Click to expand...
Click to collapse
That was my mistake - I used the RUU, but then installed TWRP right away, and the updates wouldn't work.
Updated to 4.1.1 on stock - going to see if I can get CM installed now.

zodac01 said:
That was my mistake - I used the RUU, but then installed TWRP right away, and the updates wouldn't work.
Updated to 4.1.1 on stock - going to see if I can get CM installed now.
Click to expand...
Click to collapse
Ok, so I managed to get CM 10.2 installed (the latest stable version). I'm having an issue with v11 though.
I downloaded the most recent nightly build and try to install it (after flashing the boot.img), but get the following message:
Code:
Installing '/sdcard/cm-11-20140315-NIGHTLY-ville.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11 <cut off here>
Error flashing zip '/sdcard/cm-11-20140315-NIGHTLY-vil <cut off here>
Updating partition details...
Unlike the last few times I tried updating, where I got a clear error (like bootloader or hboot errors), the log doesn't seem to specify why the update failed.

zodac01 said:
Ok, so I managed to get CM 10.2 installed (the latest stable version). I'm having an issue with v11 though.
I downloaded the most recent nightly build and try to install it (after flashing the boot.img), but get the following message:
Code:
Installing '/sdcard/cm-11-20140315-NIGHTLY-ville.zip'.
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11 <cut off here>
Error flashing zip '/sdcard/cm-11-20140315-NIGHTLY-vil <cut off here>
Updating partition details...
Unlike the last few times I tried updating, where I got a clear error (like bootloader or hboot errors), the log doesn't seem to specify why the update failed.
Click to expand...
Click to collapse
It might be the recovery, I think CM11 needs a modified version of TWRP 2.6.3.0, its in the OP of the CM11 thread.
http://forum.xda-developers.com/showpost.php?p=47483838&postcount=1
Edit: You should also be able to use TWRP 2.7.0.0 : http://techerrata.com/browse/twrp2/ville

rosswhite said:
It might be the recovery, I think CM11 needs a modified version of TWRP 2.6.3.0, its in the OP of the CM11 thread.
http://forum.xda-developers.com/showpost.php?p=47483838&postcount=1
Edit: You should also be able to use TWRP 2.7.0.0 : http://techerrata.com/browse/twrp2/ville
Click to expand...
Click to collapse
Dammit, it was actually in the OP. I really should have seen that. Sorry for wasting your time - that was the problem. I've got 4.4.2 running nicely now.
Thank you very much for your time and patience.

zodac01 said:
Dammit, it was actually in the OP. I really should have seen that. Sorry for wasting your time - that was the problem. I've got 4.4.2 running nicely now.
Thank you very much for your time and patience.
Click to expand...
Click to collapse
No problem at all, glad you got it sorted.

Hi,
I'm having a similar problem with flashing CM11 nightlies. This is what I have done:
I have been running MaximusHD for a couple of months. Before that I was running CM11 nightlies just fine.
I used this guide (http://forum.xda-developers.com/showthread.php?t=2322755) to successfully downgrade to hboot 2.15. I then ran MIUI for a few days, which worked fine, but I still wanted the AOSP goodness that you get with a CM-based ROM, so I decided to change to the official CM11 nightlies.
I then tried to flash CM11 (and also PA and Vanir, both based on CM11, plus several other versions of the nightlies, which I found on download.cyanogenmod.com) in TWRP 2.7.0.0. Each time failed with the error: "E:Error executing updater binary in zip 'name-of-zip'".
Then I looked at the CM11 OP on XDA (http://forum.xda-developers.com/showthread.php?t=2528113). I read that you must have one of the two "updated recoveries". While I thought that the zips should flash on TWRP 2.7.0.0, I flashed those recoveries via fastboot also. When flashing the same files as above on the modified TWRP 2.3.3.0, I got exactly the same error as I did with 2.7.0.0. When I tried flashing the ROMs on ClockWorkMod, I got a "Status 7" error.
I googled around a bit and found some (old!) posts on various forums that said that there was a recovery called philz-touch that seemed to be working for some people. I downloaded it, flashed it, and got another "status 7" error when I tried to flash any of the zips.
Then I tried using several versions of TWRP (all the ones here http://techerrata.com/browse/twrp2/ville from 2.3.3.0 to 2.7.0.0 to be precise) and tried flashing each of the zips again. Still no luck.
Other things I have tried:
*I re-ran the steps here (http://forum.xda-developers.com/showthread.php?t=2322755) to ensure that it had definitely worked the first time.
*I tried using the hboot 2.15 and 2.13 (both modded and unmodded) that I found here (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266)
*I tried re-downloading the ROM zips that I had been flashing to make sure that none of them had been corrupted in any way.
*I tried flashing the CM10.2 stable ROM that I found on download.cyanogenmod.com. It flashed no problem and booted fine with no fuss.
I feel like I am the only one on the internet who is having these issues even after changing to the updated recoveries! Please excuse my English, it is not my first language! I would really appreciate some help on this, as I have absolutely no idea what to do.
Thank you very much!

c1aran said:
Hi,
I'm having a similar problem with flashing CM11 nightlies. This is what I have done:
I have been running MaximusHD for a couple of months. Before that I was running CM11 nightlies just fine.
I used this guide (http://forum.xda-developers.com/showthread.php?t=2322755) to successfully downgrade to hboot 2.15. I then ran MIUI for a few days, which worked fine, but I still wanted the AOSP goodness that you get with a CM-based ROM, so I decided to change to the official CM11 nightlies.
I then tried to flash CM11 (and also PA and Vanir, both based on CM11, plus several other versions of the nightlies, which I found on download.cyanogenmod.com) in TWRP 2.7.0.0. Each time failed with the error: "E:Error executing updater binary in zip 'name-of-zip'".
Then I looked at the CM11 OP on XDA (http://forum.xda-developers.com/showthread.php?t=2528113). I read that you must have one of the two "updated recoveries". While I thought that the zips should flash on TWRP 2.7.0.0, I flashed those recoveries via fastboot also. When flashing the same files as above on the modified TWRP 2.3.3.0, I got exactly the same error as I did with 2.7.0.0. When I tried flashing the ROMs on ClockWorkMod, I got a "Status 7" error.
I googled around a bit and found some (old!) posts on various forums that said that there was a recovery called philz-touch that seemed to be working for some people. I downloaded it, flashed it, and got another "status 7" error when I tried to flash any of the zips.
Then I tried using several versions of TWRP (all the ones here http://techerrata.com/browse/twrp2/ville from 2.3.3.0 to 2.7.0.0 to be precise) and tried flashing each of the zips again. Still no luck.
Other things I have tried:
*I re-ran the steps here (http://forum.xda-developers.com/showthread.php?t=2322755) to ensure that it had definitely worked the first time.
*I tried using the hboot 2.15 and 2.13 (both modded and unmodded) that I found here (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274&nocache=1&z=674317537341266)
*I tried re-downloading the ROM zips that I had been flashing to make sure that none of them had been corrupted in any way.
*I tried flashing the CM10.2 stable ROM that I found on download.cyanogenmod.com. It flashed no problem and booted fine with no fuss.
I feel like I am the only one on the internet who is having these issues even after changing to the updated recoveries! Please excuse my English, it is not my first language! I would really appreciate some help on this, as I have absolutely no idea what to do.
Thank you very much!
Click to expand...
Click to collapse
You just got bad luck and probably missed the right recovery. Starting with 1/05 nightly you need a special recovery due to some CM commits. It is an unofficial 2.7.0.8 and you can find it by looking in CM11 official thread in the last pages. It is posted by intervigil a link to CM wiki from where you can download it. You will need this recovery to flash any CM nightly newer than 1/05 and also for any ROM that's based on CM tree and build lately.
The TWRP 2.7.0.0 was fine as long as you flash an older nightly or a ROM that doesn't have those commits yet.
I'm on the phone right now but I'll try to look for a link and give to you if you don't find it
Edit: Here you go...
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
Sent from nowhere over the air...

Rapier said:
You just got bad luck and probably missed the right recovery. Starting with 1/05 nightly you need a special recovery due to some CM commits. It is an unofficial 2.7.0.8 and you can find it by looking in CM11 official thread in the last pages. It is posted by intervigil a link to CM wiki from where you can download it. You will need this recovery to flash any CM nightly newer than 1/05 and also for any ROM that's based on CM tree and build lately.
The TWRP 2.7.0.0 was fine as long as you flash an older nightly or a ROM that doesn't have those commits yet.
I'm on the phone right now but I'll try to look for a link and give to you if you don't find it
Edit: Here you go...
LINK REMOVED
Sent from nowhere over the air...
Click to expand...
Click to collapse
Hi,
I got a bit frustrated last night and must have missed that information in the CM11 thread. I had a look at that link and it has fixed my issues. Thank you very much!

Step-by-Step to InsertCoin

Hey Guys, cause i can't getting S-Off in case of a Secured STOCK-ROM and secured Kernel i need to change it.
I wanna get now
[NIGHTLIES][4.4.2]CyanogenMod 11.0 for AT&T HTC One Mini - m4 - THE NEW ROM
and
[KERNEL] [CM11] [S2W/DT2W] Sweep2Wake/DoubleTap2Wake Kernel for CM11 - THE NEW KERNEL
after that i think i can get my S-off and finally flashing InsertCoin till cm11 is stable.
First Question:
Is that possible to avoid my problem with S-off cause i am changing Rom and Kernel?
Second Question:
When i switch from cm11 nightlies to Insertcoin will i get any problems cause the kernel is only for CM11?

I flashed insertcoin 2.6 without s off, from cyanogenmod without any problems, just make sure that you use the latest version of twrp. There is also 2.7 but I think you need s off for that, and I heard that there are some problems with flashing that version.
Sent from my HTC One mini using XDA Free mobile app

ziedje said:
I flashed insertcoin 2.6 without s off, from cyanogenmod without any problems, just make sure that you use the latest version of twrp. There is also 2.7 but I think you need s off for that, and I heard that there are some problems with flashing that version.
Sent from my HTC One mini using XDA Free mobile app
Click to expand...
Click to collapse
Well...i flashed todax cm and packman without any problems!
But when i am going to flash insert coin i am not getting any happy end...after reboot i am still on the last rom that flashed? Same things have happened to Stock-Rom and now to Pac-man and CM
I am done with inserctoin ;D

aJay2k1 said:
Well...i flashed todax cm and packman without any problems!
But when i am going to flash insert coin i am not getting any happy end...after reboot i am still on the last rom that flashed? Same things have happened to Stock-Rom and now to Pac-man and CM
I am done with inserctoin ;D
Click to expand...
Click to collapse
just flash the firmware again by miniwhooper and itll fix the problem...

htconemini said:
just flash the firmware again by miniwhooper and itll fix the problem...
Click to expand...
Click to collapse
I had an ordeal getting IC on my mini, the main problem was the TWRP 2.7.1.1 dropped my USB connection which then meant I had no access to Sideload or ADB and couldn't send the zip to my phone.
Pre checks that you will need to make sure you have in place;
HBOOT 2.22 - http://forum.xda-developers.com/showthread.php?t=2759131
CID - 11111111 - http://forum.xda-developers.com/showthread.php?t=2789272
S-OFF (I used Rumrunner) - http://forum.xda-developers.com/showthread.php?t=2789272
TWRP - 2.7.1.1 - This version is a must as it uses the new partition layout
If you wipe everything apart from Data it will remove the existing Rom, then install IC 3.0.3
Once it is installed flash the boot.img that is inside the IC 3.0.3 zip and will stop getting boot loop.
Hope this helps