Related
Can someone help me understand how we can have root methods for the HD 10, but no custom recovery or ROMs?
Any news or updates on the effort here? I'm willing to pay or donate to get it done!
I REALLY want to turn my tablet into an Android tablet... Not a fire tablet with an almost Android experience.
If we can get some one to create safestrap probably we can have a custom Rom !ade
There's no ROM(s) because root was just gained in December. So far as I know, no developers own a HD 10 (at least none that have said so) so no one is able to build one. I am willing to try, but unfortunately I don't have all the resources yet. There is no custom recovery because the bootloader is still locked (so far as I know). Its very hard, almost impossible to get a custom recovery on a locked device. Give it some more time. Maybe @ggow will surprise us.
DragonFire1024 said:
There's no ROM(s) because root was just gained in December. So far as I know, no developers own a HD 10 (at least none that have said so) so no one is able to build one. I am willing to try, but unfortunately I don't have all the resources yet. There is no custom recovery because the bootloader is still locked (so far as I know). Its very hard, almost impossible to get a custom recovery on a locked device. Give it some more time. Maybe @ggow will surprise us.
Click to expand...
Click to collapse
I have a 'maybe dumb' problem, because we only can flash with FlashFire.
Months ago, I owned a Samsung Galaxy Core Prime. I tried to compile Oreo for it. But, what happened to me is, before I get the ROM to BOOT, I compiled it exactly 17 times, fixing bugs. I never had a problem because I had the TWRP handy, but in this case we will not have a custom recovery at all. If the ROM fails to boot, we'll have to sideload stock ROM. Sideloading stock 17 times... doesn't it look tedious? From my experience, any developer no matter how clever he is, will have to compile at least 10 or so times before getting the ROM to boot???
Thanks!
Supersonic27543 said:
I have a 'maybe dumb' problem, because we only can flash with FlashFire.
Months ago, I owned a Samsung Galaxy Core Prime. I tried to compile Oreo for it. But, what happened to me is, before I get the ROM to BOOT, I compiled it exactly 17 times, fixing bugs. I never had a problem because I had the TWRP handy, but in this case we will not have a custom recovery at all. If the ROM fails to boot, we'll have to sideload stock ROM. Sideloading stock 17 times... doesn't it look tedious? From my experience, any developer no matter how clever he is, will have to compile at least 10 or so times before getting the ROM to boot???
Thanks!
Click to expand...
Click to collapse
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
DragonFire1024 said:
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
Click to expand...
Click to collapse
Hi! I pretty much agree with you. But you never know what it can do until you flash stock Android.
Thanks!
Supersonic27543 said:
Hi! I pretty much agree with you. But you never know what it can do until you flash stock Android.
Thanks!
Click to expand...
Click to collapse
That's one of my projects
DragonFire1024 said:
To be honest, FireOS is pretty awesome with root and debloated. I've not had a single problem debloating, and I'm still going lol.
Click to expand...
Click to collapse
Could be that I don't know how to solve the problems I have, but for me not all the Google play applications I want (for my kid) work. Issues vary from validating my authorized purchase to core functionality of applications not working. Some of the applications refer to Android os content and services that either aren't in fire os, are named differently, or have different functionality.
Not to mention that I dislike my son's user experience... He's only 3, quite smart but I've not been able to strike a good balance of protecting him and allowing him to actually use his tablet without learning wierd tricks to access Google play apps.
I'm ok if I have to stay on Fire Os if I can have complete control over profiles, launchers and have a genuine experience using my Google Play applications. Some of the FreeTime stuff is ok... My son might like some of it. But more importantly I want him to have the far superior applications on Google Play which are not currently available on Fire.
I'm willing to contribute to get a custom rom on the fire 10.
I really want to compile one, my skills are getting blunt without some compiling, but it turns out that I only have a HD 8.
Can someone please educate me on getting the GPS to work with google maps, like my phone? My HD 10 7th gen is rooted w/supersu. I have xposed and flashfire installed.
Is a custom ROM really required for this? I tried GPS tethering over hotpot but even that didn't work properly. I wish Amazon had their own proper NAV app to use the GPS chip, could be a bonus to being a prime member.
kferling said:
Can someone please educate me on getting the GPS to work with google maps, naively like my phone? My HD 10 7th gen is rooted w/supersu. I have Xposed and flashfire installed.
Is a custom ROM really required for this? I tried GPS tethering over hotpot but even that didn't work properly. I wish Amazon had their own proper NAV app to use the GPS chip, could be a bonus to being a prime member.
Click to expand...
Click to collapse
Clear data of 4 Google apps. Uninstall and reboot. Make sure nothing of the apps are left in /data/data. If so, delete folders and reboot. When booted again, toggle off location services for about 30 seconds and turn it back on. Then install the 4 APKs in this exact order: gfs_login, gfs, gms, vending. After install wait about a minute or two and reboot then log in. Wait several minutes, watching the two desktop icons. When they flash, the apps have updated. Go to location services and it might be turned off. If so, turn it on and press accept/yes for ALL OPTIONS. If it's turned on, toggle it off for 30 seconds then turn it on and again accept/yes all boxes that appear.
Sent from my Galaxy S4 using XDA Labs
DragonFire1024 said:
Clear data of 4 Google apps. Uninstall and reboot. Make sure nothing of the apps are left in /data/data. If so, delete folders and reboot. When booted again, toggle off location services for about 30 seconds and turn it back on. Then install the 4 APKs in this exact order: gfs_login, gfs, gms, vending. After install wait about a minute or two and reboot then log in. Wait several minutes, watching the two desktop icons. When they flash, the apps have updated. Go to location services and it might be turned off. If so, turn it on and press accept/yes for ALL OPTIONS. If it's turned on, toggle it off for 30 seconds then turn it on and again accept/yes all boxes that appear.
Click to expand...
Click to collapse
Thanks, although I did not get location prompts at the end. :/
Data was wiped for all 4, and uninstalled. rebooted and verified no data with ES.
Installed google apks in the exact order, waited 2 minutes, rebooted, then logged into playstore.
Went to home screen, saw apps flash after waiting. Went to location services (was off) turned on and no prompts
Turned off, waited 30 secs, turned back on, still no prompts.
Is this any different from your guide here?
Step 6. states "Once all the APKs are installed, open the Play Store and sign into your account and IMMEDIATELY go to settings and TURN OFF auto-updates. "
Perhaps that's what I need to do?
Just ordered an HD10, will this tutorial still work? https://forum.xda-developers.com/hd...7-root-box-t3726443/post75187398#post75187398
Will that debloat Fire OS also?
So I've figured out numerous things that get this closer to a custom rom. I just want to report my progress. As I'm working to get my PC in a good enough shape to run Windows and Linux again, I can't compile from source yet. my biggest issue is space. I need to free a lot up. But that doesn't mean anything.
I have been able to track down a lot of useful old school tools here on XDA. The amount of resources that exist on this site never cease to amaze me. Given what I've been doing to these tablets (the resources are old, 2012 onward), I kept looking in that era for tools to assist in getting us to a rom. In the past week I've been able to do these things, with success but have not tested a rom yet. Amazon has had it a bit more difficult with this device.
- Successfully deodexed the stock ROM 5.6.1.0. This was very easy to do...once I found tool that was compatible with deodexing Lollipop. Apparently it not easy to do.
- Successful library integration and editing of a stock AOSP Gallery3d apk. Fully 100% operational and full picture editing availability. Combine my wallpaper discovery, Amazon Photos is no longer required as a wallpaper or gallery source.
- Successfully addition of other surprises
- Figured out how Amazon restocks the ROM on a reflash. In the update.bin is a .dat file. When compiled, produces the system files in whole fresh stock. This can be edited then recompiled back into a system.img or can be used to build a ROM .zip style. That also means once I can build from source, a real ROM can be built.
- Will be pre-rooted with busy box.
- Viper4Android
- Ad blocking from open source free ware.
- Includes my framework and Settings mods.
Any questions please feel free to ask.
Have a new 2015 HD 10. Will definitely be following your progress
FuNKSioN said:
Have a new 2015 HD 10. Will definitely be following your progress
Click to expand...
Click to collapse
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Sent from my Galaxy S4 using XDA Labs
DragonFire1024 said:
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Click to expand...
Click to collapse
Try digging in files. I guarantee that Amazon took a very similar approach as Samsung did, requiring you to flash a break encryption zip.
I would try to help, as I've made several AOSP roms, but that was when Android 4.4 was the newest and you could compile it with 4 gb of ram.
Once I upgrade or get a new PC, I will most definitely install Linux, and try to help this forum.
---------- Post added at 06:31 AM ---------- Previous post was at 06:26 AM ----------
DragonFire1024 said:
Or a severe lack of progress...
I have been at it for hours and hours and I am no closer than I was when I made my last post. I've looked at dozens of updater-scripts and the mount points are no different than the Fire 7, but it just won't flash a zip and when the rare chance comes along that the zip does flash, booting doesn't get past the white Amazon logo (first power on logo). I finally managed to get nearly all of the script right, and now when I add assert getprop for device ID verification, it rejects it despite the fields being properly filled out. I'm not giving up, I just need to figure out why.
On a side note, I have been able to do a switcheroo on the system, sorta. In trying to further mod the settings apk, I have been able to use a settings apk from an AOSP rom to replace FireTabletSettings. There is a trick...uninstall the stock FireTabletSettings APK, wipe the caches and dalvik, and took a resigned AOSP settings apk (test key signed), installed it as a user app then converted it to a system app. It installs fine, but I can only get half of it to work. I haven't tried with the framework or systemUI yet because I haven't been successful with the settings.
Back to the drawing boards...
Click to expand...
Click to collapse
Haven't been up-to-date.
Do we have TWRP? If not how are you flashing the files?
I'd be open to porting TWRP to the HD 10 and maybe the 8 if we needed.
Reason being TWRP backups can be converted to a flashable .zip file, meaning that once you've gotten all the AOSP apps working (settings, gallery, etc) you could theme it, debloat it, deodex it, and everything else then save it and convert it to a zip. Would save people the time of doing it, and would be one step forward.
TechNash said:
Try digging in files. I guarantee that Amazon took a very similar approach as Samsung did, requiring you to flash a break encryption zip.
I would try to help, as I've made several AOSP roms, but that was when Android 4.4 was the newest and you could compile it with 4 gb of ram.
Once I upgrade or get a new PC, I will most definitely install Linux, and try to help this forum.
---------- Post added at 06:31 AM ---------- Previous post was at 06:26 AM ----------
Haven't been up-to-date.
Do we have TWRP? If not how are you flashing the files?
I'd be open to porting TWRP to the HD 10 and maybe the 8 if we needed.
Reason being TWRP backups can be converted to a flashable .zip file, meaning that once you've gotten all the AOSP apps working (settings, gallery, etc) you could theme it, debloat it, deodex it, and everything else then save it and convert it to a zip. Would save people the time of doing it, and would be one step forward.
Click to expand...
Click to collapse
Not sure about the encryption. It has to be a script problem, or the system partition won't accept zips and that's the barrier. However if I just flash the system directory instead, everything works fine. I can flash stuff into it just fine that way, but seems any time I go the way of the partition, I can't win. Flashing your own system image works too. However I haven't been able to get one to flash if I modify it. So I can decompile a system.img add to it, remove items and recompile it and it won't flash.
I am using flash fire to flash zips. We still have a locked bootloader so twrp isn't a likely option.
Sent from my Galaxy S4 using XDA Labs
DragonFire1024 said:
So I've figured out numerous things that get this closer to a custom rom. I just want to report my progress. As I'm working to get my PC in a good enough shape to run Windows and Linux again, I can't compile from source yet. my biggest issue is space. I need to free a lot up. But that doesn't mean anything.
I have been able to track down a lot of useful old school tools here on XDA. The amount of resources that exist on this site never cease to amaze me. Given what I've been doing to these tablets (the resources are old, 2012 onward), I kept looking in that era for tools to assist in getting us to a rom. In the past week I've been able to do these things, with success but have not tested a rom yet. Amazon has had it a bit more difficult with this device.
- Successfully deodexed the stock ROM 5.6.1.0. This was very easy to do...once I found tool that was compatible with deodexing Lollipop. Apparently it not easy to do.
- Successful library integration and editing of a stock AOSP Gallery3d apk. Fully 100% operational and full picture editing availability. Combine my wallpaper discovery, Amazon Photos is no longer required as a wallpaper or gallery source.
- Successfully addition of other surprises
- Figured out how Amazon restocks the ROM on a reflash. In the update.bin is a .dat file. When compiled, produces the system files in whole fresh stock. This can be edited then recompiled back into a system.img or can be used to build a ROM .zip style. That also means once I can build from source, a real ROM can be built.
- Will be pre-rooted with busy box.
- Viper4Android
- Ad blocking from open source free ware.
- Includes my framework and Settings mods.
Any questions please feel free to ask.
Click to expand...
Click to collapse
I mean, if PC performance is an issue I can give you access to a brand new xeon if it means there will be a custom ROM out.
Been thinking about buying the Fire HD 10 this black Friday and flash the Amazon garbage out, and was amazed to see none exist even though it has been a year since they figured out the rooting.
This will be an outstanding value if it was possible...
Hello everyone.
Can we please get root on this phone?
Specs are:
Operating System: KaiOS
System chip: Qualcomm Snapdragon 205 MSM8905
Processor: Dual-core, 1100 MHz, ARM Cortex-A7, 32-bit, 28 nm
Graphics processor: Adreno 304
System memory: 0.5 GB RAM
Built-in storage: 4 GB
Storage expansion: up to 64 GB
sgmarouf said:
Hello everyone.
Can we please get root on this phone?
Specs are:
Operating System: KaiOS
System chip: Qualcomm Snapdragon 205 MSM8905
Processor: Dual-core, 1100 MHz, ARM Cortex-A7, 32-bit, 28 nm
Graphics processor: Adreno 304
System memory: 0.5 GB RAM
Built-in storage: 4 GB
Storage expansion: up to 64 GB
Click to expand...
Click to collapse
Im also wondering the same thing
Yes, have been able to flash my own system and it is also possible to get ADB.
I am currently working on it, but it might take some days to get something useful out of it. As I just created a new account here, I am currently not able to post any links, but you can find my stuff linked on Twitter via @nexus511.
nexus511 said:
Yes, have been able to flash my own system and it is also possible to get ADB.
I am currently working on it, but it might take some days to get something useful out of it. As I just created a new account here, I am currently not able to post any links, but you can find my stuff linked on Twitter via @nexus511.
Click to expand...
Click to collapse
Good job! :good:
0312birdzhang said:
Good job! :good:
Click to expand...
Click to collapse
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
This is a good news! I just bought a "banana" today, waiting for your good news :fingers-crossed:
nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
Sounds like you've made some impressive progress here, can't wait for more details!
Will you be posting a more detailed tutorial/how-to here or on your blog in the future?
Keep up the great work! :good:
Great work, would be great to uninstalled preinstalled *tty demo games.
@nexus511, any way you could please share the root procedure or point to some resources?
Or...at the very least when you get a spare second, how you did manage to unlock your bootloader knowing Nokia has publicly acknowledge disabling Device > Developer?
Muchas,
nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
fpb4 said:
@nexus511, any way you could please share the root procedure or point to some resources?
Or...at the very least when you get a spare second, how you did manage to unlock your bootloader knowing Nokia has publicly acknowledge disabling Device > Developer?
Muchas,
Click to expand...
Click to collapse
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
0312birdzhang said:
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
Click to expand...
Click to collapse
Cheers mate :good: , that's a step forward (and cookie points to OmniJB's dev for the firefox 52.9 esr trick) - now WebIDE lists all runtime apps in Unrestricted DevTools privileges...which is great should I be willing to debug any of those or create my own. What I am looking for though is a way to *delete/un-install/remove* (no cigar remounting /system/b2g/webapps rw without root) some of the certified pre-installed applications (assistant to start with or the bunch of packaged Gameloft bloatware). Any idea - i've pm'ed @nexus511 for some root procedure but no answer yet?
0312birdzhang said:
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
Click to expand...
Click to collapse
Is there anyway I could revert installing omniJB? I'd love to be able to install factory updates again.
hello all, just give an update on how's everything regarding nokia 8110 is going
fpb4 said:
Cheers mate :good: , that's a step forward (and cookie points to OmniJB's dev for the firefox 52.9 esr trick) - now WebIDE lists all runtime apps in Unrestricted DevTools privileges...which is great should I be willing to debug any of those or create my own. What I am looking for though is a way to *delete/un-install/remove* (no cigar remounting /system/b2g/webapps rw without root) some of the certified pre-installed applications (assistant to start with or the bunch of packaged Gameloft bloatware). Any idea - i've pm'ed @nexus511 for some root procedure but no answer yet?
Click to expand...
Click to collapse
Could you remove the pre-installed apps?
Hi!
It's possible, to get full ADB-Root by injecting a patched adbd-binary. And with real swap instead of zram, the device is more responsive (background-tasks like Launcher/Homescreen are killed less often...)
As soon, as I have build my own patched adbd, I will provide an 'update.zip' -- it seems chainfire doens't like others to use his version. (OpenSource -- anyone? )
BTW: no, I don't have 'su' -- only my own priviledged additional startscript and ADB-Root but for me this is more than enough to 'work'
(my goal is to create native apps with Ada/Gnoga - meaning native but with HTML5-GUI. First tests are working well...)
I would love to have this phone without the pre-installed social media and game garbage, would your planned update.zip allow someone reasonably competent at following instructions to do this easily or is experience required?
It should be possible to remove those apps - but for me it's hard to say how. On my device there were no preinstalled apps/games other than snake. Everything else is (un)installable normally. Could be a region-thing
(I've got the european/german version)
-- but on my device the store seems to be a 'static' bunch of zips - so it could kill the store to just remove those.
(i think I would need to adjust configs for the store if I want to clean them up)
If I remember correctly, there is a flag in the app-manifest to config if an app is removeable... my first try would be to edit this flag and check if I could uninstall it normally after this
On the other hand: there is nearly no need to uninstall - KaiOS-Apps are small and with a sdcard....
(I created an extra 1GB-Swap on /data - even then enough space left)
BTW: if You have a little experience with android-stuff, rooting is simple when You know how
Enable adb --> just type *#*#33284#*#* on keypad of your phone (the digits spell 'debug' )
-- build an update.zip - sign with AOSP-Test-Keys
--- let it create '/data/opt', '/data/opt/bin'
--- put an patched adbd (chainfire's v22 works) in /data/opt/bin
--- create /data/opt/init as a shellscript, remounting / rw, replace /sbin/adbd with patched one, remount / ro kill adbd so it restarts the patched version. (you may add commands for other stuff on boot - I disable zram, enable swapfile, start en Ada-Server....)
--- and add a call to '/data/opt/init' as last line to '/etc/init.qcom.post_boot.sh' so this 'init' will start with root-rights on startup.
This way /data/opt/init will inherit root from /etc/init.qcom.post_boot.sh, so it can replace adbd - and because the patched version won't drop it's root-rights you'll have a root shell over adb.
As You see - it's quite trivial, but at the moment I don't have a patched adbd which I'm allowed to include.
(I hadn't time to build an AOSP-tree until now)
Has anyone tried installing OmniJB from 4pda.ru website? (Sorry can't post links)
If you google "4pda 890710" it will bring it up.
Also, anyway of installing whatsapp yet?
PolePolisher said:
I would love to have this phone without the pre-installed social media and game garbage, would your planned update.zip allow someone reasonably competent at following instructions to do this easily or is experience required?
Click to expand...
Click to collapse
root or create an update to edit /data/local/webapps/webapps.json
it worked on my phone no more s*** games and google stuff
Can I not just replace the /sbin/adbd from the boot.img?
(by extracting the boot.img with a flashable zip, and then unpack/repack with kitchen)
October release is available with or without root
Made a few changes as far as adding in some apk's to hopefully make it stable for everyone.
Besides that, the usual with normal default font BUT lots more choices in the font section.
Enjoy!
*if anyone has solid reasons to remove any apk files i've put back please let me know as some I should not have been removing and others... not so sure
I will no longer be able to provide new copies of this after the October security patch. I no longer own an A8 2018 and without a device to test the work, I do not feel it is appropriate to continue the project. I'd like to thank everyone that participated and I hope you enjoyed using it! If anything changes in the future that will allow me to provide the latest edited firmware, I will definitely be providing it here for you. I am using an S7 now so if you own one and like this work, there shall be downloads available there similar to this one. (Already testing).
Anyone that would like to continue on their own or have access to files used in making it I will try to include as much as possible from the link provided below by the end of October. There is currently a slightly outdated set of files and instructions (from June I believe) on how I made it already available.
Thanks Again!
Oct Security patch zip ready for download
Available with or without root AND with or without exo font - also an attempt to allow printing feature version. "Attempt" meaning I've placed a set of apk files into a separate and clearly labelled zip on the main download page that may allow proper use of the feature which has not been validated as operational by me or any other user. The "print fix" zip is rooted with exo font
This was made ONLY for the SM-A530W! Please do not use if not W (Canadian) variant. Check your phone info before attempting to flash
All ROMS/extras here:
https://drive.google.com/drive/folders/12Vwzn1CxNdT-ISsrOnSL4D353Nr14iRb?usp=sharing
The ROM will function very well and does not require any special patches, kernels, etc except obviously TWRP
Any additional issues you face with added mods most likely will need to be addressed with the creator
*Built by Superr's Kitchen*
Over 100 apps removed
***Find my mobile and pop-up asking to store lockscreen info removed- BE AWARE reduced ability to locate lost device!***
retro shutdown qmg
Overloaded notifications and ringtones
Oreo Weather (pie weather is a serious downgrade)
August Security release
FM tuner and App Lock (Next Radio may now be used starting from July 2019). Gee, THANKS SAMMY! What took you so long? Was it the polar bears?
Goofy selfie stickers that are funny... and creepy *big thanks to hadesRom genius Corsicanu for the find*
Other typical CSC changes
If your plan has wifi calling, turn it on/off once in phone settings to "break in" the qs tile
Dedicated Screen Recorder access in launcher with no shortcut style appearance (if deleted may be re-enabled with activity launcher as shortcut)
Chrome can be safely disabled at any time if desired and auto replaced with system webview
dm-verity + force encrypt already removed
Magisk rooted
Installation is easy as pie
BACK UP FIRST!
Wipe caches, data, system. Internal may be safely wiped and give the "freshest" install but is optional. Then flash away.
Once flash completes, just reboot.
-*Usage*-
You are free to use any ideas/changes included in the zip. In fact, I encourage you to do so. I've mostly pieced together work from other very difficult projects to create this. Nobody has asked me to add, remove or alter anything contained within this page or in shared downloads. Their work is everywhere and it's what made this possible.
Built with Superr's Kitchen
Some screens to sample below. yay
nobody home
empty
I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.
Ok. I can't really suggest anything other than the obvious.
But you've let it boot once before trying, and are adding the apk as well after flashing magisk in twrp?
Hard to figure that one out. If you're using Magisk, i am assuming.
burnt_31 said:
I followed your instructions. I was already updated to pie previous to flashing your rom. I am not able to get root. Any ideas why. I also have the Canadian version. Good job on the Rom, I like it. I wish I could get root.
Click to expand...
Click to collapse
Have you tried 19.1 you may need to flash twice.
I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.
burnt_31 said:
I used magisk 19.1. First I used supersu and magisk uninstaller first. I have root now. Thanks for your help. It amazes me that sometime we over look the simplest thing.
Click to expand...
Click to collapse
I know exactly what you mean. I do it all the time.
Nice you got it going. It's pretty lame if you don't root this. I just cut it up and added a couple things and they can be taken out, except radio and the recorder.
Curious if i got it right. If you're on anything other than VMC, is call recording and other micro features working? All the cscfeature xml files are decrypted so you can see what was done.
Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.
burnt_31 said:
Everything seems to be working. I appreciate the work, Canadians are usually the last to get Roms. Most are made for the sm-a530f model. I was using the wrong method. One post said about waiting 166 hrs to reboot your phone after zipping RMM_State Bypass etc. etc.. Your way is simple. Once I get a chance I wlll have a look at what you have done, I work long hours. And as you said, what is the point if you cant root. Thanks again.
Click to expand...
Click to collapse
It is 168 hours no reboots and rmm did work that rmm was for Oreo.
I think his would be fine but no guarantees.
Custom kernel 2.0 flash twice.
Light rom works without issue make sure you flash magisk.
Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks
fabian_barrios said:
Hello I have a530f model with lastest pie version for Russia. I would like to install native screen recorder. Can yo help me ? Please. My email is [email protected]. thanks
Click to expand...
Click to collapse
Yeah bud. If you unzip the attached file, you can place it in /system/priv-app/ and make sure the permissions are set correctly for the folder and apk. Compare with other apps in the directoty and make it the same.
Then get the activity launcher app from the play store. Use that to make a link for it.
Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8
boominboodhoo said:
Getting random freezes sometimes, have to reboot phone using hardware buttons. Using Freedom A8
Click to expand...
Click to collapse
okay thanks for that. It is probably from my csc edits. I can adjust for freedom and hope it makes a difference.
Anything else to mention about it? What you did before flashing, are you using latest twrp, root or non root.... anything at all
no-verity... favourite snack... p.i.n. number(s)... oops sorry not the last two. My mistake. TOO MUCH info. Disregard.
Do a search on xda for rooting your model for the correct version of twrp. U will need no verify no encript. I used the latest Magisk to root. Supersu did not work. I used twrp for the A8 plus and had problems. Get the right one. It's a great rom. https://www.google.com/amp/s/forum....ery-twrp-3-2-2-0-galaxy-a8-2018-t3818201/amp/
I am looking at the csc for FMC and it appears i have doubled an entry. I need to go over all of them to see if i've done it elsewhere. I will have 2 updated ones hopefully late tonight. (Takes forever to upload).
Not sure if that is the cause but i will definitely adjust it.
Quick question in regards to your Rom. I been using it for a while now. Its the best one I can find, I did post a few times at the start. By any chance, did u get adoptable storage working? I know Samsung removed it in Pie. I tried root essentials but still no luck. Thus is not my first time rooting or installing roms. I started with the HTC 1. Lol. So far, u have the best rom for the A8 2018. Its nice and clean. Almost compares with lineage in my opinion. Thanks again. And by the way, I am Canadian.
Thanks
Hey i appreciate the gesture but even though i "made" this, i did it because of other people. SuperR is an invaluable tool. Then you got magisk, the twrp recovery and heck even give ol' Sammy some credit, haha. All i did was spend time learning everything from this site. I can't stress that enough. I still have not paid for superR and i am going to see how i can right after this.
ANYWAY!
Your question. I've never attempted it but i am very certain there's a magisk module that'll do it.
It involved formatting sd to ext 4 or 3. So i will get on it. Got a few 64 gig cards to spare. If you have a computer, grab the superR linux distro. I've run it on 32 bit machines. K... pay superr... adopt a card heheh.
I will look again in the magisk module section. And I give everybody right now credit for all their hard work and sharing it amongst all of us. Thank you. Thank you. I love modding my phones and I could not do it without everybody's help. All my PC's are 64bit.
Nice. If you need any help just ask. Just bought the kitchen.
I'll have something very soon. Mexico's pie has the classic csc folder of old. I think we should unify with some fiesta pie zip ui sorta thingy... um rom.
I DONT TAKE ANY WARRANTY WHATSOEVER IN ANY DAMAGE THAT MAY RESULT IN FOLLOWING THIS GUIDE OR USING THE SOFTWARE, ROM IN QUESTION, IN ANY WAY, MAY IT BE AS INTENDED OR NOT. IF YOU HAVE ANY FEELING YOU COULD END UP SUING ME FOR RISKS *YOU ALONE* ACCEPTED TO TAKE, YOU SHOULD IMMEDIATELY STEP BACK AND LEAVE THIS POST, ALL THE OTHERS: BE CAREFUL. YOU WILL LOSE ALL OF THE DATA ON YOUR PHONE'S USERDATA, CACHE AND SYSTEM PARTITION AND THE PHONE WILL BE FACTORY RESET!
STOCK FIRMWARE INSTALLER: https://support.wikomobile.com/maj/Lenny5_OPE_V34.zip <-- if you brick your device.
Hey folks
This is just a brief explanation on how i built this ROM, a complete guide to building the rom may be published at a later point in time. For the Downloads, go to the Links section. The flashing guide will be focused on Lenny 5, but the image may work on other treble-enabled devices, too, so feel free to try and report if your device works with this build.
Build variant: arm-aonly-floss-su-userdebug
If there's interest in other build variants (specifically with microg and floss - fdroid, moz-nlp, openweatherprovider - implemented), ask me, i will do my best.
Build description:
I have an old Wiko Lenny 5 around here and wanted to use it as a Kodi Remote etc. at home, but didn't want to use their stock ROM. Also i wanted some freedom in using my device, specifically a rooted device and microg implementation. After trying to build TWRP with no success and the Wiko Build information being massively outdated i then focused on Generic System Images, as Lenny 5 is Treble-enabled. Big thanks to @phhusson for the whole lot of effort he put into building AOSP GSI's (and also clues towards building LineageOS GSI's). After having AOSP9 installed on it for some time, i got bored and tried to compile LineageOS using the patch-and-build system provided on phhusson's github. That worked just great on AOSP9, but failed to build a bootable LOS16 in the first place. So after some recherche, i stumbled across @AndyYan's thread, containing some LineageOS GSI's prebuilt and ready to use. These worked great on my phone, but as stated above, i wanted to customize my LineageOS even further, so i manually patched my build-tree with AndyYan's Lineage-Treble-Patches by doing what this build script does, tested and it booted (i guess it's mainly related to the SELinux Policies not being correctly built for LOS with only phh's treble-patches). So far so good.
Additionally, i implemented the MicroG services by cloning these prebuilts on github to the respective folder in the build tree and before the build executed
Code:
export WITH_SU=true
to include LineageOS's root system in the build. I adapted the treble_arm_afS.mk device config to not use phh's su and the device/lineage/floss.mk file to include
FDroid
FDroidPrivilegedExtension (which is being built from treble sources)
MicroG services (use Play Store Apps)
FakeStore (use Play Store Apps)
MozillaNlpBackend (MicroG Network Location backend)
NominatimNlpBackend (MicroG Network Location backend)
OpenWeatherMapWeatherProvider (for LineageOS Weather Provider)
You are then free to use no Playstore at all or i.e. Yalp Store to download Play Store Apps.
After downloading the Image you may need to Unpack it via 7-zip or another tool.
Flash the device:
To install this custom ROM on the Wiko Lenny 5, in your stock ROM go to Settings->Developer Options->OEM unlock->Enable. Also, in the Developer Options, make sure, ADB Debugging is active and, on prompt, accept debugging connections from your computer.
On your computer, enter Command Prompt and issue the following commands:
Code:
adb reboot bootloader
*wait for device reboot*
fastboot oem unlock [COLOR="Red"]<-- this will factory reset the device!!![/COLOR]
*press vol up on the phone to allow unlocking the bootloader, and wait for the phone to return to fastboot mode*
fastboot erase userdata
fastboot format cache
fastboot format system
fastboot flash system <path-to-the-downloaded-gsi>
*wait for each process to finish*
fastboot reboot
now, wait for the phone to reboot, it should, after some time, show you the usual LineageOS startup screen. Take your time to set up your phone. To make MicroG and FakeStore work properly, you will have to Go to Settings->Apps&Notifications->App-Permissions->Spoof package signature->Menu->Show System Apps and allow FakeStore to spoof Signature. Go to Settings->System->Advanced->MicroG Settings and add your Google account. Activate Device Registration. Then activate Google Cloud Messaging and Google SafetyNet, if you want to take advantage of those services. Inside the UnifiedNlp Settings choose MozillaNlp in the first, and NominatimNlp in the second setting.
Go back and choose "Self check", if required, if required, grant MicroG GmsCore the permission to spoof signature, this should make most of the boxes go "checked". If Phonesky shows errors about signature spoofing, this should normally be gone after a reboot of the phone (given you allowed FakeStore sig spoofing). Disable battery optimization and then reboot the phone.
Check back in MicroG Settings->Self check, if all the boxes have been checked. If not, most mandatory points are self-explanatory.
This Lineage ROM will not allow you to update to a newer version. I cannot guarantee continuous updates, but encourage you to try building LineageOS treble with the way explained above, yourselves. If enough interest is around, i will consider doing updated builds from time to time.
Update:
Today i compiled a recent source tree containing the 5th of October patches. I will try to keep up with updating the Image whenever security fixes are released. The download links below have been updated to the newest version. To update your phone without deleting the data on it (make sure you have adb debugging enabled), you can simply do
Code:
adb reboot bootloader
fastboot flash system <system-image.img>
fastboot reboot
and then give your phone some time to "update". it should boot normally without erasing your data.
Links:
ROM .7z [~430MB]
ROM .img (~1.1GB)
(version was compiled at 19th of October '19, containing the October 5th security fixes.)
Let me know if this works for you, too!
Cheers
ivelischt
*reserved for additions/build guide*
Nice work
Nice work, I'll test the ROM later or tomorrow, also I like to see some development for this phone, also, It would be very nice to develop a custom recovery for it for better flashing experience and being able to flash gapps.
I have kinda workplace on my PC, I'm still wondering to build my first ROM but I think it will take lot of time.
Hanthonious said:
Nice work, I'll test the ROM later or tomorrow, also I like to see some development for this phone, also, It would be very nice to develop a custom recovery for it for better flashing experience and being able to flash gapps.
I have kinda workplace on my PC, I'm still wondering to build my first ROM but I think it will take lot of time.
Click to expand...
Click to collapse
Thanks. The custom recovery thing is a bit more difficult for treble devices, but i'd be happy to learn more from more experienced people.
I was not able to get TWRP running despite "successful" Custom recovery builds.
The build is quite straightforwards if you have some experience on compiling with linux. But you need around 200400Gigs of free space per build tree (lineage, aosp, ...). The most difficult thing for me was to alter the sources for inclusion of the packages i mentioned above, including microG. to build with opengapps, i expect, you'd use the same approach to include them in the build tree as with microG, just using the other packages and probably slightly customized CUSTOM_PACKAGES config. there is a k300 recovery out in the wild net. so there should be at least *some* possible way to port twrp for the k400, too.
about the time to build the rom: it took me about a day to sync sources and, using 2 cpus at 4gig's of java virtual memory, about 6 hours to compile the first round. after that, only compiling the changes made, it took me about another half an hour to recompile the changes. the editing process is marginal, if you know how to append to/remove from/patch the source files, the lineage4microg and treble rom-builder bash-scripts on github give you a pretty good insight in how to apply patches. also, from the dockerfiles you can get a list of all the dependencies your system needs to build the tree. i used these sorts of "tricks" to ensure my build runs well.
so far from me. i will try to find some free time in the future to put up some guide on how i built the rom as-is.
feel free to report if the rom works on your device!
best regards
edit: 400Gigs is better
ivelischt said:
Thanks. The custom recovery thing is a bit more difficult for treble devices, but i'd be happy to learn more from more experienced people.
I was not able to get TWRP running despite "successful" Custom recovery builds.
The build is quite straightforwards if you have some experience on compiling with linux. But you need around 200400Gigs of free space per build tree (lineage, aosp, ...). The most difficult thing for me was to alter the sources for inclusion of the packages i mentioned above, including microG. to build with opengapps, i expect, you'd use the same approach to include them in the build tree as with microG, just using the other packages and probably slightly customized CUSTOM_PACKAGES config. there is a k300 recovery out in the wild net. so there should be at least *some* possible way to port twrp for the k400, too.
about the time to build the rom: it took me about a day to sync sources and, using 2 cpus at 4gig's of java virtual memory, about 6 hours to compile the first round. after that, only compiling the changes made, it took me about another half an hour to recompile the changes. the editing process is marginal, if you know how to append to/remove from/patch the source files, the lineage4microg and treble rom-builder bash-scripts on github give you a pretty good insight in how to apply patches. also, from the dockerfiles you can get a list of all the dependencies your system needs to build the tree. i used these sorts of "tricks" to ensure my build runs well.
so far from me. i will try to find some free time in the future to put up some guide on how i built the rom as-is.
feel free to report if the rom works on your device!
best regards
edit: 400Gigs is better
Click to expand...
Click to collapse
The ROM works great but I'd like to see one like this with gapps to install on my device (freaking system image size), I've never used MicroG before and I don't know well how to use it.
Also, if you have the knowledge (I'm pretty sure you know more than me) we can investigate a way to create a TWRP version for K_400
Hanthonious said:
The ROM works great but I'd like to see one like this with gapps to install on my device (freaking system image size), I've never used MicroG before and I don't know well how to use it.
Also, if you have the knowledge (I'm pretty sure you know more than me) we can investigate a way to create a TWRP version for K_400
Click to expand...
Click to collapse
Hi Hanthonious
ivelischt said:
If there's interest in other build variants (specifically with microg and floss - fdroid, moz-nlp, openweatherprovider - implemented), ask me, i will do my best.
Click to expand...
Click to collapse
as the microG variant requires some "special sauce", namely the ability to spoof signature as well as other small fixes in the source code, my source tree is a bit different from the "vanilla/gapps" source tree. thus, to build variants not containing microg, you can simply sync the lineage source tree and apply the additional phh treble sources&patches. *edit: next to phh's patches, you will also need AndyYan's patches; you can find information about it in the OP. given, i write a guide (which i still intend to, but this takes some time), the patching step will be explained more clearly* basically, it's one step less than compiling it with microg. at the moment i cannot afford enough disk space to create another work tree, which is why i "can't promise" other build variants, until this issue is gone. which may be tomorrow or in a year. maybe you can find a gapps-version of treble-lineage 16 here in the xda boards. otherwise you will have to wait, or try to build it yourself. also, you might be interested in @AndyYan's lineage version, which is vanilla (no gapps or microg).
i would guess that the system image will not grow excessive just by including opengapps, but i may be wrong. i think that you'd possibly would have to choose a "non-complete" opengapps-package, to make it fit.
to quickly summarize what microg does is, that it spoofs its signature to make your phone think that you have the real Google Services Framework, Google Cloud Messaging, etc. services installed. this makes apps, which depend on these services, work even though you don't really "have" them. additionally, microg establishes an "essential" communication between itself and the real google services to allow you to use google services despite having all their bloatware.
to round this up, you have fakestore which spoofs existence of Google Play Store for those apps and games, which specifically check for GPS's existence (Phonesky app).
i think this should quite generally point out, what microg is for (an api which connects you to google, whilst only handing out information, which is crucial to keep a specific connection alive)
you can then use i.e. Aurora Store to download and update your preferred playstore apps. i tell you this specifically, as i hope that, using it right, microg might be able to give you a "fully stocked" phone experience, whilst keeping most of your data secure and your phone unbloated by google's app-hoard.
if you follow the instructions in the OP on how to fully enable microG, this might be a very handy solution for you, too, so maybe, you want to give it a chance.
to point out my issues with twrp (as far as i can tell using my little experience): twrp is device specific. which means, you need a vendor tree and you need to include it whilst building, so twrp can compile against it. now, treble is a way of excluding your device specific vendor tree from the build altogether (your system image basically doesnt contain the vendor files in a "folder" (/vendor), but in a seperate partition. this partition is "simply" beeing symlinked to from your system partition. this way you will never need to build vendor-specific sources but android builds against standardised "api's" which are being "serviced" by treble-enabled phone's vendor-files (lying at the vendor-partition). this makes building aosp and/or lineage, etc. easier as you can build one variant per architecture, which fits all treble enabled phones of that architecture (arm/64/binder32/64,a/ab,...). this is, very basically said, what is called a HAL (hardware abstraction layer) on a desktop computer.
but at the same time it's much more difficult to find vendor sources for those phones, as there is no more need at all for manufacturers to make these sources publich (as far as i understand it). as a matter of fact, you may not need these vendor sources for modern aosp (8.1+), which really is a grace!! but twrp doesn't seem to work when compiled against treble trees.
i even managed to compile a kernel which is mentioned at the wikogeek site for the lenny 5. i tried to include that kernel when compiling the recovery image but even that did not work out. as i am no experienced programmer (especially not in the high languages), i will not be the person to ask when it comes to finding out what bugs and how to circumvent it.
there is a little light at the end of the tunnel, though. as far as i understand it, treble-phones come with mostly generic kernels, which *could* make it easier to find a way to build a kernel/boot/recovery image in a similar fashion we build the gsi (generic system image) with. additionally, if there is some effort on it, i imagine, that it would be possible to generally modify twrp in a way so it's able to build against treble source trees with missing vendor source. this would enable twrp to run on virtually any phone which is treble enabled and there would be few to no need to port it for each device, specifically. maybe there would then be versions as in the treble gsi's (arm/64,a/b,...) as well as build variants for alternative display sizes etc.
but i wouldn't even know where to start...
i hope i was able to answer your questions. if you decide to stick with the variant in the OP, you should consider downloading and installing the most recent updated build.
best regards
Problems I found in the rom and if there is a way to solve them
Yo,
I wanted to point out the problems I found in the rom and if there is a way to solve
These are the problems I encountered:
1: *THE MOST IMPORTANT*
I can't pass the safetynet test, I researched a lot and I still couldn't solve
When I try to pass the safetynet test on magisk it gives "safetynet API Error"
When I try to do the test with the "SafetyNet Helper Sample" app it gives "SafetyNet request: success
Response validation: fail
Error Msg:
ApException [17]: API: SafetyNet .API is not
available on this device. Connection failed with:
ConnectionResult {statusCode = SERVICE_INVALID,
resolution = null, message = null}
And the "SafetyNet Test" app gives me "fail (Google Play services not available)"
I am aware of the new problem with the safetynet:
(sometimes people are still able to pass the test probably because it is still in maintenance or something)
https :// www . androidpolice . com /2020/03/11/safetynet-improvements-kill-magisk-hide
https :// twitter . com /topjohnwu/status/1237656703929180160
https :// twitter . com /topjohnwu/status/1238514375150850048
https :// twitter . com /topjohnwu/status/1237830555523149824
But even so I should be able to run the test even if it give both negative should run instead of showing those errors
2: The contacts I had on the SIM card and Google account do not appear in the contacts.
So I went on WhatsApp to save the ones I wanted to save, but after a few days and a few restarts the contacts are still saved, but on WhatsApp it shows that they are not saved even appearing in the contacts, to appear again saved on WhatsApp, I have to save them all again
3: Cant login in Clash Royale with google play games account, can i flash the rom and gapps to work or the microg and google play services will create some conflict, is there a way to unninstall microg completly and reflash the rom without microg and flash gapps?
4: Error when login in pokemon go: unable to authenticate, I researched it and it seems to be because the safetynet is negative but I can't even run the test (only after I became aware of the new safetynet problem) even with this new problem I would like to try to run the test to see if it passed since some people still are successfully passing the test
5: in the microg settings in self-check an option is not checked in the box "UnifiedNlp do not have location to test geocoder" I already researched to see if it solved something but I couldn't
edit: I solved it using the "Apple WI-FI" backend instead of the "Déjà Vu Location Service"
BUT NOW ITS GIVE ME AN UNCHECKED BOX
"Network-based location enabled:
you either disabled network-based location
(in system settings) or the system is not
supported"
6: some times in the time widget just appear "loading widget..."
and these are all the problems that I encountered, pls help me
solving these problems, thx!:good:
sorry for some mistakes i translated from portuguese to english with google translator and my knowledge of english
CooperTUGA, thanks for writing. And I want to apologize for letting you wait for so long. In fact, at the moment i do not actively develop this ROM (due to data loss on my virtual machine).
Anyways, i will try to address your issues as good as i can, though i must admit, none of these issues happened on my device.
ad 1: The only thing that comes to my mind is, that something went wrong when registering your device with the Android-ID. (see OP activation instructions). The SafetyNet-API itself should be working, atleast I had no similar issues (after Registering the device it takes some time - around 5 minutes - for Android to reflect the registered state).
But if someone happened to have this issue and knows another solution, you are welcome to tell!
ad 2: Does it help when you try to import the Files from the SIM card? As for Google contacts, it is - from my POV - stringent, that, if the SafetyNet API doesn't work properly, you will be unable to access Google Services (as Google Contacts) which would explain the missing Google Contacts.
ad 3: GApps and microG are two different things. GApps install a version (open-source fork, contains proprietary binaries) of the Official Google Apps, that is, they provide full functionality towards google services, provided you registered your device correctly.
microG is a pure Open Source fork of that, providing but the Framework with which Google Apps can be run. It does not provide Google Apps (like PlayStore etc.) by itself but merely allows them to run, given the configuration is right. This microG-ROM is not built to work with GoogleApps like PlayStore, but instead relies on the microG Services to get Apps, providing same or similar services, running (like Aurora Store etc.). To address your question, it is possible, to change the source code which was used to build this ROM, so it builds with Gapps or completely free of any such services, in fact it would mean to exclude certain patches, but such projects (Treble-enabled) are covered by others and because of above stated reasons i will not be able to provide such in near future.
Short but clear: No, there is no way to "uninstall" microG as it is built together with the ROM and the source used was especially prepared to use microG. But if configured right, you should be able to use your Google-Account in combination with Google-Services-Apps or Games despite using microG.
ad 4: See above. If everything's configured right, you should be able to play Pokemon GO, although i don't use any of these Apps (Clash Royale, Pokemon GO, WhatsApp). I never encountered any Problems along using Google Apps with this ROM.
ad 5: Well, the error says it all. I have Mozilla Location Service installed, which works like a charm. Maybe try this one? You can get it from FDroid, search for "MozillaNlpBackend" and see if it helps to sort this out? This works for me, after all.
ad6: as this is very unspecific, i cannot really tell what's the problem, but i would guess it has to do with the SafetyNet API not doing what it should or even the Location Backend not reporting position in time...
Did you clean your cache and data partitions while installing this ROM? I really am not sure what could create the behaviour you describe. Maybe there was a change in the SafetyNet/Device Certification process since this ROM-Build, maybe theres someone in those boards who could answer this, but i unfortunately can't...
I'm sorry that i cant give you more positive news, but hopefully it helps you in orienting what some common problems could be caused by.
Let me know about your success in trying to get the ROM working.
Best regards and greetings to portugal!
ivelischt
additionally: if you are interested in porting the Lineage Source for GSI/Lenny 5, you might be interested in this Thread: https://forum.xda-developers.com/android/help/how-to-root-wiko-lenny-5-t3819469
specifically, i wrote a guide there on how to build Android/Lineage Source for Treble devices. Maybe this helps you in getting your own build environment, enabling you to build to your disguise.
Images are not available anymore. Anyone here?
Ok, I am now desperate. I've tried everything I could find and nothing worked. I have posted in several threads, pmed a bunch of people, got some answers and help, but my problem continues.
I have a Samsung S21+ (Exynos) running Android 12 and Viper4Android works great. My Samsung S22 Ultra, rooted SnapDragon running Android 12 with Dr. Ketan ROM keeps asking for drivers everytime I open V4A (driver installation loop).
I have tried everything I could find in XDA, including:
- Several modules like: AML, Audio Compatibility Patch, Dolby, JamesDSP, V4A Repacked, Shadow fix and several other modules fixes. All of those in different orders of installation according to the thread they were described. Didn't work.
- Changing post-fs-data.sh. At this time, I noticed that my device only has audio_effects.xml in two paths: vendor/etc and vendor/etc/audio/sku_taro (system/vendor is the same as vendor/). So, I changed the "mount" path inside post-fs-data.sh to those two path and pasted it again inside data/adb/modules/Viper4AndroidFX/. Didn't work.
- As nothing worked, I began to try to understand what the hell V4A needs to work. I noticed that my device have several audio_effects xml that have code lines with "V4A" inside vendor/etc. Those are:
audio_effects_haptic.xml
audio_effects_sec.xml
audio_effects_vr360.xml
audio_effects.xml
There are other audio xml, but they doesn't seem to have V4A lines. Those files, however were not present in sku_taro folder. And I'm not sure if they should. Sku_taro folder files cannot be renamed/edited, so I had to create a magisk module for that.
I added all those 4 modified files (copied from vendor/etc) to sku_taro. Also, sku_taro have audio_effects.conf, while vendor/etc doesn't. However V4A ins't able to modify any file insisde sku_taro, so I don't have a modified version of audio_effects.conf.I tried pasting audio_effects_common.conf from my S21+ (Exynos) but didn't work.
So, what I need is help from someone who knows about Samsung devices or has a Samsung Snapdragon running Android 12 and V4A. If someone has aphone from S21 line SnapDragon running A12 and V4A, please help me!
What I need to know is:
1- What V4A modified files should be in each of the vendor folders?
2- What should be added in audio_effects.conf?
3- Should I use post-fs-data.sh?
I really, really hope we can fix that. I'm sure there will be a LOT of Samsung users that will be very happy if we do.
PS: Some info
Phone: Samsung Galaxy S22 Ultra (S908E) SnapDragon Android 12
Root: Magisk 24.3 (Dr. Ketan ROM).
SELinux: "Permissive" when command getenforce on Termux
If any more information, like prints or file code lines are needed I can provide them!
Also fellow S22U Snapdragon owner here (S908N). I've been seeing you around the threads as I am also trying to get Viper working on this thing. Hope you find a way to get it working, I hope you'll share the steps if you can make it work. Best of luck.
If you want an accelerated progress you might have to put a bounty on this.
ffp. said:
Ok, I am now desperate. I've tried everything I could find and nothing worked. I have posted in several threads, pmed a bunch of people, got some answers and help, but my problem continues.
I have a Samsung S21+ (Exynos) running Android 12 and Viper4Android works great. My Samsung S22 Ultra, rooted SnapDragon running Android 12 with Dr. Ketan ROM keeps asking for drivers everytime I open V4A (driver installation loop).
I have tried everything I could find in XDA, including:
- Several modules like: AML, Audio Compatibility Patch, Dolby, JamesDSP, V4A Repacked, Shadow fix and several other modules fixes. All of those in different orders of installation according to the thread they were described. Didn't work.
- Changing post-fs-data.sh. At this time, I noticed that my device only has audio_effects.xml in two paths: vendor/etc and vendor/etc/audio/sku_taro (system/vendor is the same as vendor/). So, I changed the "mount" path inside post-fs-data.sh to those two path and pasted it again inside data/adb/modules/Viper4AndroidFX/. Didn't work.
- As nothing worked, I began to try to understand what the hell V4A needs to work. I noticed that my device have several audio_effects xml that have code lines with "V4A" inside vendor/etc. Those are:
audio_effects_haptic.xml
audio_effects_sec.xml
audio_effects_vr360.xml
audio_effects.xml
There are other audio xml, but they doesn't seem to have V4A lines. Those files, however were not present in sku_taro folder. And I'm not sure if they should. Sku_taro folder files cannot be renamed/edited, so I had to create a magisk module for that.
I added all those 4 modified files (copied from vendor/etc) to sku_taro. Also, sku_taro have audio_effects.conf, while vendor/etc doesn't. However V4A ins't able to modify any file insisde sku_taro, so I don't have a modified version of audio_effects.conf.I tried pasting audio_effects_common.conf from my S21+ (Exynos) but didn't work.
So, what I need is help from someone who knows about Samsung devices or has a Samsung Snapdragon running Android 12 and V4A. If someone has aphone from S21 line SnapDragon running A12 and V4A, please help me!
What I need to know is:
1- What V4A modified files should be in each of the vendor folders?
2- What should be added in audio_effects.conf?
3- Should I use post-fs-data.sh?
I really, really hope we can fix that. I'm sure there will be a LOT of Samsung users that will be very happy if we do.
PS: Some info
Phone: Samsung Galaxy S22 Ultra (S908E) SnapDragon Android 12
Root: Magisk 24.3 (Dr. Ketan ROM).
SELinux: "Permissive" when command getenforce on Termux
If any more information, like prints or file code lines are needed I can provide them!
Click to expand...
Click to collapse
Okay, I got JamesDSP working now. Had to install AML, and then install JameDSP with the Huawei installation method. I'm gonna try to flash Viper on see if that does anything.
Fireburito said:
Okay, I got JamesDSP working now. Had to install AML, and then install JameDSP with the Huawei installation method. I'm gonna try to flash Viper on see if that does anything.
Click to expand...
Click to collapse
I tried that too. I can get Jamesdsp to work, but it is way inferior to V4A. At least I couldn't get a good bass from it.
I know several other users that want that too. It would be nice to have someone who knows the working of V4A to help or at least a S21 SD owner to share his files and codes, maybe we can copy them.
What you mean by bounty? I ambwilling to try anything for this to work and I will not stop until we make it. The main reason I rooted this damn thing was to get V4A.
ffp. said:
I tried that too. I can get Jamesdsp to work, but it is way inferior to V4A. At least I couldn't get a good bass from it.
I know several other users that want that too. It would be nice to have someone who knows the working of V4A to help or at least a S21 SD owner to share his files and codes, maybe we can copy them.
What you mean by bounty? I ambwilling to try anything for this to work and I will not stop until we make it. The main reason I rooted this damn thing was to get V4A.
Click to expand...
Click to collapse
Yeah, before I couldn't even get JamesDSP to work, so just having it now as some form sound mod is semi-okay. I'm trying to use that to piggyback off to install Viper, but to no avail.
I think it's something with the Huawei install method that got it working ? As installing with the normal method before just made the app crash. The module files in JamesDSP correctly targeted the sku-taro folders too, unlike Viper.
A bounty is basically you post a reward amount to any dev that can get Viper working on our SD S22U, it will at least get some experienced and knowledgeable people onboard trying to figure it out instead of us grasping at straws.
Fireburito said:
Yeah, before I couldn't even get JamesDSP to work, so just having it now as some form sound mod is semi-okay. I'm trying to use that to piggyback off to install Viper, but to no avail.
I think it's something with the Huawei install method that got it working ? As installing with the normal method before just made the app crash. The module files in JamesDSP correctly targeted the sku-taro folders too, unlike Viper.
A bounty is basically you post a reward amount to any dev that can get Viper working on our SD S22U, it will at least get some experienced and knowledgeable people onboard trying to figure it out instead of us grasping at straws.
Click to expand...
Click to collapse
I understand. That's a good idea. And I am willing to help the devs anyway i can.
How do I start the bounty? Where should I post and how I get people to participate?
I know there are a bunch of people who wants that.
Also, it would be very good to know if v4a works in S21 SD, since that can either lead to a hint on how to make it work or at least get more people into the matter, since the systems probably are very similar.
ffp. said:
I understand. That's a good idea. And I am willing to help the devs anyway i can.
How do I start the bounty? Where should I post and how I get people to participate?
I know there are a bunch of people who wants that.
Also, it would be very good to know if v4a works in S21 SD, since that can either lead to a hint on how to make it work or at least get more people into the matter, since the systems probably are very similar.
Click to expand...
Click to collapse
No idea tbh, I saw one guy post a bounty to get viper working on snapdragon s21 ultra, and it was claimed, but that was mostly it. I don't participate in these forums much so don't know about the specifics.
I have seen a few posts about snapdragon S21U with viper on one ui 4, but whatever methods they were using didn't work on s22u iirc, probably because those phones started with android 10, 11, whilst S22U is android 12 out of the box.
ffp. said:
Ok, I am now desperate. I've tried everything I could find and nothing worked. I have posted in several threads, pmed a bunch of people, got some answers and help, but my problem continues.
I have a Samsung S21+ (Exynos) running Android 12 and Viper4Android works great. My Samsung S22 Ultra, rooted SnapDragon running Android 12 with Dr. Ketan ROM keeps asking for drivers everytime I open V4A (driver installation loop).
I have tried everything I could find in XDA, including:
- Several modules like: AML, Audio Compatibility Patch, Dolby, JamesDSP, V4A Repacked, Shadow fix and several other modules fixes. All of those in different orders of installation according to the thread they were described. Didn't work.
- Changing post-fs-data.sh. At this time, I noticed that my device only has audio_effects.xml in two paths: vendor/etc and vendor/etc/audio/sku_taro (system/vendor is the same as vendor/). So, I changed the "mount" path inside post-fs-data.sh to those two path and pasted it again inside data/adb/modules/Viper4AndroidFX/. Didn't work.
- As nothing worked, I began to try to understand what the hell V4A needs to work. I noticed that my device have several audio_effects xml that have code lines with "V4A" inside vendor/etc. Those are:
audio_effects_haptic.xml
audio_effects_sec.xml
audio_effects_vr360.xml
audio_effects.xml
There are other audio xml, but they doesn't seem to have V4A lines. Those files, however were not present in sku_taro folder. And I'm not sure if they should. Sku_taro folder files cannot be renamed/edited, so I had to create a magisk module for that.
I added all those 4 modified files (copied from vendor/etc) to sku_taro. Also, sku_taro have audio_effects.conf, while vendor/etc doesn't. However V4A ins't able to modify any file insisde sku_taro, so I don't have a modified version of audio_effects.conf.I tried pasting audio_effects_common.conf from my S21+ (Exynos) but didn't work.
So, what I need is help from someone who knows about Samsung devices or has a Samsung Snapdragon running Android 12 and V4A. If someone has aphone from S21 line SnapDragon running A12 and V4A, please help me!
What I need to know is:
1- What V4A modified files should be in each of the vendor folders?
2- What should be added in audio_effects.conf?
3- Should I use post-fs-data.sh?
I really, really hope we can fix that. I'm sure there will be a LOT of Samsung users that will be very happy if we do.
PS: Some info
Phone: Samsung Galaxy S22 Ultra (S908E) SnapDragon Android 12
Root: Magisk 24.3 (Dr. Ketan ROM).
SELinux: "Permissive" when command getenforce on Termux
If any more information, like prints or file code lines are needed I can provide them!
Click to expand...
Click to collapse
Well did you figure it out?
ffp. said:
Ok, I am now desperate. I've tried everything I could find and nothing worked. I have posted in several threads, pmed a bunch of people, got some answers and help, but my problem continues.
I have a Samsung S21+ (Exynos) running Android 12 and Viper4Android works great. My Samsung S22 Ultra, rooted SnapDragon running Android 12 with Dr. Ketan ROM keeps asking for drivers everytime I open V4A (driver installation loop).
I have tried everything I could find in XDA, including:
- Several modules like: AML, Audio Compatibility Patch, Dolby, JamesDSP, V4A Repacked, Shadow fix and several other modules fixes. All of those in different orders of installation according to the thread they were described. Didn't work.
- Changing post-fs-data.sh. At this time, I noticed that my device only has audio_effects.xml in two paths: vendor/etc and vendor/etc/audio/sku_taro (system/vendor is the same as vendor/). So, I changed the "mount" path inside post-fs-data.sh to those two path and pasted it again inside data/adb/modules/Viper4AndroidFX/. Didn't work.
- As nothing worked, I began to try to understand what the hell V4A needs to work. I noticed that my device have several audio_effects xml that have code lines with "V4A" inside vendor/etc. Those are:
audio_effects_haptic.xml
audio_effects_sec.xml
audio_effects_vr360.xml
audio_effects.xml
There are other audio xml, but they doesn't seem to have V4A lines. Those files, however were not present in sku_taro folder. And I'm not sure if they should. Sku_taro folder files cannot be renamed/edited, so I had to create a magisk module for that.
I added all those 4 modified files (copied from vendor/etc) to sku_taro. Also, sku_taro have audio_effects.conf, while vendor/etc doesn't. However V4A ins't able to modify any file insisde sku_taro, so I don't have a modified version of audio_effects.conf.I tried pasting audio_effects_common.conf from my S21+ (Exynos) but didn't work.
So, what I need is help from someone who knows about Samsung devices or has a Samsung Snapdragon running Android 12 and V4A. If someone has aphone from S21 line SnapDragon running A12 and V4A, please help me!
What I need to know is:
1- What V4A modified files should be in each of the vendor folders?
2- What should be added in audio_effects.conf?
3- Should I use post-fs-data.sh?
I really, really hope we can fix that. I'm sure there will be a LOT of Samsung users that will be very happy if we do.
PS: Some info
Phone: Samsung Galaxy S22 Ultra (S908E) SnapDragon Android 12
Root: Magisk 24.3 (Dr. Ketan ROM).
SELinux: "Permissive" when command getenforce on Termux
If any more information, like prints or file code lines are needed I can provide them!
Click to expand...
Click to collapse
All that you should need is root, your device set to permissive mode, install V4A and let it install the drivers when it prompts you the first time you open V4A(grant V4A superuser/root permissions).
Can you confirm that you are properly rooted with correct permissions and r/w properly set?
Can you confirm your device is actually in permissive mode?
I will add that you could also use Wavelet
Wavelet: headphone specific EQ - Apps on Google Play
Headphone specific equalization with lots of customizability
play.google.com
Made by the same developer whom made Viper4Android. There are reports saying It provides the same level of quality.
Droidriven said:
All that you should need is root, your device set to permissive mode, install V4A and let it install the drivers when it prompts you the first time you open V4A(grant V4A superuser/root permissions).
Can you confirm that you are properly rooted with correct permissions and r/w properly set?
Can you confirm your device is actually in permissive mode?
Click to expand...
Click to collapse
Yes, i have root, however S22U do not havr system rw. I can change things via magisk, though.
No, i didn't manage to get it to work. I'm using james dsp, which is pretty good if correctly set.
I had custom kernel (obligated, to have unofficial TWRP installed) with SElinux permissive mode permanently - V4A still did not work on my s22u model S908E (snapdragon; stock A12) - Kept getting driver install loop everytime I opened V4A app.
According to Dr. Ketan (see link message), V4A will not work on s22u Snapdragon models regardless of SElinux being permissive or enforcing.
Awaiting new development/ resurrection of this beloved sound Mod (s22u speakers suck, coming from a buttery smooth ROG-3).
GitHub - AndroidAudioMods/ViPERFX_RE: Reverse Engineering of ViPER4Android FX
Reverse Engineering of ViPER4Android FX. Contribute to AndroidAudioMods/ViPERFX_RE development by creating an account on GitHub.
github.com
Fytdyh said:
I will add that you could also use Wavelet
Wavelet: headphone specific EQ - Apps on Google Play
Headphone specific equalization with lots of customizability
play.google.com
Made by the same developer whom made Viper4Android. There are reports saying It provides the same level of quality.
Click to expand...
Click to collapse
they didnt make viper for Android. He had no part in the development of the so driver that makes the sound change. Viper520 did and I still dont understand why he walked away and has never came back. Dewitt just made some changes to the apk file. I can assure you he hasnt got a clue on how to make a sound driver. Technically james dsp is a so file sound driver that he did make.
I have a new tab s8 plus on one ui 4.1.1 right now and I can't believe viper wont work with a permissive kernel even. I like you guys got jamesdsp to work by installing as Huawei device and thought maybe that would correct the problem with viper and it didnt.
I do believe system RW would make the difference and I know the developer for the S8 tablet is working on making a twrp and a rw file that will work on that. I thought the s22 ultra was able to make RW now with the RW file. You would have to find the twrp tab s8, s8+, s8 ultra thread and go onto their telegram where DR. Keaton also hangs out and see if it works on the s22 ultra because its working on some devices. I was thinking s22 ultra and fold 4. I don't know how long until the tab s8 will have it and I hope you guys read this look into and try it and get viper4android working. So god speed
James dsp installs a lib64 driver into the system when you use Huawei setting. Normally the sound driver installs in the lib folder instead. I dont think its possible with viper
Huawei install
/data/adb/modules/ainur_jamesdsp/system/vendor/lib64/soundfx/libjamesdsp.so
Normal install
/data/adb/modules/ainur_jamesdsp/system/vendor/lib/soundfx/libjamesdsp.so
I do believe system RW will allow viper to work
Im almost 95 percent sure s
ffp. said:
I understand. That's a good idea. And I am willing to help the devs anyway i can.
How do I start the bounty? Where should I post and how I get people to participate?
I know there are a bunch of people who wants that.
Also, it would be very good to know if v4a works in S21 SD, since that can either lead to a hint on how to make it work or at least get more people into the matter, since the systems probably are very similar.
Click to expand...
Click to collapse
Have you made your system read/write yet? Im 95 percent certain that the problem. Im on android 13 on my poco f3 and now viper wont install and it says Error Could not mount system read write s22 ultra is able to be rw with Dr. Keaton's stuf I believe
It worked?
amar100 said:
It worked?
Click to expand...
Click to collapse
I couldn't figure it out you want to try mine?
amar100 said:
It worked?
Click to expand...
Click to collapse
What device do you have any details please
ScarletWizard said:
The 64 bit version of viper has been released. If you're on Android 13 on a 74 bit soc. You gonna need the new v4a 64
Click to expand...
Click to collapse
What are you talking about? Where's the 64bit version
Yes
Techguy777 said:
I couldn't figure it out you want to try mine?
Click to expand...
Click to collapse
Yes Pls