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

Search This thread

exocetdj

Senior Member
Dec 2, 2011
6,896
4,416
Jah's making me crazy
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 :p
 

Attachments

  • app-debug.zip
    16.6 MB · Views: 209
Last edited:

exocetdj

Senior Member
Dec 2, 2011
6,896
4,416
Jah's making me crazy
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!!
 
  • Like
Reactions: 白い熊

exocetdj

Senior Member
Dec 2, 2011
6,896
4,416
Jah's making me crazy
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
 

exocetdj

Senior Member
Dec 2, 2011
6,896
4,416
Jah's making me crazy
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)
 

JazonX

Senior Member
Dec 16, 2009
2,115
823
Xiaomi Mi 11 Ultra
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?
 

白い熊

Senior Member
Aug 29, 2011
828
286
相撲道
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!!
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...
 

ultramag69

Senior Member
Nov 6, 2007
5,940
1,043
Waratah
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.
 

exocetdj

Senior Member
Dec 2, 2011
6,896
4,416
Jah's making me crazy
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.
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 😂
 

ultramag69

Senior Member
Nov 6, 2007
5,940
1,043
Waratah
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 😂
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.
 
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.
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.
You can remove and/or disable bloat with adb commands for now. There is a thread about it somewhere in our forum
 
  • Like
Reactions: dirtybudha

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    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 :p
    4
    @exocetdj
    I have the same problem with the Gallery, also, when trying to send an image or a video in Telegram I get an error and when using Sync I cant watch videos and images. Maybe it has something to do with storage permission.
    No – this has to do with decrypting /data – I've confirmed this on my setup – you won't be able to get it working after formatting /data in TWRP. BTW you will also not be able to use Dex on your setup like this. That's a gift from Samsung to us.

    The only way to overcome this currently is like I have done:

    - Follow @exocetdj guide up to and including flashing the Magisk apk in TWRP.
    - From TWRP, reboot to Download mode.
    - In Odin disable autoreboot and flash Stock recovery, you have to make a tar for this from the stock firmware AP, just keep the recovery file in the tar.
    - Reboot to recovery via the key combo in the guide.
    - In stock recovery now, format /data again - this will encrypt it.

    Now reboot, you'll set up the system again and you'll have root, sharing will work, Dex will work etc.

    However you won't have TWRP. It's possible to flash just the TWRP recovery again after this without formatting /data however without accessible /data it's mostly useless.
    4
    ok no progress on Dex today from my end - seems to be a commonn issue and @abun880007 reported an error message stating that dex wouldn't work due to a modded system

    on a side note i have disabled WSM which means watch pairings remain on reboot - this was a fix in my rom already but module dependant meaning that watch pairings would go even if the module was disabled- thanks to @starbucks2010 for the wsm fix as always

    ill upload a new firmware tonight with this fix and it has been based on BTB (no difference to MSR firmware as is OXM)
    4
    F926B users - rooted firmware is now here

    This time round i have cooked in @Andrei1973 's WSM fix so no need for any modules to keep wearable pairings (cheers as always mate :) )

    Rebased to BUL8 firmware and including A7 TWRP from IanMacD

    Removed forrceencrypt and have also used df18bcf5 Magisk Alpha build (aka app-debug.zip) attached to this post for flashing in TWRP

    Update procedure

    1 reboot to download and load Odin

    2 Load the Odin files and uncheck "Auto reboot"

    3 Reboot straight to TWRP (remember the button combos!)

    4 ONLY IF YOU HAVENT GOT MAGISK ON INTERNAL STORAGE - check that MTP is disabled and copy app-debug.zip to adb folder then in CMD window "adb push app-debug.zip /sdcard"

    5 - Flash the app-debug.zip and then reboot to system from TWRP power menu

    You will boot rooted, updated and with intact data if all the steps above are followed correctly
    3
    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.