Database Develop

Aosp kitkat rom with gesture for gionee m2

This rom is a free, community built, aftermarket firmware distribution of Android 4.4 (KK), which is designed to increase performance and reliability over stock Android for your device. 100% stable ROM with no any bug​
ROM FEATURES-
Based on latest KK and it's almost bugfree
Good Battery Life..........better than stock
Themed all icons to beautiful AOSP
Fully deodexed /app, /priv-app, /framework for faster apps opening speed
Gesture working
[U]---BUGS---[/U]
1. Show Phone Memory as SD-Card, SD-Card as Phone Memory..... but this not cause any problem in working. Others no any Bugs........if you found please let me know......
---FIXES---
1. Storage fix http://d-h.st/DgR
2. Network, GPS, Compass fix http://d-h.st/qy8
3. Launcher with Motion & Gesture Support http://d-h.st/hg6
4. BOOTIMG for 8GB users http://d-h.st/aU9
All fixes flashable through CTR/CWM...........Cache & Dalvik Cache cleaning is recomended.
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
First time installing to your GIONEE M2, or coming from another ROM:
- Make sure you're running a proper working CWM or CTR.
- Copy ZIPs to your SDCard
- Boot into Recovery
-Wipe all Data(System, Data, Cache, Dalvik Cache for wipe menu::::THIS STEP IS NECCESSARY)
- Flash zip from SDCard
- Reboot
DOWNLOAD SECTION
https://docs.google.com/uc?id=0B3s_rEgYp08YZ3pLZnFrTmNFU2s&export=download
New link:- single zip with all bug fixed. Thanks to Geo & Abizz for fixing all bug and uploading.
http://www.mediafire.com/download/q696695dcy60b9v/aosp_gesture_gioneem2_fullwrkng.zip. If you are downloading from this link then no need to download any fixes.
About KITKAT ROM 4.4.2:
ROM OS Version: 4.4.2 KITKAT
ROM Kernel: Linux 3.4.67
Based On: AOSP KITKAT
Version Information
Status: 100% Stable
SCREENSHOTS

Thanks for the update and your awesome work. Kindly upload this and other files to mediafire site or any other one. Am finding it difficult to download from Google Drive links
---------- Post added at 05:00 AM ---------- Previous post was at 04:56 AM ----------
Please do provide screenshots

Here's what am facing while trying to download it

paeffiong said:
Here's what am facing while trying to download it
Click to expand...
Click to collapse
Use desktop mode in ucweb.
---------- Post added at 06:35 AM ---------- Previous post was at 06:32 AM ----------

Restore applications from titanium backup not showing up, while it is working normally in cleankat rom, i m using titanium version 6.1.5.5

how to remove G symbolbefore each network bar
how to remove G symbolbefore each network bar , it takes space and looks ugly too

rakesh61 said:
how to remove G symbolbefore each network bar , it takes space and looks ugly too
Click to expand...
Click to collapse
You can install Gravity BOX and Xposed framework to your phone. Once installed open up gravity box, then go to display tweaks and there you can modify all settings. Hope this helps !:good:
LInk to download Xpose : http://repo.xposed.info/module/de.robv.android.xposed.installer
Just make sure you dont use ART, Xposed will not work with ART.

Titanium backup working before flashing storage swap zip, ;after flashing storage swap zip file it does not show any fies in restore file option. i M using titanium backup without flashing storage swap file. Using this rom for 2 days, indeed a very good rom, good job sir

Gallery application force closed sometimes

Cant stop the error pop up... This is bad. The zips dosnt work.. I tried putting in zip by modifying manually... Almost 6 hours now...

drdeepakpatel said:
Restore applications from titanium backup not showing up, while it is working normally in cleankat rom, i m using titanium version 6.1.5.5
Click to expand...
Click to collapse
root your device properly .
if problem persists , go to preferences -> back location->scan->select current location.
drdeepakpatel said:
Titanium backup working before flashing storage swap zip, ;after flashing storage swap zip file it does not show any fies in restore file option. i M using titanium backup without flashing storage swap file. Using this rom for 2 days, indeed a very good rom, good job sir
Click to expand...
Click to collapse
set default write disk as sd card in system settings.
go to preferences -> back location->scan->select current location.

thanks

finance.resat said:
Cant stop the error pop up... This is bad. The zips dosnt work.. I tried putting in zip by modifying manually... Almost 6 hours now...
Click to expand...
Click to collapse
...don't understand what are you talking about. No one faced any errors in zip files.
try downloading again with good internet speed.
thanks

HI
After installing the storage fix zip, my SD card is no longer writable, have tried the <media r/W> tweak but didnt help... Any body faced such an issue with this ROM ?

anilyarki, no body faced any problem like this. Have you changed default write disk in storage setting. Try clearing cache and dalvik cache from recovery.

can u port those android one stock roms
can u port those android one stock roms
that would be very nice
in your rom i have a problem some apps are incompatible like the hdfc bank in play store it says incompatible with ur device many such apps also reprt this problem , any fix please

Im constantly getting pop-up error like android.process.media has stopped. Tried everything but it still shows up.
Please help.

anisharsenal said:
Im constantly getting pop-up error like android.process.media has stopped. Tried everything but it still shows up.
Please help.
Click to expand...
Click to collapse
clear cache, dalvik cache from recovery.

this rom does not work in my device.. just waste of time... may be my device is faulty...

finance.resat said:
this rom does not work in my device.. just waste of time... may be my device is faulty...
Click to expand...
Click to collapse
Working fine with all M2 version (4gb & 8gb)
Reflash the ROM
1.reboot to ctr recovery
2.backup current ROM
3.preflash wipe (from wipe menu)
4.install ROM zip

[Recovery]Twrp v3 for Galaxy J700T/T1

Twrp Recovery v3 For Samsung Galaxy J7 (SM-J700T/T1) Variants​This recovery is ported from j700f/h twrp recovery , my kernel and stock dt images were included to get it to work
Code:
*** Disclamer
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
Warning : if it didn't work for you , you should use my kernel to get it to work
HTML:
http://forum.xda-developers.com/galaxy-j7/j700t-development/kernel-mina-kernel-v1-j700t-t3427446
How to flash [no need to have root] :
Code:
* Download the odin format recovery zip *
* Extract it *
* Enable oem unlock in the developer options *
* Enter download mode *
* Flash the extracted [recovery.tar.md5] file using odin *
* Enjoy *
-if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
-If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
HTML:
https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
-If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
HTML:
https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt.zip
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP
-Source
HTML:
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
Click to expand...
Click to collapse
Downloads :
twrp v3 image format
https://www.mediafire.com/download/ehygrybdq7a2j8e
twrp v3 odin format [extract zip then flash (recovery.tar.md5) using odin]
https://www.mediafire.com/download/4f5sz13cz5gy466
Thanks to my testers:
@OriginalShinken1 @!Led*Eyes!
Please Conider donating if you appreciate my work, Ty :highfive:
Paypal donation link: https://paypal.me/messi2050

Thanks again for your work here.
Bring on the ROMS!!!!!!
That was just out loud in general.....not aimed anywhere in particular.
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
@messi2050
This also works for J700T (T-Mobile). May need to add to op.
-sent from this device using this app.

OriginalShinken1 said:
Thanks again for your work here.
Bring on the ROMS!!!!!!
That was just out loud in general.....not aimed anywhere in particular.
---------- Post added at 09:43 PM ---------- Previous post was at 09:32 PM ----------
@messi2050
This also works for J700T (T-Mobile). May need to add to op.
-sent from this device using this app.
Click to expand...
Click to collapse
You are welcome , ok ty i will add it

Only because this isn't obviously stated:
TWRP does see your external sd card. That being said, those of you who are already rooted can download these files (su and twrp fix zip) to your external sd card. Also use titanium backup for your apps and save to that same sd card. When you format storage, you can install fix and su from the untouched sd card. Once you're booted and set up, use titanium backup to restore your apps.
-sent from this device using this app.

After using flashify to install your kernal, flashify says that i do not have root and cant flash twrp. What do i do from here?

SallySalad said:
After using flashify to install your kernal, flashify says that i do not have root and cant flash twrp. What do i do from here?
Click to expand...
Click to collapse
I'm gonna make an odin flashable twrp so you can flash it directly with odin

SallySalad said:
After using flashify to install your kernal, flashify says that i do not have root and cant flash twrp. What do i do from here?
Click to expand...
Click to collapse
odin flashable file added but it's not tested yet please test and report here

messi2050 said:
odin flashable file added but it's not tested yet please test and report here
Click to expand...
Click to collapse
thank you so much it works in odin

brandonlee96 said:
thank you so much it works in odin
Click to expand...
Click to collapse
I'm Happy to know that it worked for you , thank u for reporting

I put it under AP on Odin, yeah? Sorry about all of this still trying to learn.

messi2050 said:
I'm Happy to know that it worked for you , thank u for reporting
Click to expand...
Click to collapse
is there any way to get rid of the red text about the kernal and the recovery on boot up?
just wondering

brandonlee96 said:
is there any way to get rid of the red text about the kernal and the recovery on boot up?
just wondering
Click to expand...
Click to collapse
No it also appear on j700h/f/m ,it reports the selinux status

messi2050 said:
No it also appear on j700h/f/m ,it reports the selinux status
Click to expand...
Click to collapse
im sorry to bother you. but how exactly can i access the internal storage in TWRP recovery. i did what you said above but it seems like it doesn't work on the next restart to recovery?

TWRP_Internal_Access
brandonlee96 said:
im sorry to bother you. but how exactly can i access the internal storage in TWRP recovery. i did what you said above but it seems like it doesn't work on the next restart to recovery?
Click to expand...
Click to collapse
--So you flashed the Mina kernel image
--booted into Download mode
--Flashed the TWRP.tar via ODIN
--Booted into TWRP
-- Choose WIPE --> Format DATA --> type YES
-- Go back to HOME screen in TWRP and select REBOOT -----> RECOVERY
I was able to access the internal storage in TWRP at this point. You can check it by going to Install ---> Select Storage ---> Internal Storage.
EDIT: Do you mean how can you copy the zip files to the Internal Storage while still inside of TWRP?

brandonlee96 said:
im sorry to bother you. but how exactly can i access the internal storage in TWRP recovery. i did what you said above but it seems like it doesn't work on the next restart to recovery?
Click to expand...
Click to collapse
check this thread
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770

Working great for me, on the J700T just a few questions what are the new icons in the bar one looks like the Carolina Hurricanes logo and the other says Vo))LTE?
---------- Post added at 10:46 AM ---------- Previous post was at 10:05 AM ----------
Im sorry but one last stupid question is the J700T ARM or ARM64?

Why is it that i still can't make a nandroid backup with this twrp i flashed everything and i am still rooted.

Krumplife4400 said:
Why is it that i still can't make a nandroid backup with this twrp i flashed everything and i am still rooted.
Click to expand...
Click to collapse
those are new samsung restrictions and security , i can't do anything towards it , this restriction is found on s7 too , check this thread and u will understand
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770

O ok i see now... Is there anyway to get xposed framework to work on this phone?

messi2050 said:
I'm Happy to know that it worked for you , thank u for reporting
Click to expand...
Click to collapse
Testing now. Thank u. I love u for this mate

[CLOSED]TWRP 3.3.1-1 for Pixel 3A XL [OFFICIAL]

Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
[I]#include <std_disclaimer.h>
/*
* Your warranty is not void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/[/I]
Note: Please be aware that you cannot install this without a kernel with LZMA compression support, I believe most ROMs have included my commit for this so you should be good for all custom ROMs and kernels. If not please file a request to the maintainer.
In addition, please be aware that TWRP is currently not compatible with Android 10. If you would like to use TWRP you will need to go back to Android 9. If you would like more information you can read at the link here.
Not a huge problem, stock users can just temporarily boot TWRP if you have access to a PC.
Not compatible with Android Q.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to transfer the zip onto your device.
Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Changelog:
[BETA]
3.3.1-0: Initial release for Pixel 3A XL devices
3.3.1-1: Fixed having to manually change slots before rebooting.
3.3.1-2: Updated to July blobs!
3.3.1-3: Can now install TWRP to boot image. ADB, MTP, LOGD, Repack Tools and Logcat have all been removed to save the necessary space for this to work. You can grab stuff while in the OS, then flash it in TWRP (Keep in mind I have only tested this on stock as of now, feel free to test it on whatever ROM you use. It should work, but let me know if it doesn't).
3.3.1-4: Changed back to LZMA compression, also added back all the features besides ADB/Logcat. As long as your kernel supports LZMA you will be able to take advantage of installing it permanently without having to worry about space restrictions.
3.3.1-5:
Add persist entry to fstab
* To allow TWRP to store a backup settings file on /persist
and also to be used as QCOM time fix source during early boot.
Revert "Don't include logcat."
Revert "Don't include repack tools."
3.3.1-6:
Revert "Revert "Don't include repack tools.""
Add haptics firmware.
* This obviously on it's own isn't enough to get haptics working for the 3A in TWRP, but its a start.
Don't include a precompiled update_engine_sideload
* This should fix the issue of flashing officials for StatiXOS
[STABLE]
3.3.1-0: Initial official release!
Download:
https://twrp.me/google/googlepixel3axl.html
XDA:DevDB Information
TWRP, Tool/Utility for the Google Pixel 3a XL
Contributors
ZVNexus, janjan
Source Code: https://github.com/TeamWin/android_device_google_bonito
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-07-17
Current Beta Version: 3.3.1-6
Beta Release Date: 2019-06-27
Created 2019-06-27
Last Updated 2019-11-15

Reserved

Awesome! Thank you so much!
So as of this moment, there is only the ability to boot to twrp via fastboot?

DriveEuro said:
Awesome! Thank you so much!
So as of this moment, there is only the ability to boot to twrp via fastboot?
Click to expand...
Click to collapse
Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.

So does anyone know if TWRP + Magisk work on Android Q for root?

ZVNexus said:
Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.
Click to expand...
Click to collapse
I don't mind, I haven't flashed TWRP to a device since Treble came out, but it's easy enough to boot an image, so at least for my usage case, this is all I need

otg mounting problem
ZVNexus said:
Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.
Click to expand...
Click to collapse
no you shouldn't have waited!! thanks a lot specially from all of us checking if twrp came out every day!
hey maybe you can give me a tip since i have a problem mounting otg:
when i boot twrp image if i go to backup/select storage i find a storage/usb partition (0MB)
when i connect otg (and go to mount) it becomes storage/usbotg 1 (12000MB)
but the problem is that if i click it doesn’t remain selected, and the log reports “Unable to find partition for the path ‘/storage’ ”
if i go to mount or backup/select storage and click usbotg 1 storage it doesn’t remain selected and the log reports “E: unable to locate partition for ‘/storage/usbotg-1’ ”
(i’ve tried also with different keys but i don't think it's the point anyway the 1st was an 256GB usb/SD and the 2nd a 16GB usbkey but logs reports same error)
any tip?

I'm on Q DP4. Anyone having luck flashing Magisk (canary)? In B slot it fails to mount system and vendor. I change to A slot. It completes. I reboot on A slot, I get stuck at Google starting logo and the phone never boots. If I attempt to boot B slot afterwards, it boots up fine, but I obviously don't have Magisk installed, verified with the Magisk APP.
Anyone have a clue?

Just to provide feedback.
Fastboot booted the image, it prompted for my pin, mounted system, and was able to backup properly, moved backup to computer.
Wiped the phone, reboot and went through setup, everything was working.
Back to twrp, adb pushed the backup to the phone, restored the backup and everything was functioning.
Also tested and was able to sideload flash Magisk.
So everything seems to be working as intended.
Thank you so much for your hard work!

My TWRP is NOT prompting for pin/pattern. That has to be part of this...
Wiped data via google recovery. The phone booted to Pie (i had previously did the OTA from Pie to Q beta 4). So now I'm back on Pie somehow (without reflashing). I booted to TWRP, installed Magisk successfully.
So overall, I'm not sure if this was related to Q beta 4 OTA occupying B slot while Pie still was on A slot.
Thanks to all for their work with TWRP!

Antonyo13 said:
Just to provide feedback.
Fastboot booted the image, it prompted for my pin, mounted system, and was able to backup properly, moved backup to computer.
Wiped the phone, reboot and went through setup, everything was working.
Back to twrp, adb pushed the backup to the phone, restored the backup and everything was functioning.
Also tested and was able to sideload flash Magisk.
So everything seems to be working as intended.
Thank you so much for your hard work!
Click to expand...
Click to collapse
On previous devices I have run into TWRP restore issues if I had a security PIN set on the device when I backed up. During your test did you have a PIN setup on the phone?

artiemon said:
On previous devices I have run into TWRP restore issues if I had a security PIN set on the device when I backed up. During your test did you have a PIN setup on the phone?
Click to expand...
Click to collapse
I had a pattern, not sure if it makes a difference between pattern and pin.
I will say the only thing weird i noticed was when i wiped the phone (the default wipe from twrp, not a full format of data from twrp), when i booted I was prompted for my pattern on first unlock before the device setup. Even though it was wiped.
But restoring was perfectly fine.

Antonyo13 said:
I will say the only thing weird i noticed was when i wiped the phone (the default wipe from twrp, not a full format of data from twrp), when i booted I was prompted for my pattern on first unlock before the device setup. Even though it was wiped.
But restoring was perfectly fine.
Click to expand...
Click to collapse
That is normal on pixels. If you factory reset in TWRP your password still stays

spaceman860 said:
That is normal on pixels. If you factory reset in TWRP your password still stays
Click to expand...
Click to collapse
Thank then everything is working great. No issues at all with TWRP

So just confirming - I am , I assume encrypted , as I have a PIN and a pattern with DU ROM. Can i safely backup the existing ROM and flash another and then be able to restore if need be using this version of TWRP?

jcrompton said:
So just confirming - I am , I assume encrypted , as I have a PIN and a pattern with DU ROM. Can i safely backup the existing ROM and flash another and then be able to restore if need be using this version of TWRP?
Click to expand...
Click to collapse
Yes. This is how it has worked in the past. Don't see why it wouldn't work like this currently. If you flash a different vendor image or system image, you'll want to revert back before you restore your old ROM backup.

DriveEuro said:
Yes. This is how it has worked in the past. Don't see why it wouldn't work like this currently. If you flash a different vendor image or system image, you'll want to revert back before you restore your old ROM backup.
Click to expand...
Click to collapse
Revert back to what? Sorry I don't understand?

Flash back the original vendor and system images.

GQJ said:
Revert back to what? Sorry I don't understand?
Click to expand...
Click to collapse
He was answering my question about hypothetical referring back to a prior rom from a backup

neshipda said:
no you shouldn't have waited!! thanks a lot specially from all of us checking if twrp came out every day!
hey maybe you can give me a tip since i have a problem mounting otg:
when i boot twrp image if i go to backup/select storage i find a storage/usb partition (0MB)
when i connect otg (and go to mount) it becomes storage/usbotg 1 (12000MB)
but the problem is that if i click it doesn’t remain selected, and the log reports “Unable to find partition for the path ‘/storage’ ”
if i go to mount or backup/select storage and click usbotg 1 storage it doesn’t remain selected and the log reports “E: unable to locate partition for ‘/storage/usbotg-1’ ”
(i’ve tried also with different keys but i don't think it's the point anyway the 1st was an 256GB usb/SD and the 2nd a 16GB usbkey but logs reports same error)
any tip?
Click to expand...
Click to collapse
I didn't test OTG before I uploaded, didn't have an OTG cable, but now that I know its a problem I'll look into it.

[OFFICIAL] [REBASED] [EMUI 5] TWRP 3.4.0 for P9 Lite 2016

What is TWRP?
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing, or rooting Android devices.
WARNING
Code:
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
Bugs:
On official build, MTP Name and Serial Number is broken (fixes already merged to src, working on hotfix build and rebase)
You tell me here or in Telegram Group
Download:
Official
Hotfix Build (reupload)
Rebase
Note: MTP Name on Rebase Build is set to "P9 Lite 2016" on all models. Don't worry, it's not a bug. I have to add libinit later.
Sources:
Device Tree (Official + Hotfix)
Kernel Source (Official)
Device Tree (Rebase)
Kernel Source (Rebase)
My other Works for P9 Lite:
Click me
Telegram Group for P9 Lite development:
Click me

sir

I have installed your fixed version and I can't mount internal memory to flash downloaded zip files

lionen said:
I have installed your fixed version and I can't mount internal memory to flash downloaded zip files
Click to expand...
Click to collapse
are you on emui?

GG2501YT said:
are you on emui?
Click to expand...
Click to collapse
Yes, I'm on stock b371

lionen said:
Yes, I'm on stock b371
Click to expand...
Click to collapse
try to format internal storage to ext4

GG2501YT said:
try to format internal storage to ext4
Click to expand...
Click to collapse
Don't write nonsense please.
P.S.: Data cannot be decrypted in TWRP 3.4.0-0.

-Alf- said:
Don't write nonsense please.
P.S.: Data cannot be decrypted in TWRP 3.4.0-0.
Click to expand...
Click to collapse
That ain't nonsense, since this worked for me just fine.
I formatted data in ext4 and everything worked and still works

TheTimeLord32 said:
That ain't nonsense, since this worked for me just fine.
I formatted data in ext4 and everything worked and still works
Click to expand...
Click to collapse
"internal storage" and "data" are two different things.

Works fine here! Good job dev

-Alf- said:
"internal storage" and "data" are two different things.
Click to expand...
Click to collapse
Yes but i did that on another huawei device and it worked there too.

GG2501YT said:
Yes but i did that on another huawei device and it worked there too.
Click to expand...
Click to collapse
In TWRP you can format data , wipe data, wipe internal storage, but it's impossible to FORMAT internal storage, I quote: " try to format internal storage to ext4" . Comprende? Peace!

GG2501YT said:
Rebase
Note: MTP Name on Rebase Build is set to "P9 Lite 2016" on all models. Don't worry, it's not a bug. I have to add libinit later.
Sources:
Device Tree (Rebase)
Kernel Source (Rebase)
My other Works for P9 Lite:
Click me
Telegram Group for P9 Lite development:
Click me
Update: I have rebased my TWRP for VNS. Would be nice if you can test it on all hi6250 devices supported. Report your bugs here or on my Telegram Group
Click to expand...
Click to collapse

Make any GSI work fully on the Xiaomi Redmi 8

Code:
/*
* Your warranty is now void lol.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this tutorial
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
You will need:
1. LineageOS 16 from this link:
[ROM][9.0.0][UNOFFICIAL] [redmi 8/olive LineageOS 16.0
my name is mohamed first of all sry am not good in making threads :D today am going to share my device tree from scratch including The Rom for lineage-16 am doing my best to get this phone stable as i could if you like my work send me thanks...
forum.xda-developers.com
2. LOLZ kernel from this link:
[KERNEL][4.9.229] LOLZ V10 [olive] [01/07/2020]
/* * Your warranty is now void lmao. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
3. TWRP (Not gonna show you where to get this, if you are on this forum you probably should have it.
4. And any GSI rom that is arm64 and uses the AB partition scheme.
And a basic sense of how rom flashing works
If you flash any GSI normally you will experience bugs such as Bluetooth audio not working and sensors not working.
Thats why I realized i could write the system partition from a GSI onto the lineageOS system partition, which is fully functional.
Result is a working GSI with all features (Not including voLTE, its useless).
I used Havoc OS android 11 GSI for this tutorial:
1. Wipe every partition on your phone, so thats Vendor System Data Cache and Internal storage.
2. Use a SD card or MTP over these files:
LineageOS 16.0 zip
LOLZ kernel zip
Magisk
And the GSI, but I personally MTP this at the last step.
And GAPPS for the GSI, if it doesnt have them built in.
3. Flash the lineageOS zip.
4. After its done flash magisk.
5. And last flash LOLZ kernel.
6. Reboot your device and wait for lineage to boot, once its done set it up until you are in the Pixel Launcher.
7. Reboot back into TWRP or any custom recovery.
8. Now if you haven't already MTP over the GSI and Gapps (if needed).
9. Flash the System partition from the GSI, DO NOT FORMAT ANY PARTITIONS UNTIL YOU DO THIS.
10. Resize the system partition if needed.
11. Install GAPPS.
And last but not least, step 12!
Format data!
Reboot into system and the rom should start booting. After its booted you are gonna set it up normally like you would any other rom. But this time the GSI has features like bluetooth, Gyroscope working and Automatic Brightness (a big issue on any GSI on this phone).
I hope you enjoyed using my tutorial

Forgot to mention that magisk WONT WORK on roms that use android 11!!
Its a limitation of android 11 and i cannot fix this.

Seems promising. Would try on weekend and cast vote.
Thanks for you efforts for community.

Realized once again that you dont even need to boot, just flash the lineageOS rom, then the GSI on top.

thank you very much its working the problem i always encounter is my bluetooth but now its working fine sorry for my bad english BTW i use havoc <3

I was in stock firmware 12.0.1 and I did the following.
1) Formated system, data, vendor and internal storage in twrp.
2) Flashed lineage 16
3) Flashed Magisk 20.4
4) Flashed loz kernel.
5) Reboot
Phone did not boot and was back to twrp. Tried twice and got the same result.
Do I need to flash other files like vbmeta, certification patch or permissive etc to make it work?

thanks, in the evening I will check and tell exactly what works and what does not work, probably all GSIs are giving me some problems (problem with brightness or bluetooth headphones)

Thank you for this guide. I installed havoc os 4.1 using this exact method wiped everything formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?

Thank you for this guide. I installed havoc os 4.1 using this exact method wiped every partition (I didn't wiped the USB OTG partition )formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?

Dragonnuu said:
Thank you for this guide. I installed havoc os 4.1 using this exact method wiped every partition (I didn't wiped the USB OTG partition )formated data flashed lineage and lolz kernel formated data , I flashed havoc on top without booting into lineage formated data again and voala everything is working smoothly as of now. I am curious tho why do we need to flash lolz is it necessary?
Click to expand...
Click to collapse
We need LOLZ because the lineage kernel gets carried over and its broken (Try booting lineage clear, you wont get far)

mwaseem851 said:
I was in stock firmware 12.0.1 and I did the following.
1) Formated system, data, vendor and internal storage in twrp.
2) Flashed lineage 16
3) Flashed Magisk 20.4
4) Flashed loz kernel.
5) Reboot
Phone did not boot and was back to twrp. Tried twice and got the same result.
Do I need to flash other files like vbmeta, certification patch or permissive etc to make it work?
Click to expand...
Click to collapse
Sorry for the late response, did you format data after installing?
Or did you even flash the GSI?
If so you might actually need the new vbmeta, if you do respond to this and i'll send it to you.

I have done lots of experimentation since last post and finally settled with Havoc OS 3.12 (all android 11 roms are still buggy).
Thanks.
boofiboi said:
Sorry for the late response, did you format data after installing?
Or did you even flash the GSI?
If so you might actually need the new vbmeta, if you do respond to this and i'll send it to you.
Click to expand...
Click to collapse

boofiboi said:
Code:
/*
* Your warranty is now void lol.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this tutorial
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
You will need:
1. LineageOS 16 from this link:
[ROM][9.0.0][UNOFFICIAL] [redmi 8/olive LineageOS 16.0
my name is mohamed first of all sry am not good in making threads :D today am going to share my device tree from scratch including The Rom for lineage-16 am doing my best to get this phone stable as i could if you like my work send me thanks...
forum.xda-developers.com
2. LOLZ kernel from this link:
[KERNEL][4.9.229] LOLZ V10 [olive] [01/07/2020]
/* * Your warranty is now void lmao. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
3. TWRP (Not gonna show you where to get this, if you are on this forum you probably should have it.
4. And any GSI rom that is arm64 and uses the AB partition scheme.
And a basic sense of how rom flashing works
If you flash any GSI normally you will experience bugs such as Bluetooth audio not working and sensors not working.
Thats why I realized i could write the system partition from a GSI onto the lineageOS system partition, which is fully functional.
Result is a working GSI with all features (Not including voLTE, its useless).
I used Havoc OS android 11 GSI for this tutorial:
1. Wipe every partition on your phone, so thats Vendor System Data Cache and Internal storage.
2. Use a SD card or MTP over these files:
LineageOS 16.0 zip
LOLZ kernel zip
Magisk
And the GSI, but I personally MTP this at the last step.
And GAPPS for the GSI, if it doesnt have them built in.
3. Flash the lineageOS zip.
4. After its done flash magisk.
5. And last flash LOLZ kernel.
6. Reboot your device and wait for lineage to boot, once its done set it up until you are in the Pixel Launcher.
7. Reboot back into TWRP or any custom recovery.
8. Now if you haven't already MTP over the GSI and Gapps (if needed).
9. Flash the System partition from the GSI, DO NOT FORMAT ANY PARTITIONS UNTIL YOU DO THIS.
10. Resize the system partition if needed.
11. Install GAPPS.
And last but not least, step 12!
Format data!
Reboot into system and the rom should start booting. After its booted you are gonna set it up normally like you would any other rom. But this time the GSI has features like bluetooth, Gyroscope working and Automatic Brightness (a big issue on any GSI on this phone).
I hope you enjoyed using my tutorial
Click to expand...
Click to collapse
Can you flash the AOSP beta GSIs from released on the Android website? For example the Android 12 Beta GSI?
I tried installing Android 12 on Redmi 8 but it did something perplexing.
TWRP said no OS was installed. Rebooting had the phone boot back into TWRP. I tried installing through both fastboot and TWRP. Installations were successful tho.