Database Info

[Q] I need help with S-Off/Installing ROMs on hboot 1.14. See my problem?

So I've done the procedures correctly from the Facepalm S-Off for HTC One S and I still don't have S-Off.
I got to the last process of getting S-Off, did the:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
then rebooted to bootloader to see if I have S-Off, but then I still don't.
I read online somewhere that with S-Off, I could install a ROM easily through recovery, is it true?
I also need help installing ROMs on this phone ):
Here's the story:
I hardbricked my old HTC so I got a new one. My old one, one that I bought after graduation around June, it had hboot 1.09 and was able to install ROMs easily in twrp while I was S-On+Unlocked Bootloader ONLY. No SuperCID or S-Off. So, I bought a new HTC One S from someone selling it on Craigslist. It had hboot 1.14, which I did not check yet. I bought it, so happy I got another One S until I realized I was only getting EDGE/2G. I read somewhere online where it was part of T-Mobile's update that messed it up, and a way to fix it was to install a new ROM. Any ROM I tried installing wouldn't go past the boot animation screen. Let's say I installed BB7, it wouldn't go past the boot animation.
If anyone can help, please. I'm on a 4g plan on T-Mobile getting only EDGE/2g and not able to install any other ROMs w/out getting stuck on boot animation. Old phone was faster than this.
HTC One S | hboot 1.14 | radio 1.08 | SuperCID | Stock Rom atm (until I install new ROM)
If anyone needs any additional info to assist in my doing, feel free to ask. Thank you!

dinodustin said:
So I've done the procedures correctly from the Facepalm S-Off for HTC One S and I still don't have S-Off.
I got to the last process of getting S-Off, did the:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
then rebooted to bootloader to see if I have S-Off, but then I still don't.
I read online somewhere that with S-Off, I could install a ROM easily through recovery, is it true?
I also need help installing ROMs on this phone ):
Here's the story:
I hardbricked my old HTC so I got a new one. My old one, one that I bought after graduation around June, it had hboot 1.09 and was able to install ROMs easily in twrp while I was S-On+Unlocked Bootloader ONLY. No SuperCID or S-Off. So, I bought a new HTC One S from someone selling it on Craigslist. It had hboot 1.14, which I did not check yet. I bought it, so happy I got another One S until I realized I was only getting EDGE/2G. I read somewhere online where it was part of T-Mobile's update that messed it up, and a way to fix it was to install a new ROM. Any ROM I tried installing wouldn't go past the boot animation screen. Let's say I installed BB7, it wouldn't go past the boot animation.
If anyone can help, please. I'm on a 4g plan on T-Mobile getting only EDGE/2g and not able to install any other ROMs w/out getting stuck on boot animation. Old phone was faster than this.
HTC One S | hboot 1.14 | radio 1.08 | SuperCID | Stock Rom atm (until I install new ROM)
If anyone needs any additional info to assist in my doing, feel free to ask. Thank you!
Click to expand...
Click to collapse
Did you try fastboot flashing the boot.img?

dbrewer24 said:
Did you try fastboot flashing the boot.img?
Click to expand...
Click to collapse
Yes, I did that before flashing the ROM zip in twrp

dinodustin said:
Yes, I did that before flashing the ROM zip in twrp
Click to expand...
Click to collapse
Have you tried doing it after? I have seen different instructions that say to do it different ways.

I have heard about the data issue too. I heard you could just go to network settings. change it to GSM only and then reboot. then switch back to Auto and rebooted again and it would come back (not an official solution... just something I read on here somewhere)
I am not have this issue.
regarding flashing a new ROM.... the phone should not be doing this...
I would go through the final steps of S-off again and see if you can get it to work.
I have heard of some issues that people are having... so I have not tried S-off yet... It doesnt bug me... it takes two more seconds to use fastboot.
just keep trying with different process... like hard reset then flash. or recover an old ROM then wipe and flash... IDK... just trying to help.
good luck

dbrewer24 said:
Have you tried doing it after? I have seen different instructions that say to do it different ways.
Click to expand...
Click to collapse
Like which instructions? I've tried to flash through TWRP, but I've seen other people have problems with flashing through TWRP with hboot 1.14, which includes me. So, I've tried that method and using CMD to fastboot it. Both didn't go so well. I also haven't tried testing other ROMs cos I've tried to flash 2 different ROMs (BB7, Liquid Smooth, JellyBam 4.1.0), but all 3 of them stayed on the boot animation screen and I never got to use my phone. My solution to those not working since I'm not able to flash any ROMs was to Go into Bootloader> Relock Bootloader > Go to Fastboot > & Ran RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe
Ryandroid86 said:
I have heard about the data issue too. I heard you could just go to network settings. change it to GSM only and then reboot. then switch back to Auto and rebooted again and it would come back (not an official solution... just something I read on here somewhere)
I am not have this issue.
regarding flashing a new ROM.... the phone should not be doing this...
I would go through the final steps of S-off again and see if you can get it to work.
I have heard of some issues that people are having... so I have not tried S-off yet... It doesnt bug me... it takes two more seconds to use fastboot.
just keep trying with different process... like hard reset then flash. or recover an old ROM then wipe and flash... IDK... just trying to help.
good luck
Click to expand...
Click to collapse
I'll try changing my network settings and get back to you on that.
How long would you wait on the Boot Animation screen? Cos I waited for about 5 minutes for it to load and it never loaded all the way.
I've tried the final step +3 times. The last few times I've tried it, it looked successful when I saw that my CMD sent the file and it said "OKAY", so I rebooted into my Bootloader like the very last step Facepalm's S-Off guide had said, but I didn't see what I was looking for ):
I've tried hard reset and flash, no luck. I'll try the old ROM thing.
It's such a hassle to get back to a working ROM, which you all know is phone's stock ROM I've been using, with the RUU exe.

suggestion
If your s off u should try flashing the .1.09 hboot, with s off its easier than ever to upgrade or downgrade an hboot, I have had throuble on higher hboots to even with s off

dinodustin said:
So I've done the procedures correctly from the Facepalm S-Off for HTC One S and I still don't have S-Off.
HTC One S | hboot 1.14 | radio 1.08 | SuperCID | Stock Rom atm (until I install new ROM)
If anyone needs any additional info to assist in my doing, feel free to ask. Thank you!
Click to expand...
Click to collapse
I have a Tmous too, the only way i got S-off was installing previously all t-mobile updates, ithen was easy getting s-off, but i don't know if that will solve your 4G problem, because i never had that.
(sorry about my english)
charly

Sorry I got ahead of my self I my post, I could only s off on viper 1.2 it was wierd, but let me ask u this do u get error 92 or 99 after flashing the zip

Ice Master Ben said:
Sorry I got ahead of my self I my post, I could only s off on viper 1.2 it was wierd, but let me ask u this do u get error 92 or 99 after flashing the zip
Click to expand...
Click to collapse
The very first time i get 92 an then failed in the second part of "pushing soffbin", when i tried again, i get error 99, but then i read some post about powering off the device, and it worked i get again error 92 and worked fine.

I had the same error and situation, first time error 92 but not after that,keept getting error 99 keept trying with diffrent Roms until I got the 92. I was on the 1.09 hboot the funny part is since I have s off I upgraded to the latest hboot 2.15( thanks to the flashable zips in the theam section) to my surpprize I could not flash viperon that hboot, so I went back to my 1.09 hboot and everything worked really good like always, so my poqint is were still having problems on higher hboots even with s off why?????, the only good thing about s off I have found is thanks to the flashable zips we can upgrade or downgrade the hboot just by flashing it, now its back to the 1.09 hboot

Ice Master Ben said:
If your s off u should try flashing the .1.09 hboot, with s off its easier than ever to upgrade or downgrade an hboot, I have had throuble on higher hboots to even with s off
Click to expand...
Click to collapse
Related to this, i have S-Off and Hboot 1.09, yet am still having problems flashing the latest daily CM 10.1 roms to by One XL, any suggestions?
I'm getting an immediate FAILED error in TWRP 2.6

Try twrp 2.3.3.0 it's supposed to be the most stable
Sent from my HTC One S using xda app-developers app

[Q] Can not get any Rom or Ruu to flash my soft bricked device

New to HTC One S.
Device Sim unlocked but branded Bell Mobility, was running 4.1.1 hboot 2.15 Dev Unlocked and I am able to use fastboot to push boot images and recovery images. I am able to mount the internal SD to my computer and copy zips. However nothing will flash. Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
P.S. when I flashed the boot images for the rom it honestly wiped my internal SD and I lost my nandroid... wishing I had copied it to my computer.
Open to advice! thanks!
WiL

citats said:
New to HTC One S.
Device Sim unlocked but branded Bell Mobility, was running 4.1.1 hboot 2.15 Dev Unlocked and I am able to use fastboot to push boot images and recovery images. I am able to mount the internal SD to my computer and copy zips. However nothing will flash. Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
P.S. when I flashed the boot images for the rom it honestly wiped my internal SD and I lost my nandroid... wishing I had copied it to my computer.
Open to advice! thanks!
WiL
Click to expand...
Click to collapse
Have you tried flashing with an older version of twrp
Verstuurd van mijn HTC One S met Tapatalk

citats said:
New to HTC One S.
Currently I have twrp 2.4.4.0 and am hopeful someone might have a nandroid for Bell... or able to create one and share.
Click to expand...
Click to collapse
Use 2.3.3.0 instead...

Thanks guys, I have actually tried 2.3.3.0 due to reading that in another thread. What I see is I can get various aroma installers to start, but at the actual install they seem to fail gaining access to areas on the phone. It's worth mentioning that I have reflashed stock boot img and stock recovery, relocked and attempted various RUU's but I understand that the hboot at 2.15 is most likely why that method fails.
I'm unlocked again but I think I'm going to try reflash stock recovery relock clear and reset all storage etc. then unlock use twrp and re-attempt a flash.
Any suggestions on a rom that should'nt have issues with hboot 2.15?

To flash RUUs you need to be on stock recovery, not custom.
2.15 came with JB. Trickdroid or ViperOneS would be sense roms, else you could flash CM 10.1 or derivates (AOSP/AOKP).
As long as you flash the according kernels in fastboot mode you can also use ICS roms. That doesn't matter.
--- edit
as with 2.15 you could only flash the 3.16 RUU which still isn't available (the one here is for ONE S SE and exits with errors. To flash earlier RUUs you will need an earlier bootloader version. There are two ways: To downgrade bootloader or s-off. As downgrading is a pain you should think about s-off.

Thank You
Yes I was on stock recovery and stock boot img and relocked during that attempt.
does the hboot version matter?
(based upon what I have read it won't flash if my hboot is newer)

Ok, just answered this as edit while you posted. lol

Thank You again!
I have looked into downgrading and a pain might be an understatement I'm looking into the One S toolkit to see what i can do for me... Here's hoping the RUU with hboot 2.15 gets leaked soon.

Let me pm you with a few useful links for a s-off device this evening (Germany, UTC +1) as it's 5:45 in the morning here and I've got to go to work now... :laugh:

rootrider said:
Let me pm you with a few useful links for a s-off device this evening (Germany, UTC +1) as it's 5:45 in the morning here and I've got to go to work now... :laugh:
Click to expand...
Click to collapse
OK that would be great thanks!
WiL

Holy crap that was painful...
I once again have a rom running! I did so many things but in the end I pushed Energy Rom to the device and it's boot.img after wiping multiple times reformating. Energy Rom is the only one that would complete install without write errors. Very strange stuff but for now i am happy.
Thanks again man!

Damn, I searched this thread for 20 minutes... :cyclops:
Which recovery are you using?
Anyway you should better use TWRP <= 2.3.3.0 for flashing roms.
(gonna write your pm now, will take some time and sorry for the delay!)

I'm all good now. Running Venom and very happy. I appreciate your efforts.
The recovery question tho I had to swap back and forth between twrp 2.3.3.0 and the most recent cwm. Mainly because of I could only send adb via twrp and I could only use adb shell with cwm, the nightmare is over!
Sent from my HTC One S using xda app-developers app

[HELP] T-mobile UK Soft Brick Noob

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

[Q] Flashing RUU on s-off?

Didn't find to much related to specifically to what I want to do.
I was tinkering with my software and messed something up and won't boot.
I can seem to find a strict stock rooted rom from t-mobile
Can I do the following without messing up my phone?
I already have s-off and twrp and a none working rom.
I want to relock bootloader, flash ruu
unlock again and flash recovery and root file.
I think this should work without messing up the phone and I should still have s-off right?

M9x3mos said:
Didn't find to much related to specifically to what I want to do.
I was tinkering with my software and messed something up and won't boot.
I can seem to find a strict stock rooted rom from t-mobile
Can I do the following without messing up my phone?
I already have s-off and twrp and a none working rom.
I want to relock bootloader, flash ruu
unlock again and flash recovery and root file.
I think this should work without messing up the phone and I should still have s-off right?
Click to expand...
Click to collapse
I've ran an RUU a couple times and still had S-off when it was done. It should not impact that at all.

Or you can skip all that and just flash the t mobile ROM in the dev section.
But, yeah, you will keep soff through the ruu
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me

No need to relock bootloader if s-off. You should flash stock recovery so and use a CID according to your RUU file.

Stock recovery not needed.
Just ruu away
Verstuurd van mijn HTC One S met Tapatalk

Oooh
I also thought too you needed to re lock to flash a ruu.
I guess that is only if not s off then.
Just need to match cid though still.

SCID will work with any RUU. But you shouldn't use it if you insist to upgrade by OTA... Some people reported a brick this way.

Updating EU RUU from 2.31.401.5 to 3.16.401.8 (going from a CM10.1 version)
Well here is what I've done if it can help some. No warranty that it'll work for everyone, but let's go:
First thing : I've started with CM10.1, S-OFF, SuperCID (11111111) and TWRP 2.5.0.0
I DID NOT relock the bootloader and NOT put back the original Recovery
1) I've put back my original CID (EU Bouygues eg. HTC__203. You should put your original one). Fortunately, I had the original mmcblk0p4 file backup (just copy back the original file to /dev/block. See here : http://forum.xda-developers.com/showthread.php?p=26516911#post26516911).
2) once my original CID has been put back (still S-OFF and TWRP and not relock), I've started in bootloader mode the RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5 and let things run
3) after the installation and reboot, I went to Parameters/Update/Check to force the JB update 3.16.401.8 download.
4) I've let the JB update to be performed (several reboot): all went fine. Going into fastboot, I'm still Unlocked / S-OFF / HTC__203 (original) / Radio 1.11.50 and HBOOT 2.15.000. Sounds good !
5) I went back into fastboot to re-flash the TWRP 2.5.0.0 (fastboot flash recovery openrecovery-twrp-2.5.0.0-ville.img)
6) I then reboot into Recovery : now TWRP is back ! In TWRP, try to reboot into bootloader. TWRP will warn you that you're not ROOT and suggest to install root on your phone. Hit YES.
7) Reboot normally your phone : you should have now a Super SU Installer icon in your apps. Open it, choose install via TWRP, and you're good to go! You've now the latest HTC JB sense version with root.
Optional :
-You can perform a full TWRP backup (with Sense/original CID) in case of further HTC update (?)
-You can put back your SuperCID if wanted
Now if you want to test the CM10.1-3.4 kernel here http://forum.xda-developers.com/showthread.php?t=2302248, it's booting fine (after full wipe)
Voilà !
Hope this helps

yeah
with the tmo model I can get the JB ruu right from HTC
I have just been having issues that I want to get stock and maybe root.
Will double check CID and just flash then.
I think hboot and radio on jb equivlent already but will try that.
Thank you

I wanted to post a little warning here, and relate what happened with my RUU update. First, I'm unlocked, s-off, Hboot 1.13.0000, superCID (11111111), running TWRP 2.5.0.0.
So I read somewhere that the latest RUU may not install correctly if on an older Hboot so I fastboot flashed the latest 2.15, no problems. Then I found a decrypted ROM that Hasoon2000 had posted thinking that this would give me the firmware I wanted, I believe this was based off of RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release. I then Fastboot flashed: (I didn't relocking bootloader or changing CID but I did first flash stock recovery because I wasn't sure it I needed to or not)
1. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip "name of ROM".zip
The script ran and everything flashed successfully, so I reflashed TWRP 2.3.3.0 and the phone booted just like stock ROM. At this point I checked the Hboot and it was 2.04 something! with a 1.11?? radio. (So this told me I likely wouldn't have needed to first flash the 2.15 Hboot not sure about this tho) I then tried to restore my backed up SDcard and here is where I ran into problems. My SDcard/internal storage only had 48.6MB of space! Nothing I did would change it I worked with this for several hours last night before giving up and this morning I thought to try running a different Tmobile RUU. Found this thread http://forum.xda-developers.com/showthread.php?t=2250573 and downloaded this Firmware package: http://www.filedropper.com/firmware_1 and ran the same fastboot commands (changed recovery back to stock which I probably wouldn't have needed to do...??) and everything flashed perfectly (I needed to run the "fastboot flash zip firmware.zip" the second time, which is normal). I now have my SDcard back with Hboot 2.15, radio 1.13, superCID and s-off yet, "hopefully" am ready to flash the new 3.4 updated stuff!
I suspect the reason for my problems lay in my flashing a euro ROM/RUU, but I really don't know that for sure. This is just what happened to me. Hope this helps a bit!

i believe i have an issue that is too challenging for me. i flashed the lates trickdroid and for some reason i couldnt get my radio to show. my baseband version was unknown. i tried to flash a new radio tto no avail. finally i flashed the jb ruu and now the rom will work for a couple of minutes and then reboot still with unknow baseband radio version. im s off with super cid. any thing to help woul be appreciated.

Did you run the ruu exe or how did you flash it?
Sent from my HTC VLE_U using xda premium

Clom801 said:
i believe i have an issue that is too challenging for me. i flashed the lates trickdroid and for some reason i couldnt get my radio to show. my baseband version was unknown. i tried to flash a new radio tto no avail. finally i flashed the jb ruu and now the rom will work for a couple of minutes and then reboot still with unknow baseband radio version. im s off with super cid. any thing to help woul be appreciated.
Click to expand...
Click to collapse
Have you tried the fastboot flash zip firmware.zip method? It's working great at updating firmware for all the AOSP ROMs.

TheArtiszan said:
Did you run the ruu exe or how did you flash it?
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
i ran the RUU. i tried the TMOUS ICS and EU JB
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
el_smurfo said:
Have you tried the fastboot flash zip firmware.zip method? It's working great at updating firmware for all the AOSP ROMs.
Click to expand...
Click to collapse
is that the new method posten in the development section? i will try
ok, tried it and it didnt work. still shows no signal with an x ans reboots after a couple minutes

You can try the tmous jb one.
That might be better as not a downgrade.
Not sure about the eu one but that could be why the ics one is not working.
Sent from my HTC VLE_U using xda premium

Clom801 said:
i ran the RUU. i tried the TMOUS ICS and EU JB
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
is that the new method posten in the development section? i will try
ok, tried it and it didnt work. still shows no signal with an x ans reboots after a couple minutes
Click to expand...
Click to collapse
Interesting thought... Try a cm based ROM. They use a radio in a different system folder. If it still doesn't work, sounds more like a hardware failure.

[Q]Solved ! Cricket- BRICK - Black Screen after HTC logo

Ok, so i got a problem. I wanted to return my phone to its stock, unrooted state so i could update to 4.1. Through the process, i installed a zip in recovery that installed but now my phone wont start. this was a stock JB rom title "JB_Crkt 2.04.1050.3_stock_odexed" but i didn't have JB installed i was till on stock 4.0.3 but rooted. I can get into fastboot and work from there but i cant boot into android, i just get a black screen after the 'HTC quietly brilliant' logo. I tried to install I am rooted and unlocked but with S-On. I hope that I just need to flash the stock ICS rom so i can get back to square one. do i need to turn s-off? if so, how do i do that without booting into android?
edit: i forgot to mention that my backup wont work ether. i think it became corrupt when i copied it to my compy.
I tried to install each of the zips below but none of them installed:
-JmzStockCricketSVDeodex.zip
-OTA_K2PLC_CL_ICS_40_Cricket_US_1.03.1050.7-1.03.1050.5_release_308166hdmxobmuj18gunis
-JmzStockK2UL_Deodex.zip
EDIT: SOLVED!!!!! Just needed to flash boot.img But now i have no service!!!
******TAMPERED*******
******UNLOCKED******
K2_PLC_CL SHIP S-ON RL
HBOOT-1.01.0000
RADIO-1.12.00.0208
OpenDSP-v7.2.0221.1123
eMMC-boot
Feb 8 1213, 16:29:40:-1

As you are S-On you have to flash the boot.img (from inside the rom.zip) over fastboot, after flashing the rom.
Did you do that?

old.splatterhand said:
As you are S-On you have to flash the boot.img (from inside the rom.zip) over fastboot, after flashing the rom.
Did you do that?
Click to expand...
Click to collapse
Thanks so much for the reply!
I cant seem to find a rom.zip that works. Would you happen to know a link? Do i install rom.zip from recovery or do i flash it in fastboot.
EDit. Awesome I did as u said and it workded great. Now im running JB thanks a bunch

Ok so its up and working now but i dont get any service. I installed k2ul_JB_2.14.401.6_stock_odexed_03_06_13 and then flashed the boot.img inside.......should i revert back to ICS??

I think you need to grab the radio.img for your device and flash it via fastboot.

Billgonzo said:
Ok so its up and working now but i dont get any service. I installed k2ul_JB_2.14.401.6_stock_odexed_03_06_13 and then flashed the boot.img inside.......should i revert back to ICS??
Click to expand...
Click to collapse
The ONLY Rom you should install is JB_Crkt 2.04.1050.3_stock_odexed.zip, because this is made from stock cricket files.
I'm not sure if it helps to install this or ICS.
Maybe radio.img helps but you need to be S-off to flash this.

Oops my eyes tricked me, I thought I read soff

old.splatterhand said:
The ONLY Rom you should install is JB_Crkt 2.04.1050.3_stock_odexed.zip, because this is made from stock cricket files.
I'm not sure if it helps to install this or ICS.
Maybe radio.img helps but you need to be S-off to flash this.
Click to expand...
Click to collapse
Sweet!!!! that rom worked perfect! thanks for the help!!! Now my phone is all good!