[ZSKF] Galaxy S10e (SM-G97xF) OFFICIAL OneUI2/10 beta (NO ROOT/CUSTOM ROM TALK!!!) - Samsung Galaxy S10e Guides, News, & Discussion

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Because I use the expertise from henklbr to make this seperate issue for Samasung Galaxy S10e, I want to thank him
ADB-method:
1. Download SDK platform tools from here https://developer.android.com/studio...platform-tools
2. Extract them on your desktop.
3. Inside the extracted folder put the update.zip
4. Inside this folder, holding left shift, right click the mouse and select "open command prompt here". The command prompt will open.
5. Shutdown the phone.
6. Holding power+bixby+volume up buttons, enter into recovery mode.
7. Select "update via ADB". (you scroll down using the volume buttons and select using the power button).
8. Connect the phone to the PC using original samsung USB cable.
9. In the command prompt run the following command:
./adb devices
10. Wait to see that the daemon has started and that your device is found.
11. If you device is found, run the following command:
./adb sideload update.zip
The update process will start. You will see a percentage counting. First it will verify, then patch etc. Do not move the cable, disconnect the phone or power off the PC.
Once the process is completed (it takes some time) the phone will boot itself, update the apps and log into your home screen.
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options in win10 you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Hold simultaneously Power+bixby+volume up buttons to get into stock recovery.
5. Using your volume keys navigate to "update via SdCard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes. It will take some time.
8. Phone will reboot by itself and load android.
This will not trip KNOX if done by the method i told
NOTE: THESE UPDATE.ZIP's ARE ONLY FOR DEVICES WITH MULTI-CSC OXM!!!
You can check this, to type in your dialer *#1234#, and check if OXM is in the CSC-build...
Beta1 (14 Oct) ASII -> ZSJ8: G970F_ASII_ZSJ8
http://fota-secure-dn.ospserver.net/...k1BQfoG43U+3c=
Known BUG: https://forum.xda-developers.com/sho...&postcount=161
Beta2 (25 Oct) ZSJ8 -> ZSJF: G970F_ZSJ8_ZSJF
http://fota-secure-dn.ospserver.net/...xtVupQ4zpu2lE=
Needs to be installed with the "SD-Card method"!
RENAME THE FILE TO update.zip
You will find beta 3, beta 4 and beta 5 in post 2
You will find beta 6 in post 6
You will find beta 7 in post 9
You will find Stable/Final (28 Nov) in post 10
NOTE: after installing the update, CLEAR your cache by going into recovery (VolUP - Bixby - Power)
If you want to run the BETA-firmware flawlessly, do a FACTORY-reset afterwards... (not necessary, but... )
UPDATING to Beta is your own choice, and I don't take responsibility if something is going wrong!
If you're NOT officially registered, you WON'T receive OTA: you'll have to update everytime MANUALLY with above method!!!
If you want to DOWNGRADE back to Pie: download the latest Pie-firmware for your own CSC, flash AP BL CP & CSC_OXM -> your device will reset afterwards which is mandatory!
Greetzzz, Henk.
You must use above if you are on G970F_ASII

EMERGENCY UPDATE (29 Oct) ZSJF -> ZSJL: G970F_ZSJF_ZSJL
http://fota-secure-dn.ospserver.net/...Kt30eJ4JXeDQE=
If your phone is on G970F ASJG look at post 3: you don't need beta1, beta2 and emergency update..
Beta3 (07 Nov) ZSJL -> ZSK3:
http://fota-secure-dn.ospserver.net/firmware/DBT/SM-G970F/nspx/7d8c60670fc14b4ab99db4a58dc07edf.bin?px-time=5e15c69b&px-hash=6d92fa484b2a55f8ec814f5812749a3e&px-wid=56720191109-WSA76840831&px-wctime=2019-11-09%2012:09:57.0&px-unum=2FW3ezZxYmUvolmac0CfCi0Aqg7sX/l4AmJs0dXEnEU=&px-nb=UGtezEZ854jbmFcvWGxLEA==&px-nac=g2/EC9sWD3aMZZDMG4GJNL7PoD/dD5Kt30eJ4JXeDQE=
S10e: Beta4 (15 Nov) ZSK3 -> ZSK9: G970F_ZSK3_ZSK9
http://fota-secure-dn.ospserver.net/firmware/DBT/SM-G970F/nspx/c16ea0c3307043c4b26b76affadbb501.bin?px-time=5e1d85b5&px-hash=aa0db8e4c79b96e6ba9a1724dca061ee&px-wid=20220191115-WSA54192764&px-wctime=2019-11-15%2009:11:14.0&px-unum=2FW3ezZxYmUvolmac0CfCi0Aqg7sX/l4AmJs0dXEnEU=&px-nb=UGtezEZ854jbmFcvWGxLEA==&px-nac=g2/EC9sWD3aMZZDMG4GJNL7PoD/dD5Kt30eJ4JXeDQE=
Beta5 (18 Nov) ZSK9 -> ZSKF: G970F_ZSK9_ZSKF (thanks to @Robert Smali)
http://fota-secure-dn.ospserver.net/firmware/PHE/SM-G970F/nspx/a9e0befdad6f4413a0ce8eddef8e6fef.bin?px-time=5e21c721&px-hash=5bdbf141cc018bb36b2bf4dcff477948&px-wid=96420191118-WCB46710733&px-wctime=2019-11-18%2014:39:28&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==&px-nac=AkiC0ae8BFw/JOl8sSMgNAC4f3w7U42d3PkvOPNrWs4=

New!! S10e G970F Beta 3 link OTA.
From Android 9 ASJG to Android 10 beta 3 ZSK3 ONLY!!
G970F ASJG->ZSK3 G970F_ASJG_ZSK3
http://fota-secure-dn.ospserver.net/firmware/PHE/SM-G970F/nspx/ca605ad6d980438e8d70a9d98a8e61fb.bin?px-time=5e12d906&px-hash=a27315bc498618bdafd120d71e7176e6&px-wid=28520191107-WCB64585695&px-wctime=2019-11-07%2006:51:48&px-unum=&px-nb=zxkBmlUlhe9OuEcZtFyo8w==&px-nac=AkiC0ae8BFw/JOl8sSMgNAC4f3w7U42d3PkvOPNrWs4=

i used this file but get error
E:Signature verification failed
E:error 21
Click to expand...
Click to collapse
my devices run is G970FXXS3ASJG

letruong127646 said:
i used this file but get error
my devices run is G970FXXS3ASJG
Click to expand...
Click to collapse
I got this when trying the SD method but it worked ok using the ADB method. Use adb ffrom 1st post.

Beta6 (21 Nov) ZSKF -> ZSKJ: G970F_ZSKF_ZSKJ
http://fota-secure-dn.ospserver.net/firmware/DBT/SM-G970F/nspx/8661a9a2c0b846f982e3a414ae02c3fb.bin?px-time=5e25675b&px-hash=2b2e0e26812e2b3cd28fca813ea0175f&px-wid=71320191121-WSA29522152&px-wctime=2019-11-21%2008:39:48.0&px-unum=2FW3ezZxYmUvolmac0CfCi0Aqg7sX/l4AmJs0dXEnEU=&px-nb=UGtezEZ854jbmFcvWGxLEA==&px-nac=g2/EC9sWD3aMZZDMG4GJNL7PoD/dD5Kt30eJ4JXeDQE=
Update via SD-Card method!
RENAME THE FILE TO update.zip
NOTE: after installing the update, CLEAR your cache by going into recovery (VolUP - Bixby - Power)
If you want to run the BETA-firmware flawlessly, do a FACTORY-reset afterwards... (not necessary, but... )
UPDATING to Beta is your own choice, and I don't take responsibility if something is going wrong!
If you're NOT officially registered, you WON'T receive OTA: you'll have to update everytime MANUALLY with above method!!!
If you want to DOWNGRADE back to Pie: download the latest Pie-firmware for your own CSC, flash AP BL CP & CSC_OXM -> your device will reset afterwards which is mandatory!

How does it look if the firmware is final or the future firmwares? If you install the BETA without registration via MicroSD. If you get these via OTA or you have to downgrade to get OTA updates.

[email protected] FX said:
How does it look if the firmware is final or the future firmwares? If you install the BETA without registration via MicroSD. If you get these via OTA or you have to downgrade to get OTA updates.
Click to expand...
Click to collapse
If you're NOT officially registered, you WON'T receive OTA: you'll have to update everytime MANUALLY with above method!!!
First time I think you have to use Odin 3.13.3 for your own CSC and after that you shall get OTA updates.

Beta 7 is out now.
Beta7 (25 Nov) ZSKJ -> ZSKL: G970F_ZSKJ_ZSKLhttp://fota-secure-dn.ospserver.net/firmware/INS/SM-G970F/nspx/7069d92ffae7419896abd65fce952f95.bin?px-time=5e2a91cf&px-hash=f19065f7d56430fdcbfe3fbc91654195&px-wid=57320191125-WSA80659135&px-wctime=2019-11-25%2006:42:20.0&px-unum=ZtPfUYBTugN9xGp7oERXXT1qDFHylb1jQDFFa5UX27Q=&px-nb=UGtezEZ854jbmFcvWGxLEA==&px-nac=L2+zIHzZBZqz6LWz7hxJ0uQG3gmZbZvKUyNtr3nlj4o= (Thanks to SamMobile)
Update via SD-Card method!
RENAME THE FILE TO update.zip

Stable/Final (28 Nov) ZSKL -> BSKO: G970F_ZSKL_BSKO
http://fota-secure-dn.ospserver.net/firmware/DBT/SM-G970F/nspx/ae6ae47d9a8c45918f0c86f234c9cae5.bin?px-time=5e2eab24&px-hash=1410a08e2643d667faa6b8afb0535f21&px-wid=06120191128-WCC03371167&px-wctime=2019-11-28%2009:19:28&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA==&px-nac=g2/EC9sWD3aMZZDMG4GJNL7PoD/dD5Kt30eJ4JXeDQE=
RENAME THE FILE TO update.zip
NOTE: after installing the update, CLEAR your cache by going into recovery (VolUP - Bixby - Power)
If you want to run the BETA-firmware flawlessly, do a FACTORY-reset afterwards... (not necessary, but... )
UPDATING to Beta is your own choice, and I don't take responsibility if something is going wrong!
If you're NOT officially registered, you WON'T receive OTA: you'll have to update everytime MANUALLY with above method!!!
If you want to DOWNGRADE back to Pie: download the latest Pie-firmware for your own CSC, flash AP BL CP & CSC_OXM -> your device will reset afterwards which is mandatory!

The stable build of Android 10 / OneUI 2.0 has been released today in Germany.
Model SM-G970F
Model name Galaxy S10e
Country Germany (DBT)
Version Android 10
Changelist 17369399
Build date Tue, 26 Nov 2019 14:08:29 +0000
Security Patch Level 2019-12-01
Product code DBT -----> OXM
PDA G970FXXU3BSKO
CSC G970FOXM3BSKO
You can download it from https://www.sammobile.com/samsung/ga...U3BSKO/304048/ or with SamFirm and flash it with Odin v3.13.3.

Release build was offered OTA to the UK after 4pm local time.

pinsb said:
Release build was offered OTA to the UK after 4pm local time.
Click to expand...
Click to collapse
I opened a new site OFFICIAL STOCK FW-update (Odin) thread (28 Nov 19) GALAXY S10e SM-G970F, because beta is over now. https://forum.xda-developers.com/galaxy-s10e/how-to/bsko-official-stock-fw-update-odin-t4011867

@Idebutterpiep I'm encountering 403 Forbidden when I attempt to download any of these betas.
I am on Samsung Galaxy S10e (SM-G970F) Beta 1 (ZSJ8), and would like to upgrade all the way to BSKO (Android 10 stable).
Is there anywhere I can still download the betas 2 through 7 and the beta 2 emergency update? Thanks very much for anything you can do.

bran-muffin said:
@Idebutterpiep I'm encountering 403 Forbidden when I attempt to download any of these betas.
I am on Samsung Galaxy S10e (SM-G970F) Beta 1 (ZSJ8), and would like to upgrade all the way to BSKO (Android 10 stable).
Is there anywhere I can still download the betas 2 through 7 and the beta 2 emergency update? Thanks very much for anything you can do.
Click to expand...
Click to collapse
I cannot help you anymore. Try to go back Android 9. Factory reset and then download the Android 10 for your phone and try to flash with Odin.
Good luck.

Related

Umidigi A3 Pro - TWRP & Stock Rom

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reserved exclusively for the stock rom V1.0_20181122
Download the stock rom V1.0_20181122 at the following link :
https://mega.nz/#!yxkUVA4I!0exovcsKTXb75YIBZfrqDC6Ak01wsv_Bp3Nl5mGQ7o8
Download the TWRP at the following link :
https://mega.nz/#!G510QIbL!sbPzFXUi1Nw5mPFZZOsejeES7-togQxg9mrUNjAeWrA
Download "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip" at the following link :
https://mega.nz/#!a092gK4A!SYjKF4EUujCmCfkDG5LJL1vJygij0Ure4bFhxVuCjX0
Download "Bu_&_Ma.rar" (Busybox & Magisk) at the following link :
https://mega.nz/#!C9lUjCqT!fBoh8p1Jg7pwbVRg8KQWKKs-eXH1eHq67_IKb1IUyyw
Please follow very carefully all the next steps :
1) Copy "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip" onto your microSD.
2) Unrar "Bu_&_Ma.rar" and copy Busybox zip & Magisk zip onto your microSD.
3) Flash the stock rom V1.0_20181122 through SP Flash Tool.
I strongly recommend the "Firmware Upgrade" option (on SP Flash Tool).
4) Tap on Settings --> System --> About phone
5) Tap seven times on Build number
6) Then, tap on Developer options.
7) Enable OEM unlocking & USB debugging.
8) Unrar the TWRP rar.
9) Run SP Flash Tool.
10) Load the scatter file inside the twrp folder.
11) Select Download Only option.
12) Click Download.
13) Connect your turned off phone to the pc with USB cable.
14) When at 100% please disconnect the USB cable.
15) Enter onto twrp recovery (volume up + power buttons simultaneously).
FUNDAMENTAL STEP
16) Select the first white line with volume up.
17) Press volume down to confirm.
18) Select language
19) "enter password" tap on cancel
20) Tap on WIPE
21) Tap on FORMAT DATA (type yes).
Consideration :
FORMAT DATA will wipe your internal storage.
I suggest you to make a backup before to format Data.
22) Return to the twrp home screen.
VITAL STEP
23) Tap on Reboot and choose Recovery.
DO NOT reboot your device onto System !
Tap on Do Not Install.
24) Tap Install, Select Storage, Micro SDCard, OK.
25) Tap on "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip".
26) Swipe to confirm Flash.
Consideration about "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip" :
Many thanks to @Zackptg5 for this zip.
This zip disable Dm-Verity, Forced Encryption, and Disc Quota Disabler.
Like Zackptg5 says :
"This zip should be flashed after anything that modifies your boot img (like a custom kernel) but before magisk/supersu since this zip creates the files that tells magisk/supersu to not encrypt".
27) Tap on Magisk.zip
28) Tap on Busybox.zip
29) Swipe to confirm Flash.
30) Tap on Reboot (into System) and tap on Do Not Install.
31) Be patient.
32) Set up as new.
33) Tap on Settings --> System --> About phone
34) Tap seven times on Build number
35) Then, tap on Developer options.
36) Enable OEM unlocking & USB debugging.
EXTREMELY VITAL :
37) Tap on Magisk Manager.
38) Upgrade to full Magisk Manager.
NOW you can see NOT ROOTED phone :
39) Reboot the phone.
NOW you can see ROOTED phone :
UPDATE
UPDATE - NEW STOCK ROM & NEW TWRP
TWRP reserved exclusively for the stock rom V1.1_20181211
Download the NEW stock rom V1.1_20181211 at the following link :
https://mega.nz/#!G9kwVSrT!yiS38SKmPfOGkKSCfrum4OzD2T2SKpctmUBr3fIBPNo
Download the NEW TWRP at the following link :
https://mega.nz/#!uwkkQYCb!Sb5ObKguewDLDE0Z3ma4m-W5KjZ28TUiK6QbrCm3cN8
Update - 01
UPDATE - NEW TWRP 3.2.3-0
There are two TWRPs :
The first TWRP is reserved exclusively for the stock rom V1.0_20181122
The second TWRP is reserved exclusively for the stock rom V1.1_20181211
Please follow very carefully all the steps at the first post.
Both TWRPs are available on Needrom
UPDATE
UPDATE - NEW STOCK ROM & NEW TWRP
GUIDELINES FOR THE INSTALLATION OF THE OTA ZIP
Please follow carefully all the next steps in order to install properly the OTA zip :
1) Flash the stock rom V1.1_20181211 (Firmware Upgrade option on SP Flash Tool).
2) Set up as new.
3) Download the OTA zip (V1.2_20181221_update .rar) at the next link :
https://mega.nz/#!bpsxxCCb!k-G1ndw1iygOsr1VQ_IM1xhEcm-mMJAxoxHMTSqZk-s
4) Unrar the V1.2_20181221_update.rar
5) DO NOT unzip the update.zip
6) Copy the entire folder "V1.2_20181221_update" onto your microSD.
7) Turn off your phone.
8) Hit simultaneously volume up + power buttons.
9) Hit the volume up button to select Recovery mode.
10) Dead Android and red triangle error - NO PANIC
11) Hit simultaneously volume up + power buttons several times.
12) Hit the volume up or volume down buttons to move between the options.
13) Hit the power button to select any option.
14) Select Apply update from SD card.
15) Select the folder "V1.2_20181221_update" onto your microSD.
16) Select the update.zip
17) Hit power button to start the installation process.
18) Select Wipe data/factory reset --> Select Yes.
19) Select Wipe cache partition --> Select Yes.
20) Select Reboot system now.
21) Set up as new.
22) Tap on Settings --> System --> About phone
23) Tap seven times on Build number
24) Then, tap on Developer options.
25) Enable OEM unlocking & USB debugging.
TWRP :
A3_P-NEW-twrp_03.rar (ROOT STEPS AT FIRST POST)
The twrp is available on Needrom
I use umidigi A3. Will it work for me
answer
Toluene15 said:
I use umidigi A3. Will it work for me
Click to expand...
Click to collapse
Absolutely not.
This thread is reserved exclusively to the Umidigi A3 Pro
Can you help A3 users?
A3 Pro V1.2 LIGHT
Umidigi A3 Pro V1.2 LIGHT version
It is a debloated version of the original stock rom V1.2_20181221.
Added TWRP 3.2.3 and Simple Gallery.apk
In the original stock V1.2_20181221 the free space onto System is 155 MB
Instead, in the A3 Pro V1.2 LIGHT the free space onto System is 625 MB
Download the A3_Pro_V1.2-LITE.rar at the following link :
https://mega.nz/#!jsVTUCCQ!qg4WabDN5U2QKHaSDFWjYZNBrMFv2mSKoVQ6dszEMUA
Please follow very carefully all the next steps :
1) Flash the A3 Pro V1.2 LIGHT through SP Flash Tool.
I strongly recommend the "Firmware Upgrade" option (on SP Flash Tool).
2) Turn on your phone.
3) When the setup wizard will appear, turn off your phone.
4) Enter onto twrp recovery (volume up + power buttons simultaneously).
5) Select the first white line with volume up.
6) Press volume down to confirm.
7) Select language
8) "enter password" tap on cancel
9) Tap on WIPE
10) Tap on FORMAT DATA (type yes)
11) Return to the twrp main screen.
12) Tap on Reboot and choose System.
13) Complete all the requirements of the setup wizard.
14) Tap on Settings --> System --> About phone
15) Tap seven times on Build number
16) Then, tap on Developer options.
17) Enable OEM unlocking & USB debugging.
18) Tap on Magisk icon.
19) Upgrade to full Magisk Manager.
20) VITAL : Reboot the phone (it is needed for the fully functioning of Magisk).
21) Tap on the Play Store to update the apk.
In the Play Store, the first time that you update (apk), it takes a little time.
DO NOT update the A3 Pro V1.2 LIGHT to a newer version (no OTA)
Toluene15 said:
Can you help A3 users?
Click to expand...
Click to collapse
If somebody will take Lineage OS 16, it must be suitable for A3Pro and A3
Android pie custom rom
Great work in bringing twrp to our devices. It will be so much nicer if lineage 16 os or any other treble gsi custom rom running android 9 would work without ussd or sms issues on mtk devices like the a3 and a3 pro
answer
shifi_11 said:
Great work in bringing twrp to our devices. It will be so much nicer if lineage 16 os or any other treble gsi custom rom running android 9 would work without ussd or sms issues on mtk devices like the a3 and a3 pro
Click to expand...
Click to collapse
Also my A3 Pro V1.2 LIGHT version looks pretty sweet.
Regarding the Project Treble, I am already working on it.
But I cannot confirm anything at this point.
Please be patient (and fingers crossed).
Cleopatra Bianchi said:
Also my A3 Pro V1.2 LIGHT version looks pretty sweet.
Regarding the Project Treble, I am already working on it.
But I cannot confirm anything at this point.
Please be patient (and fingers crossed).
Click to expand...
Click to collapse
Thanks thats all i wanted to know. Waiting patiently.
Do I need to install each ROM in order, or can I just go straight to the light ROM?
answer
kd7eir said:
Do I need to install each ROM in order, or can I just go straight to the light ROM?
Click to expand...
Click to collapse
You can go straight to the light rom.
Follow very carefully all the steps at the 8th post.
Cleopatra Bianchi said:
You can go straight to the light rom.
Follow very carefully all the steps at the 8th post.
Click to expand...
Click to collapse
Thank you.
I went straight to the light ROM with no issues at all. Thank you for your work on this project.
Grande Cleopatra!
I've just bought the phone for my uncle, so I'll follow your thread with pleasure.
Thank you @Cleopatra Bianchi for working on this phone.
Very much appreciated.
Got the A3 Pro yesterday, connected WiFi, let it OTA update to V1.2_20181221.
Turned off, followed to OP directions to install TWRP and got it rooted with Magisk.
Works like a champ.
This is a really nice phone for the price ($99 on Amazon, minus some gift cards). We will see how it holds up in everyday use.
Bought Umidigi A3 Pro on Amazon for $95 free shipping.
Installing straight to the light rom then Magisk.
All work out, has no problems at all.
Thanks Cleopatra Bianchi...
Today 1/17/2019
***It is reduced price on Amazon $89.99 -%5 ( clip the coupon) = 85.50$ free shipping***
I think I bricked my A3 non Pro. I firmware upgraded the light rom with sp flash tool and it said ok.
Now screen stays black volume up + power doesn't work.

How to Flash Nokia 6 stock firmware 7.1.1

RESTORING NOKIA 6 (TA-1021) TO STOCK ANDROID.
ONLY FOR TA-1021
1. DOWNLOAD ALL THE FILES FROM GOOGLE DRIVE.
2. PUT THE DECEMBER 2017 OTA UPDATE ON YOUR SD CARD AND REBOOT THE PHONE TO RECOVERY MODE AND APPLY THE UPDATE VIA SD CARD
3. DON'T WORRY IT WILL SHOW ERROR AND ABORT THE INSTALLATION.
4. NOW REBOOT THE PHONE.
5. AND NOW REBOOT TO RECOVERY AGAIN.
6. IT WILL NOW SAY SOMETHING LIKE 7.1.1 ON TOP OF THE RECOVERY MODE SCREEN IN SMALL LETTERS.
7. THAT'S A GOOD THING BECAUSE BY INSTALLING THE DECEMBER OTA WE GET NOUGHT BOOTLOADER AND RECOVERY.
8. NOW EXTRACT THE FOLLOWING FILES :
1. OST_TOOL.ZIP
2. ONLINE UPDATE TOOL.ZIP
3. PLE-3320-0-00WW-A02_3 Nokia 6.ZIP
9. YOU CAN DOWNLOAD 7-ZIP TO EXTRACT THE FILES.
10. AFTER EXTRACTING OPEN UP OST_TOOLS AND INSTALL launcher.exe JUST CLICK AND NEXT,NEXT,NEXT TILL YOU SEE FINISH. BUT DO NOT OPEN THE SOFTWARE.
11. NOW GO INTO THE INSTALLATION FOLDER OF THAT SOFTWARE IT'S UNDER PROGRAM FILES X86/OST LA.
12. NOW OPEN THE EXTRACTED ONLINE UPDATE TOOL.ZIP EXTRACTED FOLDER AND COPY THAT ONE FILE TO THE OST LA FOLDER AND REPLACE THE FILE.
13. NOW DELETE ONLINE UPDATE TOOL.EXE.CONFIG FILE
14. NOW YOU CAN OPEN THE ONLINE UPDATE TOOL.EXE
15. CLICK NEXT AND LOAD THE FIRMWARE FROM PLE-3320-0-00WW-A02_3 Nokia 6, IT SHOULD BE AN NBO FILE.
16. REBOOT THE NOKIA 6 TO RECOVERY AND THE SELECT REBOOT TO BOOTLOADER.
17. THE NEXT BUTTON SHOULD APPEAR ON THE OST TOOL. CLICK NEXT THE SOFTWARE WILL WORK BUT THEN IT SHOULD SHOW THAT IT FAILED OF AN ERROR, AND THAT'S OKAY. IT SHOWS THE ERROR WHEN INSTALLING THE SOFTWARE FOR THE FIRST TIME.
18. NOW CLICK CONTINUE AND REBOOT THE PHONE INTO BOOTLOADER AND FLASH THE FIRMWARE AGAIN. IT WILL WORK !! AND THE PHONE AUTOMATICALLY REBOOTS.
LINKS
1. DECEMBER UPDATE
https://drive.google.com/open?id=18CxEOGUbf0XGcJ53ftpjI6GIozBVmPdt
2. OST TOOLS
https://drive.google.com/open?id=1OQHPfGEaQ2wFDpo3ABIo48AVbFTvl-SI
https://drive.google.com/open
id=1DLTM6F2xFGs1SWljZoPIIxIsn2X-osy9
3. NOKIA FIRMWARE 7.1.1
https://drive.google.com/open?
id=1ObwKEBvIF9ItrjAEanqMdANhoSOUIRum
******* I DO NOT OWN ANY SOFTWARE FROM NOKIA ******* ALL SOFTWARE ARE FROM XDA IT'SELF ****
******* I AM NOT RESPONSIBLE FOR DAMAGING YOUR PHONE **********
thank you for sharing
my device was successfully downgraded,
but from os 7 the update via ota jumps to os 9 instead of 8 first
Not funny.
ONLINE UPDATE TOOL.ZIP is password protected. Great, now I have a bricked device. What's the password?
EDIT1: It was 123 .... seriously???
EDIT2: After flashing it asks for password to load Android. System is encrypted. Wtf?
EDIT3: Did a wipe, works now. But it asks to download almost 2gb update and there is no way to cancel it. I hope it's not 9.
EDIT4: Yep, it's 9. Phone demanded to update to Android 9, only then it allowed to use it.
OnlineUpdateTool.zip PASSWORD IS 123
Can't bypass android 9 update
My phone was downgraded successfully but it doesn't start unless I update to android 9..... Plz help
Wantz Elshe said:
thank you for sharing
my device was successfully downgraded,
but from os 7 the update via ota jumps to os 9 instead of 8 first
Click to expand...
Click to collapse
can you tell me how to bypass android 9 update after factory reset im stuck plz help me
Hi there,
Sorry everyone I wasn't aware that this thread was active, if you still have problems I would like to help
Hi there,
Those who found it helpful no problem
And again my apologies I was not aware that there was a password for the onlineupdatetool
tomasxp said:
ONLINE UPDATE TOOL.ZIP is password protected. Great, now I have a bricked device. What's the password?
EDIT1: It was 123 .... seriously???
EDIT2: After flashing it asks for password to load Android. System is encrypted. Wtf?
EDIT3: Did a wipe, works now. But it asks to download almost 2gb update and there is no way to cancel it. I hope it's not 9.
EDIT4: Yep, it's 9. Phone demanded to update to Android 9, only then it allowed to use it.
Click to expand...
Click to collapse
Apologies for any inconvenience, when I bricked my phone non of the method online did not worked this is the only way I found working. And I did not came across any problems like you faced.
KIBS2173 said:
RESTORING NOKIA 6 (TA-1021) TO STOCK ANDROID.
ONLY FOR TA-1021
1. DOWNLOAD ALL THE FILES FROM GOOGLE DRIVE.
2. PUT THE DECEMBER 2017 OTA UPDATE ON YOUR SD CARD AND REBOOT THE PHONE TO RECOVERY MODE AND APPLY THE UPDATE VIA SD CARD
3. DON'T WORRY IT WILL SHOW ERROR AND ABORT THE INSTALLATION.
4. NOW REBOOT THE PHONE.
5. AND NOW REBOOT TO RECOVERY AGAIN.
6. IT WILL NOW SAY SOMETHING LIKE 7.1.1 ON TOP OF THE RECOVERY MODE SCREEN IN SMALL LETTERS.
7. THAT'S A GOOD THING BECAUSE BY INSTALLING THE DECEMBER OTA WE GET NOUGHT BOOTLOADER AND RECOVERY.
8. NOW EXTRACT THE FOLLOWING FILES :
1. OST_TOOL.ZIP
2. ONLINE UPDATE TOOL.ZIP
3. PLE-3320-0-00WW-A02_3 Nokia 6.ZIP
9. YOU CAN DOWNLOAD 7-ZIP TO EXTRACT THE FILES.
10. AFTER EXTRACTING OPEN UP OST_TOOLS AND INSTALL launcher.exe JUST CLICK AND NEXT,NEXT,NEXT TILL YOU SEE FINISH. BUT DO NOT OPEN THE SOFTWARE.
11. NOW GO INTO THE INSTALLATION FOLDER OF THAT SOFTWARE IT'S UNDER PROGRAM FILES X86/OST LA.
12. NOW OPEN THE EXTRACTED ONLINE UPDATE TOOL.ZIP EXTRACTED FOLDER AND COPY THAT ONE FILE TO THE OST LA FOLDER AND REPLACE THE FILE.
13. NOW DELETE ONLINE UPDATE TOOL.EXE.CONFIG FILE
14. NOW YOU CAN OPEN THE ONLINE UPDATE TOOL.EXE
15. CLICK NEXT AND LOAD THE FIRMWARE FROM PLE-3320-0-00WW-A02_3 Nokia 6, IT SHOULD BE AN NBO FILE.
16. REBOOT THE NOKIA 6 TO RECOVERY AND THE SELECT REBOOT TO BOOTLOADER.
17. THE NEXT BUTTON SHOULD APPEAR ON THE OST TOOL. CLICK NEXT THE SOFTWARE WILL WORK BUT THEN IT SHOULD SHOW THAT IT FAILED OF AN ERROR, AND THAT'S OKAY. IT SHOWS THE ERROR WHEN INSTALLING THE SOFTWARE FOR THE FIRST TIME.
18. NOW CLICK CONTINUE AND REBOOT THE PHONE INTO BOOTLOADER AND FLASH THE FIRMWARE AGAIN. IT WILL WORK !! AND THE PHONE AUTOMATICALLY REBOOTS.
LINKS
1. DECEMBER UPDATE
https://drive.google.com/open?id=18CxEOGUbf0XGcJ53ftpjI6GIozBVmPdt
2. OST TOOLS
https://drive.google.com/open?id=1OQHPfGEaQ2wFDpo3ABIo48AVbFTvl-SI
https://drive.google.com/open
id=1DLTM6F2xFGs1SWljZoPIIxIsn2X-osy9
3. NOKIA FIRMWARE 7.1.1
https://drive.google.com/open?
id=1ObwKEBvIF9ItrjAEanqMdANhoSOUIRum
******* I DO NOT OWN ANY SOFTWARE FROM NOKIA ******* ALL SOFTWARE ARE FROM XDA IT'SELF ****
******* I AM NOT RESPONSIBLE FOR DAMAGING YOUR PHONE **********
Click to expand...
Click to collapse
thanks for your sharing
i wanna test your way , but someones said that we force to upgrade to android pie after that !
is that true ?!
Try this
#MmdRza said:
thanks for your sharing
i wanna test your way , but someones said that we force to upgrade to android pie after that !
is that true ?!
Click to expand...
Click to collapse
Hi there,
Well if you turn off your wifi and mobile data at the beginning of the setup you will not be forced to download the latest version of android.
Regards
KIBS2173
After the flash, if you are prompted for a code, do a full delete.
Do not use network during setup, there will be no update.
Perfect description!
Thank you very much!
before u downgrade u have to remove all the Google accounts. otherwise when u got finished downgrading u will force to update to android 9 unless u haven't unlock the boot loader..
if bootloader unlocked u can bypass setup wizard using twrp file manager.
Downgrading deletes all data, including accounts.
Simply set up your phone without a sim card and don't connect to wifi. There will be no update.
Thank you
I made an account specifically to thank you. This works very well.
Just a note:
Remove your google account from your device before flashing. Otherwise, it won't let you skip the setup when you boot the phone after the flash.
This is due to a security feature in Android called Factory Reset Protection (FRP). Which essentially makes sure that the owner of the device (or basically the last account that was on it) is the same one logging in after the reset. That's why it doesn't let you skip the setup, thus forcing you to upgrade to Android 9.
If you didn't remove your google account before flashing, you'll have to:
1- Do the Pie update during the setup
2- Sign in with the same google account you had logged in before flashing
3- Remove that account
4- Do the whole flashing process from the start again
You can save yourself from this hassle just by removing the account BEFORE you flash to begin with.
Needless to say, you should disable WiFi and remove your SIM card to bypass the update on boot.
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
Also if I may, I have a small question. After downgrading to stock 7.1.1, can I re-flash the December OTA update to get a more recent version?
I want to do this because there's an issue with USB connection and I am hoping that the December OTA fixes it.
UPDATE: I was able to get the OTA zip files from teamandroid (I can't post the link because my account is new , sorry)
I was on 7.1.1 June 2017, so I flashed July, August, September, and October in order.
This gave me Android 7.1.2, October 2017 security patch, and fixed the USB issue.
MohRez said:
thanks for your sharing
i wanna test your way , but someones said that we force to upgrade to android pie after that !
is that true ?![yes ]
Click to expand...
Click to collapse
maniacalthief said:
MohRez said:
thanks for your sharing
i wanna test your way , but someones said that we force to upgrade to android pie after that !
is that true ?![yes ]
Click to expand...
Click to collapse
Check my reply, it explains what you should do to avoid having to upgrade.
Click to expand...
Click to collapse
Try This
Satharus said:
maniacalthief said:
Check my reply, it explains what you should do to avoid having to upgrade.
Click to expand...
Click to collapse
Hi everyone,
To prevent your phone from updating, after flashing and resetting, just skip the wifi connection, or eject your sim therefore no update will be found.
Kind Regards
KIBS2173
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
can someone help me i get this error on my Windows 10, do I need to install something?
NETWORK problem
Has anyone faced network problem , like VOLTE not appearing? If any fix is available please write it here !

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note 10/+/5G Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note 10/+/5G​Only for exynos variants - N970F / N975F / N976B (Europe - Global, Single/Dual-SIM), N971N, N976N (South Korea)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
latest kernel source release
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
spoofed config for firmware checks
Recovery Features:
built in full 64 mode
toybox/busybox support
compatible with Android 10.0 and above
Downloads:
Note 10 - d1 - N970F
Note 10 5G - d1x - N971N
Note 10+ - d2s - N975F
Note 10+ 5G - d2x - N976B/N976N
avb disabled vbmeta
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download avb disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download avb disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13d60000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - d1 / d1x / d2s / d2x
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9820/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
Compatibility and changelog:
07.03.2022 - TWRP 3.6.1
Security patch: 2022-02-01
Compatibility: only GVA*/GVB* firmwares, OneUI 4.0
Spoiler: Archive
09.01.2022 - android 12 support
Security patch: 2022-01-01
Compatibility: only GUL* firmwares, OneUI 4.0
08.01.2021 - android 11 support
Security patch: 2020-12-01
Compatibility: only ETL* firmwares, OneUI 3.0
27.12.2020 - TWRP 3.5.0 bringup - december release
Security patch: 2020-12-01
Compatibility: only DTK* and DTL* firmwares
09.12.2020 - december release
Security patch: 2020-12-01
Compatibility: only DTK* and DTL* firmwares
05.12.2020 - Initial release
Security patch: 2020-11-01
Compatibility: DTJ* firmwares
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Patch TWRP with Magisk
Use recovery to boot up rooted
Background on Android Verified Boot
Rollback protection
FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version and only if you don't plan to boot rooted with TWRP (some kernels deliver root prebuilt in kernel), or Rollback protection will kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
official builds will be up in few hours
Well done Corsi, thanks for your constant passionate work!
Do I need to patch recovery in magisk manager for root?
Can I install an Android 11 based GSI after successful installation? Or is this not recommended?
Guys im new to this gn10+ rom, i havent used a custom rom for a while (while warranty was available in my country lol)
got a few questions,
1.- If i use this rom, will i be loosing access to bank apps?
2.- how good is the performance from stock to custom rom?
thanks in advance, and sorry for the newbie questions, i havent flashed any rom in the last couple of years (i used to flash sony's roms in my xperias )
asafegous said:
Do I need to patch recovery in magisk manager for root?
Click to expand...
Click to collapse
If you want to boot with the stock kernel, yes. If you want to use a custom kernel then don't patch it
AlfredS said:
Guys im new to this gn10+ rom, i havent used a custom rom for a while (while warranty was available in my country lol)
got a few questions,
1.- If i use this rom, will i be loosing access to bank apps?
2.- how good is the performance from stock to custom rom?
thanks in advance, and sorry for the newbie questions, i havent flashed any rom in the last couple of years (i used to flash sony's roms in my xperias )
Click to expand...
Click to collapse
This isn't a ROM, this is a custom recovery / TWRP
And yes, It is possible that you lose access to banking apps with root
Wow. I am happy with this, easy to install and working like a charm
Hmm... no news about TWRP 3.5.0??
No news about android 11 support??
galaxy mini said:
Hmm... no news about TWRP 3.5.0??
No news about android 11 support??
Click to expand...
Click to collapse
The kernel source of Android 11 has not been released ...
Android 11 TWRP is up already for a while, in case you didn't notice it yet grab it from twrp.me.
Don't forget to use targeted TWRP for your android version and release, read more about compatibility in second post of this thread.
Regards!
corsicanu said:
Android 11 TWRP is up already for a while, in case you didn't notice it yet grab it from twrp.me.
Don't forget to use targeted TWRP for your android version and release, read more about compatibility in second post of this thread.
Regards!
Click to expand...
Click to collapse
Hi , Can I flash this after having patched magisk firmware installed without losing data ?
Hi everyone, after flashing the twrp twrp-3.5.0_9-2-d2s.img.tar, I entered Twrp and it works very well, I rebooted and then tried in various ways to re-enter Twrp, both from off with vol Up key + power key and both restarting by holding down the vol Up keys + power key but I can't get back into Twrp. Only by going first into download mode and then from there by pressing vol down + power button immediately changing to vol Up can I enter Twrp, what should I do to go directly to Twrp? Thank you all.
siriow said:
Hi everyone, after flashing the twrp twrp-3.5.0_9-2-d2s.img.tar, I entered Twrp and it works very well, I rebooted and then tried in various ways to re-enter Twrp, both from off with vol Up key + power key and both restarting by holding down the vol Up keys + power key but I can't get back into Twrp. Only by going first into download mode and then from there by pressing vol down + power button immediately changing to vol Up can I enter Twrp, what should I do to go directly to Twrp? Thank you all.
Click to expand...
Click to collapse
Is your device on Android 11? Samsung has changed access to recovery on this device. To enter TWRP use this app:
Recovery Reboot - Apps on Google Play
This is a very small app for "rooted" phones to reboot into a custom recovery.
play.google.com
I also think I haven't read where, that having a type c headset connected, and you want to get into recovery with those combinations should work (I haven't tried it, I use that app).
@siriow Did you do well what I told you? It's just that there's no answer, not a simple thank you for your part.
Hi
Im trying to flash this recovery. Got the files, flashed and started pressing the Power+VOL+, but it reboots to Download Mode saying DT Load Fail, not found rev 0x18? Any idea?
Im still on A10
EDIT: So Nobodys Rom 3.5.0_9-2 with vbmeta mod works, -3 doesnt...
@corsicanu I wanted to restore my DTB and DTBO files so I installed https://github.com/corsicanu/9825-bootloaders_and_modems/releases FUBD-twrp-flashable.zip and since then I got bootloop. Im using DrKetan ROM, I tried reinstalling it dirty with AP BL CP and formated /system before. But it bootloops on bootsplash... What I did ROM? Is clean flashing the only way to recover?
Edit:
Nevermind I got it booting again with another kernel. I hope I don't messed up something in the system.

How To Guide Root for all Exynos 850 devices.

Root for all Exynos 850 devices.
A. Root part 1 - Preparing the file
I accept no responsibility for bricked phones but I will help you to recover.
1. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Samsung Firmware Download - Lastest official firmware update​Samsung Firmware Download Official and fast update Lastest and old version Max speed and free download Best Samsung Galaxy website
samfw.com
2. Download patched magisk
3. Use zarchiver to extract the apxxxxxx....md5 section from the firmware.
4. Use patched magisk to patch the ap section. Allow the extra files.
Click on install and select patch file.
The output will be a patched tar file.
B. To Unlock Bootloader
1. Activate developer options by going to settings, about phone, software information and tapping on build number 7 times.
On phone developer options in settings allow OEM unlocking and enable usb debugging by moving both
sliders RIGHT
If you don't see the OEM unlock
-Disable Auto System Update
-Then disable Automatic date and time (Found in General Management) > then set the time back 14 days
- Connect to the internet
-Go to software update then check for update and wait a long time till it registers the device on server
-Once it's registered the OEM Unlock should be visible in the Developer Options
then connect phone to PC
2. Reboot into download mode by holding down both Vol up and Vol down
(You might need to long press vol up to unlock bootloader)
then press vol up to continue
Reboot and skip through the setup process.
C. Root part 2
Reboot into download mode again
6. Flash the patched ap tar file using special Odin.
https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/
(Click on the ap button and choose the patched tar file. Press start)
7. Reboot.
8. Skip all the way through the set-up process.
I successfully rooted my SM-A127F U3 with this manual. There are two problems.
USB tethering to Debian 10 and Ubuntu 20.04 is broken after rooting.
Second problem is that I can't update my service provider.
First time rooting I replaced only the AP. Later I tried replacing everything. Once with CSC and once with HOME_CSC nothing works. When I patch with the original AP there is no CID manager problem. Tethering I didn't try
Usbtt said:
I successfully rooted my SM-127F U3 with this manual. There are two problems.
USB tethering to Debian 10 and Ubuntu 20.04 is broken after rooting.
Second problem is that I can't update my service provider.
First time rooting I replaced only AP. Later I tried replacing everything. Once with CSC and once with HOME_CSC nothing works. When I patch with the original AP there is no CID manager problem. Tethering I didn't try
Click to expand...
Click to collapse
Interesting.
Exynos 850 Resources
A127 M127 F127 A135 M135 A217 A047
t.me
Rooting with magisk is better option
@Malware said:
Rooting with magisk is better option
Click to expand...
Click to collapse
Yes.
A patched magisk is needed for this device.
2. Download patched magisk
3. Use zarchiver to extract the apxxxxxx....md5 section from the firmware.
4. Use patched magisk to patch the ap section. Allow the extra files.
Click on install and select patch file.
The output will be a patched tar file.
This method will give a patched vbmeta so twrp will then work properly.
physwizz said:
Yes.
A patched magisk is needed for this device.
2. Download patched magisk
3. Use zarchiver to extract the apxxxxxx....md5 section from the firmware.
4. Use patched magisk to patch the ap section. Allow the extra files.
Click on install and select patch file.
The output will be a patched tar file.
This method will give a patched vbmeta so twrp will then work properly.
Click to expand...
Click to collapse
Bruh, no. I mean yes one can root that way but a developer of magisk suggest not to use this way instead patch boot.img for your device using magisk and then flash it.
@Malware said:
Bruh, no. I mean yes one can root that way but a developer of magisk suggest not to use this way instead patch boot.img for your device using magisk and then flash it.
Click to expand...
Click to collapse
That will work but it doesn't give you a patched vbmeta.
So custom recovery gives an error
physwizz said:
That will work but it doesn't give you a patched vbmeta.
So custom recovery gives an error
Click to expand...
Click to collapse
Ig no.......
is there any android 12 patched magisk
please send without telegram link
TheWorldYT said:
is there any android 12 patched magisk
please send without telegram link
Click to expand...
Click to collapse
Yes
how to update magisk?
pando345 said:
how to update magisk?
Click to expand...
Click to collapse
Install the apk
physwizz said:
Root for all Exynos 850 devices.
A. Root part 1 - Preparing the file
I accept no responsibility for bricked phones but I will help you to recover.
1. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
Samsung Firmware Download - Lastest official firmware update​Samsung Firmware Download Official and fast update Lastest and old version Max speed and free download Best Samsung Galaxy website
samfw.com
2. Download patched magisk
3. Use zarchiver to extract the apxxxxxx....md5 section from the firmware.
4. Use patched magisk to patch the ap section. Allow the extra files.
Click on install and select patch file.
The output will be a patched tar file.
B. To Unlock Bootloader
1. Activate developer options by going to settings, about phone, software information and tapping on build number 7 times.
On phone developer options in settings allow OEM unlocking and enable usb debugging by moving both
sliders RIGHT
If you don't see the OEM unlock
-Disable Auto System Update
-Then disable Automatic date and time (Found in General Management) > then set the time back 14 days
- Connect to the internet
-Go to software update then check for update and wait a long time till it registers the device on server
-Once it's registered the OEM Unlock should be visible in the Developer Options
then connect phone to PC
2. Reboot into download mode by holding down both Vol up and Vol down
(You might need to long press vol up to unlock bootloader)
then press vol up to continue
Reboot and skip through the setup process.
C. Root part 2
Reboot into download mode again
6. Flash the patched ap tar file using special Odin.
https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/
(Click on the ap button and choose the patched tar file. Press start)
7. Reboot.
8. Skip all the way through the set-up process.
Click to expand...
Click to collapse
Will this a21s file work for m12 also?
Star_xda said:
Will this a21s file work for m12 also?
Click to expand...
Click to collapse
Use delta magisk
physwizz said:
Use delta magisk
Click to expand...
Click to collapse
Can I do this without losing Data?
Star_xda said:
Can I do this without losing Data?
Click to expand...
Click to collapse
Yes
physwizz said:
Yes
Click to expand...
Click to collapse
Just tried but no luck. I flashed by bootloader but it was stuck at sending boot.img
Star_xda said:
Just tried but no luck. I flashed by bootloader but it was stuck at sending boot.img
Click to expand...
Click to collapse
Follow instructions exactly
physwizz said:
Yes
Click to expand...
Click to collapse
I am having issue rooting my samsung m12. The magisk is unable to patch the AP. Screenshot for reference. Please help me fix the issue.
mdbshuvo said:
I am having issue rooting my samsung m12. The magisk is unable to patch the AP. Screenshot for reference. Please help me fix the issue.
View attachment 5874391
View attachment 5874393
Click to expand...
Click to collapse
you must use delta magisk

(GUIDE:) How to ROOT the TAB S6 - SM-T860 (Wi-Fi Model) - (12/10/21):

Hello all,
BORING INTRO STUFF (Safely Ignore This):
I couldn't find any guide that was current enough to make me feel confident in going through with rooting this tablet. So because of that, I decided I would make on my own guide for those that needed this. I tried multiple guides here and all of them resulted in a boot-loop.
VERY SMALL PSA: I'm apologizing in advance if this guide is both pointless and longer than it needs to be. I figured it would be useful as a future reference in-case anyone needed this.
THINGS YOU WILL NEED:
* TAB S6 - SM-T860 (Wi-Fi)
* This can be done on Android 9,10 & 11 (Process is the same)
* Your specific firmware downloaded (*DO NOT SKIP THIS*)
* Tablet is charged to at least 50%
* Maximum of 20 minutes to both read & follow the process
* FIRMWARE: The link below is the firmware I used. I would still advise you to both look for your specific version and to use the link provided below only if your tablet is exactly as followed:
* (T860XXU4CUI4) - BUILD NUMBER
* (ANDROID 11) - ANDROID VERSION
* (XAR - CELLUAR SOUTH) - SERVICE PROVIDER SOFTWARE VERSION
( https://samfirms.com/SM-T860/KOR/T860XXU4CUI4 )
* SAMSUNG USB DRIVERS: ( https://developer.samsung.com/android-usb-driver )
* ODIN: ( https://samfirms.com/download-odin ) Latest is 3.14.4. Use that one or the newest one
* TWRP (OPTIONAL): T860 (Wi-Fi) ONLY. DOWNLOAD VERSION "twrp-3.6.0_9-0-gts6lwifi.img.tar" OR THE LATEST ONE AVAIABLE.
( https://dl.twrp.me/gts6lwifi/ )
* MAGISK APP: ( https://magiskmanager.com/downloading-magisk-manager )
* LZ4 TOOL: ( https://github.com/lz4/lz4/releases )
* 7-ZIP: ( https://www.7-zip.org/download.html )
HOW TO ROOT:
1. UNLOCKING THE BOOTLOADER: *** THIS WILL WIPE YOUR DATA *** (GO TO SETTINGS > ABOUT TABLET > SOFTWARE INFORMATION & TAP BUILD NUMBER 7 TIMES. GO TO DEVELOPER OPTIONS > TOGGLE ON OEM UNLOCKING) TURN OFF THE TABLET. AT YOUR PC, HAVE A CABLE CONNECTED TO THE PC. WHILE HOLDING BOTH VOLUME DOWN + VOLUME UP, PLUG IN THE CABLE. WHEN THE SCREEN TURNS ON, PRESS AND HOLD VOLUME UP.
WHEN THE SCREEN CHANGES PROMOTING YOU TO UNLOCK THE BOOTLOADER, PRESS VOLUME UP. ONCE BOOTED UP, GO THROUGH THE SETUP AGAIN AND MAKE SURE Wi-Fi IS CONNECTED. GO BACK TO SETTINGS, ENABLE DEVELOPER OPTIONS AGAIN AND THEN ENABLE USB - DEBUGGING.
2. EXTRACT THE BOOT.IMG.LZ4 FILE AND MOVE IT TO YOUR TABLET: After 7-Zip is installed, the LZ4 Tool and the firmware you downloaded is extracted somewhere, open the extracted firmware folder. Right-click on the AP file and select 7-zip then open archive. Look for boot.img.lz4, drag it inside of the LZ4 Tool. Once done, drag the boot.img.lz4 on top of the LZ4 executable. It will be extracted as boot.img. Right-click the boot.img file and select 7-zip then add to archive. Change "Archive format" to tar and rename it to boot.tar. Finally, move it to your tablet's storage.
3. DOWNLOAD THE MAGISK APK: Install the Magisk apk that you downloaded and open it up. Within the app, select install, uncheck recovery mode and press next then check "Select and Patch a file". Locate your boot.tar file that you moved into your storage from earlier and wait for Magisk to process it.
4. USING ODIN: Go ahead and locate the new file, it starts with Magisk (NOT THE BOOT.TAR FROM EARLIER SHOULD START WITH MAGISK). Once done, move the Magisk tar file to your computer and turn off the tablet. With the tablet off and Odin open (Run as administrator) , press and hold both VOLUME DOWN & VOLUME UP then plug the cable from your pc into your tablet. With Odin open, go into the "options" tab, uncheck "Auto Reboot" and Select "AP". Locate the Magisk tar file you moved from your tablet and then press "Start".
ONCE IT SAYS "PASS" THEN STOP AND READ THIS BEFORE CONTINUING. *IMPORTANT*
PRESS AND HOLD BOTH POWER AND VOLUME DOWN FOR 7 SECONDS. THE SCREEN WILL TURN BLACK. VERY QUICKLY WHILE STILL HOLDING POWER, PRESS AND HOLD VOLUME UP INSTEAD. PRESS POWER TO THE BOOTLOADER UNLOCK PROMPT AND YOU SHOULD BE IN RECOVERY. THIS SHOULD BOOT YOU INTO STOCK RECOVERY. USE THE VOLUME KEYS TO NAVIGATE, SELECT "Wipe data/factory reset" then press the power button and select "Factory data reset". Finally, select "Reboot system now" and Wait for the tablet to reboot into the OS.
5. FINISHING UP: After the tablet has restarted back into android and you took a couple of minutes to go through the setup one last time. Scroll up into the app drawer and make sure that you see the app "Magisk", go ahead and select it and press ok to download Magisk. Afterwards, open it up and Magisk will ask you to reboot to finish setting up root. Press ok. Once restarted you are done with the rooting process.
Lastly, as an optional step you can install TWRP.
6. TWRP INSTALLATION (OPTIONAL): With the tablet off and Odin running on your pc, go ahead and press VOLUME DOWN AND VOLUME UP at the same time then plug in the data cable from your PC. Press VOLUME UP to go into download mode. Once in download mode, select "AP" then select the TWRP tar file you downloaded and make sure to uncheck "Auto reboot" from the options tab in Odin. Click start and after it says "PASS" unplug the data cable. On the tablet, press VOLUME DOWN AND POWER to reboot and when you see THE SCREEN TURN BLACK, QUICKLY PRESS AND HOLD BOTH POWER AND VOLUME UP. You should be in TWRP and you are now officially done.
* From now on, I would recommend you use the Magisk app or some reboot app to boot into recovery as it is difficult to use the button combinations to access recovery.
* IF YOU'RE NOT USING MAGISK TO REBOOT TO RECOVERY, I WOULD USE THIS APP INSTEAD: https://play.google.com/store/apps/details?id=com.eypcnnapps.quickreboot&hl=en_US&gl=US
Credits: If all went well then I appreciate you taking the time to read through this guide carefully. Hope it was as clear as possible and that you found it helpful. I will be editing this post from time to time to make it cleaner.
Again, Thank you and if you have any questions, I will answer them when I see them.
THANK YOU SO MUSH IVE BEEN STRUGGLING SO HARD TO GET ROOT ON THIS TABLET FINALLY THANK YOUUUUUU
by the way guys, when it says to reboot to make magisk work.
you are risking a bootloop.
Oh by the way, aside from TWRP being wonky thank you for the guide I had been playing with the idea of rooting this thing for over a year now. You made it easy.
I go through all the steps and it works fine. Once I try for TWRP I end up with
"partition recovery
Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM recovery
VBMETA T860XXU4DVG6, 54204454R"
From that point it just loops back to that message and downloading mode until I wipe it all and start over again. I TWRP a no go for the S6 now? I guess I can dig around on their site as well. Any input anyone wants to throw my way will also be appreciated.
Hi Sadistic - ,
I need to start with a complement. This is a really clear guide.
But, When I get done with step 3, the Magisk patched boot file has a .img extension
On step 4, Odin is expecting a .tar file extension so the file doesnt show up.
Did I miss something?
Thanks
mvanwey said:
Hi Sadistic - ,
I need to start with a complement. This is a really clear guide.
But, When I get done with step 3, the Magisk patched boot file has a .img extension
On step 4, Odin is expecting a .tar file extension so the file doesnt show up.
Did I miss something?
Thanks
Click to expand...
Click to collapse
Yep..... try step 2
seppukuudere said:
Yep..... try step 2
Click to expand...
Click to collapse
Yes, step 2 is moving the extracted boot file (re-named to .tar) to my tablet and then patching it with magisk.
The patched file from Magisk has an .img extension.
mvanwey said:
Yes, step 2 is moving the extracted boot file (re-named to .tar) to my tablet and then patching it with magisk.
The patched file from Magisk has an .img extension.
Click to expand...
Click to collapse
Ah I see, I would try to do step 3 again, take screenshots of the end result from magisk o:
Let's just cancell this. it was over 20 days since I asked for help & now I'm getting asked for screenshots.
I have moved on.
I probably should have put that in my reply.
mvanwey said:
Let's just cancell this. it was over 20 days since I asked for help & now I'm getting asked for screenshots.
I have moved on.
I probably should have put that in my reply.
Click to expand...
Click to collapse
oops yikes, yeah probably should have. happy new year!
seems like after rooting mine the storage has been cut by a big margin, from 128 to 32gb. any way of fixing this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi. Is there any update guide for last android 12 version, to install twrp? Can se still use this, as it is for android 11?
Thanks,

Categories

Resources