Database Develop

[Q] [RESOLVED] DroidSansFallback-htc.ttf replaced by the original when phone restarts

Hi All,
Last week I bought this HTC one, after using iphones for many years. First I loved the phone and I was so annoyed after realizing that it doesn't support my native language "Sinhalese".
So after some trouble, I rooted the phone and replaced the DroidSansFallback-htc.ttf with a Sinhala ttf file which I took from a Samsung phone. I was using Root Explorer App. Wallah!! it was rendering everything fine. :laugh:
The happiness did not last long, after I realized that every time I restart the phone DroidSansFallback-htc.ttf gets replaced with the original. So everytime I restart, I have to replace the file.
Would anyone be able to give a solution for this? Top of my head, would flashing the phone by clockworkmod with a .zip with my DroidSansFallback-htc.ttf fix my problem?
Also what's the reason for this? My friend's got a Samsung S4 with fresh Kit Kat installed in it. And it doesn't do this.
Thanks in advance for your opinion guys.
uadissa
(HTC One; Android 4.3; Rooted)

uadissa said:
Hi All,
Last week I bought this HTC one, after using iphones for many years. First I loved the phone and I was so annoyed after realizing that it doesn't support my native language "Sinhalese".
So after some trouble I rooted the phone and replaced the DroidSansFallback-htc.ttf with a Sinhala ttf file which I took from a Samsung phone. Wallah!! it was rendering everything fine. :laugh:
The happiness did not last long, after I realized that every time I restart the phone DroidSansFallback-htc.ttf gets replaced with the original. So everytime I restart, I have to replace the file.
Would anyone be able to give a solution for this? Top of my head, would flashing the phone by clockworkmod with a .zip with my DroidSansFallback-htc.ttf fix my problem?
Also what's the reason for this? My friend's got a Samsung S4 with fresh Kit Kat installed in it. And it doesn't do this.
Thanks in advance for your opinion guys.
uadissa
(HTC One; Android 4.3; Rooted)
Click to expand...
Click to collapse
how are you 'installing' the sinhala font?

Re
cr1960 said:
how are you 'installing' the sinhala font?
Click to expand...
Click to collapse
Used the Root explorer app to copy and replace the file.

uadissa said:
Used the Root explorer app to copy and replace the file.
Click to expand...
Click to collapse
in system>fonts?

Re
cr1960 said:
in system>fonts?
Click to expand...
Click to collapse
Correct.

uadissa said:
Correct.
Click to expand...
Click to collapse
which rom are you running?
I find easiest way for me is to change the font in the rom zip before flashing the rom. no problems with things not 'sticking'.

Flash the entire ROM?
cr1960 said:
which rom are you running?
I find easiest way for me is to change the font in the rom zip before flashing the rom. no problems with things not 'sticking'.
Click to expand...
Click to collapse
I'm still using the stock ROM with OS ver 4.3. You mean flash the entire rom after changing the DroidSansFallback-htc.ttf in the ROM zip file?
Can't I just flash the Fallback font without flashing the entire ROM?

uadissa said:
I'm still using the stock ROM with OS ver 4.3. You mean flash the entire rom after changing the DroidSansFallback-htc.ttf in the ROM zip file?
Can't I just flash the Fallback font without flashing the entire ROM?
Click to expand...
Click to collapse
did you unlock bootloader and flash a custom rom, or just unlock bootloader?
you need to have a rooted rom to change stuff like fonts etc. if you want the changes to stick.

Flash with a fresh new ROM
Since still I'm only one week after buying the phone, bit reluctant to flash it with a fresh new ROM

Phone is rooted
cr1960 said:
did you unlock bootloader and flash a custom rom, or just unlock bootloader?
you need to have a rooted rom to change stuff like fonts etc. if you want the changes to stick.
Click to expand...
Click to collapse
Yes I have unlocked the phone and rooted the phone after installing TeamWin Recovery. So now my rom is rooted. But it still has the stock ROM in it.
would you be able to explain me bit more on what you meant by
change the font in the rom zip
Click to expand...
Click to collapse
.
you meant download a customer ROM. edit it with my new font and flash entire ROM? or correct me if I'm wrong.
thanks

RESOLVED
I was able to resolve this issue easier than expected. This is what I did.
1. Boot the phone in to the Recovery mode( I have TWRP recovery installed)
2. Connected the phone to PC
3. From PC command prompt access a phone shell using I]adb shell[/I]
4. mount /system
5. Changed the properties like user, group and access permissions of my DroidSansFallback-htc.ttf to match the file in ROM's /system/fonts
6. Copy my DroidSansFallback-htc.ttf which has sinhala to /system/fonts( I made sure my original file was backed up)
7. umount /system
8. Exit from recovery and reboot
All works well :laugh::laugh:

uadissa said:
I was able to resolve this issue easier than expected. This is what I did.
1. Boot the phone in to the Recovery mode( I have TWRP recovery installed)
2. Connected the phone to PC
3. From PC command prompt access a phone shell using I]adb shell[/I]
4. mount /system
5. Changed the properties like user, group and access permissions of my DroidSansFallback-htc.ttf to match the file in ROM's /system/fonts
6. Copy my DroidSansFallback-htc.ttf which has sinhala to /system/fonts( I made sure my original file was backed up)
7. umount /system
8. Exit from recovery and reboot
All works well :laugh::laugh:
Click to expand...
Click to collapse
glad you got it sorted.
there is a difference between being unlocked and running a rooted rom. unlocked means you can install a custom recovery which then means you can flash roms. the rom contains 'files' which provide the ability to change things, which unlocking the bootloader and flashing a custom recovery do not. if you were running a custom rom, simply replacing the font using root explorer would have worked the way you wanted without having to use adb commands.

I believe the phone is rooted.
cr1960 said:
glad you got it sorted.
there is a difference between being unlocked and running a rooted rom. unlocked means you can install a custom recovery which then means you can flash roms. the rom contains 'files' which provide the ability to change things, which unlocking the bootloader and flashing a custom recovery do not. if you were running a custom rom, simply replacing the font using root explorer would have worked the way you wanted without having to use adb commands.
Click to expand...
Click to collapse
thanks for your comment. from all these I'm learning because i'm little new to android.
However I still believe my ROM OS is rooted. Because
1. After installing the TWRP custom recovery I installed SuperUser.zip by Koush to root the ROM
2. When I run root explorer it allows me to replace files into System folders with root access( Super User).
HTC has their own HTC Sense thing running on top of Android. Can that be replacing the system folders every-time it restarts? which is not happening in other phones.
if you were running a custom rom, simply replacing the font using root explorer would have worked
Click to expand...
Click to collapse
Yes I would have fixed but I was only running my stock OS rooted.

uadissa said:
thanks for your comment. from all these I'm learning because i'm little new to android.
However I still believe my ROM OS is rooted. Because
1. After installing the TWRP custom recovery I installed SuperUser.zip by Koush to root the ROM
2. When I run root explorer it allows me to replace files into System folders with root access( Super User).
HTC has their own HTC Sense thing running on top of Android. Can that be replacing the system folders every-time it restarts?
Click to expand...
Click to collapse
you need an insecure kernel .. thats why he's recommending you just flash a rom, it's much simpler

Thanks
clsA said:
you need an insecure kernel .. thats why he's recommending you just flash a rom, it's much simpler
Click to expand...
Click to collapse
But I had a insecure kernal. That's why I had root access when I was in adbd shell and it allowed me to replace files into /system.

uadissa said:
But I had a insecure kernal. That's why I had root access when I was in adbd shell and it allowed me to replace files into /system.
Click to expand...
Click to collapse
nope
this is from ARHD
ROM details:
Removed software (CPU) rendering - full Snapdragon 600 (GPU) rendering
Fully optimized and tweaked
Root access
Unsecured boot.img
Newest BusyBox
RAM optimizations
System signatures check enabled for system security and safety
Improved virtual memory management
Speed optimizations
Enabled GPU UI rendering
Data, cache and system partitions mounting tweaks
Bloatware applications removed
All /system applications updated to latest available
All /data applications updated to latest available
Improved CPU governors performance
Most optimal system scheduler
Disabled kernel debugging for better performance
Zipaligned (Improved RAM management)
Zipalign on boot (for user applications on data partition)
Fully de-odexed
init.d scripts (BusyBox run-parts) support
Auto init.d permissions set on boot
sysro/sysrw commands support
Excellent battery life!
Improved EXT4 performance
OpenVPN support
Most up-to-date system files permissions
Adobe Flash Player support
Support almost 24h a day
...and many more!
Click to expand...
Click to collapse
you don't get all those things just by being Root

Something about TWRP recovery

Hi guys, I have got a very urgent problem right now, and hope someone can help me out...I am currently using a HTC One M7, and I used the TWRP recovery and the official bootloader or something rooted my phone, the reason why I need root it is that i need a app move into the system apps which may be easier in using it. And after I moved the app into the system apps using Root Explorer and then reboot my phone, the app just disappeared. After tried many times...I think it is because of the twrp just wipe it... do u guys have a method to solve this problem?...really...pls help me out!!

luvu4evermore said:
Hi guys, I have got a very urgent problem right now, and hope someone can help me out...I am currently using a HTC One M7, and I used the TWRP recovery and the official bootloader or something rooted my phone, the reason why I need root it is that i need a app move into the system apps which may be easier in using it. And after I moved the app into the system apps using Root Explorer and then reboot my phone, the app just disappeared. After tried many times...I think it is because of the twrp just wipe it... do u guys have a method to solve this problem?...really...pls help me out!!
Click to expand...
Click to collapse
This is not a twrp issue, /system partition is write-protected by the stock kernel, every changes made in the /system partition will be reverted after a reboot. If you want to be able to write to /system when booted in the rom, you'll need a custom kernel with write-protection disabled (pretty much all custom kernels here have this). The other option is to make the changes you want in your /system partition before the stock kernel boots, so using the embedded file manager of twrp recovery for example.
If you want to use a custom kernel, you must choose one that works with your rom type and version. For example, ElementalX kernel will only works for Sense or GPE rom (stock or custom). The version of ElementalX required depends on your android version so newer doesn't mean better, you need the right one. Flashing a custom recovery is done using twrp recovery. When installing the custom kernel, you can choose the features you want to be installed so if you don't want a specific feature that the kernel offers, its not a problem. The write-protection is removed by default.
If using the twrp file manger, boot in twrp select "advanced" ---> "file manager"
Then to move a file, select it (tap on it) then it will open another menu. Select "move" then select the location you want to move it to. There is also a chmod menu to edit the files permissions.

alray said:
This is not a twrp issue, /system partition is write-protected by the stock kernel, every changes made in the /system partition will be reverted after a reboot. If you want to be able to write to /system when booted in the rom, you'll need a custom kernel with write-protection disabled (pretty much all custom kernels here have this). The other option is to make the changes you want in your /system partition before the stock kernel boots, so using the embedded file manager of twrp recovery for example.
Click to expand...
Click to collapse
Oh, thanks for answering me~ uh, can u be more specific about how to do that? about the kernel thing? I never did this before and actually this is just my second time to root a phone and try to move an app into system app (as last time i did so there is no such a problem...) Also, about the twrp recovery file manager, tried that one yesterday, and it did not show the " app" folder under the system one, which means i just cannot move it using the twrp file manager...

luvu4evermore said:
Oh, thanks for answering me~ uh, can u be more specific about how to do that? about the kernel thing? I never did this before and actually this is just my second time to root a phone and try to move an app into system app (as last time i did so there is no such a problem...) Also, about the twrp recovery file manager, tried that one yesterday, and it did not show the " app" folder under the system one, which means i just cannot move it using the twrp file manager...
Click to expand...
Click to collapse
see my post above (edited while you were replying)
You can also use aroma file manager within twrp recovery
here a nice xda-video about both twrp file manger and aroma file manager

alray said:
see my post above (edited while you were replying)
You can also use aroma file manager within twrp recovery
here a nice xda-video about both twrp file manger and aroma file manager
Click to expand...
Click to collapse
OMFG!!! Finally I made it! I watched the video and find out that I did not mount the permission to the TWRP file manager! Thank you so much!!!

luvu4evermore said:
OMFG!!! Finally I made it! I watched the video and find out that I did not mount the permission to the TWRP file manager! Thank you so much!!!
Click to expand...
Click to collapse
Yep sorry, should have mentioned that, you always have to mount the partition you want to access when using a recovery. Some are mounted by default, but /system isn't.

alray said:
Yep sorry, should have mentioned that, you always have to mount the partition you want to access to when using a recovery.
Click to expand...
Click to collapse
Nah, still thanks a lot,

luvu4evermore said:
Nah, still thanks a lot,
Click to expand...
Click to collapse
you're welcome :good:

[Root][SM-T380][SM-T385] Samsung Tab A 8.0 (2017) Root Tutorial

Method was kindly shown to me by user Mefody in answer to a thread I posted.
Rooting SM-T380/T385 via Magisk Manager APK v.5.5.3 & Magisk 15.2:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet Magisk Manager APK.
4. Put "boot.img" on SDCARD.
5. Run Magisk Manager, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point Magisk Manager to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google registry will be wiped.
11. After wiping & rebooting install Magisk Manager APK again... And YEAH!!! You got root!

Thanks for creating this thread. I used the original thread to root my tab, so seeing this as its own thing will be helpful to a lot of people.

a.brooding.mage said:
Thanks for creating this thread. I used the original thread to root my tab, so seeing this as its own thing will be helpful to a lot of people.
Click to expand...
Click to collapse
Now all we need is TWRP and we'll have Xposed and custom rom support

shahmir_k said:
Now all we need is TWRP and we'll have Xposed and custom rom support
Click to expand...
Click to collapse
For TWRP: https://forum.xda-developers.com/galaxy-tab-a/development/recovery-t3426560

I will get this tab.
BTW, can it install Samsung Game Tuner?

mingkee said:
I will get this tab.
BTW, can it install Samsung Game Tuner?
Click to expand...
Click to collapse
Yes... Game Tuner installs & wokrs good.

Could you clarify on these two steps?
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.

Nerd10 said:
Could you clarify on these two steps?
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
Click to expand...
Click to collapse
You have to open the stock firmware with an archive manager like WinRar or 7zip. Inside you should find an AP-Block folder. Inside of that should be your boot.img file

shahmir_k said:
You have to open the stock firmware with an archive manager like WinRar or 7zip. Inside you should find an AP-Block folder. Inside of that should be your boot.img file
Click to expand...
Click to collapse
Thanks, where can I find the stock firmwares?

Here is another problem
Is OEM unlock in Developer Section required to install patched kernel and TWRP with Odin?
I can't find it even it's updated.

Does anybody know if this rooting method will work with T-585 on Android 7.0 (January 2018 update)? I guess KNOX will be triggered, right?
Yours
WeT-Klb

I say the root is TOTALLY FALSE!!!
I have been waiting for two week and there's no update to enable OEM Unlock option.
I have returned the unit with restocking fee.

mingkee said:
I say the root is TOTALLY FALSE!!!
I have been waiting for two week and there's no update to enable OEM Unlock option.
I have returned the unit with restocking fee.
Click to expand...
Click to collapse
Have you tried this method even without the option in developer settings to OEM Unlock? On my SM-T350, I don't have the option to OEM unlock either. But I can still root and install TWRP anyways.

Delgoth said:
Have you tried this method even without the option in developer settings to OEM Unlock? On my SM-T350, I don't have the option to OEM unlock either. But I can still root and install TWRP anyways.
Click to expand...
Click to collapse
I tried to flash modified kernel or TWRP with Odin and I got error
Only official software can be installed.

Perhaps someone could provide boot.img files and links here?
I for instance found no matching firmwares for mine. The one that had both matching versions numbers, said it was for Cellular US. This is a wifi only model. Confused
Thanks

Barsky said:
Perhaps someone could provide boot.img files and links here?
I for instance found no matching firmwares for mine. The one that had both matching versions numbers, said it was for Cellular US. This is a wifi only model. Confused
Thanks
Click to expand...
Click to collapse
I have that original boot.img and magisk modified one.

There's a 7 days waiting period after you turned it on the first time regardless reboot or not.
I will make a instruction how to root and I will post kernel and modified kernel.

mingkee said:
I have that original boot.img and magisk modified one.
Click to expand...
Click to collapse
I didn't realize it was so effortless to pull the boot.img out. BUt, until I have that oem unlock option in there, doesn't matter.
Come on, 14 days

Finally, mine has successfully rooted with Magisk.
I will post a guide.

Trouble rooting SM-t380
shahmir_k said:
Method was kindly shown to me by user Mefody in answer to a thread I posted.
Rooting SM-T380/T385 via Magisk Manager APK v.5.5.3 & Magisk 15.2:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet Magisk Manager APK.
4. Put "boot.img" on SDCARD.
5. Run Magisk Manager, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point Magisk Manager to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google registry will be wiped.
11. After wiping & rebooting install Magisk Manager APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
When I try to flash the archived boot.tar via Odin it just hangs and sits there. Any help would be much appreciated. Thank You.

(Guide)Root +Busybox + OEM Fix + EFS backup Note 9 N960F/FD/N Exynos only

How to ROOT Samsung Note 9 N960F/FD/N
Before trying make sure that flashing said file,
- Warranty will be void
- You won't be able to use Secure Folder/Samsung Pay forever (or may be more)
- May lose OEM unlock option
- Backup important stuff as you need to full wipe device (including internal storage)
DO IT ON YOUR OWN RISK
What is OEM fix?
Since Note8 samsung have introduced OEM unlock control remotely and flashing any custom binary removes OEM unlock option and rebooting in this state it ends with custom binary error and have to flash stock firmware. OEM patch will retain OEM unlock option in spite of having custom recovery. If you are not sure your device have OEM issue then there is nothing wrong to use 'OEM patch' option.
If you don't have OEM unlock option out of box then it may appear after 7 days, before this nothing can be done. Also this suggest, you have OEM affected device.
Click to expand...
Click to collapse
METHOD 1 : Root with TWRP Also works on Android Q (RECOMMENDED)
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (Currently no workaround for those who doesn't have this option)
3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card
4.Download TWRP for N9
5.Switch Off device
6.Press Vol down + Bixby and connect to PC to reboot to download mode, press volume up when asked to continue to download mode
7.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
8.Select TWRP (tar image) with AP tab of Odin and Start
9.Once Successfully flashed, you will see 'Passed' in Odin tab
10.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
11.Select to allow modification
12.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
13.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
14A (If you are on Pie)
.Now select Install and navigate path to Ext SD card - N960_root_OEM_issue_devices_V*.zip, you have copied earlier, select desired root method and select 'OEM Patch' option if your device have OEM issue. If you are not sure about this then better select 'OEM Patch', this will prevent losing OEM unlock option and so prevent 'custom binary error'
OR
14B (If you are on Android Q)
Flash Latest magisk & then DM-VERITY, FORCED ENCRYPTION, AND DISC QUOTA DISABLER
15.Once flash successfully finish, Reboot to System
Magisk app may appear in drawer after one reboot.
Important Note for Pie - There will be OEM unlock option there in developer setting but it will be disabled and can not enabled, this is because of it is hacked. Just ignore it. You can not boot device with TWRP if it is really disabled. Also If magisk app may not appear then simply download Magisk_for_Pie.apk from below attachement and install as regular app.
Open settings - Developer option - Look for OEM Unlock option. If it is there, it is safe to reboot device.
Credits and Thanks goes to BlackMesa123 for OEM fix
Click to expand...
Click to collapse
METHOD 2: Root with Stock Recovery (NOT SAFE ON OEM ISSUE DEVICES)
1.Download Magisk.apk attached below
2.Download Prerooted_N960_Exynos.zip (For Oreo Only)
3. Keep stock ROM file ready in case this doesn't work
4.Download De-Knox tool attached below (optional)
Installation :
- Enable OEM unlock
- Reboot to Download mode
(Here method changed - Switch off device - connect top PC - Press Vol down + Bixby)
- Extract (Unzip) Patched kernel - you will get N960F_kernel_PreRoot_RH5_DrKetan.tar.md5
Flash it using latest Odin with AP tab
- Once file successfully flashed, device will reboot and ask to reset device.
- Reset device, keep patience, device may take 5-7 minutes to boot.
- Once device reboot - Install Magisk manager apk manually
- install De-Knox tool apk and click icon, this will remove all knox app (no more useful on rooted device). This will also remove security messages
YOU MUST BACKUP EFS AS SOON AS ROOT DEVICE, and copy it to safer place,
Click to expand...
Click to collapse
14.01.2019 - Added support for Pie
Credit and Thanks to breakersvd for ril patch (defex fix) and @topjohnwu for magisk
EFS Backup Tool
As soon as you root device, you must make backup of EFS and must store a copy of backup to safer place like on cloud and on a PC
XDA version - Free version, complimentary tools for XDA users attached below.
Play Store version - You can buy from Play store to support us.
Both version make same form of backup and have no difference, Paid version have additional function to make Auto Backup when you change the ROM

So if we do lose OEM unlock, this means we will never be able to unlock the bootloader later on down the road, right?
I love your work and look forward to it every time I get a phone.

chrispyutec said:
So if we do lose OEM unlock, this means we will never be able to unlock the bootloader later on down the road, right?
I love your work and look forward to it every time I get a phone.
Click to expand...
Click to collapse
No, on previous device you get oem unlock option back again after 7 days
Though this is csc related and not all users will lose this option. Usually if your device have unlock option out of box then mostly you won't lose it. Though if we get root working we may need move forward to fix this

When its a kernel parched with normal magisk it will break ril because samsung added defex to the galaxy n9. I have only a semi working root on mine with ril

Here you see the half working root with ril. Normal magisk will break ril like i said

geiti94 said:
Here you see the half working root with ril. Normal magisk will break ril like i said
Click to expand...
Click to collapse
Have you tried hex patch similar issue reported on A series? Tried TWRP? Or you are waiting for kernel source. We badly needed it now.

dr.ketan said:
Have you tried hex patch similar issue reported on A series? Tried TWRP? Or you are waiting for kernel source. We badly needed it now.
Click to expand...
Click to collapse
Twrp with stock zimage dont boots and with compiled img from s9+ source same thats why i am waiting soueces. Twrp tree is allready finished and defconfig too. Only source is missing but sammy dont released it today. And n9 defex is different from a8 one

geiti94 said:
When its a kernel parched with normal magisk it will break ril because samsung added defex to the galaxy n9. I have only a semi working root on mine with ril
Click to expand...
Click to collapse
Wow! Wtf Samsung!!!??

How did you manage that half working root ?

siriom said:
How did you manage that half working root ?
Click to expand...
Click to collapse
Its a modded magisk where magisk hide and magisk manager gives fc. That means root is all time enabled and i dont need to press confirm and works only with some apps. For example es file explorer cant get root and titanium backup same

geiti94 said:
Its a modded magisk where magisk hide and magisk manager gives fc. That means root is all time enabled and i dont need to press confirm and works only with some apps. For example es file explorer cant get root and titanium backup same
Click to expand...
Click to collapse
If you to open a prompt and su ? would that work ?
I would like to mount or chgroot ....
This obviously blows up the whole knox deal right ?

geiti94 said:
Twrp with stock zimage dont boots and with compiled img from s9+ source same thats why i am waiting soueces. Twrp tree is allready finished and defconfig too. Only source is missing but sammy dont released it today. And n9 defex is different from a8 one
Click to expand...
Click to collapse
It's up now

FINALLY ROOTED NOTE9
May be Worlds first fully rooted Note9
Big thanks goes to @breakersvd for his special hex fix for recent samsung devices.

I will re-write first post with new files soo

Amazing @dr.ketan ??

Amazing @dr.ketan ??

Really appreciate this! Just to confirm, by rooting we will lose Secure Folder and Samsung Pay only (for now)?
If I unroot, will I receive ota?

Plzz let us know how to fully root note 9 dr.ketan
Plzz update file and root process .. i am very excited to root my note 9 .. dr. Ketan u r the best.. love ur work????

Nasty_z said:
Really appreciate this! Just to confirm, by rooting we will lose Secure Folder and Samsung Pay only (for now)?
If I unroot, will I receive ota?
Click to expand...
Click to collapse
You will lose secure folder and Samsung pay forever even if you unroot. You cannot undo this once done

pankajgavri said:
You will lose secure folder and Samsung pay forever even if you unroot. You cannot undo this once done
Click to expand...
Click to collapse
Yes, I know. I asked about ota after unrooting. I can still get ota if I unroot?

[Root][SM-T590] Samsung Galaxy Tab A 10.5 (2018) root tutorial

Disclaimer: Your warranty will be void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Hi.
Based on the feedback from this thread, the following steps can be used to aquire root on the SM-T590. The process is quite similar to rooting other devices by using Magisk. It might also work on other versions of the SM-T59x family, which can be OEM unlocked (sorry Verizon users).
Obtain the boot image
Get the firmware that matches the version installed on your device. This is important, otherwise you can easily end up in a bootloop.
Extract the AP tar.md5 file, e.g. "AP_T590XXU2ARJ1_CL14463952_QB20043720_REV00_user_low_ship_MULTI_CERT_meta.tar.md5".
Upon the extracted files, there is a file called boot.img.lz4. Extract it. Important: Most standard compression tools, e.g. 7-zip, are unable to extract lz4 compression ccorrectly. Use the offical lz4 binary from your Linux distribution or get the Windows version here. Once extracted, you should have a file called boot.img.
Patch the boot image
Copy the boot.img file to your device.
Download and install the Magisk Manager apk from the offical Magisk Thread.
In Magisk Manager settings, set the image format to "img.tar".
Enable the "Keep AVB2.0/dm-verity" in the Magisk main screen.
Hit "Install" and select "Patch boot image".
Select the boot image copied previously to your device.
Once finished, the patched image will be located in the Download directory on the internal storage.
Copy the patched image back to your PC.
Unlock and flash
Go into settings and enable developer settings.
In the developer settings, select OEM unlock, read the help text and enable the unlock, if you consent.
Once the device is factory reset and rebooted, turn the device off.
Boot the tablet into download mode.
Flash the patched boot image with Odin in the AP-slot
Reboot, Install Magisk Manager apk again and check if root is available.
Have fun.
Thanks to @gscollier, @airmaxx23 and @EinsamerSpieler for testing.

Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn

J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology

J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
did you find a solution?

stupid question
I know this is a dumb question but where do you get the firmware....
Also was wondering if that reboot thing is still an issue.
I'll still root, I would like to try the LineageOS, eventually... how well does this work with Android apps/F-droid?
Update: still looking for confirmation on which boot image to use... guess you can't do a backup before flashing like you used to be able to do.
I installed heimdall and adb both seem to work
heimdall instructions

User848 said:
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
Click to expand...
Click to collapse
the same happens to me.
I also tried removing some microsoft apps with Titanium, but after removing the excel, it goes to a kernel panic...
And then there's the "Security notice" from "SecurityLogAgent" notifications (unauthorised actions have been detected, unauthorised access to a secured area)

any solutions, followed steps but no root

I have the same problem Root is present but once i try to rename a file in /system/app, the device reboots.
Using SM-T590 with canadian image:T590XXU2ASC1
Using Magisk version V7.1.2(208) - V19.1 (19100)

I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.

Quick help please, I have the patched boot image on my pc but when I click the AP slot on odin it doesnt detect it only finds tar, md5 files etc. in the settings i cant change the format to .tar there is no option.

IET_DEMO said:
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Click to expand...
Click to collapse
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time

mingkee said:
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
Click to expand...
Click to collapse
Well I did it on android 8.1.0, seems like it work on Oreo too

IET_DEMO said:
Well I did it on android 8.1.0, seems like it work on Oreo too
Click to expand...
Click to collapse
How about Titanium Backup?
It works on rooted T510

mingkee said:
How about Titanium Backup?
It works on rooted T510
Click to expand...
Click to collapse
I dont have or use Titanium Backup, I usually clone my devices with twrp backup

There needs to be a better option that works without the current issues when rooting. You either end up with reboots or can not log in to Samsung account at all

For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.

kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Would it work on 595? Bootloaders should be the same without boot loop?

vq8acsxht said:
Would it work on 595? Bootloaders should be the same without boot loop?
Click to expand...
Click to collapse
I honestly don't know as I don't have a 595. I took a chance on mine and it worked

kidkrooks said:
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
Click to expand...
Click to collapse
Mine is on it's way. I will try it when I get it. I think bootloaders should be same in in both 590/595.

kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Does this still have "Modifying system files leads to reboot" issue or it's solved ?