LineageOS 14.1 Port ROM
Lenovo Tab 3 8"/TB3-850F
•WARNING:
You are installing this custom Android ROM at your own discretion and risk. If you are unclear on anything, please stop and do some research before proceeding further. This is not a Q & A thread, so please post comments on topic with subject matter relating directly to this ROM. I will not be held responsible for devices which become bricked or damaged as a result of installing this ROM. You are encouraged to read and re-read the OP prior to installing this ROM on your device. Please visit this thread for now to make general inquiries about this ROM or about any other questions or issues you may have regarding the 850F. Either myself or XDA Senior Member @pndwal, who is very knowledgeable about this device and Android in general, will try to address your questions. https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786 User input and feedback are essential in making improvements, fixing bugs, and in helping development for this device to continue to evolve.
Any skilled devs interested in contributing in any way to development for the 860F, please use the above thread to contact @pndwal and coordinate with him in that area.
I am not a developer, nor did I contribute to the porting of this LineageOS 14.1 custom ROM for the TB3-850F. I merely packaged up the files, added GApps Pico, made a few minor tweaks, and created a TWRP flashable zip installer for this ROM. Please do not request updates or make ETA type inquiries on this thread. Whether or not this ROM will be maintained is still up in the air. Please give any and all credit to the individuals I have listed below under Mentions & Credits.
LineageOS 14.1 is a free, aftermarket distribution of Android 7.1.2 Nougat, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many individuals within the Android community. Although this particular LineageOS build does have GApps Pico preinstalled, it can be used without any need to have any Google application installed. LineageOS does still include various hardware specific code, which is nonetheless slowly being open-sourced anyway.
SOURCES:
LineageOS Source Code: https://github.com/LineageOS
Kernel Source Code: https://support.lenovo.com/us/en/downloads/ds112711
LineageOS Gerrit Code Review: https://review.lineageos.org/q/status:open
FEATURES & SPECS:
•LineageOS Version: 14.1
•Android Base Version: 7.1.2_r8 Nougat
•Build ID: N2G470
•SDK Version: 25
•Build Date: May 15, 2017
•Security Patch Level: May 5, 2017
•Kernel Version: 3.18.19 (mods by @wezroot2k)
•LineageOS API Level: Guava (7)
•GApps Pico Pre-installed
•Insecure Boot Image Support
•Force Encryption Disabled (Opt-Encrypt)
•AVB/dm-verity Disabled
•Fully Deodexed
•Fully Zip-aligned
•User Opt Root or Non-Root
•Status: Unofficial/Stable
WORKING:
•Booting
•WiFi
•Bluetooth
•Graphics/Video Playback
•Audio
•GPS/Location Services
•GApps
•Magisk Universal Systemless Interface
BUGS:
I am presently working on Settings UI to omit the mobile networks/telephony entries. These are present because this ROM was originally a smartphone port. Otherwise, please feel free to submit a proper bug report or, at a minimum, a clear description of the bug or instability, including screenshots if possible.
A bug has been reported for apps that require superuser permissions (Greenify, root file managers, etc), and I have determined that installing the latest Magisk systemless root will alleviate that bug.
Upon initial boot, during setup, you may experience an issue with Setup Wizard force closing. I have posted a quick workaround for this below under the Installation Instructions heading.
REQUIREMENTS:
You need an unlocked bootloader and TWRP custom recovery installed. If you need help with either of these topics, please visit this thread for guidance: https://forum.xda-developers.com/android/general/guide-lenovo-tab3-8-tb3-850f-t3559786
INSTALLATION INSTRUCTIONS:
1. Download the ROM zip from the below download link and save it to your device storage...
2. Boot your device into TWRP recovery mode...
3. Wipe Data, Cache & Dalvik/ART (my installer automatically formats the /system partition)...
4. Select Install, navigate to saved location of the ROM zip, select it and swipe the action bar to begin installation...
5. Reboot system (installation will take around three minutes).
*Because this ROM is fully deodexed, first boot can take several minutes to complete while the Dalvik/ART directories are being written for the first time. The second and subsequent boot times will be much faster. Also, on first boot, select your language then choose SKIP on the Insert SIM Card screen. You will then be prompted to set up your device as new or copy data from another device as part of setup. At this stage, if the Setup Wizard force closes, swipe down from the top of the screen to access Quick Settings and go ahead and connect to a WLAN/WiFi network. Now, go back to the previous screen and Setup Wizard should function normally and allow you to proceed with setup of your device. I am presently working on removing SIM/Mobile Network settings on this device, so hopefully this will be fixed soon, and a true WiFi-only tablet port will be yielded.
**As mentioned supra, this ROM is packaged with GApps Pico, which provides the bare bones minimum for Google Play functionality. If you want a GApps package other than the one preinstalled, visit https://opengapps.org/, choose ARM64, Android 7.1, and select your preferred package. Simply install the GApps package after Step 4 above. If you want root, visit the official Magisk release & announcement thread here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445, and download the latest Magisk Manager apk. Install the apk, go to Developer Options and enable Apps & ADB in the root options menu. Open Magisk Manager, select Install, pick the direct install option, and systemless root will be installed via patched boot image. Reboot and systemless root should be properly installed & stable. Be sure and hit the Thanks button on @topjohnwu's thread if you use Magisk.
MENTIONS & CREDITS:
This port was made possible by a number of individuals both here at XDA and abroad:
- Credit goes to 4PDA (Russian Development site) member chipa76 for the original TB3-850M port, and to 4PDA member al_rus for his contributions to, and for posting that port.
- Credit and thanks for the breakthrough moment for TB3-850F users must go to XDA member @wezroot2k who, after others tried for many months, was finally able to stabilise this ROM for our device by recompiling the ported boot image with TB3-850F stock kernel. Also, he has worked on tweaks to streamline the ROM for TB3-850F.
- TWRP flashable ROM package as well as some tweaks to streamline the ROM for TB3-850F have been made by the OP, @AeonFlux1603, who will continue to work on a few further improvements, insomuch as spare time will allow
- Thanks to XDA Senior Member @pndwal for his dedication to this device and for passing on suggestions from the 4PDA Devs regarding the adopted method of stabilising ROM for TB3-850F.
- Last but not least, thanks and credit goes to the entire LineageOS Dev Team for making this custom aftermarket distribution of Android possible for low-grade, mid-grade & flagship devices alike.
DOWNLOAD LINK:
LineageOS 14.1 for TB3-850F: https://drive.google.com/file/d/1bbpwyvP_S4k1PJaLa6RN3dFDF8UYEcNj/view
@wezroot2k, I just wrote up a full thread for the ROM and hit the post button. It posted the first paragraph and that's it. Two hours of work and my XDA Labs app deleted everything.
AeonFlux1603 said:
•WARNING:
You are installing this custom Android ROM at your own discretion and risk. If you are unclear on anything, please stop and do some research before proceeding further. This is not a Q & A thread, so please post comments on topic with subject matter relating directly to this ROM. I will not be held responsible for devices which become bricked or damaged as a result of installing this ROM. You are encouraged to read and re-read the OP prior to installing this ROM on your device.
•LineageOS
Click to expand...
Click to collapse
I wonder why that is?
I think you should talk to PW
---------- Post added at 08:49 AM ---------- Previous post was at 08:46 AM ----------
AeonFlux1603 said:
@wezroot2k, I just wrote up a full thread for the ROM and hit the post button. It posted the first paragraph and that's it. Two hours of work and my XDA Labs app deleted everything.
Click to expand...
Click to collapse
Y would the app do that?
Maybe you would have to create the thread from a PC.
wezroot2k said:
I wonder why that is?
I think you should talk to PW
Click to expand...
Click to collapse
Oh. Did I do something wrong?
wezroot2k said:
I wonder why that is?
I think you should talk to PW
---------- Post added at 08:49 AM ---------- Previous post was at 08:46 AM ----------
Y would the app do that?
Maybe you would have to create the thread from a PC.
Click to expand...
Click to collapse
I'll redo the work in the morning. That's got me as aggravated as you can get. I posted full sources, credits, instructions, specs, etc. All got erased.
AeonFlux1603 said:
Oh. Did I do something wrong?
Click to expand...
Click to collapse
No man,just saying PW might know why the app would just post part of the thread and not the full thing.
---------- Post added at 09:08 AM ---------- Previous post was at 09:07 AM ----------
AeonFlux1603 said:
I'll redo the work in the morning. That's got me as aggravated as you can get. I posted full sources, credits, instructions, specs, etc. All got erased.
Click to expand...
Click to collapse
Sorry to hear about that man.
App could've timed out. Similar to chrome. I copy/select all before confirming just incase (with pretty much every hefty message I write)
Hemphiz said:
App could've timed out. Similar to chrome. I copy/select all before confirming just incase (with pretty much every hefty message I write)
Click to expand...
Click to collapse
Oh ok. Between that, copy/pasting and backspacing a lot, that's likely what happened. Working on reworking the thread now. Thanks for the insight. I'm editing in a little at a time to play it safe.
AeonFlux1603 said:
Oh ok. Between that, copy/pasting and backspacing a lot, that's likely what happened. Working on reworking the thread now. Thanks for the insight. I'm editing in a little at a time to play it safe.
Click to expand...
Click to collapse
Just read this new thread! Well done n many thanks.
As I explained in other thread (not sure if you understood properly - please read it carefully again to avoid heartache), XDA Labs does have a serious fault. Simply put, posts are shortened to a point where '*' symbol occurs, and because copying and pasting often swaps spaces (between words) for this symbol, the post gets truncated and your efforts are lost!
I said:
Frustrating to lose all that typing . Sorry to hear that.
Beware of accidently hitting 'backspace' after highlighting text!
***Also, please be aware (if you use it,) that XDA Labs app is flawed, and will often unexpectedly truncate your post when sending. This usually happens when you've copied and pasted info - you'll find '*' substituted for spaces in places, and the first one will be near the point the post is truncated. I always highlight and copy complete post before sending, and if I lose text I repost it from browser, which doesn't have these issues.
Click to expand...
Click to collapse
Sounds like @Hemphiz and others have all learned the hard way as I did, and take the same precautions.
Hope it helps in future, and bravo for your efforts and hard work for us! Regards, PW
:highfive: Hey AF just read the thread and I love and thanks for the kudos and well done.
I have installed your LOS 14.1 packages and must say it is stable very smooth and love your installer :highfive: I am using it right now and loving it
Also I did notice I minor thing and this for all user of this rom ,this is maybe not the ROM port fault but maybe the specific app bug or compatibility issue. I notice that the Greenify app does not do well with the default SU add-on of this ROM Greenify just does not load. Keeps crashing at getting su root access screen, but it does work with other root method so maybe something to look into.
Also I think you should edit the build.prop values for things like model number should be changed to 850F and not 850m and so fourth.
I have a build.prop file I can send you to look at.
Otherwise everything else is good
Excellent work AF
pndwal said:
Just read this new thread! Well done n many thanks.
As I explained in other thread (not sure if you understood properly - please read it carefully again to avoid heartache), XDA Labs does have a serious fault. Simply put, posts are shortened to a point where '*' symbol occurs, and because copying and pasting often swaps spaces (between words) for this symbol, the post gets truncated and your efforts are lost!
I said:
Sounds like @Hemphiz and others have all learned the hard way as I did, and take the same precautions.
Hope it helps in future, and bravo for your efforts and hard work for us! Regards, PW
Click to expand...
Click to collapse
Yeah. And I did take your advice, but instead of using my notebook, I used Labs again, except this time I posted every time a section was complete, fully copying all my text before hitting the post button. Thank you for the warnings and info. I will know in the future.
wezroot2k said:
:highfive: Hey AF just read the thread and I love and thanks for the kudos and well done.
I have installed your LOS 14.1 packages and must say it is stable very smooth and love your installer :highfive: I am using it right now and loving it
Also I did notice I minor thing and this for all user of this rom ,this is maybe not the ROM port fault but maybe the specific app bug or compatibility issue. I notice that the Greenify app does not do well with the default SU add-on of this ROM Greenify just does not load. Keeps crashing at getting su root access screen, but it does work with other root method so maybe something to look into.
Also I think you should edit the build.prop values for things like model number should be changed to 850F and not 850m and so fourth.
I have a build.prop file I can send you to look at.
Otherwise everything else is good
Excellent work AF
Click to expand...
Click to collapse
That's good to know on Greenify. Flashing a Magisk v18.1 systemless root installer zip via TWRP would likely fix the issue. I have noticed a similar problem using MiXplorer in root file manager mode. The problem like you said is likely the LOS 14.1 su_addon.
Glad you're loving it my friend. After working so hard to help make it possible, you are deserving indeed.
AeonFlux1603 said:
That's good to know on Greenify. Flashing a Magisk v18.1 systemless root installer zip via TWRP would likely fix the issue. I have noticed a similar problem using MiXplorer in root file manager mode. The problem like you said is likely the LOS 14.1 su_addon.
Glad you're loving it my friend. After working so hard to help make it possible, you are deserving indeed.
Click to expand...
Click to collapse
Not sure if you're using adoptive storage, or where MiXplorer (or Greenify) loads by default, but generally apps requiring root access lose functionality or won't load at all if installed on SD storage.
I use ES File explorer which installs to SD by default, but it must be moved to internal to enable its inbuilt root explorer, otherwise its root test fails and root explorer toggles off.
This just may be your problem too. - Pays to check SuperUser enabled apps in manager, and ensure each of these is on internal storage. PW.
---------- Post added at 09:49 AM ---------- Previous post was at 09:42 AM ----------
wezroot2k said:
Y would the app do that?
Maybe you would have to create the thread from a PC.
Click to expand...
Click to collapse
Yet the Labs app does this often . I've explained in my last post on page 1. PW
---------- Post added at 09:57 AM ---------- Previous post was at 09:49 AM ----------
wezroot2k said:
...I notice that the Greenify app does not do well with the default SU add-on of this ROM Greenify just does not load. Keeps crashing at getting su root access screen
Click to expand...
Click to collapse
My post to AF above re storage may help here, but could be SU used as you say. PW
pndwal said:
Not sure if you're using adoptive storage, or where MiXplorer (or Greenify) loads by default, but generally apps requiring root access lose functionality or won't load at all if installed on SD storage.
I use ES File explorer which installs to SD by default, but it must be moved to internal to enable its inbuilt root explorer, otherwise its root test fails and root explorer toggles off.
This just may be your problem too. - Pays to check SuperUser enabled apps in manager, and ensure each of these is on internal storage. PW.
---------- Post added at 09:49 AM ---------- Previous post was at 09:42 AM ----------
Yet the Labs app does this often . I've explained in my last post on page 1. PW
---------- Post added at 09:57 AM ---------- Previous post was at 09:49 AM ----------
My post to AF above re storage may help here, but could be SU used as you say. PW
Click to expand...
Click to collapse
I'm not running adoptive storage now. I had previously tried it to ensure operability. But, you actually just helped me troubleshoot a problem I was having on my LG G4 with root. It was due to adoptive storage. Haha. Man PW you know your Android for sure. Thanks.
So on our 850F I'm going to try Magisk or phh-superuser systemless root (or maybe SuperSU v2.82-SR5) to see if that fixes root access of the OS.
Also, I'll be posting the stock 6.0 firmware this evening sometime, with fastboot instructions. I was wrong about it being the most current build. It is actually one of the initial builds that shipped with the 850F in mid to late April, 2016. Hard to believe this device is nearly three years old now. So, once installed, the user will be prompted to install a series of OTA updates subsequent to initial boot and setup.
Hemphiz said:
App could've timed out. Similar to chrome. I copy/select all before confirming just incase (with pretty much every hefty message I write)
Click to expand...
Click to collapse
I've found even if it times out, or can't connect when sending, things are generally handled properly by Labs app, a message appears that 'send failed', and text is all still there allowing further attempts.
However, the space-substituted-for-*-symbol problem (when copying and pasting) will truncate the post and successful send in one operation. This means a large portion of text is often lost and irretrievable. (Also, the * symbol still shows as a space while editing, so one doesn't realise that the space has been substituted until its too late.)
Great advice to copy all before sending. PW
---------- Post added at 06:17 AM ---------- Previous post was at 05:22 AM ----------
@wezroot2k, @AeonFlux1603
TB3-850F users are privileged, blessed, ecstatic, proud, happy and very thankful to have two budding (though clearly possessed of valuable experience and practical knowledge) developers on board the Good Ship TB3-850F, and its been a long time coming!
Thank you both especially for Stable and Virtually Bug Free Port to LOS14.1 for TB3-850F, as well as for other valuable resources we are gaining - including this new thread for our brand new Lineage Operating System!
Your sincere expressions of thanks / praise for helpful posts are also much appreciated.
Just a small heads-up (and sorry to spell it out) - Please don't neglect the 'thanks' (thumb up) button when a post is useful, or a sincere attempt to help is made. This is kind of the expected / default expression of thanks around here, and is possibly the most sincere form of flattery as it also elevates a members XDA profile. It's a simple and immediate way to say 'thanks', and often makes further comment unnecessary. (Incidentally, thanked posts are indexed, and are often perused for helpful information.)
Many thanks, and loving your work! PW :good::good::good::good::good:
It looks like I have the Settings UI ironed out, with all mobile networks/SIM options removed in the Settings menu. I'm going to to repackage the Settings apk, implement it back into the /system directory and see if it works. If so I will update the OP with a new build.
Also, Magisk systemless root appears to be a fully stable root protocol on this LOS build. . Oddly, after flashing the Magisk v18.1 systemless root installer zip with TWRP, the Magisk Manager app doesn't appear upon reboot. But, once you manually install Magisk Manager v7.0.0 (185), root shows as properly installed and up to date. Thus far, I have noticed no instabilities or bugs with Magisk.
So, the recommended method of installing Magisk systemless root on this ROM is to first install the latest Magisk Manager v7.0.0 (185) apk, select Install from the app, and choose the direct install option. Reboot and Magisk v18.1 systemless root should be properly installed and stable. Go here to visit the official Magisk release and announcement thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 where you can download the latest Magisk Manager apk and systemless root installer zip. Be sure and thank @topjohnwu if you use Magisk.
Update on Settings UI. After repackaging the Settings apk and framework-res.apk, I am experiencing force closes every time Settings is opened. It is probably something as simple as an encoding issue or an error during repacking but I'll keep progress posted.
Update on the Settings UI. I now realize that my issues were due to my failure to properly encode my edits of the relevant .XML files with UTF-8 encoding prior to repackaging. As I may have mentioned previously, I am interested in bringing this port up to date with the latest upstream sources. So my next build release will hopefully include current LOS sources and have the Settings UI ironed out. While progress is not nearly as quick as I'd like, I am working on it.
I don't know about you guys as far as audio preferences, but I was really partial to the stock Dolby Atmos app that ships preinstalled on this device. I done a little testing to find a comparable audio setup. There is a Magisk Module titled Collective Dolby Atmos (ZTE Axon 7) v1.8 (2.2.1.7_r1), last updated on January 15, 2019, that works great on this ROM, with nearly exactly the same features and UI as the stock Lenovo version of Dolby Atmos. To install it, of course, you can simply download the Module and install it via Magisk Manager or via TWRP. There are several different Dolby ports available. This is the official support and release thread: https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
AeonFlux1603 said:
I don't know about you guys as far as audio preferences, but I was really partial to the stock Dolby Atmos app that ships preinstalled on this device. I done a little testing to find a comparable audio setup. There is a Magisk Module titled Collective Dolby Atmos (ZTE Axon 7) v1.8 (2.2.1.7_r1), last updated on January 15, 2019, that works great on this ROM, with nearly exactly the same features and UI as the stock Lenovo version of Dolby Atmos. To install it, of course, you can simply download the Module and install it via Magisk Manager or via TWRP. There are several different Dolby ports available. This is the official support and release thread: https://forum.xda-developers.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342
Click to expand...
Click to collapse
Quite like ViPER4AndroidFX ( @ahrion, @Zackptg5) Magisk module. I think it auto-installs AML - Audio Modification Library - Magisk module (by @ahrion, @Zackptg5) also. (Used to anyway.)
AML currently supports all these mods too, so its a smörgåsbord:
- AM3D
- AudioWizard
- V4AFX
- V4AXhifi
- Dolby Atmos (ahrion's ports)
- Dolby Atmos Axon 7 Oreo (guitardedhero's port)
-Dolby Digital Plus
-Bang&Olufsen ICEPower (only tested ainur version)
- Arkamys (only tested ainur version)
- Dirac (only tested ainur version)
- Dirac Hexagon (only tested ainur version)
- JamesDSP
- MaxX Audio 3
- Audio Compatibility Patch (formerly universal deep_buffer remover)
- Ainur Sauron
- SquareSound
- DTS Wizard
- Sony Xperia Z2 Sound System
I see Dolby Atmos Axon 7 Oreo in this list too. Haven't tried it, but I know guitardedhero's a bit of a genius with these mods. PW.
Related
Hello, i bring to you the QuickRemote app for your AOSP Marshmallow rom, CM13 or any rom based on CM13 (Resurrection Remix, Bliss, AICP), you may ask, "Why would i want QuickRemote on my AOSP rom if MM has native IR support and Peel or Anymote works without all this mambo jambo?
Well, even though what i just said is true, no remote controller app has the learning method enabled, even on a stock rom, only QuickRemote can enable the IR receiver to learn a controller that does not appear on the device/manufacturers list.
So, that's the reason we want QuickRemote to work on our AOSP rom.
So, before anything, i would like to thank @hikarisei23 because in a comment of his post HERE i found the files for QuickRemote to work on MM wich leads to the second person i want to thank wich is @syndre who on said comment, posted the files that worked on MM, also @KronicSkillz who helped a lot to troubleshoot and also confirmed that the method i'm posting here works.
Well, this is it, after personally testing with: Resurrection Remix, AICP and Bliss, all of them MM amd CM13 based, all of them with the stock kernel and Lambda Kernel i'm confident enough to post it here, days of testing and troubleshooting and 3 different roms later.
So first, the mandatory disclaimer, im not responsible for any problem that may result from using my method and the files i'm providing you, either with your phone or your self-esteem, it's your responsibility to read, re-read and only do what you are comfortable with.
What you will need:
1. - The phone, this only has been tested with Lg G2 and Lg G3, this may or may not work on another LG phone with IR, you can try, but at your own risk.
2. - The Rom, this only have been tested with AOSP roms either CM13 or CM13 based roms, again, you can try in another rom but at your own risk.
3. - Obviously a Custom Recovery (twrp, cwm, philz)
4. - The three zips im leaving at the end of the post, QRemote_AOSP_MM.zip Fix_Part1.zip and Fix_Part2.zip.
5. - Maybe necessary or not, depending on your rom, Universal init.d from Playstore HERE and Selinux Mode Changer from HERE.
6. - Root Access.
Ok, once you checked and have everything needed, we have to make a little prep on your Rom before starting to flash the zips.
Rom Preparation 100% Needed
You need to set Selinux to permissive, here is where you may or may not need Selinux Mode Changer, First go into "About Device" on your phone settings and in the bottom you will find an indicator for Selinux state, if its "Permissive" you are good to go, some Roms and Kernels have this set to Permissive by default, if it's Enforcing, search in your Rom or Kernel settings, some of them have an option to set it to Permissive, if your rom does not have any option to change it, you will need Selinux Mode Changer, you install it and set Selinux to permissive, after reboot you can check in About Device again to see if it succeded, if it does not work, try again and check the original post, most of the answers are there, i cant give support for this app, also, this app needs root rights, and preferably two reboots after setting Selinux to Permissive.
Next you need to have init.d support, again, some roms have it, but at least for the test that me and the other users did, even though you are pretty sure init.d is enabled it's better to just install Universal init.d from the Play Store and enable init.d manually after doing so, reboot the system at least two times and grant Root access.
Installation!
Now we are ready to start flashing, reboot into recovery and RECOMMENDED, do a Nandroid Backup just in case, but at the moment no boot loops or any other problems had raised from flashing this, but again, just in case. After that, flash the first file: QRemote_AOSP_MM.zip, reboot your system and let it settle for a bit, 1 minute at least.
Now is the part where almost everyone has problems, you have to check in your Sdcard root for a log file named Qremote.log, if the file is there, it means init.d is enabled and in the file it will say if Selinux is Ok, if you don't have the file, check back the first two prep steps and try again.
Now if everything is going ok, is time for the second file, Fix_Part1.zip, reboot and let the system settle again, you may have some force close errors from QuickRemote or QuicksetSDK, its ok, you can try and check if QuickRemote is working, in allmost every case it will not work just yet, but you may have some luck.
Now, is the time to flash the third file, Fix_Part2.zip, again, reboot and let the system settle, now, you should have a working QuickRemote app on you AOSP MM Rom.
This are the steps, if you need more information about what all of this is doing and why you need Selinux and init.d, also why you need to flash 3 files, you can read the troubleshooting section where i explain what i understand about it.
TROUBLESHOOTING
Well, if you are here, it means that this didn't work as planned, so lets make this like a FAQ so you just search your problem and get the answer for it.
P.- I can't see QuickRemote on my app drawer. A: be sure that QuickRemote.apk is not showing as "com.lge...." and has the default green Android icon on your app drawer, sometimes and for reasons unknown to me, this happens for the first day or so, it will automatically change to QuickRemote and it will have the correct icon at least 5 hours after you installed it, it can take more time. A2: Maybe the flashing proccess was not successful, re-flash the file, it will automatically delete previously flashed files and install a new copy of them.
P. - I get force close messages for QuickRemote or QuicksetSDK after completing the proccess. A: try to run QuickRemote after the system settled, most of the times is 1 minute, in some roms and for reasons unknown to me, this messages will appear at boot but after the system settled, you will be able to run QuickRemote without any problem.
P. - QuickRemote opens up but no manufacturers are showing and it also gets really slow. A: this problem shows when either QuicksetSDK is not correctly installed or Selinux is not set to permissive, the solution for the first problem is in my 2 part fix, the version of Selinux included in the first zip, works great with MM but for some reason it will not work out of the box, i dont know if it's missing some files but it may or may not even show under system apps list on your settings menu, what my 2 part fix does is that, deletes the version of QuicksetSDK that the first flash installs and installs a temporary copy of QuicksetSDK wich i believe, writes information needed for QuicksetSDK to work properly, but this newer temporary QuicksetSDK apk, will allmost never work on MM, you can try but allmost every time it will not work, it will constantly force close, so the second fix zip, will delete this temporary QuicksetSDK and the folder it creates in your Sdcard root and install the previous version of QuicksetSDK again, and now, if everything went well, it will work as it's supposed to, i really dont know why exactly, but it works.
A2: the first thing you will notice when you switch to MM is that allmost every app will ask for permission to your Sdcard or camera or microphone wich in LP was not doing, since 4.3 Google is taking extra steps to ensure that you and your information are better protected one of this steps is Selinux (Security Enhanced Linux) wich, for putting it in simple terms, is like a sandbox for your system, only some trust-signed apps can get out of that sandbox and copy files etc... Into your system, those not-so privileged apps cant output anything outside the sanbox and thats why you need to disable or "set to permissive" Selinux, so QuicksetSDK can make the changes necessary for QuickRemote to do its work, it's true that now your system is in a degree "more vulnerable" but if you are a user of this forum, the odds to install something that will damage your system or jeopardize your information are minimal, you need to be really silly to fall for those "your system has problems" or "your battery is gonna explode if you don't install this app" ads that appear on your phone on the daily basis, so, dont worry, but at the same time, just be carefull and have some common sense, if there is a way for this to work with Selinux set to Enforcing, i will update it in the same second.
P. - QuickRemote force closes whenever i try to open it. A: this is caused by either a bad zip flash, or problems with Selinux or init.d, follow the previous answer and the first installation steps again.
P. - I can see QuickRemote and QuicksetSDK on my apps list, no force closes but still no manufacturers. A: Be sure init.d is enabled, i had problems with Roms that had "native init.d support" and emulated init.d will not work, the only way i got no problems with this was with Universal init.d, install that even though you are "pretty sure" your rom supports init.d, the 10QuickRemote.sh script on your init.d tries to get your country to see if you will use the app in, either Korean or any other supported language, it will also give some permissions to a file and it will check if Selinux is Permissive and finally, it will log this to a file called Qremote.log on the root of your Sd, if you have problems and you cant see the file, the problem is 99% most of the time, init.d.
P.- I don't want to flash three files, isn't there a simpler way? A: Unfortunately no, at this moment and after A LOT of testing etc... This is the only effective way i found.
P. - I'm afraid to set Selinux to permissive and leave the door open for all kind of bad ju ju and stuff to invade my sacred Android system, what can i do? A: Skip this hole thing, at the moment, the only way to make this work on AOSP MM is by doing the previous, just be careful, get some common sense and everything will be just fine.
Well, thats all i can think of right now, if you have suggestions, problems or a better way to make this work, please tell me in the comments or PM me, i'm glad to help as far as i can, i hope this helps, i leave you with the needed files and proof that it works.
QRemote_AOSP_MM.zip - MEGA - DRIVE
nice you started a new thread!
Ive been messing around with this a lot the last few days and I have been seeing the same fix you were talking about by swapping the quickset apks back and forth. Ive put together a zip for flashing that I think would make things as easy as possible for people to get the list to show up.
The script in this one sets the correct permissions for everything on flash. It will instal;l the L version of Quickset, which doesnt show the manufactures list. The M quickset apk also gets flashed but i just put it in /system, so its there and can be moved easily. When you boot the first time after flashing, the the ROM uses the L version. All you should have to do then is use a file manager app to move the QuicksetSDK.apk from /system to /system/app/QuicksertAPK/ replacing the one thats there already. Set perms to 644 if necessary. Now wipe tjhe app data for quickset app, forcing the new one to restart, you dont even have to reboot.
Last thing is you have to delete the Quickset Settings folder made by the lollipop quickset. The Marshmallow version will make a working folder of its own the first time you start Quick Remote.
I like your idea to make fixes in separate flashes, that is probably easier
link to my 01262016.AOSP-6.x.x-M_LGQuickRemote_v4.50.19.zip on MEGA
it's working great!
tnx!
i just ran a nightly update on mokee6 which is cm13 similar and i had to reflash the fixes to get it working again and strange thing is i noticed lib folder is gone from quickset sdk folder but it's working
another thing i noticed is quickset sdk is not in my apps list so don't use that as a way to test if it's working either see if manufactures show up after waiting a bit or try the learning feature to test app functionality
im using d852 with stock mokee6 kernel btw of anyone's wondering and yes i have all apps selected
The mult-zip installation also worked out here on BrokenOS. Remote is working fine.
Originally I used "init.d scripts support" app to handle the init.d file. Worked just fine, BTW. Reason for that is I wasn't sure what would happen if I used Universal Init.d with Broken as it has a directory full of tweaks.
On later examination I see that each script needs to be enabled before it will run (via Settings. True/false values are then looked up in a cfg file).
So I reckon I can safely use Universal Init.d.
LG G3 D851, BrokenOS MM ROM, Tapatalk 4.9.5
can i delete universal init.d after enabling it?
@syndre well yes, i think that flashing zip it's pretty straight forward, your new method is simpler but i think that just flashing and not having to deal with system folders and permissions is better for the less tech savvy, but a little more hideous because of the various reboots
smolchy said:
it's working great!
tnx!
Click to expand...
Click to collapse
You're welcome
@marcdw yes, the thing with Universal init.d is that it really enables init.d at boot, Resurrection Remix and AICP also have their individual init.d scripts and they run, i don't know why the QuickRemote script does not run, and Universal init.d does not mess with the existing scripts, so it's not harmful for the system and runs the script at boot and thats what we want
@KronicSkillz well, I'm glad it works, i used the QuicksetSDK thingy because it seemed like it was the only consistent thing, sometimes the Quickset Setup folder would not show, or it will show with the first QuicksetSDK but at least at first QuicksetSDK would not show in the apps list, after the first fix it would and it would show again, i will put it in the post, thanks for the feedback
Roi007leaf said:
can i delete universal init.d after enabling it?
Click to expand...
Click to collapse
I think you can i but i have not tested that, if you do, tell me what that did to update the post, i keep Universal init.d for other scripts that i have installed so i need it, if you only use it for QuickRemote i dont think you'll have a problem
ok checked.. safe to uninstall...
---------- Post added at 04:56 PM ---------- Previous post was at 04:19 PM ----------
btw.. i did all the steps and i can see manufactures but the IR itself doesnt work.. the devices wont react to it..any solution?
Roi007leaf said:
ok checked.. safe to uninstall...
---------- Post added at 04:56 PM ---------- Previous post was at 04:19 PM ----------
btw.. i did all the steps and i can see manufactures but the IR itself doesnt work.. the devices wont react to it..any solution?
Click to expand...
Click to collapse
What variant/rom you have?
Jc_master said:
What variant/rom you have?
Click to expand...
Click to collapse
LG d855 32GB 3GBRAM RR 5.6.2 android 6.0.1
Roi007leaf said:
LG d855 32GB 3GBRAM RR 5.6.2 android 6.0.1
Click to expand...
Click to collapse
Try force closing QuicksetSDK and delete its data, re-flash the fix part 2 and see in that helps, also i think that you need Universal init.d again, the Qremote.log updates at every boot and it wont update if Universal init.d is not installed
Thanks for creating a new thread, I've been busy for a while and won't be able to do much androidy stuff for now.
I have seen an interesting changelog in cyanogenmod that creates selinux policies for QuicksetSDK, but they haven't merged it yet. So fingers crossed that it'll be merged ASAP so things will be easier for us
link: http://review.cyanogenmod.org/#/c/127449/
hikarisei23 said:
Thanks for creating a new thread, I've been busy for a while and won't be able to do much androidy stuff for now.
I have seen an interesting changelog in cyanogenmod that creates selinux policies for QuicksetSDK, but they haven't merged it yet. So fingers crossed that it'll be merged ASAP so things will be easier for us
link: http://review.cyanogenmod.org/#/c/127449/
Click to expand...
Click to collapse
I hop they do, and thank you for your work also
No quicksetsdk in apps but I saw its library in systrm/app and the permissions are correct.. Any idea ?
Roi007leaf said:
No quicksetsdk in apps but I saw its library in systrm/app and the permissions are correct.. Any idea ?
Click to expand...
Click to collapse
Did you flash both fix zips? The need for those 2 fix zips is because the QuicksetSDK that comes in the Qremote_AOSP_MM.zip works with Marshmallow but by itself it will not create some required files in the system and it will most likely not show in the apps list, the QuicksetSDK that comes in fix part1 most of the times wont work on Marshmallow but it will create some necessary files on the system it will show in the apps list but it force closes, and the QuicksetSDK in the fix part 2 is the same as in Qremote_AOSP_MM.zip but this time it has everything needed to work properly and it now should show in apps list allmost every time, so you need to follow the steps again closely and i recommend that before you flash the fix part 2, you go into your apps list and force close QuicksetSDK and delete its data, also report if you get Qremote.log on the root of your Sd and what this shows if its there
Jc_master said:
@KronicSkillz well, I'm glad it works, i used the QuicksetSDK thingy because it seemed like it was the only consistent thing, sometimes the Quickset Setup folder would not show, or it will show with the first QuicksetSDK but at least at first QuicksetSDK would not show in the apps list, after the first fix it would and it would show again, i will put it in the post, thanks for the feedback
Click to expand...
Click to collapse
ya i was using quickset sdk check (apps list) to see if it was working too until i realized it's working without showing up this time
So... here I will share 2 scripts I made to fix permissions for ViPER4Android running with enforced SELinux.
Why 2 scripts?
I like to keep everything open-source. Here I like to notice, Cyanogenmod is taking the wrong direction in my point of view. Every update takes out something of the customization possibilities of the user, so I am thinking of choosing new ROM. I faced real nightmare with SELinux permissions (well... SELinux is good, but Cyanogenmod doesn't provide any tool or way to manage those permissions). The more funny part is that with branch 13.0 of cyanogenmod there is no more init.d. Before someone corrects me - yeah... there is init.d, but SELinux blocks any script from executing at boot time, so don't use it. You will get your logs spammed by error messages. So... I've tried to enable init.d again, but there is no way to manage init.d to work as before. I've tried lots of different fixes from other posts, but nothing seems to work anymore, because of SELinux restrictions. I didn't managed to find any way to run scripts on boot time with root permissions in a suitable way... without messing with other system files or rebuilding build.img... so I came with those 2 solutions:
ViPER4Android (OpenSource) This is the solution I recommend to all of you. It is full open source. It doens't mess with you current system and it should work on any device/ROM. The zip file contains ViPER4Android app and driver, sepolicy-inject tool from setools-android so we can set permissions for ViPER4Android to work with enforced SELinux and Universal Init.d.
sepolicy-inject is open source equivalent to supolicy tool of Chainfire's SuperSU. I strongly recommend sepolicy-inject over supolicy, because every root closed source app should be threaten as security risk as the code can't be examined. I don't trust it esepcially when it is part of your android root manager
Universal init.d is just a application - it simulates init.d function. Imagine it like init.d on the user side... sadly enough you need to be pre-rooted to get it running.
ViPER4Android (Legacy) Maybe more of you will like this solution as it is more automated and it doesn't require any user action after installing the zip. This zip will do the same as the one above - it will install ViPER4Android removing all other DSP apps, but here come the difference - THIS SCRIPT WILL INSTALL CHAINFIRE'S SUPERSU in order to set SELinux policies for ViIPER4Android. Chainfire's SuperSU uses supolicy-tool - it let you manage SELinux policies on boot time. Chainfire's SuperSU will run everything in /system/su.d/ so again... you have init.d support - this is the real pain in the ass.
Before you download and flash, please read:
Both scripts WILL REMOVE other DSP apps from your device and will install ViPER4Android 2.4.0.1. I STRONGLY RECOMMEND TO USE SOLUTION 1 AS IT IS FULL OPEN SOURCE! Support open source software!!!
INSTRUCTIONS
ViPER4Android (OpenSource) - IN ORDER TO WORK, YOUR DEVICE MUST BE ROOTED! (Your device need to be rooted as Unversal Init.d needs root permissions in order to simulate init.d functionality)Download the .zip; Flash and reboot; Open Universal Init.d and grant root permission if asked; Reboot once more in case it don't work!
Sometimes Universal init.d is not fully initialized and needs some root permissions. That's why you need to reboot second time - then everything works. No further actions needed.
ViPER4Android (Legacy) - Just flash and reboot... but once more - SUPPORT OPEN SOURCE AND CHOOSE SOLUTION 1!!!!
For Samsung devices - if the scripts above doesn't work for you, check this post. Thx to Viper4713 for the instructions and voshchronos for solving the issue!!!
Hope to make someone happy
PS: If u want to make me happy with some beer, here you can donate a small amount. Thank you for your support.
Can i flash it on android one device running on 6.0.1
Yes. If you have any issues, please let me know!
rpangelov said:
Yes. If you have any issues, please let me know!
Click to expand...
Click to collapse
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
hiropandaz said:
Hi, i tried to install the open source version on my kltedv running resurrection remix 6.0.1 however it is still not working. The init.d shows the kernel doesnt support init.d, and v4a drivers status is abnormal. It is also cause screen freeze and random restart. Any ideas? Your kind input would be very much appreciated. Thanks.
Click to expand...
Click to collapse
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
rpangelov said:
I've just readed some info about the ROM you use. As it is based on Cyanogenmod I assume there is root manager builded in. Maybe it is disabled as CM root access is disabled by defaults? Look at: Settings -> Developer Options -> Root Access - turn in on by "Apps only".
Then just follow this steps:
1. Start Universal Init.d
2. Turn it off from the toggle button
3. Run test from the button on the bottom of Universal Init.d
4. If ask for root permissions, grant them!
5. Turn Universal Init.d ON from the toggle (step 2 you turned it off)
6. Restart your device and check once more!
If you still have any issues, please let me know!
Greetz,
Angelov
Click to expand...
Click to collapse
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
hiropandaz said:
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Hi Angelov, many thanks for your helpful instruction. I couldnt get it work with open source version. However it is working now after i install V4A legacy version. Many Thanks once again.
Click to expand...
Click to collapse
You are welcome! As I mentioned in the instructions - the legacy script will work always, but I don't like the implementation of it. I am working on new version of the opensource script, so there won't be any issues of that kind. When I am ready I will upload it here after updating my first post.
Greetz,
Angelov
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Primokorn said:
This "universal" fix has been shared several months ago on XDA and a simple root shell is enough to use V4A in enforcing mode.
FYI init.d is deprecated now but it's not related to CM. Use su.d instead.
Click to expand...
Click to collapse
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
rpangelov said:
Can you provide me a link to this universal fix you are talking about?
PS: init.d is deprecated in AOSP, i get that. Please read my first post once more, obviously isn't clear enough. Using su.d will result in using closed source tools to manage your Selinux policy's. As I mentioned it above - please support open source software. Every closed source root app has to be threaten as security risk. My opinion...
Click to expand...
Click to collapse
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Primokorn said:
Check the official V4A thread for instance. Others have opened threads in device specific forums or in the App & Games forum.
Have a look at this thread, it might interest you: http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
FYI I do support open-source free/libre softwares, as much as I can.
Click to expand...
Click to collapse
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
rpangelov said:
I've seen phh's SuperUser but I didn't tried it - this is one of my tasks for this/next week.
As I've tried the most scripts, I didn't liked all the actions needed to be taken before running the .zip script in order to get viper working. I compile my own Cyanogenmod and I don't use gapps. Almost all apps I use on my device are opensource as I use F-droid as my only market (well... I need whatsapp, but I download it just from the website). Anyway... Cyanogenmod has it's own root manager builded in.... so why I need to install one more, which contains closed source tools in it? That is also the reason I don't advice people to use it... and I don't see that as solution to my problem. AOSP is opensource, but nowadays it is very dependent on some closed-source elements and I want to wipe them all out and use open source alternatives for. I hope you understand why using su.d isn't solution in this case. You just make your self and others dependent on one more closed source app, so I don't get where is the support for open source? I think that opensource script is good solution to the problem without using any closed source tool.
To make it easy as possible - just flash the .zip and you are ready to go, I included the latest version of Chainfire's SuperSu in the legacy script, so you don't need to install it before running the .zip. It looks easier to me....
Actually it is very stupid because the result of using the scripts (doesn't matter which one) you will end up with rooted device anyway (if it isnt already), but in order to get opensource script working your device has to be rooted before running the .zip, but if your device is already rooted, you just flash the zip and you are ready to go.
Click to expand...
Click to collapse
I mentioned su.d because that's a solution with newer Android versions but I didn't say it's the best one. Using FLOSS softwares is a good move but you are using proprietary codes with CM.
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
trongtin64 said:
Hi everyone, i flashed both of the zips with TWRP but i got an error code : 255. Any idea how to fix it ? Please help me. I'm using an x86 phone btw
Click to expand...
Click to collapse
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
rpangelov said:
I think it's because your phone architecture... anyway - I will look at it today and I will let you know if I find a solution for your problem. Can you tell me which phone exactly you own ? Thank you.
Greetz, Angelov
Click to expand...
Click to collapse
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
trongtin64 said:
i'm using a zenfone 5 (A501CG) with resurrection remix mm 5.6.7
Click to expand...
Click to collapse
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Primokorn said:
You have a x86 architecture and this zip is probably for arm only. I guess you need the updater-binary for x86 and place it into the zip in META-INF/com/google/android.
Click to expand...
Click to collapse
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
trongtin64 said:
Ok so i need an updater-binary for x86 right? Can i copy it from other zip to your zip? Will it work?
Click to expand...
Click to collapse
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Primokorn said:
AFAIK you can use the one from a custom rom. You need a compatible custom recovery of course.
Click to expand...
Click to collapse
I'll use the one from my custom rom . Thank you for helping me :good:
It works great. thanks.
my bad for not following the instructions.
Custom ROM Manager finds all the ROMs, GApps and other zip files that are downloaded on your device, lets you install or manage them easily. It also helps you visit official sites of some ROMs/GApps from where you can download them or see changelog.
NOTE: This app does not search the internet for ROMs, GApps and other mods for your device. You have to download them from their respective sites yourself to your device. Then this app will take care of the rest.
Screenshots
Check screenshots tab
Key Features
Finds all the zip files on your device - Custom ROM Manager features multiple file searching algorithms to find the zip files on your device. They are fast, customizable or both fast and customizable at the same time. Users can even choose their file searching technique to their liking.
Sorting and grouping of zip files - After zip files have been found, app sorts and groups them to their appropriate category, like detects which of them are ROMs, GApps etc. It can even detect the properties of a ROM/GApp, like their build dates, version, whether or not they are OFFICIAL builds and what not. The techniques used are efficient and smart.
Popular ROMs/GApps - The app shows list of popular ROMs/GApps. They are selected based on observations of the most popular and most user responded ROM threads across the XDA forums for top devices, and they are listed alphabetically in the app. App is also capable of detecting other ROMs, which will be listed in the "Other ROMs" category.
Official information for popular ROMs/GApps - For all the popular ROMs/GApps listed, you can even check their official information. Like their official sites, download pages etc. It can even check whether your device is officially supported or not, and depending on this, it will open download page for your device when you visit their download page.
Disclaimer - The app makes use of the information that is already available on the internet. It does not use any unauthorized or confidential data. The links are also opened in an external web browser of user's choice, not in some in-app browser or something like that.
Manage your ROMs/GApps - Under each popular ROM/GApp listing, you can see the builds present on your device listed their. Like all your LineageOS ROMs gets listed under "LineageOS" category. You can view them in any way, view them in sorted order based on their build dates or version, or see only unofficial ROMs, or official ROMs. You can delete them, view them etc.
Install them - And finally, you can select them for flashing/installation. This is arguably the most significant feature of the app. You can choose any number of zips for flashing, you can specify which partitions to be wiped before each zip is flashed. You can modify your selection in any way you want, like re-order your selection, delete any entry and what not. And finally, when you confirm, device will boot into (TWRP) recovery, flashing the zips in the very order you selected.
To see the complete feature list, visit the play store page or XDA Labs page.
Google Plus Community - https://plus.google.com/u/0/communities/109799614948604849024
Requirements
Root Access is must.
If you havent flashed custom ROMs before, this app is not for you.
Only TWRP is supported.
Download
Play Store
XDA Labs
XDA:DevDB Information
Custom ROM Manager, App for all devices (see above for details)
Contributors
corphish
Version Information
Status: Stable
Created 2016-07-22
Last Updated 2019-02-04
Sounds interesting.
I will give it a try when i get home and get my hands on my tablet.
@corphish
Cool
One request.
Can u recognise xpossed framework Zip and modules Zip ?? Like Roms and gapps?? It will be damm helpful for everyone ^~^ just a request
Sent from my sprout4 using XDA Labs
harsh. said:
@corphish
Cool
One request.
Can u recognise xpossed framework Zip and modules Zip ?? Like Roms and gapps?? It will be damm helpful for everyone ^~^ just a request
Click to expand...
Click to collapse
Well I am not much acquainted with Xposed and its modules coz I don't use it, but I remember they are .apk's.
Can you link me to those zip files which you are talking about, so that I can take a look and add it in next update?
http://dl-xda.xposed.info/framework/
This
And sorry I just forgot that modules are apk
And if there is way to get kernels differently, is also welcomed.
And sorry for making so many requests!
:fingers-crossed:
Sent from my sprout4 using XDA Labs
harsh. said:
http://dl-xda.xposed.info/framework/
This
And sorry I just forgot that modules are apk
And if there is way to get kernels differently, is also welcomed.
And sorry for making so many requests!
:fingers-crossed:
Click to expand...
Click to collapse
We will see about xposed.
And custom kernel support is not possible because various devices have various custom kernel, sorting them would be simply not possible..
corphish said:
We will see about xposed.
And custom kernel support is not possible because various devices have various custom kernel, sorting them would be simply not possible..
Click to expand...
Click to collapse
Its 10:30am in morning and I'm already out of thanks(8 are given idk where let me check)
So thank you.
Sent from my sprout4 using XDA Labs
Great app.
Very useful especially for beginners.
But I have 4 main requests that will improve the app :
1_it's really bothering that every time I want to launch the app it scans for zip files, it takes a lot of time especially for the low-end phones and for phones that have large Memory.
Maybe you should make it saves the path of the zips and names and add a refresh button in the AppBar in case we add new zip.
2_Add wipe davlik-cache,
It's really needed when flashing modes.
3_maybe in the future you should add an options to explore the zip and extract some files.
4_add a new layout for backup and restore specific files from system (build.prop_framework-res....etc) or the whole ROM and save it as a flashable zip in case the flashed ROM has bootloop or some problem you can restore it form recovery.
Sorry for asking a lot I know it's the first release and that is a lot to ask.
So far the app works great and the design is simple and beautiful as usual (I know from your previous apps)
Thanks for your hard work
Great app UI and Idea, but on my Nexus 6 XOSP 6.3, It doesnt detect anything. I give the root access and storage permission, but it stays at "uhh,nothing here". And thats really it. Any idea? Is there some folder i need to put my zips in?(like delta uses). Thanks!
Root Wizard said:
Great app UI and Idea, but on my Nexus 6 XOSP 6.3, It doesnt detect anything. I give the root access and storage permission, but it stays at "uhh,nothing here". And thats really it. Any idea? Is there some folder i need to put my zips in?(like delta uses). Thanks!
Click to expand...
Click to collapse
Same with me on my lenovo a7000 cm13 rom
Please reply if you want any logs. The idea is awesome and I will surely be gald to help
Root Wizard said:
Great app UI and Idea, but on my Nexus 6 XOSP 6.3, It doesnt detect anything. I give the root access and storage permission, but it stays at "uhh,nothing here". And thats really it. Any idea? Is there some folder i need to put my zips in?(like delta uses). Thanks!
Click to expand...
Click to collapse
anaandshailu said:
Same with me on my lenovo a7000 cm13 rom
Please reply if you want any logs. The idea is awesome and I will surely be gald to help
Click to expand...
Click to collapse
Sorry for late reply, I was busy in the mean time with M and N bringups for some devices.
In Marshmallow ROMs, there is a problem detecting internal storage, which will be fixed in next update, which will come very soon.
Edit: 1.5 is up, check labs
Update 2.5
With previous update (2.0 and 2.1), app was recoded from scratch, resulting in many optimizations and bug fixes.
For example, with 2.0, came better storage detection logic and faster file scanning algorithm, while 2.1 added more modern UI elements.
With 2.5 comes many of the requested features like Zip scan caching, separate option for dalvik cache, and new features like search, respective logos for popular custom ROMs etc.
Please refer to XDA Labs for full changelog.
And do rate and review .
Version 3.0 was released with many cool features.
- Zip selection for flashing was totally revamped. When you tap a card, it will now flip and you will see various partitions you can wipe. Select any if you want to and then tap the card back, it will flip back and notify that the zip has been selected for flashing. And now you can even update what you want to wipe by tapping one of the already selected card back and re-doing the drill. You can even remove it from the flash queue.
- The UI where you are shown what you are going to flash (i.e flash queue) is also revamped.
- Statistics section is also revamped, now shows total size each class of zip is consuming.
- You can also perform TWRP backup and restore operations from the app.
- Some SU related issues (especially on newer security models) were fixed.
- There are always under the hood performance improvements and cleanups.
And all this feature additions barely saw the app size rising. Do check the new screenshots under screenshots tab.
And btw, Custom ROM Manager was released in Play Store too, few days back.
Free version
Donate Version
I use yunicorn 5530 and I tried to search custom ROM for my device but didn't find anything... Do you guys can help me
A new and major version of 3.1.1 has been released.
Summary:
1. Quick selection for zips/backups for flashing/restoring.
2. Ability to delete files.
3. Completely revamped FlashQueue Interface.
4. Inbuilt troubleshooter.
Detailed changelog : Google+ Post
سامسونج s2
3.3 update
Released 3.3 update yesterday
Detailed changelog - Google+ Post
Version 4.0
Version 4.0 was released recently.
Detailed changelog - https://plus.google.com/u/0/+AvinabaDalal97/posts/Deqcbgpq8nJ
4.3
Version 4.3 was released few days back.
Thread updated.
corphish said:
Version 4.3 was released few days back.
Thread updated.
Click to expand...
Click to collapse
Maybe was i to lazy to find it, but it took already a lot of Time to find the "Custom ROM Manager". How can i add My LIGHT PATCH to the Patch Section of Your Project? I wold like to push Your App by default alongside with My Patch in the Future to use it as kind of OTA Updater. Maybe could You direct Me, or do i even have something new for You? (Checking build.prop for the Patch Version so the App can advise a Update if needed!?)
Would be cool to be Part of that! I'm really looking forward to contribute to it...
BR
During the last few months I have been testing several Nougat rom/kernel/modem/su combinations for the hlte N9005 international.
I created this thread to share my setup, hoping it will help others to save the many hours of research, trial, error and frustration I had before reaching the jackpot.
I have 3 hlte phones at my disposal, two myself and one my wife. All three are running trouble free.
By using my setup you will get:
Absolutely no freezes, reboots or FCs
Stable root and Safetynet checks ok
GPS fast and stable fix - average 5 seconds worst 20 seconds
Low battery drain (of course actual drain depends heavily on your apps and usage)
Everything works (AFAIK - you tell me what does not)
Keep in mind my main goal is to provide a stable setup. I will do my best to update this thread regularly, but it is very unlikely I will be using the very latest builds available, mainly because before I adopt a new build it must be thoroughly tested.
If you're interested head to the guide in Post #2
Why Resurrection Remix?
RR has, IMHO, the best combination of features and stability. The RR team has been around for a long time without the ups and downs of other roms. For the Note 3 we are in a very fortunate time, with an official build and many unofficial builds to choose from.
Since RR is based on LineageOS, it is available for most devices. It is very likely when we finally retire our Note 3 and move to another flagship, RR will be there for it.
Why Not Oreo?
Well, thread title says it all.
Credits and Thanks:
@vidwhal for the current RR build
@gj86 for Synergy kernel
@Jairus980 for Xenial kernel
@Hereiwas and @jcadduono for modems and bootloaders
@topjohnwu for Magisk
@stangri and @kantjer for Magisk unofficial daily beta builds
@Deic for the Safetynet fix Magisk module and @NovelliJack for finding the module
@MastahF and all other contributors that made the Open GApps project possible
Special thanks to @tarkzim for the RRN build used in initial setups.
and everyone else I forgot to mention.
>>>>>>> I know - screenshots below are from a previous setup. I will update then sometime in the future.
Rock Stable Setup
Using Resurrection Remix
Revision 11 - 11-Mar-2018
Phase 1 - Prepare for install
Here I am assuming you have a Windows PC. If not you will need to use google search to adapt my instructions to your available OS/hardware. The PC is only required for this phase.
1 - Samsung USB Driver:
Make sure you have the Samsung USB driver installed in your Windows PC.
If not download and install the latest driver:
- SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.65.0.exe
2 - Odin:
If you do not have Odin, get it here, unpack to any folder and create a shortcut pointing to Odin3 v3.09.exe.
There are newer versions of Odin, but they may have issues with our Note 3. Odin v3.09 is the one to use.
3 - TWRP
New to TWRP? Read this guide: TWRP: the complete guide to using Recovery on Android.
If you do not already have it, install TWRP 3.2.1-0. Download it from https://dl.twrp.me/hlte. More info here.
If you no not have TWRP installed download the .tar file and flash with Odin.
If you have an older version download the .img file and use your current TWRP to flash the image into recovery partition.
4 - Update Bootloader and Modem:
You have to install latest Nordic Countries Bootloader and Modem. I have prepared a "tar.md5" with both.
And yes, modem is not country or region dependent. Rest assured Nordic will work no matter where you are.
Get it from here: N9005_Nordic_XXUGPQB1-Modem_XXSGBQD1-Bootloader.tar.md5
Updating bootloader and modem is a must!
If you don't you may get the "SIM Card not detected" error and GPS fix will be slow or not work at all.
There are many sure ways to flash modem and bootloader so that they "stick". What always works for me is:
- Restart into Recovery (TWRP)
- Select Reboot->Power off
- Turn on directly into download mode by holding Down Arrow+Home+Power at the same time
- Connect phone to PC
- Flash with Odin using the AP slot
Now you should check if update was successful. The best way is to install the app Phone INFO, run it and select the Firmware tab. The correct Bootloader and Baseband (modem) above should be displayed. There is a screenshot in first post.
If the update did not work repeat the steps carefully until it does. You may, as a last resort, after powering off remove the battery, wait for about 30 seconds, reinsert the battery and then turn on directly into download mode.
Thanks to @Hereiwas for the files I have used in previous setups. Check out in his thread Bootloader and Baseband for SM-N9005.
If you need more info on flashing modems and bootloaders also take a look at @jcadduono thread [Direct Download] Latest Bootloaders & Modems.
PHASE 2 - Download the necessary installation files
1 - Resurrection Remix Nougat rom - thanks @vidwhal:
Download from here: RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip.
Please note that I am not the rom builder or developer. All credits go to @vidwhal and the RR Team.
This is the rom thread: [ROM][HLTE][UNOFFICIAL][OMS]Resurrection Remix N.
Please note this build may not be the latest available. The goal here is to have a stable rom that you will be able to use as a daily driver with no issues for a long time. Only after a lot of testing a new build makes into my setup.
I modified the zip to remove Magisk. This will make it easier to use newer or beta Magisk builds if necessary in the future. Remember Safetynet is a cat and mouse game and changes happen fast.
Special thanks to @tarkzim, who produced the RR builds used in earlier setups. He did a fantastic job of producing a very stable build without a Note 3 device for tests. His builds led me to create this thread.
2 - Magisk v16.0 Official - thanks @topjohnwu):
Magisk Installer: Magisk-v16.0.zip
Magisk Manager: MagiskManager-v5.6.1.apk (optional - you might need it in the future)
Magisk Uninstaller: Magisk-uninstaller-20180222.zip (optional - you might need it in the future)
if you decide to use newer builds do it at your own risk. I strongly recommend to keep these.
3 - Gapps:
Open Gapps Pico: open_gapps-arm-7.1-pico-20180311.zip
Not much to say here. Open GApps FTW.
Again the above build is the one I tested. Use this for a failproof installation, but feel free to use a newer build. Usually it will not be a problem.
I prefer Pico Gapps so I have the bare minimum as system apps. And I live by the KISS Principle. All other gapps I need are installed as user apps so I am allowed to use Titanium Backup to backup/restore them with data.
If you would rather use another Gapps package just pick the one you want. All packages should work but the Aroma. Aroma does not work in TWRP 3.
4 - Xenial Kernel - thanks @Jairus980:
Xenial Kernel: [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
Kernel thread: [Kernel][Xenial][Hlte].
With Xenial you have some fixes like the correct charging current in lock screen and working Gravity, Linear acceleration and Orientation sensors. Of course there is a lot more under the hood. If you plan to do some kernel tweaking Xenial offers more options.
If you do flash Xenial kernel do not report any bugs in RR thread. To report a bug you must first go back to stock kernel by dirty flashing RR and Magisk. If you are still able to reproduce the bug then you may post it in RR thread.
Even if there is a newer kernel release, you should keep using the build I posted here to have my tested stable setup.
Special thanks to @gj86 for his Synergy Kernel, used in my previous setup. It is also a great option.
5 - GPS Fix:
In this setup there is no need for a GPS fix. GPS is fast and rock stable as it should always have been.
But you really must update your modem to my recommend Nordic QB1 or GPS will be slow or not work at all.
Do not worry about your current location. The modem will work not matter where you are.
Latest RR builds somehow made GPS fix slower. I checked the gps.conf file and it is exactly the same as in previous builds.
I have my own optimized gps.conf, prepared originally for Marshmallow CM13, with a few more adjustments for Nougat.
After installing my gps.conf in latest RR build, gps fix is back to normal, taking only a few seconds.
I prepared a flashable zip to install my gps.conf. It saves existing gps.conf and put mine in its place.
Download it from here: Fix-GPS-for-hlte-la14.1-based-roms-v1.zip.
PHASE 3 - Backup!!
Now it is time to make backups of your current setup.
Use TWRP to make a nandroid backup. You will need it if something goes wrong. If you are paranoid like me make two and save them on your PC hard drive.
If you use Titanium make also a Titanium full backup. Remember that you should never restore system apps or settings. Use Titanium only to restore user apps and xml backups of wifi passwords, call log and sms messages.
The steps to install the new ROM will not erase your internal storage, but why not make a backup of everything to your PC or an OTG USB Drive.
PHASE 4: Install
- Make sure you have updated TWRP and your bootloader and modem as instructed in phase 1
- Make sure you have all files downloaded from phase 2 in your phone - preferably in external sdcard
- Make sure you have backups!!
- Reboot into Recovery (TWRP)
- Use advanced wipe to wipe System, Data and Cache
- Flash RR-N-v5.8.5-20180101-hlte-Official-vidwhal.zip
- DO NOT WIPE ANYTHING
- Reboot System (be patient - it will take a while, around 3-4 minutes)
- Pick your preferred launcher
- Check Settings->Date & Time and make sure it is ok
- Reboot into Recovery (TWRP)
- Flash [Hlte][Xenial-b26x][02.01.18][N7.1-GSM].zip
- Flash Magisk-v16.0.zip
- Flash open_gapps-arm-7.1-pico-20180311.zip (or the one you prefer)
- DO NOT WIPE ANYTHING
- Reboot System (this time it will be faster)
- Go to Settings->Accounts and add your google account
- Customize your other settings
- Run Magisk Manager and check if SafetyNet passes
- If not disable/reenable "Magisk Hide" option in Magisk Manager Settings and try again
- Restore/install apps/data
- PROFIT!
[Reserved]
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
tarkzim said:
wow, nice to see that someone using and "sharing" my builds
but a little tip for you, maybe you can ask me first before you post something are modified from me, no offense and i saw that includes my name on it.
just remind you and i think i will keep building this when i'm free, anyway, thank you for posing this. all good.
EDIT: also i think there is no need for removing magisk separately, it's fine for flashing newer magisk over the older one.
Click to expand...
Click to collapse
Sorry, you are absolutely right.
Thanks for being cool with it.
The main point in changing the rom zip is removing the magisk manager system app. It is a little tricky for noobs to remove the system app to be able to install the v5 beta Magisk Manager.
And thanks again for making your fantastic RR build available.
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
sperug said:
Thank's for your work. I installed all, but then I had a problem. When I try to open settings/apps, it crashes everytime....
Click to expand...
Click to collapse
This does not happen in my phones.
In my work phone I have 600+ apps installed. It takes a while to open but no crashes.
If you post a logcat I may be able to help.
I reinstalled everything, and before made a full wipe, also of the internal storage. And the problem was no more present! Wow! And thank you again...
I checked AFH and have 30+ downloads of installation files.
Any more success or failure cases? Please let me know.
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
BobbyKa said:
This might be a silly question: You wrote I should download the latest NORDIC COUNTRY Bootloader and Modem.
Is this also correct if im not living in an other region or should I download the one from my Country? Thanks.
Click to expand...
Click to collapse
AFAIK it should work for you no matter where you are.
I live in Rio de Janeiro, Brasil and use it.
If it does not work for you just flash another one.
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
BobbyKa said:
I tried the Nordic ones and everything seems to work. Not a killer but would be great: is there a way to get SPen functions inclidung Air Command? Thanks for the help.
Click to expand...
Click to collapse
To use Sammy Spen apps/features you need a Touchwiz based stock rom.
There are some apps with similar features for AOSP roms.
Many users say the best is SPenCommand developed by @emandt. It is paid but users say that the app is well worth the price.
Check the SPenCommand Google+ Comunity.
Great post. I don't see google assistant working, any clue?
Sent from my Pixel using Tapatalk
---------- Post added at 09:22 PM ---------- Previous post was at 09:10 PM ----------
Please ignore, I installed nano gapps and it worked
Sent from my Pixel using Tapatalk
what about battery life ?
has anyone tried this on Sprint Note 3 sm-n900p ?
svbarbosa said:
Check the SPenCommand Google+ Comunity[/URL].
Click to expand...
Click to collapse
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
BobbyKa said:
I installed SPenCommand but the App doesn't open. When clicking the Icon nothing happens. Anyone knows about this Problem or knows another app for this?
Beside that everything (incl. Batterylife) seems great on this first day of testing.
Click to expand...
Click to collapse
I have never used SPenCommand myself. Just read good things about it many times in other threads. Try to search and get help from people who are using it.
You may also check these apps: Note Buddy (S Pen Helper) and CM S Pen Add-on(ROOT).
And this guide on them: The Ultimate S Pen Customization Tool for Your Galaxy Note 3.
But be advised that I have no experience using these apps. Just found them using google.
opexblue said:
I have followed your step to instal, wipe dalvik/art, system, data & chache. Flash ROM then reboot.
I got 'Could not do normal boot'.
Enter TWRP again and instal synergy kernel and reboot, I still got 'Could not do normal boot'.
My phone:
Samsung Galaxy Note 3 SM-N900S (Korea)
TWRP 2.8.7.0 hlteskt
CP N900SKSU0GPC5
BL N900SKSU0GPB1
sent from my Galaxy Note 3 using XDA Labs
Click to expand...
Click to collapse
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
svbarbosa said:
Sorry I can not be of help here. I only have the hlte N9005 international Note 3.
Maybe you could replace Synergy RC9 by a kernel that you are sure works with your N900S.
Click to expand...
Click to collapse
Thank you for fast response. I will try other kernel.
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.