After updating January security patch 2018 im unable to to root my s7 edge (SM935FD)....
I tried by TWRP and cf-auto root, after flash device shows verification failed plz reset device.....
Plz help me.....to root my device
I have the same problem
---------- Post added at 14:37 ---------- Previous post was at 14:30 ----------
after disabled auto reboot in odin, then holding vol up and home and boot it booted to twrp.
is there any solution for this problem? i can't restore my s7 edge now? what to do in this situation I mean after installing January update?
Related
Hey I have a G530H XXU Version and its rooted and i have twrp recovery v2.8.7.0 and when i try to reboot the phone from the recovery it freezes so i have to remove the battery and put it back again
Any help??
First tell me how do ya installed it??
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
Download TWRP manager from playstore and update ur recovery...:good:
Hello, since i updated my phone to new stock firmware i.e 5.0.2 i can't install any recovery like Twrp on my Grand Prime G530-H. I want to try new roms here please help, Thanks.
Twrp freezing
Make sure that mount read only is clicked on
CID is 15. I don't know if the bootloader is locked or not and couldn't get adb to recognize device to check it. Does that matter if already rooted on 4.4.4? Any help appreciated.
To check if boot loader is locked boot into download mode and check for a line that says developer mode if you don't see that you are on a locked boot loader
---------- Post added at 07:54 AM ---------- Previous post was at 07:51 AM ----------
It depends on what you want to do with your phone
Do you want stable secure official warranty stock
or crazy good performance and ability to personalize everything but bad battery life and somewhat less secure experience
Thanks, [email protected]. I don't have "developer mode" when booting into download mode but...I tried that on a G900P that has rooted 6.0.1 on it and I believe an unlocked bootloader and it doesn't say anything about "developer mode" either.
I just want to upgrade to rooted stock MM 6.0.1 but not if it's a real pain in the neck. Knox doesn't matter at this point.
Try flashing twrp in Odin that will tell you for certain if your boot loader is unlocked and developer mode is only for Verizon s5 bootloader unlock
Thanks again, [email protected]. I tried latest version of ODIN to install latest TWRP but it failed with S5 reading "secure magiccode check fail: recovery." I don't know if that means the bootloader is locked or some other problem. At this point I'll probably just forget it and stay on KK 4.4.4 hoping somebody comes up with an easy way to root MM 6.0.1 like Towelroot or CF-Auto-Root or something. Thanks for the help.
It means your bootloader is locked that was just to test your bootloader unlock status
---------- Post added at 01:58 AM ---------- Previous post was at 01:46 AM ----------
To get bootloader unlocked go to getex kk-mm bootloader unlock for s5 Verizon on XDA developers under s5 Verizon section
Then flash twrp in odin
Then flash your custom ROM in twrp In this order
Do a twrp full backup to SD card or USB otg drive
Then do a Full wipe except usb storage and external storage
mm kernel
Mm modem
ROM
Optional Extras
Su hide
Xposed
Custom kernel
SuperSU zip
That doesn't look too bad. Will have to wait until tomorrow to start it. Thanks!
I got the bootloader unlocked and installed TWRP and did a full backup but now stumped. Don't know what to flash next or where to find it.
Still on rooted KK 4.4.4 but now with unlocked bootloader. Will probably just stay here until there is an easier method. Thanks!
I screwed up and left the bootloader unlocked when I flashed the 7.0 OTA. So, SafetyNet test fails and Android Pay refuses to work. Based on what I have found and read, I believe it is impossible (currently) to simply relock the bootloader. I think I need to root with Magisk and then use the appropriate module to hide root and unlocked status from Android Pay. Is that the possible? Is that the correct approach? I have been searching and reading but my mind is swimming now. Must be getting too old for this stuff.
Thanks in advance.
Root with magisk - hide is inbuilt - don't need add. module.
How to:
Boot twrp - fastboot boot NameTwrp3xx.img
Backup all with twrp
Restore boot with twrp
Install Magisk14+.zip
Reboot.
If you need - you can flash twrp.
---------- Post added at 07:21 AM ---------- Previous post was at 07:21 AM ----------
@BigBadger
dzidexx said:
Root with magisk - hide is inbuilt - don't need add. module.
How to:
Boot twrp - fastboot boot NameTwrp3xx.img
Backup all with twrp
Restore boot with twrp
Install Magisk14+.zip
Reboot.
If you need - you can flash twrp.
---------- Post added at 07:21 AM ---------- Previous post was at 07:21 AM ----------
@BigBadger
Click to expand...
Click to collapse
So I did this, and Magisk is installed, set to hide for Android Pay, and it's still not working. It still recognizes the unlocked bootloader. Is there anything else I can do?
What is in magisk manager - safety net status?
Magisk 14? Stock Nougat? @yaoverstand
@dzidexx
ctsProfile: false
basicIntegrity: false
stock nougat
Magisk 14
Latest TWRP
Sorry, I don't know why.
Wipe all, restore boot + system, format data and try again.
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
@yaoverstand
yaoverstand said:
So I did this, and Magisk is installed, set to hide for Android Pay, and it's still not working. It still recognizes the unlocked bootloader. Is there anything else I can do?
Click to expand...
Click to collapse
Go into Settings in the Magisk app, scroll down about halfway, and make sure the Magisk hide slider is on.
If it shows on toggle it off then back on and again then reboot and try the safety net check again. I've had to do this once or twice right after flashing Magisk.
@jason2678
Tried this just now, and I'm still failing the safety net check in the same manner.
Could it have to do with the fact that I flashed a stock nougat image instead of taking the ota?
What did you flashed?
Give here link to thread.
Your model is...? Give full info. @yaoverstand
dzidexx said:
What did you flashed?
Give here link to thread.
Your model is...? Give full info. @yaoverstand
Click to expand...
Click to collapse
Just an update. I flashed the official image from the when the OTA came out.
I restarted Magisk with hide slider off, and then turned it on when the phone came back on. Then I restarted again, and all is well. Passed safetynet and everything. Thanks guys!
jason2678 said:
Go into Settings in the Magisk app, scroll down about halfway, and make sure the Magisk hide slider is on.
If it shows on toggle it off then back on and again then reboot and try the safety net check again. I've had to do this once or twice right after flashing Magisk.
Click to expand...
Click to collapse
I think in magisk 14.3 it's on by default now
Spencervb256 said:
I think in magisk 14.3 it's on by default now
Click to expand...
Click to collapse
I think so too, but I've had it happen a few times where hide wasn't really on until I turned it off, then back on again. That might have been pre 14 versions. I don't flash my phone too often.
I got this OTA notification earlier today
Im on Nougat 7.1.2 December 1 Security Patch
Rooted with Magisk 15.3 Stable
Thru Boot Twrp only
I have Stock recovery.
How can i update to oreo thru my OTA notification w/out losing my current data/s ?
Any assistance would kindly appreciated
Thank you XDA
Follow this thread
https://forum.xda-developers.com/mi-a1/help/forgot-phone-rooted-tapped-download-t3740661/page2
Alanjameson99 said:
Follow this thread
https://forum.xda-developers.com/mi-a1/help/forgot-phone-rooted-tapped-download-t3740661/page2
Click to expand...
Click to collapse
Can i install it thru ota?
Sent from my Mi A1 using Tapatalk
Magisk "claims" to be ota foolproof according to this doc:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
But not everyone has able to do it successfuly. Try it yourself and see if it works. Use it at your own risk as some people have went to boot loop.
---------- Post added at 06:53 AM ---------- Previous post was at 06:45 AM ----------
BTW here is my personal experience with Magisk:
I installed magisk without twrp (using modified boot.img). I didn't installed any modules. Since my phone system has been modified using magisk I was not able to get the ota. So, to get the ota I followed a YouTube video in which I had to uninstall magisk using uninstall.zip, flash stock boot.img, relock bootloader and resetted my phone. After several days I received OTA (remember my system is now unrooted and magisk uninstalled). The update download but at the step it gave me an error "installation failed".
The reason is simple, installing magisk modules system partitions and now you can't install OTA's. The only option which was left to me is by downloading stock stable Oreo rom from mi global website and flashing it using mi flash. Hopefully, now my system is in it's native state and I will be able to install future updates. The current stable tomorrow is the up-to-date with January security patch hence I didn't had to update.
i have flashed the offical stock firmware via odin, before data i wiped all the data via custom recovery.
then i also locked the bootloader again because it is was open by lock oem.
is that enough and means my phone is fully unrooted? i dont want that google will detected my device is rooted.
should i install stock recovery? or can i stay with the custom recovery ?
what custom rom i can use that there is anything about root ?
EREVtov said:
i have flashed the offical stock firmware via odin, before data i wiped all the data via custom recovery.
then i also locked the bootloader again because it is was open by lock oem.
is that enough and means my phone is fully unrooted? i dont want that google will detected my device is rooted.
should i install stock recovery? or can i stay with the custom recovery ?
what custom rom i can use that there is anything about root ?
Click to expand...
Click to collapse
Bootloader and root are 2 different things.
What method of root did you have installed?
SuperSU? Magisk? Something else?
magisk.
i flashed the offial firmware of 6.0, same bootloader and mm for it.
i earsed all the data and system before flashing the offical firmware, even the custom recovery has been removed while flashing that.
however i saw the the oem button at develpoers options was enbaled even after the flashing, so i turn it off.
anything else i need to do ?
and if i will custom recovery, would it detected as root? or it is fine ?
garylawwd said:
Bootloader and root are 2 different things.
What method of root did you have installed?
SuperSU? Magisk? Something else?
Click to expand...
Click to collapse
magisk.
i flashed the offial firmware of 6.0, same bootloader and mm for it.
i earsed all the data and system before flashing the offical firmware, even the custom recovery has been removed while flashing that.
however i saw the the oem button at develpoers options was enbaled even after the flashing, so i turn it off.
anything else i need to do ?
and if i will custom recovery, would it detected as root? or it is fine ?
i think its because you flagged knox counter:/
You can still install Magisk v12 with fake knox 0x0
Reply if it solved your problem, and "OEM" its just a FRP (factory reset protection). You can see if you have a custom rom and you disable ACCIDENTLY FRP your will stuck at boot "frp lock..."
sry for my bad english
---------- Post added at 09:32 PM ---------- Previous post was at 09:32 PM ----------
Sorry if you cant unroot without having problem, soo try hide root
BaconOFBurgerPS said:
i think its because you flagged knox counter:/
You can still install Magisk v12 with fake knox 0x0
Reply if it solved your problem, and "OEM" its just a FRP (factory reset protection). You can see if you have a custom rom and you disable ACCIDENTLY FRP your will stuck at boot "frp lock..."
sry for my bad english
---------- Post added at 09:32 PM ---------- Previous post was at 09:32 PM ----------
Sorry if you cant unroot without having problem, soo try hide root
Click to expand...
Click to collapse
what is it knox counter: ?
i flashed a firmware stock from sammobile.
so oem unlock is not root? or custom recovery ?