Root oppo f1s marshmallow 6.0 on 2021 without TWRP or PC, ONE CLICK, read all the words i wrote here
Video tutorial :
WARNING : ur responsible on any damage you may cause while using root access ,
This is how you can root your oppo f1s with one click
-Install Mtk-easy from this link https://www.mediafire.com/file/uykcln2dgmqxkid/mtk-easy-su-v2.0.6.apk/file
-Click on the # button
-when you get the message , get ou of mtk-easy and wait until the "magisk" with default android image pop up on the apps list
click on it then update it and wait for the installation
And done, u can run magisk and manage root access
U NEED TO REPEAT THESE STEPS EVERY TIME U REBOOT YOUR PHONE
uninstall magisk when u turn off then on your phone next time, and use mtk-easy again to grant root access for u , it will install magisk again and u'll keep repeating these steps to never lose root access
Kinda easy , waited for years
Hear me out. Some people will be doing that and probably Safety net will be an issue, if it was that easy then why did I and many people as well write long tutorials that tell you how to root? It's for a reason that MTK phones are finicky with root and if you don't root them carefully it can become cumbersome and probably brick your device. I don't want to hurt your feelings, this is a great method, but it requires too much user interaction every time your phone reboots.
if anyone failed this even after turning on 64-bits on mtk-easy
Go to mobile data settings and get out google services and playstore from connecting to the Internet
uninstall magisk and mtk-easy then install only mtkeasy, open mtk easy then the method should be 100% working
muhammad42620 said:
Hear me out. Some people will be doing that and probably Safety net will be an issue, if it was that easy then why did I and many people as well write long tutorials that tell you how to root? It's for a reason that MTK phones are finicky with root and if you don't root them carefully it can become cumbersome and probably brick your device. I don't want to hurt your feelings, this is a great method, but it requires too much user interaction every time your phone reboots.
Click to expand...
Click to collapse
yeah i agree, but its better than getting up to the risk of changing the recovery with another one like TWRP which is the part that most users fail and end up with a bootloop on other previous methods that require 0 fails on the downloadtool usage
CESTRayCRYSTAL said:
yeah i agree, but its better than getting up to the risk of changing the recovery with another one like TWRP which is the part that most users fail and end up with a bootloop on other previous methods that require 0 fails on the downloadtool usage
Click to expand...
Click to collapse
These methods may be really good for devices that don't even have a custom recovery. As for us, we have CTR recovery which is really smooth and doesn't bug out unlike TWRP. So this method may not have any use because I also have a custom ROM coming up
muhammad42620 said:
These methods may be really good for devices that don't even have a custom recovery. As for us, we have CTR recovery which is really smooth and doesn't bug out unlike TWRP. So this method may not have any use because I also have a custom ROM coming up
Click to expand...
Click to collapse
Hey, do you have a link to any custom ROM for OPPO F1s? I am still stuck at 5.0 and many apps are no longer supported.
Related
i believe kingroot does not work on 5.1.1 but is there another way to root? ive looked everywhere...
Xnitro67 said:
i believe kingroot does not work on 5.1.1 but is there another way to root? ive looked everywhere...
Click to expand...
Click to collapse
Kingroot does work, you will have to try several times...
Xnitro67 said:
i believe kingroot does not work on 5.1.1 but is there another way to root? ive looked everywhere...
Click to expand...
Click to collapse
I'm sorry but no, you haven't looked everywhere. Try using the search function.
http://forum.xda-developers.com/announcement.php?f=3676
i do get the padlock on reboot at times but doesnt show that i have root access
Xnitro67 said:
i do get the padlock on reboot at times but doesnt show that i have root access
Click to expand...
Click to collapse
Both Kingroot and Kingoroot will grant you TEMPORARY and very unstable root access, but it only lasts for a minute or two, at best, and definitely NOT through a reboot. Look for a guide to Permanent Root and TWRP for instructions on how to gain permanent root privileges. To summarize the process, you'll need to exploit the temporary root access in order to push some commands to modify your CID, essentially converting your retail phone to a Developer Edition. Repeating a similar process cracks the kernel open (and trips Knox, but that isn't necessarily a deterrent), at which point you can install a custom TWRP recovery, then flash custom rooted firmware. Upgrading to Marshmallow requires most of these procedures to be repeated all over again. Obviously, there is more to it than what I've stated, but that is a basic overview of what you'll need to do in order to achieve perma-root. There is a lot of reading involved and no real shortcuts, but all the information you'll need is in this forum and it is very much worth all the aggravation. Just be sure to set aside a few hours to dedicate to the process. Good luck!
Hey does anyone know a way to make PokemonGo work after rooting the phone? Any help is appreciated
Sorry, but as soon as they blocked root, it became a dead game. I don't think root cloak even works nor does xposed framework. Also Nougat doesn't have xposed yet so yeah...
I haven't played PokemonGO in a long time however I'd suggest you try some of the following options:
1. Try toggling root off from SuperSU and see if it works
2. See if AutoMagisk can help if hiding root access of the app. There's plenty of tutorials out there on how to work with it.
3. You can wait until someone mods (unless someone has already done so) the .apk for use with root (and still have multiplayer / internet capabilities), which I highly doubt since the game is kinda dead.
I love how Pokemon go is "dead" already.
We have the attention span of a teaspoon
asaqwert said:
I love how Pokemon go is "dead" already.
We have the attention span of a teaspoon
Click to expand...
Click to collapse
I believe he was referencing that the game was dead to him since they blocked rooted users. It is dead to me as well, if they wouldn't have blocked root, then I still would be playing. My wife doesn't play anymore because I cannot play.
enmajo said:
I haven't played PokemonGO in a long time however I'd suggest you try some of the following options:
1. Try toggling root off from SuperSU and see if it works
2. See if AutoMagisk can help if hiding root access of the app. There's plenty of tutorials out there on how to work with it.
3. You can wait until someone mods (unless someone has already done so) the .apk for use with root (and still have multiplayer / internet capabilities), which I highly doubt since the game is kinda dead.
Click to expand...
Click to collapse
Supposedly Magisk works for hiding root from pokemon go however from what i have seen Magisk doesnt support the pixel yet because of the changes with the file system.
absolutely nothing can bypass this dame root detection of you have a unlocked bootloader! its annoying. i used to like this game but not i cant play. unless your talented on how to make a special boot.img you cant get around this
xdarkmario said:
absolutely nothing can bypass this dame root detection of you have a unlocked bootloader! its annoying. i used to like this game but not i cant play. unless your talented on how to make a special boot.img you cant get around this
Click to expand...
Click to collapse
Those posts were from November... It's easy to get around root detection now, and you don't need a "special boot.img."
A) suhide + Root Switch + custom kernel that hides unlocked bootloader flag. In fact, I have a whole write up on it here.
B) Flash the same ROM to both boot slots + only root one of them + custom kernel that hides unlocked bootloader flag. Enter TWRP to reboot to other slot when you want to switch.
fiveighteen said:
Those posts were from November... It's easy to get around root detection now, and you don't need a "special boot.img."
A) suhide + Root Switch + custom kernel that hides unlocked bootloader flag. In fact, I have a whole write up on it here.
B) Flash the same ROM to both boot slots + only root one of them + custom kernel that hides unlocked bootloader flag. Enter TWRP to reboot to other slot when you want to switch.
Click to expand...
Click to collapse
i have just realized that this forum is for the google pixel (i followed a link here) my phone is a xiaomi redmi 3s. But is some way i can maybe incorporate this to work for me?
xdarkmario said:
i have just realized that this forum is for the google pixel (i followed a link here) my phone is a xiaomi redmi 3s. But is some way i can maybe incorporate this to work for me?
Click to expand...
Click to collapse
This only works for us because of the pixels A/B partition layout. If you have multirom support you could probably do something similar though.
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Edit: Opps sorry thought was OP3 thread :laugh:
ncsuwolfs said:
i want to buy this phone but cant live without xposed, so is there a 6.0 rom anywhere for this phone? ive looked but havent found anything
Click to expand...
Click to collapse
This phone launched with nougat. You can't run marshmallow on it.
liam_davenport said:
Sultanxda and Arter97 CM MM Roms are still up im sure you can find a few others too
Click to expand...
Click to collapse
where do i find those? (i have searched but can only find cm14 for pixel?
toknitup420 said:
This phone launched with nougat. You can't run marshmallow on it.
Click to expand...
Click to collapse
this is what i was afraid of....
ncsuwolfs said:
where do i find those? (i have searched but can only find cm14 for pixel?
this is what i was afraid of....
Click to expand...
Click to collapse
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
There are no Marshmallow ROM's anywhere for this phone.
Never was, never will be.
Magisk isn't an Xposed replacement.
There is no replacement for Xposed.
Dammit, I miss my ~17 Xposed modules.
Most of which gave me options that you won't find on any custom Nougat ROM.
toknitup420 said:
They do have magisk for this phone. I haven't used it but from what I've seen it's similar to xposed.
Click to expand...
Click to collapse
It's a root option. As in you can run SuperSU or Magisk. Magisk has mods that can accomplish certain things that Xposed did but the majority of them don't work with the pixel so don't count on a suitable replacement.
jhs39 said:
I don't understand how it works but unless I misunderstood if you go to the official Magisk thread the creator claimed he was able to run Xposed with Magisk because his app prevented Xposed from needing to write anything to the system image. I supposed if you can't live without Xposed that would be worth looking into further.
Click to expand...
Click to collapse
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
CZ Eddie said:
Magisk isn't an Xposed replacement.
Click to expand...
Click to collapse
This isn't completely true. There are Magisk mods that overlap things that Xposed was capable of. So depending on what you are trying to do and IF mods even worked for the pixel. It could be a replacement for some.
The Magisk on pixel is supported by a guy that frequents the RR thread and he modded Magisk to work on the pixel so it's unofficial. Also there is NO Xposed for android n
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
jhs39 said:
Well that explains why on the official Magisk page the developer said he didn't know if there would ever be a working version for the Pixel phones but people are using Magisk anyway. Unfortunately Magisk seems to run into the same problems as SU on the Pixel in that it doesn't always install properly or maintain root if it does install--plus most Magisk modules don't work with the Pixel, which makes it much less functional than on other phones.
Click to expand...
Click to collapse
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
pcriz said:
I've been running magisk since 11.6 was dropped. I haven't had any issues keeping root or installing. Works every time and I flashing a new rom every 3 or 4 days.
Same with SU.
For magisk people keep leaving busy box in Magisk Manager turned on so it screws up root. It's in the magisk FAQ.
Click to expand...
Click to collapse
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
jhs39 said:
If you've been running SU for more than a few months on the Pixel then you know Google broke root on it and SU had to rewrite the app to fix the issue. That doesn't happen on other phones and is very likely intentional on the part of Google. At another point SU was suddenly causing problems and SU devs had to add a boot signature file to the flashing process. Again, this kind of thing doesn't happen with other phones. Pretending that SU and Magisk have always worked without problems on the Pixel is extremely misleading.
Click to expand...
Click to collapse
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Yeah for the pixel it's pretty straight forward, if you want to root use chainfire's zip it's 2.79 SR3, you're even advised on 2.82 that pixel users will not want to upgrade.
As far as the may bootloader situation, flash the april bootloader and you don't need to bother with the signing zip. Besides, I think dealing with knox was much worse
pcriz said:
Lol why would I lie. I've been on magisk now since Feb. Tell me why I don't lose root?
Maybe you can't get it to work but that doesn't mean it doesn't work.
Also if you are following the evolution of things, signed builds are more secure. Root isn't broken you just have to resign the boot image because of HOW root is attained on the pixels.
Yes it only happens on the pixels because of the partition changes in the pixel. Since they have to be signed now with any bootloader from may and older, users need the verified boot signer.
But if you are paying five minutes worth of attention to all this you would know that all you have to do is flash the April bootloader and there is no longer a requirement for builds to be signed.
I've been through all this a million times. That said I'm still rooted like a champ.
Click to expand...
Click to collapse
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
jhs39 said:
I've been paying a lot of attention to it actually. When you have to flash an old bootloader to prevent boot looping (which is what actually happens if you use the up to date bootloader) or you have to flash a boot signature file that wasn't previously needed then the flashing procedure suddenly changes again I wouldn't say it's easy to maintain root on a Pixel. I guess different people have different definitions for what easy is. As for Knox, I used to have many Samsung phones and once a procedure was figured out to get around it and root you were good for as long as you had the phone. With the Pixels Google seems to be actively trying to screw up apps that create root or bypass safety net via its monthly updates. It's a completely different situation in my opinion.
Click to expand...
Click to collapse
You went from saying "Magisk and SuperSU don't install properly or don't keep root" to talking about the changes to boot signing on newer bootloaders.
If you are going to share information at least try to be accurate. There is a whole slew of users in the development section running rooted ROMs just fine but if a new user reads your posts they will assume root is broken and flashing the pixel leads to boot loops.
You don't want to deal with the verified boot signer all you need to do is flash the april bootloader and reboot. It happens once. If that is too difficult then maybe those same people shouldn't bother flashing anything period.
No one said flashing and modding would be easy but flashing a bootloader ain't hard.
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
jhs39 said:
You might also want to take a look at the other threads in the Q&A which show people unable to flash TWRP, people boot looping when they flash TWRP, people unable to maintain root or flash custom Roms, etc. Even if you are able to maintain root like a pro there is plenty of very easy to find evidence from other people who don't have the same no problems experience as you.
Click to expand...
Click to collapse
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
pcriz said:
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. QUOTE]
I answer these questions a lot and that is most certainly true.
Click to expand...
Click to collapse
pcriz said:
The only thing that proves is we have a ton of users that don't take the time to research.
You got users coming back from O that don't know they need an Android N bootloader in both slots to flash TWRP again.
You have users that are fastbooting ZIP files
You have users fastboot FLASHING TWRP
I read through those threads and in just about every case if you can't get recovery and root on the april boot loader it's probably user error. Welcome to XDA, it's the same on every device.
I guess all the guys that are rooted must full it. Or wizards or something.
I guess reading step by step directions makes me a wizard.
Click to expand...
Click to collapse
Actually that's absolutely not true. I came from a Nexus 6P. On the XDA threads for that phone there is an accurate, clear, up to date step by step guide on how to flash anything with that phone, including separate instructions for how to root, install a custom recovery, how to install a custom Rom and how to go back to stock. On the Pixels the threads are a complete free for all filled with confusing, contradictory and inaccurate information. I just read posts from earlier today from someone who is getting boot loops when flashing SuperSu. Not a single person responded by suggesting that he use the April bootloader. The suggested solution (which didn't work) was to flash the boot sig zip. How exactly is somebody supposed to research flashing on the Pixel when the XDA threads for this phone are a complete shambles? And since you are supposedly such an expert at flashing on this phone why don't you do something useful and help other people who are having problems instead of wasting everybody's time with your utterly pointless posts about how easy it is to flash on this phone and how people having trouble are idiots who didn't do their own research? You aren't simply part of the problem, dude--you are literally the personification of everything that is wrong with XDA.
jhs39 said:
.
Click to expand...
Click to collapse
This discussion ain't worth reading whatever it is you typed dude. I'm going to agree to disagree.
Sorry stable root is an unattainable unicorn for you. Sorry you're having such a difficult time. Sorry that making excuses for false information is a priority over finding out how it's actually done.
Happy flashing, best of luck to you sport.
Hello,
I recently started using Moto G6 Play, and am wondering now what is the best and easiest option for root. I searched a bit on the forum and found one thread for root that includes unlocking bootloader and is more complicated than some info i have found on google - rooting with KingoRoot without pc (if that's even possible).
Device info: XT1922-3, 3/32gb
Build number: OPPS27.91-177-2
Android 8, latest security patches, available 9 Pie update.
Soo, my question is - Will methdos like KingoRoot work because that will suit just fine for me since i do not want to flash anything extra, but only debloat and optimize stock rom? And i suppose my bootloader is locked because when i power up with volume down + power it says oem_locked so thats another reason for pcless root.
Anyone can help?
petar_markovic said:
Hello,
I recently started using Moto G6 Play, and am wondering now what is the best and easiest option for root. I searched a bit on the forum and found one thread for root that includes unlocking bootloader and is more complicated than some info i have found on google - rooting with KingoRoot without pc (if that's even possible).
Device info: XT1922-3, 3/32gb
Build number: OPPS27.91-177-2
Android 8, latest security patches, available 9 Pie update.
Soo, my question is - Will methdos like KingoRoot work because that will suit just fine for me since i do not want to flash anything extra, but only debloat and optimize stock rom? And i suppose my bootloader is locked because when i power up with volume down + power it says oem_locked so thats another reason for pcless root.
Anyone can help?
Click to expand...
Click to collapse
DONT USE KINGO ROOT. For one you have to unlock the bootloader anyway so you can root please just use my guide https://forum.xda-developers.com/g6-play/how-to/guide-t3929928 to avoid screwing up your phone with any root like KINGO root. You have come on here asking what the preferred method is and over 5,000 people are using my guide lol so my guide is the preferred. You need all that in order to pass play store safety net if you even want be able to download alot of games or if you download the apks the game won't load and KINGO root 100% fails safety net checks to make sure your passing it
ninjakira said:
DONT USE KINGO ROOT. For one you have to unlock the bootloader anyway so you can root please just use my guide https://forum.xda-developers.com/g6-play/how-to/guide-t3929928 to avoid screwing up your phone with any root like KINGO root. You have come on here asking what the preferred method is and over 5,000 people are using my guide lol so my guide is the preferred. You need all that in order to pass play store safety net if you even wont be able to download alot of games or if you download the apks the game won't load and KINGO root 100% fails safety net checks to make sure your passing it
Click to expand...
Click to collapse
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
petar_markovic said:
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
Click to expand...
Click to collapse
The link for unlocking it is in the guide...... Just read the guide. And my guide is plenty reliable on here you just have to read it.....
petar_markovic said:
Hi, thanks for quick response,
Well yea, i gave up on KingoRoot after some researching that it might not be safest thing to use. But it seemed pretty handy for my situation. And yes i saw your guide and considered it as option but didnt really find any more reliable threads (maybe i didnt search long enough tho). Btw, as i noticed you method requires unlocked bootloader so if you have some thread available about it throw it here if you can, if not thanks anyways.
Regards
Click to expand...
Click to collapse
It's not an option, it's THE WAY. It's how to root.
Unlock bootloader, flash TWRP, use TWRP to flash encryption disabler and magisk.
Systemless root is the way now. Root is in the boot.img now. One click roots are dead.
The end
ninjakira said:
The link for unlocking it is in the guide...... Just read the guide. And my guide is plenty reliable on here you just have to read it.....
Click to expand...
Click to collapse
Ok, i will post an update on how it went if i actually decide to root.
madbat99 said:
It's not an option, it's THE WAY. It's how to root.
Unlock bootloader, flash TWRP, use TWRP to flash encryption disabler and magisk.
Systemless root is the way now. Root is in the boot.img now. One click roots are dead.
The end
Click to expand...
Click to collapse
Got it.
Hi everyone, I'm new to the community and I had few previous experiences with phone modding so I'm here to ask you some support. I'd like to unlock bootloader, root and maybe install a custom rom o just xiaomi.eu rom but I don't want to brick my phone. I don't know what disadvantages i get other than losing the warranty( i read something about banking apps and netflix). If someone could guide me or link to some detailed guide I'll be very grateful.
The first question about bootloader is do i lose data when i start the process of unlocking the first time and should pop up the error of 160hours? or i lose data only in the second "try" after 1 week?
As said i have a poco f3 8-256 if could be useful.
You won't lose data, at least in my case but just make a backup to be safe.
You can start here:
You can look at his other videos too about Poco F3. They are very helpful to me and it is in English.
I personally prefer xiaomi.eu ROM 12.5.19 gives me 700k AnTuTu, google apps, miui cam, good battery life, good gaming experience, game turbo, and debloated miui which is optimized for the phone.
Yes correct, your phone will only do a Factory Reset after the "2nd try", aka. when the bootloader gets actually unlocked.
On the 1st try, nothing happens with your phone, it'll just ask Xiaomi's servers to allow your Xiaomi Account to unlock the BL.
Munchy's videos (the video above that LynnnXDA linked) are a good starting point for info.
To give you useful info along the way, the other day I made a comment about the disadvantages of Unlocking your bootloader in this thread, I will copy&paste it here:
If you unlock your bootloader, you must be aware of the downsides. Some apps won't work (at least not without a workaround), like Banking apps, Netflix, Super Mario Kart, Google Pay.
That's cuz Google's SafetyNet API reports to those apps that the Security-Status of your phone is "Fail", because of the unlocked bootloader.
You can hide it with Custom ROMs that specifically list "SafetyNet passed" or by using Magisk Root with a SafetyNet Fix Module. Or Both idk whatever.
I use Xiaomi.eu Custom ROM on Android 12 with Magisk Root. Everything works, but this stupid cat & mouse game with Google and Android Modders definitely sucks.
Click to expand...
Click to collapse
I also made another comment about the risk of bricking your phone when flashing a ROM, in this thread:
Critical partitions are being modified in the Flashing-process.
There is no protection.
If your phone shuts down during the Flashing-process, your phone can get bricked (black screen) and you can't even boot Fastboot & Recovery anymore. I know this. I have experience.
You must ensure that you have enough Battery (I recommend 75% Battery at least), that the USB connection is stable (will not disconnect randomly), and that your PC won't crash/shut down.
IF IT HAPPENS, that the Flashing-process errors out, DON'T REBOOT THE PHONE. If you do so, you won't be able to enter Fastboot anymore. You must stay in Fastboot. Just reconnect USB, and try again to Flash. Just don't reboot the phone.
Sorry for fear-mongering, but this is definitely dangerous and not to be taken lightly.
Click to expand...
Click to collapse
Despite the disadvantages (which might increase, because of Google fighting against it), there are some nice advantages, like being on the cutting edge ROMs with the latest updates, freedom, Access to system files, System-backup/restore, Call Recording (which may otherwise not be available for you), Cool Magisk Modules, Mods and other things...
dreamytom said:
Yes correct, your phone will only do a Factory Reset after the "2nd try", aka. when the bootloader gets actually unlocked.
On the 1st try, nothing happens with your phone, it'll just ask Xiaomi's servers to allow your Xiaomi Account to unlock the BL.
Munchy's videos (the video above that LynnnXDA linked) are a good starting point for info.
To give you useful info along the way, the other day I made a comment about the disadvantages of Unlocking your bootloader in this thread, I will copy&paste it here:
I also made another comment about the risk of bricking your phone when flashing a ROM, in this thread:
Despite the disadvantages (which might increase, because of Google fighting against it), there are some nice advantages, like being on the cutting edge ROMs with the latest updates, freedom, Access to system files, System-backup/restore, Call Recording (which may otherwise not be available for you), Cool Magisk Modules, Mods and other things...
Click to expand...
Click to collapse
Thanks a lot for your help, today I'm gonna start the unlocking procedure. One last question, do i need specific usb drivers and where can i find them? is there an official source?
generale48 said:
Thanks a lot for your help, today I'm gonna start the unlocking procedure. One last question, do i need specific usb drivers and where can i find them? is there an official source?
Click to expand...
Click to collapse
The best drivers are included in Mi Flash, under the menu "Driver".
Before installing the drivers, I recommend starting Windows with Driver Signature Enforcement disabled.
Otherwise not all drivers get installed, because a few are not signed (They are safe to install though).
To temporarily start Windows with Driver Signature Enforcement disabled:
1. Hold SHIFT while clicking the Restart-Button
Windows automatically boots into Advanced Startup Options
2. Click "Troubleshoot" > "Advanced options" > "Startup Settings" > Restart
Windows boots into Startup Settings
3. Click 7 for "Disable driver signature enforcement"
Then when you're in Windows, you can install the drivers from Mi Flash.
Hi everyone, tomorrow i will unlock my bootloader and during this days I looked for some custom roms. First of all I want to ask you which are advantages and disadvantages of rooting the phone, I read about safetynet problem, and also some custom roms that are compatible with safetynet.
I'd like a stable rom but not stock like miui.eu, I was thinking something like lineageos or arrow os, what are the differences?
Hi All, what is best stable EU 12.5 rom for POCO F3 best better battery life?
Hi All, is it every time request unlock bootloader from xiaomi.com have to wait a week 7 days ??
@coolkillermax Yes, you have to wait.
I
generale48 said:
Hi everyone, I'm new to the community and I had few previous experiences with phone modding so I'm here to ask you some support. I'd like to unlock bootloader, root and maybe install a custom rom o just xiaomi.eu rom but I don't want to brick my phone. I don't know what disadvantages i get other than losing the warranty( i read something about banking apps and netflix). If someone could guide me or link to some detailed guide I'll be very grateful.
The first question about bootloader is do i lose data when i start the process of unlocking the first time and should pop up the error of 160hours? or i lose data only in the second "try" after 1 week?
As said i have a poco f3 8-256 if could be useful.
Click to expand...
Click to collapse
After you complete all the steps to unlock the bootloader and to flash it using twrp I recommend you to use this website to download the perfect miui based ROM for your device (note: it can be prerooted).
MIUI Custom-ROM Builder for Xiaomi Poco F3!
Create your own MIUI Custom-ROM for your Xiaomi Poco F3! Select from more than 20 Features!
mi-globe.com
cyanGalaxy said:
@coolkillermax Yes, you have to wait.
Click to expand...
Click to collapse
Than no choice, Haiz..... Yesterday i just done unlock bootloader & during flashing EU rom once done installed saw 2 slot show in TWRP, Slot A & Slot B ?? What is that ?? choose slot B it just can not normal boot but fastboot only, than i choose Slot A than my NEW EU rom boot OK, seem now day flashing ROMs quite complicated compare old time So simple easy!! Could anyone explain this... Appreciate if anyone can tell me
coolkillermax said:
Than no choice, Haiz..... Yesterday i just done unlock bootloader & during flashing EU rom once done installed saw 2 slot show in TWRP, Slot A & Slot B ?? What is that ?? choose slot B it just can not normal boot but fastboot only, than i choose Slot A than my NEW EU rom boot OK, seem now day flashing ROMs quite complicated compare old time So simple easy!! Could anyone explain this... Appreciate if anyone can tell me
Click to expand...
Click to collapse
I suggest reading this:
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
AOSP Doc:
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
cyanGalaxy said:
I suggest reading this:
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
AOSP Doc:
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Thanks but it seem too long & complicated to understand, could you explain main notes & simple to understand ? Is it Slot A & Slot B is no way to skip or remove it ? Or is it after remove next time i unable to return to global stock roms ?
Can anyone give eu rom 12.5 weekly rom as i search in eu rom all in "Fastboot rom" not TWRP roms, so anyone can give me links it is appreciate