CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
This rom is for both the Nook Tablet 512M/8GB and 1GB/16GB versions. The device code name is "acclaim".
Prerequisites:
A CWM recovery. To install CWM when coming from a stock device, you need to prepare a special SD card. Installation instructions can be found here on xda.
Installation:
Grab a new recovery (e.g. here http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-20140502.img) and flash it with fastboot. You will need to update the recovery in case you have an older one from CM 10.2 or older.
If you have a recent CM 10.1 installed, flash the new recovery and try the updater, otherwise download the zip from nightlies, boot to CWM and flash it.
Once a version is installed, you can update with CM Updater
Settings->About tablet->CyanogenMod updates->Refresh
Building:
The CM wiki explains that here: http://wiki.cyanogenmod.org/w/Build_for_acclaim
Returning to stock BN firmware:
If you have installed above rom and the CWM recovery and you really hate it and want to go back to stock, you may wish to try to flash the original acclaim_update.zip from BN. You have to unzip that file and edit META-INF/com/google/android/updater-script. Drop the first two lines here:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Zip the package again. Then go to CWM, flash the zip, wipe, and reboot.
Support:
For any issues encountered, please post into this forum, but add steps to reproduce and dmesg and logcat information. If you don't know what this is or how to get them, try to find that out first before posting here.
Developers:
hashcode, ntemis, kuzma30, fattire, mik_os, chrmhoffmann, and many others that contribute to cyanogenmod and especially this version
Thanks:
kuzma30 - great kernel job
hashcode - we have reused lots of your work and effort for the various omap devices (esp kindle fire). It is thanks to you mainly that we are now official CM device.
mik_os - great touchscreen firmware flasher and other efforts
fattire - for helping us everywhere he can
ntemis - thanks for giving so much energy to this - esp for 4.4 I have copied lots of things from you
DISCLAIMER:
- update the CWM if you come from older versions - otherwise you'll see funny error messages when installing zip
- It is possible that you need to wipe your device. I did not do that, but...
- Also you must flash 4.4 gapps. It can be found somewhere....
- The SELINUX policies are not yet enforced.
Known issues:
- Wifi "works" but a clean fix has to be thought of...
- from time to time boot hangs/crashes. In that case, you need to reboot - I don't know how to fix that - seems that surfaceflinger randomly crashes on boot, but it was the case in older releases (cm-10.2), too.
Get it from http://download.cyanogenmod.org/?device=acclaim
Get recovery from here
File: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-20140502.img
md5sum: 0613b47d01400088d09284eb22c5ecc8
Older versions:
File: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-0.2.img
md5sum: e2a87c433171b3d97d852d27aea1ff49
Get it here:
http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/cm-11-20131213-UNOFFICIAL-acclaim.zip
md5sum 5658cdfa0c043ac28e25d2fbc50d746e
CM 11.0 build 1: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim//cm-11-20131208-UNOFFICIAL-acclaim.zip
md5sum: c4c251501cc8b6c4ff4b66443230820f
CWM Recovery 6.0.4.5: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery.img
md5sum: fe92011742acaa0190f4180f4e7c77ce
Thanks! I'll be downloading this later.
Sent from my Nexus 4 using Tapatalk
Is there any way to flash the new cwm as a zip through the cwm recovery I have now?
Sent from my LG Optimus G using xda app-developers app
Mirror?
hello,
Installing to a bone stock unit
from a CWM 6.0.2.8 SD card
Im getting
"set_metadata_recursive: some changes failed"
"error in /sdcard/CM-11-20131208-UNOFFICIAL-acclaim.zip"
Log shows
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed : Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
edit: appears to have installed with no errors thru twrp 2.6.3.1 (as altboot on same sdcard)
thanks for the work !
I am getting constant android.process.media force closes. Only way to get around them was to delete MediaProvider.apk in /system/priv-app. Probably not OK to do this?
Sent from my Galaxy Nexus
this is a great ROM !
----------
for those who like me , really want to have a working flash player in their web browser
this appears to work quite nicely
( forum.xda-developers.com/showthread.php?t=2548001 )
Download Dolphin Browser
Download Dolphin Browser Jetpak
get his modified flash player from that thread.
I turned flash "Always ON" in Dolphin settings
Thanks again to the devs for all their work.
---------------- workaround 2
"unfortunately android.process.media" has stopped keeps popping up for me
Its probably been addressed, but I stopped it for now with no noticeable ill effects yet by disabling the app "media storage"
----------------------
rajsris said:
I am getting constant android.process.media force closes. Only way to get around them was to delete MediaProvider.apk in /system/priv-app. Probably not OK to do this?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
So far, this too is my biggest problem. I can't open Play to install any other apps. WiFi does work though, so hallelujah! I'll try deleting MediaProvider.apk when I get home just so I can install some other apps.
mikeataol said:
this is a great ROM !
----------
for those who like me , really want to have a working flash player in their web browser
this appears to work quite nicely
( forum.xda-developers.com/showthread.php?t=2548001 )
Download Dolphin Browser
Download Dolphin Browser Jetpak
get his modified flash player from that thread.
I turned flash "Always ON" in Dolphin settings
Thanks again to the devs for all their work.
---------------- workaround 2
"unfortunately android.process.media" has stopped keeps popping up for me
Its probably been addressed, but I stopped it for now with no noticeable ill effects yet by disabling the app "media storage"
----------------------
Click to expand...
Click to collapse
Yep, it works OK after that. If you want to change the wallpaper however, you can't do it using a longpress in the home screen, it must be done using settings->display->wallpapers. Even with that, I keep getting Google search force closes when I try to use the stock KitKat wallpapers.
Sent from my Galaxy Nexus
billy8362 said:
Is there any way to flash the new cwm as a zip through the cwm recovery I have now?
Sent from my LG Optimus G using xda app-developers app
Click to expand...
Click to collapse
Ok what I meant was, is there a zip to flash the new cwm to internal emmc??
In addition, MX Player says it is an incorrect android version, which might be related to MediaProvider being deleted.
Sent from my Galaxy Nexus
mikeataol said:
hello,
Installing to a bone stock unit
from a CWM 6.0.2.8 SD card
Im getting
"set_metadata_recursive: some changes failed"
"error in /sdcard/CM-11-20131208-UNOFFICIAL-acclaim.zip"
Log shows
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed : Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
edit: appears to have installed with no errors thru twrp 2.6.3.1 (as altboot on same sdcard)
thanks for the work !
Click to expand...
Click to collapse
You need to install new CWM - or some working twrp.
Chris
rajsris said:
In addition, MX Player says it is an incorrect android version, which might be related to MediaProvider being deleted.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I think that is just a problem with the app. Same problem on other tablets.
Chris
billy8362 said:
Is there any way to flash the new cwm as a zip through the cwm recovery I have now?
Sent from my LG Optimus G using xda app-developers app
Click to expand...
Click to collapse
Just install with fastboot....
Chris
billy8362 said:
Is there any way to flash the new cwm as a zip through the cwm recovery I have now?
Sent from my LG Optimus G using xda app-developers app
Click to expand...
Click to collapse
You can install it from a terminal emulator, if you want to.
1. Download the cwm-recovery.img file referenced in the first post of the thread.
2. Copy this file to the internal memory of your Nook Tablet. Rename this file to cwm.img.
3. On your Nook Tablet, launch Android Terminal Emulator (ATE).
4. In ATE, type in 'su' [ENTER]. Grant it access when prompted.
5. In ATE, type in 'cd /emmc' [ENTER]. This will change your file system current directory to /emmc, which corresponds to the internal storage drive.
6. In ATE, type in 'ls' [ENTER]. This will list the contents of the /emmc directory. You should see the cwm.img file you copied over and renamed earlier (step 2).
7. In ATE, type in 'dd if=/emmc/cwm.img of=/dev/block/mmcblk0p3' [ENTER]. This will write the contents of the cwm.img file to partition 3 of device mmcblk0 (internal memory).
You should now be able to reboot and use cwm. CAREFUL, as you could brick your device if you get step 7 wrong.
Nevermind my phone finally did the job
I see process.media crashes a lot. I'll see what I can dish out.
Well I have one solution..disable the Media Storage app in the App section of Settings. That should flush it away..
Sent from my XT907 using xda app-developers app
billy8362 said:
Is there any way to flash the new cwm as a zip through the cwm recovery I have now?
...
Click to expand...
Click to collapse
You can find a flashable cwm zip (e.g.,from Succulent's recovery repo http://goo.im/devs/succulent/acclaim/recovery), then use an archive file manager (e.g., 7-zip) to replace the copy of recovery.img inside that zip archive file with the new recovery version you want (remember to rename it to recovery.img first).
Got ART to work, everything seems to run fine, except for the boot crash that is known about. Is there any plans to move us to emulated storage?
murkurie said:
Got ART to work, everything seems to run fine, except for the boot crash that is known about. Is there any plans to move us to emulated storage?
Click to expand...
Click to collapse
alil confusing.........i thought it was a known issue art in these new 4.4 builds bootloops on ART......atleast thats wut i have been reading and have found out for myself.......how do mind asking did u get it up and running......?
Related
Team Win Recovery Project 2.4, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
Phone look:
Tablet look:
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
CHANGELOG for 2.3.3.0:
-Fix renaming backups with a space in the name
-Add decrypt button to mount page if you cancel decryption during startup
-Added ignore blkid flag
-Fixed handling of MTD partitions during mount
-Fixed some keyboard mapping issues on 800x1280 layout
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Special thanks to toastcfh, the sexy, neckbearded, nice thighed, elite guy that he is, for helping to get TWRP working properly on the S3 Mini.
Reserved!
yayyyyyyyyyyyyyyyyyyyyy
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
Aaawwwwweeeeesssoommeeeeee!
Sent from my GT-I8190 using xda app-developers app
Oh yeah! Great work.
So will this work with other versions too? (Specifically the I8190L version )
And my flashable zip again.
Sv: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
With goomanager I get "no recoveries were found for your device".
Maybe because I already done "dd",or isn't it on server yet?
Sent thru time and space from my s3mini.
tys0n said:
With goomanager I get "no recoveries were found for your device".
Maybe because I already done "dd",or isn't it on server yet?
Sent thru time and space from my s3mini.
Click to expand...
Click to collapse
Same with me. But through Rom manager there is also upgrade to recovery
Sent from my GT-I8190 using xda premium
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
Benzonat0r said:
And my flashable zip again.
Click to expand...
Click to collapse
I tried this zip.
You are the master!
ExtSd is found here.
All features works pretty cool.
Only the version inside must be upgraded.
Very good work.
Only one thing were so much fun,
Partition sd card..
Good evening
Sent from my GT-I8190 using xda app-developers app
mermigas said:
Same with me. But through Rom manager there is also upgrade to recovery
Sent from my GT-I8190 using xda premium
Click to expand...
Click to collapse
Yes, but with rom manager you won't find a recovery for our device because CWM in this forum isn't official build.
Not saying it's no good. xd.bx did a great job, it's just not official
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]
In rom manager there are official cwm and twrp recoveries on ma phone.
There is listed as samsung g9190 golden.
Quiet interesting..
Sent from my GT-I8190 using xda app-developers app
Trykall8 said:
In rom manager there are official cwm and twrp recoveries on ma phone.
There is listed as samsung g9190 golden.
Quiet interesting..
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Oh, I didn't know it was official CMW! Thats great!
Can you really install TWRP with rom manager?
Isn't it CWM touch?
No no, you got that all wrong.
First of all this is not CWM it's TWRP custom recovery.
You can't install it via ROM Manager but you can install it via GooManager.
Benzonat0r said:
No no, you got that all wrong.
First of all this is not CWM it's TWRP custom recovery.
You can't install it via ROM Manager but you can install it via GooManager.
Click to expand...
Click to collapse
Well the goomanager didn't find anything for my device, I mean didn't find no recoveries.
Sent from my GT-I8190 using Tapatalk 2
It's probably a bug, use my flashable zip.
Also does flashing this recovery increase the binary count?
Sent from my GT-I8190 using Tapatalk 2
If you flash it via CWM or via Terminal with dd if command then no, but if you flash it via Odin yes
And yes there's an official CWM recovery and also CWM touch recovery for our device.
For anyone that isn't able to have GooManager find a recovery for you, open up your /system/build.prop and find ro.product.name and give me that line.
Dees_Troy said:
For anyone that isn't able to have GooManager find a recovery for you, open up your /system/build.prop and find ro.product.name and give me that line.
Click to expand...
Click to collapse
ro.product.name=goldenxx
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT EMMC from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., from http://wiki.cyanogenmod.org/w/Google_Apps
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file (obtained in step 1(a)).
Select reboot to boot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously enabled Google backup service on your CM10.x your Google Playstore apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
A day before i moved from CM 10 to CM 11 , with the help of mikeataol
Anyway Thanks a lot for this guide.
Few questions
* Any good custom kernel ? I tried Bexus but its giving me "android.phone" stopped responding error and wont allow me to do anything , it just keeps on coming even after pressing "OK"
* What happend to multi touch feature ? any ROM , way to enable it ?
* Is it only me or others too feel that the screen lags a lot wrt to touch input ? Its more evident during scrolling or reaading pdf. Also anyway to resolve it ? I desperately need a fix for this.
* I used gapps from here : http://wiki.cyanogenmod.org/w/Google_Apps
CM 11 20140105 , is it fine or i should use PA Gapps only ?
naveen_reloaded said:
...
* What happend to multi touch feature ? any ROM , way to enable it ?
Click to expand...
Click to collapse
Look for the Touch FW Flasher app on the App Drawer screens.
* Is it only me or others too feel that the screen lags a lot wrt to touch input ? Its more evident during scrolling or reaading pdf. Also anyway to resolve it ? I desperately need a fix for this.
Click to expand...
Click to collapse
Did you do wipe /data and /cache in the CM11 installation process?
* I used gapps from here : http://wiki.cyanogenmod.org/w/Google_Apps
CM 11 20140105 , is it fine or i should use PA Gapps only ?
Click to expand...
Click to collapse
The Gapps KK package you installed is fine, the PA package just has a few more apps (such as Maps and YouTube, etc. -- all of which you can get from the Google Playstore) and is more frequently updated (-> less likelihood/need for updates for the apps in the package immediately after first installation).
digixmax said:
Look for the Touch FW Flasher app on the App Drawer screens.
Did you do wipe /data and /cache in the CM11 installation process?
The Gapps KK package you installed is fine, the PA package just has a few more apps (such as Maps and YouTube, etc. -- all of which you can get from the Google Playstore) and is more frequently updated (-> less likelihood/need for updates for the apps in the package immediately after first installation).
Click to expand...
Click to collapse
Thanks , I heard that multitouch has bug which makes tablet slow at <50% battery , is it so ? also does that app work on cm 11?
Yes , i did wipe everything and installed CM 11 , still the screen is stuttering. very annoying. Is there a way to increase the fps ? or see if GPU drivers are working properly ?
The default Gapps are giving error when flashed with Bexus kernel
---------- Post added at 08:12 AM ---------- Previous post was at 07:32 AM ----------
https://play.google.com/store/apps/details?id=com.aatt.fpsm&hl=en
Used this app and saw that fps varies and it varies like from 7 - 50 during reading pdf.
On slow scrolling of pdf , it only shows 11 or so fps , which is why i think shows the stuttering effect
Used the same app on my GS3 to see the difference and it holds its FPS at 60+ and not dropping below 50.
I think if i can make this tablet to render everything at 30+ fps i might not feel this stuttering effect.
https://dl.dropboxusercontent.com/u/15488514/nooktablet.mp4
here is the video i tried to take regarding the screen lag.
its all real time , there is no , afaik any camera lag ( taken with sg3) , its pretty much how it looks . Also i have shown the FPS . You can see when i scroll slowly , the FPS drops to 20 or so making it jerky. if i do it fast , it reaches 50+ but not stable and not very responsive to my touch feedback either.
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/#xjwc1a482a6ll which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
The mediafire link does work anymore. Could you reupload the zip file?
Hannibal2050 said:
The mediafire link does work anymore.
Click to expand...
Click to collapse
Link fixed.
digixmax said:
Link fixed.
Click to expand...
Click to collapse
WHen I pressed to Install zip from sd card, the screen only show the symbol of ROM Manager (a hat), and stucked.
What should I do now?
Hannibal2050 said:
WHen I pressed to Install zip from sd card, the screen only show the symbol of ROM Manager (a hat), and stucked.
What should I do now?
Click to expand...
Click to collapse
What version of CWM do you currently have on emmc?
digixmax said:
What version of CWM do you currently have on emmc?
Click to expand...
Click to collapse
Sorry, I handled this issue.
But now if I selected the ZIP file I downloaded from the first post, CWM reported that this file is BAD, and I cannot install.
I am using CWM 5.5.0.4.
I downloaded this file several times, but the issue does not disaapear
Hannibal2050 said:
Sorry, I handled this issue.
But now if I selected the ZIP file I downloaded from the first post, CWM reported that this file is BAD, and I cannot install.
I am using CWM 5.5.0.4.
I downloaded this file several times, but the issue does not disaapear
Click to expand...
Click to collapse
You need a newer version of CWM 6.0.[1-3].x to install CM10.x.
If you have a SD card handy, try the method outlined at http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163.
digixmax said:
You need a newer version of CWM 6.0.[1-3].x to install CM10.x.
If you have a SD card handy, try the method outlined at http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163.
Click to expand...
Click to collapse
Hi,
I did exactly like that. I tried to update CWM to 6.0.45 and the current CWM reported that the zip file of CWM 6.0.45 is BAD
Hannibal2050 said:
Hi,
I did exactly like that. I tried to update CWM to 6.0.45 and the current CWM reported that the zip file of CWM 6.0.45 is BAD
Click to expand...
Click to collapse
For CM10.x you need 6.0.[1-3].x (e.g., 6.0.2.8).
6.0.4.5 and later versions are for CM11 only.
If you follow the SD-based CWM recovery method in the referenced post the CWM recovery you'd be using (to flash the new CWM, ROM, Gapps) is provided by the file recovery.img (downloaded and copied to the SD card) rather than your current 5.5.0.4 on emmc. Make sure that you boot the NT off the SD card as prescribed in step #3 (otherwise you will end up booting emmc cyanoboot and CWM).
FYI, i'm pretty sure TWRP 2.7 (official from GooManager/TWRP site) doesn't work. if you click on the console button (square with lines in it, top) it'll say "This kernel doesn't support configuring SELinux" or something like that. i tried wiping stuff and it would just do a soft reboot. i may go file a proper report to TeamWin but i have CWM on there now and i don't particularly feel like reflashing a broken recovery.
TL;DR don't use TWRP
Hello, I'm new and trying to learn so please don't be too harsh. In following the instructions I somehow overwrote the stock rom and now duel boot CM 10.1 and 11. Any clue as in what I have done wrong?
Thanks in advance.
phrozen_flame said:
Hello, I'm new and trying to learn so please don't be too harsh. In following the instructions I somehow overwrote the stock rom and now duel boot CM 10.1 and 11. Any clue as in what I have done wrong?
Thanks in advance.
Click to expand...
Click to collapse
This thread OP is for updating the NT Internal Emmc to CM11 (from CM10.x), i.e., CM11 would be installed internally. If you were still running stock ROM internally, it wold be replaced by CM11.
good looking out
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
Ive been trying to update for a while now and i just couldn't figure it out until i came across your thread.and as right now i am running cm 11 and its all good so far.you made my day.
Help
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
So, will pa_gapps-modular-mini-4.4.2-20140608-signed.zip work with any cm11?
11lump said:
So, will pa_gapps-modular-mini-4.4.2-20140608-signed.zip work with any cm11?
Click to expand...
Click to collapse
Yes.
Can't seem to figure this out myself. I have Twrp 2.6.3.0 and it won't let me flash CWM or CM11. Just gives the standard flashing error. Any ideas?
Sent from my XT1058 using XDA Free mobile app
PLEASE READ NEW FLASHING INSTRUCTIONS
Disclaimer:
I am not responsible for any bricks. By flashing this you understand that no one involved with the making of this Rom is responsible for a brick. However, if two nations go to war, that's okay, because they will destroy themselves and their people will worship me, THE BUTTAHLORD OF BUTTERNOOBIA!!!
I mean uhh... No, very bad thing, no countries should not go to war *cough* destroy yourselves *cough*
PLEASE READ ENTIRE THREAD BEFORE FLASHING, D/Ls and Changelog in 2nd Post
Okay past the joking, this is a stock, rooted KitKat ROM for the ZTE ZMAX. The deodexed version would not boot, so this is odexed. However, this version is free of any King Related apps and I've also removed the little bit of crapware in the device.
FEATURES:
Removal of All King Related Apps
Pre-Rooted
Clear of Bloatware
Added Xposed
Added SuperSU
Removed crappy ZTE/Metro/TMO apps
Overall Clean experience
HOW TO FLASH (NEW INSTRUCTIONS):
1. Place ZIP on SD Card
2. Reboot Into TWRP
3. NANDROID (DO NOT SKIP THIS FOR YOUR SAKE)
4. Don't factory reset the normal way, go to wipe > advanced wipe and click "dalvik cache", "data", "cache" and "system". If you don't, you run the risk of getting an updater-script error (not from the zip, it's a bug in some TWRP builds).
5. New Step: Reboot recovery (in the recovery menu). It will ask if you want to install su, press do not install.
5. Flash the ROM
6. Reboot and rep Butternoob!
BUGS:
Free and clear, you tell me!
ADDITIONAL INFORMATION:
Butternoob has been confirmed to work on all variants of the ZTE ZMAX by at least two people on each variant. THIS IS NOT SUPERBUTTER! For those that don't know, Superbutter will be a heavily modified custom rom. Butternoob was designed to be a stock, clean experience with solid performance. I may add tweaks, but you won't find a lot beyond the stock experience.
CREDITS:
-XDA User Mazer.One for the Bootanimation. I made some edits to his and don't take credit for the original work.
-JCase for helping us get root
-Hroark13 for helping me fix the wifi issue in the updater-script
-ZTE Because I have to... They are banished from ButterNoobia though...
-Masterchief87 for the 4.4.4 base and boot.img
ENJOY, REPORT BUGS, FEEL FREE TO USE AS A BASE AND GIVE PROPER CREDITS!
People have asked what my PayPal email is for donations, it is [email protected] . Never required but always appreciated, I'll give 100% regardless
Changelog:
V2:
-Updated to Android 4.4.4 base
-Band 12 Ready
-Replaced Google Launcher with Apex
--Advice on Apex: Go into menu > apex settings > drawer settings > drawer animation > circle to enable Lollipop-style animation for the drawer opening!
-Fixed SuperUser (All binaries updated)
-Fixed Gapps Force Closes
- New Wallpaper, taste of the SuperButter
-All bugs are squashed
V1:
-Initial Release
-Android 4.4.2
-Removed T-Mobile Apps
-Removed ZTE Apps (i.e. music, file manager, etc.)
DOWNLOAD:
BUTTERNOOB Stock 4.4.4 v2.0
md5: E44F1F84B47D3C4401DA522D0A7494F5
BUTTERNOOB Stock 4.4.2 v1.0
md5: 092cee0504d07fa4decde02d2206a2b7
Mine again
Cricket Zte Z987
Will this work on Cricket ZTE Z987 model
How to enable VOLTE on this rom?
work
will this work on ZMAXX Z958 ?
kas hif said:
will this work on zmaxx z958 ?
Click to expand...
Click to collapse
no. Don't try it. Unless you want to buy another phone.
Having an odd issue with LTE. When I call with LTE enabled, it tries to force the call through VOLTE, rather than handing off to a 4g (or whatever) local band. The call, of course, fails with no audio in or out; is this a known issue, is there a workaround, do I need to re-flash, or is this something weird that nobody's heard about before?
Does this work on Grand X Max + Z987?
Sent from my Z987 using Xparent Blue Tapatalk 2
Zmax Z970 RamDisk Boot.img packing problem
Hi,
Im attempting to repack the ram-disk image for my boot img on my ZTE Zmax z970 running the BN 2.0-oxed ROM. I was trying to use gzip with mkbootimg and it is not working, im assuming due to the fact that my newly repacked ram-disk cpio compressed file was not the same size as the original making the phone fail to boot when the boot.img was sent back to the boot block. My pc is running Ubuntu 14.04-32 bit. I know that the unpack-bootimg and mkbootimg scripts are working correctly because when i repack an unchanged boot.img-ramdisk.cpio.gz file (unpack the img and recreate the boot.img file) and re-upload it to the boot block, the phone boots correctly so I know that my procedures outside of the ram-disk cpio file are correct. My question is, How can I find out how much padding i need on the ram-disk file, where the padding should go, and how to apply the padding to get the file the correct size so that it will work as intended? Any help you can give me would be greatly appreciated.
P.S. I only unpackaged the boot image to change one entry in the ramdisk to the default.prop file. If there is a way to open the compressed cpio file with an archive manager and could update the file once i make my change. that would work as well. I can open the gz file with the archive manager but can not open the cpio folder contained inside.
Thanks,
Much appreciation.....f20062e
I followed your directions. Surprisingly it was super easy! Thanks!!!!!
Does this work on 6.0.1 Zmax Pro Tmobile?
link
Need link to root the z981 and link for twrp to install the recovery image. Thanks all for the hard work this excellent community pours out on a daily basis!
Hi there! I just got this flashed, and I need to know if it's safe to do an OTA update over your ROM.
Thanks a ton!
ZTE 982
Hi there good morning I have a big question, I have the ZTE z982 from MetroPCS I went ahead and rooted and installed TWRP on it. Now I was having some issues trying to flash a custom rom Slimrom to be exact (https://forum.xda-developers.com/zte-zmax/development/slimrom-5-0-2-t3161888) but I kept getting errors about legacy property? So something along those lines. Well I then read somewhere that it could be because of TWRP being outdated. I took it upon myself to look and find an .IMG witch I then flashed and now am stuck with a sorta bootloop flashes on but the screen goes black. Any suggestions? I would really appreciate it.
how did you get past fastboot. my z982 cant find device there?
soLo1Blue said:
Hi there good morning I have a big question, I have the ZTE z982 from MetroPCS I went ahead and rooted and installed TWRP on it. Now I was having some issues trying to flash a custom rom Slimrom to be exact (https://forum.xda-developers.com/zte-zmax/development/slimrom-5-0-2-t3161888) but I kept getting errors about legacy property? So something along those lines. Well I then read somewhere that it could be because of TWRP being outdated. I took it upon myself to look and find an .IMG witch I then flashed and now am stuck with a sorta bootloop flashes on but the screen goes black. Any suggestions? I would really appreciate it.
Click to expand...
Click to collapse
No matter what I do I cannot get this vile little phone to root. It is located in adb but fastboot just isnt there or doesnt' want to find it. I have tried every dang driver you can think of and still nothing in fastboot. I must know its driving me crazy. I have got to where i absolutely hate this phone!
works on z981 ??
Samsung Galaxy Tab A 7.0 LTE/WIFI 2016 TINKER EDITION ROM (DEOXED/ROOT/XPOSED)
============================================
Update 01/04/2017
-----------------------
Tinker Edition V5.1 is now out.
* Re-added Samsung stock camera and gallery
* revert back to stock vold to fix issues people are having with micro sdcards
Now available for the SM-T285, SM-T280 to follow
Update 10/29/2016
------------------------
TWRP for the SM-T285 here
Early Build of TWRP for the T285 (see post by @ashyx will update this if an official version is released. The T280 version should be available not far behind I believe
Update 09/21/2016
-----------------------
V5 now out (root, deodexed, xposed) for the SM-T280/T285, still working on the SM-T280
Update 09/20/2016
------------------------
Turns out this device is not as locked as we all thought it too be. See thread below for my ordeal and more details:
http://forum.xda-developers.com/galaxy-tab-a/help/resources-samsung-galaxy-tab-7-0-2016-t3431022
Modifications:
===========
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Busybox
* Hijacked Vold (using CM 12.1 sources) to run shell scripts stored in /data/scripts/vold.init
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
* Dolby Atmos mod (09/11/2016) (thanks to @Nando14sunny)
* Deodexed/Xposed (09/13/2016) (thanks to @wanam and @rovo89)
* soft linked /etc/hosts to /data/scripts/hosts and can be edited using adb shell (09/13/2016) (thanks to @venomrat)
* V5: root chainfire's SuperSu 2.78 (09/21/2016) (thanks to @Chainfire)
* stock boot animation
Special thanks also to @ashyx for initially taking a look at this device , I haven't given up on rooting this device yet.
Special thanks to @klemen241 for helping me try out the SM-T280 build
Haven't done extensive testing on Xposed modules, but the pokemon go iv mod/hacked worked and that was good enough for me (Before pokemon Go was patched). If you use this ROM feedback is highly appreciated
NOTES: To be safe, perform a cache wipe using recovery. I didn't need to do this personally but I haven't tested all use cases
NOTES: Since this rom is deodexed, the first boot will take quite a while, so please be patient .
NOTES: if you are coming from V2 and are using the mount_ext4 apps2sd scripts please update it for additional support for the V3 ROM HERE:
https://github.com/jedld/smt285_data_scripts
NOTES: (09/13/2016) Unfortunately, the V3 build fails the Google SafetyNet check, will be a problem if you play Pokemon Go
Other Notes: Removed support for zygote.init scripts in V3 as I am now using the app_process32_xposed binary, will work to get this back soon. I haven't had a need for zygote scripts though. The vold.init scripts shoud still work as before if you are using the apps2sd script
Installation Instructions:
Odin or Heimdall Required. I you are coming from the Stock Rom please wipe/factory reset to be sure. If you are upgrading from V1 or V2 you are not required to wipe unless there are problems. If you are upgrading to V3 cache wipe is recommended using recovery.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Choose the appropriate download for the model (wifi only T280/ lte T285) that you have:
WIFI ONLY Download (SM-T280)
==========================
Link (V5 Deodexed, Rooted and Xposed):
https://mega.nz/#!0Jdg0a4D!XWLES1BwCPrkBlUzqNhRfRi_91LOdawYHydQ_scV2dI
Link (V3 Deodexed and Xposed - with special thanks to wanam with his custom Xposed build (86.0), and credits also to rovo89):
Download from Mega (v3 09/13/2016)
LTE Version Downloads (SM-T285)
===========================
Link (V5.1 Deodexed, Rooted and Xposed):
https://mega.nz/#!ZFFTFKYZ!NAeajNUjIgYI7zOslpWoJ2AeJ-NCKG0Ut8Buz_6eCgU
Link (V3 Deodexed and Xposed - with special thanks to wanam with his custom Xposed build (86.0), and credits also to rovo89):
Download from Mega (v3 09/13/2016)
Link (Original V2 odexed version):
Download from Mega (V2 09/11/2016)
If you have suggestions, send me a PM.
Other Notes (So people don't have to ask):
* I've tried to run superuser daemonsu, but unfortunately the sepolicy scopes for vold and zygote are too narrow in this device for supersu to use despite being root. In theory a version of daemonsu can be made specifically to run on this device with a somewhat castrated functionality though I don't have access to the source code to figure it out. Navigating the sepolicy landmine is hard.
WIFI ISSUES
=========
There are reports of wifi problems with the latest build due to wrong permissions with dhcp hooks, if so you can do the following (big thanks to @_mone):
Using adb shell:
Code:
su
mount -o rw,remount,rw /system
chmod 755 /system/etc/dhcpcd/dhcpcd-run-hooks
mount -o ro,remount,ro /system
/system is readonly by default, which is why you need the remount commands. Reboot your device after just to make sure.
Hi,
The mount_ext4_sdcard.sh script moves all apps to SD card on reboot?
Edit: did not read till the end. System apps are not move.
venomrat said:
Hi,
The mount_ext4_sdcard.sh script moves all apps to SD card on reboot?
Edit: did not read till the end. System apps are not move.
Click to expand...
Click to collapse
It won't by default for safety purposes, however you are welcome to edit the script and try to move them all
jedld said:
It won't by default for safety purposes, however you are welcome to edit the script and try to move them all
Click to expand...
Click to collapse
Thanks for your hard work. It's a pity this device is not as popular as their other models or more people would have already signed the petition.
I regret not doing more research before buying this tablet.
Hello there
At first i want to thank you for your hard work so far
Then i've got a question,
I just built this Tablet (LTE version) in my car. Now i'm on to configure it with Tasker to "act more like a car radio". It was really hard, because of the non rooted device.. But i did it so far
I used a sound mod, called Dolby Atmos (i think it's from lenovo?) on allmost every of my rooted devices to improve its sound.
I'm wondering if it would be possible that you could build in this mod inside a rom for me?
Normally i flash it as a zip file via a custom recovery so it's in the system files. but maybe you could edit it in there before the rom get flashed via odin? I could give you the zip, if u dont find it. It would be really nice!
Greetings from germany
Nando14sunny said:
Hello there
At first i want to thank you for your hard work so far
Then i've got a question,
I just built this Tablet (LTE version) in my car. Now i'm on to configure it with Tasker to "act more like a car radio". It was really hard, because of the non rooted device.. But i did it so far
I used a sound mod, called Dolby Atmos (i think it's from lenovo?) on allmost every of my rooted devices to improve its sound.
I'm wondering if it would be possible that you could build in this mod inside a rom for me?
Normally i flash it as a zip file via a custom recovery so it's in the system files. but maybe you could edit it in there before the rom get flashed via odin? I could give you the zip, if u dont find it. It would be really nice!
Greetings from germany
Click to expand...
Click to collapse
we could try, could you point me to a rom that has the specified libraries for Dolby?
Thank you, for the fast answer!
Here is the flashable zip of the Dolby Atmos, mod i used successfully on my other devices:
Mega
Greetings
Nando14sunny said:
Thank you, for the fast answer!
Here is the flashable zip of the Dolby Atmos, mod i used successfully on my other devices:
Mega
Greetings
Click to expand...
Click to collapse
Ok, wish granted, updated the ROM to include Dolby ATMOs, just redownload the ROM from the link in the main post.
jedld said:
Ok, wish granted, updated the ROM to include Dolby ATMOs, just redownload the ROM from the link in the main post.
Click to expand...
Click to collapse
Wow thank you! I'll test it right now
Edit:
It works like a charm! You really improved my devie with it!
Hi,
If it's not too troublesome, perhaps the next version can symlink the host file to a r/w folder so that ads can be blocked.
Thanks.
venomrat said:
Hi,
If it's not too troublesome, perhaps the next version can symlink the host file to a r/w folder so that ads can be blocked.
Thanks.
Click to expand...
Click to collapse
Possible, though the only r/w partition is data and cache, and it may potentially cause problems when you suddenly try to do a wipe. I'm working on deodexing and porting xposed framework for now. Either that if you've got some IP addresses that need to be blocked I can create an edition that has those entries. I'll see what I can do though there might be away to do it without breaking factory reset/wipe cache.
jedld said:
Possible, though the only r/w partition is data and cache, and it may potentially cause problems when you suddenly try to do a wipe. I'm working on deodexing and porting xposed framework for now. Either that if you've got some IP addresses that need to be blocked I can create an edition that has those entries. I'll see what I can do though there might be away to do it without breaking factory reset/wipe cache.
Click to expand...
Click to collapse
No hurry. I can wait. What you are doing now is more important. :good:
venomrat said:
No hurry. I can wait. What you are doing now is more important. :good:
Click to expand...
Click to collapse
Wish Granted. As a bonus, the latest version of the ROM is now deodexed and Xposed, please refer to the main post for the updates.
Feedback is appreciated.
How can i change the dpi?
Sent from my SM-T285 using XDA-Developers mobile app
corzradio said:
How can i change the dpi?
Sent from my SM-T285 using XDA-Developers mobile app
Click to expand...
Click to collapse
May need to modify build.prop, you may do this yourself here:
http://forum.xda-developers.com/galaxy-tab-a/how-to/guide-samsung-galaxy-tab-7-0-sm-t285-t3438296
Also there may be an Xposed framework modules that do that. Not sure though since I'm ok with the stock DPI
jedld said:
Wish Granted. As a bonus, the latest version of the ROM is now deodexed and Xposed, please refer to the main post for the updates.
Feedback is appreciated.
Click to expand...
Click to collapse
Thanks. Will need to find time to re-flash this weekend.
Regarding xposed have you actually tested any other modules that need root?
I already built a rom with xposed but it was all but useless because pretty much all the modules I use need root.
most of those I tried don't need root so far (youtube adaway, pokemon go iv). Haven't tried those that need root but I suppose those wouldn't work.
I use app settings and it works for dpi change, and you are welcome. I am glad to test stuff, its fun haha. If anyone has questions about t280 you can ask me
how can i boost the volume? since its not rooted i cant find the mixer.xml
Haven't seen anyone else discussing this particular solution yet so figured I'd share that we can boot multiple roms using dual boot patcher by @chenxiaolong.
*The only things I'd recommend are the following:
*MAKING A BACKUP FIRST IN RECOVERY. Especially if you've never used the app, this helps in case you misunderstood something or didn't read enough or didn't think enough or the dog ate your homework.
*I recommend using TWRP version 3.0.3-0 which can be found here - https://dl.twrp.me/angler/
* I have not tried this with f2fs only ext4 so naturally I'd only recommend using ext4 partitioning on your device.
* If your device is encrypted in any way booting multiple roms will not work, which should be obvious but I'll state that anyways. Thanks @JKforUA for helping us figure this out.
*If you want to boot more than just two roms, that you use the data slot options for your roms which can be named anything you'd like and they will be stored on the phones internal storage.
* Make sure you're on the latest Radio and Bootloader for the nexus 6p, I flashed this and it works fine and is backwards compatible with Marshmallow roms.
Radio & Bootloader link -
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637
* Use the patcher app to update the ramdisk and set your primary rom's kernel as Primary before patching or flashing anything.
*If you use the fingerprint scanner you'll have to delete the file /data/system/locksettings.db in each multi boot directory, this disables getting an incorrect pin error when switching roms.
*If using a marshmallow and nougat rom you'll need to flash the appropriate vendor image in recovery before boot.
*Vendor images should not be patched.
This process is fairly simple to me because I've been using it for years but if you have any questions feel free to ask in this thread and hit thanks if I helped ya.
* Before reporting errors I would suggest you try the following steps-
1. Make sure you're using this version of the patcher app because it is the one I have been using without issue -
Version 9.1.0r80-
https://dbp.noobdev.io/files/9.1.0....atcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
2. Make sure you have enough free space to have two of the zips you want to use because that is what you will have after you patch.
3. Make sure your path to the zip is correct when browsing for the zip, go through internal storage to the directory where the zip is.
4. If you get any error patching, uninstall the patcher app, re-download it, and reinstall it.
5. There is also a Windows version you can try if you prefer.
*If you are still having issues we can discuss it here, and if nobody can seem to come up with a fix in this thread then errors can further be reported by following instructions here - https://dbp.noobdev.io/downloads/
Credits - @chenxiaolong for the patcher app!
Links :
Dual boot patcher (All versions) - https://dbp.noobdev.io
Original forum - https://forum.xda-developers.com/showthread.php?t=2447534
* Screen shots of my current setup attached below for additional guidance if desired.
Status - sharing, using, in some cases testing, always learning (^_-)...
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Thanks for sharing. Used this on my further G4. Didn't know that our device is supported. So no need to wait until multirom is working on 7.1.1. Gonna play around now.
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
DaringDomino3s said:
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Click to expand...
Click to collapse
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
OmegaBlaze said:
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
Click to expand...
Click to collapse
Hmmm I found this
https://forum.xda-developers.com/showpost.php?p=64727670&postcount=8259
I would try re-downloading the app because I haven't had it crash in any roms I've used yet, I just grabbed the latest build, installed, opened, granted root when prompted, updated the ramdisk if needed which is indicated the app, rebooted when prompted, set kernel, and done.
If it's still crashing for you there's the usual force closing the app from your roms settings and clearing the apps cache and data but you probably already tried that?
t83wood said:
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
Click to expand...
Click to collapse
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
DaringDomino3s said:
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
Click to expand...
Click to collapse
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
t83wood said:
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
Click to expand...
Click to collapse
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
DaringDomino3s said:
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
Click to expand...
Click to collapse
Yep looks good!
t83wood said:
Yep looks good!
Click to expand...
Click to collapse
Awesome, thanks, I'll see what happens :good:
Edit: it worked! It's a little more involved than multirom, but it seems to be fine! Easier than I thought.
I've not yet switched between the two, but the app on the secondary (data slot) recognizes the primary
Wow great. Running great on data-slot. Even magisk is supported. Good to have a new playground. Happy to have the 128 GB variant. Gonna do some test with Viper.
How do I switch roms
All perfect. Viper running with magisk. Every rom i tried booting without any problem. So atm the perfect tool to test other rom!
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
DEVILOPS 007 said:
How do I switch roms
Click to expand...
Click to collapse
Install dualpatcher app and choose rom in 'ROMs'. Then reboot. Or run utulities in twrp (install).
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Donric13 said:
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Click to expand...
Click to collapse
Okay thanks Bro, I might try out lineage. Also open gaps failed for me bit do I need the rom first or do I need to use dynamic gaps? I appreciate the help!
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Donric13 said:
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Click to expand...
Click to collapse
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
DEVILOPS 007 said:
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
Click to expand...
Click to collapse
Did you flash in twrp (3.0.3.0)? I only use twrp to flash a new multiboot rom. Before flashing a new rom just make sure, you patch all necessary zip files (rom, gapps, etc.). Same name means u choose where (on angler i always choose Data slot - this is internal sd card). Then you give the name (no capital letters) and choose the directory to save the patched file. This you do with every zip file for the rom u gonna flash. The new zip file have the original name and the text "....._data-slot-namegiven.zip" (example for data-slot). The part "data-slot-namegiven" should appeir in every name of the patched zip file. I think with our device it's goot to use the data-slot if you have enough space on your internal sd-card. Using Multi Slot could lead to space problems on system partition of the device. Then just flash the patched files one after another in twrp. Don't forget to flash also patched supersu.zip oder magisk.zip to get root (if it's not in the rom included). You need to patch gapps and supersu or magisk for each slot separately. The name of the patched file just says the path for the multiboot rom. So twrp flashes the patched zip to the right place. Sorry if i wrote to much. Hope it's gonna give you some help. More information you find in the original thread of multiboot.