Samsung A5 "only official released binaries are allowed" when trying to install twrp - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

Samsung A5 "only official released binaries are allowed" when trying to install twrp
Short story: I'm trying to install a custom recovery(twrp) on my Samsung A5 phone (A520F) using ODIN and not matter what I've tried it always fails with "only official released binaries are allowed [recovery]" being displayed on my device's download screen. My phone has a stock Samsung ROM running 7.0 Android (however I tried 3 different roms from sammobile and none of them work, no matter the version of android or release date).
Long Story: The full story of my struggle is simply that I installed twrp, rooted and flashed a custom rom onto my phone (lineage os), however the sim card wasn't getting detected, after some searching I found that the solution was to install an official samsung rom with android 7.0 (as my phone had android 8.0 but lineage os only supports android 7.0 on my phone), and after flashing that rom, I can't install a custom recovery back on. Honestly I felt like I've tried everything, any ideas?

You can try flashing a magisk tar file to gain root access, this may not wok as it's not an "official binary". Once you have root access you can use the app flashify to flash twrp.

Related

sm-j5nltexx - v. sm-j5nlte

For a few days now i have being trying to install a customer ROM on my Samsung J5, EVERY ROM i have downloaded has failed with errors stating that the ROM is for J5nlte NOT for j5nltexx even if the file name has been relating to j5nltexx.
I have tried to change/remove the assert line in the install package with no success.
has anybody got/or can recommend a ROM that WILL work with samsung J5 (j5nltexx) - I Currently have a phone that will not boot into a ROM, but will happily boot into TWRP 3.1.1-0
***Update***
The CM13 firmware installed and initially booted, but then went into a boot loop at "optimising apps", still unable to successfully install a custom ROM of any sort, tried Skies and ASUX both didn't boot, even with an Aroma aware TWRP install (confirmed by attempting to install CM13)
Since rebuilding with a "greek" factory ROM, my phone is now showing as sm-j5lte anymore advise will be well recieved
Thanks in Advance
PB
pdjbarber said:
For a few days now i have being trying to install a customer ROM on my Samsung J5, EVERY ROM i have downloaded has failed with errors stating that the ROM is for J5nlte NOT for j5nltexx even if the file name has been relating to j5nltexx.
I have tried to change/remove the assert line in the install package with no success.
has anybody got/or can recommend a ROM that WILL work with samsung J5 (j5nltexx) - I Currently have a phone that will not boot into a ROM, but will happily boot into TWRP 3.1.1-0
Thanks in Advance
PB
Click to expand...
Click to collapse
first install a aroma supported recovery then install ASUX or Skies ROM i should boot if it dosent let me me know with the error
I have managed to get a booting phone, using an old Samsung Factory ROM (5.1.1), re-rooted using CF-Auto-Root. Re-installed TWRP (this time with Aroma support) from @Zonic here To be able to install CyanogenMod 13.0 for Galaxy J5 Here do i need to Marshmallow (6.0.1) BEFORE i attempt a firmware upgrade?
Thanks

[Question]Only official released binaries are allowed to be flashed

Hi everyone,
I have had an S8 for almost a year now and its currently on android oreo with the June security patch.
Yesterday I wanted to install a custom ROM(RenovateICE) but first, I installed TWRP and wiped my phone (in TWRP). The phone rebooted and brought the configurations and all those things which I quickly did.
I wanted to restart the phone into recovery so that I can install the ROM, but I couldn't. It keeps bringing the boot step(Galaxy S8 powered by Android) and on top in red letters it says 'only official released binaries are allowed to be flashed'.
someone please help me recover my phone:
-i have tried installing an official ROM, but it says 'SW REV. CHECK FAIL(CM) DEVICE: 2, BINARY : 1'
someone please help me out.....
man your are trying to flash old bootloader .it wont work download latest firmware and flash

Need Help Flashing Lineage 16

I really try to do stuff on my own without having to make other people repeat themselves a million times but this process is just so complicated and confusing that it's giving me a headache.
My goal: Be able to boot up LineageOS 16.
Code:
httpsforum.xda-developers.comnote-4snapdragon-devrom-lineageos-16-0-t3900807
It says it requires MM firmware and TWRP 3.2 or higher.
I have the retail 900V Note 4.
So far I have managed to downgrade to 5.1.1 and unlock the bootloader. (It says MODE: Developer)
From there I was able to install TWRP 3.0.2.
But now what?
Right now I have a phone that won't boot because there is no OS on it.
1. I can't get Odin to flash any other TWRP besides the 3.0.2 version. Odin just freezes halfway through and never completes. I'm assuming this might be because I'm not on an unlocked MM build yet. Currently still on LP.
2. I'm unsure how to get root back once I upgrade to a MM build. (I only have access to WiFi atm and this guide says it will disable it.)
Code:
https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144
Any help is greatly appreciated.
I'm no expert so some of the things I'll suggest may not work.
As a first thought have you tried installing Lineage from TWRP 3.0.2
I'd suggest
1. downloading the OEM MM ROM from Sammobile and install that first so at least you have an OS to start with.
2. after setting it up install the official TWRP App update to the latest version of TWRP
3. ensure SuperSU is on the internal drive although I've not had problems installing it from a MicroSD and install it from TWRP Recovery. You should now have a rooted phone on the latest version of TWRP
4. put the Lineage ROM on the internal drive although again I've not had problems installing from a MicroSD (although it does take longer) and after 'Wiping' the system (it should tell you what steps are required from the Lineage guidance) install it.
5. After setup you will probably have to install SuperSU again or Magisk assuming there's no trace of SuperSU left on the system.
Hopefully someone will jump in and comment if I've missed something obvious or got it all wrong. Although I've rooted all 3 of my SM-N910Fs and SM-N910C at least once and installed various ROMs I don't consider myself particularly knowledgable. So far I've not bricked any of my phones or Tablets.
I really appreciate the reply.
Currently I am trying to flash 5.1.1 stock onto the phone and Odin just freezes about 25% into system.img.ext4
I have tried a dozen times.
I believe what makes my phone so difficult to flash is the stock bootloader is locked.

[PLEASE HELP] HW P9 Lite (VNS-L21) Downgraded to MM, unable to get back to Nougat.

So, due to my Pixel's battery life being atrocious I wanted to try LineageOS 14.1 and use my P9 Lite as a daily driver.
I started by downgrading to Marshmallow from Nougat as DC-Unlocker wouldn't work on 7.0 and I needed the bootloader unlock code.
( I used the firmware and tutorial from 4mobiles dot net, looks to be a polish one. )
Once on 6.0 MM I was able to get the code and unlock the bootloader, however, LineageOS and it's TWRP does not seem to work on 6.0 so I needed to upgrade to Nougat again.
Unfortunately, when I try the official update it says there are no updates available and any time I try to use the firmware finder app either the download fails or upon attempting install the phone reports a 'compatibility issue' and won't accept any firmware.
I tried loads of different update.zip files via the recovery update as well as through ADB. Nothing seems to work.
Finally I was able to get TWRP 3.0.2.0 on it, but again, only the version from 4mobiles dot net works. Other versions of TWRP just remove recovery altogether. (I guess they don't work with 6.0)
At this point it's a bit easier to try roms, but still none of 'em seem to work.
-I tried sideloading and manually installing lineageos 14.1 from the sdcard, it fails with ERROR CODE 7
(currently I'm stuck on the 'YOUR PHONE CAN NOT BE TRUSTED/BOOTLOADER UNLOCKED' screen, no splash but I can get into recovery and fastboot)
-Tried flashing boot.img and system.img of various OEM firmwares as well as LineageOS's manually through ADB, same result, bootloops
It seems to me that some other file makes the phone believe that it's incompatible with any of my roms. Maybe the firmware i got for 6.0 is region locked, or perhaps it's the vendor.img that I don't know how to flash?
I know it's a grave mistake but I didn't take a note on what my original version number was. It was the latest 7.0 Nougat EMUI 5.0 update on a UK based unlocked VNS-L21. The 6.0 MM I flashed on it with a rollback update was C900B300.
I tried the proxy method, custom DNS, and manual download on various roms in the Firmware finder app. Even when the download doesn't fail, the system always says the firmware is incompatible when I try to install.
Right now I could put 6.0 MM back on it and make it usable, but I doubt it would be much better than the 7.0 that was on it originally.
Can anyone tell me how I could put the original Nougat firmware back on it? eRecovery doesn't detect any possible updates.
Any help would be appreciated and thanks in advance!
richplays said:
So, due to my Pixel's battery life being atrocious I wanted to try LineageOS 14.1 and use my P9 Lite as a daily driver.
I started by downgrading to Marshmallow from Nougat as DC-Unlocker wouldn't work on 7.0 and I needed the bootloader unlock code.
( I used the firmware and tutorial from 4mobiles dot net, looks to be a polish one. )
Once on 6.0 MM I was able to get the code and unlock the bootloader, however, LineageOS and it's TWRP does not seem to work on 6.0 so I needed to upgrade to Nougat again.
Unfortunately, when I try the official update it says there are no updates available and any time I try to use the firmware finder app either the download fails or upon attempting install the phone reports a 'compatibility issue' and won't accept any firmware.
I tried loads of different update.zip files via the recovery update as well as through ADB. Nothing seems to work.
Finally I was able to get TWRP 3.0.2.0 on it, but again, only the version from 4mobiles dot net works. Other versions of TWRP just remove recovery altogether. (I guess they don't work with 6.0)
At this point it's a bit easier to try roms, but still none of 'em seem to work.
-I tried sideloading and manually installing lineageos 14.1 from the sdcard, it fails with ERROR CODE 7
(currently I'm stuck on the 'YOUR PHONE CAN NOT BE TRUSTED/BOOTLOADER UNLOCKED' screen, no splash but I can get into recovery and fastboot)
-Tried flashing boot.img and system.img of various OEM firmwares as well as LineageOS's manually through ADB, same result, bootloops
It seems to me that some other file makes the phone believe that it's incompatible with any of my roms. Maybe the firmware i got for 6.0 is region locked, or perhaps it's the vendor.img that I don't know how to flash?
I know it's a grave mistake but I didn't take a note on what my original version number was. It was the latest 7.0 Nougat EMUI 5.0 update on a UK based unlocked VNS-L21. The 6.0 MM I flashed on it with a rollback update was C900B300.
I tried the proxy method, custom DNS, and manual download on various roms in the Firmware finder app. Even when the download doesn't fail, the system always says the firmware is incompatible when I try to install.
Right now I could put 6.0 MM back on it and make it usable, but I doubt it would be much better than the 7.0 that was on it originally.
Can anyone tell me how I could put the original Nougat firmware back on it? eRecovery doesn't detect any possible updates.
Any help would be appreciated and thanks in advance!
Click to expand...
Click to collapse
use full update.zip from firmware finder. to upgrade, you can't use latest package. you must use first nougat update.zip.
RyotaGamer said:
use full update.zip from firmware finder. to upgrade, you can't use latest package. you must use first nougat update.zip.
Click to expand...
Click to collapse
I've only used Full-OTAs, no bugfixes. None of them seem to work.
Yesterday I tried manually selecting a different model in Firmware Finder;
VNS-L21C185 instead of the default VNS-L21C432-
and downloaded VNS-L21C185B397 update. It verified fine but I couldn't install it due to my recovery being TWRP and not the stock one. What I think I'll try is flashing the recovery of the original Marshmallow firmware that's currently on the system and seeing if it will install this update. I kinda doubt it will tho.
Any other suggestions?
Is there any way I can install a nougat TWRP without my current working firmware being on nougat?
If not, is there any way I can install a nougat firmware with TWRP 3.0.2.0? In order to flash update.zip / update.app files I need to get the stock recovery back, but I can't seem to be able to do that.
Is there any way I can flash a standard OEM Rom onto it with TWRP?
richplays said:
Is there any way I can install a nougat TWRP without my current working firmware being on nougat?
If not, is there any way I can install a nougat firmware with TWRP 3.0.2.0? In order to flash update.zip / update.app files I need to get the stock recovery back, but I can't seem to be able to do that.
Is there any way I can flash a standard OEM Rom onto it with TWRP?
Click to expand...
Click to collapse
you can't install nougat TWRP in EMUI 4. you can install update.app with original recovery.
extract UPDATE.APP from update.zip
place UPDATE.APP to dload folder in sdcard.
press power button, vol+ and vol-

SM-T380 Stock Image Files

I just upgraded to Pie on my SM-T380 and am now running into an issue after trying to re-root the tab.
I had previously rooted the tab using TWRP and Magisk and didn't have any problems except that I could not update Magisk since every time I went to TWRP I could not mount data, etc. I did an upgrade from Oreo to Pie today and it appeared to work without problems. I then tried re-rooting following the instructions here SM-T380 Rooting Guide but now only get an error screen when booting up (Security Error...) stating that "Only official released binaries are allowed." I can't boot into recovery and I've tried to reflash TWRP and get a FAIL in Odin every time.
I've tried to find the stock images to just reflash everything through Odin but am unsure which is the right image file (https://www.sammobile.com/samsung/galaxy-tab-a-2017/firmware/#SM-T380, I'm in the US). Can someone point me in the right direction?
Appreciate any help!
I found firmware for my T280 at this website https://samfrew.com/

Categories

Resources