Related
Hey guys,
so I thought about getting a Redmi note 3 Pro since my wileyfox swift broke.
I am a person that "needs" his phone rooted for adaway and viper audio. I also like CyanogenMod a lot.
After reading through a lot of threds here I got kind of confused and I am really sorry for the dumb questions following.
So what exactly do I have to do to get my phone unlocked rooted and maybe install CM (if it is stable enough).
And there seem to be quite many MIUI Roms out there. what is the difference between all these "global", "eu" and stable or developer versions?
Thanks in advance.
EDIT: Also I read that I can change MIUI Roms with locked bootloader. Can someone explain this?
First the firmware
Global rom is intended for worldwide use (has google play store installed, and other google apps)
China rom is for the chinese and has mostly china specific apps / china app store
Developer rom is usually the latest MIUI version so it could be buggy and is intended for testing
Stable rom is been thoroughly tested and is thought to be the most stable and reliable rom.
Vendor rom is a very stable rom given to sellers to flash for international buyers, most users would never notice, however for enthusiasts it can cause problems getting the device unlocked since it's not identified by the unlock tool, causing users to have to go through a semi-difficult process getting it back to the stable or developer firmware so we can properly unlock it.
(if you do buy one I suggest you ask them to send one with the Chinese firmware since they are easier to flash and unlock)
then there is the eu/smiui roms which are built form the official source but they are 3rd party firmwares, just compiled by someone else maybe with additional features or tweaks.
For the bootloader there is several ways to unofficially unlock it but they are risky, I won't go into that since it should be only as a last resort.
to request xiaomi to unlock your device you go to this website
http://en.miui.com/unlock/
fill out the required information, sign up for an account (you need to use a phone number you can receive sms messages on), and in a few days they usually grant permission, remember your username / email and password since you will need it later when you unlock it., then download the unlock tool, boot your phone to fast boot and then press unlock on the tool, and it should unlock (unless you have the troublesome vendor firmware), if unlocked now you can install twrp / cm13 / root / xposed ..etc
--
you can flash the official miui roms with the locked bootloader
Just to add, if you get an international version of the phone (Special Edition, codename Kate) then the bootloader unlock process does not seem to work at all. I had to resort to an unofficial unlock after trying for over a week (and I'm not new to this).
I would wait. I rely on my phone and mine stopped charging after 10 days. Followed all the silly guides about flashing this, flashing that. Only time phone is recognised is in fast boot mode but no charge. Now my phone is dead and Xiaomi support is nowhere to be seen. They said they will contact me in 24h and its been 3 days.
If you really rely on your phone then please buy a phone that has real customer support. Best case scenario you have to send phone to China and worst case scenario you have to buy a new phone.
otyg said:
Vendor rom is a very stable rom given to sellers to flash for international buyers, most users would never notice, however for enthusiasts it can cause problems getting the device unlocked since it's not identified by the unlock tool, causing users to have to go through a semi-difficult process getting it back to the stable or developer firmware so we can properly unlock it.
(if you do buy one I suggest you ask them to send one with the Chinese firmware since they are easier to flash and unlock)
....
For the bootloader there is several ways to unofficially unlock it but they are risky, I won't go into that since it should be only as a last resort.
to request xiaomi to unlock your device you go to this website
http://en.miui.com/unlock/
....
....boot your phone to fast boot and then press unlock on the tool, and it should unlock (unless you have the troublesome vendor firmware), if unlocked now you can install twrp / cm13 / root / xposed ..etc
--
you can flash the official miui roms with the locked bootloader
Click to expand...
Click to collapse
I bought for my parents 2 Redmi 3 for them to enjoy. I know vendors hinder with the Rom so I usually ask to keep the phone on its original chinese Rom when i buy for myself or for my wife.
However this time I made a mistake thinking that who needs OTA for my parents and i ordered it as it is.
Turned out all google services stops working in the next day whatever I do (reboots, resets, formats, etc...).
I tried flashing via updater app the global rom, it failed.
I tried flashing by rebooting to recovery, it didnt reboot to recovery.
I tried some other stuff which failed.
I downloaded xiaomi unlock tool, signed in, and tried to unlock the bootloader. It didn't work.
I read somehow on miui forums that it's probably a driver issue (something about disabling signature which i'm not familiar with).
Can you please help me?! What to do now? Steps or a guide would be awesome.
Thanks,
ok so please be gentle here, coming back here after 7 years, from old Windows Mobile days!
I am a newbie to Android and want to root my Z5 compact. The only reason I want to root it is to enable some apps like Greenify and GSam battery monitor to work with all their features enabled. I do not want to flash a new ROM. I am happy with Sony's stock ROM.
Is it possible to get root access without installing / flashing a new ROM?
I have searched the internet but people talk about flashing every time I read about rooting. Then I also saw this thread: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Lots of geeky stuff there which is fine, but again, it seems to talk about flashing the ROM, which I really do not want to do or do not see the need (yet).
Unlock boot loader:
I see that Sony lets me unlock the boot loader from their dev site. I am willing to unlock the boot loader. (Not sure if I want to do that first. Maybe unlocking BL is all I need?)
rajdude said:
ok so please be gentle here, coming back here after 7 years, from old Windows Mobile days!
I am a newbie to Android and want to root my Z5 compact. The only reason I want to root it is to enable some apps like Greenify and GSam battery monitor to work with all their features enabled. I do not want to flash a new ROM. I am happy with Sony's stock ROM.
Is it possible to get root access without installing / flashing a new ROM?
I have searched the internet but people talk about flashing every time I read about rooting. Then I also saw this thread: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Lots of geeky stuff there which is fine, but again, it seems to talk about flashing the ROM, which I really do not want to do or do not see the need (yet).
Unlock boot loader:
I see that Sony lets me unlock the boot loader from their dev site. I am willing to unlock the boot loader. (Not sure if I want to do that first. Maybe unlocking BL is all I need?)
Click to expand...
Click to collapse
The only reason to use that guide is to backup ta keys for whatever reason you'd want to do that.
If you're after root on stock ROM the single easiest way is to unlock bootloader, flash twrp 3.0.2, flash xpower 3.0, and that's it. Solid marshmallow with root goodies. Xpower has everything and is deodexed and ready for xposed framework.
just a little more clarification please?
civicsr2cool said:
.....easiest way is to unlock bootloader, flash twrp 3.0.2, flash xpower 3.0, and that's it. ......
Click to expand...
Click to collapse
Ok thanks.....that sounds straight forward.....but isn't TWRP a ROM? (sorry, the moment I hear flashing...I think ROM)
And I am looking up xpower...not sure what that is (yet) and why do I need it
I do want xposed framework though.
I wish there was a simple straightforward answer
rajdude said:
Ok thanks.....that sounds straight forward.....but isn't TWRP a ROM? (sorry, the moment I hear flashing...I think ROM)
And I am looking up xpower...not sure what that is (yet) and why do I need it
I do want xposed framework though.
I wish there was a simple straightforward answer
Click to expand...
Click to collapse
Twrp is your recovery,you flash through fastboot, xpower 3.0 is the ROM, just a pre-modded stock ROM with options of xperia x addons. Use lite and stock kernel for xpower and you'll be set.
still a little confused
civicsr2cool said:
Twrp is your recovery,you flash through fastboot, xpower 3.0 is the ROM, just a pre-modded stock ROM with options of xperia x addons. Use lite and stock kernel for xpower and you'll be set.
Click to expand...
Click to collapse
Ok thanks! So my understanding (so far) is :
We "must" flash a ROM in order to root a phone. Did I get that correct?
Since I said I like the stock Sony ROM, you recommended the xpower 3.0 ROM.........but the point is.....I still have to flash ROM.
A little confused here...
I am a systems engineer (my day job). In Linux or Windows OS, if we want root access (to run some software or a low level command, like partitioning a disk etc), we either run SU command and put root's password OR right click and run as administrator......
We never have to install a brand new Operating System to get root access.
Just a total newbie question.....Why do we have do install a whole new OS (flash new ROM) on our Android phones to get root access?
rajdude said:
Ok thanks! So my understanding (so far) is :
We "must" flash a ROM in order to root a phone. Did I get that correct?
Since I said I like the stock Sony ROM, you recommended the xpower 3.0 ROM.........but the point is.....I still have to flash ROM.
A little confused here...
I am a systems engineer (my d Linux or Windows OS, if we want root access (to run some software or a low level command, like partitioning a disk etc), we either run SU command and put root's password OR right click and run as administrator......
We never have to install a brand new Operating System to get root access.
Just a total newbie question.....Why do we have do install a whole new OS (flash new ROM) on our Android phones to get root access?
Click to expand...
Click to collapse
Android is Linux, to gain root in the ROM you have on your phone currently all you need is an unlocked bootloader to run SU, but then you'll be left with a phone that still needs a customized kernel to keep root and a DRM fix for the camera. Xpower 3.0 is that package.
You could really benefit from reading more. Google up on dm-verity and Sony Ric, and fastboot/adb for a little better understanding of what you're getting into without a pre compiled ROM. Messing around with any Android you'll have the majority of the same steps, unlock bootloader with fastboot, flash Supersu, customized kernel.. Etc
Why use a stable compiled ROM?
Let me list down and explain to you why it's best to use a stable compiled ROM. But first you need to understand these few things before you decide to unlock your bootloader and root.
Before Sony Z models kicked in, every rooted Sony device are still able to retain all the features that came together with the phone before it was rooted. When Sony introduce the first Z model, they start to create these things called DRM keys. DRM keys are unique algorithm (i guess i should put it that way) which is attached to every phone the same way an IMEI number is attached to every phone. In short, my DRM keys cannot be used on your phone and vice versa.
DRM key: It's a unique algorithm that holds all the unique features that an unrooted Sony phone boast such as camera quality, X-reality, High Res Audio etc etc.
The moment you unlock your bootloader, that's the moment your DRM keys will be lost. But don't panic, the wonderful devs on XDA have prepared a tool to backup your TA partition (a partition that contains your DRM key) for your own convenience if you want to relock your bootloader.
Then recently Sony/Android come up with new features called Sony RIC and dm-verity. (You may Google what these are all about but to my understanding it is placing limitations to people who root their phones to meddle around with the system settings of thier phone)
With all these "hurdles", it have taken some time for devs here to find a work around and like every fairytale ending, they manage to find a way.
Now you're wondering if you can actually root without flashing another rom. Good news for you: you can! There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting.
.. But ask yourself what's the point of going through the hassle of rooting and your phone is not tweaked for performance or for theming purposes?
That's when people flash roms and in Z5 compact's case, XPower is the best rom there is. It gives you all the performance tweak you need to make your phone lag free, it has a lite version that removes all the unnecessary system apps you can't delete without root, it gives you an option to add themes and framework from Xperia X with all those work around in place.
For your second question: why is there a need to install TWRP?
TWRP is a recovery tool which is a need for all rooted phone. It's also a tool for you to backup and restore your current rom so that you can rollback to the last working configuration if your phone went into a bootloop etc. Plus i believe all these guides require you to actually use TWRP to flash the SuperSU to successfully root your phone.
I hope this explains your doubts.
Thanks a lot but...
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
By unlocking bootloader, you lose DRM keys. There is a way to backup DRM keys which are in the TA partition, but this is to be done BEFORE you unlock bootloader. Good that I have not done anything to my X5c yet.
The next steps for me would be to look into XPower 3 ROM…which I did and here is what I found out:
http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
First, what's up with the scary looking warning in RED right at the top of the first thread. I did read the OP and the second post, I did not see anything in there which IF I missed will cause my phone to explode! That is probably posted to make noobs read all instructions, right?
Second, I do not see any step in there to backup the DRM / TA partition. I guess the dev is assuming the phone already has lost the DRM, right? So I gotta find instructions on how to backup DRM / TA
Then I searched for problems in this ROM and seems to me that the fingerprint sensor is reported by many to be not working and/or buggy. I rely on the fingerprint sensor day and night. I have many apps which rely on that, like lastpass. That would be a major deal breaker for me.
So going back to stock ROM option…I remember you said "There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting."
Could you please post a link to that?
Thanks again!
I think this is a pretty great thread rajdude. It's getting people to spell out a lot of information to noobs like us that it seems most posters have taken for granted over time.
I'm a complete novice at all of this. Sort of gleaning information as I go along, but I used this guide: http://twigstechtips.blogspot.hk/2016/04/sony-z5-compact-root-without-losing-ta.html?m=0
Along with this guide: http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
The first guide is pretty basic step-by-step instructions. It unfortunately occasionally kind of skips over a couple very small things (that will be clear as you go along), or occasionally words things in such a way that might not be completely intuitive, but maybe that's cause I need things explained to me like I'm five sometimes. Any time I might have had a question about something in the the first guide, I went to the other and found the answer. It didn't take me long to get the gist of the whole thing though, and overall, it wasn't as scary as I thought it was going to be. It'd be fantastic if someone created a video walkthrough, but so far as I know, no one has done that yet.
The guide will help you back up your TA Partition where your DRM keys are stored, unlock your bootloader, root your device, and then restore your DRM keys. In order to do this you need to downgrade to Lollipop (if you're not already on it), and then upgrade back up to Marshmallow. It will also install TWRP (which I had no clue was installed until I went into "recovery mode" by pressing UP when I saw the LED flash yellow during boot). There may be an easier way to go about this whole process, but this is the process I used.
Before jumping into anything, I'd hold off until you heard more from firdyRAY or someone more experienced. They may look at the guide I linked and be horrified.
And yeah, I haven't installed xpower yet for the same reasons you haven't. Sounds like there's even an xpower 4.0 that was released recently, but still seems kinda buggy. Being rooted with stock I've been able to give Greenify access to root. Install Adaway (which was worth getting root to begin with). Install sound/music mods like DiVA-X, Viper4Android and Dolby Atmos. Install Titanium Backup. And make a few other minor tweaks (that I've since reversed). I still don't know much about custom ROMs and all that jazz, so I'm holding off until I get more understanding. I'd love to install the xpower ROM (when the bugs are worked out), and maybe some sort of sound ROM. I also need to get more understanding on some of the other vernacular like what exactly a "dirty flash" is.
rajdude said:
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
By unlocking bootloader, you lose DRM keys. There is a way to backup DRM keys which are in the TA partition, but this is to be done BEFORE you unlock bootloader. Good that I have not done anything to my X5c yet.
The next steps for me would be to look into XPower 3 ROM…which I did and here is what I found out:
http://forum.xda-developers.com/z5-compact/development/rom-xpower-v1-0-aroma-debloat-custom-t3371100
First, what's up with the scary looking warning in RED right at the top of the first thread. I did read the OP and the second post, I did not see anything in there which IF I missed will cause my phone to explode! That is probably posted to make noobs read all instructions, right?
Second, I do not see any step in there to backup the DRM / TA partition. I guess the dev is assuming the phone already has lost the DRM, right? So I gotta find instructions on how to backup DRM / TA
Then I searched for problems in this ROM and seems to me that the fingerprint sensor is reported by many to be not working and/or buggy. I rely on the fingerprint sensor day and night. I have many apps which rely on that, like lastpass. That would be a major deal breaker for me.
So going back to stock ROM option…I remember you said "There's a guide that will teach you how to actually root and apply the work around after unlocking your bootloader and rooting."
Could you please post a link to that?
Thanks again!
Click to expand...
Click to collapse
sony ric is a layer of security for sony roms so that they can protect nfc and fingerprint stuff. samsung and htc have there own variants as well.
yes lol the big red lettering is there to make you read, although hes not far off on the melting your phone part, the s810 is ridiculously hot.
the xpower thread doesnt not include the drm backup instructions because: 1) you need bootloader unlocked to flash it. and 2) because it includes the drm fix in it so you dont have to backup your ta keys.
the fingerprint sensor bug is on any bootloader unlocked phone, the hardware fails after x amount of hours and requires a reboot to work again. xpower is a stock rom, the only thing different is its pre-rooted, de-bloated, and deodexed for xposed to work. we have a separate thread for the fingerprint sensor bug and its been solved.
rajdude said:
firdyRAY, thanks a lot for the comprehensive reply to my questions. And yes, it has shed a LOT of light on my doubts.
I googled Sony RIC and dm-verity:
I could not get find much on ric
Dm-verity seems to me a way to check if the boot image has been modified from the last boot, and if it has, stop from booting. Sounds like a good idea until we understand that to flash a ROM dm-verity needs to be bypassed/turned off.
So to compile what I have understood so far:
Click to expand...
Click to collapse
Sony RIC main function is to disable /system write even you got root permission(you still able to do /system write but after a reboot will restore to original). There is a workaround but very trouble, TWRP recovery file manager can bypass Sony RIC(it works in the old day for me, not sure about now). BTW, all 3rd kernel should be disabled RIC nowadays. For any regular computer, there is no hardware or software lock to prevent you gain root access in linux but there are many such trouble stuffs in the android world... lol
I'm running XPower 3.0 Full as a daily driver since June and been very happy. Battery life, stability and speed is good.
Please note, that you MAY lose your warranty when you lose your DRM keys. That's why I didn't unlocked my phone before there was a way to backup TA partition. Now I'm after warranty repair, and before it I was able to fully restore stock ROM with DRM and all features fully functional. In my country, there is only one Sony approved repair center and they check DRM keys before repairing anything - even if it's mechanical fault.
When I had Z1c in KitKat days, it didn't had dm-verity and Sony RIC. It was possible to gain permanent root with bootloader locked, so I was happily using stock ROM and kernel. In Z5c case, first thing I tried was to do the same and it was possible (just backup TA, unlock bootloader, and flash TWRP with patched kernel (dm-verity and Sony RIC disabled) to begin with), but going XPower way was much more confident - I didn't had to think about removing every bloat app. I just flashed lite version in June and I'm using it till this day without any problems at all
Another thing is that you lose OTA (Over-The-Air Update) functionality when you unlock bootloader and disable Sony RIC and dm-verity. Updating to newer versions of firmware, even on stock ROM is problematic when you modify it.
michuroztocz said:
Another thing is that you lose OTA (Over-The-Air Update) functionality when you unlock bootloader and disable Sony RIC and dm-verity. Updating to newer versions of firmware, even on stock ROM is problematic when you modify it.
Click to expand...
Click to collapse
It's simply not possible. If you are rooted you can't apply OTA updates and neither should you.
flopower1996 said:
It's simply not possible. If you are rooted you can't apply OTA updates and neither should you.
Click to expand...
Click to collapse
That's just what I wrote - just put it in another words
Stock Pixel/Pixel XL Kernel + SafetyNet Patch
Current version: android-9.0.0_r0.111
Suitable for build(s): August 2019
Suitable for devices(s): Pixel XL (marlin) | Pixel (sailfish)
I compiled the stock kernel for the Pixel/Pixel XL and applied the SafetyNet patch by sultanxda. The kernel name says marlin, but this also works on sailfish. Google just created one kernel that works on both sailfish (Pixel) and marlin (Pixel XL) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay and Netflix.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is only for the builds listed above!!!! This will not work on any prior build.
- All stock features will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the stock kernel, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Be prepared with backups or the factory image from Google in case you do something wrong
- Extract kernel from zip file
- Test with command: fastboot boot <filename>
- Flash with command: fastboot flash kernel <filename>
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
The current version will always be attached to this post. Older versions can be found HERE.
(shamelessly copied from Sakete's kernel for the Pixel/Pixel XL, which is no longer being maintained. Thanks for the inspiration, Sakete!)
Wow. I literally just compiled the patched kernel myself just now. What a ninja! While I'll be running my own, thanks for posting this so I didn't have to
For those who already downloaded the kernel, I checked and saw a new mr2.1 update so I've attached an updated kernel.
iissmart said:
For those who already downloaded the kernel, I checked and saw a new mr2.1 update so I've attached an updated kernel.
Click to expand...
Click to collapse
Mine is based on that but mr2 and mr2.1 have the same commit so I'm pretty sure it's the same kernel.
Cheers
I'm running a pixel on the nof27b build I don't really want to flash a new kernel would it be possible for you to make the patch a flashable zip
Cardflip said:
Mine is based on that but mr2 and mr2.1 have the same commit so I'm pretty sure it's the same kernel.
Cheers
Click to expand...
Click to collapse
Good catch, I didn't look that closely before recompiling but they are indeed the same. Oh well! Maybe I'll start going off of tag names instead of branches...
ipeedalil said:
I'm running a pixel on the nof27b build I don't really want to flash a new kernel would it be possible for you to make the patch a flashable zip
Click to expand...
Click to collapse
Curious - what difference is there between flashing a kernel using fastboot and using a flashable zip? Isn't the end result the same?
iissmart said:
Curious - what difference is there between flashing a kernel using fastboot and using a flashable zip? Isn't the end result the same?
Click to expand...
Click to collapse
I think he's asking for the patch itself to be a flashable zip so he can patch the boot image while it's already compiled and on the phone. Which AFAIK is impossible
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I was thinking the same thing, That K is for the Verizon model. good to know.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I'll look into it tomorrow!
Thank you.
puertorecon said:
We need one for the Non-Verizon models (N2G47E) & (N2G47J). This modified kernel is only for the Verizon version. If you can compile two more versions for Non-Verizon builds.
Click to expand...
Click to collapse
I believe the kernel would still work.
It looks like the same kernel is used among NHG47K, N2G47J, and N2G47E, so my patched one should work for all of them. I'll update the post.
I'm just curious... So assuming you have the Google version and the oem unlock switch is fuctional and turned on, if you are not intending to root the device why would you unlock the bootloader? I mean you can always unlock it if you want or need to root, right?
bobby janow said:
I'm just curious... So assuming you have the Google version and the oem unlock switch is fuctional and turned on, if you are not intending to root the device why would you unlock the bootloader? I mean you can always unlock it if you want or need to root, right?
Click to expand...
Click to collapse
In the past I would always root or install a custom ROM on my phone. I would like to with the Pixel, but I want to keep Android Pay since I use it almost daily and I haven't been satisfied with the root solutions I've seen for the Pixel so far. It seems like Google is doing a good job of making it difficult to root, given the three or four different ways to root a Pixel that I've seen. Also, with the advent of monthly security patches I would imagine it is a growing headache to unroot, flash the update, then re-root each month. Google has also done a great job with the stock experience on the Pixel that the reasons I'd root are fairly minor.
It's also just been a habit of mine that the first thing I do with a phone is to unlock the bootloader. I don't like the idea of artificially restricting full access to a device, whether it's software or hardware. Plus I don't have to deal with the silly anti-theft checks that people encounter when they wipe the phone and sell it legitimately (like with Swappa or eBay). There was also a time when Nexus phones would bootloop after receiving an OTA, and if you weren't already unlocked before the OTA hit you'd be stuck with a bricked phone.
iissmart said:
In the past I would always root or install a custom ROM on my phone. I would like to with the Pixel, but I want to keep Android Pay since I use it almost daily and I haven't been satisfied with the root solutions I've seen for the Pixel so far. It seems like Google is doing a good job of making it difficult to root, given the three or four different ways to root a Pixel that I've seen. Also, with the advent of monthly security patches I would imagine it is a growing headache to unroot, flash the update, then re-root each month. Google has also done a great job with the stock experience on the Pixel that the reasons I'd root are fairly minor.
It's also just been a habit of mine that the first thing I do with a phone is to unlock the bootloader. I don't like the idea of artificially restricting full access to a device, whether it's software or hardware. Plus I don't have to deal with the silly anti-theft checks that people encounter when they wipe the phone and sell it legitimately (like with Swappa or eBay). There was also a time when Nexus phones would bootloop after receiving an OTA, and if you weren't already unlocked before the OTA hit you'd be stuck with a bricked phone.
Click to expand...
Click to collapse
Ok, fair enough. As I said I was just curious as to the reasoning. But what do you mean by anti-theft checks? I've never sold a phone so I don't really run into anything like that. But if you ever did need to sell it and you could unlock it at a moment notice wouldn't that suffice? I have a Verizon model locked bl so this is all rather moot to my situation, but I do have a 5x that I can unlock if I had to. I like the idea of being able to toggle the oem switch even though I would still remain locked. Something about being able to flash a factory image that I like. Thanks for your reasoning. Not that I agree or disagree with you entirely hehe. Personally, I just like the security of not being able to access my data if it's ever lost or stolen, but I suppose a concerted effort would get in.
bobby janow said:
Ok, fair enough. As I said I was just curious as to the reasoning. But what do you mean by anti-theft checks? I've never sold a phone so I don't really run into anything like that. But if you ever did need to sell it and you could unlock it at a moment notice wouldn't that suffice? I have a Verizon model locked bl so this is all rather moot to my situation, but I do have a 5x that I can unlock if I had to. I like the idea of being able to toggle the oem switch even though I would still remain locked. Something about being able to flash a factory image that I like. Thanks for your reasoning. Not that I agree or disagree with you entirely hehe. Personally, I just like the security of not being able to access my data if it's ever lost or stolen, but I suppose a concerted effort would get in.
Click to expand...
Click to collapse
If a locked phone is wiped/factory reset then only the Google account that was previously on the phone is allowed to be added back to the device. Tons of people were selling Nexus phones when this change rolled out, and the people that bought the phones were unable to add their accounts even after factory resetting. By unlocking the bootloader it disables this restriction. Yeah, I could do it at the time of selling the phone but there's always a chance I'd forget if I got out of the habit of unlocking the bootloader.
I thought about it a lot - and I've never lost a phone before so I'm OK with having my phone accessible in that regard. If I lose my phone I'll have bigger issues (like 2FA locking me out of my accounts) anyway.
I'm on Verizon, but I intentionally bought the phone from Google just to be able to unlock the bootloader .
iissmart said:
If a locked phone is wiped/factory reset then only the Google account that was previously on the phone is allowed to be added back to the device. Tons of people were selling Nexus phones when this change rolled out, and the people that bought the phones were unable to add their accounts even after factory resetting. By unlocking the bootloader it disables this restriction. Yeah, I could do it at the time of selling the phone but there's always a chance I'd forget if I got out of the habit of unlocking the bootloader.
I thought about it a lot - and I've never lost a phone before so I'm OK with having my phone accessible in that regard. If I lose my phone I'll have bigger issues (like 2FA locking me out of my accounts) anyway.
I'm on Verizon, but I intentionally bought the phone from Google just to be able to unlock the bootloader .
Click to expand...
Click to collapse
I've seen the term 2FA bandied about. I presume that's what you're talking about regarding the lockout. So to clarify, if you don't have an unlocked bootloader you can't sell the device? That seems weird. How do you get your account off? If I gave the phone to my wife she can't add her account?
I've never lost a device either although I have smashed one of them disastrously. But now I have a lot more stuff on the device including some personal pics and videos, password files, banking app and of course AP. I actually think my reasoning was more of like there is so much hacking and theft going on that rather than take a chance let me see what it's like being locked like normal people. It's hasn't been bad at all so far as I'm sure you know since you're not really modded either. I get the OTA on another slot and while it's updating I can use the device and a simple reboot updates it. But the bigger reason is that I got a Verizon model (Pixel 32gb) for $240 and not the $650 the Google one would have cost. I'm not sorry although I will revisit that once the Pixel 2 is released. Black Friday is your friend. I would even have bought the Google Pixel for $350 if they had a deal but they didn't. With a fully functioning 5X I just couldn't justify the full price.
Hmm I extracted the file and used fastboot flash kernel kernel_marlin-3.18-nougat-mr2.img and it gives me an error "error: cannot load 'kernel_marlin-3.18-nougat-mr2.img"
coldconfession13 said:
Hmm I extracted the file and used fastboot flash kernel kernel_marlin-3.18-nougat-mr2.img and it gives me an error "error: cannot load 'kernel_marlin-3.18-nougat-mr2.img"
Click to expand...
Click to collapse
After extracting the file I just renamed it to sailfish-image and used that in the command fastboot flash kernel sailfish-image. Flashed fine.
Sent from my Pixel using XDA-Developers Legacy app
Hey guys, I just bought my RN10 and am waiting for it to arrive. My plan is to turn it into a DeGoogled phone (Custom ROM + MicroG) to use as a daily driver.
As someone who has no experience doing such a thing, but who has been familiarizing oneself with the topic and keeping up with this thread for a bit; I have a few questions that I was hoping I could get some help with:
1.
Is the 168 Hour waiting time a guarantee, or are there some of you who didn't have to wait that long?
-----
I plan to root the device, to pass SafetyNet, get Aurora Services, get Bromite Webview, maybe install oandbackupx, etc...
2.
What is your experience with Aurora services and Bromite Webview?
Do these (+ magisk and microG) need reinstalling after updates?
What is your preferred backup solution? I plan to back up to an SD card.
-----
I will try out some ROMs at first to see what works best for me, before I settle on one. But I am not sure if I can just use my backups from say CrDroid in DotOS for example.
These are the ROMs I am leaning towards (in order of preference): DotOS, CrDroid, and LOS:
3.
What should I be aware regarding backups when trying these ROMs? Can I use backups in different ROMs? Does it apply to oandbackupx or just TWRP ones of data partition?
Would you say they are stable enough for daily driving? (I am aware there are some minor bugs like video recording - not a problem for me)
-----
I am aware that TWRP is in alpha for the RN10 bc of the A/B partitioning system, and that it will be a long time for a stable version to come out.
Once I set on a ROM, I will wait until a stable version is released before I do updates.
4.
What should I be aware of when using TWRP? (specially this alpha version)
-----
I use Ubuntu in my system, and I wonder what is the best approach to Unlock the Bootloader and install custom ROMs there.
5.
Is anyone in this thread also using Linux? What is your experience?
What do you guys think of XiaomiTool V2? Is it reliable?
Or would you guys recommend doing these procedures via fastboot and adb? (android-tools-fastboot & android-tools-adb)
1.
there is no way around 1 week waiting. if you are unlucky you might have to wait another week. this might happen when you didn't use the phone enough in this week period, or if you reset the mi account.
also, from this unlock faq: https://c.mi.com/thread-2262302-1-0.html
If you're facing "User Portrait Scores Too Low Or Black", please create or use a new Mi Account to unlock.
Click to expand...
Click to collapse
what that means can only be speculated. in worst case this means, if you cover your camera so it is black, or if you have low light conditions in your drawer where to phone lies, or at the moment you press the unlock button, you can't unlock your phone.
or if the front camera can't recognize a face with its AI, so the portrait score is too low, it also might not unlock your phone. or if internet is blocked so it can't send the data home.
imho, this is a privacy nightmare, but there are no details anyware and everybody just seems to accept this insanity.
2.
I don't use aurora services, but webview browser work very well and magisk+microG does work if you get it installed once (this can be tricky because you have to find the right versions and variations that work together). if you choose a ROM that allows signature spoofing it isn't so much trouble, otherwise it gets more tricky. The rest works pretty easy with latest Magisk and MinMicroG (other microG variants I had trouble with).
You always have to reflash: 1) custom 3rd party recovery (like twrp), 2) Kernel, 3) magisk if you flash another ROM. this is always the same on every custom ROM.
3.
nandroid backup and restore is messy with TWRP currently. best way is to do backup with oandbackupX as root and/or a nandroid /data backup without encryption pin. backing up system is useless. in case of restoration install fresh ROM, start it up once for setting up encryption of /data, then restore /data partition.
you can't move /data partition between ROMs, you have to backup your apps with oandbackupX or the like.
nandroid backups on ext. SDCard currently don't work. better make space on your internal memory.
4.
TWRP is currently buggy or features not working correctly. don't expect anything that worked before in non virtual A/B environments to work perfectly fine here. upgrading was always tricky due to A and B slot changes, but thats not all a problem of TWRP but of the ROMs too.
Just read the older posts in the threads of CrDroid and LineageOS and TWRP and you will learn a lot what works and what doesn't work.
5.
Just install a virtual PC with windows 10 and use everything related to Xiaomi software in there. (most things are windows only). you can bridge your usb connected phone to the virtual PC.
There is no need for XiaomiTool V2 if you are on custom ROMs. just use fastboot/adb commands as needed.
1.
I plan to cover the front camera and not register the fingerprint scanner until I get a custom ROM on it. So I will discover if that is the case or not and let you guys know here.
2.
What is the best way to install microg? magisk module or flashing it via TWRP? I am under the impression one can go both ways about it.
having to flash the kernel is news to me. is there any post in this sub that I can read more about it?
3.
Okay, I will stick with oanbackupX for the time being then, and read about nandroid.
And could you further clarify what you mean by SD cards not working? Is it only for backups or at all? Does that apply to oandbackupX?
4. thanks I will read those posts. hopefully a stable is out soon though.
5.
I have a notebook that I am not sure is capable enough of running a Win VM. So i would really prefer to do these things on my Ubuntu install if I can. Plus it would be a peace of mind knowing i have all it needs and I am not dependent on having Windows machines near me should I have an emergency with the phone.
Is there any issue with XiamiTool V2? Would it not work to do the things i am trying to do?
Thanks in advace for your reply, they are very clarifying in getting me started on this!
best of luck with unlocking. hope you won't need another week. remember both cameras are eligible for face recognition and brightness measurement.
the way of installing microG may be different for each variation, ROM and phone (remember virtual A/B devices, read-only system, etc.). best way is to read the official installation manual that the microG variant provides. on virtual A/B devices you flash almost everything in Magisk with magisk-modules so you get a systemless patched system. the only thing you flash in recovery, beside kernels and other recoveries maybe, is actually magisk.
about kernels, just read the threads about the two released kernels so far.
well, you might be lucky if you try running the xiaomi software using wine, but it might not work. blame Xiaomi for not releasing all the wanted tools for all OS's.
for unlocking keep in mind that you don't change your setup, keep the same virtual PC, tool, data, etc. in place and don't change anything, they collect also PC data (os, hardware, ip - keep IP the same on PC and phone while unlocking!) for the unlocking process (also a privacy nightmare).. if you want to mitigate that you have to build much more around it than just a virtual pc, though.
I didn't use Xiaomi Tool so I can't really answer that. I think the software is outdated and it's main purpose is to remove some but not all bloatware on non rooted stock rom devices. you can do everything without that tool.
keep in mind that these are unofficial tools and there are many of them, and there are many fake ones uploaded to sharehosters which might be infected with malware. it's hard to find the right sources (but check the official sticky posts in this forum for links) and if you get all these tools by googling around chances are high you get some modified versions with malware.
I'd recommend doing things manually and learning step-by-step how to do things.
Oh damn, I will definitely cover the back camera after I test it then. Thanks for the heads up.
regarding flashing the kernels, I understand it now. I thought I had to reflash the stock kernel every time. silly me
keep IP the same on PC and phone while unlocking!
Click to expand...
Click to collapse
Do you mean keep the phone connected to the same wifi as the PC during the waiting period? bc otherwise I don't think that is possible at all, given that one must turn off wifi and use carrier data to add the Mi account to device.
I am not sure I understand what you mean :\
And the main purpose of the tool is to unlock bootloaders, install custom ROMs, etc. But you are right, latest version is one year old and I would like to avoid it if I can. Also there are 'official' links to download it from the Github page or the tool website.
I'd recommend doing things manually and learning step-by-step how to do things.
Click to expand...
Click to collapse
I agree with you, I will likely do the bootloader unlock procedure on Windows and then install TWRP via fastboot/adb on my Ubuntu laptop, and move on from there. I believe it is possible to do that much on linux right?
regarding the IP, I have the suspicion that they (xiaomi) rate the IPs that you use and for some they might block the unlocking attempt. VPN, TOR and other proxies might be suspicious to them and they might block them (this is not necessarily true for all VPNs, TOR nodes, regions, etc., though). There should be no problem with your default ISPs IP address however, but you'll let your pants down using them.
First unlocking on your phone has to be with mobile data, but you could also use VPN,Tor,etc. there, thats why I'm saying it. Some people I've talked to went as far as buying burner sims just for the unlocking process because they are afraid of what china does with their data.
there should be no problem at all if you use normal mobile data for phone Mi account and your default ISP ip on the computer with the unlock tool. They just spy monitor your phone for that week (until you delete the crap) and if the score is good you are good to unlock the phone. nobody besides them knows exactly what they do but you get a clue when you read their Terms of Service. if your ip address varies geographically very much in this week it might also look suspicious, or if the ip-range is used for many different unlocks. all that obviously plays a role in the score at the end.
ok, I didn't use any other tool for unlocking the bootloader than the original and official xiaomi unlock tool. all the rest can be done without additional tools.
the only things you might need is actually MiFlash (to reset/reflash factory ROMs), MIFlash unlock for unlocking the bootloader, and the latest fastboot+adb versions for all the rest.
fastboot+adb requires the correct phone drivers to work on windows, it might be the same on linux. if they are also available for linux it should be ok. for fastboot try the official general android drivers provided by google, they might also be available for linux (or are already implemented)
I was planning on getting a burner for this. but given the covid restrictions in where I am at, it is gonna be a hassle.
I think Xiaomi does most of that because of the people who buy their phones from China, unlock them, put a custom rom and resell them. I think I should be in the clear though, I wanna get a custom rom working asap, so I wont try using tor and vpn and risk it.
I really don't plan on reflashing the stock rom ever again, unless I absolutely need to. I think i read that there are some cases where one must reflash the stock rom in between custom rom installs(?), but I hope that it is not the case for me. I only plan to try dotos and crdroid, maybe los.
and I would think there is a way to get the drivers for Linux, given that xiomitool v2 does get drivers from somewhere and its available on Linux. I gotta do some digging here though
Hi, I just changed the battery on my H930 (Italy) and it's back to life. I kindly wanted to know, starting from the already unlocked Bootloader and from an LG Pie, if there is a custom rom, even if not very recent, without any bugs, which retains all the main functions (in particular Hi-Fi DAC, NFC, photos, Wi-Fi, bluetooth ,etc). Furthermore, I would need to use payments with Google Pay and therefore bypass the related checks. If someone can give me a hand of help ... eternal gratitude!
Stock Pie ROMs have been known to be poorly setup by LG. Since they have discontinued their development, these will not be fixed.
In the USA, custom ROMs don't work with VOLTE or VOWIFI... which is why I always recommend stock for USA phones to retain this capability. I don't know if Italy/Europe has any of these issues.
For these reasons, I have always recommended stock Oreo ROMs here in the USA, as these were the most stable and worked well. I have since left my V30 phone but it still has Oreo on it (and still works). For US users, I often recommend US998 ROMs as these work for most carriers (including international). So I might suggest that one to start.
As for GPay, they have gotten quite advanced with root detection. I would recommend skipping root if you can, of course. If you cannot, then I did use Magisk Hide in the past and it worked for me, but that was a few years ago, so I don't know if that works anymore. I would advise NOT using Xposed, as this was being detected as well... besides which Xposed was causing problems anyway, so I found it was not worth the hassle.
I thank you for the valuable suggestions, I guess I will keep it a few more years with Pie and with Magisk Hide I will try to remove the root. Actually I don't remember rooting it. Is it possible that "security reasons" that don't allow me to load cards depend on unlocking the bootloader?
Yes, just unlocking the bootloader can be part of the detection, even if it's not rooted. You often have to go the next step to root and then use Magisk Hide to make it "safe" from there.
Note, at least on older versions, you had to start with the TWRP install of an older version of Magisk. Once installed, then you can update it (usually) without much problem. I recall doing that myself. I believe the TWRP install required Magisk 18.x, and then I had updated to 20.x. You can check the WTF thread to see what that requires, as those instructions should still be valid.
Another option is relocking the BL, of course.
Also note, I know that at one time I had seen where once you fail the security check, you had to clear data for Google Services or something, and maybe even GPay. Otherwise, it "remembered" that you had failed, and would not recheck. By deleting data, it would force it to recheck, so you may need to do this after doing Magisk Hide. Note that you ay need to hide services as well. Again, I'm saying this based on older info... I don't know if things have changed since then.
clalos33 said:
I thank you for the valuable suggestions, I guess I will keep it a few more years with Pie and with Magisk Hide I will try to remove the root. Actually I don't remember rooting it. Is it possible that "security reasons" that don't allow me to load cards depend on unlocking the bootloader?
Click to expand...
Click to collapse
Yes, unlocking the bootloader will cause the security check to fail because you've broken the front door down. You can now do other things like root and make changes to your phone. They know this, so the assumption is if you unlocked the bootloader you are now attempting to take control of your own phone, and they don't want that.
Thank you again for your helpful suggestions. In consideration that I do not plan to use custom rom I will try to lock the Bootloader