Related
Hello,
I am trying to install Lineage OS 14.1 on my SM-G930R4 herolte device. I have tried multiple odin versions, ranging from 3.09 to 3.12.3. I am trying to flash to newest TWRP, but I did try twrp-3.1.1-0 aswell. Nothing has worked. The error I am getting in ODIN when using 3.10.6 and 3.12.3 is "Complete(Write) operation failed." and in 3.09 I am getting "NAND Write Start!!" where it gets stuck.
I have ticked OEM unlock and USB debugging. I have also spent awhile googling this issue. But I am not finding anything and am not skilled enough to figure this error out myself. Any help is greatly appreciated!
I'm having similar issues. Any luck?
Robby98756 said:
I'm having similar issues. Any luck?
Click to expand...
Click to collapse
I can fix it for you by teamviewer and in process i need your whatsapp number for convenience.
Everything I can find suggests the G930R4 is USA snapdragon. You can't flash TWRP on USA snapdragon models, bootloader is locked permanently and the unlock option in settings doesn't actually do anything for them.
Beanvee7 said:
Everything I can find suggests the G930R4 is USA snapdragon. You can't flash TWRP on USA snapdragon models, bootloader is locked permanently and the unlock option in settings doesn't actually do anything for them.
Click to expand...
Click to collapse
Please Make an engineering boot for V9 binary in latest csc G930UUES9CSC2.
NONE CAN ROOT OR EVEN INSTALL TWRP FOR THE LACK OF V9 OR S9 BINARY ENGINEERING BOOT FILE
Hello,
I am attempting to downgrade from Android 8 to 7 on Galaxy S7. When I attempt to flash the old firmware I get the error 'Device 3 - Binary 2'. Does anyone know if there is a workaround for this yet?
DannySB1 said:
Hello,
I am attempting to downgrade from Android 8 to 7 on Galaxy S7. When I attempt to flash the old firmware I get the error 'Device 3 - Binary 2'. Does anyone know if there is a workaround for this yet?
Click to expand...
Click to collapse
Odin will not let you flashback to a previous boot loader version, you have to do it through TWRP. So either flash the nougat firmware with TWRP first or any nougat based rom, then flash nougat via odin which will remove root and TWRP.
cooltt said:
Odin will not let you flashback to a previous boot loader version, you have to do it through TWRP. So either flash the nougat firmware with TWRP first or any nougat based rom, then flash nougat via odin which will remove root and TWRP.
Click to expand...
Click to collapse
Are there any instructions for this?
Will secure apps (Banking etc) work again after removing root?
I was under the impression you could via Odin if OEM unlock was enabled, without needing TWRP or root. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-downgrade-android-oreo-8-0-t3821495
edit: As for banking, if you go root then flash back to stock you should have no issues. Even if you stay root, things like Magisk will hide root status from apps and pass safetynet. Your biggest issue would be the loss of Knox, which voids warranty and breaks some Samsung apps.
Beanvee7 said:
I was under the impression you could via Odin if OEM unlock was enabled, without needing TWRP or root. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-downgrade-android-oreo-8-0-t3821495
Click to expand...
Click to collapse
It is not possible as per some of the replies to that thread. I spent a few hours playing TWRP yesterday and it was not possible either.
DannySB1 said:
It is not possible as per some of the replies to that thread. I spent a few hours playing TWRP yesterday and it was not possible either.
Click to expand...
Click to collapse
Ok so listen, it can be done as i said but it's not easy. The choice you have of course before attempting this is to just install a android 7 custom ROM? many nougat ROMs are just stock with the bloatware removed and the boot-loader version isn't checked during flash.
Here's another way to go back, i can't guarantee it will work though i haven't tried it on an S7.
Downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's how's it done?
Download the firmware file (.tar) which you want to downgrade to and open it with an archiver application (7zip). Extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends in .bin (e.g. sboot.bin etc.). This .tar file can now be flashed like any other firmware file via Odin and it should run through it without any problems.
Hope this helps.
plz tell me how to downgrade i upgraded my phone to oreo now there's no network i need to downgrade back to marshmellow i also installed marshmellow but it stuck on samsung bootloop plz help me
Bipnbarsha said:
plz tell me how to downgrade i upgraded my phone to oreo now there's no network i need to downgrade back to marshmellow i also installed marshmellow but it stuck on samsung bootloop plz help me
Click to expand...
Click to collapse
What device? What firmware? What Rom?
S7 edge on oreo and stock rom my network was working fine on marshmellow but after oreo update my mobile network not working unfortunatly my binary has been updated before update i back up everything with twrp but now when i restore using twrp my phone stuck on samsung logo plz help mee
downgrand note 9 N9600 ZTO
i need to downgrand my note 9 i pay for the service of someone who can help me. i'm on the last firmawre bdo android 9 and i want to downgrand to the latest firmware of android 8.1. My note 9 is the N9600 ZTO.
email
[email protected]
whatsapp and telegram
+5582994311001
cooltt said:
Ok so listen, it can be done as i said but it's not easy. The choice you have of course before attempting this is to just install a android 7 custom ROM? many nougat ROMs are just stock with the bloatware removed and the boot-loader version isn't checked during flash.
Here's another way to go back, i can't guarantee it will work though i haven't tried it on an S7.
Downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's how's it done?
Download the firmware file (.tar) which you want to downgrade to and open it with an archiver application (7zip). Extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends in .bin (e.g. sboot.bin etc.). This .tar file can now be flashed like any other firmware file via Odin and it should run through it without any problems.
Hope this helps.
Click to expand...
Click to collapse
Hey man, can you please explain this better ? Im using a galaxy s7 edge, but my firmware doesnt have a TAR file. there are 4 .md5 files (AP,BL,CP,CSC) that are flashable through odin. I want to downgrade bootloader
laurentiudll said:
Hey man, can you please explain this better ? Im using a galaxy s7 edge, but my firmware doesnt have a TAR file. there are 4 .md5 files (AP,BL,CP,CSC) that are flashable through odin. I want to downgrade bootloader
Click to expand...
Click to collapse
Hello that method no longer works, you can't downgrade anymore
cooltt said:
Hello that method no longer works, you can't downgrade anymore
Click to expand...
Click to collapse
I can downgrade to 14.1 Lineage OS.
Edit: There is no way do downgrade the official firmware
Hi guy I am panicking here I accidentally wiped everything from my samsung note 9 and there is no OS on the phone. I tried to flash older firmware but Odin is stuck at recovery and the phone shows a red line saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 6, BINARY:5
PLEASE SOMEONE HELP ME
Skulper said:
Hi guy I am panicking here I accidentally wiped everything from my samsung note 9 and there is no OS on the phone. I tried to flash older firmware but Odin is stuck at recovery and the phone shows a red line saying "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 6, BINARY:5
PLEASE SOMEONE HELP ME
Click to expand...
Click to collapse
The firmware that you flashed has a lower binary than the firmware that you had on the device before you modified it. You need to flash a firmware that has the same binary as what you had before you modified the device, or you need to flash a firmware that has a higher/newer binary than what you had.
See where the error says that your device is binary 6 but the firmware that you flashed has binary 5? You need a binary 6 or higher firmware. You can identify the binary by looking at the 5th character from the right end of the firmware build number.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
The firmware that you flashed has a lower binary than the firmware that you had on the device before you modified it. You need to flash a firmware that has the same binary as what you had before you modified the device, or you need to flash a firmware that has a higher/newer binary than what you had.
See where the error says that your device is binary 6 but the firmware that you flashed has binary 5? You need a binary 6 or higher firmware. You can identify the binary by looking at the 5th character from the right end of the firmware build number.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
i think i might be in love with you,(not in a weird way) this reply here saved my ass,i was stuck on odin wondering what was wrong & just this simple explanation helped me a lot
brokboi said:
i think i might be in love with you,(not in a weird way) this reply here saved my ass,i was stuck on odin wondering what was wrong & just this simple explanation helped me a lot
Click to expand...
Click to collapse
Be aware, once you flash a firmware that upgrades your device binary to a higher binary, you can not go back to the lower binary. A lot of times, flashing a firmware that upgrades the binary also upgrades the bootloader to a more secure bootloader that can't be unlocked, this kills virtually any chance of rooting the device or flashing TWRP custom recovery and/or custom ROMs. Then you're stuck with a device that you can't modify the way you want.
Droidriven said:
Be aware, once you flash a firmware that upgrades your device binary to a higher binary, you can not go back to the lower binary. A lot of times, flashing a firmware that upgrades the binary also upgrades the bootloader to a more secure bootloader that can't be unlocked, this kills virtually any chance of rooting the device or flashing TWRP custom recovery and/or custom ROMs. Then you're stuck with a device that you can't modify the way you want.
Click to expand...
Click to collapse
Ya i had that in mind so i flashed accordingly & i have unlocked bootloader with twrp not that i needed it though, cuz i just wanted to use samsung dex
brokboi said:
Ya i had that in mind so i flashed accordingly & i have unlocked bootloader with twrp not that i needed it though, cuz i just wanted to use samsung dex
Click to expand...
Click to collapse
Have you used TWRP to create a android backup of your stock ROM after you got it fixed? If not, do so, then store a copy of the backup on a PC or USB flashdrive, external sdcard, etc.. That backup can be used to restore your device, if needed.
Root Samsung Galaxy A52 SM-A525F Android 11 Official - AUC4 Firmware. TWRP Recovery for Galaxy A52 Android 11 does not available yet when I posted this rooting guide. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Rooting Instructions ( Don't make mistake )
Make sure the bootloader are unlocked, OEM unlock option is grey out
Patch boot.img then Pack it to magisk_patched.tar. If you don't want to do it by your self, you can download it from link below
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN
Insert magisk_patched.tar in AP, then click start. The phone will rebooting to ANDROID RECOVERY MODE
in ANDROID RECOVERY, Select Factory data reset and press power key to confirm
select 'Factory data reset' again and confirm
Setup the phone
Connect to Internet
Install and Open Magisk App, it will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Download
magisk_patched
Telegram: https://t.me/SamsunGalaxyA52
Watch This Video Tutorial
Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.
Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?
<deleted>
VonSparq said:
Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?
Click to expand...
Click to collapse
On qcom devices, not really. Even on exynos devices after removing that you still need to physically press the power button or if you don't wanna even do that you have to w8 bout 10 to 15 extra seconds..
hansxl said:
Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.
Click to expand...
Click to collapse
Okay, solved. Flashed latest firmware (AUC5) and patched boot.img with Magisk. Fingerprints works now and no reboots so far
Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?
Rerel14 said:
Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?
Click to expand...
Click to collapse
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com
hansxl said:
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?
Rerel14 said:
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?
Click to expand...
Click to collapse
Yes, it's more or less the procedure. But I would just download the latest magisk (22.1) from
Magisk v22.1 brings an improved log writer, resetprop bootloop fixes, and much more
The latest stable update for Magisk (v22.1) has been released with tons of bug fixes and feature improvements. Read on to know more!
www.xda-developers.com
the UI is a bit different from the one in your video
My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?
Rerel14 said:
My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?
Click to expand...
Click to collapse
bootloader unlocked
hansxl said:
bootloader unlocked
Click to expand...
Click to collapse
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?
Rerel14 said:
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?
Click to expand...
Click to collapse
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also
hansxl said:
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also
Click to expand...
Click to collapse
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?
I think I found one :
Rerel14 said:
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?
Click to expand...
Click to collapse
How To Unlock Samsung Galaxy A52 Bootloader - NaldoTech
In this tutorial, you will learn how to unlock the bootloader on your Samsung Galaxy A52. A bootloader is the piece of code that runs before the operating
www.naldotech.com
don't forget to backup your data. I think after unlocking bootloader your phone will return to factory settings
I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?
I installed Magisk from an other source and eventually I succeeded to get root !
Huge thanks Hansxl for your help and patience. Really appreciated it.
Last question : if I update the firmware I'll need to make the full procedure described above again ?
Rerel14 said:
I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?
Click to expand...
Click to collapse
deinstall magisk and install magisk again
Hey guys, I'm on an SM-F711B. Today when trying to update my rooted OS, I had Odin fail twice while trying to install the patched AP file. I also noticed that the patched AP file was about half the size of the original - 3.2gb instead of 8gb. I then tried to install with the stock AP file, but now (duh) it says the file system is corrupted and Android can't boot. Is there any way I can a) fix the patched AP file without access to my phone, or b) at least recover the files (especially images) from my device before having to factory reset? many thanks
Hi,
there's no twrp yet and I doubt that there will ever be. Can you download the firmware again and flash the stock rom to begin again?
Edit:
what size is the original AP file?
thanks for the response
is flashing the stock rom different from loading the stock AP/BL/CP/CSC from Odin? If so, how do I do it?
The AP file is 7.74 GB according to Windows
my AP file is 8.11 GB, which firmware are you trying to flash?
yes the stock rom is different words for stock firmware but if you've already flashed the CSC file (instead of HOME) then you've probably lost any photos as it wipes the storage
Oh, to clarify, I did flash HOME_CSC. my AP filename is AP_F711BXXS2CVG1_F711BXXS2CVG1_MQB53367836_REV00_user_low_ship_MULTI_CERT_meta_OS12.tar if that at all helps narrow down the firmware? I just got whatever was latest from Frija
can you install magisk on a friend or family phone and try patching the AP file again and check the patched file size? it should be slightly larger than the original AP file
Thanks for the advice. I tried patching on my partners phone, a Pixel 2XL. Magisk printed
Code:
-- Copying: super.img.lz4
! Process error
! Installation failed
Do I need to run the patch on another Z Flip 3? Or is this a sign that the AP file i got from Frija is corrupt? It's interesting that it failed during super, as Odin also failed during super when trying to install the patched version
Edit: Her phone was full. We've cleared up some space and I'm trying again
yes I think the firmware might have a gremlin in it, I'd try downloading from a different website and start again
Download Galaxy Z Flip3 5G SM-F711B (O2C) F711BXXS2CVG1 in Samfw - Samsung firmware download
Galaxy Z Flip3 5G SM-F711B (O2C - Czechia) F711BXXS2CVG1 S(Android 12) samsung firmware download all model, lastest, fast update, completely free and fast speed in Samfw.com ✅
samfw.com
Hi, I've managed to patch the AP file using my partners phone. It is slightly larger than the original AP file (on Android, 8.39 instead of 8.31 GB). Can I use this patched AP file on my Z Flip 3? or is it model-specific?
yes you can flash it...good luck!
OMG it worked!!!! thank you so so much for your help!
lesbianpinkie said:
OMG it worked!!!! thank you so so much for your help!
Click to expand...
Click to collapse
Wait - spoke too soon. phone boots, but in my file manager, Internal Storage is being shown as 0b / 0b, and no apps seem to be able to access it..... any idea what to do now?
this has happened to me before and in twrp I would choose repair file system, but of course we don't have twrp hmm. did you try flashing the stock AP file to see if that fixes it, then can root afterwards