Related
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application: http://www.mfunz.com/en/developer-application, you can host your unofficial MoKee builds on our server!
Forum:http://bbs.mfunz.com
Guide:http://bbs.mfunz.com/thread-754544-1-1.html
Statistics:http://stats.mokeedev.com
Review:http://review.mfunz.com
Download:http://download.mokeedev.com
Github:https://github.com/MoKee
Bug Tracker:http://issues.mokeedev.com/
Credits:
Google, Qualcomm, Motorola, Samsung, Lge, TI, Nvidia, Intel, Sony,
CyanogenMod, Omnirom, Slim Roms, Koush for open-sourced SuperUser
Code:
* 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.
Found on Chinese MIUI forum.
->Download Link1<-
->Download Link2<-
LATEST VERSION 19-08-2015
Found on Chinese MIUI forum.
->Download Link<-
Not merged/Unmerged partition patch
->Download<-
Latest version 13-10-2015 can be found here:
http://www.miui.com/thread-3012343-1-1.html
Tested and works fine
for which layout type is this rom? I'm using the old one... with previous Mokee version...
New version found by the dev in Chinise Forum
I am installing this right now. Wait for Dropbox to Upload because baidu _____ and i want to help you download this faster
https://dl.dropboxusercontent.com/u/54386997/MK51.1-aries-201508181111-UNOFFICIAL.zip
NightHeron said:
New version found by the dev in Chinise Forum
I am installing this right now. Wait for Dropbox to Upload because baidu _____ and i want to help you download this faster
https://dl.dropboxusercontent.com/u/54386997/MK51.1-aries-201508181111-UNOFFICIAL.zip
Click to expand...
Click to collapse
Thanks but I already got a more recent version uploaded, see first post.
SWADED said:
Thanks but I already got a more recent version uploaded, see first post.
Click to expand...
Click to collapse
The patch is for merged partitions?Cause till now i think it was for not merged.
T3sla said:
The patch is for merged partitions?Cause till now i think it was for not merged.
Click to expand...
Click to collapse
It is for not merged, you are right.
already flash it on my mi 2s, awesome, thanks dude
Simple guide to update from not merged data-sdcard mokee official 4.4.4 to the last mokee unofficial 5.1.1 with merged partition 30/12/2015 update
1) optional - make a full nandroid backup in case anything went wrong
2)REPARTITION TO MERGED DATA
- download MIUI 5.9.2 fastboot package from official miui.com site or from here
- flash it via MiFlash, selecting "flash_all.bat" from advanced properties (the flash_all.bat is inside the miui 5.9.2 fastboot package)
-reboot from fastboot and wait (10 minutes more or less) until miui rom finally boot to the home screen
3)FLASH CUSTOM RECOVERY TWRP 2.8.7.0 FOR MERGED PARTITION
-use this guide (point 2) to flash TWRP via fastboot
4)FLASH MOKEE 5.1.1 ROM + GAPPS
-from twrp wipe data, system, caches -> flash MK51.1-aries-201511292011-UNOFFICIAL -> flash OTA-MK51.1-aries-201511292011-201512311830-UNOFFICIAL.zip -> flash gapps -> reboot
tested on MI2 32GB with mokee 4.4.4, use at your own risk
thanks to zipalign and swaded
I see the files is't same, i will try another file source, the dropbox files i got loss my imei
NightHeron said:
New version found by the dev in Chinise Forum
I am installing this right now. Wait for Dropbox to Upload because baidu _____ and i want to help you download this faster
https://dl.dropboxusercontent.com/u/54386997/MK51.1-aries-201508181111-UNOFFICIAL.zip
Click to expand...
Click to collapse
Hi, on my mi2s installed success, but imei is gone, how to fix this? i already restore EFS but if use mokee its still Unknow imei
gonewild87 said:
Simple guide to update from not merged data-sdcard mokee official 4.4.4 to the last mokee unofficial 5.1.1 with merged partition 30/12/2015 update
1) optional - make a full nandroid backup in case anything went wrong
2)REPARTITION TO MERGED DATA
- download MIUI 5.9.2 fastboot package from official miui.com site or from here
- flash it via MiFlash, selecting "flash_all.bat" from advanced properties (the flash_all.bat is inside the miui 5.9.2 fastboot package)
-reboot from fastboot and wait (10 minutes more or less) until miui rom finally boot to the home screen
3)FLASH CUSTOM RECOVERY TWRP 2.8.7.0 FOR MERGED PARTITION
-use this guide (point 2) to flash TWRP via fastboot
4)FLASH MOKEE 5.1.1 ROM + GAPPS
-from twrp wipe data, system, caches -> flash MK51.1-aries-201511292011-UNOFFICIAL -> flash OTA-MK51.1-aries-201511292011-201512311830-UNOFFICIAL.zip -> flash gapps -> reboot
tested on MI2 32GB with mokee 4.4.4, use at your own risk
thanks to zipalign and swaded
Click to expand...
Click to collapse
:fingers-crossed: it's work good for my aries, just one my problem, the diel USSD Code is Chines languange, how to fix this i already change the locale, change font, but still chines :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is one-of-a-kind multi-boot mod for Moto Z. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is encrypted).
MultiROM has 2 parts you need to install:
Modified recovery - download the IMG file from second post and use fastboot or TWRP or Flashify app to flash it.
MultiROM - download the ZIP file from second post and flash it in recovery.
Go into TWRP MultiRom settings and check "Enable No-KEXEC Workaround" (if it's not working check out troubleshooting in next Post)
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/nkk71/multirom
Modified TWRP - https://github.com/nkk71/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/motoTurboZ/android_device_motorola_griffin---MR
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
XDA:DevDB Information
MultiRom for Moto Z, Tool/Utility for the Moto Z
Contributors
erfanoabdi
Source Code: https://github.com/motoTurboZ/android_device_motorola_griffin---MR
Version Information
Status: Testing
Current Beta Version: 33
Beta Release Date: 2016-12-06
Created 2016-12-06
Last Updated 2017-03-30
Video :
Downloads :
IT WILL NOT WORK WHEN ENCRYPTED
https://www.androidfilehost.com/?w=files&flid=140728
Old Versions :
TWRP : https://mega.nz/#!mQpzyRJL!rfWAhx9ZFKgL_WQ2I0dcZ6aSWtqJE98YYByXAaIK5ZU
Multirom : https://mega.nz/#!zFRjjA7I!v_EehAAX0REmVX7DC_y2M7Dl0B-q91K50VxTNT0Ut8E
Multirom Uninstaller : https://mega.nz/#!OEZAEbRK!p8qVatt_YcctZ4cbRR7CK9Mou6oaPT1YN-5NKCc1lh8
How to install :
Flash recovery
Flash multirom zip
Enable kexec workaround in TWRP mr settings
Enjoy!
Changelog :
26 March :
- Nougat Support
- TouchScreen Fixed
30 December :
- SD Card and OTG Fixed
- Updated Multirom and TWRP
- modded Multirom Manager app
09 December :
- initial build
Bugs/issues :
*Let me know, i'll add them here and consider it my todo list on this
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to nkk71
[url]http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4[/URL]
Troubleshooting :
no-kexec workaround is enabled on TWRP but not working in Multirom :
go to "/data/media/0/multirom/multirom.ini" and set "no_kexec=1" (from 0 to 1)
Multirom manager app doesn't recognize your device :
make sure you're using my modded app and add this line
ro.product.device=griffin
into your build.prop at the root of system partition
Moto mods not working :
copy "init.gbmods.sh" from root in somewhere at your data partition like "/data/local/"
Than use init.d of kernel adiutor app to call it like :
Code:
chmod 0755 /data/local/init.gbmods.sh
chmod +x /data/local/init.gbmods.sh
./data/local/init.gbmods.sh
Hi thanks for the Multirom support...
Twrp works just fine but while flashing Multirom zip it give some update error 7
Here is the recovery log :
erfanoabdi said:
info : http://forum.xda-developers.com/oneplus-3/development/multirom-v33b-op3-t3415654
XDA:DevDB Information
MultiRom for Moto Z, Tool/Utility for the Moto Z
Contributors
erfanoabdi
Source Code: https://github.com/motoTurboZ/android_device_moto_griffin
Version Information
Status: Testing
Current Beta Version: 33
Beta Release Date: 2016-12-06
Created 2016-12-06
Last Updated 2016-12-06
Click to expand...
Click to collapse
Does it work with forced encryption enabled?
gomisensei said:
Does it work with forced encryption enabled?
Click to expand...
Click to collapse
No it's not working on encrypted phones
I'm a little bit busy on cm14 I'll add encryption support as soon as possible
@erfanoabdi I've been considering this phone for my next upgrade. I was starting to lean towards not buying, but you just made my decision for me. It will be my first multiROM experience when I get it :laugh:
erfanoabdi said:
No it's not working on encrypted phones
I'm a little bit busy on cm14 I'll add encryption support as soon as possible
Click to expand...
Click to collapse
CM14!! Super excited!
immadeofpixels27 said:
@erfanoabdi I've been considering this phone for my next upgrade. I was starting to lean towards not buying, but you just made my decision for me. It will be my first multiROM experience when I get it :laugh:
Click to expand...
Click to collapse
thanks man
but you need to know there's no kernel with kexec support for this device and on my kernel i need some one to help me to fix it (https://github.com/motoTurboZ/kernel-msm/tree/kexec) if no one add kexec support we can't use secondary roms on multirom
and "nkk71 no kexec" is not working with motorola stock rom and having 2 CM in multirom is just funny
so we have to wait for a good developer, someone smarter than me to fix kexec for multirom :good:
by buying moto z you won't lose anything this is first high-end phone with multirom support (except oneplus 3(T)) and no one had success to add kexec to msm8996 (it's possible on msm8994)
i'm trying by best to develop my kernel and other stuffs for you and other moto z lovers
when i done my device tree for moto z, porting other roms for moto z will be too easier and hopefully we can see more roms for this amazing hardware in near future :fingers-crossed:
erfanoabdi said:
thanks man
but you need to know there's no kernel with kexec support for this device and on my kernel i need some one to help me to fix it (https://github.com/motoTurboZ/kernel-msm/tree/kexec) if no one add kexec support we can't use secondary roms on multirom
and "nkk71 no kexec" is not working with motorola stock rom and having 2 CM in multirom is just funny
so we have to wait for a good developer, someone smarter than me to fix kexec for multirom :good:
by buying moto z you won't lose anything this is first high-end phone with multirom support (except oneplus 3(T)) and no one had success to add kexec to msm8996 (it's possible on msm8994)
i'm trying by best to develop my kernel and other stuffs for you and other moto z lovers
when i done my device tree for moto z, porting other roms for moto z will be too easier and hopefully we can see more roms for this amazing hardware in near future :fingers-crossed:
Click to expand...
Click to collapse
Well,i wasn't planning on getting it immediately anyway. Keep up the awesome work :good:
erfanoabdi said:
thanks man
but you need to know there's no kernel with kexec support for this device and on my kernel i need some one to help me to fix it (https://github.com/motoTurboZ/kernel-msm/tree/kexec) if no one add kexec support we can't use secondary roms on multirom
and "nkk71 no kexec" is not working with motorola stock rom and having 2 CM in multirom is just funny
so we have to wait for a good developer, someone smarter than me to fix kexec for multirom :good:
by buying moto z you won't lose anything this is first high-end phone with multirom support (except oneplus 3(T)) and no one had success to add kexec to msm8996 (it's possible on msm8994)
i'm trying by best to develop my kernel and other stuffs for you and other moto z lovers
when i done my device tree for moto z, porting other roms for moto z will be too easier and hopefully we can see more roms for this amazing hardware in near future :fingers-crossed:
Click to expand...
Click to collapse
Wait, doesn't only the main rom have to have kexec support? that's how multirom on my HTCm8 worked...
gomisensei said:
Wait, doesn't only the main rom have to have kexec support? that's how multirom on my HTCm8 worked...
Click to expand...
Click to collapse
Yes only primary kernel should have kexec hardboot support
erfanoabdi said:
Yes only primary kernel should have kexec hardboot support
Click to expand...
Click to collapse
so you could have cm as primary, and stock motorola as secondary (after making a nandroid backup of course)
gomisensei said:
so you could have cm as primary, and stock motorola as secondary (after making a nandroid backup of course)
Click to expand...
Click to collapse
I tried this but I got bootloop
I didn't play with this so much but next week I'll
Test more and tell about it
Good Newsss and Updates
my new year gift for you guys is new version of multirom
30 December Update :
OTG fixed
SD Card fixed
Updated Multirom and TWRP sources
and the Big one :
Now you can Multirom Stock and CM together
How to install CM and Stock Rom together ?
first if you're on stock make full backup (system, data, boot) with TWRP
if you're on CM and don't have stock backup, please uninstall it and go back to stock to get backup
now
install multirom TWRP
install CM14 (or other custom rom)
install multirom zip
reboot and setup your CM (maybe you need to change multirom.ini for nkk71-no-kexec boot [see troubleshooting])
go back to recovery
and use multirom setting to install your stock rom backup as secondary rom
reboot
ENJOY
i've only tested this with MM and turboZ kernel but this should work with N too
i've not tested stock as primary and CM as Secondary rom and not sure it's working
root (and xposed) is working well on primary and Secondary roms
you can also install 3 or 4 roms together with this method
:fingers-crossed: :fingers-crossed: :fingers-crossed:
erfanoabdi said:
Good Newsss and Updates
my new year gift for you guys is new version of multirom
30 December Update :
OTG fixed
SD Card fixed
Updated Multirom and TWRP sources
and the Big one :
Now you can Multirom Stock and CM together
How to install CM and Stock Rom together ?
first if you're on stock make full backup (system, data, boot) with TWRP
if you're on CM and don't have stock backup, please uninstall it and go back to stock to get backup
now
install multirom TWRP
install CM14 (or other custom rom)
install multirom zip
reboot and setup your CM (maybe you need to change multirom.ini for nkk71-no-kexec boot [see troubleshooting])
go back to recovery
and use multirom setting to install your stock rom backup as secondary rom
reboot
ENJOY
i've only tested this with MM and turboZ kernel but this should work with N too
i've not tested stock as primary and CM as Secondary rom and not sure it's working
root (and xposed) is working well on primary and Secondary roms
you can also install 3 or 4 roms together with this method
:fingers-crossed: :fingers-crossed: :fingers-crossed:
Click to expand...
Click to collapse
After flashing latest multirom.zip all the mods stopped working.
Sent from my Pixel using XDA-Developers mobile app
silvercat said:
After flashing latest multirom.zip all the mods stopped working.
Click to expand...
Click to collapse
Yes if you want to make them working you need to copy init.gbmods.sh from root in somewhere at your data partition
Than use init.d of kernel adiutor to call it like :
Code:
chmod 0755 /data/local/init.gbmods.sh
chmod +x /data/local/init.gbmods.sh
./data/local/init.gbmods.sh
This is happening because multirom change some permissions accidentally
This method is tested on stock Motorola rom as secondary
Tried dual booting with lineage and it's not working. Used lineage as my primary and stuff but still no luck. Lineage boots up fine as it's the internal (primary) ROM but when you select stock it'll just reboot back into multirom and not boot at all
I'm on the n bootloader.
ethanscooter said:
Tried dual booting with lineage and it's not working. Used lineage as my primary and stuff but still no luck. Lineage boots up fine as it's the internal (primary) ROM but when you select stock it'll just reboot back into multirom and not boot at all
I'm on the n bootloader.
Click to expand...
Click to collapse
Yes I just exactly right now tried that and same as you
Let me check for problem
This may related to stock nougat system, always want to boot from verified partition, if that's it I can't do anything
Thanks for sharing your experience
Update : Fixed
erfanoabdi said:
Yes if you want to make them working you need to copy init.gbmods.sh from root in somewhere at your data partition
Than use init.d of kernel adiutor to call it like :
Code:
chmod 0755 /data/local/init.gbmods.sh
chmod +x /data/local/init.gbmods.sh
./data/local/init.gbmods.sh
This is happening because multirom change some permissions accidentally
This method is tested on stock Motorola rom as secondary
Click to expand...
Click to collapse
I have a stock based rom as secondary and a camera mod. The camera mod works when the rom is in primary but once in secondary it doesn't. Applying this only makes it work partially. The power button responds by opening and closing the camera app, but the lens never opens up and extends. The zoom controls do nothing either.
Moved to:
https://forum.xda-developers.com/showthread.php?t=3609358
Hello
This is a place holder for the Device tree I'm about to submit for our device.
Currently, I'm in the middle of testing restore, but I totally did a cannibal install of 3.1.1 straight to my recovery partition, while I had Rootkernel 5.23 Boot.img TWRP 3.0.2 installed... and I had dual boot.
So I'm fairly confident, I have and can get the other versions of Android working for the E5823.
You all should just be able to pull the specific device branch, download the TWRP source, and then build using your prebuilt binary that Sony supplies, or use Flashtool to extract the ELF of the FOTA-Kernel.
I'll update this as the project progresses
Adios.
https://github.com/NeoBeum/XpeRicoverE5823
EDIT: Yep, just did a full restore. I will test encryption this week. I can go back and forth from the other boot image too. DRM Keys intact too, if you have your DK.ftf.
I'll get it working with Rootkernel & Magisk next.
Test Passed:
Complete Backup & Restore
Restore TA Partition to revert lost DRM Keys on Bootloader Unlock
Current issues:
Install from Zip/Image Permissions - 16/5/2017
Enlighten me please, what is this? Source code for recovery or rom?
MakeHav0 said:
Enlighten me please, what is this? Source code for recovery or rom?
Click to expand...
Click to collapse
TWRP Recovery Source for vanilla Sony AOSP. So no need for CM or Omnirom.
Team Win says they should be able to review the build in about a fortnight
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.
PHP:
* 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.
Changelog For 3.3.1-0
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
Install Guide:
For non rooted and rooted phones
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Brain
Download https:// drive .google.com/file/d/1-1MQqE42zIoLnqbYx-JTRQtVtnIV85Rt/view?usp=sharing (Remove space)
Put phone into fastboot mode (hold vol down + power button)
Connect phone to PC
Open a command prompt where you have fastboot and the TWRP image file located
Type the following in command prompt:
PHP:
fastboot flash recovery twrp-3.3.1-0-aljater.img
Note: For Windows 10 users who use the powershell and not cmd
The command will become:
PHP:
./ fastboot flash recovery recovery.img
Note: Test if it works in the JETER variant (I do not have that device, I have the ALJETER variant)
XDA: DevDB Information
twrp, Tool/Utility for the Moto G6 Play (Aljeter)
Contributors
TWRP Team
Me
Version Information
Status: Stable
Stable Release Date: 2019-06-03
Created 2019-06-03
Last Updated 2019-06-03
So this will allow flashing of A/B roms?
kwiksi1ver said:
So this will allow flashing of A/B roms?
Click to expand...
Click to collapse
I am not bad Moto G6 Play as the Moto G6 only have a / Vendor type A partition, you can also install custom rom (GSI) from an image file.
In the same way, I will try to compile a TWRP that supports the partition / vendor as a defect so that a custom roms GSI installation can be performed from a zip file.
Thread cleaned!
Kanged work must be addressed by developer himself using the report button or contacting any Mod. Future public posts will be cleaned again and users will be addressed.
Thank you
Will this TWRP be available on unofficialtwrp.com/
Do you know if there will ever be a official TWRP for Moto G6 Play?
I ask because I have enough experience to follow guides, but not enough to be security smart, which is ironic as I want a custom ROM to move away from Googles spying and bloat.
DulfaGreyny said:
Will this TWRP be available on unofficialtwrp.com/
Do you know if there will ever be a official TWRP for Moto G6 Play?
I ask because I have enough experience to follow guides, but not enough to be security smart, which is ironic as I want a custom ROM to move away from Googles spying and bloat.
Click to expand...
Click to collapse
To install a Custom ROM you do not need an build official TWRP , because in my opinion the cell phone should go better with the 64bit architecture and thus the device would be more useful, but since currently there is no support for the device itself, you can try installing a GSI ROM, apparently everything works, in LineageOS 16 Moto Actions do not work.
Don't use this.. yes it works, because the developer made sure of it, but this isn't the developer,
This guy was kindly helped by the developer and then stole that developers work. Then turned around and posted it here, risking all of your devices since he has no clue about it, just for a little attention.
Nice guy right?
If it seems like he's talking gibberish, it's cause he is. He has no clue how any of this works. But yes an official is in the works. In the meantime, thank god this guys an idiot and didn't erase his footsteps, suck it Allan
Alan1231999 said:
To install a Custom ROM you do not need an build official TWRP , because in my opinion the cell phone should go better with the 64bit architecture and thus the device would be more useful, but since currently there is no support for the device itself, you can try installing a GSI ROM, apparently everything works, in LineageOS 16 Moto Actions do not work.
Click to expand...
Click to collapse
I have installed custom roms before and as starkiller2 pointed out you make no sense. My question was about the security and quality control of what you have offered -which for all I know could be invasive or broken. Hence I was seeking some kind of verification of legitimacy; which you have given me albeit the opposite of what you may have intended.
It appears that some concern is shared by starkiller2 -thanks
I maintain my stance that Allan can choke on it
Give a link to twrp 3.3.1 I can not download
bronislav808 said:
Give a link to twrp 3.3.1 I can not download
Click to expand...
Click to collapse
That's because it was stolen work bud.
Why is this thread even up? @mods
Kuntitled said:
Why is this thread even up? @mods
Click to expand...
Click to collapse
When I tried taking my first guide thread down a mod told me they don't remove posts for archival purposes or something like that. Might be different though for the situation involved with this thread though
Kuntitled said:
Why is this thread even up? @mods
Click to expand...
Click to collapse
The mods were supposedly "investigating" it but never did anything. And Allan's ***** ass disappeared
finally i can say after long work 1 month to fix bugs and porting the tree from another exynos7870 phone and adapting the kernel source, i build the first custom rom for M10: lineage-17.1
first i thanks Astrako and 7870 team for bring up the universal7870 trees without them M10 won't have a custom rom
trees:
GitHub - AndVer2/android_manifest_samsung_m10lte at lineage-17.1
Contribute to AndVer2/android_manifest_samsung_m10lte development by creating an account on GitHub.
github.com
kernel source:
https://github.com/AndVer2/android_kernel_samsung_m10lte
the rom:
https://roms.cirrus-ci.workers.dev/0:/m10lte/lineage-17.1-20221016-UNOFFICIAL-m10lte.zip
please support me to make another rom the next custom recovery if i get 3 tester will be lineage 18.1 then aex
how to flash:
pre:
1) a twrp with internal storage decrypted (required)
2) a laptop with your firmware (optional/recommanded)
3) a sdcard (recommanded)
flash:
-1) do a backup a full backup
0) oem unlocked and kg state: checking
1) download the zip, twrp and gapps (gapps: arm64, android 10, arm64)
2) flash twrp
3) go to twrp wipe: system, vendor, cache, dalvik cache, data for internal storage (dont wipe it if the lineage in internal storage)
4) flash zip
5) boot to system
feature:
all lineage feature
bugs:
you tell me
please help me i have crdroid 10 tree and if this works i will build crdroid for M10 guys
before ending lets check m10 supports
SM-M105G : didnt tested
SM-M105F : didnt tested
SM-M105M : didnt tested
for SM-M105Y next time
thanks
Kakang_Ragil said:
m105G bootlop
Click to expand...
Click to collapse
ok
link is broken, can you upload it again?
fahimscirex said:
link is broken, can you upload it again?
Click to expand...
Click to collapse
dont bother yourself on that it wont work
youssef_none said:
finally i can say after long work 1 month to fix bugs and porting the tree from another exynos7870 phone and adapting the kernel source, i build the first custom rom for M10: lineage-17.1
first i thanks Astrako and 7870 team for bring up the universal7870 trees without them M10 won't have a custom rom
trees:
GitHub - AndVer2/android_manifest_samsung_m10lte at lineage-17.1
Contribute to AndVer2/android_manifest_samsung_m10lte development by creating an account on GitHub.
github.com
kernel source:
https://github.com/AndVer2/android_kernel_samsung_m10lte
the rom:
https://roms.cirrus-ci.workers.dev/0:/m10lte/lineage-17.1-20221016-UNOFFICIAL-m10lte.zip
please support me to make another rom the next custom recovery if i get 3 tester will be lineage 18.1 then aex
how to flash:
pre:
1) a twrp with internal storage decrypted (required)
2) a laptop with your firmware (optional/recommanded)
3) a sdcard (recommanded)
flash:
-1) do a backup a full backup
0) oem unlocked and kg state: checking
1) download the zip, twrp and gapps (gapps: arm64, android 10, arm64)
2) flash twrp
3) go to twrp wipe: system, vendor, cache, dalvik cache, data for internal storage (dont wipe it if the lineage in internal storage)
4) flash zip
5) boot to system
feature:
all lineage feature
bugs:
you tell me
please help me i have crdroid 10 tree and if this works i will build crdroid for M10 guys
before ending lets check m10 supports
SM-M105G : didnt tested
SM-M105F : didnt tested
SM-M105M : didnt tested
for SM-M105Y next time
thanks
Click to expand...
Click to collapse
Do you have telegram? i will contact you.. help me
Aldho110499 said:
Do you have telegram? i will contact you.. help me
Click to expand...
Click to collapse
hey, thanks for testing los. yep it doesnt works, so i build crdroid (it works), if you want to test it:
Crdroid [Q/10] for SM-M105G/SM-M105F
hi, hope you are fine, first thanks Astrako and all 7870 contributor for giving the best device tree for exynos7870 family also thanks for me because i build and adapte device tree vendor tree kernel source for M10 so first lets talk about the...
forum.xda-developers.com
fahimscirex said:
link is broken, can you upload it again?
Click to expand...
Click to collapse
hey this crdroid:
Crdroid [Q/10] for SM-M105G/SM-M105F
hi, hope you are fine, first thanks Astrako and all 7870 contributor for giving the best device tree for exynos7870 family also thanks for me because i build and adapte device tree vendor tree kernel source for M10 so first lets talk about the...
forum.xda-developers.com