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!
Hey guys,
I'm trying to update my gf's Galaxy S to JP6 via the latest Kies 2. The program connects initially and notifies about a firmware update.. accepting this brings up some T&C nonsense, choosing 'accept' brings up a box asking what to backup, at this point whether I backup or skip it will bring up an error about failed update, i9000 disconnected etc...
I've uninstalled & reinstalled Kies, no difference, can anyone suggest what the issue is and how to fix it?
It's UK O2 Branded, currently running JP5 (which was updated by an older version of Kies v1.5 that worked on Win XP). The PC in question this time is running Windows 7 64bit. I rooted the phone using SuperOneClick and had installed RyanZA's OCLF v2 from the market.. i've undone the OCLF now though.
Kies and Win 7 x 64 i have never got it working . But have on Win 7 x32 .
jje
viva.fidel said:
Hey guys,
I'm trying to update my gf's Galaxy S to JP6 via the latest Kies 2. The program connects initially and notifies about a firmware update.. accepting this brings up some T&C nonsense, choosing 'accept' brings up a box asking what to backup, at this point whether I backup or skip it will bring up an error about failed update, i9000 disconnected etc...
I've uninstalled & reinstalled Kies, no difference, can anyone suggest what the issue is and how to fix it?
It's UK O2 Branded, currently running JP5 (which was updated by an older version of Kies v1.5 that worked on Win XP). The PC in question this time is running Windows 7 64bit. I rooted the phone using SuperOneClick and had installed RyanZA's OCLF v2 from the market.. i've undone the OCLF now though.
Click to expand...
Click to collapse
Try to run Kies as "administrator" with "windows xp compatibility mode".
viva.fidel said:
Hey guys,
I'm trying to update my gf's Galaxy S to JP6 via the latest Kies 2. The program connects initially and notifies about a firmware update.. accepting this brings up some T&C nonsense, choosing 'accept' brings up a box asking what to backup, at this point whether I backup or skip it will bring up an error about failed update, i9000 disconnected etc...
I've uninstalled & reinstalled Kies, no difference, can anyone suggest what the issue is and how to fix it?
It's UK O2 Branded, currently running JP5 (which was updated by an older version of Kies v1.5 that worked on Win XP). The PC in question this time is running Windows 7 64bit. I rooted the phone using SuperOneClick and had installed RyanZA's OCLF v2 from the market.. i've undone the OCLF now though.
Click to expand...
Click to collapse
Could you fix it?
End to the Noob Bashing...
Just realised that i was looking at the wrong post when i posted this data so the reasons for posting bit at the top of this will make no sense....sentiment still true though. Hope it helps either way.
Ok, i'm a Techie. I know without a shaddow of a doubt that my Laptop is fine in every respect and yet it was doing this to me also.
Believe me when i say, you're not insane, and despite what others say you DO have a valid question which DOES deserves a valid answer...ENOUGH of the trollish Noob bashing 'non answers'.
If you are having the EXACT same issue as the original poster, heres what you do:
With your phone unplugged....
Update Kies:
Make sure you have updated Kies to the most recent version. Either do this by going to your mobile phone opperators website and downloading the updated software version directly or by using the help --> Check for Updates option. Latest version at time of writing is: 2.0.2.11071_128.
Once up-to-date, close Kies. Although probably not essential, use 'Task Manager' to end any Kies related processes.
Uninstall Samsung USB Driver Software:
1) Navigate to Control Panel and open either (Windows 7/Vista) 'Programs and Features' or (Windows XP/2000) 'Add Remove Programs'
2) Scroll through the list of programs to find one called 'SAMSUNG USB Driver for Mobile Phones'. If it is installed, right click it and select 'Uninstall'
3) Run through the process of uninstalling the software.
Tidy up Devices:
1) Right Click 'My Computer' select properties
2) On windows 7 (possibly Vista also...dont know as I skipped that generation) ONLY, select the 'Advance System Settings' option over to the left of the window.
3) Select the 'Advance' tab in the 'System Properties' window that appears.
4) Click 'Environmental variables'
5) In the 'System Variables' section of the window that appears, click 'New...'
6) In 'Variable Name:' type 'DEVMGR_SHOW_NONPRESENT_DEVICES' without the quotes
7) In 'Variable Value:' type '1' without the quotes
8) Click 'OK' times 3 to exit the windows you opened
9) If Windows 7 (or Vista) close the 'View basic information about your computer' window also.
10) Open 'Control Panel' and navigate through to 'Device Manager'
11) Click the 'View' menu and select 'Show Hidden Devices'. This will display all mothballed devices i.e. those devices which have previously been plugged in but then removed. Windows stores a record of the drivers in the background of the system to speed up the process of installing the device drivers when you next plug in said device. Sometimes, in the case of Network Cards for example, not only will it store the drivers but it will also store its settings. This can cause a problem as if you were to plug in a replacement Network Card and set it to use the same static IP address, the mothballed device will clash with the current device. Without the environmental variable setting being configured as above, even when you show hidden devices, mothballed devices remain hidden.
12) Starting from the top, expand each of the branches in the tree to see the devices within them.
13) Look for anything with a 'Samsung', 'MTP', 'GT-I9000' prefix. If found, right click and select 'Uninstall' and confirm at the prompt. BE CAREFUL NOT TO UNINSTALL ANYTHING YOU ARE UNSURE ABOUT. Google it if need be to figgure out what it is and if its not a Samsung or android related device then leave it well alone.
14) Close Device Manager once you have assessed the final branch.
Re-Install Samsung USB Driver Software:
1) Open Kies
2) Expand the 'Tools' menu and select the 'Install Driver' option.
3) Click ok to any prompts to fire off the process.
4) Wait for it to complete.
5) On completion click 'Ok' to acknowledge if required.
At this stage, it may be worth turning off your Windows Firewall and AV scanners just to be on the safe side. Probably not an essential step but may make a difference. If you're not confident enough with computers to do this then dont bother.
Re-Connect Samsung Galaxy Device:
1) Plug the Micro USB cable that came with your device in to ANY of your most trust worthy USB sockets.
2) Plug the other end into the Micro USB socket of your Samsung Galaxy S.
3) Allow Kies to pickup your device and display the storage information proving it is properly connected.
4) If an update is avaialble for your device, Kies should prompt you. If you are confident that you have all the data backed up onto your computer, then proceed with the Firmware update.
5) Click either the Backup or Skip Backup option.
6) Panic a little when the device appears to disconnect YET AGAIN!
7) Chuckle to yourself knowingly once it blasts through this onto the update.
8) Once completed unplug from and re-plug your Samsung into your computer again.
9) Upload your backed up data.
10) Get rid of the God-Awful default dasktop layout that your Mobile provider forces onto you.
SORTED!
Dont know what causes this but what i have noticed is that once you have tidied the mothballed system devices related to your phone and re-installed the device drivers again, it appears as if there isn't any devices named with the prefix of 'MTP' in the device list but there are a few more labelled with a 'Samsung' prefix.
I suspect this is something to do with Samsung at long last fully qualifying their own drivers but not bothering to tidy up the mess that the old devices left behind as part of the Kies update process. Either that or Windows prevents the Samsung USB Driver installer software from being able to delete/update existing Samsung devices.
Enjoy!
I wish I could say this worked for me... but alas, it has not...
This is from a post I entered earlier today... (no change from this either)
ghosty_uk said:
... steps that worked for me
1, downloaded MyBackup (free version)
2, did backup of both apps and data (put both on ext memorycard)
3, used the restore to factory option under privacy in the settings menu
4, unmounted internal sd card and formated it (to remove the mtp loop issue)
5, run kies,
6, select update firmware,
7, at the box where it says no device connected, put into test mode (ctrl + alt + U + P)
8, connected phone
9, detected thaqt there was an update to JM1 available
10, started update,
Click to expand...
Click to collapse
I have yet to do any of this (other than get a backup using MyBackup), but have some questions... (noob here)
Step 3: Will this remove all the definitions for my phone number and/or provider as well?
Step 7: the CTRL+ALT+U+P thing doesn't work with Kies 2.0.2 so if I am unable to do an update, will the phone be at Froyo (2.2) as it is now? or does it revert to 2.1 (which it was when I bought the unit)?
I also got this "Informational" record from the Event Manager... (I could hear the system connect, then drop the Kies connection)
Fault bucket 17725111, type 5
Event Name: PnPGenericDriverFound
Response: Not available
Cab Id: 0
Problem signature:
P1: x64
P2: USB\MS_COMP_MTP
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
D:\Dad\AppData\Local\Microsoft\Windows\WER\ReportArchive\NonCritical_x64_d1b8bb6482961a133bbee52e8072f0433f363959_21d02bae
Analysis symbol:
Rechecking for solution: 0
Report Id: 5ebfff60-c94e-11e0-948f-005056c00008
Report Status: 0
Well had to go through Samsung Support... they got me to reset to factory default (since I had a backup) then do the Kies update...
All is better although it would be nice to know what had gone wrong...
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!)
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.
Hello everyone!
One UI 5.0 beta is out, so I have put together this guide on installing it on your Galaxy device. I will show you how to sideload the beta even though the beta programme may not be available in your country or may be full.
❕️ If your device has an SD Card slot, check out the SD Card Method.
NOTE: When you sideload the beta, you will not receive OTA updates automatically. You must install the stable One UI 5.0 when it's released (or downgrade back to One UI 4.1) via Odin.
Links (will be updated):
• Galaxy S22/S22+/S22 Ultra (Exynos) ➜ https://forum.xda-developers.com/t/oneui-5-beta-exynos-galaxy-s22-s22-s22-ultra-beta-thread.4476641/
• Galaxy S22/S22+/S22 Ultra (Snapdragon) ➜ https://forum.xda-developers.com/t/...-s22-s22-ultra-oneui-5-0-beta-thread.4475549/
• Galaxy S21/S21+/S21 Ultra (Exynos) ➜ https://forum.xda-developers.com/t/one-ui-5-0-beta-exynos-official-android-13.4486617/
• Galaxy S21/S21+/S21 Ultra (Snapdragon) ➜ https://forum.xda-developers.com/t/one-ui-5-0-beta-snapdragon-oficial-android-13.4496577/
• Galaxy S20/S20+/S20 Ultra ➜ https://forum.xda-developers.com/t/s20-series-oneui-5-0-beta-download-install.4499079/
• Galaxy A52 (4G) ➜ https://forum.xda-developers.com/t/one-ui-5-beta-galaxy-a52-4g.4504749/
• Galaxy Z Fold3 ➜ https://forum.xda-developers.com/t/ui-5-beta-is-live-at-samsung-members.4505291/
• Galaxy Z Flip3 ➜ [Beta is out, waiting for link]
• Galaxy Note20/Note20 Ultra ➜ [Beta is out, waiting for link]
• How to install ADB
• Update or downgrade via Odin
• Alternative method via Alliance Shield (thanks to @woodchild )
Video guide:
Steps:
Download the update file from XDA Forums. Make sure to download the right build for your device.
Go to where you downloaded the file.
At File Explorer, go to View, then Show and enable "File name extensions".
Right click on the file and click on Rename.
Rename (including the file extension) the .bin file to "update.zip".
A warning may appear. Click on Yes.
Download, install ADB. Make sure to have "C:\Android\platform-tools" added to "Path" in System variables.
At your phone, go to Settings, About phone, Software information.
Tap repeatedly on the build number until Developer options are enabled.
Back to Settings, tap on Developer options at the bottom.
Scroll down and enable "USB debugging". Tap on OK.
Connect your phone to your PC.
You may enable the "Always allow from this computer" if it's your personal PC.
Tap on Allow.
Back to the PC, move the "update.zip" file to "C:\Android\platform-tools".
Right click on the Start Button.
Click on Windows Terminal (Admin) or PowerShell (Admin).
In the Terminal, type "adb devices" and execute it.
If you didn't enable "Always allow from this computer", the pop up will appear again on the phone. Tap on Allow.
Type "adb reboot recovery" and execute it.
Your phone will boot to Recovery Mode.
Navigating with the volume buttons and selecting with the power button, go to "Apply update from ADB" (if you want to force exit from this screen, hold down the Volume down and Power buttons).
Back to the PC, type "adb sideload update.zip" and execute it.
The installation process will start and One UI 5.0 will be installed. (If you get an error, you may have downloaded the wrong build, or your device doesn't support the beta programme at all. If you are sure that you have downloaded the right build, try again using different cables, USB ports or PCs.)
After the update process has finished, back to the PC, execute "adb reboot recovery" again.
Go to "Wipe cache partition" and select Yes.
Then select "Reboot system now".
Report any bugs to the Samsung Members app!
I hope this helps you! If you have any issues, please let me know and I will try to help you!
Click to expand...
Click to collapse
BredzProh said:
Hello everyone!
I am back with another guide!
I have put together this guide on installing One UI 4.0 (Android 12) beta on your Galaxy device. I will show you how to sideload the beta even though the beta programme may not be available in your country or may be full.
NOTE: When you sideload the beta, you will not receive OTA updates automatically. You must install the stable One UI 4.0 when it's released (or downgrade back to One UI 3.1) via Odin.
Links:
• Galaxy S21/S21+/S21 Ultra Exynos ➜ https://forum.xda-developers.com/t/...-download-and-install-in-here-exynos.4333281/
• Galaxy S21/S21+/S21 Ultra Snapdragon ➜ https://forum.xda-developers.com/t/one-ui-4-beta-snapdragon-s21-ultra.4333523/
Video guide:
Step-by step guide:
1. Download the update file from XDA Forums. Make sure to download the right build for your device.
2. Go to where you downloaded the file.
3. At File Explorer, go to View, then Show and enable "File name extensions".
4. Right click on the file and click on Rename.
5. Rename (including the file extension) the .bin file to "update.zip".
6. A warning may appear. Click on Yes.
7. Download, install ADB. Make sure to have "C:\Android\platform-tools" added to "Path" in System variables.
8. At your phone, go to Settings, About phone, Software information.
9. Tap repeatedly on the build number until Developer options are enabled.
10. Back to Settings, tap on Developer options at the bottom.
11. Scroll down and enable "USB debugging". Tap on OK.
12. Connect your phone to your PC.
13. You may enable the "Always allow from this computer" if it's your personal PC.
14. Tap on Allow.
15. Back to the PC, move the "update.zip" file to "C:\Android\platform-tools".
16. Right click on the Start Button.
17. Click on Windows Terminal (Admin) or PowerShell (Admin).
18. In the Terminal, type "adb devices" and execute it.
19. If you didn't enable "Always allow from this computer", the pop up will appear again on the phone. Tap on Allow.
20. Type "adb reboot recovery" and execute it.
21. Your phone will boot to Recovery Mode.
22. Navigating with the volume buttons and selecting with the power button, go to "Apple update from ADB" (if you want to force exit from this screen, hold down the Volume down and Power buttons).
23. Back to the PC, type "adb sideload update.zip" and execute it.
24. The installation process will start and One UI 4.0 will be installed.
If you get an error, you may have downloaded the wrong build, or your device doesn't support the beta programme at all. If you are sure that you have downloaded the right build, try again using different cables, USB ports or PCs.
25. After the update process has finished, back to the PC, execute "adb reboot recovery" again.
26. Go to "Wipe cache partition" and select Yes.
27. Then select "Reboot system now".
28. Report any bugs to the Samsung Members app!
Samsung Members | Apps - The Official Samsung Galaxy Site
Go to the Samsung Members app to get expert support, community connections, insider tips & exclusive perks.
www.samsung.com
I hope this helps you! If you have any issues, please let me know and I will try to help you!
Click to expand...
Click to collapse
No Apple in this universe .bruh.
amoyan said:
No Apple in this universe .bruh.
Click to expand...
Click to collapse
Omg.
Fixed the typo.
Does anyone have files for S21+?
Morzas said:
Does anyone have files for S21+?
Click to expand...
Click to collapse
Exynos or Snapdragon?
I have not been able to find the S21+ Snapdragon variant yet. Either nobody is trying to catch the update file or it's not yet out for it.
As for Exynos, it's in the thread I've linked.
BredzProh said:
Exynos or Snapdragon?
I have not been able to find the S21+ Snapdragon variant yet. Either nobody is trying to catch the update file or it's not yet out for it.
As for Exynos, it's in the thread I've linked.
Click to expand...
Click to collapse
Snapdragon.
Thanks for the guide . Does it work for BRI SM-G 9980 ?
[email protected] said:
Thanks for the guide . Does it work for BRI SM-G 9980 ?
Click to expand...
Click to collapse
I just checked.
Unfortunately there's no update file for SM-G9980 online yet. It either hasn't been released or no one who got the update is capturing & sharing it.
Hey guys,
I'm trying to sideload via adb on G996B, from AUIE > ZUJ1 on non-supported beta country.
Everything goes fine until 47% on terminal, when starts verifying partitions:
...
Verify partitions...
Verified system image...
Verified vendor image...
Verified product image...
Verified odm image...
Unable to use metadata to correct errors
E2004: prism partition fails to recover
E:Error in /sideload/package.zip (status 1)
Install from ADB completed with status 503
Installation aborted
Then, I can only reboot system back to One UI 3.1.
Someone managed to install after this error?
I believe the common mistake is people updating from the October security patch. I was also getting an error at 47% until i downgrade to the September update before sideloading. Try that and remember to always backup your device.
rainer_alvin said:
I believe the common mistake is people updating from the October security patch. I was also getting an error at 47% until i downgrade to the September update before sideloading. Try that and remember to always backup your device.
Click to expand...
Click to collapse
Gonna try
rainer_alvin said:
I believe the common mistake is people updating from the October security patch. I was also getting an error at 47% until i downgrade to the September update before sideloading. Try that and remember to always backup your device.
Click to expand...
Click to collapse
MatheusApolonio said:
Gonna try
Click to expand...
Click to collapse
My phone didn't receive September Security Patch:
MatheusApolonio said:
My phone didn't receive September Security Patch:
Click to expand...
Click to collapse
Oh you're using an s21+? I do not think anyone has even captured the one ui 4 image for your device yet, i guess you'd just have to take your time and wait.
rainer_alvin said:
Oh you're using an s21+? I do not think anyone has even captured the one ui 4 image for your device yet, i guess you'd just have to take your time and wait.
Click to expand...
Click to collapse
Yeah, but the main thread points to a link with G966B version of OneUI 4.
MatheusApolonio said:
Yeah, but the main thread points to a link with G966B version of OneUI 4.
Click to expand...
Click to collapse
Where? I don't see that link
rainer_alvin said:
Where? I don't see that link
Click to expand...
Click to collapse
[OneUi 4.0 Public Beta] Download and install in here! [Exynos)
Today One Ui 4 testing has started in 7 countries: - South Korea - US - UK, - China - India - Germany - Poland How to install: 1: Open the Samsung Members app and select the pilot program banner 2: Download and install the software once you...
forum.xda-developers.com
"Update from October Security Patch" bottom lines
MatheusApolonio said:
[OneUi 4.0 Public Beta] Download and install in here! [Exynos)
Today One Ui 4 testing has started in 7 countries: - South Korea - US - UK, - China - India - Germany - Poland How to install: 1: Open the Samsung Members app and select the pilot program banner 2: Download and install the software once you...
forum.xda-developers.com
"Update from October Security Patch" bottom lines
Click to expand...
Click to collapse
Oh yeah that's true. So does your baseband version end with "AUIE"?
rainer_alvin said:
Oh yeah that's true. So does your baseband version end with "AUIE"?
Click to expand...
Click to collapse
Yep.
MatheusApolonio said:
Yep.
Click to expand...
Click to collapse
Then it should work, maybe you'd need to back up, factor reset, and then sideload if you want it that bad. But I'm not sure about it because I really don't see much about the s21+ on here. I was having that 47% error on my s21. Reset with "AUHD" (s21 exynos) and then the sideload worked after.
I'm trying to install the update following all the steps, but it won't work. Using powershell I type in adb devices and it recogizes the command. have put the update.zip in platform tools folder, I go to recovery and type in again adb devices and it says that the device is connected, then I type in adb sideload update.zip, and get this message "adb: failed to stat file update.zip. No such file or directory. Can someone help me get this setup, don't know what I'm doing wrong.