Database Users

[GUIDE] Error 7 Solution While flashing 7.1.2 ROMs

A brief Intro.
Starting from the 7.1.2 ROMs most of the developers decided to follow the process of checking modem version at the time of flashing the rom. Many peoples ended up in
"Error 7- assert(xiaomi.verify_modem("MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1") == "1")"
The main reason for this is the outdated firmware or it is happened to those who had unofficially unlocked the bootloader.
Some more info..
1. You must be on MM build bootloader. If you are unofficially unlocked bootloader it will give you ERROR7.
@TheStrix have alreday given a short information about it in his Official LineageOS thread. If you are unaware of it read it here
2.Outdated Firmware.
Your firmware must be from from MIUI Global DEV v7.5.4 or above.
Get MIUI Global DEV v7.5.4 from here
or the latest firmware from here
NB:-
- Iam using the MIUI Global DEV v7.5.4 firmware. All working fine including Volte. I dont know about the second one,you can give it a try.
-If you are unofficially unlocked ,MIUI Global DEV v7.5.4 will re lock your bootloader you will end up in bootloop.
- I will not be reponsible for any damages.
Solution 1 [Permanent Solution] ..
1. So if you are unofficially unlocked, i will suggest to clean flash the latest MIUI Fatboot Rom. Kenzo users get it from here.
2.Flash it using MIFlashTool ,and officially unlock it.
HOW TO UNLOCK THE BOOTLOADER OF REDMI NOTE 3?
PART 1 : REQUESTING FOR UNLOCK PERMISSION
Step 1 – Open up your favorite web browser in your computer (Chrome is recommended) then go to this link
Step 2 – You’ll see the official page of “Unlock Your Mi Device”. Now simply click on the blue “Unlock Now” Button in the middle of the page.
Step 3 – You’ll see a login page in the next page which is in Chinese. If you use Google Chrome to open the page, then you can simply use its built-in Google Translate feature.
Step 4 – Once logged in, you’ll see the Unlock Application Permissions page.Now simply fill in all required fields then click on that green Apply Immediately button.
Step 5 – In the next page, you’ll need to enter a verification code sent to you via SMS. Check your phone for any SMS verification sent by Xiaomi server. The code is usually valid for only 5 minutes so you need to enter it immediately.
Step 6– Once you have submitted the 6 digits code, you’ll then be redirected to another page saying that from the point toward all you need to do is just waiting for Xiaomi Developers to review and approve your application. Once approved, you’ll get another SMS which normally arrives in 15 min(Atleast for me. For some it may take time). The approval process is manual so just be patient on this.
PART 2 : BOOTLOADER UNLOCKING PROCESS
Requirements for Bootloader Unlocking :
-An active Mi account linked to your device, your phone number and it has permission to proceed with bootloader unlock (follow previous steps above)
-Please backup your data for just in case scenario.
-Again, if you are not fully aware of flashing custom ROM, then you better stay away of unlocking your phone’s bootloader.
Download Mi Flash Unlock tool for Windows here, and install it on your computer / PC.
Step 1 – On your device, please login to your Mi account.
Step 2 – Put / reboot your device into bootloader mode. To do that, simply turn off your device, press the Power button and Volume down ( – ) button at the same time.
Step 3 – On your computer, open MiFlash Unlock tool you’ve just installed. Click on the Agree button when asked.
Step 4 – Login to MiFlash Unlock tool with the same Mi Account.
Step 5 – Now connect your phone to computer using its USB cable.
Step 6 – Once your phone is connected, the Unlock button will become active. Next, simply click on the Unlock button to start the process. The unlock process will take about 10 – 15 seconds to complete. That’s all.
After unlocking your phone’s bootloader, you’ll be able to flash TWRP and other custom ROM. Enjoy..
Please take these as your concern upon unlocking bootloader :
One Mi account could only unlock one device within 30 days.
If you see a notice saying that “current user is not logged in connected device” then please reboot your device normally then login with your account in the device (see Step 1).
Unlocking bootloader will wipe all user data especially if your device is encrypted. That’s why you’ll need to create backup before going to proceed.
Neither Xiaomi or I will guaranteed if anything goes wrong during and as the result of unlocking. Proceed with your own risks.
Also, unlocked Xiaomi devices will be marked in the official service end.
PART 3 : Installing TWRP and Custom Rom.
Step 1 –. Get latest TWRP from here. Flash it via fastboot { I will not be explaining that in details}
Step 2 –. Take back up of EFS using Twrp. Wipe Everything including internal storage.
Step 3 –. Install Firmware-Rom-Gapps in order. Error 7 will be solved
Solution 2[Temporary Solution] ..
Only try this method if you are not able to officially unlock your device . Dont use the Firmware by Strix.It will relock your bootloader.
Step1 - Downalod the rom to your pc.
Step2 - Use any notepad. Suggestd one Notepad++. Get it from here
Step3 - Open the Rom.zip{dont extarct}. Navigate to META-INF/com/google/android/updater-script.
Double click on updater-script and open it with notepad++. Edit and remove this line from the file
Code:
assert(xiaomi.verify_modem("MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1") == "1")
Allow the file to save and close the zip.{Rom will recompress by itself}.
Step4 - Flash in order. Firmware -Rom-Gapps.
Some FAQ's ..
1. Iam not getting volte
Ans:- Restore the EFS. Try rebooting your phone 2 or 3 times. After Clean flash ,I had to reboot 3 times to get volte working. :fingers-crossed:
2.Iam not able to see FingerPrint Option?
Ans:- Your are defenitely on an old Firmware.Update to Latest Firmware It will work.
3.Iam getting Some other Errors. :crying:
Ans:- Post your Screen Shot Below.Will Check.
4.Iam getting some other problems in ROM.
Ans:- Report it with proper logs to the developer.Iam helpless.
5.I bricked my device
Ans:- I will Laugh at you. Always do everything at your own risk. :silly:
Some Advices ..
* At least use search once in your life time. From my observation its clear that no one ever uses search in the Rom Section. Even is there is a solution in every page you keep on asking same questions.
*Dont flood the thread.
*Dont qoute the whole op.
*Respect other members
If this was of help to anyone hit the like :fingers-crossed:

First

There's a problem with not updating the bootloader (aboot) and staying with a LP bootloader, you will most likely encounter bootloops. Say you edit that code line for the modem check, it will flash but it won't boot/work properly. You must update the bootloader in order to boot newer ROMs. And you need to update the modem and other stuff so you won't face issues. You need to offcially unlock no matter what you do, it's very easy.

Asphyxiate666 said:
There's a problem with not updating the bootloader (aboot) and stay with a LP bootloader, you will most likely encounter bootloops. Say you edit that code line for the modem check, it will flash but it won't boot. You must update the bootloader in order to boot newer ROMs. And you need to update the modem and other stuff so you won't face issues. You need to offcially unlock no matter what you do, it's very easy.
Click to expand...
Click to collapse
that's why I wrote temporary method..only for those who are lazy and not willing to start from root by flashing fastboot rom

adithyan25 said:
that's why I wrote temporary method..only for those who are lazy and not willing to start from root by flashing fastboot rom
Click to expand...
Click to collapse
I understand but with their laziness they will ruin their devices then come here and say "omg sir it doesn't boot wtf is this useless rom crap developers".

Asphyxiate666 said:
I understand but with their laziness they will ruin their devices then come here and say "omg sir it doesn't boot wtf is this useless rom crap developers".
Click to expand...
Click to collapse
I know that...most people don't even bother to use search..even if there is a solution just above their question they won't give a damn to look it..

guys help..i had officially unlocked the bootloader..and i don't remember the firmware i had installed...n i am still getting the error code 7..do i need to flash the kenzo global or dev firmware from the link..??

PrathaM X said:
guys help..i had officially unlocked the bootloader..and i don't remember the firmware i had installed...n i am still getting the error code 7..do i need to flash the kenzo global or dev firmware from the link..??
Click to expand...
Click to collapse
you must format your phone (not wipe) using twrp then install fw-rom-gapps...use fw by strix from above method(permanent)

I flashed v8.5.1.0 using MiFlash and it said flash completed successfully. However now it is stuck on the Mi splash screen with "powered by android" logo at the bottom. The dots are moving so I assume it is loading but it's been on that same screen for the past 10 minutes now.
Previously, the bootloader was officially unlocked but some stuff broke as I tried to upgrade to a new ROM and that's why I decided to flash v8.5.1.0 in order to go back to stock and start from scratch.
Edit: It works!

adithyan25 said:
you must format your phone (not wipe) using twrp then install fw-rom-gapps...use fw by strix from above method(permanent)
Click to expand...
Click to collapse
I'm on Marshmallow boot loader (flashed faatboot ROM) and officially unlocked & formated data.
Yesterday I did a update RR ROM (9th july) then I got error 7.
at the time of flashing I was on latest firmware 7.7.6.
So reflashed 7.5.4 firmware and it's worked.
So we should always stick to 7.5.4 firmware ? For avoiding error 7?

baku2313 said:
I'm on Marshmallow boot loader (flashed faatboot ROM) and officially unlocked & formated data.
Yesterday I did a update RR ROM (10th july) then I got error 7.
at the time of flashing I was on latest firmware 7.7.6.
So reflashed 7.5.4 firmware and it's worked.
So we should always stick to 7.5.4 firmware ? For avoiding error 7?
Click to expand...
Click to collapse
yep..in my knowledge the latest firmware has a change in modem version(updated version) so it wont match with one in updater script... so i will say to stick with some older firmware unless the developers chabge it in the roms update-script file...
iam using strix fw 7.6.15

adithyan25 said:
yep..in my knowledge the latest firmware has a change in modem version(updated version) so it wont match with one in updater script... so i will say to stick with some older firmware unless the developers chabge it in the roms update-script file...
iam using strix fw 7.6.15
Click to expand...
Click to collapse
Can you provide me the link please.

baku2313 said:
Can you provide me the link please.
Click to expand...
Click to collapse
its in the aosp extended 4.4 update op...
im quite busy now...i will share it later if you havent found it .... you will find the link in aosp extended thread

adithyan25 said:
its in the aosp extended 4.4 update op...
im quite busy now...i will share it later if you havent found it .... you will find the link in aosp extended thread
Click to expand...
Click to collapse
Strix updated his thread with 7.7.6 firmware (Kenzo).

I am on MM on Redmi note 3 Snapdragon version! I tried firmware (7.7.0 I guess) and then ROM Zip but still got the Problem ! Any thing else I can do?

What if i have locked bootloader and flashed twrp through miflash?

coolguy22 said:
What if i have locked bootloader and flashed twrp through miflash?
Click to expand...
Click to collapse
In theory it should work I guess? Assuming you used the guide from @khajiit here you should have a MarshMellow bootloader, as the MIUI version linked there is based on MM (kate_global_images_6.11.3_20161103.0000.00_6.0_global_16db0fc5fa), so it shouldn't relock. Can't try myself since I unlocked mine recently.

Amon_Re said:
In theory it should work I guess? Assuming you used the guide from @khajiithere you should have a MarshMellow bootloader, as the MIUI version linked there is based on MM (kate_global_images_6.11.3_20161103.0000.00_6.0_global_16db0fc5fa), so it shouldn't relock. Can't try myself since I unlocked mine recently.
Click to expand...
Click to collapse
Ok so if i get the latest firmware and install some 7.1.2 rom it shouldn't bootloop?

coolguy22 said:
Ok so if i get the latest firmware and install some 7.1.2 rom it shouldn't bootloop?
Click to expand...
Click to collapse
In theory, it should work.

..

Samsung s5 have 5.0 want update, keep root and unlocked phone need simple instruction

Hello, I have a rooted, unlocked Samsung Galaxy S5 -SM-G900V. I want to update to Marshmallow 6.0 or higher and keep the root and unlock or easily add those after I update to 6.0. I have downloaded the Samsung usb driver onto my laptop and Odin3_v3.09 (however, I have read different recommendations and am confused which version I should use). I tried to find firmware to download from sammobile.com/firmwares but when I type in my phone it doesn't recognize it. 1. What is a simple way to update to 6.0 and keep a root and unlock? 2. Which version of Odin3 should I use? 3. What it is the list of things I need to download to do it? Thank you

Update using FlashFire. This will no update your bootloader. Later in odin3 update the correct modem and nonhlos for they specific MM firmware (QD1,QF2,QH2)

This worked for me
newbie000001 said:
Hello, I have a rooted, unlocked Samsung Galaxy S5 -SM-G900V. I want to update to Marshmallow 6.0 or higher and keep the root and unlock or easily add those after I update to 6.0. I have downloaded the Samsung usb driver onto my laptop and Odin3_v3.09 (however, I have read different recommendations and am confused which version I should use). I tried to find firmware to download from sammobile.com/firmwares but when I type in my phone it doesn't recognize it. 1. What is a simple way to update to 6.0 and keep a root and unlock? 2. Which version of Odin3 should I use? 3. What it is the list of things I need to download to do it? Thank you
Click to expand...
Click to collapse
I just finished updating from 5.0 to 6.0.1 pre-rooted using this guide: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Scroll down and follow jrkruse's great very clear instructions. However, before you start make sure Reactivation lock under Settings --> Security is turned off. You have to sign into a Samsung account for this to work. If you forget that step you'll get stuck at the 13th step and have to reimage with stock again. to disable it.

acej2 said:
I just finished updating from 5.0 to 6.0.1 pre-rooted using this guide: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Scroll down and follow jrkruse's great very clear instructions. However, before you start make sure Reactivation lock under Settings --> Security is turned off. You have to sign into a Samsung account for this to work. If you forget that step you'll get stuck at the 13th step and have to reimage with stock again. to disable it.
Click to expand...
Click to collapse
*****
Thank you for the information, I appreciate it!
1) As suggested, I made sure the reactivation lock was not selected,
2) I downloaded jrkruse's eMMC_CID_Checker_.apk to Check my CID
3) then downloaded the file EMMC_15_Root_Bootloader_Unlock S5_QB2_PB1.zip
4) As suggested I moved the the root s5 folder (but I didn't see those exact file names in the folder so I am attempted to download them individually
((EMMC_15_SafeStrap_QA1_6_0_1_MM_Bootloader_Unlock_A IO.zip, The link I click on for this one doesn't seem to work and the EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip)) when I try and download that it says I don't have any storage space . The total space I have is 16gb it says 300 mb available. I also have an sd card that is 122gb available. I moved several apps to that the sd card, cleared caches and pictures and videos... with no luck. Do you have any suggestions?

for my not_unlockable bootloader, the EMMC_11_ Root S5_QB2_PB1.zip contained a folder, an MD5 file, and 2 zip files. I checked for your unlockable bootloader, and found much the same; hope this helps. I copied those to an SD card, and continued from there.

No sim card detected on custom roms

I have a XT1572 (Indian variant dual sim) . The sim card works good on both 6.0 & 7.0 (official roms) however remains undetected on any custom rom . Any guidance would be of great help .

Using magisk? It will cause that. Flash magisk uninstaller and reboot system once before flashing a new rom.

Tried but no success
jason2678 said:
Using magisk? It will cause that. Flash magisk uninstaller and reboot system once before flashing a new rom.
Click to expand...
Click to collapse
So I was on stock mm , had magisk -uninstalled and rebooted afterwards . Installed RRemix(RR-N-v5.8.5-20171230-clark-Final) . Again no sim . Attaching two screen shots for your reference .
One thing to note I have a dual sim variant and under all custom roms imei of only one is being displayed .
This whole thing is very strange since I could run Lineage very easily on the same phone sometime back , roughly around Oct'17 . Used the phone on stock nougat afterwards .

Anyone ?
Sir2taj said:
So I was on stock mm , had magisk -uninstalled and rebooted afterwards . Installed RRemix(RR-N-v5.8.5-20171230-clark-Final) . Again no sim . Attaching two screen shots for your reference .
One thing to note I have a dual sim variant and under all custom roms imei of only one is being displayed .
This whole thing is very strange since I could run Lineage very easily on the same phone sometime back , roughly around Oct'17 . Used the phone on stock nougat afterwards .
Click to expand...
Click to collapse
@antariksh
I am very well aware of the fact that lineage would not run on nougat modem. Have tried aicp rremix unofficial lineage etc . The issue remains the same no sim detected .
What I have done for installation -
fastboot install marshmallow/nougat build (depending upon the custom rom)
flash latest twrp
in twrp factory reset (don't mount/unmount anything, all default)
rom boots but doesnt detect any sim .
details of only one imei of the two is displayed under about phone .

Sir2taj said:
@antariksh
I am very well aware of the fact that lineage would not run on nougat modem. Have tried aicp rremix unofficial lineage etc . The issue remains the same no sim detected .
What I have done for installation -
fastboot install marshmallow/nougat build (depending upon the custom rom)
flash latest twrp
in twrp factory reset (don't mount/unmount anything, all default)
rom boots but doesnt detect any sim .
details of only one imei of the two is displayed under about phone .
Click to expand...
Click to collapse
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'

antariksh said:
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'
Click to expand...
Click to collapse
Will try the guide and get back to you
Update
Tried each and every step as per your suggestions . No change .
The phone is failing to recognize sims on all custom roms .

Sir2taj said:
Will try the guide and get back to you
Update
Tried each and every step as per your suggestions . No change .
The phone is failing to recognize sims on all custom roms .
Click to expand...
Click to collapse
@antariksh pls help

Sir2taj said:
@antariksh pls help
Click to expand...
Click to collapse
I'm afraid it must be your device issue.
Cause last week I followed the same steps to Flash Stock Nougat and went back to NucleaROM.
You sure you are using Nougat Modem based Custom ROMs?

antariksh said:
I'm afraid it must be your device issue.
Cause last week I followed the same steps to Flash Stock Nougat and went back to NucleaROM.
You sure you are using Nougat Modem based Custom ROMs?
Click to expand...
Click to collapse
Very very strange because I do recall that all these custom ROMs used to run fine without any such stupid issues back in October last year . its really disheartening. Yes I am using nougat firmwares for nougat modem compatible ROMs and mm firmware for rhe mm compatible one's . Its just that be it any custom ROM this thing won't work at all ! Is it anyhow related to recovering phone from brick state because I do remember that I had to flash the bootloader on a memory card in order to get the device up ?
Appreciate your efforts brother.

i have similar problem

antariksh said:
Have you tried this version with this guide?
P.S: Nougat has 9 system.img_sparsechunk's. So flash accordingly and then try any other custom ROMs.
P.P.S: Flash Modem twice if you get any 'prevalidation failed error'
Click to expand...
Click to collapse
HI there , I hope my constant requests aren't bothering . If they are kindly let me know & I shall refrain in future .
I just realised one thing . On installing nougat fastboot file from " https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257" as per suggestions I get model as XT 1572 on connection to PC . Although in recovery mode when connected (twrp) the same pc recognizes the phone as XT1575 . Is it normal ?

Sir2taj said:
HI there , I hope my constant requests aren't bothering . If they are kindly let me know & I shall refrain in future .
I just realised one thing . On installing nougat fastboot file from " https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257" as per suggestions I get model as XT 1572 on connection to PC . Although in recovery mode when connected (twrp) the same pc recognizes the phone as XT1575 . Is it normal ?
Click to expand...
Click to collapse
Yep. It is normal. TWRP was probably based out on XT1575. But it doesn't matter.
Only modems differ between XT1575 and XT1572.

Flash the MM firmware, make sure the modem has no validation issues, then flash the custom ROM you want. Flashing with Nougat firmware won't allow boots. Also, sometimes the MM firmware just doesn't work, and flashing stock firmware will "rejuvenate" it.

parker.stephens said:
Flash the MM firmware, make sure the modem has no validation issues, then flash the custom ROM you want. Flashing with Nougat firmware won't allow boots. Also, sometimes the MM firmware just doesn't work, and flashing stock firmware will "rejuvenate" it.
Click to expand...
Click to collapse
I wanted to try installing it on 6.0 . The install process didn't initiate saying that the bootloader (A**52) isnt compatible.
Plus I noted that on downgrading to 6.0 from 7.0 the loader and gpt bin gave failure errors in fastboot.

Sir2taj said:
I wanted to try installing it on 6.0 . The install process didn't initiate saying that the bootloader (A**52) isnt compatible.
Plus I noted that on downgrading to 6.0 from 7.0 the loader and gpt bin gave failure errors in fastboot.
Click to expand...
Click to collapse
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."

parker.stephens said:
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."
Click to expand...
Click to collapse
Will give it a try

parker.stephens said:
GPT is not downgradeable and it doesn't need to flash successfully. Also, one you are on 0xA052 firmware, you can't go back, but you can edit the rom's files and make it skip the bootloader check. This is a quote of myself on how to do that from the LOS thread,
"Extract the ROM zip into it's own subdirectory. Then go into the folder META-INF, then com, then google, android, then open updater-script in a text editing program. I prefer Notepad++. Locate the line that says assert getprop ro.bootloader. Should be line 2. You can either add your bootloader by copying another item, or this is easier, edit a line already there, such as "|| getprop("ro.bootloader") == "0xA048" ||" and replace 0xA048 with 0xA052 or the bootloader your device has. Then save it by going to the root folder, not the folder labeled "lineage-14.1-xxxxxxxx-nightly-clark-signed", but the folder with the folders install, META-INF, system, and etc. Select everything by dragging your cursor over all the files, then right-click, send-to, compressed zip. Name it anything, then copy it to your device however you prefer, I just sideloaded it in TWRP. If you get an error talking about a digest file, you might have accidentally deleted something you shouldn't have."
Click to expand...
Click to collapse
Iam gettign error 6 . Pls share the edited updater script for bootloader - A0.52

I've got exactly the same issue.... Sim not detected on Nougat, can't boot Marshmallow roms.
Someone found a fix to this?

Perhaps I'm not the only one having the issue of no sim

Sir2taj said:
Perhaps I'm not the only one having the issue of no sim
Click to expand...
Click to collapse
i have the same issue my friend and i dont know what to do.

TWRP, Rooting and Custom Rom HELP SM-T510 Tablet Tab A 10.1

Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)

You don’t unzip the .tar files. Keep them as is.

secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5

My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.

fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.

is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse

fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!

framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.

lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?

framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.

lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.

framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.

lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!

lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY

framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.

lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!

framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.

Downgrade Galaxy s10+ Binary 15 android 12 to android 11

Hi guys,
Sorry if it is a silly question but I have been trying to get the information with no results.
I have a Samsung galaxy s10+ SM G975F... It is binary 15 and when I use Odin, I can get a newer binary than 14... I want to downgrade from Android 12 to 11... The Batery drain is insane now...
Odin always said that the Binary is incorrect and can't flash any diferent rom
Any ideas or suggestions? Can I install a custom Rom at least?
Thanks and I hope you can help me.

Downgrading Samsung phones is pretty much impossible without unlocking bootloader some funky playing around (manually flashing system, boot, and probably way more) and a TON of luck. I could help you better with an older android Version as i dont have much experience with android 9 or newer.

Arash2803 said:
Hi guys,
Sorry if it is a silly question but I have been trying to get the information with no results.
I have a Samsung galaxy s10+ SM G975F... It is binary 15 and when I use Odin, I can get a newer binary than 14... I want to downgrade from Android 12 to 11... The Batery drain is insane now...
Odin always said that the Binary is incorrect and can't flash any diferent rom
Any ideas or suggestions? Can I install a custom Rom at least?
Thanks and I hope you can help me.
Click to expand...
Click to collapse
Bump same question my device is 16 and binary i want to install is 14? help

no, you CANT downgrade the binary but you can try make a rom with older version of android but expect bugs and a lot of issues due the bootloader

i got s10+ "G975FXXUFHVE1" i cant downgrade also im new to this whole stuff i really need help
🥹

Ch_ali134 said:
i got s10+ "G975FXXUFHVE1" i cant downgrade also im new to this whole stuff i really need help
Click to expand...
Click to collapse

Same boat here... S10+
i'm on G975FXXUGHVJ5 (android 12), so locked to bin 16. Wanted to go back to G975FXXSEFUL1 (android 11) So I could use my GearVR again, but that is bin 14... Backporting GearVR is out of the question... So i'm left with a feature downgraded p.o.s.. and this was the last moddel to support GearVR...

Pandoriaantje said:
Same boat here... S10+
i'm on G975FXXUGHVJ5 (android 12), so locked to bin 16. Wanted to go back to G975FXXSEFUL1 (android 11) So I could use my GearVR again, but that is bin 14... Backporting GearVR is out of the question... So i'm left with a feature downgraded p.o.s.. and this was the last moddel to support GearVR...
Click to expand...
Click to collapse

From what i've read, its mainly dowload mode/odin that does the check and blocks the downgrade. But what about converting an official samsung update to a flashable twrp/recovery zip? I already have a fully magisk rooted stock android 12 rom, i just want do downgrade the system to stock android 11 (rooted) for GearVR. I don't think actually loading the kernel/system is blocked at the bootloader lvl right?
Maybe with a rom kitchen it could be possible to convert to a flashable zip?

Pandoriaantje said:
From what i've read, its mainly dowload mode/odin that does the check and blocks the downgrade. But what about converting an official samsung update to a flashable twrp/recovery zip? I already have a fully magisk rooted stock android 12 rom, i just want do downgrade the system to stock android 11 (rooted) for GearVR. I don't think actually loading the kernel/system is blocked at the bootloader lvl right?
Maybe with a rom kitchen it could be possible to convert to a flashable zip?
Click to expand...
Click to collapse

Pandoriaantje said:
From what i've read, its mainly dowload mode/odin that does the check and blocks the downgrade. But what about converting an official samsung update to a flashable twrp/recovery zip? I already have a fully magisk rooted stock android 12 rom, i just want do downgrade the system to stock android 11 (rooted) for GearVR. I don't think actually loading the kernel/system is blocked at the bootloader lvl right?
Maybe with a rom kitchen it could be possible to convert to a flashable zip?
Click to expand...
Click to collapse
its only blocked when the bootloader is locked, you can just slap the files into an unsigned tar and it will flash fine with odin (bootloader cant be downgraded tho), but you will have to unlock bootloader and the binary version wont be downgraded just ignored

NigrumTredecim said:
its only blocked when the bootloader is locked, you can just slap the files into an unsigned tar and it will flash fine with odin (bootloader cant be downgraded tho), but you will have to unlock bootloader and the binary version wont be downgraded just ignored
Click to expand...
Click to collapse

NigrumTredecim said:
its only blocked when the bootloader is locked, you can just slap the files into an unsigned tar and it will flash fine with odin (bootloader cant be downgraded tho), but you will have to unlock bootloader and the binary version wont be downgraded just ignored
Click to expand...
Click to collapse
My bootloader is already unlocked. haven't tried downgrading through ODIN, as this is my Daily driver Phone, but i'dd love to get GearVR back. The phone is fully unlocked, with custom kernel, as per my Signature ... So (according to you) I should be able to downgrade to G975FXXSEFUL1 without error through ODIN? despite everyone claiming it can't be done? (I realise that the bootloader binary can't be downgraded, but ODIN/Download mode checks everything. Bootloader, kernel, etc.. no?)
What do you mean with "unsigned tar"?
side question: What about kernel? could I reuse/reflash (from TWRP) my current kernel (Ambasadii HVJ5, android 12) as it is pre-patched with latest magisk, on an older android 11 rom?

Pandoriaantje said:
My bootloader is already unlocked. haven't tried downgrading through ODIN, as this is my Daily driver Phone, but i'dd love to get GearVR back. The phone is fully unlocked, with custom kernel, as per my Signature ... So (according to you) I should be able to downgrade to G975FXXSEFUL1 without error through ODIN? despite everyone claiming it can't be done? (I realise that the bootloader binary can't be downgraded, but ODIN/Download mode checks everything. Bootloader, kernel, etc.. no?)
What do you mean with "unsigned tar"?
side question: What about kernel? could I reuse/reflash (from TWRP) my current kernel (Ambasadii HVJ5, android 12) as it is pre-patched with latest magisk, on an older android 11 rom?
Click to expand...
Click to collapse
unpack the stock tar.md5 using 7zip or some tool and repack it into a normal .tar, to my knowledge odin only checks the binary of original unmodified tar.md5 files like they come from samsung (my newest samsung is from 2017 so that may not be true anymore but it should still be)
for the kernel question i dont really know as i run android 8 with a modded stock kernel

NigrumTredecim said:
unpack the stock tar.md5 using 7zip or some tool and repack it into a normal .tar, to my knowledge odin only checks the binary of original unmodified tar.md5 files like they come from samsung (my newest samsung is from 2017 so that may not be true anymore but it should still be)
for the kernel question i dont really know as i run android 8 with a modded stock kernel
Click to expand...
Click to collapse
Any updates on this process, i would also give it a try if it works out.

crucknova said:
Any updates on this process, i would also give it a try if it works out.
Click to expand...
Click to collapse
not really, my newest samsung is an a5 2017 (where this process works fine)
but it should work, downside is that your bootloader needs to be unlocked as you build you own unsigned flashfile
EDIT: i cant get it to work anymore even tho thats how i did it the first time, flashing using a custom recovery will work tho if thats an option for you
QUICK TUTORIAL
1: download your desired stock firmware
2: extract AP****.tar.md5 (basically just a normal tar with signatures at the end use 7zip or any other program you know)
3: repack boot.img system.img vendor.img (vendor.img may not be there depending on the android version) into an uncompressed tar (using 7zip or any other program)
4: flash said tar using odin
you could also manually flash the image files using heimdall without repacking into an tar

NigrumTredecim said:
not really, my newest samsung is an a5 2017 (where this process works fine)
but it should work, downside is that your bootloader needs to be unlocked as you build you own unsigned flashfile
QUICK TUTORIAL
1: download your desired stock firmware
2: extract AP****.tar.md5 (basically just a normal tar with signatures at the end use 7zip or any other program you know)
3: repack boot.img system.img vendor.img (vendor.img may not be there depending on the android version) into an uncompressed tar (using 7zip or any other program)
4: flash said tar using odin
you could also manually flash the image files using heimdall without repacking into an tar
Click to expand...
Click to collapse
Thanks for the reply and a quick tutorial
NigrumTredecim​i have an s10 plus and a m30, im a bit hesirtant on trying it on s10 plus, but i will try the process on m30, as i need to downgrade it as well!
can you give me an more detailed tutorial on the 3rd step which includes repacking the boot.img system.img vendor.img, should i delete everything except these 3 and repack or what!
Thank you

download lz4 https://github.com/lz4/lz4/releases and drag and drop your .img.lz4 files onto the exe to get the img files
AAAAAAAAAAAAAAA i cant get it to work even though thats how i did it before already, using a custom recovery to flash the images will definitely work, so thats an option for you thats easier just unpack the .img.lz4 and skip the rest and flash using a custom recovery
just leaving the rest here in case somebody wants to find where i made the oopsie here
select your files in 7zip and then click the green plus in the top left corner
then pick tar in the format dropdown menu and then click ok to create the archive
then open said tar with odin

NigrumTredecim said:
download lz4 https://github.com/lz4/lz4/releases and drag and drop your .img.lz4 files onto the exe to get the img files
AAAAAAAAAAAAAAA i cant get it to work even though thats how i did it before already, using a custom recovery to flash the images will definitely work, so thats an option for you thats easier just unpack the .img.lz4 and skip the rest and flash using a custom recovery
just leaving the rest here in case somebody wants to find where i made the oopsie here
select your files in 7zip and then click the green plus in the top left corner
then pick tar in the format dropdown menu and then click ok to create the archive
then open said tar with odin
Click to expand...
Click to collapse
if i do a custom recovery the knox would trip and i wont be able to use the samsung pay. which i use a lot for payments. And thanks for your support dude.