Hi guys
I'd like to know if it's possible to root my phone and get S-OFF because I want to run MaximusHD on my One S.
So the 'specs' are the following
*** LOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
Android 4.1.1
Sense 4+
3.16.401.9
SDK 4.63
HTCExtension_Sense45_2
If it is possible what tutorial should I follow? And is SuperCID necessary voor MaximusHD?
Thanks!
From here, your options are:
-Get an unlock code from htcdev and unlock the bootloader. This will let you flash the Maximus ROM. You are still S-ON at this point so you need to flash the boot.img file that came with the ROM after flashing the ROM using a custom recovery like TWRP
-Get SuperCID and use Facepalm to get S-OFF. From here you can just flash the ROM. Done.
-Use Moonshine to get S-OFF. This may work... your stock software is not one of the officially supported versions...
I think s-off is really needed, why?
Upgrading hboot can normally be done with s-on, but going back is the real problem then you need s-off.
Supercid is not needed. S-off is. (sometimes supercid is needed temporarily to get s-off)
The .9 firmware is problematic for s-off with facepalm. .8 will work. (you maybe can reruu to .8)
Or Try moonshine, check 4 compatiblity first.
Verstuurd van mijn HTC One S met Tapatalk
I am having the same problem when trying to get S-OFF. I have succesfully rooted and installed the Super CID. But when entereing the following command during the Facepalm S-OFF process, it fails:
Code:
c:\Development\android\UNLOCK>adb shell su -c "/data/local/tmp/soffbin3"
Segmentation fault
My software version is also .9. So maybe just this partition part is locked with this software version.
I have already tried installing RUU .8, but it failed the first time. Will do it again the other day.
It is possible considering I had the same Hboot and specs as you did.
To get S-OFF, I first ran the 3.14.531.11 RUU (I have T-Mobile) [Note: make sure to lock the bootloader before you run the RUU - fastboot oem lock] The RUU can be found http://www.androidruu.com/index.php?developer=Ville <- that thread. Considering you might be using a different network and what not, just make sure the supported RUU for moonshine is the one you run for you phone.
After that I ran moonshine S-OFF. I tried with Windows 8, I kept getting stuck on the process. What I ended up doing was partitioning a spare Harddrive and installing Ubuntu on it (partitioning is part of the installation). You can maybe run it from the disk as well, but I have not tried it. Moonshine worked the first run for me and got S-OFF.
With the MaximusHD you need SuperCID as well, with S-OFF, you can just use the command fastboot writecid 11111111 when you got the fastboot usb.
Flash rom, follow the instructions for the firmware. Reflash the firmware if you have troubles with the internal SD.
My two cents, I tried Maximus, it's is nice, however I like using my phone has a wireless hotspot for my tablet, and it doesn't allow me that function. I used Dark Jelly instead and haven't had that problem. However tethering and bluetooth is causing me some troubles. Just throwing it out there. Hope this helps.
I have maximushd and I have no issues using my phone as a Wi-Fi hotspot. Didn't even have to install any separate apps for it
Sent from my HTC One S using xda app-developers app
rgrpark said:
I have maximushd and I have no issues using my phone as a Wi-Fi hotspot. Didn't even have to install any separate apps for it
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Weird, I might try reflashing MaximusHD then, it had a very nice look to it. Quick question, what network are you running on?
myl0h said:
Weird, I might try reflashing MaximusHD then, it had a very nice look to it. Quick question, what network are you running on?
Click to expand...
Click to collapse
I'm on the $30 t mobile Wal-Mart plan
Sent from my HTC One S using xda app-developers app
rgrpark said:
I'm on the $30 t mobile Wal-Mart plan
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'm running T-Mobile too, guess I have a mini project to do when I go home then.
Related
First off here's what I'm working with:
Rogers HTC One X
Cyanogenmod from http://forum.xda-developers.com/showthread.php?t=2205183
Recovery - TWRP 2.5
Hboot - 2.14
radio - 0.23a.32.09.29
Rooted - I don't think so
SuperCID - 22222222
S-OFF - No
Lock status - Unlocked with HTCDev after SuperCID
Story time:
After deciding to install cyanogenmod on the weekend I've run in to a myriad of issues. I was able to unlock, flash CWM recovery, and install Cyanogen fairly easily, but I ran into the issue where the touch screen doesn't work.
What I've done:
I've found the fix detailed here: http://forum.xda-developers.com/showthread.php?t=2159863, but have been unable to get all the prerequisites going. From the screen fix thread linked above I need to be rooted, s-offed, and superCIDed.
I believe I got the superCID working by following the steps in this post: http://forum.xda-developers.com/showpost.php?p=41482419&postcount=2 and fastboot oem readcid returns 22222222
After that I was unlocked before but locked and relocked with a new unlockcode from htcdev
For rooting, I've looked at the methods listed under Root on http://forum.xda-developers.com/showthread.php?t=1671237, but I'm not too sure where to find which firmware I'm on. That would be the version of cyanogen would it not. I've tried the x-factor method using All-In-One Toolkit from http://forum.xda-developers.com/showthread.php?t=1952426 to no avail, as well as SuperSU from http://forum.xda-developers.com/showthread.php?t=1673935 and this one: http://forum.xda-developers.com/showthread.php?t=1644167, but I don't think any method has worked so far.
In order to use S-Off I'm pretty sure you need to be rooted, so it of course it didn't work, what made me think I wasn't rooted was when I was going through the Facepalm S-Off guide here: http://forum.xda-developers.com/showthread.php?t=2155071 when I ran "adb shell su -c "/data/local/tmp/soffbin3" it would just me the error su: not found, which means your not in as root according to: http://forum.xda-developers.com/showthread.php?p=38278577#post38278577
I've also tried going back to stock using the RUU RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe from http://ruu.androidfiles.org/getdown...9.28L_10.103.32.24L_release_268972_signed.exe, but when I run it I get error 99: Unknown Error, and I if I look in the log it creates it says error 44 HBOOT mismatch. I'm running after relocking, and I've tried just grabbing the rom.zip from %temp%, extracting it and flashing the boot and system imgs, but it says the system.img is too big.
At this point I'd just like to get my phone to work. If I can get it with CM that'd be cool, but stock would be good too. Any help would be appreciated.
Thanks!
In cyanogenmod you have to allow adb root access in developer options.
To ruu without s-off you need to change your cid back to the default but you will brick if you update to 3.18 after. Best to s-off since you changed your cid.
Sent from my Sony Tablet S using xda app-developers app
exad said:
In cyanogenmod you have to allow adb root access in developer options.
Click to expand...
Click to collapse
The touchpad doesn't work in cyanogenmod though, that's the root of the issue
exad said:
To ruu without s-off you need to change your cid back to the default but you will brick if you update to 3.18 after. Best to s-off since you changed your cid.
Click to expand...
Click to collapse
I was trying to RUU before changing CID, but was running in to "FAILED (remote: 44 hboot version check fail)", when running the RUU mentioned in the OP
Ah I see the ruu must have had an older hboot version than the one on your phone. You cant downgrade firmware without s-off.
To fix your issue you will need to flash a sense rom and then s-off and then downgrade your touchscreen firmware. Then you can flash whatever evita rom you like.
Sent from my Sony Tablet S using xda app-developers app
exad said:
Ah I see the ruu must have had an older hboot version than the one on your phone. You cant downgrade firmware without s-off.
To fix your issue you will need to flash a sense rom and then s-off and then downgrade your touchscreen firmware. Then you can flash whatever evita rom you like.
Click to expand...
Click to collapse
Thank you very much!
I flashed the Sense build from http://forum.xda-developers.com/showthread.php?t=2293032 and was then able to S-Off. After that I was able to down grade the touchpad firmware and install cyanogenmod.
Thanks again for pointing me in the right direction
:victory:
I am looking for a Stock T-Mobile Jelly Bean image that won't brick my phone. I tried searching for one, but I couldn't find anything or I found RUUs for outdated versions of HBoot. I am trying to revert back to stock, but I am sorta scared to do so with an outdated RUU. I have HBoot version 2.15 and Radio version 1.13.50.05.31. Thanks in advance.
Would this be the RUU I have to download? http://bugsylawson.com/files/file/1...531-10305008l-release-309489-signed-ics-2exe/
I would just prefer a nandroid backup of the stock image that I can just flash with CWM.
I downloaded the RUU, I just need to know if that is the correct one for my phone before I use it. I really don't want a bricked phone. I checked the MD5sum already and it matches, that is the only thing holding me back.
Sent from my One S using xda premium
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
OccupyDemonoid said:
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
Click to expand...
Click to collapse
If you are on TMOB US then it's for you. Furthermore, you can match thr CID of your phone to that in the RUU.exe --> Firmware.zip --> android-info.txt.
You'll have to extract firmware.zip from temporary files when you run RUU without connecting phone.
Sent from my Nexus 7 using Tapatalk HD
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
The RUU installs the Stock Recovery automatically. You don't have to do anything extra.
You can find stock recovery (if you want to keep it for any purpose) inside the RUU (extraction would require you to run the RUU and then extract the recovery from Temporary Files)
OR
you can find it in the forums.
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
I believe that is the stock recovery. The red exclamation mark is telling you that you don't have access to it. Perfectly normal.
tivofool said:
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Click to expand...
Click to collapse
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
DroidLuvver said:
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
Click to expand...
Click to collapse
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
tivofool said:
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
Click to expand...
Click to collapse
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
DroidLuvver said:
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
Click to expand...
Click to collapse
It will install the newer hboot to 2.15
tivofool said:
It will install the newer hboot to 2.15
Click to expand...
Click to collapse
So I should be able to run the RUU with lower boot like mine and it will upgrade the boot to 2.15 -
Is it true that with 2.15 hboot, modifying the CID is not allowed ?
Any reason why I should stay with 1.13 HBOOT and not go to 2.15 Hboot? Meaning any disadvantages of upgrading to HBOOT 2.15 ?
Well, say you updated your phone via ota & your cid is European or something. And all of the ruus for that CID are lower hboots. If u are s-on and and needed to ruu you wouldn't be able to.
But there is a guide to run a ota.zip for those people, so it isn't hopeless.
So not too many disadvantages.
In fact I just installed the newest Rom and firmware today. So my hboot is 2.16.
And the gossip is that update will be officially put out by HTC in a few weeks.
Sent from my HTC One S using Tapatalk 2
Remember this.
if you want to go stock again in future (warranty purpose)
some providers have only provided an ota (only ruu with lower hboots) when upgrading to jb. So downgrading gets hard
It's not that easy to flash an ota as is a ruu.
If your s-off downgrading is no issue.
Verstuurd van mijn HTC One S met Tapatalk
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Bump
Sent from my One S using XDA Premium 4 mobile app
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
bump
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
evrycard said:
Look for 3.14.531.11. It should be available somewhere. Lock the phone back and RUU it. Then you can unlock again and S-OFF with moonshine.
Click to expand...
Click to collapse
He probably cannot downgrade from *.17 to *.11.
I don't know what parts of the firmware moonshine needs. But you could try downgrade using a OTA or Nandroid.
Same here
I'm pretty much stuck with a One-S Bootloader unlocked with S-on.
I can't find a way to get S-Off. Just googling and throwing prayers in the sky someone develops a way.
pyrocide said:
Well gave this a shot and after 5 hours I am back on CM10.2 with S-ON and latest firmware still.
Thanks for the help though. Cheers.
Anyone else got any idea?
Click to expand...
Click to collapse
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
havikx said:
If that procedure took you 5 hours... Maybe s-off isn't for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It took me 5 hours total to begin finding all req's and trying the above method, finding it not to work, redoing the RUU *.17 and getting BACK on CM10.2 and having a phone to make calls with. The method above took maybe 20-30 minutes of double checking and making sure i didn't miss something.
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
tivofool said:
Maybe PM this guy. He posted that it moonshine worked on .17.
http://forum.xda-developers.com/showpost.php?p=45955250&postcount=1091
Ask if he ran moonshine on Linux.
Click to expand...
Click to collapse
PM'd him for more info. Thanks!
So I was having problems getting s-off as well, eventually I got it done, but it was definitely a big trial and error process.
What I ended up doing was:
1) Get the 3.14.531.11 RUU from http://www.androidruu.com/index.php?developer=Ville (make sure you get the TMOUS one) This link is also provided in the first post in the Android development section
2) I ended up using Moonshine S-Off (http://forum.xda-developers.com/showthread.php?t=2325590) but I needed to use it in conjunction with running it on Ubuntu. Luckily I had a spare hard drive lying around. If you don't, I believe you can run it through the CD as well as long your burn the Ubuntu.iso on a disc. Plug in your phone to the computer and let it do its magic
3) From there, if you wanted to, you can change to SuperCID. Since you have s-off by then, you can change it from the fastboot usb in the bootloader with the line fastboot oem writecid 11111111 (double check, i'm just writing off the top of my head)
4) Then install roms and etc through the usual custom recovery
Note. I tried the Maximus HD, yes it was nice, but it didn't allow me to utilize my phone as a hotspot, so I ended up using the Dark Jelly rom instead. So far it's been very nice. The hotspot works, but the tethering portion is still unavailable. Just my two cents.
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
tivofool said:
My steps I took: (don't know if all were necessary)
Made a backup (nandroid) in recovery and saved it to my pc to be safe.
flashed stock recovery
locked bootloader
ran a RUU.exe to get on the supported firmware.
unlocked bootloader
Then I ran moonshine.
flashed recovery I had before
Restored the backup in recovery and had my original setup plus I was now S-off.
Click to expand...
Click to collapse
i can say that this worked for me as well. i didn't relock bootloader before installing the 3.14.531.11 ruu though. still worked for me. also installed moonshine on windows. ( guess i'm lucky )
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
You saved me so much time. Thanks!
bnd10706 said:
I had a hell of a time getting S-OFF pyrocide
Just like you I had H-boot 2.15 and the .17 firmware
here is what you do... this worked for me
download this RUU http://forum.xda-developers.com/showthread.php?t=2279588
adb reboot bootloader
fastboot oem lock
run the RUU
after RUU is loaded and all done 15-20 min
unlock your bootloader with HTC Dev tools
Run moonshine
Works. Promise
Click to expand...
Click to collapse
I do not understand meet all the requirement and I run it step by step and still gets stuck in step 3 moonshine I need urgent help, thanks
pyrocide said:
I have S4 Ville on firmware 3.14.531.17 and need to know if S-OFF is possible using whatever method available. Moonshine thread states that only 3.14.531.11 (T-MOB) is supported and haven't found any details in the Facepalm thread.
Anyone know for sure?
Click to expand...
Click to collapse
Test... click here
http://forum.xda-developers.com/showthread.php?t=2569755
[Q]Hboot/Firmware update 2.15 to 2.16 et al.
Sorry wrong thread.
Hello everyone!
A few weeks ago I had some problems with my rom being almost unusable. Got some help, see this thread for more info.
Right now I have CleanROM 7.0
Tampered/Unlocked
Evita PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19s 32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012
Don't have SuperCID, but I'm rooted.
The rom worked fine for a bit, but now I cannot connect to mobile networks and cannot make or receive calls. I can deal with a lot of problems with my phone, but not this is not one of them.
Another important glitch for CleanRom is that I cannot mount the SD card. I can do it through Fastboot and TWRP, but not inside the OS. This severely limits what I can do to the phone, and I haven't found anything to fix it.
Okay, so basically I need a new rom.
Cannot do anything through USB so I transferred .zip onto the phone and flash through TWRP.
assert failed: getprop ("ro.bootloader") == "2.12.0000"
getprop ("ro.bootloader") = 2.15.0000
Error in SD card ....... (Status 7)
FAILED
Maybe I need to update the bootloader? It's been a year and a half sine I initially rooted etc so I don't remember how I did it.
Tried this (unlock through HTC Dev): http://forum.xda-developers.com/showthread.php?t=1671396 got (./adb shell device not found)
Tried this (X Factor root exploit): http://forum.xda-developers.com/showthread.php?t=1952038
(Waiting for device...
adb server is out of date. killing...
cannot bind 'tcp:5037'
ADB server didn't ACK
* failed to start daemon *
error:
Device found.
Restoring first backup...
adb: unable to connect for backup)
Tried borrowing a friend's PC and install RUU, but I get error cannot connect through USB after initially telling me the device is connected.
Wanted to try this: http://forum.xda-developers.com/showthread.php?t=2242635 but all the links are removed.
Any ideas at all? Thanks!
What RUU...
I just tried RUU again, and I got error 159 Please get the correct ROM update utility and try again.
Okay! I was following instructions from the previous thread. Ignorance is bliss.
954wrecker said:
What RUU...
Click to expand...
Click to collapse
I got the RUU from here: http://forum.xda-developers.com/showthread.php?t=2119610
Chose the latest!
Supercid and soff before ruu or you'll brick
Sent from my HTC One XL using xda app-developers app
exad said:
Supercid and soff before ruu or you'll brick
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
So I'm trying this: http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Couldn't access the Spoof-CID.zip file because the website was glitched and wouldn't allow it. I found another Spoof-CID here: http://d-h.st/nSk
Hoping it's the right file I run it, and I get
"Restarting ADB
Pulling files
Checking files
Couldn't pull files from device. Your device is not altered.
Press any key to continue..."
I tried this: http://www.talkandroid.com/113533-att-htc-one-x-bootloader-unlocked/ so changed the CID to think it was Rogers. Got sent an unlock token by HTC and I flashed it, but there was supposed to come on the screen a disclaimer on step 13 (Step 13 On your phone you will now see the disclaimer..) nothing happened. Can I use this method to get SuperCID?
exad said:
Supercid and soff before ruu or you'll brick
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hey again, I managed SuperCID and S-OFF as you suggested. Someone else, also a Senior Member, told me that RUU while S-OFF would brick. Is this 100% sure not true?
S-on = brick. S-off you're okay
Sent from my VENOMized HoxL
S-on = brick.
S-off = safe.
Either you misunderstood or they were wrong.
Sent from my Evita
mollysue said:
Right now I have CleanROM 7.0
Tampered/Unlocked
Evita PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19s 32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012
Don't have SuperCID, but I'm rooted.
1. The rom worked fine for a bit, but now I cannot connect to mobile networks and cannot make or receive calls. I can deal with a lot of problems with my phone, but not this is not one of them.
2. Another important glitch for CleanRom is that I cannot mount the SD card. I can do it through Fastboot and TWRP, but not inside the OS. This severely limits what I can do to the phone, and I haven't found anything to fix it.
Okay, so basically I need a new rom.
Click to expand...
Click to collapse
1. Did you check your APNs? And add the one for your network?
2. A lot of Sense ROMs now have the glitch/bug that the sd card does not mount properly, with the dev options on and USB Debugging on It should auto mount as a portable media player (crap transfer speeds though)
Going to an AOSP ROM fixed my sdcard issues. Always be s-off before doing anything crazy.
Hi, I just unlocked and rooted my Boost One SV. I can't get S-Off and tried all methods - Revone, Moonshine, and Rumrunners. I did not try Facepalm because I read it does not work with jellybean. My device info is below
K2_CL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.12.50.0516
OpenDSP-V10.2.0268.0401
OS-
eMMC-boot 1024MB
I have ADB and Fastboot on Windows 7 PC. My phone is running latest OTA update Jelly Bean 4.2.2. Also I am running a modded TWRP with screenshot capability I found on another site. Any advice is always appreciated. TIA.
Is the model K2PLC_CL the same as K2_CL? If yes, just give facepalm a try. Last week I S-OFF-ed my sister's One SV with latest hboot using facepalm without any problem. Well the difference between her and you is that she owns a K2_UL. But as far as I experienced with my One S the "worst" thing that can happen if you follow the instructions and if your hboot is too high is that your are unable to push the modified mmcblk0p4 for receiving superCID.
Rumrunner usually works on 4.2.2 One SV. At least for all other variants of this phone.
Facepalm exploit should be gone since JB hboot.
The cricket and boost variant is NOT the same. For future reference, do not get them confused.
Use rumrunner universal and insure your device is properly prepped before attempting to use it to S-Off or else you will fail at trying to gain S-Off successfully. This will result in a user error of the current device holder - that being the individual who owns the device and fails to follow instructions or skip steps by taking "shortcuts"...
Sent from my C525c using Tapatalk
Modding.MyMind said:
The cricket and boost variant is NOT the same. For future reference, do not get them confused.
Use rumrunner universal and insure your device is properly prepped before attempting to use it to S-Off or else you will fail at trying to gain S-Off successfully. This will result in a user error of the current device holder - that being the individual who owns the device and fails to follow instructions or skip steps by taking "shortcuts"...
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Dunzo!! Facepalm moment! Yes it was user error. This time I extracted the complete universal zip file into my C Drive folder. Before, I just extracted soju.exe and that caused rumrunner to hang up. Thanks again. Any advice on any custom roms to flash for my device. Is ViperSv Rom the only one for this device?
biga1 said:
Dunzo!! Facepalm moment! Yes it was user error. This time I extracted the complete universal zip file into my C Drive folder. Before, I just extracted soju.exe and that caused rumrunner to hang up. Thanks again. Any advice on any custom roms to flash for my device. Is ViperSv Rom the only one for this device?
Click to expand...
Click to collapse
It's for K2_UL and K2_U. Support for K2_PLC_CL is in the works by my understanding.
It's not for K2_CL.
Sent from my C525c using Tapatalk
biga1 said:
Any advice on any custom roms to flash for my device. Is ViperSv Rom the only one for this device?
Click to expand...
Click to collapse
There is no real custom rom for this device (cm, pac, slim, etc). Viper and dream beats are stock with big/small modification. For best stability/performance you should debloat or even desense your stock rom, root it, and use xposed for desired mods. This combo work best for me.
old.splatterhand said:
Rumrunner usually works on 4.2.2 One SV. At least for all other variants of this phone.
Facepalm exploit should be gone since JB hboot.
Click to expand...
Click to collapse
i have the boost model on 2.21 i have tried rumrunner numerous times over the pas few days with no luck. i have also tried flashing viper rom and it always gets stuck at weather...mp4.
Rumrunner can be some kind of tricky, but i don't know at all, if it is still up and running (on any devices). It's along time ago, when i have heard last time from it.
Asfar as i know, Sunshine supports One SV. It needs a running Os and costs 25 USD. But it does a compatibility test beforepaying.