Database Develop

[HOW-TO] ROOT/MODEM/FIRMWARE flash GT-I9295 using Download Mode, Recovery Mode

Phone: S4 Active GT-I9295
This is a collection of knowledge from xda-forum and own experience. Consider information found here as advise to avoid possible issues.
Please give feedback if material presented here helped or need correction. Contributors are welcome and due credit will be placed.
Remember to give credit when you copy advice from my thread.
Qcomm based phones i9295 and i9505 need same procedure when flashing. Files to flash is not interchangeable between the phones. Method to flash any item SUCCESSFULLY in Download Mode using Odin is described in this thread.
Some guides may tell you to flash firmware, baseband or modems twice using Odin in Download Mode to "make it stick" or say there is an "unknown bug somewhere". People usually loose IMEI and/or WiFi because they have entered download mode using wrong method and started flash of modem, non-hlos.bin or firmware.
The reason the flashed file won't stick on first attempt is that you have entered download mode by software reboot menu or holding Vol- while rebooting. Don't enter download mode when phone is rebooting.
Remember that you are responsible for every action you do to your phone.
If you don't have Samsung Kies the Samsung USB drivers is reccomended to install before running Odin and connecting PC-USB-PHONE.
Never run Odin to flash phone in Download Mode on the same PC where Samsung Kies is running. Odin and Kies will fight to gain control of USB connected device. Close all running Kies processes in Task Manager or uninstall Kies.
Some Windows installations need to run a Fix It from Microsoft Support to properly detect Samsung phone even after installation of Samsung Android USB driver.
Always connect phone directly to 5V-powered PC USB port - never USB hub.
Use original USB cable or make sure it is in good condition. Cable working for charging can have broken wire making it unusable for communication and file transfer.
GSM modem (modem.bin, *.tar, *.tar.md5) or LTE modem (NON-HLOS.bin, *.tar, *.tar.md5 ) can be flashed using Odin form PHONE/CP without repeating the flash twice.
Download Mode
Why
To flash (change/update) phone recovery, firmware, kernel, bootloader or modem using computer software Odin or Heimdall with phone connected by USB to computer.
How
Completely Power Off , wait at least 5 seconds after vibration or led stop blinking. Now you can enter download mode:
Power + VolDown buttons pressed
Release Power after vibration
Release VolDown when screen turn on
VolUp to confirm
Start Odin as Administrator
Connect USB cable PC-PHONE and make sure ID:COM confirm "Added" phone in Odin
Remark: Home button is NOT USED
Recovery Mode
Why
To flash (change/update) phone custom recovery, custom ROM, SuperSU or kernel by install zip from Custom recovery like TWRP or CWM.
How
Can be entered from the phone reboot menu OR from phone in powered off state:
Power + VolUp buttons pressed
Release Power after vibration
Release VolUp when you see blue text RECOVERY BOOTING.... in upper left corner of screen
Remark: Home button is NOT USED
ROOT
When you have stock recovery and plan to flash a custom recovery like TWRP or CWM (ClockWorkMod) the first time, you need to enter Recovery Mode immediately on first boot after Odin flash custom recovery.
The steps are independent of the stock Android version currently installed on your phone, this is how it's done for both Kitkat 4.4x and Lolipop 5.0x
The steps are also independent of which custom recovery (CWM-based or TWRP)
you prefer.
Advice to use the latest version custom recovery built for i9295 - linked in post #3
WARNING: The CWM built by LeJay back in 2013 on CM10.2 source (=CWM-Recovery-gt-i9295_v1-2.tar.md5) do not support external SD card or Nandroid backup/restore for Samsung Kitkat 4.4x or Lolipop 5.0.x. That recovery is outdated.
Make sure you have minimum 60% battery capasity
1st step - Install custom recovery
Copy SuperSU(latest).zip to phone storage
Power off, Boot phone to Download Mode
Start Odin with AutoReboot disabled, Re-Partition disabled
Connect USB cable PC-PHONE
Odin flash (CUSTOM-RECOVERY).TAR.MD5 as PDA
Disconnect USB cable
Remove phone battery - wait - insert battery
Enter Recovery Mode
2nd step - Install SuperSU from custom recovery, TWRP or CWM
TWRP touch "install" / CWM go to "install zip" by VOLUME buttons
TWRP touch-select / CWM select by pressing POWER button
Browse to and select SuperSU(latest).zip
Reboot
Download files from links in post #3:
(USB drivers, Odin, Custom recovery, SuperSU)

If you wonder what is baseband, baseband version, GSM modem, LTE/4G modem, and find time to read and courtesy to suppress the urge to ask same question recently explained -
... here is a treat for you:
MODEM.BIN and NON-HLOS.BIN HOW-TO flash using Odin
Alternative solution
Thanks @Formhault
What version of modem.bin can you flash?
Thanks @hawkerpaul
Make sure you have non-hlos.bin and bootloader version match:
http://forum.xda-developers.com/showthread.php?p=62994941
Samsung lettercode decoded for firmware/bootloader/modem
Example: I9295XXUCNE4
I9295 = phone model
XXU = baseband (XXU is Global, valid almost everywhere, any country regardless of carrier)
C = baseband build version
NE4 = datecode
Datecode
N = year = 2014 (14th letter of alphabet)
E = month of year (May in this case, 5th letter of the alphabet)
A = build # of that month (10th for, "A", as they start 1-9, then letters)
NE4 = 2014, May, Build 4
NE5 = 2014, May, Build 5
NH2 = 2014, Aug, Build 2
Identify your bootloader
Make sure you have LTE/ audio/ network certificate (=NON-HLOS.bin) version matching your bootloader (=ABOOT, SBL*, TZ) version. Reason explained in 1st post.
NON-HLOS.bin inside the apnhlos partition /firmware and the bootloader is never updated or downgraded by AOSP/CM ROMs or custom recovery flashing. Some customized stock ROMs may mess with the relationship between bootloader and NON-HLOS.bin. Or you have messed up because you wanted to have the latest modem and flashed a *N-- version NON-HLOS.bin on your *M-- version bootloader. This will have bad impact on sound and WiFi functionality leading to you can not activate WiFi.
Earlier versions of PhilZ CWM recovery had an option to wipe partitions
/firmware
(LTE, audio, network certificate, NON-HLOS.bin)
/firmware-mdm
(GSM-modem, MODEM.BIN)
This wipe was not needed because flashing to this partitions overwrite the existing content. Wiping the same partitions without flashing modem or complete stock ROM can render telephone, audio and network functionality useless.
The partitions /firmware and /firmware-mdm is removed from later PhilZ Recovery fstab.
Ref. PhilZ Recovery 6.23.9 change log http://forum.xda-developers.com/showpost.php?p=51389599&postcount=3520
Identify bootloader and select corresponding NON-HLOS.bin
NON-HLOS.bin is also called LTE-modem or WiFi-fix when discussed in xda-forum
1. Connect phone from ADB or use Terminal app and do this command:
Code:
getprop ro.bootloader
( ADB =Android Debug Bridge )
The output is Samsung lettercode and will tell what version of bootloader you currently have.
2. Select version of NON-HLOS.bin to flash according to 3rd last letter of Samsung lettercode bootloader:
BOOTLOADER 3rd last letter = NON-HLOS.bin 3rd last letter
I9295xxxxMxx = I9295xxxxMxx JellyBean 4.2.x
I9295xxxxNxx = I9295xxxxNxx KitKat 4.4.x
I9295xxxxOxx = I9295xxxxOxx Lollipop 5.0.x​
Not known exactly what's first version of i9295 firmware/bootloader that has Knox feature. Strong indications nominate all KitKat 4.4.x to have it on QualComm based phones. And GT-I9295 has QualComm chipset.
Updating bootloader to a higher version should not trigger Knox 0x1, but downgrade Knox featured bootloader may cause that.
Status of KNOX is shown in Download Mode upper left corner of screen.
This S4 thread discuss the limitation introduced by Knox:
http://forum.xda-developers.com/showthread.php?p=45666586

Samsung firmware
Sammobile and Samdownloads links removed for violating XDA rules 11 & 13
7-zip v9.3x beta
- Bootloader, modem.bin, NON-HLOS.bin can be extracted from firmware tar package using 7-zip. The extracted files can be flashed one-by-one using Odin or Heimdall.
Heimdall
- a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung mobile devices.
Odin v3.07
- Samsung (leaked) tool to flash firmware files to phone from Windows.
- default setup with unticked Auto Reboot, best setting for recovery 1st time flash.
- faster summary of flash results, 10 seconds.
(attachment)
Samsung USB Drivers for Mobile Phones (v1.5.45.0)
MultiROM TWRP
- custom recovery
[quote name="O-T" post=57277967]Interested in replace CWM 6.0.5.0 with TWRP. Not sure if ready to use the rest of mulirom setup yet. Is TWRP stand-alone capable of replacing CWM in a single ROM setup?[/QUOTE]
Developer spegelius reply:
"Yes, TWRP works without MultiROM. There are few checkboxes, like Inject MultiROM that need to be disabled when installing roms for example, but basic stuff works without multirom."
CF-Auto-Root
- install and enable SuperSU on your system, so apps can gain root access.
- Odin included and pre-setup to flash root to phone from Windows.
What's installed
SuperSU binary and APK
Stock recovery (note that any other recovery you may have installed will be overwritten !)​SuperSU
- install and enable SuperSU on your system, so apps can gain root access.
- SuperSU flashable zip is installed using custom recovery (like TWRP)
What's installed
SuperSU binary and APK​
Credits
@spegelius MultiROM TWRP
@Chainfire CF-Auto-root, SuperSU
Bevare the Thanks Button under each post - it's there for you to show you are happy to receive help

Dear friend,
I read carefully all the tread but was unable to determine weather my device can be TWRP recovered via Odin or not (multirom_twrp_20150215_000001.zip - from your repository).
I feel a bit dumb to ask but would really appreciate some help.
GT-I9295
4.4.2
I9295XXUCNI1
Default KARNEL
Already ROOTED - CF-Auto-Root-jactivelte-jactiveltexx-gti9295.zip
Thanks in advance and sorry for bothering you

Thomas.A.A said:
Dear friend,
I read carefully all the tread but was unable to determine weather my device can be TWRP recovered via Odin or not (multirom_twrp_20150215_000001.zip - from your repository).
I feel a bit dumb to ask but would really appreciate some help.
GT-I9295
4.4.2
I9295XXUCNI1
Default KARNEL
Already ROOTED - CF-Auto-Root-jactivelte-jactiveltexx-gti9295.zip
Thanks in advance and sorry for bothering you
Click to expand...
Click to collapse
If you're still running Samsung default recovery start to flash multirom_twrp_20150215_000001.tar.md5 in Download Mode using Odin. Zip packed twrp recovery has built in update script made for updating from custom recovery only. You can use zip packed to update or change only after custom CWM based or TWRP recovery is installed in phone. Zip file can then be copied to phone internal storage or SD card and run from custom recovery to update when you want to update/downgrade or change to a different recovery.
Custom recovery doesn't run tar or tar.md5 files. They are made for Odin or Heimdall flashing.

O-T said:
If you're still running Samsung default recovery start to flash multirom_twrp_20150215_000001.tar.md5 in Download Mode using Odin.
Click to expand...
Click to collapse
Thanks for the quick reply (really appreciated!)
Though... I am now even more confused X*X*X!!
Still I will follow your lead:
1. I will Flash multirom_twrp_20150215_000001.tar.md5 in Download Mode using Odin
2. I will do NOT Flash multirom_twrp_20150215_000001.zip in Download Mode using Odin, because...
O-T said:
Zip packed twrp recovery has built in update script made for updating from custom recovery only.
Click to expand...
Click to collapse
and also because...
Custom recovery doesn't run tar or tar.md5 files. They are made for Odin or Heimdall flashing.
Click to expand...
Click to collapse
3. Afterwards, I can freely do the hack I want with ZIP packed, since:
You can use zip packed to update or change only after custom CWM based or TWRP recovery is installed in phone. Zip file can then be copied to phone internal storage or SD card and run from custom recovery to update when you want to update/downgrade or change to a different recovery.
Click to expand...
Click to collapse
Sorry I am so dumb.... Thanks for posting
Really appreciated

1 yes
2 yes
3 yes. Perhaps update root to latest SuperSU 2.46 by recovery flashing.
http://forum.xda-developers.com/showthread.php?p=23427715
All right. Read some posts about TWRP in that thread to learn how to use recovery.

Is it possible to downgrade from 5.0.1 bootloader to 4.2.2?

tasken said:
Is it possible to downgrade from 5.0.1 bootloader to 4.2.2?
Click to expand...
Click to collapse
The link in 1st post to investigation by Chainfire is for S4 i9505 from 442 to 422.
Did you read that?

I was able to do it through odin without breaking knox

tasken said:
I was able to do it through odin without breaking knox
Click to expand...
Click to collapse
If you have been recovery flashing CM12 5.0.1 lately the bootloader is never touched or updated to any version.
Are you sure you had OB4 lollipop 5.0.1 bootloader?

Update
Add confirm step in download mode
Rearrange paragraph in OP

Update
add SuperSU and TWRP to recovery Why

Update:
- added link to latest Samsung USB drivers
- tidy up post #3 with inline links
Bevare the Thanks Button under each post - it's there for you to show you are happy to receive help [emoji106]

Update :
- rooting steps in post #1
The steps are independent of the stock Android version currently installed on your phone, this is working for both Kitkat and Lolipop.
The steps are also independent of which custom recovery (CWM-based or TWRP)
you prefer. Advice to use the latest version built for i9295 - linked in post #3.

CWM and TWRP steps added to post #1
to Root ANY version of Android

MODEM.BIN and NON-HLOS.BIN
- rewrite how to flash correct version

Hi.
I have a i9295 and I experience problems with log-offs or sim disconnects while wifi is working well.
Will a reflash of modem.bin help?
If yes: where can i get the file required for odin of recovery flash?
Thanks in advance

augek said:
Hi.
I have a i9295 and I experience problems with log-offs or sim disconnects while wifi is working well.
Will a reflash of modem.bin help?
If yes: where can i get the file required for odin of recovery flash?
Thanks in advance
Click to expand...
Click to collapse
Shouldn't be needed if you did this http://forum.xda-developers.com/showthread.php?p=61418876
correctly.
You can do a factory reset.
Read post 1-3 slowly if you need modem.bin, non-hlos.bin or bootloader of right version for you.
ThumbsUp button under every post is free to use in case you're in the mood to show appreciation.

Hi.
I did read and still am not sure about it.
I've done factory reset with every flash but still the problem persists.
Tried a different sim, still on joy.
From the thread linked i can not see where to find the modem for lollipop.
When the mobile disconnects phono tells me ihre some 14 - 16 asu. So service is available.
Drives me nuts.

Won't boot

Went to recovery, tried wiping cache, after about an hour I thought it was just frozen and not doing anything, so I restarted the phone, then went back into recovery and factory reset. Now the M logo appears for a few seconds, then disappears, but the screen buttons are unresponsive. At this point, the only thing I can do is hold the power button and the M screen will come back up, OR I can get into fastboot and everything acts normal until I try rebooting. I've wiped cache and factory reset several more times and the same problem keeps persisting.
Any tips?
Thanx

VooDooCC said:
Went to recovery, tried wiping cache, after about an hour I thought it was just frozen and not doing anything, so I restarted the phone, then went back into recovery and factory reset. Now the M logo appears for a few seconds, then disappears, but the screen buttons are unresponsive. At this point, the only thing I can do is hold the power button and the M screen will come back up, OR I can get into fastboot and everything acts normal until I try rebooting. I've wiped cache and factory reset several more times and the same problem keeps persisting.
Any tips?
Thanx
Click to expand...
Click to collapse
It's entirely possible you are having some kind of hardware failure, but as we can't help you fix that let's focus on software for now.
Is your bootloader unlocked and do you have TWRP recovery? If you have TWRP, have you tried to restore any backups of your system?
Have you tried reflashing firmware, either lastest stock via ADB or custom ROM? (choice depending on whether your bootloader is unlocked or not)

bootloader is locked, everything is stock.

VooDooCC said:
bootloader is locked, everything is stock.
Click to expand...
Click to collapse
do you have TWRP installed? If so, do you have a backup you can restore?
If not, then reflash latest firmware (either via TWRP or via ADB).

ChazzMatt said:
do you have TWRP installed? If so, do you have a backup you can restore?
If not, then reflash latest firmware (either via TWRP or via ADB).
Click to expand...
Click to collapse
TWRP is not installed. Is there a guide somewhere how to reflash? Everything I have found is for a normally working phone.

VooDooCC said:
TWRP is not installed. Is there a guide somewhere how to reflash? Everything I have found is for a normally working phone.
Click to expand...
Click to collapse
See section 0 (zero) of this thread.
[GUIDE] How to unlock your bootloader, install TWRP and gain root access
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
realbbb said:
Flash with RSD or FASTBOOT.
BUILD REQUEST INFO:
SW Version: quark_verizon-user 6.0.1 MCG24.251-5-5 5 release-keysMDM9625_41.51.07.22.04R
MBM Version: 70.96
Modem Version: MDM9625_41.51.07.22.04R
FSG Version: UNKNOWN
Build Fingerprint: motorola/quark_verizon/quark:6.0.1/MCG24.251-5-5/5:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 24.91.5.quark_verizon.verizon.en.US
Model number: DROID TURBO
Android Version: 6.0.1
Baseband Version: MDM9625_41.51.07.22.04R
Build Number: MCG24.251-5-5
Build Date: Mon Jan 30 08:40:14 CST 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_b_default_v1.0.nvm
Regulatory Info (eLabel): None
Blur Version: Blur_Version.24.91.5.quark_verizon.verizon.en.US
Version when read from CPV: quark_verizon-user 6.0.1 MCG24.251-5-5 5 release-keys
QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip
Download Link : https://mega.nz/#!dd4wXYiI!sRgo3aathlCDcg4YqBLxrRrd2ZK4u8BbnvHSCDoP7hE
SHA1 hash : 723f1d2b40f21343ecd87ebf4bb36c0f921e01e3
Recovery Only
Download Link : https://mega.nz/#!EFZFRKoC!G62yatqnQMJI4lEFZPlYHtMEIvUCgLYBjFE-p5uZ4Tw
SHA1 hash : 670b3830bc990f78a223273a99b42b9b9d5c74c8
Radio Only
Download Link : https://mega.nz/#!pJIFGCpS!CbyB1S3kDUKvh81-TjcDB-f_TKaP1XFSiN7JISwDU0o
SHA1 hash : 4eaea2d55f5fab1048b78598500d47c4fd3ca063
BBB
Threw Nead
Click to expand...
Click to collapse

Edit 1: Read faster than I was understanding. Trying it now.
Edit 2: Didn't understand how to flash the one you linked, so I used the one supplied in the guide and flashed everything. Still getting the same issue though.

VooDooCC said:
bootloader is locked, everything is stock.
Click to expand...
Click to collapse
whoa, I somehow mis-read this. Your bootloader is locked? Do you want to unlock your bootloader? If so, if you do not have the latest firmware, then don't flash the latest firmware. Ignore my last post.
However, if you are already on the latest firmware, then you can't unlock your bootloader anyway, so you might as well re-flash that firmware to fix whatever is corrupted.
---------- Post added at 02:56 PM ---------- Previous post was at 02:54 PM ----------
VooDooCC said:
Read faster than I was understanding. Trying it now.
Click to expand...
Click to collapse
I read too fast also. I thought your bootloader was UNlocked and you were still stock.
What firmware were you on before you had this trouble?
If you were on the very latest already, then you can't flash that firmware in that thread -- because you can't downgrade with a locked bootloader. You can only flash same version or higher.

I assume I was on the latest, at least I know I didn't have any pending OTA's
Sorry for being a bit ignorant on this, I told myself with this one I was just going to leave everything alone and not unlock or do anything like I did on all my others.

VooDooCC said:
I assume I was on the latest, at least I know I didn't have any pending OTA's
Sorry for being a bit ignorant on this, I told myself with this one I was just going to leave everything alone and not unlock or do anything like I did on all my others.
Click to expand...
Click to collapse
OK, let's assume you were on the latest already.
With these instructions below, on step 4 instead of the link he provides you would use the link I provided (which is the very latest firmware). @TheSt33v's goal for this thread is to unlock the bootloader -- and these instructions were originally intended to get users with older firmware to upgrade and install the very last version firmware that could be unlocked with Sunshine. We are re-purposing the instructions to get you to re-flash the latest firmware on your phone, hoping that will fix any corruption issue.
TheSt33v said:
Section 0: Installing Firmware Version MCG24.251-5 (instead you would be installing Official Stock Firmware 6.0.1 MCG24.251-5-5. Note the extra "5" on the end. It's the very latest stock firmware, but cannot be unlocked as of this date by Sunshine.)
1. Go to Settings -> About phone -> Build number. If it says SU4TL-44, SU4TL-49 or MCG24.251-5, skip to section 1 of this guide. If it says MCG24.251-5-5, you are probably out of luck. This guide will not work for you. If it says anything else, continue reading.
Flashing MCG24.251-5 using this method will erase all of your data. Back up any important files/information before proceeding.
2. Download and install Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790.
3. Download and install the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
4. Download the MCG24.251-5 firmware package from here: https://www.androidfilehost.com/?fid=889764386195901169
(instead download THIS VERSION: Official Stock Firmware 6.0.1 MCG24.251-5-5)
5. Extract the contents of the MCG24.251-5 firmware package to the installation directory of Minimal ADB and Fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot on any 64-bit installation of Windows). (INSTEAD you would extract the firmware version I linked to.)
6. Power off your phone.
7. Hold down the volume down button and power on your phone. Release the volume down button when you see that the phone has booted into bootloader mode. You'll see a dead green android.
8. Plug the phone into your computer.
9. Open the Minimal ADB and Fastboot shortcut on your desktop. This will open a command prompt.
10. Type "fastboot devices" and press enter. If it displays your device's serial number, you're ready to go. If it displays nothing, your computer is not recognizing your device properly.
11. Navigate to the installation directory of Minimal ADB and Fastboot and double click on FlashAll.bat. This will flash MCG24.251-5 to your device and erase all of your data. (This will instead install MCG24.251-5-5 if you downloaded that version, but yes it will erase all your data.)
12. Use the power button to select Start in the bootloader menu to boot normally.
13. Set up your phone at least to the point where you can install apps if you want to.
Click to expand...
Click to collapse

ChazzMatt said:
OK, let's assume you were on the latest already.
With these instructions below, on step 4 instead of the link he provides you would use the link I provided (which is the very latest firmware). @TheSt33v's goal for this thread is to unlock the bootloader -- and these instructions were originally intended to get users with older firmware to upgrade and install the very last version firmware that could be unlocked with Sunshine. We are re-purposing the instructions to get you to re-flash the latest firmware on your phone, hoping that will fix any corruption issue.
Click to expand...
Click to collapse
The blue link you provided in that post doesn't work. Assuming it's the same that you provided a few posts earlier, there is no flashall.bat file.

VooDooCC said:
The blue link you provided in that post doesn't work. Assuming it's the same that you provided a few posts earlier, there is no flashall.bat file.
Click to expand...
Click to collapse
I fixed the download link, so should work now.
As for the bat.file, I don't know.
I searched and found some more download versions, like this:
https://easy-firmware.com/index.php?a=browse&b=file-info&id=80611

Sweet Sassafrass, it works! I simply copied the .bat file from the -5 zip to the -5-5 (newest FW) took almost 5 minutes on the Droid splash screen, but it's alive. Thank you so much @ChazzMatt for all your help.

Is there anyway to flash TWRP as official binary? Gets blocked due to OEM lock.

Is there anyway to flash TWRP as official binary? Gets blocked due to OEM lock
I messed up my Note8 SM-N950F, locked OEM flashed with odin to stock now in bootloop. Says EFS cant be mounted. DM-Verity error. I dont know what to do. :crying:

mohiminul said:
Is there anyway to flash TWRP as official binary? Gets blocked due to OEM lock
I messed up my Note8 SM-N950F, locked OEM flashed with odin to stock now in bootloop. Says EFS cant be mounted. DM-Verity error. I dont know what to do. :crying:
Click to expand...
Click to collapse
No you cant flash twrp as official binary. Can you get back to download mode and flash stock firmware?

sefrcoko said:
No you cant flash twrp as official binary. Can you get back to download mode and flash stock firmware?
Click to expand...
Click to collapse
Yes, but as soon as flashing is finished the device reboots to recovery and shows error failed to mount efs nd dm-verity verification failed. Downloaded firmware with Samfirm tool.

mohiminul said:
Yes, but as soon as flashing is finished the device reboots to recovery and shows error failed to mount efs nd dm-verity verification failed. Downloaded firmware with Samfirm tool.
Click to expand...
Click to collapse
Ok I see. Hmm not sure...I googled and found this thread that has a few solutions (Kies, Smart Switch, etc.) that seem to resolve the issue. If someone knows for sure they can chime in, but in the meantime I would start here (even though it's for Note 4...might still work, or at least point you in the right direction).
https://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531

This thread may help.
https://forum.xda-developers.com/ga...-hard-bricked-note-8-sm-t3735009/post75195355

TWRP Backup for A600FN

Hello,
I bricked my phone and can't restore it through Odin because it gives me an error: "sw rev check fail device 3 binary 1". I have installed TWRP on my phone though. I want to try to restore an TWRP backup, I made one but then formatted my SD-Card
Has someone got a backup that I can restore and it then works fine? I just want to have an working OS because I want to flash the Phoenix Kernel on my device. (An older version because it isn't working with the December Patch). Can someone help me please?
- Jxnas

nxtJxnas said:
Hello,
I bricked my phone and can't restore it through Odin because it gives me an error: "sw rev check fail device 3 binary 1". I have installed TWRP on my phone though. I want to try to restore an TWRP backup, I made one but then formatted my SD-Card
Has someone got a backup that I can restore and it then works fine? I just want to have an working OS because I want to flash the Phoenix Kernel on my device. (An older version because it isn't working with the December Patch). Can someone help me please?
- Jxnas
Click to expand...
Click to collapse
i don't think if anyone will share their TWRP backup.
regarding your error, you must flash U3 firmware. maybe you flash U1 firmware but your phone already on U3. Flash latest...

an-_-dro said:
i don't think if anyone will share their TWRP backup.
regarding your error, you must flash U3 firmware. maybe you flash U1 firmware but your phone already on U3. Flash latest...
Click to expand...
Click to collapse
Amazing! Now that I downloaded the "U3" firmware (i think i did) I get another error: "sw rev. check fail(bootloader) device: 3, binary: 1" what does that mean?? Is now something with the Bootloader wrong?
//EDIT
Wrong, flashed the wrong firmware. Now it works. Thanks I am just stupid.

Cant flash TWRP Recovery

Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.

VortexHD said:
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
Click to expand...
Click to collapse
ARE YOU EXYNOS OR SNAPDRAGON ?? Below guide is for EXYNOS!!
Did you follow this guide --> https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143 ??
And did you do step 3 ? 3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card ??i haven't rooted my Note 9 yet but i think that's where you messed up!

Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f

rana14301 said:
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
Click to expand...
Click to collapse
read dr ketans guide in the general discussion thread.