Root [Boost Mobile] Recovery fix

[smith058]

I did not make this.... BUT it must be shared!!!!

kevindroid showed me the link @ ODIN Backup for --> SPH-L710_MG2

All credit goes to the makers at XDA

New recoveries for new phones that won't mount storage!!

If you just purchased a new S3 or got a replacement and you found out you could not mount anything in your custom recovery, good news!!!! After much collaboration and the input of @ktoonsez and the hard work of @CNexus, a modified recovery has been created!!! It has been tested by a few to work (big thanks to @notmyepic for being the first) and allow you to flash away again!


http://forum.xda-developers.com/showthread.php?t=2391616

Odin Images are at the bottom
.

For me, i had to use mod2

it works!!!! i can use CWM and/or TWRP again

:dancing2::dancing2::dancing2:

 

[HiiiPowers]

I did not make this.... BUT it must be shared!!!!

kevindroid showed me the link @ http://androidforums.com/boost-mobi...586-odin-backup-sph-l710_mg2.html#post6093978

All credit goes to the makers at XDA

New recoveries for new phones that won't mount storage!!

If you just purchased a new S3 or got a replacement and you found out you could not mount anything in your custom recovery, good news!!!! After much collaboration and the input of @ktoonsez and the hard work of @CNexus, a modified recovery has been created!!! It has been tested by a few to work (big thanks to @notmyepic for being the first) and allow you to flash away again!


http://forum.xda-developers.com/showthread.php?t=2391616

.

For me, i had to use mod2

it works!!!! i can use cwm again
:dancing2::dancing2::dancing2:

Maybe you can ask them but why is it that we both have the same boostmobile s3 but the sprint recovery works fine on mines without any mooding TWRP is another story but the cwm posted here works fine i do get this weird E:unknown volume path for [/sd-ext] when trying to wipe dalvik cache but i believe it wipes fines

 

[smith058]

They are exactly the same except in newer phone they added more prevention to keep us from rooting...


These flags restrict rooting and can restrict mounting of anykind based on what code is added to the kernel based on these flags:
# Add rooting prevention
# CONFIG_SEC_RESTRICT_ROOTING is not set
# CONFIG_SEC_RESTRICT_SETUID is not set
# CONFIG_SEC_RESTRICT_FORK is not set
# CONFIG_SEC_RESTRICT_ROOTING_LOG is not set

With these flags and code applied within "#" tags can enforce any amount of restrictions that they want to. With kernel source of course it is very easy to get around unless they get even more sneaky and hide the code, like we found in the S4 for camera firmware updates (was restricted to only official kernels). Hope that helps out for the explanation***

 

[HiiiPowers]

They are exactly the same except in newer phone they added more prevention to keep us from rooting...


These flags restrict rooting and can restrict mounting of anykind based on what code is added to the kernel based on these flags:
# Add rooting prevention
# CONFIG_SEC_RESTRICT_ROOTING is not set
# CONFIG_SEC_RESTRICT_SETUID is not set
# CONFIG_SEC_RESTRICT_FORK is not set
# CONFIG_SEC_RESTRICT_ROOTING_LOG is not set

With these flags and code applied within "#" tags can enforce any amount of restrictions that they want to. With kernel source of course it is very easy to get around unless they get even more sneaky and hide the code, like we found in the S4 for camera firmware updates (was restricted to only official kernels). Hope that helps out for the explanation***

I understand

 

[kingpickle]

Maybe you can ask them but why is it that we both have the same boostmobile s3 but the sprint recovery works fine on mines without any mooding TWRP is another story but the cwm posted here works fine i do get this weird E:unknown volume path for [/sd-ext] when trying to wipe dalvik cache but i believe it wipes fines

Thanks. Used the odin modded twrp, booted into twrp and it rooted my ota updated (G2) phone. I think you mentioned this fix in another thread a week or two ago and I forgot to thank you. Thanks again for the info.