Related
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
After various requests, official and unofficial I have taken the time to consolidate all the needed information to make the flashing process as simple and as noob friendly as possible! Please follow the guide below!
This is the A to Z guide on how to Flash custom SBF, Root, Install Recovery and enable such things as GreyBlur and 1080p recording on the Atrix!
After the release of 2.1.1 from France’s MotoAtrix I was anxious to see what could be done on this SBF.
As we know this is the latest SBF released on the 29th of April, 2011. It is, based on the version numbers, the next step forward from 0.37 on the Stock BELL phone.
After a lot of benchmarking (now 2800-2900 hundered on Smartbench 2011) and testing as well as feedback from the Intl/Bell community, it seems this is the most responsive and battery efficient SBF. I’m amazed at how speedy the phone is, including boot up (which is at least a third faster than 1.4.2)… HSUPA is unlocked as well on this SBF, so this is good news for us as there is no need to flash custom, sketchy mods to enable this on our phones. As for the fingerprint reader, the driver appears to have been updated so it is incredibly responsive so this is an improvement although 1.4.2 was great in this regard.
*To find out more about HSUPA, read the FAQ at the end of the post.
At the moment though, as it stands I can only recommend you install GreyBlur as it is currently the one with the least amount of bugs, and the BEST battery performance.
DISCLAIMER: All of the procedures below require some basic computer knowledge and could potentially brick your phone. Please proceed with caution and make sure you read everything CAREFULLY.
Everything has been tested but requires that this guide is followed TO THE LETTER. AT&T ATRIX NOT SUPPORTED
>> Be aware that sections of this guide apply ONLY to 2.1.1 and now 2.2.3 and are NOT for AT&T Atrix at all! <<
Please check out this AWESOME VIDEO GUIDE HERE! (Thanks to J-Roc!)
Part 1
Part 2
Part 3
Part 4
Make sure your device is in the list below:
Supported devices:
South Korean Atrix (Information pending)
Brazillian Atrix (Base OLYLA U4 0.50.0)
Argentinian Atrix (OLYLA U4 0.50.0 Variant)
Canadian Atrix (OLYLA 0.37.4)
Mexican Atrix (Information pending)
Australian Atrix (OLYEM 1.4.2)
UK Atrix (Orange. Information pending) <----- DO NOT INSTALL GINGERBLUR/GREYBLUR... just 2.1.1
French Orange Atrix (OLYEM_U4_1.3.3)
Required files: (Download all of these as needed)
RSD Lite 5.0 -> Here
Win 7 Drivers x32 (if applicable) -> Here
Win 7 Drivers x64 (if applicable) -> Here
Download 2.1.1 SBF if you are going to Flash this.
OLYEM 2.1.1 SBF -> Here
Mirror -> Here
The Preparation script includes the needed APKs to obtain root and install Clockwork Recovery.
Seven’s Prep Script - > Here
GreyBlur 2.1 -> Here <-- 100% working, great performance.
GingerBlur 4.0 -> Here <-- Nasty startup bug, work around soon.
Seven’s BlurFix -> Here
Seven's DeOdex Tool 2.0 -> Here
GUIDE INDEX:
STEP 1: How to Flash the latest SBFs (Guide for EVERYONE)
STEP 2: ROOT and RECOVERY (and now: DEODEXING!)
STEP 3: Flashing GreyBlur/GingerBlur
STEP 4: Apply BlurFix Patches: Fix issues with BLUR Roms and enable 1080p recording + tweaks!
STEP 5: APN Information and FAQ!
ENJOY!!
GingerBlur/GreyBlur was created by XDA's very own Kenpenneth! Support his work!
{
"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"
}
STEP 1: How to Flash the latest SBF (Guide for EVERYONE)
This is a quick guide on how to flash the latest SBF.
This applies to all SBFs as well so use as needed but operate with caution as doing something wrong here could seriously damage your phone. Make sure the SBF file you are attempting to flash is compatible with your phone. (RESEARCH, do no ask in these threads as Google will easily yield the correct results)
-Make sure your phone is unplugged
-Install the required Drivers for your phone (x32 bit or x64 as needed)
-Extract the SBF zip file to your desktop. It will create a folder with a file with an .SBF extension and should be about 1.4gb in size.
-Install RSD Lite using the installer linked above. This will create an Icon on your Desktop
-Execute RSDLite. This process will take a long while the first time, about 3-4 minutes max.
-Once the program is open, plug in your phone in to the computer. Wait for Windows to notify you that the drivers have been configured correctly (takes 2-3 minutes max)
-Unplug your phone from your PC and then reboot your phone.
-As the the phone powers up (Right as the Red M appears) HOLD the VOLUME UP key…
-The phone will display this message: “Starting RSD protocol support”
-Wait about 20 seconds (on the safe side)
-Having the RSD Lite window open, plug in your phone.
-RSD Lite will display your phone information in the bottom and should list it under slot 1.
Status: Connected…
-Click the button the left of START, a button labeled as: “…”.
-Navigate to the SBF file you extracted above.
-Once you have selected this SBF file, the information readout will display in the “File Properties” Window.
Now you are ready to flash:
-Select START
This process will take about 5-10 minutes depending on your computer. You will know this process is finished once your phone has fully booted and about 2 minutes have passed. WAIT the 2 minutes as sometimes people unplug the phone before RSDLite clears and this has caused issues previously. At this point, after having flashed:
REBOOT your phone. DO NOT SETUP until after the first reboot.
-Unplug your phone from your computer, close RSDLite
-After Reboot, complete the MotoBlur setup. (you can skip it but it’s better not to as it is known to cause some issues on some SBFs and phones).
Wait a few minutes and now the phone is ready for the next step.
You have now successfully flashed!
STEP 2: ROOT and RECOVERY
REQUIREMENTS:
External SD card. Make sure your phone has it inside. <– THERE IS NO WAY TO ROOT WITHOUT THIS.
Noob HELP – Skip this section if you are experienced with ADB and debugging mode.
In order to prepare for this download the “Preparation Script” from the Required Files section above.
-Making sure your phone is unplugged go to:
“Settings -> Applications -> Development”
-Enable USB Debugging – Tick the box.
-Plug in the USB cable to the phone
-Wait for the phone to acknowledge the connection.
-Pull down the Notification bar up top and select “USB Connection”
-In this prompt select “None” and press OK
-The phone will reconnect to the computer with USB.
-Unplug the phone and reboot
-After the phone boots up, plug the phone to the computer.
Now let’s move on to ROOT and RECOVERY
-Make sure USB Debugging is enabled. Plug in your phone (if not already plugged)
-Extract SevenPrepare.zip to your C:\ drive, Example: C:\SevenPrep
-Double click SevenPrep.bat
-Follow the prompt. This will basically install GingerBreak and System Recovery
-After the prompt closes, execute GingerBreak from your appdrawer and hit "Root".
-The phone will reboot. After the phone reboots, execute "System Recovery" from your appdrawer and hit "Install Recovery"
-You will get a SuperUser prompt, asking you to either Allow or Deny this application access to your phone. Hit “Allow”
-After a few seconds it will say “Install complete”
Your phone is now Rooted and Recovery has been installed - Stop here if you are interested in keeping your phone on STOCK and are not interested in flashing the Ginger/Grey ROMS. If you wish to de-odex stock 2.1.1 read below, if you do not know what this is, skip it.
DE-ODEXING (OPTIONAL)
If you are interested in theming stock 2.1.1 or installing language packs such as arabic, you will need a De-Odexed ROM. In order to do so I've created a little tool that will get you going.
REQUIREMENTS:
Make sure you have downloaded Seven's Deodex Tool 2.0.
>>Please be aware this tool is ONLY for 2.1.1. Using it otherwise WILL brick your phone.<<
-Make sure USB Debugging is enabled. Plug in your phone (if not already plugged)
-Extract SevenDeodex2.zip to your C:\ drive, Example: C:\SevenDeodex2
-Double click SevensDeodex.v2.0
-Follow the prompt. This will basically install the deodexed system files and give you instructions on what to do next.
-DO NOT CLOSE THE CMD PROMPT.
-After all the files have been copied, simply follow the instructions listed in the BAT file.
If you read the prompt carefully you will see it instructs you do the following the following:
-Open up ADB Shell and type the following commands in this order, one by one:
su
cd /data/local/tmp
chmod 755 install_script.sh
./install_script.sh
Simple! It will take a minute to finish. Once it is done your phone will reboot and you will be de-odexed!
Step 3: Preparing and Flashing GreyBlur/GingerBlur
>> IF YOU HAVE A LAPDOCK READ HERE!! << - >> If not skip this portion and move to: How to Flash GreyBlur!
It just so happens that if you simply flash over 2.1.1 the default keyboard layout for the Lapdock will be stored as AZERTY and your special characters will not function properly. This is mainly because by default the hardware keyboard layout is set to France.
BEFORE flashing GingerBlur/GreyBlur you MUST follow these steps to ensure that the selected Keyboard layout matches your current Lapdock SKU.
You must do the following:
-Dock your Phone with Stock 2.1.1 on your Lapdock.
-Wait for Webtop Environment to properly initialize.
-Once the Webtop has booted, go to the upper right hand corner and click the COG. This will open up a menu.
-Select Keyboard
-Click on the "Test settings box" and type freely using your Lapdock keyboard. As you will notice it will not type what you keyboard layout is unless you have the French lapdock.
-Click the Keyboard Language... button
-This will boot you into Settings->Language & Keyboard Settings
-Scroll to the bottom and you will see two boxes that will allow you select which Keyboard layout you wish to choose.
-Set BOTH of them to English US (if this is your keyboard layout, this applies to Canada, US). If you have a different layout, choose it from here!
-You will notice it will NOT let you set the bottom one untill you unplug your phone and replug it. Follow the instructions!
-Once you have successfully changed these settings go back to the "Test settings box" and type freely using your Lapdock keyboard.
Now it will properly reflect your current layout and these settings will be saved! Move on to the next section below.
How to Flash GreyBlur!
REQUIREMENTS: AC Power Adapter – keep this plugged in until you finally boot GreyBLur.
-Having downloaded either GreyBlur or GingerBlur, copy one of these files the root of your INTERNAL SD card.
-Make sure Recovery has been installed (if you followed the guide above you are ready to go!)
-Once Recovery has been installed, open the program and plug your phone to the AC power.
-Select “Recovery Mode” -> You will receive another SuperUser Prompt. Select ALLOW.
-The phone will now reboot and enter Clockwork Recovery.
NOTE: If at this point you could not enter recovery, it is because you are NOT plugged into AC power. It will NOT work on USB power as this is a security measure so that we can access Clockwork Recovery when our phone is not booting into Android OS.
-Once in Recovery, use the VOLUME UP and DOWN keys to navigate.
-Navigate down to the option “Install zip from SDCARD”, Press the power button to enter that submenu.
-Once in this new menu select: “Choose zip from internal SD Card”
-Select the zip file you copied in the steps above. Example: GreyBlur-2-1.zip
-Once you have selected this zip file, scroll down and select YES.
-The installer will run and once it is finished it will say “Install from sdcard complete”
-Select “+++++Go Back+++++”
-Once at this menu select: “Wipe DATA/Factory Reset”
-Select “Yes”
-It will take a few seconds until this is complete and you will see a message that says “Data Wipe Complete”
You are now ready to start your phone!
-Unplug your phone from the AC power
-Select “Reboot System Now”
You will now see how the GingerBlur/GreyBlur logo as your phone boots up shortly after the Red M “Dual Core” Logo.
-After the boot finished, ALWAYS ALWAYS ALWAYS select “Set-Up”
NOTE: >>SKIPPING THIS MAY CAUSE ISSUES SO DO NOT SKIP IT. SWYPE WILL CRASH. <- This is normal until we apply a fix! <<
-Complete the MotoBlur setup. (In this case, NEVER SKIP THIS….!!!!!!!!)
-Register or log into motoblur blah blah blah you’re done!
-As you are finishing it will prompt you to update your phone. DO NOT UPDATE!!! Just select later….
-Add any needed APNs to enable DATA on your phone. If you don’t know how to do this read the FAQ at the end of this post.
-You will also see a POWER icon on your upper left hand corner. Open the notification bar, click the notification and select the correct profile for you. I use PERFORMANCE MODE.
You now have successfully Flashed GreyBLUR on your phone but this is NOT all that is needed.
Read below.
Step 4: Apply BlurFix Patches to fix compatibility issues with GreyBlur/GingerBlur and enable performance tweaks!
This patch will fix update notification NAGS, remove Swype and also will enable 1080p Video recording as well as enable performance tweaks!
READ FAQ for more information.
Noob HELP – Skip this section if you are experienced with ADB and debugging mode.
-Pull down the Notification bar up top and select “USB Connection”
-In this prompt select “None” and press OK
-The phone will reconnect to the computer with USB.
-Debugging mode will now be enabled.
If it does not:
-Unplug the phone and reboot
-After the phone boots up, plug the phone to the computer.
Patching:
-Having downloaded Seven’s Blurfix Patch from the Required Downloads above, extract this file to your C:\ drive. Example: C:\SevenBlurpatch
-Open SevenBlurpatch folder
-Run “Seven's Blurfix”
-Follow the steps prompted in the CMD window.
-After the script files have been copied over it will ask you to press any key to continue.
-It will leave you with an open ADB Shell, displaying the “$” symbol.
Type in the following commands in this order:
su
At this point, MAKE SURE YOUR PHONE’s SCREEN IS ON. PAY ATTENTION as it will prompt you to ALLOW or DENY. Select ALLOW on your phone or this will FAIL. If it fails run Seven’s Blurfix again.
The $ sign will change to a # sign.
This means you have Root access through the terminal window. Now we will manually execute the script.
Type the following command at the # prompt:
./data/local/tmp/blurfix_script.sh
After this the phone will reboot and then you are READY TO GO! Read Step 5 for APN information and FAQ!
No more ATT update nags, no more issues and 1080p recording enabled! Performance tweaks enabled, tethering re-enabled. Read the FAQ Section on how to record in 1080p!
STEP 5 - APN Information and FAQ
Here is the correct APN information for all pertinent carriers. I was unable to find the Korean APN information so if someone will PM me this, I will gladly add it!
It can be found -> Here
This is how you add APN settings:
-Press the Menu key
-Go to Settings
-Go to Wireless controls
-Go to Mobile networks
-Go to Access Point Names
-Press the Menu key
-Select New APN
-Add pertinent information
Depending on what carrier you use, these are the settings:
You might need to add 2 APNs for your specific carrier.
Whatever is does not have settings, leave blank.
After you have added your APN information make sure you ENABLE the little RADIO icon.. its the circular icon, that is usually empty after adding APN information.
Frequently Asked Questions!
Q) What's so special about 2.1.1 vs Stock or 1.4.2
A) A lot of things! Some of the most noticeable improvements are the boot time when using stock 2.1.1. It is FAST and the display is much more responsive than stock Bell Motoblur. Also MotoBlur is much more responsive in loading and switching between screens, even the stock keyboard is an improvement in terms of feedback and usability. Stock 2.1.1 no longer lags when typing. The fingerprint reader has improved significantly as well in comparison to previous SBF. Quadrant scores also went up for me in comparison to 1.4.2 GreyBlur. There is a lot of feedback regarding this but all of it has been GOOD.
Q) Should I stay on 2.1.1 STOCK or should I flash GreyBlur/GingerBlur?
A) Stock is actually quite decent, for Canadian Fido users there is a HUGE improvement as the carrier name is actually correct now and does not take 50% of the notification bar. None the less, GreyBlur runs beautifully and even faster on this SBF! Its quite impressive in boot time, smoothness and the loss of all the bloatware is quite good. It also provides theming support for us International users, so that we may use 1.5.7/1.8.3 framework themes!
Q) 1080p recording?!
A) Yes.. By running Seven's Blurfix Patch, LGCamera Free is installed. This as well as an internal mod allows 1080p recording on the phone! There are however special settings to get it to work.
Instructions:
-Start LGCamera
-Press the Back key to get rid of the purchase nag or buy the full version!
-Select the Video option to switch Video recording
-Press the menu key to open the options menu
-In the options menu scroll down to Video settings and set the following settings. (This is the only way 1080p will work!)
Video Resolution: 1920 x 1080 (1080p)
Encoder: Default
File Format: MPEG4
Video Bitrate 13 Mbit
Hit the red button and you're good to go!
Q) What is HSUPA?
A) High-Speed Uplink Packet Access (HSUPA) is a 3G mobile telephony protocol in the HSPA family with up-link speeds up to 5.76 Mbit/s. By default both the ATT and Bell ROMS have this disabled and therefore features like Voice over IP, skype, videochat are almost unusable. By enabling HSUPA this allows you to use these and also benefit from faster uplink access therefore speeding up you're mobile internet.
Q) Why is GingerBlur 3.1 not recommended.
A) It has been shown in various threads and people's reports (in my original thread) that 3.1 has various glitches and issues. Non functional Home button (when skipping motoblur setup), wifi issues (although most of them resolved now) as well as terrible battery life. GreyBlur on the other hand has proven to work PERFECTLY and is a better platform to have custom framework modded ontop of it. Use all both of these at your own risk!
Q) Why is Swype removed by applying BlurFix Patch?
A) Because there are issues with it. I'm also not allowed to post information or files related to swype on how to fix it. The alternative is to install the updated beta which can be found here in the DEV section. Much better fix/alternative.
Q) I want my Launcher to be smoother! How?
A) Use LauncherPro. It is by far the smoothest. A good alternative is GoLaucher Ex which is also great.
Q) I did not get the Power Icon that you mentioned in your guide.. what did I do wrong?
A) This is a feature of the Atrix called Power Management. It can be accessed at: Settings->Battery Manager -> Battery Mode. There you can select whatever profile you want!
Q) I want to flash other themes! What do I do?!
A) Feel free to flash any theme that is for ATT framework ONLY.. As long as you have GreyBlur installed this will work. Try to flash themes for 1.5.2 and 1.8.x ATT. Previous ones are unknown and unsupported.
Q) I flashed a theme and now, my phone wont boot!!! what do I do? Do I have start over again?
A) No you dont! First if this happened, you have to Factory Reset. (That sucks.. But its the price we have to pay to get this functioning)
Follow this short guide below: How to access Android Recovery
-On your first reboot after flashing a new theme, hold VOL down as the phone powers on.
-Then use power down again to select Android Recovery
-Once selected, press Power button ONCE, then VOL UP
-Tap lower right hand corner of screen if you have no buttons
-Select Wipe data/factory reset using volume buttons
-Triple tap (or more) on the lower left hand corner of the screen to select OK
-Using the same method, reboot the phone using that option in the menu!
-The phone should boot.
Should the phone not boot, it means you flashed something unsupported so back to square one!
Q) My Lapdock Keyboard is all messed up!! What do I do?
A) Unfortunately you did not read the section above (STEP 3) which specifically states what should be done in preparation to flash so that your Lapdock Keyboard functions properly. I am attempting to create a hotfix patch for this to avoid people having to reflash but at the moment there is no other way.
Q) I wish to DeOdex Stock 2.1.1 so that I may theme my phone without using GingerBlur/GreyBlur or to install Arabic Language pack. What do I do?
A) Read STEP 2, after ROOT and RECOVER there is a section now, which contains instructions on how to use the 2.1.1 DeOdex tool I've created.
Q) I'm having connectivty issues with DATA and VOICE.. what do I do?
A) Flash this radio -> HERE. This generally solves issues with connectivity.
If you have any more questions please let me know!
thanks, but why do you say gingerblur 3.1 is not recommended?
running it on 1.4.2 and don't have any issues... just wondering before I update to 2.1.1
scorneil said:
thanks, but why do you say gingerblur 3.1 is not recommended?
running it on 1.4.2 and don't have any issues... just wondering before I update to 2.1.1
Click to expand...
Click to collapse
This info will be added to the FAQ section but just be aware 3.1 drains battery like hell. Don't mind people saying that resetting stats will fix it but a lot of people have reported issues with that. (I suspect it has something to do with Gallery3D version which is a known drain)
2.1 on the other hand has much snappier performance and the battery life is just a lot better.
Also people using phones from other regions, international regions have reported issues with it if you read the thread.
Well done guides!
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
seven2099 said:
This info will be added to the FAQ section but just be aware 3.1 drains battery like hell. Don't mind people saying that resetting stats will fix it but a lot of people have reported issues with that. (I suspect it has something to do with Gallery3D version which is a known drain)
2.1 on the other hand has much snappier performance and the battery life is just a lot better.
Also people using phones from other regions, international regions have reported issues with it if you read the thread.
Click to expand...
Click to collapse
ya, i did have the battery issue but it's much improved (in my case anyway) with a battery calibration.
Battery drain or not that Gallery3D is horrible.
thanks for the info
scorneil said:
ya, i did have the battery issue but it's much improved (in my case anyway) with a battery calibration.
Battery drain or not that Gallery3D is horrible.
thanks for the info
Click to expand...
Click to collapse
No problem! Thanks for the feedback. Make sure you read the section on the BlurFix Patch I've created. This will disable the OTA nags and add a few goodies!
Enjoy SIR!
Question about the 1080p recording - is this sufficient for a daily driver? I don't use my camera a ton but when I do, it's normally extremely critical. And because we have another camera app included (which has the options to allow 1080p after we've applied the appropriate mod) is it safe to assume that the native camera app is the same?
I guess what I'm asking is if the normal camera app stays as is, where as the LGFree camera app is able to use the mod?
Thanks for all your hard work, man. And thanks so much for giving us Bell Atrix users MUCH more than just a glimmer of hope. I'm floored at how well the new SBF file is. Holy ****!!! Now I can't even begin to imagine how much opportunity there is once we start looking at Gingerbread and future framework. Never knew how much of an improvement we'd see without even unlocking the full capabilities and dual core processor.
Ok so what exactly is fixed in this sbf? Telstra fixed the hsupa... what does this fix?
edit: nevermind...
Sent from my Motorola Olympus
bongd said:
I guess what I'm asking is if the normal camera app stays as is, where as the LGFree camera app is able to use the mod?
Click to expand...
Click to collapse
The regular app does not support 1080p yet. This is simply because there was probably no budget left when developing this to enable it (although simple enough, would probably require a lot tweaking on their part to get the best out of the camera)
As for LGCamera, the Free version or paid version can both produce MUCH better image quality than the Stock camera. I will add some more information to the FAQ as to how to improve image quality using LGCamera.
Cheers! and Glad you like it! I do agree, it is AMAZING.
ChongoDroid said:
Ok so what exactly is fixed in this sbf? Telstra fixed the hsupa... what does this fix?
Sent from my Motorola Olympus
Click to expand...
Click to collapse
Read the guide and user feedback.
Hi seven,
First of all, thanks for the hard working!!!
Everything is fine, except that I didn't get the power icon after flashing greyblur. What program is that?
Also, how can I get gingerbread theme on greyblur?
Cheer!
Thiago
Beat me to the edit haha... All right well I guess I'll have to flash this at my friends windows machine.
Sent from my Motorola Olympus
seven2099 said:
The regular app does not support 1080p yet. This is simply because there was probably no budget left when developing this to enable it (although simple enough, would probably require a lot tweaking on their part to get the best out of the camera)
As for LGCamera, the Free version or paid version can both produce MUCH better image quality than the Stock camera. I will add some more information to the FAQ as to how to improve image quality using LGCamera.
Cheers! and Glad you like it! I do agree, it is AMAZING.
Click to expand...
Click to collapse
You are a machine, brother!
Thanks for helping us increase the user experience with this phone 10-fold! Only ****ty thing is that a few people at my work place are getting Atrix's and now they want me to put these amazing mods on their phones too.. sheesh. Look what you've done!
bongd said:
You are a machine, brother!
Thanks for helping us increase the user experience with this phone 10-fold! Only ****ty thing is that a few people at my work place are getting Atrix's and now they want me to put these amazing mods on their phones too.. sheesh. Look what you've done!
Click to expand...
Click to collapse
LOL hahahahaha
No worries dude! I do what I can because I LOVE this phone.
tsouza said:
Everything is fine, except that I didn't get the power icon after flashing greyblur. What program is that?
Click to expand...
Click to collapse
Glad you enjoy the effort! The power icon can be accessed under:
Settings-> Battery Manager -> Battery Mode.
There you can select what you want!
tsouza said:
Also, how can I get gingerbread theme on greyblur?
Click to expand...
Click to collapse
Yes you can get Gingerbread theme. Check the Themes and Apps section! you can find plenty that work on ATT framework! After you flash though and if your phone does not boot, make sure you simply do Factory Reset (I know this sucks terribly.. but its the price we pay to get this functional!)
I want to write this post to speak about my experience with l7 of my girlfriend. In this moment her l7 is fast and nice.
What I did?
Install v20a by homero: http://forum.xda-developers.com/showthread.php?t=2214717
Make format (restore settings) by setting of the phone
Wait that phone reboot and set correct language and make first access
Go in to cwm recovery (with android terminal emulator write: su , click enter, write reboot recovery , click enter) and make wipe data, wipe cache and advanced-wipe dalvik cache
If initial android settings appears again (because "wipe data") choose correct language and make first access
Now install 20b rooted http://forum.xda-developers.com/showthread.php?t=2239786 (I install 20a before because it has more language; but if you update 20b over 20a you don't lose choosed language also if it isn't present in 20b)
Install root explorer to make some changes
From system/app delete browser (I suggest to install dolphin mini e set desktop mode user agent) ,youtube (you can install from play store and don't have in system) and weather (I use beautiful widget) ; if you have maps, gmail, polaris office, delete them and download and install from play store (or you can copy and paste them in sdcard, delete from system and reinstall); I use quickpic as gallery and mx player as video player
From notification bar you can edit and unflag in QSlide options "Calendar" because doesn't work; for browser(deleted before) is not a problem, because after reboot it will not appear more
I install seeder 1.4 to reduce lag: http://forum.xda-developers.com/showthread.php?t=2237776 , open, enable rng and set "start automatically on boot"
I install v6 supercharger in this manner: download this http://www.mediafire.com/?8ei5qbzy5s0bp68, unzip and copy in sdcard.
From android terminal emulator digit su , click enter, digit sh sdcard/SuperCharger_Starter_Kit/StartMeUp.sh , click enter. Choose YES to different options.
After download http://www.mediafire.com/?sdytjb056bje98a , install lg drivers if you don't have, choose debugUsb from developer options, connect phone in "charge only" mode. Start downloaded exe file from your pc and press enter when it asks; when it ask about "adb", choose "No".Follow steps (choose die(D) for kernel mode if it ask, 1 for scrolling if it ask) and click YES to others;when a superSU popup will appear in your phone, click OK (phone will restart); go until ask about multitask mod (choose No, so process will end).
Copy this in sdcard http://www.mediafire.com/view/?ngomnmpbs3ya9ol and from android terminal emulator write su ,click enter, write sh sdcard/99SuperCharger.sh , click enter.
Will start superchanger configuration; choose "YEs" to different option (1 for scrolling if it ask, die(D) for kernel mode if it ask);when you can choose option from 1-33 choose 5. After finish, close terminal emulator.
With script manager (browser as root if it ask) go in data/99SuperCharger.sh and press su, boot and save
Install kickasskernelizer: http://www.mediafire.com/view/?4zf6hbko51gf8nh .As v6 supercharger, copy in sdcard, from terminal emulator write su , press enter, write sh sdcard/S98KickAssKernelizer.sh , press enter.
Choose K (kernelizer) and choose yes for IO scheduler tweeks. With script manager (browser as root if it ask) go in data/S98KickAssKernelizer.sh and press su, boot and save
Enable hardware acceleration: http://forum.xda-developers.com/showthread.php?t=2231523
Install rambooster and for the first time open and make boost now (will appear on the top a red icon, so when you want free ram you tap there)
Reboot phone and wait scanning of storage
Yout phone will be fast and updated
simply.. install cm10 with oc kernel and seeder
That is it
CM10 has working camera? All hardware working fine? thanks
how ever someone can prefer "LG style" over CM10 UI, like my girlfrind
CM10 camera is working great on my L7. The only thing is that it saves the pictures in the internal memory, and I cannot configure it to save on SD card.
No hardware problem, but if you are on V20 you need to flash V10 bootloader to make radio and wifi work. Did that and works great.
The only issue with CM10 seems to be the random reboot. Some say it no longer occurs with V6 supercharger's hard rock kernel. Had mine supercharged 50% and still occurs. Since yesterday it's 100% supercharged and haven't got any reboots but to be fair the phone was not used too much, just a couple of phone calls and some facebook.
In cm10 you can't configure storage of camera
You can't run radio tm
You can't play all vedio extensions
You can't record at background
Sent from my LG-P700 using xda premium
Have you successfully run the fm radio m
Sent from my LG-P700 using xda app-developers app
mine worked smoothly with V6 and crossbreader, even in the crappy carrier rom (is the only one for p708g )
fenomeno83 said:
I want to write this post to speak about my experience with l7 of my girlfriend. In this moment her l7 is fast and nice.
What I did?
Install v20a by homero: http://forum.xda-developers.com/showthread.php?t=2214717
Make format (restore settings) by setting of the phone
Wait that phone reboot and set correct language and make first access
Go in to cwm recovery (with android terminal emulator write: su , click enter, write reboot recovery , click enter) and make wipe data, wipe cache and advanced-wipe dalvik cache
If initial android settings appears again (because "wipe data") choose correct language and make first access
Now install 20b rooted http://forum.xda-developers.com/showthread.php?t=2239786 (I install 20a before because it has more language; but if you update 20b over 20a you don't lose choosed language also if it isn't present in 20b)
Install root explorer to make some changes
From system/app delete browser (I suggest to install dolphin mini e set desktop mode user agent) ,youtube (you can install from play store and don't have in system) and weather (I use beautiful widget) ; if you have maps, gmail, polaris office, delete them and download and install from play store (or you can copy and paste them in sdcard, delete from system and reinstall); I use quickpic as gallery and mx player as video player
From notification bar you can edit and unflag in QSlide options "Calendar" because doesn't work; for browser(deleted before) is not a problem, because after reboot it will not appear more
I install seeder 1.4 to reduce lag: http://forum.xda-developers.com/showthread.php?t=2237776 , open, enable rng and set "start automatically on boot"
I install v6 supercharger in this manner: download this http://www.mediafire.com/?8ei5qbzy5s0bp68, unzip and copy in sdcard.
From android terminal emulator digit su , click enter, digit sh sdcard/SuperCharger_Starter_Kit/StartMeUp.sh , click enter. Choose YES to different options.
After download http://www.mediafire.com/?sdytjb056bje98a , install lg drivers if you don't have, choose debugUsb from developer options, connect phone in "charge only" mode. Start downloaded exe file from your pc and press enter when it asks; when it ask about "adb", choose "No".Follow steps (choose die(D) for kernel mode if it ask, 1 for scrolling if it ask) and click YES to others;when a superSU popup will appear in your phone, click OK (phone will restart); go until ask about multitask mod (choose No, so process will end).
Copy this in sdcard http://www.mediafire.com/view/?ngomnmpbs3ya9ol and from android terminal emulator write su ,click enter, write sh sdcard/99SuperCharger.sh , click enter.
Will start superchanger configuration; choose "YEs" to different option (1 for scrolling if it ask, die(D) for kernel mode if it ask);when you can choose option from 1-33 choose 5. After finish, close terminal emulator.
With script manager (browser as root if it ask) go in data/99SuperCharger.sh and press su, boot and save
Install kickasskernelizer: http://www.mediafire.com/view/?4zf6hbko51gf8nh .As v6 supercharger, copy in sdcard, from terminal emulator write su , press enter, write sh sdcard/S98KickAssKernelizer.sh , press enter.
Choose K (kernelizer) and choose yes for IO scheduler tweeks. With script manager (browser as root if it ask) go in data/S98KickAssKernelizer.sh and press su, boot and save
Enable hardware acceleration: http://forum.xda-developers.com/showthread.php?t=2231523
Install rambooster and for the first time open and make boost now (will appear on the top a red icon, so when you want free ram you tap there)
Reboot phone and wait scanning of storage
Yout phone will be fast and updated
Click to expand...
Click to collapse
Sir, whenever I enter the 'digit su' it would always say '/system/bin/sh: digit: not found'
How can I fix this? Please Help. Thanks.
cloud26 said:
Sir, whenever I enter the 'digit su' it would always say '/system/bin/sh: digit: not found'
How can I fix this? Please Help. Thanks.
Click to expand...
Click to collapse
Just type "su"..
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??
Hello everyone,
Some Italian guys asked me for this guide because they did not find anything complete and detailed. Thanks to the XDA members' publications I could put together the pieces and write it down. I apologize for my English but I'm not very good, especially for technical terms. I hope I can help someone.
BACK TO ANDROID WEAR 1.5 FROM 2.0(COMPLETE GUIDE)
1. Download the software ADB installer 1.4.3 from this link compatible with Windows 10: http://uploadboy.com/tsp1bpbe9gtj/1082/zip
From here you can download an older version 1.3 for Windows 7: https://forum.xda-developers.com/showthread.php?t=2588979
2. Open the .exe file already downloaded with administrator privileges and follow the installation procedure to install the drivers
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
4. Insert the files into the folder that created the ADB Installer that is normally the path "c:\adb"
5. Download tool "WinDroid Toolkit" from here (some antivirus swapping it for threat and eliminating it, in this case turn it off momentarily) :
https://forum.xda-developers.com/devdb/project/dl/?id=17244
6. Start with administrator privileges "WinDroid Toolkit"
7. Follow the instructions for installing the drivers required by the tool and select the model of the clock
8. Activate developer options on the clock: (Settings> System) by clicking "build number" repeatedly until unlocking the menu that will be among the main options
9. In the developer options menu, activate the "debug ADB"
10. Turn off the clock
11. With the clock off, hold down the physical key and in the meantime repeatedly tap your finger on the screen from minute 55 to 25 until the watch has entered the mode fastboot
12. Connect the clock to PC usb port via cable and charging base
13. Now "WinDroid Tool" should recognize the clock and below you will see that the "Offline" script becomes "Fatboot"
14. Click on "Unlock Bootloader" and proceed by accepting the various message from the tool
15. A confirmation message appears on the clock display, click on the right arrow and then on the central button to continue
Now the bootloader of the clock is unlocked and we can continue to install the three previously downloaded files. Close "Windroid Tool"
16. In the "adb" folder at the "c:\adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
17. In the newly opened window, give the following commands one at a time and wait for each one to complete the operation:
1) fastboot -w
2) fastboot flash boot M1D65H_boot.img
3) fastboot flash recovery M1D65H_recovery.img
4) fastboot flash system M1D65H_system.img
Finally, to restart the clock, use the following command:
5) fastboot reboot
N.B. Before pairing the watch on the cellphone again remove the link, inside the Android wear app, clock and uninstall and reinstall the app.
Finished!
ELIMINATE THE PERSISTENT UPDATE NOTIFICATION
1. Download the .zip file containing the custom recovery and root to this address:
http://www.mediafire.com/file/qllnc7...+R+Utility.zip
2. Unzip the .zip file and insert the "twrp-3.0.0-0-lenok+squashfs.img" file into the "c:\adb" folder
3. In the Clock Developer Options menu, activate the "Debug ADB" (to enable them to follow the procedure above)
4. Connect the clock to the pc via the cable and charging base
5. Open "WinDroid Tool", go to the "Commands" tab and click on "push file". Select the file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete and disconnect the clock from the PC.
6. Turn off the clock
7. With the clock off, hold down the physical key and in the meantime crawl your finger repeatedly on the screen from minute 55 to minute 25 until the clock has entered fastboot mode
8. Connect the clock to the pc
9. In the "adb" folder at the "c: \ adb" path, click on a drop-down menu at any point in the chain and right-click and shift at the same time. Click on "Open command window here"
10. In the window just open, give the following command and wait for the completion:
-) fastboot flash recovery twrp-3.0.0-0-lenok+squashfs.img
11. From the clock using the arrows and the confirmation button down to start the "recovery mode"
12. Accept the warning message and after selecting the language click on "install" and select, with the touchscreen, the .zip file "SR1-SuperSU-v2.78-SR1-20160915123031.zip", wait for the procedure to complete.
13. Restart the system and wait for the clock to turn on.
14. In the previously opened command window, give the following commands one at a time and wait for them to complete and complete:
1) adb shell
2) su
3) pm disable com.google.android.gms/.update.SystemUpdateService
4) pm disable com.google.android.gsf/.update.SystemUpdateService
Finished!
Many thanks riccardo423
I have managed to rollback my lg g watch r to android wear 1.5 AND suppress those pesky update notifications using your guide. I noticed your mediafire link to the custom recovery file is broken. There is an alternative download at http://www.mediafire.com/file/qllnc77jtdqxtdl/Lg+Watch+R+Utility.zip (posted by Dettofatto in a previous xda thread) which also contains the two additional required files.
Luigino1
Hello, thanks for inserting a working link. I've modified the text of the guide by entering your link. I'm glad to have helped you.
Riccardo423
For step 3 if I click the link it says the post does not exist. Anyway here's where I found the images if anyone needs it: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
BTW: Thank you for the complete guide, step by step, i was able to go back to 1.5 and disable the persistent notification thank you very much!
Hi, thank you for inserting the working link. I'm glad to have helped you. Riccardo423
After downgrade from 2.0 to 1.5, I don't received Facebook messenger notifications on watch. Other notifications work fine (Gmail, sms etc). Anyone know what's going on?
Hi I have never had this problem I think I can depend on your Facebook app. Which version of Facebook and which cell phone?
Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates
szczurx said:
Latest version of Facebook app from Google store. Phone - Samsung Galaxy S6 with Latest Marshmallow updates
Click to expand...
Click to collapse
You've already tried uninstalling and reinstalling the app?
The app wear permissions are unlocked for notifications?
Android wear app reinstalled twice. Even made watch factory reset. On Phone in settings/apps, Android Wear app have permissions for everything possible
Thanks for this Riccardo ( or grazie, from a fellow italian )!
Can't believe I managed to do the entire procedure without making a mess of it, lol. Everything appears to be working again, I'm so happy! Really hated AW 2.0. Hope the notification does not come back, I'll keep an eye out for it in the coming days.
hello, can anyone answer me why these commands dont work
pm disable com.google.android.gsf/.update.SystemUpdateService
and why superSu crashes on watch
Thank you Riccardo423 for great manual, it works great for my watch. No AW2 anymore!
riccardo423 said:
3. Download the three image files of the build "M1D65H" (boot, recovery, system) that you find here: https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
charging base
Click to expand...
Click to collapse
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?
LionheartSilver said:
Noob question: why the "M1D65H" versión? Is the last with AW 1.5? The NXG47C version is for 2.0?
Click to expand...
Click to collapse
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.
pidobeuliou said:
Yes, it's the last AW1.5 version. However, perhaps it was due to something I didn't made correctly during the downgrade but this M1D65H version had not a good battery performance on my watch (battery was drained in less than 40 hours).
It's why I have used the M1D64Y version which is perfect in terme of battery performance (>48 hours) and applications responsiveness.
Click to expand...
Click to collapse
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?
LionheartSilver said:
Really? ... hmmm i see.... mine has always lasted less than 40 hrs... did you install any mod for the watch? core enablers or smth?
Click to expand...
Click to collapse
Nothing specific, just installed the basic factory image + root . I have installed about 16 apps (including Watchmaker with a quite "sophisticated" watchface, wear messenger, WearMail, Wear Battery stats, Feel the Wear, Runtastic, ...) but mainly I have deactivated Google Fit which is a true battery killer app on both the Smartwatch and the Smartphone!.
mediafire link is dead (twrp) - please, reupload it!
Thanks so much for this, it worked perfectly! So great to have my watch back!
Hi, I have problem connecting in ADB mode to PC - when I plug in craddle nothing is happening Win10 not even play a sound, not trying to find drivers etc. Is it connected with new version NXG47C/LENOKZ22b ??
In fastboot mode there is green "secure boot" enabled, lock state - locked and bootloader in Z22b version. Is it possible to connect ADB in this case? Im stucked witn AW2 and there is nothing I can do for now Please help.