Database Info

[ROOT GUIDE] KNOX 0x0 NOTE 3 LTE (SM-N9005) LOLLIPOP DB 5.0 KNOX 0x0 [ROOT GUIDE]

Hello Everybody.
I have finally successfully rooted Note 3 N9005 on Android 5.0 Dev Base (DB) only, without tripping knox. The Dev base (DB) is made or compiled by Alexander on OB6 (the latest firmware). It has Multi-CSC feature and hence you will not have to worry about the CSC feature being a reason for holding you back from Rooting Note 3 N9005.
Disclaimer: I am not responsible if you mess up any of the steps and neither am I responsible for anyone bricking their phone. I have personally tested this step 3 times over to confirm its validity.
UPDATE: We have finally been able to root all LOLLIPOP without dev base. The new guide is on its way. All your data can remain, you will be able to root without having to worry about losing your DATA.
UPDATE: Here is the link to my ROM, you can replace this rom with Alexander's Dev Base in the Instruction Steps and all will be fine.
:: MEGA DOWNLOAD ::
:: DROPBOX DOWNLOAD ::
UPDATE: Added updated Links for Alexander DevBase, Bootloader and CP File.
NOTE: KNOX apps have been disabled by default by Alexander himself. Thank you Alexander.
NOTE: Moderators please move this thread to the right section. Also, please note, I will be giving credits to the original Devs for the rom and the root methods which I used common sense and made them work. All these changes will be released in the final Guide. In a few hours the whole guide with the complete step-by-step procedure will be uploaded here.
NOTE: I have written this guide on my own and have not copied anything from anywhere except the rooting process provided by W0lfDroid. If required, I will remove it and replace it with the link to the page to make it easier. But, in my opinion my steps are simpler
Things you will need.
Precautionary step: Make a backup of your PIT File just in case. You might need it though I had no need for it and its simply taking up a few KBs of Space on my PC
1). Official Stock 4.4.2 Firmware. (Grab it via Sammobile).
2). N9005XXUGBOEA_DevBase_alexndr.zip (Grab it HERE).
3). ODin v3.09. (Grab it HERE).
4). Mobile ODin Pro. (Buy it and support Chainfire).
5). SuperSU 2.46 APK. (Grab it from Google Playstore).
6). Towel Root APK v3 Offline. (Grab it HERE)
6). Device drivers. (My suggestion would be to just install Kies 2 and Kies 3).
7). ADB should be set up and accessible via CMD.
8). Root Kernel
9). Stock Kernel: NF4, NG1, NG2, NH1, NI4, NJ1, NJ2, ZTFUNJ1, NK1
10). Bootloader File (OEA – Latest as of now).
11). CP File (OD3 – Latest as of now).
Credits:
The Root Kernel and Stock Kernels are all credited to W0lfDroid.
SuperSU, Mobile ODIN Pro 4.20 are credited to Chainfire.
DevBase Rom, Bootloader File, CP File are credited to Alexander.
Towel Root is credited to Geohot.
Instructions:
Part 1: Downgrade 5.0 >> 4.4.2 (Skip this if you have 4.4.2 and move over to Part 2).
Procedure:
1). Run ODin v3.09 as Administrator.
2). Unzip the stock rom zip package that you downloaded for 4.4.2 and you will get a ".TAR.MD5" file. That is the one that you require.
3). Attach your phone in “Download Mode”. To enter this mode, turn off your phone. Press and hold POWER + MENU (Home Button) + Volume Down keys. Then a confirmation dialogue will pop up and ask you to continue to enter the mode by pressing the Volume UP key.
4). Click on AP and select the “.TAR.MD5” file extracted.
5). Make sure only "Autoreboot" and "F.Reset Time" are "checked".
6). Flash the Firmware by clicking "Start".
7). Once flashed, let your phone reboot. Should take about 10-15 mins.
NOTE: If your phone doesn't boot up after a considerable amount of time. Turn it off. Pull out the battery. Re-insert the battery and boot your phone into “Recovery Mode” by holding the Power + Menu (Home Button) + Volume UP keys. Wipe your data and cache partitions.
8). Setup your phone but better not connect it to Google/Samsung/Dropbox or any other accounts because you are going to get those wiped again.
Part 2: Rooting Note 3 on 4.4.2 (Skip this is you have a Rooted 4.4.2 phone and move over to Part 3).
Procedure:
Before starting this find your kernel version and build number, the last 3 letters/digits matter such as NG1 or NH1, etc.
Install SUPERSU 2.46 APK
1). Run Odin v3.09 and connect your phone in “Download Mode”
2). Click AP on the ODin screen and navigate and select the file Root Kernel.
3). “Auto-reboot” and “F.Reset Time” are selected and click “Start”.
4). Let it flash and reboot.
5). Install Towel Root v3 Offline APK.
6). Open the Towel Root APK now and tap “Make it rain”.
7). Install SuperSU from Playstore.
8). Update the SU Binary and Disable KNOX.
9). Reboot your phone.
10). Now flash the Stock Kernel, Follow the same steps 1 – 4 but just replace the Root Kernel with the Stock Kernel to allow you to have full functionality as Wi-Fi gets disabled with the root Kernel.
Part 3: Upgrading to Android 5.0 Lollipop Dev Base Alexander OEA.
Procedure:
1). Install Mobile ODIN Pro 4.20
2). Move the N9005XXUGBOEA_DevBase_alexndr.zip to your Internal SD Card.
3). Run Mobile ODIN Pro and choose the option OTA/Zip Update.
4). Select the N9005XXUGBOEA_DevBase_alexndr.zip file.
5). Uncheck (untick) the “Everroot” Option.
6). Flash Firmware. If it asks to verify the checksum let it, if it does not then don’t worry.
7). Let Mobile ODIN Pro do it’s thing.
8). The Aroma Installer will pop up. Leave every option as-is. The only extra options we have to select are “Wipe Data” and “Update Stock Recovery”.
9). Let it install.
10). Uncheck (untick) the “Reboot Device” option.
11). If your phone reboots, then let it start up and then DO NOT set up your phone, just hold the power button and turn it off.
12). Enter “Download Mode”.
13). Run ODin v3.09 and click on BL and select the OEA Bootloader File and click on CP and select the OD3 CP File.
14). Make sure Auto-reboot is not checked.
15). Now, hold down the power key and turn off your phone.
16). Boot into “Recovery Mode” by holding the POWER + MENU (HOME BUTTON) + VOLUME UP keys. You will see a msg at the bottom Applying Multi-csc which is essential to prevent your phone from entering boot-loop or crashing after the Samsung LOGO.
17). “Wipe Data/Factory Reset” and “Wipe Cache Partition”.
18). Reboot your phone and set it up. But DO NOT install any app, my opinion or suggestion is not to connect your google account just yet.
19). After the phone has booted, open play store and connect your GMAIL Account and install Root Checker from Playstore.
20). Do not open any app and do not install anything.
21). Turn off your phone and wait for 2 – 5 mins.
22). Turn it back on and open Root Checker and grant it SU permission.
23). Then open SuperSU, update the binary if asked and set it up as you like.
24). Have fun, you now have a Rooted Lollipop 5.0 Phone on the latest Build Number OEAwithout Tripping KNOX
Updated and Maintained as of 19th June 2015.
Consider buying me a couple of beers for my contribution
​

Nice job! I was waiting for this to update my note 3 to use new kernels. Is it possible to compile the same thing for n900w8, NB7 ? http://www.sammobile.com/firmwares/download/26653/N900W8VLUCNB7_N900W8OYACNB7_BMC/
Thanks a lot

I think my team has been able to come up with the solution.

patate331 said:
Nice job! I was waiting for this to update my note 3 to use new kernels. Is it possible to compile the same thing for n900w8, NB7 ? http://www.sammobile.com/firmwares/download/26653/N900W8VLUCNB7_N900W8OYACNB7_BMC/
Thanks a lot
Click to expand...
Click to collapse
We are trying to figure this out. If we can get this kind of rom for any phone then we will have better luck getting all lollipop phones rooted. Also I'm in the process of getting the official stock firmware installed on top of this to allow us to have official kernel installed to. But I might just flash the original kernel to avoid the hassle and check it out

XxXKINGMAKXxX said:
We are trying to figure this out. If we can get this kind of rom for any phone then we will have better luck getting all lollipop phones rooted. Also I'm in the process of getting the official stock firmware installed on top of this to allow us to have official kernel installed to. But I might just flash the original kernel to avoid the hassle and check it out
Click to expand...
Click to collapse
Nice! Sounds very good. If I understand everything about your developpement, we will be able to root it but not to flash custom rom without tripping. Is that right?

patate331 said:
Nice! Sounds very good. If I understand everything about your developpement, we will be able to root it but not to flash custom rom without tripping. Is that right?
Click to expand...
Click to collapse
Well yes. Flashing a stock rom with pre-root seems like the only case right now.

Sounds good enough for me! Awesome what you guys did, keep up the good work!

UPDATE
All variants (possibly) root knox 0x0

Thanks. worked like a charm. Just 1 suggestion. After point (14). Make sure Auto-reboot is not checked.) you can add "start odin flash" to avoid confusion. IMHO.

Yes very true. I will add it.
Also please note that I have tripped my knox in the learning process and will not continue any new guides regarding knox 0x0.
I'm quite satisfied and will now move forward towards hardcore development of Custom ROMS or development of stock ROMS with addition to more development of apps.
Check for new updates regarding new development apps that I am working on. I hope these apps become a game changer

thnks a ton KINGMAK.
Hey is there a way to saferoot stock Lollipop ROM rather than using the dev based one? Will u post a guide on that regardless of the post u added recently that u wont write guides on knox 0x0, since ur Knox is tripped I am eagerly waiting for that guide frnd.
Also, how to enable knox apps, container and all that on this dev based ROM? Is that possible?
If not, will I be able to use Knox apps, container in future? I suppose that a stock ROM should be flashed to get that. Is that?

sword_fish89 said:
thnks a ton KINGMAK.
Hey is there a way to saferoot stock Lollipop ROM rather than using the dev based one? Will u post a guide on that regardless of the post u added recently that u wont write guides on knox 0x0, since ur Knox is tripped I am eagerly waiting for that guide frnd.
Also, how to enable knox apps, container and all that on this dev based ROM? Is that possible?
If not, will I be able to use Knox apps, container in future? I suppose that a stock ROM should be flashed to get that. Is that?
Click to expand...
Click to collapse
Yes it is possible. The dev_base is not entirely different from the Stock ROM. You would need to use the same procedure but the only change that would be required is the flashing of the Stock Based ROM.
I can make a rom with KNOX apps enabled but the root in the system will always remove/disable the KNOX apps since knox tries to reset the root.
Since the very beginning of KNOX system, the security is lost when you root your device. KNOX cannot be used and I doubt anyone will ever try to make them work.
Sincerely,
KINGMAK

XxXKINGMAKXxX said:
Yes it is possible. The dev_base is not entirely different from the Stock ROM. You would need to use the same procedure but the only change that would be required is the flashing of the Stock Based ROM.
I can make a rom with KNOX apps enabled but the root in the system will always remove/disable the KNOX apps since knox tries to reset the root.
Since the very beginning of KNOX system, the security is lost when you root your device. KNOX cannot be used and I doubt anyone will ever try to make them work.
Sincerely,
KINGMAK
Click to expand...
Click to collapse
So that means should I add Stock rom from sammy (BOB6.zip) in Mobile Odin pro as mentioned in step 4. of part 3 instead of N9005XXUGBOB6_DevBase_alexndr.zip file?
If so, do i need to flash BOB6's bootloader and modem again via desktop Odin? Plz clarify..

sword_fish89 said:
So that means should I add Stock rom from sammy (BOB6.zip) in Mobile Odin pro as mentioned in step 4. of part 3 instead of N9005XXUGBOB6_DevBase_alexndr.zip file?
If so, do i need to flash BOB6's bootloader and modem again via desktop Odin? Plz clarify..
Click to expand...
Click to collapse
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.

Thank you. Followed your guide and managed to get Lollipop into my phone with root privileges. Flashed Xposed alpha via mobile odin and now my phone is stucked in a bootloop. Went to recovery to do a factory reset but it is still the same. What should I do to restore my phone?
Would it be fine following part 1 and 2 , although I am running the newest bootloader?

if i already trip my knox 0x1 can it be changed to 0x0 with this method?sorry newbie question

XxXKINGMAKXxX said:
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.
Click to expand...
Click to collapse
erevoz said:
if i already trip my knox 0x1 can it be changed to 0x0 with this method?sorry newbie question
Click to expand...
Click to collapse
No. This is to preserve 0x0. It won't change 0x1 to 0x0.

arvin2212 said:
Thank you. Followed your guide and managed to get Lollipop into my phone with root privileges. Flashed Xposed alpha via mobile odin and now my phone is stucked in a bootloop. Went to recovery to do a factory reset but it is still the same. What should I do to restore my phone?
Would it be fine following part 1 and 2 , although I am running the newest bootloader?
Click to expand...
Click to collapse
Flash the CP and Bootloader files. Then wipe your data and cache partitions am all should be fine.

Once the whole setup is complete and i wanted to debloat the rom, can i just install thru mop the dev base rom? Is it necessary to do the bl and cp again?

XxXKINGMAKXxX said:
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.
Click to expand...
Click to collapse
Thnx for the reply KingMak. But i hav few mre doubts.
1. Suppose if i use stock rom bob6.tar.md5 in mobile odin, how do we get that Rom rooted?
Should i tick everroot option and add supersu zip file and then flash to do that?
2. Does dev base (by alexndr) zip package include root installer? Is everroot option unticked for this reason?
3. Can we saferoot(knox 0x0) note 3 sm 9005 using the same method for s4 as posted by xda member Tyxerakias? Plz have a look>> forum.xda-developers.com/galaxy-s4/general/rooted-stock-lollipop-5-0-1-knox-0x0-t3061536

Nokia 3 /twrp recovery/ TA-1032 firmware

Cause my Nokia 3 was bricked then I searched for some information about Nokia 3 firmware from gsmhosting
Here is Details >----
[Nokia3_MT6737M_Heart_7.0_alps-mp-n0.mp1-V1.0.2_fih6737m.35.n_P96.rar 18.7 days old 1.3 GB 2017-Jul-15
Link
"https*://drive*.google*.com/drive/folders/0B0oLdVAk2l5va1ZlR05EVk5DXzQ"] Google drive
Upload by @pijush das
How to unlock Nokia3？Ref the threads =)
https://forum.xda-developers.com/nokia-3/how-to/guide-unlock-bootloader-root-flash-twrp-t3726649
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
how to get the unlock code?
https://forum.xda-developers.com/nokia-3/how-to/getting-unlock-code-t3757899
If you got the bricked phone, flashing the rom to rescue ,
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Require: use Chinese Miracle 2mtk(cm2mtk)tool to flash.
Finally, you need 3rd recovery to flash the supersu.
Ref https:/*/1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
twrp for nokia3
How to get the rooted phone
Maybe you can refer @JBData's tutorial like this:
After many fails, I root my Nokia3.
- You must be easy with adb and fastboot and accept a full reset of your phone (data + soft).
- USB driver ok on your PC to connect device (device is always USB connected when roadacting)
- Be developper on your device (7 click on the series number), select USB debugging.
- Unlock your device (thanks to the_lazer), so you have the orange warning when starting.
- No need of TWRP. So many attempt with it, never succed. I even try, via the shell, the install-super.sh...
- Get the stock rom archive with this excellent post.
Here is my roadacts:
/ Install MagiskManager apk (MagiskManager-v5.5.5.apk) on your device.
/ Upload the boot.img file from the stock archive on your device.
/ In MagiskManager install Magisk and select the patch method.
/ Select the boot.img uploaded.
/ Upload the boot_patch.img file created on your PC.
/ Boot your device in recovery (power + volume up)
/ Select the full reset (data + soft) : You gonna loose everything on your device ! 3 partitions are formated : /data /nvdata...
/ Boot your device in recovery (power + volume up)
/ Select bootloader.
On your PC : fastboot devices -l, so you can see the connexion.
/ Re-flash all with the patch.
fastboot flash recovery recovery.img (maybe it's not necessary, but I prefer full reset and del TWRP...)
fastboot flash system system.img
fastboot flash boot boot_patched.img
fastboot reboot
/ Your device is (re)born.
/ let the config do.
/ Unactivate android update in the developper menu
/ In MagiskManager select install Magisk
/ You can do the check SafetyNet and so everything is green (If I could upload image, you would see)
/ Install RootChecker to confirm that your device is well rooted...
Click to expand...
Click to collapse
Thanks @JakesDen
(at) THE_lazer
@SkaboXD @blackpanther0582
AND
Thank for all supports from Nokia3's users. =3

i don't think that is possible to flash twrp on locked bootloader, but i will try it.
EDIT: Nope didn't worked

confirmed, this TWRP recovery working on ta-1032 with unlocked bootloader

the_laser said:
confirmed, this TWRP recovery working on ta-1032 with unlocked bootloader
Click to expand...
Click to collapse
without bugs?

battery percentage seems to be wrong, can't decrypt originally encrypted USERDATA volume ( i'm believe it is okay ), but main things working - can install SR2-SuperSU-v2.79-SR2-20170103215521.zip and that all i want from it.
very important - not allow /system modification until supersu installation !
another note - can't enter recovery by combination volume-up + power button, if phone not connected to computer

How did you unlock it ?
Sent from my TA-1032 using Tapatalk

fastboot-android.exe -i 0x2e04 oem key <unlockcode>
fastboot-android.exe -i 0x2e04 oem unlock

Hi Volks!
I am new to Android - well, a bit late, lol. Could someone please clarify the procedure to root the TA-1032 with the assets provided in this thread?
Also, are there any caveats when using TWRP Recovery Firmware, like are official updates possible?

Swordfishx86 said:
Hi Volks!
I am new to Android - well, a bit late, lol. Could someone please clarify the procedure to root the TA-1032 with the assets provided in this thread?
Also, are there any caveats when using TWRP Recovery Firmware, like are official updates possible?
Click to expand...
Click to collapse
My advice is: DON'T do it ! At this moment there is no safe mode to have root on TA-1032 and the latest news
on the future OS on Nokia3 says the Oreo will be delivered and even Android P !! You will loose those if you proceed now with root and unlocking.
All the best !

So ... Wait and hope?

Swordfishx86 said:
So ... Wait and hope?
Click to expand...
Click to collapse
The Warranty is 2 years,the same time Nokia will provide updates to OS.So,why to rush damaging the phone ?
In 2 years will be enough time for the Wonderful guys from TeamWin to make a safe TWRP for Nokia 3.

confirmed, this TWRP recovery working on TA-1032 with locked bootloader

Petrica said:
My advice is: DON'T do it ! At this moment there is no safe mode to have root on TA-1032 and the latest news
on the future OS on Nokia3 says the Oreo will be delivered and even Android P !! You will loose those if you proceed now with root and unlocking.
All the best !
Click to expand...
Click to collapse
Lol and how slower the phone will get with all those updates ?

If there are phones with OS versions older then the latest Google Android,it is a good motiv to rush to install a custom ROM build from the newest version of Android.
But its NOT the case for Nokia series who will have the latest OS for 2 Years !
Also I remind you that NOT the Android OS(pure on Nokia) is slowing down the phone-Its the apps:look at Facebook who was 8MB at the beginning and now consume a lot of resources-is almost 300 MB and is doing the same thing as was 8Mb .
All the best LOL !

Petrica said:
If there are phones with OS versions older then the latest Google Android,it is a good motiv to rush to install a custom ROM build from the newest version of Android.
But its NOT the case for Nokia series who will have the latest OS for 2 Years !
Also I remind you that NOT the Android OS(pure on Nokia) is slowing down the phone-Its the apps:look at Facebook who was 8MB at the beginning and now consume a lot of resources-is almost 300 MB and is doing the same thing as was 8Mb .
All the best LOL !
Click to expand...
Click to collapse
but it's still better to have custom roms because they have a lot more customization, wider compatibility with apps (for example xposed), better performance, maybe better battery if greatly optimized for our devices.
Also if we flash some custom rom, data encryption will be automatically removed.

SkaboXD said:
but it's still better to have custom roms because they have a lot more customization, wider compatibility with apps (for example xposed), better performance, maybe better battery if greatly optimized for our devices.
Also if we flash some custom rom, data encryption will be automatically removed.
Click to expand...
Click to collapse
With encryption eliminated you'll have boost in performance but this boost is lost due to not so greatly optimization of unofficial roms.
Sent from my TA-1032 using Tapatalk

Max brackenz said:
confirmed, this TWRP recovery working on TA-1032 with locked bootloader
Click to expand...
Click to collapse
Did you actually get twrp with a locked bootloader or that was a typo?

redweaver said:
Did you actually get twrp with a locked bootloader or that was a typo?
Click to expand...
Click to collapse
yes. its true . i flashed with spflashtool.

Max brackenz said:
yes. its true . i flashed with spflashtool.
Click to expand...
Click to collapse
Which spflashtool did you use? The usual one or a specialised one

redweaver said:
Which spflashtool did you use? The usual one or a specialised one
Click to expand...
Click to collapse
usual one. i have a nokia 3 support DA file.

S7 edge SM-G935F remove root/ back to stock

Hello all, i have some questions. I owe model S7 edge SM-G935F.
On weekend i tried to flash it and install TWRP and Magisk Manager - manaed to install it and play a round.
Now changed my mind and want to get back to official firmware which i was using before. At the moment i can access TWRP ( i wiped everyting) , but if i boot to system it just stays in ODIN dowload mode ( probably because i wiped everyting)
Before work today i left downloading official rom with latest security patch. After work will flash on official ROM.
After flashing do i need to enable/disable any settings inside phone to receive latter OEM updates? Can i lock bootlader? Or it will be locked automatically when i flash stock firmware.
Thanks

Vinni777 said:
Hello all, i have some questions. I owe model S7 edge SM-G935F.
On weekend i tried to flash it and install TWRP and Magisk Manager - manaed to install it and play a round.
Now changed my mind and want to get back to official firmware which i was using before. At the moment i can access TWRP ( i wiped everyting) , but if i boot to system it just stays in ODIN dowload mode ( probably because i wiped everyting)
Before work today i left downloading official rom with latest security patch. After work will flash on official ROM.
After flashing do i need to enable/disable any settings inside phone to receive latter OEM updates? Can i lock bootlader? Or it will be locked automatically when i flash stock firmware.
Thanks
Click to expand...
Click to collapse
No. If you flash full firmware you will receive oem updates again. You need to unlock developer settings and disable oem unlock to lock bootloader

kpwnApps said:
No. If you flash full firmware you will receive oem updates again. You need to unlock developer settings and disable oem unlock to lock bootloader
Click to expand...
Click to collapse
Thanks for reply. Will do today.
Can i flash using latest odin or i need patched version?
I know its rookie questions, but i was allready stressed to go work without phone as i run out of time yesterday.
Most important for me to get OEM updates and be able use Sam Pay and Etc.

Vinni777 said:
Thanks for reply. Will do today.
Can i flash using latest odin or i need patched version?
I know its rookie questions, but i was allready stressed to go work without phone as i run out of time yesterday.
Most important for me to get OEM updates and be able use Sam Pay and Etc.
Click to expand...
Click to collapse
You need to get the latest odin version because of the lz4 format of the firmware files. Unfortunately you cannot use sampay and knox again because of tripped warranty void

kpwnApps said:
You need to get the latest odin version because of the lz4 format of the firmware files. Unfortunately you cannot use sampay and knox again because of tripped warranty void
Click to expand...
Click to collapse
Thanks mate. I managed yesterday to flash on latest software and everything works perfectly apart Sam Pay and Sam Health Offcourse android pay and etc works fine.

[S20_FE SM-G781U/U1_Snapdragon]-[Upgrade Easily Firmware Using Odin]-[Automatically Root Remove Forceencrypt Patch Bluetooth And Fix Safetynet]

Must Have An Unlocked Bootloader To Do This!
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install magislk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2
I Do Not Recommend Mixing Bit 1 With Higher Firmware!!!!
Unless Using Bit Safe Firmware That Is Patched​
Downloads
SM-G781U/U1/W- Model
USERDATA_AIO_S20FE_5G_FORCE_WIPE_10_10_21.tar.md5
This will force a wipe of data no mater what.
Full Odin 3.1.1 Bit1 Safe Firmware
G781USQS6DUI1_BIT1_SAFE.7z Thanks @markfm
This are odin files and will safely update all image files too bit 4 and keep bit 1 bootloaders. Unfortunately this will wipe data this is beyond my control as it seems to be a side affect of mixing firmware it causes data not to mount and therefore my AIO will format it. This is full firmware with USERDATA_AIO. This will put you on U firmware. Before flashing I recommend removing your google account and make sure in download mode you are not frp locked
If above USERDATA_AIO_G78*_FORCE_WIPE_NO_BL is newer than the one in this zip use the newer one from above
Odin3_v3.14.1_3B_PatcheD.zip
TWRP Recovery Provide by afaneh92
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions For Newly Unlocked Devices
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load file USERDATA_SLOT_G78*U_**.tar.md5 you must choose one of the FORCE_WIPE files and load in the USERSDATA slot of odin and flash file
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Install Instructions For Updating Firmware On Phone Already Unlocked
1. Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above
2. Use patched 3.14 odin and load stock firmware in appropriate slots use regular CSC file in the CSC slot and load file one of the USERDATA_SLOT_G99*U_**.tar.md5 in the USERSDATA slot of odin and flash firmware. Do not use the User Data file that comes with firmware.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not
Install Instructions If Updating Images With TWRP
1. When done flashing images in TWRP Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above.
2. Use patched 3.14 odin and load file USERDATA_AIO_G78*_NO_WIPE_NO_BL.tar.md5 in the USERSDATA slot of odin and flash file.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not.
4. Alternatively to using USERDATA_AIO_G78*_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_22_S20_Series.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
elliwigy
klabit87
Krog18
me2151
stang5litre
Raymonf for modified odin
rayan-refoua for boot animation
TheMadScientist
afaneh92
kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
JDBarlow for test S20 stuff
Xylvion for testing s21
dark11b for testing s21

Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Z Fold2 5G BL V1
Fold 5G BL V1-4
Fold BL V1-4
Z Flip 5G BL V1
Z Flip BL V1-3
Note series 20 BL V1
S20 series BL V1
S20 FE 5G BL V1-2
Note 10 series BL V1-5
S10 Lite BL V1-3
Note 10+ 5G N976U BL V1-4
Note 10+ 5G N976V BL V1-5
S10 5G BL V1-5
S10 series BL V1-4
Note 9 BL V1-7
S9 series BL V1-9
Tab S6 BL V1-3
Tab S7 BL V1
Tab S7+ BL V1
A71 5G BL V1-2
A51 BL V1-5
A51 5G BL V1-4
A50 A505W BL V1-A
A50 A505U BL V1-B
S21 BL V1
A32 5G BL V1-3
Tab Active Pro 10.1 BL V1-4
XCover Pro BL V1-7

jrkruse said:
G781U / Twrp
Click to expand...
Click to collapse
Evening
Will this work on the G781B?
Does your version of twrp support the external SD card?

b1k3rdude said:
Evening
Will this work on the F781B?
Does your version of twrp support the external SD card?
Click to expand...
Click to collapse
im sure it will work on that mode. I use afaneh’s twrp so if it works for you then it will work I imagine

jrkruse said:
im sure it will work on that mode.
I use afaneh’s twrp so if it works for you then it will work I imagine
Click to expand...
Click to collapse
I dont follow, did you mean device?
afaneh’s twrp dosent support external SD card access yet (see his thread).

b1k3rdude said:
I dont follow, did you mean device?
afaneh’s twrp dosent support external SD card access yet (see his thread).
Click to expand...
Click to collapse
Then flash different twrp when done. I don’t have the device so im not sure

jrkruse said:
Then flash different twrp when done. I don’t have the device so im not sure
Click to expand...
Click to collapse
Unfortunatly his is the only one that works, hence asking about yours when your thread appeared.

b1k3rdude said:
Unfortunatly his is the only one that works, hence asking about yours when your thread appeared.
Click to expand...
Click to collapse
Sorry but I just use his twrp so I guess the problem will persist

jrkruse said:
Must Have An Unlocked Bootloader To Do This!
This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install magisk root along with remove force encryption and patch bluetooth library file. It will also patch safetynet. No flashing of zips is required
Info For Bootloader Unlocks Can Be Found In Post 2​
Downloads
SM-G781U/U1- Model
USERDATA_AIO_G781_FORCE_WIPE_NO_BL.tar.md5
This will force a wipe of data no mater what. This Must Be Used On U1 Firmware and can be used on U firmware if you choose so.
USERDATA_AIO_G781_NO_WIPE_NO_BL.tar.md5
This will only wipe if you have encrypted data. This Can Only Be Used On U firmware
Odin3_v3.14.1_3B_PatcheD.zip
TWRP Recovery Provide by @afaneh92
Be prepared to have your data wiped. The process tries to determine if you do or do not need to have data wipe but as a precaution just assume your data will be wiped. Especially if using U1 or W firmware
Install Instructions For Newly Unlocked Devices
You must be OEM Unlocked Bootloader
1. On Initial unlock of phone you must through setup and be signed into your google account.
2. Reboot phone too download mode and make sure KG STATUS=CHECKING (see pic) and not PRENORMAL. If PRENORMAL then do step 1 again
View attachment 5217631
3. Use patched 3.14 odin and load file USERDATA_SLOT_G78*U_**.tar.md5 you must choose one of the FORCE_WIPE files and load in the USERSDATA slot of odin and flash file
4. Phone will reboot to TWRP and remove encryption which will wipe phone. Phone will reboot back too TWRP to finish install then reboot to setup
Install Instructions For Updating Firmware On Phone Already Unlocked
1. Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above
2. Use patched 3.14 odin and load stock firmware in appropriate slots use regular CSC file in the CSC slot and load file one of the USERDATA_SLOT_G78*U_**.tar.md5 in the USERSDATA slot of odin and flash firmware. Do not use the User Data file that comes with firmware.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not
Install Instructions If Updating Images With TWRP
1. When done flashing images in TWRP Reboot phone too download mode and make sure KG STATUS=CHECKING. If not see above.
2. Use patched 3.14 odin and load file USERDATA_AIO_G78*_NO_WIPE_NO_BL.tar.md5 in the USERSDATA slot of odin and flash file.
3. Phone will reboot to TWRP and check for encryption and remove if needed which will wipe phone. If phone is not encrypted data will not be wiped. Phone will reboot back too TWRP to finish install then reboot to setup if data was wiped or reboot normally if it was not.
4. Alternatively to using USERDATA_AIO_G78*_NO_WIPE_NO_BL.tar.md5 in odin you can use AIO_Magisk_22_S20_Series.zip found in post 2
Features
No patches or mod zips are needed phone will already be rooted
Fix Safetynet
Bluetooth is patched for pairing to survive reboots
Samsung Health working
Bugs
Samsung Pay, Secure Folder and Samsung Pass do not work as on most Samsung Rooted Roms
Thanks To People That Make My Life Easier
@elliwigy
@klabit87
@Krog18
@me2151
@stang5litre
@Raymonf for modified odin
@rayan-refoua for boot animation
@TheMadScientist
@afaneh92
@kdrag0n for safetynet fix
3arthur6 for bluetooth patch zip
@JDBarlow for test S20 stuff
Click to expand...
Click to collapse
Is that this model SM-G781UZBZAIO thats from samsung website for cricket model which I expect shortly. Ive used odin before .

jrkruse said:
im sure it will work on that mode. I use afaneh’s twrp so if it works for you then it will work I imagine
Click to expand...
Click to collapse
So you can make twrp backup in recovery mode to your external storage?

Tigerevo said:
So you can make twrp backup in recovery mode to your external storage?
Click to expand...
Click to collapse
did you even read the above post. I think this has been answered. The answer is no

Van u help me to pay for bootloader unlock fro samsung s20 f3 sm-g78u

CHINOGAMBINO said:
Van u help me to pay for bootloader unlock fro samsung s20 f3 sm-g78u
Click to expand...
Click to collapse
if you got the phone via a network you're paying your monthly bills with money, if you bought the phone outright you paid for it with money. unless you've bought a stolen or lost phone for very very cheap you have money.

Can you pleaseeeee make it for u2????!!!!

Hi, could you please share the method ?
I would like to do the same on G781B with CSC XEF:
Download Samsung Galaxy S20 FE 5G SM-G781B XEF France firmware
All Samsung firmwares for Galaxy S20 FE 5G in France with model code SM-G781B. We offer free and fast download options. Check them out now.
www.sammobile.com

Deleted - dumb question...

So why TWRP cannot access external SD card? Back in the day when I had Motorola X Pure Edition unlocked and rooted with TWRP installed I was using my SD card as the backup location. What differs?

Hitti2 said:
So why TWRP cannot access external SD card? Back in the day when I had Motorola X Pure Edition unlocked and rooted with TWRP installed I was using my SD card as the backup location. What differs?
Click to expand...
Click to collapse
the dev doesn't actually have the phone in his hands and google has changed how android works quite a bit under the hood.

Can you elaborate on how the safetynet is fixed
does it use the kdrag0n module

is this working on SM-G781W ?

How To Guide [Root] Samsung Galaxy A52 SM-A525F Magisk Root

Root Samsung Galaxy A52 SM-A525F Android 11 Official - AUC4 Firmware. TWRP Recovery for Galaxy A52 Android 11 does not available yet when I posted this rooting guide. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Rooting Instructions ( Don't make mistake )
Make sure the bootloader are unlocked, OEM unlock option is grey out
Patch boot.img then Pack it to magisk_patched.tar. If you don't want to do it by your self, you can download it from link below
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN
Insert magisk_patched.tar in AP, then click start. The phone will rebooting to ANDROID RECOVERY MODE
in ANDROID RECOVERY, Select Factory data reset and press power key to confirm
select 'Factory data reset' again and confirm
Setup the phone
Connect to Internet
Install and Open Magisk App, it will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Download
magisk_patched
Telegram: https://t.me/SamsunGalaxyA52
Watch This Video Tutorial

Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.

Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?

<deleted>

VonSparq said:
Any way to get rid of the "PRESS POWER KEY TO CONTINUE"?
Click to expand...
Click to collapse
On qcom devices, not really. Even on exynos devices after removing that you still need to physically press the power button or if you don't wanna even do that you have to w8 bout 10 to 15 extra seconds..

hansxl said:
Thanks, nice job. Only problem is that I get daily spontaneous reboots. E.g. I try to activate fingerprints and the phone asks me to start scanning my fingerprint it reboots.
Click to expand...
Click to collapse
Okay, solved. Flashed latest firmware (AUC5) and patched boot.img with Magisk. Fingerprints works now and no reboots so far

Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?

Rerel14 said:
Glad to see it's working. I just purchased the device today but I don't have a PC with Windows, I'm on Ubuntu. Would it work as well using Odin for Mobile ? Does a version of Odin exist for Linux ?
Click to expand...
Click to collapse
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com

hansxl said:
Sorry I'm not a Linux user, but if you google for Odin and Linux/Ubuntu you results like:
Odin3 v3.11.1 Flash Tool [Windows, Mac & Linux] – Odin Downloader
Download Odin3 v3.11.1 for Windows, Mac and Linux Systems. Odin downloader helps in flashing Firmware files, Root files, Recovery files, and other patch files to Samsung Android devices. Odin Flash Tool (Odin3 v3.11.1.zip) also allows the user to Unbrick the Samsung Phone.
odinflashtool.com
[Utility] Odin for Linux !!! (JOdin3 CASUAL)
I have finally found a working version of Odin for Linux! JOdin 3 Casual powered by Heimdall You need at least Java 8, if you don't have it already: To see the java version type: java -version Aptitude Package Manager: sudo add-apt-repository...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?

Rerel14 said:
Thank you for your reply, I'll take a look at that.
I have a other question : I checked the firmware and it's AUB5. I guess I can't use the file attached in the post and I need to patch boot.img as described here :
(I assume it's the same for any samsung device...) ?
Click to expand...
Click to collapse
Yes, it's more or less the procedure. But I would just download the latest magisk (22.1) from
Magisk v22.1 brings an improved log writer, resetprop bootloop fixes, and much more
The latest stable update for Magisk (v22.1) has been released with tons of bug fixes and feature improvements. Read on to know more!
www.xda-developers.com
the UI is a bit different from the one in your video

My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?

Rerel14 said:
My phone had an update, I'm on firmware (AUC5) now. I tried to patch boot.img with Magisk and install it with Odin but I got a message FAILED. Don't know whether the problem comes from a bad procedure during patching AUC5 boot firmware or a problem with ODIN. I activated "USB debogging" in settings which is not specified in the instructions above, can it be the problem ? Any idea ?
Click to expand...
Click to collapse
bootloader unlocked

hansxl said:
bootloader unlocked
Click to expand...
Click to collapse
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?

Rerel14 said:
Yes OEM unlocked and USB debugging unlocked. When I connected the phone via Odin it was well recognized, the Id Com was blue but I when click on start button I had a failed message. Don't remember if there was a specific message but I think there wasn't (may be I could try again). My device model is SM-A525F/DS and baseband version A525FXXU1AUC5.
Coul it be that I didn't patch the boot.img correctly ?
If I'm correct you flashed latest firmware (AUC5) and patched boot.img with Magisk and everything went fine, right ?
Click to expand...
Click to collapse
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also

hansxl said:
just to be sure, oem unlocked means it's permitted to unlock bootloader, but did you really unlocked bootloader also
Click to expand...
Click to collapse
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?

I think I found one :

Rerel14 said:
OK, I think you pointed the problem. I checked the option in the dev options but that's all I did. I assume that's why it is not grey as described in the video above.
Where can I found a reliable tuto on how to unlock bootloader ?
Click to expand...
Click to collapse
How To Unlock Samsung Galaxy A52 Bootloader - NaldoTech
In this tutorial, you will learn how to unlock the bootloader on your Samsung Galaxy A52. A bootloader is the piece of code that runs before the operating
www.naldotech.com
don't forget to backup your data. I think after unlocking bootloader your phone will return to factory settings

I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?

I installed Magisk from an other source and eventually I succeeded to get root !
Huge thanks Hansxl for your help and patience. Really appreciated it.
Last question : if I update the firmware I'll need to make the full procedure described above again ?

Rerel14 said:
I'm getting closer but still not performed yet...
Bootloader unlocked successfully
Installation via Odin successfull
When I want to install Magisk I have an error message : "There was a problem while parsing the package"
I allowed Magisk in "Install unknown apps" but I stuck anyway with that message.
Should I install Magisk from an other source ?
Click to expand...
Click to collapse
deinstall magisk and install magisk again