Related
Hi, is there any known benefit in going to arb 4 if a device is on arb 3?
Ps. I didn't update at all since purchase, i had a hunch something bad might happen, probably because i had a history of jailbreaking gaming consoles and stuff in the past. And i know how most manufacturers almost always screw with the user's freedom intentionally or otherwise.
more recent firmware + vendor , needed for new custom roms
bugmen said:
Hi, is there any known benefit in going to arb 4 if a device is on arb 3?
Ps. I didn't update at all since purchase, i had a hunch something bad might happen, probably because i had a history of jailbreaking gaming consoles and stuff in the past. And i know how most manufacturers almost always screw with the user's freedom intentionally or otherwise.
Click to expand...
Click to collapse
upto date firmware... only thing is you cant downgrade lowre than 9.5.0.19 but why would you.?? it miui9.5
and now you cant flash twrp. you must boot then install within twrp.
only thing is not able to downgrade to lower than 9.5.0.19
Yes, you can flash miui pro ?
Adi5 said:
more recent firmware + vendor , needed for new custom roms
Click to expand...
Click to collapse
Erm... are you sure?
I have latest firmware, and always wiped vendor (which is also flashed with rom) and I still have ARBV3...
---------- Post added at 10:51 AM ---------- Previous post was at 10:48 AM ----------
raptorddd said:
upto date firmware... only thing is you cant downgrade lowre than 9.5.0.19 but why would you.?? it miui9.5
and now you cant flash twrp. you must boot then install within twrp.
only thing is not able to downgrade to lower than 9.5.0.19
Click to expand...
Click to collapse
Erm, also not true, if you have ARBV4 you can't downgrade lower than current rom version.
If you have ARBv3, you can downgrade to anything.
9.5.0.19 was, if I remember correctly, when ARBv4 was introduced.
And you can get up to date firmware with ARBv3, simply taking the "non arb" version.
https://sourceforge.net/projects/xiaomi-firmware-updater/files/non-arb/Stable/V10/whyred/
You guys are verifying information prior to share it?
htchd2sucks said:
Erm... are you sure?
I have latest firmware, and always wiped vendor (which is also flashed with rom) and I still have ARBV3...
---------- Post added at 10:51 AM ---------- Previous post was at 10:48 AM ----------
Erm, also not true, if you have ARBV4 you can't downgrade lower than current rom version.
If you have ARBv3, you can downgrade to anything.
9.5.0.19 was, if I remember correctly, when ARBv4 was introduced.
And you can get up to date firmware with ARBv3, simply taking the "non arb" version.
https://sourceforge.net/projects/xiaomi-firmware-updater/files/non-arb/Stable/V10/whyred/
You guys are verifying information prior to share it?
Click to expand...
Click to collapse
Oh u must used non-arb firmware
bugmen said:
Hi, is there any known benefit in going to arb 4 if a device is on arb 3?
Ps. I didn't update at all since purchase, i had a hunch something bad might happen, probably because i had a history of jailbreaking gaming consoles and stuff in the past. And i know how most manufacturers almost always screw with the user's freedom intentionally or otherwise.
Click to expand...
Click to collapse
You did good not to upgrade directly, you paused, to make an educated choice/ action as opposed to blindly update.
Good.
There's no benefit to go to ARBv4* (which comes from version equal or higher than 9.5.0.19). But you might already have it, depending on what version was installed in your device initially.
You can update separately the firmware, using the non arb link I gave in previous post.
Keeping arbv3 means you can flash the device more easily, without having to bypass ARBv4.
*By the way, ARB means Anti Roll Back and was supposed to be some sort of defence against older version non patched. As these might have security problems, they might be exploited to access user data. Doing an incorrect flashing (downgrade) will end up bricking your device to "protect your data" (allegedly). In practice it means, either struggle to workaround that, or send it to the official maintenance center.
Is that a benefit? In my opinion it's not a constraint intended for stupid users. Maybe it's required to have a better "experience" or more security. I see it as a restriction.
Bottom line, is that needed? No absolutely not. Devices with ARBv3 works perfectly fine. Do you need it? Probably if you are installing custom roms, from random developers and even eventually rooting your device, then you should not worry about that particular security concern...
How to go from arb4 to arb3? You need to flash lower firmware? Which? And what do you think about it https://www.youtube.com/watch?v=L4nRqwUfzAg. Will it lower the arb?
How to go from arb4 to arb3? You need to flash lower firmware? Which? And what do you think about it https://www.youtube.com/watch?v=L4nRqwUfzAg. Will it lower the arb
Click to expand...
Click to collapse
As far as i know, we haven't found a way to decrement arb. Arb4 version doesn't affect us as long as you don't hardbrick by attempting to go back to lower arb. So no need to try to go back. You probably already know that.
That video is probably using a method where you flash firmware-less roms so it doesn't change/ touch the arb version, so you can go to any version of miui available.
bugmen said:
As far as i know, we haven't found a way to decrement arb.
Click to expand...
Click to collapse
Yes, if it was so easily possible then it would means ARB would be entirely useless!!!
Since it's supposed to prevent "rollback" to older version... If it was possible to install older ARB then it would means it's completely not efficient.
Therefore, unless/until someone manage to hack it, it's not possible.
As said, it's not a big deal either, simply need to be a bit more careful during flashings.
bugmen said:
As far as i know, we haven't found a way to decrement arb. Arb4 version doesn't affect us as long as you don't hardbrick by attempting to go back to lower arb. So no need to try to go back. You probably already know that.
That video is probably using a method where you flash firmware-less roms so it doesn't change/ touch the arb version, so you can go to any version of miui available.
Click to expand...
Click to collapse
htchd2sucks said:
Yes, if it was so easily possible then it would means ARB would be entirely useless!!!
Since it's supposed to prevent "rollback" to older version... If it was possible to install older ARB then it would means it's completely not efficient.
Therefore, unless/until someone manage to hack it, it's not possible.
As said, it's not a big deal either, simply need to be a bit more careful during flashings.
Gentlemen, thank you
Click to expand...
Click to collapse
gsiwy said:
How to go from arb4 to arb3? You need to flash lower firmware? Which? And what do you think about it https://www.youtube.com/watch?v=L4nRqwUfzAg. Will it lower the arb?
Click to expand...
Click to collapse
htchd2sucks said:
You did good not to upgrade directly, you paused, to make an educated choice/ action as opposed to blindly update.
Good.
There's no benefit to go to ARBv4* (which comes from version equal or higher than 9.5.0.19). But you might already have it, depending on what version was installed in your device initially.
You can update separately the firmware, using the non arb link I gave in previous post.
Keeping arbv3 means you can flash the device more easily, without having to bypass ARBv4.
*By the way, ARB means Anti Roll Back and was supposed to be some sort of defence against older version non patched. As these might have security problems, they might be exploited to access user data. Doing an incorrect flashing (downgrade) will end up bricking your device to "protect your data" (allegedly). In practice it means, either struggle to workaround that, or send it to the official maintenance center.
Is that a benefit? In my opinion it's not a constraint intended for stupid users. Maybe it's required to have a better "experience" or more security. I see it as a restriction.
Bottom line, is that needed? No absolutely not. Devices with ARBv3 works perfectly fine. Do you need it? Probably if you are installing custom roms, from random developers and even eventually rooting your device, then you should not worry about that particular security concern...
Click to expand...
Click to collapse
I really liked that reply.
I have 9.5.6.0. So no i don't have arb4 and i read it too using that other... adb tools i used to debloat.
I did come across the non arb firmwares. And most of the things you said i was already aware of. And really, thanks for that caring reply.
Moving on to that last part, did you mean to say arb should be upgraded to run some custom roms from those random developers and rooting or did i read that wrong?
I have only begun unlocking the bootloader and i am currently on stock, not stock android XD. So i haven't read all these long threads with duplicate posts as part of finding the best setup. I don't plan on jumping through all the custom roms and other stuff. So the inevitable question, what setup did you keep as of now? By that i mean which fw, kernal, rom, other files? I know it could vary with persons, but still, your answer could speed up my progress since I'd like to save a bit of time.
stay in arb 3 is the benefit
abdullah alotaibi said:
stay in arb 3 is the benefit
Click to expand...
Click to collapse
It's bull****, not benefit Or you tell me what's benefit?
bugmen said:
I really liked that reply.
Moving on to that last part, did you mean to say arb should be upgraded to run some custom roms from those random developers and rooting or did i read that wrong?
I have only begun unlocking the bootloader and i am currently on stock, not stock android XD. So i haven't read all these long threads with duplicate posts as part of finding the best setup. I don't plan on jumping through all the custom roms and other stuff. So the inevitable question, what setup did you keep as of now? By that i mean which fw, kernal, rom, other files? I know it could vary with persons, but still, your answer could speed up my progress since I'd like to save a bit of time.
Click to expand...
Click to collapse
No, I meant that ARB is a security feature to prevent rolling back (because some flaws could be exploited to ultimately access the data).
But, if someone is using a custom rom (made by many developers and certainly not knowing all they have done or could have done), that's already not entirely secure. It's based on some trust and assumptions that it's "safe to use". More, if you add rooting, then you potentially enable some apps to access other data, rendering the whole thing even less secure.
That's what I meant, ARB makes some sense for specific security purpose, but we're not in an entirely secure environment (ROM + rooting), so probably attempting to reach 100% security here is not realistic.
I use the latest NON ARB Firmware, stable:
https://forum.xda-developers.com/redmi-note-5-pro/development/firmware-xiaomi-redmi-note-5-t3766138
(I have global, so it's fw-non-arb_whyred_miui_HMNote5HMNote5ProGlobal_V10.0.6.0.....)
Then the latest PE rom.
For recovery I have the latest OrangeFox Recovery.
Magisk for rooting.
So after a clean flash it's:
using fastboot for flashing orangefox.
Using orange fox to flash the FW non arb, PE rom, Magisk.
it's a great setup, works great. I've been tested since May 2018, 7-8 months later we've reached a great working state, finally!
Adi5 said:
more recent firmware + vendor , needed for new custom roms
Click to expand...
Click to collapse
firmware I know but what is 'vendor'? I thought I would just install latest firmware + install rom + install gapps later
abdullah alotaibi said:
stay in arb 3 is the benefit
Click to expand...
Click to collapse
Devs said : You should be on arb4 ?
htchd2sucks said:
No, I meant that ARB is a security feature to prevent rolling back (because some flaws could be exploited to ultimately access the data).
But, if someone is using a custom rom (made by many developers and certainly not knowing all they have done or could have done), that's already not entirely secure. It's based on some trust and assumptions that it's "safe to use". More, if you add rooting, then you potentially enable some apps to access other data, rendering the whole thing even less secure.
That's what I meant, ARB makes some sense for specific security purpose, but we're not in an entirely secure environment (ROM + rooting), so probably attempting to reach 100% security here is not realistic.
I use the latest NON ARB Firmware, stable:
https://forum.xda-developers.com/redmi-note-5-pro/development/firmware-xiaomi-redmi-note-5-t3766138
(I have global, so it's fw-non-arb_whyred_miui_HMNote5HMNote5ProGlobal_V10.0.6.0.....)
Then the latest PE rom.
For recovery I have the latest OrangeFox Recovery.
Magisk for rooting.
So after a clean flash it's:
using fastboot for flashing orangefox.
Using orange fox to flash the FW non arb, PE rom, Magisk.
it's a great setup, works great. I've been tested since May 2018, 7-8 months later we've reached a great working state, finally!
Click to expand...
Click to collapse
Thanks a lot.
Dead Pool Brasil said:
firmware I know but what is 'vendor'? I thought I would just install latest firmware + install rom + install gapps later
Click to expand...
Click to collapse
/vendor is a partition which contains some data or library or files. It's usually updated or wiped by the ROMs (or the firmware)... It's supposed to be "self managed", (I mean you are not supposed to care about that during the flashing).
The only interaction one is supposed to have with that, is that in a "clean flash" (or what I call a "clean flash") you are suppose to do in recovery: advanced wipe, and wipe that partition (/vendor) among others.
I've done that during each of my clean flashs, and it appears that flashing a ROM always put back the things it requires to work properly.
PS: in your comment, it should be more:
-Install latest firmware STABLE (as opposed to development) and (easier) without ARB
-Install rom
-Install gapps (only for rom which are not including it, like Pixel Experience already has).
So, I decided that I wanted to try flashing GSI's on this phone and on checking 2 different apps, they specify that the OP9P isn't treble compatible. What gives? Are the apps just not capable of knowing since it's a new device or has something changed and are devices no longer required to be treble compatible?
You sure you want to try flashing roms when we don't even have TWRP yet?
Jhoopes517 said:
So, I decided that I wanted to try flashing GSI's on this phone and on checking 2 different apps, they specify that the OP9P isn't treble compatible. What gives? Are the apps just not capable of knowing since it's a new device or has something changed and are devices no longer required to be treble compatible?
Click to expand...
Click to collapse
Keep in mind the partitioning scheme of the 9 pro. OnePlus phones typically have a different list of partitions when compared to other standard android phones.
I assumed it was but when trying to flash via fastboot, just didn't work out as planned. Thank y'all for answering though.
I think it's gonna be the same as the 7pro you have to have the original boot and vbmeta and used fastbootd
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
I'm a senior engineer, PC user since Windows 3.11, owned and rooted numerous Android phones over the years, wrote computer programs both for Big Data cloud solutions as well as embedded software for microcontrollers AND xdadevelopers tutorials still baffle me to this day. Unfortunately the way to comprehend what's going on is to:
a) lurk on multiple threads and try to piece it together
b) wait for somebody like you to create a simple step-by-step tutorial that doesn't assume high-degree of inside knowledge
Good luck. I'm receiving my Pixel 6 Pro so I'm in the same situation as you.
cd993 said:
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
Click to expand...
Click to collapse
My guide for flashing Safetynet is a bit more foolproof now. For being rooted on Nov firmware, you would need to OTA to the .036 build first and use the unofficial user uploaded boot.img and vbmeta.img mentioned in my post.
Otherwise, you can root on .015 and wait for the .036 factory images to be uploaded, and wait until we work out how to update without wiping.
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com
RushPL said:
I'm a senior engineer, PC user since Windows 3.11, owned and rooted numerous Android phones over the years, wrote computer programs both for Big Data cloud solutions as well as embedded software for microcontrollers AND xdadevelopers tutorials still baffle me to this day. Unfortunately the way to comprehend what's going on is to:
a) lurk on multiple threads and try to piece it together
b) wait for somebody like you to create a simple step-by-step tutorial that doesn't assume high-degree of inside knowledge
Good luck. I'm receiving my Pixel 6 Pro so I'm in the same situation as you.
Click to expand...
Click to collapse
Sadly, that's the way XDA developed in the most recent years. A lot of developers have become "impatient", they rarely tolerate questions (which they consider unnecessary for reasons of their own) or consider everything that is not in their concise jargon offtopic and either ignore, flame or delete those.
The basics are not explained anymore, they expect everyone to work naturally with the tools at hand, most often or not "small" steps are left out (like clicking on something, or changing a menu), or they refer to "go look at that guide" - only then - that guide tells you (aswell) "for step 3, go look at that guide", because "everyone should know" - that way the rooting community is quite small and elitist; and it's hard for outsiders to come in (and potentially add something to the pool of stuff) simply because it's not a pleasant experience to "dive" into the world of Android customization. It's a sad development and only very few seem to be intend on breaking it.
Then we also have the problem of manufacturers trying to make this communities life harder, just take a look at Google and the constant war to have safetynet NOT trip, to give people the chance to use banking apps or GPay. It's a constant struggle and many "guides" get out of date pretty quickly - and most often or not, those are not kept up to date, or getting demolished by a mod team, so that also adds to the whole confusion, when people try to work with guides / community fixes that won't even work anymore.
cd993 said:
Hey all,
Hope someone can offer an insight here...
I've successfully managed to unlock the bootloader and at one point had rooted the October firmware, but I can't work out how to root the latest Nov firmware. I see a few sets of instructions but I'm struggling here...
I'm currently back on stock and so unsure how to update to the latest system update and then root that?
If someone could lead me to some detailed instructions I (and I'm sure many others!) would be highly grateful!
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...irmware-sd1a-210817-036.4353807/post-85857811
I followed the instruction from this post to restore my P6P to preinstalled October firmware, then updated with November firmware OTA, then unlocked bootloader and root again. My phone works much better now.
I made a mistake of flashing the vbmeta and boot imgs of October firmware for rooting after updating November firmware OTA. I experienced some strange issues with my phone until I restored it with Official Google Android Flash Tool and start the whole rooting process again with the correct version of vbmeta and boot imgs.
Pekempy said:
My guide for flashing Safetynet is a bit more foolproof now. For being rooted on Nov firmware, you would need to OTA to the .036 build first and use the unofficial user uploaded boot.img and vbmeta.img mentioned in my post.
Otherwise, you can root on .015 and wait for the .036 factory images to be uploaded, and wait until we work out how to update without wiping.
Working SafetyNet with Pixel 6 Pro Android 12
This is no longer using an Unofficial Magisk app, it's the official Canary and USNF 2.2.0 1. Download the latest Magisk Canary build 2. Patch the boot.img from the Factory Images in Magisk, you'll also need the vbmeta.img if you aren't already...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much for helping the poor newbies! With your updates I think I can comprehend what's going on. What's changed from my experience with rooting One Plus 6 is that I never had to patch boot images on the phone itself and this "vbmeta" is completely new to me as well.
Can I buy you a coffee via some donation?
RushPL said:
Thank you so much for helping the poor newbies! With your updates I think I can comprehend what's going on. What's changed from my experience with rooting One Plus 6 is that I never had to patch boot images on the phone itself and this "vbmeta" is completely new to me as well.
Can I buy you a coffee via some donation?
Click to expand...
Click to collapse
No need but thank you for offering.
The vbmeta is also new to me. I want to be clear, I've mostly compiled others' instructions (credited in the post) with my own experience, and tried to make it as easy to follow as I can
I was able to root successfully with working Safety Net! Thank you @Pekempy
I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!
CacheOnlyPlease said:
I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!
Click to expand...
Click to collapse
As far as I know, only the original Pixel 1 has an all-in-one tool* ("click button, wait, have fun - even though the P1 tool only came years after release!"), it has always been the culmination of a couple ADB steps/commands in a certain order, plus some manual flashing/magisk file creation incl. copying a couple files from your phone to your PC or vice versa.
Especially since Google changed alot of stuff with Android 11 and Android 12, it's a bit more complicated to root since the days of the original Pixel.
That doesn't mean that there can be no all-in-one root tool here, but as of now we have none and I don't see how one could be created in the foreseeable future.
*https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730227/
Morgrain said:
As far as I know, only the original Pixel 1 has an all-in-one tool* ("click button, wait, have fun - even though the P1 tool only came years after release!"), it has always been the culmination of a couple ADB steps/commands in a certain order, plus some manual flashing/magisk file creation incl. copying a couple files from your phone to your PC or vice versa.
Especially since Google changed alot of stuff with Android 11 and Android 12, it's a bit more complicated to root since the days of the original Pixel.
That doesn't mean that there can be no all-in-one root tool here, but as of now we have none and I don't see how one could be created in the foreseeable future.
*https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3730227/
Click to expand...
Click to collapse
For sure, that's actually the All in One tool that I remember using with my Oneplus 7 Pro. This is my first Pixel phone (does the Nexus 6P count?) so I wasn't sure if developers would be all over it, or if Google has made things more complicated over the past couple of years. Either way I appreciate the reply and will probably dive into unlocking/rooting over the holiday weekend.
CacheOnlyPlease said:
For sure, that's actually the All in One tool that I remember using with my Oneplus 7 Pro. This is my first Pixel phone (does the Nexus 6P count?) so I wasn't sure if developers would be all over it, or if Google has made things more complicated over the past couple of years. Either way I appreciate the reply and will probably dive into unlocking/rooting over the holiday weekend.
Click to expand...
Click to collapse
If you want to read a bit about complication, take a search engine and find out what
Android 11 scoped storage
Android 12 Dm-verity (device-mapper-verity)*
Android 12 Vbmeta verification**
SafetyNet Android
Android Hardware Attestation
means.
*is a method by which an image on block devices (the underlying storage layer of the file system) can be checked to determine if it matches an expected configuration, using a cryptographic hash tree. If the hash doesn't match, dm-verity prevents the stored code from loading.
**is the other half of this - it provides a cryptographically signed reference hash which is used to verify the integrity of /boot, /system, and /vendor partitions. The vbmeta image is only used to verify /boot, while vbmeta-system is used to verify /system.
Click to expand...
Click to collapse
Google has been actively working - for a couple of years now - at making the modding/rooting communities life harder. We have always found a workaround, some require work (spoofing device ID, forcing software attestation, et cetera) or don't work that well at all, but it's a constant struggle.
Every firmware update is a small struggle and you got to pray to the man above that your device will still boot up, even if you have those pesky magisk modules disabled.
Morgrain said:
Google has been actively working - for a couple of years now - at making the modding/rooting communities life harder. We have always found a workaround, some require work (spoofing device ID, forcing software attestation, et cetera) or don't work that well at all, but it's a constant struggle.
Click to expand...
Click to collapse
I think Google's goal was to make our devices more secure, not making modding/rooting harder.
CacheOnlyPlease said:
I really hate asking this type of question as it makes me sound like a choosy beggar, but is there an all in one tool in the works for unlocking/rooting/flashing/etc? As I grow older, I desire rooting and tinkering, however I also value my free time a lot more lately (can't have both, right?).
Apologies if this is a silly question, however I thought I'd ask anyway! Thanks!
Click to expand...
Click to collapse
Not sure if this fits the bill of what you're looking for
Android Flash Tool
Perhaps this
Android Dollhouse (Flashtool) | TESTERS REQUIRED
Android Dollhouse The Definitive Android Flashtool. This is the support thread for Pixel 6 Pro. If you have another device, please check the other threads: Pixel 2XL: Support Thread Pixel 6: Support Thread I'm releasing the first user-facing...
forum.xda-developers.com
Az Biker said:
Not sure if this fits the bill of what you're looking for
Android Flash Tool
Click to expand...
Click to collapse
Sort of. Like I mentioned, I haven't dove into the details yet of rooting my Pixel 6 Pro yet, however can this tool you linked get me out of a potentially sticky situation if I ever need to load the stock firmware (ROM) onto it? That's really my biggest concern is messing something up. If I have a tool handy to get me back to stock, even if it wipes the whole phone, then I'm much more likely to dive in, you know.
For an all-in-one tool... what's wrong with fastboot?
CacheOnlyPlease said:
Sort of. Like I mentioned, I haven't dove into the details yet of rooting my Pixel 6 Pro yet, however can this tool you linked get me out of a potentially sticky situation if I ever need to load the stock firmware (ROM) onto it? That's really my biggest concern is messing something up. If I have a tool handy to get me back to stock, even if it wipes the whole phone, then I'm much more likely to dive in, you know.
Click to expand...
Click to collapse
If you haven't already looked them over, check the 6 PRO link in my sig, Step by step directions, pretty much each and every detail to make it easy for people like me who aren't rooting gurus.
Fastboot is the tool to pull you back from the abyss should you screw the pooch. Plenty of places you can find commands to help you out in a pinch, usually bringing you back to a factory fresh image.
Fastboot, update, and root a few times and it'll become much less concerning and tedious.
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