Develop Bugs

Rooting JB OTA from OS X (no flash counter)

The short story (links explain each step) of rooting your OTA updated JellyBean d2tmo from OS X (Mountain Lion in my case).
If you've installed Kies for Mac, you need to clean up
Install heimdall 1.4 (probably have to build from source)
You can download a binary as well.-0
Download root66_TMO_T999UVDLJA ROM (in my case)
Unpack the downloaded file. It's in 7z format. You can download Unarchiver for OS X
Get adb (platform tools addition to android sdk), and make sure it is in $PATH
Run the commands below after connecting to mac
The heimdall command to run:
Make sure your computer can see your phone:
Code:
adb devices
Code:
adb-kill-server
Flash the rooted image:
Code:
heimdall flash --primary-boot boot.img --cache cache.img.ext4 --system system.img.ext4
Finally, to install CWM Recovery, try id_twin's method (worked for me). A note on this: after installing the ROM Manager app from Play Store, the app doesn't realize that CWM Recovery is installed, so it wants to flash it again. I happened to let it -- but that upped the flash counter on the phone. I've resolved it using Triangle Away.

Does this work for jellybean?
Sent from my SGH-T999 using xda app-developers app

xxqbnxx said:
Does this work for jellybean?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
According to the topic of the thread, this is specifically for Jellybean.

Not sure how to build heimdall can someone be of help please?
Sent from my SGH-T999 using xda app-developers app

xxqbnxx said:
Not sure how to build heimdall can someone be of help please?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Are you on OS X? Which version, if so?

OS X 10.6.8
Sent from my SGH-T999 using xda app-developers app

I wound up downloading a 1.4 binary for OSX, which I found on wikiDOTcyanogenmodDOTorg/index.php?title=Install_CM_for_galaxysmtd . Please try that and let me know how it goes (it worked for me (TM)).
PS The outside link restriction, while understandable, is a bit silly.
xxqbnxx said:
OS X 10.6.8
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse

alecsharp said:
I wound up downloading a 1.4 binary for OSX, which I found on wikiDOTcyanogenmodDOTorg/index.php?title=Install_CM_for_galaxysmtd . Please try that and let me know how it goes (it worked for me (TM)).
PS The outside link restriction, while understandable, is a bit silly.
Click to expand...
Click to collapse
Hey thanks for all your help man. I went and tired to build heimdall but i need xcode? do i ? i tired installing xcode took 3 hours to download and then i went to install it and it was going to take 4 hours to install. i thought that was to much and i might be doing something wrong. Sorry but as you can tell i am a Noob on this here. What am i doing wrong ?

xxqbnxx said:
Hey thanks for all your help man. I went and tired to build heimdall but i need xcode? do i ? i tired installing xcode took 3 hours to download and then i went to install it and it was going to take 4 hours to install. i thought that was to much and i might be doing something wrong. Sorry but as you can tell i am a Noob on this here. What am i doing wrong ?
Click to expand...
Click to collapse
Hi! If you download heimdall from that link I posted into the cyanogen wiki, you don't need to build/compile it. That download is precompiled, so all you have to do is the following:
Go to wikiDOTcyanogenmodDOTorg/index.php?title=Install_CM_for_galaxysmtd <--- replace DOT with a . of course -- heimdall is independent of the type of phone you have, so don't worry that that page is for Galaxy S.
Download the heimdall 1.4rc1 zip file for OSX on that page. <-- Look for "
Code:
Mac OS X:
Heimdall Suite 1.4RC1 Command-line Binary: download
on that page.
Unpack the downloaded zip file, to find two files.
Copy 'libusb-1.0.0.dylib' to the /opt/local/lib directory on your Mac
Copy the file called 'heimdall' into /usr/local/bin <-- after you copy it over, in a terminal do: sudo chmod 644 /usr/local/bin/heimdall to make sure you can run it.
then you can just run heimdall (no front-end, just the command line tool) <-- see my original post up there for exactly how to do that.

OK thanks I'm going to have to wait for Monday to try this
Sent from my SGH-T999 using xda app-developers app

ok so after some work arounds i think i got it all set up. heimdall seems to be running on terminal. How safe is this ?

xxqbnxx said:
ok so after some work arounds i think i got it all set up. heimdall seems to be running on terminal. How safe is this ?
Click to expand...
Click to collapse
Well, considering what heimdall does, it's an inherently risky venture whether or not you have a GUI on it. The GUI lets you limit the amount of damage you can potentially do, of course, whereas the CLI is not as restrictive.
As far as those commands: I've run them on a couple of phones to successful ends. YMMV, of course.

im stuck i donwload the heimdall and the md5 file
but im stuck here
Copy 'libusb-1.0.0.dylib' to the /opt/local/lib directory on your Mac
Copy the file called 'heimdall' into /usr/local/bin <-- after you copy it over, in a terminal do: sudo chmod 644 /usr/local/bin/heimdall to make sure you can run it.
i dont have those folders
maybe im over looking this but can someone write a simpler tutorial?
no pun intended! maybe its just me, ive been googling how to root my s3 on a mac for so long!

Did you try this from the command line or Finder? If in Finder, did you try searching for those directory names?
beto0216 said:
im stuck i donwload the heimdall and the md5 file
but im stuck here
Copy 'libusb-1.0.0.dylib' to the /opt/local/lib directory on your Mac
Copy the file called 'heimdall' into /usr/local/bin <-- after you copy it over, in a terminal do: sudo chmod 644 /usr/local/bin/heimdall to make sure you can run it.
i dont have those folders
maybe im over looking this but can someone write a simpler tutorial?
no pun intended! maybe its just me, ive been googling how to root my s3 on a mac for so long!
Click to expand...
Click to collapse

OK... I had problems then I fixed them and then I found some more problems.
Here is what I receive:
Code:
$ heimdall flash --primary-boot boot.img --cache cache.img.ext4 --system system.img.ext4
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http : // www glassechidna com au /
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http : // www glassechidna com au / donate /
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
I didn't have any Kies kext's loaded as this is what I get:
Code:
$ kextstat | grep -v apple
Index Refs Address Size Wired Name (Version) <Linked Against>
126 2 0xffffff7f81e95000 0x36000 0x36000 org.virtualbox.kext.VBoxDrv (4.1.18) <7 5 4 3 1>
128 0 0xffffff7f81ed3000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (4.1.18) <126 7 5 4 3 1>
129 0 0xffffff7f81ed8000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (4.1.18) <126 5 4 1>
My process:
1. Phone -> Download Mode
2. Open Terminal
3. CD to the folder with all of the system files to be flashed
4. Run, verbatim, exactly what you said to run in OP
Any ideas?

Hi, basically that interface is busy and occupied by another process. Did you try unloading the Kies kexts anyway?
jhlax95 said:
OK... I had problems then I fixed them and then I found some more problems.
Here is what I receive:
Code:
$ heimdall flash --primary-boot boot.img --cache cache.img.ext4 --system system.img.ext4
Heimdall v1.4 RC1
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http : // www glassechidna com au /
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http : // www glassechidna com au / donate /
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!
I didn't have any Kies kext's loaded as this is what I get:
Code:
$ kextstat | grep -v apple
Index Refs Address Size Wired Name (Version) <Linked Against>
126 2 0xffffff7f81e95000 0x36000 0x36000 org.virtualbox.kext.VBoxDrv (4.1.18) <7 5 4 3 1>
128 0 0xffffff7f81ed3000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (4.1.18) <126 7 5 4 3 1>
129 0 0xffffff7f81ed8000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (4.1.18) <126 5 4 1>
My process:
1. Phone -> Download Mode
2. Open Terminal
3. CD to the folder with all of the system files to be flashed
4. Run, verbatim, exactly what you said to run in OP
Any ideas?
Click to expand...
Click to collapse

alecsharp said:
Did you try this from the command line or Finder? If in Finder, did you try searching for those directory names?
Click to expand...
Click to collapse
I'm having the same problem.... i cant find any of those folders, and nothing comes up searching for each individual one in the finder. I then tried to type in the adress to the command line and it said directory could not be found. What am i missing here?

OSX Developer tools
fred8785 said:
I'm having the same problem.... i cant find any of those folders, and nothing comes up searching for each individual one in the finder. I then tried to type in the adress to the command line and it said directory could not be found. What am i missing here?
Click to expand...
Click to collapse
Do you have XCode installed?

alecsharp said:
Do you have XCode installed?
Click to expand...
Click to collapse
i do.....

fred8785 said:
i do.....
Click to expand...
Click to collapse
Thanks for verifying. Do you use homebrew at all? If not, can you install it and then run:
Code:
brew install libusb
That should create /usr/local/bin and /usr/local/lib directories. Use /usr/local/lib instead of /opt/local/lib at that point.

[Q] Android Tool kit for Galaxy note 2

Hi there.
Apparently I can't post this under galaxy note II android development (due to the low number of posts) so I have no choice but to ask you here instead.
I have myself a GT N7105 version of the samsung galaxy note 2. I'm trying to use the android tool kit to root my phone. However after choosing my Recovery option and superuser method, it says creating tar file to flash ..
tools\tar: boot.img: could not create file: permission denied
tools\tar: error exit delayed from previous errors
tools\tar: recovery.img: could not create file: permission denied
tools]tar: error exit delayed from previous errors
IZArc Command Line Compression Add-On Version 1.1 <Build: 130>
Copyright <c> 2007 Ivan ......
archive file: boot-insecure-dll1-recovery-n7105.tar
adding: boot.img ok
adding: recovery.img ok
1 file<s> moved.
Click to expand...
Click to collapse
and it got stuck there.
it doesn't show me any instructions after that .
I used the original stickied android tool kit thread in the GT N7105 android development forum (http://forum.xda-developers.com/showthread.php?t=2052779) , I watched the video in the 4th post (step by step guide on what to do). in the video, something else appeared after the last sentence "1 file<s> moved" and it asks him to plug it in with USB debugging mode enabled.
Any idea what I should do? Do take note what I said above doesn't always appear. Usually only the first part appears i.e. this
tools\tar: boot.img: could not create file: permission denied
tools\tar: error exit delayed from previous errors
tools\tar: recovery.img: could not create file: permission denied
tools]tar: error exit delayed from previous errors
Click to expand...
Click to collapse
_______________________________________________
If you wanted to know what I did before this,
I flashed my note 2 back to it's stock rom following the instructions in this site (http://www.smartphonejam.com/2012/1...te-2-Back-to-Original-Stock-ROM-Firmware.html) -> basically just using Odin to flash to stock rom.
As the GT N7105 stock rom wasn't up for download there, I downloaded it off here -> http://forum.xda-developers.com/showthread.php?t=2032849 .
I used this one N7105XXDLL7 N7105OLBDLL2 - Download - Singapore 2012 December.
________________________________________________
Any idea what I should do to get permission to create the tar file? Maybe I flashed the wrong stock rom using odin ? Thanks.
p.s. I know how to root my phone using other methods but I want to try out this one so if you are not going to give me constructive feedback then I don't need your reply here. Thanks (;

http://download.chainfire.eu/255/CF-Root/CF-Auto-Root/CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip
Flash via pc odin 3.07
Sent from my GT-N7100 using xda app-developers app

[Q] How to root SM-T113 ?

Hello, i have one question.
I have a Samsung Galaxy Tab 3 7.0 ( SM-T113 ) i can't find any rom and root package for my pad.
Maybe someone can help me?

I support this request. The T113 is a new device. I was thinking of getting me a cheap t110, but the t113 is also cheap. If it would be possible to root this I would take it.

Rooting SM-T113
Hello everybody
I struggled to root my Samsung Galaxy Tab 3 Lite
(SM-T113). So I decided to shared my experience and writing this tuto.
Of course, this is "a non standart" device, and elements for rooting
SM-T110 or SM-T210 didn't work. Android version of this device is 4.4.4
Methodology and tries :
I have proccured myself the Samsung official firmware (here). This image
allow me to get back during beetwen the experimentations. I tried several
experimentation and restore the device after each fail.
Installing with Odin the Clockworkmod (CWM) for SM-T110 , for SM-T210, and
SM-T211. (Has preconnised here) Each time, when loading the CWM, I got a little
(1 ascii character) exclamation mark at the top-left of the screen. The device
didn't boot on recovery
Installing with Odin the (TWRP) for SM-T110. Same symptom
Installing philz_touch : against the message with only the red exclamation
mark.
I conclude of checked of some signature before executing recovery.
Using Kingo root application : software try to root during 20 minutes and
finaly fail.
Using Towel root application : The device isn't reconized
Conclusion: Security breach for rooting have been fixed in this version of android
I have downloaded UPDATE-SuperSU-v2.46 for android. The idea is to push this
application by the standart android update way. (native recovery).
Sending the zip archive 'as is' => failure to check the whole archive
Re-sign the archive with the autosign tools => failure to check footer of archive
Rewriting the update-script (see here) and (here) and auto-sign the archive
: failure to check footer
I am procured myself some pre-rooted image. Odin fail to import them. (and I
have no succed to use heimdall for linux on my debian)
I have try to improve the official samsung Image by adding root manually , using
simg2img and make_ext4fs. Odin fail at the same point
It's remaining me two way : Or I try to generated a correct update file, or I
try to understood why odin fail to import prerrooted system and my custom
image. I choosed the second option.
The offical update is splited by several blocks, each block having is own
header. A master header provide global information about the image (number of
blocks, size, ...). I have putting some spies in simg2img and
observate the headers of official update and of my custom uptate. Result is
surprising : It is missing 4 bytes by headers. in custom update. According to
samsung orginal update, missing values seem to be constant. I suppose it's a 'magic
number', checked by the device to be sure the 'good' update is applied. So I
modifed this headers in make_ext4fs for adding the missing constants. My custom update is now
accepted by my devices, and I got root (!)
I will now describe how to generate and import this update.
DISCLMAIMER
I or Xda-developers are not responsable of any damage one your device, in particular if you bricked it
You waranty will probably void
Rooting device may lead to some dysfonctionnement, or may open some security breach. You are the only responsable.
1. What do you need :
Your device, and a cable to connect it to your PC
A Windows distribution, with Odin (www (dot) samsungodindownload (dot) com/) and the samsung drivers (www (dot) samsung (dot) com/us/support/owners/product/SM-T110NYKAXAR#")
A Linux distribution, with the appropriate compilation package (build-essential), and with git.
A way to transfers big files beetwen your Linux and your Windows.
The Official samsung update (best-tech-reviews (dot) com/update-sm-t113-t113xxu0aoa4-android-4-4-4-2152 or rapidgator (dot) net/file/7140bfdc421eea86eda5a5cbca00216e)
The UPDATE-SuperSU-v2.46 in zip format (download (dot) chainfire (dot) eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1") (or root program for your android)
Method assume you never installed root on your device
2. Generate the update
Uncompress the Samsung official image.
Code:
unzip image_official.zip
tar -xf image.tar.md5
Uncompress and make_ext4fs and simg2img (here)
Code:
cd ..
git clone https:// github.com/YuLaw/ext4-utils.git
cd ext4_utils
Download and applied the patch (see attachment)
Code:
patch -p1 < ../patch_ext4_utils.diff
Build ext4_utils
Code:
make
Extract the image
Code:
cd ..
unzip DBT-T113XXU0AOA4-20150121104149.zip
tar -xf T113XXU0AOA4_T113OXA0AOA4_HOME.tar.md5
ext4_utils/simg2img system.img system.img.raw
Mount the image
Code:
mkdir mount_point
sudo mount -o loop,rw system.img.raw mount_point
unzip the UPDATE-SuperSU-v2.46
Code:
mkdir UPDATE-SuperSU-v2.46
mv UPDATE-SuperSU-v2.46.zip UPDATE-SuperSU-v2.46/
cd UPDATE-SuperSU-v2.46/
unzip UPDATE-SuperSU-v2.46.zip
cd ..
Now, copy common file and armv7 one the mount_point. If you use an other
device, replace the armv7 repository by the appropriate repository according
to your device processor. You can refer to the
UPDATE-SuperSU-v2.46/com/google/android/update-binary to find them.
Code:
sudo cp UPDATE-SuperSU-v2.46/armv7/{su,supolicy} mount_point/xbin
sudo cp UPDATE-SuperSU-v2.46/armv7/su mount_point/xbin/daemonsu/
sudo cp UPDATE-SuperSU-v2.46/armv7/libsupol.so mount_point/lib
sudo mkdir mount_point/etc/init.d
sudo cp UPDATE-SuperSU-v2.46/common/99SuperSUDaemon mount_point/etc/init.d
sudo cp UPDATE-SuperSU-v2.46/common/Superuser.apk mount_point/app
sudo mv mount_point_app/etc/install-recovery.sh mount_point/etc/install-recovery.bak
sudo cp UPDATE-SuperSU-v2.46/common/install-recovery.sh mount_point/etc
sudo chmod 0755 mount_point/xbin/daemonsu
sudo chmod 06755 mount_point/xbin/su
sudo chmod 0755 mount_point/xbin/supolicy
sudo chmod 0644 mount_point/lib/libsupol.so
sudo chmod 0755 mount_point/etc/install-recovery.sh
sudo chmod 0744 mount_point/etc/init.d/99SuperSUDaemon
sudo chmod 0644 mount_point/app/Superuser.apk
We will regenerate the file system. Do not umount them. If patch on
ext4_utils is not applied, you shall applied it now.
Code:
mkdir output
sudo ext4_utils/make_ext4fs -s -a system -l 1500M output/system.img mount_point
cd output
tar -cf system.img system.img.tar
md5sum -t system.img.tar >> system.img.tar
mv system.img.tar system.img.tar.md5
You can now transfert this file to your windows operating system.
3. Android prepartion
You must ensure your device is allowed to install apk from untrusted source. See
in option/application or in developper menu option
Connect the android to you pc.
Boot your android device into downloading mode. On SM-T113 Samsung galaxy Tab3 lite,
press power, volume down and pad when booting.
Run odin, ensure Repartion is NOT checked, and select the AP (PDA) button. (The
only checked case is autoreboot and F.Reset time) Load the previously generated
file and click start.
Your android device may now reboot and install the root application.
Congratulation, you have now rooted your device. You can clean up the downloaded files.
4. One of these step fail, what I can do to come back. :crying:
You may import with odin the official samsung firmware or proceed to a factory return from the recovery.
5. May I eat my devices if I can't root it ?
Samsung user manual say to not do it.

samsung tab 3 sm-t113 root
Thank for the update about for the root. But I don't have Linux and I don't know how to use Linux too. It's there a way without Linux

If you don't have linux, you can try using Cygwin. This is a linux like environment running on Windows.
or if you find my solution is too complicated, I do it for you.
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
https://drive.google.com/file/d/0Bwao3SgtdOPPYm9XNF8wQXEyWjg/view?usp=sharing
unzip file and upload it to you device with Odin
Nb: This file will remain on my google drive until I need space or until I decide to remove it. (in a long time)

grizzlyfute said:
If you don't have linux, you can try using Cygwin. This is a linux like environment running on Windows.
or if you find my solution is too complicated, I do it for you.
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
unzip file and upload it to you device with Odin
Nb: This file will remain on my google drive until I need space or until I decide to remove it. (in a long time)
Click to expand...
Click to collapse
Thank you for your great work!!
Do you think the package will work also with Tab3 lite SM-T116? (Sm-t116 should have only the 3g module more than sm-t113)

Root Worked
Thanks for the your great effort grizzlyfute.
Worked perfectly and finally got my device rooted

beodev said:
Do you think the package will work also with Tab3 lite SM-T116? (Sm-t116 should have only the 3g module more than sm-t113)
Click to expand...
Click to collapse
No. Package will erase the system partition, including configuration file (/system/etc), and probably some drivers. Importing the SM-T113 package will probably put the 3G module out of service.
I suggest you to procure an 'official firmware' for your device (see in Settings/about for the exact version) and follow procedure in post#3.

grizzlyfute said:
No. Package will erase the system partition, including configuration file (/system/etc), and probably some drivers. Importing the SM-T113 package will probably put the 3G module out of service.
I suggest you to procure an 'official firmware' for your device (see in Settings/about for the exact version) and follow procedure in post#3.
Click to expand...
Click to collapse
I tried to follow your linux-instructions (by using cygwin, with an official sm-t116 firmware), but something go wrong (i think cygwin doesn't know batch commands like "sudo", or "su" etc..).
I put your md5 file to my sm-t116: the results is that the device is rooted, but no network connection works (Wi-Fi too) .
I jump back to the original firmware, maybe in the future someone will develop the firmware for the sm-t116 version.
Thank you for the Help

Thanks buddy! It works! :good:
Just got my t113 today and now rooted. Awesome!

Light at end of tunnel
grizzlyfute said:
...
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
https://drive.google.com/file/d/0Bwao3SgtdOPPYm9XNF8wQXEyWjg/view?usp=sharing
unzip file and upload it to you device with Odin
...
Click to expand...
Click to collapse
FABULOUS!!! And thank you! And have i said fabulous? And thank you??? And this, only for giving me rooting hope!
I am a proud user of a gt-i9100 for a few years, rooted/unlocked/custom rom(ehndroix), so, all the 9 miles, but, that´s the phone... And since i am not very proficient when it comes to using odin, and if you don´t write all the steps, i am like a fish out of water (can´t breathe or swim) and i am afraid to do some wrong step.
So, when you say upload it to your device, which will be the parameters in ODIN?
Edit: I confirm, it works, i was afraid of doing something wrong and brick the thingy, but its working fine, thanks to odin and pda and this developpers work!:victory:
!! Thanks !!

I followed these instructions step-by-step on my SM-T113, but for some reason the device would always fail to receive the image I'd built (Odin would just sit there saying NAND Write Start! for a while, then fail. So I tried downloading your precompiled version... and what do you know, it worked straight away.
Thanks a ton, HUGE help!

(q)how to root tab sm-t116nu ?
please help me

cjmac said:
I followed these instructions step-by-step on my SM-T113, but for some reason the device would always fail to receive the image I'd built (Odin would just sit there saying NAND Write Start! for a while, then fail. So I tried downloading your precompiled version... and what do you know, it worked straight away.
Thanks a ton, HUGE help!
Click to expand...
Click to collapse
Sorry for the delay.
I encountered the same problems before I make the patch. Cause of the problem is the file generated by ext4_utils tools is not immediately compatible with the sm-t113 device. I have to add constants in the encapsulation headers for the device to accept the file. You can see details in the patch provided.
To determine theses constants, I put some spies in simg2img and extracts the official firmware. It is not exclude these values change in function of the device.
For the sm-t116, I suggest to open an other thread. I think the works can be picked up and adapted.

wifi issues?
Thanks for your work!
I have successfully rooted my tablet, but its now not connecting to a weak wifi signal it was previuosly connecting to. In fact, it previuosly rratd the same signal as "fair".
Is this connected in any way to the rooting package, and can be resolved somehow?

Hello, thanks for your help! now, i have my Samsung SM-T113 rooted.
but, there any way to put the cmw?
I want to make a backup image and not as .... thanks

Anyone know if this way working in model SM-T113NU ?

Samsung official image ?
grizzlyfute said:
2. Generate the update
Uncompress the Samsung official image.
Click to expand...
Click to collapse
I don't understand what is the "Samsung official image" :
i don't see it neither in the 1. What do you need : list , nor in attached files
I thought it could be "The Official samsung update ", but its name is not "image_official.zip" I see in the first line of code, and moreover I see "unzip DBT-T113XXU0AOA4-20150121104149.zip" in the following lines.

any chance to make more easy the way to get root? btw I have the variant SM-T133NU 4.4.4 KK please!

Minimalistk0 said:
any chance to make more easy the way to get root? btw I have the variant SM-T133NU 4.4.4 KK please!
Click to expand...
Click to collapse
I second that! Rooted custom rom highly appreciated! I'd even pay some bucks

[ROOT]G955U/G955U1 SnapDragon SamPWND Root IS HERE!

FINALLY!
We Present To You
SamPWND!
Root for the USA Variants of the S8 & S8 Plus Devices!
(This thread will focus only on the S8+)
This thread had been closed/locked until further notice. The thread and links should remain active and the thread has served it's purpose. You will need to search the thread if you have any questions pertaining to root or any errors/issues that you are facing. The other reason I have decided to close the thread is because it has gone off topic one too many times, people like to argue and debate and MODS have had to come in here 1 too many times to clean it up so as to make life easier, I will just shut it down. Please do not bombard me with PM's for root assistance because if it has been answered in this thread already (and it most likely has) I will just direct you to search in the thread if I am able to respond at all.
ALSO, please do not utilize our firmware/root files/method without gaining permission first or I will ask for the thread to be removed/locked. Just because the thread gets closed does not mean we didn't spend a lot of time to get to this point.
Thank you and enjoy SamPWND root!​
DISCLAIMER:
We are not responsible for any damage done to your device as no one is "forcing" you to root your phone! If you are not sure of how to follow instructions or use ADB then I would suggest waiting for someone to help you or that you read up on how these things work before diving head first. The ENG system is not very stable when it comes to root as well as it has a ton of tools and binaries not available on stock devices so we are not responsible if you break something while on any firmwares but especially while on the ENG firmware.
DISCLAIMER 2:
Please do not take our work and post it elsewhere. We spent a lot of time on this for people to take it and use it as if it is their own. With that being said, if you have a better process for something or find any issues/errors, please PM myself or one of the listed contributors of this root method, do NOT post it directly in the thread because it causes confusion. We know with 100% certainty the files and method presented WORK. If it is not working for someone there are a number of possible reasons why. If users start modifying our files/scripts and posting them and you decide you are going to use someone else's files/scripts, do not post in our threads asking for us to help you because we will have no idea what was modified or changed and will just tell you to use the original files.
Returning to Stock:
- It is possible to return to 100% stock and it is very EASY to do.
- This is the reason why I provide both Normal, and Comsey ODIN's.
- All you need is a full stock 4 files firmware of your choice.
- Extract those files. Open ODIN and select the 4 files in their respective slots.
* IF YOU GET ERRORS such as model mismatch, start with 1 partition at a time to find out which one is throwing the error. (In my experience, it is the BL file that causes the error.) Once you find the culprit, throw that partition into the other ODIN. (For example, the BL file is giving an error in Comsey ODIN, throw the BL file in NORMAL ODIN and flash it by itself.)
* Typically you might have to throw individual partitions into either of the ODIN's but in the end you will be back on full stock firmware.
What doesn't work while rooted?
- On ANY ROOTED device, anything that utilizes "SafetyNet" will NOT work.
- Magisk and/or SuHide will NOT work. Our bootloader is still locked and these two modify the boot.img which would cause our devices to not boot up and having to start the root process over again, you have been warned!
- Systemless root also does NOT work. Again, this patched the boot.img which we cannot do because of our locked bootloader.
- Battery currently only charges to 80%. There are a few that feel it legit doesn't charge fully but others are claiming they get the same amount of life as they did with a 100% battery so the 80% might just be a visual issue or "fake" when it is really at 100%. Either way, we are still looking into this.
Main Contributors:
@elliwigy
@Harry44
@akiraO1
@BotsOne
@GSMCHEN
@jrkruse (for uploading system.img.ext4 and his root zip for the part 2 instructions)
@V0idst4r (for help in creating a "1 click" method for part 1!)
Initial Description on the process:
We are essentially flashing a modified 4 file firmware package in ODIN and then utilizing a few binaries in conjunction with SU binary and a permissive kernel. We will then be running some ADB commands and in order to have a fully working, amazing root with all things working we will be utilizing a stock system.img & a root script in conjunction with Flashfire. If you want to know all the technical details, you can take apart the files if you would like. It is released, so it is no longer a secret!
PART 1 Instructions: NEW
Flashing SamPWND 4 Files Firmware:
1) Download the PART 1 FILES Listed Below (this includes SamPWND_Root.zip and Initial ODIN 4 Files FIRMWARE and ODIN's if you do not already have them.)
2) Extract the 4 Files ODIN Firmware Package (also extract the ODIN's if you do not have them already.)
3) Open Comsey ODIN and select each partition and then select the files from the 4 File Firmware Package you extracted (BL goes in BL slot, AP in AP, CP in CP & CSC in CSC.) The options you select in ODIN shouldn't matter but I typically select F. Reset Time, Auto Reboot, Re-Partition, Nand Erase All & Update Bootloader.
4) Press Start and Wait for it to Finish. Once it finishes, if it boots into stock recovery simply select "Reboot System"
Take a breather, the ODIN portion is done (unless you have to start over for some reason...)
Now the NEW Root Process:
1) Once the phone is booted up, make sure you have ADB Enabled and connected to your PC. It should have prompted you to accept USB debugging as soon as it booted up.
2) Unzip the SamPWND_Root.zip
3) Double click "step1"
4) Wait for it to finish and once it reboots and comes back on you will be rooted with SuperSU!
5) Continue to PART 2 for "EVEN BETTER ROOT"
* It is a Windows bat file so not sure if it works on MAC. If you can't run bat files, use the OLD instructions.
* The bat will take about 30 seconds to run it's course. This is due to giving enough time for the remount script to mount the system as RW.
PART 1 Instructions: OLD
1) Download the PART 1 FILES Listed Below (this includes Systemroot + ADB zip, Initial ODIN 4 Files FIRMWARE and ODIN's if you do not already have them)
2) Extract the 4 Files ODIN Firmware Package, Also extract the ODIN's if you don't have them already.
3) Open Comsey ODIN and select each partition and then select the files from the 4 File Firmware Package you extracted (BL goes in BL slot, AP in AP, CP in CP & CSC in CSC.) The options you select in ODIN shouldn't matter but I typically select F. Reset Time, Auto Reboot, Re-Partition, Nand Erase All & Update Bootloader.
4) Press Start and Wait for it to Finish. Once it finishes, if it boots into stock recovery simply select "Reboot System"
Take a breather, the ODIN portion is done (unless you have to start over for some reason...)
Now the ADB Process to actually Root:
1) Extract the Systemroot + ADB zip listed below in an easy to find directory.
2) Make sure phone is connected to PC and ensure USB Debugging is enabled.
3) In the folder you extracted, you should see a "cmd-here" file. Double click it and it should open up an ADB cmd window.
4) Now we will start with the ADB commands:
- Type
Code:
adb push systemroot /data/local/tmp
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb push systemroot /data/local/tmp
/data/local/tmp/systemroot/: 8 files pushed. 0 files skipped. 10.0 MB/s (7072263 bytes in 0.673s)
- Type
Code:
adb shell chmod -R 7777 /data/local/tmp
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb shell chmod -R 7777 /data/local/tmp
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>
- Type
Code:
adb shell setsid su
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb shell setsid su
(It will be blank with the blinking cursor, move to next step)
- Type
Code:
id
(you should at this point see that your are in a root shell!)
What it will look like:
id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
- Type
Code:
echo /data/local/tmp/systemroot/remount2.sh > /sys/kernel/uevent_helper
What it will look like:
echo /data/local/tmp/systemroot/remount2.sh > /sys/kernel/uevent_helper
(Again, it will be blank with a blinking cursor after you type the command in, move to next step)
- WAIT ABOUT 30 SECONDS BEFORE MOVING TO THE NEXT COMMAND
- Type "
Code:
mount
" (you should now see rw next to rootfs and system partitions)
What it will look like:
mount
(After we type in mount, we are looking for the below two items to say rw like they do in the next two lines)
rootfs on / type rootfs (rw,seclabel,size=1586716k,nr_inodes=396679)
/dev/block/sda19 on /system type ext4 (rw,seclabel,relatime)
- Type
Code:
sh /data/local/tmp/systemroot/root.sh
What it will look like:
sh /data/local/tmp/systemroot/root.sh
rm: /system/bin/install-recovery.sh: No such file or directory
cp: /system/bin/.ext/.su: No such file or directory
chmod: /system/bin/.ext/.su: No such file or directory
chcon: /system/bin/.ext/.su: No such file or directory
touch: '/data/.supersu': Permission denied
/data/local/tmp/systemroot/root.sh[55]: can't create /data/.supersu: Permission denied
chmod: /data/.supersu: No such file or directory
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot\NEWSAMPWNDFILES>
5) If you followed all of the above commands to the T, your device will reboot and you will have SuperSU installed.
6) Install Flashfire from the Play Store.
7) Up to this point, you are on an ENG system.img with root that doesn't function the way we would like it to. This means you will feel a vibrate every time you try to gain SU access as well as it will take quite a while for an SU prompt. You can stay on this root if you would like to experiment with the ENG system, but outside of that I would HIGHLY recommend you proceed to the STEP 2 PROCESS.
PART 2 Instructions:
1) Download the PART 2 FILES listed below (this includes the system.img.ext4 and the add CSC Systemroot zip both provided courtesy of @jrkruse , view post #195 for specifics on what these are but essentially they are stock QD2 system.img and the zip has multi CSC, root, and a bunch of other goodies!)
2) Extract the System.img.ext4 zip and place that actual "system.img.ext4" onto the Internal SD Card (might work from external but some users have reported issues with chainfires root.zip and FF with external sd cards, this is not a fault of the SamPWND files/process.)
3) Place the entire Add CSC Systemroot zip onto Internal or Externdal SD Card (THIS FILE DOES NOT NEED TO BE UNZIPPED, THROW THE WHOLE ZIP FILE ONTO SD CARD OR INTERNAL)
4) Open Flashfire and grant it root when it prompts you. IF FLASHFIRE IS NOT LOADING FILES AND YOU JUST SEE A CIRCLE OR LIKE ITS CONSTANTLY LOADING, PUT THE PHONE IN AIRPLANE MODE AND THEN GO BACK INTO FLASHFIRE AND THE FILES SHOULD NOW APPEAR.
5) Press the + sign and select "Flash Firmware Package" & navigate to where you placed the system.img.ext4 and select it
6) Press the + sign and select "Flash ZIP or OTA" & navigate to where you placed the Add CSC Systemroot zip and select it, select Mount System as r/w
7) Press the + sign and select "Wipe" and select System data, 3rd party apps, Dalvik cache, Cache partiton, Cache Partiton format
8) Now, long press on "Wipe" and make sure it is on the top by dragging it. The order should be Wipe, Flash Firmware Package & finally Flash ZIP or OTA
9) Make sure the "Everoot" is disabled!
10) Flash away!
If you followed all of PART 1, then followed all of PART 2, then you will be updated to QD2, rooted with busybox (and have some other goodies) and the phone will be running great! Root will be stable and snappy as ever. Adaway, Root Checker, V4A etc. etc. are now all possible.
XDA:DevDB Information
S8 Plus SamPWND ROOT, ROM for the Samsung Galaxy S8+
Contributors
elliwigy
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 7.0, Any Current Firmware
Based On: Stock Touchwiz
Version Information
Status: Beta
Current Stable Version: 1
Stable Release Date: 2017-08-19
Current Beta Version: 1
Beta Release Date: 2017-08-19
Created 2017-08-19
Last Updated 2017-08-19

DOWNLOADS SECTION:
PART 1 FILES:
SamPWND_Root.zip
https://mega.nz/#!8YcgTSwI!hIfbdJZ466sr1AyfiHLdtr1p-To0QdthTPDmVwtv0dc
Initial ODIN 4 Files FIRMWARE
https://mega.nz/#!5cUjnCwK!Zgw5_CaINbES08gwDzl7yMN0N4nzm56Fa12ow-gppKA
Mirror: https://www.androidfilehost.com/?fid=961840155545589828
AFH MD5: 73720c409782b751355b9443a003a6e8
Normal + Comsey ODIN
https://mega.nz/#!cFN2DD4C!I7AT4TgNSzBp7Py0UhC7pHZ0M4WDQhEC5qj2xD_qluM
Systemroot + ADB zip - OLD
https://mega.nz/#!1MVDhZxQ!Wd4Umvju1sS1DAe-jBcTue9NKSJ4co0I2gwiyC3c2pE
PART 2 FILES: (Potentially will be providing a rom.zip soon that will have latest updated U1 with multi CSC pre-rooted with other goodies)
system.img.ext4
https://www.androidfilehost.com/?fid=817550096634794132
Add CSC Systemroot
https://www.androidfilehost.com/?fid=745425885120757028
For more info on these files please see @jrkruse post located here:
https://forum.xda-developers.com/showpost.php?p=73489978&postcount=925
THANK HIM WHILE YOU'RE AT IT!

@elliwigy @Harry44 @akiraO1 @BotsOne
These months these four people are very hard, and I very relaxed!! lol

Cool Job!

GSM CHEN said:
@[email protected]@[email protected]
These months these four people are very hard, and I very relaxed!! lol
Click to expand...
Click to collapse
haha but we know it wouldnt be possible without you man

Dam it, if I wasnt drunk, and tired, I eould vet myself out of bed and do this now, lol. Thanks for all your hard work.
One thing i would suggest would be to either put the commands that need to be typed in as bold face type or im not sure if its possible on here, as im on my phone atm, but there are Code/code tags avaiable that will make them easier to copy and paste.
Again, thanks for this......I did not think it was going to be possible. This will be my morning present when i wake up, feels like Xmas.......

theboz1419 said:
Dam it, if I wasnt drunk, and tired, I eould vet myself out of bed and do this now, lol. Thanks for all your hard work.
One thing i would suggest would be to either put the commands that need to be typed in as bold face type or im not sure if its possible on here, as im on my phone atm, but there are Code/code tags avaiable that will make them easier to copy and paste.
Again, thanks for this......I did not think it was going to be possible. This will be my morning present when i wake up, feels like Xmas.......
Click to expand...
Click to collapse
to be honest its late haha, threw it together lol ill try to tidy it up when i get time lol

Awesome can't wait to try this out soon!

elliwigy said:
to be honest its late haha, threw it together lol ill try to tidy it up when i get time lol
Click to expand...
Click to collapse
You are forgiven, lol. I figured it would be out in the morning, just not this early in the morning.
You guys should have gotten some sleep you may need it after this weekend.

What a nice thing to wake up to when I'm getting ready to head to work at 530 in the morning lol. Can't wait to give this a shot once I get off work 12 hours later. Thanks for everything devs.

S8 thread will be posted tomorrow, too late to do it tonight

You guys are the ****. Thanks for all of your hard work.

Just want to know if Knox will be triggered or not? Please also add this to the first post [emoji397]

Where's the best place to get the stock firmware we might need just in case? As far as best download speed etc.

Wow,. I honestly didn't think it was possible. Amazing accomplishment ellwigy.
Sent from my SM-G955W using XDA-Developers Legacy app

powerstroke said:
Where's the best place to get the stock firmware we might need just in case? As far as best download speed etc.
Click to expand...
Click to collapse
I got mine here... Took awhile to download... Someone gave me the link in the 955U1 thread
http://updato.com/firmware-archive-select-model?record=F6B451FD73EE11E7963AFA163EE8F90B
Also do we need to back up our EFS/Imei stuff? I know its recommended when flashing roms in recovery but our bootloader is locked.... Is there a way to back up without root?
Edit* I asked about the backup before in a previous thread but didn't get an answer.... Sorry to ask again

Techvir said:
Just want to know if Knox will be triggered or not? Please also add this to the first post [emoji397]
Click to expand...
Click to collapse
Knox is not triggered

Kjc99 said:
I got mine here... Took awhile to download... Someone gave me the link in the 955U1 thread
http://updato.com/firmware-archive-select-model?record=F6B451FD73EE11E7963AFA163EE8F90B
Click to expand...
Click to collapse
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol

powerstroke said:
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
Click to expand...
Click to collapse
If you have the system.img for the latest update then correct, if not and you want those features with root you will have to download the AP and CSC from thw firmware you want

powerstroke said:
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
Click to expand...
Click to collapse
I have the U1 model so I'm not sure...
Edit* Deleted

How To Guide Installing OneUI 4 Beta / Android 12 on US Galaxy Z Fold 3 F926U/1

Updated with more compatible adb link!
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then follow the guide to install adb https://www.xda-developers.com/install-adb-windows-macos-linux/
7. Follow the XDA adb install guide and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"

Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?

shadi90 said:
Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?
Click to expand...
Click to collapse
This is for US Fold 3 models f926U/1. Sorry brotha. Basically you need to change the beta file you downloaded to this http://fota-secure-dn.ospserver.net...48:16&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA== as well as flash AUJ7 firmware first. I hear UK with CSC BTE works fine. Get it at https://samfw.com/firmware/SM-F926B/BTE/F926BXXU1AUJ7 . After you replaced those files, just follow the instructions again

Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.

Haven't logged in to XDA in years. Just wanted to say THANK YOU.

mha1021 said:
Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.
Click to expand...
Click to collapse
Don't rename the file.
What I always do with adb related stuff is put it in the root of my C drive. So it would be
Code:
C:\adb\platform-tools\
Then put the .bin file in here as well.
After that open cmd and do
Code:
cd C:\adb\platform-tools\
and hit enter.
After that do adb sideload 94 and hit tab so it should autofill the name of the update file.
Let me know if you have any questions.

Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!

AlexMartin00 said:
Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!
Click to expand...
Click to collapse
The baseband is just something that gets updated, so ZUJH is the Android 12 beta firmware. Every time you update your firmware the baseband gets updated as well.
More technical: Baseband is firmware that controls all radio devices on the phone, including GPS, Wi-Fi, Bluetooth, NFC, cellular data, and more.

Will this work on att Galaxy fold 3 since I can't get update cause att blocks it.

Hero_is_Over said:
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then download the "15 Second ADB Installer" HERE
7. Install the 15 second adb installer and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"
Click to expand...
Click to collapse
hi I'm getting a status 1 error with my sideload

erneyone said:
hi I'm getting a status 1 error with my sideload
Click to expand...
Click to collapse
What does the error say?

I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop

zimgir124 said:
What does the error say?
Click to expand...
Click to collapse
Status 1

Is there a mirror for the beta download anywhere? It looks like the link isn't working for me.

ElGuyarc said:
I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop
Click to expand...
Click to collapse
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com

Dick_Stickitinski said:
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
thank you so much...

I updated my SM-F926U1 with the Beta 4 its really buggy for me
Just want to get my facts straight. Can I just flash back to non-beta ?
What will happen to my Beta status will I still be able to OTA update when the next beta comes out ?

I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide

Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
Is it a good idea to wipe my data when doing an downgrade like this ?

Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
I thought you can't flash a previous version of Android once you're on the higher version?