kernel is not seandroid enforcing set warranty bit kernel
My Sprint Galaxy S5 will only show the above no matter what I try. I had just rooted my new phone and I was trying to install TWRP. I must have made an error. In my search others have had the same problem however, when I tried their fix it did not work for me. I reran root using Odin3 but no luck. In an other post they said to put these 2 files "firasusman and META-INF" on an external sd card and flash them using the custom recovery. Unfortunately I don't have access to any recovery. The only thing I can do is get my phone in ,is download mode with Oden3.
When in download mode in the upper left corner of my phone it says -
"odin mode
product name: SM-G900P
current binary: custom
system status: custom
knox warranty void 0x1 (4)"
So I guess no warrenty if there is no fix. Obviously I would be extremely grateful for any help.
Thank you
I'll start by discussing why the phone became unusable, move to what I've tried to fix it, and then move into questions about solutions.
Root Process:
I began by rooting my Galaxy s7 SM-G930V Snapdragon (Chainfire method). Installed the fixed and debloater with no problems. (secureboot was not enabled at this point). KNOX did not trip.
Magisk:
After rooting process. Enabled password protection, which automatically started secureboot. Installed Magisk and allowed root privileges; required reboot. Which is where the problem begins.
KNOX:
Obviously, with root privilege system changes and secureboot enabled, KNOX froze startup processes. I was lazy, and didn't want to lose the work put in to gain SuperSU, and tried to use some exploits to bypass FRP lockout. One of these attempts triggered a factory reset, which I did not want (Like I said.. I was being lazy, and didn't want to have to redo all the settings and logins I'd just redone after root). I forced the phone to shut down, and broke the system. lol..
Attempts to repair:
- After about 4 hours of exploring exploits, I finally gave in, and attempted factory reset. Phone wiped data, but the recovery data seems to be corrupted, cannot be fixed by factory reset, or erased entirely, because the process continued no further than the wipe.
- Tried Samsung SmartSwitch (Replacement for Kies), but device was not recognized, and would not accept IMEI (Serial), nor would it allow any emergency recovery without these.
- Acquired stock firmware, and attempted flash with Odin. (BL, AP, CP, CSC) and received message "FAIL! (Auth)" (PC side), and "SW REV CHECK FAIL: [aboot]Fused 4 > Binary 1 [1]eMMC write fail: aboot" (Device side). Which I assume means that secureboot is blocking flashing from ODIN..
- Attempted to flash firmware from SD - Secureboot will not allow updating from SD or from ADB.
Repair (possible?): So, my question is this: Has anyone experienced this, or is there any kind of advanced solution to this? I am of low to mid-level computer programming expertise. I do not understand the theory behind what I was doing, just the process itself. Is there any way to reset the device to stock functionality, and if so.. How?
Hello! Does
Odin Fails with eMMC write fail error.
Hello everyone. I just purchased a Sprint Note 4 (SM-n910P) that has Android 5.1.1 currently installed. While I know there is no current chainfire autoroot for this version of android, I was planning on downloading to 5.0.1 using the ROM file...
forum.xda-developers.com
help you?
Hi,
1- I was asked by the family to help unlock the phone of a tragically and untimely deceased person.
I do NOT want to reset !!!!!!!!, must recover photos, whatsapp and more
2- Phone is pattern lock, SM-G930F
3- phone is active and can receive calls
4- FRP lock: ON
5 - USB debugging: OFF
6 - I have access to google account, but it says "cant locate active phones"
7 - phone is registered in "Google Play"
I would appreciate and assistance, the family is really heart broken and waiting or this.
Thanks, Harris
The phone must be connected to a network, in order to find it using android device manager. Or else you need a custom recovery to remove the lock screen key. Or ADB, I don't know the exact method but try searching for removing lockscreen security using ADB.
Most services will provide access to an account if you provide a valid death certificate, that may be an option in getting the google account credentials to unlock FRP.
I would like to help you if you still having this problem
Is it a bit 1 or a bit 2 G930F check this is download mode will be under AP SWREV: B:1=BIT 1 AP SWREV: :B:2=BIT 2 if bit 1 just find a full version of the bit 1 combination file it will have FXXU1 as part of the file name or FXXU2 for bit 2 REMOVE THE .PIT FILE from combination though first of there is one this will wipe the device,
flash in the AP tab of odin let it boot, once booted in the top left tap the menu icon now look for an app with a folder icon all personal data is stored here, this works for S8 with combination file but im not sure as i havent tested on S7 before with it also DO NOT flash a bit 2 binary to a bit 1 device you will never be able to use bit 1 firmware of any kind again after flashing with a bit 2 firmware and also if the knox counter is tripped the comhination files will not boot on the device for some reason i have confirmed this with a knox tripped and non knox tripped device so it cannot have knox 0×1 - 0x50c - 0x500 for some examples
If the app isnt there with personal data then just flash the device with stock firmware again but DO NOT use the CSC you MUST USE the HOME_CSC as this will keep all data and apps in place and will take you straight back to the lock screen again,
If adb were enabled i would of been able to help you out but theres no way to enable adb without the risk of losing the personal data on the device
Hello dear XDA community,
as new user here I was very excited to find this great platform and have learnt finally how to improve privacy on my samsung... I installed TWRP, successfuly rooted by Magisk, added Xposed, Xlua Privacy... all was good until... My phone didn't become FRP locked... Probably locked the device when I was trying to log into google account because of WhatsApp backups
I tried to get to download mode and flash it by Odin in this download mode but process failed, FRP locked appeared and... before when I was recovering system by TWRP I was successful but second time probably OEM was turned off and that's why I have a problem now
could you please advice me any software which with I can get rid of this FRS lock from download mode? I don't mind to pay also for this software but I am worried about fake software...
My problematic mobile phone Samsung Galaxy A5 Duos (2017) SM-A520F/DS - It is dual sim phone (It is international version of A5)
Android: Oreo 8.0.0
Serial Number: R58K24KNKKR
Build Number: R16NW.A520FXXS8CSB1
Please give me an advice
thank you
The only way I have been able to do this is to flash an egnineering bootloader and then run an adb command that wipes the security then reflash your bootloader, load your ROM from recovery, and reboot.
any guidance how to flash an egnineering bootloader and then run an adb command please?
Thank you for you advice
It may be not easy for some users. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Flashing Instructions
Make sure the bootloader unlocked
Enter Download Mode
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing twrp-3.5.2_10-0-a52q.tar as AP in ODIN, then click start.
DO NOT SKIP THIS STEP! Don't remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key until red warning "This phone is not running Samsung's official software..." disappears. Then release all keys. It will take more time than usual until TWRP recovery appears.
Install Kakarot-UNI-1-A52-2021-05-13-23-11.zip
Install Disable_Dm-Verity_ForceEncrypt_20210320.zip
Install Magisk-v23.0.zip, Swipe to confirm Flash ( Ignore this if you don't want to root it )
Format data
Select Reboot to System
Setup the phone
Done!
Rooting
Connect Phone to Internet
Install Magisk and Open it. Magisk will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done
Recommended to Watch This Video!
Download and Terms
The phone bootloader must be unlocked, if not read How to unlock bootloader Galaxy A52
Download TWRP twrp-3.5.2_10-0-a52q.tar
Download Disable_Dm-Verity_ForceEncrypt_20210320.zip
Download Kakarot-UNI-1-A52-2021-05-13-23-11.zipsafetynet-fix-v1.1.1.zip
Download Magisk-v23.0.apk stable Rename to Magisk-v23.0.zip
Credits to:@RealVelosh for TWRP 3.5.2
@neel0210 for Kakarot Kernel
Thanks a lot, this is what I was looking for an updated guide on how to root these great phones! Will this work with the July 1 security patch update?
kidkree1 said:
Thanks a lot, this is what I was looking for an updated guide on how to root these great phones! Will this work with the July 1 security patch update?
Click to expand...
Click to collapse
Yes, it works
So I have been looking into rooting as well. And dozens of threads are mistakenly assuming OEM unlock is an available option under Developer Options on this phone. It's not there. So anything after that is not going to happen. I am referring to the A52 5G US version with the 750c Snapdragon chipset.
The only supported option is paying ransom for a 3rd party unlock as far as I can tell.
Anyone tried this version on A52 5G version? Simply cant find any root methods for my device.
Faakarna said:
Anyone tried this version on A52 5G version? Simply cant find any root methods for my device.
Click to expand...
Click to collapse
This method should work, unless you have the U.S. variant in which case you won't be able to use any method until you unlock the bootloader (paid services afaik)
So ive been rooted for a few weeks now and was successfully passing safetynet. But now out of nowhere CTS started failing, i cant pass it anymore even without magisk. Anyone having the same issue?
Simon1511 said:
So ive been rooted for a few weeks now and was successfully passing safetynet. But now out of nowhere CTS started failing, i cant pass it anymore even without magisk. Anyone having the same issue?
Click to expand...
Click to collapse
Yes, a few people are having this issue. Seems that Google pushed something out that detects current known bypass methods.
ShaDisNX255 said:
Yes, a few people are having this issue. Seems that Google pushed something out that detects current known bypass methods.
Click to expand...
Click to collapse
Urg. Is there a fix for that? Or do i need to re-lock my bootloader (since it still fails even without magisk)
Simon1511 said:
Urg. Is there a fix for that? Or do i need to re-lock my bootloader (since it still fails even without magisk)
Click to expand...
Click to collapse
Well this is quite new as in it started to fail today (for me) so I think people are scrambling right now to get a fix. I haven't read anyone that has fixed it yet.
ShaDisNX255 said:
Well this is quite new as in it started to fail today (for me) so I think people are scrambling right now to get a fix. I haven't read anyone that has fixed it yet.
Click to expand...
Click to collapse
Ok, thanks. Was just curious if relocking BL could fix it
Magisk Hide has been removed from the main server, so it won't pass CTS now. There is a fix, please search!
Hi! I did everything according to instructions, but I don't get past step 5.
After pressing and holding Volume Down + Power Key, when the screen went blank I quickly pressed and held Volume Up + Power key, got the Red Warning, but instead of going away it stayed and I got a few lines with green background:
RPMB fuse set
RPMB PROVISIONED
CURRENT BINARY: Custom (0x00C)
FRP LOCK: OFF
OEM LOCK: ON (U)
KG STATUS: CHECKING
WARRANTY VOID: 0x1 (0x30C)
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B1(1,1,1,1,1,1) K1 S1
SECURE DOWNLOAD: ENABLE
HDM STATUS: NONE
DID: [16 digits]
That's it. Never went further.
HELP PLEASE! Thanks!
P.S. - I've made sure the bootloader is unlocked.
FlugHund said:
Hi! I did everything according to instructions, but I don't get past step 5.
After pressing and holding Volume Down + Power Key, when the screen went blank I quickly pressed and held Volume Up + Power key, got the Red Warning, but instead of going away it stayed and I got a few lines with green background:
RPMB fuse set
RPMB PROVISIONED
CURRENT BINARY: Custom (0x00C)
FRP LOCK: OFF
OEM LOCK: ON (U)
KG STATUS: CHECKING
WARRANTY VOID: 0x1 (0x30C)
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B1(1,1,1,1,1,1) K1 S1
SECURE DOWNLOAD: ENABLE
HDM STATUS: NONE
DID: [16 digits]
That's it. Never went further.
HELP PLEASE! Thanks!
P.S. - I've made sure the bootloader is unlocked.
Click to expand...
Click to collapse
Did you figure out how to fix this?? I have the same issue!
Hello guys, so I was rooting my phone and I had just ended loading the "A52_MagiskPatched_AndroidHowTo.tar" AP thing via Odin. Instead of taking me to the recovery and is stuck at this screen.View attachment 5474237
I can still load into the download screen, but that's all.
If any one has any solutions please reply, I am sure I did all the steps, but now I'm doubting myself is there a way to revert it or something?
If someone can help me I promise to give a small compensation!
Discord: Non Sense Speaks#4580
DID YOU FIND SOLUTION TO THIS? I HAVE SAME LOGO ISSUE AND WANT TO REMOVE BOOTLADER UNLOCKED RED ALERT
I have samsung sm-a525f android 12 OUI 4.0 security patch 1 dec 2021, i've read this tutors n find that if we want to root the device we must install TWRP before rooting it. Now, i have a question, why must we install the custom recovery before doing that root session? Why cant we just flashing the root files using the stock recovery ? thank you.
frenxl said:
I have samsung sm-a525f android 12 OUI 4.0 security patch 1 dec 2021, i've read this tutors n find that if we want to root the device we must install TWRP before rooting it. Now, i have a question, why must we install the custom recovery before doing that root session? Why cant we just flashing the root files using the stock recovery ? thank you.
Click to expand...
Click to collapse
Because you can't flash root files using stock recovery, they're unofficial files.
Hi! I have a new Samsung Galaxy A52 (SM-A525M variant, Latin America). Anyone tried this method on the "M" variant yet? I've already unlocked the bootloader successfully.
More data:
A525MUBU4AUJ3
nov. 2021 security update
I can debloat it with ADB, but I love root.
Thanks in advance to this great community!
EDIT: I want to thank explicitly ShaDisNX255 for the guide and help in succesfully rooting my phone!