Friday, August 5, 2016

Reactivation lock can be turned off finally for those stuck on reactivation lock

Reactivation lock is off!!!!!!!!!!
I installed TWRP I NEED testers to confirm:D
This only works on sm-g900v VERIZON S5 ONLY so far if you try another device i'm not responsible for any broken or unusable devices or softbricked devices

I booted NCG on PB1 Bootloader
is a new thread by Brens123 on s5 verizon general on xda

exactly i started out by flashing pb1 firmware with odin on s5 verizon
then rooted using ok3 root (search xda)
use supersume (avaliable as a paid app on google play) to get supersu instead of kingroot setup supersu update busybox before you proceed make sure to give busybox root access and update it
then install flashfire app (from google play) and also allow it root access

then go to brens guide I booted NCG on PB1 Bootloader
follow brens123 guide to the letter i used flashfire v.52 make sure busybox is updated and supersu is updated before you use flashfire
dont sign into google play during setup
and sign in to samsung account right away
and go to settings security reactivation lock there was a update to samsung account app and i dont know if it will break this method
dont turn on security updates either at least until after your bootloader is unlocked

after you complete brens123s guide go to getex bootloader unlock kk-mm guide
This is for users with 15' Sasmung eMMC's not users with 11 Toshiba eMMC's. You can check this by reading the file using a root file manager from google play
/sys/block/mmcblk0/device/cid
Just the first 2 15xxxxxxxxxxxxxxxxxxxxxx or 11xxxxxxxxxxxxxxxxxxxxxxx(my number of x's are random, just read the first 2
After that you should be good try to install a custom recovery to make sure

THANK YOU Bren123, for your method to install kk with ss without it this wouldn't be possible
THANK YOU Getex for bootloader unlock
Thank you Geohot for towelroot KK
Thank you Jrkruse for LL root
Thank You Hashcode and Jrkruse for safestrap


from xda-developers http://ift.tt/2aDjNCm
via IFTTT

No comments:

Post a Comment