Related
Most of you are stuck on a yellow screen with”Emergency mode!!” or the phone is not responding at all. You guys wanted a custom rom like Optimus Prime-v2 and let me tell you, this time it will work. Optimus One P500 comes with stock android 2.2 – V10a, V10b … and android 2.2.1 – V10n. They might be done for different regions depending upon the phone release and its popularity and definitely bug fixes and enhancements. To have Prime-v2 on your handset you will require V10a or V10b on your handset. Reason, V10n stock cannot be rooted easily. Rooting the handset is must if Prime-v2 is required on the device. Steps to install V10a, V10b series. I am using Windows 7 32-bit, 3 GB RAM laptop:
1. Clean your system first; get rid of LG PC suite and other stuff shown in Uninstall Program with vendor name as LG. Remove MSXML builts from the handset. Remove Nokia and other drivers if they are on system like Ovi suite etc. I also removed a lot of Microsoft runtime environments. Not sure about the reason but it worked for me.
2. LG usb device drivers, download the application B2CAppSetup.exe http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe .
3. In the Menu Bar, click "Options & Help", and click "Country & Language". Select the appropriate Country & Language. I used India and select P500 from the list that popup after you change the country and region. It will download, install and save the drivers somewhere in C:\LGP500\USB_Driver, it will prompt to open the rar files, just click and install the exes seen in them.
4. Reboot the system.
5. Right click on Computer -> Properties -> Device Manager and see for three drivers – LG android usb modem, LGE serial usb port and LG composite USB device. Disable the modem driver and reboot once again.
6. Switch off the phone and press volume up + BACK button + POWER button. Phone should turn yellow with text “Emergency Mode!!” To switch it off you have to remove the battery (I know it hurts, but that’s the only way out here). Switch off and let’s continue with the setup.
7. To do the KDZ of system you will require the KDZ software updater, links keep going off and on internet. Try searching for “KDZ_FW_UPD_EN” or “KDZ_FW_UPD_EN.7z” in Google and download the software. It should be somewhere around 2.3 MB. To use it you will required some good version of WinZip or winrar again Google it and install the 7z archive utility.
8. Install msxml.msi as the manual or readme.txt says to do so.
9. To get the V10x Official ROM, you need to first determine the ROM of your choice. List of all firmware available for LG Optimus One P500 (list of codes) http://csmg.lgmobile.com:9002/csmg/b2c/client/ezlooks_model_list.jsp?model=LGP500 , search for your country (use IE it looks sexy in it), I looked out for IND/INDIA. Download link to the ROM is http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/XXXXX/V10a_00/V10A_00.kdz where XXXX is code from list of codes. In my case it was: AINDBK. Save the file.
10. Prepare the handset by removing the SD card and boot it to emergency mode (some are already stuck on it so reading this post…: D) using the key combination stated above.
11. Connect to the PC and it should say, installing drivers’ blah… blah … your device is ready to use now.
12. Run the KDZ updater downloaded in step 7. Select 3GQCT in Type, DIAG in PhoneMode, and browse for ROM V10a in KDZ file and hit Launch Software update. Wait for somewhere around 5-10 minutes. It should say ===FINISHED=== in the log window of updater.
13. Handset will reboot, if not wait for another 5 minutes. Unplug from USB and try to switch it on.
If you guys wants help with details on setting up the custom ROM, I mean more detailed information like above let me know. I will try to help you out.
What's about some kind of merge...
http://forum.xda-developers.com/showthread.php?p=10006406#post10006406
Yes, I think we should + I am thinking of doing detailed notes on How to Root and do the custom rom with proper steps for newbies.
Tell me what you need from me... my post is also not having stuff in bold/italics and proper links.
"[HowTo] Newbie guide to recover a dead P500"
I think if the phone can start in emergency mode is not completely dead. Here people have the realy dead phone http://forum.xda-developers.com/showthread.php?t=878286
This is very similar thread.
I sugest you to merge your thoughts with The_ERROR that has already this one:
http://forum.xda-developers.com/showthread.php?t=883314
Thread closed!
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!)
HP TouchPad Battery Drain issues during sleep (Important):
New Video and methods for flashing the A6 Firmware with the TPtoolbox (Method 3)
https://www.youtube.com/watch?v=NnWH7FhaMg4
Full Guides for the TPtoolbox:
[ROM GUIDE] How to Install Android 8.1.x/7.1.2 builds on the HP TouchPad(XDA)
How to test:
To monitor your battery drain history during sleep install the free app Battery Monitor Widget:
1) Download and install the Novacom drivers below:
Download and run the Universal Novacom Installer 1.4.1 here:
Note: You will need to have Java installed to run the Universal installer, click here:
Note: You may need to reboot after installing this software.
Or
Download, extract and install the appropriate version of Novacom for your OS here or here:
Note: Under Linux the Novacom driver is installed at /opt/Palm run it from this location.
2)Place the tablet into WebOS recovery mode and run the TPtoolbox
3)Download, unzip and run the TPtoolbox
Battery Monitor Widget:
-Once installed open the app and go to history to see a log of your devices sleep history.
-To setup the Battery Calibration correctly for the HP TouchPad,
-go to BMW settings/calibration/Battery capacity/ and set it to 6300 (*f29c), 6000 (*i29c) or 5800 (*s29c) and tap OK
-Note* See the Battery p/n # on the original packaging.
-Note* after setting the calibration, users will have to allow several hours to pass before the history can be accumulated.
Or
You can also use Cool-Tools to monitor your battery drain in real time.
-Watch the instructional video Here.
A6 Firmware Threads & Info:
Battery Drain issues on HP TouchPad
How to Reflash the A6 Firmware Method 2:
https://www.youtube.com/watch?v=5lOGY94RRDs
1) Boot to WebOs and in the "Just Type" box enter the following: webos20090606 or upupdowndownleftrightleftrightbastart
-Tap the developer mode icon and slide the toggle to on, then press submit.
WARNING: Do not enter a password. Just tap submit.
-Plug the USB cable into the HP TouchPad and your PC.
2)On your PC Install Java, Novacom and the WebOSQuickInstall-4.5.0 software*
- Note* If you have already previously installed Android with Java and Novacom, then skip it.
a]Download Java:
c]Download WebOSQuickInstall-4.5.1:
3)Run the WebOSQuickInstall-4.5.1 software, note your TouchPad must be connected with the USB cable.
-Click on the Small globe icon located under the plus minus buttons.
-This will take us to a new menu where we will search “preware”
-Click the install button and the Preware app will be installed.
-You may now unplug the USB cable.
4)On the tablet while booted into WebOS navigate to downloads and select Preware.
-scroll down until you see a button appear to continue
-Search for “wterm” and install the app.
-Run wterm, and set a password to give the app Root permissions.
- You can set or change the password by looking for the wterm menu in the upper left corner and select setup.
-Click on New password and enter a simple password like ”0000”
-Confirm the password and press “Set Password” button, now hit done and exit.
-Note you can increase the font size by going to wterm preference settings.
5) Now in wterm enter one of the following commands:
PmA6Updater -f -d 0 /lib/firmware/a6_firmware.txt.00
PmA6Updater –a (Note this shorter command flashes two firmwares)
-It should take about 20-30 seconds to complete and will inform you upon completion.
-Congratulations you have now reflashed the A6 Firmware and can safely close the terminal and reboot your HP TouchPad.
Note: If you input the command and get a message saying it said can't open the A6 device, then try toggling developer mode off and on.
Additional WebOS Preware Performance Tweaks:
I would highly recommend doing the following tweaks. Read the full instructional guide in the link below:
HP TouchPad Setup Guide Part 1: Speed Up Your Tablet With Preware, Homebrew & Patches [WebOS]
Download and install the following packages from Preware:
You should see a noticeable speed improvement while using WebOS. Also a few apps to improve functionality.
Note* You will need to reboot the device after installing most of these packages:
-EOM Overlord Monitoring
-Muffle System Logging
-Remove Dropped Packet Logging
-Unset CFQ IQ Scheduler
-Unthrottle Download Manager
-Increase Touch Sensitivity and Smoothness 10
-Quiet Powerd Messages (sic)
-Faster Card Animations HYPER Version
-Advanced Rest Options
-Disk Cache Mod
-Unhide Developer Mode Icon
-Reduce Minimum Brightness
-CyBoot
-Ad Blocker OR Max Block – Do not install both.
-Private Browsing (adds an option to your browser)
Reduce Logging & Patch ‘em Up:
This patch require you to log into Skype with the "Phone and Video Calls" app.
Once there place a call to this number using the dialer type: "##5647#"
A logging window will launch, choose to "Clear Logs" first then "Change Logging Levels" and setting logging to "minimal".
Once done, exit the app – your logging levels are now changed.
If you have never used Preware you can watch this video about Flashing the HP Touchpads A6 Firmware.
You will also learn how to use the WebOSQuickInstall-4.5.0 software to install Preware.
Both of these procedures are highly recommended and can be done as part of your post apocalyptic WebOS Survival.
How to Reflash the A6 Firmware Method 3:
https://www.youtube.com/watch?v=3T2Apdc15uY
1) Boot to WebOs and in the "Just Type" box enter the following: webos20090606 or upupdowndownleftrightleftrightbastart
-Tap the developer mode icon and slide the toggle to on, then press submit.
WARNING: Do not enter a password. Just tap submit.
-Plug the USB cable into the HP TouchPad and your PC.
2)Install Java and the Novacom software*
- Note* If you have already previously installed Android with, Java and Novacom drivers, then proceed to step 3.
a]Download Java:
b]Install Novacom drivers for your OS:
Win32:
Win64:
Linux32:
Linux64:
Mac OSX:
3)Open windows explorer and go to C:\Program Files\Palm, Inc\Terminal
-Now run the Terminal.bat*
-Note* if you are using a 64 bit OS and get the Error "Windows cannot find Javaw..." you will need to copy the Javaw.eve from C:\Windows\SysWOW64 and paste it into C:\Windows\System32.
4)In the open Novaterm window, select file\connect\Ok
-Now copy and paste the following line into Novaterm and press enter*
PmA6Updater -f -d 0 /lib/firmware/a6_firmware.txt.00
-Note* Do Not! disconnect the TouchPad After starting this procedure.
-Novaterm will tell you "firmware update complete"
- In the open Novaterm window, select file\disconnect\Ok
-Congratulations you have now relfashed the A6 Firmware and can safely disconnect your HP TouchPad from the USB cable.
Note: Get the latest version of WebOS Doctor 3.0.5 Official here:
[Video+Guide] HP TouchPad Root Certificate fix for WebOS cloud services
https://www.youtube.com/watch?v=L63RiBXhQCY
How and when to Use the WebOS Doctor(Important):
https://www.youtube.com/watch?v=wFAIJiS8g4o
Q: What’s the WebOS Doctor and when should I use it?
The WebOS Doctor is a program that has two main functions for HP TouchPad users. It can either update your version of WebOS or fix problems with a damaged WebOS by completely reinstalling it. If WebOS no longer boots or apps and preware have stopped working correctly, then you will need to resinstall WebOS with the Doctor. A failed or interrupted attempt at changing the partition sizes with WebOS preware app Tailor may cause these problems. To check what version of WebOS is currently installed go to Launcher(Up Arrow)/Settings/Device Info/ Version
Note: If run the WebOS doctor after March, 15 ,2015. then you will need to bypass the WebOS activation with the instructions here
Note(Important): You MUST uninstall Android before running the WebOS doctor. Failing to remove Android before running the Doctor can result in the process becoming stuck at 8-12% and potentially bricking the device. If you are currently stuck visit the thread below for information about fixing the problem. If you’re unable to use the tablet at all follow the instructions in Jcsullins TPDebrick thread.
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(Rootzwiki)
The Official Fix your TouchPad ( 8-12% stopped, No SD, Opps reformat, $&^#[email protected]&# crap....) thread.(CM)
TPDebrick v004 - Jcsullins dedicated thread for fixing Bricked TouchPads:
Note(Important): Running the Doctor will completely wipe all personal information, applications and preware from the TouchPad. Media like music and movies will not be affected. However I would recommend backing up your important files to PC, before running the Doctor.
Note(Important): In order to install apps from the WebOS store you will need to get the Root Certificate fix for WebOS cloud services.
[Video+Guide] HP TouchPad Root Certificate fix for WebOS cloud services
How to run the WebOS Doctor:
1) Install Java
-Java must be installed in order for the TouchPad to communicate with your PC.
2) You MUST completely uninstall Android from the HP TouchPad before running the WebOS doctor. Remove Android by running the ACMEUinstaller2. Watch the following video for full uninstall instructions.
How to Uninstall Android or CyanogenMod on the HP TouchPad (All versions)
3) Download the latest 3.0.5 WebOS doctor application to your PC. If upgrading you can check your current version from WebOS by going to Launcher(Up Arrow)/Settings/Device Info/ Version.
WebOS Doctor 3.0.5 Official Link
4) Put the tablet into WebOS recovery mode by doing the following:
-In WebOS Reboot the device by going to Launcher(Up Arrow)/Settings/Device Info/ select “Reset options” choose restart.
-As soon as the screen goes dark hold down the volume up button until you enter WebOS Recovery mode. Note the large USB symbol that should be on the screen. If you miss it just reboot again and hold down the Volume up button right away. Once in WebOS recovery mode connect your USB cable to the PC.
5) Now you’re ready to run the WebOS Doctor app by clicking on the .jar file you downloaded in the previous step. Be sure that your tablet is fully charged and connected with the USB cable before starting this process. Running out of power or interrupting this process in anyway could brick your HP TouchPad. Please be careful and fully read the instructions before beginning.
-Double click the webosdoctor.jar file to launch the app
-Select your language then click next
-Accept the licence agreement, read the warning message then select next to begin the install.
-Be patient the process can take anywhere from 15min to 1hour to complete.
Is this a one time thing? Or do we have to reflash the firmware whenever we notice battery issues?
Every month or so depending on usage
Juan685 said:
Is this a one time thing? Or do we have to reflash the firmware whenever we notice battery issues?
Click to expand...
Click to collapse
The discussion over at Rootzwiki seems to indicate that it should be done every month or so depending on your usage. I turn my tablet off when I'm not using it actively so I can do it every couple months or so.
Use the battery monitor widget to check the sleep history. After you've run this procedure once it becomes very easy to repeat.
A6 Firmware Threads & Info:
Battery Drain issues on HP TouchPad
How to test:
How to monitor your battery
To monitor your battery drain history during sleep install the free app Battery Monitor Widget:
-Once installed open the app and go to history to see a log of your devices sleep history.
-To setup the Battery Calibration correctly for the HP TouchPad,
-go to BMW settings/calibration/Battery capacity/ and set it to 6300 (*f29c), 6000 (*i29c) or 5800 (*s29c) and tap OK
-Note* See the Battery p/n # on the original packaging.
Or
You can also use Cool-Tools to monitor your battery drain in real time.
-Watch the instructional video Here.
Hopefully someone figures a way to do this in Android, I don't even know my WebOS account and I've not bothered to even set it up, so webos boots to the setup wizard and I don't want to make another account. I only lose about 1% every 8 hours though anyway.
FYI, after doing the above I had to reinstall the hd fix patch. I'm on SGA's 4.2.2 rom. After reinstalling, all is good again.
theronkinator said:
Hopefully someone figures a way to do this in Android, I don't even know my WebOS account and I've not bothered to even set it up, so webos boots to the setup wizard and I don't want to make another account. I only lose about 1% every 8 hours though anyway.
Click to expand...
Click to collapse
i hope so too. especially if it is recommended to do this once a month =/
chicle_11 said:
FYI, after doing the above I had to reinstall the hd fix patch. I'm on SGA's 4.2.2 rom. After reinstalling, all is good again.
Click to expand...
Click to collapse
Thank you for the heads up, I will have to make a note about it in my CM10.1 thread.:good:
Would give a thanks right now, but apparently I've hit my limit. Thanks.
BTW, What would be the difference of just doing "PmA6Updater –a" instead of the other full command?
jacobas92 said:
Would give a thanks right now, but apparently I've hit my limit. Thanks.
BTW, What would be the difference of just doing "PmA6Updater –a" instead of the other full command?
Click to expand...
Click to collapse
I should add a little note about that. The shorter command flashes two firmwares (as seen in the video) and therefore takes a little longer but less time to type in. Once you've typed it once in the terminal you can just hit page up to bring up again for future flashing.
Just wanna say thanks again, my battery life has increased by tenfold.
Sent from my cm_tenderloin using xda premium
Got "Unable to connect to service" when I tried to connect to the touchpad on a Win7 x64. Can't resolve the problem by re-install Novacom, re-connecting touchpad, or replace the data cables.
Finally get it to work on another Win7 x64 laptop with 32-bit Java installed. Wondering whether 32-bit vs 64-bit Java would make a difference.
henry333 said:
Got "Unable to connect to service" when I tried to connect to the touchpad on a Win7 x64. Can't resolve the problem by re-install Novacom, re-connecting touchpad, or replace the data cables.
Finally get it to work on another Win7 x64 laptop with 32-bit Java installed. Wondering whether 32-bit vs 64-bit Java would make a difference.
Click to expand...
Click to collapse
I assume you were using method 1. Did you try copying the Java file, like in this note? Copy it with administrator permissions.
-Note* if you are using a 64 bit OS and get the Error "Windows cannot find Javaw..." you will need to copy the Javaw.eve from C:\Windows\SysWOW64 and paste it into C:\Windows\System32.
RolandDeschain79 said:
I assume you were using method 1. Did you try copying the Java file, like in this note? Copy it with administrator permissions.
-Note* if you are using a 64 bit OS and get the Error "Windows cannot find Javaw..." you will need to copy the Javaw.eve from C:\Windows\SysWOW64 and paste it into C:\Windows\System32.
Click to expand...
Click to collapse
Yes, I was using method 1 and copied javaw.exe on both PC. I remember doing WebOSQuickInstall stuff when I first got the touchpad and try not to install WebOS stuff if I can avoid it.
Finally, I am seeing lots of -3 and some -4 from BMW when I was content with -19. From the early A6 thread, I though that I would have to re-setup everything for the touchpad.
Thank you very very much.
Would this wipe my sd ?
having issue.while input PmA6 updater -a, it said can't open A6 device??
Does this affect everyone? I haven't had a problem with battery life since JC fixed the deep sleep in cm10
Sent from my TouchPad using Tapatalk 2
I am running CM9 and have noticed this. If you shut down the device from within android, the battery will drain... even with it shut off (not talking about sleep, but rather having the device off).
My solution. When your in CM9 or whatever android version your running, reboot the device. When it reaches the Moboot screen, toggle down and select power off. Your battery will not drain. I can leave it unplugged for weeks and it holds its charge.
More info needed
wqt0926 said:
having issue.while input PmA6 updater -a, it said can't open A6 device??
Click to expand...
Click to collapse
Which method are you using? Is WiFi connected? Did you remember to set a password for method 2? Help me, help you
Deteriorating battery health
apicia said:
I am running CM9 and have noticed this. If you shut down the device from within android, the battery will drain... even with it shut off (not talking about sleep, but rather having the device off).
My solution. When your in CM9 or whatever android version your running, reboot the device. When it reaches the Moboot screen, toggle down and select power off. Your battery will not drain. I can leave it unplugged for weeks and it holds its charge.
Click to expand...
Click to collapse
Lets see your battery monitor widget history. There should be gapps from where you have the tablet turned off and on. This could also be a symptom of your battery health deteriorating. We were just talking about these sorts of problems today.
Nevertells has another battery health thread here:
unable to find wterm in Preware, used Method 1
Just to mention this, I used to have all kinds of stuff installed in WebOS when I first got my TouchPad and then it died on my and had to use the TPDebrick process in RootzWiki to bring it back to life... anyway, I know I used to have terminal installed but I also remember having to add feeds so that I could find the terminal package.
This time around, I had only gone through the WebOS wizard because I needed to connect via USB so I could add the cminstall folder to the SD so I could reinstall Android...
Long story short, when I went into the Preware app to search for "wterm" it was nowhere to be found in available or installed packages... so I used the Method 1 and it worked just as well, the whole process took no more than 5 minutes
So, if anyone knows what feed url has to be added to Preware to find wterm it may be helpful...
Thanks for all your work guys on keeping the TP alive
PS: the only reason I flashed the A6 firmware is because yesterday I finally made the leap from CM10 to 10.1... I even dirty flashed on top of the 0418 CM10 build and have had absolutely zero issues (I just hate the dang navigation bars in the center but I like the status bar on top because I can now use CoolTool again :good:
PPS: Just want to mention also, I have read in a couple of threads that Windows 7 x64 users haven't been able to get UMS drivers to use the TP in mass storage mode in case anyone has any suggestions for that as well...
Windows 10 Windows Technical Preview is available for more than a week. Since i have an extra old 40gb hdd for the shift, i decided to give it a try, and i can say that it works perfectly well. Everything works including touchscreen, wifi, bluetooth, modem, etc.
However installing the drivers may be a little tricky. Here are the steps:
1. Download Windows Technical Preview from microsoft website (download the x86 version)
2. Extract the .iso file to a usb stick (i used power iso to do that)
3. Plug the stick to the shift and boot from it
4. Follow on screen instruction to install windows
5. When done copy the drivers for the shift (you have the download link bellow the video ) to a stick
6. First install "VistaECDrvV" in compatibility with windows vista (right click on the file - properties - compatibilty tab- run this program in compatibility mode for: - select windows vista (service pack 2) !! do that for all of the drivers) - restart later
7. Install "TouchScreen"
After installing touch screen driver the touch should work - give a restart
8. Install "Synaptics MicroPad" - restart later
9. Install "shagctrl" ignore the Microsoft .NET Framework missing error - restart later
10. Install "Marvell Wifi driver" - restart later
11. Press the Win+R key combination and type msconfig in the run box and hit enter - switch over to the boot tab, and click on the Safe Boot check box - select minimal -apply -ok - restart
13. With windows booted in safe mode navigate to C:\Windows\System32\drivers right click on "sdbus.sys" -> properties -> security -> advanced -> owner TrustedInstaller click on change -> in the field labelled "enter the object name" type your username -> ok -> apply -> ok -> now back on security tab edit permissions -> click on users -> check all boxes from "permissions for users" tab on allow -> apply -> yes -> ok. Now delete "sdbus.sys"
14. Copy the "sdbus.sys" from the archive that i attached here to C:\Windows\System32\drivers
15. Press the Win+R key combination againg and type msconfig in the run box and hit enter - switch over to the boot tab, and unthick the Safe Boot check box - apply -ok - restart
16. You should have wifi working now - If you cannot find any wifi networks, as it was in my case, go to device manager - right click on the "Marvell sd8686 Wireless LAN SDIO Adapter" (the one without the exclamation mark if you have two) - properties - advanced - from the property box select 802.11D support - on the value box value box select enable. Your wifi should work ok now.
17. Install the "sherry driver 1.3" for the best performance of the video card.
18. That's it! enjoy
What i like most about windows 10 is that it have a "card view" of the running apps just like maemo 5 on noka n900, or the blackberry 10 os. Overall it runs a little better than windows 7 and similar with windows 8.1.
Maybe i will install it as a replacement for windows 8.1 update 1 on the main 120 gb hdd
Here is a small video to see how it runs:
Download HTC X9500 DRIVERS
ryu1 said:
Windows 10 Windows Technical Preview is available for more than a week. Since i have an extra old 40gb hdd for the shift, i decided to give it a try, and i can say that it works perfectly well. Everything works including touchscreen, wifi, bluetooth, modem, etc.
However installing the drivers may be a little tricky. Here are the steps:
1. Download Windows Technical Preview from microsoft website (download the x86 version)
2. Extract the .iso file to a usb stick (i used power iso to do that)
3. Plug the stick to the shift and boot from it
4. Follow on screen instruction to install windows
5. When done copy the drivers for the shift (you can find them on this forum) to a stick
6. First install "VistaECDrvV" in compatibility with windows vista (right click on the file - properties - compatibilty tab- run this program in compatibility mode for: - select windows vista (service pack 2) !! do that for all of the drivers) - restart later
7. Install "TouchScreen"
After installing touch screen driver the touch should work - give a restart
8. Install "Synaptics MicroPad" - restart later
9. Install "shagctrl" ignore the Microsoft .NET Framework missing error - restart later
10. Install "Marvell Wifi driver" - restart later
11. Press the Win+R key combination and type msconfig in the run box and hit enter - switch over to the boot tab, and click on the Safe Boot check box - select minimal -apply -ok - restart
13. With windows booted in safe mode navigate to C:\Windows\System32\drivers and delete "sdbus.sys" and "dumpsd.sys"
14. Press the Win+R key combination againg and type msconfig in the run box and hit enter - switch over to the boot tab, and unthick the Safe Boot check box - apply -ok - restart
15. When booted in normal mode copy the files from the "wififix" archive, that i attached to C:\Windows\System32\drivers and restart
16. You should have wifi working now - If you cannot find any wifi networks, as it was in my case, go to device manager - right click on the "Marvell sd8686 Wireless LAN SDIO Adapter" (the one without the exclamation mark if you have two) - properties - advanced - from the property box select 802.11D support - on the value box value box select enable. Your wifi should work ok now.
17. Install the "sherry driver 1.3" for the best performance of the video card. Search it on google.
18. That's it! enjoy
What i like most about windows 10 is that it have a "card view" of the running apps just like maemo 5 on noka n900, or the blackberry 10 os. Overall it runs a little better than windows 7 and similar with windows 8.1.
Maybe i will install it as a replacement for windows 8.1 update 1 on the main 120 gb hdd
Here is a small video to see how it runs:
Click to expand...
Click to collapse
Thanks alot, I am going to install it now
http://www.mediafire.com/download/c9g6a23223zr3sk/sherry1.3.2betaGMEGSE.rar
Excellent how-to. Clear and precise.
For those who want to perform it: taking a look at ryu1's comment in Post#14 is crucial!
You bring shift to future.
Also an interesting Video- as i see you've only 1GB RAM installed, and nevertheless your Shift runs pretty fast-
faster than mine with 2GB and Win7U.
Network connection, connection to SnapVue... i'm really amazed.
How long does it take to boot, and what about GPS?
Think i'll create a new partition on my 128GB SSD and run Win10 from there.
How large do you think should it be?
B-44 said:
Excellent how-to. Clear and precise.
You bring shift to future.
Also an interesting Video- as i see you've only 1GB RAM installed, and nevertheless your Shift runs pretty fast-
faster than mine with 2GB and Win7U.
Network connection, connection to SnapVue... i'm really amazed.
How long does it take to boot, and what about GPS?
Think i'll create a new partition on my 128GB SSD and run Win10 from there.
How large do you think should it be?
Click to expand...
Click to collapse
Well, i'm sure gps work ok (at least on the windows mobile side) but didn't tested on the windows 10 side.
For booting, i'm sure it take less than 1 minute, but don't know the exact time.
If you want to make a partition for win10, that should be at least 10 gb.
It would be really nice to see how it will run on your shift with 2gb of ram.
Please post the result if you install it
Made 20GB... had been frequently suggested for win8
Now taking a look if I've got a spare usb stick.
Maybe I'm missing something here. On my X9500 I can't get by the error about the 800 MHz processor. Maybe you are on a different model?
Same thing occured with win8 if i recall right... early releases worked fine, and later ones also came up with this problem. (It may have been with BenQ MID S6 instead Shift, I'll try to find out.)
Don't know if there had been some workaround.
As MS is continuously working on it, it may depend on the releases' date.
Mine dates october 20th, but i won't be able to test until next weekend.
If ryu1 doesn't have another idea, it may be useful to share the release he uses.
The processor should always be the same.
edit: Post#86
http://forum.xda-developers.com/showthread.php?t=1264742&page=9
What error are you talking about? i installed windows 8, then 8.1 and now 10 but never got any error about cpu.
Are you sure you didn't download the 64 bit version?
Win 10 Technical Preview lists as a requirement:
Processor: 1 gigahertz (GHz) or faster
Error complained about lower specification.
It was the 32-bit version.
"error" may be the wrong word.
The problem had been discussed in the thread i have linked above.
Again: it may be interesting to know the date of release.
ryu1 said:
What error are you talking about? i installed windows 8, then 8.1 and now 10 but never got any error about cpu.
Are you sure you didn't download the 64 bit version?
Click to expand...
Click to collapse
Maybe i've got it...
in your how-to you say "Plug the stick to the Shift and boot from it".
You mean plug it in, start your shift, enter boot options and select usb stick to boot from, right?
I had prepared my usb stick with powerISO, plugged it in, opened my stick in devicemanager and doubleclicked "Install".
And ran into "your device won't be able to run Win10 because of less than 1GHz".
Maybe this was my mistake, and i won't have this problem when booting from stick.
Will report asap.
That's it..
Just do what daddy told us
(And DON'T use windows installer.)
I haven't finished installation completely,
but right now i must say speed is amazing!
As some drivers are automatically installed to volume "C" i think i'll switch the names of C and X
(the partition i'm installing to), reinstall all drivers and then switch back.
edit: obsolete, win has done it by itself
Sorry for the delay, but i am very bussy these days. Anyway the installation mus be done by booting from usb stick, not via installer.
I have allready installed windows 10 on the main hdd instead of windows 8.1. There are a few things i forgot to mention on the first post, when booting into safe mode to delete the "dumpsd" and "sdbus" files you'll need permission to delete them. Just follow this instructions to change the permission: http://www.askvg.com/guide-how-to-take-ownership-permission-of-a-file-or-folder-manually-in-windows/
That's what i just was about to ask you, as i am stuck at this point...
Will try later and report
Tomorrow.
edit: Think you should for your own sake update your initial post, concerning boot process and rightsmanagement.
Further visitors won't follow the whole thread and'll bomb you with questions.
B-44 said:
"error" may be the wrong word.
The problem had been discussed in the thread i have linked above.
Again: it may be interesting to know the date of release.
Click to expand...
Click to collapse
Oh, by error I meant I received an error message when trying to do the install the way I had tried it. I will read the new information posted here, thanks all.
Finished installation yesterday, everything was fine, quick'n'clean when suddenly wifi stopped working.
Marvell shows error code 10 and winupdate seems to have installed a different adapter.
SD adapter same error.
Had a similar experience when i installed win7, but there i already had a restore point to return to,
and since then everything was fine.
Will make a clean reinstallation, and after adding the wififix disable wifi to avoid possible system updates
and create a basic restore point i can return to each time winupdate kills something.
Preview build 9879
Anyone managed to get the latest build to work. Mine gives a message that my display resolution is too low and stops the upgrade.
Shame really as this works very well on the Shift, and with rumours that win 10 could be free it would have been a good o/s for this computer.
Please post code 0f builtversion.
Build 9860
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.