Related
MOD EDIT @gregbradley
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned. For more information read the whole OP here
Getting ROOT rights to Android 5.0 Lollipop (KingRoot) It is not my work. Taken from a russian forum.
1.Download and install latest version of Kingroot to phone.
2.Run the application and get the Root. Important - do not restart the device, because it can lead to failure in obtaining Root.
3.Enable "USB debugging" and "unknown sources".
4.Install the latest version from the PC XZDualRecovery to get full access to reading and writing to the section System (connect your phone to a PC via a cable, run the install.bat to select a number " 1 "on the screen to confirm a request for superuser)
5.Phone will reboot automatically to recovery. Install supersu.
6.Boot
Files to root.
https://mega.co.nz/#!eUgAiSDZ!R1bU-_hIxa2GW11Pjd8ikc-AzfbbJsoAXWkh7DG8j1A
isaekrem said:
Getting ROOT rights to Android 5.0 Lollipop (KingRoot) It is not my work. Taken from a russian forum.
1
Click to expand...
Click to collapse
I've been waiting for a one click root, but everything I'm reading says this is really sketchy and no one is quite sure what it is doing.
Can anyone confirm working on Z3?
For which phone? T-Mobile?
se1zure31 said:
For which phone? T-Mobile?
Click to expand...
Click to collapse
Tested by owner z3c.
And I tested on my phone D6603.
Is everything working good ???
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned.
gregbradley said:
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned.
Click to expand...
Click to collapse
Thanks.........for the information.
gregbradley said:
Also, users should be aware that Kingo root sends your IMEI to an unknown IP address in china during the root process, you have been warned.
Click to expand...
Click to collapse
Correct me if I'm wrong, but Kingo root is not the same as this, which is King Root?
haste75 said:
Correct me if I'm wrong, but Kingo root is not the same as this, which is King Root?
Click to expand...
Click to collapse
AFAIK they are the same
haste75 said:
Correct me if I'm wrong, but Kingo root is not the same as this, which is King Root?
Click to expand...
Click to collapse
Yes they are the same ...
Well, I couldnt resist. I've now got a working root with SuperSU, and have removed all I can find of the KingRoot app.
So far, seems to be working well.
Someone else tried it?
haste75 said:
Well, I couldnt resist. I've now got a working root with SuperSU, and have removed all I can find of the KingRoot app.
So far, seems to be working well.
Click to expand...
Click to collapse
Were you able to remove KingUser and install SuperUser?
scoder said:
Were you able to remove KingUser and install SuperUser?
Click to expand...
Click to collapse
Yes I believe so. I have the Kinguser icon in my app draw, but It wont open. I deleted all files associated with King via ES Root Explorer, and cannot find anything.
I still wouldn't recommend anyone else doing this, god knows what information was sent to China upon installing it, but I really wanted root.
haste75 said:
I still wouldn't recommend anyone else doing this, god knows what information was sent to China upon installing it,
Click to expand...
Click to collapse
But if try to isolate PC and phone from the internet during installing?
artlov said:
But if try to isolate PC and phone from the internet during installing?
Click to expand...
Click to collapse
I tried that, it needs internet connectivity. However, the reason I allowed this was I understand that this root is based on a Ping exploit, which would need internet connecivity to work.
I figured the risk werent THAT high for me. I dont re-use passwords and no bank details stored on my phone.
Can confirm this method works.
You might want to try going in Airplane mode if you're paranoid for the Chinese. In any case, Kingroot + XZDR + SuperSU 2.49 works perfectly.
It works for me I can confirm now.I have root on lollipop locked bootloader so nice haha ? thanks
E66666666 said:
Can confirm this method works.
You might want to try going in Airplane mode if you're paranoid for the Chinese. In any case, Kingroot + XZDR + SuperSU 2.49 works perfectly.
Click to expand...
Click to collapse
did you flash the recovery?
krugu said:
did you flash the recovery?
Click to expand...
Click to collapse
Not yet will do tomorrow, now I accidentally cleared the data of kinguser and now any app can't recognize root on my devices although it's installed, it says root denied, but şu binaries are installed, I will try tomorrow the recovery after school, if it really works I will release my ultimate sound mod I'm working since months and ofc I can test it myself and don't need any testers hope the pc cam.recognize the root on my.device and install the .bat files
Thought I was good at this. Never mind.
So I have managed to brick my device after 6 hours of having it.
Managed to unlock the BL, install TWRP, but the OS has gone, and I have no way of getting the thing mounted to copy over a ROM or anything.
What's the best way for me to sort this out ?
I'm thinking I could buy an SD card, copy a ROM to it, then flash it via TWRP.
Is this the only option ?
Help
grifforama said:
Thought I was good at this. Never mind.
So I have managed to brick my device after 6 hours of having it.
Managed to unlock the BL, install TWRP, but the OS has gone, and I have no way of getting the thing mounted to copy over a ROM or anything.
What's the best way for me to sort this out ?
I'm thinking I could buy an SD card, copy a ROM to it, then flash it via TWRP.
Is this the only option ?
Help
Click to expand...
Click to collapse
If you can get to the bootloader then just use the restore to stock tool from shawn5162. Should work fine as long as you have successfully unlocked the bootloader. Here is the link http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
Should be clear that this will put your device to LP 5.1.1 without root or TWRP. Then just do the OTA MM update and re-root and flash TWRP. You can follow this guide I created if you like.
http://forum.xda-developers.com/moto-x-style/help/updating-to-mm-lp-moto-x-pure-t3270473
robn30 said:
If you can get to the bootloader then just use the restore to stock tool from shawn5162. Should work fine as long as you have successfully unlocked the bootloader. Here is the link http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
Should be clear that this will put your device to LP 5.1.1 without root or TWRP. Then just do the OTA MM update and re-root and flash TWRP. You can follow this guide I created if you like.
http://forum.xda-developers.com/moto-x-style/help/updating-to-mm-lp-moto-x-pure-t3270473
Click to expand...
Click to collapse
Thanks for this, and I now have a booting , but wifi is not working ? I cannot connect to any wifi at all ? And when I try to turn wifi on, it turns itself off immediately ?
grifforama said:
Thanks for this, and I now have a booting , but wifi is not working ? I cannot connect to any wifi at all ? And when I try to turn wifi on, it turns itself off immediately ?
Click to expand...
Click to collapse
You have to flash correct modem to your device. Check that thread for more info.
kadopt said:
You have to flash correct modem to your device. Check that thread for more info.
Click to expand...
Click to collapse
I have never had such issues when setting up a phone before. Now I have this message
"there's a problem signing in to your google account on this device
Please sign in from a browser on your computer or tablet first, then try signing in again on this device"
Needless to say, I've done this numerous times, and I still cannot sign in on the phone.
Ugh.
grifforama said:
I have never had such issues when setting up a phone before. Now I have this message
"there's a problem signing in to your google account on this device
Please sign in from a browser on your computer or tablet first, then try signing in again on this device"
Needless to say, I've done this numerous times, and I still cannot sign in on the phone.
Ugh.
Click to expand...
Click to collapse
Ouch...Thats a security feature on MM... Only way ive found to avoid it is to restore a backup and before you wipe/flash your next ROM either disable the lockscreen(i.e. unsecured lockscreen), re-enable OEM unlocking, or factory reset your device from it from your running phone(not in TWRP) through settings->Backup and reset...that removes your google account from your phone so once you reset it you can set your phone up with your google account
pizzlewizzle said:
Ouch...Thats a security feature on MM... Only way ive found to avoid it is to restore a backup and before you wipe/flash your next ROM either disable the lockscreen(i.e. unsecured lockscreen), re-enable OEM unlocking, or factory reset your device from it from your running phone(not in TWRP) through settings->Backup and reset...that removes your google account from your phone so once you reset it you can set your phone up with your google account
Click to expand...
Click to collapse
Think I'm screwed. No backup. No ability to log into the OS to reset from within. Just keeps looping on the input screen.
I think I read somewhere that if you wait 72 hours it fixes itself. We'll see.
Joyful start to the year
grifforama said:
Think I'm screwed. No backup. No ability to log into the OS to reset from within. Just keeps looping on the input screen.
I think I read somewhere that if you wait 72 hours it fixes itself. We'll see.
Joyful start to the year
Click to expand...
Click to collapse
Why not use the restore to stock tool then before taking the update just make sure your phone has no security on it or the OEM unnlocked turned on...
pizzlewizzle said:
Why not use the restore to stock tool then before taking the update just make sure your phone has no security on it or the OEM unnlocked turned on...
Click to expand...
Click to collapse
That's what I've tried. I used the return to stock tool, and when it asks for my google email address and password, that's what it won't go past. that's exactly where I'm at right now. Stuck at the verification screen.
Is this an xt1575? If so, try my TWRP stock backup?
gokart2 said:
Is this an xt1575? If so, try my TWRP stock backup?
Click to expand...
Click to collapse
Can you give me me a link ?
grifforama said:
That's what I've tried. I used the return to stock tool, and when it asks for my google email address and password, that's what it won't go past. that's exactly where I'm at right now. Stuck at the verification screen.
Click to expand...
Click to collapse
hmmm thats weird... the new security feature wasn't implemented until MM... The restore to stock should take you to 5.1.1. not sure what else to try. Hopefully you can get in after the wait...next time you get your phone running make a backup to save a headache down the road
edit: you couldnt use the restore to stock then before it loads flash a 5.1 ROM?
gokart2 said:
Is this an xt1575? If so, try my TWRP stock backup?
Click to expand...
Click to collapse
Do you have a link ?
I keep trying and trying. I just keep getting sent back to a screen saying "This device was reset. To continue, sign in with a Google account that was previously synced on this device"
infuriating
http://www.androidpolice.com/2015/03/12/guide-what-is-android-5-1s-antitheft-device-protection-feature-and-how-do-i-use-it/
OK looks like this is a "feature" I guess. I'm stuck for 72 hours
grifforama said:
Can you give me me a link ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Its the stock TWRP backup from either 5.1.1 or 6.0....whichever you are currently supposed to be on.
wait, if this is a new phone and you had added your google account before "bricking," why cant you just sign in using that google account. My understanding is that the lockout is to prevent a NEW google account that was not associated with your phone from being used to set it up
pizzlewizzle said:
Ouch...Thats a security feature on MM... Only way ive found to avoid it is to restore a backup and before you wipe/flash your next ROM either disable the lockscreen(i.e. unsecured lockscreen), re-enable OEM unlocking, or factory reset your device from it from your running phone(not in TWRP) through settings->Backup and reset...that removes your google account from your phone so once you reset it you can set your phone up with your google account
Click to expand...
Click to collapse
That error means you don't have a 72 hour lock yet. Go to https://accounts.google.com/b/0/displayunlockcaptcha on your computer. Login, hit the accept button, then try logging in your phone. Your phone is not locked out, just to to the website. If you changed your password, though, then you shot yourself in the foot with the Google protection.
This is too complicated for me to explain everything but here is my Cheat Sheet !
If you have been flashing you probably already have these files.
1. Odin SamMobile N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar
reboot and factory reset a few times if needed to remove custom icon, Block SDM
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar
( ! System and Cache only ! ) Unblock SDM
8. Now with FlashFire installed and Granted SU Access, Check for new system updates in Phone Setting.
It could start downloading automatically or it may not download for hours. I have tested both scenarios
9. When Updates finishes downloading open FlashFire to install the update.
I got the Build update MMB29M.N910VVRU2CPF3 over the air.
Your mileage may vary.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting of 5.1.1
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on[Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1]then you can use FlashFire.
EDIT: You have to do step 7 manually with N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar manually download to your phone. Automatic updates start after step 8 with SDM unblocked.
Credit AstonsAndroid I found it HERE
Reserved
FlashFire
Many of the problems we have been having with the Safe Upgrade to Marshmallow are not present with the FlashFire System Flash.
Interesting, may have to give this a spin at some point. This fixes the issue of DM-Verity, produces a clean EFS folder to go along with Root/unlocked bootloader when the steps are finished?
It's true, I tried this awhile back when doctor-cool posted this in one of the theads in the development forums. I was experiencing an inability to send MMS messages, the "Roam Indicator" message and missing the Applications option in the Setting menu. After reflashing CPD1 through FlashFire, it fixed everything. Flashed the CPF3 update through FlashFire as well and am currently up to date.
doctor-cool said:
This is too complicated for me to explain everything but here is my Cheat Sheet !
If you have been flashing you probably already have these files.
1. Odin SamMobile N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with adb , samsung_unlock_n4-fix
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP then boot System
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar
( ! System and Cache only ! )
8. With FlashFire installed and Granted SU Access, Check for new system updates in Phone Setting.
It could download automatically.
9. When Updates finishes downloading open FlashFire to install the update.
I got the Build update MMB29M.N910VVRU2CPF3 over the air.
Your mileage may vary.
Credit AstonsAndroid I found it HERE
Click to expand...
Click to collapse
So reading your instructions we don't worry about rooting (unlocking the bootloader) till step 3? I need to try this if I can because I suspect Kingroot and Kingoroot has screwed up my EFS folder. It's to the point that when I try to root again thru those 2 apps it locks up and throws me into a bootloop everytime. I'm really hoping to get my Note 4 back to normal operating but I'm to the point I think an XDA expert who had their hands on it would be my only hope. Any suggestions or help would be greatly appreciated :fingers-crossed:
lorilucille9 said:
So reading your instructions we don't worry about rooting (unlocking the bootloader) till step 3? I need to try this if I can because I suspect Kingroot and Kingoroot has screwed up my EFS folder. It's to the point that when I try to root again thru those 2 apps it locks up and throws me into a bootloop everytime. I'm really hoping to get my Note 4 back to normal operating but I'm to the point I think an XDA expert who had their hands on it would be my only hope. Any suggestions or help would be greatly appreciated :fingers-crossed:
Click to expand...
Click to collapse
that's the way I did it
doctor-cool said:
that's the way I did it
Click to expand...
Click to collapse
Well my problem is I'm stuck btw being rooted and not rooted. The phone says I am (phone state = custom) but any other app says I'm not. I try to root again thru Kingroot/Kingoroot and it fails both by APK and Desktop version. Reinstalling official LP still holds remnants over and it's not a clean install like everone thinks. I'm on my last nerve with this and all I want is to get my phone back to root so I can clean up the crap in efs folder or truly do a clean back to stock flash. Can accessing the phone to do this be done any other way?
Sent from my SM-G935V using XDA-Developers mobile app
lorilucille9 said:
Well my problem is I'm stuck btw being rooted and not rooted. The phone says I am (phone state = custom) but any other app says I'm not. I try to root again thru Kingroot/Kingoroot and it fails both by APK and Desktop version. Reinstalling official LP still holds remnants over and it's not a clean install like everone thinks. I'm on my last nerve with this and all I want is to get my phone back to root so I can clean up the crap in efs folder or truly do a clean back to stock flash. Can accessing the phone to do this be done any other way?
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
Try from within Phone Setting a Factory Reset after the first step
doctor-cool said:
Try from within Phone Setting a Factory Reset after the first step
Click to expand...
Click to collapse
Several times I have... nothing wipes it completely clean. Does EFS folder get touched when flashing or Odining official firmware? I think that folder is my problem to it all.
Sent from my SM-G935V using XDA-Developers mobile app
lorilucille9 said:
Several times I have... nothing wipes it completely clean. Does EFS folder get touched when flashing or Odining official firmware? I think that folder is my problem to it all.
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
You absolutely could have corruption of the efs folder. The only way I personally know of to clean the efs folder is HERE.
But you need Root to do it.
doctor-cool said:
You absolutely could have corruption of the efs folder. The only way I personally know of to clean the efs folder is HERE.
But you need Root to do it.
Click to expand...
Click to collapse
Everything worked though before I switched phones. I have a backup of my EFS folder via TWRP... is there any way to edit the backup so just the files that should be there are there then reinstall? Do you know anyone that would be willing and trusting to fix my phone if I sent it to them? I'd pay to get it fixed too!
Sent from my SM-G935V using XDA-Developers mobile app
lorilucille9 said:
Everything worked though before I switched phones. I have a backup of my EFS folder via TWRP... is there any way to edit the backup so just the files that should be there are there then reinstall? Do you know anyone that would be willing and trusting to fix my phone if I sent it to them? I'd pay to get it fixed too!
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
No Way, I would not try to edit that backup partition. It may end up unable to mount.
You're on the wrong thread. You need to establish a simple unlocked 5.1.1 bootloader.
doctor-cool said:
No Way, I would not try to edit that backup partition. It may end up unable to mount.
You're on the wrong thread. You need to establish a simple unlocked 5.1.1 bootloader.
Click to expand...
Click to collapse
The backup is what I meant on editing and I'm on this thread because in the beginning you made it sound like I don't have to start from LP... I asked that... and was hoping this may be a different way to get my root back. Sorry!
Sent from my SM-G935V using XDA-Developers mobile app
lorilucille9 said:
The backup is what I meant on editing and I'm on this thread because in the beginning you made it sound like I don't have to start from LP... I asked that... and was hoping this may be a different way to get my root back. Sorry!
Sent from my SM-G935V using XDA-Developers mobile app
Click to expand...
Click to collapse
It's Okay good luck but I was able to skip the recommended rooting of 5.1.1
In this example, I did not unlock until step 3 and I did not permanent root until step 6.
The process I used to unlock is
HERE I just re-tested and the OP is valid.
Thanks for the detailed listing of downloads and links for instructions. To be clear, in both of the links you provided for instructions on unlocking your bootloader, the instructions say you need root (su) in order to run the samsung_unlock_n4-fix. However, you are saying that you were able to run it successfully without root (or at least without Kingroot)? Also, could you clarify what you mean by "use SIM card for data" in step 3 of the OP?
azumandias said:
Thanks for the detailed listing of downloads and links for instructions. To be clear, in both of the links you provided for instructions on unlocking your bootloader, the instructions say you need root (su) in order to run the samsung_unlock_n4-fix. However, you are saying that you were able to run it successfully without root (or at least without Kingroot)? Also, could you clarify what you mean by "use SIM card for data" in step 3 of the OP?
Click to expand...
Click to collapse
Thanks, I should have said permanent root. You do have to use Kingroot to use the samsung_unlock_n4-fix but you don't have to install Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
I tryed to do flash fire only problem was I wasn't able to do anything. I hit the plus icon to search for it with no luck and it was there because I got the box asking to install now or later
Sent from my SM-N910V using XDA-Developers mobile app
rmc198501 said:
I tryed to do flash fire only problem was I wasn't able to do anything. I hit the plus icon to search for it with no luck and it was there because I got the box asking to install now or later
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
You have to do step 7 manually with N910VVRU2CPD1_N910VVZW2CPD1_N910VVRU2CPD1_HOME.tar manually download to your phone. Automatic updates start after step 8
I have been trying to root for days and I can not get anywhere. I'm doing something wrong but I don't know what it is. And trying to get help is like asking for a million bucks just ant gonna happen.
Sent from my VS990 using Tapatalk
mwebb34 said:
I have been trying to root for days and I can not get anywhere. I'm doing something wrong but I don't know what it is. And trying to get help is like asking for a million bucks just ant gonna happen.
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
You could have a hardware problem even a bad usb cable
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
in theory according to posts ive seen for other devices you need magisks latest beta version.
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
Check by Playstore>settings... you're probably uncertified...
EDIT: You need magisk to pass the safetynet...
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
EVR_PR said:
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
Click to expand...
Click to collapse
It won't unless you either 1) Use magisk as mentioned or 2) use a custom kernel with SafeyNet patches.
When you unlock your bootloader, the prop (which you can read using a terminal emulator and typing getprop) has a flag called verifiedbootstate. If it returns anything but green SafeyNet will fail.
Sent from my OnePlus 3T using XDA Labs
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
gameofdroness said:
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
Click to expand...
Click to collapse
Of course..why not...
HatRiGt said:
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
Click to expand...
Click to collapse
I've flashed v. 13 (https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589) and worked as a charm!
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
oowaymike said:
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
Click to expand...
Click to collapse
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
yubimusubi said:
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
Click to expand...
Click to collapse
Thanks for the suggestions. I tried the stable version with no luck as well. I'll wait for the next beta version, and if that doesn't do the trick ill try reflashing the stock partition. If anyone finds a custom kernel that gets around safety net I'd really appreciate it.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Eric214 said:
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Click to expand...
Click to collapse
I don't know if this is OP'S reason, but you can boot TWRP without actually installing it... So you can take nandroid backups of an otherwise stock device.
Also, unlocking bootloader wipes your phone, so if you want it stock for now but think you might root in the future you won't have to deal with that...
TBH though, SafetyNet is working as advertised by failing an unlocked bootloader. We like to have our cake and eat it too.
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Great job keep us posted
zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
I think you would need a boot.img that disables it. Or you can disable encryption manually and erase all data to keep it disabled.
zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
@jcadduono can help you to have a perfect job about TWRP ...
Ask him on irc ...
Backup failed because /data cannot be mounted, which suggests a mismatch twixt TWRP and device. Decided to push on and try to root. This failed, so that stock firmware had to be installed. I've hacked a number of phones and tabs here, so I was itching to see what could be done with existing N7 mods. Now I know.
It looks as though we need recovery etc specific to FE. Not sure we will have the numbers for it, though. If anyone has any ideas...
zamzenos said:
I've managed to install TWRP - ver twrp-3.1.1-0-gracelte.img.tar (for N7) via Odin. Straightforward. Could access recovery, but need now to work out how to deal with encryption in order to make backup. Any help would be appreciated.
We're on our way!
Click to expand...
Click to collapse
Your a brave man for trying this and the first to do so on here so thank you!.
As for the encryption on all the last few sammy devices ive had/have including the original Note 7 once you flash twrp you have to format data in twrp (not wipe mind you...format) to remove encryption.
We also had to then flash a zip to deal with dm verity but now SU does that anyway and also keeps the device decrypted when you reboot.
Id hazard a guess and say if you formatted and flashed SU this might actually work.
Now that we know flashing twrp (which was my main worry) and then odin stock without any issues this just got alot less risky.
sent from my Note FE, S8 plus, S7 edge or S6
Well I'm traveling now and will give this a go when I return home. Question: does DM Verity and Magic's or SU root require a a Note FR boot image to work or can they simply patch the boot image?
force70 said:
Your a brave man for trying this and the first to do so on here so thank you!.
As for the encryption on all the last few sammy devices ive had/have including the original Note 7 once you flash twrp you have to format data in twrp (not wipe mind you...format) to remove encryption.
We also had to then flash a zip to deal with dm verity but now SU does that anyway and also keeps the device decrypted when you reboot.
Id hazard a guess and say if you formatted and flashed SU this might actually work.
Now that we know flashing twrp (which was my main worry) and then odin stock without any issues this just got alot less risky.
sent from my Note FE, S8 plus, S7 edge or S6
Click to expand...
Click to collapse
Ah, I followed directions I found on the N7 forum, from which I assumed that SU would do the encryption. This is the first time I have come up against this barrier. I was resigned to possibly not having root, but from what you say I now think we might well manage it.
I've had a number of narrow shaves with various devices, so I felt that I could find my way out of any difficulty I encountered hacking the FE (maybe just fool's luck) . While cortez.i will try it at some stage, I am tempted to dive back in and see what happens.
Incidentally, sammobile didn't have the K variant firmware (may have now). I found it through google on a vietnamese site.
Just found this comprehensive guide to removing dm-verity:
http://www.theandroidsoul.com/disable-dm-verity-forced-encryption-galaxy-note-7/
Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.
zamzenos said:
Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.
Click to expand...
Click to collapse
You are THE MAN !!!!
WOOOOOOOOOO
wolfgart said:
You are THE MAN !!!!
WOOOOOOOOOO
Click to expand...
Click to collapse
I second that!
You shoukd be able to freeze security log agent with TIBU or package disabler pro to get rid of that message
force70 said:
I second that!
You shoukd be able to freeze security log agent with TIBU or package disabler pro to get rid of that message
Click to expand...
Click to collapse
I uninstalled the log agent with Titanium, ripped out all the Knox, still getting that message. I think I'll backup progress so far and restart FE from within the warning message and see what happens...**
Thank you both for the kudos. But some work still to be done. I'm finding some apps won't start - unfortunately some of them important. It's OK for now - I'm not using the FE yet - but need to get some real benefits from root, otherwise it's back to stock with Adhell (tho' I'd say sammy will spike that soon). Maybe folk with more tech xp than I have can work out what's wrong here.
**Restart from within Security boots into Recovery - in this case TWRP. Looks like a response to the decrypted state, and is set off by any root level action. Can we get rid of this?
zamzenos said:
Posting this separately.
FE WILL ROOT!
Factory reset is automatic (with less KT bloat, for some reason).
Titanuim can uninstall apps. But Adaway cannot copy edited hosts file. Sdfix cannot release the card: says there are no groups in WRITE_EXTERNAL_STORAGE. Keep getting a security warning with each reboot from security log agent, but no action on reboot. Hopefully, all this can be sorted.
Finally, TWRP backup successful. Assume for now that it would restore, if needed.
Click to expand...
Click to collapse
which root package did you use, Magix or SU and did you have to use no verity disable zip?
EDIT: Nevermind, i'm rooted with SuperSU. have a 4 hour plane ride home so i'll have plenty time to checkout root before i get home..
cortez.i said:
which root package did you use, Magix or SU and did you have to use no verity disable zip?
EDIT: Nevermind, i'm rooted with SuperSU. have a 4 hour plane ride home so i'll have plenty time to checkout root before i get home..
Click to expand...
Click to collapse
Just curious if Knox is now tripped,by using SU ?
For myself,I'm not too worried about it either way,but,those interested in root may want to know,for future Samsung Pay use/possible resale value loss due to Knox 0x1/etc....
KOLIOSIS said:
Just curious if Knox is now tripped,by using SU ?
For myself,I'm not too worried about it either way,but,those interested in root may want to know,for future Samsung Pay use/possible resale value loss due to Knox 0x1/etc....
Click to expand...
Click to collapse
Yes sir as soon as you flash twrp its tripped.
And we need twrp for SU so no way around it.
sent from my Note FE, S8 plus, S7 edge or S6
force70 said:
Yes sir as soon as you flash twrp its tripped.
And we need twrp for SU so no way around it.
sent from my Note FE, S8 plus, S7 edge or S6
Click to expand...
Click to collapse
I figured that much hadn't changed since I last rooted/ROM'd a Samsung device,thanks for confirming. :good:
Again,for myself,it's not much of an issue,I plan on keeping this phone for the long haul (at least 1-2 yrs) & loss of Samsung Pay/Android Pay is of no consequence to me.
KOLIOSIS said:
I figured that much hadn't changed since I last rooted/ROM'd a Samsung device,thanks for confirming. :good:
Again,for myself,it's not much of an issue,I plan on keeping this phone for the long haul (at least 1-2 yrs) & loss of Samsung Pay/Android Pay is of no consequence to me.
Click to expand...
Click to collapse
Ive never cared about knox either....and this phone I will keep until it dies or I do lol
force70 said:
Ive never cared about knox either....and this phone I will keep until it dies or I do lol
Click to expand...
Click to collapse
+1
LMFAO,let's hope for the former................... :highfive:
so... after renaming SecurityLogAgent.apk from TWRP, i've had no problems running root apps, modifying build.prop, etc. google Adaway Vesion 3.2 and install this version and it will configure hosts files without issue (at least on my device). will continue testing and report findings should things changes. thanks @zamzenos for risking your device to confirm that the Note 7 version of TWRP is working.
cortez.i said:
so... after renaming SecurityLogAgent.apk from TWRP, i've had no problems running root apps, modifying build.prop, etc. google Adaway Vesion 3.2 and install this version and it will configure hosts files without issue (at least on my device). will continue testing and report findings should things changes. thanks @zamzenos for risking your device to confirm that the Note 7 version of TWRP is working.
Click to expand...
Click to collapse
The Adaway update worked. Thanks for that. I followed the N7 forum guide, except that I formatted data using TWRP, and used SU as advised. I uninstalled the log agent with Titanium (and as much of Knox as I could find). I no longer get security notifications, but something is still being tripped by any root activity. The apps that won't start don't require root, for instance, Adobe Reader, and sms and call log restore apps. I cannot see any common cause here. SDfix (latest version) says it can't find any groups, so can't do its work.
I'll nose around the S7 & 8 forums and see if any of these problems are turning up there (dev on the N7 was seriously interrupted by the problems caused by sammy's battery restrictions).