I am really pissed about this one.. tried to make a Titanium Backup of my stuff before I unrooted and wiped the phone to ODIN the ANE update (it refused to update after being towelrooted).. So that was my first introduction to the bug that prevents TiBu from writing to the extSD.. I found several threads pointing to adding a line to the profiles.xml file in system/etc/permissions. Well I added the line using ES3 note editor (copied the original file to .bak first), saved and rebooted, and as soon as I unlocked the phone, the toasts started popping up that nearly everything was crashing - repeatedly. I went and deleted the modified file and changed the .bak back to normal, but it did not fix it. No apps would open, and I had no data connection (neither Wifi or 3G). The only thing that fixed it was booting into recovery and wiping it.
And then it happened AGAIN when I tried it again (after the ANE update was flashed via ODIN, so I know it was clean). So WTF is happening, and why does restoring the original file not fix it??
At this point I can't even get TiBu to back up to the internal storage.
Taz420nj said:
I am really pissed about this one..
Click to expand...
Click to collapse
There is no obvious reason why it shouldn't work of you reverted the changes. But of course that is the ultimate value of a tested backup method.. that ability to roll the clock back and revert accidental or inexplicable changes.
If you are certain that you reverted the edits.. no typos or line feed errors e.g.you used a linux aware file editor.. not notepad on a PC or something similar - then it's likely a permissions error.
What permissions does the file currently have? And what app did you edit the .xml with?
.
fffft said:
There is no obvious reason why it shouldn't work of you reverted the changes. But of course that is the ultimate value of a tested backup method.. that ability to roll the clock back and revert accidental or inexplicable changes.
If you are certain that you reverted the edits.. no typos or line feed errors e.g.you used a linux aware file editor.. not notepad on a PC or something similar - then it's likely a permissions error.
What permissions does the file currently have? And what app did you edit the .xml with?
.
Click to expand...
Click to collapse
As I said, I made a copy of the file and edited it with ES3 Note Editor right on the phone. Then I renamed the original file to platform.xml.bak, and copy/pasted the new platform.xml file into system/etc/permissions. When everything went haywire, I didn't try editing the file back (I couldn't - the toasts were popping up almost faster than I could clear them and Note Editor kept crashing), I just deleted the modified file and renamed platform.xml.bak back to platform.xml. I never edited the original file at all, so that's how I am 100% positive there are no errors in it - and that's why I can't figure out why renaming it back doesn't fix the mayhem.
Now I am a total weenie when it comes to Linux - I know OF the -rw-r--r-- permissions and what they mean, but I don't know how to make the phone tell me.. But in ES3 Explorer under file properties it simply says Readable: Yes Writable: Yes Hidden: No.
What sucks is I've had to go through and set the phone back up twice now, and lost all my settings/data in the meantime over this.. And I STILL don't have a working backup method, so if it borks again I'll be doing it all over again.. I am unwilling to blow the Knox fuse, hence not having a custom ROM at this point.. But I'm fine using Towelroot just so I can unbloat and install some things.
No one wishes for things to go awry. But of course they do sometimes and it would be imprudent not to plan for that eventuality. You didn't, nor do you seem to realize just how risky the changes you have been making are to your basic system stability. You are modifying critical, system level files and properties. The expected result if there is a typo or permissions error is chaos and corruption. If I was unable to have a working backup method (from refusing to increment Knox), I wouldn't risk the changes you are making.
It's all well and nice to customize features when things turn out smoothly. But all along you have been working without a safety net, so it's not reasonable to complain about the onerous amount of work it is to reinstall the firmware when fate bites you. You can't have it two ways at once. Either you incremement Knox, allowing inclusive backups and a way to recover. Or you accept that that you are taking crazy risks and having to start over the price for doing so.
You'd be in a better position if you had some basic tools to delineate what is going on. But you haven't taken the time to learn how to read file permissions. You are working deep within a linux filesystem, so this is a very basic and useful skill.
You don't use the same file manager as me, with mine (fx), you would long press and view details. Or even easier, use the ls command e.g. ls -la. There are a dozen ways you could check permissions and a simple forum search would elaborate on many of them. It sounds like you have permissions errors, i.e the system can't access the restored .xml sheet thereby causing numerous apps to crash.
.
Uhhh, except in order to implement the safety net I have to make this simple change to this one critical system file. It's no different than not having a means to backup before rooting/flashing (since TiBu requires root and you can't do a nandroid from stock recovery) and something goes wrong.
Adding the <group gid="media_rw" /> line to the profile.xml is posted in MANY locations as a "this is all you have to do" solution to this rather stupid quirk in 4.4, with no mention whatsoever of checking/verifying permissions or any other cautions, and other people are not having this issue.
I installed FX, and it lists the permissions of all the files (including the copies of platform.xml and platform.xml.bak that I had saved on the SD card, and the virgin file currently in use) as 0644.
Taz420nj said:
Uhhh, except in order to implement the safety net I have to make this simple change to this one critical system file
Click to expand...
Click to collapse
It's your phone so you can do as you like. But risks don't go away because you ignore them. There is nothing wrong with accepting a risk that you may have to start over if things go sideways. But plunging ahead recklessly then complaining about the work to recover is patently unreasonable
I had no problem effecting the changes you are attempting. Nor have many others. Perhaps you made a typo or followed a thread with erroneous advice. You may well have a permissions error because you didn't explicitly set it or check to see if it was correct.
It's all about attention to detail e.g. checking permissions and being prepared to deal with fallout when things go astray.
.
Related
Title says it all. I've seen this question asked but too many times I see people saying. "Use Search Function"
The search function has been scoured and I see plenty of great apps that restore and backup apps, contacts, etc.. none restore data WITHIN the apps.
Is there an app that backs up DATA within the apps not just the apps.
Thank you,
come again.
Titanium backup backs up my apps plus all system data
I'd like to know this too, with possible Rom coming in September I'm desperate to make the change over as smooth as possible.
post in general section
Mooved
Good question. I use MyBackup (online) for saving my data - but only sms-contacts..
If you find an app that save all you need, please post its name here ^^
thx
The process is quite complex (at least the way I do it) but it can be done!
Note: YOU NEED LINUX FOR THIS (or if you're brave you can mess with the tools on this site: http://www.chrysocome.net/download. success is not guaranteed. Still post about your experiences though )
Note: Steps 1 to 3 are not always necessary, it depends on which Android build you are using.
1) Give Root Explorer (or a similar file explorer app - must be able to access system/data files) root access
2) Locate the folders containing the user data you want to backup, this is usually somewhere near /data/data. The folders have various naming conventions and dont always contain the name of the app (i'll check and edit this post if i have time)
3) Change the folder's permission settings - I usually just permit everything
4) Shut down Android and in one way or another, mount your sd card on your Linux machine, and locate your data.img or userdata.img file.
5) Open a command line window, enter the following:
Code:
sudo mount -o loop data.img /mnt/data
Note: you might need to create the folder you are mounting too
Note: sudo not always neccesary
Note: change data.img to userdata.img, you'll know if this applies to you
6) Browse to the folder containing the data you want to backup and copy it onto your computer. DONE!
You can restore these backups on a different build by using the same method, just in reverse. Also, don't forget to check if the same folder already exists, if yes, it can be extremely annoying to find you dont have permission to change/overwrite it!
I used this to copy all of my saved games, i especially didn't want to loose my Asphalt 5 progress
P.S. if this solves your problem, please change the title of this thread to simplify things for other users
Thanks Kev007, I'll try this
filou75 said:
Thanks Kev007, I'll try this
Click to expand...
Click to collapse
While it is good to know how to do this stuff, just download Titanium from the market. It backs up all apps plus data in about a minute. You can restore individually or in batches using filters. Search around there is lots of info on this app.
It is great to learn some basic Linux stuff. It will help when you are trying to do things in Android. If you have no intention of learning Linux, Titanium is the way to go.
that be good actually - on my last android reinstall I lost my paper toss high score (allbeit only 3 pmsl) but still seems like a good thought considerin the games etc with save data.
Seconded - Titanium Backup preserves all my app data.
This is one of the reasons I love Android over WinMo - backing up app data is practically a nobrainer when you have the right tool.
+1 on Titanium Backup.
Works great on all builds. Just don't try to restore native HTC apps/data from sense to vanilla Froyo.
Kev007 said:
The process is quite complex (at least the way I do it) but it can be done!
Note: YOU NEED LINUX FOR THIS (or if you're brave you can mess with the tools on this site: http://www.chrysocome.net/download. success is not guaranteed. Still post about your experiences though )
Note: Steps 1 to 3 are not always necessary, it depends on which Android build you are using.
1) Give Root Explorer (or a similar file explorer app - must be able to access system/data files) root access
2) Locate the folders containing the user data you want to backup, this is usually somewhere near /data/data. The folders have various naming conventions and dont always contain the name of the app (i'll check and edit this post if i have time)
3) Change the folder's permission settings - I usually just permit everything
4) Shut down Android and in one way or another, mount your sd card on your Linux machine, and locate your data.img or userdata.img file.
5) Open a command line window, enter the following:
Code:
sudo mount -o loop data.img /mnt/data
Note: you might need to create the folder you are mounting too
Note: sudo not always neccesary
Note: change data.img to userdata.img, you'll know if this applies to you
6) Browse to the folder containing the data you want to backup and copy it onto your computer. DONE!
You can restore these backups on a different build by using the same method, just in reverse. Also, don't forget to check if the same folder already exists, if yes, it can be extremely annoying to find you dont have permission to change/overwrite it!
I used this to copy all of my saved games, i especially didn't want to loose my Asphalt 5 progress
P.S. if this solves your problem, please change the title of this thread to simplify things for other users
Click to expand...
Click to collapse
Now THIS is an answer. I knew I wasnt the only one trying to do this. I dont need to backup the APPS because I already have them backed up oin my PC.
My buddy has a linux box ill try this with. Thanks.
PS. To the titanium suggestions. I've tried that. Doesnt seem to save game states or 3rd party app preferences...
Good day, all!
I've been working on [my first] ROM for Verizon S5 and everything seems to be going great! I've cleaned out as much Samsung/Verizon/Google trash as I can, applied some tweaks to build.prop, changed some default apps to (IMHO) better replacements, and anything that is left (functions correctly) has been moved to /data/app so they can be Uninstalled fully (not just Turned Off). Just a few quick questions:
1) How can I "bake-in" app data? I have replaced the normal, crap launcher with Holo Launcher and cannot seem to get correct permissions when the ROM is installed thru SS. I believe the issue is permissions for /data/data/ get screwed up or not set correctly. I have looked and looked and tried to determine the correct permissions, but still no joy. I've tried to fix /data/data permissions in the updater-script, but it seems like each subfolder/file has different permissions making me think I'll have to go thru them one-by-one.
I have a work-around in place using a OneTimeInit script that does work, but it seems like that's not really the best approach?
2) Kind of ties into question number 1, I patched the framework-res.apk in to allow WiFiHotspot, but without being able to install the system settings data properly, there is not a "Quick Shortcut". Again, I've resolved the problem using the OneTimeInit to update Sqlite DBs after the system is up.
3) How do I de-odex the stock ROM? Using Android Kitchen doesn't seem to do it right. It works mostly but I still seem to get various FCs. I tend to believe that some things just cannot (should not) be De-Odex'd?
I've also discontinued Zip-Aligning because it sometimes produces errors on my ROM. Is it not advised to use Android Kitchen to do these tasks or is there some trick to getting it to work just right?
Bonus Question) I was going to share my ROM on XDA but it says I'm not allowed to post in Development. I assume because of my low post count. Any way I can get an over-ride or should I just make a few more posts and then do it?
Thanks again guys!
I appreciate all the help as always!
Jake
jake5253 said:
Good day, all!
I've been working on [my first] ROM for Verizon S5 and everything seems to be going great! I've cleaned out as much Samsung/Verizon/Google trash as I can, applied some tweaks to build.prop, changed some default apps to (IMHO) better replacements, and anything that is left (functions correctly) has been moved to /data/app so they can be Uninstalled fully (not just Turned Off). Just a few quick questions:
1) How can I "bake-in" app data? I have replaced the normal, crap launcher with Holo Launcher and cannot seem to get correct permissions when the ROM is installed thru SS. I believe the issue is permissions for /data/data/ get screwed up or not set correctly. I have looked and looked and tried to determine the correct permissions, but still no joy. I've tried to fix /data/data permissions in the updater-script, but it seems like each subfolder/file has different permissions making me think I'll have to go thru them one-by-one.
I have a work-around in place using a OneTimeInit script that does work, but it seems like that's not really the best approach?
2) Kind of ties into question number 1, I patched the framework-res.apk in to allow WiFiHotspot, but without being able to install the system settings data properly, there is not a "Quick Shortcut". Again, I've resolved the problem using the OneTimeInit to update Sqlite DBs after the system is up.
3) How do I de-odex the stock ROM? Using Android Kitchen doesn't seem to do it right. It works mostly but I still seem to get various FCs. I tend to believe that some things just cannot (should not) be De-Odex'd?
I've also discontinued Zip-Aligning because it sometimes produces errors on my ROM. Is it not advised to use Android Kitchen to do these tasks or is there some trick to getting it to work just right?
Bonus Question) I was going to share my ROM on XDA but it says I'm not allowed to post in Development. I assume because of my low post count. Any way I can get an over-ride or should I just make a few more posts and then do it?
Thanks again guys!
I appreciate all the help as always!
Jake
Click to expand...
Click to collapse
1: All I had to do was place apk in /system/app or /system/priv-app and thats it. Make sure when you add your apks you dont unzip the archive. basically use kitchen and build your base rom then simply open the archive and make your edits. I also used the updater script from beans base build and only edited the ui print.. Messing with the updater script i wouldnt recommend as it could be causing some of your issues.
2: If using beans base theres no reason for you to edit anything as the hotspot is already baked in.. you must have borked it.. If you are not using beans base then maybe you should copy his files for the native hotspot as its already done properly. I wouldnt mess with framework or settings apks unless you know what your doing. Id work on gettin the fcs n other issues sorted first as you might b doin too much too fast.. work on learning how to make your apks work first before making edits to framework n settings apks.
3: The kitchen is best to deodex and zipalign.. also these two things should not cause fcs or errors if done properly. zipalign should help more than anything.. i just like workin with deodex bcuz its easier and only one set of files instead of .apk and .odex for just bout everything..
Again, if you are not using beans bases id recommend to do so.. his bases are already deodexed have hotspot zipaligned read/write to ext sd etc.. so you wouldnt have to do all from scratch and have so many issues..
Sent from my SM-G900V using XDA Premium HD app
elliwigy said:
1: All I had to do was place apk in /system/app or /system/priv-app and thats it. Make sure when you add your apks you dont unzip the archive. basically use kitchen and build your base rom then simply open the archive and make your edits. I also used the updater script from beans base build and only edited the ui print.. Messing with the updater script i wouldnt recommend as it could be causing some of your issues.
2: If using beans base theres no reason for you to edit anything as the hotspot is already baked in.. you must have borked it.. If you are not using beans base then maybe you should copy his files for the native hotspot as its already done properly. I wouldnt mess with framework or settings apks unless you know what your doing. Id work on gettin the fcs n other issues sorted first as you might b doin too much too fast.. work on learning how to make your apks work first before making edits to framework n settings apks.
3: The kitchen is best to deodex and zipalign.. also these two things should not cause fcs or errors if done properly. zipalign should help more than anything.. i just like workin with deodex bcuz its easier and only one set of files instead of .apk and .odex for just bout everything..
Again, if you are not using beans bases id recommend to do so.. his bases are already deodexed have hotspot zipaligned read/write to ext sd etc.. so you wouldnt have to do all from scratch and have so many issues..
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Thank you for the response!
It seems perhaps I didn't quite make clear what I've done versus what I'm trying to accomplish.
Firstly, I wouldn't go so far as to say I'm "having so many issues". Everything in my ROM is in perfectly fine working order. I just have these few quirks that I would like to address both so I can learn, and to make this and future projects better.
While I appreciate the recommendation to use bean's base, I have taken a look at his and there seems to be nothing in his which copies data into /data/data/com.whatever.package (or at least there's nothing in his zip in the /data/data folder -- not sure if his ROM has the toggle activated?)
I have the Apps working correctly in my ROM -- they just go in /data/apps, /system/app or /system/priv-app, respectively.
What I need, is to get /data/data/com.whatever.package/ copied With Correct Permissions when the ROM is installed; I do not want a second zip to update things after install, especially for a toggle and a couple shortcuts, seems silly.
For instance, when you boot your phone up with the default [stock] samsung launcher, it has a list of default apps and widgets on the first screen you see such as phone, messages, a clock widget, etc, etc. Since I've replaced the stock launcher with Holo Launcher HD and some other default apps have also been replaced, there's very few shortcuts on the main launcher screen.
** Holo Launcher does have a list of default apps it adds to your main page, but many of those have been removed in my rom.
The solution I've come up with basically waits for the system to boot up to the point that Holo Launcher actually creates the default (mostly blank) /data/data/com.mobint.hololauncher.hd/databases/launcher.db and then my script uses sqlite3 to update the DBs with a list of different shortcuts -- ones to apps that actually exist.
The Hotspot Toggle is the same way as above.. Hotspot works fine in my rom if you go through settings!
I just cannot add the notification panel pull-down toggle to /data/data/com.android.providers.settings/database/settings.db until after the system boots up at least ONE time, and then update the DB to include WiFiHotspot in notification_panel_active_app_list and notification_panel_active_app_list_for_reset
As for the zipalign and deodexing, I will have to try those again now that I have a fairly stable rom.
****EDIT****
I think I figured it out. I can just use busybox to kill the systemui after I update the databases during the first boot. I also figured out how I can add the SetupWizard without it locking up on activation.
Thanks anyways, guys.
Look for my rom, coming soon!
=P
Please add support for more languages
I found a mod for Motorola latest 4.4 please port it
Sent from my SM-G900T using XDA Free mobile app
*edit* deleted thread. Unfortunately this doesn't fix it. QFIL then flashing EUI ROM 14s and then upgrading to a newer EUI ROM or device firmware update then custom ROM is the only true fix.
Sadly, it doesn´t work for mine, maybe you can help me?
Greetings.
Iceee44 said:
Sadly, it doesn´t work for mine, maybe you can help me?
Greetings.
Click to expand...
Click to collapse
Heyyo, hmm darn that's unfortunate... Well, I have a test build of LineageOS 15.1 for the Le Max 2 with the calibration fixes in place and same with the upcoming official weekly build of LineageOS 14.1 for the X2 this Saturday. It's up to you which you would want to try. Hopefully one of them will work for you.
If not? I'm unsure what else could be causing the issue then hmm...
Hey thanks for reply!
I don't why, but something worked!
I got the splitscreen bug, then I flashed the recovery to the newest twrp (the blue one, don't know which version, but I will look it up). Then I wiped everything and install your fix. Result = bricked. Another try with one flash 2.0 and no error from flash. Fastboot recovery flash and everything was perfect.
I think it was luck, but my leeco le max 2 is repaired :victory:
Wow that's lucky! Congrats on fixing it!
May I please ask what happened to cause the brick? I've heard of device bricking but haven't seen an exact answer as to what unfortunately caused it.
It was totally my fault... I Format my data...and no image on storage... And one flash did the screen problem, maybe the program doesn't decompress a file finally... I decompressed the qfil data two times... The first time I got an error, after full decompressed everything...
Ah if you format data without any ROM on the device you can always use a PC and USB cable to do this...
adb push NameOfROM.zip /sdcard
Which will copy the zip file to the root of your data storage. Same can be repeated for Gapps or Magisk, etc.
I tried to push a 1,8GB file...
But after 2 hours it wasn't transferred, so I found the software and this is much easier.
Could you explain what exactly the "Unbricked devices split screen" bug is?
So from understanding the changes, does this mean that the 4 profiles in the Display -> Colour mode menu won't actually activate for people with the issue? (So if they do change then you don't have the bug?)
I'm guessing that editing those xml files could help with this problem? https://forum.xda-developers.com/le-max-2/how-to/le-max-2-black-crush-survey-t3744594
Or are there other places where those parameters are set?
ThE_MarD said:
Heyyo, this is a TWRP flashable zip file to replace the broken formatting on the qdcm calibration xml files for the display panels used in the LeEco Le Max 2
Click to expand...
Click to collapse
Which bug your fix is intended to fix? Do you mean this: https://youtu.be/3yXnrkfsJMI - I have never seen it on my device.
Or you mean color calibration, which is currently terrible by default (too much yellowish)
oneNight1 said:
Could you explain what exactly the "Unbricked devices split screen" bug is?
So from understanding the changes, does this mean that the 4 profiles in the Display -> Colour mode menu won't actually activate for people with the issue? (So if they do change then you don't have the bug?)
I'm guessing that editing those xml files could help with this problem? https://forum.xda-developers.com/le-max-2/how-to/le-max-2-black-crush-survey-t3744594
Or are there other places where those parameters are set?
Click to expand...
Click to collapse
For both of these questions the hopes is that the main issue with most people who unbrick their devices having screen issues is due to calibration settings being lost which this in theory should restore as it would have XML files with proper formatting unlike before where stock EUI ROM for the Le Max 2 had broken calibration XML files.
In theory if the black crush issue is also a calibration issue there's a chance this could also fix it... But still, I haven't really looked into that as I was mainly looking for a better solution for those unfortunate people suffering from unbrick device woes. If it fixes it? Cool... If not? Then I'm not too sure. Calibration files could potentially be modified to fix black crush if the issue is in there that LeEco never addressed.
giaur said:
Which bug your fix is intended to fix? Do you mean this:
- I have never seen it on my device.
Or you mean color calibration, which is currently terrible by default (too much yellowish)
Click to expand...
Click to collapse
How do i view the config files and transfer them to my computer to compare them to yours? I enabled usb debugging, thinking that would let me see everything but when i connect to my computer with MTP mode i can only see standard files, not all the linux config files etc.
(edit: I tried using adb shell and i could view the root directory but it wouldn't let me access the config folder - permission denied. Do i need root access? If so, how do i get it temporarily and then remove it once i have transferred the files? I can't just run adb as root because you need root on the phone apparently).
Also i did a search of the available EUI x829 source (http://opensource.le.com/ or http://opensource.le.com/ or https://forum.xda-developers.com/le-max-2/how-to/source-code-available-t3482334 )and i couldn't find those xml files. Are they generated by the OS or something?
To me it seems like the files are probably already formatted correctly on my particular phone as changing the colour mode does appear to function. However they obviously seem to be not calibrated properly (or intentionally calibrated very badly).
I wonder if it only reads these files on boot? Otherwise i guess an application could be made to interactively adjust them.
I wonder if KCAL uses these files.
However from looking at how large the data is and also the mention of LUTs (lookup tables), it would seem that this is actually more advanced than kcal? And could potentially give proper screen calibration if using a colourimeter etc?
Of course, more than one profile would be necessary for different brightness levels though.
But anything is better than nothing.
It is definitely to do with the eui colour mode settings because if you go to google translate and translate the names in for each profile, they match up with colour mode options.
These are part of EUI ROM as I did mention the XML formatting is broken on all the EUI ROM versions I looked at.
You can use an Android ROM extractor like this to open up EUI ROM and see the files yourself if you'd like.
https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
I found this https://usermanual.wiki/Pdf/KBA160907024936QDCMPCToolDebugGuide.968066270 which implies that the xml file is used directly.
Have you considered that <Calib_Data /> just means that the Calib_Data section is empty deliberately and that the colour profile and LUT sections were never intended to be within the calibration data tag?
We do not have the specification of the QDCM xml file that the tool generates.
It would be beneficial if the QDCM tool could be somehow leaked or obtained, then the end user could calibrate their phones. Or at least a specification of the file format of the QDCM xml files so correct data could be generated.
I suggest this should be brought up to the wider android community as it applies to all recent qualcomm phones.
Then we can compare with the QDCM xml files distributed with their handsets. Maybe some handsets even contain the same panels and therefore maybe we could attempt to use their profile / calibration settings. Of course it won't give perfect results because screens should be calibrated on an individual basis but it might be a lot better than the awfullness i currently have.
I wonder, do Le Eco calibrate each handset individually because if they do and then CFW overwrites the calibration with a "random" one then i can understand how that would cause issues. However my display has been bad before i loaded CFW... (unless the seller tampered with the FW but i don't know how you are meant to tell that).
I am not saying you are wrong but you have not given sources for your findings and to me, the individual colour profiles are working it's just that the overall calibration (or all of the profiles themselves) is extremely awful with huge black crush.
That tools seems to be for looking at backup images? But i want to view what is on my phone currently. Do you have to root your phone to do so? If so how can i root and then unroot it after i'm done?
Thanks
oneNight1 said:
I found this https://usermanual.wiki/Pdf/KBA160907024936QDCMPCToolDebugGuide.968066270 which implies that the xml file is used directly.
Have you considered that <Calib_Data /> just means that the Calib_Data section is empty deliberately and that the colour profile and LUT sections were never intended to be within the calibration data tag?
We do not have the specification of the QDCM xml file that the tool generates.
The way the XML formatting is? Calib_Data is supposed to house the entire XML file to let QDCM know where the calibration data starts and ends... So on the broken EUI ROM XML files it only has an end and never loads the calibration data.
It would be beneficial if the QDCM tool could be somehow leaked or obtained, then the end user could calibrate their phones. Or at least a specification of the file format of the QDCM xml files so correct data could be generated.
I suggest this should be brought up to the wider android community as it applies to all recent qualcomm phones.
Then we can compare with the QDCM xml files distributed with their handsets. Maybe some handsets even contain the same panels and therefore maybe we could attempt to use their profile / calibration settings. Of course it won't give perfect results because screens should be calibrated on an individual basis but it might be a lot better than the awfullness i currently have.
I wonder, do Le Eco calibrate each handset individually because if they do and then CFW overwrites the calibration with a "random" one then i can understand how that would cause issues. However my display has been bad before i loaded CFW... (unless the seller tampered with the FW but i don't know how you are meant to tell that).
I am not saying you are wrong but you have not given sources for your findings and to me, the individual colour profiles are working it's just that the overall calibration (or all of the profiles themselves) is extremely awful with huge black crush.
That tools seems to be for looking at backup images? But i want to view what is on my phone currently. Do you have to root your phone to do so? If so how can i root and then unroot it after i'm done?
Thanks
Click to expand...
Click to collapse
Heyyo, it's definitely a formatting error. XML standard has open and close brackets.
For example, the OnePlus 5T
https://github.com/TheMuppets/propr...b_data_samsung_s6e3fc1_cmd_mode_dsi_panel.xml
Or the Xiaomi Mi5 (Gemini)
https://github.com/TheMuppets/propr...calib_data_sharp_fhd_cmd_incell_dsi_panel.xml
As for viewing the files on your phone? Yes you would need root and a root file explorer.
Magisk, SuperSU, KingRoot or such all work for root but some versions of EUI ROM have issues.
For root enabled file browser? Amaze works... Amazing. Just get it from the Play store and then in settings enable root explorer.
For uninstalling root please Google the uninstall method to whichever root method you use as they are all different.
That's not true, XML tags can close themselves. If you don't believe me look here: https://www.w3schools.com/xml/xml_elements.asp (scroll down to empty xml elements)
How they had formatted their tags was valid xml.
Code:
<Calib_Data />
is just an element with nothing in it, the same thing as:
Code:
<Calib_Data> </Calib_Data>
However what you showed me from the other xml files for other phones make it look like it should be the way you have changed it
Okay i will have a look and let you know. I have small eui installed atm. So if you just flash an su to your system and then once you uninstall the app root is completely gone? I never would have thought it would be that simple.
It seems when you have root you can use an adb shell as root so i might try that rather than bothering to install anything on the phone.
Is there a way also to view what it was in the backup of my original fw without restoring it? (i used this guide for backup https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151 ).
How can i find out which of the 3 display types my device is using? (Preferrably via adb).
I will be really surprised if it's wrong in mine because the colour modes work which will be very weird if that xml file isn't being used - they must do it another way too if that's the case :S
It's also weird how those xml files have been hand tampered with!
Thanks!
oneNight1 said:
That's not true, XML tags can close themselves. If you don't believe me look here: https://www.w3schools.com/xml/xml_elements.asp (scroll down to empty xml elements)
How they had formatted their tags was valid xml.
Code:
<Calib_Data />
is just an element with nothing in it, the same thing as:
Code:
<Calib_Data> </Calib_Data>
However what you showed me from the other xml files for other phones make it look like it should be the way you have changed it
Okay i will have a look and let you know. I have small eui installed atm. So if you just flash an su to your system and then once you uninstall the app root is completely gone? I never would have thought it would be that simple.
It seems when you have root you can use an adb shell as root so i might try that rather than bothering to install anything on the phone.
Is there a way also to view what it was in the backup of my original fw without restoring it? (i used this guide for backup https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151 ).
How can i find out which of the 3 display types my device is using? (Preferrably via adb).
I will be really surprised if it's wrong in mine because the colour modes work which will be very weird if that xml file isn't being used - they must do it another way too if that's the case :S
It's also weird how those xml files have been hand tampered with!
Thanks!
Click to expand...
Click to collapse
Write this in the terminal.
Code:
cat /sys/devices/virtual/graphics/fb0/msm_fb_panel_info | grep panel_name
Thanks Sergio, so my device is running:
Code:
le_x2_mdss_dsi_truly_qhd_dualdsi_cmd_pvt
Hmm it seems that SmallEUI ( https://forum.xda-developers.com/le-max-2/development/rom-small-eui-5-9-aurel-battery-t3524531 ) wiped the configs folder. It looks the same through both ADB --> shell ---> su ---> cd config as it does through the Amaze app on the phone itself - empty.
I am pretty sure that I have root properly, supersu seems to be installed.
For some reason though, if i try and get ADB to get root, it says:
Code:
adbd cannot run as root in production builds
I don't have a folder named configs, only one called "config" and it is completely empty.
Is there any way to view the files that were in my TWRP backup of my stock X829 FW without reflashing it?
I have lots of data.ext4.win000 files etc. Which archive would it be in? System? Data? EFS? Boot? And how do i browse the archives?
Thanks
oneNight1 said:
Thanks Sergio, so my device is running:
Code:
le_x2_mdss_dsi_truly_qhd_dualdsi_cmd_pvt
Hmm it seems that SmallEUI ( https://forum.xda-developers.com/le-max-2/development/rom-small-eui-5-9-aurel-battery-t3524531 ) wiped the configs folder. It looks the same through both ADB --> shell ---> su ---> cd config as it does through the Amaze app on the phone itself - empty.
I am pretty sure that I have root properly, supersu seems to be installed.
For some reason though, if i try and get ADB to get root, it says:
Code:
adbd cannot run as root in production builds
I don't have a folder named configs, only one called "config" and it is completely empty.
Is there any way to view the files that were in my TWRP backup of my stock X829 FW without reflashing it?
I have lots of data.ext4.win000 files etc. Which archive would it be in? System? Data? EFS? Boot? And how do i browse the archives?
Thanks
Click to expand...
Click to collapse
You should notice this does not work, garbage screen is there even with this fix applied. I have it all the time on latest Lineage 15.1.
Okay I checked in
Code:
system/etc
and I do have the files. They are formatted as
Code:
<Calib_Data />
too.
Why does your github page say that they should be in
Code:
config/qcdm
???
Anyway, I flashed your zip to see if it would make a difference but it didn't help with the black crush sadly.
Although maybe modifying the calibration data would - but of course we would need to understand the format.
I checked my TWRP backup image (you can just browse them with 7zip) and they have the same empty tag too.
cacerts.bks updated 12-6-20
When the original search was on to repair the aging cacerts.bks file in order to get the Kindle app working again, one of the things I came across was a remark from a fellow who had located a Honeycomb ROM (Android 3.2...last stop before the format of the security certificate storage was changed) and copied the cacerts.bks file from it to his Android 2.2 device which was having problems with websites, etc.
I still can't get the method described by @tshoulihane in this thread to work for me. But his edited cacerts.bks file works really well in solving the problem.
Yesterday I managed to locate a CM 7 ROM (Honeycomb). It contains a largish cacerts.bks file (compared to ours) with 127 certificates, 17 of which have expired. These seem to be mostly for central/eastern European and Asian entities, so perhaps not that critical. Well, it's only 10 years old
It has worked for me with the Kindle app and perhaps will help with some of the websites that complain about a secure connection even though I have enabled TLS 1.2 in Opera Mobile. More testing is needed there.
For anyone who wants to try it out, it is attached below. To use, rename your current cacerts.bks file (that's in /system/etc/security) to cacerts.bks.bak or similar. Then move the new file (unzip) into the same place. Check permissions. They should be rw-r-r. Reboot.
This looks great... though when I tried to rename and copy the new cacerts file, I am getting blocked due to the lack of root permissions.
I'm running the 1.2.1 tweaked/modded rom so I thought it wouldn't be an issue. I also tracked down the supersu3.1.3 apk and sideloaded it, but it didn't help either. Wondering if you had any ideas?
xrayd2 said:
This looks great... though when I tried to rename and copy the new cacerts file, I am getting blocked due to the lack of root permissions.
I'm running the 1.2.1 tweaked/modded rom so I thought it wouldn't be an issue. I also tracked down the supersu3.1.3 apk and sideloaded it, but it didn't help either. Wondering if you had any ideas?
Click to expand...
Click to collapse
So was your SU app missing? Or did your file manager just not have root access?
Hard to know where to start. From my experience, the best-behaving SU for the NST/G is the one that comes with NookManager (attached below). It's old and the binaries are probably out of date, but you don't need anything better for the device.
You can try removing the one you have now, reboot, and install the one below. Then check that your file manager has root acccess. In ES File Explorer, for example, you have to go into settings and tick the selection for root access. It's not automatic. And even with that, you have to tick an additional box to mount /system as rw while you're working in it.
At one time the superuser app was included -- but is no longer linked, and I had overlooked it after initially flashing the rom.
Unfortunately, the su app you provided also doesn't work. When I try to delete the old cacerts.blk it looks like it's doing something, but then the file still remains. If I instead try to rename the file, I get "operation failed".
I tried to delete or rename using an app called "root browser", and also the file manager in "super manager" suite. When I try to enable the root explorer function in ES file manager , I get "sorry, test failed. This feature cannot run on your device."
When I go under Device info, the ROM name does indeed say "Tweaked Modded ROM". I assume this should mean it's rooted but I'll have to dig deeper.
I appreciate your help though!
xrayd2 said:
When I go under Device info, the ROM name does indeed say "Tweaked Modded ROM". I assume this should mean it's rooted but I'll have to dig deeper.
Click to expand...
Click to collapse
Mmm.... so the ROM came "rooted"? I've attached a root check app which I've tried on my NST. This should answer the question of root.
If root has been lost somehow, it might be possible to salvage what you have by running NookManager. If you don't want the various additions like Relaunch, you can remove those apps from the data/app folder once you've written the card and then make the other needed changes as described here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048
Or, you could just use NM as-is and uninstall unwanted material afterwards. The important thing is root and a functioning SU.
Okay... turns out my device was NOT rooted after all; I had assumed the binaries were already installed. Fortunately, I was able to find a superSU 0.93 binary and root through CWM. I replaced cacerts.blk with yours, and now the kindle app works! At first I had difficulty logging in, but turns out Amazon was emailing me a one time password after every attempt. After entering the OTP I am now up and running.
My next issue is getting Pocket working -- I installed Read it Later 1.0.1 but it's not syncing.
Thanks for the link to your other post. I will sideload the apk's you recommended.
xrayd2 said:
My next issue is getting Pocket working -- I installed Read it Later 1.0.1 but it's not syncing.
Click to expand...
Click to collapse
Might not be possible. Chatter here: https://forum.xda-developers.com/showthread.php?t=1604661&page=2 goes back to 2013.
I found reference to a functioning version in 9/2016. Had hoped it was a cacerts issue but maybe pocket changed their api.
https://forum.xda-developers.com/showpost.php?p=68600731&postcount=54
Would this be what's causing my Nook to not load certain https sites?
I can get to gmail fine, but I can't for the life of me load the todoist website
Tried loading your cacerts.bks, doesn't seem like it changed anything
I had no problem getting the Todoist home page. Logging in may be another matter.
Are you using Opera Mobile and did you make the settings change for TLS 1.2?
Background: Really not loving the default New Contact icons and the random colors. Should be easy enough to change. What I tried (and failed miserably...)
MODest ROM 11 (Twiz/stock 6.01-based)
Flashpoint 5 Kernel
Copied SecContacts_M_OSup_Note_Legacy_USA.apk from
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
to my Win7 PC.
Used 7-Zip to unpack the file to a temporary folder.
Found the .qmg files I didn't like.
Found a .qmg that would be a passable replacement for the ones I didn't dig.
Made 11 copies of that image in a working folder.
Renamed each copy to the exact name of each of the 11 files I wanted to replace.
Dragged those 11 files back into the open .apk in 7-Zip
On the Phone, in Root Explorer:
Made a copy of SecContacts_M_OSup_Note_Legacy_USA.apk in the same folder:
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
deleted the original
Copied my mod'd apk back into this folder and set the perms.
Rebooted.
No Phone or Contacts on home screen or in Apps
Tried to 'install' the apk from Root Explorer.
Wouldn't install
Tried to delete cache & Dalvik from TWRP.
No Joy.
Tried to do a partial Nandroid restore of Contacts and sec.phone from Titanium (nothing there called /systempriv-app/SecContacts_M_OSup_Note_Legacy_USA)
No Joy.
Nandroid restore from TWRP.
Back to normal.
Okay, what did I do wrong, and how can I change the icons?
Should I have used APKTook instead of 7-Zip, created a new signature, etc?
Should my mod'd apk somehow be flashed from recovery rather than copied to a system folder?
Is this some perverted Samsung-ism that would have worked fine on any other phone on the planet?
Thanks for reading.
ForestCat said:
Background: Really not loving the default New Contact icons and the random colors. Should be easy enough to change. What I tried (and failed miserably...)
MODest ROM 11 (Twiz/stock 6.01-based)
Flashpoint 5 Kernel
Copied SecContacts_M_OSup_Note_Legacy_USA.apk from
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
to my Win7 PC.
Used 7-Zip to unpack the file to a temporary folder.
Found the .qmg files I didn't like.
Found a .qmg that would be a passable replacement for the ones I didn't dig.
Made 11 copies of that image in a working folder.
Renamed each copy to the exact name of each of the 11 files I wanted to replace.
Dragged those 11 files back into the open .apk in 7-Zip
On the Phone, in Root Explorer:
Made a copy of SecContacts_M_OSup_Note_Legacy_USA.apk in the same folder:
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
deleted the original
Copied my mod'd apk back into this folder and set the perms.
Rebooted.
No Phone or Contacts on home screen or in Apps
Tried to 'install' the apk from Root Explorer.
Wouldn't install
Tried to delete cache & Dalvik from TWRP.
No Joy.
Tried to do a partial Nandroid restore of Contacts and sec.phone from Titanium (nothing there called /systempriv-app/SecContacts_M_OSup_Note_Legacy_USA)
No Joy.
Nandroid restore from TWRP.
Back to normal.
Okay, what did I do wrong, and how can I change the icons?
Should I have used APKTook instead of 7-Zip, created a new signature, etc?
Should my mod'd apk somehow be flashed from recovery rather than copied to a system folder?
Is this some perverted Samsung-ism that would have worked fine on any other phone on the planet?
Thanks for reading.
Click to expand...
Click to collapse
That apk took me a long time to figure out too. It's one of the apps you I had to modify for multi dpi. The only way I know of is to change the compression when you're putting the app back together and even then it took a couple tries. There's probably a better way but the compression change seems to work well enough.
I don't know if 7-zip has this option, but with winrar you can change the compression to "store". You should know right away whether or not it worked. You'll see the little phone icon in the bottom left of the lock screen. You may still have to do a factory reset to see your changes (probably not though) but the app should work without it.
By the way, you can swap those image files for .png files if you'd like. Just delete the corresponding .qmg or .pio file.
I saw your post in the rom thread about theming TouchWiz. You should check out @supergrobi94's theming threads. He's put together an impressive collection of options for 6.0.1 and 5.1.1 and there's also a [how to] section that uses the vrtheme zip that will modify the res folder of a specific app without having to break it down. I'm not sure how active he is these days but he's always been very helpful with requests and questions in the past if you need it.
Supergrobi94's theming threads:
This one has all the themes
This is the [how to] thread
kevintm78 said:
That apk took me a long time to figure out too. It's one of the apps you I had to modify for multi dpi. The only way I know of is to change the compression when you're putting the app back together and even then it took a couple tries. There's probably a better way but the compression change seems to work well enough.
Click to expand...
Click to collapse
Ah, that makes perfect sense. But I'd never have figured it out myself, lol.
I'll dig into those theming threads, thanks.
kevintm78 said:
☆☆Edge Panel for ModestRom v11☆☆
DOWNLOAD-This will change your Contacts app to the S6 version and the IncallUI app to the Note 7 version because the people stripe will not work with the N4 contacts.
Click to expand...
Click to collapse
OK, this is from the MODest ROM thread, but I think it's germain here.
SO.....
If I want to 'try out' that Edge Panel, is there a way to revert back to the stock apps in question other than restoring a nandroid backup or re-flashing the ROM?
I ask because I'm thinking that, at least in the case of the Note 4 and its well known memory problems, 'bulk' memory writes like ROMs, nandroid retores, etc., stress the device, so I'm trying not to do it more than I have to.
During my last episode(see above) putting the stock apk back in its original folder didn't work.
Is there a standard procedure for either android generically, or touchwiz specifically, for safely reverting back to the stock system apps after experimenting w/ custom stuff?
EDIT: Just tried something. In Root Explorer, went into:
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
and simply renamed the .apk to .foo
Rebooted.
No Contacts, as expected, but no Phone either??? Not sure why.
Anyway, back into Root Explorer.
Rename .foo back to .apk
Reboot.
Still no Contacts or Phone, so something bigger at work here.
Before I have to restore Nandroid anyway (unless there's a better way???),
I flashed your EdgePanel.zip in TWRP to see if it would restore the Phone/Contacts apps.
Wiped the cache. Reboot.
Edge Panel is now there, but still no Phone or Contacts. WTF???
Last resort-TWRP- Factory Reset.
Now the Contacts/Phone are back (and all my other stuff is gone, lol)
So is whacking the Data a necessity here?
If so, it makes trying out things related to the phone/contacts a LOT more tedious...
Any workaround???
Thanks again.
ForestCat said:
OK, this is from the MODest ROM thread, but I think it's germain here.
SO.....
If I want to 'try out' that Edge Panel, is there a way to revert back to the stock apps in question other than restoring a nandroid backup or re-flashing the ROM?
I ask because I'm thinking that, at least in the case of the Note 4 and its well known memory problems, 'bulk' memory writes like ROMs, nandroid retores, etc., stress the device, so I'm trying not to do it more than I have to.
Click to expand...
Click to collapse
No, it doesn't look like I ever made an easy way to go back. I had thought I did but I'm either overlooking it or it's not there. Feel free to rifle through my androidfilehost folders if you want to double check. All of my stuff is very organized so it could be buried in there somewhere.
If you still need a recovery zip let me know and I'll get one together. I'm actually going to make one anyway but if you need it right away I can get on it. I didn't realize that there wasn't a way back to stock.
ForestCat said:
During my last episode(see above) putting the stock apk back in its original folder didn't work.
Is there a standard procedure for either android generically, or touchwiz specifically, for safely reverting back to the stock system apps after experimenting w/ custom stuff?
EDIT: Just tried something. In Root Explorer, went into:
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
and simply renamed the .apk to .foo
Rebooted.
No Contacts, as expected, but no Phone either??? Not sure why.
Anyway, back into Root Explorer.
Rename .foo back to .apk
Reboot.
Still no Contacts or Phone, so something bigger at work here.
Before I have to restore Nandroid anyway (unless there's a better way???),
I flashed your EdgePanel.zip in TWRP to see if it would restore the Phone/Contacts apps.
Wiped the cache. Reboot.
Edge Panel is now there, but still no Phone or Contacts. WTF???
Last resort-TWRP- Factory Reset.
Now the Contacts/Phone are back (and all my other stuff is gone, lol)
So is whacking the Data a necessity here?
If so, it makes trying out things related to the phone/contacts a LOT more tedious...
Any workaround???
Thanks again.
Click to expand...
Click to collapse
That is strange that they are not coming back. You may just want to double check your permissions and that there isn't two of the same apps in your folder. At the time of making that Edge zip I was still using other programs to make zips for me and the major downside to that is having to name the new apps the exact same as the old so it would get overwritten so if it doesn't match you'll end up with two active apps in one folder.
Now I think the best way to do that is to use a binary script (osm0sis has great tutorials for this) to change the app getting replaced to a .bak file and then just copy the new app to the system, set perms, and reboot (dalvik cache/ cache needs to be wiped if it's a framework .jar file). But to each their own. If you can get the job done a better way then I would use what you're comfortable with.
My system to test apps isn't much difference than yours. I think the only thing I do differently is change the app to be replaced to .bak instead of .foo although I can't imagine there's much difference. There's been a few apps like the Contacts app that gave me a bunch of trouble when modifying them but I can't remember ever having trouble bringing back the stock app. I wish I had more insight on that situation for you. If push comes to shove I would reflash the rom zip over factory reset only because the factory reset won't correct the system partition problem, if that's what's going on in this case.
kevintm78 said:
If you still need a recovery zip let me know and I'll get one together..
Click to expand...
Click to collapse
First, Merry Christmas!
Thanks very much. No rush on that, I'm OK on the Edge version for the minute.
What would be extremely useful if you have some time/curiousity would be to replicate my steps, ie renaming the untouched apk in a fresh MODest flash (i.e. break the contacts/phone function), and then see if you can get the whole thing working again without a factory reset, or if not, why. I see on xda, you & I are not the first ones to be tripping over this contacts.apk issue.
The other thing that would be telling is after successfully installing the Edge.zip, whether you can modify something (like a picture) within the contacts apk within the zip, reflash the zip and have contacts/phone still working with the change active.
I think there just HAS to be abetter way than Factory Resets.
Thanks so much again for the insights. I really want to become at least minimally competent at hacking my own ROMs together so I don't have to feel like such a noob/mooch on here, but I really do appreciate the help.
What are your weapons/platform of choice, or, if there are better tools for noobs learning the ropes, I'm all ears.
EDIT: Just found this. The last post is interesting...
https://forum.xda-developers.com/galaxy-s5/devs-only/recompile-seccontacts-apk-t3377142/page2
ForestCat said:
First, Merry Christmas!
Thanks very much. No rush on that, I'm OK on the Edge version for the minute.
What would be extremely useful if you have some time/curiousity would be to replicate my steps, ie renaming the untouched apk in a fresh MODest flash (i.e. break the contacts/phone function), and then see if you can get the whole thing working again without a factory reset, or if not, why. I see on xda, you & I are not the first ones to be tripping over this contacts.apk issue.
The other thing that would be telling is after successfully installing the Edge.zip, whether you can modify something (like a picture) within the contacts apk within the zip, reflash the zip and have contacts/phone still working with the change active.
I think there just HAS to be abetter way than Factory Resets.
Thanks so much again for the insights. I really want to become at least minimally competent at hacking my own ROMs together so I don't have to feel like such a noob/mooch on here, but I really do appreciate the help.
What are your weapons/platform of choice, or, if there are better tools for noobs learning the ropes, I'm all ears.
EDIT: Just found this. The last post is interesting...
https://forum.xda-developers.com/galaxy-s5/devs-only/recompile-seccontacts-apk-t3377142/page2
Click to expand...
Click to collapse
I'm not exactly sure what's going on with your contacts app not showing back up. Ever since modestrom v8 (I think) I've been doing the multi dpi on SecContacts_M_OSup_Note_Legacy_USA and every time I would test it doing the same as your way. After a reboot if the modified app was no good, then I would just delete that new app and change the name of the old app back to .apk, reboot and it would work again. I can't remember running in to any problems where I would have to factory reset or reflash the rom to get things working again.
There has been a couple times where I've had to factory reset to get a color change to show up or if you're adding toggles to the QS drop down that also (sometimes) requires a factory reset to show up.
As far as the post you linked, that is exactly how I do it except I use winrar to open the newly compiled app and drag the changes to the original. When I drag the changes over I change the compression method from "normal" to "store". If I don't change the compression the app doesn't work for me. The apps that I've ran into where I had to change the compression are: secContacts, secCamera, secSettings, and framework-res.apk. Any other app that I've worked on can be dragged and dropped without compression changes.
Jar files don't need an original signature though (so long as signature verification has been disabled, which it has in modestrom). They can be decompiled, edited, recompiled, and copied to the system. It does require a dalvik cache/cache wipe though on all framework files except for the framework-res.apk and twframework-res.apk
If you get a chance, you should start using apktool to decompile/recompile. It will make things easier for you in the long run and most of the time if you've made any mistakes in your edits apktool will catch it. If you're not familiar with apktool you can try using Tickle My Android or Advanced Apktool. You may also want to get Apktool by itself. I use all three of them. Android can be fickle and sometimes what works with one app won't work with another. What's nice about TMA and Advanced Apktool is that they'll do the drag and drop method for you, but when the compression needs to be changed that's when I use apktool by itself.
Sorry for the word vomit. Hopefully, this all makes sense.