Related
Heres the Latest CM11 Snapshot M12 that CyanogenMod released
This is Android 4.4.4
This ROM includes:
- F2FS-ALL (System,Cache and Data)
- PA Micro GAPPS (Feb 15, 2015)
- M-Kernel a69 (credits to Metallice for this Awesome kernel)
- All CM11 unnecessary apps (bloatware) Removed.
- AdBlock (02102015) thanks to BSDgeek_Jake
Installation:
Theres tons of guides here on how to do this:silly:
- If you have already F2FS-ALL your System,Cache and Data using TWRP 2.8.5 or later
Just do a Factory Wipe in TWRP and manually Wipe System for a Clean install.
Doing so Would Not Format your Internal Storage.
- Install CM11 SNAPSHOT M12 F2FS-ALL-grouper.zip
- Then Flash the latest SuperSU
- Wipe Cache and Davlik
- Reboot
- Enable ART(optional)
- Install Nova Launcher for More Speed(Highly Recommended)
Download Links:
NEW: F2FS-ALL
ROM:CM11 SNAPSHOT M12 F2FS-ALL-grouper
MD5: 5DEDCDB4435549CE93811A25E6128C63
NEW: EXT4
ROM: CM11 SNAPSHOT M12 EXT4-grouper
MD5: E2CC59B4C59094BD20706EC16F0B2E59
OLD:
Rom: CM11 M9 F2FS-ALL Grouper
MD5: ced60d458ba060da7c3edc696d47bc5f
Get latest SuperSU here: SuperSU 2.46
I've got pristine CM11 M8 with clockwork mod 6.0.4.3
There are *lots* of posts... but can anyone direct me to a clear safe path from this to M9 with F2FS system and data?
There are many posts that involve fiddling with custom kernels on each update, and so on, but I want to avoid that and just have rolling CM 11 updates with support for F2FS on system and data.
thanks
samjam said:
I've got pristine CM11 M8 with clockwork mod 6.0.4.3
There are *lots* of posts... but can anyone direct me to a clear safe path from this to M9 with F2FS system and data?
There are many posts that involve fiddling with custom kernels on each update, and so on, but I want to avoid that and just have rolling CM 11 updates with support for F2FS on system and data.
thanks
Click to expand...
Click to collapse
Use [ROOT] Rashr - Flash Tool to install the latest TWRP recovery.
Then follow this guide [Guide][WIP] To ALL-F2FS
animatrix999 said:
Use [ROOT] Rashr - Flash Tool to install the latest TWRP recovery.
Then follow this guide [Guide][WIP] To ALL-F2FS
Click to expand...
Click to collapse
Darn, that guide didn't work, failed flashing;
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/usb-otg/CM11 M9 F2FS-ALL Grouper.zip'
On reboot it is stuck at "Google" screen with unlocked padlock
I have TWRP 2.7.1.1 (flashed using RASHR)
[EDIT] I repeat f2fs and try again and this time it works
Ack! now I restore data the restore will first format as ext4;
so to backup the ext4 data ina way I can restore it, I get a command window in /data and do:
tar -c . > /usb-otg/data.tar
then reboot back into recover and make data as f2fs again, and then:
tar -xv < /usb-otg/data.tar
Although data restored I had to so a wipe for the new system to work properly.
Thanks animatrix999 this is much slicker than CM11 M8 standard.
Only fault is also with CM11 standard is that Google play videos won't play, even when downloaded, although music will
Sent from my Nexus 7 using Tapatalk
Hi,
Can this ROM be installed in Tilapia? Nexus 7 3g 2012?
sudipt123 said:
Hi,
Can this ROM be installed in Tilapia? Nexus 7 3g 2012?
Click to expand...
Click to collapse
Only on Nexus 7 WiFi 2012 model.
I went back to stock 4.4.4 (with hacks to get boot to load), loaded twrp 2.7.1.0 with fastboot, rooted, left bootloader unlocked, and movies play OK.
I found that a twrp backup consists of tar files; e.g. data.ext4.win000 and data.ext4.win001 so I migrated bacl to f2fs and restored data manually by getting a shell in the backuo dir and running:
tar -C / -x < data.ext4.win000
tar -C / -x < data.ext4.win001
and that restored fine but most apps still failed unless I re-installed. google play movies and tv had an update and it didn't crash after the update but still could not play any movies so i think maybe there is a drm library missing or something.
So I am back to 4.4.4 stock image with trim but no f2fs.
I may do a diff on the files to see what might be missing from this all-f2fs image
- intersting the official 2048 force closes in stock but not in this m9 image.
This ROM is missing
/vendor/lib/mediadrm
/vendor/lib/mediadrm/libwvdrmengine.so
which sound related
Also missing: /vendor/lib/libfrsdk.so
but i don't know what that is
also: /lib/libchromeview.so
Later I will try transfer the libwvdrmengine.so to see if google play movies & tv starts working
Not just google play movies & tv, but also bluetooth is not working on M9 as well.
I don't know if it was working on M5 (did not try that).
How long does the first boot take. Think i have s bootloop. It's almost 15 minutes on the cm logo
r-l said:
How long does the first boot take. Think i have s bootloop. It's almost 15 minutes on the cm logo
Click to expand...
Click to collapse
Did you convert all the file systems to f2fs?
samjam said:
Did you convert all the file systems to f2fs?
Click to expand...
Click to collapse
All ready fixed it. I flashed it after coverting to f2fs and got a bootloop. Then i sideloaded it with the Nexus toolkit and flashed it again and now it works.
Let's see if f2fs really works (first time using it)
---------- Post added at 12:44 PM ---------- Previous post was at 11:56 AM ----------
Next problem i can't cast (bubbleupnp or any other app) to my chromecast anymore.
Edit: also fixed
r-l said:
All ready fixed it. I flashed it after coverting to f2fs and got a bootloop. Then i sideloaded it with the Nexus toolkit and flashed it again and now it works.
Let's see if f2fs really works (first time using it)
---------- Post added at 12:44 PM ---------- Previous post was at 11:56 AM ----------
Next problem i can't cast (bubbleupnp or any other app) to my chromecast anymore.
Edit: also fixed
Click to expand...
Click to collapse
How did you fix them?
Fix what? Chromecast?
Did a hard reset and rebooted my tablet a few times
jazzespresso said:
Not just google play movies & tv, but also bluetooth is not working on M9 as well.
I don't know if it was working on M5 (did not try that).
Click to expand...
Click to collapse
Bluetooth works fine
r-l said:
Bluetooth works fine
Click to expand...
Click to collapse
mine not....it was clean install by the way...no idea...could be one of xposed or CM11 themes causing?
jazzespresso said:
mine not....it was clean install by the way...no idea...could be one of xposed or CM11 themes causing?
Click to expand...
Click to collapse
Was a clean install too. Flashed it as my first rom on f2fs. Using xposed an android L cm theme
Works for me. I don't use xposed
animatrix999 said:
Only on Nexus 7 WiFi 2012 model.
Click to expand...
Click to collapse
Hi, animatrix999 , can you build the ROM for tilapia with M-Kernel a69 or point me in the right directon? I have the ROM- to F2fs convert app
OFFICIAL CyanogenMod 12.1 for the Kindle Fire HD 7"
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2128848
CHECK KNOWN ISSUES BEFORE FLASHING. MAY NOT BE GOOD ENOUGH FOR DAILY USE.
Official nightly builds can be found here:
http://download.cyanogenmod.org/?device=tate
Download Google Apps for Android 5.1:
https://www.androidfilehost.com/?w=files&flid=25361
(Choose newest *-5.1-* file)
NOTES:
Older versions of TWRP will show a "mount failed error". This is safe to ignore.
First boot after a clean wipe will take a LONG time. Be patient.
KNOWN ISSUES:
Use XDA Bug Reporter
SCREEN SHOTS:
Use XDA Screenshots
XDA:DevDB Information
CM12.1 KFire HD 7 (LP 5.1.x), ROM for the Amazon 7" Kindle Fire HD
Contributors
Hashcode
Source Code: http://www.github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Beta Release Date: 2015-06-24
Created 2014-12-27
Last Updated 2015-06-24
Reserved
KERNEL UPDATES for Lollipop Android 5.0 / 5.1
Added F2FS support which can be turned on (with a full /data format) in a future release of TWRP
Combined defconfig setup to better support all HD models
Picked "Wakeup reason" patchset from Google's common 3.4 kernel (not fully implemented yet)
Picked IPV6 routing changes from Google's common 3.4 kernel
Reverted a hardcoded disable of Secure Discard and added the official upstream patch for Secure Discard support detection
Reserved
Android 5.1 / CM-12.1 changes:
SElinux Enforcing as default enabled
Woke up from my nap and saw this! Amazing!!! Downloading now
Edit: I would like to point out that there will be a mount failed error in TWRP when flashing the build. Ignore the error and be patient. It'll flash! It took about 2-3 minutes.
Edit2: And it has booted! Approx time is 8 minutes. Be patient on your first boot guys!
Very very thanks Hashcode you are awesome!
Always knew we could rely on the master. Flashing asap once downloaded.
Hashcode, I flash it and 5Ghz Wifi works for me
davigar said:
Hashcode, I flash it and 5Ghz Wifi works for me
Click to expand...
Click to collapse
Mines not. It's not detecting my 5Ghz network.
Can confirm the 7/8 minute 1st boot. Must be to do with initialising ART?!
Anyway, now for a play and a few customisations.
Once again, Thank you and hope you managed to find some time to enjoy Christmas!!
I just got 5Ghz to work. At least on mine. So since a lot of my android devices don't detect my 5Ghz I had to do some researching. Changing the 5Ghz channel from Automatic/Auto to 44 or 48 will make it work. Can confirm on my Nexus 4 and the Kindle. Works superbly!
Source
Glad to see you sorted out all of the issues quicker than any of the other developers could. We're not horrible, but there's no matching the talent that you have when it comes to this type of thing.
And we thought we were close ?. At least we learned a lot and more to come! Thanks Hash for putting your time and effort into this.
How to fix allot of FC's? Google play is giving me trouble. I flashed 12/20 gapps right? And su 1.94
Everything seems to be working very nicely so far. Just flashed about an hour ago. Seems much smoother than kit kat did. Thank you very much. Looking forward to the updates.
Sent from my Amazon Tate
cell2011 said:
How to fix allot of FC's? Google play is giving me trouble. I flashed 12/20 gapps right? And su 1.94
Click to expand...
Click to collapse
As the title of thread says, its in Alpha. But may I ask what FC's your'e getting? I'm running the build on my Kindle at the moment and the only FC I get is Bluetooth Sharing. Bluetooth was activated on the main user and when I switch to another user it FC's.
I did advance wipe cache system dalvik data and flashed rom gapps and super su 1.94
---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------
Should i reflash just rom and gapps and supersu after i boot up?
cell2011 said:
I did advance wipe cache system dalvik data and flashed rom gapps and super su 1.94
---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------
Should i reflash just rom and gapps and supersu after i boot up?
Click to expand...
Click to collapse
There's no need to flash SuperSU . SuperUser is built in already and working. Wipe System, Data, Cache, and Dalvik. Then flash the ROM and gAPPS.
---------- Post added at 04:43 AM ---------- Previous post was at 04:17 AM ----------
Is anyone else getting a bootloop when clicking on reboot? I have to fully power down to be able to make it boot. Also, I'm unable to tick unknown sources when on another user (using Multi-Acc). Don't worry, I'm not downloading pirated apps xD. I download the APK's over at the Android Apps and Games forum.
Awesome work man! Flashing now...
This is great! Thank you Hashcode!
When I flash it, I get the error
Code:
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/sys
(I can't read further)
Is this something to be worried about? It boots just fine.
Random Username said:
This is great! Thank you Hashcode!
When I flash it, I get the error
Code:
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/sys
(I can't read further)
Is this something to be worried about? It boots just fine.
My other problem is that I can't log in with my Google account? Is this maybe related?
Click to expand...
Click to collapse
I get the same error and google account works fine for me
{
"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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod. 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
Manual 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.
MultiROM has 3 parts you need to install:
MultiROM (multirom-YYYYMMDD-vXX-shieldtablet.zip) - download the ZIP file from second post and flash it in recovery.
Modified recovery (twrp-multirom-YYYYMMDD-UNOFFICIAL-shieldtablet.img) - download the IMG file from second post and use fastboot or Flashify app to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the image and flash it through fastboot or Flashify.
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 Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
2. Ubuntu Touch
Not yet ported.
3. Firefox OS
Not yet ported, but should be as easy as other Android ports.
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 Advanced -> 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 Advanced -> 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/CM-Shield/multirom (branch flipped-screen)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
Device Tree - https://github.com/CM-Shield/android_device_nvidia_shieldtablet (branch cm-12.0-unified-mrom)
Kernel w/ kexec-hardboot patch - https://github.com/CM-Shield/android_kernel_nvidia_shieldtablet (branch cm-12.0-mrom)
Downloads
1. Main downloads
MultiROM: multirom-20150909-v32a-UNOFFICIAL-shieldtablet.zip
MultiROM Touch Support (only needed if not upgrading): multirom_shieldtablet_touch_support.zip
Modified recovery (based on TWRP 2.8.7.0): twrp-multirom-20150909-UNOFFICIAL-shieldtablet.img
Kernel kexec-hardboot patch (Stock 5.1.1 all variants): kexec_patch_stock_311.zip
Kernel kexec-hardboot patch (Stock 5.1.1 all variants): kexec_patch_stock_31.zip
Kernel w/ kexec-hardboot patch (Stock 5.1.0 wx_na_wf): kexec_boot_stock_na_wf_30.img
Kernel w/ kexec-hardboot patch (Stock 5.1.0 wx_na_do): kexec_boot_stock_na_do_30.img
Kernel w/ kexec-hardboot patch (Stock 5.1.0 wx_un_do): kexec_boot_stock_un_do_30.img
Kernel w/ kexec-hardboot patch (Stock 5.0.1 wx_na_wf): kexec_boot_stock_na_wf.img
Kernel w/ kexec-hardboot patch (Stock 5.0.1 wx_na_do): kexec_boot_stock_na_do.img
Kernel w/ kexec-hardboot patch (Stock 5.0.1 wx_un_do): kexec_boot_stock_un_do.img
MultiROM Manager: MultiROMMgr.apk
2. third-party kernels with kexec-hardboot patch
BitO-K - http://forum.xda-developers.com/shield-tablet/development/tweaked-kernel-nvidia-shield-tablet-t3069776
Nicely ask your kernel developer to merge kexec-hardboot patch (patch for shieldtablet).
3. Other downloads
Ubuntu (kernel and packaging by Bogdacutu):
Download Thread
4. Old downloads by Bogdacutu
v31/r3
Patched TWRP
MultiROM Installer
Patched Lollipop kernel (for kernel devs, here's the patch: http://hastebin.com/timaneyuwi.diff)
v31/r2:
TWRP
v30/r1:
TWRP
MultiROM
Works in 5.0.1?
PDNKED said:
Works in 5.0.1?
Click to expand...
Click to collapse
yes. it won't work on kitkat though, since there's no patched kernel yet (I'll compile one for kitkat too eventually)
Bogdacutu said:
yes. it won't work on kitkat though, since there's no patched kernel yet (I'll compile one for kitkat too eventually)
Click to expand...
Click to collapse
All done. Now... How i add mrom images? I can't wait for ubuntu touch.[emoji1]
nexus 6
could this work on nexus 6? also would i have to uninstall cwm and use twrp for this with shield tablet 32 lte us version?
Amazing work bogdan.
Bogdacutu said:
yes. it won't work on kitkat though, since there's no patched kernel yet (I'll compile one for kitkat too eventually)
Click to expand...
Click to collapse
But kitkat can be installed as secondary isn't?
YAAAAYYYYYY!
Time to liberally screw around with some experimental 3rd party ROMs! :laugh:
lowsum said:
But kitkat can be installed as secondary isn't?
Click to expand...
Click to collapse
I haven't tried but theoretically yes, it should work
sent from my Darkside of SHIELD Tablet
---------- Post added at 10:54 AM ---------- Previous post was at 10:50 AM ----------
grv00711 said:
could this work on nexus 6? also would i have to uninstall cwm and use twrp for this with shield tablet 32 lte us version?
Click to expand...
Click to collapse
to flash another recovery isn't required to uninstall the previous one, actually you can't even do it, just flash, it will replace the cwm or whatever you used before
sent from my Darkside of SHIELD Tablet
The only downside is that recovery still makes all devices look like they're WiFi only versions, which makes universal kernel installers go dumb and install wrong version of the kernel.
Other than that, great job, much appreciated.
xanthrax said:
I haven't tried but theoretically yes, it should work
sent from my Darkside of SHIELD Tablet
---------- Post added at 10:54 AM ---------- Previous post was at 10:50 AM ----------
to flash another recovery isn't required to uninstall the previous one, actually you can't even do it, just flash, it will replace the cwm or whatever you used before
sent from my Darkside of SHIELD Tablet
Click to expand...
Click to collapse
thank you
xanthrax said:
I haven't tried but theoretically yes, it should work
sent from my Darkside of SHIELD Tablet
---------- Post added at 10:54 AM ---------- Previous post was at 10:50 AM ----------
to flash another recovery isn't required to uninstall the previous one, actually you can't even do it, just flash, it will replace the cwm or whatever you used before
sent from my Darkside of SHIELD Tablet
Click to expand...
Click to collapse
what are the chances of being able to run windows 8.1 os on the shield tablet us 32 lte?
grv00711 said:
what are the chances of being able to run windows 8.1 os on the shield tablet us 32 lte?
Click to expand...
Click to collapse
extremely close to 0. even if it happens, it would still be just the RT version
Bogdacutu said:
extremely close to 0. even if it happens, it would still be just the RT version
Click to expand...
Click to collapse
new to this -sorry for the stupid questions..
Hey i installed multirom v28 and i have sd gpe and sd sense roms can i flash diff kernels for each one ? Thanks
Windows 8 is never running on our shield tablets. More feasible ideas : Ubuntu, kali, debian, etc.
---------- Post added at 01:44 AM ---------- Previous post was at 01:44 AM ----------
ahmad.gh1 said:
Hey i installed multirom v28 and i have sd gpe and sd sense roms can i flash diff kernels for each one ? Thanks
Click to expand...
Click to collapse
Not unless they're made for this device
For a proof of concept I will be flashing OTA.1.2.1 side by side with lollipop 2.1, wish me luck!
i wish i had a clue!
berryman13 said:
For a proof of concept I will be flashing OTA.1.2.1 side by side with lollipop 2.1, wish me luck!
Click to expand...
Click to collapse
I tried, it didn't work for me, I also tried other roms but didn't found any that booted. I'm used to multi rom on my nexus 7, I don't think it's an error on my part. Wish you luck!
•••• Qualcomm Moto E4 (xt1766) SPerry Only ••••
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and functionality of your device. Although this ROM has been thoroughly tested on my own device, I take no responsibility for bricked or otherwise inoperable devices incurred as a result of this thread. Follow the instructions carefully, and things should go smoothly and without negative results.
SPECIFICATIONS:
• Moto E4 (XT1766) SPerry
• Sprint, Virgin Mobile, Boost Mobile
• Android Version: 7.1.1 Nougat
• Build No. NCQS26.69-64-10
• System Version: 26.231.8.sperry_sprint.en.US
• Radio Version: M8920_15000.280.06.58.05R
• Kernel Version: Linux 3.18.31-perf
• Security Patch Level: September 1, 2018
FEATURES:
• Stock Configuration
• Systemless Root - Magisk v17.1 Stable
• SafetyNet Pass (ctsProfile & basicIntegrity)
• Zipaligned /system/app & /framework
• Optimized RAM efficiency
• Disabled AVB & dm-verity
• Disabled Force Encryption (Opt-Encrypt)
• BusyBox v1.29.2 (Static Binaries)
• TWRP Flashable Installer
PREREQUISITES:
An unlocked bootloader and TWRP custom recovery are required to install this ROM. IMPORTANT: Use @squid2's TWRP v3.2.1-r1 or older for installation https://forum.xda-developers.com/devdb/project/dl/?id=27958 Newer builds will cause a conflict with the /vendor & /oem partitions when installing my partition updater zip. After installation, you may update TWRP to a newer or current version.
The conflict is due to the partition scheme of my updater-script, and is not due to any fault in @squid2's current TWRP builds. Here is a link to @squid2's TWRP thread for the Qualcomm Moto E4. https://forum.xda-developers.com/mo...velopment/twrp-twrp-moto-g4-qualcomm-t3655160 Please be sure and hit the thanks button on his thread if you use his work.
NOTES:
• If you have previously installed the 26.221.3 OTA to bring your build version up to NCQS26.69-64-10, you should have no need to install the partition updater zip prior to installing the ROM. However, if you are unsure of your present firmware build, or if you have not installed the latest OTA, the partition updater should be installed per the instructions below, in order for the ROM to work with the best results;
• As to force encryption, the kernel fstab has been modified to disable this OEM security feature. However, you may still manually encrypt your /userdata by fully charging your device, going to Settings>Security>Encrypt Phone, and following the on-screen prompts;
• This OTA update did not augment the baseband (radio firmware) version (M8920_15000.280.06.58.05R), which remains unchanged from NCQS26.69-64-8. While the radio firmware did receive a couple of minor patches, the changelog in this regard is insignificant, so I did not include these in either the partition updater or the ROM. If anybody wants these radio patches, leave a comment and I'll fix up a TWRP flashable installer.
INSTRUCTIONS:
• 1. Download the ROM and Partition Updater from the download link below and save them to your device's external storage (because the /usedata partition needs to be formatted to disable force encryption, saving the downloaded zips to internal storage would be futile);
• 2. Make a backup of any important files on your device;
• 3. Boot your device into TWRP recovery mode;
• 4. Select Wipe>Advanced Wipe and select System, Cache & Dalvik Cache. Swipe the action bar to commence the wipe;
• 5. Again select Wipe>Format Data, input the word "YES" when prompted, and swipe the action bar to commence the format. Reboot Recovery (often necessary to ensure proper mounting of /usedata after a format);
• 6. Select Install, navigate to the saved location of the Partition Updater zip, and swipe to commence install (this updates your /oem partition, /rpm primary bootloader, /tz trust zone partition, and /devcfg partition to Build No. NCQS26.69-64-10);
• 7. Select Install, navigate to the ROM zip, and swipe to commence install;
• 8. Reboot System.
Kernel Source Code (msm8920): https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NCQ26.69-48
THANKS & CREDITS:
•Thanks to the long-dedicated @squid2 for his TWRP builds for this and many other Motorola devices;
•Thanks to the great @SuperR. for his amazing Windows version SuperR's Kitchen;
• Thanks to the world famous @topjohnwu for his Magisk Universal Systemless Interface;
• Thanks to @madbat99 for his dedication to Motorola devices, and for taking the time to assist so many Motorola device owners;
• Thanks to @osm0sis for his static BusyBox installer and his Magisk Modules;
• Thanks to @Davey126 for his support of Motorola devices, and his dedication to helping other members on various device threads.
DOWNLOAD LINKS:
NCQS26.69-64-10 Partition Updater: https://drive.google.com/file/d/1VmOPXbYBQQkqB475iVzKip2JI_AO0YCM/view?usp=drivesdk
NCQS26.69-64-10 Stock Android 7.1.1 ROM: https://drive.google.com/file/d/1VRuKnSgVHNkewbk5juB7_WWeLm_ptmUP/view?usp=drivesdk
I have also made a debloated build of this ROM, with all Amazon, Sprint and OEM related apps removed from /system/app, /system/priv-app, /oem/app, etc. I will try and post this version this coming week for anybody interested.
I'm new bee kinda so flashing this os just the update so if I have everything up and running good them really don't need this update seems updates have me screwed from getting data on custom rom now so any advice
Bailey36375 said:
I'm new bee kinda so flashing this os just the update so if I have everything up and running good them really don't need this update seems updates have me screwed from getting data on custom rom now so any advice
Click to expand...
Click to collapse
If you have taken the OTA update and you are on Build No. NCQS26.69-64-10, and everything is running smoothly, you have no need to install anything here.
I'm not on 10 I'm on 8 but would like that debloted version
Bailey36375 said:
I'm not on 10 I'm on 8 but would like that debloted version
Click to expand...
Click to collapse
It'll be up in a couple of days. By the way, there is no danger in taking the OTA. No reported bugs, instabilities, etc. And you can still flash the debloated ROM when I post it.
Thanks for taking time to do this and keep support going for the E4. I'm planning on trying the debloat when you post it.
S o S just flashed and now it is only booting to TWRP it says its flawed but
Only boots to TWRP help after flash
---------- Post added at 05:34 AM ---------- Previous post was at 05:18 AM ----------
Really need help I have TWRP 3.2.1 r1 I did what the instructions said but now just goes to the TWRP what's the issue I'm sure it's something I'm doing help this is my only phone
---------- Post added at 05:52 AM ---------- Previous post was at 05:34 AM ----------
Got it woohoow
MotoJunkie01 said:
I have also made a debloated build of this ROM, with all Amazon, Sprint and OEM related apps removed from /system/app, /system/priv-app, /oem/app, etc. I will try and post this version this coming week for anybody interested.
Click to expand...
Click to collapse
Yayyyyyyy!!!!!! I,ll be waiting for that one. Thanks motojunkie01.
Does Radio work in Custom Roms.
EarthMan1 said:
Does Radio work in Custom Roms.
Click to expand...
Click to collapse
The radio was not updated with the new OTA. The Baseband Version remains the same as the previous build, M8920_15000.280.06.58.05R
That means the voice calls won't work on Custom ROMs.
EarthMan1 said:
That means the voice calls won't work on Custom ROMs.
Click to expand...
Click to collapse
Voice, MMS/SMS, and 4G/LTE data works on my device with LineageOS 14.1 on the 05R radio firmware. Although I am aware that an earlier OTA (NCQS26.69-64-8) did break the cell radio for some device owners running custom ROMs.
MotoJunkie01 said:
Voice, MMS/SMS, and 4G/LTE data works on my device with LineageOS 14.1 on the 05R radio firmware. Although I am aware that an earlier OTA (NCQS26.69-64-8) did break the cell radio for some device owners running custom ROMs.
Click to expand...
Click to collapse
So, if i want to update I have to wipe my data.
EarthMan1 said:
So, if i want to update I have to wipe my data.
Click to expand...
Click to collapse
No. But if you want to install this ROM, you will need to format /userdata in order to disable force encryption. If you want your data encrypted, you are not required to format /userdata.
No, I want only to install the partition updater.
EarthMan1 said:
No, I want only to install the partition updater.
Click to expand...
Click to collapse
Then formatting data is not necessary. Keep in mind that the partition updater does not change your radio firmware. You'll still have the 05R radio version after updating your partitions. The partition updater updates your bootloader, /devcfg and /oem partitions.
So if your radio didn't work on custom ROMs before, the partition updater likely will not change that.
Why this partition updater size is big compared to the NCQS26.69-56 one.
EarthMan1 said:
Why this partition updater size is big compared to the NCQS26.69-56 one.
Click to expand...
Click to collapse
Because the /oem partition is large (656 MB)
Why isn't it included in the 56 one
How can i install lineage 15.1 on j4+ 2018?
The phone is new and you must wait for someone to release
zhelev81 said:
How can i install lineage 15.1 on j4+ 2018?
Click to expand...
Click to collapse
GSI? Possibly with some issues.
ashyx said:
GSI? Possibly with some issues.
Click to expand...
Click to collapse
issues like ? the stock rom is awefull .. can you tell us how to flash and what issues to expect
zhelev81 said:
issues like ? the stock rom is awefull .. can you tell us how to flash and what issues to expect
Click to expand...
Click to collapse
Issues like no network etc.
There are plenty of tuts on flashing GSI's. I suggest to read up before hand.
kapmino269 said:
Man do you have download link for lineage OS for j415f please send it to me I tried from downloading and flash files .
---------- Post added at 10:22 PM ---------- Previous post was at 10:20 PM ----------
Ashyx which thread I should follow to install GSI
and links please.
I used :
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
1- I flash : https://forum.xda-developers.com/pr...t/experimental-lineageos-16-0-treble-t3835094
but phone wasn't boot .and when I install lineage16 ing only without opengapps arm64 9.0 (I download from opengapps.org) twrp continue tell me your sdk23 android 6.0 you should
2- What is A-A/B mean ? to choose what I should download from :
https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
Click to expand...
Click to collapse
A only device 64bit.
Format data and install. Flash Magisk immediately afterwards.
kapmino269 said:
I download v5 A only arm64 with gapps
phone didn't boot to system and continue restart
what should I do ?
Click to expand...
Click to collapse
I suggest to try this one first:
Image for ARM32 A-only device vanilla.
https://github.com/phhusson/treble_...lineage-v21/system-arm-aonly-vanilla-nosu.img
Just realised this device is running in 32bit mode.
Remember dmverity needs to be disabled so flashing Magisk is required.
Data also needs to be formatted (not wiped)
kapmino269 said:
What do you mean one ?
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
Are you mean lineage 16 ?
It wasn't boot too
---------- Post added at 11:35 AM ---------- Previous post was at 11:32 AM ----------
System installed and opengapps and boot.img changed by magisk
!!!!!what is the reason?
I said lineage isnot encrypted but I tried to flash disable encryption but all in vain.!!!!!
---------- Post added at 11:37 AM ---------- Previous post was at 11:35 AM ----------
Ok ,I will try
Click to expand...
Click to collapse
See my edit this device is running in 32bit mode.
kapmino269 said:
No 64bit man , img not flash if it was arm 32
Click to expand...
Click to collapse
What do you mean it does not flash? What error?
kapmino269 said:
Later,I tried flash opengappsarm64 it( didnot install) because s4 is arm 32 , yesterday I, i tried to install lineage without opengapps in j4 + Then I install opengapps arm64 8.1 it( installed ) but phone didnot boot to system .
[I mean from all the speach the phone is arm64 not arm 32]
---------- Post added at 12:18 PM ---------- Previous post was at 12:10 PM ----------
I tried install RR ,LINEAGE ALL NOT WORK
L: DIDNOT BOOT .
RR : DIDNOT INSTALL: get error 255.
I THINK THEY DOESNOT WORK ON DEVICE OR PHONE NEED ANOTHER BOOT.IMG
Sorry Do not you have this phone?
If you have it whynot tried and reply me you will be
Better than me.
---------- Post added at 12:33 PM ---------- Previous post was at 12:18 PM ----------
Ok,i will try arm32
Click to expand...
Click to collapse
Ignore the specs the device is 64 bit capable, but runs in 32bit mode. The kernel is arm not arm64 and so is twrp.
I do not own this device as stated in my TWRP thread.
Boot.img is not required as everything that is manufacturer specific is in the vendor partition.
The whole purpose of project treble.
kapmino269 said:
P1:
Click to expand...
Click to collapse
Yep you need to FORMAT(not wipe) data with twrp to decrypt data then install magisk.
kapmino269 said:
ok please give me 5 minutes.
---------- Post added at 02:15 PM ---------- Previous post was at 02:09 PM ----------
Device reboot to recovery said decrypt Data enter password
Click to expand...
Click to collapse
Are you sure you are formatting and not wiping? This is imperative. It will ask you to type yes. Then immediately flash magisk as this will both disable dmverity and prevent re-encryption.
kapmino269 said:
P:
Click to expand...
Click to collapse
It's only saying that because data has become encrypted or is not mountable.
Formatting should remove the encryption and magisk should patch the fstab to prevent further encryption unless something else is amiss here.
Also do not set any pin or password at first boot.
Are you absolutely sure you are formatting in TWRP?
Can you mount data?
http://xiaomitips.com/media/2016/07/Format-Data-TWRP.png
kapmino269 said:
A-.After install system img :-
1 -I used format data and write yes.
2- I install magisk .
After that i could mount data and see its file i rememver it was there one file 'media'
B-After reboot system :-
-System boot like the picture i send you but System didn't open still make lineage boot shape .
-then phone reboot to recovery to decrypt data but i choose once cancel then i see data it was mounted and its file in picture :
Can you sent me your email and sent your whatsapp to send you videos and you see the error man because vedio uploading 3minutes take 2hours and 1:59minute take 1hour.
please man
But what is the reason if data mounted and countain files???
My mail : [email protected]
Click to expand...
Click to collapse
How long are you waiting for lineage to boot? Sometimes it can take up to 10 minutes or more.
kapmino269 said:
for long time I let it but the phone didn't open
it auto Reboot to recovery
---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------
Please send me your WhatsApp please to send you the videos
---------- Post added at 09:49 PM ---------- Previous post was at 09:13 PM ----------
If you don't send your whatapp reply my I won't be annoyed.
Click to expand...
Click to collapse
I don't have WhatsApp and I'd prefer to keep everything documented on the forum.
I'm guessing maybe there is an issue with the rom itself.
You could try it without magisk, but I suspect it might not boot if you overwrite the vendor partition.
However there are plenty of other GSI'S you can try. Maybe you'll get lucky with one?
kapmino269 said:
RR ALSO REBOOT TO RECOVERY I THINK THERE IS SOMETHING IN PHONE WE Don't KNOW
---------- Post added at 08:50 AM ---------- Previous post was at 08:27 AM ----------
Is imges work for somw devices only ?
Click to expand...
Click to collapse
Can you run treble check from Google play and report if it comes back enabled?
kapmino269 said:
P:
Click to expand...
Click to collapse
There is a user in the J6+ forum that managed to install the Pixel experience rom. Considering they are practically the same device it may work.
However I think he had issues with mobile data.
kapmino269 said:
1 - Send my the url of thread
2 - Please how to know block of device like ( 2sdcard partition recovery system data ) and the necessary of apps and email owndata where partiton
Is df linux command will show me the blocks because
Since last year when I format 2p of sdcard the sdcard formatted (1p,2p) all please reply me how to get blocks.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=78484627&postcount=24
ls -laR dev/block
Don't panic your imei is probably fine. It's just the rom having issues with the RIL.
Restoring the stock rom should fix it.
Which rom did you install?
kapmino269 said:
Pixel experince treble rom p
:https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
---------- Post added at 04:38 PM ---------- Previous post was at 03:59 PM ----------
issue2 hidden wifi solved
: I had to change wlan advanced option hidden network
Click to expand...
Click to collapse
Might be worth trying Pixel experience 8.1 now that you know this rom boots?
Also I would try maybe not installing Magisk and see if it boots.
Root can break mobile data on Samsungs due to Defex security.
Also if you have your twrp backup restore the modem.