I know I shouldn't have done this. But somehow I managed to "cut" the system fonts instead of copying them. And when I realized it, I tried to put the fonts back. but everything messed up and fonts started disappearing from every app. So I restarted the phone and boom. Stuck at Samsung boot animation.
Now, I've searched for this issue and now know that I've to replace system fonts with a genuine one for my device. So do I need to replace just the Roboto-regular.ttf or every font that was present in /system/fonts?
Secondly, I'm rooted and have Philz recovery installed. But I'm not able to use adb when phone is booting in normal mode. It says device unauthorized (I believe we need to authorize a pc for the first time).
Again, I can't push files using adb in recovery to /system/fonts because su right is not available. It says access denied.
And the data is important. So any method except RESET would be welcome.
Ok, I got it working partially. I'm able to push files to system partition. I pushed roboto regular ttf file. The phone boots now but systemui keeps on crashing. So can someone just provide me the stock fonts folder dump? I will try to push every font to see if the crashes still occur or not.
Edit: Finally solved it. What I was missing was the permissions. I was just pushing the font file but never bothered to think about permissions. So it could help someone in future. Push the font file to /system/fonts and change the permission to rw-r--r-- . I used aroma file manager for this purpose in philz recovery. I think you can also change the permission using adb.
Related
Hi all,
i often noticed people(including me) who tried to modificate their framework-res.apk resulting in boot loops(e.g. looping at white/green quietly brilliant screen).
So i tried to find out a fast way to get back to my(original) framework-res.apk without usage of recovery console each time my framwork-res.apk did not work as expected.
How it could help you:
It's a fast way to:
check out your moddings when doing numerous modifications in different versions of your modded framework-res.apk on your way to get it to work.
if you want to get back to your original/working framework-res.apk, even when it boot loops!
Click to expand...
Click to collapse
When you do numerous modifications on framework-res.apk and your modded apk leads to a boot loop you will be able to replace the current apk through e.g. the original apk.
At this boot point(boot loop screen) Android nearly finished booting and you have access on ADB commands.
What do you need to do this:
Download and extract/install QtADB from the link below:
QtADB
to replace the erroneous(current) framework-res.apk by the original or a fixed one.
Click to expand...
Click to collapse
There's no need to describe how to get a copy of your untouched framework-res.apk from device, since there are numerous tutorials around here.
Please check this tutorials to get a copy of your apk.
Please note before beating your device:
this probably will work with the most visual moddings of framework-res.apk - but i can't guarantee it works 100%.
It probably will not work when you play around with hardware or connections setting, other apk's or other stuff in other folders, so i am not responsible if it does not work.
always backup your current ROM/settings/whatever and save a copy of your untouched framework-res.apk
There is a little catch in it in comparsion with using recovery:
After you did like described, you have to set your background image and your (google) accounts anew.
But this is just a little work and it's not necessary until your framework-res.apk is doing the modded stuff correctly - or if you want to set the original framework-res.apk back.
Click to expand...
Click to collapse
So let's start to revive your original framework-res.apk.
(Of course you can use this method to push a modded to your device, to check out if your modding works):
Boot your device and let it load until you're at boot loop
(Download, extract,) run QtADB
Navigate in left window(Computer) to your copy of original framework-res.apk(e.g. in root directory of SD card, but i recommend a folder on your computer)
Navigate in right window(Phone) to device folder /system/framework/
Use in left window(Computer) context menu on your original framework-res.apk and select copy or drag&drop it to right window to copy the original framework-res.apk to your device
(just ignore that your device is doing strange stuff then, since it cannot access your framework-res.apk correctly at this point)
Then enter shell of QtADB(at left toolbar of QtADB) and enter the following commands to set the apk's prermissions:su
cd /system/framework/
chmod 777 framework-res.apk
Reboot your device( e.g. by using top menu->tools-ADB->reboot)
Set your background image and your (google/HtcSense) accounts anew.
Hope it helps you a bit on modding,
Greetings, brush2(Stephan)
error
hey man, Im getting an error on this. I changed my transitions effects ( folder anim on framework-res.apk) using the app metamorph. well, now every time I open an app the phone ( xt920) reboot. I ask my friend that have the same phone to send me his framework-res.apk. I try to replace using this method but dont got. I draged and droped the new apk and when I would type the shell's code the last code dont work because it said that the file is a "read-only system". What can I do to have my phone back? Please help.
Thanks.
I've been running cm7 nightlies and now stable 7.0 for some time now. I have the new radio, ladios' kernel, and the sdcard read fix flashed.
I installed super manager and successfully deleted some of the stock cm7 media off my phone last week. Today, I came across the new GPS.conf files and wanted to try them.
Super manager couldn't switch the system to r/w despite saying "ok"
When I try to delete or write in the system with EStrongs file explorer, ghost commander, or android mate, they all give strange errors. The deleted files disappear but reappear after reboot. If I try to paste a file in system/etc I only get an error.
Superuser is successfully allowing permissions. I have the latest busybox. I have r/w enabled in each file manager.
I even tried an adb push test which first said "system is r/o only". The next try was "successful" but didn't do anything.
I'm still new with adb so I probably did something wrong. I typed in that r/w command, mount now shows: /dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
I can't figure out what changed and what I need to do to get r/w permissions. My only theory is that i had uninstalled and reinstalled super manager earlier and that somehow messed with my permissions.
You cannot permanently modify the system partition while the phone is booted into Android. The only way is to use adb while the phone is in recovery mode. Any changes you make while the phone is booted will be lost after a reboot.
Go check on those media files you thought you deleted. I bet you'll find they are still there.
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
You don't need to sign them on the aria
Sent from my Liberty using XDA App
jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Click to expand...
Click to collapse
Those programs will work on some phones but not the Aria.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
It really is as simple as adding or removing a few files from the zip file if you want to modify it.
goodtime of the day to all XDA people out there!
Running stock with Root (using the automated MSKIP's rootkit) [using CWRecvery]
Tried to edit the build.prop using ES notepad from the ES filemanager, wanted to hide the Navbar
So, I made a backup file (copied build.prop and renamed it to build.prop.backup and pased it back into System) edited the original one, just wrote the line of code on the bottom of the list
Code:
qemu.hw.mainkeys=1
Since than I get a Bootloop with "X" , can access FASTBOOT mode just fine, never made a recovery up-until now
So, before I make it worse, what should I do to fix it?
Thanks in advance!
alright I got it fixed
For those who wandered, you can replace files using the ADB system,
I couldn't log into android(ie no ADB) and only after I got into Recovery (Fastboot...) My ADB link was acknowledged by MSKIP's Rootkit
I Pulled the Backupfile, and than after renaming it, pushed it back into place.
Have fun, and always remember to backup!
I've had my A500 running fine for months rooted on a stock ROM. Yesterday I decided to install a different font with a font installer. My system is now stuck in a boot loop on the screen which displays "ANDROID". It turns out the font I installed ended in *.txt, not *.ttf, but it is indeed a valid font file. I know this because I had the same problem on another device and I was able to spot the problem before rebooting the other device.
The easiest way to fix this would be to simply mount the tablet memory on my computer, find the font, and change the file extension - but how do I do that? Is it possible without booting the device?
meztek said:
I've had my A500 running fine for months rooted on a stock ROM. Yesterday I decided to install a different font with a font installer. My system is now stuck in a boot loop on the screen which displays "ANDROID". It turns out the font I installed ended in *.txt, not *.ttf, but it is indeed a valid font file. I know this because I had the same problem on another device and I was able to spot the problem before rebooting the other device.
The easiest way to fix this would be to simply mount the tablet memory on my computer, find the font, and change the file extension - but how do I do that? Is it possible without booting the device?
Click to expand...
Click to collapse
If it boots far enough you should be able to access a terminal via adb. The adb service is started quite early during boot. Get the android sdk and try typing "adb shell". If it works you get a normal linux shell and then you can delete or rename the font using that.
EDIT: Fixed by flashing latest factory images via fastboot, then the latest TWRP, then MagiskSU.
Hi there,
I'm rooted on stock 7.1.1 but I can't seem to make write changes consistently on the system partition. I was trying to rename NotoColorEmoji.ttf in /system/fonts so I could copy across the version with the iOS emojis, and somehow the rename worked so it's now named NotoColorEmojiOld.ttf - I managed to do this with root permissions in Solid Explorer. However, when I try and copy across the new NotoColorEmoji.ttf to the fonts folder, Solid Explorer says it's unable to do so. I've tried rebooting into TWRP, mounting system and using the file manager but it fails with Error 1. What's worse is I can't seem to rename NotoColorEmojiOld.ttf back to NotoColorEmoji.ttf either - neither Solid Explorer nor TWRP work for this despite both obviously having root access, both throw errors. As a result I have no emoji font file so all my emojis are blank boxes.
Any help in fixing this would be appreciated!
Try flashing a zip version of notocolor in twrp
CarteNoir said:
Hi there,
I'm rooted on stock 7.1.1 but I can't seem to make write changes consistently on the system partition. I was trying to rename NotoColorEmoji.ttf in /system/fonts so I could copy across the version with the iOS emojis, and somehow the rename worked so it's now named NotoColorEmojiOld.ttf - I managed to do this with root permissions in Solid Explorer. However, when I try and copy across the new NotoColorEmoji.ttf to the fonts folder, Solid Explorer says it's unable to do so. I've tried rebooting into TWRP, mounting system and using the file manager but it fails with Error 1. What's worse is I can't seem to rename NotoColorEmojiOld.ttf back to NotoColorEmoji.ttf either - neither Solid Explorer nor TWRP work for this despite both obviously having root access, both throw errors. As a result I have no emoji font file so all my emojis are blank boxes.
Any help in fixing this would be appreciated!
Click to expand...
Click to collapse
Are you using either phh superuser or magisksu?
Try changing your SELinux to Permissive with this app https://forum.xda-developers.com/showthread.php?t=2524485
bozinsky73 said:
Try flashing a zip version of notocolor in twrp
Click to expand...
Click to collapse
I get "set_perm: some changes failed, Updater process ended with ERROR: 7" and it doesn't work.
blitzkriegger said:
Are you using either phh superuser or magisksu?
Click to expand...
Click to collapse
Nope, just plain old systemless SuperSU.
collinjames said:
Try changing your SELinux to Permissive with this app https://forum.xda-developers.com/showthread.php?t=2524485
Click to expand...
Click to collapse
For some reason the app claims I don't have root permission despite the SuperSU dialog popping up and me granting it root.
CarteNoir said:
I get "set_perm: some changes failed, Updater process ended with ERROR: 7" and it doesn't work.
Nope, just plain old systemless SuperSU.
For some reason the app claims I don't have root permission despite the SuperSU dialog popping up and me granting it root.
Click to expand...
Click to collapse
Selinux didn't work for me at first on 7.1.1, I got the same error as you. But I went into twrp made sure system mounted, go into twrp terminal and cd into /system/bin and /system/xbin and in both of these directories type in (touch su) with out parenthesis. Reboot and see if that makes selinux changer works now.
Fe Mike said:
Selinux didn't work for me at first on 7.1.1, I got the same error as you. But I went into twrp made sure system mounted, go into twrp terminal and cd into /system/bin and /system/xbin and in both of these directories type in (touch su) with out parenthesis. Reboot and see if that makes selinux changer works now.
Click to expand...
Click to collapse
That got the app working and I was able to change SELinux to permissive, but I still can't make lasting changes to /system unfortunately.
Bumping - anyone else have any ideas? I'm not so much concerned with not being able to change emoji fonts as I am concerned with the ramifications of not having system write access - if anything breaks or comes up in the future that I need rw system for, I won't be able to fix stuff unless I sort this out.