Database Develop

[How to] Install android_winusb.inf, create adb shell loop, and root your phone

First off you need to have Android-SDK installed on your computer. I will not go into details about that process but here is the link to Google's official install page. Navigate to the folder you placed Android-SDK and run the SDK Setup.exe and make sure that you download the usb 3.0 driver software from the sdk updater window. I recommend erasing any HTC Sync software or drivers so that you can start from a clean point then reinstalling them.
Once you get the SDK installed from Google you need to go in a modify the USB 3.0 .inf file. Navigate to the folder you placed the Android-SDK and one step down you will see a folder that is named usb driver. Open the usb driver folder and then open the android_winusb.inf file in notepad. It should default into notepad when you click it. Next you need to copy and paste this text into notepad.
Find the section labeled [Google.NTx86]. At the end of that section, add the following lines.
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
Then find the section [Google.NTamd64]. At the end of that section, add the following lines.
;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
Again just copy and paste. I have attached pictures to show where these need to go.
So now we have the USB driver on the computer and ready to be installed once you plug-in your Incredible.
On your Incredible press->Menu->Settings->Applications->Development->(check)USB debugging. Plug in your Incredible and you should get the found new hardware notification, select the No, not this time radio button, Install from a specific location(Advanced), Don't search, I will chose the driver to install. You should now have "Android Composite USB Device" in the white field selection box, click have disk and browse to the location of the android_winusb.inf file and click ok. Click next and it should install the USB driver you need for ADB to work properly.
Now if you click Start->(right click)My Computer->Properties->Hardware(tab)->Device Manager, you should see Android Phone at the top then when you open the tree you should see Android Composite USB Interface.
This will enable you to use the Android SDK from a command prompt to access your Incredible.
Once that is done open a command prompt by clicking Start->Run(XP) or the search box in W7 and type CMD(in W7 you need to right click command prompt and run as admin.). Then in the command prompt window type; cd (your file path to Android-sdk). now to test it type adb shell and press enter then reboot recovery and press enter. This should reboot your Incredible into recovery. (You can also type reboot bootloader to get to that screen.)
Once you make sure that is working press vol. up and power, then select reboot with the power button. GO back into Settings and deslect the USB debugging check box. Now we need to get adb shell to loop so that it can catch the Incredible in its flawed sequence that allows us to access the phone in recovery. Navigate your command prompt box to your tools folder and then follow these directions courtesy of prerunnerseth over at AndroidForums.com
type edit loop.bat
in edit enter the following
Code:
@echo off
:TOP
adb shell
GOTO TOP
press alt-f then x
hit enter for yes
Here is a link to Androidforums.com with two different methods for gaining root access on your phone.
This is a great 10 min. video on how to root as well.
I hope this helps clear some confusion up for those that can't quite get the Android Composite USB interface going. This credited to all parties involved and is just a collection of info.

So what you are saying is we need to take it off of debug mode before looping the shell command?

Hmmm...I had mine in Debug mode every time (failed every time, too). Ok...headed to BB to get the PNY card and try again w/o debug mode on.

Here's the android_winusb.inf file for the Incredible.
Switch this file out with the one that's inside your AndroidSDK/usb_driver folder.
http://www.megaupload.com/?d=S2H4R3QZ
Here's the adb shell loop for Windows.
I placed it inside my AndroidSDK/tools folder.
http://www.megaupload.com/?d=N0150VUI
I hope this helps!

SeanRinVA said:
Hmmm...I had mine in Debug mode every time. Ok...headed to BB to get the PNY card and try again w/o debug mode on.
Click to expand...
Click to collapse
I had mine on and it worked. Try, try, try you'll get it!
Good luck!!!

SeanRinVA said:
Hmmm...I had mine in Debug mode every time. Ok...headed to BB to get the PNY card and try again w/o debug mode on.
Click to expand...
Click to collapse
Report back. Rooting the DI will only get simpler and more reliable the old fashioned way: a LEAK from HTC!! If we had something to flash from fastboot or recovery without first obtaining root, we would all have root except for those who didn't check their MD5's, in which case they'd brick. So this new (not you, OP, or you Unrevoked team, but this exploit in general), ****ty, hard way = relatively safe, totally unreliable. Old way = almost 100% reliable but little room for error.

jesus this is frustrating
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately

sylent101 said:
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately
Click to expand...
Click to collapse
It is supposed to say that... and you can't install the android sdk you can only open it... its is just a basic dos applicarion with a GUI front of it if I'm not mistaken so just try redownloading it

Try following the 10 minute video exactly on a cpu that does not have the sdk already on it. I used the same exact sd card and could not get it on my pc that already had the sdk , sync , drivers on it. I followed the instructions on the 10 minute video using the sdk and htc sync from the video link on a machine that did not have them prior and it worked first try using the first (adb shell) method. I think it had something to do with the prior sdk install I had.

another let down, tried with the 10 mins video also, oh well

sylent101 said:
when i click on android phone it says android adb interface am i doing something wrong??! also when i try to install sdk a black box flashes then leaves immediately
Click to expand...
Click to collapse
Right click on Android adb interface and then select update drivers, then follow the instructions above for installing the android_winusb.inf file. As stated before SDK doesn't actually "install' it is more on an interface that you can open to download the new sdk's for app development and debugging. you should get the black box and another box that is called Android SDK and AVD manager. Within that window you should have these options on the left; Virtual devices, installed packages, available packages, Settings, and About.
Edit; Did you follow the instructions about editing PATH with the C:\Android-SDK-Windows\tools directory path?

[Q] ABD Drivers + Windows 7 issues (plus a couple more questions)

Hello XDA Community.
I'm attempting to install the new RC of CyanogenMod-6 for the Hero CDMA. I'm currently running the stock 2.1 version of Android. I've been following the guides that were referred to in the thread (I tried posting the urls but new users can't do so to prevent spam).
I've successfully rooted my phone and now I'm trying to do a Nandroid backup. I'm running Windows 7 32-bit and have hit a road block with ADB not recognizing my device. I followed the guide put together by Nephron to install the Android SDK. I've spent several hours going through threads and doing google searches looking for the solution. I have debugging turned on and I don't mount my SD drive when I plug the USB cord in. I've used USBDeview as some have suggested to delete current HTC drivers and then reinstall - no luck.
Here is a screen shot of what happens when I plug in my Hero:
See attached - "failedinstall.jpg"
Then I'll go to device manager to manually install the driver (it never allows me to manually select upon connection for some reason):
See attached "devicemgr.png"
And then this is the message I get when I point it to the "right" folder with the drivers:
See attached - "unabletoinstall.png"
So, on the Android SDK site I noticed this message:
"The USB driver for Windows provides support for the following Android-powered devices:
T-Mobile G1* / ADP1
T-Mobile myTouch 3G* / Google Ion
Verizon Droid*
Nexus One
* Or similar hardware on other carriers
Any additional devices will require Windows drivers provided by the hardware manufacturer.
^So is all of this HTC's fault? I've downloaded a couple of different .zip folders from different threads claiming that these drivers would work. But none of them have yet to do the trick for me.
I'm new at this so I have a few other questions as well:
Most guides I've read about how to do a Nandroid backup always recommend flashing a ROM b/f doing a backup. But I want to backup my current stock rom and settings before I flash. Wouldn't I want to create a recovery image before installing any other ROMs? Perhaps I'm misunderstanding some requirements?
Referring again to the thread on the CyanogenMod RC, can someone help me understand step #3? How do I know if it is necessary to update my radio? What implications does this have? I tried looking for info about this on the wiki and I couldn't find anything comprehensive enough to answer my question.
I'd appreciate any guidance!

Before you modify anything you will want to boot into recovery, assuming you flashed one, by holding down Home and turning the phone phone back on(power button). But since you don't have adb working then you probably haven't. You can still do this using terminal on your phone.
Download terminal emulator from market and then download a revoery image (AmonRa 1.6.2 or Darch's 1.7xx) and then mount your sdcard to the computer and transfer the recovery to the root of the sdcard. Open up terminal emulator and type in
Code:
su
cd /sdcard
flash_image recovery recovery-RA-heroc-v1.6.2.img(type the exact file name of the recovery you are using)
reboot recovery
If you had factory 2.1 on your phone then you have the latest radio. The radio can be flashed just like any ROM, but make sure that the radio is not for GSM phones as this will destroy your phone.
Instructions from Android Developers and ADB, Fastboot, and Nandroid for Noob
Download the latest Android SDK.
Unzip to C:\AndroidSDK
Right-click on (My) Computer, and select Properties
Go to Advanced settings
XP: Click the Advanced tab
Vista/7: Click Advanced system settings on the left
Click the Environment Variables button
double-click on Path (under System Variables)
Add the full path to the tools/ directory:
C:\AndroidSDK\tools\
(make sure a semicolon ( separates this new path from all the others)
Latest windows sdk version appears to need: "C:\AndroidSDK\android-sdk-windows\tools", install location may change with further updates..
Run C:\AndroidSDK\SDK Setup.exe
If you get an error about not having Java SDK installed but you do, add the path to 'bin' within your Java installation location to the Path environmental variable as described above before the sdk entry you just made. (eg add "C:\Program Files\Java\jdk1.6.0_20\bin;") This is likely to only be necessary where the 64 bit Java SDK is installed (obviously) on a 64 bit machine.
If it gives you an error about http go to settings and click on "Force http//....."
Unselect all options except for the USB driver
If you can't get the setup to work, download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
On your phone, click Settings > Applications > Development and make sure USB Debugging is on.
Plug your phone into your computer via USB cable (it needs to be on). It should say installing drivers if using Windows.
After it installs the drivers, goto the Start menu and type cmd into the search bar (Vista or higher) or click Run then type in cmd (XP) to open the command prompt.
Type the following into the command prompt window:
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set. If you do NOT see a serial number, then we need to reinstall the drivers.
Download USBDeview
While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the HTC/Android drivers and uninstall them all. (Windows Vista requires program to be run as an administrator, otherwise files won't uninstall.)
Once all have been uninstalled, unplug the phone from the USB cable and plug it back in.
The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
To check, go to Devices in your Start menu then click on the “Android Phone”. Click on the Hardware tab, and check the list of drivers for ADB Interface under Type.
Done! Now you can use ADB to alter your phone from your computer.
If all else fails try installing HTC Sync software-- http://member.america.htc.com/download/Driver/HTC Hero (Sprint)/HTC_Sync_2.0.40.exe and then removing the drivers for it and then trying to install the android sdk drivers
Or you can dual boot with Linux and all you will need to do is download and unzip android sdk and edit 2 files and everything will work.

WOW>>>>>no that is way to confusing. the best thing to do is install vmware workstation. Then do a virtual WINDOWS XP MODE. from there you will be able to install the drivers and such in order to get the phone to be seen.

the version of htc sync i used for all my computers including win 7 was 2.0.33
if you want it then just pm me and I will get it to you
they don't offer it for a download anymore
this version corrected all my driver issues

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] Any easy way to completely copy the state of one Moto X to another?

I got a new phone with a wood back and will be selling my old one soon. Is there an easy way to completely clone my old phone's contents onto my new one?

Could try doing an NAND backup on the old one. Then putting it in the same directory of the new one. The directory would be /twrp/backups/(some numbers assigned to be your phones ID)/backup name.
Your ID will change, but you should be able to use that backup to restore on the new phone.
Sent from my XT1060 using xda app-developers app
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
You might have to make an NAND on the new phone to have the recovery make the new filepath
Sent from my XT1060 using xda app-developers app

kkeller87 said:
Could try doing an NAND backup on the old one. Then putting it in the same directory of the new one. The directory would be /twrp/backups/(some numbers assigned to be your phones ID)/backup name.
Your ID will change, but you should be able to use that backup to restore on the new phone.
Sent from my XT1060 using xda app-developers app
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
You might have to make an NAND on the new phone to have the recovery make the new filepath
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Thanks. This requires root, right? I haven't rooted either of the phones, although I would if it sped this process up. It's something that I eventually want to do anyway.

beelbeel said:
Thanks. This requires root, right? I haven't rooted either of the phones, although I would if it sped this process up. It's something that I eventually want to do anyway.
Click to expand...
Click to collapse
Yea. Sorry. A custom recovery/safestrap is required. I kinda assume anyone who's on XDA has it. Without root I'm not entirely sure how to do it any other way than manually.
Sent from my XT1060 using xda app-developers app

Without root the best you can do is mybackup pro or titanium backup. They will back up app data but not the apps themselves. Get your new phone, download your apps, restore app data from mybackup.

I wrote this before, but this is how you can backup your apps and their data with a computer and without root. Moto X's have Motorola Migrate that can move over some settings.
This process can take a bit to explain, so sorry for the long post.
First, you'll need to install Oracle’s Java Development Kit, which the Android SDK requires. Download and install the 32-bit version. The Android SDK wants the 32-bit version, even if you're using a 64-bit version of Windows.
Next, download the Android SDK from Google. Extract the .zip folder to a location of your choosing, but remember where you put it. If you have the option to open extracted contents in a new window, do so.
Okay, now open the Android SDK Manager (you may have to open a subfolder or two) with administrative rights. You do this by right clicking on the .exe and choosing the option "Run as administrator". A window will pop up, click yes, and after a small wait, the SDK Manager will open.
Now within the SDK Manager, under the tools section, check the box for Android SDK Platform-tools and click Install. This can take some time depending on your Internet connection. Once installed, go back to the open window where you clicked the SDK Manager .exe and navigate to the folder named "Platform Tools". If you're unsure where this is, the SDK Manager has the path of install located near the top.
Now let's get the phone ready. If you can, charge your device to its fullest. Now go into the settings, scroll down to 'development options'. Near the top of this menu, make sure the toggle switch is in the 'on' position. Now scroll down to USB debugging, and tick the box. Tap "OK" when the message shows up. Now plug the smaller end of the USB cable (preferably the one that came with your phone) into the bottom of the phone and the other into an open USB port of your computer. It's best to use a 2.0 USB port (no blue end) and if on a desktop, a port located in the rear.
If your computer starts installing any drivers, let it do this. Once that's finished, go to the window with the Platform Tools folder open. You should see a few files, two named "ADB" and another "Fastboot". Now hold your Shift key, right click in an open area, and choose the option "Open command window here". You may release the shift key at this time.
We're almost done. To make sure your tablet is seen by the computer type:
Code:
adb devices
One device should be listed. If you see no devices, adb can’t communicate with your device because its driver isn't installed properly. In this case, go back to the SDK Manager and download the USB drivers. You may also need to restart your computer.
Assuming you're up and working, type:
Code:
adb backup -apk -shared -all -f C:\backup.ab
This backs up all the installed apps (APK files) and shared storage (SD card) data to the C:\backup.ab file on your computer.
After running this command, you'll have to agree to the backup on the device. You can also encrypt the backup with a password here, if you like (leave it blank if you don't want encryption). Depending on how much data there is to back up, this can take some time. The device will let you know when it's done.
Now for the restoration process:
On the new device, make sure USB debugging is enabled. On the computer, follow the same steps for opening the adb command window. Ensure adb can see the device, then type:
Code:
adb restore C:\backup.ab
On the device, you will need to confirm you want to do a full restore. If you encrypted the backup, enter in the password, then hit "Restore my data". If you didn't add encryption, then leave that area blank. Once the restoration is done, you're good to go.

Thanks for the replies.
Hikikomori-Otaku said:
I wrote this before, but this is how you can backup your apps and their data with a computer and without root. Moto X's have Motorola Migrate that can move over some settings.
This process can take a bit to explain, so sorry for the long post.
First, you'll need to install Oracle’s Java Development Kit, which the Android SDK requires. Download and install the 32-bit version. The Android SDK wants the 32-bit version, even if you're using a 64-bit version of Windows.
Next, download the Android SDK from Google. Extract the .zip folder to a location of your choosing, but remember where you put it. If you have the option to open extracted contents in a new window, do so.
Okay, now open the Android SDK Manager (you may have to open a subfolder or two) with administrative rights. You do this by right clicking on the .exe and choosing the option "Run as administrator". A window will pop up, click yes, and after a small wait, the SDK Manager will open.
Now within the SDK Manager, under the tools section, check the box for Android SDK Platform-tools and click Install. This can take some time depending on your Internet connection. Once installed, go back to the open window where you clicked the SDK Manager .exe and navigate to the folder named "Platform Tools". If you're unsure where this is, the SDK Manager has the path of install located near the top.
Now let's get the phone ready. If you can, charge your device to its fullest. Now go into the settings, scroll down to 'development options'. Near the top of this menu, make sure the toggle switch is in the 'on' position. Now scroll down to USB debugging, and tick the box. Tap "OK" when the message shows up. Now plug the smaller end of the USB cable (preferably the one that came with your phone) into the bottom of the phone and the other into an open USB port of your computer. It's best to use a 2.0 USB port (no blue end) and if on a desktop, a port located in the rear.
If your computer starts installing any drivers, let it do this. Once that's finished, go to the window with the Platform Tools folder open. You should see a few files, two named "ADB" and another "Fastboot". Now hold your Shift key, right click in an open area, and choose the option "Open command window here". You may release the shift key at this time.
We're almost done. To make sure your tablet is seen by the computer type:
Code:
adb devices
One device should be listed. If you see no devices, adb can’t communicate with your device because its driver isn't installed properly. In this case, go back to the SDK Manager and download the USB drivers. You may also need to restart your computer.
Assuming you're up and working, type:
Code:
adb backup -apk -shared -all -f C:\backup.ab
This backs up all the installed apps (APK files) and shared storage (SD card) data to the C:\backup.ab file on your computer.
After running this command, you'll have to agree to the backup on the device. You can also encrypt the backup with a password here, if you like (leave it blank if you don't want encryption). Depending on how much data there is to back up, this can take some time. The device will let you know when it's done.
Now for the restoration process:
On the new device, make sure USB debugging is enabled. On the computer, follow the same steps for opening the adb command window. Ensure adb can see the device, then type:
Code:
adb restore C:\backup.ab
On the device, you will need to confirm you want to do a full restore. If you encrypted the backup, enter in the password, then hit "Restore my data". If you didn't add encryption, then leave that area blank. Once the restoration is done, you're good to go.
Click to expand...
Click to collapse
Thanks for the detailed response. I actually use a mac, and I might have to do some research to see what parts of this process still apply. I may also just investigate other methods of transferring most (perhaps not all) of the data.

beelbeel said:
Thanks for the detailed response. I actually use a mac, and I might have to do some research to see what parts of this process still apply. I may also just investigate other methods of transferring most (perhaps not all) of the data.
Click to expand...
Click to collapse
This may help with getting adb to work on your Mac http://forum.xda-developers.com/showthread.php?t=1917237 Otherwise you could use an application like VMware Fusion to virtually run a Windows OS on your Mac. I know you can get evaluation copies of Windows to use that don't require a product key (they only work for 90 days though).

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