Database Develop

Does Titanium Backup have to be side loaded?

Was running FROYO 2.2. Rooted using z4root.1.3.0 following the video instructions at Mobile.Tech.Videos.com, a great site. In the video, he talks about side loading Titanium Backup. I installed it straight from the Market without side loading. Do I need to un-install it and re-install it by side loading?
thanks
retnuh

no. you will just want sideloading enabled on your phone

retnuh said:
Was running FROYO 2.2. Rooted using z4root.1.3.0 following the video instructions at Mobile.Tech.Videos.com, a great site. In the video, he talks about side loading Titanium Backup. I installed it straight from the Market without side loading. Do I need to un-install it and re-install it by side loading?
thanks
retnuh
Click to expand...
Click to collapse
Any app loaded outside of market is considered "side loaded".
Enabling side loading is done typically by setting the appropriate option in the database file. This could be done manually at command prompt or through any of the programs available.
For TB to install apps from backup, it needs side loading to be enabled.

"For TB to install apps from backup, it needs side loading to be enabled."
Does TB automatically enable "side loading" when you select to restore apps?

retnuh said:
"For TB to install apps from backup, it needs side loading to be enabled."
Does TB automatically enable "side loading" when you select to restore apps?
Click to expand...
Click to collapse
Nope. Its a process u need to do.
Steps to enable side loading using adb
What you’ll need:
* Android SDK
* BusyBox
o If you don’t have BusyBox, go search “BusyBox” on the Android Market
o Once installed, open up the BusyBox app and follow the full installation directions to enable it
* Samsung Captivate with root
* SQL Database Manager
o We suggest trying the SQLite plugin for Firefox, you can find it here.
Process:
1. Turn on USB debugging: Settings >> Applications >> Development
2. Plug in your Samsung Captivate
3. Open up Command Prompt on your computer (Windows: start, search, type “cmd”, right click cmd, Run as Administrator)
4. Type in: cd _____PATH TO ANDROID SDK FOLDER______\tools
Example:
cd C:\Users\USERNAME\Desktop\android-sdk-windows\tools
Press ENTER
5. Type in: adb shell
Press ENTER
6. Type in: su
Press ENTER
7. Type in: cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
Press ENTER
8. Type in: cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db.backup
Press ENTER
9. Type in: exit
Press ENTER
10. Type in: exit
Press ENTER
11. Type in: adb pull /sdcard/settings.db %userprofile%\desktop
Press ENTER
Leave Command Prompt open
12. Open SQLite Manager in Firefox by pressing Tools >> SQLite Manager
13. Click “Database”
14. Then click “Connect Database”
15. Navigate to “settings.db” on your Desktop
16. Expand the tables
17. Click “Secure” on the panel
18. Scroll down to ID 6, “install_non_market_apps”
19. Double click it and change “value” from 0 to 1.
20. Close SQLite Manager
21. Go back to the command prompt window, type in: adb push %userprofile%\desktop\settings.db /sdcard
Press ENTER
22. Type in: adb shell
Press ENTER
23. Type in: su
Press ENTER
24. Type in: cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings
Press ENTER
25. Type in: chmod 777 /dbdata/databases/com.android.providers.settings/settings.db
Press ENTER
26. Type in: reboot
Press ENTER
27. Disconnect your Captivate from your computer while your phone reboots.
Congratulations! You can now sideload non-market applications on your Samsung Captivate.

Excellent sideloading advice. Question, once you have sideloading enabled...do you lose this functionality if you flash a new ROM?

NISMOFO said:
Excellent sideloading advice. Question, once you have sideloading enabled...do you lose this functionality if you flash a new ROM?
Click to expand...
Click to collapse
Yes. Most i9000 based roms have this option enabled by default. If not, u would need do this anytime u flash a new rom.

diablo009 said:
Yes. Most i9000 based roms have this option enabled by default. If not, u would need do this anytime u flash a new rom.
Click to expand...
Click to collapse
Last question, can I used the AC Sideload Wonder Machine instead without messing with any code?

(25/3)Best and most stable rom ever[ext2][daily-use]

Simply it's the best rom combination to be the most stable rom i have ever used and now am using it daily with no problems :-
(you may find it difficult but i swear u will be very happy with the results just give it a try)
Download rom:-
http://www.multiupload.com/T589I4WUX9
__________________________________________
Installation ...
1- Create (ext2) partation on your card ...
like in this video....
http://www.neopeek.com/viewtopic.php?f=16&t=146
2- Copy contents from the rar file to SD card ...
3- Open folder npkinstall and run install.exe
4- After restart open haret.exe normaly ...
5- download better keyboard from attachements and put it in ur androidapps folder in sd card
__________________________________________
you must do this to make ur button work and to be able to restart it by one press
open terminal emulator then type the following :-(press enter when u write the letters in each line)
Code:
su
mkdir /data/opt
cp /sdcard/autostart.sh /data/opt
chmod 755 /data/opt/autostart.sh
Then install autostart.apk (found in the rom source folder)
When your buttons stop functioning, you have to run a script from GScript that reinstalls the modules so they work once more. Perform these steps:
Install GScript.apk
Open GScript Lite and press <menu> button, then <add script>
Press the <Load file> button.
The script you need is located autmatically and is called "XPEROID Gscript Button restarter script.sh"
Select it and then in the new screen press <Save>
You can now return to your homescreen and add a shortcut to the script so you can reset your buttons easily. To do this do the following:
Press <menu> and then <add> to add widgets.
Select <shortcut> from the list and then locate and select <GScript Lite>
Then select the "XPEROID Gscript Button restarter script" and you now have a shortcut on your homescreen to reset your buttons.
_________________________________________________
thanks to "needo" for pure froyo rom main topic address
http://forum.xda-developers.com/showthread.php?t=941059
thanks to Duckly for the "keyboard as a module kernel" main topic address
http://forum.xda-developers.com/showthread.php?t=978309
thanks to tiad8 for the 3d files main topic address
http://forum.xda-developers.com/showthread.php?t=852937
note guys it's just a collective topic to make it easy for the noobs and am one of them don't be angry coz i got ur work and edited it a lil bit,,,
__________________________________________________
u can find the apps needed for keyboard restarting in androidapps folder
__________________________________________________
this allows u to get :-
Battery Life ( woooooooow so nice)
Bluetooth ( u can accept items efficiently i havent tried to send)
Wifi (nice but not so fast)
Baclight Control
Landscape Support
Phone ( WHEN u accept a call and u find no sound from the ear speaker just press the speaker button two times after u answer ur call)
Browser ( nice )
3D (playing angry birds lite so smoooooooooth)
working 3.5mm jack
SMS
_________________________________________________

Keyboard not working
Hi
I formated the SD-Card, went trough the installation as described, but when it comes to add my Googleaccount I have no way to enter any data since there seams no Softkeyboard installed and also the Hardwarekeyboard does not work.
Any information, how I can proceed?
Regards
agadir9866

unfortunately the buttons dont work after installing

semiran said:
unfortunately the buttons dont work after installing
Click to expand...
Click to collapse
read first post!!!

It seems like you forgot to say that some keyboard application should be downloaded and placed on SD card before taping a script code that you have posted in Emulator, because at the time of first run there is no possibility to tape anything at all (HW keyboard doesn't work without running the script, but the script itself cannot be run without it) Anyway it is useless because there is no way to run Edit command within Gscript, because... HW keys don't work!
Please, correct your first post keeping in mind that HW keys don't work without some doing.
Anyway, it could be a really good thing, it runs so smooth!

so i should copy
Better KB.apk
Ginger KB.apk
Smart KB.apk
SwiftKey KB.apk
to the root of the sd card first before i run haret is that correct?

Here is the guide wich allows you to wake keyboard with 1 click instead of rebooting the device. Guide is for freshly installed android (so no just updating the kernel).
1. Move autostart.sh from the included Folder and place it to your SD card
2. Install android like normal.
Until step 8, keys won't work, except for camera and power button. If you screw up, press camera button to return to the home screen.
3. Launch "Terminal Emulator". Soft keyboard should pop up.
4. Type "su" (everything without quotes from now on). Press enter. Symbol on the left should change to #.
5. Type "mkdir /data/opt" and press Enter.
6. Type "mv /sdcard/autostart.sh /data/opt" and press Enter.
7. Type "chmod 777 /data/opt/autostart.sh" and press Enter.
8. Type "sh /data/opt/autostart.sh" and press Enter. Software keyboard should disappear now and keys should be working.
9.Install application "autostart.apk"
From here, your android is working. If you wish to add 1-click keypad fix, then continue reading ...
10. Install application "GScript Lite".
11. Open GScript Lite.
12. Press left softkey (menu) and select "Add Script".
13. Load (XPEROID Gscript Button restarter script.sh)
14. Press save.
15. Return to the homescreen
16. Hold your thumb to get "Add to home screen" menu.
17. Select Shortcuts --> GScript Lite --> Script that you just created.
And now, each time your keyboard or front keys stops working, simply press camera key and tap on that icon you've just created
P.S.: this is not my work, i have just adapted what users seandean and yaana created. All credits go to them.

ON screen soft keyboard not present?
I can notate that screen keyboard is not present/installed?
And for the keyboard you can connect the phone through adb shell navigate to /sdcard/ and do the next:
chmod 775 autostart.sh
sh autostart.sh
Then you can do the configuration above ;-)

Hi , everything sounds good.
I am going to install / try directly when i am free of work
Most steps are normal steps when installing Android on X1.
However i do not understand what is meant by:
"open terminal emulator then type the following". Could someone explain how to do this (open terminal emulator)?
Is this done when having booted in Android? And if yes, how can i do this
Many MANY thanks in advance.
Willp ost results when i have had the time to test tonight
EDIT: ok tried it....looks VERY smooth, however i cna not get terminal emulator to do naything..
The peeps above are right... no soft Keyboard is present.
Any easy solution to this? (asume i have to install a soft kb first i gues...think i will give that a try.

Well i got this version up and running .
I just installed a software tobo myself and then i went through all the steps required.
Have not yet had much time to check the possibilities and speed.
but first impressions are good
(before this one i had the honeycomb V2 Android running. this one "feels" better.
Wifi: still unstable (on/off at random, like in every build i installed)
Speed: looks VERY good
Battery: hard to say, going to see how long he will be up today.
Charging: Still have to connect in winmo in order to be able to load
Software: Market etc. running very good.
Going to test upcoming time and report in

Hi
I formated the SD-Card, went trough the installation as described, but when it comes to add my Googleaccount I have no way to enter any data since there seams no Softkeyboard installed and also the Hardwarekeyboard does not work.
Any information, how I can proceed?
Regards
agadir9866
Click to expand...
Click to collapse
well sth have gone wrong i thought there is a software keyboard in the rom
ok u can find the app in the 1st post attachement
u have to download the SW keyboard and put it in androidapps folder in ur sd card
for the hardware butons u have to do all the steps accurately
u didn't do this steps
you must do this to make ur button work and to be able to restart it by one press
open terminal emulator then type the following :-(press enter when u write the letters in each line)
Code:
su
mkdir /data/opt
cp /sdcard/autostart.sh /data/opt
chmod 755 /data/opt/autostart.sh
Then install autostart.apk (found in the rom source folder)
When your buttons stop functioning, you have to run a script from GScript that reinstalls the modules so they work once more. Perform these steps:
Install GScript.apk
Open GScript Lite and press <menu> button, then <add script>
Press the <Load file> button.
The script you need is located autmatically and is called "XPEROID Gscript Button restarter script.sh"
Select it and then in the new screen press <Save>
You can now return to your homescreen and add a shortcut to the script so you can reset your buttons easily. To do this do the following:
Press <menu> and then <add> to add widgets.
Select <shortcut> from the list and then locate and select <GScript Lite>
Then select the "XPEROID Gscript Button restarter script" and you now have a shortcut on your homescreen to reset your buttons.
Click to expand...
Click to collapse
____________________

It seems like you forgot to say that some keyboard application should be downloaded and placed on SD card before taping a script code that you have posted in Emulator, because at the time of first run there is no possibility to tape anything at all (HW keyboard doesn't work without running the script, but the script itself cannot be run without it) Anyway it is useless because there is no way to run Edit command within Gscript, because... HW keys don't work!
Please, correct your first post keeping in mind that HW keys don't work without some doing.
Anyway, it could be a really good thing, it runs so smooth!
Click to expand...
Click to collapse
thx dude i edited it

Well i got this version up and running .
I just installed a software tobo myself and then i went through all the steps required.
Have not yet had much time to check the possibilities and speed.
but first impressions are good
(before this one i had the honeycomb V2 Android running. this one "feels" better.
Wifi: still unstable (on/off at random, like in every build i installed)
Speed: looks VERY good
Battery: hard to say, going to see how long he will be up today.
Charging: Still have to connect in winmo in order to be able to load
Software: Market etc. running very good.
Going to test upcoming time and report in
Click to expand...
Click to collapse
thx dude waiting ur feedback

so i should copy
Better KB.apk
Ginger KB.apk
Smart KB.apk
SwiftKey KB.apk
to the root of the sd card first before i run haret is that correct?
Click to expand...
Click to collapse
just copy the kb in attachements to ur androidapps folder in ur sd card

anyone else has trouble with automatic reboots and freezes of this stable rom... :S
had this installed and tried it today, but it rebooted over 10 times already!

Yes, launcherpro doesn't really works properly?
proces android.process.acore
Click to expand...
Click to collapse
and the phone reboots like every 5 min...

anyone else has trouble with automatic reboots and freezes of this stable rom... :S
had this installed and tried it today, but it rebooted over 10 times already!
Click to expand...
Click to collapse
Yes, launcherpro doesn't really works properly?
proces android.process.acore
and the phone reboots like every 5 min...
Click to expand...
Click to collapse
well guys i swear am using this build without any problems it's so smoooth
i haven't experienced this problem so plz make sure u obeyed the instructions and u made the ext2 partition

bob 4ever said:
well guys i swear am using this build without any problems it's so smoooth
i haven't experienced this problem so plz make sure u obeyed the instructions and u made the ext2 partition
Click to expand...
Click to collapse
I really followed the instructions as in the first post, I also made the ext2 partition, so I don't know

plz give it a 2nd try and tell me

Ok, installing again as we speak.. but thats only because it has dutch language support
(ok, ok, ánd because of full launcherpro version
ánd beautifull widgets (even while i dont use the widgets)
but it would be so much perfect if...
- keyboard would be installed on start (since no soft-keyboard is installed by default)
- kernel will be updated to last (Duckly's Kernel [3-9-2011]) (it also contains changelog = No Sleep Of Death)
- maby overclock to 650 Mhz (or is it already overclocked?
- betterterminal ssh would be fixed, or deleted, because both times i installed it didnt work..
(java.io.IOException: Unexpected http status code 404 Expected 200)
Jhonnie's own graphic request:
- auto-install startupcleaner would be banished,
it has a hideous icon in top! Juch! (and it can't uninstall it )
- bootanimation.zip will be changed to gingerbread's one
- why it got the fancy transitions between screens? fast, but may be to kinky.....
(can i disable the transitions in android install??)
Q's:
1.can some1 tell me how i do install drivers for ADB/debug usb?
2.does the android setup (first boot) always crash?
3.if you add autostart to AndroidApps, does it really autostart keyboard drivers,
or is this a one-time install android ever..?

[ROM][ICS][AOSP] Lenovo Ideapad K1

This is a 100% AOSP ICS build for the Lenovo Ideapad K1. It will wipe your entire system. You will lose all data except what is stored on the EXTERNAL sdcard.
Includes
Android ICS 4.0.4
ClockworkMod Recovery 6.0.1.0
Google Apps
Rooted version includes Superuser and busybox
Issues
Video Camera face effects
Rotation Lock Switch (Software switch works)
Downloads
As always flash at your own risk. I'm not responsible for your device.
Nvflash versions
K1_ICS_AOSP_Rooted_R2.zip
dfddf13bf51e357a4964a11a8adbfd53
Mirror
K1_ICS_AOSP_Stock_R2.zip
b359ec6a06289ccf8c6b83f07346be17
Mirror
CWM versions
CWM_K1_ICS_AOSP_Rooted_R2.zip
90341324a0927f3035e92dc81ffb9416
Mirror
CWM_K1_ICS_AOSP_Stock_R2.zip
c026beb4dc2a11defbc3c3bcbec041cc
Mirror
Instructions
Nvflash version
1. Download one of the packages above and extract it to a directory
2. Power off device
3. Press and hold both the Vol + and Vol - buttons
4. While holding both Volume buttons power the tablet on
5. The screen should go black and the two front LED's should remain lit. You are now in APX mode
6. Connect your device to USB
7a) Windows: Install the APX drivers from the 'drivers' folder
Double click the 'flash-windows.bat' file
7b) Linux: run 'chmod +x flash-linux.sh && sudo ./flash-linux.sh' from the extracted directory
CWM version
1. Download one of the CWM_K1_*.zip versions and move to external sdcard
2. Reboot into recovery
3. Install zip from sdcard
4. Choose zip from sdcard
5. Flash the update.
How to boot into recovery
Non-rooted version
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Rooted version
From a Terminal Application
Run the follow two commands
Code:
su
k1recovery
From adb
1. Make sure you have the Android SDK installed. http://developer.android.com/sdk/index.html
2. Make sure USB Debugging is enabled on the tablet. Go to Settings > Developers options > and check "USB Debugging"
3. Connect the device to USB
4. Open a terminal or command prompt window and type
Code:
adb shell k1recovery
Changelog
Code:
8/11/2012 R2
-Fixed external sdcard permissions
-Fixed keylayout
-Modifed build.prop to spoof Moto Xoom (App compatibility)
7/31/2012 R1
-Initial Release
Source Code
http://github.com/khanning

So from now on we will be able to flash future updates through recovery without wiping everything?

So from now on we will be able to flash future updates through recovery without wiping everything?
Click to expand...
Click to collapse
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...

khanning88 said:
Exactly, future updates will be CWM flashable .zip's.
All, I just noticed that Google Chrome isn't showing in the market, but Maps is. I swear it was showing up when I was testing previously. Will have to investigate...
Click to expand...
Click to collapse
I dont know if it's me or because of the ROM. WIth the rooted ROM before AOSP, I was able to install Chrome with a APK downloaded from mobilism but sometimes the pages are fine then just rendered white , for all tabs.
Does anybody use SKYPE ? When I do video chat, my broadcast picture stretched vertically when I broadcast-only (no picture feed from the other side), the picture my friend saw is fine though.
Many thanks for your hard work.

That is the main thing that i hate about Lenovo's Factory ICS image, i still cant install Chrome or Evernote, or many of my NEEDED apps. I hope that you get this working soon. or at least a temp fix.

Just flashed the rooted aosp, the boot animation is a nice touch. The app compatibility issue seems fully resolved outside of Chrome, pointed out already, which is no biggie for me atleast. I still can sideload Chrome and runs perfectly. Also, so far the dictionary miss-spell issue doesnt seem to be a problem anymore. Maybe its just me but touch responsiveness seems a little better/quicker with this build. Just tried using the command 'k1recovery' to boot into recovery and it keeps giving me an error relating to permissions, saying it cant create /dev/block/mmcblk0p5. Seems like I just need to change the permissions of the /block folder but wasnt sure if I was just not doing something right.
Massive improvements from Lenovo's vanilla ICS still, thanx khanning!

Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.

@Khanning88 Can you provide a mirror please? Goo.im is down and shows "Internal server error".
Never mind. It's up again.

me_is_rushin said:
Noticed some graphical glitches. Screen goes black if switching orientations on lockscreen and home screen.
Click to expand...
Click to collapse
Yup the screen flashes when switching orientations, for a split second...

That's great. thanks for share.

Flashed this one and works wonderful.
Rebooting to recovery didn't work 1st, but then mounted filesystem as rw and tried the command and could get to recovery.
Got an error "Can't mount backup path" when trying to make a backup. Is it because I didn't have an external sd card.
If yes, is there a way to take a nandroid backup to internal memory?
BTW, thanks again for providing this ROM.

Thanks khanning88 for giving this fabulous AOSP ROM
Does this ROM support the Wifi+3G version?

I found some issues installing apps, including some games, Zinio magazine reader, google earth, etc, all saying incompatible with my device.

I experienced alot of freezes while restoring my backup with titanium backup.
I keep testing if it also occurs in normal use.

Installed AOSP-Rooted. So far, Chrome (already noted as issue in OP), and POGO Games showing up as Incompatible.
Other than that, and possible other apps being incompatible, looks great and installed as easy as can be.
Thanks Khanning!
-Cybie

we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?

several more freezes. obviously not depending on any special app..

erickwan said:
Does this ROM support the Wifi+3G version?
Click to expand...
Click to collapse
I'm not sure if 3G works since I have a Wifi version, but if someone with a 3G version could meet me in freenode IRC room #ideapad-k1 I would be happy to work on it. If you aren't familiar with IRC just go to this link and join the chat.
http://webchat.freenode.net/?channels=ideapad-k1
we need an easy way to enter recovery. Rom Manager button doesn't work.
Reboot recovery from terminal emulator doesn't work either.
Could you implement the nice options when turning the unit off?
Click to expand...
Click to collapse
From a terminal app type:
Code:
su
k1recovery
Or from adb type:
Code:
adb shell k1recovery
Either method will reboot the device into recovery. I will work on adding the power menu options later.
several more freezes. obviously not depending on any special app..
Click to expand...
Click to collapse
I haven't experienced any "freezes" but when it happens to you could you please document what you were doing and take a logcat to help debug.
http://rootzwiki.com/topic/11930-learn-to-logcat-like-a-pro/

Here is a very simple way to reboot into khanning's CWM recovery.
1. Playstore --> Download/Install aShell app
2. Run App
3. Select Checkbox for "Root" (In Settings, you can set app to start Root as Default)
4. type "k1recovery" into textbox
5. press "start command" button.
Simple, no need to be in "true shell" mode. This app allows you to run shell commands without the terminal. Great for newbies, quicker for anyone.
Hope this helps!
-Cybie

Here is a quick fix for the hardware keys. Just flash the .zip file from recovery. Updated first post with more detailed booting into recovery instructions.
K1_keylayout_fix.zip

[ROM & Kernel] Aurora 1.0.0 Beta - Tutorial now included

Please note that this ROM is intended for the S5830i only! Flash at your own risk!
If you like Aurora just press the thanks button!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Contents
Quote 1: Introduction
Quote 2: Features and Credits
Quote 3: Download Link and Installation Instructions
Quote 4: Known Issues
Quote 5: Screenshots
Quote 6: Other Information
2nd Post: Android Shell Environment Information and Tutorial​
1. Introduction
I've been working on this for a couple of months now and this is a very stable ROM that I hope you will agree, has some great features (see below). It doesn't try to act like any particular later version of Android, I've just gone for what looks best in each individual case. I am experiencing almost no force closes whatsoever and no forced reboots at all. Hopefully others will confirm the same. I have declared this first version a beta as I haven't tested it on every firmware and one person can only test for and eliminate so many bugs. It should run fine on all firmwares. I would be grateful if you could report any bugs or issues in this thread.
Click to expand...
Click to collapse
2. Features and Credits
Core System Features
Prerooted with su binary and Supersu root access management tool
BusyBox v1.20.2-linusyang - Fully working - the latest and best version.
ROM deodexed by me
Rafael.Baugis kernel E3 rev. 201212101860
Android (Bash) Shell Environment (original thread) with many great features including:Bash shell v4.1.11(2)
Custom login screen
Multi-session command history
Tab auto-completion
Colour coded ls output
Nano text editor - fully working!
Dropbear secure shell (ssh) server
adbwifi script - surprisingly it allows you to connect to adb over wifi
reboot script - reboot, reboot recovery, soft/hot reboot, power off device
remount script - easily remount /system as re-writable / read-only​AdAway hosts file - blocks advertisements - install Adaway to remove/update
ROM based on XXLI1 - Was thinking of upgrading it to latest firmware but there has been issues with that particular firmware
Apps Features
Bloatware deleted
Chrome as default browser
Total Commander as default file manager
ICS Gallery as default gallery
No-Frills CPU Control
DroidWall firewall
Latest Play Store
Slightly modded Terminal Emulator included with Bash as default shell (Hacker's Keyboard recommended)
Zipaligned all apps for optimized performance
Still 62.3MB free on /system
Theming Features
Xperia S Launcher
SkyRaider boot animation
15 Toggles and 6 Lockscreens Mod
Lidroid Preferences
Almost all icons of all apps changed for custom hand-picked ones
1% Battery Mod
Light blue right-hand status bar icons - personally redesigned some of the icons
Light blue status bar clock
Themed status bar drop-down
Jellybean menu sound
Aurora-coloured overscroll
Aurora landscape wallpaper
Other minor theming stuff
Credits
Rafael Baugis for his excellent kernel
SenseiSimple for Android Shell Environment
Alucard1989pl for 15 Toggles and 6 Lockscreens
bijoy91 for camera settings small fonts fix
UOT kitchen for some of the theming
dsixda's Android Kitchen to deodex the ROM
Anybody else that I've accidently missed out!
Click to expand...
Click to collapse
3. Download Link and Installation Instructions
Download Link (Click Here)
1. Download Aurora's zip file.
2. Put Aurora's zip file in "/sdcard".
3. Reboot into recovery.
4. If you have stock recovery, select "apply update from sdcard" and use this zip file (put it in /sdcard) to open CWM recovery.
5. Once in CWM recovery, select "wipe data / reset" > "Yes"
6. Now select "install zip from sd" > "choose zip from sd card" > "aurora<version>.zip" > Yes
7. Wait for installation to finish, press the back button and select "reboot system now"
The phone will now reboot into Aurora. The first boot will take around two minutes, during which the screen will go blank for around one minute, so no need to panic! Subsequent boots will be much quicker.
Note: When you install this ROM, you will get e3 (stock) recovery. If you need the permanent version of CWM (because and only if you have an ext4 filesystem), then simply flash Rafael's CWM boot.img after flashing Aurora's zip file.
Click to expand...
Click to collapse
4. Known Issues
An icon of an app that is stored on the SD card that has been placed on the home screen / desktop occasionally dissapears after rebooting. This is a bug in the Xperia S launcher and there is not an awful lot I can do about this personally. There are a couple of workarounds however.
Workaround 1: The obvious, move the app to the phone's internal memory
Workaround 2: Place apps stored on the SD card in a folder on the home screen / desktop and they will not dissapear after reboots.
Click to expand...
Click to collapse
5. Screenshots
Click to expand...
Click to collapse
6. Other Information
You may use and/or redistribute my work but please give me credit. If redistributing this ROM, please link to this thread.
By the way this is my first ROM, thought I'd sneakily leave that until last
Click to expand...
Click to collapse

Android Shell Environment Information and Tutorial
Android Shell Environment Information and Tutorial
You may want to read through the original thread first.
Android Shell Environment Aurora Specific Information
​
The main difference between the original version of Android Shell Environment and the one included in Aurora is that all files are stored on the /system partition except for a couple of configuration files.
Take a look in /system/sbin for the useful utilities mentioned in the original thread
Scripts are in /system/bin (along with a lot of other Android system files).
Most of the configuration files are in /system/etc although a couple are in /data/local
In Aurora, unlike the original version, there is no option to make Bash the default shell. Firstly, this causes a bootloop on the S5830i and secondly it is pretty pointless anyway because Bash doesn't load its configuration files when set as the default shell which removes much of its functionality.
The binaries htop, scp, ssh and vim have been removed because they do not work. For all of these, there are working alternatives. For htop, use top instead, for scp use rsync, for vim use nano, for ssh use adbwifi. The text editor Joe does not work properly but has been included. Either use Nano instead or if you can get it working then please tell me how you did it!
Click to expand...
Click to collapse
Android Shell Environment Tutorial​
How To Use Bash​To start Bash:
ADB: From your PC command line, type 'adb shell' <enter>, then type 'bash' <enter>. Do not type 'adb shell bash' all in one go, this will cause problems.
Terminal Emulator: Bash loads automatically.​
Command History - Press the <UpArrow> and <DownArrow> keys to scroll through your command history. Use Hacker's Keyboard to do this in Terminal Emulator.
Auto Completion - Start typing the name of a file, folder or command, then press <Tab> to have Bash automatically complete the rest of the text. If nothing happens when you press <Tab>, then there may be multiple options, double press <Tab> to see the multiple options.
For auto-completion in Terminal Emulator, I have set a default preference so that when the phone's back key is pressed it send's out the keyboard <Tab> key. Note that this means that you cannot close Terminal Emulator using the back key, you have to enter the 'exit' command. You can change this preference in the app's settings.
To leave Bash: - Enter the command 'exit'
Click to expand...
Click to collapse
How To Use Nano Text Editor​
Nano is a user friendly command line editor. To start nano and create a new file simply type 'nano'. To start nano and open a specific file for editing type, e.g. 'nano /system/build.prop'.
If you are editing on the system partition then make sure you enter the command 'remount rw' before starting nano to mount /system as re-writable.
When you are finished editing, to exit nano enter the key combination <Ctrl>+<X>. If you have modified the file, nano will ask you if you wish to save it and request that you enter a file name.
That's basically all there is to it when it comes to the basics of this program.
Click to expand...
Click to collapse
How To Use the Reboot Command​I have rewritten the original reboot script to include a couple more parameters. Reboot now accepts the following options:
reboot - normal reboot
reboot recovery - obvious
reboot hot - hot/soft/quick reboot, restarts the Android runtime
reboot off - powers off the device, alternatively you can use the command 'halt' to acheive this
Click to expand...
Click to collapse
How To Use The Sudo Command​sudo is a well known Linux feature that runs a single command as root, useful if you generally want to work as a normal user for safety/security.
An example of this would be 'sudo adbwifi on'
Click to expand...
Click to collapse
How To Enable/Disable ADB Over WiFi​Do NOT do this from ADB shell, do this from Terminal Emulator.
Enter the command 'adbwifi on'
Follow the prompts on-screen, it tells you the rest.
To disable use 'adbwifi off'
Click to expand...
Click to collapse
How To Demote Yourself To Normal User In ADB Shell​Note: Do not do this from Bash because it doesn't work, either run it before you start bash or type 'exit', run the command, then start Bash again.
By default, ADB shell logs you in as root because Rafael's kernel has an ADB 'root mod'. This is generally very handy but sometimes, working as root is not ideal because it's very easy to brick your phone. Thankfully it is actually possible to be demoted to normal user status with the following command:
'su shell'
If you wish to return to root user, enter the command 'exit'
Click to expand...
Click to collapse
How To Use DropBear Secure Shell Server​
Dropbear allows you to login to your phone's shell (i.e. like adb shell / terminal emulator) from another device such as a PC or phone using, for example, WiFi.
To start Dropbear with the password 'pickledjelly' enter the command:
/system/sbin/dropbear -A -N root -U 0 -G 0 -C pickledjelly -r /system/etc/dropbear_rsa_host_key -b /system/etc/.dbbanner
To login from another Android device you can use e.g. Connect Bot,
use ssh protocol and in the text box enter [email protected]
Replace x and y with your phone's IP address from your WiFi router (you can get this with the command 'ifconfig')
To login from a PC running Linux enter the command:
ssh 192.168.x.y
To stop the Dropbear server issue the command 'killall Dropbear'
Click to expand...
Click to collapse

gud work man......i think this rom can have great future.....

make it final.

great job dude..:good:. now trying to combined with cronmod script by styrke...(only this way to solve our internal memory issue)
well done... all working with cronmod...

Glad some like it, cheers :good:

your rom sounds great! but is there really no way to get it based on xxlk3 (ins) ?

HeathenMan said:
your rom sounds great! but is there really no way to get it based on xxlk3 (ins) ?
Click to expand...
Click to collapse
Hi HeatherMan, I have held back on upgrading the ROM to XXLK3 so far because there were issues with IMEI numbers going awol when combining XXLK3 ROMs with custom kernels. I'll look at this again at some point though.
Aurora does work perfectly fine on XXLK3 firmware though, I currently have XXLK3 UK myself.

hi. why u don't use hell_lock kernel? thats might be better.i guess so.

SemBoyHehe said:
hi. why u don't use hell_lock kernel? thats might be better.i guess so.
Click to expand...
Click to collapse
hell_lock? wtf it is pre alpha and not stable with less features, what kind of better is THAT ?!?

HeathenMan said:
hell_lock? wtf it is pre alpha and not stable with less features, what kind of better is THAT ?!?
Click to expand...
Click to collapse
hey bro. u se ' I GUESS SO' u see that many people have trouble on that ketnel like dont have imei, earphone prob n etc. that why i guesd so

I chose Rafael's kernel because it has the most features and is currently quite stable. Hells Fusion does not presently have full IP tables needed for firewalls and has no governors or schedulers other than the standard ones.
When testing the XXLK3 IMEI issue I found that it occurred in Hells Fusion kernel as well as Rafael's. I also encountered the headphone problem at one point and found that it was because I'd flashed the boot.img but did not have the kernel modules installed.

How I installed Marshmallow to Nexus 4...

I did this 4 days ago and only published this now as I wanted to make sure it was stable and be as close to stock (aka pure Google experience). Only problem I have now is "Now on Tap" doesn't seem to work. Advise from those in the know if appreciated. Credits to those in their respective links I've included here.
-------
How I installed Android 6.0 (Marshmallow) on my Nexus 4...
I used Windows 7 as the base platform as all the tools needed are easily found on this platform.
WARNING: You will lose all data in phone, backup as necessary. I will not be responsible for this HOWTO, do so at your own risk. Yes, it worked for me. Your mileage may vary...
A. Prior to building/installing the Marshmallow build, you will need the following.
A.1. Install ADB and FASTBOOT tools.
These are the tools used to install Marshmallow on your phone. You can either install the full Android SDK or get them from this XDA thread at URL http://forum.xda-developers.com/showthread.php?t=2317790
A.2. Install WinRAR.
You will need to use a tool called WinRAR to extract or replace certain files in an archive. You can download a copy from URL http://www.win-rar.com/
A.3. Download a Mako Google factory image of Lollipop at URL https://developers.google.com/android/nexus/images?hl=en#occam
We are going to modify the factory image of a Lollipop build. To upgrade my Mako, I used the LMY48M build.
A.4. Download the WORKING IMAGE of Android M on Nexus 4
Get the image file from URL http://dmitry.gr/index.php?r=06.+Thoughts&proj=02.+Android+M+on+Nexus4
You will get an archive called "MakoM_bin_v2.zip" file. If there is a newer version, use that instead but I used this version when I installed on my Mako.
A.5. Download TWRP for Mako
Get the TeamWin Recovery Project (TWRP) v2.8.7.0 from URL https://dl.twrp.me/mako/twrp-2.8.7.0-mako.img
A.6. Download the Google Apps (not provided in the AOSP builds).
Get the file "gapps-mm-fix.zip" from URL https://www.androidfilehost.com/?fid=24052804347833783
A.7. Download a patched kernel image that allows you to install SuperSU root.
Get the file "Fixed_Data_root.img" from URL https://www.androidfilehost.com/?fid=24052804347833767
A.8. Download a fix for Location services (GPS) not working.
Get the file "framework-res.apk" from URL http://forum.xda-developers.com/showpost.php?p=63229334&postcount=434
A.9. Download the root manager utility.
Get the file "BETA-SuperSU-v2.52.zip" from URL http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
B. Checklist
B.1. If you have downloaded everything, you should have a list of the following:
- minimal_adb_fastboot_v1.3.1_setup.exe
- wrar521.exe
- occam-lmy48m-factory-03ae06e5.tgz
- MakoM_bin_v2.zip
- twrp-2.8.7.0-mako.img
- gapps-mm-fix.zip
- Fixed_Data_root.img
- framework-res.apk
- BETA-SuperSU-v2.52.zip
C. Installation and building the installer
C.1. Install the "minimal_adb_fastboot_v1.3.1_setup.exe" and "wrar521.exe" installers, leave settings as default.
C.2. Extract the content of file "occam-lmy48m-factory-03ae06e5.tgz" using WinRAR, it'll create a folder called "occam-lmy48m". Rename "occam-lmy48m" to "mako-marshmallow".
C.3. Extract the content of file "MakoM_bin_v2.zip" and you should get the following files:
- system.img
- Choose either "n4_lte_modem.img" or "normal_modem.img" depending if you want LTE support or just 3G (UMTS) support and rename that file to "radio-mako-m9615a-cefwmazm-2.0.1701.07.img"
C.4. Rename the file "twrp-2.8.7.0-mako.img" to "recovery.img", and "Fixed_Data_root.img" to "boot.img"
C.5. Replace the "radio-mako-m9615a-cefwmazm-2.0.1701.07.img" file inside the "mako-marshmallow" folder with our "radio-mako-m9615a-cefwmazm-2.0.1701.07.img" which we extracted from file "MakoM_bin_v2.zip"
C.6. Open the "image-occam-lmy48m.zip" file and replace the following files which we downloaded from the twrp.me or dimitry.gr site. They are:
- boot.img
- system.img
- recovery.img
C.7. Open a command shell:
Start -> Run -> cmd
From the command shell, go to the folder called "mako-marshmallow"
C.8. Make sure the Nexus 4 has at least 80% battery and restart the phone into bootloader mode (by switching off the phone, the pressing the on button and at the same time pressing the volume down button). To confirm you are in bootloader mode, type in the command:
fastboot devices
You should now see the output "xxxxxxxxxxxxxxxx fastboot" appear, where "xxxxxxxxxxxxxxxx" is the serial number that appears on your Nexus 4 screen. They should be the same and you should only have one line appearing, disconnect any other device if they appear on the list.
C.9. Install the image you just build by running the script "flash-all.bat". A Series of statuses will appear on the screen. Do not disconnect the phone from the cable and let the script install everything. If done correctly, you will find the Nexus 4 rebooting. WARNING: This will erase all user data on your Nexus 4!
C.10. Once you see the Home screen of Marshmallow on your Nexus 4, go to Settings -> About Phone and tap the BUILD number seven (7) times. When you go back to the Settings screen, just above the "About Phone" is a new menu item called "Developer Options".
C.11. Go to Settings -> Developer Options and enable "USB debugging". To ensure debugging is on, go to the command shell and type:
adb devices
It sure display the list of devices with the same serial number and should have the word "device" next to the serial number. You will be prompted on the phone if you want to allow this connection.
C.12. Make sure the USB is connected in MTP mode (Transfer files mode). In windows file maanger (Press the Win-E keys), you will see a device called "Nexus 4". Open it and in the "Internal storage", go to the "Download" folder and copy the following files:
- gapps-mm-fix.zip
- framework-res.apk
- BETA-SuperSU-v2.52.zip
Then, in a command shell, issues the command:
adb reboot bootloader
C.13. From the bootloader screen, press the volume down button until the option "Recovery" appears, then press the Power button once to boot into TWRP/Recovery.
C.14. In TWRP, select to install the file "gapps-mm-fix.zip" and "BETA-SuperSU-v2.52.zip" from the "Download" folder. Once completed, press the "Reboot" button that appears in TWRP.
C.15. When the phone restarts. Go to Settings -> Backup & reset and reset the whole phone. If you get a error message from the "Setup Wizard", press the Open-apps (ie. the square softkey on the screen) and you should see the "Settings" pane.
C.16. Once the phone restart from the master reset exercise. You will be prompted as if you just switched on a new phone. Fill in as necessary until you get to the Home screen.
C.17. We will need to replace a file to get Location Services (GPS) working. From you command shell:
adb root
adb remount
adb shell
cp /sdcard/Download/framework-res.apk /system/framework/
exit
adb reboot
C.18. I disabled the following apps (drag the app to the "App Info" button, and press the "Disable" button) for the following and replaced the with similar app from Google Play (name in brackets). This was done as the built in apps kept crashing every few minutes or didn't work as expected. The apps are:
- Browser (Chrome Browser)
- Clock (Clock)
- Camera (Google Camera)
- Calendar (Google Calendar)
- Contacts (Google Contacts)
- Music (Google Play Music)
- Gallery (Google Photos)
- Search (Google)
- EMail (GMail)
C.19. Restart phone and you're ready to experience a stable (close to Google stock) build of Marshmallow on your Mako (Nexus 4).
C.20. Fixing the "Google Now on Tap" not working problem (thanks to gamekid94).
Go to Settings -> Apps
- Tap on the "Gear" (icon on the top right) -> Default Apps -> Assist & voice input -> Assist app
- Select "None", then select "Google App".
Go to Settings -> Google -> Search & Now -> Voice
- Enable "Now on Tap"
C.21. Install and customize as you see fit.

While this can probably be useful to new users I don't think it belongs in the development subforum. A better place for it would probably be the general subforum.

OR... Or.. Or- You could just install a custom M ROM via flashing in TWRP. Much more easier lol.
Use Nexus Root Toolkit to backup everything, unlock bootloader, flash TWRP, and Root. Download Custom M ROM and Gapps, reboot to recovery, make a backup, wipe everything except internal storage, flash ROM. Done.
No need for extracting everything, ridiculous ADB commands, etc.

thanks, this is usefull to new users and detailed to avoid any doubt. will try

ajack2001my said:
I did this 4 days ago and only published this now as I wanted to make sure it was stable and be as close to stock (aka pure Google experience). Only problem I have now is "Now on Tap" doesn't seem to work.
Click to expand...
Click to collapse
Here's how i managed to get Now on Tap to work :
1. Go to settings .
2. Open "Apps" from the settings menu.
3. Tap on the "Gear" icon on the top right.
4. Select "Default Apps" and open "Assist and voice input".
5. Here, tap on Assist app, set it to None and then Back to google app.
Also, make sure that Now on Tap is switched on in the settings menu of the Google App.

It now works thanks...

Thank you so much for the nice post.
I got stuck up at C12. I do see the Nexus 4 in the as one of the devices connected. However when I click on it, I don't see any folders under it called as "internal storage", also when I try to copy these files (as in C12) I get an error "Cannot copy item - The device has stopped responding or has been disconnected". I am stuck here, any direction here is well appreciated.

mahavirvemuri said:
Thank you so much for the nice post.
I got stuck up at C12. I do see the Nexus 4 in the as one of the devices connected. However when I click on it, I don't see any folders under it called as "internal storage", also when I try to copy these files (as in C12) I get an error "Cannot copy item - The device has stopped responding or has been disconnected". I am stuck here, any direction here is well appreciated.
Click to expand...
Click to collapse
Connect using MTP mode...

ajack2001my said:
Connect using MTP mode...
Click to expand...
Click to collapse
Thanks a ton, that resolved it

Milion Thanks..!!
Thanks a lot..

Title should be "how i installed marshmallow the most difficult way possible"
Sent from my Nexus 4 using Tapatalk

I thought I'd post this in hope that people will appreciate how much effort needs to be put into it, yet simple enough to allow newbies to try building something. It's also a very light build without all the unnecessary apps which people end up uninstalling or disabling.
People here can always choose a ready build and ignore my post. I rather those with more experience help with problems in this build instead of condemning it.
If the senior members here feel this is unnecessary, I will delete this thread.

Yes, thank you for this tutorial, very much appreciated

question N4 with Marshmallow
Hi ajack2001my,
How is working N4 with the android M ? What is your experience about battery., stabilty .... afther two months ?
thanks
Pedro

ajack2001my said:
I did this 4 days ago and only published this now as I wanted to make sure it was stable and be as close to stock (aka pure Google experience). Only problem I have now is "Now on Tap" doesn't seem to work. Advise from those in the know if appreciated. Credits to those in their respective links I've included here.
-------
How I installed Android 6.0 (Marshmallow) on my Nexus 4...
I used Windows 7 as the base platform as all the tools needed are easily found on this platform.
WARNING: You will lose all data in phone, backup as necessary. I will not be responsible for this HOWTO, do so at your own risk. Yes, it worked for me. Your mileage may vary...
A. Prior to building/installing the Marshmallow build, you will need the following.
A.1. Install ADB and FASTBOOT tools.
These are the tools used to install Marshmallow on your phone. You can either install the full Android SDK or get them from this XDA thread at URL http://forum.xda-developers.com/showthread.php?t=2317790
A.2. Install WinRAR.
You will need to use a tool called WinRAR to extract or replace certain files in an archive. You can download a copy from URL http://www.win-rar.com/
A.3. Download a Mako Google factory image of Lollipop at URL https://developers.google.com/android/nexus/images?hl=en#occam
We are going to modify the factory image of a Lollipop build. To upgrade my Mako, I used the LMY48M build.
A.4. Download the WORKING IMAGE of Android M on Nexus 4
Get the image file from URL http://dmitry.gr/index.php?r=06.+Thoughts&proj=02.+Android+M+on+Nexus4
You will get an archive called "MakoM_bin_v2.zip" file. If there is a newer version, use that instead but I used this version when I installed on my Mako.
A.5. Download TWRP for Mako
Get the TeamWin Recovery Project (TWRP) v2.8.7.0 from URL https://dl.twrp.me/mako/twrp-2.8.7.0-mako.img
A.6. Download the Google Apps (not provided in the AOSP builds).
Get the file "gapps-mm-fix.zip" from URL https://www.androidfilehost.com/?fid=24052804347833783
A.7. Download a patched kernel image that allows you to install SuperSU root.
Get the file "Fixed_Data_root.img" from URL https://www.androidfilehost.com/?fid=24052804347833767
A.8. Download a fix for Location services (GPS) not working.
Get the file "framework-res.apk" from URL http://forum.xda-developers.com/showpost.php?p=63229334&postcount=434
A.9. Download the root manager utility.
Get the file "BETA-SuperSU-v2.52.zip" from URL http://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
B. Checklist
B.1. If you have downloaded everything, you should have a list of the following:
- minimal_adb_fastboot_v1.3.1_setup.exe
- wrar521.exe
- occam-lmy48m-factory-03ae06e5.tgz
- MakoM_bin_v2.zip
- twrp-2.8.7.0-mako.img
- gapps-mm-fix.zip
- Fixed_Data_root.img
- framework-res.apk
- BETA-SuperSU-v2.52.zip
C. Installation and building the installer
C.1. Install the "minimal_adb_fastboot_v1.3.1_setup.exe" and "wrar521.exe" installers, leave settings as default.
C.2. Extract the content of file "occam-lmy48m-factory-03ae06e5.tgz" using WinRAR, it'll create a folder called "occam-lmy48m". Rename "occam-lmy48m" to "mako-marshmallow".
C.3. Extract the content of file "MakoM_bin_v2.zip" and you should get the following files:
- system.img
- Choose either "n4_lte_modem.img" or "normal_modem.img" depending if you want LTE support or just 3G (UMTS) support and rename that file to "radio-mako-m9615a-cefwmazm-2.0.1701.07.img"
C.4. Rename the file "twrp-2.8.7.0-mako.img" to "recovery.img", and "Fixed_Data_root.img" to "boot.img"
C.5. Replace the "radio-mako-m9615a-cefwmazm-2.0.1701.07.img" file inside the "mako-marshmallow" folder with our "radio-mako-m9615a-cefwmazm-2.0.1701.07.img" which we extracted from file "MakoM_bin_v2.zip"
C.6. Open the "image-occam-lmy48m.zip" file and replace the following files which we downloaded from the twrp.me or dimitry.gr site. They are:
- boot.img
- system.img
- recovery.img
C.7. Open a command shell:
Start -> Run -> cmd
From the command shell, go to the folder called "mako-marshmallow"
C.8. Make sure the Nexus 4 has at least 80% battery and restart the phone into bootloader mode (by switching off the phone, the pressing the on button and at the same time pressing the volume down button). To confirm you are in bootloader mode, type in the command:
fastboot devices
You should now see the output "xxxxxxxxxxxxxxxx fastboot" appear, where "xxxxxxxxxxxxxxxx" is the serial number that appears on your Nexus 4 screen. They should be the same and you should only have one line appearing, disconnect any other device if they appear on the list.
C.9. Install the image you just build by running the script "flash-all.bat". A Series of statuses will appear on the screen. Do not disconnect the phone from the cable and let the script install everything. If done correctly, you will find the Nexus 4 rebooting. WARNING: This will erase all user data on your Nexus 4!
C.10. Once you see the Home screen of Marshmallow on your Nexus 4, go to Settings -> About Phone and tap the BUILD number seven (7) times. When you go back to the Settings screen, just above the "About Phone" is a new menu item called "Developer Options".
C.11. Go to Settings -> Developer Options and enable "USB debugging". To ensure debugging is on, go to the command shell and type:
adb devices
It sure display the list of devices with the same serial number and should have the word "device" next to the serial number. You will be prompted on the phone if you want to allow this connection.
C.12. Make sure the USB is connected in MTP mode (Transfer files mode). In windows file maanger (Press the Win-E keys), you will see a device called "Nexus 4". Open it and in the "Internal storage", go to the "Download" folder and copy the following files:
- gapps-mm-fix.zip
- framework-res.apk
- BETA-SuperSU-v2.52.zip
Then, in a command shell, issues the command:
adb reboot bootloader
C.13. From the bootloader screen, press the volume down button until the option "Recovery" appears, then press the Power button once to boot into TWRP/Recovery.
C.14. In TWRP, select to install the file "gapps-mm-fix.zip" and "BETA-SuperSU-v2.52.zip" from the "Download" folder. Once completed, press the "Reboot" button that appears in TWRP.
C.15. When the phone restarts. Go to Settings -> Backup & reset and reset the whole phone. If you get a error message from the "Setup Wizard", press the Open-apps (ie. the square softkey on the screen) and you should see the "Settings" pane.
C.16. Once the phone restart from the master reset exercise. You will be prompted as if you just switched on a new phone. Fill in as necessary until you get to the Home screen.
C.17. We will need to replace a file to get Location Services (GPS) working. From you command shell:
adb root
adb remount
adb shell
cp /sdcard/Download/framework-res.apk /system/framework/
exit
adb reboot
C.18. I disabled the following apps (drag the app to the "App Info" button, and press the "Disable" button) for the following and replaced the with similar app from Google Play (name in brackets). This was done as the built in apps kept crashing every few minutes or didn't work as expected. The apps are:
- Browser (Chrome Browser)
- Clock (Clock)
- Camera (Google Camera)
- Calendar (Google Calendar)
- Contacts (Google Contacts)
- Music (Google Play Music)
- Gallery (Google Photos)
- Search (Google)
- EMail (GMail)
C.19. Restart phone and you're ready to experience a stable (close to Google stock) build of Marshmallow on your Mako (Nexus 4).
C.20. Fixing the "Google Now on Tap" not working problem (thanks to gamekid94).
Go to Settings -> Apps
- Tap on the "Gear" (icon on the top right) -> Default Apps -> Assist & voice input -> Assist app
- Select "None", then select "Google App".
Go to Settings -> Google -> Search & Now -> Voice
- Enable "Now on Tap"
C.21. Install and customize as you see fit.
Click to expand...
Click to collapse
thanks man

ladysuin said:
thanks man
Click to expand...
Click to collapse
Really?? You quoted the original post for this??