Database Develop

[Solution] Win7 Adb driver failing to install in adb sideload

I had mutiple issues getting adb to work in adb sideload. It worked while in the OS but not in recovery after selecting sideload. This is how I fixed it!
You must first have SDK installed and know the basics of adb and fastboot. If you do not know how to install SDK or how to use terminal emulator or command prompt (cmd) to get to the platform tools folder you must do all that first. You must also have developers tools and USB debugging on.
See here if you have no idea what I am talking about: http://forum.xda-developers.com/showthread.php?t=2141817
Go to stock recovery and click adb sidload
In Win7 go to:
1. Go to Start
2. Right Click Computer
3. Click Manage
4. Click Device manager
5. You will see the nexus 5 with a yellow !
6. Right Click on nexus 5 and click update driver
7. then choose to browse for driver
Windows 8? See here:
gaga111 said:
http://www.theandroidsoul.com/nexus-5-driver-adb-fastboot-installation-guide/
this helped me
i used the naked driver and disabled the driver signature enforcement (only for windows 8 and 8.1)
Click to expand...
Click to collapse
8. then choose the second option search for driver by device
zallaaa said:
I believe that's the same "wall" I've found.
Select "Android Phone" and next, then you'll find a list of all the compatible "Android ADB Interfaces". I used "Android ADB Interface ver. 8.0.0.0" and it worked, thank The Greek!
Click to expand...
Click to collapse
9. click on Android ADB Interface
10. Should install driver succesfully.... check adb devices it will show device id in sideload mode
Hope this helps the people who can't function without an ota
Hit thanks if this helped:thumbup:

Step 8.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Android The Greek said:
I had mutiple issues getting adb to work in adb sideload. It worked while in the OS but not in recovery after selecting sideload. This is how I fixed it!
Go to stock recovery and click adb sidload
In Win7 go to:
1. Go to Start
2. Right Click Computer
3. Click Manage
4. Click Device manager
5. You will see the nexus 5 with a yellow !
6. Right Click on nexus 5 and click update driver
7. then choose to browse for driver
8. then choose the second option search for driver by device
9. click on Android ADB Interface
10. Should install driver succesfully.... check adb devices it will show device id in sideload mode
If someone can add screen shots of their computer while following these steps it would be helpful. I can't seem to replicate the issue now that its working on my PC
Click to expand...
Click to collapse
When i click step 8, no option for Android ADB Interface is on the list?

Can you post a screen shot of what the options are?
In the os not recovery does you device show up in adb?
Sent from my Nexus 5 using XDA Premium 4 mobile app

jonyid said:
When i click step 8, no option for Android ADB Interface is on the list?
Click to expand...
Click to collapse
I believe that's the same "wall" I've found.
Select "Android Phone" and next, then you'll find a list of all the compatible "Android ADB Interfaces". I used "Android ADB Interface ver. 8.0.0.0" and it worked, thank The Greek!

Android The Greek said:
Can you post a screen shot of what the options are?
In the os not recovery does you device show up in adb?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
when not in recovery yes it appears in adb and android device appears. When i got through the process of updating the OTA i get up to:
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
and then it appears device not found

jonyid said:
when not in recovery yes it appears in adb and android device appears. When i got through the process of updating the OTA i get up to:
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
and then it appears device not found
Click to expand...
Click to collapse
When device is in adb sideload type in you command prompt adb devices. Do you see anything? Try Ctrl alt delete kill adb.exe in process the retry if adb sees the device I'd in adb side load mode then your good. If not you need to get the drivers to work by following step 8. If you do not see that option add a screen shot of your options.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Android The Greek said:
When device is in adb sideload type in you command prompt adb devices. Do you see anything? Try Ctrl alt delete kill adb.exe in process the retry if adb sees the device I'd in adb side load mode then your good. If not you need to get the drivers to work by following step 8. If you do not see that option add a screen shot of your options.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm now getting the error message (i uninstalled and re-installed the drivers) "adb cannot run as root in production builds" at stage 3:
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'

http://www.theandroidsoul.com/nexus-5-driver-adb-fastboot-installation-guide/
this helped me
i used the naked driver and disabled the driver signature enforcement (only for windows 8 and 8.1)

jonyid said:
I'm now getting the error message (i uninstalled and re-installed the drivers) "adb cannot run as root in production builds" at stage 3:
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
Click to expand...
Click to collapse
Are you stock? Why are you using adb recovery? If adb works in the os but when you manually boot into recovery mode adb sideload and it says failed to install the drivers my method will work.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Android The Greek said:
Are you stock? Why are you using adb recovery? If adb works in the os but when you manually boot into recovery mode adb sideload and it says failed to install the drivers my method will work.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm 100% stock. This is the guide i was advised to use:
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. Its attached at the bottom
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press power then immediately press volume up and release. The menu will appear. Select “apply update from adb”
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
I've installed the google drivers and when plugged in it recognises both the phone (no yellow ! there) and also an 'android device - android composite ADB interface" option. Both say that the drivers are up-to-date.

jonyid said:
I'm 100% stock. This is the guide i was advised to use:
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. Its attached at the bottom
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press power then immediately press volume up and release. The menu will appear. Select “apply update from adb”
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
I've installed the google drivers and when plugged in it recognises both the phone (no yellow ! there) and also an 'android device - android composite ADB interface" option. Both say that the drivers are up-to-date.
Click to expand...
Click to collapse
In recovery adb sideload do a adb devices in command prompt. What does it say
Sent from my Nexus 5 using XDA Premium 4 mobile app

Android The Greek said:
In recovery adb sideload do a adb devices in command prompt. What does it say
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you mean at stage 3? it says:
List of devices attached
03b911s908eb03ff device

jonyid said:
you mean at stage 3? it says:
List of devices attached
03b911s908eb03ff device
Click to expand...
Click to collapse
Why not manually put your device in adb sideload
Sent from my Nexus 5 using XDA Premium 4 mobile app

Android The Greek said:
Why not manually put your device in adb sideload
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do i do this? Will it then allow me to install pretty quickly?

jonyid said:
How do i do this? Will it then allow me to install pretty quickly?
Click to expand...
Click to collapse
Pm me your number
Sent from my Nexus 5 using XDA Premium 4 mobile app

Android The Greek said:
Pm me your number
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i'm in the UK that's the problem

I had to follow the instructions that were listed here to get my laptop to see my N5 in recovery mode. Worked like a charm afterward.
http://stackoverflow.com/questions/15721778/adb-no-devices-found

Sephiroth_Darko said:
I had to follow the instructions that were listed here to get my laptop to see my N5 in recovery mode. Worked like a charm afterward.
http://stackoverflow.com/questions/15721778/adb-no-devices-found
Click to expand...
Click to collapse
I'm on my work PC and not 100% about doing this

jonyid said:
I'm on my work PC and not 100% about doing this
Click to expand...
Click to collapse
I did it on my home laptop it and it worked fine. But I understand how you could be a bit hesitate to do this on a work machine. Best of luck!

MM Update

was just wondering : has anyone got the MM update already ?
cheers

OTA update link: https://android.googleapis.com/pack...5e909bdec.signed-signed-sprat-ota-2576000.zip
This next part is assuming you have ADB installed on your computer. If you don't, google how to install ADB first.
To sideload the update:
1. Enable Developer Options: Settings>About>Tab Build Number 7x
2. Go back to the Settings Menu
3. Go into Developer Options (All the way at the bottom, below About)
4. Enable USB Debugging
5. Go to wherever ADB is installed on your PC (For me, it is C:\Program Files (x86)\Android\android-sdk\platform-tools\)
6. Shift+Right Click inside the folder, but not on a file in the folder, then click "Open command window here"
7. Type "adb devices"
8. At this point, on your watch, it should pop up a dialog asking if you would like to authorize the connection. Hit Always.
9. Type “adb reboot recovery”
10. On your watch, tap the screen once, then swipe down until you're hovering on “apply update from ADB.” then swipe to the right.
11. In the command prompt on your PC type “adb sideload” followed by a single space then drag and drop the zip to the command prompt window then hit Enter.
12. It will now begin installing the update on your device. Whatever you do, do not disconnect your watch from the computer or close the command prompt window.
13. Depending on the situation, your watch may or may not reboot automatically. If it doesnt, after it is done installing the update and goes back to the main Recovery menu, swipe to the right on "Reboot system now."
Click to expand...
Click to collapse

BTW I highly recommend forgetting your watch from the Android Wear app on your phone/tablet and factory resetting your watch after updating.
After I installed it, settings on the watch were funky, like it offering phone options which we shouldn't have without a speaker, and it wouldn't install the new Wear Messenger app that is included in the newest version of Google Messenger.

Dudash said:
OTA update link: https://android.googleapis.com/pack...5e909bdec.signed-signed-sprat-ota-2576000.zip
Click to expand...
Click to collapse
cool, thanks, have just installed it !
cheers

Dudash said:
OTA update link: https://android.googleapis.com/pack...5e909bdec.signed-signed-sprat-ota-2576000.zip
This next part is assuming you have ADB installed on your computer. If you don't, google how to install ADB first and since the zip file doesn't say which "version-from-version" it is for like they normally do, for example LCA43-from-LDZ22J, I'd recommend being on LCA43 before sideloading the update.
Click to expand...
Click to collapse
Someone correct me if I am wrong, but that OTA update is a full image unlike all previous updates. So, it should work as long as you have partition in place. Also, it looks like they added "new" features to the stock recovery. It has more options now.

aligatro2010 said:
Someone correct me if I am wrong, but that OTA update is a full image unlike all previous updates. So, it should work as long as you have partition in place. Also, it looks like they added "new" features to the stock recovery. It has more options now.
Click to expand...
Click to collapse
It is possible that you could flash it from an earlier build and end up with the same system. If you want to be a guinea pig for other people, be my guest
I was merely stating the safest way to not end up with a watch that won't go past the boot logo.
Also, since MM updates for other watches include the "version-from-version" text in the name of the update.zip, I assumed they just forgot to put it in the Gear Live .zip.

Dudash said:
It is possible that you could flash it from an earlier build and end up with the same system. If you want to be a guinea pig for other people, be my guest
I was merely stating the safest way to not end up with a watch that won't go past the boot logo.
Also, since MM updates for other watches include the "version-from-version" text in the name of the update.zip, I assumed they just forgot to put it in the Gear Live .zip.
Click to expand...
Click to collapse
Nope, they didn't forget, but its just a full image. I was able to sideload it to my watch after formatting the partitions(so no prev firmware at all).

Does anyone know if root is available already ?
Cheers !
Enviado desde mi Galaxy Nexus mediante Tapatalk

thagringo said:
Does anyone know if root is available already ?
Cheers !
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
Haven't tried it on the latest version, but I think you can root it by installing latest supersu. Just need to remove the apk that comes with it, as it will crash on launch.

One thing I don't like about the new update is how they changed the "Simple" and "Incremental" watchfaces.
They used to have a daytime color (light blue), an evening color (yellowish-orange), and a nighttime color (dark blue/purple).
Now the colors/images are updated (more clouds) but there isn't an evening color anymore and it doesn't change to the nighttime one until like 10pm.
Kind of a strain on the eyes to see a light blue background after the sun goes down.
I'm curious why they removed the evening color.

thagringo said:
was just wondering : has anyone got the MM update already ?
cheers
Click to expand...
Click to collapse
Mine updated automatically. I left it charging and when I came back, there it was, waiting to be installed.
One thing though: it won't show starred contacts (favorites) anymore, which it did before the update, and I can't figure out how to fix it.
Anyone else notice this?

I got it. So far so good
Sent from my SM-G935P using XDA-Developers mobile app

[GUIDE] How to revert back to Android Wear 1.5

How to revert back to Android Wear 1.5
Flashing stock AW1.5 build:
- Unlock your bootloader
- Reboot into FASTBOOT MODE
- Download STOCK ROM MWG68 images
- via adb type commands:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase userdata
fastboot reboot
How to block OTA to AW 2.0
- adb shell
- pm disable com.google.android.gms/.update.SystemUpdateService
- pm disable com.google.android.gsf/.update.SystemUpdateService
- exit

ingbrzy said:
How to block OTA to AW 2.0
- adb reboot bootloader
- adb shell
- pm disable com.google.android.gms/.update.SystemUpdateService
- pm disable com.google.android.gsf/.update.SystemUpdateService
- exit
Click to expand...
Click to collapse
This probably won't work, you don't have adb shell available in bootloader, and while booted up you can't use the pm disable command without root..

Maxr1998 said:
This probably won't work, you don't have adb shell available in bootloader, and while booted up you can't use the pm disable command without root..
Click to expand...
Click to collapse
true.. it will be more easier to boot TWRP, disable dm-verify and edit build.prop line
Code:
ro.build.id=MWG68
to
Code:
ro.build.id=MWG68_something

Thanks, i had to revert because i started getting random reboots since 2.0... Now I'mm gonna wait and see if it continues.
BTW, i think you forgot "fastboot oem lock" after downgrading.

after following the guide and flashing aw 1.5 I get an error saying zenwatch manager has stopped and then the reboots, and so on.
any ideas what went wrong and how can I fix this?

asafgolan said:
after following the guide and flashing aw 1.5 I get an error saying zenwatch manager has stopped and then the reboots, and so on.
any ideas what went wrong and how can I fix this?
Click to expand...
Click to collapse
make factory reset.. unpair and reset in the settings..

ingbrzy said:
make factory reset.. unpair and reset in the settings..
Click to expand...
Click to collapse
Thanks, that did the trick!

I'm having to much issues with 2.0 and overall I hate the update, so this guide is very appreciated, yet my watch is brand new and I don't want to mess things up, can you please do a complete guide with links to all the software needed and stuff? This seems to be for those who are already in the "knowing how to flash the FW", I believe I need to unlock the bootloader to in order to revert to AW 1.5 right? Or isn't that needed?
Thanks for the help @ingbrzy

Any chance one of you can help with this issue?
https://forum.xda-developers.com/zenwatch-3/how-to/fastboot-recovery-getting-g-co-abh-t3637403

Ok, I've been doing some reading and I'm almost ready to flash the watch back to 1.5, but just in case I'll make here the full list of what I've done/about to do, please check if all is correct:
1 - Download and place the Platform-tools folder from here on a easy access place to access on your PC
1.b - Edith Path Variable as shown here just be make things easier
2 - Enable USB debugging on watch by going to the watch Settings/System/About and pressing a few times on the Build Number
2.B - To check if the connection is well done between watch and PC open a command line on Windows and write "adb devices", it should show the watch SN listed
3 - Unlock the bootloader!
3.1 - Reboot to fastload (via *adb command* (You do this by opening a command prompt window from within windows itself) "adb reboot bootloader")
3.2 - type command "fastboot oem unlock"
4 - Download STOCK ROM MWG68 images
From here is where I have doubts, DON'T FOLLOW THESE INSTRUCTIONS until someone more experienced confirms if it's correct or not
5 - Place the files unziped: system.img / boot.img and recovery.img downloaded on point 4 inside the platform-tools folder in point 1
6 - Open a command prompt window and past the following code ***DOUBT*** Full code at once as shown bellow or line by line followed by enter??
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase userdata
fastboot reboot
7 - make factory reset on watch by... "unpair and reset" in the watch settings...
7.1 - Re-lock bootloader is advised? How and why to do it?
8 - Don't install AW 2.0 again?
@ingbrzy is this correct or am I missing something?

Thank you for this thread :good:
I'm back on 1.5 it's better for me in this moment...
My watch understand me again :laugh::laugh::laugh:
Edit:
I have two questions:
How I lock bootloader?
How to block Ota? Easiest way?
Thank you very much

Android Wear Updates
Does anyone know if leaving the bootloader unlocked prevents android wear 2.0 OTA
updates or any other updates?
Thanks, have a great day!

Misterjunky said:
Does anyone know if leaving the bootloader unlocked prevents android wear 2.0 OTA
updates or any other updates?
Thanks, have a great day!
Click to expand...
Click to collapse
No, I have unlocked bootloader and after night my watch download AW2.0 update

TWRP Recovery
I wonder if installing TWRP recovery might prevent Android Wear 2.0 OTA update?
I am on Android Wear 1.5 and do not want to update or get notifications to update.
Thanks,
---------- Post added at 01:02 AM ---------- Previous post was at 12:47 AM ----------
Hoffmanns said:
No, I have unlocked bootloader and after night my watch download AW2.0 update
Click to expand...
Click to collapse
Have you or anyone found a way to delete the AW2.0 update file from the watch?
Thanks!

Misterjunky said:
Have you or anyone found a way to delete the AW2.0 update file from the watch?
Thanks!
Click to expand...
Click to collapse
In this moment NO
Factory reset in recovery may help...
But I need block OTA update first

re: Build Prop file
ingbrzy said:
true.. it will be more easier to boot TWRP, disable dm-verify and edit build.prop line
Code:
ro.build.id=MWG68
to
Code:
ro.build.id=MWG68_something
Click to expand...
Click to collapse
@ingbrzy
Is it possible to use adb to pull and push the build-prop
file from /system to /sdcard or some other place where it would be
accessible making it easy to edit without rooting the watch?
(preferably someplace in Windows 10 or in my S7 Edge phone?)
If it's possible, could you please post the adb commands to pull and push the file?
Thanks in advance, have a great day!

I may go back as well. Aw 2.0 hasn't been a totally smooth experience even after wiping data and clearing cache. Sometimes it'll stutter and I will end up clearing all notifications instead of going one by one

Someone, please explain how to block OTA update to 2.0.... Please

re: Block OTA notifications
avchd said:
Someone, please explain how to block OTA update to 2.0.... Please
Click to expand...
Click to collapse
The only way I found to block updates and notifications for updates
is to ROOT the watch.
I rooted my watch 3 days ago after really trying to like this AW 2.0
but after all was said and done I just could not see any reason to
keep the new AW 2.0.
The only two things which we good and nice in AW 2.0 was the
really good looking and smooth/fast scrolling of the app drawer
and the nicer notifications which AW 2.0 has.
But everything else in AW 2.0 is really crappy way too crappy for me.
If you are interested in rooting and twrping your watch here is the link
with step by step instructions and download links for the rom.
Android Wear v1.5 pre-rooted and twrp'ed custom rom:
https://forum.xda-developers.com/zenwatch-3/development/rom-asus-zenwatch-3-swift-t3537340
The main problem with keeping AW 1.5 without flashing
a custom rom is all those OTA notifications you get over
and over again without a way to disable the notifications.
Come on guys, do we really need a Google Play store in our watch... LOL
Also the only way a watch can be called "stand-alone" is if it has a sim card.
Good luck, have a great day!

Even though I knew what I was doing, I was on a new computer so I "followed" your instructions because I've never seen anyone write it out so thoroughly from no ADB at all, and glad to say you pretty much nailed it through that. Except step 2, it's more like a whole bunch of times. Don't know why you've gone un-thanked and un-replied!
Step 5 is unnecessary because of the method of setting up ADB with the path variable described in 1b (if you don't do step 1b, then the files need to be in the platform-tools folder). You just need to get to the same folder in the command prompt as the files. The command prompt by default opens to C:\Users\pyroguysf (or whatever your own name is), which is where your downloads folder is located by default, so if you unzip the files to your downloads folder, type "cd Downloads" to navigate into your downloads folder. Once you're in the same folder as the img files you unzipped, then run the commands listed in step 6, each line, one at a time. After each one, it should show the progress, and make sure it says completed not failed (I forget the exact words used) before going to the next. If it fails that's a separate topic, but it shouldn't. I always advise a factory reset after any significant software changes. Re-locking the bootloader is for security's sake, and while not 100% necessary, is highly recommended, unless you plan to be changing the software again anytime soon (I see a modified version in this thread that supposedly has OTA's disabled I might try, but this is slightly more advanced). Re-locking is basically the reverse of step 3 - reboot into bootloader with "adb reboot bootloader" and then once it's there "fastboot oem lock" instead of unlock.
Edit: That's right, you get the message upon boot for a while that your device can't be checked for corruption when it's unlocked. Also, my watch won't boot now, so I'm going to try a few more things... That's why I waited until the weekend.
Edit2: Re-unzipped the files (md5 was fine), did boot, recovery, then system, and did "fastboot format userdata" instead of "fastboot erase userdata" in step 6.
Edit3: Edited the quote from MK2ever below with what worked for me.
MK24ever said:
Ok, I've been doing some reading and I'm almost ready to flash the watch back to 1.5, but just in case I'll make here the full list of what I've done/about to do, please check if all is correct:
1 - Download and place the Platform-tools folder from here on a easy access place to access on your PC
1.b - Edit Path Variable as shown here just be make things easier
2 - Enable USB debugging on watch by going to the watch Settings/System/About and pressing repeatedly on the Build Number until it says "you are a developer!"
2A. Go to Settings>Developer Options and turn on "ADB Debugging" and plug your watch cradle into your computer and wait until windows installs drivers (Win 7 found them automatically for me)
2.B - To check if the connection is well done between watch and PC open a command line on Windows and write "adb devices", it should show the watch SN listed
2.C - when your watch asks to allow connections, tap "always allow from this computer"
3 - Unlock the bootloader!
3.1 - Reboot to fastboot (via *adb command* (You do this by opening a command prompt window from within windows itself) "adb reboot bootloader")
3.2 - wait until the watch says "fastboot mode" then type command "fastboot oem unlock"
4 - Download STOCK ROM MWG68 images
5 - Place the unzipped files system.img boot.img and recovery.img into your downloads folder.
6 - Open a command prompt window and type "cd Downloads" to get to navigate into your downloads folder (Windows 7 default, 8 and 10 too I think) and then enter the following commands one at a time waiting for it to give a "completed" message before moving on
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot format userdata
fastboot reboot
7 - make factory reset on watch by... "unpair and reset" in the watch settings...
7.1 - Re-lock bootloader is advised. Repeat steps 2 through 3.1 and then "fastboot oem lock"
8 - Don't install AW 2.0 again?
Click to expand...
Click to collapse

How To Guide [OneUI 4.0 Beta 1 & 2](EXYNOS) Update.zip for S21 / Plus / Ultra - Download OTA Link

So, now that we have OneUI 4.0 Beta 1 rolling out to countries (ofc only 7), it has come so far in Germany & Korea (as far as I know). So the rest of the world wants an update.zip link, so don't be selfish and please, if you have one, capture the .bin file and share it in this thread.
How to capture:
I:
Install HTTP Canary app: https://m.apkpure.com/httpcanary-—-http-sniffer-capture-analysis/com.guoshi.httpcanary
1. Load canary
2. Start the update download but don't pause it.
3. Go back to canary and start that and it will grab the link.
(easiest method, by AndrzejDwo)
II:
Follow this: https://www.androidjungles.com/how-to-capture-ota-update-url-for-android/
If someone uploads it to the internet, you'll find the link/s in the second post in this thread.
[UPDATE] New link for the S21 Ultra (Exynos) - down on the second
[UPDATE2] You can watch a tutorial that I did back when OneUI 3.0 Beta was a thing on my S10 (the process is similar): YouTube
* This thread was made in order to centralise the update conversation / OTA links.

This is where I'll put the OTA /update.zip/ links for the S21 / S21P / S21U:
How To:
Rename [name].bin to [name].zip and paste it into the adb folder
Enable USB Debugging from the Developer Options
Reboot your phone
./adb start-server
Trust the computer
./adb reboot recovery
With vol-up and vol-down go to ADB Update and press the Side/Power button
./adb sideload update.zip
!!! Remove ./ if you're using Windows
!!! Obviously Google Pay and (possibly) other banking apps don't work
Download Links:
Galaxy S21: Link
Galaxy S21 Plus: ...
Galaxy S21 Ultra (Beta 1): http://fota-secure-dn.ospserver.net...WSA210914132817&px-wctime=2021-09-14 13:28:17 - From gashishpetim
S21 Ultra (Beta 2): Link

KokosTech said:
So, now that we have OneUI 4.0 Beta 1 rolling out to countries (ofc only 7), it has come so far in Germany & Korea (as far as I know). So the rest of the world wants an update.zip link, so don't be selfish and please, if you have one, capture the .bin file and share it in this thread.
How to capture:
Install HTTP Canary app: https://play.google.com/store/apps/details?id=com.guoshi.httpcanary
1. Load canary
2. Start the update download but don't pause it.
3. Go back to canary and start that and it will grab the link.
(easiest method, by AndrzejDwo)
If someone uploads it to the internet, you'll find the link/s in the second post in this thread.
* This thread was made in order to centralise the update conversation / OTA links.
Click to expand...
Click to collapse
The app is not in Google play.

vlubosh said:
The app is not in Google play.
Click to expand...
Click to collapse
Thanks, I updated the link

adamlee2012 said:
If we side load the update via ADB can we still register in the UK on Samsung members and receive future beta OTA or not?
Click to expand...
Click to collapse
Yeah I did that last year and the year before

vlubosh said:
The app is not in Google play.
Click to expand...
Click to collapse
it's there but seems to be region locked

adamlee2012 said:
If we side load the update via ADB can we still register in the UK on Samsung members and receive future beta OTA or not?
Click to expand...
Click to collapse
Well, I don't know, I don't have any experience with that, since I live in an unsupported region.

link to bin file here: https://forum.xda-developers.com/t/...ountries-how-to-install.4333281/post-85630907
For s21 ultra exynos

Sideloading through recovery: Using Android Debug Bridge (ADB)​
Make sure you have the latest version of ADB installed.
Rename the downloaded .bin package to update.zip.
Now reboot to the recovery mode. Inside the stock recovery environment, you can scroll down using the volume buttons and select an entry using the Power button.
Select apply update from ADB and connect the phone to the PC using a working USB cable.
In the Command Prompt/Terminal window, run the following command:adb devices
Wait to see that the daemon has started and that your device is found. Then run the following command:adb sideload PATH_TO_update.zip

Change the CSC, I have DBT and I don't want to lose it.

wh1t3w0lf said:
Sideloading through recovery: Using Android Debug Bridge (ADB)​
Make sure you have the latest version of ADB installed.
Rename the downloaded .bin package to update.zip.
Now reboot to the recovery mode. Inside the stock recovery environment, you can scroll down using the volume buttons and select an entry using the Power button.
Select apply update from ADB and connect the phone to the PC using a working USB cable.
In the Command Prompt/Terminal window, run the following command:adb devices
Wait to see that the daemon has started and that your device is found. Then run the following command:adb sideload PATH_TO_update.zip
Click to expand...
Click to collapse
You can just put the zip file in the same folder as the ADB then just do sideload update.zip

So, I added a how-to video (of OneUI 3.0 Beta on my S10 from "back-in-the-day") as well as the OTA link for the S21U. Don't forget to change .bin to .zip

Thank you for creating this thread @KokosTech !
I have one suggestion. Write which build can upgrade to which build. For example, like here.
I will be making a video guide on how to install via ADB as soon as possible and if I have your permission may I post it here?

BredzProh said:
Thank you for creating this thread @KokosTech !
I have one suggestion. Write which build can upgrade to which build. For example, like here.
I will be making a video guide on how to install via ADB as soon as possible and if I have your permission may I post it here?
Click to expand...
Click to collapse
No problem, the more info people have, the better.

BredzProh said:
Thank you for creating this thread @KokosTech !
I have one suggestion. Write which build can upgrade to which build. For example, like here.
I will be making a video guide on how to install via ADB as soon as possible and if I have your permission may I post it here?
Click to expand...
Click to collapse
yes and must important i think for all who try to update to beta one ui 4 must be on latest September patch example : for s21 ultra AUHD.

adamlee2012 said:
Thank you for this. I've done everything right I can think of but can't get it to install. Someone suggested renaming the file on pc but doesn't work. I get update.zip.zip
Click to expand...
Click to collapse
Do "cd C:\adb" and the "adb sideload update.zip"
Also, run CMD as admin if still doesn't work.

SD-card method ?

gois74 said:
SD-card method ?
Click to expand...
Click to collapse
nope , as s21 series no sd card man

Thanks for update zip
Worked perfectly

i cannot get ADB to sideload as well.. Status 5 error on the phone. I wonder if Samsung blocked it or its my PC?
i gave admin right already.

How To Guide Install One UI 5.0 (Android 13) beta on unsupported countries

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.