Database Users

[HOW-TO][ROOT][Unlock BL] Sony Xperia Z3 Tablet Compact

/*
* Your warranty is (probably) now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about rooting
* 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.
* PLEASE READ THE ENTIRE THREAD BEFORE YOU DO ANYTHING!
*/
Please leave a reply if this worked or didn't work. I will be most grateful! Thanks
Hi there!
I present the best, the easiest (mm maybe not) and most proper way to root and flash a custom ROM on your Sony Xperia Z3 Tablet Compact!
Requirements:
- A basic understanding of Rooting and Android Development
- ADB and Fastboot (Have a google for Minimal ADB And Fastboot)
- A windows PC (I am not sure how to root with mac, although I am sure it is the same process)
- OEM Unlocking Enabled on your Device.
Don't know how to enable OEM Unlocking? Do this:
Settings -> About Device -> Tap Build Number 7 Times - Back -> Developer Options -> OEM Unlocking -> Enable
Also, if you ever get a message saying: Allow USB Debugging, do this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We'll start with Unlocking your Boot loader. I might as well point out that this will remove ***ALL*** of your apps and files etc. I should also say that you will lose some capability features - such as the Camera may not be as good - although to be perfectly honest I haven't noticed any changes!
Lets start right away: Bootloader
What is your Bootloader?
Your bootloader is a part of your android device that when unlocked, allows you to do lots of things with it! This includes rooting (Like we are now :laugh, flashing recoveries and more.
Is it safe to do this?
As long as you follow my steps, you should be ok. But I have warned you.
Now head to here. This is the official Bootloader unlocking page. Scroll down to the device selection and put in "Z3 Tablet Compact"
Connect your tablet to your compter,
Do the steps it asks and... done!
Congratulations, your Bootloader is Unlocked!
It may seem silly, but for me, this is the only Hard part!
Now let's flash our TWRP!
Before you do this, make sure you have booted after unlocking your Bootloader. I dont know if it will make a huge difference, but I did it, so you should as well. It worked for me like that
What is TWRP
TWRP is a Custom Recovery
Wow, helpful. :laugh: What's a custom recovery?
As android central say:
In Android, recovery refers to the dedicated, bootable partition that has the recovery console installed. A combination of key presses (or instructions from a command line) will boot your phone to recovery, where you can find tools to help repair (recover) your installation as well as install official OS updates.
This means it is a way of changing things that you can't change if you are booted into System (System is Usual Home screen etc...)
Is TWRP Safe?
It's only ever as safe as you are! - Just make sure you flash (install) the right version!
We start by flashing TWRP.
Head to http://twrp.me and click on Devices. Find specifically YOUR version if the Tablet (scorpion_windy is the NON-LTE Version).
Download it.
Drag that file into an empty folder. Then in the address bar, type "cmd"
A black window should pop up.
In this window, type: adb devices
This should display your device.
Now type: adb reboot bootloader
You should now have a blue light on your device.
You cannot perform adb commands anymore! You now are in Fastboot mode. I dont need to explain that, but you need to know that!
Now type: fastboot flash boot twrp-xxxx-scorpion(_windy).img
Congratulations, TWRP Recovery is now Flashed!
(Provided it says everything is ok. )
Our last step is rooting This is an easy task, but requires TWRP - hence why we installed it.
Grab the latest copy of SuperSU from supersu.com - make sure you get the XPERIA SuperSu - and boot into twrp. (Booting into twrp can be done by mashing volume keys after holding down the power key and it vibrates haha). Press install and find your copy of SuperSU (which you should have loaded onto your tablet beforehand). Swipe to flash, and done!
If your tablet bootloops (doesn't turn on), Install a custom rom. I am currently using: this unofficial lineage (14.1).
To do this, boot into TWRP and press install. Find your Rom file (Like you did for Rooting) and swipe to flash. (Make sure you wipe data, system, cache and dalvik beforehand!). You can now reflash your SuperSU Zip and bam, rooted.
You may also want GApps (Google Apps). So head to opengapps.org and select the right package for you. When you flash GApps, make sure you do right after you flashed the rom (dont boot after flashing your rom.)
When I am flashing something I will normally do this:
TWRP -> Wipe -> Advanced Wipe -> System, Cache, Data, Dalvik Cache -> Back -> Install -> ROM -> Add more Zips -> GApps -> SuperSU -> Back -> Reboot -> Reboot system.
Hopefully, you should now be rooted with a custom rom and all. Enjoy!
I should point out that (At the time of writing this) I am only 12 years old. If I have made a few mistakes, please correct me! Thank you

MajorPlayz said:
Now type: fastboot flash boot twrp-xxxx-scorpion(_windy).img
Click to expand...
Click to collapse
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel.​...so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.

XperienceD said:
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel.
...so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.
Click to expand...
Click to collapse
Well actually I did fastboot flash boot twrp.img
This works perfectly fine for me

XperienceD said:
That should be fastboot flash recovery twrp-xxxx-scorpion(_windy).img. As this is the most recent guide I'll post this here, yesterday I decided to wipe my tablet and it turned into a real pita, flashing the recovery partition flashed ok would was real problematic trying to get it to to boot for some reason and in trying to get it to boot I was flashing numerous different files to the phone, but as hate I doing things that way I soldiered on trying to find the cleanest solution and eventually managed it.
These are the steps that I used, my BL is already unlocked...
1. Full clean install of 291.
2. Run my stock kernel through PoC and Rootkernel.
3. Used Rootkernel to add SuperSU and TWRP to the kernel.
...so now I have a rooted stock 291 with TWRP 3.0.2-0 and my DRM keys intact. To enter TWRP I start pressing the vol+ repeatedly when a yellowish light appears.
Click to expand...
Click to collapse
What's 291 sorry?

MajorPlayz said:
Well actually I did fastboot flash boot twrp.img
This works perfectly fine for me
Click to expand...
Click to collapse
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
MajorPlayz said:
What's 291 sorry?
Click to expand...
Click to collapse
The FW version.

XperienceD said:
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
The FW version.
Click to expand...
Click to collapse
Ok cool

XperienceD said:
Interesting, might have one last try then, strange though that it uses the same command as flashing the kernel.
The FW version.
Click to expand...
Click to collapse
I may be mistaken though, so if it bricks the device, use Sony's Emma flash tool
It's a pretty useful tool (if you don't have just Google: Sony Emma)

MajorPlayz said:
I may be mistaken though
Click to expand...
Click to collapse
Just tried it on the off chance it might work but doesn't, it just writes the recovery to the boot partition so will only boot to TWRP, just flashed the recovery partition again and now not getting any light. It's a strange one this, going to stick my method.

XperienceD said:
Just tried it on the off chance it might work but doesn't, it just writes the recovery to the boot partition so will only boot to TWRP, just flashed the recovery partition again and now not getting any light. It's a strange one this, going to stick my method.
Click to expand...
Click to collapse
Weird ?
I'm using the SGP612 So there might be a difference? I'm assuming your using 621 (You mentioned PoC)
My friend did the command but he told me that is what it was. I'll grab the full list of commands from him, but flashing twrp was definitely to boot!
Nevermind haha!

MajorPlayz said:
Weird
I'm using the SGP612 So there might be a difference? I'm assuming your using 621 (You mentioned PoC)
Click to expand...
Click to collapse
SGP611, I just don't get it.

XperienceD said:
SGP611, I just don't get it.
Click to expand...
Click to collapse
Weird

For those with any trouble and that can't flash twrp, a full procedure for injecting TWRP into the kernel is here:
https://forum.xda-developers.com/showpost.php?p=74528751&postcount=22

Just out of curiosity, about how much battery power does it take to flash the custom ROM to solve the bootloop problem (which happened to me) and are there any other ways of flashing a custom ROM that do not consume battery power?

Ishtvan said:
Just out of curiosity, about how much battery power does it take to flash the custom ROM to solve the bootloop problem (which happened to me) and are there any other ways of flashing a custom ROM that do not consume battery power?
Click to expand...
Click to collapse
Hi there, sorry for long reply - I've been inactive for quite a while as I didn't have a device to hack with. My tablet unfortunately died!
Anything done on a device, whether it be playing games, streaming media, or using TWRP Recovery will consume Battery.
The un-bootloop problem will take charge from your device, but it is safe to keep the device plugged in, charging, whilst you perform the commands.
If all else fails, use Emma as I mentioned before.

hi,
Following this "how-to" everything fine till end of bootloader unlock.
going under developper option, and can't find OEM unlock
trying to make :
Code:
fastboot flash boot twrp-3.0.2-0-scorpion_windy.img
[sudo] Mot de passe de youb*:*
target didn't report max-download-size
sending 'boot' (12372 KB)...
OKAY [ 0.410s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.413s
Trying under linux and then window 7, same error
I ticked usb debug and paired with my laptop.
don't know what to do now ( I'm under firm 23.5.A.1.291)
edit:
ok working, reflash same firmware (us version) and then flash this kernel
glimmling said:
Hi,
I made a boot.img for the SGP612 [6.0.1] [23.5.A.1.291] unlocked BL.
Sony RIC disabled
TWRP 3.0.2
(DRM fix)
Root and Xposed is NOT included. I recommend flashing Magisk v12 later in TWRP and enable Magisk Core Only Mode and Magisk Hide in the settings. Then it will pass the SafetyNet test and you can use su.
To flash the boot.img, put your SGP612 into fastboot mode (Volume Up + connect USB) and then run:
Code:
fastboot flash boot boot.img
If you have a backup of your TA partition, before you unlocked, see the rootkernel thread by tobias.waldvogel, how the DRM fix works.
Thanks to codfx for give me the idea for a SGP612 counterpart and to tobias.waldvogel for his tool :good:
Click to expand...
Click to collapse
from https://forum.xda-developers.com/z3-tablet-compact/development/kernel-t3472019/page2

hazote said:
hi,
Following this "how-to" everything fine till end of bootloader unlock....
Click to expand...
Click to collapse
Where you able to get this working?
Sorry for the very late reply.

Here you find some more details incl. Magisk root instructions: https://forum.xda-developers.com/showpost.php?p=78588234&postcount=14

Hello, i hope people will be able to help me, i've been stupid and tried rooting my tablet without the necessary knowledge , from what i understood i flashed twrp on boot instead of recovery and now i can't use my tablet at all.
Is there a way to get the old system back ?

lacarte said:
Hello, i hope people will be able to help me, i've been stupid and tried rooting my tablet without the necessary knowledge , from what i understood i flashed twrp on boot instead of recovery and now i can't use my tablet at all.
Is there a way to get the old system back ?
Click to expand...
Click to collapse
Have you tried Flashtool: http://www.flashtool.net/index.php ?

[TWRP & ROOT] Ticwatch E/S & Unroot Instructions for Updates - v003

{
"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"
}
DISCLAIMER:
I'm not responsible for any damaged watches or other broken things! All of this is still heavily in development and mainly a developer release, not at all recommended for normal usage!
The following tutorial CAN brick your watch if you're not careful enough! Once again I'm not taking any responsibility!
This has only been tested on Android N so far, Android O is not yet fully tested!​
---------------------------------------------------------
Please read before doing anything:
This is a port of TWRP for the Ticwatch E. Currently we're not able to boot it via fastboot (well, it technically does but there's an issue with the video driver) and when trying to flash it the watch will instantly flash the stock recovery over it upon reboot.
To avoid this we have to do a little workaround! Once you reboot your watch it'll restore the stock recovery again! After following these steps your watch will be stuck in a bootloop which we'll fix too tho.
Please keep the Changelog below in mind and read what's working and what's not before asking. We may or may not have seen this issue before already.
Files you'll need:
v003 of "TWRP for Ticwatch E" (and most likely S) - OneDrive Mirror
Stock Recovery for Ticwatch E (and most likely S) - OneDrive Mirror
ADB and Fastboot drivers installed (I recommend "15 Seconds ADB Installer")
Changelog:
Updated Instructions:
Slightly updated the instructions so you won't lose any data if you're already on an bootloader unlocked watch!
v003 (OneDrive Mirror):
Managed to make TWRP persistent! Check Instructions on how to.
v002 (OneDrive Mirror):
Now includes systemless root package inside the TWRP image so you're able to root your watch!
v001 (OneDrive Mirror):
Initial release, no ADB so far. Can't be booted from fastboot directly either due to weird fastboot behavior and has to be flashed first. However upon normal reboot Mobvoi decided to flash over the stock recovery again so we have to do a workaround.
Instructions:
The new Instructions by Luxios require a few less steps AND if you've already unlocked your watch before you won't even lose data!
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you [font=Verdana, Arial, Helvetica, sans-serif]can skip this[/font])
Follow the on-screen instructions on your watch to unlock it (if you already have an unlocked bootloader you can skip this)
Reboot via "fastboot reboot" and wait until Android Wear fully starts up
One started reboot to the bootloader via the same command as above
Once the bootloader shows up again type "fastboot flash recovery TWRP_TicwatchE_v003.img"
After that type "fastboot oem reboot-recovery" to reboot to the TWRP recovery
In order to make TWRP persistent you need to go to "Install" > "Install ZIP" > "supersu" > "TicwatchE_TWRP_keeper.zip" and flash it
Upon rebooting you may notice it'll get stuck in an infinite TWRP bootloop. To fix this boot into TWRP, then choose "Reboot" > "Bootloader", back in fastboot type "fastboot boot StockRecovery_TicwatchE.img" and wait a few seconds, a few reboots later Android Wear should start right up again.
If you want to root your watch reboot it once again with "adb reboot recovery" and go to the same folder as above, tho this time flash "SuperSU-2.79-wear_systemless.zip"
Unroot/Remove TWRP for Android O Update:
Go to this thread to also update directly to the last Android O update and revert all customizations: https://forum.xda-developers.com/sm...es/android-o-super-easy-ticwatch-e-s-t3789835
Have fun!

You're the best! I'm gonna try as soon as I can, and let you know.

Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?

Piereligio said:
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Click to expand...
Click to collapse
If your bootloader is (or was) already unlocked you have to lock and then unlock it again for it to work.

Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.

Piereligio said:
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Click to expand...
Click to collapse
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.

Sadly it looks like SuperSU failed to root. It gave a data partition mounting error at the end of the script, don't know if it is normal. TWRP isn't able to mount data either.
EDIT: Looks like I found a way to boot TWRP without having to lock/unlock bootloader.
Doing this, I managed to boot TWRP after setting the watch up, and in this way, it didn't fail to mount /data. Let's see...
EDIT2: now SuperSU still fails, but for a different reason. I'm gonna ensure that it failed though.
EDIT3: su command responded, so seems that root works. I'll do some more tests.

TWRP is now persistent! Check the updated guide

Rooting succeeded!
Seems like I managed to root the smartwatch using the version 2. For the moment I'm happy like this, next times I'll indeed use new procedures.
EDIT: Yes, I rooted it.
My steps (the ones on OP are the recommended ones):
-Bootloader unlock;
-Boot in Android Wear to enable ADB from Settings;
-Reboot in bootloader with "adb reboot bootloader";
-Flashed this TWRP v2;
-"fastboot reboot", then "adb reboot recovery" as soon as adb was detected while booting.
In this way I managed to avoid the system to flash stock recovery over TWRP.
By the way, I don't recommend my way of rooting it, it's less safe, just follow the updated instructions in OP.
Huge thanks to @EpicLPer

Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.

BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.

BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
You can flash again the stock recovery with spflash tool.

EpicLPer said:
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
Click to expand...
Click to collapse
I really wish I knew what. All I did was flash a bad recovery, pretty sure something was was wrong with the ram disk. All I get is the splash logo for 3 seconds and a brief vibrate.
Luxios said:
You can flash again the stock recovery with spflash tool.
Click to expand...
Click to collapse
I think I need a scatter file to even get started. I've never used the tool so any other instructions would be greatly appreciated.

Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?

elios93 said:
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
Click to expand...
Click to collapse
I have the same problem...
EDIT: I have a Ticwatch S.

Niktendo said:
I have the same problem...
EDIT: I have a Ticwatch S.
Click to expand...
Click to collapse
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!

elios93 said:
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
Click to expand...
Click to collapse
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)

EpicLPer said:
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Click to expand...
Click to collapse
Can you get me the device tree or at least BoardConfig.mk used for this? I have a working watch (still working on recovering the old one) and I think I can get the rest of the partitions working but I would really like to avoid any more mistakes.
Luxios said:
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
Click to expand...
Click to collapse
That 'fastboot oem reboot-recovery' command sure is a nice find!

Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol

hassanabid94 said:
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
Click to expand...
Click to collapse
Maybe it's a specific developer unit. Don't do anything with it yet, we could loom further into this if it is something special.

[ROM][STABLE] LineageOS 18.0 [MI A3] [laurel_sprout]

{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS 18.0 based on Android 11.0
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
WHATS WORKING :-
- RIL
- WiFi
- Bluetooth.
- Camera
- Audio
- Sensors
- Flash
- GPS
- VoLTE
- FOD (Fingerprint on display)
- Face unlock.
- DT2W.
- Proximity in calls.
- FBE.
WHAT DOESN'T :-
- You tell.
HOW TO FLASH :-
1) Download ROM zip and Gapps (optional).
2) Reboot to Recovery.
3) Wipe Data, System, Cache.
4) Format data. (It might work without this too but its recommended to format data to boot successfully. If stuck on splash or boot animation or reboots back to fastboot or recovery, format data)
5) Flash ROM + Recovery installer (any as per your choice).
6) Reboot to Recovery.
7) Wipe cache.
8) Reboot and enjoy.
IMPORTANT INSTRUCTIONS :-
- The build is based on OSS vendor. Firmware is included in the ROM zip. No need to flash any firmware.
- Fingerprint works fine with no flicker. (Accuracy is improved.)
- Face unlock works.
DOWNLOADS :-
ROM :- LineageOS 18.0
GAPPS :- GAPPS (optional)
DONATION LINKS :-
PLEASE DONATE ME IF YOU LIKE MY WORK
PayTM : [email protected]
Paypal : http://paypal.me/pms2299
GPay : [email protected]
I can't build continuously on my laptop and I need a server to build. Consider donating for continuous support. I will be able to provide bug fixes sooner if I get a server. Please donate if you can. Thanks
SUPPORT GROUP :-
LineageOS Support group :- Telegram
SOURCES :-
KERNEL
XDA:DevDB Information
LineageOS, ROM for the Xiaomi Mi A3
Contributors
PrathameshMS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 18.0
Stable Release Date: 2020-10-10
Created 2020-10-10
Last Updated 2020-10-10

Thank you so much

Great, and I mean, GREAT job!!
As usual....
Thank you for your hard work.

You're my [email protected]|<ing idol!
Starting download rigth now

So it is based on Android 11 or 10?

r3pairer said:
So it is based on Android 11 or 10?
Click to expand...
Click to collapse
It's based on 11

Can it be used daily?

i dont know is it only me or not
when im in a call (in discord or any other apps) others say that they can hear my phone sound like instagram or any other thing
i have this problem with any other roms so as lineage
please fix it thanks i realy want to use android 11

Great work. Fod is better than stock to recognize my finger, it has just a small and quickly brightness flickering but is almost unnoticeable.
SElinux is permissive and FM radio is missing but they aren't a big issues for me.
Thanks for this rom.

Hi! Does LOS18 supports signature spoofing? Thanks!

Step by step install procedure for LOS18
1 - Turn your phone into fastboot mode (run adb reboot bootloader or shutdown the phone and turn it on again while pressing Power + Vol- keys)
2 - On fastboot mode set a as the active slot by running the command:
Code:
fastboot set_active a
3 - Now, flash latest STOCK FASTBOOT ROM using flash_all.bat (or flash_all.sh if you're using Linux)
4 - Wait for the installation to finish and, after seeing the welcome screen, go to fastboot mode again
5 - Now run these commands:
Code:
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
(keep pressing Vol+ key to force the phone into recovery mode)​
6 - We're on TWRP Recovery using slot B. Do this:
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip
Reboot to Recovery
Format Data with "yes"
Install lineage ROM zip
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip (yes, again...)
Reboot to Recovery​
7 - Now we're on TWRP Recovery using slot A. Do this:
Install NikGApps Core version. (This is optional! The ROM works fine without any GApps but if you want them, use CORE version!)
Install Magisk (This is also optional! The ROM works fine without it but if you want it, get the MagiskR zip you'll find on the telegram support group!)
Reboot to fastboot and run:
Code:
fastboot flash dtbo dtbo.img
Code:
fastboot reboot
Your device will now reboot to System and you may enjoy LineageOS 18!​
NOTES:
By doing this procedure you will have LineageOS 18 system installed only on slot A!
If your device fails to boot, you should just start all over again! Trust me, it's easier than trying other flashing methods.
You can now install a different Recovery if you like, for example, SHRP Recovery. Simply go to TWRP and flash SHRP installer zip.
You can, also, install a different Kernel. Check the Telegram support group, there are other kernels compatible with this ROM (I'm using No. 192 OSS Batt version, for instance).
All files mentioned on this post can be found on the Telegram support group (including latest ROM build, MagiskR version, twrp and dtbo.img)
Cheers!

wifi does not work

Etzio_Auditore said:
wifi does not work
Click to expand...
Click to collapse
Did you use the correct procedure right before your post? I feel like the developer won't answer you lol

Does anyone got any issues ussing screen share? My device restart once I choose my tv, I've not tried it with a chromecast, Its a LG smart tv

Typhus_ said:
1 -
Turn your phone into fastboot mode (run adb reboot bootloader or shutdown the phone and turn it on again while pressing Power + Vol- keys)
2 - On fastboot mode run the command:
Code:
fastboot set_active a
3 - Now, flash latest STOCK FASTBOOT ROM using flash_all.bat (or flash_all.sh if using Linux)
4 - Wait for the installation to finish and as soon as you see the welcome screen on stock, go to fastboot mode again
5 - Now run these commands:
Code:
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
(keep pressing Vol+ key to force the phone into recovery mode)​
6 - Now we're on TWRP Recovery using slot B. Do this:
Wipe Dalvik, System and Data
Install lineage-18.0-20201010-UNOFFICIAL-laurel_sprout.zip
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip
Reboot to Recovery​
7 - Now we're on TWRP Recovery but on slot A. Do this:
Wipe Dalvik, System and Data (Yes, again. I'm not Stupid, trust me.)
Install lineage-18.0-20201010-UNOFFICIAL-laurel_sprout.zip
Install twrp-3.3.1-17-laurel_sprout-Installer-mauronofrio.zip
Reboot to Recovery​
8 - You will be on slot B again. Change it back to slot A and reboot to Recovery. Now Format Data with "yes" option to remove stock encryption
9 - Reboot to Recovery again
10 - Install GApps (This is optional! The ROM works fine without any GApps. If you really want GApps you may install any version but I recommend just Core version)
11 - Reboot to bootloader and flash the dtbo.img by running the command:
Code:
fastboot flash dtbo dtbo.img
Code:
fastboot reboot
Your phone while boot into LineageOS 18 and it will be awesomely lag free!
NOTES:
By doing this procedure you will have LOS18 system and vendor installed on both slots!
dtbo.img has to be flashed because when you flash a "new vendor" on both slots you need to flash dtbo as well. If you don't do this you will lose your WiFi and Bluetooth!!
Now you can install Magisk if you want root features (for the time being you must use Magisk 20422 Canary Version)
You can now also install a different Recovery if you like, for example, SHRP Recvoery. Simply go to TWRP and flash SHRP installer zip.
I've tested this procedure yesterday like 2 or 3 times. I've been up almost to 3 AM testing stuff. Right now I'm on LOS18 WITHOUT ANY BUG!
All files mentioned on this post can be found on the Telegram support group (including Magisk version)
Of course that you must store the TWRP img file on the same folder you have platform-tools and the TWRP zip file on your SDCard or phone internal memory....duh...
If you feel like this procedure sucks because it's too long, or if you think that this can be completely ignored and just flash the ROM like you've always done then DON'T ASK FOR ANY HELP!!! This will SOLVE any stupid problem your phone might have, so.... yeah, I won't give you credit if you don't want to spare 20 minutes (if so...) flashing things the correct way.
Cheers!
Click to expand...
Click to collapse
Thank you for this great how to do process.
Always most informative and helpful.
I have just one question.
I am now in the latest STOCK EU rom, which I flashed through RECOVERY rom and then used the magisk_patched boot method to root. No TWRP or any other recovery in it.
My question is this:
Can I skip fastboot flash the STOCK rom again AND go to step 2 , OR it is mandatory to start from step 1?
Again, thanks for all your help giving us all that knowledge
:good::good:

If you never had any other custom ROM installed on other slot, or did but have gone back to stock using fastboot, yes you can ignore step 1.
Cheers!

Typhus_ said:
If you never had any other custom ROM installed on other slot, or did but have gone back to stock using fastboot, yes you can ignore step 1.
Cheers!
Click to expand...
Click to collapse
so I have to go from step 1, as I have flashed EVERY custom rom available
Thanks man you are GREAT:good:

after executing commands
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
i am booting back in fastboot even holding Vol+ while booting what should i do? Thank you

If you have the phone locked with a pin, when you go into SHRP recovery, typing the same pin doesn't decrypt the phone.

pol00001 said:
after executing commands
fastboot set_active b
Code:
fastboot erase boot
Code:
fastboot flash boot twrp-3.3.1-17-laurel_sprout_Android_10_mauronofrio.img
Code:
fastboot reboot
i am booting back in fastboot even holding Vol+ while booting what should i do? Thank you
Click to expand...
Click to collapse
Have you flashed stock ROM with flash_all.bat? If not, try that.

LineageOS starts booting, but then phone goes to Qualcomm Crash Dump Mode

Hello,
I am new to phone rooting/modding, this is my first time trying to install a custom ROM (lineageOS) to my OnePlus 8 Pro.
First, I followed this guide for rooting, installing TWRP and then Magisk. The only different thing that I did was, when flashing TWRP, not usingfastboot flash recovery twrp-image-filename.img, but fastboot flash recovery_a/b twrp-image-filename.img, because I read that the former may lead to a boot loop.
Everything worked. Then I proceeded to Install LineageOS on instantnoodlep, where it said I needed to upgrade my stock OS to Oxygen 11/Android 11 first (it came with O10/A10). I did that successfully.
However, it turned out that O11/A11 had overwritten TWRP with the stock recovery. So I flashed TWRP again. This too was successful.
I decided not to install the LineageOS with the LineageOS recovery, as in the official guide, but through TWRP. I copied the LineageOS image to phone memory, booted to TWRP, selected Wipe and did a Factory Reset - Wipes Data, Cache and Dalvik (DID NOT choose Advanced Wipe, probably this was the problem?)
After the reset, I selected the LineageOS ZIP file and installed it.
After booting to system, LineageOS starts loading, but after 4-5 mins I see
QUALCOMM CrashDump Mode
--------------------------------------------------
Panic requested on external modem boot failure
mdm_force_reset
Any help for getting out of this?
It will be MUCH appreciated.

Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.

Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.

MaybeDontAsk said:
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
Click to expand...
Click to collapse
The unlock command would be:
Code:
fastboot flashing unlock

Thanks for the suggestions, I will try them when I get to my home PC, I'm at work now.
In the meantime: can someone explain to me what is the exact procedure for installing LineageOS with the latest TWRP image? More specifically, which options in "Advanced Wipe" should be checked, because in all the tutorials I found they were using old versions of TWRP which did not include the "system" option. Mine had it, so I decided not to use Advanced Wipe at all and use the default wipe options (this is also what they did in one of the tutorials). Could this be the cause for the crash dump error?
Also, I am kind of reluctant to re-lock the bootloader and go back to stock OxygenOS. I still have access to the (LineageOS) recovery mode (it overwrote TWRP). Can I try doing something from there, like maybe overwriting it with TWRP again, then wiping everything (the right way) and installing LineageOS again?

Well when ever I get a Qualcomm crash dump error I always like to go back to stock and re do everything fresh just in case something else goes wrong but if you just don't wanna go back to stock you can do this:
If you wanna overwrite lineage os recovery you can reboot into the bootloader, and just do fastboot flash recovery (drag and drop twrp image here)
So it will be something like:
Code:
fastboot flash recovery C:\Users\YourUsername\Desktop\(recovery name).img
Or if you have the twrp image in the same place at platform-tools you can do:
Code:
fastboot flash recovery (recovery.img)
Or a one time twrp boot:
Code:
fastboot boot C:\Users\YourUsername\Desktop\(recovery name).img
Or:
Code:
fastboot boot (recovery name).img
But like I said it's probably better to re-lock the bootloader to start fresh then you can unlock it again and do anything else. Good Luck.
Anyways in TWRP Navigate To:
Wipe>Advanced Wipe> Dalvik/Cache>Data>swipe to wipe
Go back to TWRP home
Advanced>Adb Sideload
Now in PC cmd do:
Code:
adb sideload (drag and drop lineage os zip here)
Hit Enter And Wait Until It Finishes Flashing
Now For The Google Apps (GAPPS):
Download Nik GAPP From:
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
Select "Download"
Then look through all packages and read what each one contains, I would go with either core or basic. But you may need another apps so just read and choose.
Once you choose, click "download now"
Navigate To Folder
Releases>NikGAPPS R if lineage is 18.1(Android 11)>Latest Version>then choose from here and download.
Back to TWRP
If the download for gapps Finished:
Navigate to:
Advanced>adb sideload
Back On CMD:
Flash Gapps:
Code:
adb sideload (drag and drop NikGAPPS zip)
once it finishes:
On TWRP go back to home menu and navigate to:
Wipe>Format Data>Type "yes">Hit Enter>Go Back To TWRP Menu>Reboot>System if it says "no rom is installed" just swipe to confirm reboot, Lineage OS Is Actually Already Flashed. Good Luck!
I know this is long but it's really not lol.

@MaybeDontAsk
Thanks a lot! I will try again via TWRP first. I don't want to re-lock the bootloader just yet, because I fear something may go wrong in the process and I may end up with a bricked phone AND a locked bootloader, and that will really be the worst scenario, from what I've read in forums.
As for the GAPPS part - I don't plan to install them. Just a LineageOS image will be fine.

Alright well hope everything goes well and yeah I also feared I may end up bricking my device with the msm download tool but I've already done it multiple times.
It has fixed a lot of issues for me wether it is that the device is booting straight into recovery or fastboot or that it's not even booting up!

Just something about TWRP: when I tried just booting to it, the phone froze on the "Fastboot Mode" splash screen and stopped there. So I had to use the flash option.
Also, about flashing: I should use
Code:
fastboot flash recovery (recovery.img)
and not
Code:
fastboot flash recovery_a (recovery.img)
fastboot flash recovery_b (recovery.img)
right?
Just double checking to make sure.

Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
{
"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 forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?

freeride01 said:
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
View attachment 5543241
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
Click to expand...
Click to collapse
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.

MaybeDontAsk said:
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
Click to expand...
Click to collapse
Alright.
I gotta find a Windows PC though, I am on Linux/Fedora.
My OxygenOS before the wipe was 11.0.10.10.IN11BA, I guess from the list I should download "OOS 11.0.4.4", because its the latest.
I'll post again when there is some progress.

MaybeDontAsk said:
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Click to expand...
Click to collapse
OK, I got my hands on a Windows 10 PC. I downloaded and extracted the MSM tool and watched the video you linked.
There is no Win7 version of the .exe file, so I guess I'll use the "normal" one anyway.

Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?

freeride01 said:
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
Click to expand...
Click to collapse
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.

MaybeDontAsk said:
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
Click to expand...
Click to collapse
Hi again,
I did the whole process again and when I did adb sideload I got this:
Code:
[[email protected] phone root]$ adb sideload lineage-18.1-20220214-nightly-instantnoodlep-signed.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Now what? There's a slide in TWRP that says "Swipe to start sideload", should I swipe it?
EDIT: Maybe Ishould use adb install as described here?

No, you need to reinstall the adb interface drivers, search up on how to do it on Linux.
Tht link you put is for installing apk directly from adb and not roms.

But adb seems to work, adb devices returns my phone ID.

It says something like "(Device ID) | Sideload?
If yes then reboot both the laptop/pc and phone.

Code:
[[email protected] phone_root]$ adb devices
List of devices attached
19356f32 recovery
(changed some digits in serial no. for privacy)

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note 20 & Note 20 Ultra Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 Ultra​Only 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.

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

well done sir

Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!

edsoedso said:
Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!
Click to expand...
Click to collapse
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards

corsicanu said:
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards
Click to expand...
Click to collapse
Nothing changes in the screen phone. Attached is odin screen. Thank you!

edsoedso said:
Nothing changes in the screen phone. Attached is odin screen. Thank you!
Click to expand...
Click to collapse
Can you please check Kg state line from download mode? What's written there?

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
I installed twrp but it seems that it does not read the internal storage.

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
And how to flash the multidisabler? it seems that everything is encrypted and is impossible to locate it in twrp?

I found it!
1. enter into TWRP (after flashing twrp.tar and Vbmeta.tar via odin), format data and reboot again in TWRP
2. Being in TWRP, transfer from PC to your phone multidisabler.zip and magisk zip.
3. flash them both
4. reboot system
That is all!

i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system

Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?

m7mdo_93 said:
i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system
Click to expand...
Click to collapse
edsoedso said:
Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?
Click to expand...
Click to collapse
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
yeah , after flashing multidisabler second time my mobile able to working .. thanks for your help

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
Thank You very much. It worked!

A big thank you, it works fine.

hey.
i did everything from this guide, and i got root access+twrp installed.
the problem that i am facing, is that i canot install anything from twrp, due to insufficient space.
the system size that twrp is reading is only 8384kb, so every installation of gapps is failed.
i tried to wipe ,format data, and changing the file system, but nothing helped.
please give me an idea how to solve it.
thanks.

Good day
Does this work for Android 13 One UI 5.1?