{
"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"
}
I would like to thank TeamWin for their amazing work!
I saw that the newer Samsung MediaTek phones were not getting any sort of love, so I bought one myself to kick start the development.
I have already made TWRP for M32 & A41 and thought why not add support for a sister device.
KEEP IN MIND THIS IS A BETA BUILD, expect bugs!
TWRP is the obvious choice as it is reliable and trustworthy with frequent updates and patches.
INSTALLATION:
Odin Method (Windows):
Step 0: Unlock Device Bootloader by toggling the OEM Unlock option in Developer Options. Device will reboot to Odin mode and will prompt you to long press volume up, device will then unlock bootloader and perform a complete factory reset so make sure to backup any data.
Step 1: Download the unofficial TWRP image from the link attached below.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Select the downloaded recovery.tar in AP slot and vbmeta_disabled_R.tar in USERDATA slot, connect the device to PC, go to options and untick "Auto-Reboot"
Step 4: Click START and the Device will get flashed, Odin will say SUCESS!.
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your F22 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
Heimdall Method (Linux):
Step 1: Install heimdall tool on linux , google it.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Open up terminal in the downloaded TWRP directory, extract twrp image from recovery.tar
Step 4: Enter the command "heimdall flash --RECOVERY recovery.img --no-reboot" where twrp.img is name of the downloaded image
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your F22 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
COMPATIBILITY:
TWRP Recovery is compatible with latest Android 11 firmware
tested on:
E225FXXU4AVB1 by @sunmughan thank you bro.l
First time you boot into TWRP, don't forget to backup your EFS, Secondary EFS and NVRAM! Go into Backup and select "EFS,", "Secondary EFS" and "NVRAM" and backup to preferably MicroSDcard and copy it to your PC in case you need it if IMEI corrupts.
DON'T IGNORE THIS STEP!
All kernel source and device tree below!
Device Tree: TWRP Device Tree
Kernel Tree: TWRP Kernel Tree
DOWNLOADS:
VBMETA DISABLED FOR R: MEGA LINK
TWRP TAR: MEGA LINK
I am getting:
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
fermi6-626 said:
I am getting:
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
Click to expand...
Click to collapse
you tried with ODIN or HEIMDAL?
MrVenom. said:
you tried with ODIN or HEIMDAL?
Click to expand...
Click to collapse
i tried with both odin and heimdall
First off, the twrp itself boots. But I couldn't find "System" or "Super" in erase section. I am not sure how useful it will be if I can't erase that before flashing another image.
fermi6-626 said:
I am getting:
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
Click to expand...
Click to collapse
This error is not from TWRP itself. He just didn't unmount the partitions first. That's all. I didn't get the error when I dismounted first. Without dismounting, I see 16 unable to unlock errors.
Update: Another setback, TWRP can't flash super images. Only way would have been to use fastboot which is botched by uncle sam. Any other way to flash gsi images to this?
This error is not from TWRP itself. He just didn't unmount the partitions first. That's all. I didn't get the error when I dismounted first. Without dismounting, I see 16 unable to unlock errors.
Click to expand...
Click to collapse
Actually, The errors persists even after I unmount the partitions before flashing.
The errors are there whether I mount or unmount the partitions(at least for my device), but the correct procedure is unmounting before flashing.
But I couldn't find "System" or "Super" in erase section. I am not sure how useful it will be if I can't erase that before flashing another image.
Click to expand...
Click to collapse
Beats me.
[edit: /system partition is by default always unmounted before flashing a zip]
I should have heeded the warning. I didn't backup EFS, Secondary EFS and NVRAM.
Now , there is no IMEI and cant use the sim.
Is there any solution to this?
Thank you in advance.
dekisugihidetoshi said:
I should have heeded the warning. I didn't backup EFS, Secondary EFS and NVRAM.
Now , there is no IMEI and cant use the sim.
Is there any solution to this?
Thank you in advance.
Click to expand...
Click to collapse
I am fighting myself real hard not to reply with akhils avatar, but efs (for sure) and nvram (can't say for sure) is included in the stock, flash stock, probably gonna be alright.
fermi6-626 said:
Beats me.
Click to expand...
Click to collapse
There're these packages.... DynaPatch is less known and probably not so much polished and then there's the ChonDoe_Flasher, they can be used to flash gsi and then there was a linux thingy which is used to pack system.img into super.img with vendor.img and others so that twrp can flash it directly.
Akhil99 said:
I would like to thank TeamWin for their amazing work!
I saw that the newer Samsung MediaTek phones were not getting any sort of love, so I bought one myself to kick start the development.
I have already made TWRP for M32 & A41 and thought why not add support for a sister device.
KEEP IN MIND THIS IS A BETA BUILD, expect bugs!
TWRP is the obvious choice as it is reliable and trustworthy with frequent updates and patches.
INSTALLATION:
Odin Method (Windows):
Step 0: Unlock Device Bootloader by toggling the OEM Unlock option in Developer Options. Device will reboot to Odin mode and will prompt you to long press volume up, device will then unlock bootloader and perform a complete factory reset so make sure to backup any data.
Step 1: Download the unofficial TWRP image from the link attached below.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Select the downloaded recovery.tar in AP slot and vbmeta_disabled_R.tar in USERDATA slot, connect the device to PC, go to options and untick "Auto-Reboot"
Step 4: Click START and the Device will get flashed, Odin will say SUCESS!.
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your F22 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
Heimdall Method (Linux):
Step 1: Install heimdall tool on linux , google it.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Open up terminal in the downloaded TWRP directory, extract twrp image from recovery.tar
Step 4: Enter the command "heimdall flash --RECOVERY recovery.img --no-reboot" where twrp.img is name of the downloaded image
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your F22 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
COMPATIBILITY:
TWRP Recovery is compatible with latest Android 11 firmware
tested on:
E225FXXU4AVB1 by @sunmughan thank you bro.l
First time you boot into TWRP, don't forget to backup your EFS, Secondary EFS and NVRAM! Go into Backup and select "EFS,", "Secondary EFS" and "NVRAM" and backup to preferably MicroSDcard and copy it to your PC in case you need it if IMEI corrupts.
DON'T IGNORE THIS STEP!
All kernel source and device tree below!
Device Tree: TWRP Device Tree
Kernel Tree: TWRP Kernel Tree
DOWNLOADS:
VBMETA DISABLED FOR R: MEGA LINK
TWRP TAR: MEGA LINK
Click to expand...
Click to collapse
hello brother, this unofficial twrp tar cause me bootloop pls can you fix this. on my samsung f22 android 12 E225FXXU4BVF1
fermi6-626 said:
I am getting:
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
Click to expand...
Click to collapse
Just ignore those errors.
Hello there! Is there any files that I could directly use to flash twrp? I already am root through magisk and didn't find the supported module/device of twrp which I downloaded from play store. Still no support for F22. So how do I install it? Without any desktop or pc. directly through my rooted phone? Thanks!
I haven't tried it yet, but in theory, shouldn't it work with android S & T if the appropriate vbmeta is flashed?
There is a new binary update, u5. Downgrading won't be possible and this device has only this twrp for it, to my knowledge.
dekisugihidetoshi said:
I should have heeded the warning. I didn't backup EFS, Secondary EFS and NVRAM.
Now , there is no IMEI and cant use the sim.
Is there any solution to this?
Thank you in advance.
Click to expand...
Click to collapse
Does this error got solved or not because i want to try custom rom in my samsung f22 please help me
Related
Team Win Recovery Project 3.0.2-0
This is for the Exynos WiFi SM-T580 model only!
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your retailer to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxytaba101wifi2016.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR OBTAINING ROOT
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"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"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for gtaxlwifi.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Initial build on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/jcadduono/android_device_samsung_gtaxlwifi (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_exynos7870 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
Thanks for this work!
I managed to flash and boot into TWRP recovery but i have partition problem :
"failed to mount data"
"internal storage is listed as 0MB"
http://imgur.com/a/Ut3S7
http://imgur.com/qDCs9iS
EDIT2: As mentionned by @jcadduono , there is a simpler method than mine :
BTW you can just flash TWRP and use the [Format Data] button on wipe page which will do the same thing, making data available (but completely wiped, including internal storage!!!)
Click to expand...
Click to collapse
EDIT3: use@ashyx' patch to remove encryption:
BOOT IMAGE PATCHER
Boot image patcher to remove DM-verity and Forced encryption.
Flash the zip below with TWRP.
This was built by jcadduono not me, so props to him, I just modified it to work for this device and to remove the SEANDROID ENFORCING message.
NOTE: IF YOU INTEND TO ROOT THEN FLASH THIS AFTER SUPERSU.
no-verity-no-encrypt_ashyx
.
Click to expand...
Click to collapse
bws78 said:
Thanks for this work!
I managed to flash and boot into TWRP recovery but i have partition problem :
"failed to mount data"
"internal storage is listed as 0MB"
http://imgur.com/a/Ut3S7
http://imgur.com/qDCs9iS
EDIT: I found out a solution to solve my problem, at least to root my device.
-Flash back stock recovery using odin
-Boot in stock recovery and Wipe data/factory reset
-Boot DIRECTLY in download mode (DO NOT NORMAL BOOT)
-Flash TWRP recovery using odin
-Boot DIRECTLY in TWRP recovery (DO NOT NORMAL BOOT)
(/data partition should be visible)
-For root flash Supersu.zip (or what you want)
-reboot system (device is now rooted)
Each time my device boot on android I lose /data partition in TWRP, maybe due to partition encryption
Click to expand...
Click to collapse
yes Exynos 7870 devices currently have a bug where Samsung is using their own crypto daemon and telling vold to force encryption regardless of fstab flags, I reported it to Samsung security team but not sure if they are looking into it. So far haven't found a way to prevent encryption from happening. (I removed all references to encryption in ramdisk & system.prop and it still encrypts, wow!)
BTW you can just flash TWRP and use the [Format Data] button on wipe page which will do the same thing, making data available (but completely wiped, including internal storage!!!)
Could it possibly work for SM-T585? Would it be possible to use your repos and compile a build for my tab?
Alexander_the_B0ss said:
Could it possibly work for SM-T585? Would it be possible to use your repos and compile a build for my tab?
Click to expand...
Click to collapse
I've been hoping someone would show up with the T585 in the #twrp channel on freenode so we could work on it, it would only take minimal changes (basically just take the dtb from stock T585 rom I guess, kernels should be exactly the same)
You could try flashing T580 TWRP and let me know if it works though, then I can just combine them if so.
jcadduono said:
I've been hoping someone would show up with the T585 in the #twrp channel on freenode so we could work on it, it would only take minimal changes (basically just take the dtb from stock T585 rom I guess, kernels should be exactly the same)
You could try flashing T580 TWRP and let me know if it works though, then I can just combine them if so.
Click to expand...
Click to collapse
I am too tired right now and not in the mood. Very sick, having some tooth issues and maybe we can sort this out somehow. But not today, I am really sorry. May be tomorrow. Add 13 hours to your time and you'll know if I am on-line or not. It's about 7 am here, been up all night and need some sleep. Just PM me whenever you can and I'll hop on Freenode.
I'm having problems booting from Download mode (after flashing recovery via Odin) directly into Restore mode... Is there a trick I'm missing? I can't seem to find a way to get the battery out so right now all I can do is reboot in Download_mode>cancel>volume up and I'm in TWRP but same partition/data issue as above. Thanks for any help
8BitAirwaves said:
I'm having problems booting from Download mode (after flashing recovery via Odin) directly into Restore mode... Is there a trick I'm missing? I can't seem to find a way to get the battery out so right now all I can do is reboot in Download_mode>cancel>volume up and I'm in TWRP but same partition/data issue as above. Thanks for any help
Click to expand...
Click to collapse
In download mode press [power + vol down + home], when the screen turn off press [power + vol up+ home].
But you should try format data in twrp (on wipe page) as mentioned by jcadduono. It's a easier way to remove partition encryption (wipe everything on /data)
bws78 said:
But you should try format data in twrp (on wipe page) as mentioned by jcadduono. It's a easier way to remove partition encryption (wipe everything on /data)
Click to expand...
Click to collapse
First off thank you so much for the fast reply, I should have thought of that- well the button swap I never would have come up with the quoted I'm rather new/in middle of a dedicated but gradual move from iOS Dev to Android! Loving it and this community, thanks again
root sm-t580
@bws78
Hello,
Sorry for my bad english, first!
To Boot DIRECTLY in download mode from stock recovery correctly once i wipe data/factory reset, do i have to power off and then use buttons power + (volume -) + home?Is that correct?
Same thing when i finish to Flash TWRP recovery using odin to boot DIRECTLY in TWRP recovery, buttons : power + (volume +) + home ?
Thanks fo your response
yetibiker said:
@bws78
Hello,
Sorry for my bad english, first!
To Boot DIRECTLY in download mode from stock recovery correctly once i wipe data/factory reset, do i have to power off and then use buttons power + (volume -) + home?Is that correct?
Same thing when i finish to Flash TWRP recovery using odin to boot DIRECTLY in TWRP recovery, buttons : power + (volume +) + home ?
Thanks fo your response
Click to expand...
Click to collapse
To boot in download mode from stock recovery, go to power off or reboot system and when the screen turn off press
[power + vol down + home].
To boot in recovery mode from download mode, long press [power + vol down + home], when the screen turn off press [power + vol up+ home].
But this method it's tedious. Try @jcadduono method to wipe /data encryption from TWRP:
BTW you can just flash TWRP and use the [Format Data] button on wipe page which will do the same thing, making data available (but completely wiped, including internal storage!!!)
Click to expand...
Click to collapse
recovery t580
Hello,
I flash the TWRP in download mode whithout doing data/factory reset before in stock recovery but when i try to reboot in TWRP, because odin say success, i'm finally in stock recovery!
How many times i've to wait the bar stop in download mode? Because the bar wasn't totally full when i reboot, miss just a very little bit, but after few(too long) minutes i try to reboot to go on TWRP but not here, just stock recovery. I missed up something? I can't remove battery, is that for?
Thanks for your time
So this replaces the regular recovery image? If so the first thing I'd want to do is make a backup I guess right?
I know this looks to be early days, but anyone looking into cm on this device(just got it today) also any luck with xposed?
---------- Post added at 04:22 PM ---------- Previous post was at 04:19 PM ----------
UntouchedWagons said:
So this replaces the regular recovery image? If so the first thing I'd want to do is make a backup I guess right?
Click to expand...
Click to collapse
Samsung is really good about having odin flashable packages available so if there is issues you can always restore via download mode (never heard of a permanent soft brick in years for a Samsung device)
jaykoerner said:
Samsung is really good about having odin flashable packages available so if there is issues you can always restore via download mode (never heard of a permanent soft brick in years for a Samsung device)
Click to expand...
Click to collapse
Do you know where I'd get one of these packages just in case?
I've used the first site not the second, sammobile is trustworthy. The other is for redundancy.
http://www.sammobile.com/firmwares/database/SM-T580/
http://samsung-updates.com/device/?id=SM-T580
Also recovery and stock firmware is on xda, somewhere it's just hard to find since this device doesn't have a forum.
jaykoerner said:
I've used the first site not the second, sammobile is trustworthy. The other is for redundancy.
http://www.sammobile.com/firmwares/database/SM-T580/
http://samsung-updates.com/device/?id=SM-T580
Also recovery and stock firmware is on xda, somewhere it's just hard to find since this device doesn't have a forum.
Click to expand...
Click to collapse
What's with all the countries? What would I choose for North America?
UntouchedWagons said:
What's with all the countries? What would I choose for North America?
Click to expand...
Click to collapse
Yes, but the only real reason is so the device has the correct language settings. They should all be compatible but if you choose your region you don't have to worry.
Step 8 says to download the tar file in the AP slot, but the download page for TWRP is an img file, do I just tar the image using 7zip?
UntouchedWagons said:
Step 8 says to download the tar file in the AP slot, but the download page for TWRP is an img file, do I just tar the image using 7zip?
Click to expand...
Click to collapse
You'll find the link for the tar file in the OP (Temporary Download).
Unofficial release -TWRP recovery for the Samsung Galaxy Tab S3 - SM-T820/T825, Qualcomm MSM8996
{
"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:
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 (jlask)
Update 18/5/2018
TWRP 3.2.1-1 build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below) >> to be added
NTFS support
F2FS support >> To be added
Twrp app support
IMPORTANT:
PLEASE READ ALL OF THIS POST BEFORE FLASHING ANYTHING TO YOUR DEVICE.
WHATEVER YOU DO BEFORE FLASHING ANYTHING MAKE A BACKUP OF YOUR DEVICE AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE, DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
Flash with ODIN using the AP slot.
1. Put your device in DOWNLOAD mode.
2. Uncheck Auto reboot.
3. Load the respective file below into the AP slot and hit start.
4. After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
Failure to implicitly comply with step 4 will result in stock recovery replacing TWRP at first boot
NOTE: Since android 5.1.1 it is necessary to enable OEM Unlock.
Settings -> Developer Options -> OEM unlocking
ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD -
Device must be running at least AQD6 or later firmware. Earlier firmware may need the previous builds:
UPDATE: 18/5/2018 TWRP 3.2.1-1
twrp_3.2.1-1_T820_28518
twrp_3.2.1-1_T825_29518
UPDATE: 8/5/2017 TWRP 3.1.0-1
twrp_3.1.0-1_sm-t820_AQD6
twrp_3.1.0-1_sm-t825_AQD6
Previous builds:
SM-T820:
https://www.androidfilehost.com/?fid=745425885120721426
SM-T825:
https://www.androidfilehost.com/?fid=673368273298945058
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then Magisk needs flashing below to disable dm-verity.
Follow the instructions below to disable dmverity, forced encryption and mount internal storage(DATA):
MARSHMALLOW AND NOUGAT ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
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 Magisk
5. Reboot
OREO ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
1. Boot to TWRP
2. Install the Forced encryption patch: Tabs3_oreo_forced encryption_disabler
3. Format DATA using the *FORMAT DATA button* under the wipe options.
(NOTE - THIS WILL WIPE ALL INTERNAL STORAGE!)
4. Install Magisk
5. Reboot and check DATA is mountable
Done.
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @suzook, @jonathonalexander, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
RESERVED
Delete
Deleted.
ashyx said:
How do you mean it bootloops? I thought you said that you were able to mount the partitions and flash supersu?
Click to expand...
Click to collapse
I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.
suzook said:
I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.
Click to expand...
Click to collapse
Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA
The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.
.
ashyx said:
Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA
The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.
.
Click to expand...
Click to collapse
Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.
suzook said:
Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.
Click to expand...
Click to collapse
Its in the first post.
ashyx said:
Its in the first post.
Click to expand...
Click to collapse
, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.
suzook said:
, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.
Click to expand...
Click to collapse
I need the recovery log after installing supersu and boot.img patcher.
ashyx said:
I need the recovery log after installing supersu and boot.img patcher.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk
suzook said:
https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk
Click to expand...
Click to collapse
Looks like Chainfires script can't find partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.
Try this, recovery log if possible please after installing.
https://www.androidfilehost.com/?fid=529152257862715887
If there is still an issue I will patch the boot image manually.
.
ashyx said:
Looks like Chainfires script can't mount partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.
Try this, recovery log if possible please after installing.
https://www.androidfilehost.com/?fid=529152257862715887
If there is still an issue I will patch the boot image manually.
.
Click to expand...
Click to collapse
Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?
suzook said:
Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?
Click to expand...
Click to collapse
Yes apply the patch after supersu to be on the safe side.
Wow, I haven't got the tab in my hands yet, and there's already recovery & root!
Have some beer: Confirmation number: 49581192XS319942M
ashyx said:
Yes apply the patch after supersu to be on the safe side.
Click to expand...
Click to collapse
Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?
suzook said:
Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?
Click to expand...
Click to collapse
Yep. Just extract it from the tar archive and then select install in twrp.
ashyx said:
Yep. Just extract it from the tar archive and then select install in twrp.
Click to expand...
Click to collapse
Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log
suzook said:
Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log
Click to expand...
Click to collapse
Damn, even defining the boot device in the command line doesn't allow named partitions to mount.
Back to the previous twrp then.
Looks like manual patching of the boot image is going to be required.
ashyx said:
Damn, even defining the boot device in the command line doesn't allow named partitions to mount.
Back to the previous twrp then.
Looks like manual patching of the boot image is going to be required.
Click to expand...
Click to collapse
Ok, sounds good. Ready to test whenever you need. I'm available rest of day, and all weekend. Thanks.
Hello everyone! In this guide I'll show you how to root ZTE's official release of Android Oreo 8.0. This is important if you wanted to upgrade (or downgrade....depending on your view) to ZTE's official release of Android 8.0 by going back to complete stock first and then installing the update zip file in stock recovery. Doing it this way fastboot does not work anymore since Nougat B32 and you do not have a custom recovery anymore, making you stuck on a rootless Android Oreo. Since there isn't a rooted TWRP flashable version of this just yet, this guide will show you how to root your Android and also become unstuck from having a stock recovery without fastboot. This could also help in unbricking with an incompatible recovery or if you accidentally flashed an official release of MiFavor or StockUI+ and the custom recovery is overwritten by stock recovery without root and fastboot.
This could also help if you have trouble with EDL drivers.
This has only been done and tested on an A2017U. If you're attempting this on another model, do so at your own risk! This guide is only for Windows 10!
This is not exactly noob friendly. This guide assumes you have ADB installed and everything.
I attempted this on my own whim. It was certainly a pain in the butt to get this to work for me as well because of EDL driver trouble. But if I managed to figure it out, you can too!
First you're gonna need to download tennear's axon7tool here. Rename is to just axon7tool so it's easier to type.
Download NFound's TWRP 3.2.1-8 for Oreo here and rename it to recovery.bin. Put it in the same directory where axon7tool is.
Download Zadig here. This is for replacing the EDL drivers to some generic ones that this tool can use to connect to your phone in EDL mode.
Download Magisk 16.2 here. Any newer Magisk version especially 17.1 causes a bootloop unfortunately so do NOT update. You can try different versions, but try at your own risk.
We need to get into "proper" EDL mode. It is not recommended to do the "shut down your phone and hold both volume buttons and power on to get into EDL mode" way. This did not work for me. In order to get into proper EDL mode, make sure you're booted into Android and make sure Android Debugging is turned on. Open ADB on your computer and type
Code:
adb reboot edl
and the phone will boot into proper EDL mode.
After your phone is booted into proper EDL mode, connect your usb cable into your phone and go into the Control Panel of Windows and go to Device Manager
In Device Manager, look for either "qualcomm usb loader 9008" or "QUSB_BULK". It doesn't really matter. Once you found it, its probably not necessary but I did it anyway, right click on it and click to uninstall. If it asks to uninstall any software then click that as well.
{
"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"
}
After it is uninstalled, unplug your phone and plug it back in. It'll probably install some drivers again but that's okay. It might reinstall as QUSB_BULK even if you had "qualcomm usb loader 9008"
It gets kinda tricky after this part, but it should work. If it doesn't, drop a comment below and I will try to help!
Open Zadig. Click on Options and then click List all devices. Look for QUSB_BULK in the drop down menu and select it.
After you've found it and selected it, you'll see on the bottom box it'll display what kind of driver it is loading. We need to replace it with WinUSB. Click on Replace Driver. After a few seconds it'll say it finished successfully. QUSB_BULK should read this now:
This means that we can now use axon7tool.
Open command prompt and navigate to where you downloaded axon7tool. In this case, it is on my desktop. Let's test to see if we have a connection. First we need to backup our recovery image, so we can test that out by typing
Code:
axon7 tool -r recovery
This will read our recovery image and back it up and put it on our directory as "backup-recovery.bin"
If you get an error that says
Code:
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
Then you need to go back into EDL mode manually again. Turn off your phone by holding power for 10 seconds and then turn it on back into Android. Once there open ADB and type again
Code:
adb reboot edl
so we can go back to proper EDL mode and try the above axon7tool command again. It should work successfully this time.
If it works, it'll backup recovery and then reboot your phone as shown below.
You'll have a backup-recovery.bin saved into your directory. Now that we know this works, we can write our TWRP recovery image!
Type
Code:
axon7tool -w recovery
and it'll successfully write and reboot as shown below.
While it reboots, go into recovery by holding Volume UP and Power, or while on the unlocked bootloader message press a volume button and select "Recovery" to get into recovery. This is to make sure that the stock rom does not overwrite our custom recovery with stock recovery
You will now be greeted with NFound's custom TWRP recovery!
Well, backup system and data in TWRP and then flash Magisk 16.2 as you would do! Wipe cache/dalvik if you want and then reboot, you should be rooted!
magisk 16.7 can use,how to pass safenet check?
zouyiqiang said:
magisk 16.7 can use,how to pass safenet check?
Click to expand...
Click to collapse
That's the thing. For me, even after factory reset oreo without root it seems like the official release of oreo does not pass safetynet
I was able to install the official B20 zip file on my A2017U, but I already had the latest official TWRP by @jcadduono, so I was able to skip the EDL steps. Yes, it can be installed from TWRP, stock recovery not required.
Steps to success and what you need:
1. TWRP (I would use official version, just download the appropriate *.img file from twrp.me
2. B20 zip (you can download it from the support page on zteusa.com)
3. Magisk 16.7 (don't try to use 17.1 or 17.2, your phone will not boot, you can get it from https://github.com/topjohnwu/Magisk/releases
Copy both of these files to external MicroSD and place it in your phone, internal storage won't work because the installer formats /data. If you don't already have TWRP installed, then use Axon 7 EDL tool to install it. Axon7Tool will also work but it needs Zadig drivers rather than the Qualcomm EDL driver. I won't go into more detail, since the steps for using these are elsewhere on the A7 subforum.
Boot into recovery. Format /system, /data, and /cache as ext4. Make sure to format /data, not just wipe, to remove encryption.
Unmount the system and persist partitions from the Mounts menu.
Then go to TWRP's terminal and do the following commands:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/boot
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/system
These will take some time to finish, so just wait. This zeros out the system and boot partitions. Doing this is necessary because B20 uses dm-verity, you will not be able to boot if the dm-verity check fails. This also ensures that you will be able to install future stock OTAs, as long as you don't modify /system in any way (or mount it as read/write from TWRP).
Select the B20 zip file and wait for it to install. Do not touch anything in the mounts menu, other than ensuring that system and persist boxes are unchecked.
Next, select the TWRP *.img and install it to the recovery partition. Don't forget to do this or you will temporarily be stuck with stock recovery! Last, reboot into recovery from TWRP. If a message comes up about mounting system, select the keep read only box (DONT MESS THIS UP!). Check the mounts menu and ensure that system and persist are still unchecked. Select the Magisk zip file and install it.
Go into TWRP terminal, type:
reboot disemmcwp
This will disable ZTE's system write protection, so that you can still modify /system from TWRP in the future if you wish (but system can still not be mounted as writeable while you are booted into Android, because of the bootstack).
If you did everything as I've posted then you should be running B20 with Magisk. I'm using it right now and the above were my steps.
AnonVendetta said:
I was able to install the official B20 zip file on my A2017U, but I already had the latest official TWRP by @jcadduono, so I was able to skip the EDL steps. Yes, it can be installed from TWRP, stock recovery not required.
Steps to success and what you need:
1. TWRP (I would use official version, just download the appropriate *.img file from twrp.me
2. B20 zip (you can download it from the support page on zteusa.com)
3. Magisk 16.7 (don't try to use 17.1 or 17.2, your phone will not boot, you can get it from https://github.com/topjohnwu/Magisk/releases
Copy both of these files to external MicroSD and place it in your phone, internal storage won't work because the installer formats /data. If you don't already have TWRP installed, then use Axon 7 EDL tool to install it. Axon7Tool will also work but it needs Zadig drivers rather than the Qualcomm EDL driver. I won't go into more detail, since the steps for using these are elsewhere on the A7 subforum.
Boot into recovery. Format /system, /data, and /cache as ext4. Make sure to format /data, not just wipe, to remove encryption.
Unmount the system and persist partitions from the Mounts menu.
Then go to TWRP's terminal and do the following commands:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/boot
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/system
These will take some time to finish, so just wait. This zeros out the system and boot partitions. Doing this is necessary because B20 uses dm-verity, you will not be able to boot if the dm-verity check fails. This also ensures that you will be able to install future stock OTAs, as long as you don't modify /system in any way (or mount it as read/write from TWRP).
Select the B20 zip file and wait for it to install. Do not touch anything in the mounts menu, other than ensuring that system and persist boxes are unchecked.
Next, select the TWRP *.img and install it to the recovery partition. Don't forget to do this or you will temporarily be stuck with stock recovery! Last, reboot into recovery from TWRP. If a message comes up about mounting system, select the keep read only box (DONT MESS THIS UP!). Check the mounts menu and ensure that system and persist are still unchecked. Select the Magisk zip file and install it.
Go into TWRP terminal, type:
reboot disemmcwp
This will disable ZTE's system write protection, so that you can still modify /system from TWRP in the future if you wish (but system can still not be mounted as writeable while you are booted into Android, because of the bootstack).
If you did everything as I've posted then you should be running B20 with Magisk. I'm using it right now and the above were my steps.
Click to expand...
Click to collapse
Do you pass safetynet this way?
Sent from my ZTE A2017U using Tapatalk
@bluenote73: No, SafetyNet check fails (according to Magisk Manager). But I also dont care about passing SN, it is so stupid. SN, Android Pay, Pokemon Go, etc, are all stupid. I dont care for Google or their apps, policies, etc. Or Magisk, for that matter. But it is the only way to root B20. Better to be rooted than unrooted. As soon as I get more free time I will be switching to an AOSP-based Oreo ROM. But I just had to try official Oreo first. Battery life is pretty good, and the near-stock look is a huge improvement over MiFavor. But it just doesnt have the level of customization that I'm used to.
AnonVendetta said:
I was able to install the official B20 zip file on my A2017U, but I already had the latest official TWRP by @jcadduono, so I was able to skip the EDL steps. Yes, it can be installed from TWRP, stock recovery not required.
Steps to success and what you need:
1. TWRP (I would use official version, just download the appropriate *.img file from twrp.me
2. B20 zip (you can download it from the support page on zteusa.com)
3. Magisk 16.7 (don't try to use 17.1 or 17.2, your phone will not boot, you can get it from https://github.com/topjohnwu/Magisk/releases
Copy both of these files to external MicroSD and place it in your phone, internal storage won't work because the installer formats /data. If you don't already have TWRP installed, then use Axon 7 EDL tool to install it. Axon7Tool will also work but it needs Zadig drivers rather than the Qualcomm EDL driver. I won't go into more detail, since the steps for using these are elsewhere on the A7 subforum.
Boot into recovery. Format /system, /data, and /cache as ext4. Make sure to format /data, not just wipe, to remove encryption.
Unmount the system and persist partitions from the Mounts menu.
Then go to TWRP's terminal and do the following commands:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/boot
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/system
These will take some time to finish, so just wait. This zeros out the system and boot partitions. Doing this is necessary because B20 uses dm-verity, you will not be able to boot if the dm-verity check fails. This also ensures that you will be able to install future stock OTAs, as long as you don't modify /system in any way (or mount it as read/write from TWRP).
Select the B20 zip file and wait for it to install. Do not touch anything in the mounts menu, other than ensuring that system and persist boxes are unchecked.
Next, select the TWRP *.img and install it to the recovery partition. Don't forget to do this or you will temporarily be stuck with stock recovery! Last, reboot into recovery from TWRP. If a message comes up about mounting system, select the keep read only box (DONT MESS THIS UP!). Check the mounts menu and ensure that system and persist are still unchecked. Select the Magisk zip file and install it.
Go into TWRP terminal, type:
reboot disemmcwp
This will disable ZTE's system write protection, so that you can still modify /system from TWRP in the future if you wish (but system can still not be mounted as writeable while you are booted into Android, because of the bootstack).
If you did everything as I've posted then you should be running B20 with Magisk. I'm using it right now and the above were my steps.
Click to expand...
Click to collapse
Internal storage 0 MB after flashing rom in twrp, how to fix that??
agnn_a said:
Internal storage 0 MB after flashing rom in twrp, how to fix that??
Click to expand...
Click to collapse
Internal storage is corrupted or encrypted. You might have to format data if you don't care about losing your data
Teet1 said:
That's the thing. For me, even after factory reset oreo without root it seems like the official release of oreo does not pass safetynet
Click to expand...
Click to collapse
Ouch. Is there no way to have magisk and root on the latest stock rom that passes safetynet? I think i'll just have to stay on my beta oreo build forever...
kgptzac said:
Ouch. Is there no way to have magisk and root on the latest stock rom that passes safetynet? I think i'll just have to stay on my beta oreo build forever...
Click to expand...
Click to collapse
Is it possible to use the same method we using in the Pie GSI thread?
Install MagiskHide Props Config module and reboot
Install Termux app if you don't have it
Run Termux, in terminal type su
Grant root privileges to Termux
Then type props to run the Props config module
Choose 1 to edit device fingerprint
Choose f to pick certified fingerprint
Choose ZTE, then choose Axon
Then choose Yes you're sure and yes to reboot
Hopefully this solves the safetynet issues for those of you on stock too.
Teet1 said:
Internal storage is corrupted or encrypted. You might have to format data if you don't care about losing your data
Click to expand...
Click to collapse
my phone ask me password bro?
kgptzac said:
Ouch. Is there no way to have magisk and root on the latest stock rom that passes safetynet? I think i'll just have to stay on my beta oreo build forever...
Click to expand...
Click to collapse
EBeatFLA said:
Is it possible to use the same method we using in the Pie GSI thread?
Install MagiskHide Props Config module and reboot
Install Termux app if you don't have it
Run Termux, in terminal type su
Grant root privileges to Termux
Then type props to run the Props config module
Choose 1 to edit device fingerprint
Choose f to pick certified fingerprint
Choose ZTE, then choose Axon
Then choose Yes you're sure and yes to reboot
Hopefully this solves the safetynet issues for those of you on stock too.
Click to expand...
Click to collapse
This method should work but use the MagiskHidePropsConf v2.4.0 version as it is compatible for magisks lower then 17.1. From v2.4.1 it's compatible with 17.1+.
Use Termux or Terminal Emulator to run the module as mentioned above.
Let us know if you succeeded this way
agnn_a said:
my phone ask me password bro?
Click to expand...
Click to collapse
If it asks for password and you enter the one you made but says it's wrong or you don't know it you need to format data
To a T...
I'VE TRIED EVERYTHING, YET THIS IS THE OUTCOME! URGH....!!!
C:\Users\wiels_xpspro\Downloads>axon7tool -w recovery
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Writing recovery ...
F: failed to open recovery.bin
terminate called after throwing an instance of 'std::runtime_error'
what(): error: No error
---------- Post added at 07:22 AM ---------- Previous post was at 07:08 AM ----------
This is just to show the -r recovery worked, but the -w did not...
C:\Users\wiels_xpspro\Downloads>axon7tool -r recovery
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Reading recovery ...
Success!
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...
C:\Users\wiels_xpspro\Downloads>axon7tool -w recovery
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Writing recovery ...
F: failed to open recovery.bin
terminate called after throwing an instance of 'std::runtime_error'
what(): error: No error
@wielluk: Try using @djkuz's Axon 7 EDL Tool to flash TWRP. I have found it to be more reliable than Axon7Tool. Afterwards, you can follow the instructions from my post and you're set to boot up stock Oreo.
Hope that helped!
wielluk said:
I'VE TRIED EVERYTHING, YET THIS IS THE OUTCOME! URGH....!!!
C:\Users\wiels_xpspro\Downloads>axon7tool -w recovery
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Writing recovery ...
F: failed to open recovery.bin
terminate called after throwing an instance of 'std::runtime_error'
what(): error: No error
---------- Post added at 07:22 AM ---------- Previous post was at 07:08 AM ----------
This is just to show the -r recovery worked, but the -w did not...
C:\Users\wiels_xpspro\Downloads>axon7tool -r recovery
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Reading recovery ...
Success!
Reset in 5 seconds ...
Reset in 4 seconds ...
Reset in 3 seconds ...
Reset in 2 seconds ...
Reset in 1 seconds ...
C:\Users\wiels_xpspro\Downloads>axon7tool -w recovery
Connecting to device...
Sending programmer...
Connecting to programmer...
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
log: Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke getnumdisksectors
Writing recovery ...
F: failed to open recovery.bin
terminate called after throwing an instance of 'std::runtime_error'
what(): error: No error
Click to expand...
Click to collapse
I get the same error looking to root an existing Oreo install (unlocked), but with stock recovery. Stock Recovery backed up OK, but does not accept the TWRP Recovery. The other tool asks for Android 6 or 7 so I have not attempted it. Any other ideas? Thanks
[deleted]
RockCityGeek said:
After I type props, it says it's not found.
Click to expand...
Click to collapse
Replied to you in Liquid thread.. no need to double post.
People.....stop bothering with Axon 7 Tool, use Axon 7 EDL Tool instead. TWRP will flash just fine with that. A7 Tool is very finicky, and it replaces the Qualcomm EDL drivers with Zadig drivers, which means you cant also use MiFlash or A7 EDL Tool.
EBeatFLA said:
Replied to you in Liquid thread.. no need to double post.
Click to expand...
Click to collapse
Sorry, I thought my post disappeared. I didn't realize I posted it in this thread.
How to Install TWRP:
Note: that version is UNOFFICIAL TWRP-3.3.0-0524
.Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here https://devsjournal.com/usb-drivers-...d-devices.html
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here https://devsjournal.com/download-min...boot-tool.html
Pre-Requisite 3
Your device needs this with unlocked bootloader
if it is not unlocked do the tutorial to unlock HERE
Pre-Requisite 4
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
------------------------------------------------
1) Download TWRP: recovery-TWRP-3.3.0-0524-LENOVO_Z5PRO_GT-CN-wzsx150.img
2) After getting the TWRP file put it in the same ADB folder
3) Now start the phone in bootlader by doing this:
Connect the phone to the PC
Start the Minimal ADB & Fastboot program from the PC
On the PC screen, type:
adb reboot bootloader
(A request may appear on the phone screen with permission of USB debugging, accept it)
The phone will now restart in Bootloader mode.
4) Now that you are in bootloader mode, from the PC, from the screen
Minimal ADB and Fastboot type:
fastboot flash recovery recovery-TWRP-3.3.0-0524-LENOVO_Z5PRO_GT-CN-wzsx150.img
Sending 'recovery' (98304 KB) OKAY [ 5.970s]
Writing 'recovery' OKAY [ 0.539s]
Done !
---------
.How to Install Root Magisk:
{
"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"
}
Done !
Credits:
Maker: wzsx150
Developer Team: LR.Team
Is there any issues related to this recovery?
firemax13 said:
Is there any issues related to this recovery?
Click to expand...
Click to collapse
I had no problem with this recovery
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
BlueIce84 said:
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
Click to expand...
Click to collapse
Have the same scenario as you but I haven't done the tutorial yet as I read your post and I got concerned. Have you fix you issue? Is it safe to do this tutorial?
No solution so far. No twrp and no root
Now I have flashed the original rom with ZUI 10. Works well and updated to ZUI 11.
luigi0824 said:
Have the same scenario as you but I haven't done the tutorial yet as I read your post and I got concerned. Have you fix you issue? Is it safe to do this tutorial?
Click to expand...
Click to collapse
I've read somewhere that you need to flash vbmeta.img if verified boot is enabled, however I couldn't find the correct img to flash anywhere. Maybe if we ask someone that has the phone already rooted.
Can anyone post wzsx150's newest TWRP 3.3.1 from October 4? It's in this thread but the download link is for registered users only. I can't sign up for a Club Lenovo account.
BlueIce84 said:
No solution so far. No twrp and no root
Now I have flashed the original rom with ZUI 10. Works well and updated to ZUI 11.
Click to expand...
Click to collapse
What method would you follow to install the stock rom, like you, it comes with the bootloader unlocked by the seller and I don't know how to flash stock rom
Use this guide:
https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
carlshark said:
Can anyone post wzsx150's newest TWRP 3.3.1 from October 4? It's in this thread but the download link is for registered users only. I can't sign up for a Club Lenovo account.
Click to expand...
Click to collapse
I gave up on clublenovo. They require SMS authentication to post so even when you log in you can't post and download. TWRP 3.3.1 is also available from 4PDA. That's what I used.
I was able to flash the TWRP 3.3.1 but i cant root nor i cant flash anything as the folders inside the sdcard directory is showing in weird names
luigi0824 said:
I was able to flash the TWRP 3.3.1 but i cant root nor i cant flash anything as the folders inside the sdcard directory is showing in weird names
Click to expand...
Click to collapse
You need to decrypt the internal storage.
normally this is done by entering to ping code to unlock the phone in TWRP on start up.
thorvall said:
You need to decrypt the internal storage.
normally this is done by entering to ping code to unlock the phone in TWRP on start up.
Click to expand...
Click to collapse
Will I lose any data if I decrypt my phone? And where do I find that pin code?
luigi0824 said:
Will I lose any data if I decrypt my phone? And where do I find that pin code?
Click to expand...
Click to collapse
Its the pin code you use to open the phone.
And enabling does not remove data, but it does give twrp read/write permission
Is it possible to implement support for OTA updates through TWRP?
BlueIce84 said:
My device was unlocked by vendor. I'm unable to boot into twrp to root my device. The flashing is successful but it will only boot in a simple recovery where I can only install an "update.zip".
Have tried this https://forum.xda-developers.com/z5...-guide-lenovo-z5-pro-gt-t3915945#post81055547 but the problem remains.
Hope anyone can help. I need to root my device. Thanks
Click to expand...
Click to collapse
i had the same issue and discover a solution
1) you have to manually go to your phone after you finish the flash below. DO NOT cmd fastboot reboot as it will flash stock
recovery
a) fastboot flash recovery twrp.img ( i rename the tweak recovery file to twrp.img)
b) http://4pda.ru/forum/index.php?showtopic=973179&st=0
(tweak recovery version 3.31)
2) after flash quickly go to your phone fastboot mode ( reminder again: do not tyoe fastboot reboot after flash successful appear in cmd)
3) manually select recovery , select english then select reboot and TWRP will appear
issues
1) i cannot manually tweak recovery via phone ( power +volume down ) as stock recovery will appear again.
A) so you need to go your PC to redo flash recovery again
B) i did a back up and redo PC flassh recovery again and mine files are stored successful
c) there is no install root in TWRP
D) about backup...
.best to back up via OTA-USB. pixel GCI crash ( QUALCOMM CRASH DUMP MODE ) my phone and my restore
file was missing as TWRP rename the restore file. spent one hour it so decide to do stock rom
current
a) I have not flash any rom yet and my original ANTUTU benchmark hovers around 300000 to 350000 based on vendor custom global rom
b) my phone model is 8gb 128gb android version 9 and lenovo version 11.0.084
c) updatess and NFC not supported
d) i opt not too root
e) bootloader still unlock
REQUEST...
would appreciate a ROM recommendation
a) have anyone flash a rom (not china stock rom) wirh an antutu beachmark abve 400000 ?
from a novice... after 2 weeks i can finally flash tweak recovery from the phonE.
about flashing stock rom..
i opt for stock rom and my antutu hovers around 409000 to 418000. from LENOVO app centre you can install play store
butterx2341 said:
i had the same issue and discover a solution
1) you have to manually go to your phone after you finish the flash below. DO NOT cmd fastboot reboot as it will flash stock
recovery
a) fastboot flash recovery twrp.img ( i rename the tweak recovery file to twrp.img)
b) http://4pda.ru/forum/index.php?showtopic=973179&st=0
(tweak recovery version 3.31)
2) after flash quickly go to your phone fastboot mode ( reminder again: do not tyoe fastboot reboot after flash successful appear in cmd)
3) manually select recovery , select english then select reboot and TWRP will appear
issues
1) i cannot manually tweak recovery via phone ( power +volume down ) as stock recovery will appear again.
A) so you need to go your PC to redo flash recovery again
B) i did a back up and redo PC flassh recovery again and mine files are stored successful
c) there is no install root in TWRP
D) about backup...
.best to back up via OTA-USB. pixel GCI crash ( QUALCOMM CRASH DUMP MODE ) my phone and my restore
file was missing as TWRP rename the restore file. spent one hour it so decide to do stock rom
current
a) I have not flash any rom yet and my original ANTUTU benchmark hovers around 300000 to 350000 based on vendor custom global rom
b) my phone model is 8gb 128gb android version 9 and lenovo version 11.0.084
c) updatess and NFC not supported
d) i opt not too root
e) bootloader still unlock
REQUEST...
would appreciate a ROM recommendation
a) have anyone flash a rom (not china stock rom) wirh an antutu beachmark abve 400000 ?
from a novice... after 2 weeks i can finally flash tweak recovery from the phonE.
about flashing stock rom..
i opt for stock rom and my antutu hovers around 409000 to 418000. from LENOVO app centre you can install play store
Click to expand...
Click to collapse
If you boot your ZUI system, your twrp will be overwritten by a stock recovery.
However if you flash magisk, your twrp won't be overwritten anymore. If you want to preserve your twrp after rebooting on ZUI, you need to flash magisk.
whatever I do.. the twrp wont be installed (let alone the root/magisk). ADB does say the twrp is flashed... but it will always boot to or the bootloader.. or the system (not the lenovo recovery or twrp recovery). Quiet frustrating... what can I do? Want this boy rooted!
Edit: done. The twrp linked in the tutorial is not correct use this one: https://drive.google.com/file/d/13mt0RLmT83BHSUBpH-J7EhaeZQ-MPYUu/view
That worked!
I want to unlock my bootloader but the site where you request the image file for unlocking it wont accept my IMEI1.. any idea guys?
{
"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 20 & Note 20 UltraOnly for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
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:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
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 (magisk patched) 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 (magisk patched) 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/13100000.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 - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.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:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
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
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 or Rollback protection might 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.
Thanks for this. Where is twrp.img for Note 20 Ultra 5G / N986B
Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards
Thanks, for this I'll keep for more year Note 20 Ultra. Time to wait or maybe make GSI for Note.
Yaayyyy
I m newbie to note 20 ultra...i want to flash root and twrp... What steps shld i follow.... Currently i m on stock non rooted.. Confused what to flash via odin..
@corsicanu
Many thanks for the latest update mate. It's working perfectly, as everything from you does
corsicanu said:
Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
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
Background on Android Verified Boot
Rollback protection
Click to expand...
Click to collapse
I notice I have bootloder on my device that I didn't install my self. I'm just a average user and have no clue how this was put on my phone. Also all of my apps are older versions an I'm unable to update them. I need help figuring out what's going on. Anyone please help!!!
@corsicanu
Many thanks for the latest update mate
1. Can I use this TWRP version with any custom ROM (e.g. Dr. Ketan ROM)?
2. Do I have to flash vbmeta.img, even when I have that custom ROM?
3. Is there a twrp.img for N986B that supports Android encryption, since right now encryption is somehow disabled after installing Dr. Ketan ROM: the lockscreen password has no effect and I can access and read all files on all partitions with the TWRP file manager !
monicaONxda said:
1. Can I use this TWRP version with any custom ROM (e.g. Dr. Ketan ROM)?
2. Do I have to flash vbmeta.img, even when I have that custom ROM?
3. Is there a twrp.img for N986B that supports Android encryption, since right now encryption is somehow disabled after installing Dr. Ketan ROM: the lockscreen password has no effect and I can access and read all files on all partitions with the TWRP file manager !
Click to expand...
Click to collapse
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
corsicanu said:
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
Click to expand...
Click to collapse
Where's 2.8
corsicanu said:
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
Click to expand...
Click to collapse
Many Thanks!
Re. 3.: With "fw" you meant FRP? But when I have root I can simply erase FRP and most Knox and other unwanted bloatware apks on /system, /product, /prism etc. ?
Btw. do you know if there is there a possibility to completely remove the Samsung ROM and replace it with a plain Android? You may lose one hardware driver for the "Sasmung Pen" but everthying else should work..?
monicaONxda said:
Many Thanks!
Re. 3.: With "fw" you meant FRP? But when I have root I can simply erase FRP and most Knox and other unwanted bloatware apks on /system, /product, /prism etc. ?
Btw. do you know if there is there a possibility to completely remove the Samsung ROM and replace it with a plain Android? You may lose one hardware driver for the "Sasmung Pen" but everthying else should work..?
Click to expand...
Click to collapse
Fw as in firmware. Regarding plain android - search for AOSP based projects, i'm not aware of the active developement so i can't properly advice you in this matter.
Regards
corsicanu said:
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 UltraOnly for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
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:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
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 (magisk patched) 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 (magisk patched) 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/13100000.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 - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.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
Click to expand...
Click to collapse
i am trying to root my note 20 u device. when all succesfully start from magisk module and twrp, i find the screen flicker for a second every 15 seconds. I'm trying to figure out which app the problem is from. looked in screen recorder and found the problem. apparently from system ui. then start again from the initial step one by one. and the cause of the problem is after installing twrp. I'm on Ui5.1 N986B exyns. i feel twrp has a bug
Now im use back stock recovery and problem has gone
Hi it's been a while since I last install TWRP on SS phone, it got complicated now I have few question, can you help answering?
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
Click to expand...
Click to collapse
- For this, do I have to press the key combo 1 time only after clicking Start Odin or I have to hold till the progress done?
2.
!! 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.
Click to expand...
Click to collapse
- I never install TWRP on my phone, do I have to follow this step?
-If yes, do I have to install that file right after TWRP first boot (when odin completed flashing)
And finally, does it support android 13?
Thank you so much