Develop Bugs

G925F Kernel rev. problem during root.

Hello! This is my first post, please move my thread if I posted it on the wrong place.
Issue:
Tried to root a costum rom for my S6 edge. I used ODIN to root BL and a modem. A message came up "Custom binary blocked by Reactivation Lock". Went i booted my phone up, it's stuck on Samsung Galaxy S6 edge screen. A red text in the upper left corner says "Kernel rev. Check fail. Device: 2, Binary: 1"
So the problem is I can not boot my phone. Tried to download stock firmware and root it via Odin. Did not work. I can not get into recovery mode either.
Please help me. My phone is stuck and can not be used.
Kind regards.

roniit said:
Hello! This is my first post, please move my thread if I posted it on the wrong place.
Issue:
Tried to root a costum rom for my S6 edge. I used ODIN to root BL and a modem. A message came up "Custom binary blocked by Reactivation Lock". Went i booted my phone up, it's stuck on Samsung Galaxy S6 edge screen. A red text in the upper left corner says "Kernel rev. Check fail. Device: 2, Binary: 1"
So the problem is I can not boot my phone. Tried to download stock firmware and root it via Odin. Did not work. I can not get into recovery mode either.
Please help me. My phone is stuck and can not be used.
Kind regards.
Click to expand...
Click to collapse
Welcome to the new brick.
Your phones built-in security has determined that your custom ROM and odin activities are a security threat and has locked up the phone so that you cannot do anything with it.
If you had set up a security password for the reactivation lock you would be able to input password and unlock /reboot phone back to working order.
Don't know if you can get out of this, the purpose of this is so that if phone is stolen it becomes useless.
Pp.

S4 Mini GT-i9195i crashes after recovery - (how to reinstall stock ROM)

Hi,
I have Galaxy S4 Mini VE GT-i9195i. The phone was a bit laggy, so I decided to factory reset. When I did it, the phone didn't booted. It was showing Odin download screen with red text "Could not do normal boot, odin mode" (or something like that). In thread [index] Galaxy S4 mini i9195i were some recoveries, so I used odin to recovery it. Now, when booting, it shows "Kernel is not seandroid reinforcing, set warranty bit:kernel" and when it boots up, there is setup screen (the one which shows when you firt turn the phone on), but the phone is spamming with message boxes "<random process or app> stopped working", so I can't do anything(by fast taping OK, I manage to get through few screens, but when it come's Google account choose, the screen goes black).
I tried another recovery, but none of them worked.
In the forum, there is also link to stock ROM, I think wiping all the data and flashing the phone with stock ROM could help, but last time I did something like this was about 5 years ago with Xperia, and I couldn't find any guide how to do this, so could you guys please tell me what to do?
Thanks.

adamjezek98 said:
Hi,
I have Galaxy S4 Mini VE GT-i9195i. The phone was a bit laggy, so I decided to factory reset. When I did it, the phone didn't booted. It was showing Odin download screen with red text "Could not do normal boot, odin mode" (or something like that). In thread [index] Galaxy S4 mini i9195i were some recoveries, so I used odin to recovery it. Now, when booting, it shows "Kernel is not seandroid reinforcing, set warranty bit:kernel" and when it boots up, there is setup screen (the one which shows when you firt turn the phone on), but the phone is spamming with message boxes "<random process or app> stopped working", so I can't do anything(by fast taping OK, I manage to get through few screens, but when it come's Google account choose, the screen goes black).
I tried another recovery, but none of them worked.
In the forum, there is also link to stock ROM, I think wiping all the data and flashing the phone with stock ROM could help, but last time I did something like this was about 5 years ago with Xperia, and I couldn't find any guide how to do this, so could you guys please tell me what to do?
Thanks.
Click to expand...
Click to collapse
Sorry to hear about your situation. I think flashing the stock rom is the last best option. Anyways here r the steps:
1. Download Odin 3.1x.x version( its the program via which you can flash samsung stock roms, modems,recoveries and caches etc,...google it)
2.If possible, before doing anything to your phone, take a nandroid backup from recovery like TWRP or CWM)
3.Hold power+home+volume down button to boot into bootloader menu. Once booted, it will ask you to press volume up button to continue, do that.
4.Now connect your phone to your pc via data cable( kindly confirm that your pc usb ports are working properly otherwise the flashing will corrupt)
5. Open Odin. If connected properly, you will see the ID:COM tab turn blue mentioning the port name you connected.Now click AP on right hand side and search /select the location where your Stock rom(md5) file is located. Now on left side panel(logs) you will see something is going on. Wait for a few minitues and after processing is done (when you see the lines "leave cs...") Click start and relax.
6.It will take some time to flash the rom. If everything went well, there will be a "PASS" message on top left of Odin. The phone will boot into recovery and do some cleaning and reboot again.......................................................Congratulations!!
Note: I follow this method on GT-9192 and i think its same with your model.

I think the message "Kernel is not seandroid reinforcing" means incompatible recovery software for this device. Try different one.

The only working recovery for our phone is TWRP recovery. Flash the .img through flashify after rooting with Kingroot / Supersu me and you are done . Be sure to flash the stock rom through odin to fix any hiccups with app not responding and after proceed normally.

Phone stopped working, no idea how to fix it now

I don't know what happened but all of a sudden my gs4 stopped working and I could only get it up to the logo before it rebooted again. I am a total noob so I don't have any developer apps or firmware or whatever. I tried using Kies but I get stuck on the serial number part as I have entered everything on the box and behind the battery with none of them working. Now I am trying to use Odin but I think I messed up my phone even more. On the box it says M919NUVUEMK5 so I downloaded the firmware with that same code but originally I had downloaded the NUVUFOK one and used that. So I followed the guide and used that NUVUFOK file, and it seemd to be working as the download bar on my phone was almost done, but then all of a sudden it failed. I figured that was the wrong firmware so I went back and got the MK5 one, but now when I try to do the same thing with this firmware the bar only loads a tiny bit and then stops. Also the phone won't start up properly after I tried this, now it says there is an issue with the firmware upgrade and I need to use recovery mode in Kies. I have no idea what to do or what I am even doing, all I want to do is get my phone working again.

If you live in the US, you can take it to Best Buy an they will use there software to get it working again. Its hell of a lot less work.

Reformat
Operation Ivy said:
I don't know what happened but all of a sudden my gs4 stopped working and I could only get it up to the logo before it rebooted again. I am a total noob so I don't have any developer apps or firmware or whatever. I tried using Kies but I get stuck on the serial number part as I have entered everything on the box and behind the battery with none of them working. Now I am trying to use Odin but I think I messed up my phone even more. On the box it says M919NUVUEMK5 so I downloaded the firmware with that same code but originally I had downloaded the NUVUFOK one and used that. So I followed the guide and used that NUVUFOK file, and it seemd to be working as the download bar on my phone was almost done, but then all of a sudden it failed. I figured that was the wrong firmware so I went back and got the MK5 one, but now when I try to do the same thing with this firmware the bar only loads a tiny bit and then stops. Also the phone won't start up properly after I tried this, now it says there is an issue with the firmware upgrade and I need to use recovery mode in Kies. I have no idea what to do or what I am even doing, all I want to do is get my phone working again.
Click to expand...
Click to collapse
Hello. You will need to reformat your device so odin can recognize it. This can be done by using odin to flash a custom recovery like TWRP. The download link for that custom recovery is: https://dl.twrp.me/jfltetmo
Once you have that downloaded open odin and select AP option. Browse to where you saved TWRP and select it. Now proceed with flashing like normal. after its done flashing turn off the device.
After it is completely off hold the power button and volume up button simultaneously until you see the blue words on the top right corner of the boot logo screen.
Now you are in the twrp custom recovery menu. Go to Wipe > Advanced Wipe then select everything except for external sd, USB, and internal storage.
Once it is complete formatting turn the phone off again and boot back into download mode. Now you can reflash the correct firmware for your phone. I recommend using this firmware instead since it is a whole image rather than an incremental update. After flashing this your phone will reboot, give you the loading android logo and then the phone will start up once again! Good luck

The phone is giving the firmware error message because you tried to flash an older firmware to the phone.
Download the latest firmware for your phone and reflash it using Odin and the original Samsung USB cable.

AndroidInitiate said:
Hello. You will need to reformat your device so odin can recognize it. This can be done by using odin to flash a custom recovery like TWRP. The download link for that custom recovery is:
Once you have that downloaded open odin and select AP option. Browse to where you saved TWRP and select it. Now proceed with flashing like normal. after its done flashing turn off the device.
After it is completely off hold the power button and volume up button simultaneously until you see the blue words on the top right corner of the boot logo screen.
Now you are in the twrp custom recovery menu. Go to Wipe > Advanced Wipe then select everything except for external sd, USB, and internal storage.
Once it is complete formatting turn the phone off again and boot back into download mode. Now you can reflash the correct firmware for your phone. I recommend using this firmware instead since it is a whole image rather than an incremental update. After flashing this your phone will reboot, give you the loading android logo and then the phone will start up once again! Good luck
Click to expand...
Click to collapse
I downloaded it and it worked but now can't get past the "blue words" part. When trying to go into recovery it gives me either of two screens, one says "system software not authorized by samsung has been found on your phone." with red words "secure fail: kernel" or the blue words show up followed by red words that say "recovery is not seandroid enforcing" and then yellow words "set warranty bit: recovery". the phone is still resetting and freezing randomly.

Operation Ivy said:
I downloaded it and it worked but now can't get past the "blue words" part. When trying to go into recovery it gives me either of two screens, one says "system software not authorized by samsung has been found on your phone." with red words "secure fail: kernel" or the blue words show up followed by red words that say "recovery is not seandroid enforcing" and then yellow words "set warranty bit: recovery". the phone is still resetting and freezing randomly.
Click to expand...
Click to collapse
you are using the T-Mobile Samsung Galaxy S4 right?

AndroidInitiate said:
you are using the T-Mobile Samsung Galaxy S4 right?
Click to expand...
Click to collapse
Yes it is the SGH-M919N model.

Operation Ivy said:
Yes it is the SGH-M919N model.
Click to expand...
Click to collapse
You need to boot into recovery holding volume up and power button simultaneously. Once your in recovery mode format it. then you can reflash stock firmware.

Custom binary blocked by FRP.

My friend's J2 Prime (SM-G532G/DS) happened to be stucked at Security Error (blue screen), no idea how it get there. Tried to flash stock firmware. But after flashing, the phone booted back into the same blue screen, now with a line of red text at the top saying, "Custom binary blocked by FRP. (recovery. img)". Tried many different stock firmware (with 4 files) but none of them solved the problem. Can't boot into recovery, only download mode. Can someone give me detailed step by step on how to fixed this.
If it help, I'm from Malaysia. So maybe the firmware might need to be from this region. Not sure about the origin of the phone though. Also, what could be the reason for this to happen? I'm assuming root. Could it even happen on its own, I mean without rooting or flashing?

also G532G/DS - ARH1 bootloader
i've been going thru lots of ROMs (including testing Lineages), this have never happened to me before.
Flashing stock firmware thru Odin though, require OEM Unlocking ON in Developer Settings.
^ I mean, did you/your friend turn it on before flashing? if not, it actually succeeded?
Only solution might be possible:
Go to stock recovery (POWER + HOME + VOL-UP), wait for it to load, then factory reset from there.
I suppose some images might help!

I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...

JEDAlive said:
I'm pretty sure the OEM if off because he know nothing about this thing. When I got it, it already like this. Can't get into recovery, after the first Samsung logo appear, it went straight into the error screen. Same thing happened after flashing.
I don't know how to post images here...
Click to expand...
Click to collapse
+ OEM Unlock: if disabled, Odin should've failed straight away and no reboot stuff going.
+ Can't get into recovery:
Is it true that you cannot get into recovery? If left stock, It should be an Android with spinning stuff, text is "installing update" then no command for a while ~2min, and it will go to normal recovery.
I mean, it is supposed to do "recovery" :v
+ Images: post it on Imgur (or any online image service). Copy link here, add space between "https://" and all the stuff there. Wont be considered URL i guess (havent tried)

Recovery boot loop on P605. Device constantly disconnects in ODIN download mode.

I have recently successfully rooted my P600 and P605. However I had an old version of TWRP on the P605 (which I installed to get this non-western model of the P605 upgraded to 5.11 as OTA updates wouldn't work) so I decided to update it to using the offical Google Play store app. That's when disaster struck and I hit a rapid infinite boot loop, rebooting every 3 seconds or so.
It says this on the screen:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
I've read around and I have managed to get the device into download mode without having to let the battery drain. I achieved this holding down the power button for 26 seconds. At 26 seconds the screen goes black and take my finger off the power button. Then by pausing for a few beats and then holding down the -vol button and holding the power button I am able to get into download mode.
Sadly though, when I connect the broken P605 to Odin it connects then rapidly keeps disconnecting every couple of seconds, making it impossible to get anything uploaded onto it. I have a P600 that I have tested the Odin connection on and it manages just fine with the same lead, so the problem could be the usb port on the device itself, but given that it was functioning perfectly prior to this botched upgrade I am now at a loss. Is this tablet only useful for parts now, or is something else I can try? I'm happy to wipe this if I can just get a new firmware onto it.
Here's what the screen says in the Download mode if it helps shed light on the situation:
ODIN MODE
PRODUCT NAME: SM-P605
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 0X1 (2)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, R2, A2, P2
SECURE DOWNLOAD: ENABLE
UDC START
Hope someone can come to my aid.

Well it looks like I managed to come to my own aid. So I thought I would record what I did in case it can help somebody else.
I considered the issue might be the Windows machine that I was on. I only have 1 Windows machine in the house, but 2 Macs, so I looked up how to get Odin working on a Mac. Thankfully, even though there is a fair amount of messing around I managed to get the device to connect first time (and stay connected). There were some teething issues so I will describe what I did as best I can.
First off I did some searching and found Jodin (a Java version of Odin). I needed to install Heimdall and Java as well, but luckily I had already installed Heimdall before when attempting to connect my Mac to my Droid before. This is just as well because Mojave doesn't let me install Heimdall 1.40, possibly because of some new security sandboxing. But because it was already there from El Capitan I was ok. If you any one else in the future needs Heimdall then I guess you need to research the latest developments around that.
Once I installed Java I ran Heimdall. I followed the instructions from this good chap: https://www.youtube.com/watch?v=UeUqaZiGoZk and got the PIT file that I needed for Jodin to work correctly.
Once inside Jodin it all seemed fine, but then a dialog wanting my password to run OSAscript was requried and it seemed to FAIL the upload. After closing Heimdall and relaunching Jodin I was able to install "twrp-3.0.2-0-lt03ltexx.img.tar" using the settings from the video and it finally rebooted to the splash logos and finally 5.1.1.
Hope this helps someone who was as unfortunate as me. I will be more cautious in the future.