Database Info

ultimate rooting flashing ..............etc

Android and iOS are the most popular mobile operating systems on the market. Both offer a variety of apps and settings but, eventually reach their limits at a certain point. Rooting or Jailbreaking your phone (or tablet) will offer you thousands of tweaks, skins and new apps that you should not miss out on. It will also help you to remove bloatware.:laugh:
Android Launchers and lock screen widgets are great tools to customize your Android experience without rooting your device. You are also able to root your device and customize it with a launcher and widgets afterwards. If your Android device is rooted but you don’t want flash a custom ROM, Xposed Framework might be the perfect solution for you. You are, however, also able to add new features to your custom ROM with Xposed. With the release of Android 5.0 Lollipop Google replaced the former Dalvik cache with ART. Luckily, Xposed was adapted to Android 6.0 Marshmallow
This guide is based on Google Nexus devices, but most of the things also apply to other Android devices. Some might require more work while others can be rooted quite easily, but in the end it’s no rocket science. Rooting and customisation is especially easy on Nexus devices as factory images are freely available on the Google website. However, many other popular devices like the can easily be restored using different tools available on XDA developers. I would suggest to have a quick look at the forums and I’m pretty sure that you’ll find help for your device.
Android Rooting Terms You Should Know
Before we get started, I would like to explain a few terms because the terminology can get complicated and confusing. This will help you to understand other device specific guides. I’ll try to keep it short and not go into (technical) details. Please share any questions regarding this in the comments below – I’ll do my best to answer them.
ART
ART stands for Android Runtime and replaces the formerly used Dalvik cache. It was introduced in Android 4.4 and has completely taken over in Android 5.0. I don’t want to go too deep into technical differences, but ART is said to improve battery life and app performance, amongst others.
Bootloader
The Bootloader is your phone’s software foundation. It’s basically what runs before your operating system starts (like a PC’s BIOS). As many manufactures don’t want you to modify your phone’s OS, it needs to be unlocked before you are able to root your phone or install custom ROMs (explained later).
Brick
This is something you don’t want to happen to your Android device. Like the name already implies, a bricked phone (or tablet) can only be used as a paperweight or nice decoration for your apartment. Bricked devices are irreversibly damaged and won’t work anymore. This can, for instance, happen if damaged ROMs are installed or wrong firmwares are flashed. Always make sure to read instructions and verify checksums (a set of numbers that identify the file) to make sure nothing goes wrong. If you’re lucky and your device is only soft-bricked, meaning that it does not boot but still turns on, you might be able to get it back to life.
BusyBox
Android, being based on Linux/Unix, offers a limited amount of UNIX commands (which most users won’t need anyways). BusyBox will implement more commands that are necessary for some root apps to work properly.
Custom ROM
A custom ROM is a modified version of the Android operating system. Tweaks, additional features, different themes or an enhanced performance are usually included. Custom ROMs also offer the possibility to use a newer, unreleased, version of Android on your phone that might usually not be available for your device because of restrictions from manufacturer or providers.
Dalvik
Dalvik is a virtual machine that processes Android app code. Consequently, it is responsible for translating app code into actions on your Android device.
Fastboot
Fastboot is a diagnostic- and engineering tool which offers you several features such as launching in recovery mode or flashing image files.
Kernel
The kernel is the brain of your phone that controls how the system and hardware interact. It’s basically the lowest level of your operating system that manages memory and hardware.
NAND partition
NAND stands for “Negated AND” or “NOT AND” and describes the hard drive partition that stores all system relevant information like the bootloader, recovery mode or the kernel.
NANDroid backup
A NANDroid backup is a complete system backup of your Android device. This backup can be restored later and might save your phone after flashing a faulty ROM or theme.
Radio
The radio is responsible for sending and receiving voice and data. Using an optimized radio can improve your phone’s reception or increase battery life.
Recovery Mode
Recovery mode offers you the possibility to perform system-level tasks (like formatting, defragmenting, etc.), backing-up your devices or install custom ROMs. Android offers a limited stock recovery function. More sophisticated recoveries like ClockworkMod Recovery and TWRP Recovery offer additional features and are easier to use.
Root
Rooting will give you full administrator access of your device. It might also void your warranty (depending on the device and your place of residence), so make sure to handle your device with care after rooting it. You are always able to revert this process by simply flashing a stock-ROM (the original ROM installed by your phone’s manufacturer). Doing this will also “restore” your warranty.
S-OFF
S-OFF means that the NAND partition of your Android device is unlocked. This mostly applies to HTC phones.
Superuser
Rooting your phone will create a new “account” with complete administrative permissions. This superuser account is used by some apps and functions.
Xposed Framework
Xposed Framework is an app that can be installed on a rooted Android device which offers custom ROM like features on stock Android. It has been updated and is now fully compatible to Android 5.0 and Android 6.0.
5 Reasons to root
With Android becoming better and better, many people ask themselves if it’s still worth rooting. For example, you’re not able to use Android Pay if your Android phone is rooted. The same applies in other cases, where App developers decide to not support rooted devices for security reasons.
In addition to that, Android M will come with many features like “Doze” which basically replace root apps such as Greenify. So what exactly are reasons to root in 2016?
You have an old(er) Android device. With root access, you’re able to flash a custom ROM with the latest version of Android. Because of this, you don’t rely so much on your device manufacturer to keep you up to date.
AdAway. While I’m all-in for supporting developers, some apps don’t offer an ad-free paid version. With AdAway you’re able to get rid of all unwanted ads which is simply not possible without root.
Titanium Backup. Android M will bring Auto Backup for Apps, but unfortunately it’s still up to the developer if he/she wants to implement it or not. Titanium Backup is a simply but powerful tool that backups simply everything.
Change DPI. With many devices coming with high-res displays nowadays, some people prefer to have more screenspace than big app icons. While changing DPI can also be done without root, it often breaks different apps.
Remove bloatware. This one is easy. Remove all the crap your mobile carrier put on your device. Who doesn’t want to do this?
How to Fully Backup Your Device Without Root
If your Android device is not rooted yet, you won’t be able to perform NANDroid backups. I wouldn’t suggest to root your tablet or phone without having a proper backup, because there is always a chance of error and you don’t want to brick your device.
Simple ADB Backup let’s you create a full backup of your device without root access and is the perfect solution for users without root access. The free program also offers a restore function and runs on Windows and Linux.
If you’re already rooted, make sure to check out our guide on performing a NANDroid backup.
How to Root Your Android Device
The rooting process differs from device to device which makes it impossible to give general instructions on rooting here. I’ve linked guides for some of the most popular devices below. Using the terms described earlier should make the rooting process easier for you. If your phone or tablet is not on the list, you most certainly can find a guide on the XDA-Developers forums.
Google Nexus 4, Nexus 5, Nexus 7 and Nexus 10
Google Nexus 6P
Google Nexus 5X
Oppo OnePlus 2
Samsung Galaxy S6
LG G4
Samsung Galaxy Note 5
Always make sure to perform NANDroid backups of your devices to be able to restore your phone or tablet to a working state. I would also recommend to validate checksums and carefully read through the instructions to avoid bricking your device.
Most Important Fastboot Commands
When confronted with Android rooting, you often have to work with fastboot. Fastboot is part of Google’s Android SDK and is mostly used to re-flash partitions on your Android device, similar to (custom) recovery mode. You usually use fastboot in the following manner:
fastboot [ <option> ] <command>
Here’s a list of all options and commands:
Options
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
Commands
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
Now that we’ve covered all existing fastboot commands and options, let’s have a closer look at the most important ones and what they do / mean:
fastboot oem unlock
This is a special command and not part of the initial list. Using this command, you can unlock the bootloader for Google Nexus devices.
fastboot flash recovery recovery.img
This command will flash a custom recovery to your Android device. Depending on the file name, you need to change the bold part of the command. Please not that this only works with *.img files
fastboot -w
Caution: This command will completely wipe your device
fastboot update filename.zip
This command will update your ROM based on the provided *.zip file
Custom Recovery Mode
The standard Android recovery mode is very limited and does not offer many features. That’s where replacement recoveries like Team Win Recovery Project (TWRP) and ClockworkMod Recovery (CWRM) come in place. They offer the possibility to flash custom ROMs which is not possible with the stock recovery mode. Other features include a file browser for update.zips, adb shell and NANDroid backups. Without a custom recovery you won’t be able to flash a custom ROM.
It does not really matter which replacement recovery you install, just go with the one that suits you most. In some rare cases the root script or custom ROM installation only works with either TWRP or CWM. Nowadays, TWRP is the king of custom recoveries and would be my suggestion for you to use.
TWRP – Team Win Recovery Project
Team Win Recovery Project‘s custom recovery offers an easy and touch driven user interface. It includes all typical recovery features needed to install custom ROMs, kernels, other tweaks and many more. You are also able to backup and restore your device using TWRP.
ClockworkMod Recovery used to be one of the most popular custom recovery modes. However, in the last 2 years TWRP took over the throne and became the most popular recovery. It also includes all advanced recovery features like installing custom ROMs and other files, as well as a backup and restore function. You can control the CWM UI via touch or key-input.
Understanding Custom ROM Versions
As Custom ROMs are constantly improved, they usually come in four different categories: Nightly, Milestone, Release Candidate and Stable. This is what you can expect in every stage:
Nightly
Nightly versions are usually generated every 24 hours and can be highly experimental and unstable. Especially early versions of a new custom ROM can have many bugs and missing features. If you want to have the latest features while risking instability – go for nightlies!
Milestone Snapshot
Milestone Snapshots are basically nightly versions that have reached a certain milestone. They can be regarded as being quite stable, but may include certain bugs and issues. Since they are only created every few weeks (or months), they won’t have the latest features that might be included in the nightly versions. If you are looking for the latest features while having a rather stable system, check out milestone snapshots.
Release Candidate
Release candidates, as the name already implies, are one of the last builds before the stable version of a custom ROM is released. RCs are mostly stable but might have a few minor issues. If you’re looking for something stable and ready for daily use, I would recommend to go with release candidates!
Stable
Stable versions are (obviously) the most stable versions around, with all or nearly all problems fixed. Some stable ROMs may still include some smaller issues or certain things not working. Stable versions are definitely the safest way to go, but it might take months before a new stable with new features or fixes is released.
Official, Unofficial & Combined Releases
It is also important to say that custom ROMs are often available as official and unofficial releases. Later use the source code of the official release (if publicly available) and adapt it to devices not supported by the main developers. Unfortunately, this often leads to a delay. In addition to that, many developers combine features of different custom ROMs.
Custom ROMs
Custom Roms offer you a variety of new features, tweaks and visual enhancements. The best source to find a working one for your device is the XDA-Developers forum. Many custom ROMs are based on the two big releases: CyanogenMod and Paranoid Android. The easiest way to find the best custom ROM for you is to compare their features or simply test them for a few days. To make your start easier, I’ve written a few words about the major custom ROMs below.
I’m only able to give you a limited overview in here. If you really want to dive in I would recommend checking out your device specific sub forums on XDA developers. With Android modding becoming more and more popular, you’re often able to find many different custom ROMS for your device, especially if it’s one of the more popular phones or tablet.
CyanogenMod
CyanogenMod looks very similar to stock Android, but offers several enhancements and tweaks. Besides increased system performance and reliability, it includes many interface enhancements and integrated features. CM is one of the most popular custom ROM solutions as it brings a stock Android experience to many devices that come with a heavily-skinned Android version such as LG or Samsung Galaxy devices.
CyanogenMod Features
OpenVPN integration
Lockscreen gestures
Expanded quick settings
DSP equalizer
Complete Theme engine including own theme store
Wi-Fi, bluetooth, and USB tethering
CPU over- & underclocking
Based on Stock Android
Latest CyanogenMod Version
CyanogenMod is usually up-to-date and uses the latest Android version. The latest version available is:
CM 13.0 – based on Android 6.0 Marshmallow
A quite unique feature of CyanogenMod is it’s installer which makes installing the custom ROM quite easy. Besides flashing the ROM it will also root your Android device and will guide you through the whole process. Unfortunately, the installer is currently only available for Windows.
CyanogenMod is available for the majority of popular Android devices. You can find a list of supported devices on the CyanogenMod website.
BlissRom
BlissRom is a new kid on the block. They basically take CyanogenMod as a source and add some magic to its. While updates are not as frequent as with CyanogenMod, the team covers the most important stuff and usually releases up-to-date stuff.
BlissRom Features
Based on CyanogenMod (= all of its features)
Audio Improvements
Endless list of visual improvements
Global gestures
Modified power menu
Latest BlissRom Version
The latest BlissRom version is based on CM 12.1 and is called BlissPop and still running Android 5.1.1.
BlissRom is available on a range of devices. You can find a list here.
ParanoidAndroid
ParanoidAndroid is completely different to CyanogenMod and one of the “newer” custom ROMs out there. It’s currently my favorite custom ROM as it’s fairly close to stock Android while adding cool features like Peek and Hover. Next to CyanogenMod it seems like PA is king in the custom ROM scene. Unfortunately, the team only supports a small range of devices (Google Nexus & Oppo, OnePlusOne). There are, however, so-called Legacy versions available which support other devices.
ParanoidAndroid Features
Floating notifications & multitasking
Hidden Navigation PIE mode
UI customization
Gesture controls
CyanogenMod themes support
I was running PA on my Nexus devices and really loved it. It’s stable, fast and battery life is great. I can highly recommend this ROM.
Latest ParanoidAndroid Version
The latest PA version is based on Android 5.0 Lollipop. PA usually works with nightly version that are quite stable and frequently updated. Unfortunately it has not been updated to Marshmallow yet. It also seems like the official version for Oppo devices is maintained more frequently than the legacy versions.
ParanoidAndroid Availability
An overview of officially supported Google Nexus, OnePlusOne and Oppo devices can be found here. Legacy devices are listed here.
Device-specific custom ROMs
The custom ROM scene developed itself into a certain direction in the last year, especially with stock ROMs including more and more features. As device manufacturers often don’t publish official drivers, custom ROMs like CyanogenMod are not able to support all features. Because of this, custom ROMs are often developing in a direction of adapting ads to devices. Because of this, I cannot give you great recommendation for all devices. I would personally suggest to either go with the big players like CyanogenMod or look for a popular specific ROM for your device. The XDA Developers forums should do the trick for that.
Flashing Custom Kernels
Kernels are the brain of your Android device and communicate between software and hardware. Therefore, they are responsible for managing things like CPU / GPU clocking speed, screen sensitivity / colors or voltage. By using a custom kernel you can not only improve battery life, but also increase system performance.
Many custom ROMs already come with their own kernels. This is done to implement software communication of the custom ROM with the hardware of the device and also to ensure a better performance. Nevertheless, you are often also able to flash custom kernels to custom ROMs. If you decided to stick to a rooted version of stock Android, flashing a new kernel can offer you additional performance with the convenience of a stock OS. Unfortunately, there are no “big” kernel releases that work for multiple devices and it’s hard for me to give any suggestions here. I would suggest to check the dedicated XDA-Developers forum for your device
After downloading the custom kernel, you usually have to reboot to recovery and flash it from there. That’s it! Always make sure to check compatibility of the kernel with your ROM and device, because flashing a wrong kernel can brick your phone!
Apps
Rooting your Android device will offer you many benefits. Besides the features mentioned above, you can also install great apps that require to go deep into the system. Using them with an un-rooted device is not possible. Below I’ve listed a few apps that I like and use on an everyday basis. Feel free to share other apps in the comments section below!
Titanium Backup
Titanium Backup is a great backup tool for Android devices that offers tons of features. It provides the possibility to backup your data, settings and apps. Scheduled backups are also available. The paid pro version offers lots of great features like syncing backups with cloud-based storage providers such as Dropbox, Google Drive or Box. In my opinion this is one of the best root apps and a must-get. Especially if you’re a flash-a-holic, performing and restoring quick backups of all your apps (incl. settings and save games) is really easy and convenient with Titanium Backup.
ROM Manager
When you constantly switch between custom ROMs, ClockworkMod’s ROM Manager is one of the essential apps to get. Besides flashing ClockworkMod recovery, it will help you to organise and install your custom ROMs and backing-up your Android device. The paid premium version includes additional features like automatic backups, web connect and incremental ROM downloads.
AdAway
I struggled a little bit when deciding to either include AdAway or not, because it’s great for users but bad for app publishers and marketers. Google removed it from Google Play but you can still get it on the AdAway website. Like AdBlock Plus on your computer, the app modifies your Android devices hosts file to prevent apps and browsers to display advertisements. This will not only improve your app usage experience, but also increase battery life and decrease mobile traffic. Be fair and purchase paid versions of apps or donate a small amount to developers to make sure they will keep on programming great apps!
Google has recently begun to remove certain apps that violate their distribution agreements from Google Play. If you’re still interested in installing AdAway, please refer to the AdAway website.
Xposed Framework
Xposed Framework is a great app that offers the possibility to add features to your Android devices without flashing a custom ROM (or in addition to it). You’re able to install modules which offer visual customisation or battery improvements, amongst others.
Greenify
Greenify is a great app to improve battery life and system performance because it puts selected apps in hibernation mode. Not having tons of apps stored in RAM or running as system processes will make your Android device faster and increase your user experience. Please refer to full review for more information.
Frequently Asked Rooting Questions
1. How can I restore stock Android?
To get back stock Android, simply flash a stock ROM suitable for your device. This way you’ll get an unrooted, stock Android version with restored warranty.
2. What happens to my settings, contacts and apps when I install a custom ROM?
It’s always recommended to wipe your device before installing a custom ROM for the first time. If your Google account is linked to your phone, contacts, emails and apps will automatically be downloaded after launching the custom ROM and logging in to your Google account. You can backup your settings with apps like XYZ.
3. How can I upgrade a custom ROM?
Most custom ROMs offer a update function, some directly integrated to the OS, others using a specific app. You can also use ROM Manager to update certain custom ROMs.
4. Is it possible to just root a phone and not install a custom ROM?
Yes, simply use a stock ROM and root it. If you update it, your root-access will be gone, though.
5. Do I need to go step-by-step to upgrade my Android device or can I directly go to the latest version available?
You can usually simply flash the latest ROM and are good to go. Custom ROM updates usually come in a full package, meaning that you have to download the complete ROM to update it. The downloads are usually about 100-200 MB.
6. Is there a special order to flash a ROM or kernel?
I would suggest flashing the ROM first as they often include their own custom kernels. Afterwards, boot your phone with the custom ROM, go back to the recovery mode and flash the kernel. Also make sure to check whether your custom kernel is supported by the ROM.
7. Can I update or change certain parts of Android without flashing a ROM?
Not in terms of getting a newer Android version. However, you should have a look at Xposed Framework as it brings many custom ROM features to your Android installation.
8. Do I have to downgrade my phone to flash ROM XYZ?
No – as long as your bootloader is unlocked and you have a custom recovery installed. With some devices, you need to downgrade to be able to do that. Custom ROMs usually don’t require a certain Android version because everything OS-wise is overwritten anyways.
9. Is there a custom ROM for my phone / tablet?
I would recommend to head over to the XDA developers forums and perform a search query there. If you’re using one of the popular devices there are usually many custom ROMs available. You can always check out Xposed Framework to add some more features to your Android device if no custom ROM is available.
Final Words
Do you have any questions about the rooting process, custom ROMs, tweaks or apps? Do you maybe want to share other great apps that I might have forgotten? Feel free to do so in the comments below!

I am interested in rooting my android but do not know how to begin and how to identify my LG

how to know whether the recovery image in working or not without flashing on android
how can i create a virtual android environment that mimics my android kernel and os .So that i can flash recovery on virtual android without damaging my physical device........plesae help me .i am new to this :crying::crying:

sai2698 said:
how can i create a virtual android environment that mimics my android kernel and os .So that i can flash recovery on virtual android without damaging my physical device........plesae help me .i am new to this :crying::crying:
Click to expand...
Click to collapse
you can use virtual box on PC
just get a tutorial on internet

monterlarge said:
I am interested in rooting my android but do not know how to begin and how to identify my LG
Click to expand...
Click to collapse
just google your device and search for the compatible ROM
EASY PEASY

sai2698 said:
how can i create a virtual android environment that mimics my android kernel and os .So that i can flash recovery on virtual android without damaging my physical device........plesae help me .i am new to this :crying::crying:
Click to expand...
Click to collapse
Use virtual box

[ROM] iPioneer Slim 10c v0.1 for LGV521 - Rooted, busybox, init.d, debloated, etc...

ROM Ipioneer Slim 10c v0.1
A light, clean & faster rom!!!
Disclaimer:
/***
* Your warranty is now void (and I'm sure it was void before this process).
* I am not responsible for hard or soft bricked devices, boot loops, dead or corrupt sd cards, strange behavior or you getting a heart attack 'cuz your youtube app is not working properly.
* YOU and only YOU are choosing to make these modifications, do not blame on me.... I will just ignore you.
***/
iPioneer Slim 10c v0.1 is a light, clean and fast custom rom designed for the Lg G Pad X 8.0 (T-Mobile variant only) and it's aim is to become a replacement for the default system of this device.
iPioneer Slim 10c v0.1 it is light because it only takes 519.8Mb of disk space which is a big difference when you compare the 1.2Gb of a stock rom, it is clean because it only contains the essential apps to make it work properly and it is faster because the whole system have been 100% optimized.
iPioneer it have been designed with the User Freedom in mind, it only provides you with the basic OS so you can do what you need to do on top of that.
Features:
Based on stock (10c)
Rooted
Busyboxed
Init.d Support
Extremely debloated (very serious)
Deodexed
Zipaligned
Nova as default launcher
Installation instructions:
Download the rom to your desire location (link to download to the end of this post).
Boot into Twrp recovery and do a standard wipe (factory reset).
Install the downloaded rom .zip.
Reboot the device.
Be patient, is going to take more time than a regular stock rom to boot into the system, at first is going to be stuck at T-Mobile logo but after few seconds is going to enter into App Optimization mode and after that you will be able to setup your system.
Enjoy it.
First things to do after you install this rom:
Add your google account (if you didn't complete that step at the first setup).
Download your favorite app manager (Rom Toolbox, Titanium, etc.).
Freeze the application called App Updates in order to stop the system update beacon for OTA. I removed 3 core apps in order to stop OTAs but it seems to be very integrated with the system, there is no way I can remove it from the rom without breaking the system. This is the most practical way to my knowledge right now.
Optionals things to do after you install this rom:
You can uninstall Nova Launcher if you want as is not part of the system apps, but before you need to install your favorite launcher. If you don't install another launcher and remove Nova you will have a broken system and most likely you'll have to re-flash the rom.
On purpose bugs and missing options:
On purpose bugs are bugs that comes when you remove a functionality from the system but it can not be removed from a third party component, example: LG VPN app it has been removed but the options remains in the Settings of the device and when you tap that option you will provoke a crash event, the way to resolve this is to decode the third party component (very difficult) or reinstall the missing part (in this case the LG VPN app).
iPioneer Slim 0.1 it comes without some apps that can not be removed from the system setting options, this is like that because I believe that these apps are not necessary for all people, if someone need them they can be downloaded/replaced from the Play Store or I will provide a flashable file with these apps so you can install them.
On Purpose bugs (located at settings):
From the Share & Connect menu:
File Sharing that contains BLE and Android Beam doesn't work, package SmartShare it has been removed.
Media Server (DLNA) doesn't work, package SmartShare that also contains SmartShare.MediaServer it has been removed.
Lg Airdrive doesn't work, package LGAirDrive & LGAirDriveSettings were removed.
From More>VPN menu:
LG VPN doesn't work, package VpnClient_LG it has been removed. Basic VPN it works.
From Display menu:
Home screen doesn't work, packages LGHome, HomeSelector, LGHome_Theme_Optimus, com.lge.launcher3, com.lge.launcher2.theme.optimus were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.​
Missing options (located at settings):
Smart Cleaning not present, package LGSpringCleaning it has been removed.
Cloud (cloud integration in settings) not present, package CloudHub (maybe dependant on SmartShare package) it has been removed, please also note that this cloud integration it was integrated on the stock File Manager, so... if you want a full integration of the Cloud service on settings maybe you will have to install the stock File Manager provided by LGFileManager package.
From Backup & reset menu:
LG Backup is not present, packages LGBackupLauncher and LGBackup were removed.
From About tablet menu:
Update Center and its content (App updates & System updates) is not present, packages com.lge.appbox.client (app updates), com.lge.updatecenter & LGUpdateCenter (main menu for updates) were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.​Flashable zip with system apps:
Coming soon when I have a free time.
What to do if you get the OTA notification:
Freeze the app called App Updates with your favorite app manager.
With your favorite file manager go to /cache and delete the update.zip (the downloaded ota).
Tap on Restart & Install button on OTA pop-up, the pop-up it will start counting to 0 in order to restart but your device won't restart because there are 3 core apps removed from this rom plus 1 app that you just disabled (all these 4 app controls the OTA), the notification is just gonna disappear, push recent button and clear the ota pop-up window.
Bugs Report:
If you find a bug in this rom just notify me about that in this thread, please, just use the title as "Bug Report" so I can pay close attention to that, my time is very limited. Thank you.
Feature Request:
If you want a feature to be added into future revisions of this rom just notify me about that in this thread, please, just use the title as "Feature Request" so I can pay close attention to that, my time is very limited. Thank you.
More info:
-------------------------------------
Device: Lg G Pad X 8.0
Model: LGV521
Code Name: b3
Carrier: T-Mobile
Android version: 6.0.1
Security patch level: 2016-07-01
Software version: V52110c
Link: https://www.androidfilehost.com/?fid=385035244224403624

Screenshots:
Default View: (sorry guys, I was not able fix Nova in order to show an organized and clean layout by default).
Default App Drawer: remember this is an extremely debloated rom, only the most basic core apps remains.
Settings view, yes some options are not present, read above about this.
Software info.

Reserved 2...

For some reason this post doesn't show up on ET page: lg-g-padx
Too bad, a lot of people won't be able to see this rom, but I can do nothing.
If someone knows an admin who can fix this issue please make mention of this post to him. I would do it but I don't have the time to.
Thank you.

Some screenshots added on post #2...

How fast does it run compared to the stock rom?

Munns86 said:
How fast does it run compared to the stock rom?
Click to expand...
Click to collapse
How fast it can go is a subjective matter:
It will depend on hardware lifetime span (how you use it and how other people use this tablet).
It will depend how much apps and content you put in it (the more things you download the more slow android is gonna be, this is kind a Swap area).
I did not do a benchmark, when I declared that is faster than a stock rom is because that speed response enhacement it comes based on the Deodex and Zipalign process. It can be or maybe not noticeable to your eyes but based on deodex and zipalign process is for sure that is faster than an odex and not-zipaligned rom.
The best answer is that you need to try it on your own and see the difference.
Sent from my LG-H918 using Tapatalk

Poll added at the beginning (not visible in tapatalk or xda app).
Please only select the apps that you really need or you really think that should comes with the next revision of iPioneer Slim rom.
This will help me to build a better version with features that users needs.

C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!

xtremelora said:
C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!
Click to expand...
Click to collapse
The reason is that the xda app can't see the vote going on.
Personally, I will be excited to see a cm/aosp custom build, which will sure draw much more attention.

googlephone said:
The reason is that the xda app can't see the vote going on.
Click to expand...
Click to collapse
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...

xtremelora said:
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...
Click to expand...
Click to collapse
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.

googlephone said:
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.
Click to expand...
Click to collapse
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.

xtremelora said:
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.
Click to expand...
Click to collapse
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.

Munns86 said:
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.
Click to expand...
Click to collapse
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.

xtremelora said:
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.
Click to expand...
Click to collapse
There is already a TWRP recovery for v521. Why you need to compile cm recovery?

googlephone said:
There is already a TWRP recovery for v521. Why you need to compile cm recovery?
Click to expand...
Click to collapse
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk

xtremelora said:
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.

shabbypenguin said:
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.
Click to expand...
Click to collapse
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.

xtremelora said:
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.
Click to expand...
Click to collapse
i built it from scratch, id be careful looking too much at the v500, it's a snapdragon 600 SOC which is very old and is a quad core. the 615 in the g pad x is octacore and much newer. even the ramdisk is going to have big differences in how its handled.

[Symbit] A tool to help with rooting and updating of Android devices

I've just finished building a small tool called symbit which helps with rooting and updating of existing rooted devices. With Android 10, some TWRP versions have not been updated to support the new /system partition format and do not work for those devices. This tool aims to solve the issue by making it easier to root and update existing rooted Android devices.
Source code
About
Install
My original motivation to create this was when my friend asked me for help updating his Pixel 3 XL. Due to the fact that TWRP does not support Android 10 on the Pixel, I had to tell him to use the manual updating method which involved typing many commands to update the system and patching the boot.img file via Magisk. I decided then to create this small utility to help him and (hopefully) someone else who may have difficulties rooting/updating their rooted device.
Please give me feedback on what I should improve on. I plan to support more devices soon.

[GUIDE] How to install Android 10 (Q) eOS GSI custom build

My Moto G6 is not my daily driver anymore so I thought I'd try to install e/os on it. My sole purpose for doing this is to get a feel for the interface and overall functionalities with an ecloud account. Would not be fair to comment on performance as it's a generic 32bits build image.
The Moto G6 is not officially supported by e/os and there are no specific custom builds for this phone (yet) so I used an existing GSI posted on their website.
What you need:
#1. VERY IMPORTANT - Pie Stock ROM needed as it requires some 32bits code to work. I reflashed PPSS29.55-37-7-10 found here​#2. Download latest twrp (twrp-3.6.0_9-0-ali.img) here​#3. Download e/os image partition A only (treble check) / 32 bits only from here and unpack the img file​#4. Download Disable_Dm-Verity_ForceEncrypt_04.03.19.zip here - not sure it's really needed. I'm using this version because I had it saved. I assume that a newer one should work.​#5. Put all the files onto a sd card​#6. (Optional) Create an ecloud account at https://e.foundation/ecloud/​
I followed these steps:
#7. Boot and flash TWRP​#8. Format /data​#9. Install system.img into system partition​#10. Flash Disable_Dm-Verity_ForceEncrypt​#11. Reboot​
A few more links for reference:
https://e.foundation/e-os/​https://community.e.foundation/t/custom-build-android-10-q-eos-gsi/19626/143​https://play.google.com/store/apps/details?id=com.kevintresuelo.treble​

First impressions are good:
- Minimal image, nearly no clutter.​- Seems to work as expected and having the ecloud account is nice for syncing contacts amongst other things.​- I don't really like the desktop theme which is very similar to another phone OS but that's a personal thing. I need to look at other themes / icons.​- I have no SIM in the phone so no idea about call quality etc...​- Not tried rooting it yet for examples.​
I'm at the very early stages playing with it. If anybody has any tips please share

Sadly, still in 2023 no official support for the G6 (ALI) from /e/os, even though it was been request several times in the forums.
Is there such a big difference hardware-wise that making a port from G6 plus is too complicated or time-consuming?

Question AOSP rom for S22U Snapdragon ?

Hello
I will perhaps keep my S22U instead of upgrading to s23u , I will then most probably root it as my warranty will soon come to an end and I won't care about knox flag. But is there any AOSP based custom rom for the S22U snapdragon ? If yes can you use Expert Raw app?

The S22 should be capable of running Generic System Images, so if you would like to try running actual AOSP, check out my guide here. Nothing is customized as these are directly from AOSP, but that also means they have zero bloat.

V0latyle said:
The S22 should be capable of running Generic System Images, so if you would like to try running actual AOSP, check out my guide here. Nothing is customized as these are directly from AOSP, but that also means they have zero bloat.
Click to expand...
Click to collapse
Thanks
Though it looks like an update thread for Pixel phones no?

vegetaleb said:
Thanks
Though it looks like an update thread for Pixel phones no?
Click to expand...
Click to collapse
I made a mistake with the link, here's the correct one:
[GUIDE] How To: Install AOSP GSI on Samsung Devices **NOT FOR BEGINNERS**
For those of you who want the AOSP experience, here is how to install generic Android system images. This -should- work on any Samsung device for which TWRP is available. A GSI is only a system image and does not include the kernel. You can use...
forum.xda-developers.com

V0latyle said:
I made a mistake with the link, here's the correct one:
[GUIDE] How To: Install AOSP GSI on Samsung Devices **NOT FOR BEGINNERS**
For those of you who want the AOSP experience, here is how to install generic Android system images. This -should- work on any Samsung device for which TWRP is available. A GSI is only a system image and does not include the kernel. You can use...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks
Do you get the new AI stuff that are in the Pixel 7 Pro ?

vegetaleb said:
Thanks
Do you get the new AI stuff that are in the Pixel 7 Pro ?
Click to expand...
Click to collapse
I don't think so - I'm pretty sure features like that are not core Android mechanics, so they wouldn't be included in AOSP. I don't know for sure. Keep in mind that the whole idea behind a GSI - Generic System Image - is that it can run on pretty much any device. Google has been using this model since the Pixel 3 - instead of having different system builds for each device, they use a generic common system image, while device specific features are contained in other partitions such as /product. This way, when they provide the monthly update for Pixels, they don't have to completely rebuild the firmware; they can just use the AOSP GSI for the "core", and any device specific changes are separate in /system_ext and /product. It's a modular design that really helps streamline the update process; it also means that devices that no longer receive updates can still potentially run the latest AOSP core.
I imagine you could extract the product.img from the Pixel 7 factory zip and flash it to /product on your device, but because it's device specific, it most likely wouldn't work properly.