i accidentally deleted many .ttf and .otf files from system/media/fonts
now emojis and special characters are showed as a box with an x inside
what can i do to recover it?
are u on magisk ? if yes, try to use this magisk mod https://forum.xda-developers.com/one...-font-t3797613 maybe it could help. thx
oneplus6tuser said:
i accidentally deleted many .ttf and .otf files from system/media/fonts
now emojis and special characters are showed as a box with an x inside
what can i do to recover it?
Click to expand...
Click to collapse
Dirty flash your current ROM is the easiest way.
Or you could extract the missing files from the system partition in the ROM zip and copy them back to where they should be on the phone /system partition.
Related
Hello, I would like to know how I could extract backed up TWRP data on my computer? maybe because the data was large TWRP split it into two files : data.ext4.win000 and data.ext4.win001 (sizes 1.5 and 1.2 GB)
How I got there:
I've been using XenonHD rom for quite a while, and this rom uses koush's superuser app.
I noticed there was a newer version on the market so I installed it; however it appears the one used by the rom developer was modified and therefore had a different package name: I ended up with two superuser apps, one of them asking to update the binaries, which I did.
After that the phone got stuck and rebooted two or three times before being stuck indefinitely at 'updating app' message right after the bootanimation. I tried:
- to wipe dalvik cache but it was still stuck;
- I reflashed the rom + gapps but it was still stuck;
- then I went to the /data/app/ folder (via TWRP) and deleted the superuser app i installed from market, as well as the corresponding data in /data/data, wiped cache and dalvik again: still the same...
-the I decided to make a backup via TWRP : one of the whole system, and one of Data partition only;
- then I realised I couldn't transfer it to my computer in TWRP, so I finally made a factory reset, re-flashed the rom+gapps, and then (it worked) copied my backup to the computer
now; how can I retrieve the data of my apps only, as I guess it is the system data that is messed up?
Of course I tried to restore the Data backup in twrp and it got stuck again the same way....
any help greatly appreciated!
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
forvrknight said:
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
Click to expand...
Click to collapse
It actually helped me, thanks a lot!
Two Questions
asim0 said:
On this file I used AccessData FTK Imager,
Click to expand...
Click to collapse
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
asim0 said:
All you have to do now is to merge the two data folders and voilà
Click to expand...
Click to collapse
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
pi_yush said:
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
Click to expand...
Click to collapse
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
number_thirty_two said:
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
Click to expand...
Click to collapse
Thanks number_thirty_two, I copyed thes to a folder I named untar in my home folder of CYGWIN, and extracted my system files perfectly
C:\cygwin\home\carl\untar\
system.ext4.win000
system.ext4.win001
tar xvfz system.ext4.win000
tar xvfz system.ext4.win001
Apologies for resurrecting this, but does anyone know how to extract them if they were compressed as .comp files?
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voil
Click to expand...
Click to collapse
Can someone show me a way to reseal File/Folder to System.img.
I extract these file/folder from Stock Nexus 4 zip. What I want to do is install a font then zip it back to System.img so I can flash it.
Thank
ronnyckb said:
Can someone show me a way to reseal File/Folder to System.img.
I extract these file/folder from Stock Nexus 4 zip. What I want to do is install a font then zip it back to System.img so I can flash it.
Thank
Click to expand...
Click to collapse
There are ways to repack it (I've never done it myself, but if you search, you'll probably find some tools), but there is an easier way to just install a font: package it up in a recovery-flashable zip. A guide on how to create recover-flashable zips can be found here.
I just have a couple questions, I've been adjusting theme zips by changing around files in the zip then flashing.
I wanted to alter a rom I have by changing the apks that are in the system/app , data/app, and framework folders. Usually I'm able to view apks as zips, but I'm the rom zip file, I cannot. I can't seem to write in the zip file at all...
And I can't change is permissions cuz when I go into the root section in my xplore file manager, anytime I view the sd or extsd Cards, I don't get the same options.
Any guidance is appreciated
You've Just Been Tapatold ♧♢dbombROMv3beta♤♡
☆FlappyBird☆Score ☆ 85 ☆
Or if I'm in the wrong section... where should I go?
You've Just Been Tapatold ♧♢dbombROMv3beta♤♡
☆FlappyBird☆Score ☆ 85 ☆
you cant edit files IN compressed files. (zips)
extract the files you want to edit. edit them, then place them back in the zip, overwriting the old versions of the files you edited.
though it is best to extract the whole rom zip, edit then re-zip everything. most recoveries dont require signed zip files, or can be disabled, so you dont even need a special tool to re-zip them most of the time. just use windows zipping. or win rar with 0 compression.
Start reading here.
http://forum.xda-developers.com/general/xda-university
one of the top posts is how to make recovery flashable zips.
I've changed bootanimations before on other devices, but the file was always called "bootanimation.zip." Looking at the files in the SGS5, I see 3 different "boot*.qmg" files, but no "bootanimation.zip."
Since we don't have a custom recovery yet, I'm hesitant to rename the *.qmg files and drop in a "bootanimation.zip" I created for my SGS4 into the same folder. Is there some new way to replace bootanimations on an SGS5 due to the *.qmg file extension, or it's safe to just rename/delete the *.qmg files and drop in the "bootanimation.zip" file into the appropriate folder?
I'd hate to get stuck in a bootloop and have to odin back to stock only to be unable to fully "restore" my phone's settings afterwards (yes, I have TiBu & other apps that'll allow me to restore, but it's certainly not as easy or as complete as restoring a nandroid backup).
Icculus760 said:
I've changed bootanimations before on other devices, but the file was always called "bootanimation.zip." Looking at the files in the SGS5, I see 3 different "boot*.qmg" files, but no "bootanimation.zip."
Since we don't have a custom recovery yet, I'm hesitant to rename the *.qmg files and drop in a "bootanimation.zip" I created for my SGS4 into the same folder. Is there some new way to replace bootanimations on an SGS5 due to the *.qmg file extension, or it's safe to just rename/delete the *.qmg files and drop in the "bootanimation.zip" file into the appropriate folder?
I'd hate to get stuck in a bootloop and have to odin back to stock only to be unable to fully "restore" my phone's settings afterwards (yes, I have TiBu & other apps that'll allow me to restore, but it's certainly not as easy or as complete as restoring a nandroid backup).
Click to expand...
Click to collapse
Follow these instructions. Enjoy.
Misterxtc said:
Follow these instructions. Enjoy.
Click to expand...
Click to collapse
Thank you very much for the direction. While I'll give it a shot a later, that still won't allow me to replace the default bootanimation w/ the ones I've previously created. The bootanimation.zip files I want to use only contain *.png files (the *png's are in "part0" folder and there is a desc.txt file in the parent directory). There are no *.qmg files in those zip's to extract, so that process won't work for me & the bootanimations I'm trying to use.
Any other ideas, or is my only option to use something like the Samsung Theme Designer process? (http://forum.xda-developers.com/showthread.php?t=2696914)
Icculus760 said:
Thank you very much for the direction. While I'll give it a shot a later, that still won't allow me to replace the default bootanimation w/ the ones I've previously created. The bootanimation.zip files I want to use only contain *.png files (the *png's are in "part0" folder and there is a desc.txt file in the parent directory). There are no *.qmg files in those zip's to extract, so that process won't work for me & the bootanimations I'm trying to use.
Any other ideas, or is my only option to use something like the Samsung Theme Designer process? (http://forum.xda-developers.com/showthread.php?t=2696914)
Click to expand...
Click to collapse
Contact the maker of the OP of the thread with the boot animations, I'm pretty sure he/she can help you out converting the files. It's been done before in that thread.
Misterxtc said:
Contact the maker of the OP of the thread with the boot animations, I'm pretty sure he/she can help you out converting the files. It's been done before in that thread.
Click to expand...
Click to collapse
What the heck, man. Stop helping me so quickly! :laugh:
Thanks again!!
I was trying to disable the hardware buttons, the one next to the home button, and use on screen buttons. But when I edited the file the first time the back button was disabled which is what I wanted but not the other button (menu?). So I tried again and when es file explorer saved it, it saved it as a empty text document. So what I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout. Im sorry if this is in the wrong place im just kinda scared about what could happen, like not being able to power back on. Thank you!
xada162 said:
I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout.
Click to expand...
Click to collapse
You should start making backups. Everyone runs into problems eventually and if you had a backup you could revert to a 100% stable system with only a few clicks.
The file that you can want can be found in the full, stock firmware image. Just download the full firmware and use winrar to extract what you need.
.
Just dirty flash the rom you have (without a wipe).
fffft said:
You should start making backups. Everyone runs into problems eventually and if you had a backup you could revert to a 100% stable system with only a few clicks.
The file that you can want can be found in the full, stock firmware image. Just download the full firmware and use winrar to extract what you need.
.
Click to expand...
Click to collapse
So I have backups of my phone with twrp but I'm lost as to what I need to look for/where that file is going to be
xada162 said:
So I have backups of my phone with twrp but I'm lost as to what I need to look for/where that file is going to be
Click to expand...
Click to collapse
I thought you knew exactly what file you accidentally corrupted. In your original post you said
xada162 said:
I'm asking you is a copy of your generic.kl file which is located in system>use>keylayout.
Click to expand...
Click to collapse
So on that basis, you could extract the cited file from the TWRP system image. Or temporarily restore it and copy that file. Or for that matter simply restore the entire /system partition. The latter would cover you even if you weren't positive which system files were corrupted.
So boot to TWRP, wipe your system cache, then restore the system partition from a known good backup and call it day.
.