[ROM] SM-T825 TWEAKED.........................[rom] sm-t825 tweaked.

Search This thread

ZPeppe

Member
Jun 17, 2013
20
4
Yes without any issue. Flashing the new bootloader did the trick for me, even with a clean installation of the rom. Sorry, I haven't been clear enough in the last post.
 
Last edited:
  • Like
Reactions: rorymc928

rorymc928

Senior Member
Jan 28, 2010
617
587
Yes without any issue. Flashing the new bootloader did the trick for me, even with a clean installation of the rom. Sorry, I haven't been clear enough in the last post.
That's good, my last flash was straight over a restored oreo and have a broken fingerprint reader , I might get a chance to try just the bootloader as a test tonight
 

rorymc928

Senior Member
Jan 28, 2010
617
587
Yes without any issue. Flashing the new bootloader did the trick for me, even with a clean installation of the rom. Sorry, I haven't been clear enough in the last post.

Thanks for your insight....

That's confirmed now by me, same effect.

So for others, a dirty flash over 4.0 will work it will boot, but the bootloader update is required to keep the fingerprint reader working.

Thanks to all for your involvement in sorting this
 
  • Like
Reactions: ZPeppe

Lexycompany

Member
Apr 8, 2017
6
2
NY
i cant flash bl

i flashed the rom , and everything working fine except fingerprint
ty for ur awesome rom
and please could u set the selinux to permissive instead of forcing?, or if i u know script or kernel that can do that please tell me(i tried https://forum.xda-developers.com/ga.../sm-t825-flash-kernel-0-1-permissive-t3692328 and its get stuck on boot loop)

when i try to flash bl in odin i get this

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn.lz4
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

plz help me , what should i do
 
Last edited:

rorymc928

Senior Member
Jan 28, 2010
617
587
i flashed the rom , and everything working fine except fingerprint
ty for ur awesome rom
and please could u set the selinux to permissive instead of forcing?, or if i u know script or kernel that can do that please tell me(i tried https://forum.xda-developers.com/ga.../sm-t825-flash-kernel-0-1-permissive-t3692328 and its get stuck on boot loop)

when i try to flash bl in odin i get this

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn.lz4
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

plz help me , what should i do

Late reply,
2 possibilities, use the latest odin, or
Corrupted file, try re download from the op,
Let me know how it works
 

Lexycompany

Member
Apr 8, 2017
6
2
NY
hi im again
dude i got serious problem , i flashed the bl and then ROM , everything looks good and working, installed riru core and edxposed , i reboot for edxposed to be enabled and then didn't boot again , and show me the custom binary warning, i couldn't go to recovery mode, all the same message, so i tried install twrp again with odin 3.13 but i get "only official released binaries are allowed to be flashed" so i download latest stock rom and install it successfully , every thing is stock and working ,
i enable debug mode and i cant see the oem lock , but when im going to download mode it says fap and oem is off , so im good i think , but there is more info like below
KG status: prenormal
qualcomm secureboot: enable
secure download: enable

i tried to flash twrp with odin again , but i get the same message "only official released binaries are allowed to be flashed", i searched and i found this
"You must have forgot to flash the RMM fix. You either have to flash the RMM disabler or flash a custom Kernel that disables it that way before the first reboot after flashing TWRP. It's a new safety feature Samsung has introduced that locks the device after anything gets flashed or modified. Unfortunately, your only option is to re-odin stock files and then wait 7 days again for OEM unlock to appear.

After you get TWRP flashed again, mke sure you flash the fix or a custom Kernel. "

1-what cuz this ? BL? Rom? or riru? gravity?
2-is this RMM fix exist for tab s3 ? and will it work?
3-should i realy wait 7 days for installing twrp ?

thank u so mush for ur awesome work
 

rorymc928

Senior Member
Jan 28, 2010
617
587
hi im again
dude i got serious problem , i flashed the bl and then ROM , everything looks good and working, installed riru core and edxposed , i reboot for edxposed to be enabled and then didn't boot again , and show me the custom binary warning, i couldn't go to recovery mode, all the same message, so i tried install twrp again with odin 3.13 but i get "only official released binaries are allowed to be flashed" so i download latest stock rom and install it successfully , every thing is stock and working ,
i enable debug mode and i cant see the oem lock , but when im going to download mode it says fap and oem is off , so im good i think , but there is more info like below
KG status: prenormal
qualcomm secureboot: enable
secure download: enable

i tried to flash twrp with odin again , but i get the same message "only official released binaries are allowed to be flashed", i searched and i found this
"You must have forgot to flash the RMM fix. You either have to flash the RMM disabler or flash a custom Kernel that disables it that way before the first reboot after flashing TWRP. It's a new safety feature Samsung has introduced that locks the device after anything gets flashed or modified. Unfortunately, your only option is to re-odin stock files and then wait 7 days again for OEM unlock to appear.

After you get TWRP flashed again, mke sure you flash the fix or a custom Kernel. "

1-what cuz this ? BL? Rom? or riru? gravity?
2-is this RMM fix exist for tab s3 ? and will it work?
3-should i realy wait 7 days for installing twrp ?

thank u so mush for ur awesome work


1. Not sure of the cause, I encountered this during my first mucking round with the firmware and rooting, it seems to be related to a subtle difference in how you flash. The most reliable way is flash the firmware, reboot.... Giving you Stock unrooted.
Check oem unlock in developer options, it should be there, I had no 7 day issue however , my galaxy s9 had the 7 day wait issue.(twice due finger trouble)
From there to get twrp and flash the rom or just plain root no encrypt, you need to flash twrp, which should be possible now, but the important thing is not to allow reboot to system. This can be done by either catching it as it reboots with the button switch, or simpler, untick" reboot" in odin (on the second menu page, return to the first page so you can watch the log of the flash), then flash twrp. It will now stay in download mode at completion.
From here press power, volume down and home together holding until it asks for reboot or download again.
Now the quick bit, volume down selects reboot first, but before it does much, just see the lights go out /screen off, swap your fingers to volume up and home key, no need for the power key as it's already trying to reboot. Once you see the script showing recovery booting, release the keys. It will boot to twrp.
Now it's necessary to format (not wipe) the data to permit mounting of the internal data in TWRP, if you check first you'll probably find data won't mount, after the format, it will.
From here you can flash the rom it will take care of rooting (magisk), and force encryption Dm-Verity,or if you wanted flash them only yourself without the rom, then reboot.

2. using the process above RMM fix is not necessary, I have never used it.

3. I did not encounter a 7 day wait on this tablet, I would expect it to be part of the stock firmware if it existed, so should be the same for all, I've used both a Korean and UK firmware on pie without it occurring, this rom is based on the UK version.

Hope that gets you through this,
Post how you get on,
Good luck.
 
Last edited:

Lexycompany

Member
Apr 8, 2017
6
2
NY
1. Not sure of the cause, I encountered this during my first mucking round with the firmware and rooting, it seems to be related to a subtle difference in how you flash. The most reliable way is flash the firmware, reboot.... Giving you Stock unrooted.
Check oem unlock in developer options, it should be there, I had no 7 day issue however , my galaxy s9 had the 7 day wait issue.(twice due finger trouble)
From there to get twrp and flash the rom or just plain root no encrypt, you need to flash twrp, which should be possible now, but the important thing is not to allow reboot to system. This can be done by either catching it as it reboots with the button switch, or simpler, untick" reboot" in odin (on the second menu page, return to the first page so you can watch the log of the flash), then flash twrp. It will now stay in download mode at completion.
From here press power, volume down and home together holding until it asks for reboot or download again.
Now the quick bit, volume down selects reboot first, but before it does much, just see the lights go out /screen off, swap your fingers to volume up and home key, no need for the power key as it's already trying to reboot. Once you see the script showing recovery booting, release the keys. It will boot to twrp.
Now it's necessary to format (not wipe) the data to permit mounting of the internal data in TWRP, if you check first you'll probably find data won't mount, after the format, it will.
From here you can flash the rom it will take care of rooting (magisk), and force encryption Dm-Verity,or if you wanted flash them only yourself without the rom, then reboot.

2. using the process above RMM fix is not necessary, I have never used it.

3. I did not encounter a 7 day wait on this tablet, I would expect it to be part of the stock firmware if it existed, so should be the same for all, I've used both a Korean and UK firmware on pie without it occurring, this rom is based on the UK version.

Hope that gets you through this,
Post how you get on,
Good luck.

i really appreciate it , ty u so much for ur answer
 
  • Like
Reactions: rorymc928

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    SM-T825 TWEAKED 5.1 ***** PIE ***** 20JUN2020

    T825_CTD1_TWEAKED_5.1_DB4_by_rorymc928

    Based on latest stock CTD1 firmware
    Tweaked, stable, zip aligned. SU/D
    Forced encryption disabled
    Deknoxed
    Debloated
    (GPU driver updated to latest adreno 313 rev 23.... returning soon)
    Busybox
    *****
    Magisk updated 20.4
    Matched edxposed version can be installed, or not, if preferred via magisk
    (note that edxposed is the new framework replacing xposed to allow use with pie, it requires a number of steps, but fairly simple, guide to follow )
    Edxposed installer
    Gravity box PIE pre installed

    Can be dirty flashed over CSH9 , or factory reset both will work. Recommend straight flash over PIE rom / CSH9, negligible benefit from wipe
    Requires bootloader update to a pie bootloader if not on pie already.
    (it will work without, but experience shows the bootloader update is required for the fingerprint reader to function )

    For edxposed......
    Xposed does not support android pie.
    However, we now have edxposed, a magisk module which does basically the same thing.
    Requirements are,
    1. Riru core. Go to magisk downloads and type in the search bar "riru" , near the top you'll see riru core, click the download and it will install and offer a reboot.
    2. Riru edxposed. Same search and you'll see riru edxposed further down 2 versions I chose sandhook, no reason but it works for me, same thing download it, it installs and offers reboot.
    3. Edxposed installer , almost identical to the xposed installer, already installed in the Rom, open it and you should find gravitybox pie version in the modules section it may require switching on.

    Advantage of edxposed is it passes safety net,..... I'm told.

    Gravity box pie is still in early development, so whilst it has quite a bit there it's still a way off being complete, some selections didn't function for me, but a lot did.

    Gravity box will still need to be switched on in edxposed modules.

    More mods to follow...

    Let me know how it goes


    ****DOWNLOADS ****
    SUPER DEBLOAT

    T825_CTD1_TWEAKED_5.1b_DB4_by_rorymc928
    Fix for encryption disable...
    https://androidfilehost.com/?fid=8889791610682887843

    T825_CTD1_TWEAKED_5.1_DB4_by_rorymc928

    Withdrawn


    *********************

    SM-T825_CSH9_TWEAKED_5.0_DB4
    https://androidfilehost.com/?fid=1899786940962579651

    Bootloader
    https://androidfilehost.com/?fid=1899786940962579621

    SM-T825 TWEAKED 4.0

    https://androidfilehost.com/?fid=1395089523397964302
    new bootloader
    https://androidfilehost.com/?fid=1395089523397964296

    SM-T825 TWEAKED 3.9 (rc)
    Magisk root
    https://androidfilehost.com/?fid=11410963190603896745

    SM-T825 TWEAKED 3.8(a)
    Magisk root
    https://www.androidfilehost.com/?fid=11410932744536994829
    Supersu
    temp removed


    SM-T825 TWEAKED 3.6s DB4 (systemless supersu)
    https://androidfilehost.com/?fid=11410932744536989439
    SM-T825 TWEAKED 3.6m DB4 (magisk)
    https://androidfilehost.com/?fid=11410932744536989437

    SM-T825 TWEAKED 3.5 DB4
    https://androidfilehost.com/?fid=1322778262903997340
    SM-T825 TWEAKED 3.3 DB3
    https://androidfilehost.com/?fid=5862345805528055090

    Debloat list
    https://androidfilehost.com/?fid=1322778262903995061

    FULL ROM...
    SM-T825 TWEAKED 3.2

    https://www.androidfilehost.com/?fid=890278863836290631


    ****************
    Previous builds
    ****************
    SM-T825 TWEAKED 2.1 02APR2018

    Based on latest ARA2 stock firmware,
    Smoother and quicker, identical tweaks to T-820 version

    Rooted
    Init d
    Deodex
    Zip aligned
    Zip align on boot
    Sqlite

    Extensive testing by kainanmaki SM-T825 user,
    ****Major credit to kainanmaki, for methodical testing, this wouldn't be here without his help. ****


    Version 2.1M2 Magisk root, systemless xposed included, best of both worlds.
    Version 2.1S2 Superuser, system xposed.
    Both with.
    Gravity box Xposed module
    3minit battery included
    attachment.php



    rovo89 and xposed, forum link below
    https://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053

    C3C076 and gravity box
    https://forum.xda-developers.com/xposed/modules/app-gravitybox-v7-0-0-tweak-box-android-t3653953

    gharrington and 3minit battery mod, please visit for a full explanation of its functions
    https://forum.xda-developers.com/showthread.php?t=2799958

    Best flashed over updated firmware, should dirty flash but tested with factory reset, so do your backups.
    Follow instructions below....


    1. If you have xposed installed,either select it off in the app or uninstall, I only selected it off.
    2. Boot to TWRP
    3. Go to wipe,and select factory data reset.
    4. Install ROM
    5. Long boot........,
    6. Ignore the xposed force close
    7. Do your normal startup load.
    8. Magisk, if that version flashed, will function at this point.
    9. If you wish to operate xposed as well,go to the xposed installer app(matched version preinstalled),open it and install the framework,which will be systemless/system. Non recovery installation works fine. It will require reboot.
    10. On Magisk version it will pass safetynet check whilst xposed is selected off by its switch,otherwise it indicates fail. So you can swap, as needed by work perhaps, with one reboot.
    11. Use gravity box module to switch off stock battery icon.

    Link below.........
    *****************************************************
    TWEAKED 2.1M2 Magisk root, systemless xposed.
    *****************************************************
    https://androidfilehost.com/?fid=746010030569966037

    ***********************************************
    TWEAKED 2.1S2 Superuser standard xposed.
    ***********************************************
    https://androidfilehost.com/?fid=818070582850504971


    TWEAKED 2.0M
    https://androidfilehost.com/?fid=890129502657594126
    8
    New rom out update to the latest firmware

    T825_CTD1_TWEAKED_5.1_DB4_by_rorymc928


    https://androidfilehost.com/?fid=8889791610682870340

    Not tested on the T825 so do all your backups, twrp, titanium, copy internal storage and please report back with your experiences.
    The T820 version is good it dirty flashed nicely over the previous rom(5.0) so that would be a good starting point.
    Have fun :D

    Ps I didn't update the bootloader on the T820 and was fine
    6
    Ok,
    Android pie version up now
    Tweaked 5.0
    I have tested bootloader requirement on the T820 , no bootloader update required.
    Based on CSH9 base, not sure yet as to backwards compatibility if you did upgrade the bootloader , though as I said it's not required
    Got myself tangled up in frp lock at one stage, suspect that was an error on my part, so make sure you have oem unlock selected, numerous dirty flashes over full pie worked fine.
    Will check a wipe then flash next.
    I see no reason it won't flash direct from bsd1 firmware or Tweaked 4.0,but make sure of your encryption state, and backup fully,and have the new bootloader at least standing by.
    Links to follow....

    SM-T825 TWEAKED 5.0 based on UK T-825 CSH9 firmware

    https://androidfilehost.com/?fid=1899786940962579651

    The T820 version has an issue with the fingerprint scanner, still debugging this.
    Recommend dirty flashing over the earlier 4.0, for the time being
    5
    Unfortunately there was an error in the last rom, leading to the encryption disable not actioning properly during install. I have built a new version which fixes the error (Tweaked 5.1b), a quick read of the T820 thread below will lay out the issue.
    Those who have flashed a Dm-Verity disable script will have already rectified the issue. If you're still on 5.0,dirty flash of the new modified rom will function now as intended without any format requirement.
    Further details in the other thread below....
    https://forum.xda-developers.com/galaxy-tab-s3/development/rom-sm-t820-tweaked-t3659433/post83020803
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone