Database Develop

Best way to factory reset the 3T before trading it in?

I am needing to send my device in to TMobile after trading for the 6t. I am rooted with Xposed on the latest stock OOS (3T). Would someone be able to let me know if there are any toolkits or simple steps to locking my bootloader and factory resetting the device?
Any help is greatly appreciated

Format the device in twrp (not talking about wiping but formating).

Or just use the Unbrick tool to completely reset everything back to stock. It removes and resets everything, including your bootloader status.
Thanks for being in the 3/T community and have fun with your new device!

0xPraeT0Rian said:
Format the device in twrp (not talking about wiping but formating).
Click to expand...
Click to collapse
For someone who don't know much this could result at a device with no Os.
Why not to use the standard factory reset from inside the device?
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
For someone who don't know much this could result at a device with no Os.
Why not to use the standard factory reset from inside the device?
Click to expand...
Click to collapse
Yeah I have but the dm-verity is annoying it's coming up as not enforced I think, but my mom is trading in her 3T as well and I never unlocked her BL so it does not come up at all during boot.
Does anyone know if TMobile would void the trade-in because of that?

https://forums.oneplus.com/threads/...not-enforcing-at-boot-for-oneplus-3-t.735219/
This fixed my issue

Unlocked Bootloader = No Fingerprint

Fingerprint on this device is disabled after i unlocked bootloader, I tried complete wiping the device multiple times as i thought this was my own fault since i had setup the device prior to unlocking bootloader. No dice.
I thought maybe that a wipe would clear the fingerprint cache or something and make it work.
After locking the bootloader the reader starts working again.
Was this supposed to be the expected behaviour?
I refuse to believe that they would completely disable it system wide instead of just preventing payments etc like normal.
As a side note, transferring user data from an old phone is also broken by bootloader unlock, errors out with "something went wrong" when hitting the copy button to start the transfer.

Just as another side note, the system partition cannot be erased with fastboot either, access denied error even with unlocked bootloader. I figured this out while trying to get my fingerprint reader working. I tried multiple commands and also mfastboot instead of android sdk fastboot

Good news BL is unlockable, bad news FP scanner gets disabled. How about unlocking the BL, rooting the phone with Magisk, and then relocking the BL? Will this work? I haven't got the phone yet, it's arriving next week. Thanks for sharing your findings.

I haven't had a chance to try that. This phone is now my daily driver and I'm working for the next few days so I won't be able to get around to trying until then. I'm sure it wouldn't work though because I believe the device wouldn't boot after the bootloader was modified since locking the bootloader after installing magisk would probably not work.

Might actually brick the device https://forum.xda-developers.com/oneplus-5t/help/relock-bootloader-flash-magisk-t3840071/

darkdaemon32 said:
Might actually brick the device https://forum.xda-developers.com/oneplus-5t/help/relock-bootloader-flash-magisk-t3840071/
Click to expand...
Click to collapse
Certainly looks too risky

Hey, that's weird. I unlocked BL, flashed magisk and my fingerpring works flawlessly.

Hi all, can someone point me in the right direction/guide for unlocking BL and rooting my Motorola One Zoom (Retail US) I appreciate your feedback ??? really looking to get Viper4Android and some other rooted app goodies on my device. Thanks!

Jaysmith696 said:
Hi all, can someone point me in the right direction/guide for unlocking BL and rooting my Motorola One Zoom (Retail US) I appreciate your feedback ??? really looking to get Viper4Android and some other rooted app goodies on my device. Thanks!
Click to expand...
Click to collapse
Hey, I'm gonna prepare a guide for BL unlocking, magisk and xposed for our device. Should be available in 4-5 hours from now.

rafikowy said:
Hey, I'm gonna prepare a guide for BL unlocking, magisk and xposed for our device. Should be available in 4-5 hours from now.
Click to expand...
Click to collapse
You're the best! Thank you so much

Jaysmith696 said:
You're the best! Thank you so much
Click to expand...
Click to collapse
Sorry but unfortunately I won't be able to prepare instructions tonight. Too busy before holidays. Will be back on 25th of Sep. But what can I say is that procedures to "unlock bootloader", "magisk" and "xposed" are very common for many devices (including moto one zoom) and can be easily found in the internet.
btw: PPH29.59-34 software update has just arrived (I live in Poland).

rafikowy said:
I unlocked BL, flashed magisk and my fingerpring works flawlessly
Click to expand...
Click to collapse
Model №? FW Version?
OP, did you try Magisk?

I did not have a chance to try magisk as I was only testing unlocking to see if anything broke. And whenever I couldn't set it up with fingerprint I relocked and wanted to wait to see if others have the same issue. I'm on this fw https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Hi - I was on Motorola website and didn't see anything listed for device bootloader unlock for Motorola One Zoom, how were you guys able to do this?

You need to create a Motorola account but the pages are located here
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Jaysmith696 said:
Hi - I was on Motorola website and didn't see anything listed for device bootloader unlock for Motorola One Zoom, how were you guys able to do this?
Click to expand...
Click to collapse

darkdaemon32 said:
You need to create a Motorola account but the pages are located here
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Click to expand...
Click to collapse
Thanks darkdaemon, I was able to unlock Bootloader and root with Magisk, the only thing my Fingerprint lock method no longer enabled, I can't use pin, pattern or password, so my device has no way to screen lock ?
I'm just happy it's rooted, if there's a way to fix this I hope someone can shed some light ?

Jaysmith696 said:
Thanks darkdaemon, I was able to unlock Bootloader and root with Magisk, the only thing my Fingerprint lock method no longer enabled, I can't use pin, pattern or password, so my device has no way to screen lock
I'm just happy it's rooted, if there's a way to fix this I hope someone can shed some light
Click to expand...
Click to collapse
I'm having the exact same issue after unlocking bootloader. I didn't modify anything at all and still my phone's lock function is completely disabled. Only way I could fix it was going back to stock and re locking bootloader. I'm currently without root or any modifications because of this. I'm also waiting on a fix

Have unlocked the BL straight upon receiving the device and FP scanner is working no problem. I didn't register any fingerprints (or set up any screenlock) prior to unlocking. My Build is PPH29-59-29, SW channel retgb.

This may be where my issue is. I had setup the phone and registered my fingerprints prior to the unlock. Im guessing that they are being stored somewhere that I cannot wipe such as /system or inside an enclave chip etc. Because the only partition I couldn't manually use an erase command for was /system as I was getting access denied error. I may get around to trying the Lenovo phone tool and/or removing fingerprints first to see what happens. I just need to find the time to mess with it.

crubbish said:
Have unlocked the BL straight upon receiving the device and FP scanner is working no problem. I didn't register any fingerprints (or set up any screenlock) prior to unlocking. My Build is PPH29-59-29, SW channel retgb.
Click to expand...
Click to collapse
I don't know why you've got figerprint and everybody's not. I don't have one either. This is also a problem with phones from other manufacturers.
Would you mind seeing who the fingerprint scanner manufacturer is?
I have Goodix.
Maybe it depends. Or maybe the system will shutdown it after unlocking the bootloader.

Can i unroot and relock my Pixel 4 XL ?

I unlock bootloader and root my PIxel 4 XL by Magisk . Can i relock and unroot my phone to original ?

truongcoi85 said:
I unlock bootloader and root my PIxel 4 XL by Magisk . Can i relock and unroot my phone to original ?
Click to expand...
Click to collapse
Yes
1) uninstall magisk
2) flash factory image (with or without wipe)
3) lock bootloader (this will wipe the phone)

prgopala said:
Yes
1) uninstall magisk
2) flash factory image (with or without wipe)
3) lock bootloader (this will wipe the phone)
Click to expand...
Click to collapse
Thanks you <3

truongcoi85 said:
Thanks you <3
Click to expand...
Click to collapse
Personnaly (and tested) I would prefer the OTA sideload method before relocking bootloader, this may avoid bootloop or start screen stuck.

dd66 said:
Personnaly (and tested) I would prefer the OTA sideload method before relocking bootloader, this may avoid bootloop or start screen stuck.
Click to expand...
Click to collapse
Can you give specific instructions? Does rooting cause a loss of battery life?

truongcoi85 said:
Can you give specific instructions? Does rooting cause a loss of battery life?
Click to expand...
Click to collapse
Specific instructions may be found on Google developer site, quite easy.
Regarding the battery loss, no, it won't interfere. More, I have a custom kernel (EX) which preserve it significantly.

Just a personal preference maybe but... I would say flashing the full factory image WITH wipe still enabled is your safest route. Also DO NOT toggle off the "OEM Unlocking" switch until you are super sure all is back to the should and booting properly! There is actually no reason to ever toggle that switch back off in my opinion.

If the relocking process wipes the phone (I've never done it myself), then there is zero benefit to flashing the factory image without having it do a full factory image. You need to backup your data in either case (if you have anything you want to keep). Having the phone do a full factory reset is the best way to ensure everything is back to normal prior to relocking the phone.

sic0048 said:
If the relocking process wipes the phone (I've never done it myself), then there is zero benefit to flashing the factory image without having it do a full factory image. You need to backup your data in either case (if you have anything you want to keep). Having the phone do a full factory reset is the best way to ensure everything is back to normal prior to relocking the phone.
Click to expand...
Click to collapse
Perfect follow-up to my post. You did a better job articulating the risk avoidance aspect. Lol

Better yet... Flash full October image and then take Nov ota before locking.

Sorry for the late reply to this thread, but I just went through this with my Pixel 4XL. I did a complete uninstall of Magisk and rebooted. I then went to the Google Pixel image page and used the flash feature for the latest version. I selected the option to wipe, restore partitions and lock the bootloader. It all seemed to go well until I booted the phone and ran through the setup pages and it prompted me to re-download my T-Mobile eSIM. I went into settings and deleted the eSIM and then did another factory reset on the phone just to be sure.

I have a question what happened to my eSIM if I unroot and flash the stock images? Can I use same eSIM QR Code or I have to get new QR code from my carrier. I'm using it on Middle East.

Lost system on A partition, how to get back?

Totally stock pixel 5. Tried to sideload 12, and due to crappy instructions on XDA, that failed to mention the need to do the OEM unlock step, I ended up with a ADB sideload flash that failed at 94% and resulted in a empty A partition and a phone that failed to boot, so it switched to the backup system partition.
I'm now booted on the B partition (Android 11).
How can I fix my phone, so it's got 2 good system partitions?

Enable OEM unlocking, unlock bootloader, then use the Android Flash Tool to flash 12 Beta 5. Wiping /data shouldn't be necessary; however, if this fails and you have to force flash all partitions, a /data wipe will be required.
I highly recommend you keep the bootloader unlocked while using beta firmware, because it makes it a LOT easier to downgrade back to production firmware.
If you intend to root, don't forget to disable dm-verity and vbmeta-verification.
Detailed instructions on using the Android Flash Tool
Tip: When you get to the step of selecting which build to flash to your device, click the pencil icon to change options. Make sure you leave Relock Bootloader unchecked,

V0latyle said:
Wiping /data shouldn't be necessary
Click to expand...
Click to collapse
But unlocking the bootloader will wipe the phone.....
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it

xunholyx said:
But unlocking the bootloader will wipe the phone.....
Click to expand...
Click to collapse
Correct, but it's still necessary to install the beta (and downgrade)
xunholyx said:
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it
Click to expand...
Click to collapse
There is indeed. It's actually quite comprehensive.

I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,

Chr1stOnABike said:
I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,
Click to expand...
Click to collapse
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work. Requires unlocked bootloader
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.

V0latyle said:
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work.
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.
Click to expand...
Click to collapse
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)

Chr1stOnABike said:
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
Click to expand...
Click to collapse
Ah. Well, you can fix this, but it will require unlocking the bootloader.
You can always relock it after you're done.
Chr1stOnABike said:
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Click to expand...
Click to collapse
Don't know. Given that you can't boot into recovery, you can't sideload the OTA to test this theory. I personally doubt it. You can either wait and see, or you can just bite the bullet and fix the issue.
Chr1stOnABike said:
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)
Click to expand...
Click to collapse
Link to the post? You may not be the only one, but the majority of folks (including myself, I was in the Marine Corps for 9 years so you can guess my mental acuity) have been able to use the instructions to our success.

Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?

How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.

Chr1stOnABike said:
Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?
Click to expand...
Click to collapse
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
Chr1stOnABike said:
How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.
Click to expand...
Click to collapse
I have updated my phone using both of these methods and can personally confirm the instructions are correct. The only difference I would point out is that I'm comfortable enough using adb and fastboot commands that I manually type them and don't use the batch file.
It is your responsibility to understand the instructions and follow them. You flash and modify your device at your own risk. If you do not fully understand the instructions, it is also your responsibility to either find the details you need, or ask for help.
This may seem rather condescending or apathetic, but the situation is this:
- You tried to run experimental beta firmware on your device despite your concerns for the warranty
- You did not ask questions before doing so, and if you did read any of the multiple threads on this issue, you would have been acutely aware of the recommendation to unlock your bootloader before you proceed
- You are now left with few options to fix your device because you decided to ignore experienced advice and do things your own way
As I stated previously, the responsibility for fixing things is yours and yours alone. If you were that concerned with your warranty, you should have kept your phone completely stock and avoided installing the beta.
I have one last recommendation for you:
Disenroll from the beta program and wait for the OTA to take you back to A11 public release. A data wipe will be required.
You have been told in detail what you can do to fix your device. What you do now is completely up to you.

V0latyle said:
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
I have updated my phone using both of these methods and can personally confirm the instructions are correct. .
Click to expand...
Click to collapse
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.

Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
Click to expand...
Click to collapse
Yes - I unlocked and rooted my phone the day I got it, and I bought it full price direct from Google. Your point?
Chr1stOnABike said:
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
Click to expand...
Click to collapse
Yes, it's always worked for me. I've been trying to work with you here and give you options that do not require OEM Unlock or unlocking the bootloader. The reason I thought the Android Flash Tool might work is because it's literally a tool provided by Google, and though it uses ADB, I figured they might have some sort of security to allow recovery of locked phones.
What exactly is it you don't think I understand? As I've pointed out, you decided to install beta software on your device despite your concerns for warranty. As I ALSO pointed out, if warranty was that much of a concern for you, you should have stayed on stock public release firmware and not messed with anything at all.
I will admit that the guide you linked does not mention needing an unlocked bootloader. I think it's generally been assumed among us in the community that modifying your device requires an unlocked bootloader. I will talk to the mods and see if we can get a note added to the post. However, you seemed to miss the big warning that advises against using the beta on your daily driver.
Chr1stOnABike said:
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
Again, how so? If you're going to call me ignorant, you had better explain how.
OEM Unlock simply sets a flag: "unlock-ability" to 1. It's an on/off switch that corresponds to the 1 or 0 set for the "unlock-ability" flag. It has no other function.
When someone attempts to unlock the bootloader, the device checks that flag. If it's 0, the bootloader cannot be unlocked. If it's 1, it can.
Unlocking the bootloader disables security features that prevent you from flashing partitions on your phone, or booting images sent via ADB. The reason why this is important when running custom or experimental firmware is because it allows the user to reflash corrupted partitions (like in your case). It allows a lot more freedom over what you can do with your phone.
I've been doing this for years - more than 10 years in fact. I would be careful about making accusations like "you don't understand the difference" or "you don't know what you're talking about'" to someone who is trying to help you. I understand you're frustrated, but you're going to have to swallow your pride here and admit, at least to yourself, that you screwed up. It seems pretty clear to me that you either did not fully understand the risk of trying to modify your device with a locked bootloader (yes, installing the beta counts as a modification), or you ignored the risk and tried to do it anyway. Yet you come here and impugn my credibility? As they say, "check yourself before you wreck yourself". You screwed up and got yourself into this mess. You alone are to blame. No one has to help you, and believe me, I've been quite tempted to tell you to pound sand. The least you can do is show a little gratitude for someone who's trying to help, and respect for experience and knowledge far beyond your own.
I have one more option for you: Rescue mode.
Reboot your phone into bootloader (hold power + volume down, release power but keep holding volume down when screen turns off)
Use volume buttons to select rescue mode on the right side, then press power to select
Google Pixel Repair Tool
This probably won't work because the repair tool only works if the firmware on your phone is older or equivalent to the firmware the repair tool has.

Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
I haven't had time to read much of this thread yet, but why insult the one person I see who's trying to help you?
I've seen this before and other users who may know what to do, usually just walk away as they don't want to help someone who may just insult them or are clearly unappreciative of the help given.
Everyone let's all keep it civilized.
If you have issue with a post, please hit report button and walk away.
Positive vibes, all.
--andybones

@Chr1stOnABike I am indeed trying to help you, as I understand your situation is frustrating. I also understand that it may be frustrating to be told to do what you didn't want to do in the first place, but the reason why I'm telling you to do it is because it'll be of the most help to you.
Losing your data sucks. I get it. But fortunately the Pixel 5 is great about backing everything up to your Google account. Just make sure your photos are backed up and you'll be fine. Setting it back up after a wipe is a pain in the ass, but again, I'm recommending the bootloader unlock because I believe it's your best chance at recovery.
As far as that goes, I'm still trying to be flexible and provide you with different options. Be aware that if these other options don't work, you have no other choice. I'm not saying that to be rude, that's just the reality of it.
And lastly, I would very much appreciate you making the distinction between thinking I'm wrong because you have evidence to the contrary, vs thinking I'm wrong simply because you don't like my recommendations. If you sincerely believe I'm incorrect and can demonstrate how, please feel free to do so.
My only objective here is to help people the best I can with the knowledge and experience I have.

For those who ever get stuck like I did. When I got stuck in a bootloop, I realized I could 'fastboot boot twrp.img' and was able to save my internal storage from being lost by backing up to PC with TWRP, then move it back onto internal after the factory reset. Did I lost app data in these cases, yes. But that's my own fault for not regularly backup app data up with something like Swift or AppDash.

@Chr1stOnABike just checking in to see if you were able to get your problem resolved?

Question Can I install root on my device WITHOUT wiping any data from it?

i just want to say, i used my device for long, i dont wanna wipe my data but i want to root it. is that possible?
THX in advance

If your bootloader isn't unlocked then doing so will wipe data. If it is unlocked you can use the latest version of Magisk. Following this guide:
Magisk Root without custom Recovery and without losing Encryption
So, I unlocked my bootloader a couple of days ago, but when I got into the point of flashing TWRP, I realized that there is no custom recovery that supports device encryption. For that reason I didn't root my phone but there is a way around...
forum.xda-developers.com
Obviously you will need the correct boot.img file relevant to your specific Redmi Note 10s device extracted from an official rom.
You'll also need to enable usb debugging in the hidden developer options and configure ADB properly on your computer.
If you don't use the correct rom for your device it will get stuck in a bootloop, or just won't boot at all, requiring a hard reset and loss of all data.
There are guides for all these things on the XDA forums.
If you haven't heard of these things before, this is your main phone, or you aren't confident in your abilities then I don't recommend doing it, but it's your choice just don't blame others if something goes wrong.

stuntdouble said:
You can use the latest version of Magisk. Following this guide:
Magisk Root without custom Recovery and without losing Encryption
So, I unlocked my bootloader a couple of days ago, but when I got into the point of flashing TWRP, I realized that there is no custom recovery that supports device encryption. For that reason I didn't root my phone but there is a way around...
forum.xda-developers.com
Obviously you will need the correct boot.img file relevant to your specific Redmi Note 10s device extracted from an official rom.
You'll also need to enable usb debugging in the hidden developer options and configure ADB properly on your computer.
If you don't use the correct rom for your device it will get stuck in a bootloop, or just won't boot at all, requiring a hard reset and loss of all data.
There are guides for all these things on the XDA forums.
If you haven't heard of these things before, this is your main phone, or you aren't confident in your abilities then I don't recommend doing it, but it's your choice just don't blame others if something goes wrong.
Click to expand...
Click to collapse
okay! i think i dont wanna root it then if you give advice to not do so

Sorry I missed out the part about the bootloader which is important and edited the post above so please re-read.
Yeah if unsure then just don't do it as you could end up losing everything very easily.

KerbMario said:
i just want to say, i used my device for long, i dont wanna wipe my data but i want to root it. is that possible?
THX in advance
Click to expand...
Click to collapse
technically there is a way to unlock the bootloader without losing data but magisk is kinda fuc*ed up on MIUI, and it can cause the phone to not boot

J6idot said:
technically there is a way to unlock the bootloader without losing data but magisk is kinda fuc*ed up on MIUI, and it can cause the phone to not boot
Click to expand...
Click to collapse
isnt unlocking bootloader an option in developer mode options?

KerbMario said:
isnt unlocking bootloader an option in developer mode options?
Click to expand...
Click to collapse
it's not as simple as that, you can register to unlock your bootloader by xiaomi from the dev options, but you still have to do the unlock though your pc with the miunlock program logged into your account. This takes 7 days to verify and the moment you do it it wipes your data.
This is the official way of unlocking your bootloader and being able to do with the device whatever you want.
There is an alternative unofficial way of doing it and that method claims to not delete data on your device, but I have no idea how well that method works since it seems to rely on some sort of workaround. here's a link to the post about that method, I just did mine the official way and copied my files back and redownloaded the apps.
[Rosemary] Instant Unlock Bootloader with no data wipe
Hi I want to share with you guys how to unlock Bootloader without waiting dan best of part is your data will no wiped I am not the programmer of this software, I just want to shares All credit goes to developer: Tapin Recovery Installer Here's...
forum.xda-developers.com
also if you do decide to unlock your bootloader one way or the other, I recommend the following Kernel if you want a less throttled gaming experience.
https://forum.xda-developers.com/t/shared-kernel-beta-genom-r-kernel.4342549/

Cryptonite26 said:
it's not as simple as that, you can register to unlock your bootloader by xiaomi from the dev options, but you still have to do the unlock though your pc with the miunlock program logged into your account. This takes 7 days to verify and the moment you do it it wipes your data.
This is the official way of unlocking your bootloader and being able to do with the device whatever you want.
There is an alternative unofficial way of doing it and that method claims to not delete data on your device, but I have no idea how well that method works since it seems to rely on some sort of workaround. here's a link to the post about that method, I just did mine the official way and copied my files back and redownloaded the apps.
[Rosemary] Instant Unlock Bootloader with no data wipe
Hi I want to share with you guys how to unlock Bootloader without waiting dan best of part is your data will no wiped I am not the programmer of this software, I just want to shares All credit goes to developer: Tapin Recovery Installer Here's...
forum.xda-developers.com
also if you do decide to unlock your bootloader one way or the other, I recommend the following Kernel if you want a less throttled gaming experience.
https://forum.xda-developers.com/t/shared-kernel-beta-genom-r-kernel.4342549/
Click to expand...
Click to collapse
+1 this works

Yes its possible to not wipe data or lose it during the process at this point in time.
Just this past week (I'm new to redmi phones ) did the same process for the note 10s and note 9.
The issue with bootloader unLocking (which normally means a data wipe) is negated with mtkclient.
A Data backup is just a good standard practice but understanding the procedures posted before and following them correctly should give no issue.

You can root it by using termux too.
To root an Android phone using Termux, follow these steps:
Install Termux app from the Google Play Store
Open Termux and run pkg install git to install Git
Run git clone https://github.com/Magisk-Modules-Repo/termux-root.git to clone the root repository
Change directory with cd termux-root
Run sh install.sh to install the root tool
Restart the phone and the phone should be rooted.
Note: Rooting a phone voids its warranty and can potentially harm the device if not done carefully. Proceed at your own risk.