PIMP MY ROM V2.0 FOR LG THRILL:fingers-crossed:
Hey guys I have just tried the ROM customizer PIMP MY ROM by Androguide.fr for all android devices,and I found that V2.0 of this CWM flashable Aroma Installer works fine on LG THRIL 4G.However extra apps like sony ericsson walkman suite and and DSP manager from this installer doesn't install,except this everything works cool.
First download V2.0 MDPI version for LG thrill 4G then do as follows:
Open the zip of the rom you are running with winrar or 7zip or whatever (the .zip file that you flash in recovery)
Inside this zip, navigate to : META-INF/com/google/android
Extract the file called "update-binary" and rename it to "update-binary-installer" then close your rom's zip
Open Pimp my Rom's zip (i.e : PIMP_MY_ROM-v1.5.3-by-Androguide.fr.zip)
Do not unzip it, inside this zip, navigate to : META-INF/com/google/android and delete "updater-binary-installer"
Now copy the "update-binary-installer" file you extracted & renamed from your rom to Pimp My Rom's zip (still in META-INF/com/google/android). Simply drag and drop it into PmR's zip to add it.
Close the zip and flash it
How to Flash PMR installer:
You can flash this on top of any custom rom with init.d support(like DNA_GB3.33)
- Download the version of Pimp My Rom that corresponds to your device's screen resolution (Not sure what res your device is ? Here "http://blog.blundell-apps.com/list-of-android-devices-with-pixel-density-buckets/" is a well-furnished list of android devices with their screen-res)LG THRILL'S SCREEN RESOLUTION IS MDPI.
- Make sure you are running a custom recovery (CWM or TWRP)
- Make a nandroid backup of your current ROM, just in case
- Wipe cache and dalvik cache in recovery
- Flash PmR in recovery
- A wonderful touchscreen interface will pop-up
(devices need different touchscreen calibration, if the touchscreen doesn't work, use the menu button of your device, select "Calibration Tools" and follow the instructions)
- Follow the on-screen instructions, make your choices between all the different features to Pimp your Rom
- Select "Reboot my device" on last screen (or reboot from recovery) and enjoy.
MDPI version for LG THRILL;
http://tinyw.in/5B8x
md5 : 2efcc11abcfbb606ff8a0ac513358a4d
Size : 74.21 mb
original thread:http://forum.xda-developers.com/showthread.php?t=1908269
IF THIS HELPED HIT THANKS!!!!
Has anyone tried this at all?
Welcome to... Atrix Boot Emporium!
Powered by AROMA Installer with custom ICS theme!
Test out different kernels for the same ROM or boot a second ROM hosted on SD card in a sleek, menu-driven environment. No need for fastboot or heavy installers.
Easy to flash via CWM, but... “I will let YOU DECIDE whether to wipe /data !” See Notes below.
Atrix-Boot-Emporium-V2.0-signed.zip: http://www.mediafire.com/?azassaimbbgmnxd
Checksum: ed9649db8b2990e3280d37b6a78104f7
Version 2.0 features:
Menus to select ROM location (EMMC or SD Card) and ROM family (GB, CM7 or CM10)
GB NottachTrix:
AT&T
Faux 1.00GHz
Faux 1.30GHz
Faux 1.45GHz
(D00 and 1100 were pulled to reduce zip size)
GB MROM:
HW Voltage
SW Voltage
CM7 MROM:
HW Voltage
SW Voltage
CM7 Neutrino:
EE
GT
GT+
CM10 (EMMC-only):
epinter Stock and OC1300
Th3Bill JB AOKP and JB MIUI
Dual-boot support! Boot supported ROMs hosted on SD card. Here I assume that your SD-based ROM resides at the following ext3[4] partitions:
/dev/block/mmcblk1p2 (/system)
/dev/block/mmcblk1p3 (/cache)
/dev/block/mmcblk1p4 (/data)
Instructions:
1. Download Atrix-Boot-Emporium-V2.0-signed.zip to SD card
2. Boot to CWM and "install/choose zip from sdcard".
3. Select Atrix-Boot-Emporium-V2.0-signed.zip
4. Install zip and follow instructions on the Welcome screen
5. Select ROM location: EMMC (internal memory) or SD (external memory)
6. Select ROM family: GB, CM7 or CM10 (CM9 and ICS not yet available)
7. Select kernel
8. Confirm and reboot (ignore “Status 0” error --- AROMA Installer bug)
Note 1: Atrix Boot Emporium is not a ROM store. I only stock boots (sorry). Also, I don't have version numbers for the kernels. But you can look inside the zip and view the timestamps of the boot images. You can also verify kernel version by going to Settings > About Phone.
Note 2: I did not include boot images for ROMs that are new or frequently updated. I'll wait until things settle down a bit
Note 3: This is a powerful tool, so remember which ROM you have installed on EMMC (or SD if applicable), and try not to cross ROM families, e.g. don't boot to CM10 with a CM7 kernel or you will soft-brick. You MAY need to wipe data and/or reintall GApps, even if booting to a member of the same ROM family. Please Nandroid backup or at least Titanium backup system + apps beforehand.
Note 4: If you have problems booting a ROM hosted on SD even after wiping /cache and /data, try repartitioning /system, /cache and /data using my Smart Part partitioning tool, found here: http://forum.xda-developers.com/showthread.php?t=1651356 . Then reinstall ROM and reboot. This always works for me except for CM10 ROMs. For some reason I can't get them to boot off SD. Maybe a security / permissions issue.
Standard disclaimers apply.
Enjoy!
Credits: NottachTrix, faux123, Notorious544d, mmontouri, Th3Bill, epinter, amarullz (AROMA Installer), Koush (CWM Recovery) and any others I didn't mention (sorry).
seems nice but how about listing the install steps?
dude u r awesome !
What exactly is this might I ask? I don't exactly know its function. I should be ashamed if it was something basic...
syngamer96 said:
What exactly is this might I ask? I don't exactly know its function. I should be ashamed if it was something basic...
Click to expand...
Click to collapse
^ this. I dont know either what exactly is this.. and the instructions aren't as clear as a noob like me would want
Is this a JB or ICS
Sent from my MB860 using xda premium
Not having downloaded or tried anything (yet), my initial guess is this is just a brand new way of dual-booting, no ROMs are included.
ranjithkumar1201 said:
Is this a JB or ICS
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
This is not a ROM , I guess its just some ways to flash kernels and such?
I'm confused.
Sent from that Atrix.
? Same as Cyanoboot ?
This is a Rom I think based on nochttatrix Rom. Gonna test it.
Sent from my MB860 using xda app-developers app
Not a ROM. No ROM is only 40 MB in size. And there's especially no evidence it has anything to do with Nottachtrix. Where did you get that?
Just downloaded it, seems it's an Aroma installer with a bunch of kernels to choose from, ramfix included.
Note to OP: there is no point in making the MD5 checksum a downloadable file or a spreadsheet or whatever it is. Just put the MD5 string directly in the OP.
ravilov said:
Not a ROM. No ROM is only 40 MB in size. And there's especially no evidence it has anything to do with Nottachtrix. Where did you get that?
Just downloaded it, seems it's an Aroma installer with a bunch of kernels to choose from, ramfix included.
Note to OP: there is no point in making the MD5 checksum a downloadable file or a spreadsheet or whatever it is. Just put the MD5 string directly in the OP.
Click to expand...
Click to collapse
Yeah its compatible with Nottachtirx ROM. This is a kernel installer i flashed it. U can choose between different kernels. About the themen i didnt get any to choose or what every.
ravilov said:
Not a ROM. No ROM is only 40 MB in size. And there's especially no evidence it has anything to do with Nottachtrix. Where did you get that?
Click to expand...
Click to collapse
First thing the OP says is : Initial release features the original NottachTrix 1.3.1-compatible kernels and ramfix
ravilov said:
Not a ROM. No ROM is only 40 MB in size. And there's especially no evidence it has anything to do with Nottachtrix. Where did you get that?
Just downloaded it, seems it's an Aroma installer with a bunch of kernels to choose from, ramfix included.
Note to OP: there is no point in making the MD5 checksum a downloadable file or a spreadsheet or whatever it is. Just put the MD5 string directly in the OP.
Click to expand...
Click to collapse
This is strictly a custom boot image loader that I developed on my own. And the Welcome screen explicitly says: "Initial release features NottachTrix-compatible boot images".
Atrix-Boot-Emporium assumes that at least one ROM is installed on your device and features the six boot images found in the NottachTrix1.3.1 ROM. Emporium also features each of these six images with modified ramdisks to redirect the /system, /cache and /data filesystem mounts to SD card for dual-boot --- assuming the three "ext" partitions exist on SD and are of adequate size.
So if you flash the zip and follow instructions, you should find the original six NottachTrix1.3.1-compatible boot images and a corresponding six identical images adapted for SD-based ROMs (for dual boot).
So if I flash Nottatrix-ext to my SD and have ICS or CM7/9/10 on my phone, this zip will automatically arrange everything (creating folders with boot-images from both Roms) that I can switch between both? I was only able to that on Blur-based Roms until now - never got it working properly on Cm7.
In this initial release, the user selects a single boot image and that image is flashed to the boot partition, nothing else.
I was thinking that a subsequent release could feature a master menu where the user can select among GB (NottachTrix), CM7[9, 10] and ICS. Then a menu of boot images is presented for each class of ROMs.
The main idea behind the initial release was to enable quick selection of different boot images (e.g. OC kernels) for a particular ROM, in this case NottachTrix.
And it's already bailed me out of some trouble while on the road (no fastboot), lol.
Thank you, that´s awesome! Now I finally get the full purpose of this Release. Definitly I good thing - plz develop it further, I can get everything working with DualBoot except the boot.img thingies... That really bumped me every time.
Thanks for the feedback. I will look at my work schedule and see what I can do for the next release.
Atrix Boot Emporium V2.0 Released!
Version 2.0 features...
Menus to select ROM location (EMMC or SD Card) and ROM family (GB, CM7 or CM10).
Includes boot images from...
GB NottachTrix
AT&T
Faux 1.00GHz
Faux 1.30GHz
Faux 1.45GHz
(D00 and 1100 were pulled to reduce zip size)
GB MROM
HW Voltage
SW Voltage
CM7 MROM
HW Voltage
SW Voltage
CM7 Neutrino
EE
GT
GT+
CM10 (EMMC-only)
epinter Stock and OC1300
Th3Bill JB AOKP and JB MIUI
Dual-boot support! Boot supported ROMs hosted on SD card. Here I assume that your SD-based ROM resides at the following ext3[4] partitions:
/dev/block/mmcblk1p2 (/system)
/dev/block/mmcblk1p3 (/cache)
/dev/block/mmcblk1p4 (/data)
See OP for details!
DISCLAIMER:
I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED
TO YOU OR YOUR PHONE AS A RESULT OF THE CONTENTS OF THIS THREAD.
Created for and tested on the GT-I9300 ONLY.
If you flash 80-100 times a month like me, then you know how annoying it is to
uninstall unwanted system apps all the time.
Presenting the AROMA Installer for CyanogenMod for GT-I9300 devices.
Designed to give you a head start in enjoying your ROM.
Many thanks to the CyanogenMod Team but a lot of their stock apps have limited features
making them redundant.
Features:
- Select which CM Apps you want to Install
- Select which GApps you want to install
- Choose to perform a Megawipe before install
Important Info!! Read before proceeding!:
- If you have never uninstalled system apps before, this is not for you!!!
- The installer simply allows you to customize what goes into your "/system/app" folder
(and "/system/priv-app/" for cm11)..
- Everything else will be installed in it's original fashion (i.e. everything else in "/system/").
- Be mindful of what you pick and choose as many combinations can lead to a non-functional ROM.
You and ONLY you are responsible for what you do or don't choose.
- I will only be making these installers for Stable/RC/Snapshot versions (provided there is any demand).
I simply cannot push out nightly versions as fast as the CM Team releases them.
- Tested extensively on my GT-I9300 running CWM 6.0.4.4.
In the event that I missed something, please report it.
- Suggestions/Bug reports are welcome. However keep in mind that my programming skills are
about as good as a wet turd.
Notable Bad Combinations besides the obvious ones:
CM 10.1.3:
- Installing GApps but not it's 'Setup Wizard' causes several ROM functions to disappear (Quick settings panel items, Power menu items, etc.).
CM 10.2.0:
- Installing GApps but not it's 'Setup Wizard' causes several ROM functions to disappear (Quick settings panel items, Power menu items, etc.).
- Not installing the CM Welcome screen causes GApps' Welcome screen to crash and loop on first boot
i.e. stuck at welcome screen.
CM 11:
- Installing GApps but not it's 'Setup Wizard' causes several ROM functions to disappear (Quick settings panel items, Power menu items, etc.).
Installation:
1. Flash like you would any other .zip file via CWM.
2. Keep in external sd card if you intend to use megawipe.
Batch file for manual update:
The only reason I don't do these more frequently is my horrible upload bandwidth.
So here's a batch file for windows users to manually update to the latest cm11 nightly fairly quickly.
It simply moves the new apk's to the appropriate folder and replaces the /system/ contents and the boot.img file.
IMPORTANT NOTE ABOUT THE BAT FILE:
If the cm team has added new apps or removed old ones, or made any changes to the updater-script, this will not
be reflected in this batch update. The installer will also not show the new version details in the ROM info.
BE AWARE OF THESE CHANGES AND USE AT YOUR OWN RISK.
Instructions for manual update:
1. Extract any of my cm 11 aroma installers to a temporary directory (say "temp-directory").
2. Download and extract the latest cm11 nightly to another directory "another-directory".
3. CUT (not copy) and paste all the apk's from "/system/app/" and "/system/priv-app/" to the root of "temp-directory".
4. CUT and paste "/system/" folder and "boot.img" file to the root of "temp-directory".
5. Place cm.batch.updater.bat in the root of temp-directory and run as admin.
6. If you see any .apk's remaining in the root folder, then abort as it means cm has added an
app to their package that needs to be manually added to the config files.
7. Zip and enjoy!
Changelog:
06.01.2013
- added cm 11 SNAPSHOT M2
- added option to install CM 11 Apps ONLY if you forgot something
27.12.2013
- added .bat file for manually updating.
21.12.2013
- added latest cm 11 NIGHTLY.
12.12.2013
- Fixed Installer waits to reboot on something finished rather than immediately when no items are selected in the customize installation screen
- Changed to delete Velvet.apk only if Google Search is being installed.
- Several minor tweaks and modifications.
11.12.2013
- First released
Downloads:
CyanogenMod 10.1.3 Stable + Gapps for Android 4.2.2 (12.Aug.2013)
(267.83 MB)
Mediafire Link
CyanogenMod 10.2.0 Stable + Gapps for Android 4.3.0 (13.Aug.2013)
(267.72 MB)
Mediafile Link
CyanogenMod 11 SNAPSHOT M2 (04.Jan.2014) + Gapps for Android 4.4.1 (08.Dec.2013)
(288.66 MB)
Mediafire Link
Manual Update batch file:
View attachment 2476504
Credits:
The CyanogenMod Team for their ROM
@zoot1 for his Megawipe script
@amarullz for the AROMA Installer
Looks good. I can't wait for CM11...
CM11 nightly link added. Enjoy!
Updated cm10.1.3 and 10.2.0 installers.
added latest cm11 NIGHTLY (20 Dec 2013)
added a batch file to help you guys update manually rather than wait for me to upload on my 56K modem
added cm 11 snapshot and option to choose cm 11 apps only if you forgot something first time around.
This is my first guide so if I left something out please tell me.
I do not take any credit for any of this work. I just read in a thread how another user did it. I tried it and it worked.
This isn't nessassarily the right way to do this but this is what I did, and all don't from my nexus 7.
I've only tried it on slimkat. I'm going to be testing more ROMs today.
Thanks to
Legolas93
Slimroms.net
ryanrudolf
Things you will need:
A file explorer (I use solid explorer)
Zip app to extract and compress ( included in solid explorer)
Modified TWRP recovery from this post.
1. Download the latest weekly build of Slimkat. http://slimroms.net and extract the zip file to a folder.
2. Next either download the last build from legolass of slimkat here and extract it to its own folder or download attached boot.IMG and updater-script. (Only 2 files that I found that needed to be updated.)
3. If you just decided to download the attached files, extract the archive and inside you will find 2 files. Copy boot.IMG into the root of latest slimkat that you already extracted, overwriting when prompted. Next copy updater-script to./META-INF/Com/Google/android. overwriting when prompted.
If you didn't download the files from the post and choose to do this manually. Just follow above directions and get the files from the latest slimkat f2fs. Same directories.
4. Now its time to zip up the archive so we can flash it. Zip the files so the root of the archive is the same as the one you extracted. Meta-inf, system, Boot.IMG and file_contexts.
5. Flash in twrp.
B]List of working roms.[/B]
Liquid Smooth
Slimkat
CyanogenMod (with method below)
Tested but not fully working.
Paranoid
Method for CM By ryanrudolf
CM Nightly with All-F2FS (Unofficial Method)
1. download latest CM nightly (here is link for CM Nightly already modified for ALL-F2FS http://d-h.st/9By )
2. download faux025 kernel.zip
3. open CM nightly zipfile, extract the boot.img
4. open faux025 zipfile, extract the zImage
5. unpack the boot.img in step3
6. replace the zImage in step5 with faux025 zImage (step4)
7. replace fstab.grouper with this one -
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system f2fs ro,noatime,nosuid,nodev,discard,nodiratime,inline_ xattr,errors=recover wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xat tr,errors=recover wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xat tr,errors=recover wait,nonremovable,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/tegra-ehci auto vfat defaults voldmanaged=usbdisk:auto
8. repack boot.img. place it back in the CM nightly zipfile
9. on the CM nightly zipfile, edit updater script and look for these 3 lines -
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
replace it with
run_program("/sbin/busybox", "mount", "/system");
and these lines too -
format("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
replace with -
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/APP");
run_program("/sbin/busybox", "mount", "/system");
10. save the updater script and put it back to the zipfile. CM nightly zipfile is complete and ready for flashing.
11. flash modded twrp with f2fs support. also download the formatpartitions.zip (credits to legolas http://forum.xda-developers.com/show....php?t=2678140)
12. boot to the modified twrp, flash the formatpartitions.zip. reboot back to recovery
13. flash the modified CM nightly zipfile
14. flash gapps.zip (i use slimroms minimal gapps)
15. Wipe > Format Data > yes
16. reboot
17. enjoy!
NOTE - everything is CM ramdisk, except for the fstab.grouper. If I use the original CM fstab.grouper and just edit to f2fs, it does not work.
Credits -
Legolas for the modified TWRP with F2FS
Faux for faux025 kernel with F2FS support
CM for the CM Nightlies
SlimRoms for the minimal gapps
[
Thanks again. I will give this a try very soon. Glad someone figured out what these devs are doing. I hope others will come in here and share even more information. :good:
EDIT: So, you managed to do all of this on your device? Wow nice work.
SkOrPn said:
Thanks again. I will give this a try very soon. Glad someone figured out what these devs are doing. I hope others will come in here and share even more information. :good:
EDIT: So, you managed to do all of this on your device? Wow nice work.
Click to expand...
Click to collapse
Ryanrudolf in the all f2fs slimkat thread said what files he changed. I just followed his direction.
And yes I did all this from my n7.
No problem I'm glad I could contribute.
Sent from my Nexus 7 using XDA Premium HD app
Any ROMs u want me to test? I'm about to try paranoid 4.2 beta 2 (latest)
For all the other ROMs I'm going to remove the slimroms text that scrolls in twrp when installing. I'll update the op with unbranded updater file so they can try it on other ROMs and not get confused lol.
Sent from my Nexus 7 using XDA Premium HD app
ronedogg said:
Any ROMs u want me to test? I'm about to try paranoid 4.2 beta 2 (latest)
For all the other ROMs I'm going to remove the slimroms text that scrolls in twrp when installing. I'll update the op with unbranded updater file so they can try it on other ROMs and not get confused lol.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah that would have been great, but the dev on my preferred ROM is already working himself to figure it out. I'm probably going to be testing his latest build here soon. I just want to know what you guys did so that next week, when I want to try another ROM I will have a larger menu to choose from
If you want to mess around and test several ROM's I suggest you try AOSPAL SaberDroid in your list. There will be a new build here soon, maybe today I think.
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build. (i just replaced some rows in the updater-script and replaced boot.img in the zip file)
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue.
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build.
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue (i replaced boot.img with the one you attached).
Click to expand...
Click to collapse
That is a known issue with CM, not this mod. I get that same FC when I use CM11. Its not there on Slim, or Omni or AOSPAL, using the same mod.
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build.
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue (i replaced boot.img with the one you attached).
Click to expand...
Click to collapse
Hmmm. I tried paranoid and got the same result but was keyboard throwing up error....
In the all f2fs slimkat thread another user said he tried cyanogen as well and got same error. Maybe this is just for slimkat, I thought we might have gotten lucky.
I'm going to try to compare the updater scripts for cm and pa with the slimkat script. See if there is something obvious we can change.
Actually I take that back, I never tried straight PA, just modified versions of it. I only get that message with CM11.
SkOrPn said:
Actually I take that back, I never tried straight PA, just modified versions of it. I only get that message with CM11.
Click to expand...
Click to collapse
looking at comparing files now.
in cm latest nightly there is a line of code refering to f2fs already.
symlink("../bin/fsck.f2fs", "/system/bin/dump.f2fs");
not sure what that is.
im gonna upload a updated version of the script for cm. Using notepad ++ and compare plugin, should have something shortly that i can test.
Just tried this with the latest liquid smooth build, works fine so far. no fc and running really smoothly
PatrickMac said:
Just tried this with the latest liquid smooth build, works fine so far. no fc and running really smoothly
Click to expand...
Click to collapse
sweet!. im going to update the OP with working roms.
Thanks for testing
Just a suggestion, I would rename the thread to
[Guide] Converting ANY ROM to All-F2FS Partitions - Working ROM list Included!
SkOrPn said:
Just a suggestion, I would rename the thread to
[Guide] Converting ANY ROM to All-F2FS Partitions - Working ROM list Included!
Click to expand...
Click to collapse
it wont let me rename the title
2 failed attempts at editing the updater script on paranoid.
onto 3rd attempt.......
after some testing I got paranoid to install. but when i install gapps package all kinds of errors get thrown up....
waaay over my head there. ill try again later tonight see what I can come up with. i might be close... I might be waaay off.
maybe someone will see this thread and give me some pointers.
ronedogg said:
after some testing I got paranoid to install. but when i install gapps package all kinds of errors get thrown up....
waaay over my head there. ill try again later tonight see what I can come up with. i might be close... I might be waaay off.
maybe someone will see this thread and give me some pointers.
Click to expand...
Click to collapse
Haha, that's how I felt the weekend before last when I spent 20 straight hours trying to figure this out.
I have seen a few people ask for this so i'm going to try and edit the SlimRoms SlimBean 4.3.1 version of there rom to see if i can get this working on 4.3.1 Jelly Bean Roms.
I have already edited the fstab file in the SlimBean 4.3.1 kernel/boot.img and have already edited the updater script now just doing a backup of important stuff and going to give it a try
CptKlink said:
I have seen a few people ask for this so i'm going to try and edit the SlimRoms SlimBean 4.3.1 version of there rom to see if i can get this working on 4.3.1 Jelly Bean Roms.
I have already edited the fstab file in the SlimBean 4.3.1 kernel/boot.img and have already edited the updater script now just doing a backup of important stuff and going to give it a try
Click to expand...
Click to collapse
Good luck. :good:
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build. (i just replaced some rows in the updater-script and replaced boot.img in the zip file)
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue.
Click to expand...
Click to collapse
same i got that error too on the latest nightly of CM.
will try more on weekend
Sent from my C6503 using Tapatalk