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

pvillasuso

Senior Member
Hi, already done that, same problem, the only thing that remains untouch is the unlocked bootloader
but I don't think that's a problem, correct me if I'm wrong. Thanks
Try to flash the newest stock firmware , maybe that will fix the issue.
And wait for the Pro's to help with the new "coming soon" rooting steps , files and guide.

F926BXXU1BVA9
 
Nov 27, 2016
23
0
Try to flash the newest stock firmware , maybe that will fix the issue.
And wait for the Pro's to help with the new "coming soon" rooting steps , files and guide.

F926BXXU1BVA9
what is really strange is that I managed to root the phone the first time,
then upgrading to BUL8 I started having this problem and now I can't go
back to BUL6 rooted stock rom because it gives me the same problem.
I hope @exocetdj and the other pros will come up with some sort of solution.
 

milkychipz

New member
Apr 11, 2013
4
3
Is it safe to direct install v24 magisk? I tried earlier with a different magisk build and it put me into a bootloop, lucky my data was intact and I just refreshed in odin
 
  • Like
Reactions: exocetdj

exocetdj

Senior Member
Dec 2, 2011
6,896
4,413
Jah's making me crazy
Is it safe to direct install v24 magisk? I tried earlier with a different magisk build and it put me into a bootloop, lucky my data was intact and I just refreshed in odin
yes

Also TO ALL USERS BVA9 rooted stock firmware has been uploaded and is now in testing

I have messed up bluetooth in the firmware but will provide a TWRP flashable zip to fix that (just flash after Magisk when updating to BVA9) - this is folder reset v1.1 and installs the stock bluetooth lib

This issue will only rear its head if you are trying to connect watch but that works perfect when the fix is flashed

I could upload a new firmware but with 20mb ADSL internet, im sure you guys will allow me to not have to do that and just flash a quick zip instead ;)
 

frwerewolf

Senior Member
Jan 12, 2013
121
18
@exocetdj
Hello. Just installed your BVA9. Perfect. It didnt repair my problems with Samsung Gallery crashing when i want to share a picture in another app. But i use Google photo to do that instead.

Question: do you know a module to install or an apk that offers like you have in your Magisk Rom "custom power app with several reboot options" ? . The ones i have tested are not compatable with A12 yet.
Thanks a lot for these rooted methods
 

frwerewolf

Senior Member
Jan 12, 2013
121
18
this phone is ****ing me up. Bootloop and not starting yet by update to BVA9. can i fix them?
You are wanting to use a rooted A12 version right ?
Are you sure your bootloader is unlocked ? Have you Activated in settings "oem unlock" and then the first time you were in download mode have held volume up 7 seconds to confirm the unlock ?
Anyways following exactly @exocetdj procedure must work...unless its not the same phone model.

Can you re flash the original stock files to go back to original state ?
 

verplanloster

Member
Oct 18, 2012
9
0
You are wanting to use a rooted A12 version right ?
Are you sure your bootloader is unlocked ? Have you Activated in settings "oem unlock" and then the first time you were in download mode have held volume up 7 seconds to confirm the unlock ?
Anyways following exactly @exocetdj procedure must work...unless its not the same phone model.

Can you re flash the original stock files to go back to original state ?
I am rooting my Phone in AQQ okay. First Install AUI7? Then Install A12 BUL8 okay already works fine. Today i would Update to BVA9 but Screen goes to Apps are updating and then sucks. Restart bring's bootloop. New Install BVA9 bring's Bootloop. This Phone ist very difficult. Greetz
 

frwerewolf

Senior Member
Jan 12, 2013
121
18
I am rooting my Phone in AQQ okay. First Install AUI7? Then Install A12 BUL8 okay already works fine. Today i would Update to BVA9 but Screen goes to Apps are updating and then sucks. Restart bring's bootloop. New Install BVA9 bring's Bootloop. This Phone ist very difficult. Greetz
Did you reflash app-debug.zip (magisk) with twrp before rebooting ?
 

kepke

Senior Member
Dec 24, 2010
76
9
@exocetdj
Hello. Just installed your BVA9. Perfect. It didnt repair my problems with Samsung Gallery crashing when i want to share a picture in another app. But i use Google photo to do that instead.

Question: do you know a module to install or an apk that offers like you have in your Magisk Rom "custom power app with several reboot options" ? . The ones i have tested are not compatable with A12 yet.
Thanks a lot for these rooted methods
@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.
 

白い熊

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

白い熊

Senior Member
Aug 29, 2011
827
286
相撲道
It's actually good for other things, like rescuing a Samsung blocked system too… So it's better to have it flashed than stock.

You just need stock recovery to format /data after rooting, so that it's encrypted and Dex and sharing and stuff works…

After this I prefer flashing TWRP and staying with it – you just can't format /data from TWRP, since it'll remove encryption, and thus break Dex, sharing etc.
 

frwerewolf

Senior Member
Jan 12, 2013
121
18
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.
Nice procedure, I'll try it. Just need to downoad stock BV9 and to reinstall the whole thing
 

frwerewolf

Senior Member
Jan 12, 2013
121
18
It's actually good for other things, like rescuing a Samsung blocked system too… So it's better to have it flashed than stock.

You just need stock recovery to format /data after rooting, so that it's encrypted and Dex and sharing and stuff works…

After this I prefer flashing TWRP and staying with it – you just can't format /data from TWRP, since it'll remove encryption, and thus break Dex, sharing etc.
If You reinstall TWRP over the stock recovery to get Encryption again, will you be able to flash packages for example ? I guess it won't be possible becaise TWRP cannot access encrypted volume. .Am i right ?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    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
    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
    @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.
    3
    We now have TWRP working on A12

    Big thanks to @ianmacd for this and for @abun880007 for helping him with testing

    I will produce a much easier rooting process later and will provide the neccesary files
    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.