I have flashed the TWRP .tar file. But when I do a restart, I get this error, SECURE CHECK FAIL: recovery.img
Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost.
How do I fix this issue? Thanks.
secretwolf98 said:
I have flashed the TWRP .tar file. But when I do a restart, I get this error, SECURE CHECK FAIL: recovery.img
Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost.
How do I fix this issue? Thanks.
Click to expand...
Click to collapse
Any luck with this? I'm encountering the same problem.
Cheers
secretwolf98 said:
I have flashed the TWRP .tar file. But when I do a restart, I get this error, SECURE CHECK FAIL: recovery.img
Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost.
How do I fix this issue? Thanks.
Click to expand...
Click to collapse
I faced the same issue.
Possibly you are on Android 10; you need to flash a less secure bootloader (BL).
I attached it; extract the file to find a .rar file. Flash it using ODIN as "BL". Then flash the recovery file, as "AP". You can also flash them both at the same time.
BTW, did you get GSI working by any chance?
I am facing the same issue. I know how to get out of that boot loop but cannot figure out how to get TWRP to boot. To get out of that boot loop, just press VOL+ && VOL- simultaneously and go back into download mode that way, then just reboot.
waxxx333 said:
I am facing the same issue. I know how to get out of that boot loop but cannot figure out how to get TWRP to boot. To get out of that boot loop, just press VOL+ && VOL- simultaneously and go back into download mode that way, then just reboot.
Click to expand...
Click to collapse
Thank you so much! This seemed to work fine for me
secretwolf98 said:
I have flashed the TWRP .tar file. But when I do a restart, I get this error, SECURE CHECK FAIL: recovery.img
Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support. Please note that repair/return for this issue may have additional cost.
How do I fix this issue? Thanks.
Click to expand...
Click to collapse
I Had the same problem with my smt295 and I did fix it by using the bootloader mode to get it to connect to Odin, ( which it never did in the error window) then I flashed it using an official firmware. I made a video about it
I had this same problem...Odin would always fail out right after it got to "aboot.mbn.lz4" every time i tried to flash it with anything.
Fixed the problem by running Odin 3.13 instead of Odin 3.12
Same problem here but can't seem to enter download mode. When the device is plugged in it doesn't let me shut it down (I guess because of the battery loading thing) and pressing both vol keys and then plugging in the usb also does nothing but just bring up that same screen. Any ideas?
Tizu69 said:
Same problem here but can't seem to enter download mode. When the device is plugged in it doesn't let me shut it down (I guess because of the battery loading thing) and pressing both vol keys and then plugging in the usb also does nothing but just bring up that same screen. Any ideas?
Click to expand...
Click to collapse
Click the power button; the device will shut off. Give it a few minutes, then hold both Volume buttons and plug in the USB cable. It should boot into download mode.
What you'll need to do is reflash the factory firmware in Odin, then when the device reboots, you must not let it boot into Android. Click one of the volume buttons when the orange Unlocked screen comes up, and select Download Mode. Or, hold Volume Up after selecting Power to continue to boot into recovery, then select Reboot to bootloader.
Once you're in download mode again, you can flash TWRP. However, again, you must not let the device boot normally; you must boot into Android, then once in TWRP, flash the Multidisabler and wipe data.
Related
This is not the first time i root an android device but it is the first time im doing it on an S5, nonetheless I am pretty much stuck right now.
I tried to install CF-Auto-Root-klte-kltexx-smg900f.tar using Odin from here, it installed with no problems, but when the phone restarted I get:
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
and then it shuts down.
I tried to enter recovery mode by doing power+vol up+menu but nothing happens ?
Can anyone help ?
EDIT: ok, so I did manage to get it running again by flashing openrecovery-twrp-2.8.5.0-gt-klte. This got me past the "Recovery is not seandroid...", but all in all I still didn't manage to get root access...
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
You don't flash .img - you flash .tar
*Detection* said:
You don't flash .img - you flash .tar
Click to expand...
Click to collapse
I did flash .img.tar actually. Still no effect - boots to regular recovery. Can't figure this out...
i get in the same situation...why still rebooting in original recovery?
i installed this one CF-Auto-Root-klte-kltexx-smg900f.tar with odin with succes but still have
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
then when i boot i get a black screen with all application error....the only way to get it back working was to wipe factory reset in original recovery.
what can i do to get it working so i can install custom roms?
thx in avance
seaskyways said:
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
Click to expand...
Click to collapse
I can't seem to get the coustom recovery installed, and after some digging i found this :
manubhargav said:
Actually the problem was that custom recovery(twrp here) was not installed at all, that above mentioned error occurs when you try to install SuperSU.zip from stock recovery<3e>.
This happens because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
VL4DST3R said:
I can't seem to get the coustom recovery installed, and after some digging i found this :
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
Click to expand...
Click to collapse
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
---------- Post added at 05:36 AM ---------- Previous post was at 05:32 AM ----------
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
manubhargav said:
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
VL4DST3R said:
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
Click to expand...
Click to collapse
Ah, So the problem you're facing is NOT getting into recovery mode
There are 2 ways to solve the problem, (1st -> flashing recovery.tar again, 2nd-> flashing stock firmware)
First method:
Enter "Download Mode" by holding down "Volume Down"+ "Home" + "Power" button.
Flash recovery.img again and check if it boots into recovery this time.
Sometimes this may not work and you may need to try flashing firmware
Second method:
Download Firmware from here
Open odin in your PC
Enter "Download mode"
Connect the device to PC using USB
Flash the PDA, BL, AP, CSC etc.
Alternatively, You can flash the firmware using SmartSwitch
manubhargav said:
Ah, So the problem you're facing is NOT getting into recovery mode
Click to expand...
Click to collapse
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
VL4DST3R said:
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
Click to expand...
Click to collapse
Which Kernel version are you in? Which TWRP version did you try? Install other custom recoveries? On locked bootloader?
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
VL4DST3R said:
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
Click to expand...
Click to collapse
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
manubhargav said:
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
Click to expand...
Click to collapse
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
VL4DST3R said:
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
Click to expand...
Click to collapse
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
Boot Rom and go into settings/aboutphone/ click build number rapidly.
Developer settings should appear, then go into developers options/ click on "root access" and enable it.
---- now test if its working . however....
2)
If its not working, take yourself back into twrp and flash that supersu beta.
----now test again. However ....
3)
If it doesn't work again .
go back to stock 5.0 rom>>> put twrp on >>> and flash DAT supersu .
now test ya rom again. However.........
4)
If it dont work again ..
go back to stock 4.4 rom>>> put twrp on>>> and flash a random supersu.
now test ya rom again. However.....
5)
if that doesn't work again,
Go back to stock rom through (odin) and restart the process from the top .
btw the "recovery is not seandorid enforcing" is normal . not an error.
GeniusisHere said:
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
---- now test if its working . however....
2)
----now test again. However ....
3)
If it doesn't work again .
now test ya rom again. However.........
4)
If it dont work again ..
now test ya rom again. However.....
5)
if that doesn't work again, .
Click to expand...
Click to collapse
First of all holy **** what an answer... let's SLOW DOWN a bit first, shall we ?
Secondly you lost me from step 1, I don't want CyanogenMod, I want the default Samsung 5.0 with TouchWiz (contrary to popular belief I actually like it).
Also I would really like to know (from someone that actually knows why this happens) why is it reverting to default recovery and how can I stop it from doing so ? manubhargav had an interesting idea, but sadly it doesn't work for everyone (as someone else mentioned on that other post)
So I'm guessing no one knows the answer to my problem considering almost a moth has passed...
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
RL is still there with LP too
Can not boot into recovery due to AT&T update wanting to install, and stuck in BTLP.
My S7 Edge is stuck in a bootloop, USB Debugging is off unfortunately cause the packages all started to crash on the phone for no reason, and now it turned off and entered a bootloop. I can not enter recovery mode cause every time I attempt to enter recovery it prompts a AT&T update and will not let me get pass that yet the update fails every time. I have attempted to reflash to original firmware although ODIN gets stuck on setupconnection every time. Please help!
I had this happen once. I had to enter bootloader (not recovery) and reflash using ODIN. Try some of the different ODIN builds floating around in these forums if you're having problems
sam2c said:
I had this happen once. I had to enter bootloader (not recovery) and reflash using ODIN. Try some of the different ODIN builds floating around in these forums if you're having problems
Click to expand...
Click to collapse
hi i have the same problem , can you explain how to enter the bootloader please ,
Bootloader aka download mode: turn device off. Hold volume down, home, and power button at same time.
Remember: volume down for download mode. Volume up gets you into recovery
Problem solved! i was installing the wrong version of twrp this is the correct version: https://eu.dl.twrp.me/j5xnlte/
I'm using SM-J510H
So I installed samsung drivers.
I even installed ADB and it's drivers (now i have samsung android in the device manager)
I downloaded TWRP for j53gxx:
https://eu.dl.twrp.me/j53gxx/
The .tar for odin (twrp-3.4.0-0-j53gxx.img.tar)
I did the OEM unlock and debugging thing I even got the notification that the computer was trying to access blah blah I did allow always.
Put the phone in download mode (Down + Home + Power)
Press up to enter download mode.
Connect the phone.
Untick reboot in odin.
Use the ap to select the correct file
Start success!
I try to reload into recovery tried so many different ways even the adb command to reboot into recovery. All I get is a little thing on the top left saying warranty bit recovery and then the screen is black.
It doesn't load into the default recovery it just stays black. I need to take the battery to rest...
I tried with adb but when i force it to load up into download mode (adb reboot bootloader)
adb doesn't recognize the phone anymore
I've now downloaded the android ask maybe that will solve things lol but does anyone have any advice please?
Should I consider installing a different recovery? like maybe CWM?
It has a costume rom on i guess it says "Hebrew by daniel mouyal for bt" in the about tab in the settings...
I tried using ADB to install but when it's in download mod it can't find the phone so when i enter the install command:"fastboot flash recovery twrp-2.8.x.x-xxx.img" it says: "waiting for device"
Well I've been installing the wrong version of twrp lol sry!
So just in case someone else hits the same problem it's not the twrp i posted before but this one:
https://eu.dl.twrp.me/j5xnlte/
When recovery is finished flashing in Odin, remove your battery to turn the device off.
Then put the battery back in and press vol+ and power button and home button at the same time.
Your device should then boot into twrp.
If you reboot before doing this the android operating system will ovewrite twrp with stock recovery and you will have to start the process again
Also you used the wrong twrp. J53gxx is 2015 model j500h and j5xnlte is j510fn not j510h. You must be careful or else you may seriously damage your device.
Use this twrp here for your device j510h
garylawwd said:
When recovery is finished flashing in Odin, remove your battery to turn the device off.
Then put the battery back in and press vol+ and power button and home button at the same time.
Your device should then boot into twrp.
If you reboot before doing this the android operating system will ovewrite twrp with stock recovery and you will have to start the process again
Also you used the wrong twrp. J53gxx is 2015 model j500h and j5xnlte is j510fn not j510h. You must be careful or else you may seriously damage your device.
Use this twrp here for your device j510h
Click to expand...
Click to collapse
Thank you for the response!
I managed to figure out the issue it was the wrong twrp version.. I can't update the title though
That's no problem.
What I would suggest though is to post how you fixed your issue in case anyone has problems in the future they can be referred to your thread here
garylawwd said:
That's no problem.
What I would suggest though is to post how you fixed your issue in case anyone has problems in the future they can be referred to your thread here
Click to expand...
Click to collapse
I did in my second post I posted the correct link to the correct version of twrp
I'll edit it so it's more visible
Seems I found a way to semi brick my SM-T500. I was attempting to install the LOS 18.1 ROM just posted in the guide section. Some how I got the "can only install official" error message on my download screen after flashing TWRP. Made the mistake of flashing only the stock AP without BL or CSC and now I can't get into either recovery or download modes. Holding vol up and down and plugging in USB cable does nothing. Same with holding power button and either vol up or down. Blank screen. Can only power on and boot to system.
Did you install twrp and can you get into recovery. I had similar problem but was still able to get into download mode from power off. However to do so I had to boot into twrp and select reboot and power off... from that menu you can also boot directly to download mode... I know that doesnt halp much if you hadnt installed twrp yet... but thought I would throw that out there...
wizzdome said:
Did you install twrp and can you get into recovery. I had similar problem but was still able to get into download mode from power off. However to do so I had to boot into twrp and select reboot and power off... from that menu you can also boot directly to download mode... I know that doesnt halp much if you hadnt installed twrp yet... but thought I would throw that out there...
Click to expand...
Click to collapse
I can't boot TWRP or download. The only thing that will boot is system. Can't even get to the lock/unlock screen.
can you connect to adb shell? and try #reboot download
or #reboot twrp. I figure if you get to download you can reflash stock and start over.
Also when your trying to boot into recovery try not being plugged in. Not sure about this device but a lot of older Samsung's that I had would not let me get into recovery if I was plugged in during boot.
Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset
I saw alot of issues with twrp so I tried Magick for first time ever on my SM-T500 and had a minor hiccup bc I wasn't paying attention to firmware and installed an old AP with newer firmware but ended up just reflashing the whole tablet with the same firmware as the AP that is required for Root and presto it worked! AND HEY IM DEF A NEWBIE!
housemusix said:
Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset
Click to expand...
Click to collapse
Yeah I've run into the same thing, I originally missed the step to run Magisk after I flashed the patched tar and rebooted into the System and it triggered the "Prenormal KG state" problems. Finally I managed to flash stock ROM back and got to exactly where you are now.
I was able to just flash the patched Magisk AP without CSC and BL, and now it will only go to stock recovery and was able to get TWRP to work once but couldn't factory reset or wipe cache due to (which I assume was) a ton of mounting failures when it loaded.
Anyone else have suggestions to get this thing stable so I can flash LOS? I can get to Download mode.
hello, I post this because it's seems the same subject. I have to password protected (forget password) original rom tablet (non root). For me the datas are not important , I just want to remove the password or reflash with original rom. I downloaded Odin , usb driver and correct firmware. I select AP firmware with Odin, I see the connexion (COM3 green) and it's stuck to "setup connexion".
My problem is that it's impossible to enter in download mode.
When I try to shutdown the tablet, it ask me for a password.
When I press for seconds the power button , after few second I see the Samsung Logo and the tablet restarts.
I try to press volume up, volume up and volume down etc...but each combinaison...no recover, no download mode, nothing and impossible to flash . is it normal ? how to do to unsticked SetupConnetion ?
regards
bruno
housemusix said:
Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset
Click to expand...
Click to collapse
This is not the same as my problem. My problem is that I flashed AP without BL and the two don't match. It isn't that things are locked but that I can't boot to anything but system. Can't boot recovery or download so I can't flash ANYTHING. Not even stock.
Hi, I tried to install TWRP. I used fastboot. Something has gone wrong. The phone boots with the three warning screens and then displays the TWRP splash screen. It will not respond at all after this point. I can reboot using Vol down and Power but the same screens appear and then stays on the TWRP screen. The phone cannot be seen by the PC using ADB or Fastboot via USB cable. Any ideas please? Is there a way to boot and install new recovery etc from SD card perhaps?
Are you able to force a reboot to download mode?
If you click one of the Volume buttons when the bootloader warning screen comes up, you should be able to select an option to power off or reboot to fastboot.
V0latyle said:
Are you able to force a reboot to download mode?
If you click one of the Volume buttons when the bootloader warning screen comes up, you should be able to select an option to power off or reboot to fastboot.
Click to expand...
Click to collapse
Hi, thanks for taking the time to help. The only thing it seems I can force is a reboot (using Vol down and Power) It won't switch off and there are no options to get to recovery. The bootloader screen doesn't appear. The only screens which appear on boot up are those I've uploaded images of! It is now powered off due to battery being drained.
[email protected] said:
Hi, thanks for taking the time to help. The only thing it seems I can force is a reboot (using Vol down and Power) It won't switch off and there are no options to get to recovery. The bootloader screen doesn't appear. The only screens which appear on boot up are those I've uploaded images of! It is now powered off due to battery being drained.
Click to expand...
Click to collapse
I think you're misunderstanding me, and I need to clarify some things.
First, the only button needed to force a reboot is Power. Holding one of the Volume buttons during and after the phone restarts tells the device what mode you want to boot into.
Second, you ARE getting a bootloader warning, and you shared a picture of it. This is what I'm talking about:
When this screen appears, you should be able to click Volume Up or Down, and a menu should appear on the screen.
All of this is irrelevant, because what you need to do is start the device in download mode, and reflash via Odin. Starting with the device OFF and NOT PLUGGED IN, hold both Volume buttons (DO NOT PRESS POWER) and plug the USB cable from your PC in. This should start the device in download mode.
If you see KG STATUS: PRENORMAL, you cannot flash any custom binaries such as TWRP, and can only flash official firmware.
Once you do this and get your device running again, we can move on to the next step.
Thanks again for your help. My phone was fully discharged. I followed your unstructions and reflashed TWRP V3.3.1-0 (recovery.tar) using Odin 3.14.4. There was no KG STATUS message. Odin signalled success. It rebooted but am now back to square one, showing the TWRP screen. The power button does not power off even after being held for minutes. Because it has minimal charge it soon switches itself off. When the bootloader warning appears the Vol +/- does not have any effect. I have repeated this process twice.
Development! Thanks to your info I've managed to reinstall Samsung A20e stock image. Phone boots (unlocked) but normally now. I'm thinking that originally I installed the wrong version of TWRP which led to the "semi-bricking". Can you point me at the relevant download or identify the the exact TWRP file I need to install please?
Setback! I tried another version of the TWRP file, again hangs on boot at TWRP splash screen. Help please, I'm convinced now that I'm using the wrong TWRP files.
I found these instructions - https://forum.xda-developers.com/t/guide-twrp-and-root-for-a20e-a202f-updated.4384841/ - and now am able to boot to TWRP recovery. This is where I am now, looking to install Lineage.
V0latyle said:
I think you're misunderstanding me, and I need to clarify some things.
First, the only button needed to force a reboot is Power. Holding one of the Volume buttons during and after the phone restarts tells the device what mode you want to boot into.
Second, you ARE getting a bootloader warning, and you shared a picture of it. This is what I'm talking about:
When this screen appears, you should be able to click Volume Up or Down, and a menu should appear on the screen.
All of this is irrelevant, because what you need to do is start the device in download mode, and reflash via Odin. Starting with the device OFF and NOT PLUGGED IN, hold both Volume buttons (DO NOT PRESS POWER) and plug the USB cable from your PC in. This should start the device in download mode.
If you see KG STATUS: PRENORMAL, you cannot flash any custom binaries such as TWRP, and can only flash official firmware.
Once you do this and get your device running again, we can move on to the next step.
Click to expand...
Click to collapse
Happy New Year. I have now got TWRP installed. I tried to move on with Magisk (that's what one thread told me to do!) I've tried various Magisk files but again it just hangs my phone. I waited for it's battery to flatten, reboot into download and reflash original firmware and then TWRP. So, TWRP is installed ok (I think) what is the next step to install Lineage please?
[email protected] said:
Happy New Year. I have now got TWRP installed. I tried to move on with Magisk (that's what one thread told me to do!) I've tried various Magisk files but again it just hangs my phone. I waited for it's battery to flatten, reboot into download and reflash original firmware and then TWRP. So, TWRP is installed ok (I think) what is the next step to install Lineage please?
Click to expand...
Click to collapse
Sorry, life has kept me busy.
To install Magisk on the stock firmware, all you have to do is flash the Magisk .apk in TWRP. Make sure you're using the latest version.
To install a GSI, you can follow my guide here, and start at the Multidisabler section since you've already unlocked bootloader and flashed TWRP. For LineageOS specifically, refer to the thread on the build you want to use. I personally have used the LineageOS 20.0 A13 GSIs by @AndyYan , they're quite good. However, many of them do not have GApps preloaded so you'll need to do that. Regardless of what GSI you decide to install, you'll have an .img file which is the system image; you can then use the instructions in my guide to install it.
Thanks for your input. I tried your guide but I think that I'm using the wrong combination of .img and GAPPS files. I ended up with a hung very dark blue blank screen after boot. I'm going to try AndyYan's .img file but I'm unsure which Open GAPPS goes with Lineage 20, is it 11?
REMOVED
I had the message in bootloader "KG STATUS - LOCKED" so I re-locked the bootloader. Re-unlocked it and had the message KG STATUS - CHECKING. so far, so good. Tried to install TWRP file "twrp-3.7.0_9-0-a20e.img" Odin reported success but now in download mode get the message "Recovery: Error validating footer.....(Rest of message hidden under camera lens)...." BVMETAA202FXXU4CVK1, 59051 788A. Phone is stuck in download mode and will only reboot to download mode with the above error message. Will wait for battery discharge and then reinstall stock OS and wait for your input please.
[email protected] said:
I had the message in bootloader "KG STATUS - LOCKED" so I re-locked the bootloader. Re-unlocked it and had the message KG STATUS - CHECKING. so far, so good. Tried to install TWRP file "twrp-3.7.0_9-0-a20e.img" Odin reported success but now in download mode get the message "Recovery: Error validating footer.....(Rest of message hidden under camera lens)...." BVMETAA202FXXU4CVK1, 59051 788A. Phone is stuck in download mode and will only reboot to download mode with the above error message. Will wait for battery discharge and then reinstall stock OS and wait for your input please.
Click to expand...
Click to collapse
you installed wrong twrp
deleted
CamiloSaenz said:
This is nat related to the main matter... but.
I have a problem, recently I installed stock rom on my J6+, tried to flash TWRP, but cant, it said: KG STATUS: PRENORMAL ..-.. so, I made a format factory, format cache using the stock recovery, but then the KG STATUS changed, from Prenormal to: CHECKING
it dont allow me to flash anything but Stock ROM.. Do you know how can I change that? ... from the KG STATUS: Checking .. to KG STATUS: NORMAL
Click to expand...
Click to collapse
Boot into Android, connect to the Internet, enable Developer Options, check for the presence of the OEM Unlocking toggle. It should be visible but grayed out. You may have to force a check for firmware update in system settings.
Once OEM Unlocking is visible again, KG STATUS should be "COMPLETED", and you'll be able to flash custom images.
deleted
CamiloSaenz said:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-J610G
CURRENT BINARY: Samsung Official
FRP LOCK: OFF
OEM LOCK: OFF
KG STATUS: Checking
WARRANTY VOID: 0x1 (0x20c)
QUALCOMM SECUREBOOT: ENABLED (CSB)
RP SWREP: S1, T1, R1, A7, P1
RP SWREP: K 7, S 7
SECURE DOWNLOAD: ENABLE
DID: 0056c0f88Bc9
DOWNLOAD MODE !!
this is the current state.
Click to expand...
Click to collapse
Did you follow the instructions I gave you?
deleted
CamiloSaenz said:
yes I did, but does not work, KB STATUS: Checking
Yesterday I locked the OEM, nothing changed, then Unlocked OEM, the status is the same, ... having an active google account it shows FRP: OFF ... it doesnt matter, having or not a google account, it shos FRP: OFF
Click to expand...
Click to collapse
Leave OEM Unlocking on and don't change it.
Try this