*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.
Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?
KingKostas said:
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?
Click to expand...
Click to collapse
May I ask quickly what steps are involved in "reflashing"? Just to make sure I don't do some extra step or miss something.
As far as the stable version goes, I looked for the d2tmo file on get.cm under the Stable tab. I'm assuming that would be the most stable build?
(Perhaps a nightly might fix it??)
Question: Is there not a way I can just install/add this "4.2" camera? I've seen videos and read that people are using that just fine on CM10. Alternately if I boot into recovery would "fix permissions" be any help?
re: odin flash
Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
First thing you need to do is to install the stock Tmobile T999 rooted firmware.
Here are the exact step by step instructions with the download link for the firmware.
After you have followed these instructions your phone will be working properly and if
you like you will be able to flash any custom roms made for the Tmobile T999 phone
or restore any backups unless the the backup is corrupted in some way or another.
Here is the link to the Tmobile Stock & Rooted firmware you need:
http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware
(a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
Here is a step by step guide for you.
Download the firmware of your choosing (use the root66 version if you want root)
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the FW you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
Misterjunky said:
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
Click to expand...
Click to collapse
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!
re: camera issue
Malumen said:
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!
Click to expand...
Click to collapse
Just download any of the custom rom zip files based on the jellybean v4.1.1 stock rom.
All of those custom roms will have the files you are looking for.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
d2vzw
This also works on the sch-i535 as well. Thank you so much.
kingsugar said:
This also works on the sch-i535 as well. Thank you so much.
Click to expand...
Click to collapse
Yes, I tried all the other options for getting my camera back on track, but only going back to a full stock (rooted) ROM got my camera up and running again. FWIW, I was running an AOSP ROM for months without issue. What kicked my camera offline (the dreaded can't connect to camera) for some strange reason was when I updated to the most recent firmware VRBMF1. Now its straight back to AOSP for me! Thanks for creating this post! Very helpful!
My fix
I'm going around posting my fix to all the camera threads in hopes of helping people find a solution sooner. I created a thread over in d2vzw http://forum.xda-developers.com/showthread.php?t=2492304
fix camera error on i9300 with cm 9 (4.0.4)
Malumen said:
*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.
Click to expand...
Click to collapse
thanks a lot, i read your post, i take your advice to copy "SlimISP" to built in (cm system) folder, its work for me perfectly.
Thanks a lottttttttttttttttttttttt, have a nice day.
This guide explains how to install and update CyanogenMod 11 (CM11) and SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers (listed below) are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
How to install Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Download the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here (or here) and the minimal Google Apps package here (or here or here). (You want the file called "GApps_Minimal_4.4.4_signed.zip". Do NOT try to install the "Standard" Google Apps package, as there is not enough room on the Defy's system partition.)
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Note: SlimKat build 4 is very stable, but it does have a bug that causes the phone to reboot into recovery mode automatically if the phone encounters a telephony error, instead of rebooting normally. To fix this issue, download DefyParts.apk here and replace the old DefyParts.apk by following the instructions in this post.
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 (or newer).
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to step 3. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone (I recommend using either Framaroot or SuperOneClick), then install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small LED light at the top of your phone. If the recovery was installed properly, the LED will light up with a blue color for a few seconds during startup. Allow the phone to fully boot up, then reboot the phone again and watch for the blue light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Install CM11 or SlimKat, and the corresponding Google Apps package.
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light. Instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.)
Select Install, choose safewipe.zip, then swipe to confirm the flash.
In the same way, flash the rom of your choice (either SlimKat or CM11), followed by the Google Apps package.
Reboot the phone. The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Set the correct baseband, and adjust performance settings.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier. (Note: This step is not necessary if you already changed the default baseband in the zip file. See "Tips for customizing & improving performance," below.)
I also strongly recommend configuring the rom for better performance, by following the tips listed below. (See especially the tips about using Aero Kernel Control. This will help with many problems, for example the infamous call wakeup delay issue.)
Step 5: Thank our awesome developers, and donate to them if you can.
You can find donation links under any post by the developers. (Just look for the button that says "donate to me.") Here's the donation link for Quarx.
How to update SlimKat or CM11 to newer versions (or downgrade to older versions)
Step 1: Backup your current rom, apps, and settings.
I recommend using Online Nandroid Backup to create TWRP-compatible backups, for the reasons mentioned here (see bug #36). In the Online Nandroid Backup app, select Custom Backup > Backup Type > TWRP. Then select Backup Mode > Selective, and select the "system" and "data" partitions to backup. Make sure the Save Location is set to /sdcard, and also check the box to "Exclude Dalvik Cache." Then press the blue arrow (looks like a "play" button) at the top right corner of the screen to begin the backup.
Also back up your apps and settings with Titanium Backup.
Step 2: Download the updated rom.
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then place it on your phone's SD card along with the appropriate Google Apps package. [Note: if using CM updater, you don't have to download the rom ahead of time.]
Step 3: Install the updated rom using one of the following three methods:
Note: If switching from SlimKat to CM11 or vice versa, you must use the clean install method.
"Clean" install (recommended)
- Boot into TWRP by pressing the menu button when you see the bootstrap image (the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup), which should appear just after the Motorola logo disappears and before the boot animation begins.
- Select "Install" and flash safewipe.zip, then flash the updated rom, followed by Google Apps.
- After rebooting the phone, you'll have to restore your apps and settings using Titanium Backup. Don't restore settings for system apps unless necessary, as that may lead to problems.
"Dirty" flash (easier, but may cause problems)
- Boot into TWRP and select Wipe > Advanced Wipe, and select Dalvik Cache, Cache, and System (not Data), then swipe to wipe. (WARNING: Wiping the system partition also deletes the custom recovery, so you must either flash a rom or restore a backup before rebooting the phone. If the phone is rebooted before a new system is installed, it will be "soft bricked" and you'll have to flash a stock sbf with RSD Lite to recover it.) Then press the back button to return to the main menu and select Install. Flash the updated rom, followed by Google Apps. Now it is safe to reboot the phone.
- Since this method does not affect the /data partition, you won't have to restore all of your apps and settings, but you may still need to switch the baseband. If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
CM updater method (easiest, but may cause problems)
- If you're using CM11, you can update via the built-in CM updater located under Settings > About Phone > CyanogenMod Updates. (Obviously this won't work on SlimKat.)
- If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
Tips for customizing & improving performance
How to customize the rom before installation:
Install 7-zip on your PC.
Right-click on the CM11 or SlimKat zip file and select 7-zip > Open archive. (Don't extract it; just open it.) Now you can:
Remove unnecessary files to save space on the system partition. For example, you can navigate to system > media > audio, and delete any ringtones you don't use. You can also delete unused apps from system > app. See @x53's post here for a list of system apps that are safe to remove; see also here and here for more info. Here's a list of system apps that I removed before installing SlimKat: BasicDreams (live wallpaper), Browser (I use Next Browser instead), Calendar, Dashclock, Deskclock, Email (I just use Gmail app), Exchange2, Gallery2, Livewallpaperspicker, PhaseBeam (live wallpaper), PhotoTable, PicoTTS, Slimcenter, SlimFileManager, SlimIRC, SoundRecorder, VisualizationWallpapers.
Replace the default bootanimation in system > media. (Just drag and drop your custom bootanimation to replace the original.)
Replace the default bootstrap image in system > bootstrap > images.
Change the default baseband. To do this, navigate to system > etc > motorola > basebands, and find the zip file that corresponds to your region and carrier. Drag that file out to a folder on your PC, and extract (unzip) it. Then drag and drop those extracted baseband files into system > etc > motorola > bp_nvm_default, replacing the default baseband files in the rom.
Edit build properties. To do this, find the build.prop file in the system directory, and drag it out to a folder on your PC. Open the file in Notepad++, and edit the build properties as desired. (For example, you can change the LCD screen density by editing the line that says "ro.sf.lcd_density=". The default density in CM11 is 240, and the default in SlimKat is 213. Larger numbers make icons appear larger on your screen.) After making any desired changes, save the file and drag it back into the rom zip file where you found it, replacing the original.
After installation, configure the rom for better performance:
Install Aero Kernel Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. For starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
If you want to try using Interactive governor, I recommend the following settings: open Aero Kernel Control, go to CPU Performance, select Interactive governor, then tap the little phone icon at the top right corner of the screen to open the settings for the Interactive governor. Set suspend_enabled to 0. That should help to reduce the call wakeup delay. Changing hispeed_freq and input_boost_freq to your maximum value (e.g. 1200000 if you've overclocked to 1200 MHz) will also boost performance, though you may see a slight drop in battery life. Note: Interactive governor is not recommended for CM11 builds prior to the 06-10 nightly, because the suspend/resume handler was missing. (See okij's note on bug #26 for more info.)
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (Explanation: HWA requires more RAM, and the Defy is already short on RAM, so enabling HWA usually does more harm than good. That's why it's best to disable it whenever it's not really needed for an app to function properly.)
The following apps require HWA: Camera, Dialer (on CM11 only), Google Maps (version 7+), Chrome browser. Other apps may also require HWA. If an app doesn't display properly, try enabling HWA again to see if that solves the problem.
Install Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Other tips & suggestions:
You may wish to install Google Camera instead of the stock camera, for the reasons mentioned here.
For offline voice recognition, see here.
For better GPS performance, you may want to try flashing this zip and/or using this app. (Thanks to @Male_zvire and @okij for recommending these solutions.)
FAQ & what to do if something goes wrong
A freshly installed rom takes some time to "settle" while various services run in the background, so the phone may be a bit unstable at first. If you're still encountering errors or other problems after a few hours, first check the bug list and use the XDA forum search feature to see if the issue you are having has already been reported.
If you think you've found a new bug, don't just complain about it; try to help solve it by taking logs. @measel has provided a very helpful guide for taking logs.
What if the phone doesn't boot up properly?
If you can still access the custom recovery, just flash safewipe again and re-install the rom, or restore a backup. (To enter TeamWin recovery after installing SlimKat or CM11, press the menu button when you see the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup. That screen should appear just after the Motorola logo disappears, and before the boot animation begins.)
If you can't access the recovery, you may need to flash an sbf file using RSD Lite. Be careful! Flashing an sbf file improperly is one of the few things that can actually hard-brick the Defy, and if you flash the wrong sbf file for your phone, it may be impossible to restore your phone back to its original firmware. Read the All-in-One Defy Beginner's guide for more information about sbfs and RSD Lite. You can also check out the Motorola Defy wiki page for other tips and tutorials.
A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.
suggestion for improvement
Thanks for the guide. I'm pretty sure it is very useful for beginners!
I would suggest to try to get rid of as much text as possible and make it more step-by-step-y, you know what I mean? People (at least I recognized that on me) tend to give up quickly when it comes to reading. Right now it looks really difficult!
Just a suggestions. People will still appreciate your work as is. Thanks.
CM 7 and SBFS
Proverbs2 said:
The following is a guide that I wrote for one of my family members, and I decided to post it here so that others may benefit. I know there are numerous similar guides already in the forums, but they have not been updated recently. I intend to keep this guide updated for as long as I own a Defy (and I have no plans to get rid of my beloved phone anytime soon).
This guide explains how to install either CyanogenMod 11 (CM11) or SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Please note that neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable. A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
Installation instructions for Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Make sure you've downloaded the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here and the minimal Google Apps package (4-16_GApps_Minimal_4.4.2_signed.zip) here.
Put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 or newer.
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to the next step. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone and install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small led light at the top of your phone. If the LED lights up with a blue color for a few seconds during startup, the custom recovery was installed properly, but you still need to upgrade the recovery to TWRP 2.6.3.0. Reboot the phone again and watch for the blue LED light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Installing CM11 or SlimKat
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light, instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter the newly installed TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.) Then select Install, choose safewipe.zip, then swipe to confirm the flash. In the same way, flash the rom of your choice (either SlimKat or CM11).
If you installed SlimKat, you can now install the minimal_Slim_AIO_gapps file in the same way, then reboot the phone.
If you installed installed CM11, don't flash the Google Apps package yet, or it will conflict with the Cyanogenmod setup and cause an error. You must first reboot the phone and allow it to fully boot up. Then reboot the phone once more and go into TWRP recovery again. (Note: This time, you won't see the blue LED light; instead you'll see a screen indicating that you can press the menu button to enter the recovery.) Select Wipe > Advanced Wipe > and wipe the Dalvik Cache and the Cache. Then press the back button twice to return to the main menu and select Install, then install the GApps_Minimal_4.4.2 zip file, and reboot the phone.
Note: The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Configure the Rom.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier.
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (I disable HWA for everything except the camera. The latest version of Google Maps also requires HWA, but I’m using an older version that doesn’t.)
I recommend installing Aero Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. I'll post some suggested settings when I have time later; but for starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
I also recommend installing Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Step 5: Thank our awesome developers, and donate to them if you can.
Click to expand...
Click to collapse
Hey
very usefull guide, thank you for it.
Two suggestions
Can you add how to switch back to CM7 from CM11 for those that installed and did not liked it?
and SBFS this Guide is intented for those who already know alot of topics like TWRP
can you insert a referneces to guide explaining how to root?
Thanks @measel and @yosef_a for your suggestions. I'll try to implement these ideas as soon as I have time.
Nice Guide
Thanks @Proverbs2 for this great guide.
For the sake of completeness, I would suggest you to add a section in the post on How to safely update from one nightly to a another newer/older nightly.
Iloveyou and thanks for that guide I've made my first succeded rom install ever
MelaPL said:
Iloveyou and thanks for that guide I've made my first succeded rom install ever
Click to expand...
Click to collapse
Congratulations! :laugh:
Aero kernel on SlimKat
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx
Mislav12 said:
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx
Click to expand...
Click to collapse
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?
Proverbs2 said:
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?
Click to expand...
Click to collapse
Firs of all thaks for reply.
I'm got one device on SK 3.85 (20140323) and other on 4.0 (didn't try to use aero kernel because of problems with first one-stupid me), eveythig working great, (first time I instal it, SK take my breath, really can't searching for more with that old and hardware limited device like Defy is). Used Aero Kernel from Play store, these days was the latest (about month ago), take a chance 3-4 times during 10 days but allways with same result - start to using AK, about 5-10 hours having no issue and then darknes
Another thing that I notice (forgive me if i'm on wrong thread, can't make post on dev section), when my devices was on stock ROM after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?
Mislav12 said:
start to using AK, about 5-10 hours having no issue and then darknes
Click to expand...
Click to collapse
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?
Click to expand...
Click to collapse
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.
Proverbs2 said:
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Click to expand...
Click to collapse
You're wright, there is no left or right boot for Defy :silly:, i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.
Click to expand...
Click to collapse
Will try tomorrow and report.
Thanks a lott.
Mislav12 said:
i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Click to expand...
Click to collapse
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.
Proverbs2 said:
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.
Click to expand...
Click to collapse
To late for log taking, won't go back on stock rom. Beside, settings for Aero K. you recommend are super, no problem annymore. Got my voice on presidential elections!:good:
Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.
Snugglehog said:
Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.
Click to expand...
Click to collapse
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?
Proverbs2 said:
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?
Click to expand...
Click to collapse
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?
Snugglehog said:
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?
Click to expand...
Click to collapse
TWRP is unstable, and sometimes causes random reboots within the first 20 seconds. I'm guessing your phone rebooted while flashing safewipe.
Home buuton stopped working
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
Sounds like the device got 'unprovisioned', this sometimes happens and leads to at least some of the effects you listed: status bar problems, home button, settings. If you haven't nuked the thing yet you might try to manually set the provisioning bits:
Code:
#!/system/bin/sh
db=/data/data/com.android.providers.settings/databases/settings.db
prv_dev="INSERT INTO secure (name,value) VALUES ('device_provisioned','1'); INSERT INTO global (name,value) VALUES ('device_provisioned','1'); INSERT INTO secure (name,value) VALUES ('user_setup_complete','1');"
/system/xbin/sqlite3 "$db" "$prv_dev"
Click to expand...
Click to collapse
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)
ktwist said:
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)
Click to expand...
Click to collapse
I've never run into that problem, and I don't know if there's any easy way to fix it, but you could try just wiping data then restoring your apps and settings with Titanium Backup. Make a nandroid backup (so if wiping data doesn't help you can restore all your data easily), then wipe data, cache, and dalvik. If that doesn't work, you may have to do a clean install.
Feel free to add if you have any mod or hack on G1600. :angel:
Starting with Volume boost. If you are not satisfied with the speaker volume output on your "Samsung Galaxy Folder 2 SM-G1600", download the attached "Volume Boost" mod and install through twrp. Don't forgot to Wipe Dalvik Cache before rebooting back to system. Volume increase Guaranteed . Even you may want to decrease the volume a bit after applying this mod.
I am using ZCU1APK1 . Rooted and supersu installed. Following xposed version working fine with it.
https://www.androidfilehost.com/?fid=529152257862685344
Enable Google Assistant on Your SM-G1600
Open Settings --> Applications --> Application Manager, choose Google and clear Google app data. Then Install CCSWE App Manager ( Root ) from Playstore. Open the app and search for Google app, press on Google Assistant and press show icon. Now go back to the home screen and search for the Google Assistant and launch it finish the setup and it should work with long press home, you can also hide the icon after it works.
Does the volume boost only adresses to the speaker? Or to the headphones too?
lucky58 said:
Does the volume boost only adresses to the speaker? Or to the headphones too?
Click to expand...
Click to collapse
Headphone too. But, I would suggest to install V4A and DAP to get best output from headphone. And present volume settings I posted, is quite annoying !! I think it is too high. So, before trying it , take a backup of your existing mixer file.
I will be updating this thread with a complete stock based deodexed, zipaligned, bloatware free ( as much I can ) - and tweaked ROM to give better battery and speed. I think I can make the volume better in my ROM with new settings.
New ROM published as promised. Please check following thread
https://forum.xda-developers.com/ge...-optimized-eng-rom-samsung-folder-2-t36282551
I'm having issues with Google Assistant. Every time I enable it, it disappears again. I also can't get it to work with the long press of the home button (keeps going to Now on Tap).
What's going on? I tried resetting the Google App and Google Play Services (delete all data)
And I also made sure my language was set to English (US)
Exact same thing happening with me. So, now concentrated on ROM. 1st stock based ROM released with bloatware removed and mostly in english. You may try to flash OpenGapp Aroma based installer to enable Google assistant when flashing the ROM, though I already added ro.opa.eligible_device=true in build.prop, but still having issue to make it work with OpenGApp nano. Not yet tried the AROMA version which is having the function to enable Google Assistant on your ROM. Feel free to research a bit and share your output.
Another problem, this is regarding Google Now and the Pixel Launcher
Have you tried moving the Pixel launcher to /system/app or /system/priv-app ?
Every time I try to convert to a system app it disappears.
What am I doing wrong?
---------- Post added at 08:30 PM ---------- Previous post was at 07:31 PM ----------
I fixed the Pixel Launcher on my stock rom (rooted with magisk)
1. install as a regular app > adb install
2. Use a file explorer or adb to move the entire directory of the pixel launcher to /system/app
3. rename the folder to base (since the name of the apk is actually base.apk
4. Set permissions. You will need to change the APK permissions, folder permissions, and also the permissions for OAT and the folder inside of it.
5. Reboot
6. Go to applications, show system applications, and find the pixel launcher
7. Hit disable, it will prompt you to restore factory version.
8. Re-enable
9. Done! Select default apps, home screen, pixel launcher
10. Swipe left for google now
Still haven't figured out assistant. I await your response on that.
i added in /system/priv-app
Hello. I need verry urgently rom with goole services and all tweakes enabled. I have some problems with accesibility, talkback dosn't turned n, and shine plus screen reader started, but turned f, after few minutes on standby shine plus has stopped woking. Also, when i turned of phone, and tured on again, shine plus osn+'t start, and i must find sited person, for enabling screen reader... T's verry frustrate.
I created a stock based ROM for G1600. Please check my other thread. Though you need to install gapps after flashing it.
bidhata said:
I created a stock based ROM for G1600. Please check my other thread. Though you need to install gapps after flashing it.
Click to expand...
Click to collapse
hi sir,
i couldn' find the other trend with rom for G1600, was it deleted? wher to install gapps? thanks if you could help.
bidhata said:
I created a stock based ROM for G1600. Please check my other thread. Though you need to install gapps after flashing it.
Click to expand...
Click to collapse
Link gives 404, you took it down?
Reuploaded. Please check .
How to root samsung galaxy folder 2 sm-g1600 marsmello 6.0.1 thank you
i dont really know where else to ask this, so im asking it here:
how to i connect headphones to it? will any 3.5mm to microusb adapter off ebay/aliexpress/whatever work?
and can type in swedish with it? does t9 work or am i stuck with multitap? can i type åäö? (important characters in the swedish language)
thanks in advance!
I AM NOT A DEVELOPER, I in no way claim to have made any of this myself, I'm just here to say how I manage to get as close to having Pixel software on my Galaxy S7 G930V as possible.
Basically I'll divide this into three main areas. ROM, Add-on Mods, and Apps.
Read All the way through before starting so as to not miss anything.
Also the add-on mods are installed at the same time as the ROM. That way you keep safety net and what not.
Lets start with the ROM, I am using Ufirm_QE2_Hybrid_Nougat_Rom_FlashFire_Install Status Official For VZW S7FLAT by CVertigo1 / jrkruse
jrkruse said:
Latest Ufirm QE2 Nougat Firmware For The S7 Flat Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G930_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Go to Step 3 Below
Click to expand...
Click to collapse
To Flash Files in Odin simply launch Odin (Downloads later)
click on each button (Labeled BL, AP, etc.) and select their respective files that were extracted from the archive.
Each respective file's label has each corresponding label. (AP at the beginning of the file name, means put it in AP slot)
Then boot phone into download mode, press home, download, and volume down keys all simultaneously.
Connect it to computer and press the begin button in Odin.
jrkruse said:
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G930_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G930U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. I'm not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
Click to expand...
Click to collapse
Rooting is very simple for this phone once the Eng Kernel has been flashed.
Here is @jrkruse's Guide:
jrkruse said:
This Root Method For S7 Nougat
Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison]
Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix
Nougat_S7_Root_2_79_All.zip For Ufirm Includes Fingerprint Fix
Download Nougat Eng Boot.img Flash in odin
S7_SU_2_79_Root_Unroot_WO_Tweaks_V3.zip Old method
S7_VOLTE_ICON_FIX_ALL_VARIANTS.zip
HotSpot_Fix_VZW_QA2.zip
HotSpot_Fix_VZW_QA4.zip
HotSpot_Fix_VZW_QC5.zip
HotSpot_Fix_VZW_QC9.zip
HotSpot_Fix_VZW_QF2.zip
Directions:
1. Shut off the phone and boot into download mode (volume down, home, and power). Use Odin And Flash Nougat_S7_Edge_EngBoot.tar.md5 In AP Slot
2. When the phone reboots, plug in phone to computer unlock developer options and enable USB debugging and Disable Verify Apps Over USB.
3. Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.zip and run root.bat from your PC. If you Have Windows 10 from inside the Nougat_S7_Root_2_82_All_Carriers_V2 folder you may need press and hold shift and right click and click open command window here from the dialog box then in command prompt type name of the root bat you want to run and hit enter
4. This will install root when done phone will reboot
5. The process wipes dalvik cache so it will take a few minutes to reboot
6. If having problems getting Grant SuperSU dialog to come up you can delete the SuperSU app and root will be granted instantly to all root request
Give phone a few min to settle open developer options set animation scales .05 and others to .05
@JUSMEJOSE for Eng Boot.img
Original Thread
Click to expand...
Click to collapse
jrkruse said:
6. Unzip FlashFire_Flashable_G930UFirmware.zip
7. Copy AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 to your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip to your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma[/B]
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source
Click to expand...
Click to collapse
Options I selected in Aroma:
Verizon Stock
NoName System UI Mods
Open Source Ad Blocking
Pixel Boot Animation
Manual Debloat
Removed Every thing except Samsung TTS and Samsung Gallary / Camera (you can remove if you prefer to use google camera, DO NOT REMOVE if you plan on using zero camera.)
I don't use the google camera because on my S7 the video records the audio out of sync with the video, I haven't figured out how to fix it. but zero camera allows me to use Photos app instead of gallary so.... yea. (Requires a purchase of the root app for alt gallery)
That's about it for the ROM install.
**note these were installed in FlashFire with the ROM so as to pass safty net.
Now here are the add-on mods I used:
Open-GApps - to get pixel icons, and connectivity service
Android 8 Emojis
iYTB Vanced (Modded YouTube)
Google Lens
Zero Camera Mod
Copy those mods onto internal storage with the ROM install and add them into FlashFire during the ROM install. Place them after the ROM zip, but before the Format Cache / Wipe System less Super SU.
Files To Download ROM / Add-on Mods
ODIN:
Odin.zip
ADB Root Files:
ADB_Root_G930U_QE2Files.zip
ODIN Firmware:
UFIRM_G930_Odin_Firmware.zip
FlashFire Flashable AP:
FlashFire_Flashable_G930UFirmware.zip
ROM installer:
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip
ADB Setup:
adb-setup-1.4.3.exe
Open GApps:
http://opengapps.org/
iYTB / Android O emojis / Google Lens (Mirrored into one download for simplicity sake alt donwloads listed later):
Flashables.zip
Zero Camera Mod:
Thread Here
Next is apps
Pixel 2 Wallpapers -
Buttons remapper - get material button layout
Nova - get a better pixel launcher
ForceDoze - bettery battery life
SystemUI Tuner
Pixel 2 Wallpapers:
https://forum.xda-developers.com/android/apps-games/port-live-earth-wallpapers-t3481640
All are on google play except for Pixel 2 Wallpapers at the moment of me typing this.
You will need to grant Force Doze and SystemUI Tuner ADB permissions using a command prompt on windows.
Comands:
SystemUI Tuner:
adb shell pm grant com.zacharee1.systemuituner android.permission.WRITE_SECURE_SETTINGS
adb shell pm grant com.zacharee1.systemuituner android.permission.DUMP
ForceDoze:
adb -d shell pm grant com.suyashsrijan.forcedoze android.permission.WRITE_SECURE_SETTINGS
adb -d shell pm grant com.suyashsrijan.forcedoze android.permission.DUMP
And thats it!
Original Authors / Threads
@jrkruse / @CVertigo1 (AWESOME ROM)
Thread
@Master_T / @ZaneZam (iYTB)
Thread
@ZeevoX (Google Lens)
Thread
@Winb33 (Android O Emojis)
Thread
@zeroprobe (Zero Camera Mod)
Thread
@Pranav Pandey (Pixel Wallpapers)
Thread
ANY OTHER Developer who I did not list
THANKS A TON DEVS!!!! :good: :laugh: :good:
Let me know if anybody has anything else they have done to get this close!
I appreciate you putting all the links and mods into the same place. I have never flashed using FlashFire before (on a G930V) and this was an excellent guide for me.
My only trip up was I didn't understand the language about Camera/Google Camera/Zero Camera Mod and I tried installing the zero mod while debloating the camera off. So I will have to go back and do that.
I skipped the "flashables" youtube, emoji, lens but may end up going back for those.
Thanks again.
Update: I found a cool way to have the new Google now page in the launcher.
Launcher App:
First is the actual app. Typicaly I would just say use Nova but on the pixel launcher the Google Now page looks different than on other third party apps. I wanted this look, so here is how I found a way to get that new Google Now pag to appear on other launchers.
Step one, if you installed Google lens mod, you should be able to get the pixel launcher from the play store, if not get it from XDA labs or APK mirror. Set Google. Set it as your default launcher. Next you will need any third party launcher and Tasker. I'm using Lawn chair Launcher. (On Google play). Use button mapper pro to map pressing the home button to launch third party app. Go into Tasker and make a task, so that whenever Google pixel launcher is launched, open third party launcher. As long as the pixel launcher is set as your default, the new Google now page will appear in apps like Nova and action launcher.
I'm *loving* this so far. Thanks to you and the devs that have worked on each stage of this.
I'm doing:
Verizon Stock
No UI Mods
No Ad Blocking
Pixel Animation
"PlayStore" Edition (not BS free, not manual)
Flashing GApps
Flashing Emoji
My only issue is like you described with the camera. It was working initially and then it updated and the update is causing problems. Also, the double home button launch doesn't work without a 3rd party app (and with screen off with no root).
So I can either figure out a way to always ignore camera app update and use a 3rd party app for launch (screen on only)
or
Will the S8 camera option include the gallery app and not be cleared by the "PlayStore" option?
MCrly7 said:
I'm *loving* this so far. Thanks to you and the devs that have worked on each stage of this.
I'm doing:
Verizon Stock
No UI Mods
No Ad Blocking
Pixel Animation
"PlayStore" Edition (not BS free, not manual)
Flashing GApps
Flashing Emoji
My only issue is like you described with the camera. It was working initially and then it updated and the update is causing problems. Also, the double home button launch doesn't work without a 3rd party app (and with screen off with no root).
So I can either figure out a way to always ignore camera app update and use a 3rd party app for launch (screen on only)
or
Will the S8 camera option include the gallery app and not be cleared by the "PlayStore" option?
Click to expand...
Click to collapse
I believe so, however I don't know, this would be a better question to ask in the ROM's Thread. the link is in the OP
It says you flashed open gapps, does it just re write over existing gapps with no problems