Related
I've been pondering whether or not to S-OFF my desire for a little while now but I'm not really sure if I should do it or not. Specifically because I can't find the risks of doing it (maybe I'm not looking hard enough though) and the potential benefits of doing it(i've seen some cool stuff such as widget locker themes but not much else).
If somebody could give me a good idea of whether or not it is worth it it'd be much appreciated
Sent using tapatalk. Get over it
the pros are that you will have r/w access to phone instead of r/o. also you can change your boot partitions to have more free internal memory.
but if you do not know what you're doing you can potentially brick your phone.
if you do so always check md5sums of downloaded files to avoid corrupted files.
jacketyjoe said:
I've been pondering whether or not to S-OFF my desire for a little while now but I'm not really sure if I should do it or not. Specifically because I can't find the risks of doing it (maybe I'm not looking hard enough though) and the potential benefits of doing it(i've seen some cool stuff such as widget locker themes but not much else).
If somebody could give me a good idea of whether or not it is worth it it'd be much appreciated
Sent using tapatalk. Get over it
Click to expand...
Click to collapse
mariosraptor said:
the pros are that you will have r/w access to phone instead of r/o. also you can change your boot partitions to have more free internal memory.
but if you do not know what you're doing you can potentially brick your phone.
if you do so always check md5sums of downloaded files to avoid corrupted files.
Click to expand...
Click to collapse
More internal storage is nice but what can I do with read and write access?
Is files being corrupted the only risk? is there any other way I can brick my phone (as in if I follow guides to the letter and the md5 checksums are the same).
Sent using tapatalk. Get over it
jacketyjoe said:
More internal storage is nice but what can I do with read and write access?
Is files being corrupted the only risk? is there any other way I can brick my phone (as in if I follow guides to the letter and the md5 checksums are the same).
Sent using tapatalk. Get over it
Click to expand...
Click to collapse
You get more internal storage through the r/w access, you can change partition tables, you can edit your boot animations/splashes and geeky stuff like that. If you're just a casual user there's not really any point in doing it, however if you like messing around with the ins and outs of your phone (which im guessing you are since your researching it), its a pretty cool thing to have. The only risk I know of is if you download a corrupt img that you're going to push to you phone or if somehow the connection between your pc and your phone is lost while your pushing the files, can brick the phone. So in order to avoid this make sure the md5 checksum is ok for the image you downloaded (use a program like hashcalc to check this) and make sure your phone has plenty of battery + dont trip over your usb cable while your pushing files
Personally I think there is no reason to S-off as long as you can't find a reason yourself why you would want to S-off. If you need to ask why you want to S-off don't do it. If you have a reason you can go for it. If you follow the procedures and check md5 (which should be in the procedures) there is no realistic risk, but I know form one person that he had a BSOD while using AlphaRev and that bricked his phone. That is just bad luck and can't be prevented.
So yes there is always a risk that something goes wrong, but that is the same risk that you get hit by a truck when you go outside even too you watch out.
I take no responsibility for what happens even too you should be good.
Another thing... as far as security goes, keep in mind that when you s-off, any app you give su rights too, also has full unrestricted access to your device
Sent from my HTC Desire using Tapatalk
xp4nd3r said:
You get more internal storage through the r/w access, you can change partition tables, you can edit your boot animations/splashes and geeky stuff like that. If you're just a casual user there's not really any point in doing it, however if you like messing around with the ins and outs of your phone (which im guessing you are since your researching it), its a pretty cool thing to have. The only risk I know of is if you download a corrupt img that you're going to push to you phone or if somehow the connection between your pc and your phone is lost while your pushing the files, can brick the phone. So in order to avoid this make sure the md5 checksum is ok for the image you downloaded (use a program like hashcalc to check this) and make sure your phone has plenty of battery + dont trip over your usb cable while your pushing files
Click to expand...
Click to collapse
Awesome, I'm still considering it. I know all about checking MD5 sums so you don't mess up everything, been flashing BIOS's on my computer for years
TheGhost1233 said:
Personally I think there is no reason to S-off as long as you can't find a reason yourself why you would want to S-off. If you need to ask why you want to S-off don't do it. If you have a reason you can go for it. If you follow the procedures and check md5 (which should be in the procedures) there is no realistic risk, but I know form one person that he had a BSOD while using AlphaRev and that bricked his phone. That is just bad luck and can't be prevented.
So yes there is always a risk that something goes wrong, but that is the same risk that you get hit by a truck when you go outside even too you watch out.
I take no responsibility for what happens even too you should be good.
Click to expand...
Click to collapse
I can find a few reasons but I'm not really sure its worth the risk. From what you guys are telling me the only risks are that you download a corrupt file, you accidentally pull out your phone or a freak of nature. From what I've been reading I'd be fine to RMA it if something went wrong though wouldn't I? If it was completely dead (i.e. brick) they wouldn't be able to tell what caused it would they?
AndroHero said:
Another thing... as far as security goes, keep in mind that when you s-off, any app you give su rights too, also has full unrestricted access to your device
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Which is a good thing to have
jacketyjoe said:
Which is a good thing to have
Click to expand...
Click to collapse
not if the application is malicious with full access they can do things like make calls without showing the dialer and send sms's without permission .....
AndroHero said:
not if the application is malicious with full access they can do things like make calls without showing the dialer and send sms's without permission .....
Click to expand...
Click to collapse
Of course, if you avoid said malicious applications everything should be good
Sent using tapatalk. Get over it
Does flashing a new radio, kernel, recovery need s-off? How about partitioning my sd card with Amonra, do i need s-off? I confused with the s-off description and just want to be sure.
Ghettonine said:
Does flashing a new radio, kernel, recovery need s-off? How about partitioning my sd card with Amonra, do i need s-off? I confused with the s-off description and just want to be sure.
Click to expand...
Click to collapse
Nothing of the above actions require s-off.
Sent from my HTC Desire using Tapatalk
Ghettonine said:
Does flashing a new radio, kernel, recovery need s-off? How about partitioning my sd card with Amonra, do i need s-off? I confused with the s-off description and just want to be sure.
Click to expand...
Click to collapse
All s-off does is give you write access to security locked areas of the nand chip while the device is booted ......
Sent from my HTC Desire using Tapatalk
So you are able to use a Custom ROM without having S-Off? because i just rooted my Desire, and i didnt flash any custom ROM, but i do have S-ON, i thought that you would have S-off when you've rooted it?
Btw i rooted it with Unrevoked 3.22
mathiasb2 said:
So you are able to use a Custom ROM without having S-Off? because i just rooted my Desire, and i didnt flash any custom ROM, but i do have S-ON, i thought that you would have S-off when you've rooted it?
Btw i rooted it with Unrevoked 3.22
Click to expand...
Click to collapse
you can still flash a custom rom just with an unrevoked root. To s-off your device you need to follow another process for instance the one here.
xp4nd3r said:
you can still flash a custom rom just with an unrevoked root. To s-off your device you need to follow another process for instance the one here.
Click to expand...
Click to collapse
Thanks! Then I don't have to read up on that s-off, as I just want to be able to save to sdcard
Offtopic: do I need to download a special radio if I want to install the newest Leedroid? I'm on a 2.2 FroYo, with a 32.43.00.32.U_5.09.00.20 RADIO (atleast I guess that my radio it says in my baseband in software info)
- Mathias
Sent from my HTC Desire using XDA App
It would be good to update to the latest radio, leedroids mini-site has download links and md5 checksums for the radios (make sure you check the md5 checksums, if it is different it can potentially brick your phone).
Sent using tapatalk. Get over it
Well, finally S-OFF'ed my phone, it was rather painless. The problem is that I can't flash the oxygen hboot because I can't get the Android sdk working
Sent using tapatalk. Get over it
Is this even possible to RUU back to the old OS then root? I downloaded this file
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.02 25_2_NV_VZW1.92_release_181303_signed.exe
I want to try it but I don't want to brick my device of only 2 days old... lol
Come on! Be bold for the rest of us! Lol..I think someone said they tried it and it didn't work with s-on, however it does work with s-off.
I've also read that it fails when trying to flash the Froyo RUU over GB. It didn't brick it or anything, though.
If it does work with S-Off, in theory, if you have 2.3, you could use at XTC clip to achieve S-Off, then use the RUU to downgrade to Froyo, then root, CWM, etc. Right?
beenz said:
I've also read that it fails when trying to flash the Froyo RUU over GB. It didn't brick it or anything, though.
If it does work with S-Off, in theory, if you have 2.3, you could use at XTC clip to achieve S-Off, then use the RUU to downgrade to Froyo, then root, CWM, etc. Right?
Click to expand...
Click to collapse
I think what they are primarily looking for right now is a temp root for 2.3.3 so we can use the s-off tool. The old root exploit was patched with the 2.3.3 update, without that we can't downgrade and use the tool to achieve s-off, correct me if I'm wrong.
Whatever they do I hope they do it quick I cannot take sense for another day lol.
Yeah, I think it may fail too. I like Sense, I just want to remove the garbage that comes on this thing.
Any RUU from Verizon suck as the one mentioned above, will work on S-OFF, that's the beauty of S-OFF you don't need a file signed by HTC... with S-ON that RUU should flash since it is by HTC, it may say main bootloader is older and fail I'm not sure... I'd put it into a PG32IMG.zip and flash in hboot.. you can do this with the .3 RUU and the .4 exe
andybones said:
Any RUU from Verizon suck as the one mentioned above, will work on S-OFF, that's the beauty of S-OFF you don't need a file signed by HTC... with S-ON that RUU should flash since it is by HTC, it may say main bootloader is older and fail I'm not sure... I'd put it into a PG32IMG.zip and flash in hboot.. you can do this with the .3 RUU and the .4 exe
Click to expand...
Click to collapse
I'm actually downloading it right now, going to try and just flash it, if that fails then going to try it with GoldCard.
Let us know if it works for you.
Sent from my ADR6350 using XDA Premium App
rm2011 said:
Let us know if it works for you.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
Tried .exe method, no go. Tried regular method by renaming, no good, funny part is it doesn't even give a error or nothing when it loads it up, it just goes back to the Bootloader menu. Then i tried the Gold Card method, no go, although i did format my card, but i read that once you have a Gold Card it stays a Gold card. So unfortunately, even if i did root this phone and didn't upgrade to 2.3, because i'm getting a much needed replacement i'm doomed for 2.3 anyway. Whelp i tried.
shoman24v said:
Is this even possible to RUU back to the old OS then root? I downloaded this file
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.02 25_2_NV_VZW1.92_release_181303_signed.exe
I want to try it but I don't want to brick my device of only 2 days old... lol
Click to expand...
Click to collapse
You try this yet?
EDIT: Sorry, when I was reading this thread the only post that came up was the original. Once I replied they all showed up. Weird, but apologies.
shoman24v said:
Is this even possible to RUU back to the old OS then root? I downloaded this file
RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.02 25_2_NV_VZW1.92_release_181303_signed.exe
I want to try it but I don't want to brick my device of only 2 days old... lol
Click to expand...
Click to collapse
I tried this way back before I got my xtc clip and the answer is no it will not work with s-on. It looks like its going to work and then displays a message about bootloader or something to that affect. I have it somewhere in these threads.
So here's a question off the top of my head. Probably not possible, but I'll ask anyway.
So the bootloader will only install HTC signed files, and we have HTC signed files of FroYo that the bootloader rejects. So there must be some kind of version check where it'll only flash a file with a higher version number than what's currently on the phone. If we knew where it was checking, would it be possible to modify a FroYo RUU file to report a higher version than the current GB so the bootloader thinks it's installing an upgrade instead of a downgrade?
Like I said, probably not possible, but it would seem to be logical.
ChrisDDD said:
So here's a question off the top of my head. Probably not possible, but I'll ask anyway.
So the bootloader will only install HTC signed files, and we have HTC signed files of FroYo that the bootloader rejects. So there must be some kind of version check where it'll only flash a file with a higher version number than what's currently on the phone. If we knew where it was checking, would it be possible to modify a FroYo RUU file to report a higher version than the current GB so the bootloader thinks it's installing an upgrade instead of a downgrade?
Like I said, probably not possible, but it would seem to be logical.
Click to expand...
Click to collapse
It does make sense, however the signature is generated from the contents of the file. If you change the contents of the file, it invalidates the signature and the boot loader won't load it. That is how HTC prevents you from modifying official HTC files.
ChrisDDD said:
So here's a question off the top of my head. Probably not possible, but I'll ask anyway.
So the bootloader will only install HTC signed files, and we have HTC signed files of FroYo that the bootloader rejects. So there must be some kind of version check where it'll only flash a file with a higher version number than what's currently on the phone. If we knew where it was checking, would it be possible to modify a FroYo RUU file to report a higher version than the current GB so the bootloader thinks it's installing an upgrade instead of a downgrade?
Like I said, probably not possible, but it would seem to be logical.
Click to expand...
Click to collapse
If you modified the file. It wouldn't be signed by HTC anymore.
If it is checked by md5, it can be spoofed.
http://www.win.tue.nl/hashclash/SoftIntCodeSign/
Sent from my ADR6350 using XDA App
slydweis said:
If it is checked by md5, it can be spoofed.
http://www.win.tue.nl/hashclash/SoftIntCodeSign/
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
I remember this being discussed before in the Eris forum. I can't find the thread, but I believe that the signature is somehow encrypted, and you would need the encryption key. I believe they even discussed if you could crack the encryption code, and although possible, it was not likely.
tpbklake said:
It does make sense, however the signature is generated from the contents of the file. If you change the contents of the file, it invalidates the signature and the boot loader won't load it. That is how HTC prevents you from modifying official HTC files.
Click to expand...
Click to collapse
I figured that, I just wondered if since all that would presumably need to be changed would be a single digit, if there would be any way to do it without screwing up the signature, like with a hex editor or something.
But, like I said, I figured it wasn't possible...
Hello all im hoping i dont get ridiculed for asking this but i need help rooting and and installing a custom recovery on my dads dinc. i I have a fair bit of knowlege with some of this but it appears to be nothing like rooting my little optimus v. i have found many guilds but they all seem to be from 2010. i know htc has a program for unlocking the bootloader but his hboot doesnt seem to be listed as a supported device. all he wants is a nice stable rom that will do away with the headaches of the stock sense rom (like the constant low memory warning). i can do all of this for him, im just a little confused as the best way of doing it. ive never had to deal with an htc before, im not even sure what the s-off is even for, so any help with this would be greatly appreciated
reaper420 said:
Hello all im hoping i dont get ridiculed for asking this but i need help rooting and and installing a custom recovery on my dads dinc. i I have a fair bit of knowlege with some of this but it appears to be nothing like rooting my little optimus v. i have found many guilds but they all seem to be from 2010. i know htc has a program for unlocking the bootloader but his hboot doesnt seem to be listed as a supported device. all he wants is a nice stable rom that will do away with the headaches of the stock sense rom (like the constant low memory warning). i can do all of this for him, im just a little confused as the best way of doing it. ive never had to deal with an htc before, im not even sure what the s-off is even for, so any help with this would be greatly appreciated
Click to expand...
Click to collapse
What hboot, radio, and android version is the phone currently on?
As for unlocking with htcdev, it makes you do an ruu which updates the hboot to a unlockable version.
S-off means security off and it allows you to flash unsigned images thru hboot such as new radios and splash screens.
The Android version is 2.3.4, and I can't remember how to get to the hboot to get that version number, I don't know were the radio version is
Sent from my LG-VM670 using Tapatalk 2
reaper420 said:
The Android version is 2.3.4, and I can't remember how to get to the hboot to get that version number, I don't know were the radio version is
Sent from my LG-VM670 using Tapatalk 2
Click to expand...
Click to collapse
You can get both the radio (baseband), and hboot versions by booting to hboot. Power off the phone, pull the battery and reinsert, and then hold vol down and power till a white screen appears (hboot). It will tell you both versions in the top left corner.
Hboot is 0.92.0000
Radio is 2.15.10.07.07
Sent from my LG-VM670 using Tapatalk 2
reaper420 said:
Hboot is 0.92.0000
Radio is 2.15.10.07.07
Sent from my LG-VM670 using Tapatalk 2
Click to expand...
Click to collapse
Then you need to follow this thread here to root and get s-off. http://forum.xda-developers.com/showthread.php?t=1306400
cmlusco said:
Then you need to follow this thread here to root and get s-off. http://forum.xda-developers.com/showthread.php?t=1306400
Click to expand...
Click to collapse
Great thanks for the help
Sent from my LG-VM670 using Tapatalk 2
So after reading that, am I right by thinking that I don't actually need to get s-off if I'm just going flash a new ROM
Sent from my LG-VM670 using Tapatalk 2
reaper420 said:
So after reading that, am I right by thinking that I don't actually need to get s-off if I'm just going flash a new ROM
Sent from my LG-VM670 using Tapatalk 2
Click to expand...
Click to collapse
Correct you can root and flash roms without being s-off. However s-off has some great advantages, like being able to flash radios, splash screens, and allows you to edit system files, along with some other stuff. S-off also makes it much easier to reroot should you somehow loose root in the future.
Hi highly recommend going S-OFF. As daunting as it may seem, it's really not that hard, and you won't regret it. Nothing really worked right for me S-ON, so just having S-ON alone might give you headaches.
yup if u already through the trouble to get root then why dont get s-off too, its really worth the time and trouble getting both root and s-off.
Howdy! Lemme preface all of this by saying that I'm less than a noob here....really inexperienced. Here's the background......
I rooted my DInc and I can't even remember which unrevoked tool I used. I was just reading along and punching commands and when the process was done I was rooted. I installed CWM successfully and flashed to CM7.2 which I've been running for quite some time. Lately I got an itch to try a JB ROM like infected, so when I looked into it, it clearly says I need S-off to accomplish that flash so I checked and realized I was S-on still.
At this point, I added the unrevoked-forever.zip to my sdcard root and tried to flash that ZIP by way CWM and i get these error messages:
E: unsupported radio version
E: update failed. Check/sdcard/soff.log
E: error in /sdcard/unrevoked-forever.zip (Status 42)
I am running Android version 2.3.7 and radio baseband version 2.15.10.12.20
Is this one of those things that I shouldn't be trying from CM7.2 and I should've dealt with before my initial flash to CM7.2?? Basically I'm totally freakin lost and in WAAAAY over my element, so any guidance would be duly appreciated. Thanks in advance!
Scott
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
PonsAsinorem said:
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
Click to expand...
Click to collapse
Sorry....i guess it pays to be extra thorough in the description of the problem. The link you left me is the one that I followed. I researched achieving S-Off on the DInc first and found this same page in my research. I followed the process and all went smooth right up until i started to flash the unrevoked-forever.zip from my sdcard via CWM. The aforementioned error messages came up on my phone and it said the process failed.
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
smvogel73 said:
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
Click to expand...
Click to collapse
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
PonsAsinorem said:
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
Click to expand...
Click to collapse
Yes thx....I'm gathering that! So this is where terminology gets so dang confusing for me. I didn't think unlocking my bootloader meant the same thing as achieving S-Off?? I already thought my bootloader was unlcoked, as I was able to flash CM7.2, which I didnt think I would be able to do if I had a locked bootloader. So wicked confused!!! And try as I miught to educate myself in these forums, I haven't located a sticky or guide that really thoroughly explains all the vernacular regarding android dev/modding/rooting/flashing/etc
So this other method will work with any radio baseband version then?? Or is it important to check compatibility there too??
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
PonsAsinorem said:
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
Click to expand...
Click to collapse
It says "UNLOCKED" and below that it says "S-ON
Thank u for the materials too!
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run. I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.
The ROM I'm looking to flash is Infection JB 4.2.2. The instructions say that if you're coming from. A non-AOSP ROM and are S-On that you've gotta extract boot.img and fastboot it after the ROM flash......whatever the heck that means???
smvogel73 said:
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run.???
Click to expand...
Click to collapse
Correct. Staying S-ON minimizes the danger. It locks your radio, and HBOOT, which are the main dangers.
smvogel73 said:
I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.???
Click to expand...
Click to collapse
Not really ROM flashing, but radio and HBOOT flashing, which is what unrevoked-forever tweaks.
I'd try to flash it one more time. When you do, what, if anything, are you wiping? You should be doing a factory reset, system, and boot wipe/format, then flash the ROM.
If that doesn't work (it might not, it's been awhile since I've worked with S-ON devices), then we'll move on to S-OFF (if you want).
Oh no.....I didn't even attempt to flash the Infection JB ROM specifically because I was not able to achieve S-Off. Whether it was intended or not, yea.....u sufficiently scared me about bricking the phone if I'm not to spec per the developer.
Are u saying I should wipe and then try to flash this ROM despite still being S-On?
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
PonsAsinorem said:
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
Click to expand...
Click to collapse
Well there you have it....I will trust your wisdom (as it is far supperior to my own) and I shall flash this ROM tonight!! I already have a nandroid backup of CM7.2 that Im running, as well as a Titanium backup of all my user apps/files.
Sincerest thanks for all your help!!
Hello. Im no expert but i think Cyanogenmod is aosp so you should be good.
I was where you were 2 yrs ago when I rooted my 1st phone: a friends froyo Dinc (ahhh...froyo). A few months ago I aquired my own and went to research how to root GB and everything has changed and is now vastly more complicated. Also I think every phone has a locked bootloader but not encrypted and I think Soff is extra security since I've only encountered it on htc phones. Anyway I've managed to get my inc to Soff but its still locked, idk how lol
Sent from my ADR6300 using Tapatalk 2
For anyone familiar with this type of thing I tend to notice that with most ways for gaining S-OFF are purely through flashing a modified boot.img.
Now with this in mind, I also know that there are variants for our devices that are already shipped with S-OFF status or people have bought these devices with it done by the seller of another country.
I was thinking, if you were to take the boot.img from a nandroid backup of someone with S-OFF or use adb commands to pull the boot.img from that device then use a boot.img extractor and compare the files with the boot.img files of the other variants of this device that are S-ON; there would be a higher possibility on figuring what fields need to be edited to enable this feature.
Anyone care to drop some knowledge on the topic?
Sent from my 710C using XDA Free mobile app
I second this. Just wish I had the nouse to do it myself.
I think it's pretty obvious that the S-ON also interferes with getting second partitions on SD cards mounted. Makes apps like Link2SD practically worthless. Any changes to init.d or other files get tossed on reboot (though changes to the permission.xml have persevered).
Really hope we can come up with some S-OFF ideas.
Thanks for bringing this up, jaysoblitzed.
Any one tried rumrunner to gain soff ? The universial version?
I tried using every other s-off technique available for m8 on 816. But none seems to work.
I think the problem is with HBOOT version. Firewater gave me an error stating that I shouldn't have updated using OTA. My HBOOT is 3.19
If anyone with 3.18 or lower can try to use firewater it might work.
Please do reply on this thread. (For the sake of warranty if not community)