[RECOVERY][UNOFFICIAL] TWRP for Galaxy Note 10 (Exynos) - Samsung Galaxy Note 10+ ROMs, Kernels, Recoveries,

[RECOVERY][UNOFFICIAL] TWRP for Galaxy Note 10 (Exynos) - Samsung Galaxy Note 10+ ROMs, Kernels, Recoveries,

Team Win Recovery Project 3.3.1
{
"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"
}
Exynos ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
Download: Note 10(Exynos variants - N970/971/975/976/N/F/B)
Download
Sources:
TWRP Tree and kernel source
Changelog:
15.12.2019
- Updated TWRP for Android 10.0
- From now on no more Magisk Prepatched images (if you need it patch it byself or flash my kernel where patched recovery is not needed)
22.09.2019
-Reverted MTP Changes from last build since for some mtp dont worked in system
21.09.2019
- Fixed the bug that mtp dont worked any more on TWRP when usb cable got disconnected and reconnected
- Modded Kernel for have MTP in TWRP, Samsung Roms and GSI roms (for GSI Roms flash GSI_MTP_ENABLER.zip)
- Reverted FFS MTP changes since new way is more stable
14.09.2019
- Fixed MTP using FFS_MTP in recovery (Thx to @bigbiff for add FFS MTP support on TWRP 3.3.0. FFS_MTP dont corrupts large files like the mtp used by samsung in the roms)
- Removed File Based backups because the phone refuses to boot from filebased backups since they breaks the rootfs
27.08.2019
-Initial Release
Bugs:
-No one
Telegram Group
https://t.me/twrp_n10
XDA:DevDB Information
[RECOVERY] TWRP for Galaxy Note 10 (Exynos), Kernel for the Samsung Galaxy Note 10+
Contributors
geiti94
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2019-08-27
Created 2019-08-27
Last Updated 2019-12-15

Guide:
Go to Developer settings and enable oem unlock
power off the device and boot in download mode with power + vol down buttons and plug in the usb (make sure usb cable is connected to the pc)
in download mode you see the long press vol up option for unlock bl
unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
after bootloader unlock boot up the phone and make sure it is connected to the internet or he triggers rmm prenormal
setup the phone without google account etc
reboot in download mode and flash twrp tar for your device with odin in the AP field (if you want to patch twrp byself patch the downloaded tar in magisk manager. patched tar is in downloads folder after patch)
hold vol up + power button while odin is flashing until you are in twrp.
format data in twrp
flash the disabler that is on TWRP download link
flash my kernel avaiable here
press reboot to system in twrp.

so all builds are uploaded unpatched. for magisk you can patch it byself with magisk manager

Beware of multidisabler 1.3 at this moment, it has some bug

oggi21 said:
Beware of multidisabler 1.3 at this moment, it has some bug
Click to expand...
Click to collapse
then ian needs to fix it. i saw only he added note 10 support.

geiti94 said:
so all builds are uploaded unpatched. for magisk you can patch it byself with magisk manager
Click to expand...
Click to collapse
so you do the patch with magisk and ap rom flash via odin route still?
its old school jsut just fllash twrp via odin

Deezy88 said:
so you do the patch with magisk and ap rom flash via odin route still?
its old school jsut just fllash twrp via odin
Click to expand...
Click to collapse
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone

geiti94 said:
then ian needs to fix it. i saw only he added note 10 support.
Click to expand...
Click to collapse
Yeah, he said he gonna fix it today

so i added in download folder byself a n10 disabler because i saw that ians one will never ever work because my twrp use busybox and not toolbox (i like it easyers for dev thats why busybox is added)
that zip disables encrpytion, fix secure storage, removed 2 libs for not let the phone fall under prenormal state etc

geiti94 said:
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone
Click to expand...
Click to collapse
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
geiti94 said:
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone
Click to expand...
Click to collapse
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow?

Deezy88 said:
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow?
Click to expand...
Click to collapse
yes you can

so since i am not all the time here on xda here is a telegram group link. use it for report bugs etc since i dont read all the time the complete thread here https://t.me/twrp_n10

thank you that was fast!

so multidisabler is updated to v2 and stock rom boots again normaly sammy added 2 more encryption in the n10 that needed to get disabled
Magisk Patched builds are now uploaded too for the one that dont wants to patch byself

geiti94 said:
so multidisabler is updated to v2 and stock rom boots again normaly sammy added 2 more encryption in the n10 that needed to get disabled
Magisk Patched builds are now uploaded too for the one that dont wants to patch byself
Click to expand...
Click to collapse
V2 worked like a charm! :good:

geiti94 said:
so multidisabler is updated to v2 and stock rom boots again normaly sammy added 2 more encryption in the n10 that needed to get disabled
Magisk Patched builds are now uploaded too for the one that dont wants to patch byself
Click to expand...
Click to collapse
Great job geiti. Just waiting for rom release.:good::good:

geiti94 said:
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone
Click to expand...
Click to collapse
So, clear me if I have something miss-understand:
1. If flash rom cook: unlock OEM, flash twrp and then flash rom cook
2. If using stock root: unlock OEM, flash twrp and then patch AP with magisk and flash as Dr Ketan guide to flash Magisk?

namfat said:
So, clear me if I have something miss-understand:
1. If flash rom cook: unlock OEM, flash twrp and then flash rom cook
2. If using stock root: unlock OEM, flash twrp and then patch AP with magisk and flash as Dr Ketan guide to flash Magisk?
Click to expand...
Click to collapse
I think you're wrong for the number 2. If you wanted stock root with twrp. AFAIK you need to. Patch the AP from stock rom. Patch the twrp recovery.img . Then replace the stock patched recovery from AP patched with the patched twrp. Then you can follow dr.ketan's guide but use this new patched AP with the patched twrp inside

great now i have to spend 1000 bux to get this.

white7561 said:
I think you're wrong for the number 2. If you wanted stock root with twrp. AFAIK you need to. Patch the AP from stock rom. Patch the twrp recovery.img . Then replace the stock patched recovery from AP patched with the patched twrp. Then you can follow dr.ketan's guide but use this new patched AP with the patched twrp inside
Click to expand...
Click to collapse
Many thanks, got it.[emoji8][emoji8]
Sent from my SM-N975F using Tapatalk

Related

[TWRP 3.2.1-1] [ROOT] A8 sm-a530f - 02/02/2018

Unofficial release -TWRP recovery for the Galaxy A8 - SM-A530F, EXYNOS 7885
{
"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"
}
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot
Update 02/02/2017
TWRP 3.2.1-1 NN build released.
Current status: Beta
Features:
MTP >> not working
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
TWRP_3.2.1-1_sm-a530f_020218
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU

Nice work ? will test it on my a8 as soon as possible

help frp off oem lock no findin oem unlock in developer option

nimanwar said:
help frp off oem lock no findin oem unlock in developer option
Click to expand...
Click to collapse
RMM STATE : Prenormal?

ashyx said:
Unofficial release -TWRP recovery for the Galaxy A8 - SM-A530F, EXYNOS 7885
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot
Update 02/02/2017
TWRP 3.2.1-1 NN build released.
Current status: Beta
Features:
MTP >> not working
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
TWRP_3.2.1-1_sm-a530f_020218
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse

only official release binaries are allowed to be flashed
HELP: Mine SM-A530F failed to be flashed: "only official release binaries are allowed to be flashed".

nimanwar said:
.
Click to expand...
Click to collapse
Please do NOT quote the entire OP.
Remove the quote please.

cuantonhonhoi said:
HELP: Mine SM-A530F failed to be flashed: "only official release binaries are allowed to be flashed".
Click to expand...
Click to collapse
As above regarding RMM STATE?

can i root without wiping my data ??

Hi, I have the same problem, I cannot flash because of : "only official release binaries are allowed to be flashed"
RMM STATE : Prenormal
FRP LOCK : OFF
OEM LOCK : OFF
Also I don't know how to find a proper rom stock recovery because rom from updato fail in odin.
What can i do ?

On my "only official release binaries are allowed to be flashed" too..

Weird you have those issues, worked like a charm for me, thanks again ashyx

At me too it does not work

Serp87 said:
At me too it does not work
Click to expand...
Click to collapse
Define 'IT DOES NOT WORK'

As soon as i installed twrp and then rebooted device it's stuck on boot loop. Maybe the twrp version is not compatible or i did something wrong?

DziugsBugs said:
As soon as i installed twrp and then rebooted device it's stuck on boot loop. Maybe the twrp version is not compatible or i did something wrong?
Click to expand...
Click to collapse
Please read the thread this has been explained as far as I know.
Look for RMM STATE: Prenormal

Hey @ashyx , My teammate is using an A530F, we just want to let you know MTP/adbsideload/adb shell isn't working. (its not aswell in my a530f twrp with disabling MTP in makefile with fevax commit because there isnt that samsung_mtp flag we are used to) Hope you can take a look in to it if you have time. Thanks in advance.

ananjaser1211 said:
Hey @ashyx , My teammate is using an A530F, we just want to let you know MTP/adbsideload/adb shell isn't working. (its not aswell in my a530f twrp with disabling MTP in makefile with fevax commit because there isnt that samsung_mtp flag we are used to) Hope you can take a look in to it if you have time. Thanks in advance.
Click to expand...
Click to collapse
Yes I'm aware of it. Samsung seem to be forcing their own MTP driver.
Also as I mentioned to someone in the A730f thread. Due to lack of responses I wasn't prepared to even tackle the issue until people could be bothered to post in the thread.
For ADB to work firstly try disabling MTP in TWRP.

what do I need to do to work properly twrp?

[Guide] [NO ENCRYPTION] TWRP with Magisk on a Pie GSI (RR)

THIS REQUIRES YOUR DEVICE TO BE COMPLETELY RESTORED, PLEASE BACK UP DATA BEFORE DOING THIS.
Code:
/*
* Your warranty is now void.
*
* 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 ROM
* 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.
*/
THIS HAS ONLY BEEN TESTED ON RESURRECTION REMIX YOU CAN TEST OTHER GSI'S WITH THIS (TELL ME YOUR RESULTS BELOW)
NO CUSTOM KERNELS CAN BE APPLIED RIGHT NOW
THIS DEVICE HAS A "AB" BOOT SET SO PLEASE GET "AB" GSI'S
{
"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"
}
Grab these two files (Big Thanks to @mac12m99, @33bca (Offain on AFH) XDA Profile
Fixed SDCard Support TWRP Image File (Download this and put this on your SDCard and Computer)-
Fixed TWRP XDA Post
Fixed SDCard Support TWRP Installer Zip (Download and put this on your SDCard)-
Fixed TWRP .zip Installer
But I got TWRP on with magisk.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA, SD CARDS, ETC ONCE AGAIN
Start with the phone being on with USB Debugging enabled with platform tools etc. correctly and bootloader unlocked
Type:
Code:
adb reboot bootloader
1. So flash the 10.0.4.0 ROM to get a fresh start (this is highly recommended) folder through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
1a. After it is done flashing it restarts, hurry and hold power + volume down to boot back into the bootloader
2. Boot up that TWRP.img file you downloaded above in this color
Type:
Code:
fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP
2a. Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip in this color above where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
2b. Hit the home button back to TWRP home screen and tap reboot >>> bootloader
3. Download this to your computer -
aboot.img
3a. Type:
Code:
fastboot flash aboot aboot_9.6.4.img
Then type:
Code:
fastboot reboot
4. Afterwards you shall go back to bootloader quickly
Type:
Code:
fastboot erase system
Type:
Code:
fastboot erase userdata
5.Open the 10.0.4.0 folder you flashed above in #1 with MiFlash and have the "userdata.img" handy from that folder.
Download (download the one with latest date and that says "arm64" and "ab") or use the Resurrection Remix Pie ROM you have, now you will have to have those files handy.
6. Flash the Resurrection Remix or GSI (No other ROM yet tested) to system
Type:
Code:
fastboot flash system GSI.img
This process takes a minute
7. Flash the userdata.img from the 10.0.4.0 folder (This is important!)
Type:
Code:
fastboot flash userdata userdata.img
7a. Go back to TWRP
8. Download this .zip file below and put it on your SD Card (by mounting SD Card in TWRP) in a place you will remember
The .zip file is located here find the "disable force encryption" BIG THANKS TO @eremitein
9. Boot to TWRP (Power+Volume Up keybind) flashing the encryption file above on #8 that you have on your SD Card
10. Boot to the system, check the storage in settings it may say that you have 8GB
11. Be careful hitting the wrong things may damage your device, but below follow this tap directions
11a Go back to TWRP and follow below!
11b. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "System" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
11c. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "Data" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
12. Boot up to system and check if the storage is fixed
13. Flash your GApps through TWRP for Google Services Functionality, I highly recommend micro, nano or pico.
14. Now flash Magisk zip (optional)
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Have fun with your GSI, nothing is buggy on RR so far. The fullscreen has been fixed!
Please tag me below upon what GSI's work with this method and make sure you hit that thanks button it took me awhile to put this together with multiple extreme failures .

reserved

Hi,
Can someone place a link to userdata from 10.0.4.0?
Official link isnt availible right know....
thanks

GaryFisher88 said:
Hi,
Can someone place a link to userdata from 10.0.4.0?
Official link isnt availible right know....
thanks
Click to expand...
Click to collapse
Not yet released to do so. Try the one from the dump.

Hello and thank you for the guide, everything works except the fingerprint reader, a solution? I followed the guide to the letter

It worked out the way you did.
only does not work for gcam and fingerprint reader

junior473 said:
It worked out the way you did.
only does not work for gcam and fingerprint reader
Click to expand...
Click to collapse
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first

If you have goodix fp yes need to install daisy_global_images_V9.6.11.0.ODLMIFF first but If you have fpc fingerprint no need , work in pie base stock
junior473 said:
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first
Click to expand...
Click to collapse

Flavien125 said:
Hello and thank you for the guide, everything works except the fingerprint reader, a solution? I followed the guide to the letter
Click to expand...
Click to collapse
junior473 said:
It worked out the way you did.
only does not work for gcam and fingerprint reader
Click to expand...
Click to collapse
junior473 said:
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first
Click to expand...
Click to collapse
Everything works for me on RR at least

InfinityXDA said:
Everything works for me on RR at least
Click to expand...
Click to collapse
yes, for me too now
Except the notch

When you get an update from Resurrection Remix (RR) or the original rom, is there any way to install the .zip update through TWRP?

Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner

Ithao said:
When you get an update from Resurrection Remix (RR) or the original rom, is there any way to install the .zip update through TWRP?
Click to expand...
Click to collapse
You must completely erase system with
Code:
fastboot erase system
and
Code:
fastboot erase userdata
and then flash the new version of RR
Code:
fastboot flash system “rr.img”
and reflash the userdata.img
Code:
fastboot flash userdata “userdata.img”
Otherwise you can’t update the stock version of the ROM that came with the device unless you provide a full store of 10.0.4.0 and test RR from there
The stable version of the stock ROM for RR is 10.0.3.0.

rosiepie said:
Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner
Click to expand...
Click to collapse
Did you switch to RR from 10.0.4.0

rosiepie said:
Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner
Click to expand...
Click to collapse
fp will be work if you install 9.6.11 fw + fix for modem + disable encryption and then flash RR
---------- Post added at 04:38 AM ---------- Previous post was at 04:32 AM ----------
InfinityXDA said:
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Click to expand...
Click to collapse
try Genom kernel
i had included autofix for wifi)

eremitein said:
fp will be work if you install 9.6.11 fw + fix for modem + disable encryption and then flash RR
---------- Post added at 04:38 AM ---------- Previous post was at 04:32 AM ----------
try Genom kernel
i had included autofix for wifi)
Click to expand...
Click to collapse
I have no problems what so ever I went to RR from 10.0.3.0!

can anyone please give me download link of userdata.img, i dont known how to extract it from the 1.0.0.4.0 rom
also, im kinda confused at part 4, do i wait it to reboot or should i directly go to bootloader

barumbads said:
can anyone please give me download link of userdata.img, i dont known how to extract it from the 1.0.0.4.0 rom
also, im kinda confused at part 4, do i wait it to reboot or should i directly go to bootloader
Click to expand...
Click to collapse
Use the 10.0.3.0 userdata file.That's what i used too
---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------
InfinityXDA said:
THIS REQUIRES YOUR DEVICE TO BE COMPLETELY RESTORED, PLEASE BACK UP DATA BEFORE DOING THIS.
THIS HAS ONLY BEEN TESTED ON RESURRECTION REMIX YOU CAN TEST OTHER GSI'S WITH THIS (TELL ME YOUR RESULTS BELOW)
NO CUSTOM KERNELS CAN BE APPLIED RIGHT NOW
THIS DEVICE HAS A "AB" BOOT SET SO PLEASE GET "AB" GSI'S
Grab these two files (Big Thanks to @Zerovoid from 4PDA, @Seryioo, and @mac12m99)
Fixed SDCard Support TWRP Image File (Download this and put this on your SDCard and Computer)-
Original Fixed TWRP XDA Post
Fixed SDCard Support TWRP Installer Zip (Download and put this on your SDCard)-
Fixed TWRP .zip Installer
But I got TWRP on with magisk.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA, SD CARDS, ETC ONCE AGAIN
Start with the phone being on with USB Debugging enabled with platform tools etc. correctly and bootloader unlocked
Type:
1. So flash the 10.0.4.0 ROM to get a fresh start (this is highly recommended) folder through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
1a. After it is done flashing it restarts, hurry and hold power + volume down to boot back into the bootloader
2.Boot up that TWRP.img file you downloaded above in this color
Type:
It would boot into TWRP
2a.Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip in this color above where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
2b. Hit the home button back to TWRP home screen and tap reboot >>> bootloader
3. Download this to your computer -
aboot.img
3a. Type:
Then type:
4. Afterwards you shall go back to bootloader quickly
Type:
Type:
5.Open the 10.0.4.0 folder you flashed above in #1 with MiFlash and have the "userdata.img" handy from that folder.
Download (download the one with latest date and that says "arm64" and "ab") or use the Resurrection Remix Pie ROM you have, now you will have to have those files handy.
6. Flash the Resurrection Remix or GSI (No other ROM yet tested) to system
Type:
This process takes a minute
7. Flash the userdata.img from the 10.0.4.0 folder (This is important!)
Type:
7a. Go back to TWRP
8. Download this .zip file below and put it on your SD Card (by mounting SD Card in TWRP) in a place you will remember
The .zip file is located here find the "disable force encryption" BIG THANKS TO @eremitein
9. Boot to TWRP (Power+Volume Up keybind) flashing the encryption file above on #8 that you have on your SD Card
10. Boot to the system, check the storage in settings it may say that you have 8GB
11. Be careful hitting the wrong things may damage your device, but below follow this tap directions
11a Go back to TWRP and follow below!
11b. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "System" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
11c. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "Data" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
12. Boot up to system and check if the storage is fixed
13. Flash your GApps through TWRP for Google Services Functionality, I highly recommend micro, nano or pico.
14. Now flash Magisk zip (optional)
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Have fun with your GSI, nothing is buggy on RR so far. The fullscreen has been fixed!
Please tag me below upon what GSI's work with this method and make sure you hit that thanks button it took me awhile to put this together with multiple extreme failures .
Click to expand...
Click to collapse
I have installed the gsi and it's working perfectly but now i wabt to get twrp on the phone how do i do it(i don't have encryption)?

a lot of thank for that.... iam waiting for that...lots of thank you admin...

If something goes wrong can we flash stock ROM and get the phone fixed? Does resizing the system/data partition affect the process of recovering the phone?

Custom ROMs and Recovery for Realme C12

Are you disappointed to see that there are no threads in Development section of XDA?
No worries, since Realme C11, C12 and C15 MTK share similar specs, things that are made for other two devices will work in our device too.
So our Custom ROMs and TWRP etc., are at Realme C11 forum https://forum.xda-developers.com/f/realme-c11-roms-kernels-recoveries-other-deve.10991/
Flashing Custom Recovery
First backup stock recovery
If you rooted the device, then see this, else follow below.
- Connect your device to PC
- Shift + Right click in platform-tools folder and select open command window here
- Run below commands to backup stock recovery
Code:
adb reboot recovery
adb root
adb pull /dev/block/by-name/recovery
adb reboot bootloader
You will get a file named recovery in your platform-tools folder. Rename it to stock-recovery.img and place it in safe place.
Click to expand...
Click to collapse
- Download latest TWRP from here in your PC
- Download vbmeta.img from here in your PC
- Place those two .img where platform-tools is extracted.
- Rename recovery file to custom-recovery.img
- Run below commands in command prompt that you opened above
Code:
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot flash recovery custom-recovery.img
fastboot reboot recovery
Custom Recovery is not permanent when you are using Stock ROM. It will be replaced with stock recovery after you boot to Stock ROM.(See 2nd post to overcome this)
There is no Hardware button Combo like Power + Vol Up to boot to recovery mode. Only way is to use adb/fastboot or root
Spoiler
You cannot see files in Internal Storage because of decryption(FBE) is broken in OUR device's TWRP. So use External SDCard for flashing if you are using TWRP
It will be blank for 1½ minute when you boot to TWRP 3.5.0. Don't touch the screen when it is blank. Press Power Button once to wake up screen in TWRP.
Flashing Custom ROMs
- Download custom ROM from here
- Place it in your External SDCard
- Backup the things in your InternalStorage, because we are going to wipe it.
- Boot to TWRP with below command
Code:
adb reboot recovery
- Choose Wipe and select Format Data and type yes
- Go back and choose Install and choose External-Storage in Select Storage at bottom
- Select the custom ROM zip that you downloaded above
- Flash it and Reboot
- Enjoy!
Spoiler
If you get recovery bootloops, then flash stock recovery. See below post to flash stock recovery
List of ROMs for C12Below ROMs are only for UI1. So don't flash when you are in UI2
Havoc-OS
ArrowOS
LineageOS
exTHm UI
PixelPlusUI
WaveOS
CipherOS
PixelExperience Plus
FluidOS
PixelExperience
Thanks

How to stop stock ROM from flashing stock recovery and keep custom recovery?
To do this, you need to root your C12 with Magisk.
Flash below attached RealmeRecoveryKeep.zip in Magisk app and flash custom recovery. Enjoy it accross reboots in stock rom.
Any recovery like TWRP, PBRP, SHRP, OrangeFox etc., will work with this.
Flashing Stock Recovery
Flashing it is same as TWRP.
Below I have attached Stock recovery from A.83, but it may work with any other version of UI1.
Don't flash this in UI2
First extract the zip and flash like TWRP.
SHA1 of img is:- a6ceb27226d09d6fbe9069f5e9f5448efaa10268
Guide for Flashing Stock ROM is at https://forum.xda-developers.com/t/gsi-phh-q-r-gsi-flashing-for-realme-c12.4244979/post-84630979
Thanks

I can't backup stock recovery. Getting this error:
adb: error: failed to copy '/dev/block/by-name/recovery' to '.\recovery': remote open failed: Permission denied
My bootloader is unlocked and I got magisk working.

JustAnormalGuy said:
I can't backup stock recovery. Getting this error:
adb: error: failed to copy '/dev/block/by-name/recovery' to '.\recovery': remote open failed: Permission denied
My bootloader is unlocked and I got magisk working.
Click to expand...
Click to collapse
Since you are rooted, run below commands in Termux to backup stock-recovery to internal storage.
Code:
su
dd if=/dev/block/by-name/recovery of=/sdcard/stock-recovery.img
Copy this stock-recovery.img to a safe place in your PC or External SDCard.
And also you can flash TWRP using
Code:
su
dd if=/sdcard/TWRP.img of=/dev/block/by-name/recovery

thanks a lot, i thought I got stuck with stockrom and have developer support for it

Hi!
I need to flash back my stock recovery. I have a question.
Should I flash the vbmeta.img too at first? (Just like I did while flashing twrp?)

Shawmik said:
Hi!
I need to flash back my stock recovery. I have a question.
Should I flash the vbmeta.img too at first? (Just like I did while flashing twrp?)
Click to expand...
Click to collapse
It is not needed, but flashing it will not do any harm.
Thanks

hello pa i need your help i can't flash castem room and stock room there is an error in my twrp

Zeyn0101 said:
hello pa i need your help i can't flash castem room and stock room there is an error in my twrp
Click to expand...
Click to collapse
Send the error picture

I can't post a photo here, may I ask your Instagram to send a photo of my twrp error

Zeyn0101 said:
I can't post a photo here, may I ask your Instagram to send a photo of my twrp error
Click to expand...
Click to collapse
Upload at https://oshi.at/ and send here

https://oshi.at/vZrBLB

Zeyn0101 said:
https://oshi.at/vZrBLB
Click to expand...
Click to collapse
Spoiler
{
"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"
}
Follow this https://forum.xda-developers.com/t/unbrick-your-realme-c12.4260759/post-84859061

where do i get the super.img file

HemanthJabalpuri said:
List of ROMs for C12Below ROMs are only for UI1. So don't flash when you are in UI2
exTHm UI
ArrowOS
PixelPlusUI
WaveOS
CipherOS
LineageOS
PixelExperience Plus
FluidOS
PixelExperience
Thanks
Click to expand...
Click to collapse
I would like to ask if the roms above now work on Realme C12 ui2 and if it's safe to flash a custom rom? Especially Arrow OS? Why can't they be flashed on ui2? Any idea on how to downgrade to ui1 so that I can flash it with Arrow OS?

GreatTech said:
I would like to ask if the roms above now work on Realme C12 ui2 and if it's safe to flash a custom rom? Especially Arrow OS? Why can't they be flashed on ui2? Any idea on how to downgrade to ui1 so that I can flash it with Arrow OS?
Click to expand...
Click to collapse
There is only Lineage OS for UI2 which is at https://github.com/techyminati/releases/releases/tag/1.0.2-RMX2185
Other ROMs based on UI2 will come soon.
Also if you want to downgrade to UI1 follow below steps
- Flash TWRP from https://androidfilehost.com/?fid=7161016148664786711 (Don't use other TWRP)
- Boot to TWRP
- Enable 'Skip Treble Compatibility error' in settings
- Flash ozip
- Format Data and wipe cache
- Reboot

HemanthJabalpuri said:
{Mod edit: Content of quoted post removed on request of OP.}
Click to expand...
Click to collapse
Hi! Thank you for the reply HemanthJabalpuri ! I would like to ask if you know the download link for ozip? I'm familiar with the other steps on TWRP except for ozip? Would I need to download ozip on Realme C12 or is it a setting? Do you know a reliable, stable and trusted download link for ozip? I apologize for the dumb question. Thank you for the explanation btw, I appreciate it!

GreatTech said:
Hi! Thank you for the reply HemanthJabalpuri ! I would like to ask if you know the download link for ozip? I'm familiar with the other steps on TWRP except for ozip? Would I need to download ozip on Realme C12 or is it a setting? Do you know a reliable, stable and trusted download link for ozip? I apologize for the dumb question. Thank you for the explanation btw, I appreciate it!
Click to expand...
Click to collapse
Normally, you can download latest stock rom(which is usually in .ozip format) can be found at realme website by searching 'Software update - realme' in Google to go your region specific site.
But many custom ROMs have bugs with different versions of stock rom. So suggested stock version version to be less buggy with custom roms is A.87.
All the latest and older .ozips can be downloaded at https://realmeupdater.com/downloads/archive/RMX2185/
So for A.87, here is the link for it https://download.c.realme.com/osupdate/RMX2185_11_OTA_0870_all_1TbYEnns8MEW.ozip
Thanks

HemanthJabalpuri said:
Normally, you can download latest stock rom(which is usually in .ozip format) can be found at realme website by searching 'Software update - realme' in Google to go your region specific site.
But many custom ROMs have bugs with different versions of stock rom. So suggested stock version version to be less buggy with custom roms is A.87.
All the latest and older .ozips can be downloaded at https://realmeupdater.com/downloads/archive/RMX2185/
So for A.87, here is the link for it https://download.c.realme.com/osupdate/RMX2185_11_OTA_0870_all_1TbYEnns8MEW.ozip
Thanks
Click to expand...
Click to collapse
Oh wow, nice. Thank you so much for this! I appreciate the help!

followed the steps you listed carefully, can't believe that it worked, thank you for the detailed instructions man, I successfully downgraded to realme ui1.

My experience - PIXEL EXPERIENCE PLUS (A11) - GSI-Unofficial

Stable enough to be used as your daily driver.
This rom is not developed nor maintained by me!
Credits: @ponces
Requirements: full stock EMUI 9.1, with stock recovery_ramdisk
Download arm64-ab-11.0-xxxxx
or arm64-ab-vndklite-11.0-xxxxx
Download: Link
Extra tip: try Lawnchair launcher
Install like any other GSI Rom including the Nfc patch.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
Quick and easy way to install GSI & NFC :
1. Extract the ROM .img file from the compressed file.
2. Flash extracted ... .img in fastboot , use command
fastboot flash system (file_name).img
3. In fastboot flash TWRP over eRecovery (!) - guide:
https://forum.xda-developers.com/t/rom-official-anne-9-lineageos-16-0.4151163/post-83603363
4. Run command fastboot reboot , enter TWRP (press and hold Volume Up)
5. In TWRP unmount all except SD Card , Vendor and System (unmount and mount again if needed) and flash NFC patch
6. Go back to the TWRP's main menu, select Reboot > Recovery.
7. Now you can perform factory reset in stock Recovery.
Note: the TWRP will remain instead of eRecovery.
MAGISK ROOT :
(Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ).
Install TWRP-9.1
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
over eRecovery (it's necessary on EMUI 9.1 - Guide
( Note: for those who want keep the erecovery as a fail-safe:
https://forum.xda-developers.com/t/...-erecovery-with-twrp-installed-on-it.4357127/ )
1. In TWRP flash Mount-fix .zip file
2. Reboot into TWRP
3. Select 'Install Image' and flash
patched recovery_ramdisk
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
over recovery_ramdisk.
4. Go back , select Reboot > Recovery.
5. Install Magisk manager apk:
https://mega.nz/file/go0m2RiR#M5UTv6FPjWPtDaGPr-u2tpJMCwdf8uwnniZg69LiGfw
(SafetyNet
Contactless payments with Magisk v23.0 )
How to boot into patched Recovery :
- Restart your phone, when appears the yellow warning on the screen, press and hold Volume Up for ~ 2 sec,
release the button and immediately press and hold again for ~ 2 sec. Repeat it 6-7 times, the device will reboot into Stock Recovery (you can perform Wipe cache or Factory reset, also you can use dload method).
ROOT WITH SUPERUSER:
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE
Not working: VoLTE, LED notification (at least for me)
Screenshots:
{
"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"
}

-Alf- said:
Stable enough to be used as your daily driver.
Credits: @ponces
Requirements: full stock EMUI 9.1, with stock recovery_ramdisk for "arm64-ab" (not vndklite!)
or EMUI 8 for "arm64-aonly"
Download: here
Install like any other GSI Rom including the Nfc patch.
Not working: VoLTE, LED notification (at least for me)
Screenshots:
View attachment 5350493View attachment 5350495View attachment 5350497View attachment 5350499View attachment 5350503View attachment 5350505View attachment 5350507View attachment 5350509View attachment 5350511View attachment 5350513
Click to expand...
Click to collapse
Thanks for sharing !
Is there any difference between Lineage and Pixel Experience?

Fjord1 said:
Thanks for sharing !
Is there any difference between Lineage and Pixel Experience?
Click to expand...
Click to collapse
On Pixel Exp. some things work easier and more flexible . And I don't think it's just a placebo

Thanks so much I've been looking for an android11 pixel experience for the p20 lite
Can you use magisk with this?

joenuts2124 said:
Can you use magisk with this?
Click to expand...
Click to collapse
GSI rom is not related to recovery_ramdisk, so it is possible to use the Magisk root on any GSI roms .

I was recently thinking to switch on that rom because there are no more lineageos updates.
Is there an easy way to backup and restore data from lineage to pixel?

Incomtus said:
I was recently thinking to switch on that rom because there are no more lineageos updates.
Is there an easy way to backup and restore data from lineage to pixel?
Click to expand...
Click to collapse
Try this method
https://forum.xda-developers.com/t/migrate-custom-rom-migration-tool.4252863/
There are several options, I do not remember exactly, but I think that the best results I had with Flasher & Helper

Tried it but magisk is not working....

Incomtus said:
Tried it but magisk is not working....
Click to expand...
Click to collapse
...not at all, or for Migrate only ? And what about SuperUser?

DSU Loader not working, phone don't support?

joenuts2124 said:
DSU Loader not working, phone don't support?
Click to expand...
Click to collapse
DSU loader requires a/b partitions (two different system partitions).

-Alf- said:
DSU loader requires a/b partitions (two different system partitions).
Click to expand...
Click to collapse
Doesn't emui 9.1 have ab?

joenuts2124 said:
Doesn't emui 9.1 have ab?
Click to expand...
Click to collapse
-Alf- said:
DSU loader requires a/b partitions (two different system partitions).
Click to expand...
Click to collapse
It should be clear, hm?
"AB" in GSIs is not the same thing as physically having AB partitions .
"AB" in GSIs means SAR - system-as-root ( on EMUI 9.1).
P20 Lite supports Project Treble AB, yet is an A-only device ( does not support Seamless Updates).

-Alf- said:
...not at all, or for Migrate only ? And what about SuperUser?
Click to expand...
Click to collapse
Not at all, it says like if was not installed, I tried super user app and it tells like not rooted. I have almost same Magiqk issue with Andy Yann lineage but Superuser is working on Andy Yann

Incomtus said:
Not at all, it says like if was not installed, I tried super user app and it tells like not rooted. I have almost same Magiqk issue with Andy Yann lineage but Superuser is working on Andy Yann
Click to expand...
Click to collapse
IMO you are doing something wrong .
If you have followed instructions in OP to the letter, it must work. Today I tested SuperUser, also works .
Try total clean flashing - flash service ROM and try again.

-Alf- said:
IMO you are doing something wrong .
If you have followed instructions in OP to the letter, it must work. Today I tested SuperUser, also works .
Try total clean flashing - flash service ROM and try again.
Click to expand...
Click to collapse
Very strange i made a clean install,
I went back to stock 9.1.0.132 with DLOAD
I unlocked bootloader and flash the rom with fastboot, i flashed TWRP (9.1) for nfc,
I made a wipe with stock recovery, I booted again on TWRP , i flashed magisk mount fix reboot again on TWRP flashed patched recovery on recovery, and exactly same issue,
I used the same twrp for nfc and magisk. Magisk aint working on last andy Yann build either but works on Emiritein Lineage Os build ( but this one is older)
Did you tried with last build?
For Pixel I tried superuser app on fdroid but doesnt work

Incomtus said:
Did you tried with last build?
Click to expand...
Click to collapse
9.1.0.257
Incomtus said:
For Pixel I tried superuser app on fdroid but doesnt work
Click to expand...
Click to collapse
And why not the superuser linked in OP? Okay, your choice bro...
I'm afraid I can't help you anymore.

I did not see there were an Superuser app in op I was confused with Andy yann forum I made a mix with that two posts
But it is strange that magisk doesn't work if it works for you
Do I have to flag magisk AND superuser ZIP file ?

Incomtus said:
flashed patched recovery on recovery,
Click to expand...
Click to collapse
Then you need boot Recovery to get root permissions (due to patched ramdisk)
Incomtus said:
I did not see there were an Superuser app in op?
Click to expand...
Click to collapse
"Root with Phh SuperUser :
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE"

-Alf- said:
Then you need boot Recovery to get root permissions (due to patched ramdisk)
"Root with Phh SuperUser :
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE"
Click to expand...
Click to collapse
Yes I know that I have to reboot on recovery that's what I did, as I use to do it with other GSI. But I did not understand I have to root with phh also

Development Exynos 850 Resources ]TWRPs] [Kernels]

{
"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"
}
Devices post#1
Root method post#2
TWRP post#3
Kernels post#4
Debloaters post #5
wizzROM creators post #6
Exynos 850 Devices
1. A12s
A127f & A127m
2. M12
M127f & M127g
3. A21s
A217f & A217m
4. F12s
F127g
5. A13
A135f & A135m
6. M13
M135f & M135m
7. F13
E135f
8. A04s
A047f
9. XCover5
G525f
10. A145f

Root for Exynos 850
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 delta magisk
3. Use zarchiver to extract the ap section from the firmware.
4. Use magisk to patch the ap section.(install, select file to patch)
5. Unlock the bootloader.
6. Flash the patched ap file using Odin.
Or with heimdall
7. Reboot.
8. Go all the way through the set-up process.
9. Don't upgrade your magisk of you won't see the online modules
@physwizz

Installing Custom Recoveries
A. Preparation.
1. Download firmware for your device
2. Extract ap file using Zarchiver and extract recovery.img from recovery.img.lz4 and compress it to recovery.tar
3. Patch the ap file with a magisk which will patch both boot.img and vbmeta.img (from magisk, choose install then select file to patch)
Alternatively you can extract boot.img.lz4 and vbmeta.img.lz4 from the ap file and compress them into a new tar file and then patch that file.
note: if you don't want root then just extract the vbmeta.img and use zarchiver to add it to my twrp.tar file.
You can flash this new file from odin at step 5
For Exynos 850 android 11 use a21s patched magisk.
For Exynos 850 android 12 and most other devices use delta magisk
4. Unlock OEM in developer options
5. Attach phone to pc and reboot to download mode
6. flash patched ap file.
Or..
Extract boot.img and vbmeta.img and add them to the TWRP zip.
7. Download the zip and extract the twrp.tar and extract recovery.img using Zarchiver.
B.Installation
Method 1.
1. Connect to pc and boot into stock recovery
2. Factory reset
3. Reboot into download mode.
4. flash twrp.tar into the ap slot
5. reboot to recovery from main menu (not just reboot)
be patient- It may take a while
6. Advanced, terminal. Type multidisabler (twice).
7.
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
8. Reboot to recovery from main menu (not just reboot)
Backup boot, data, super and dtbo
9. Reboot to system
Method 2.
If you have already installed recovery and decrypted.
Extract recovery.img
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to system then reboot to recovery
Backup boot, data, super and dtbo
(For Pitch-black just install the zip)
Method 3.
1. Install TWRP app
Extract recovery.img
2. Install TWRP
3. Choose file to flash.(don't select device)
4. Select recovery.img.
5. Reboot to recovery.
6. (You may need to change data partition to ext4 first if format ruins your system)
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
11.Reboot to recovery
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
Method 4
Using a second phone
C. Recovery Problems
Most recovery issues can be solved by attending to the following issues.
1. Did you root using the full ap file patched Magisk .
(This contains the patched boot.img and vbmeta.img)
Exynos 850 users must use the special a217 magisk?
2. Did you then go all the way through the setup process?
3. Did you download the recovery to match your device
4. Did you hold down power and volume up after Odin says pass?
5. Did you format data from stock recovery?
If you forgot to do this, just install stock recovery.img from TWRP and reboot.
6. Did you type multidisabler twice?
7. Did you reboot to recovery by choosing reboot from the menu and then choosing recovery?
8. To avoid touch issues go to settings and untick "allow time out"
D.To restore Stock Recovery
1. Attach phone to pc and reboot to download mode
2. flash patched ap file or stock recovery.tar
3. reboot
Or just flash stock recovery.img from twrp and reboot.
TWRP Building Guide
Guide to TWRP building
TWRP for a12s ============= 1. Setup -------- sudo apt update sudo apt upgrade sudo apt-get install git-all sudo apt install python-is-python3 git config --global user.email "your email" git config --global user.name "your name" 2...
forum.xda-developers.com
@physwizz
These TWRPs are all derived from my a127f device tree.
Code
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com

Kernels
Installing physwizz custom kernels
INSTALL AT YOUR OWN RISK
I AM NOT RESPONSIBLE FOR ANY BRICKED PHONES
But I will help any well-mannered person to recover.
Note: physwizz kernels work best with debloated stock or with wizzROM
Other custom ROMs may not be supported
A. Preparation
1. Root the phone
2. Compress your patched boot.img to make boot.tar
3. Copy boot.tar to PC
Note: If you have previously installed a custom dtbo, you may need to flash stock dtbo
Physwizz Collection
Dtbo installer Extract stock dtbo.img from your firmware. Add to the zip using zarchiver. Use stock dtbo.img from your baseband (not your kernel or your ROM)
t.me
B. Installation
Method 1
Install from twrp
Reboot to recovery
Backup boot and dtbo (if available)
Install kernel zip or boot.img
Wipe both caches
Reboot
Method 2
Install kernel from terminal.
1. Download magisk module (magic flash zip) https://github.com/Magisk-Modules-Alt-Repo/magic-flash
2. Install module and reboot.
3. Open terminal.
4. Navigate to folder containing kernel zip.
Use
ls to list contents
and
cd to change directories
5. Type su
6. Type flash kernel zip
7. Reboot
Method 3
Using ADB
Install adb tools on pc
Connect to PC
Copy zip file to adb folder on pc
Open terminal on pc
Navigate to adb folder
Type
adb sideload filename.zip
Method 4
Using boot.img
Install AIK Mobile from magisk modules https://t.me/physwizz2/82
Use rootexplorer to access
/data/local/AIK-MOBILE
Add patched boot.img and tap unpackimg.sh
Exit the folder and return to see the files.
Edit the files (eg to add a new Image
rename Image to boot.img-zImage and insert in split-image folder)
Tap repackimg.sh
Rename new_image.img to boot.img
Compress boot.img to boot.tar
Copy boot.tar to PC
Reboot phone to download mode
Install boot.tar from odin
Method 5
Using a second phone
1. Prepare boot.img as in Method 4.
2. Go here
Physwizz Collection
Installing boot.img using a second phone. You can install a new kernel without a PC by using patched boot.img from phone1 to phone2 Preparation 1. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or...
t.me
C. Removal
Method 1
Reboot to recovery
Restore boot and dtbo
Reboot
Method 2.
Reboot phone to download mode
Install patched boot.tar or patched-ap.tar from odin
@physwizz
Kernel Properties
Samsung securities disabled
More CPU governors
On-demand, Userspace, powersave, performance, energy_step, shedutil
Optimised for performance
Overclocked for performance
Underclocked for battery
CPU: 130MHz - 2210MHz
lz4 default compression added to zram
Kernel source code
physwizz - Repositories
physwizz has 172 repositories available. Follow their code on GitHub.
github.com

physwizz debloat module v3
(Added a70 changes)
With physwizz-2 app
Fixed apps in system/product
Installing
Physwizz Collection
t.me
NOTE: you may still need to delete some apps from the app drawer.
Magisk module to debloat any Samsung phone to remove all the apps that slow down the phone
To debloat:
Install the module from Magisk and reboot.
To rebloat:
delete the module in Magisk and reboot
@physwizz

wizzROM Creator magisk module v4 Thermal
DO NOT INSTALL FROM TWRP
for all Samsung phones
Debloated ROM with Extras
Fixed apps in system/product
Extras:
Battery charge limit
Clean Master
ES file explorer
HKtweaks
SimpleReboot
Root Explorer
Zarchiver
physwizz-2
Thermal throttling removed
Make sure your OneUI ROM iis running befote you start
Installation
1 Backup system from recovery
2 Install the creator from Magisk
Physwizz Collection
t.me
3 Reboot
4 Enjoy
NOTE: you may still need to delete some apps from the app drawer.
Name your wizzROM (optional)
1. Use a root explorer to navigate to system/build.prop
2. Tap to Edit build.prop like this
ro.build.display.id=<your-name>
3. Tap disk icon to Save & Reboot
Xda post
wizzROM Creator
wizzROM Creator module v4 Thermal for all Samsung a-series phones OneUI 2.0 will become QwizzROM OneUI 3.1 will become RwizzROM OneUI 4.0 will become SwizzROM Debloated ROM with Extras Fixed apps in system/product Extras: Battery charge limit...
forum.xda-developers.com
@physwizz

Hi guys! I'm very new to this so sorry for mi lack of knowledge on this but i wanted to ask, i've an sma135m, exynos 850 but its stock kernel comes as 32bit forced. Is there any kernel which you provides that gives the capability to use the processor at full 64bit? Thanks in advance!

arieleoar said:
Hi guys! I'm very new to this so sorry for mi lack of knowledge on this but i wanted to ask, i've an sma135m, exynos 850 but its stock kernel comes as 32bit forced. Is there any kernel which you provides that gives the capability to use the processor at full 64bit? Thanks in advance!
Click to expand...
Click to collapse
No sorry.
But my kernel will make it better

physwizz said:
Root for Exynos 850
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 delta magisk
3. Use zarchiver to extract the ap section from the firmware.
4. Use magisk to patch the ap section.(install, select file to patch)
5. Unlock the bootloader.
6. Flash the patched ap file using Odin.
Or with heimdall
7. Reboot.
8. Go all the way through the set-up process.
9. Don't upgrade your magisk of you won't see the online modules
@physwizz
Click to expand...
Click to collapse
Hello! Thanks fpr the instruction, but I faced with issue that my SM-137F is also using Exynos 850 after installing the modified AP with ODIN (flashing full BL, AP, CSC, CP) using this version of Magisk Delta (like I've tried others as well) falls into Bootloop (don't even runs the system, just starts -> logo asking press power button -> new logo with warning of custom firmware -> reboot, and then again). So I've tried many different Magisk versions - result the same.
So the question is, what do I do wrong?
Firmware version SM-A137F_XSG_A137FXXU1AVH1 (Android 12)
And I haven't do patching using the phone, I've installed the Magisk on the Android Studio emulator and patching there, may be this a reason?

Sawery said:
Hello! Thanks fpr the instruction, but I faced with issue that my SM-137F is also using Exynos 850 after installing the modified AP with ODIN (flashing full BL, AP, CSC, CP) using this version of Magisk Delta (like I've tried others as well) falls into Bootloop (don't even runs the system, just starts -> logo asking press power button -> new logo with warning of custom firmware -> reboot, and then again). So I've tried many different Magisk versions - result the same.
So the question is, what do I do wrong?
Firmware version SM-A137F_XSG_A137FXXU1AVH1 (Android 12)
And I haven't do patching using the phone, I've installed the Magisk on the Android Studio emulator and patching there, may be this a reason?
Click to expand...
Click to collapse
1. A137 is Mediatek MT6769V/CU Helio G80 (12 nm)
2. You must patch using the phone

physwizz said:
1. A137 is Mediatek MT6769V/CU Helio G80 (12 nm)
2. You must patch using the phone
Click to expand...
Click to collapse
1. Oh my god, sorry... What version of Magisk for getting root do I need to use the, maybe you know?
2. Really? Why? I thought it's just changing the binary and doesn't matter when the Magisk launched, on this phone, emulator, or any other phone

Sawery said:
1. Oh my god, sorry... What version of Magisk for getting root do I need to use the, maybe you know?
2. Really? Why? I thought it's just changing the binary and doesn't matter when the Magisk launched, on this phone, emulator, or any other phone
Click to expand...
Click to collapse
If it doesn't work on the emulator try it on the phone.
I'll ask someone else who owns one

Sawery said:
1. Oh my god, sorry... What version of Magisk for getting root do I need to use the, maybe you know?
2. Really? Why? I thought it's just changing the binary and doesn't matter when the Magisk launched, on this phone, emulator, or any other phone
Click to expand...
Click to collapse
Yes he did it with patched ap file.
He also did it using official magisk apk and with twrp

physwizz said:
Yes he did it with patched ap file.
He also did it using official magisk apk and with twrp
Click to expand...
Click to collapse
Sorry, but maybe he has the right working twrp for my device? If yes, could you share with me? I cant find it as well anywhere, thanks a lot!

Sawery said:
Sorry, but maybe he has the right working twrp for my device? If yes, could you share with me? I cant find it as well anywhere, thanks a lot!
Click to expand...
Click to collapse
I'll ask him

Sawery said:
Sorry, but maybe he has the right working twrp for my device? If yes, could you share with me? I cant find it as well anywhere, thanks a lot!
Click to expand...
Click to collapse
Good morning,
Do have a semi-working TWRP. So far didn't have the time to fix FBE for /data partitions. But if you have a big enough SD Card it should be fine to use.
ZIP file holds just recovery.img (to flash direct if phone is rooted
recovery.tar.md5.zip can be used to flash on ODIN (AP slot). First extract zip to get tar.md5 file

edward0181 said:
Good morning,
Do have a semi-working TWRP. So far didn't have the time to fix FBE for /data partitions. But if you have a big enough SD Card it should be fine to use.
ZIP file holds just recovery.img (to flash direct if phone is rooted
recovery.tar.md5.zip can be used to flash on ODIN (AP slot). First extract zip to get tar.md5 file
Click to expand...
Click to collapse
I don't know, my only goal is to add root on my device somehow, but the only way as I understand is Magisk, I hoped to install it with TWRP as nothing works for me using ODIN flashing. Nothing works for me (SM-A137F_XSG_A137FXXU1AVH1 Firmware), the device endlessly reboots after this image on the screen (even if I'm trying to get to the recovery menu). But anyway thanks for the time and for the files.

physwizz said:
1. A137 is Mediatek MT6769V/CU Helio G80 (12 nm)
2. You must patch using the phone
Click to expand...
Click to collapse
The second point should be definitely added to README.MD in official Magisk github account, because there aren't any warning about using only the same phone for patching that you are going to root, as I understand that it is patching according to the type of processor in addition to other parameters.
Anyway thanks for help, it works for me, I've successfully rooted 2 different devices already (Samsung Galaxy A13 SM-A137F and Samsung Galaxy A03 Core SM-A032F if someone will be searching for).

Sawery said:
The second point should be definitely added to README.MD in official Magisk github account, because there aren't any warning about using only the same phone for patching that you are going to root, as I understand that it is patching according to the type of processor in addition to other parameters.
Anyway thanks for help, it works for me, I've successfully rooted 2 different devices already (Samsung Galaxy A13 SM-A137F and Samsung Galaxy A03 Core SM-A032F if someone will be searching for).
Click to expand...
Click to collapse
I don't think it needs to be the same phone but I don't think the emulator does a good job in that respect

A145f twrp now available

Database Info

welcome