Jcsullins is back in the game. Hopefully he may also build cm13 in the future.
quoted from this post: http://forum.xda-developers.com/showpost.php?p=64959558&postcount=159
Latest CM12.1 builds.
https://www.androidfilehost.com/?w=files&flid=43605
G Aaps:
https://www.androidfilehost.com/?fid=24369303960689639
To find the latest, go to: http://forum.xda-developers.com/andr...107-1-t2997368
And search for "gapps-511"
Recovery:
https://www.androidfilehost.com/?w=files&flid=14847
Link to Toolbox software (v42 is the latest):
http://forum.xda-developers.com/hp-t...4-4-x-t2912820
JCsullins, HP Touchpad (main directory):
https://www.androidfilehost.com/?w=files&flid=9776
It took me a few tries, but I finally got this running. One thing I did that may have helped was to increase the cache and system partitions to 1gb each. That may have been overkill, but I got the thing running.
To get it working, I used TPTB42 to resize the partitions, then TWRP to install over a fresh install of JC's cm-11-20151116. I used these three files for the install:
cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip
gapps-lp-20141109-signed.zip
update-TWRP-jcs-dm-tenderloin-20140612b.zip
It seems pretty stable so far. I've even got a working Bluetooth connection to my home stereo!
I tried to post this earlier today to the developer thread, but I was robo-scolded for attempting to post in a developer thread. I think it's silly that I was sent to the kiddie table to post about a developer's great work. This will never be read here.
Very nice! The fact that there's still activity around this thing is amazing.
Do Not Touch said:
It took me a few tries, but I finally got this running. One thing I did that may have helped was to increase the cache and system partitions to 1gb each. That may have been overkill, but I got the thing running.
To get it working, I used TPTB42 to resize the partitions, then TWRP to install over a fresh install of JC's cm-11-20151116. I used these three files for the install:
cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip
gapps-lp-20141109-signed.zip
update-TWRP-jcs-dm-tenderloin-20140612b.zip
It seems pretty stable so far. I've even got a working Bluetooth connection to my home stereo!
I tried to post this earlier today to the developer thread, but I was robo-scolded for attempting to post in a developer thread. I think it's silly that I was sent to the kiddie table to post about a developer's great work. This will never be read here.
Click to expand...
Click to collapse
Thanks for the information. Does anyone know if there's a CWM version that will work with LP and the HP Toolbox?
May I ask where you got the gapps from?
garux said:
Thanks for the information. Does anyone know if there's a CWM version that will work with LP and the HP Toolbox?
May I ask where you got the gapps from?
Click to expand...
Click to collapse
Check jcsullins androidfilehost site, he released a new cwm version on 20150703.
Sent from my LG-v410 using XDA Premium App
googlephone said:
Check jcsullins androidfilehost site, he released a new cwm version on 20150703.
Sent from my LG-v410 using XDA Premium App
Click to expand...
Click to collapse
Thanks.
I tried to using gapps-lp-20141109-signed.zip with the HP Toolbox and I get the following error:
ERROR: Incompatible GAPPS/ROM versions 5.0/5.1
ERROR: Checking Install ZIP files. Aborting.
Could someone please let me know what gapps to use with cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip?
garux said:
Thanks.
I tried to using gapps-lp-20141109-signed.zip with the HP Toolbox and I get the following error:
ERROR: Incompatible GAPPS/ROM versions 5.0/5.1
ERROR: Checking Install ZIP files. Aborting.
Could someone please let me know what gapps to use with cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip?
Click to expand...
Click to collapse
I was never able to get TPTB to work with CM12.1, so you may have misunderstood the process I used.
1. completely uninstall Android (may be optional, but this worked for me)
2. use TPTB42 to do a fresh install of JC's cm11 with cache and system partitions bumped up to 1GB each.
3. use TWRP to install these three files:
cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip
gapps-lp-20141109-signed.zip
update-TWRP-jcs-dm-tenderloin-20140612b.zip
-------------------------
Once again, I tried to post to the thread where this reply was relevant and most likely to be read, and once again I was sent to the kiddie table. Idiotic policy that just thwarts participation.
I was able to install it by doing a complete data reset using TPTB, resizing system and cache volumes to 1 GB, modifying tptoolbox.cfg in the zip file (ROM_VERSION 5.0) and installing android using the following files:
update-CWM-jcs-dm-tenderloin-20150703.zip
cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip
gapps-lp-20150222-signed.zip
I used JCSullins' toolbox to 'wipe everything' and it sized my partitions correctly.... Amazing to see it preform almost better than cm11
Sent from my iPhone using Tapatalk
Been using JCSullin's CM11. Thinking to upgrade to CM12.1. A couple questions that I couldn't find here.
Is there anything that is known to not be working, or not fully working?
What are the ideal or minimum partition size(s)? Are the CM11 sizes (I forget what they are) not big enough? I know some people mentioned 1GB System and Cache, but it sounded like guesses and I wonder if JCSullins has any official recommendations.
GnatGoSplat said:
Been using JCSullin's CM11. Thinking to upgrade to CM12.1. A couple questions that I couldn't find here.
Is there anything that is known to not be working, or not fully working?
What are the ideal or minimum partition size(s)? Are the CM11 sizes (I forget what they are) not big enough? I know some people mentioned 1GB System and Cache, but it sounded like guesses and I wonder if JCSullins has any official recommendations.
Click to expand...
Click to collapse
The system partition size for cm11 is enough for cm12.1.
800 MB should be more than enough. On my device, it actually only used less than 500MB.
Works fine
Just flashed it by tptoolbox v.42 by using gapps-511-base-20151114-1-signed.zip
So far so good!!
gapps-511-base-20151114-1-signed.zip will work with cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip.
No need to resize system amd cache volumes, just flashed them by tptoolbox.
Works good
knockedout said:
I was able to install it by doing a complete data reset using TPTB, resizing system and cache volumes to 1 GB, modifying tptoolbox.cfg in the zip file (ROM_VERSION 5.0)
Click to expand...
Click to collapse
Are you saying TPTB version 5.0? If so, could you please include a link?
AliTanaka said:
gapps-511-base-20151114-1-signed.zip will work with cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip.
No need to resize system amd cache volumes, just flashed them by tptoolbox.
Works good
Click to expand...
Click to collapse
Yep, thank you. These GApps are from here, if anyone's wondering:
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Not sure what I'm doing wrong. Tried several times to flash cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip using CWM. I previously successfully updated my CWM to update-CWM-jcs-dm-tenderloin-20150703.zip (says version is 6.0.5.1, I believe). I always get:
"Patching system image unconditionally"
The progress meter never fills up, and it stays there forever. I thought maybe it just takes some time, but I let it sit there an hour and it never got past it. I tried doing a dirty flash and also formatting /system first, doesn't make any difference.
Thinking maybe my partition sizes are too small, I thought I'd look into that, but realized I don't know how. I guess I'd have to break down and install TPToolbox to check them? I was hoping to avoid having to set my computer up with all that novacom business.
Also I did verify the MD5 and SHA-1 hashes for the zip file are correct.
UPDATE: Got it to flash. /system has to be at least 1024MB in size. Not 800 or 1000, but 1024 exactly. Had to run TPToolbox to check the existing size and resize accordingly.
garux said:
Are you saying TPTB version 5.0? If so, could you please include a link?
Click to expand...
Click to collapse
No, the zip I was referring to was the ROM zip file (cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip). I ended up unzipping the ROM, modifying the tptoolbox.cfg file (changed the ROM_VERSION 5.1 line to ROM_VERSION 5.0), zipping it again and flashing it.
It seems like this process is not necessary anymore based on the following comment - http://forum.xda-developers.com/showpost.php?p=63949730&postcount=12
Do Not Touch said:
I tried to post this earlier today to the developer thread, but I was robo-scolded for attempting to post in a developer thread. I think it's silly that I was sent to the kiddie table to post about a developer's great work. This will never be read here.
Click to expand...
Click to collapse
Nah. I read it though I hardly ever post. I just acquired a couple more touchpads and I'm checking the latest builds. Thanks!
knockedout said:
It seems like this process is not necessary anymore based on the following comment - http://forum.xda-developers.com/showpost.php?p=63949730&postcount=12
Click to expand...
Click to collapse
That is correct, there's no need modifying tptoolbox.cfg in the Rom zip file.
I was able to use HP Toolbox v42 using the following Rom, Gapps & CWM without any problems:
update-CWM-jcs-dm-tenderloin-20150703.zip
cm-12.1-20151116-SNAPSHOT-jcsullins-tenderloin.zip
gapps-511-base-20151114-1-signed.zip
I have Bluetooth working with Keyboard, Mouse & Headset. Still checking CM12.1 out. Taking some getting use to using.
Thanks jcsullins for all your hard work you put into giving as a ROM the works right out of the box.
GnatGoSplat said:
Been using JCSullin's CM11. Thinking to upgrade to CM12.1. A couple questions that I couldn't find here.
Is there anything that is known to not be working, or not fully working?
What are the ideal or minimum partition size(s)? Are the CM11 sizes (I forget what they are) not big enough? I know some people mentioned 1GB System and Cache, but it sounded like guesses and I wonder if JCSullins has any official recommendations.
Click to expand...
Click to collapse
If you use toolbox you won't have to change partition sizes.
Related
This is an init.d script inspired by bodhisattva99's work that can be found here:
http://forum.xda-developers.com/showthread.php?t=1526827
Props to him for the idea.
This script does the same as his, but my zip does not flash a new zImage (the partition can be mounted anywhere with one single command, thanks, Chainfire!).
I do not own an SGS2, so this is untested by me personally, but it was tested by AColwill on A LOT of ROMs and he noticed seemingly better boot times than with the original script. However, he discovered that this also doesn't work on GB and earlier ICS builds. If you do happen to flash it on an unsupported build, the script should simply print out that your ROM isn't supported to /data/d2p.log, exit, and let the boot process continue.
What does it do?
Basically, what it does is it puts Dalvik cache on /preload (which is about 500 MB in size and otherwise totally unused), freeing up space on /data for even more apps.
It will not wipe any of your data, it will just put Dalvik cache on /preload. First boot will take a while since Dalvik cache needs to rebuild, afterwards, it should work like a charm, leaving you with a few hundreds of megabytes more on /data.
Requirements:
- A recovery image
- A rooted ROM
CWM update.zip:
Download link
Huge thanks to:
AColwill - testing, testing, testing and some more testing
Ante0 - providing proper hosting for the zip
brabo, GShellz admin - the bash wizard
Chainfire - providing me with the preload parition ID
mattgirv (from #villainrom, Freenode) - compiling bash for me, help with cross-compiling
sircrazy, GShellz admin - help with cross-compiling
Disclamer: I'm not responsible if something goes wrong and wreaks havoc upon you, your phone, your card, any part of your phone, your friends, your family, your close or distant relatives and/or your pet, but I will gladly provide assistance if it does.
Got some fail:
Code:
I/run-parts( 1667): /system/etc/init.d/99dalvik2preload: line 13: syntax error: unexpected word (expecting ")")
I/run-parts( 1667): run-parts: /system/etc/init.d/99dalvik2preload exited with code 2
I/logwrapper( 1667): /system/xbin/run-parts terminated by exit(1)
Sorry about that, should be fixed now. Try it now, should work like a charm!
This is great! A few questions though, a small FAQ could be useful in the first post.
1. Is this reversible?
2. Will it wipe any data?
3. Will the Wipe Dalvik command work in CWM?
4. What happens when the Dalvik becomes full?
Thanks for the mod and for replies in advance!
And the link is where??? i only see download link [fixed] but cant press it
blizzari said:
And the link is where??? i only see download link [fixed] but cant press it
Click to expand...
Click to collapse
well the link he credits (http://forum.xda-developers.com/showthread.php?t=1526827) at the end of page2 does have a valid link to his script (called dalvik2preload_proz0rmod-signed.zip) now I'm not sure the OP link is down because it is borken or because the script is being worked on and he'll make the link active again once work is completed.
---------- Post added at 08:01 PM ---------- Previous post was at 07:59 PM ----------
Phat7 said:
This is great! A few questions though, a small FAQ could be useful in the first post.
1. Is this reversible?
2. Will it wipe any data?
3. Will the Wipe Dalvik command work in CWM?
4. What happens when the Dalvik becomes full?
Thanks for the mod and for replies in advance!
Click to expand...
Click to collapse
just have a quick read at the link the OP credits ( http://forum.xda-developers.com/showthread.php?t=1526827 ) and all your questions will be answered.
Due to an issue with ASH and some retarded builds of busybox from some devs, Davor (Proz0r) has had to pull the release as it wasn't doing what it was supposed to do.
Currently, the 1.19.4 busybox which is included with the CM9 firmwares AND the one downloaded by jrummy's busybox installer (same build) is missing some core functionality required to get the script working :|
I'll be working with Davor over the next few days (hopefully) to get this fixed and released.
Exactly, thanks AColwill for the explanation as I was too busy with school at that time. I will get on it soon and deal with the Busybox issues.
Script works like a charm now, no need for Busybox. All tools required for the script to run are included, all you need is a rooted SGS2 with a recovery image and you're all set!
Just flash it or we need to wipe something too?
Getting a 404 error when I click on the link
Sent from my GT-I9100
soyef said:
Getting a 404 error when I click on the link
Sent from my GT-I9100
Click to expand...
Click to collapse
Me too. Can somebody post a link that works?
need new download link
Thanks
Whoops, fixed. AColwill also tested this with a whole bunch of ROMs to find out that it should work on KPA and newer ROMs, but no pre-KPA ones. I've also added a failsafe which will just print out that your ROM isn't supported to /data/d2p.log instead of causing a bootloop if you happen to flash it to an unsupported ROM.
As always when flashing stuff. NANDROID FIRST.
Even though I have done extensive testing with multiple SGS2's, I am not infallible (even though it appears that way).
Proz0r said:
Whoops, fixed. AColwill also tested this with a whole bunch of ROMs to find out that it should work on KPA and newer ROMs, but no pre-KPA ones. I've also added a failsafe which will just print out that your ROM isn't supported to /data/d2p.log instead of causing a bootloop if you happen to flash it to an unsupported ROM.
Click to expand...
Click to collapse
Not getting any errors on KL1 - My phone now boots in less than 10sec. Great mod. Thanx.
Awesome, thanks for the feedback!
Just flashed it... I'm on Spike's 7.1 SE
1.
Booted into CWM, wiped dalvik-cache & flashed d2p-mod.
Phone does not boot... gets stuck in bootanimation...
2. Restored phone.
Booted into CWM, this time I did NOT wipe dalvik & flashed d2p-mod.
Result: Phone stuck in infinite boot loop on the Samsung Galaxy SII screen...
It is sad there seems to be not updates at this time...
Flashed it on Westcrip's 1.0 Pro, and checked the /preload was empty....
We probably need a zImage-empty file, to install our custom rom's kernel
Ty for any update!
This is a Deodexed Version Of the newest JellyBean 4.2.2 Leak N5110XXCMG2
Features:
Rooted
insecure boot.img
BusyBox
Zipaligned
Deodexed
Init.d support
adb as root
Bash
Nano
Download: http://www.androidfilehost.com/?fid=23050663588004205
md5: 0386dd0afe5fd788ae2486b7820cfddd
Disclaimer: nothing has been edited this is a full stock rom that you would expect to get from samsung just rooted and deodexed for easy modability,themability
Thanks to:
SamMobile - for the basefirmware package
Dsixda - for the kitchen used to deodex
ChainFire - for superSU
FYI- i will be making me JellyBeans Rom with this base
Welcome back .
Is there much difference between this version and civato other than his has Aroma installer?
2swizzle said:
Welcome back .
Is there much difference between this version and civato other than his has Aroma installer?
Click to expand...
Click to collapse
this is pure stock deodexed nothing removed, and has adb as root. also doesnt have any mods
thank you for posting this here! :good:
Many thanks!
Thanks for this! Works great, feels more fluid... Except doesn't seem to fix the touchscreen deadzones that occur intermittently (but of course that's for Samsung to take care of)
How this update should be installed? Adb?
Edit. Sorry, never mind, this is for N5100 but I have N5100. Waiting for new version for my device.
I am interested in loading this rom on my wife's tablet. I have been flashing rom's on my Motorola Phones for years now and am very comfortable doing so, but a real Novice when it comes to Samsung.
I am on 4.1.2, insecure loader. I have tried both CWM and TWRP recoveries and can use either. I have also used Odin as well.
Question, do I need to wipe data first, and how do I load this rom onto a Samsung Device.
Sorry for the trouble, but I am a fast learner and will be on board soon (I hope)
BobC43 said:
I am interested in loading this rom on my wife's tablet. I have been flashing rom's on my Motorola Phones for years now and am very comfortable doing so, but a real Novice when it comes to Samsung.
I am on 4.1.2, insecure loader. I have tried both CWM and TWRP recoveries and can use either. I have also used Odin as well.
Question, do I need to wipe data first, and how do I load this rom onto a Samsung Device.
Sorry for the trouble, but I am a fast learner and will be on board soon (I hope)
Click to expand...
Click to collapse
Since this is an OS upgrade (4.1.2 to 4.2.2) a data wipe is highly suggested. Frankly, I would suggest wiping system, data, cache and dalvik just for good measure. If she wants to keep a lot of the apps' progress/settings she has, I would install Titanium Backup and back up all user apps first before doing anything. She may have everything synced with her Google account as I believe you can sync apps and their data through Google now, but I haven't tested it yet.
To install the ROM, you'd just need to put it somewhere locally on your tablet, I have a '000Flash' folder on the root of my internal SD storage for any ROMs/kernels/modems (on my phone), etc. Place it in there, then get yourself into recovery. Once in recovery, wipe everything I mentioned above, then go back to the install/flash option of whatever recovery you're using. Flash the .zip file you just downloaded and put locally on your tab. Wait a few minutes and boot her up!
Just make sure you have the right software for the right version tablet you have, N5110 vs N5100.
hayzooos said:
Since this is an OS upgrade (4.1.2 to 4.2.2) a data wipe is highly suggested. Frankly, I would suggest wiping system, data, cache and dalvik just for good measure. If she wants to keep a lot of the apps' progress/settings she has, I would install Titanium Backup and back up all user apps first before doing anything. She may have everything synced with her Google account as I believe you can sync apps and their data through Google now, but I haven't tested it yet.
To install the ROM, you'd just need to put it somewhere locally on your tablet, I have a '000Flash' folder on the root of my internal SD storage for any ROMs/kernels/modems (on my phone), etc. Place it in there, then get yourself into recovery. Once in recovery, wipe everything I mentioned above, then go back to the install/flash option of whatever recovery you're using. Flash the .zip file you just downloaded and put locally on your tab. Wait a few minutes and boot her up!
Just make sure you have the right software for the right version tablet you have, N5110 vs N5100.
Click to expand...
Click to collapse
Thank you very much, the same as I am use to really. I do have my system backed up, as well as Titanium Back UP for apps and data. So should be fine. I do have the N5110
BobC43 said:
Thank you very much, the same as I am use to really. I do have my system backed up, as well as Titanium Back UP for apps and data. So should be fine. I do have the N5110
Click to expand...
Click to collapse
No problem, shouldn't be too different than what you're already used to, but I can understand the need for clarification when it comes to different devices as they're all a little bit different.
OK, on 4.2.2, no problems at all after I found how to turn debugging mode on. THAT IS STRANGE
BobC43 said:
OK, on 4.2.2, no problems at all after I found how to turn debugging mode on. THAT IS STRANGE
Click to expand...
Click to collapse
Hello!
Can you please share how to turn on debugging mode? Thank you in avdavauce!
Sent from my GT-N5110 using xda premium
gqinside said:
Hello!
Can you please share how to turn on debugging mode? Thank you in avdavauce!
Sent from my GT-N5110 using xda premium
Click to expand...
Click to collapse
Settings / About Device /
Then tap the build number 7 times. As you are getting close to 7 taps, the screen will tell you how many more till you are in development.
BobC43 said:
Thank you very much, the same as I am use to really. I do have my system backed up, as well as Titanium Back UP for apps and data. So should be fine. I do have the N5110
Click to expand...
Click to collapse
Also you will need to have CWM or TWRP installed as a custom recovery for it to work. There are plenty of options for installing and the new versions that are non touch should fix any issues uyou had previously. Happy flashing!
Sent from my GT-N5110 using XDA Premium HD app
Yo Nate Dogg!!!!
I am Here!
Now we can get Jammin on this one too!!!!
I will be Flashing this on Friday, Looking around the hood now just seeing what is what on this Note 8!
Get some of that fly a$$ **** from the Note 2 over here! lol
Piece my brotha!
See you soon!
~B
@beanstown106
I'm all rooted and running the ROM...
This ROM definitely needs a little TLC...
How about putting a list of requests together so maybe we have an Idea of what we can expect?
Here is a thread for customizing this ROM!!!
Here is a link to the Google Edition 4.3 Camera
This works I have it installed. and it is pretty sweet. (even on a 5mp Camera)
I installed xposed framework today and it works well on this ROM. Has anyone else tried this?
You can go here for other mods to add to it...
After you have the Xposed frame work installed you can install the app_settings see attachments, to modify the per app DPI settings.
example, you open up app settings go to gmail, set the dpi to 160 & screen (dp): 1000x1600
I did this for System settings as well and they look nice.
Play around with it and we can build on it...
You can find other mods that you can see if they work and build a list in a new thread. REMEMBER TO BACK UP FIRST!
Ge the disabler in attachments to flash in case you get into a boot loop. These work well since this is a stock ROM.
NottachXposed works very nicely for this ROM... You just have to play with it a little bit, but you can tweak it out nicely...
Don't forget to grab the Multi-Window Manager over in the Themes and app section. It works Great Without any flaws so far...!
If you need a 3-way reboot menu, here is an excellent app here for that...
Knock it Off Please
OK, please stop with all the "bad-mouthing" and "trolling" and... the "Off-Topic" posts. You know the rules, especially in the Dev Forum.
You wanna post garbage or talk about who's gonna do what, then go to the main Android "Off Topic" forum.
Thread cleaned. (please don't make me come back in here again)
MD
Thanks for the deodexed, recovery flashable rom. I just flashed it and got everything set up. So far everything is running great.
Sent from my GT-N5110 using Xparent Green Tapatalk 2
Hey guys!
I have been using Omni ROM for a while. And yes, its a pretty stable KitKat ROM! Almost everything works fine without any issue. But the thing that bugged me was root. There wasn't root permission in the the ROM. So no link2sd and no other script works for expanding storage.
So basically, the only major problem in the ROM was ROOT.
So I worked it out and present before you an easy method.
Prerequisites:
Omni ROM
Root flashable zip
Method:
Download the required packages
Install Omni ROM (Refer installation from this)
Reboot
Now go back to recovery and flash root.zip
Reboot
Enjoy
NOTE:
You need to have atleast 3mb in /system
This zip is only for ARM based devices and won't work with x86 based devices
P.S. Personally this is the best ROM to use as daily driver
rhar**** said:
Hey guys!
I have been using Omni ROM for a while. And yes, its a pretty stable KitKat ROM! Almost everything works fine without any issue. But the thing that bugged me was root. There wasn't root permission in the the ROM. So no link2sd and no other script works for expanding storage.
So basically, the only major problem in the ROM was ROOT.
So I worked it out and present before you an easy method.
P.S. Personally this is the best ROM to use as daily driver
Click to expand...
Click to collapse
Congrats! Downloading and will give a try
Looks very much like a normal superuser or superSU install.
Very good that will work on other devices as well. I mean, ours would not have all the google apps on system. No room for one of them
The su binary is much smaller than cm-11's.
Comment, should probably go on xbin, be symlinked to bin.
Normally, superuser.apk is installed as a user app and would be updated as such from play. But may try it this way!
Great work.
Dovidhalevi said:
Looks very much like a normal superuser or superSU install.
Very good that will work on other devices as well. I mean, ours would not have all the google apps on system. No room for one of them
The su binary is much smaller than cm-11's.
Comment, should probably go on xbin, be symlinked to bin.
Normally, superuser.apk is installed as a user app and would be updated as such from play. But may try it this way!
Great work.
Click to expand...
Click to collapse
We can have Google apps on our phone as well. I have managed to do so, at least the important ones.
Gonna upload that too soon
rhar**** said:
We can have Google apps on our phone as well. I have managed to do so, at least the important ones.
Gonna upload that too soon
Click to expand...
Click to collapse
They should NOT be on system/app, especially on our phones. Install from Play as user apps, let link2sd symlink them.
Anyway, flash worked like a charm! Neatly got rid of CWM's superuser, installed superSU which I will leave as a system app for now.
Note that it behaves like what I tried, spawns multiple instances of su and daemonsu (should daemonsu be symlinked to su--why have two copies?).
Link2sd played immediately. Tasker took some time. Xposed almost did not make it. Finally, after a blank screen freeze, reboot, a few attempts, got the dialog! Talking a good ten minutes or aggrivation. What is unique about how this asks for root?
Dovidhalevi said:
They should NOT be on system/app, especially on our phones. Install from Play as user apps, let link2sd symlink them.
Anyway, flash worked like a charm! Neatly got rid of CWM's superuser, installed superSU which I will leave as a system app for now.
Note that it behaves like what I tried, spawns multiple instances of su and daemonsu (should daemonsu be symlinked to su--why have two copies?).
Link2sd played immediately. Tasker took some time. Xposed almost did not make it. Finally, after a blank screen freeze, reboot, a few attempts, got the dialog! Talking a good ten minutes or aggrivation. What is unique about how this asks for root?
Click to expand...
Click to collapse
Yes, it takes a bit of time sometimes. It's slow and can't help it .
So here's my suggestion, in settings, set default access to 'grant'. It's a bit faster this way
Sent from my LG-P500 using XDA Premium 4 mobile app
rhar**** said:
Yes, it takes a bit of time sometimes. It's slow and can't help it .
So here's my suggestion, in settings, set default access to 'grant'
Click to expand...
Click to collapse
The problem is unique to Xposed. Everything else comes either immediately to quickly enough. I will post to that dev thread about this.
Dovidhalevi said:
The problem is unique to Xposed. Everything else comes either immediately to quickly enough. I will post to that dev thread about this.
Click to expand...
Click to collapse
Worked fine for me.
Try again by giving root permissions by default
ROM is good.
However, after flash GAPPSLight. Root have gone. It should be not enough space in /system
z1022 said:
ROM is good.
However, after flash GAPPSLight. Root have gone. It should be not enough space in /system
Click to expand...
Click to collapse
Shouldn't happen if the OTA survival mode is present. But ya, the only problem may be the space in /system
z1022 said:
ROM is good.
However, after flash GAPPSLight. Root have gone. It should be not enough space in /system
Click to expand...
Click to collapse
MUST trim the ROM. Omni is no different here, maybe even bigger.
The superSU installation wil temporarily move some stuff to make room for the root install, then move it back. However, none of that stuff belongs on system. There is not enough room for even one of those gapps. GAPPSLight is trivial and should not fill you up. In other words, trim the ROM first.
---------- Post added at 12:36 AM ---------- Previous post was at 12:30 AM ----------
rhar**** said:
Yes, it takes a bit of time sometimes. It's slow and can't help it .
So here's my suggestion, in settings, set default access to 'grant'. It's a bit faster this way
Click to expand...
Click to collapse
First thing I tried (with my simple daemon start method). Never came up. But up and running now, all's well that ends well.
Question: SuperSU offers to make a backup script first time the UI is exercised. Promises to survive further flashes. Does this indeed work (and ... how)?
I will copy files and edit a version of the setup script from this zip and have them available on my sdcard just in case
Modded Omni Rom
@rhar****,
I have a request 4 u. Please make a modded OMNI rom 4 us. Yesterday I flashed the Jenkins 10th march version. I can't use for more than a while, 'cause i can't install any file manager or any .apk, moreover things went wrong after i flash gapps.. But I loved it and want to hav it as a daily driver. So, if u don't hv any project / busy schedule then pls.try. Anyway 2day i will flash this build.
sumansur2008 said:
@rhar****,
I have a request 4 u. Please make a modded OMNI rom 4 us. Yesterday I flashed the Jenkins 10th march version. I can't use for more than a while, 'cause i can't install any file manager or any .apk, moreover things went wrong after i flash gapps.. But I loved it and want to hav it as a daily driver. So, if u don't hv any project / busy schedule then pls.try. Anyway 2day i will flash this build.
Click to expand...
Click to collapse
Smell a rat! Trim that ROM first.
Omni has it own file manager called "Documents." The CMFileManage can be installed as a user app.
BUGs on Omni -- I still am using a daily driver, though:
1. Clock FC's. Widgets appear fine (I use Chronus) but no alarms, stopwatch, wordclocks, etc.
2. GPS apparently not functioning, though location services seem to work. Some apps dependent on GPS FC.
3. Long widget, background process startup times but much better than cm-11
4. About 10 meg worth of apps symlinked by link2sd will be un-symlinked (more probably dereferenced) on start up. Easily cleaned up every few starts. Make sure to recreate link2sd build scripts freshly, reboot after new flash or internal storage mishaps worse than this.
5. Will usually get a wait message on system on startup. Everything works anyway, just open home screen and dismiss.
Those dl builds are genuine "nightlies," scheduled, regardless of whether or not any changes made that will be noticed.
Dovidhalevi said:
Smell a rat! Trim that ROM first.
Omni has it own file manager called "Documents." The CMFileManage can be installed as a user app.
BUGs on Omni -- I still am using a daily driver, though:
1. Clock FC's. Widgets appear fine (I use Chronus) but no alarms, stopwatch, wordclocks, etc.
2. GPS apparently not functioning, though location services seem to work. Some apps dependent on GPS FC.
3. Long widget, background process startup times but much better than cm-11
4. About 10 meg worth of apps symlinked by link2sd will be un-symlinked (more probably dereferenced) on start up. Easily cleaned up every few starts. Make sure to recreate link2sd build scripts freshly, reboot after new flash or internal storage mishaps worse than this.
5. Will usually get a wait message on system on startup. Everything works anyway, just open home screen and dismiss.
Those dl builds are genuine "nightlies," scheduled, regardless of whether or not any changes made that will be noticed.
Click to expand...
Click to collapse
I saw a file manager namely"Documents", but i couldn't install any .apk from there, it said " the file can't be opened" or such that. I flash a file explorer but can't enter enter any subfolder in sdcard. But i will have a another go 2day.
sumansur2008 said:
@rhar****,
I have a request 4 u. Please make a modded OMNI rom 4 us. Yesterday I flashed the Jenkins 10th march version. I can't use for more than a while, 'cause i can't install any file manager or any .apk, moreover things went wrong after i flash gapps.. But I loved it and want to hav it as a daily driver. So, if u don't hv any project / busy schedule then pls.try. Anyway 2day i will flash this build.
Click to expand...
Click to collapse
Yea, I'll try to make a Trimmed ROM soon
sumansur2008 said:
I saw a file manager namely"Documents", but i couldn't install any .apk from there, it said " the file can't be opened" or such that. I flash a file explorer but can't enter enter any subfolder in sdcard. But i will have a another go 2day.
Click to expand...
Click to collapse
For time being, to install any apk, get a file manager. If you cant, then from Documents, navigate to the apk and hold on it. It will be highlighted. Now copy it and from documents' side panel (swipe from left) go to Downloads and paste it there. Now go to Downloads from app drawer and install from there.
The root is working pretty fine. I tried a lot of times. Sorry to say it now when maybe a week passed, but I forgot to comment. Omni seems to be a good project. And this is the first taste of omni and kit kat, so doble pleasure.
chalo99 said:
The root is working pretty fine. I tried a lot of times. Sorry to say it now when maybe a week passed, but I forgot to comment. Omni seems to be a good project. And this is the first taste of omni and kit kat, so doble pleasure.
Click to expand...
Click to collapse
Yeah. I too use it as a daily driver, and so am thinking of mading it a bit. Like Halo))) or multiwindow
But, unfortunately, not anytime soon
rhar**** said:
Yeah. I too use it as a daily driver, and so am thinking of mading it a bit. Like Halo))) or multiwindow
But, unfortunately, not anytime soon
Click to expand...
Click to collapse
Xposed Xhalo will work in cm-11 but not in omni! Omni takes the window's flag for ... its own multiwindow. So ... where is that?
Xposed multiwindow (its own UI) might work in omni or alongside halo or xhalo ... uses a different flag to avoid the conflict.
In any event, Xposed might be the best way to get these things.
Dovidhalevi said:
Xposed Xhalo will work in cm-11 but not in omni! Omni takes the window's flag for ... its own multiwindow. So ... where is that?
Xposed multiwindow (its own UI) might work in omni or alongside halo or xhalo ... uses a different flag to avoid the conflict.
In any event, Xposed might be the best way to get these things.
Click to expand...
Click to collapse
Yea, I was also wondering about multi-window
And never noticed the thing about HALO. Will try to get something done.
Hi rhar****,
I sucessfully flashed the root.zip into my device(Samsung Galaxy Tab2 10.1 GT-P5110, OMNI6.0.1 based on Android 6), but the SuperUser couldn’t work without a binary file.
The screenshot is in Chinese, it said that ‘The SU Binary file is not installed, and it can’t be downloaded and installed via SuperUser. If you just upgraded to Android 4.3, go to the forum and download the binary file, then install it manually. ’
Can you please offer me the binary file? Or give me an URL?
CM12.1 (5.1.1 Lollipop) Official nightly builds for the Droid Razr (CDMA/GSM)
*We are not responsible for any damage you or these builds do to your phone, flash at your own risk!
**Please note that I am just maintaining the thread, and do not take credit for these builds.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
These builds require SafeStrap v3.75 or later.
Downloads
CDMA/spyder: http://download.cyanogenmod.org/?device=spyder
GSM/umtsspyder: http://download.cyanogenmod.org/?device=umts_spyder
Contributors
gabhroo123, stargo, Hashcode, Dhacker29, and others!
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Sweet thanks for starting a separate thread rather then diving for it hahaha although it was fun being all new and such and hey look I'm first.woot
ktimque said:
CM12.0 (5.0 Lollipop) Unofficial builds for the Droid Razr (CDMA/GSM)
* Boot to stock
* Start the old Safestrap-version
* Uninstall Recovery
* Uninstall the Safestrap APP (due to the different key)
* Install the "debug" Safestrap-version (signed with standard test-key)
* Install recovery again
If you enter recovery, the device will now also execute a new
kernel, so you will get the kexec-vibrate at this point, too.
This new Safestrap is fully compatible with old ROMs, you don't need
to downgrade if you want to install any old ROM.
Click to expand...
Click to collapse
Thank you for the tutorial.
Are calls working?
Just a report
I accidentally installed this alpha version over a Kitkat install (AOPK) and for my surprise I haven't had any trouble at all, I have actually everything working just fine, all my apps and settings, no FCs... Well, this build are this good... Waiting patiently for bugs corrections like video acceleration... My phone is a rocky tester, keep the builds coming, I'll try to test and report them all...
---------- Post added at 08:38 PM ---------- Previous post was at 08:12 PM ----------
I can't find an option to change between diferent users, I feel like it was removed, which could be explained by the lack of memory of our devices to keep two or more users at same time, even though I kind of wanna try it.... The lantern isnt working either, probably related to the camera stuff, and is just it...
icarome said:
I accidentally installed this alpha version over a Kitkat install (AOPK) and for my surprise I haven't had any trouble at all, I have actually everything working just fine, all my apps and settings, no FCs... Well, this build are this good... Waiting patiently for bugs corrections like video acceleration... My phone is a rocky tester, keep the builds coming, I'll try to test and report them all...
---------- Post added at 08:38 PM ---------- Previous post was at 08:12 PM ----------
I can't find an option to change between diferent users, I feel like it was removed, which could be explained by the lack of memory of our devices to keep two or more users at same time, even though I kind of wanna try it.... The lantern isnt working either, probably related to the camera stuff, and is just it...
Click to expand...
Click to collapse
Are you able to make calls and receive them?
Ive tried cm 12 on my stock slot with old safestrap (xt 910) and yeah calls works fine. I experience slow response when executing (opening and installing) apps. I ll try with new safestrap and report back. Quite nice room, ty devs for making this old phone rocks....
Hello me!! Its me again!!
Noe! said:
Are you able to make calls and receive them?
Click to expand...
Click to collapse
Yes, I forgot to mention but I use the XT910, after deleting cellbroadcastreceiver.apk (or something) I got signal 100% of the time with data (3g) and calls working like charming, nothing to complain in here
CM12 Safe Strap question
Hey Guys,
I have 2 questions for installing CM12 on an XT912 Razr Phone.
Can any of you guys tell me what version of Safe Strap you are using? I still have Safe Strap 3.73 but I hear that one needs an update for it to use CM12 on an XT912 Razr phone. Is there a patch or update for Safe Strap and does it affect one's existing CM11 and stock installs?
How much partition size does one need to install the new CD12 Alpha on a Razr phone? Typically I use the following partition sizes for CM11:
Slot1 - CM11
System: 700 Mb
Data: 2,000 Mb
Cache: 300 Mb
Is this going to work for CM12 or should the partitions be larger? Since I have CM11 on slot 1 and stock is JB, will CM12 work on slot 2?
If you know, please respond. This would help me and others to get a good start on trying out the new CM12 Alpha builds. Thanks a lot for your testing and posting!
Ohmster said:
Hey Guys,
I have 2 questions for installing CM12 on an XT912 Razr Phone.
Can any of you guys tell me what version of Safe Strap you are using? I still have Safe Strap 3.73 but I hear that one needs an update for it to use CM12 on an XT912 Razr phone. Is there a patch or update for Safe Strap and does it affect one's existing CM11 and stock installs?
How much partition size does one need to install the new CD12 Alpha on a Razr phone? Typically I use the following partition sizes for CM11:
Slot1 - CM11
System: 700 Mb
Data: 2,000 Mb
Cache: 300 Mb
Is this going to work for CM12 or should the partitions be larger? Since I have CM11 on slot 1 and stock is JB, will CM12 work on slot 2?
If you know, please respond. This would help me and others to get a good start on trying out the new CM12 Alpha builds. Thanks a lot for your testing and posting!
Click to expand...
Click to collapse
As far as I understand, the new SafeStrap is needed for ROMs beyond 11/20.
I have the same setup as you: Stock is JB, Slot 1 is CM11 and now Slot 2 is CM12. Works perfectly.
I used these sizes:
System: 700 Mb
Data: 2,300 Mb
Cache: 310 Mb (Somehow SS defaulted to 10MB and let me increment in units of 100MB.)
At a glance, CM12 seemed to use a bit more space out of the box than CM11, but I did not really do any in-depth analysis. Maybe it is just due to GApps package or ART or whatever.
I originally only had around 1700Mb available for data, and that was just almost enough for the limited number of apps that I have. There was less than 30mb left, and I could not update any apps.
I recreated the slot with 2300mb, and it has worked great.
Again, I have not done any in-depth analysis. These are just my observations.
gabhroo123 said:
As far as I understand, the new SafeStrap is needed for ROMs beyond 11/20.
I have the same setup as you: Stock is JB, Slot 1 is CM11 and now Slot 2 is CM12. Works perfectly.
I used these sizes:
System: 700 Mb
Data: 2,300 Mb
Cache: 310 Mb (Somehow SS defaulted to 10MB and let me increment in units of 100MB.)
At a glance, CM12 seemed to use a bit more space out of the box than CM11, but I did not really do any in-depth analysis. Maybe it is just due to GApps package or ART or whatever.
I originally only had around 1700Mb available for data, and that was just almost enough for the limited number of apps that I have. There was less than 30mb left, and I could not update any apps.
I recreated the slot with 2300mb, and it has worked great.
Again, I have not done any in-depth analysis. These are just my observations.
Click to expand...
Click to collapse
Would you recommend using those sizes on Slot 1? Also, which GApps package are you using, and which apps come on it? Thanks.
Thanks for the much needed CM12 thread!
Noe! said:
Would you recommend using those sizes on Slot 1? Also, which GApps package are you using, and which apps come on it? Thanks.
Click to expand...
Click to collapse
If those sizes worked on Slot 2, I don't see any reason why they wouldn't work for Slot 1..
For GApps, I used these: https://s.basketbuild.com/gapps
You migth want to start with the the ones linked in thread #1 if that works. For me, the download kept getting stuck.
The ones I installed had the most of the google stuff. I don't remember exactly. I ended up uninstalling a bunch of them (play movies, books, games, etc). Again, I usually don't spend a whole lot of time looking for the "perfect" gapps. It is pretty easy to get the missing ones, and remove the ones that I don't care about.
Of course, that's just me. You can try searching for some lollippop GApps (xda/Google) and install the one that you prefer (and probably share it here to help the community).
Best of luck.
gabhroo123 said:
If those sizes worked on Slot 2, I don't see any reason why they wouldn't work for Slot 1..
For GApps, I used these: https://s.basketbuild.com/gapps
You migth want to start with the the ones linked in thread #1 if that works. For me, the download kept getting stuck.
The ones I installed had the most of the google stuff. I don't remember exactly. I ended up uninstalling a bunch of them (play movies, books, games, etc). Again, I usually don't spend a whole lot of time looking for the "perfect" gapps. It is pretty easy to get the missing ones, and remove the ones that I don't care about.
Of course, that's just me. You can try searching for some lollippop GApps (xda/Google) and install the one that you prefer (and probably share it here to help the community).
Best of luck.
Click to expand...
Click to collapse
Download was taking forever on the Dev-Host link. Thanks for the link.
---------- Post added at 07:14 PM ---------- Previous post was at 06:59 PM ----------
Are you guys using any root apps? If so, are you using SuperSU?
Noe! said:
Download was taking forever on the Dev-Host link. Thanks for the link.
---------- Post added at 07:14 PM ---------- Previous post was at 06:59 PM ----------
Are you guys using any root apps? If so, are you using SuperSU?
Click to expand...
Click to collapse
Yes. Here are the steps I took:
* Download new safestrap
* Download ROM
* Download GApps
* Download SuperSU
* Boot into stock ROM/slot.
* Open up SafeStrap
* Uninstall recovery
* Close SafeStrap
* Uninstall SafeStrap
* Install new Safestrap apk (downloaded earlier)
* Open new SafeStrap (should say 3.75 on bottom-left)
* Install new recovery (very important)
* Once this is done, it should have a button to 'Reboot to recovery'. Click this.
* After rebooting to recovery, create a new slot (or re-use existing one, your choice).
* Install ROM, Gapps and SuperSU. This will take a while
* Reboot. This will also take a while.
Ohmster said:
Hey Guys,
I have 2 questions for installing CM12 on an XT912 Razr Phone.
Can any of you guys tell me what version of Safe Strap you are using? I still have Safe Strap 3.73 but I hear that one needs an update for it to use CM12 on an XT912 Razr phone. Is there a patch or update for Safe Strap and does it affect one's existing CM11 and stock installs?
How much partition size does one need to install the new CD12 Alpha on a Razr phone? Typically I use the following partition sizes for CM11:
Slot1 - CM11
System: 700 Mb
Data: 2,000 Mb
Cache: 300 Mb
Is this going to work for CM12 or should the partitions be larger? Since I have CM11 on slot 1 and stock is JB, will CM12 work on slot 2?
If you know, please respond. This would help me and others to get a good start on trying out the new CM12 Alpha builds. Thanks a lot for your testing and posting!
Click to expand...
Click to collapse
From trying it myself and from what I have read about ART it seems to take up about 20-25% more space. I bumped up the system to 800 or 900 depending on the gapps you use (micro or full) and data to 2500 or more depending on the number of apps and how large they are or you may get the low storage space warning.
gabhroo123 said:
Yes. Here are the steps I took:
* Download new safestrap
* Download ROM
* Download GApps
* Download SuperSU
* Boot into stock ROM/slot.
* Open up SafeStrap
* Uninstall recovery
* Close SafeStrap
* Uninstall SafeStrap
* Install new Safestrap apk (downloaded earlier)
* Open new SafeStrap (should say 3.75 on bottom-left)
* Install new recovery (very important)
* Once this is done, it should have a button to 'Reboot to recovery'. Click this.
* After rebooting to recovery, create a new slot (or re-use existing one, your choice).
* Install ROM, Gapps and SuperSU. This will take a while
* Reboot. This will also take a while.
Click to expand...
Click to collapse
Thanks for the tutorial. I didn't know if we had to use the beta of SuperSU. ETA of installation and bootup time?
Noe! said:
Thanks for the tutorial. I didn't know if we had to use the beta of SuperSU. ETA of installation and bootup time?
Click to expand...
Click to collapse
I didn't time it, but if I would say in the range of 1 hour for the entire process once you have all the required files downloaded to the device.
Once you boot, give it a few minutes to settle down and install any updates. Also, more time if you are restoring apps automatically from the play store.
It was great that Google let me pick the apps that I want to be restored when setting up the phone. Super helpful.
Since this is bumping a full major version, I wouldn't use Titanium Backup for restoring anything unless critical.
gabhroo123 said:
I didn't time it, but if I would say in the range of 1 hour for the entire process once you have all the required files downloaded to the device.
Once you boot, give it a few minutes to settle down and install any updates. Also, more time if you are restoring apps automatically from the play store.
It was great that Google let me pick the apps that I want to be restored when setting up the phone. Super helpful.
Since this is bumping a full major version, I wouldn't use Titanium Backup for restoring anything unless critical.
Click to expand...
Click to collapse
I assume this is because of ART right? Anyways, thank you for help.
Hi,
gabhroo123 said:
Cache: 310 Mb (Somehow SS defaulted to 10MB and let me increment in units of 100MB.)
Click to expand...
Click to collapse
As Cache is no longer used by the system, I decided to reduce the minimum size to 10MB. There is no point in wasting space for a partition which will only ever hold a few kB.
Cheers,
Michael
---------- Post added at 10:31 AM ---------- Previous post was at 09:56 AM ----------
Hi Paul,
Ohmster said:
Can any of you guys tell me what version of Safe Strap you are using? I still have Safe Strap 3.73 but I hear that one needs an update for it to use CM12 on an XT912 Razr phone. Is there a patch or update for Safe Strap and does it affect one's existing CM11 and stock installs?
Click to expand...
Click to collapse
You need the new Safestrap you can find here: http://droid.cs.fau.de/Safestrap/
Please read the README.txt (also included in the first post).
How much partition size does one need to install the new CD12 Alpha on a Razr phone? Typically I use the following partition sizes for CM11:
Slot1 - CM11
System: 700 Mb
Data: 2,000 Mb
Cache: 300 Mb
Is this going to work for CM12 or should the partitions be larger?
Click to expand...
Click to collapse
Yes, that's fine. No need for bigger partitions.
Just use the default for cache (10MB) and don't increase it.
Since I have CM11 on slot 1 and stock is JB, will CM12 work on slot 2?
Click to expand...
Click to collapse
I'm pretty sure it will work just fine in Slot 2. (I had it there at first and then accidentally overwrote Slot 1, because I didn't pay attention, so now I'm using Slot 1)
Cheers,
Michael
Thank you
Thank you for the Early builds!
Appreciated the Effort!
Testing it now! Will get back to you
.:Edit:.
Installation Guide @ktimque if this helps for the OP
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5 (Lollipop), 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 recovery. To install a recovery 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 https://dl.dropboxusercontent.com/u...cclaim-eng-recovery-UNOFFICIAL-20150606.0.img) and flash it with fastboot.
If you have a CM 10.1 or CM 11 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 (and all bugs fixed), you will be able to use CM Updater
Settings->About tablet->CyanogenMod updates->Refresh
THE NEW NIGHTLIES HAVE EMULATED STORAGE ENABLED. YOU LOOSE ALL YOUR DATA. MAKE SURE YOU BACKUP!!!! THE INTERNAL EMMC 1GB PARTITION IS ALSO NOT ACCESSIBLE ANYMORE. COPY THE CONTENT. THE EXTERNAL SDCARD IS NOT USED ANYMORE AS PRIMARY STORAGE. ALL APP DATA ON THE SDCARD WILL BE LOST. I ALSO RECOMMEND TO WIPE.
BACKUP!
RE-PARTITIONING IS NOT MANDATORY. IF YOU WANT TO RECLAIM THE 1GB PARTITION (called media) YOU CAN TRY TO FOLLOW THE RE-PARTITION GUIDE:
https://docs.google.com/document/d/1wSAaAZfQcnvkiHKlbZ7_H1h67m2kx0mq-p3Wjgue3qA/edit?usp=sharing
PLEASE COMMENT ON THE DOCUMENT IF SOMETHING IS NOT CLEAR.
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 recovery, flash the zip, wipe, and reboot.
Support:
For any issues encountered, please post into this forum, but add steps to reproduce and dmesg, logcat and audit.log information. If you don't know what this is or how to get them, try to find that out first before posting here.
Thanks:
hashcode, ntemis, kuzma30, fattire, mik_os, chrmhoffmann, and many others that contribute to cyanogenmod and especially this version.
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. Also many thanks for the L bringup help.
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 and L 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 gapps. It can be found somewhere....
ATTENTION: IT SEEMS THAT DHACKER'S L GAPPS ARE TOO BIG TO FIT INTO THE SYSTEM PARTITION. Try to find a smaller one.
- The SELINUX policies are enforced now.
Known issues:
- system partition is too small for full gapps. use a mini gapp package.
- the touchscreen firmware flasher doesn't work on L. Use CM11 to flash it first.
Recently fixed:
- f2fs
- kernel updated to latest 3.0 stable
- developer settings and setup wizard (if you select backup) crash. that's fixed in nightly from 8-FEB-15.
- device encryption does work now (but who wants to do that? the device is laggy enough already )
- cmupdate / cm recovery: adb reboot recovery and cmupdater and auto install. Hopefully this is fixed now (not in nice way, but...). You need sdcard inserted to make this work (but I guess everybody has that anyway).
Get it from
http://download.cyanogenmod.org/?device=acclaim
Get ENG recovery from here. It allows to adb into recovery even when data is wiped.
File: https://dl.dropboxusercontent.com/u...cclaim-eng-recovery-UNOFFICIAL-20150606.0.img
md5sum: 6136fc49c5e9a32f115d40d762bb6f2d
Reserved
...
Amazing work Chris, Let the flashing begin.
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Hi,
Odd. I flashed the same (before uploading).
Did you upgrade recovery? Did you check md5 of download?
Chris
chrmhoffmann said:
Hi,
Odd. I flashed the same (before uploading).
Did you upgrade recovery? Did you check md5 of download?
Chris
Click to expand...
Click to collapse
ROM: 78f32eb89778b31a569644b21fc1e8f3
Recovery: d37f29808a682e7806fa7b77dc940453
Installed just fine here, even Netflix works!!
thanks for everyone's hard work.
topdawg7793 said:
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Click to expand...
Click to collapse
Can you share where you got the download for twrp 2.8.4.0? Thanks!
Sent from my LG-E970 using XDA Free mobile app
billy8362 said:
Can you share where you got the download for twrp 2.8.4.0? Thanks!
Sent from my LG-E970 using XDA Free mobile app
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/acclaim
Download the latest version, rename it to "recovery.img". Flash it in fastboot.
If you'd rather not go that route, download a flashable of an older version of TWRP, use 7zip to delete the recovery.img in that folder, then move this new TWRP into that folder. Then flash that.
topdawg7793 said:
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Click to expand...
Click to collapse
Hi,
Can you provide /tmp/recovery.log for those who can't flash with that provided recovery?
Chris
Installed with latest TWRP. ROM working fine, no random reboots. Have some troubles with SDcard: unmounting ok, formating, mounting, detecting not working.
Update:
All ok after i format 10+11 partitions.
chrmhoffmann said:
Hi,
Can you provide /tmp/recovery.log for those who can't flash with that provided recovery?
Chris
Click to expand...
Click to collapse
Too busy to play with my Nook this week. I recall it was having issues with signature verification. I wasn't able to locate a way to disable signature verification.
Pepe.II said:
Installed with latest TWRP. ROM working fine, no random reboots. Have some troubles with SDcard: unmounting ok, formating, mounting, detecting not working.
Click to expand...
Click to collapse
Same issue here ... used TWRP ... everything seems to work except I don't have an SD card ... which is a deal breaker for this tablet.
UPDATE: Used the wrong GAPPS the first time ... working fine now ... sluggish, but nothing seems to be broken ... and I didn't do a factory reset ... just cache/davlik cache clear then flash
Get ready for Bexus-L
Kickass! Thank you to every dev who made it possible for Android L to be on NT!
Question: is it absolutely mandatory to install Google's crapware Gapps? I use F-Droid on all my other Android devices. They run much lighter.
---------- Post added at 10:47 PM ---------- Previous post was at 10:23 PM ----------
Edit: It works without Gapps. Also, bug found: if you enable development settings, when you tap on developer options, it says "Unfortunately, Settings has stopped"
Edit2: Kodi (XBMC) for Android does not work. Says "Cannot parse CPU features." Didn't happen on CM11.
Tell me more about this F-Droid ... what does it gain me over GAPPs? Performance?
sagirfahmid3 said:
Kickass! Thank you to every dev who made it possible for Android L to be on NT!
Question: is it absolutely mandatory to install Google's crapware Gapps? I use F-Droid on all my other Android devices. They run much lighter.
---------- Post added at 10:47 PM ---------- Previous post was at 10:23 PM ----------
Edit: It works without Gapps. Also, bug found: if you enable development settings, when you tap on developer options, it says "Unfortunately, Settings has stopped"
Edit2: Kodi (XBMC) for Android does not work. Says "Cannot parse CPU features." Didn't happen on CM11.
Click to expand...
Click to collapse
jerrygarcia4295 said:
Tell me more about this F-Droid ... what does it gain me over GAPPs? Performance?
Click to expand...
Click to collapse
Google's apps come with Google's playstore, sync services, etc, which add overhead to wi-fi and CPU cycles.
F-droid doesn't have those services. It's pretty much like a Linux package manager--you use it to install and keep track of open source packages.
Besides, I only use my phones and tablets for Kodi and phone calls. I'm not into Google Hangouts or YouTube, etc. I don't take pictures, I don't use the GPS...
IMO, I find Android to be completely useless. I wish there was a completely open source and open hardware Linux running phone. With Linux, you can do whatever you want.
I had to go back to CM11 ... superuser appears to be broken when I go to CM12 ... is there a fix for this?
jerrygarcia4295 said:
I had to go back to CM11 ... superuser appears to be broken when I go to CM12 ... is there a fix for this?
Click to expand...
Click to collapse
I haven't installed cm12 on my nook tablet yet, but on other cm12 installs, you have to enable superuser in Settings / Developer options / Root access. Click one of the boxes other than the default "Disabled". If that doesn't work, some folks swear by SuperSU, which you can find in the Play Store