Database Develop

Wifi "Unable to Scan for Networks"

My wifi is always turned off, and when i enable it. It turns on for 5 seconds say "unable to scan for networks" and then turns off.
if anyone have encounter the same problem before and know how to fix it. it will be great.
thanks.
my phone is rooted and i'm runnig LCR 1.8.2

my phone does the same exact thing, It has done that since the day I got it.
In my case it is a hardware problem. I got my phone on ebay, I registered the phone with acer and had a 1 year warranty, but they said I had to take it back to the store where I got it from, so a warranty claim with acer isn't going to get you anywhere.

My liquid got the same problem too.

"Unable to Scan for Networks" SOLUTION - WITHOUT ROOTING
**** SOLUTION - WITHOUT ROOTING *****
I searched many forms to solve the "Unable to scan network" issue. All explained how to do it after rooting and I did not want to root my phone.
Yesterday, while playing with the phone and SDK, I could repair it by deleting "bcm_supp.conf" file. This is what I did:
1. Install the android SDK.
(make sure the <SDK>/tools path is added to the windows path variable. My Computer -> Properties -> Advanced -> Environment Variables -> System variable -> add the SDK path at the end of Path variable )
2. On your phone, please enable (tick mark) "USB debugging" under "Settings" -> "Applications" -> "Development"
3. Connect your phone using USB to PC/Laptop. Close phone manager application if it comes up on the PC.
4. Run "ddms.bat" from <SDK>/tools directory. The DDMS application will come up and it should readily connect to your phone. (in the main screen, under Name, you should find the phone ID and SW ver. no.)
5. Go to menu Device -> File Explorer. New window will come up.
6. Here go to data -> wifi directory. You will see a file bcm_supp.conf.
7. Though it is not possible to read this file, you should be able to delete it. (at least I could delete it). You can delete the file by selecting it and then pressing red "-" on top left of the window.
8. Now close the DDMS and disconnect the USB. Enable WiFi and scan for networks. The bcm_supp.conf file will get created and you should be able to find the networks.
Please note:
1. Do this on your own risk.
2. All your previous WiFi settings are gone as you delete the file.
3. If you don't know how to install SDK, just google, you will find many forms explaining.
4. I tried to delete the file from "Terminal Emulator", but it did not allow. I guess DDMS has some special permissions.

i think this method is for the samsung galaxy S,because i tried it for my Liquid and there is no folder called wifi in /data, the only folder called wifi i found it in /data/etc/wifi and the folder is empty there is no file on it

[Q] DDMS cannot find ADB

I am trying to fix the WiFi on my Captivate. This thread here tells how to do it. Unfortunately when I run DDMS I get the error "Failed to get the adb version: Cannot run program "adb": CreateProcess error=2, The system cannot find the file specified." I have tried installing the SDK on both a Windows 7 64-bit and XP 32-bit machine. I get the same error on both machines. I have tried both the generic Galaxy S drivers and the Captivate drivers. Any suggestions? Here are the instructions I've followed in case you don't want to read the other thread:
1. Install the SDK -> Android SDK | Android Developers
(make sure the <SDK>/tools path is added to the windows path variable. My Computer -> Properties -> Advanced -> Environment Variables -> System variable -> add the SDK path at the end of Path variable )
2. On your phone, please enable (tick mark) "USB debugging" under "Settings" -> "Applications" -> "Development"
3. Connect your phone using USB to PC/Laptop. Close phone manager application if it comes up on the PC.
4. Run "ddms.bat" from <SDK>/tools directory. The DDMS application will come up and it should readily connect to your phone. (in the main screen, under Name, you should find the phone ID and SW ver. no.)
5. Go to menu Device -> File Explorer. New window will come up.
6. Here go to data -> wifi directory. You will see a file bcm_supp.conf.
7. Though it is not possible to read this file, you should be able to delete it. (at least I could delete it). You can delete the file by selecting it and then pressing red "-" on top left of the window.
Thanks!

Post in q and a.
sent from my craaazy fast cappy running di11igaf v2.5 at 1280mhz!!!

silverslotcar said:
Post in q and a.
sent from my craaazy fast cappy running di11igaf v2.5 at 1280mhz!!!
Click to expand...
Click to collapse
Yes, Q&A would be the proper location for this thread.
Sent from my GT-I9000 using XDA App

Ok, sorry, although I just figured out the problem. The Path should have the platform-tools directory instead of the tools directory because that's where adb is located. I corrected that and it loaded right up. Unfortunately, when I click on the + sign for the Data folder it doesn't show me anything Guess I'm going to have to do a factory reset after all.

automagrt said:
I am trying to fix the WiFi on my Captivate. This thread here tells how to do it. Unfortunately when I run DDMS I get the error "Failed to get the adb version: Cannot run program "adb": CreateProcess error=2, The system cannot find the file specified." I have tried installing the SDK on both a Windows 7 64-bit and XP 32-bit machine. I get the same error on both machines. I have tried both the generic Galaxy S drivers and the Captivate drivers. Any suggestions? Here are the instructions I've followed in case you don't want to read the other thread:
1. Install the SDK -> Android SDK | Android Developers
(make sure the <SDK>/tools path is added to the windows path variable. My Computer -> Properties -> Advanced -> Environment Variables -> System variable -> add the SDK path at the end of Path variable )
2. On your phone, please enable (tick mark) "USB debugging" under "Settings" -> "Applications" -> "Development"
3. Connect your phone using USB to PC/Laptop. Close phone manager application if it comes up on the PC.
4. Run "ddms.bat" from <SDK>/tools directory. The DDMS application will come up and it should readily connect to your phone. (in the main screen, under Name, you should find the phone ID and SW ver. no.)
5. Go to menu Device -> File Explorer. New window will come up.
6. Here go to data -> wifi directory. You will see a file bcm_supp.conf.
7. Though it is not possible to read this file, you should be able to delete it. (at least I could delete it). You can delete the file by selecting it and then pressing red "-" on top left of the window.
Thanks!
Click to expand...
Click to collapse
Hi,
I am going crazy with this crap, I am not impressed how google put this **** together.
I can see you managed to fix the issue of ddms not finding adb but I didnt. Can you please explain in more details? I searched everywhere over the internet but everybody just says "add the path". Fine. Then what....?
I added a new path in the environmental system variables called "SDK" and points to:"C:\program files\Android\android-sdk-windows\platform tools\. Still no joy. What am I doing wrong?
thanks

Did you reboot after adding the path?
And I didn't realize that Google had changed the SDK path to "platform-tools" with their latest release. Just plain dumb imo as folks have been so used to it being in just the "tools" location.

Market not working in NookieFroyo

I am using NookieFroyo installed internally to EMMC from here:
http://forum.xda-developers.com/showthread.php?t=938200
This same problem was reported by someone else here:
http://forum.xda-developers.com/showpost.php?p=11117975&postcount=330
But I don't believe this is an issue specific that that particular ROM because everything was working in Market for me before Tues Feb 3, 2011; but now Market will only allow me to browse; but not download anything. This is also happening with honeybunches for me.
Anyway, Market is not working. It won't start the download of any app. I can still browse. I have tried in Settings>Applications and with Titanium Backup to clear Market cache and data... and I have rebooted the device. Still nothing.
I modified my build.prop to make the fingerprint look like a Nexus One and I was able to download 2 apps (espeak and colordict) and then it stopped working again after that. Won't even kick off the download.
Anybody else experiencing a problem with NookieFroyo and Market or have a workaround?
I should mention that I have a Nexus One and the market is working fine on it the entire time, so it isn't a problem with the Market or my internet connection. Also, I know of 2 other people report being unable to download anything in the market on NookieFroyo... and I am surprised that it isn't affecting more or that there aren't more reports.

You're definitely not alone in this. I'm having the same issue in Honeybunches. Market downloads appear to start downloading, but the app never installs and does not show up on the device.
I've seen this mentioned by other users as well in the Honeybunches topic in the dev forum.

Same here. Well I'm running nookie froyo from sd.
Sent from my Nexus One using XDA App

It got so bad that I went back to rooted 1.0.1... At the moment, I have been observing that the official Barnes and Noble OS v1.0.1 rooted is the most stable and functional configuration for the Nook Color.
I have been working on a how-to, to make it easier for people to get back from NookieFroyo on EMMC... to a rooted 1.0.1. (this should also work from a Nook Color that isn't booting at all from internal memory). Many thanks to the original contributors (attributed below). I am merely trying to itemize all the steps.
1) Download WinImage (win32diskimager won't work for the following steps...). You can get WinImage here:
http://www.winimage.com/
2) Download this Image and burn it to the SD card with WinImage (using the "Disk" -> "Restore Virtual Hard Disk Image on Physical Drive")... if you cannot see the file when you browse for it... it may be the file extension, change the browse window to look for "Files of Type" = All Files.
Image download link (it may be zipped or compressed, decompress first) - for some reason only WinImage will work for this task:
http://www.multiupload.com/5RY9YX429S
Got that from brianf21 here - http://forum.xda-developers.com/showthread.php?t=938200
3) Power off Nook, put SD card in. Power on Nook. It should boot into Clockwork Recovery screen (text menu)
4) Under mounts and store, format /data and format /system (volume buttons move up and down, N button selects, power button escapes)
5) Escape to main menu, go to "Install Zip from SD card" and install the 1.0.1 file (do not install the Froyo file). Wait until it finishes, do not interrupt this process.
6) Power off the Nook, remove the SD card. Power on Nook and register it online. As soon as you are done registration and see the Nook desktop, power off the Nook (do not let it run any updates, if it downloads the Elephant book, it's ok).
7) Download and burn this image to SD card (you can use either WinImage or win32diskimager for this):
http://legacyschool.us.to/nookdev/clockwork/rootpack_1gb-0.5.tar.gz
The remaining instructions are here (But I will itemize them more briefly for you below...)
http://legacyschool.us.to/nookdev/clockwork/rootpack-instructions.html
Much thanks to TheCubed for this thread - http://forum.xda-developers.com/showthread.php?t=922870
9) Insert the SD card (with rootpack written to it) and power on Nook. It will boot into Clockwork Recovery menu again. This time you do NOT need to format anything.
10) Go to "Install from ZIP" and go into the required folder, install "root.zip"
11) Install "googleapps.zip"
12) Install "block-1.1.zip"
13) Power off Nook. Remove SD card. Power on Nook.
Once your device reboots, you will be presented with a setup wizard. (Below instructions from GabrialDestruir’s AutoNooter post on XDA)
1. Upon boot unlock your screen.
If it asks you to select a default application, put a checkmark in the box, and select SoftKeys as the default application.
2. At the Android Welcome Screen skip Sign In.
3. Enable Location Services when given the option.
4. Connect to Wifi and launch Youtube from "Extras".
5. Click the Menu button (The one RIGHT of the Up Arrow).
6. Select "My Channel" and Login using your Gmail Account. (YOU MUST USE YOUR FULL GMAIL ADDRESS!)
7. Exit Youtube and Launch Gmail from "Extras".
8. Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
9. Open up Market and Accept Terms and Service.
10. Insert your SD card
11. Go to Settings > Device Info > SD Card > Unmount SD Card
12. Format SD Card
13. Install Dolphin Browser HD from market (and make it your default Browser)
When you install apps, they will appear under "Extras"
If you don't like the Barnes and Noble home-screen and want a different Launcher:
1) search the Market for ADW.Launcher and install it
2) Go to Extras -> SoftKeys and after you press it, there should be a bar at the bottom that has tools (second from the right). Select that
3) Virtual Home button > Normal Press > ADW Launcher
4) Virtual Home button > Long Press > Home
6) Back
Now any time you press the N button once, it will call up the "back", "home", "menu", "search", "softkeys prefs", "close softkeys" buttons.
Press the N button twice quickly, and it will bring you to ADW Launcher (a configurable desktop, with an application drawer button at the bottom, that works like most android devices)
You can still access the B&N Launcher by pressing the N to bring up softkeys, and then long-pressing the virtual home button.
I have discovered Kobo reader isn't downloading my books; but I tested Kindle works and Youtube works in the browser for me for sure. According to the documentation the YouTube app works for some people and not others. I will work on trying to figure out what the X-factors are on that.
Also, this still uses the older market; but I don't mind. At least it downloads, and seems to see more applications.

Also seeing this issue- angrybirds, facebook, & several other standard apps missing from Market. Tried changing ro.build.fingerprint a few different ways in build.prop as well as the clear cache/data on google services framework/market idea. Any other thoughts?
- JMG

[Q] Remove webos recovery?

I have already removed webOS ulimage so webos does not appear in the moboot menu. However now i want to know how to remove the webOS recovery option in the moboot menu as well.

I wouldn't completely advise removing it - maybe rename it so it's still there, but just hidden, in case you have to return to it with WebOS Doctor or anything. Especially since it's the only way to go about using ACMEUninstaller / ACMEInstaller2 / WebOS Doctor / Recovery images and the like.
Then again, I just did some looking in the /boot, and can't see anything about that recovery, unless it's tied into the WebOS one.

UnderZone7 said:
I have already removed webOS ulimage so webos does not appear in the moboot menu. However now i want to know how to remove the webOS recovery option in the moboot menu as well.
Click to expand...
Click to collapse
I wouldn't remove webOS, not only for the reasons ve6ay stated above, but because I find webOS very useful. It is a useful and elegant os, battery life is much better, and that's the beauty of the TP, the ability to dual boot.

The nice thing is, if you remove the Moboot entry for WebOS, you don't actually remove WebOS - you just remove the option to boot from it. BUT you also can bring it back with just a quick terminal command (I noticed this during my poke-around of /boot as I stated earlier).
Besides, if you want to skip it entirely, you can create two file in your /boot directory directly from your CM install.
I used Terminal Emulator, but you can from Root Explorer, too. Browse to /boot, mount it (hit the mount r/w button up top), hit Menu => Create New File. Call it "moboot.timeout" (without quotes). Long-press it, click Open With, choose Text Editor. In there, as the only line there, type in your timeout - (if you want it to be always super-fast, chose 1), then hit enter, back, then save.
Second file to create is one called moboot.next - which basically says "On next reboot, always choose <selection>" To use this, again, Menu => Create New File => Long-press it => Open With => Text Editor. In here, type in CyanogenMod, hit enter, back, save, and then reboot. On reboot, you should automatically go straight into Android, no options to go anywhere else.
Or, if you can stomach booting into WebOS long enough, install Cyboot from Preware, and use it to make your changes to the timeout and default boot options. I just did this, and can tell you, if you do set Next to Android, and timeout to something abysmally small, you automatically will boot into Android, no choice of anything else.
Hope that helps you, mate.

You REALLY don't want to do this, as stated above if something goes terribly wrong it's the only way to use ACMEInstaller and stuff. Even WebOS takes not much space and pretty cool, so i choose to leave it, but recovery is a must..

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??