You mean your fingerprint reader is working? Can you add fingerprints?
[ROM] SM-T825 TWEAKED.........................[rom] sm-t825 tweaked.
- Thread starter rorymc928
- Start date
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:
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
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
Glad I could be helpful. And thanks to you for the rom, running smoothly on my tab[emoji846]
Last edited:
I had uploaded the file must have overlooked posting the link....
https://androidfilehost.com/?fid=1899786940962579621
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
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:
Late reply,
2 possibilities, use the latest odin, or
Corrupted file, try re download from the op,
Let me know how it works
i download the file again , and upgrade my odin from 3.12 to 3.13 , it worked fine
fingerprint working
ty so much and plz help me with set selinux to permissive
Last edited:
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
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:
i really appreciate it , ty u so much for ur answer
Make sure you let us know how it goes, it often helps others who strike the problem
Hello,
Is there a link with instructions to flash this rom corectly from stock oreo?
Is there a link with instructions to flash this rom corectly from stock oreo?
Now from official SH9 Pie, please?
I just need few words in correct order (twrp, odin, bootloader, etc. ), so I don't brick my tablet.
If you're on stock pie just flash from twrp you will only need bootloader coming from oreo
For me this ROM is not debloated, all the apps from the original are there.
Gravitybox is so weak in Pie, but i found an app that adds some things missing: Firefds-kit
https://forum.xda-developers.com/xposed/modules/xposed-firefds-kit-customization-t3908114
Gravitybox is so weak in Pie, but i found an app that adds some things missing: Firefds-kit
https://forum.xda-developers.com/xposed/modules/xposed-firefds-kit-customization-t3908114
Last edited: