Hi, I am sharing my Nougat ROM for LG-P880 with the XDA community. As a tribute to the original @MoltenMotherBoard, it will continue to be named as such.
AFH download:
https://www.androidfilehost.com/?w=files&flid=109853
ChangeLog
20180122
- Android-7.1.2_r36 (N2G48H)
- kernel
* Optimized kswapd based on kernel-msm/3.10/Bullhead
- Tuned extra_free_kbytes to 4 screen buffers
- Reduced I/O read_ahead_kb from 2048 to 256 for better latency
- Set dalvik.vm.dex2oat-thread = 2
Complete changelog
https://www.androidfilehost.com/?w=files&flid=109853
SELinux for Nougat
SELinux in Nougat has been hardened to never allow text relocation for executables. This is the only rule that we had to relax to enable pre-KitKat blobs to run.
To enable SELinux Enforcing, do this from recovery
Code:
$ adb shell mount /data
$ adb shell touch /data/.selinux
$ adb shell umount /data
Known issues
- MHL not working
- Display freeze on Cast Screen disconnect
- Widevine DRM not working
Broken AOSP components
- Clock
- Browser2
- Music
- Webview
Installation
You need to have custom recovery that can flash multiple zip files without having the reboot. I personally use the official CWM 6.0.4.5 so the instructions will be based on that with no external SD.
>Coming from other ROMs
- wipe userdata/cache
- format /system
- apply ROM zip
- apply Gapps zip ...or more Gapps if using modular Gapps
- format /data and /data/media
- reboot
>Coming from the same ROM
- format /cache
- format /system
- apply ROM zip
- apply Gapps zip ...or more Gapps if using modular Gapps
- reboot
Recommended Gapps is OpenGapps stock. Default webview provider is Google WebView. Please make sure your Gapps include this. Attached you will see my Gapps config.
This is based on Grouper blobs, so as usual barcode/QR scanning will not work and will not consider this as bug. However, Grouper blobs works with Screen Cast, which for me, is more useful than barcode/QR code scanning.
Let the testing begin!!!:fingers-crossed::fingers-crossed::fingers-crossed:
Kernel
Kernel https://github.com/CyanogenMod/lge-kernel-p880/tree/cm-12.1
See attached for patches
Code:
commit 413b3fc527c086450f28acbe92893c71e73ad5b6
Author: demetris <[email protected]>
Date: Wed Nov 4 00:39:13 2015 +0200
Use "git am -3" for .patch files
Use "git apply" for .diff files.
Reserved another
Different installation hmmm Thanks for everything csk1jw
Use TWRP 3.0.2.0 and do the recommend wipes .Have the zip files on a EX sdcard.
By flashing get messages "unknow command log" in red letters
Try to install open gapps for 7.0 beta pico and get errorcode 20 .Witch gapps can i use ?
Flash without gapps and get also the messages in red letters,but
boot normally and it seems working good fast and smooth :good:
Try copy the zip files for gapps to intern sd.In recovery can flash gapps and webview,
clean dalvik/cache , reboot but cant not open playstore
Regards
Can anyone provide me touch recovery for flashing this ROM.
Also need gapps for this ROM, I am unable to access some sites in my country (Kingdom Of Saudi Arabia).
Please provide me touch recovery for this ROM and link for Gapps.
Edit: Attached CWM Touch Recovery v6.0.4.5
Anyone up for helping me????
Salman Al-Badgail said:
Anyone up for helping me????
Click to expand...
Click to collapse
Here is a link for gapps 7.0 stock:
https://www.dropbox.com/s/r4uxxnqkfcxvc6c/open_gapps-arm-7.0-stock-20160910.zip?dl=0
Here is the latest twrp recovery. Please confirm that this is a touch recovery, if it is. I'm sticking with CWM 6.0.4.5. and don't wanna flash TWRP now.
https://www.dropbox.com/s/rq4xiya446h0mgo/twrp-3.0.2-0-p880.img?dl=0
Phil_Smith said:
Here is a link for gapps 7.0 stock:
https://www.dropbox.com/s/r4uxxnqkfcxvc6c/open_gapps-arm-7.0-stock-20160910.zip?dl=0
Here is the latest twrp recovery. Please confirm that this is a touch recovery, if it is. I'm sticking with CWM 6.0.4.5. and don't wanna flash TWRP now.
https://www.dropbox.com/s/rq4xiya446h0mgo/twrp-3.0.2-0-p880.img?dl=0
Click to expand...
Click to collapse
@Phil _Smith
I use TWRP 3.0.2.0 .How get you the stock gapps to work? I can flash,but googleservices is not working !!
sourly64 said:
@Phil _Smith
I use TWRP 3.0.2.0 .How get you the stock gapps to work? I can flash,but googleservices is not working !!
Click to expand...
Click to collapse
I suggest you try CWM 6.0.4.5.
I remember that there always had been some problems with TWRP and AOSP-based ROMs.
---------- Post added at 07:27 PM ---------- Previous post was at 06:41 PM ----------
Is there any chance to get the xposed framework to work on this rom? Or is there simply no version available for android 7.0?
Phil_Smith said:
I suggest you try CWM 6.0.4.5.
I remember that there always had been some problems with TWRP and AOSP-based ROMs.
---------- Post added at 07:27 PM ---------- Previous post was at 06:41 PM ----------
Is there any chance to get the xposed framework to work on this rom? Or is there simply no version available for android 7.0?
Click to expand...
Click to collapse
Please do provide me CWM 6.0.4.5.
Thanks
Salman Al-Badgail said:
Please do provide me CWM 6.0.4.5.
Thanks
Click to expand...
Click to collapse
Here you are, sir! Hope you got adb working, as I only found this as an .img
(For myself I use Rom Manager).
https://www.dropbox.com/s/7kpdaoobfizmlum/cwm_6.0.4.5.img?dl=0
Edit: Ah, but I remember that flashing .img files is easy via twrp (a little bit ironic)
Phil_Smith said:
Here you are, sir! Hope you got adb working, as I only found this as an .img
(For myself I use Rom Manager).
https://www.dropbox.com/s/7kpdaoobfizmlum/cwm_6.0.4.5.img?dl=0
Click to expand...
Click to collapse
Thanks for providing me, many sites are blocked by govt here this is only the reason I am troubling you. Sorry.
Adb is working fine. Thanks again @Phil_Smith
---------- Post added at 11:16 PM ---------- Previous post was at 11:11 PM ----------
I found CWM Touch Recovery (6.0.4.5) HERE
I attached CWM Touch 6.0.4.5 (please do check)
Edit: Attachment Not working
Salman Al-Badgail said:
Thanks for providing me, many sites are blocked by govt here this is only the reason I am troubling you. Sorry.
Adb is working fine. Thanks again @Phil_Smith
---------- Post added at 11:16 PM ---------- Previous post was at 11:11 PM ----------
I found CWM Touch Recovery (6.0.4.5) HERE
Click to expand...
Click to collapse
No problem, I know - I read your previous post
Bluetooth does not work for me. The device is detected properly, but then there is no sound playing from my external audio speaker. Can anyone comfirm the Bluetooth issue?
Phil_Smith said:
Bluetooth does not work for me. The device is detected properly, but then there is no sound playing from my external audio speaker. Can anyone comfirm the Bluetooth issue?
Click to expand...
Click to collapse
Confirmed. Will investigate. Device paired and connected but no sound.
It is too slow on my device
fukuli053 said:
It is too slow on my device
Click to expand...
Click to collapse
Give it a couple of shots (that is reboots). At first nothing worked for me eighter, but it gets stable and really fast after like 4 restarts or so!
fukuli053 said:
It is too slow on my device
Click to expand...
Click to collapse
Well, it can't be. Nougat UX is faster than Marshmallow.
What's your Gapps installation?
Related
Official nightlies are up for our device's:
Scorpion (LTE): http://download.cyanogenmod.org/?device=scorpion
Scorpion (Wifi): http://download.cyanogenmod.org/?device=scorpion_windy
TWRP Installation:
You can install TWRP through ADB or Terminal Emulator app. Thanks to ejdan for finding this!
ADB:
Before you begin:
- Download TWRP:
Code:
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/WiFi%20-%20SGP61x/twrp.img"]WiFi - SGP61x[/URL]
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/LTE%20-%20SGP62x//twrp.img"]LTE - SGP62x[/URL] (Credits to [B]der_bert[/B] for making this)
- set Root access to "Apps and ADB" in Developer options.
- set USB Debugging Mode to "ON" in Developer options.
Instructions:
1. Put twrp.img in the root of your Z3TC.
2. Open command prompt and go to the location where ADB.exe is.
3. Start an ADB shell:
Code:
adb shell
4. Gain root access:
Code:
su
5. Flash TWRP on FOTAKernel partition
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
6. Reboot to recovery and you would see TWRP.
Terminal Emulator:
Before you begin:
- Download TWRP:
Code:
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/WiFi%20-%20SGP61x/twrp.img"]WiFi - SGP61x[/URL]
[URL="http://qzerno.troxit.nl/android/misc/TWRP/Sony%20Xperia%20Z3%20Tablet%20Compact/LTE%20-%20SGP62x//twrp.img"]LTE - SGP62x[/URL] (Credits to [B]der_bert[/B] for making this)
- set Root access to "Apps" in Developer options.
- set Local terminal to "ON" in Developer options. (If you don't have this option download then Terminal Emulator from the Play Store)
Instructions:
1. Put twrp.img in the root of your Z3TC.
2. Open the app Terminal or Terminal Emulator
3. Gain root access:
Code:
su
4. Flash TWRP on FOTAKernel partition
Code:
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
5. Reboot to recovery and you would see TWRP.
Version Information:
Status: Discontinued
Created 2014-12-24
Last Updated 2015-03-25
Nice? any plans for LTE model?
Lte model is merged into cm sources so it should work
Will try to get up an simple kernel with intelliplug and so on
moritz31 said:
Lte model is merged into cm sources so it should work
Will try to get up an simple kernel with intelliplug and so on
Click to expand...
Click to collapse
I'd be interested and thanks!
chaostimmy said:
Nice? any plans for LTE model?
Click to expand...
Click to collapse
I'm building right now for LTE but I can't test this builds.
EDIT: LTE Build is up!
I have tried the Wifi version and it seems to work fine.
First I had a few restarts when locking the screen but it seems to have fixed itself now. Maybe because I disabled double tap to sleep/wake?
SD card is not mounted. Is there a way to fix it? The card is listed in /proc/partitions so it should be possible to fix with a proper fstab.
ejdan said:
SD card is not mounted. Is there a way to fix it? The card is listed in /proc/partitions so it should be possible to fix with a proper fstab.
Click to expand...
Click to collapse
I compared fstab.qcom in CM12 with the stock kernel and found a difference. The stock kernel has /devices/msm_sdcc.3/mmc_host for sdcard1 but CM12 has /devices/msm_sdcc.2/mmc_host
I changed '2' to '3' in the ramdisk and now SD card works. I have attached my modified kernel image. Unpack the zip file and flash cm12-sdcard1-fix.img using fastboot. This kernel is taken from cm-12-20141225-0800-UNOFFICIAL-scorpion_windy.zip
Qzerno said:
I'm building right now for LTE but I can't test this builds.
EDIT: LTE Build is up!
Click to expand...
Click to collapse
Great, thank you but I could not install it. In TWRP it says:
"This package is for device: SGP621, SGP641, SGP651, scorpio; this device is scorpion_windy."
It's not. I have the LTE version, SGP621 aka Scorpion.
Thanks for the builds! What has everyone flashed?
Home Launcher
Is Trebuchet included in these builds? Ive flashed todays (26th) build and am I'm just getting the options for Google Now and Nova Launcher.
---------- Post added at 08:09 PM ---------- Previous post was at 07:55 PM ----------
Any chance of making the kernel flashable?
BUG REPORT: double tap to wake is not working
ejdan said:
I compared fstab.qcom in CM12 with the stock kernel and found a difference. The stock kernel has /devices/msm_sdcc.3/mmc_host for sdcard1 but CM12 has /devices/msm_sdcc.2/mmc_host
I changed '2' to '3' in the ramdisk and now SD card works. I have attached my modified kernel image. Unpack the zip file and flash cm12-sdcard1-fix.img using fastboot. This kernel is taken from cm-12-20141225-0800-UNOFFICIAL-scorpion_windy.zip
Click to expand...
Click to collapse
Nice, thanks for fixing this. Do you maybe know which file in the source need to edit to get this works? then I can commit it to CyanogenMod.
Noe_S said:
Great, thank you but I could not install it. In TWRP it says:
"This package is for device: SGP621, SGP641, SGP651, scorpio; this device is scorpion_windy."
It's not. I have the LTE version, SGP621 aka Scorpion.
Click to expand...
Click to collapse
The recovery (TWRP) need to get a build separately for the scorpion (SGP621), then it should work.
I will search for a alternative installation method for the scorpion.
xan_asmodi said:
Is Trebuchet included in these builds? Ive flashed todays (26th) build and am I'm just getting the options for Google Now and Nova Launcher.
---------- Post added at 08:09 PM ---------- Previous post was at 07:55 PM ----------
Any chance of making the kernel flashable?
Click to expand...
Click to collapse
Yes, Trebuchet is included in these build, PA Gapps remove Trebuchet I can upload Trebuchet separately if you want.
I want to make the kernel flashable but that has not yet succeeded.
xan_asmodi said:
BUG REPORT: double tap to wake is not working
Click to expand...
Click to collapse
Thanks for the bug report. I also noticed this. I will add this in the OP.
Qzerno said:
Nice, thanks for fixing this. Do you maybe know which file in the source need to edit to get this works? then I can commit it to CyanogenMod.
Click to expand...
Click to collapse
I made a pull request on Github. Not sure if it is the correct way to do it
https://github.com/CyanogenMod/android_device_sony_scorpion_windy/pull/1
The file fstab.qcom is in rootdir. Because of the overlay (scorpion is based on shinano common) I had to add a new file. I have not built from source so I have not checked that it is working but manually updating the ramdisk did work.
ejdan said:
I made a pull request on Github. Not sure if it is the correct way to do it
https://github.com/CyanogenMod/android_device_sony_scorpion_windy/pull/1
The file fstab.qcom is in rootdir. Because of the overlay (scorpion is based on shinano common) I had to add a new file. I have not built from source so I have not checked that it is working but manually updating the ramdisk did work.
Click to expand...
Click to collapse
Ahh that's why I can't find that file. I have add the file local and building right now.
EDIT: Yeah I have 10 posts!
Qzerno said:
Ahh that's why I can't find that file. I have add the file local and building right now.
Click to expand...
Click to collapse
You may have to add the file to a makefile somewhere but lets see how it goes.
Qzerno said:
Thanks for the bug report. I also noticed this. I will add this in the OP.
Click to expand...
Click to collapse
Your welcome Should I post stuff as I find them or PM you so you can update the OP?
Could you post trebuchet separately? That'd be a great help. I think the PA guys need to incorporate Aroma installer, because I don't think Google Now Launcher is as good as Trebuchet.
Keep up the good work, hopefully we'll get the camera drivers soon. I'll look to see if the camera module is the same as the Z2 tab, if so we may not need to wait, just take them from the other repository.
Oh, one more thing...
Xposed doesn't install through a combination of crap cyanogenmod recovery and other stuff which I can't profess to understand
Edit: I now understand that this is because of the shift from Dalvik runtime to ART. Getting CM12 to run Xposed will either require reverting to Dalvik (is this possible?) or waiting for the Xposed devs to rewrite Xposed.
When updating to a new nightly, you can flash over the previous build. When you do you need to reflash the ram disk/kernel update.
BUG REPORT: Rebooting into recovery from power menu doesn't work. Requires manual intervention at 'Sony screen'/purple LED.
Intalled it and works fine as far as i can tell. Can´t move Apps to he sd card thogh (not enough space error) but that might be because of that known sd issue. I have general access to the sd though.
Cheers and thanks
Chris
MasterTRL said:
Intalled it and works fine as far as i can tell. Can´t move Apps to he sd card thogh (not enough space error) but that might be because of that known sd issue. I have general access to the sd though.
Cheers and thanks
Chris
Click to expand...
Click to collapse
What nightly are you using and did you flash the sd card fix?
Code:
#include
/*
* 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.
*/
NOTE:
THIS IS A DEVELOPMENT THREAD.
BUILDS ARE INTENDED FOR ADVANCED USERS, SO THEY CAN TEST AND GIVE FEEDBACK.
FEATURE REQUESTS WILL BE IGNORED, THIS IS PLAIN CYANOGENMOD.
Also, there are sister threads for working on yuga, odin and dogo.
Changes:
- Jan 6: Initial release
- Jan 15: various fusion3 updates, added pollux build
- Jan 19: kernel updates, selinux changes
- Jan 28: various graphics, kernel, WiFi improvements, fixed GPS on windy
- Jan 30: WiFi MAC address fix, various optimizations, IR blaster test
- Feb 3: kernel updates, audio HAL modernization
- Feb 9: WiFi changes
- Feb 13: sysmonitor updates, volume rocker wakeup, camera focus changes, cleanups
- Feb 26: F2FS for cache and userdata
- Mar 3: smooth boot animation
- Apr 3: first 12.1 build
- Apr 20: fix for 3g data (pollux)
- Apr 22: Android 5.1.1
- Apr 24: update init, cpu governor
- Apr 28: more cpu and gpu governor updates, wifi fixes
- May 1: gpu gov and wifi updates
- May 5: app2sd fixes, selinux updates, fixed power hal, OSS THERMAL MGMT
- May 7: other wifi drivers, selinux updates
- May 10: plethora of core kernel and platform updates, init changes
- May 14: scheduler and platform updates
- May 21: reworked kernel configuration
- May 27: lollipop blobs, new sensor drivers, kernel updates
- June 30: fixes to ril, more lp updates
- July 7: fix booting into recovery by toggling volume keys
- Sep 10: (ahead of nightly!) bfq and fiops io schedulers (bfq as default), sony 5.1.1 blobs
- Mar 30: initial CM13 release
- Apr 6: latest cm fixes, kernel updates
- Apr 15: init updates, improved mac address handling, new camera app, audio fixes, clean-ups
- Apr 18: fix bt, wifi
- Apr 27: updated wifi driver, lz4 compression, new audio hal, updated gpu blobs
- May 2: fix wlan firmware loading, include new cm browser: gello
- May 9: mac addr fixes, bluetooth fixes, camera wrapper improvements
- May 18: f2fs fix attempt, kernel 3.4.112, init update
- May 23: f2fs fix, ipv6 fix
- May 25: start nightlies
All builds are synchronized with the latest CM tree.
For the specific updates to fusion3 and pollux, see the source link below!
Download:
CM-13.0 nightlies are available:
pollux: Official download site
pollux_windy: Official download site
This thread will however remain the prime location for testing new stuff and support on pollux/pollux_windy.
Installation:
If you have anything other than CyanogenMod on your device, do a full wipe, and get compatible gapps!
F2FS support: take a look here
Testing:
Some very important "rules" for this:
- Run unmodified versions (no FOTA recovery, no modified kernel, no Xposed framework, etc.)
- Please dont post "X isnt working" or "random reboots" - provide LOGS for each report you post here. This thread is actually meant for users who are capable of gathering and providing logs, so after a reboot, provide last_kmsg, and for all other problems, dmesg and logcat at the very least.
- If you can reproduce your problem, you might want to increase the logging level before posting it here, which will increase chances of me finding the problem.
I will have to ignore all other "problem reports" as they are essentially useless.
Source:
If you are willing (and able) to help, check out the patch sets, test them for the respective projects (fusion3 is also yuga, odin, and so on).
http://review.cyanogenmod.org
This is like a thunder in a clear sky.
Downloading! [emoji3]
At work, can't test just yet.
It is very nice to see that people keep supporting this great tablet by working on new LP roms.
Thanks for that. :good:
Jequan said:
At work, can't test just yet.
It is very nice to see that people keep supporting this great tablet by working on new LP roms.
Thanks for that. :good:
Click to expand...
Click to collapse
I'll let you know in 30 minutes or so how's this build.
---------- Post added at 01:52 PM ---------- Previous post was at 12:55 PM ----------
First impressions:
Rom boots fine
Sound crisp and loud! Awesome!
Cpu works as it should. Unused cores get stopped.
Kernel has enough governors.
Double tap to wake works fine.
I'll keep this, definitively
Thanks heaps @qsnc
Let the party begin :-d
@Alx31TLse you might be interested in this
varben said:
First impressions:
Rom boots fine
Sound crisp and loud! Awesome!
Cpu works as it should. Unused cores get stopped.
Kernel has enough governors.
Double tap to wake works fine.
I'll keep this, definitively
Thanks heaps @qsnc
Let the party begin :-d
Click to expand...
Click to collapse
I can confirm all this.
Great work!!!
moesus said:
I can confirm all this.
Great work!!!
Click to expand...
Click to collapse
does gps work?
anyway this is the first daily usable android 5 rom
varben said:
I'll let you know in 30 minutes or so how's this build.
---------- Post added at 01:52 PM ---------- Previous post was at 12:55 PM ----------
First impressions:
Rom boots fine
Sound crisp and loud! Awesome!
Cpu works as it should. Unused cores get stopped.
Kernel has enough governors.
Double tap to wake works fine.
I'll keep this, definitively
Thanks heaps @qsnc
Let the party begin :-d
@Alx31TLse you might be interested in this
Click to expand...
Click to collapse
Oh wow! That's great news. Once again flashing time when i get home!
Awesome work everything is gold atm!
See some apps have been changed both the aosp browser and the music app both got material design. And hold the recents button swell for app switching its really fluid
EDIT: just so people know you have to enable root access via the dev menu now its not enabled by default anymore.
Titanium backs up fine, but when I tried to restore that backup, it wouldn't work... Just gets stuck at the restoring screen. I've had the same issue on my phone when updating to lollipop.
Resolved the problem by installing super su from the play store. Just for anyone experiencing this as well!
How to install from Stock?
Sorry to be a bit of a noob, but I'm trying to install this (CM12) on my pollux_windy in place of a stock Sony ROM (292).
I'm following some standard instructions in the CM Wiki which involves flashing the boot.img (worked :good and then going into CWM recovery (worked :good.
The problem occurs at step 8 in the above wiki, which requires the use of "sideload" or "push & install".
I can't see the required commands in the CWM recovery...no "install from Zip", no "mounts and storage", etc...and I'm not sure if ADB is working in recovery either (ADB is working with the device booted up in stock ROM).
Any ideas or alternative ways? How are you guys installing?
I've done a lot of custom ROM installation on various devices over the last few years...but I've got out of practice recently so I'm stuck
Just flashed cm-12-20150106-UNOFFICIAL-pollux_windy.zip a couple of hours ago and so far these have been my results:
WiFi: Works.
Bluetooth: Works.
NFC: Works.
GPS: Doesn't work.
Sound: Works. Tested with system sounds and Spotify.
CPU Cores: Works.
Video Playback: Works. MX Player plays 1080p vids without issues. YouTube plays 1080p perfectly with sound.
Smoothness: It's crazy smooth. A thing of beauty.
Double Tap to Wake: Works.
Double Tap to Sleep: Works.
Stability: So far, no reboots, no stuttering or hangs.
Thanks so much, qsnc, I'll definitely keep this as a daily driver. It feels like a new device! Subscribed to thread and eager to test more of your work.
Any Screenshots ?
Gesendet von meinem D5503 mit Tapatalk
GretaLewd said:
Sorry to be a bit of a noob, but I'm trying to install this (CM12) on my pollux_windy in place of a stock Sony ROM (292).
I'm following some standard instructions in the CM Wiki which involves flashing the boot.img (worked :good and then going into CWM recovery (worked :good.
The problem occurs at step 8 in the above wiki, which requires the use of "sideload" or "push & install".
I can't see the required commands in the CWM recovery...and I'm not sure if ADB is working in recovery either (ADB is working with thedevice booted up in stock ROM).
Any ideas or alternative ways? How are you guys installing?
I've done a lot of custom ROM installation on various devices over the last few years...but I've got out of practice recently so I'm stuck
Click to expand...
Click to collapse
I would suggest you use twrp recovery. It will be easier flash files.
You can follow the instructions here:
http://teamw.in/project/twrp2/185
Or, since you are on stock install twrp from here
http://forum.xda-developers.com/showthread.php?t=2261606
---------- Post added at 08:58 PM ---------- Previous post was at 08:57 PM ----------
androidseb said:
Any Screenshots ?
Gesendet von meinem D5503 mit Tapatalk
Click to expand...
Click to collapse
It's just plain cm12.
GretaLewd said:
Sorry to be a bit of a noob, but I'm trying to install this (CM12) on my pollux_windy in place of a stock Sony ROM (292).
I'm following some standard instructions in the CM Wiki which involves flashing the boot.img (worked :good and then going into CWM recovery (worked :good.
The problem occurs at step 8 in the above wiki, which requires the use of "sideload" or "push & install".
I can't see the required commands in the CWM recovery...no "install from Zip", no "mounts and storage", etc...and I'm not sure if ADB is working in recovery either (ADB is working with the device booted up in stock ROM).
Any ideas or alternative ways? How are you guys installing?
I've done a lot of custom ROM installation on various devices over the last few years...but I've got out of practice recently so I'm stuck
Click to expand...
Click to collapse
You don't need adb/Fastboot after flashing the boot.img and for installing the ROM.
EDIT: Don't forget before you do any of the below to go into the recovery and backup the Sony ROM!
As long as you put this ROMs Zip file on the storage of the tablet before you installed the recovery (because the stock ROM won't boot on a CM Boot.img) If you didn't you'll need to go get a Boot.img that will allow your tablet to boot again into the stock sony ROM then put the ROM Zip file and Gapps files on the internal storage.
After that re-flash the Boot.img for this go back into recovery (select wipe Data then wipe cache partition) and then select apply update and select from internal storage. Find the Zip file and install it then install the Gapps.
GretaLewd said:
Sorry to be a bit of a noob, but I'm trying to install this (CM12) on my pollux_windy in place of a stock Sony ROM (292).
I'm following some standard instructions in the CM Wiki which involves flashing the boot.img (worked :good and then going into CWM recovery (worked :good.
The problem occurs at step 8 in the above wiki, which requires the use of "sideload" or "push & install".
I can't see the required commands in the CWM recovery...no "install from Zip", etc...and I'm not sure if ADB is working in recovery either (ADB is working with the device booted up in stock ROM).
Any ideas or alternative ways? How are you guys installing?
I've done a lot of custom ROM installation on various devices over the last few years...but I've got out of practice recently so I'm stuck
Click to expand...
Click to collapse
That part that you're trying to do is just about putting the .zip in the internal storage to flash it.
I advise you to flash in fastboot the boot.img from a CM11 nightly, that way you get a CWM recovery where you can mount Mass Storage there and then transfer the cm-12-20150106-UNOFFICIAL-pollux_windy.zip from OP (and the GApps package), from your PC to the tablet.
Then just wipe data, cache, format /system and install the zips normally.
If for some reason Mass Storage isn't working, flash with Flashtools stock firmware and copy the files normally, then repeat the steps I mentioned.
---------- Post added at 03:04 PM ---------- Previous post was at 03:02 PM ----------
Roxas598 said:
You don't need adb/Fastboot after flashing the boot.img and for installing the ROM.
As long as you put this ROMs Zip file on the storage of the tablet before you installed the recovery (because the stock ROM won't boot on a CM Boot.img) If you didn't you'll need to go get a Boot.img that will allow your tablet to boot again into the stock sony ROM then put the ROM Zip file and Gapps files on the internal storage.
After that re-flash the Boot.img for this go back into recovery (select wipe Data then wipe cache partition) and then select apply update and select from internal storage. Find the Zip file and install it then install the Gapps.
Click to expand...
Click to collapse
Oops, I'm sorry, Roxas, you posted faster than I did. Well, now he has confirmed the info. Let's hope he can manage to flash it. If not, let us know.
pangiotis24 said:
does gps work?
anyway this is the first daily usable android 5 rom
Click to expand...
Click to collapse
GPS doesn't work for me. (SGP311)
//tried 3times (clean flash + AndroITS)
//CM recovery is also not fully working for me (can't do anything) -- /can't mount /misc partition bla bla)
@qsnc did fine job, but i'm sticking to stable Omni for now.
Thanks :good:
Flashing from stock
Thanks for all your replies with help. I will give it another go.
When I got stuck I went back to stock (flashed an ftf with flashtool) so I'll start over again :fingers-crossed:
Unbelievable. This rom comes out of of nowhere as a first release download. I have yet to find anything that is broken.
As i see it this is the rom to have on the tab z from now on!
Thank you very much!
SnZ said:
GPS doesn't work for me. (SGP311)
//tried 3times (clean flash + AndroITS)
//CM recovery is also not fully working for me (can't do anything) -- /can't mount /misc partition bla bla)
@qsnc did fine job, but i'm sticking to stable Omni for now.
Thanks :good:
Click to expand...
Click to collapse
You're right about GPS, I was too quick to say that it was working. Just tested it and yeah, it's not there. For now it's not a deal breaker for me, so I'll stay with this ROM. Thanks anyway for pointing it out, I'll correct my previous post.
Any Chance to make HDMI run ??
CM11 never had a functional HDMI Output...
Here's the Unofficial TWRP recovery
Developed by @MICKEY_ANDRO100
I have tested it and it's working perfectly
How to Install
1. Copy Recovery Zip in SD card
2. Reboot In Recovery Mode (Make sure you have Unlocked Bootloader)
3. Click on Install and locate to Recovery Zip.
4 Go Back and Reboot the Recovery again to make sure it's Done successfully.
Done ?????
Contributor @MICKEY_ANDRO100 for developing TWRP recovery @DeepSahota for Zip
Status: Stable
Downloads
Link :- https://drive.google.com/file/d/0B5wsXNzlO7M1RmppSDhkdFhSQUU/view?usp=drivesdk
Thanks for suggesting my recovery. and I don't encourage Mirrors without my permission.
1cefire built is the best
Mount usb storage feature is missing. As of now 3.0.0.0 is working fine.
muthur774 said:
Mount usb storage feature is missing. As of now 3.0.0.0 is working fine.
Click to expand...
Click to collapse
New TWRP 3.0.2-3 RECOVERY MORE STABLE AND FINE. AS PER ME ALL ISSUES FIXED EVEN WITH CHANGELOGS
http://forum.xda-developers.com/cro.../unofffical-twrp-3-0-2-0-android-one-t3358636
---------- Post added at 03:13 AM ---------- Previous post was at 03:11 AM ----------
Minions_Army said:
1cefire built is the best
Click to expand...
Click to collapse
Sir NEW TWRP Try it OUT, As per me in STABLE, NO BUGS FOUND I HAVE UPLOADED ON 14 itself.
http://forum.xda-developers.com/cro.../unofffical-twrp-3-0-2-0-android-one-t3358636
Hello,
I´m trying to install CM11 in my GT-9070 via CWM and the instalation failed.
imgur.com/CYz5Gts
can i install CM11 Via ODIN?
Anyone can help me?
Have some threath that explains how i can do this?
I have Solved STATUS 7 Problem but i hava another....
imgur.com/U9duuX8
Some Help?
Install this: https://www.dropbox.com/s/h8rmmg85vc6odxi/CM11.zip?dl=1
It's the same rom, but with modified installation script and gapps already included, so you will get no errors.
Very thanks. You great
successfully instaled.
I am testing the version right now.
You're welcome.
And if you'll find the rom to be not good enough, you will be able to easily switch to a different rom without getting errors, thanks to the TWRP recovery now installed on your device.
very good.
THANKS
you saved my life.
Now you have 52 thanks xD
dark_fenix said:
you saved my life.
Now you have 52 thanks xD
Click to expand...
Click to collapse
i also have a similar problem. now downloading the file. what version of cm11 is this?
---------- Post added at 03:54 PM ---------- Previous post was at 03:52 PM ----------
Cassiusss said:
You're welcome.
And if you'll find the rom to be not good enough, you will be able to easily switch to a different rom without getting errors, thanks to the TWRP recovery now installed on your device.
Click to expand...
Click to collapse
thanks for your help..i too was having the same problem. unfortunately my queries to a particular dev was left unanswered.
i'm trying to understand the problem. can you explain why we get such errors?
thanks a million!
It's the latest Epirex's CyanogenMod 11 with this modifications:
- gapps included
- many system apps removed
- Nova Launcher as default launcher
- call recording enabled for all regions
- Android Marshmallow boot animation
- it can be installed without root and with temp cwm
These errors can caused by:
- old recovery not capable of execute new rom's update-binary
- fail to read device's ID from build.prop
The rom that i've suggested doesn't check build.prop and use basic update-binary compatible with every custom recovery.
Cassiusss said:
It's the latest Epirex's CyanogenMod 11 with this modifications:
- gapps included
- many system apps removed
- Nova Launcher as default launcher
- call recording enabled for all regions
- Android Marshmallow boot animation
- it can be installed without root and with temp cwm
These errors can caused by:
- old recovery not capable of execute new rom's update-binary
- fail to read device's ID from build.prop
The rom that i've suggested doesn't check build.prop and use basic update-binary compatible with every custom recovery.
Click to expand...
Click to collapse
Thanks for your reply. Thank you for the cm11 file too?
Hello people,
I am working on this project all alone, if anyone want to help, please do, as I don't have much experience. It's quite tough to work on this without much experience :|
CURRENT STATUS: TESTING
Current Logs: https://gist.github.com/SscSPs/f5505f9aa0ed01651c1579fc342c1e3b
Nolekat logs: https://gist.github.com/SscSPs/2b732f7dd9e9d4de17b265602dd854e8
New Update(7th Aug 2017):
Looks like the graphics drive is not being loaded at all, the Galcore is not being initialized, may be there's more that's missing, but that is the only thing I can see missing from the Kernel logs.
I've added kmsg from nolekat (till it boots up) so if anyone want to, they can compare the differences. So far, i've seen just the GPU driver not starting.
For Update logs, check Post #2.
For Install Instructions, check Post #3.
Now, I'd like to thank all of you guys for helping me in this, specially, to @Manuehlito for testing all the builds I've been unable to test by myself.
Thanks everyone
XDA:DevDB Information
LineageOS, ROM for the Samsung Galaxy Tab 3 7.0
Contributors
sscsps, gr8nole, laufersteppenwolf, more, list is big(they dont know i am continuing this work)
Source Code: [url]http://github.com/SamsungGalaxyTab3[/URL]
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Testing
Created 2017-06-14
Last Updated 2017-12-17
This post will contain list of all the updates and Milestones.
For more frequent updates and builds, join this telegram group: Tab 3 development
https://t.me/SamsungGalaxyTab3
Place for new builds: AndroidFileHost(link removed)
You can check it for new builds as I upload them. It'll probably be having all the non booting ones. I'll clear it up once we get it to boot.
UPDATE: 5 August 2017
Fourth build
I have tried a few things, the log present in op is from a build before this one, i need someone to test this one,
There's a lot of improvement from the last build that I posted here.
GDrive Link(link removed)
STATUS: NOT BOOTING
UPDATE: 23 July 2017
Third Build.
This build have a lot of improvement over the previous ones. I have successfully added SEPolicy v30 support in the kernel, so it is compatible with nougat at least in that aspect and have tried to fix the fstab.unknown issue.
I don't know yet if it boots or not, someone test it and provide logs. Read the first post for instructions of how to get logs.
It is available on the AndroidFileHost folder link provided above, or you can go directly to the file here: AndroidFileHost(link removed)
STATUS: NOT BOOTING
UPDATE: 17 July 2017
Second build.
Added T210 to flashable device list(but the name is yet lt023g/t211)(T210 users can flash it but might have a few extra things that are not needed on that device) This is done just to let users have a try.
Needs testers. I haven't been able to test it yet. Please try and report how it goes.
It is available here: GDrive Link(link removed)
STATUS: NOT BOOTING
UPDATE: 18 June 2017
First build succeeded.
It is available here: GDrive Link(link removed)
STATUS: NOT BOOTING
Reserved
INSTALLATION INSTRUCTIONS:
Okay, I think it is understood that this build is most likely not going to boot. If you want to install it and help me with making it bootable, go ahead and try to run it. Grab Logs and give them to me.
NOTE: it is highly recommended that you create a backup before flashing this. You would need it to recover.
If you have other plans, that's fine too, but I recommend to have a backup.
Steps to create a BACKUP:
1. Go to recovery
2. select backup
3. select all the partitions(if you don't want some partition, then you know better)
4. select storage where you want to save the backup.
5. swipe to backup.
it'll take a little while to back it all up, just wait and it'll be ready
Once you have created the backup, you are ready to Install, for that, you will have to first WIPE the data partition and system.
Steps to WIPE:
1. Go to recovery
2. Go to WIPE section.
3. Select data, and system. (DO NOT SELECT THE PARTITION THAT CONTAINS YOUR BACKUP)
4. swipe to start the WIPE process.
it'll takea little while to complete.
Now that you have wiped your system, follow these
Steps to Install the ROM:
1. Go to recovery, select "INSTALL",
2. find the zip file,
3. flash it.
4. reboot to system.
FETCHING LOGS
After installing the ROM, please explain how it goes, grab a logcat and/or last_kmsg
If the device boots,
Grab LOGCAT by following these steps:
1. connect the device to PC
2. open adb and check if the device is detected(run "adb devices", it should list your device there).
3. run this: adb shell logcat > logcat.txt
this will get the logcat in the file logcat.txt, located in the present working directory, you can change the name of that file if you want.
Provide this file.
grab LAST_KMSG by following these steps:
If the device doesn't boot, i.e. either stays on the SAMSUNG logo, or reboots back to recovery then follow these steps:
Reboot to recovery and follow these steps:
1. If it stayed on the SAMSUNG logo, Reboot to system once again, and let it stay as is for a while. and then reboot back to recovery.
2. connect the device to PC.
3. open ADB and ensure that the device is connected.
4. Run this: adb shell cat /proc/last_kmsg > last_kmsg.txt
this will get the last_kmsg in the file last_kmsg.txt, located in the present working directory, you can change the name if you want to.
provide this file.
After you are done taking logs, you might want to restore your backup, if you know how to, or have other plans, you are good to go, but if you need help,
Follow these steps to restore your system:
1. Go to recovery
2. Go to wipe and wipe system, data, cache
3. After wiping LineageOS off, Select Restore.
4. Select the storage location that you selected while creating the backup.
5. Select the backup that you want to restore(most likely, there will be just 1).
It'll take a while to restore, and after restoration is done, you can just reboot to system and it'll boot back to touchwhiz as nothing happened
Hmmm Well Hello I want to be a tester of your rom and btw what Is the status till now and if you release kernel,vendor,tree i will help sm-t211 community for bringing up many roms waiting for your reply
XiaomiDev said:
Hmmm Well Hello I want to be a tester of your rom and btw what Is the status till now and if you release kernel,vendor,tree i will help sm-t211 community for bringing up many roms waiting for your reply
Click to expand...
Click to collapse
Cool! I'll count you in for testing.
The current state is "not compiling". I am working on the device tree to make it compile for a start.
Yes, I have my device tree, vendor tree and kernel tree on my github, you can take a look if you want. but as i said, they are not working just yet.
If you can help me with making it workable, please do
I'll post the roomservice.xml soon so others can have same setup as mine. or can improve it.
Can you link me to rooting guide of SM-T211? Is it the same as SM-T210 or any other Tab 3 model?
sameer22 said:
Can you link me to rooting guide of SM-T211? Is it the same as SM-T210 or any other Tab 3 model?
Click to expand...
Click to collapse
Here you can find all for the Tab 3 7.0 Version. https://forum.xda-developers.com/showthread.php?t=2755532
Hi thanks for your hard work , what about sm-t116 ?
thank for dev, i'm already try to install and post the logcat to you and report any bugs later
one question where supose to be i'm post the logcat ?
sorry my languange
aditrodostress said:
thank for dev, i'm already try to install and post the logcat to you and report any bugs later
one question where supose to be i'm post the logcat ?
sorry my languange
Click to expand...
Click to collapse
upload the file containing it.
or use https://hastebin.com/ and provde link
rgsoussama said:
Hi thanks for your hard work , what about sm-t116 ?
Click to expand...
Click to collapse
I can work on it, but for start, i just need to get it to boot on one device at least.
I'll call you out once its booting for t211, so we can start working on t116 and other devices.
sscsps said:
I can work on it, but for start, i just need to get it to boot on one device at least.
I'll call you out once its booting for t211, so we can start working on t116 and other devices.
Click to expand...
Click to collapse
Ohh thanks bro, keep your good work up :good:
sscsps said:
upload the file containing it.
or use https://hastebin.com/ and provde link
Click to expand...
Click to collapse
Code:
installing update...
target: samsung/linage_lt023g/lt023g:7.1.2/NHJ47B/2c3386f0cc:userdebug/test-keys
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
cant install this package on top of incompatible data. Please try another package or run a factory reset
just run wipe data.factory reset , wipe cache parttition and wipe dalvik cache now installation running
Code:
installing update...
target: samsung/linage_lt023g/lt023g:7.1.2/NHJ47B/2c3386f0cc:userdebug/test-keys
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
patching system image unconditionaly
E:unknow comman (log)
E:unknow comman (log)
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
script succssed result was
install form sdcard complete
aditrodostress said:
Code:
installing update...
target: samsung/linage_lt023g/lt023g:7.1.2/NHJ47B/2c3386f0cc:userdebug/test-keys
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
cant install this package on top of incompatible data. Please try another package or run a factory reset
just run wipe data.factory reset , wipe cache parttition and wipe dalvik cache now installation running
Code:
installing update...
target: samsung/linage_lt023g/lt023g:7.1.2/NHJ47B/2c3386f0cc:userdebug/test-keys
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
patching system image unconditionaly
E:unknow comman (log)
E:unknow comman (log)
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
script succssed result was
install form sdcard complete
Click to expand...
Click to collapse
Thanks for the logs
Initial look says we definitely need to update the kernel.
Current kernel version is 3.4.5, i'll try to update it to 3.4.113 at least and will proceed from there.
Next test build will be available after that.
Will start the work on it from now on.
aditrodostress said:
Code:
installing update...
target: samsung/linage_lt023g/lt023g:7.1.2/NHJ47B/2c3386f0cc:userdebug/test-keys
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
cant install this package on top of incompatible data. Please try another package or run a factory reset
just run wipe data.factory reset , wipe cache parttition and wipe dalvik cache now installation running
Code:
installing update...
target: samsung/linage_lt023g/lt023g:7.1.2/NHJ47B/2c3386f0cc:userdebug/test-keys
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
patching system image unconditionaly
E:unknow comman (log)
E:unknow comman (log)
detected filesysytem ext4 for /dev/block/platform/sdhci-pxav3.2/by-name/system
script succssed result was
install form sdcard complete
Click to expand...
Click to collapse
btw, can you explain the boot process. did it stay stuck on the SAMSUNG flash screen, or rebooted again and again to the same state(SAMSUNG Flashscreen, or rebooted back to recovery?
sscsps said:
btw, can you explain the boot process. did it stay stuck on the SAMSUNG flash screen, or rebooted again and again to the same state(SAMSUNG Flashscreen, or rebooted back to recovery?
Click to expand...
Click to collapse
it just stuck on Samsung Galaxy Tab 3 screen.
i just can provide only last_kmsg.txt
bierma32 said:
Here you can find all for the Tab 3 7.0 Version. https://forum.xda-developers.com/showthread.php?t=2755532
Click to expand...
Click to collapse
Can't seem to find the rooting tutorial in this link, thanks for the files though
Will it work on 210 variant? Just asking cuz 211 is a 3g variant of 210. Glad to see that someone relesed 7.1 for this device. I tried to port it in past, but my PC is not enough powerful (random reboot), and my hard drive is too small.
Any screenshots?
And does it work for the SM-T210?
---------- Post added at 03:23 PM ---------- Previous post was at 03:04 PM ----------
Result: SM-T210
Doesn't work
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
Banan PL said:
Will it work on 210 variant? Just asking cuz 211 is a 3g variant of 210. Glad to see that someone relesed 7.1 for this device. I tried to port it in past, but my PC is not enough powerful (random reboot), and my hard drive is too small.
Click to expand...
Click to collapse
Don't worry!
After my exams (28/06/2017) I am free!
I have an SM-T210!
So I could easily port it!
---------- Post added at 03:29 PM ---------- Previous post was at 03:24 PM ----------
Here is the Error of ROM on SM-T210
E:unkown command [log]
Updater process ended with ERROR: 7
Error installing zip file '/externl_sd/lineage-14.1-20170618-UNOFFICIAL-lt023g.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
Diamond26 said:
Here is the Error of ROM on SM-T210
Click to expand...
Click to collapse
That is because it is not supported atm. I enabled the flash process to be only carried out on t211.
BTW, does it still change the system partition?
Did you loose your system partition after flashing this?