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!
Related
NOTE:
This will be my last GB rom since sources for Galaxy S Advance has been released, I'll by making a JellyBean port of the SGSA to the Ace 2. Unless Sammy releases JB to our phone. I'm also going to buy Galaxy S Advance or the Galaxy S III mini(not available yet here in HK execpt the parallel ones and in expansys.com.hk) to replace my Ace 2.
Introduction:
First of all, I made this ROM specifically for the Galaxy Ace 2 GT-I8160 with a baseband of ZSLG1/ZSLK2 which is from Hong Kong.
The reason I made this ROM started with a severe scrolling problem with all Galaxy Ace 2 here in Hong Kong installed with the I8160ZSLG1 firmware, scrolling continuously is not possible because as soon as you scroll while the menu list is still moving or scrolling, touchscreen becomes unresponsive, unless you re touch the screen. this ROM has no BusyBox installed, its just a stock ROM with same UI, same funtionality
UPDATE V3:
Sorry for the late responses. I've been busy working here in my company. Anyway, this will be my last GB rom since sources for Galaxy S Advance has been released, I'll by making a JellyBean port of the SGSA to the Ace 2.
Original Stock ROM I8160ZSLK2(Hong Kong)
GT-I8160V3
Link to Stock XXLK7 Kernel with CWM and init.d support
List of Changes:
NEW
-based on I8160XXLK7
-permanent removal of CPU rendering, uses GPU rendering by default.
-init.d support
--place your favorite init.d tweaks inside /system/etc/init.d
-busybox 1.19.4/ZipAlign/Sqlite3(compatible with the newest Supercharger V6)
-deleted some unneeded files from lib folder.
Recent Changes
-all language files are for UK, so there's no chinese, but if you know english, that would be fine
-multi tap alphanumeric keypad bug fixed
-scrolling bug fixed
-STOCK UI(Same functions, same look and feel)
-Zipaligned APK's before packing
-Deodexed
-Rooted
-disabled ScrollingCache for smooth scrolling(modified framework.jar, not a build.prop tweak)
-disabled all camera sounds including autofocus
-Samsung bloatwares REMOVED
NOTE:
It is recommended to flash the kernel from the link provided above.
Installing instructions:
-make a backup of your phone
-flash the stock ZSLK2 firmware
-flash the kernel from the link provided above
-format /data, /cache and /system(THIS WILL DELETE ALL YOUR SETTINGS AND DATA)
-wipe dalvik cache
-wipe battery stats
-unmount all volumes
-flash the ZIP file and wait it to finish
-reboot(startup takes long time since dalvik is being rebuild)
-when booting is done, setup your phone, language, time, etc.
-before installing apps, reboot phone
-then you can start installing your apps
NOTE:
-Kies over Wifi is removed, clicking on it from the menu will force close the settings application.
-Don't attempt to flash this ROM to a different baseband, your phone will still work but you will not have a GSM/3G/Network signal.
WARNING APPLIES ONLY TO V1 and V2:
WARNING: BusyBox is partially supported using the busybox installer, however, there are many chances that it will make your device bootloop.
Version 2:
Original Stock ROM ZSLG1(Hong Kong)
GT-I8160V2
XXLI2 stock kernel
Version 1:
DOWNLOAD:
CWM_flashable_ROM
all credit goes to dsixda for the android kitchen
sorry, dumb question again.
in cwm menu, i don't see option to unmount volume, so how could i do that??
edit: found it in "mount and storage", sorry.
Everything seems running just fine, but the battery graph seems broken (gaps in between) in battery status??
---------- Post added at 11:28 PM ---------- Previous post was at 11:14 PM ----------
and the chinese character in your rom is simplied chinese (GB) while i use tradional chinese (BIG5).
Could you list the files responsible for those tradional chinese chars and i put it back to system via sort of root explorer??
Thank you.
How do we flash the stock rom back ? Do i need to wipe cache again and stuff?
And what do i choose in odin? cuz the file is just one.. and it asks for bootloader and etc?
Bocko92 said:
How do we flash the stock rom back ? Do i need to wipe cache again and stuff?
Click to expand...
Click to collapse
The stock rom provided here is for flashing with odin (select "pda" in odin, and select the .tar file)
I'm not sure if it is needed for odin, but if you flash rom with clockwork mod, then wipe /data, /system, and /cache is a must. just as the instruction stated, wipe these 3 partitions, then format it and umount them.
Bocko92 said:
And what do i choose in odin? cuz the file is just one.. and it asks for bootloader and etc?
Click to expand...
Click to collapse
In odin, select pda and then select the .tar file you downloaded. DO NOT touch anything else. then click start.
** Please correct me if I'm wrong. **
xmlnoob said:
Everything seems running just fine, but the battery graph seems broken (gaps in between) in battery status??
---------- Post added at 11:28 PM ---------- Previous post was at 11:14 PM ----------
and the chinese character in your rom is simplied chinese (GB) while i use tradional chinese (BIG5).
Could you list the files responsible for those tradional chinese chars and i put it back to system via sort of root explorer??
Thank you.
Click to expand...
Click to collapse
doesn't seem to have the battery problem on me though, take a look at the screenshot, for the languages, sorry I think its from the CSC files, you can try flashing a CSC provided on my original ROM, but I don't know what effect does it have when flashed, I didn't add any language since I don't read chinese, thou I live here in Hong Kong
anyway, I'll try extracting the language traditional chinese and will make a CWM flashable file.
Anyway, the reason why I have low battery life is I use
CPU Governor: performance(only at 800Mhz - no deep sleep, no downclock, CPU always at 800Mhz full speed)
I/O Scheduler: noop
results? no lags in UI or browser. but battery last only 1 day, than 2days using default CPU settings.
kevincaja said:
doesn't seem to have the battery problem on me though, take a look at the screenshot, for the languages, sorry I think its from the CSC files, you can try flashing a CSC provided on my original ROM, but I don't know what effect does it have when flashed, I didn't add any language since I don't read chinese, thou I live here in Hong Kong
anyway, I'll try extracting the language traditional chinese and will make a CWM flashable file.
Anyway, the reason why I have low battery life is I use
CPU Governor: performance(only at 800Mhz - no deep sleep, no downclock, CPU always at 800Mhz full speed)
I/O Scheduler: noop
results? no lags in UI or browser. but battery last only 1 day, than 2days using default CPU settings.
Click to expand...
Click to collapse
Yea, i think the gap is actually the period of hard reboot, so its a false alarm The graph is ok without reboot.
regarding cwm flashable langauge file, i dont need to wipe data/ factory reset for that i assume?
Thank you.
---------- Post added at 08:21 PM ---------- Previous post was at 08:13 PM ----------
And by the way, the phone number(caller id??) format is now showing XXX-XXX-XX, can i edit it to show XXXX-XXXX or XXXX XXXX ??
xmlnoob said:
Yea, i think the gap is actually the period of hard reboot, so its a false alarm The graph is ok without reboot.
regarding cwm flashable langauge file, i dont need to wipe data/ factory reset for that i assume?
Thank you.
---------- Post added at 08:21 PM ---------- Previous post was at 08:13 PM ----------
And by the way, the phone number(caller id??) format is now showing XXX-XXX-XX, can i edit it to show XXXX-XXXX or XXXX XXXX ??
Click to expand...
Click to collapse
no need to wipe, just flash the CWM zip file, the caller ID is a feature of the Indonesian firmware, so we either have to edit some framework or apk's which will take sometime
kevincaja said:
no need to wipe, just flash the CWM zip file, the caller ID is a feature of the Indonesian firmware, so we either have to edit some framework or apk's which will take sometime
Click to expand...
Click to collapse
Arrh, regarding the caller id format, just changed the langauge to "English (UK)" get the job done o7.
xmlnoob said:
Arrh, regarding the caller id format, just changed the langauge to "English (UK)" get the job done o7.
Click to expand...
Click to collapse
yeah it worked, thanks
Have you ever used multimount sd app on rooited ace2?? this little app works fine on my old rooted HTC wildfire but not on ace2.
Wondering if any way to do dual mount on ace2, ie connect to computer as mass storage device while still the sdcard(s) are still mounted on the phone.
Thank you.
xmlnoob said:
Have you ever used multimount sd app on rooited ace2?? this little app works fine on my old rooted HTC wildfire but not on ace2.
Wondering if any way to do dual mount on ace2, ie connect to computer as mass storage device while still the sdcard(s) are still mounted on the phone.
Thank you.
Click to expand...
Click to collapse
haven't tried it yet, but I think it will not work, I guess...
Hey btw, can i use the zip created by this http://uot.dakra.lt/kitchen/ on your rom? i want the battery status in notification bar to show %.
Thank you.
xmlnoob said:
Hey btw, can i use the zip created by this http://uot.dakra.lt/kitchen/ on your rom? i want the battery status in notification bar to show %.
Thank you.
Click to expand...
Click to collapse
Just followed the instruction there and it generated a cwm compatible zip, installed and works nicely.
xmlnoob said:
Just followed the instruction there and it generated a cwm compatible zip, installed and works nicely.
Click to expand...
Click to collapse
I was just about to say yes, but then since you've done it, I'd say good for you!
I8160L can't
sathit2499 said:
I8160L can't
Click to expand...
Click to collapse
this ROM is for the GT-I8160 only.
App Downloading Problem
Hi
Great rom. Quite stable and scrolling works properly now as advertised (I actually thought the broken scrolling was an intentional design and not a bug, but its back to normal now thanks to the rom)
I do have 3 questions / problems though.
1. Not sure if anyone else has this problem, but after flashing, I am unable to install any apps from the google market when on wifi. I can browse the market and websites easily, but the downloading bar never initiates. Once I switch to 3g, the app starts downloading. Before I flashed this rom, wifi downloading of apps from google play worked on the same network.
2. When I enter recovery mode (volume up + home + power) my recovery mode is "Android Recovery 3e" not CWM recovery. As such, I only have the options to flash a .zip or wipe data / cache. Is this normal. I tried flashing Antsm's update_su and it remains android recovery.
3. This is minor. But when I try and use LMT launcher (http://forum.xda-developers.com/showthread.php?t=1330150) with the pie buttons, only the home button works. The other buttons do not. They worked fine before I flashed this mod. Not sure if anyone else has tried LMT with this rom?
4. Will kernels or roms based off of other firmwares work with our HK baseband and still have working scrolling on 3g/phone?
Thx alot for your support for the HK firmware
chzyken said:
Hi
Great rom. Quite stable and scrolling works properly now as advertised (I actually thought the broken scrolling was an intentional design and not a bug, but its back to normal now thanks to the rom)
I do have 3 questions / problems though.
1. Not sure if anyone else has this problem, but after flashing, I am unable to install any apps from the google market when on wifi. I can browse the market and websites easily, but the downloading bar never initiates. Once I switch to 3g, the app starts downloading. Before I flashed this rom, wifi downloading of apps from google play worked on the same network.
2. When I enter recovery mode (volume up + home + power) my recovery mode is "Android Recovery 3e" not CWM recovery. As such, I only have the options to flash a .zip or wipe data / cache. Is this normal. I tried flashing Antsm's update_su and it remains android recovery.
3. This is minor. But when I try and use LMT launcher (http://forum.xda-developers.com/showthread.php?t=1330150) with the pie buttons, only the home button works. The other buttons do not. They worked fine before I flashed this mod. Not sure if anyone else has tried LMT with this rom?
4. Will kernels or roms based off of other firmwares work with our HK baseband and still have working scrolling on 3g/phone?
Thx alot for your support for the HK firmware
Click to expand...
Click to collapse
ANSWERS:
To 1: I to, experiences that problem, still fixing it
To 2: You didn't flash the kernel properly, try flashing a custom kernel again.
To 3: Don't know what launcher is that.
To 4: Yes it will, we only need to copy a some specific files for 3G/GSM/Network to work.
kevincaja said:
ANSWERS:
To 1: I to, experiences that problem, still fixing it
To 2: You didn't flash the kernel properly, try flashing a custom kernel again.
To 3: Don't know what launcher is that.
To 4: Yes it will, we only need to copy a some specific files for 3G/GSM/Network to work.
Click to expand...
Click to collapse
In that case, I'll wait for that wifi fix. Will keep using the this rom in the meantime.
I'll wry about cwm next time I need to flash.
And the launcher problem started working but itself. Don't think it's a rom problem. Thx again!
Sent from my GT-I8160 using xda app-developers app
GOOGLE APPS PACKAGE FOR CM11 BUILDS
System version
These versions of gapps will be installed on your system partition (/system) just like official gapps packages.
Link to the latest package:-
gapps-kk444-20140724-v2.2.zip (7.9 MB only)
Requirements:-
Need a cm11 build from Jenkins' project: cm-ota which is built after 22/06/2014 (users of older builds are recommended to use gapps-v1.0).
Need a minimium of 12 MB free space in system partiton (Tip for galaxy5 users: 20 MBs of free space is there by default on cm11 builds after 22/07/2014).
Need CWM recovery 6.0.5.2+ by psyke83/Jenkins-cm-recovery (gapps-v1.0 can be installed using any recovery).
How to install? (With a cm11 clean install?)
Reboot to recovery. (Use CWM 6.0.5.2+ by psyke83/Jenkins)
Wipe Data/ Factory Reset.
Go to 'Install zip from sdcard' and select the ROM file (only cm11) you want to install from your sdcard. Let the process complete.
Then, Choose the above given gapps package (only use v2.0 or later for cm11 builds after 22/07/2014) for cm11 in 'install zip from sdcard'.
Then just reboot and you're done!
How to install? (Already installed the cm11 and just want to install gapps now?)
Reboot to recovery (CWM 6.0.5.2+ by psyke83/Jenkins).
Choose the gapps package (only use v2.0 or later for cm11 builds after 22/07/2014) in 'install zip from sdcard' option.
Then just reboot and you're done!
Changelog:-
v2.2
Play-Store updated to latest version: 4.9.13 (released on 23/07/2014).
Fixed updater script to install on all other devices.
v2.0 (Removed link because this version worked only on Galaxy 5)
Updated updater-script to make installation compatible with new CWM 6.0.5.2+ (with swapped partitions).
Updated Play Store to latest version (v4.8.20).
Continued using JB (cm10.1) Google Framework and Login Services as latest KK (cm11) Google Framework and Login Services exceed the free size of system partition even if slimmed to it's end.
v1.1
Fixed: Now it can be flashed using cwm 6.0.4.6 by psyke83
v1.0
Can be installed using CWM 6.0.1.2 (Trying to make it capable of flash via CWM 6.0.4.5+)
Play store, Google account and everything working.
Removed big apps like talk, youtube, etc.
Updated Play Store to latest version.
NOTE: These gapps are the minimalistic gapps possible.
SD-EXT version
This version will be installed on your sd-ext partition. (So these packages won t occupy space in system partition. This will help devices with tiny system partition.)
Link to the latest package:-
gapps-kk442-20140225-sdext-v2.0.zip (20.5 MB only)
Patch for Mountscript :-
gapps-kk442-sdext-patch.zip (128 KB only)
This patch creates a mount script for your sd-ext partition. And if your using any app2sd apps like link2sd then also please INSTALL this patch. It won't conflict with link2sd (or other app2sd apps), Don't worry.
Patch for Dalvik-cache Duplication:-
dalvik-cache-patch.zip(128 KB only)
This patch is optional and will save you 5 MBs in data partition because it removes (symlinks infact) duplicated dalvik-cache files.
Requirements:-
Need a cm11 build from Jenkins' project: cm-ota which is built after 22/06/2014.
An sd-ext partition of any size having atleast 31 MB free space for v2.0 and 11 MB free space for v1.0.
Any working recovery (Recommended: CWM recovery 6.0.5.2+ by psyke83/Jenkins-cm-recovery).
How to install?
Download gapps package, mountscript patch and dalvik-cache patch from above link.
Install mountscript patch & dalvik-cache patch.
Then install gapps package. (Install simply without any wipes). IF you are using my v1.0 sdext gapps, for upgrading to v2.0 do a full data wipe and again flash cm11.
Reboot to system and you're done!
Changelog:-
v2.0
Made from fresh official cm-11.0 gapps.
Added GmsCore.apk because without it, new cm11 gapps don't allow you to add a Google Account.
GoogleContactSyncAdapter and GoogleCalendarSyncAdapter are now moved to /system/app because they must be there (not needed to put in priv-app).
Added few necessary permission files (to /system/etc/permissions) to run Google Maps and few other things.
Added framework jars for maps, drm and media-effects.
Added system/addon.d/70-gapps.sh
Added GoogleOneTimeInitializer.apk (not OneTimeInitializer.apk)
Added ConfigUpdater.apk
v1.0 (only 6.5 MB)
Can be flashed on sd-ext partition.
NOTE: These gapps (all versions) are incompatible with ART.
Credits:-
psyke83 : for his cm10.1 gapps package and for help with mountscript and dalvik-cache patch's script.
Feby : for help of mountscript.
Me : for maintaining these gapps packages.
Problem while installing these gapps
Hi,
I'm having a big problem about getting these gapps to work. Indeed, even if they are installed perfecly through the recovery (CWM/ PhilZ Touch), when my callisto reboots there no google apps (e.g Play Sore) installed. I tried to add my google account through the settings but didn't helped, still nothing. I'm using CM11 made by psyke83 : http://forum.xda-developers.com/showthread.php?t=2453085
Any idea to get play store working ?
mehdoux said:
Hi,
I'm having a big problem about getting these gapps to work. Indeed, even if they are installed perfecly through the recovery (CWM/ PhilZ Touch), when my callisto reboots there no google apps (e.g Play Sore) installed. I tried to add my google account through the settings but didn't helped, still nothing. I'm using CM11 made by psyke83 : http://forum.xda-developers.com/showthread.php?t=2453085
Any idea to get play store working ?
Click to expand...
Click to collapse
Please read instructions. Free up enough space in system partition first. And if you're using sd-ext gapps, make sure it has free space and even it exist and you flashed mountscript patch.
READ INSTRUCTION CAREFULLY AND GET THE JOB DONE.
Bhargav97 said:
Please read instructions. Free up enough space in system partition first. And if you're using sd-ext gapps, make sure it has free space and even it exist and you flashed mountscript patch.
READ INSTRUCTION CAREFULLY AND GET THE JOB DONE.
Click to expand...
Click to collapse
Hi,
THIS IS EXACTLY WHAT I DID. I deleted all the files you mentionned (some files won't get deleted though).The recovery wasn't giving any error. Anyway, I deleted some others system apps (which I will replace with some third-party apps, it was the only solution because i didn't want to use sd-ext gapps) and finally get the play store installed. Thank you for your help and keep up the good work.
one question: what this gapps-kk442-sdext-patch script is better link2sd?
iSanechek said:
one question: what this gapps-kk442-sdext-patch script is better link2sd?
Click to expand...
Click to collapse
If you have that then you can't use link2sd because the gapps will be installed on the sd-ext partition. So, if you install link2sd it will override the gapps.
Sent from my GT-I5500 using Tapatalk
Vagelis1608 said:
If you have that then you can't use link2sd because the gapps will be installed on the sd-ext partition. So, if you install link2sd it will override the gapps.
Sent from my GT-I5500 using Tapatalk
Click to expand...
Click to collapse
Don't give wrong advice please. He can use Link2SD without any problems even if he's using that patch and gapps, already written on first post. gapps will just occupy a little space on sd-ext partition and that's it.
iSanechek said:
one question: what this gapps-kk442-sdext-patch script is better link2sd?
Click to expand...
Click to collapse
I'm not sure what you are asking. I've already written on first post that installing this patch and gapps won't create any problems with Link2SD. And, if you have link2sd then also you must install that patch because of a different (non-standard) mount-point creation by Link2SD.
Bhargav97 said:
I'm not sure what you are asking. I've already written on first post that installing this patch and gapps won't create any problems with Link2SD. And, if you have link2sd then also you must install that patch because of a different (non-standard) mount-point creation by Link2SD.
Click to expand...
Click to collapse
I asked what the plus of this script? if I use link2sd. thanks for reply and help. I understood everything.
Help Google now not working!!
HI
Thanks for providing the SD ext version of gapps but i have a major problem as Google now doesn't work. The app will be installed and start normally but when i tap the mic to start speaking it say "Unfortunately Google Search has stopped working" .
Thanks in advanced (a lot).
DETAILS:
Galaxy 5 running on cm11 20140531 NIGHTLY
SDEXT:- 512 mb
Swap:- 64mb
processor oc to 768Mhz
SDEXT gapps (provided by you):laugh:
abhijeet98 said:
HI
Thanks for providing the SD ext version of gapps but i have a major problem as Google now doesn't work. The app will be installed and start normally but when i tap the mic to start speaking it say "Unfortunately Google Search has stopped working" .
Thanks in advanced (a lot).
DETAILS:
Galaxy 5 running on cm11 20140531 NIGHTLY
SDEXT:- 512 mb
Swap:- 64mb
processor oc to 768Mhz
SDEXT gapps (provided by you):laugh:
Click to expand...
Click to collapse
The Google Now's Voice Search is not compatible with armv6 devices (like: galaxy5). Because the libs needed for them are compiled for armv7. So it's not fault of my gapps, it's where the limitation of your device arrives.
However, there's a workaround for that (it's not too pretty but it works):
http://forum.xda-developers.com/showthread.php?t=2709285
Not related to gapps but only one Question!
I wanted to ask that whether I can install cm11 Nightlies to SDEXT like "psyke" sir developed the rom for my device(GT15503) that can be installed
in the SDEXT ? As the further development has stopped of that Rom so i thought it would be great if Jenkins build could be installed on SDEXT :laugh:.If possible please give me a solution.
Thnx man this works perfectly with The CM11 for Galaxy 551 and had no problem with it whatsoever. I have to applaud you
and say good work on this.
thanks :good:
MADjohny24 said:
thanks :good:
Click to expand...
Click to collapse
Seems like you are new to XDA.
If somebody helped you, don't make a post to say "Thanks". Just click on the "Thanks" button found on the left of every post. It's the only purpose of the Thanks button which helps to keep the thread clean of common posts which are just made to say: 'Thank you', 'It helped a lot, Thanks' and such others.
Thanks mate. I managed to install it on CM11 for Galaxy Mini/Pop Plus/Next Turbo GT-S5570I (I know. Different names for different countries). The version 1.1, though. I think you updated the post just the day after I downloaded it.
Just for reference other Gapps were crashing the AOSP keyboard. With this it works just fine!
EDIT: Just installed v2.2. No issues either. The catlog is clean and AOSP works!
Mounscript link doesn't work...
aamm95 said:
Mounscript link doesn't work...
Click to expand...
Click to collapse
Checked here. Link is all fine.
I'm sorry, i was going out to the internet thru a sonicwall firewall...I've download the script.
zlock2sonyexperia
hello
bhargav97
i like your hard work for our small but good enough smarphone galaxy 5. today i was reading an article in they ported sony experia lock to their phone and that is pretty good so my question is that can we put this lock on our set bcoz i have tried and failed to put this lock on my g 5.so can you tell us whether we can use it or not, if yes than it will be great g 5 user.
thanks in advance
rztg1618:
@Bhargav97,
Can you do me a favour?
1. Your information in post #1 re: the mountscript is inaccurate - it breaks simple2ext_mod. If someone has S2E installed, they don't need this patch, as /sd-ext will be mounted by simple2ext's script.
2. The dalvik cache patch won't work with with S2E due to the order of script execution. There are two possible solutions:
a) Rename the script to "/system/etc/init.d/91linkduplicates". This will ensure that the script is executed after all userinit.d scripts (including S2E's mount script) have finished.
b) Move the script to /data/local/userinit.d.
Option B has the advantage of surviving full OTA updates... however, you will need to choose a different name for the script to make sure it is executed after /data/local/userinit.d/simple2ext. The first letter of the filename would need to start with the letters t-z (so that it's executed after simple2ext). Ideally simple2ext's script should start with a number, but since I forgot to make that change in my initial mod, it's a bit of a pain to change it now (as the app will create duplicate mount scripts)
It would probably have been a better idea to implement a userinit.d script to symlink *all* gapps files on /system (as well as the dalvik duplicates), instead of doing any symlinking in the updater-script. That would make the whole gapps sd-ext package compatible with full OTA updates (as the userinit script survives /system reformatting), and avoid the need to provide a separate dalvik cache patch. Let me know if you want me to write the script.
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
Hello everybody,
I created a tool - initially for the nexus 9 (flounder|flounder_lte) - that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
I enhanced that tool to make it work for nexus 6 (shamu) too.
Background
The Android CDD (Compatibility Definition Document) suggests that all devices SHOULD enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. FDE comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in the case of the nexus 6 (aka shamu) it's the CPU's task. Even though the nexus 6's CPU has 4 quite fast cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any measurements)
There is an ongoing discussion about this topic in cyanogenmod's gerrit for the nexus 9. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome.
Because performance is important to me and my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher)
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What do I need to make this work?
A supported device (Your nexus 6)
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
Thank you for this!
I can easily extend support for more devices. Do you guys know of some that have forceencrypt enabled?
Excellent work.
Hello everybody,
I just released version 6!
In this release, FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
Enjoy
Edit: Confirmed as working for latest Chroma build. (9/18)
Can anyone confirm this working for Chroma? Truly don't want to deal with starting from scratch ...
Hello everybody,
just to let you guys know - I just checked the new marshmallow factory image for shamu (MRA58K) => FED-Patcher should work for this new image too.
Enjoy!
This worked perfect for me just flashed then formatted data and boom I'm unencrypted again thank you op
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
gladiac said:
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
Click to expand...
Click to collapse
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
spunks3 said:
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
Click to expand...
Click to collapse
Yes that should work!
//EDIT: No it does not. It keeps looping after installing SuperSU with the following error:
Code:
avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p29" ino=104419 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
Probably some selinux problem :/. I might dive into this later this week. Sorry.
//EDIT #2: Now that I think about it... Doesn't the SuperSU flashable ZIP take care of the needed policy rules so the error that I posted above does not happen? IMHO it is SuperSU's task to take care of these things.
I might have to retest with the actual SuperSU installer. I had used TWRP's SuperSU installer. Maybe that one is broken somehow...
//EDIT #3: Nope! Supersu definitely does not work. I just tried with BETA-SuperSU-v2.50.zip. The SELinux policy-set that comes with the stock marshmallow factory images lacks the necessary rules to enable SuperSU to work.
However, adding these rules is something FED-Patcher was not designed to do. IMHO the SuperSU flashable ZIP should take care of this.
FYI: Nexus 6 is a QUAD core. Not just 2.
doitright said:
FYI: Nexus 6 is a QUAD core. Not just 2.
Click to expand...
Click to collapse
Thanks, I just fixed it. Shame on me.
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
finesse said:
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
Click to expand...
Click to collapse
Hi @finesse,
FED patcher must be run after installing a rom in order to disable the forced encryption flag. If the rom does not have forced encryption enabled (pretty common on non-stock and non-cm12.1 roms) you do not need to run FED patcher at all. Background: What FED-Patcher does is that it just takes the boot-partition of the currently installed rom and modifies it.
Wiping (in TWRP: "Wipe" - "Factory reset") is essential after backing up if the phone is currently encrypted. Sadly, you cannot simply just disable the encryption. Only formatting the partition (=wiping) will get rid of it.
I hope I could help .
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Will this work on anyother device having Marshmallow... Its a MY6753 device.
or any way to edit you patch and make it work on my device....
gladiac said:
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Click to expand...
Click to collapse
rawdealer said:
You didn't Format the Data It's quite a large button in twrp
Click to expand...
Click to collapse
Emilius said:
OMG, please don't tell anyone
Click to expand...
Click to collapse
rawdealer said:
FORMAT DATA, the extra large button
http://forum.xda-developers.com/and...v8-forceencrypt-disable-t3234422/post63810702
Click to expand...
Click to collapse
haibane said:
Rawdealer, I got it to work lol. Just seemed odd that you had to Format Data instead of doing a full wipe of everything. I'm guessing the Format Data just had to occur after CM was installed.
Click to expand...
Click to collapse
SamS1989 said:
it does not working on my n6 (7.1.1 stock)
what i do :
- flash 7.1.1 factory image
- turned off after the flash, reboot in fastboot
- boot twrp (without flash)
- flashed the V8 fed
- wipe data/cache (in twrp)
and after the reboot the phone stil decrypted
should i do the factory reset from settings or it's good from twrp ?
Click to expand...
Click to collapse
rewrite the instructions in both threads:
flash FED-Patcher.zip
use the Format Data button!!! neither Swipe to Factory Reset! nor Advanced Wipe!
v8 works well for nexus 6 stock 7.1.1, thanks to the op @gladiac and the discoverer @rawdealer, would better someone quote this in the other thread since New members (those with few posts) are not permitted to post to development-related forums
Bump
Thanks for this.
Does FED-Patcher still not work with Nougat?
I tried to use the detailed instructions here:
https://forum.xda-developers.com/nexus-6/general/how-to-disable-force-encryption-nexus-6-t3220273
I am not a pro at any of this, including TWRP.
I downloaded the Factory Image from Google (7.1.1 July for Shamu , Nexus 6)
https://dl.google.com/dl/android/aosp/shamu-n6f27h-factory-718e138f.zip?hl=vi
I unlocked and rooted my N6, flashed TWRP.
I followed all the instructions. When I got to step 8: Flash your ROM, it wouldn't work. I kept getting Zip verification errors in TWRP. I also tried to do it in NRT.
I was told that you can't install a Google factory image via TWRP. I guess the factory image would overwrite the recovery with stock. (my guess)
And when I used NRT, I got a hash mismatch when I tried to flash the factory image it as a ZIP.
NRT would only install the factory image via "Flash Stock and Unroot" which I guess defeats the purpose of this.
So I can go back to those instructions but am unclear which Android ROM to flash at step 8.
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.