Database Info

[Completed] Note 4 recovery capped

I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0

I figured it out
planb234 said:
I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
Click to expand...
Click to collapse
I fianlly figured out the deal with TWRP not flashing.
The change between file systems is what TWRP won't flash.
To flash into the new, the old, or back up property check the file type.
Ext 2, Ext 4, F2FS, etc ...
To get recovery to load install from odin with auto boot disabled, remove battery, than vol + - menu and power.
the steps below..
1. Power off (complete) boot to download.
2. Load Odin, uncheck auto reboot, PDA TWRP. after it installs pull battery to exit.
3. Boot to recovery - wipe- advanced wipe -Repairor Change File System - Check System (go thruough each)
4. Repair and change each to the file type you want to flash
5. repair and or change the files for the zip you are going to flash
6. you have done all the rest before ....

Issue resolved, thread closed, thanks.

S7 in recovery boot-loop

Hi,
I just "slightly" bricked my S7 (SM-G930F), and I hope someone can help me. My first S7 (which had Superman-Rom installed) had a burnt-out USB port, so I got a brand new replacement. I made a TWRP backup from the old one and installed that on the new one, but I think I made 1 (or even 2) critical mistakes here: I installed TWRP with ODIN on the phone directly out of the box without starting it once, so I never activated the OEM unlock. Furthermore I restored the backup including the EFS partition. The first start-up went fine, just I couldn't unlock the screen (password not valid). After restarting the phone I got the message "Custom binary locked by FRP lock". Using Smart Switch's device initialization, I could get the phone into download mode again and flashed the stock rom (G930FXXU1DQEI with VD2 carrier) via ODIN. But that got me nowhere, after showing "Installing system update" I just got a screen with "No command". Then the phone rebooted again and went directly to the recovery, showing "Successfully verify for dmverity hash tree". Any attempt to restart the phone just shows the Samsung boot logo two times and then I'm back in recovery, where it then shows "No Support SINGLE-SKU, Supported API: 3, dm-verity error, failed code: 0x02". Trying to install TWRP again just triggers FRP lock. I tried both Smart Switch and ODIN several times in different orders, but nothing works.
Here the timeline again:
1. TWRP-Backup old phone (Superman-Rom)
2. First start new phone directly to download mode, installing TWRP (no OEM unlock)
3. TWRP-Restore new phone, EFS included
4. Rom starts, lock screen password not valid
5. Restart
6. FRP lock
7. Smart Switch
8. Stock rom via ODIN
9. "No command"
10. Starting to recovery, dm-verity ok
11. Restart
12. Starting to recovery, dm-verity error
13. Restart
14. GOTO 12
15. ???
Another interesting thing is that at the first start into recovery after flashing the VD2 stock rom, I also get the message "# MANUAL MODE#, Appling Multi-CSC, Applied the CSC-code : DBT, Successfully applied multi-CSC". As I downloaded the VD2 rom, why is it setting the csc to DBT?
Anyone who can help me break the loop?

Yanai1701 said:
Hi,
I just "slightly" bricked my S7 (SM-G930F), and I hope someone can help me. My first S7 (which had Superman-Rom installed) had a burnt-out USB port, so I got a brand new replacement. I made a TWRP backup from the old one and installed that on the new one, but I think I made 1 (or even 2) critical mistakes here: I installed TWRP with ODIN on the phone directly out of the box without starting it once, so I never activated the OEM unlock. Furthermore I restored the backup including the EFS partition. The first start-up went fine, just I couldn't unlock the screen (password not valid). After restarting the phone I got the message "Custom binary locked by FRP lock". Using Smart Switch's device initialization, I could get the phone into download mode again and flashed the stock rom (G930FXXU1DQEI with VD2 carrier) via ODIN. But that got me nowhere, after showing "Installing system update" I just got a screen with "No command". Then the phone rebooted again and went directly to the recovery, showing "Successfully verify for dmverity hash tree". Any attempt to restart the phone just shows the Samsung boot logo two times and then I'm back in recovery, where it then shows "No Support SINGLE-SKU, Supported API: 3, dm-verity error, failed code: 0x02". Trying to install TWRP again just triggers FRP lock. I tried both Smart Switch and ODIN several times in different orders, but nothing works.
Here the timeline again:
1. TWRP-Backup old phone (Superman-Rom)
2. First start new phone directly to download mode, installing TWRP (no OEM unlock)
3. TWRP-Restore new phone, EFS included
4. Rom starts, lock screen password not valid
5. Restart
6. FRP lock
7. Smart Switch
8. Stock rom via ODIN
9. "No command"
10. Starting to recovery, dm-verity ok
11. Restart
12. Starting to recovery, dm-verity error
13. Restart
14. GOTO 12
15. ???
Another interesting thing is that at the first start into recovery after flashing the VD2 stock rom, I also get the message "# MANUAL MODE#, Appling Multi-CSC, Applied the CSC-code : DBT, Successfully applied multi-CSC". As I downloaded the VD2 rom, why is it setting the csc to DBT?
Anyone who can help me break the loop?
Click to expand...
Click to collapse
Hi
Main issue I see is:
Install EFS partition from one phone to the other.....lets hope you did not mess the IMEI , EFS are device specific.
OEM unlock maybe an issue but Odin flashing should solve it ( most of the times)
You said you flashed with ODin , what file you used CSC or home_csc? if you used CSC did you selected re partition?

MAX 404 said:
Install EFS partition from one phone to the other.....lets hope you did not mess the IMEI , EFS are device specific.
Click to expand...
Click to collapse
Is there a way to restore the original EFS partition? ODIN has the option to clear the EFS, but I could not find any information on what this does, only "stay away from it!!!!!".
MAX 404 said:
You said you flashed with ODin , what file you used CSC or home_csc? if you used CSC did you selected re partition?
Click to expand...
Click to collapse
I tried both, but mainly CSC to also do a factory reset, and I also tried to repartition. Only thing I still haven't tried is "Nand Erase All", because "stay away from it!!!!!"

Yanai1701 said:
Is there a way to restore the original EFS partition? ODIN has the option to clear the EFS, but I could not find any information on what this does, only "stay away from it!!!!!".
I tried both, but mainly CSC to also do a factory reset, and I also tried to repartition. Only thing I still haven't tried is "Nand Erase All", because "stay away from it!!!!!"
Click to expand...
Click to collapse
There are ways to restore the EFS , the question is do you have a copy of the original EFS??
Do not use option in Odin you do not know about.... re partition is known did you use it?
check this info regarding that

Yes, I already tried to repartition. And no, I don't have a backup of the original EFS, I accidentally restored it because I overlooked that is was checked in TWRP (or just checked everything that was there without really looking?).
Regarding Odin it's just sad that nobody seems to know what some of the options really do, maybe some combination could help me.

Yanai1701 said:
Yes, I already tried to repartition. And no, I don't have a backup of the original EFS, I accidentally restored it because I overlooked that is was checked in TWRP (or just checked everything that was there without really looking?).
Regarding Odin it's just sad that nobody seems to know what some of the options really do, maybe some combination could help me.
Click to expand...
Click to collapse
long shot but you could try this.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
or may have to take it to a service shop ( a good one) they have special boxes with special options to fix this kind of problems

Thanks for your help Max, but it seems I have to pick your last option and search for a service shop. I downloaded the latest available combination firmware, but after installing it the phone gets stuck on the boot screen with displaying "ASV TBL VER = 10; ASV TBL VER2 = 0; NAD: PASSED; NAD ACAT: FAILED; RPMB PROVISIONED" on the top. Reverting to the normal firmware brings me back to the recovery loop. The problem is also that there seems to be no combination firmware for Nougat, all the files are for Marshmallow. Not sure if this is the reason that the phone gets stuck, but I think it likely.

[SM-A310F] "Custom Binary Blocked By FRP Lock" after installing LOS

Hello all,
after spending two days trying to properly install LOS 15.1 on my Galaxy A3 (2016) (SM-A310F) and reading tons of forum posts, I'd like to describe my problem here (and hope to get the final hint). This is what I did:
Samsung stock image (Android 7.0) on the phone
Enable developer options in settings
Enable "OEM unlock" in developer options
Power down phone and enter download mode
Flash TWRP 3.2.3.0 with ODIN 3.13.1
Enter TWRP
Perform full wipe (data, system, cache, dalvik)
Copy LOS 15.1 image and Open GApps 8.1 ARM Stock to phone and install it with TWRP
Reboot phone
LOS comes up
Finalize all the Google stuff until reaching launcher
When now rebooting the phone I'm always ending up in "Custom Binary Blocked By FRP Lock" screen (only to fix by flashing Samsung stock ROM again.
Any idea highly appreciated!
BR, LostInTranslation

You need to double check OEM unlock before reboot. If it's not enabled or doesn't survive boot, you will get the error message that you mentioned.

I surely did check the OEM unlock setting before rebooting (I did the procedure above in the meantime four times - always with the same frustrating result). Any other hints?

LostInTranslation_ said:
Hello all,
after spending two days trying to properly install LOS 15.1 on my Galaxy A3 (2016) (SM-A310F) and reading tons of forum posts, I'd like to describe my problem here (and hope to get the final hint). This is what I did:
Samsung stock image (Android 7.0) on the phone
Enable developer options in settings
Enable "OEM unlock" in developer options
Power down phone and enter download mode
Flash TWRP 3.2.3.0 with ODIN 3.13.1
Enter TWRP
Perform full wipe (data, system, cache, dalvik)
Copy LOS 15.1 image and Open GApps 8.1 ARM Stock to phone and install it with TWRP
Reboot phone
LOS comes up
Finalize all the Google stuff until reaching launcher
When now rebooting the phone I'm always ending up in "Custom Binary Blocked By FRP Lock" screen (only to fix by flashing Samsung stock ROM again.
Any idea highly appreciated!
BR, LostInTranslation
Click to expand...
Click to collapse
You're getting the FRP error because you were still signed into your Google account in the stock ROM when you flashed TWRP and wiped the device.
If flashing the stock ROM fixes the FRP error but you still want TWRP and the ROM without it giving that error, the solution is not that complicated. You just need to boot into the stock ROM then go to system settings>accounts and remove your google account from the device. Once it is removed, reboot the device and let it boot back into the stock ROM, enable dev options, USB debugging and OEM unlock, then power it off. Now you can boot into download mode and flash TWRP, wipe the device and flash LOS and Gapps, you shouldn't get the error now.
Sent from my LGL84VL using Tapatalk

Droidriven said:
You're getting the FRP error because you were still signed into your Google account in the stock ROM when you flashed TWRP and wiped the device.
If flashing the stock ROM fixes the FRP error but you still want TWRP and the ROM without it giving that error, the solution is not that complicated. You just need to boot into the stock ROM then go to system settings>accounts and remove your google account from the device. Once it is removed, reboot the device and let it boot back into the stock ROM, enable dev options, USB debugging and OEM unlock, then power it off. Now you can boot into download mode and flash TWRP, wipe the device and flash LOS and Gapps, you shouldn't get the error now.
Click to expand...
Click to collapse
Your idea did sound very promising. So I did exactly what you suggested, unfortunately I'm again getting the "Blocked by FRP lock" after rebooting the LOS installation the first time after completing the google account stuff after first boot ...

One more question: does anybody know, if it makes a difference from which Samsung stock rom you start? My starting point always was Android 7.0, but also 6.0.1 or 5.11 are available at sammobile.

LostInTranslation_ said:
Your idea did sound very promising. So I did exactly what you suggested, unfortunately I'm again getting the "Blocked by FRP lock" after rebooting the LOS installation the first time after completing the google account stuff after first boot ...
Click to expand...
Click to collapse
But you aren't getting the FRP error when you flash back to the stock firmware?
I'm thinking that if you had done it the way I described from the beginning then you wouldn't have started the issue, but since you didn't do it that way the first time, it triggered FRP and now the device "remembers" it and won't let you past it.
There are ways to bypass FRP but it's against XDA rules to discuss how to do it because it could be used in the wrong way by the wrong people such as theives or someone trying to invade someone else's device.
Sent from my LGL84VL using Tapatalk

Correct. I do not get the FRP when flashing back to stock rom.
Thanks a lot for your help and all the best for 2019! Happy new year!

Thumbs up! Wish I had known this before. Had saved me a sleepless night!

GalaxyS8+ SM-G955F: BRICK (Only official released binaries are allowed to be flashed)

My device has been bricked after attempting to root the device using Odin. (Samsung Galaxy S8+)
The device is stuck in a bootloop with the following accompanying error message in red on the boot screen:
"Only official released binaries are allowed to be flashed"
Here is what happened:
I flashed TWRP using Prince Comsy Odin. (The only Odin that actually works on the s8+)
I then booted into the TWRP recovery.
I followed a set of instructions, clearing the Cash and wiping
I restarted once then booted back into TWRP using Vol-Up + Power + Bixby
I was preparing to install Magisk & "no-verity-opt-encrypt-5.1" according to instructions to complete the root.
After installing "no-verity-opt-encrypt-5.1" with TWRP, the system rebooted and i was stuck in a boot loop.
I then got the error message in the bootloop "Only official released binaries are allowed to be flashed"
Since then i have not been able to successfully re-flash TWRP.
I now cant enter TWRP recovery boot using Vol-Up + Power + Bixby anymore
The bootloop is about 2 seconds long and too short to enter TWRP recovery
I can enter download mode and thats all
I have gotten the EXACT official stock ROM for the galaxy s8+ in South Africa with the carrier, Vodacom. (XFV-G955FXXU4CRL4-20181228165540)
If i flash with any official Odin version, it either fails or doesnt do anything for hours...
If i flash any Official stock Rom using Prince Comsy Odin then i do get the whole process of flashing with stock firmware being successful with the result saying "PASS".
The phone then reboots and i am still stuck in the same loop saying "Only official released binaries are allowed to be flashed"
This is after countless times and hours and hours of reflashing successfully with Official stock rom
I still cant get back into TWRP to do any partitioning or formatting or anything
I really don't mind if i lose all of my data and format the phone but PLEASE can you help me get my phone to work again..."?
Do i need to wait 7 days for the official flash to work?
Is there a way to completely wipe my phone without requiring going into Recovery mode with TWRP? Since i cant get into that state anymore either because of the Error Knox block or because of the Loop being too fast.
Please, please, PLEASE....please help me get my phone to work again...
Sincerely,

I know that Odin 3.13.1 works on the s8+ G955F as I flashed the latest BTU stock yesterday so try that version. I had a similar problem with the G950F and after flashing the files I booted into recovery mode and did a data and cache wipe and the phone rebooted. Flashing a stock rom should have wiped TWRP from the phone.
Reflash your rom or a later one, don't forget to take the tick out of the auto reboot box in Odin, boot to recovery and wipe everything and hopefully you will be good to go. Rebooting on mine took around 35 mins or so when going back to stock.

GalaxyS8+ SM-G955F: BRICK (Only official released binaries are allowed to be flashed
I have the same problem with the model G955F binaries 4 I can not always rooted

le_pentium said:
I have the same problem with the model G955F binaries 4 I can not always rooted
Click to expand...
Click to collapse
same for me !someone asked me to delete the RMM to resolve the problem

le_pentium said:
I have the same problem with the model G955F binaries 4 I can not always rooted
Click to expand...
Click to collapse
My problem is fix

SM-T500 error when trying to root

I have a Samsung Galaxy A7 (T500) on fw BUJ1 which I rooted using magisk. It all seemed to work fine except a cpl of weeks later, there was an error of 'Enrolled knox guard prevent flashing factory binary(vbmeta)' in red, with a message of 'security error This phone has been flashed with unauthorised software & is locked'
I then re-flashed the stock version of this fw back on it and it boots as normal.
Problem is that I can no longer flash anything via odin. When I go to download mode and flash the patched fw, when the flashing process is almost complete it fails and the error 'enrolled knox guard prevent flashing factory binary(vbmeta) ' is displayed on the download mode screen and odin fails.
I also no longer have the oem unlock option in dev options, tho in download mode it does have 'oem lock off (u)' and 'kg status normal'.
How I can get past this error and how to get oem unlock to re-appear? (the date change stuff hasnt worked)