Develop Bugs

Rooting non-standard Android

Model number: GM_DSTL1
Firmware version: 1.5
Baseband version: 20/05/09,st32,x2a.m1
Kernel version: 2.6.28-svn1368
Build number: CUPCAKE.eng.long.20090720.210535.r1368
Trying to figure out how this could be rooted because I can't seem to use traditional methods like downgrading and 1-click rooting.
If I understand correctly this is possible for me due to CVE-2009-2692
In an effort to try and cover my butt I have backed up all that "adb shell" permission would let me.
Zinx's "Recovery partition flasher for Android" has not been helpful.
Getting my device to use FastBoot seems to be my first step.
Constructive comments?

still no luck
Ruled out the telnetd hack, bummer:
I run telnetd in terminal and it gives me no errors but a port scan doesn't return anything besides port 110(pop3), 25(smtp), and 21(ftp) - none of which have proved useful thus far. Must have been patched with cupcake... or something I'm missing.
Also ran cat /proc/cpuinfo for fun
--------------------------------
Processor : XScale-V3 based processor rev 2 (v5l)
BogoMIPS : 103.58
Features : swp half thumb fastmult edsp iwmmxt
CPU implementer : 0x69
CPU architecture: 5TE
CPU variant : 0x0
CPU part : 0x689
CPU revision : 2
Hardware : yuhua X2_V4 on Marvell (Littleton)
Revision : 0004
Serial : 0000000000000000
-----------------------------------------------------
103.58 is weak sauce... but apparently that is the minimum for the Marvell PXA310 RISC Microprocessor
I wonder if anyone else on this board is bumpin the DSTL1? I may be the lone fish out here

Following this guide to get Fastboot aka Engineering Bootloader
I skipped flashing the radio because I figured it had to do with the OTA stuff which doesn't affect my model...
So I downloaded spl-signed.zip and renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL.

update.log from failed update
Starting recovery on Thu Oct 8 01:22:51 2009
framebuffer: fd 4 (240 x 400)
I:text_cols 24 text_rows 22
E:Can't open /cache/recovery/command
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.long.20090710.190105.r1322
ro.build.version.incremental=eng.long.20090710.190105.r1322
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Fri Jul 10 19:15:42 CST 2009
ro.build.date.utc=1247224542
ro.build.type=user
ro.build.user=long
ro.build.host=long-desktop
ro.build.tags=ota-rel-keys,test-keys
ro.product.model=GM_DSTL1
ro.product.brand=generic
ro.product.name=gm_x2
ro.product.device=x2
ro.product.board=x2a_v4
ro.product.manufacturer=yh
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=
ro.build.product=x2
ro.build.description=gm_x2-user 1.5 CUPCAKE eng.long.20090710.190105.r1322 ota-rel-keys,test-keys
rild.libpath=/system/lib/libyh-ril.so
rild.libargs=-d /dev/ttyp1
persist.gsm.dual.mode.phone=1
persist.gsm.sim.active.phone=GSM1
sms.supports.national.lang=1
wifi.interface=eth0
ro.config.sm_notification_snd=notf_gm_02.ogg
ro.config.sm_notification_snd_2=notf_gm_02.ogg
ro.config.notification_sound=F1_New_SMS.ogg
ro.config.ringtone=GM_01.ogg
ro.config.ringtone_2=GM_01.ogg
ro.config.sync=yes
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=yuhua
ro.revision=4
init.svc.recovery=running
init.svc.adbd=running
init.svc.yuhua-board-init=stopped
ro.kernel.android.qemud=0
ro.radio.use-ppp=no
ro.com.google.locationfeatures=1
RecVer:Fri Jul 10 19:15:42 CST 2009
Recovery tools:
HOME: Sd-card update
CALL: Board test
BACK: Factory reset
POWER: Reboot system
I:Key 102 pressed, alt 0
Search /sdcard/update/*
I:Find file . in /sdcard/update/
I:Find file .. in /sdcard/update/
I:Find file update.log in /sdcard/update/
I:Find file update.zip in /sdcard/update/
Find update.zip, Home to update
I:Update package /sdcard/update/update.zip
Installing /sdcard/update/update.zip
Installation failed.

Another Fastboot attempt
http://android-dls.com/wiki/index.php?title=Engineering_Bootloader
Downloaded update.xxx, renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL... again.
From the log files it seems this stock recovery system SUCKS...

Another FAIL
Revisiting http://forum.xda-developers.com/showthread.php?t=532719 from my earlier post (#3). Tried to do the Radio Update... Downloaded ota-radio-2_22_19_26I.zip and renamed it to update.zip... yada yada yada, you know the rest.

Visit "http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support", and you can find how the update system work(it is not a G1). Also take some time to see the install package and hack it.
1. Unzip the package.
unzip Android_20090826_r1502.zip
2. Copy some missed property app(http://www.sendspace.com/file/dii80c get from adp1.5) to /system/app/ after diff it with the ADP image.
3. zip the new package.
zip Android_20090826_r1502_hack.zip -ry system boot.img
4. update package and wait it bootup.

Very cool!
@wineleven
THANKS!
That was very cool! Finally some progress
So I was not too off from that path, I had already downloaded the update from General Mobile and had been inspecting the zip file they were trying to shove in my face as a quick fix to their buggy ROM. I was asking the support some very hard questions, which is probably why it has taken them more than their 48 hours to reply to me. (its been 5 days now)
General Mobile's update is Android_20090826_r1502.zip
containing the following particularly interesting (to me) files:
/system/build.prop
/system/system-update-post-script
/boot.img
/update-validate-script
Attempt 1
Here I tried to zip up their unmodified package with the suggested -ry arguments and hope that stock recovery takes it and runs with it.
FAIL
I reviewed wineleven's suggestions noticed he omitted the file update-validate-script
This was probably my problem
Attempt 2
Here I omitted update-validate-script
SUCCESS!
Attempt 3
Spirits high I go for the gusto:
I downloaded superuser.zip from this forum and embedded it in the location /system/app
Flash SUCCESS, functionality FAIL
I got too excited and put Superuser.apk and su both in the same directory... silly mistake
Attempt 4
This time I put Superuser.apk in /system/app and su in /system/bin
Flash SUCCESS, functionality FAIL
running su in terminal gave me "permission denied" with the following carriage return:
here1here2here3here4$
obviously I'm missing something here... but have made progress and feel more confident about this.
More attempts to come. Suggestions and advice is welcome!
Question to those knowledgeable
Why are certain files in the /system/bin included as "links" and not actual files? save space in zip?
Can boot.img be modified? Replaced with a better (more useful) one?
Any ideas on obtaining root?

Root idea and shortcommings
After reviewing http://android-dls.com/wiki/index.php?title=Magic_Root_Access
I may have bin (lol) too hasty with slapping su in /system/bin
But logic tells me it shouldn't matter... bin or xbin
And I feel like permissions are my real issue because my current su (residing in /system/bin)
command
ls -l /system/bin/su
returns
-rwxr-xr-x root shell 34612 2008-08-01 08:00 su
command
chmod 6755 /system/bin/su
returns
Unable to chmod su: Read-only file system
^--- in hindsight I see that as a DUH, because I can't remount the /system partition as read/write
More questions
I have always understood chmod to use three digits, why are there four digits now?
Also, what is 's' in terms of permission... is that to see? like hidden files?

Main task accomplished!
After reviewing Cyanogen's experimental ROM I can see where and how he sets permission for su
Trying to emulate his method for myself has been plenty of trial and error, but I have finally done it.
system-update-post-script was the key file that set permissions.
One MUST keep the carriage return at the end of the file - I have a neatfreak habit of cleaning them up.
Also, using the su and Superuser.apk in Cyanogen's latest build kept restarting my device, must be because his kernel is newer than mine.
RapidShare is hosting for 90 days Android_20090826_r1502_rooted.zip - NEW BUILD HERE
MD5: F1DE9A270CDDF01ADEE708B6660B7AFA
PM me if not avail.
NOTE:
I am not responsible for your new paper-weight mode...
This has worked fine on my device, but I guarantee nothing for yours...
My device is General Mobile's DSTL1 - details in post #1
What you get:
Root access via su and Superuser.apk - procured from XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060
To use:
Your sdcard must contain "update" folder, this is where you will place the zip file after you have renamed it to "update.zip"
Happy ROOT
------------------------------------------
My next task will be to get Cyanogen's ROM to work on my device... seeing as how Cyanogen codes for the popular HTC models, I am left out - and I don't like being left out.
Side quests will be to play with the boot.img, flash the SPL, and maybe get a nice recovery
Particularly I would love to try out nandroid.
@wineleven THANK YOU for the nudge in the right direction!
Thank you:
Google for the open source Android OS - without the free SDK wouldn't have been possible for me
General Mobile for the nifty device
Remote Exploit for BackTrack3/4 - I did most of my work on this Live CD distro
XDA-Developers Forum for info and resources: superuser files and Cyanogen's ROM for info

congratulation to you.
Some notice:
As this devices is deeply modified based on Android open source and hardware different to G1. So you can not rebuild any system framework APK from open source unless you can get the DSTL1 source code. As i now, one thing we can do is to add some external APK file (API compatible to device, now SDK 1.5) to system. Like the Superuser.apk you do.

crzyruski said:
After reviewing Cyanogen's experimental ROM I can see where and how he sets permission for su
Trying to emulate his method for myself has been plenty of trial and error, but I have finally done it.
system-update-post-script was the key file that set permissions.
One MUST keep the carriage return at the end of the file - I have a neatfreak habit of cleaning them up.
Also, using the su and Superuser.apk in Cyanogen's latest build kept restarting my device, must be because his kernel is newer than mine.
RapidShare is hosting for 90 days Android_20090826_r1502_rooted.zip
MD5: C3C13F6DC75BF6F86E5C9E41D7FB4C59
PM me if not avail.
NOTE:
I am not responsible for your new paper-weight mode...
This has worked fine on my device, but I guarantee nothing for yours...
My device is General Mobile's DSTL1 - details in post #1
What you get:
Root access via su and Superuser.apk - procured from XDA forums: http://forum.xda-developers.com/attachment.php?attachmentid=211569&d=1249225060
To use:
Your sdcard must contain "update" folder, this is where you will place the zip file after you have renamed it to "update.zip"
Happy ROOT
------------------------------------------
My next task will be to get Cyanogen's ROM to work on my device... seeing as how Cyanogen codes for the popular HTC models, I am left out - and I don't like being left out.
Side quests will be to play with the boot.img, flash the SPL, and maybe get a nice recovery
Particularly I would love to try out nandroid.
Click to expand...
Click to collapse
Hi crzyruski
I'm a new android and DSTL1 user and this information is cool
it's easy to do for a newbie as I?

What do you mean easy? What would you like to do?
I took General Mobile's only update: http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support and gave it ROOT. If this is all you want to do, I have compiled the package already for you in my post above. If you want to do it manually then read the whole thread to see how I did it.
If you want to use my compiled package, it is easy.
Then again, I don't know if anyone else has tried it. It worked for me.
You are only the second individual to inquire about it, I am not sure if the other fellow had any luck - he hasn't replied to me.
Hope this helps.
Keep in touch!

I only have 3 days with Android, but I think that I want to get root access. The only thing I have to do is a second "update" with your package, isn't it?
I'm going to look for a backup system program first...
Can I have problems to update from General Mobile support web in a future? (i.e Android 2.0)

It does not need to be second. That is your choice. You can use it in any order. This is not a patch so order is no relevant.
My package is basically the original General Mobile update + 2 files.
These two files are su and Superuser.apk - nothing special (except that you will obtain root access on demand)
I currently only utilize root access to run Advanced Task Manager.
And in the future I want to overclock because I feel the DSTL1 is greatly underclocked though it should max out at ~600Mhz.
Good luck with a backup program as I have not found any free versions and NAndroid is ideal but not not yet possible as you have to flash the SPL and I am not aware how to do this for DSTL1 though I am sure it is possible.
Please let me know what you end up using to backup, if you do.
I would like to note that I am not all knowing and if something goes wrong I am sorry, but can't take responsibility.
There is no reason you should not be able to update from my package to another like: original 1.5 or new 1.6 or future 2.0 (whenever it comes out).
Hopefully when those come out I will be able to modify them similarly and make them available.
But you mentioned you will only have the device for 3 days, do you suppose 2.0 will be released within this time?
-crzyruski

crzyruski said:
Please let me know what you end up using to backup, if you do.
But you mentioned you will only have the device for 3 days, do you suppose 2.0 will be released within this time?
-crzyruski
Click to expand...
Click to collapse
I'm going to try with My Backup Pro
And about 2.0 this all I know...
http://www.boygeniusreport.com/2009/10/16/android-2-0-screenshot-walkthrough/

Good luck to you.
I think I may begin working on some more DSTL1 hacks.
Please keep me updated with your progress

I only have to do ALL this process with your zip, isn't it?
How to Install the Product Update:
Create a folder at the top-level of your memory card called 'update' , and copy file '*.zip' into your phone's memory card.
Make sure your phone is off, and press the Home key together with the Power & End key to enter the recovery mode, do the operations following the UI indication:
1- Press the Home key to search the zip file from your memory card, and press the Home key again to update the software.
2- Press the Call key to do board test.
3- Press the Back key to restore the factory settings.
4- Press the Power & End key to reboot your phone after update finishes.
Click to expand...
Click to collapse

Looks correct to me. Tell me how it works out.

crzyruski said:
Looks correct to me. Tell me how it works out.
Click to expand...
Click to collapse
I've done it! and all seems to be ok...
Thank you crzyruski.
I'll be waitng for your future DSTL1 hacks.

[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

'Odin'...for Linux!

So I've been making an unscheduled and unexpected move from Windows 7 to Ubuntu 14. In that process I've had to find new tools to do certain things. For example, recovering back to stock on a Samsung device or rerooting one. I have found a simple and quick way to do this right from a terminal in Ubuntu.
****I DID NOT CREATE THIS TOOL. I TAKE NO CREDIT FOR THIS****
I have only tested this on the Galaxy S4, but it will likely work for many other Samsung devices. You can thank @trevd for creating this. I'm not sure he expected it to really be useful. This short guide only covers recovering back to stock firmware. If demand is high enough, I'll post another guide on re-rooting and flashing custom recovery.
Odin for Linux
REQUIREMENTS:
-Download Odin for linux
-A Linux machine. I used Ubuntu desktop 14.
-A Samsung device, in this case a Galaxy S4
-Firmware package for your device
INSTRUCTIONS:
1. Locate and download the firmware package for your device. Look on 'sammobile' for example.
2. Extract the contents of the Odin package above to a folder in your home directory. Just name it 'odin'.
3. Extract the firmware package into the Odin folder you just made. There will be at least 4 files in the firmware package. It doesn't matter if there are more. We only care about 4 of those files.
4. You just want these 4 files: BL, AP, CP AND CSC (just CSC is fine. Delete the one with home in the title. If there isn't another CSC file, then keep it). Delete all others.
5. (This step is optional if you aren't 100% sure the firmware you are flashing is 100% stock. But be warned, this method isn't likely to work.) Remove the .md5 extension from each of the 4 files. Right click each one, select rename and simply remove the .md5 and save them.
6. Open a terminal and navigate to your Odin folder. If you created it in home, type:
Code:
cd odin
ls
7. You will see a list of files scroll on the screen. If you see 'odin4', type
Code:
sudo chmod a+x odin4
8. Get your Samsung device and power it off. Boot to download mode by holding down: volume down, home and power. When the warning come up, press volume up to go into download. You should see a Droid with some info at the top left of the screen.
9. Plug your phone into your PC. Open a terminal and navigate to the Odin folder (if you closed the other terminal window). Type the following below. This must all be done in one step only hit enter when all files are added. The X's represent the rest of that file name. Replace them accordingly with the WHOLE name, leaving the BL or AP etc in front).
Code:
./odin4 -b BL.XXX.XXX -a AP.XXX.XXX -c CP.XXX.XXX -s CSC.XXX.XXX --no-reboot
If all goes well, you shouldn't see any errors. The device should NOT reboot. If you do see errors, go back and readd the .md5 to each file and try again. If it still doesn't work, you have the wrong firmware or something else is wrong. Google is now your friend.
10. If successful, and no errors appear, you will see the shell command prompt reappear in the terminal. Unplug your device, and power it off by holding down the power button for at least 30 seconds AFTER the screen turns off.
11. Reboot to recovery by holding down: volume up, home and power. When you see the blue text on the screen, release the buttons. Android's stock recovery should come up. Using volume down, select the option to perform a factory reset. When done, wipe the cache then reboot normally. You should be on fresh stock.

DragonFire1024 said:
So I've been making an unscheduled and unexpected move from Windows 7 to Ubuntu 14. In that process I've had to find new tools to do certain things. For example, recovering back to stock on a Samsung device or rerooting one. I have found a simple and quick way to do this right from a terminal in Ubuntu.
****I DID NOT CREATE THIS TOOL. I TAKE NO CREDIT FOR THIS****
I have only tested this on the Galaxy S4, but it will likely work for many other Samsung devices. You can thank @trevd for creating this. I'm not sure he expected it to really be useful. This short guide only covers recovering back to stock firmware. If demand is high enough, I'll post another guide on re-rooting and flashing custom recovery.
Click to expand...
Click to collapse
@DragonFire1024 I definitely didn't create this tool... I found after many hours searching. One thing I will note is that this version doesn't support newer samsung firmwares that are lz4'd inside the tar.md5. I keep meaning to script a wrapper for this but time and motivation escapes me lol.
Thanks for the guide though and don't forget Heimdall is still a great tool for flashing Samsung devices on linux.

trevd said:
@DragonFire1024 I definitely didn't create this tool... I found after many hours searching. One thing I will note is that this version doesn't support newer samsung firmwares that are lz4'd inside the tar.md5. I keep meaning to script a wrapper for this but time and motivation escapes me lol.
Thanks for the guide though and don't forget Heimdall is still a great tool for flashing Samsung devices on linux.
Click to expand...
Click to collapse
I didn't have luck with Heimdall, however as stated in my own guide, trying non stock firmware probably won't work. However i didn't try using this tool yet.
Well I still give you the credit. This should've gotten a lot more attention. I'm going to look into how this is done. Maybe it can be applied outside the Samsung framework.
Sent from my MotoG3 using XDA Labs

I'm here to confirm to you guys... THIS WORKED LIKE A CHARM !!!
Tested in Samsung Galaxy S8 Qualcomm (NTT Docomo), machine : Linux Ubuntu 18.04
Thank god it came in Linux too !
DragonFire1024 said:
So I've been making an unscheduled and unexpected move from Windows 7 to Ubuntu 14. In that process I've had to find new tools to do certain things. For example, recovering back to stock on a Samsung device or rerooting one. I have found a simple and quick way to do this right from a terminal in Ubuntu.
****I DID NOT CREATE THIS TOOL. I TAKE NO CREDIT FOR THIS****
I have only tested this on the Galaxy S4, but it will likely work for many other Samsung devices. You can thank @trevd for creating this. I'm not sure he expected it to really be useful. This short guide only covers recovering back to stock firmware. If demand is high enough, I'll post another guide on re-rooting and flashing custom recovery.
Odin for Linux
REQUIREMENTS:
-Download Odin for linux
-A Linux machine. I used Ubuntu desktop 14.
-A Samsung device, in this case a Galaxy S4
-Firmware package for your device
INSTRUCTIONS:
1. Locate and download the firmware package for your device. Look on 'sammobile' for example.
2. Extract the contents of the Odin package above to a folder in your home directory. Just name it 'odin'.
3. Extract the firmware package into the Odin folder you just made. There will be at least 4 files in the firmware package. It doesn't matter if there are more. We only care about 4 of those files.
4. You just want these 4 files: BL, AP, CP AND CSC (just CSC is fine. Delete the one with home in the title. If there isn't another CSC file, then keep it). Delete all others.
5. (This step is optional if you aren't 100% sure the firmware you are flashing is 100% stock. But be warned, this method isn't likely to work.) Remove the .md5 extension from each of the 4 files. Right click each one, select rename and simply remove the .md5 and save them.
6. Open a terminal and navigate to your Odin folder. If you created it in home, type:
Code:
cd odin
ls
7. You will see a list of files scroll on the screen. If you see 'odin4', type
Code:
sudo chmod a+x odin4
8. Get your Samsung device and power it off. Boot to download mode by holding down: volume down, home and power. When the warning come up, press volume up to go into download. You should see a Droid with some info at the top left of the screen.
9. Plug your phone into your PC. Open a terminal and navigate to the Odin folder (if you closed the other terminal window). Type the following below. This must all be done in one step only hit enter when all files are added. The X's represent the rest of that file name. Replace them accordingly with the WHOLE name, leaving the BL or AP etc in front).
Code:
./odin4 -b BL.XXX.XXX -a AP.XXX.XXX -c CP.XXX.XXX -s CSC.XXX.XXX --no-reboot
If all goes well, you shouldn't see any errors. The device should NOT reboot. If you do see errors, go back and readd the .md5 to each file and try again. If it still doesn't work, you have the wrong firmware or something else is wrong. Google is now your friend.
10. If successful, and no errors appear, you will see the shell command prompt reappear in the terminal. Unplug your device, and power it off by holding down the power button for at least 30 seconds AFTER the screen turns off.
11. Reboot to recovery by holding down: volume up, home and power. When you see the blue text on the screen, release the buttons. Android's stock recovery should come up. Using volume down, select the option to perform a factory reset. When done, wipe the cache then reboot normally. You should be on fresh stock.
Click to expand...
Click to collapse

pixie_laluna said:
I'm here to confirm to you guys... THIS WORKED LIKE A CHARM !!!
Tested in Samsung Galaxy S8 Qualcomm (NTT Docomo), machine : Linux Ubuntu 18.04
Thank god it came in Linux too !
So I've been making an unscheduled and unexpected move from Windows 7 to Ubuntu 14. In that process I've had to find new tools to do certain things. For example, recovering back to stock on a Samsung device or rerooting one. I have found a simple and quick way to do this right from a terminal in Ubuntu.
****I DID NOT CREATE THIS TOOL. I TAKE NO CREDIT FOR THIS****
I have only tested this on the Galaxy S4, but it will likely work for many other Samsung devices. You can thank @trevd for creating this. I'm not sure he expected it to really be useful. This short guide only covers recovering back to stock firmware. If demand is high enough, I'll post another guide on re-rooting and flashing custom recovery.
Odin for Linux
REQUIREMENTS:
-Download Odin for linux
-A Linux machine. I used Ubuntu desktop 14.
-A Samsung device, in this case a Galaxy S4
-Firmware package for your device
INSTRUCTIONS:
1. Locate and download the firmware package for your device. Look on 'sammobile' for example.
2. Extract the contents of the Odin package above to a folder in your home directory. Just name it 'odin'.
3. Extract the firmware package into the Odin folder you just made. There will be at least 4 files in the firmware package. It doesn't matter if there are more. We only care about 4 of those files.
4. You just want these 4 files: BL, AP, CP AND CSC (just CSC is fine. Delete the one with home in the title. If there isn't another CSC file, then keep it). Delete all others.
5. (This step is optional if you aren't 100% sure the firmware you are flashing is 100% stock. But be warned, this method isn't likely to work.) Remove the .md5 extension from each of the 4 files. Right click each one, select rename and simply remove the .md5 and save them.
6. Open a terminal and navigate to your Odin folder. If you created it in home, type:
7. You will see a list of files scroll on the screen. If you see 'odin4', type
8. Get your Samsung device and power it off. Boot to download mode by holding down: volume down, home and power. When the warning come up, press volume up to go into download. You should see a Droid with some info at the top left of the screen.
9. Plug your phone into your PC. Open a terminal and navigate to the Odin folder (if you closed the other terminal window). Type the following below. This must all be done in one step only hit enter when all files are added. The X's represent the rest of that file name. Replace them accordingly with the WHOLE name, leaving the BL or AP etc in front).
Click to expand...
Click to collapse
This also can be done using another device and simply taking the binary and inserting it into the system bin or into xbin. You may need to do a couple more files to with I forget however I was able to successfully flash firmware back to my Galaxy S4 using this binary and a rooted shell from my rooted and unlocked Amazon HD 10.
Sent from my Amzn Fire using XDA Labs

How To Guide How to extract image collection from rom releases (and root the boot image and apply root to the phone)

1. To extract the image collection from your downloaded rom :
Download Payload Dumper from here (It's a zip file but it's not flashable) to your computer
Extract the zip file to a folder, make it a folder you can use regularly because this is the default tool you would use from now on
Download the rom version you want to root
Unzip the rom to a folder, you will find a file within it called payload.bin
Copy and paste that file into the "payload_input" folder within the Payload Dumper folder you created
Execute the payload_dumper.exe file within Payload Dumper folder, you will not have to specify any options as it always extracts from any payload.bin file in payload_input and outputs the image files to payload_output.
Leave the extraction to be completed, the program will automatically close itself once it's completed
Your extracted .img files will be shown within the payload_output folder
2. If you need to root the boot image you extracted :
Copy the boot.img file from the payload_output folder to a folder on your phone storage (Best to name it appropriately if you will be doing this regularly)
Download and Install the latest Magisk apk from the release site (Accept any prompt to allow install from external source)
Launch the app and then choose Install under the top "Magisk" section
Choose Select and Patch a File then browse to where you copied the boot.img on your storage
Magisk will then apply root to the boot image you specified, Your rooted image file will be output to your phone's Download folder : /sdcard/Download
You don't need to keep the default filename of the rooted image file so you can rename it appropriately for the rom version after you copy it to your computer, just ensure to keep the .img file extension
If you rename the rooted boot image, try not to use spaces in the filename, rather use _ or - as spaces make it more difficult to use in a command window although when you start typing the filename you can use TAB to autocomplete it, always ensure the filename shows .img as the extension and at the end of any commandline
3. If you need to use your rooted boot image to apply root to your phone :
Install the drivers from the mounted drive you should get when connecting the phone to your computer
On Windows you should then have a folder in C:\Program Files (x86)\OnePlus USB Drivers\Android with the platform tools (ADB.exe and Fastboot.exe) you will need, you can obviously copy the content from that folder somewhere else if you wish.
Connect your phone to your computer
Copy your rooted boot image to the folder that has adb.exe and fastboot.exe
Open a command window on your computer by right clicking in that folder and choosing Open command window here
In the command window, Type or copy/paste the command ADB devices and press enter
If you see a prompt on your phone to allow the computer connection then accept it, better still, tell it to allow from now on also.
You should see a string of characters shown in the command window, if you don't see that, then try another cable or re-install your drivers and reboot the computer.
Reboot your phone into Fastboot either by using ADB on your computer ( ADB Reboot Fastboot ) or by enabling Advanced reboot in your developer options in settings and then hold down the power button and use the 3 dot menu on the top right and choosing "Bootloader"
In the command window type Fastboot Boot <filename.img> i.e. Fastboot Boot rooted_boot.img and press enter
You should see a couple of lines in the command window telling you it's copying over to the phone, don't worry it's not being flashed or replacing your existing installed boot image
The phone should then restart and boot using the image from your computer, it will be a slightly slower boot than usual, your existing unlock method should still work
Launch the Magisk app, it should already have root access because the boot image you've used is already rooted
Go to Install under the top Magisk section
Choose Direct Install (Recommended)
Magisk will then apply root access to the boot image on the actual phone
You will be prompted to reboot the phone on the bottom right, do this to complete the process
You don't need the phone connected to your computer anymore as the installed boot image on the phone should now have root access
You can check for root either using any app which requires root or by using an app like Root Checker
Remember to empty the contents of payload_input and payload_output once you have finished, leaving them ready for any future rom versions
4. To retain root access after ROM/OTA update :
Install the update either from Oxygen Updater or from Settings > System > System updates
DO NOT REBOOT when prompted
Go to the Magisk app
Go to Install under the top Magisk section
Choose Install to Inactive Slot (After OTA)
Magisk will apply root to the newly installed boot image for the next version
Reboot when prompted by the Magisk app
The phone should reboot into the updated version with root already applied

Very nice write up! Hopefully many will read this and follow instructions. Too many threads being created with issues because they never bother to read.

Quick question as this is my first OnePlus device.
Will I lose root after a system update and will have to it all over again?

Levi4cyber said:
Quick question as this is my first OnePlus device.
Will I lose root after a system update and will have to it all over again?
Click to expand...
Click to collapse
Just added a new section to my original post for this.

Does flashing magisk change anything in encryption?
Does it wipe anything?

How do I get my ROM to extract the boot img?

Levi4cyber said:
Does flashing magisk change anything in encryption?
Does it wipe anything?
Click to expand...
Click to collapse
No and No

Levi4cyber said:
How do I get my ROM to extract the boot img?
Click to expand...
Click to collapse
Read the first post.

djsubterrain said:
Read the first post.
Click to expand...
Click to collapse
I'm asking where to get my ROM file, in order I should be able to extract the boot img?
A link? Somewhere on my phone?

Levi4cyber said:
I'm asking where to get my ROM file, in order I should be able to extract the boot img?
A link? Somewhere on my phone?
Click to expand...
Click to collapse
It's pinned at the top of the entire forum :
[OnePlus 9 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
They're also posted on OnePlus's site (eventually) :
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Make sure the version matches the one you're using

I updated to latest version 11.2.4.4.LE15AA
Since there's nowhere to download the OTA package and extract the boot img, can I use the boot img of a lower version - 11.2.2.2 ?

Levi4cyber said:
I updated to latest version 11.2.4.4.LE15AA
Since there's nowhere to download the OTA package and extract the boot img, can I use the boot img of a lower version - 11.2.2.2 ?
Click to expand...
Click to collapse
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom.
If you were already rooted though, you should've been able to retain it by following the last section in my original post.
If not, then follow the first 2 sections

djsubterrain said:
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom
Click to expand...
Click to collapse
Since I'm completely new to OP, is Oxygen updater an app (if yes, is it this; https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater)? Or is it built into the phone?

Levi4cyber said:
Since I'm completely new to OP, is Oxygen updater an app (if yes, is it this; https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater)? Or is it built into the phone?
Click to expand...
Click to collapse
I've linked it, it's not a default app

djsubterrain said:
No, definitely not.
Try Oxygen Updater in advanced mode, it should let you download the full rom.
If you were already rooted though, you should've been able to retain it by following the last section in my original post.
If not, then follow the first 2 sections
Click to expand...
Click to collapse
In the oxygen updater app, if I select "full update" in update method it only gives me version 11.2.2.2., if I select "incremental update", it lets me download 11.2.4.4, and when I unzipped it I have a file payload.bin (it's only 105MB).
Should I use that? Or do I need a full OTA package to extract the boot IMG?

Levi4cyber said:
In the oxygen updater app, if I select "full update" in update method it only gives me version 11.2.2.2., if I select "incremental update", it lets me download 11.2.4.4, and when I unzipped it I have a file payload.bin (it's only 105MB).
Should I use that? Or do I need a full OTA package to extract the boot IMG?
Click to expand...
Click to collapse
Are you choosing the correct OnePlus 9 Pro? It'll show you different variants under the model lookup.
To be honest, If I get the update pushed via OnePlus I always copy/paste it somewhere else cos I think it gets deleted once the upgrade is done.
If you extract the payload.bin and it shows a boot.img then that should suffice. I think it should be around 105MB (I'm on my work PC at the moment so can't check)

Thanks. I'm on the T-Mobile version of the OnePlus 9 Pro, technically my phone is currently on "11.2.2.2.LE5ACB" and the one on OnePlus's support site is "11.2.2.2.LE15AA". I'm not sure the difference but I assume T-Mobile bloatware. Hopefully they didn't do anything else to make the phone work "slightly better" on their network.
I'm not sure if the boot.img I extracted from 11.2.2.2.LE15AA will work with my currently-installed "11.2.2.2.LE5ACB"; any ideas?
Might be better to create a boot.img from my existing version and patch that. Do you know the dd command for me to just create the boot.img from my existing partition? In the past with other phones I've done something like "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/boot.img bs=4096 count=4096 skip=7552" or "dd if=/dev/block/bootdevice/by-name/boot of=boot.img" but I don't know which partition on the OnePlus 9 Pro to image. Any ideas?
--- Update 1 ---
Code:
OnePlus9ProTMO:/ $ ls -l /dev/block/bootdevice/by-name/*boot*
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/boot_a -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/boot_b -> /dev/block/sde43
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vendor_boot_a -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vendor_boot_b -> /dev/block/sde55
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vm-bootsys_a -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1970-01-20 02:38 /dev/block/bootdevice/by-name/vm-bootsys_b -> /dev/block/sde51
Then looking at my active mounts I saw this:
Code:
OnePlus9ProTMO:/ $ mount | egrep "sde16|sde43|sde28|sde55|sde24|sde51"
/dev/block/sde51 on /vendor/vm-system type ext4 (ro,seclabel,nosuid,nodev,relatime)
Which indicates that I'm on the "b" side. So I would want to create a boot.img from `/dev/block/bootdevice/by-name/vendor_boot_b` potentially. So this command "should" work, right?
Code:
dd if=/dev/block/bootdevice/by-name/vendor_boot_b of=/sdcard/Download/stock_boot.img
I might try that instead of the boot.img I extracted from 11.2.2.2.LE5ACB since it doesn't technically line up with the T-Mobile supplied ROM version.
--- Update 2 ---
Yeah, that didn't work.Turns out dd needs to be elevated to do its thing. Got a "Permission denied" when i tried to create the image. So yeah, ironically I need root to run said command and that's why I was trying to run the command, to get the boot.img to root. lol. oh well.

Thank you very detailed.

When I click on the payload_pumper.exe file, the cmd window flashes and nothing else happens.

glitchsys said:
Turns out dd needs to be elevated to do its thing.
Click to expand...
Click to collapse
Try watching this, man, I think this is exactly what you are missing:
Code:
https://www.youtube.com/watch?v=DyUainEJwLM

How To Guide SM-F926B ONLY!! Android 12 update and ROOT GUIDE - BVA9 rooted firmware provided - if you missed the good news, camera works :)

Hi All!!
This thread will now contain pre rooted Odin files for F926B users to flash and update
Before you start, download "420rom_F926B_BVA9_Odin_EUY.zip" from HERE
THIS IS FOR F926B ONLY
The process requires knowledge of basic adb and YOU MUST HAVE ADB INSTALLED BEFORE TRYING THIS
This will no longer wipe data but it is advisable to backup first anyway - i wont be responsible for any data lost that could have been backed up
PROCESS to update from rooted a11 or a12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP mount menu disable MTP
5 - ONLY IF YOU DONT HAVE A MAGISK.ZIP ON INTERNAL STORAGE copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer)
6 - go to the TWRP flash menu and you should see the app-debug.zip, flash it to root your A12 device - this needs to be done everytime TWRP is flashed in Odin it seems
7 - reboot to system from TWRP power menu
You will boot rooted, updated and with intact data if all the steps above are followed correctly
------------------------------------------------------------------------------------------------------------------
PROCESS IF COMING FROM STOCK A12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC (please ensure dev settings are enabled and that you have unlocked bootloader and checked "Oem unlock" is faded out under dev settings)
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP wipe menu and format device (type yes and press enter) - then reboot TWRP
5 - when TWRP has rebooted, go to the mounts menu and disable MTP -> this will allow us to send app-debug.zip (magisk) to your sdcard
6 - copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working
7 - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer) - go to the TWRP flash menu and you should see this app-debug.zip, flash it to root your A12 device
8 - as stated previously, i have disabled encryption therefore we just need to boot STRAIGHT to SYSTEM from the TWRP POWER MENU
9 -When phone reboots, set up as normal and you should now see a magisk stub in the app drawer meaning you are rooted

PLEASE NOTE THAT THE MAGISK PATCHED AP FILE IS UPLOADING AND WILL BE AVAILABLE IN A FEW HOURS

Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!

ok my teammate has built a tested and working AP file to use in the guide above - this will be up very shortly
mine was fine however my internet connection is not lol

Ok guys - sorry for the muck about!! the patched AP file is now live in the first post - therefore you can go ahead and root!
Follow the steps carefully, please also read and make sure you have everything prepared before you start

Had a couple of peeps join my telegram chat asking about OEM option being missing.
Please note that this guide only covers the WWE F926B at the moment (US models have a locked bootloader afaik)

Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?

JazonX said:
Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?
Click to expand...
Click to collapse
At the moment there is sadly no camera til the bootloader is relocked. Hopefully a fix is found soon

exocetdj said:
Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!
Click to expand...
Click to collapse
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...

白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
Hi mate have you managed to access it yet? if not ill try sort links out

白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
try this alternative link
If not ill ask my teammate to mirror to Mega

exocetdj said:
Hi mate have you managed to access it yet? if not ill try sort links out
Click to expand...
Click to collapse
Yeah, after an hour or so it let me in again, and didn’t fail this time. :O)

Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.

ultramag69 said:
Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.
Click to expand...
Click to collapse
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root

exocetdj said:
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root
Click to expand...
Click to collapse
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.

ultramag69 said:
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.
Click to expand...
Click to collapse
So from my understanding, Knox was actually designed for dual rom booting, as a way to keep the original firmware in tact and safe, but also be able to flash a custom rom for dual boot. But investors, carriers, and the like decided they weren't happy with that and saw that it could also be used to lock the device down to make everything more secure for their intents. After like 4 iterations where Samsung kept being pushed, it became what it is today.
I'm assuming they thought if they just impliment everything that a person would root for, that it would make people OK with it, but of course not the case. In the end, just like any other major corporation, they let money push them around

If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.

As soon as you flash any custom binary then your software is classed as custom and will not boot at all with a locked bootloader. It would soft brick requiring a stock odin flash to revive device most likely

dirtybudha said:
If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.
Click to expand...
Click to collapse
You can remove and/or disable bloat with adb commands for now. There is a thread about it somewhere in our forum

Samkey apparently now supports f926b but I'm getting unsupported firmware errors on AUG8 and AUHF. I really want to get rid of this three bloat