Related
laymil has posted a much better script for this. As such I will be discontinuing my work on this for now. Not for any hard feelings, but because it is now beyond me to help any further.
As always I am glad to have helped the community in some small way. Thank you all
CHEERS
Geniusdog254 Posted the exact lines in the build prop that needed to be changed. This is a pretty common fix for problems like this between versions of Android. There was some concern however that you may miss some of the newer apps released only for Froyo. I wrote some simple scripts that will fix this for us.
Simply: One puts the Froyo build.prop on your phone. The other puts the modded build.prop on your phone.
Prerequisites
YOU MUST HAVE GSCRIPT INSTALLED
YOU MUST HAVE BUSYBOX INSTALLED
(IF YOU ARE USING PAULS FROYO ROM FROM HERE
http://forum.xda-developers.com/showthread.php?t=686631
IT DOES NOT HAVE BUSYBOX INSTALLED
Also--
There are now 2 downloads.
One will reboot your phone automatically
One will not!
(I recommend this one for anyone that has problems, or doesn't know ADB well.)
Installation
Code:
Download the attached .zip file
Place the "buildprop" folder in the root of your sdcard
Place both "Normal_Froyo.sh" and "Modded_Froyo" files in the gscript folder on your sdcard
Code:
Open Gscript
Press menu and select Add Script
Press Load File button
Select Normal_Froyo file
Press Save button at bottom
Repeat for Modded_Froyo file
After that all you have to do is open gscript and select which one to run.
Normal_Froyo will give you stock froyo build.prop and let you see froyo only apps
Modded_Froyo will give you the market fix build.prop
You can also create shortcuts directly on your homescreen for each script if you wish
-----------------------------------------------
I've decided to skip the update.zip, I've found no way to copy the scripts to the gscript folder on the sdcard this way.
I'm going for an app instead.
P.S. I've never written an app before, java looks like russian to me lol. So if anyone has any tips, or knows any good tut's let PM me and let me know.
------------------------------------------------
fixed no buildprop folder
added NON-autoreboot download.
buildprop switcher v0.3.zip ORIGINAL
buildprop_switcher_no_rebootv0.3.zip NO REBOOT
buildprop swticher v0.3.1.zip DOWNLOAD THIS ONE
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Dayzee said:
When the file is unzipped, there are 4 files - No Buildprop folder. Now I get the part about putting the two .sh files into Gscript folder.
Do I make another folder called buildprop and put build.2.1 and build.2.2 inside?
OR
Do I put build.2.1 and build.2.2 onto the root of the SDCARD?
Dayz xx
Click to expand...
Click to collapse
So sorry lol Didn't notice until I was making the update.zip that I didn't put the other files in a folder IN the zip. Just make a folder on your sdcard called buildprop. and put them in there.
BTW testing the flashable update.zip method right now
thx, seems to work
so no more *#*#etc.. afterwards?
watercool said:
thx, seems to work
so no more *#*#etc.. afterwards?
Click to expand...
Click to collapse
Right.. the checkin service runs on each reboot. So it is not needed.
Worked just fine, but I did have to do the checkin thing. Possibly had poor signal but checkin hadn't done on reboot. Worked fine after that...
Dayz xx
followinginsanity said:
Right.. the checkin service runs on each reboot. So it is not needed.
Click to expand...
Click to collapse
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Namuna said:
Can the checkin method be used, instead of rebooting? I'd much rather switch back and forth via checkin rather than having to reboot.
Thanks.
Click to expand...
Click to collapse
The reboot is built into the script. On my phone, if I checkin, the apps still don't show till I reboot. But show if I only reboot. If checkin alone works for you though, you can remove the reboot command from the script.
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
This worked great for me I also solved my (unrelated) prob with SlideIt by forcing the dictionary to save in the settings, so I'm no longer bothered about losing shortcuts stuff on a reboot.
Dandy!!
tested again with a second n1. works perfect! automated checkin works perfect.
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
Mine did this as well, though I am unsure why just yet. Been busy all day.
Mikey1022 said:
Can you please post what changed in the .prop file.
Also you didn't add the video codecs in the "new" prop file
Click to expand...
Click to collapse
The only thing I changed from the stock to the "modded" build.prop were these 2 lines
from this
ro.build.description=passion-user 2.2 FRF50 38042 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys
to this
ro.build.description=passion-user 2.1-update1 ERE27 24178 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
I didn't add anything else to these. If you would like other things added to the build.prop files. You are welcome to edit them yourselves, or let me know what things you want changed, and I can include them.
I can make it user friendly. With descriptions for each modded line, then you can simply un-comment the options that you want.
PS: I thought I had the flashable update ready, but the update-script is giving me problems. ANYONE that wants to help please let me know. I'd really like to get this out to everyone.
InGeNeTiCs said:
I'm not sure what happened, but after following the instructions exactly, my phone crapped. It got as far as the first nexus logo (non-animated), then the buttons lit up and I got a black screen. And that's how it stayed.
Any ideas?
Click to expand...
Click to collapse
same thing here....ANY IDEAS????????????
This is a great find, inductions were perfect and easy to follow. Not one issue getting all my paid apps back! Thank again!
JDMSirEK4 said:
same thing here....ANY IDEAS????????????
Click to expand...
Click to collapse
To anyone that can't get thier phone to boot all the way after doing this
Its not a big deal. Your phone booted. But the build.prop didn't get copied before the reboot.
If you did a nandroid before you tried it. Restore that!
If you didn't, OR you know how to use adb. Do this
Code:
adb remount
adb push [COLOR="red"]/path/to/build.2.1(or)build.2.2[/COLOR] /system/build.prop
adb reboot
I hope to have this fixed quickly.
ANYONE WHO'S PHONE WILL NOT BOOT AFTERWARDS!
Check and make sure you put the files in the right place.
build.2.2
&
build.2.1
go in
build.prop FOLDER ON YOUR SDCARD
that was the only reason I got the error, i deleted the files off my card when i was testing the flashable update.
If you still get an error. open both files in the gscript folder, and remove or comment out the reboot line. Then tell me what error you get in gscript.
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
r0adki111 said:
So I did this and am able to see the new apps. When I reboot the phone I cannot see a bunch of old apps in my launcher. I revert to the normal script and reboot again and still cannot see a bunch of my apps. Appbrain says theyre installed and I can open them from there but no widgets or shortcuts for them Any Ideas?
Click to expand...
Click to collapse
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
dictionary said:
Are those apps moved to the SD by any chance? If so, best bet is to go to Settings>Applications>Manage Applications>Find your launcher, and force stop it. Should work after that.
Click to expand...
Click to collapse
Nope they're not on SD. I'll try the fc of launcher.
Ok it worked thank you! but my xiia widget still is not back and I'm assuming others. Anything I can do for the widgets?
Ok installed and reinstated the app. Works great thx again.
Update:
Ok after another reboot, apps don't show again. FC the launcher they come back but not the widgets.. Grrrrrr...
You can fix the extsd write lock by using root explorer navigating to etc\platform\permissions.xml
You need to mount as RW and edit the file to match what I'm pasting below.
You can ignore the middle part about syscope info but change your permissions for "write_external_storage" the "access_all_external_storage" and the "write_external_storage"
Don't delete anything from the file or do this without paying attention. Do not alert the syscope permission in between the 2nd and 3rd permissions that relate to storage.
I found this method through Google but it's worked for me so fast with no problems. If you use root explorer and open the file in text editor when you save the modified file, the original file will have .bak appended to it. The guide I used only changed 2 of the 3 permissions I'm saying to edit but the sd lock fix went away after restarting but since I changed the permissions to what I changed below is been working gray even after restarting.
Remember be careful with how you edit the file, only change it in the places I showed to make sure there aren't any complications. If you type it manually make sure to match the formatting and symbols exactly. If you ate going to cut/paste make sure only to change the permissions to exactly how I show it.
I'm not responsible for any damage or issues caused by following this method incorrectly. Remember to save the file with the original name of permissions.xml and then restart the phone to check your now writable ext sd card.
Much easier to use "SDFix: KitKat Writable MicroSD":
https://play.google.com/store/apps/details?id=nextapp.sdfix
Rodger
I haven't tried that one but I've used the xposed framework app that is supposed to enable extsd write but it didn't seem to work properly for me or was at best unreliable when I tried it. I like knowing what patches or fixes are doing behind the scenes in case I need to change them or if there's a problem or an update and it stops working you can do it yourself especially when its add easy as copy and paste
rbird2 said:
Much easier to use "SDFix: KitKat Writable MicroSD":
https://play.google.com/store/apps/details?id=nextapp.sdfix
Rodger
Click to expand...
Click to collapse
This one hasn't worked for me very much on a few ROMs but I did have a little better luck using the Xposed module mentioned above.
Many thanks for the post, OP. I'll add that to my notes and try it on the next ROM that gives me write issues.
Awesome glad to be able to help. .. when I first upgrades yo NG6 I couldn't believe Google could screw up one of the best features in android phones compared to the iphone. At least we're able to workaround it in the current versions at least fornow
nj12nets said:
Awesome glad to be able to help. .. when I first upgrades yo NG6 I couldn't believe Google could screw up one of the best features in android phones compared to the iphone. At least we're able to workaround it in the current versions at least fornow
Click to expand...
Click to collapse
People wonder why Google apps which work fine are still considered "beta." It's because Google isn't done with something until they screw it up completely, preferably also changing the UI a zillion times so it's unusable on more than one level.
rbird2 said:
Much easier to use "SDFix: KitKat Writable MicroSD":
https://play.google.com/store/apps/details?id=nextapp.sdfix
Rodger
Click to expand...
Click to collapse
This one as well...
https://play.google.com/store/apps/details?id=jrummy.sdfix
Thanks for adding the app add an option but can you give an idea of how well or functions and its reliability
I just rooted my phone a few days ago. My phone decided to upgrade to NG6 by itself and it crippled the SD card almost completely. I had some work arounds, but this just made it so much harder. I downgraded to NC5, had a problem, did a full reset and redid my phone. Did Towelroot V3, SuperSU, turned SDM.apk and FWUpgrade.apk into backups. Then I did the SDFix app, rebooted and now the SD card works like it did with MK2. I'm very pleased.
I am trying to figure out how to extract the camera app from the stock ROM to use in the CM13 ROM. Partly because I would like to use it for slow-motion video and to experiment with it, but also because I would like to turn this into a learning experience. I've been following instructions to flash ROMs for a few years now, but haven't gone farther than that.
So here has been my experience so far:
- Backed up CM13, flashed stock (rooted), and converted the app to user app in order to back it up.
- I noticed that it would crash on startup as a user app, so I converted it back to a system app as an experiment. It still would crash on startup.
- I decided to try going another route and extracted the stock ROM in SuperR's Kitchen. Got the apk, flashed it in CM13. Same situation: crash on startup as user or system app.
I am unsure where to go from here. Any help is greatly appreciated. Thanks in advance.
Side note: I know there is a questions sub-forum too, but I figured it fit here better as it is about extracting an app to mod the ROM. If I was mistaken, please just move the thread over to the appropriate sub-forum.
Masterjuggler said:
I am trying to figure out how to extract the camera app from the stock ROM to use in the CM13 ROM. Partly because I would like to use it for slow-motion video and to experiment with it, but also because I would like to turn this into a learning experience. I've been following instructions to flash ROMs for a few years now, but haven't gone farther than that.
So here has been my experience so far:
- Backed up CM13, flashed stock (rooted), and converted the app to user app in order to back it up.
- I noticed that it would crash on startup as a user app, so I converted it back to a system app as an experiment. It still would crash on startup.
- I decided to try going another route and extracted the stock ROM in SuperR's Kitchen. Got the apk, flashed it in CM13. Same situation: crash on startup as user or system app.
I am unsure where to go from here. Any help is greatly appreciated. Thanks in advance.
Side note: I know there is a questions sub-forum too, but I figured it fit here better as it is about extracting an app to mod the ROM. If I was mistaken, please just move the thread over to the appropriate sub-forum.
Click to expand...
Click to collapse
Did the logcat give any pointers as to why it might have crashed?
It's a camera app, for MiFavor, and only for MiFavor. It's probably depending on something else from the stock ROM, and that's why it's crashing in CM.
I like this idea. I might even look into modifying the app itself, to see if we can get it working outside of MiFavor.
I don't think I worded it clearly enough, the first time I converted it to a user app and back to system, it was still in the stock ROM. Something about the conversion screwed things up. I'll have to flash stock again at some point and grab logcats while it's working and after I screw it up.
In the meantime, I attached a logcat for everything containing "camera" after it was converted to a system app in cm13. It's kind of harsh to look at it in pure text format, but I used the matlog app with its color coding to record it.
To be honest, I'm not quite sure what I'm looking at with this, or if I went about this in the right way.
EDIT: I have no idea why the logcat is not attaching correctly. I'll need to find some other way of doing it.
It works fine under CM according to a friend. You just need the libs to go along with the app.
Here is the WHOLE folder of ZTE camera, he just put this inside the /system/priv-app/ folder and apparently it's working just fine after a reboot.
https://my.mixtape.moe/znyabg.7z
Remember to press thanks and buy me a beer.
It's still not working properly for me, but here are a few things I noticed:
- When I extracted the app from the ROM using SuperR's Kitchen, that folder did exist in /system/priv-app/ZTE_Camera/. However, the directory was completely empty, unlike your download.
- When I installed the app in CM13 and converted it to a system app, it moved to /system/priv-app/ rather than /system/priv-app/ZTE_Camera/.
- I copied the lib folder to /system/priv-app/, didn't work. I then created the folder ZTE_Camera and copied both lib and the apk into it. Didn't change anything. Of course rebooting with each change. I didn't think this would work in the first place, as the application shortcut on my home screen points to /system/priv-app/.
Definitely thanks though for helping me out. Beer... that's another matter. Nasty stuff that is. I can just hear people yelling at me behind their screens lol.
Was it a deodexed ROM? Might need to try it with the odex files? When I check /system/priv-app/ZTE_Camera, there's also an "oat" folder with odex files since this hasn't been deodexed...
Or maybe SuperR's kitchen was trying to automatically deodex while you were extracting.
To be honest, I never understood odex, just throwing ideas out at this point.
Masterjuggler said:
It's still not working properly for me, but here are a few things I noticed:
- When I extracted the app from the ROM using SuperR's Kitchen, that folder did exist in /system/priv-app/ZTE_Camera/. However, the directory was completely empty, unlike your download.
- When I installed the app in CM13 and converted it to a system app, it moved to /system/priv-app/ rather than /system/priv-app/ZTE_Camera/.
- I copied the lib folder to /system/priv-app/, didn't work. I then created the folder ZTE_Camera and copied both lib and the apk into it. Didn't change anything. Of course rebooting with each change. I didn't think this would work in the first place, as the application shortcut on my home screen points to /system/priv-app/.
Definitely thanks though for helping me out. Beer... that's another matter. Nasty stuff that is. I can just hear people yelling at me behind their screens lol.
Click to expand...
Click to collapse
I'm sure it works, friend confirmed it works on CM13 and I'm using it on BrokenOS. To clear it up.
It should be /system/priv_app/ZTE_Camera. And inside that folder should be the apk along with the lib. If you just extract the zip I gave you into priv_app it should just work. I have no idea why it doesn't work for you. Everything about the camera works. Slomo, video h265, the works.
You can try making a backup of the stock camera app using titanium backup then install it on your phone after flashing CyanogenMod. What I would do is flash zad miix then back up the stock camera app with titanium backup. Then transfer the back up to your PC. Then flash CyanogenMod and reinstall the camera app with titanium backup.
as already I will have this phone I start doing this mods
if anyone can search the file this and tell me if an entry is interesting?
I'm currently using LOS 14.1, and the method suggested does not work - File Manager throws an error about R/W, TWRP claims /system is empty, and ADB push says "Successful" but isn't.
NadavCE said:
I'm currently using LOS 14.1, and the method suggested does not work - File Manager throws an error about R/W, TWRP claims /system is empty, and ADB push says "Successful" but isn't.
Click to expand...
Click to collapse
It is working for me, just copied the files with root explorer to priv-app, restarted and it is up and running.
Thanks @BlazingBullets for providing the files!
PS. the only problem so far is that you can't access the pictures right through the app, i think we need the zte gallery for that.
lian00 said:
It is working for me, just copied the files with root explorer to priv-app, restarted and it is up and running.
Thanks @BlazingBullets for providing the files!
PS. the only problem so far is that you can't access the pictures right through the app, i think we need the zte gallery for that.
Click to expand...
Click to collapse
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
NadavCE said:
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
Click to expand...
Click to collapse
Used SuperSU 2.79SR3.
I can confirm using the files provided works. I have the stock MM camera working with all of it's shooting modes !
Any body have the files in a .zip they can upload? I have no computer access and the few apps I tried on my phone seem to corrupt the files.
First app I tried extracted the 7zip file just fine.
NadavCE said:
Root Explorer doesn't work for me either. Did you root with SuperSU or with the Lineage root zip?
Click to expand...
Click to collapse
You have to disable the write-protect on the system partition: in a terminal emulator, preferably in TWRP, type out:
Code:
reboot disemmcwp
Erahgon said:
You have to disable the write-protect on the system partition: in a terminal emulator, preferably in TWRP, type out:
Code:
reboot disemmcwp
Click to expand...
Click to collapse
Thanks, that did it. Copied successfully to /system/priv_app, but it doesn't show up after a reboot. When I accessed the folder and tapped the APK, I got "there is a problem parsing the package."
NadavCE said:
Thanks, that did it. Copied successfully to /system/priv_app, but it doesn't show up after a reboot. When I accessed the folder and tapped the APK, I got "there is a problem parsing the package."
Click to expand...
Click to collapse
Maybe the app permissions are wrong?
Erahgon said:
Maybe the app permissions are wrong?
Click to expand...
Click to collapse
Should I give it full permissions then?
---------------------------------------------------------------------------------------------------------------------------
Update: After giving everything (ZTE_Camera folder, the APK, the lib folder, the arm folder, and all the libs) full permissions, the app works. However resolution is limited to 8Mp 4:3 (3200 x 2400). Can anyone else confirm this?
Hi
I've started around three other threads here on XDA but I never seem*to get anyone answering my questions for something that should be so simple.
Anyway I've been trying to flash a ZIP folder containing third party APK files via TWRP to go alongside my fresh install of Lineage OS. All of the user apps install perfectly fine to the '/data/app' directory, however, system apps that are installing to the '/system/app' directory are only getting half installed. Basically when I boot into the ROM I can see all of the system apps in the app launcher, and even navigating through the phone with a root explorer I can see that I can see the correctly copied folder and file from inside the ZIP folder. For example the Google Snapseed app is stored as the following:-
/system/app/com.niksoftware.snapseed
>niksoftware.snapseed.apk
What's weird is that if I open the apk file and install it with the Package Installer*successfully*installs it but with a '1' suffixed to the end and two folders and a re-named apk file
/data/app/com.niksoftware.snapseed-1
> lib
> oat
> base.apk
For a little test I moved the 'niksoftware.snapseed-1' folder from '/data/app' to '/system/app', deleted the original 'niksoftware.snapseed'*folder and rebooted my phone. As expected the app continued to work perfectly fine with no force crashes.
If you're wondering why I'm installing the apps under a system app, it's because the user(s) I'll be passing the phone onto will be non-technical Android users. When the user needs to do a factory reset, the apps I pre-installed will survive if they're installed as system apps compared user apps that will get wiped.
There is literally nothing on any forums anywhere explaining how to flash system apps via recovery taking the more recent Android the OS' that have been released in the last few years. Could someone please help me out here?
Many thanks
Will
willowen100 said:
Hi
...
Will
Click to expand...
Click to collapse
Personally I never tried to install third party apps like that , but it could be interesting to test this out .
But I think you've made a mistake while trying to create the system folder :
You created this :
/system/app/com/niksoftware.snapseed
But the /com is not needed , I mean it maybe the reason of you issue .
So try to remove the /com :
/system/app/niksoftware.snapseed
Let me know if it worked
RaiZProduction said:
Personally I never tried to install third party apps like that , but it could be interesting to test this out .
But I think you've made a mistake while trying to create the system folder :
You created this :
/system/app/com/niksoftware.snapseed
But the /com is not needed , I mean it maybe the reason of you issue .
So try to remove the /com :
/system/app/niksoftware.snapseed
Let me know if it worked
Click to expand...
Click to collapse
Hi
Thank you for your reply. I've only just realised there is a typo in the directory. The 'com/' should be 'com.' However, I will give removing 'com' altogether to see if that makes any difference.
willowen100 said:
Hi
Thank you for your reply. I've only just realised there is a typo in the directory. The 'com/' should be 'com.' However, I will give removing 'com' altogether to see if that makes any difference.
Click to expand...
Click to collapse
Let me know if it worked , happy to see I helped :highfive:
RaiZProduction said:
Let me know if it worked , happy to see I helped :highfive:
Click to expand...
Click to collapse
I renamed all of the folders inside the zip folder so there is no '.' (dots) in the folder and file names and unfortunately the apps still crash. It's a shame there is no command that extracts the .APK files into their correct directories. I'd love to know how the OpenGApps package works because that basically does the same thing as my ZIP folder.
Sent from my LG-H930 using Tapatalk
willowen100 said:
I renamed all of the folders inside the zip folder so there is no '.' (dots) in the folder and file names and unfortunately the apps still crash. It's a shame there is no command that extracts the .APK files into their correct directories. I'd love to know how the OpenGApps package works because that basically does the same thing as my ZIP folder.
Click to expand...
Click to collapse
GApps does the same thing .
Basically it's a zip file with a script that copy all the file and the directories to the root directory of your phone.
I think the problem is the signature used bybthe third party apps. But that's just an hypothesis , I could be wrong I'll let you search more deep on that subject with Google , hope this helped a bit
:highfive:
RaiZProduction said:
GApps does the same thing .
Basically it's a zip file with a script that copy all the file and the directories to the root directory of your phone.
I think the problem is the signature used bybthe third party apps. But that's just an hypothesis , I could be wrong I'll let you search more deep on that subject with Google , hope this helped a bit
:highfive:
Click to expand...
Click to collapse
I've found a couple of APK/ZIP folder signing utilities but unfortunately they've made no difference.
The part that's going wrong somewhere is the folders that should be created alongside the APK files are not being created.
Sent from my LG-H930 using Tapatalk
I made some videos explaining the situation.
The first video shows the app crashing on launch. The APK file is installed at
Code:
/system/app/Snapseed
I then proceed to install it which is successful and installs itself as a user app found at
Code:
/data/app/com.niksoftware.snapseed-1
Next I rename it and move it to system directory and delete the original directory so there isn't a clash of identical apps. Finally I reboot the phone.
https://youtu.be/mL6ePOMnDQw
The second video I show that it opens up perfectly fine. To show that the two folders inside the
Code:
/system/app/com.niksoftware.snapseed
directory are important, I move them to the internal storage Downloads folder and then relaunch the app. It now crashes. I restore the folders and then app once again works again.
https://youtu.be/hL60APHTV7Q
Will
willowen100 said:
I made some videos explaining the situation.
...
Will
Click to expand...
Click to collapse
Hi , the videos you made made me understand better your issue , but I've a question , when you moved the oat and lib folders to the system , you opened the Snapseed app successfully without any bugs isn't it ?
And because the installation folders are in the system , the factory reset won't affect them .
So is your problem solved ?
RaiZProduction said:
Hi , the videos you made made me understand better your issue , but I've a question , when you moved the oat and lib folders to the system , you opened the Snapseed app successfully without any bugs isn't it ?
And because the installation folders are in the system , the factory reset won't affect them .
So is your problem solved ?
Click to expand...
Click to collapse
Yes you could say I have solved the problem but it's not the solution I'm looking for. I want to be able to install the apps in bulk during the flashing stage using a custom recovery like TWRP I'm using. The order I would flash would be:-
1) Flash Lineage OS
2) Flash OpenGApps
3) Flash additional apps (essentially third party apps from the Google Play Store)
Sent from my LG-H930 using Tapatalk
willowen100 said:
Yes you could say I have solved the problem but it's not the solution I'm looking for. I want to be able to install the apps in bulk during the flashing stage using a custom recovery like TWRP I'm using. The order I would flash would be:-
1) Flash Lineage OS
2) Flash OpenGApps
3) Flash additional apps (essentially third party apps from the Google Play Store)
Click to expand...
Click to collapse
Ok , now flashable zips are field so I can help you
If you want me to do it for you , just upload those files to Google drive and send me the link , I'll make your flashable zip and upload it to Dropbox so you can download it :good:.
The files you should upload :
• Libs folder of every third party apps you want to install
• Oat Folder of every third party apps you want to install
• Base.apk file of every third party apps you want to install
If you want to do it yourself , I'll make you a guide on how to do it ( you require a PC to do it with RAR and Notepad++ or another text editor installed on it )
RaiZProduction said:
Ok , now flashable zips are field so I can help you
If you want me to do it for you , just upload those files to Google drive and send me the link , I'll make your flashable zip and upload it to Dropbox so you can download it :good:.
The files you should upload :
• Libs folder of every third party apps you want to install
• Oat Folder of every third party apps you want to install
• Base.apk file of every third party apps you want to install
If you want to do it yourself , I'll make you a guide on how to do it ( you require a PC to do it with RAR and Notepad++ or another text editor installed on it )
Click to expand...
Click to collapse
I'd rather do it myself please if that's okay with you creating a guide, as I would like to learn how to do it for future reference? I use Notepad++ quite frequently and I use 7-zip to archive everything so I'm all setup there.
This is going to sound stupid but where do I get the Libs and Oat folders from except for copying them from Android? I am aware you can open the APK files themselves but I've never seen the Oat folders inside.
Many thanks again for your help so far.
Will
Sent from my LG-H930 using Tapatalk
willowen100 said:
I'd rather do it myself
...
Will
Click to expand...
Click to collapse
I meant I need the Content of this folder for each apps you want to install as system apps:
/data/app/com.niksoftware.snapseed-1
> lib
> oat
> base.apk
Click to expand...
Click to collapse
You will need this to make the flashable zip.
Copy and paste those files to your download folder ( Internal storage ) , then transfer those folders (and the APK file to your PC in order to use it .
I'm preparing the guide and I'll post it in around 10 min , don't forget to press the thank button on the posts
willowen100 said:
I'd rather do it myself please if that's okay with you creating a guide
...
Sent from my LG-H930 using Tapatalk
Click to expand...
Click to collapse
So , let's start with what you need :
- The folder /data/app/com.niksoftware.snapseed-1 and its content on your desktop
Now what you should do :
1) Extract the 2 folders in the template I made you
2) Open the system folder and create a folder called "app" into it
3) Copy the com.niksoftware.snapseed-1 folder (with the content inside it) and paste it into the app folder newly created
4) Repeate the step above for each and every app you want to install as system app
5) Exit the folders
6) Select the META-INF folder and the system folder and compress them with 7-Zip
7) You are ready to flash the zip to your phone !
My Advice is to do this in your Desktop in first place, because it's more easy to see what you're doing.
When you get used to this, you may do it everywhere (even on your phone).
Don't forget to disable signature verification in TWRP ( if there is the option , I don't remember well)
And make a backup of your phone before every modification , we never know what can happen (but in this case, it'll be okay since we're modifying nothing)
Hope this helped you , don't forget to press the thank button
RaiZProduction said:
I meant I need the Content of this folder for each apps you want to install as system apps:
You will need this to make the flashable zip.
Copy and paste those files to your download folder ( Internal storage ) , then transfer those folders (and the APK file to your PC in order to use it .
I'm preparing the guide and I'll post it in around 10 min , don't forget to press the thank button on the posts
Click to expand...
Click to collapse
I'm just trying to find out if there a more time saving tool that will extract the the lib, oat and base.apk from the containing .apk file so I can do it in bulk on a PC.
The problem I have is that I have about 20+ APK's that will be flashed additionally on top of the Lineage OS ROM and OpenGApps. Thinking how long it took to do one installing it as a user app, renaming it, moving it to the system partition, I would have to do that for everyone. Even if I was to do this method the contents I extracted for one Android architecture (CPU chipset type) used on one device may be completely incompatible on another.
Sent from my LG-H930 using Tapatalk
willowen100 said:
I'm just trying to find out if there a more time saving tool that will extract the the
...
on one device may be completely incompatible on another.
Click to expand...
Click to collapse
Unfortunately I don't know any tool able to do that.
And for the architecture , that's not really a problem
Because there are only 4 architecture :
x86 (rare)
x86_64 (very rare , mostly used on emulators)
arm (most common)
arm64 (common)
And the arm APKs work for arm64 devices , so you just have to do this for arm APKs and it'll be okay for almost every Android device . (Edit 1 : Not really sure of this info, should be good but I can't certify it 100%)
And I know myself that doing that takes time , but if you really want to do that , that's the only way I can suggest.
Do as you feel it , I hope my answers were clear and useful for you.
Let me know what's your decision,
Have a nice day
RaiZProduction said:
Unfortunately I don't know any tool able to do that.
And for the architecture , that's not really a problem
Because there are only 4 architecture :
x86 (rare)
x86_64 (very rare , mostly used on emulators)
arm (most common)
arm64 (common)
And the arm APKs work for arm64 devices , so you just have to do this for arm APKs and it'll be okay for almost every Android device . (Edit 1 : Not really sure of this info, should be good but I can't certify it 100%)
And I know myself that doing that takes time , but if you really want to do that , that's the only way I can suggest.
Do as you feel it , I hope my answers were clear and useful for you.
Let me know what's your decision,
Have a nice day
Click to expand...
Click to collapse
I'm going to go ahead with it. Like you said ARM will work for ARM64. Even if the apps become slightly outdated if I were to flash my ZIP onto future devices, as soon as the Play Store is installed it will hopefully update anyway.
Sent from my LG-H930 using Tapatalk
willowen100 said:
I'm going to go ahead with it. Like you said ARM will work for ARM64. Even if the apps become slightly outdated if I were to flash my ZIP onto future devices, as soon as the Play Store is installed it will hopefully update anyway.
Click to expand...
Click to collapse
Good luck my friend
Yes that is right. I poked around looking for a while until I came across a couple of files that looked good. Yeah I know...
All I did was take from the a530f the /system/etc/permissions/privapp-permissions-com.sec.android.app.fm.xml file and put it into my own directory along with the hybrid radio folder and apk in the system/priv-app/ directory. I set permissions accordingly, rebooted and that's it. Files are zipped and ready. Just set permissions right. I don't even know how to push/pull files exactly so if you're rooted then it's an easy deal.
Oh I used fx file explorer. I also hit "symlink" when I copied the folder with the apk. So just reboot and there was the app ready to go.
Enjoy, Canada! Should work generally the same on Samsung devices I would think. No expert but seems like it should.
Screenshot
Forgot the screenshots and specifics.
1) Download FX File Explorer from playstore (7 day trial and download the root add-on).
2) Put the .xml file in /system/etc/permissions/ and set permission rx- r- r- (you'll have to mount it I believe).
3) Put the folder with apk into /system/priv-app/ directory and I hit "symlink" only. Probably just sets permissions. Reboot and that's it.
*deleted*
the folder in /system/priv-app/ should be rwx r-x r-x and the apk contained within it should be rw- r-- r--
The xml in /system/etc/permissions/ is rw- r-- r--
ALL A530W ON CUSTOM ROMS: you don't have to do this because the rom already has fm radio
Yeah i thought so... that's why i thought i put in the apk twice. NOOB!
So just the .xml file then, correct?
I had no idea it was that easy. Cannot figure out how or why i never saw that in any searches.
So really apart from a few apk's, Samsung just magically omitted the files from Canadian W's.
Unreal. Even more unreal is this "locked chip" talk when really it is just not given access from 6 lines of text.
Unless you can point me to other examples, i am going to sort through other device ROMS and post .xml's for easy access. If it is similar for other Galaxy phones.
587.saboor said:
ALL A530W ON CUSTOM ROMS: you don't have to do this because the rom already has fm radio
Click to expand...
Click to collapse
Umm... ok are saying the .xml is not needed? Nothing is needed? Not quite sure now
mindlery said:
Umm... ok are saying the .xml is not needed? Nothing is needed? Not quite sure now
Click to expand...
Click to collapse
yes because the rom is based on a530f system
587.saboor said:
yes because the rom is based on a530f system
Click to expand...
Click to collapse
So you're saying in order to use the FM radio apk I need to install the SM-A530F ROM?
I think it's better to add the xml instead of flashing an F rom. I know they're the same but if you can grab any firmware from sammobile, flash and no modding I'd love to know about this!
+
mindlery said:
So you're saying in order to use the FM radio apk I need to install the SM-A530F ROM?
I think it's better to add the xml instead of flashing an F rom. I know they're the same but if you can grab any firmware from sammobile, flash and no modding I'd love to know about this!
+
Click to expand...
Click to collapse
I mean IF any a530w has an a530f rom installed already, they do not need to do this because apk and xmls already exist by default from the rom.
and I mean custom roms, NOT official. (so basically every rom available for this device because a lot of developers aren't from Canada)
(and I think official rom from a530f has fm radio too, I never tried flashing official a530f rom )
I have Lightrom on my phone, and it's for a8 and a8+ but the thread is in a8+ forums so check there if you want it
Oh ok yeah for sure. I didn't think any ROMS wwre available.
BUT... for anyone that has an A8 in Canada that has root and likes their current set up (do we ever stop)? Then this is an easy addition.
I used hades A8 port when i had my A5 and i think i got spoiled. I shall go download and flash away now...
Thanks. Gonna peek into the S9 and see if it's the same as well. (Out of curiousity).
Well, after 30 minutes, then 20, I'm done staring at SAMSUNG Galaxy A8 POWERED BY android.
Tell me the secret about installing an F rom onto a W. Not "they're the same." How?
mindlery said:
Well, after 30 minutes, then 20, I'm done staring at SAMSUNG Galaxy A8 POWERED BY android.
Tell me the secret about installing an F rom onto a W. Not "they're the same." How?
Click to expand...
Click to collapse
check pm
finally got it working
i tried on 3 different roms with no luck. finally i got it working on the floydport rom. no xml needed. i had to put the hybrid radio folder and apk into system/apps after mounting read write, then installed with the root installer built in fx explorer, rebooted and now i have working radio. for some reason every time i put them in the priv-apps folder they dissapear on reboot. just posting in case someone else is having problems. thanks for the apk!!
Yes the floyd rom had a file in peemissions already.
When i was doing it i probably did not do it right.
But i was successful at it again after going to stock after January's update.
I used fx and navigate to areas i needed and unlock the mount lock up top along the way and back out unmounting.
If you did floyd, then do the treble rom and not only is it a decent rom on its own and able to switch images easily, it has radio already there.
stringman666 said:
i tried on 3 different roms with no luck. finally i got it working on the floydport rom. no xml needed. i had to put the hybrid radio folder and apk into system/apps after mounting read write, then installed with the root installer built in fx explorer, rebooted and now i have working radio. for some reason every time i put them in the priv-apps folder they dissapear on reboot. just posting in case someone else is having problems. thanks for the apk!!
Click to expand...
Click to collapse
Do the treble!
Worked for me, thanks!
Any luck to perform this on a non rooted stock firmware? May with adb or another thing?
That's a good question. You would need to push just two files. If you had an A8 when released up until a certain point you'd only need to push the .xml
They never even bothered removing the apk.
So, since i am rooted with treble on a device without official treble support from Samsung, and a modified version of one ui, maybe you should try. I think it's a bit easier if you go first.
Is there a simple way to get the FM radio working like you said by just copying a file to a folder? I'm kind of a newbie at this and was wondering if anyone would consider writing the "how to" for this procedure that someone like me could understand. Just a simple step by step 1 2 3 on where to get the fm file and app and how to copy them in the A520W folders to make that FM tuner work. I was a little shocked Canadian carriers would even consider omitting the radio purely based on their greed......... ok, I wasn't really shocked, it's pretty much the norm up here.