Related
I have to start by telling you I am not only a Newbe I am a NO-Knowbee, a complete novice. I am an advanced computer user but smart phones make me fell stupid. So please bear that in mind when offering "how to" advice.
I bought this phone 3 weeks ago as Rooted. I think is was rooted but SuperSU will not start. I get a message that the SU Binary need to be updated. I have two choices. NORMAL which fails and the other is TWRP/CWM which does nothing either but suggests I manually reboot into recovery manually. I have no idea what to do.
Nice mess there ... maybe others have better opinion here but .. the question would be to fine out what version of android you have (aka like windows xp, 7, 8/8.1 etc) then from that point I would almost want to start over ..
Some people have differ opinions on this but my opinion is to start over and re-root the phone. Either they failed on the unlocking boot loader or something and just decided to sell it. (in windows terms they basically corrupted everything).
So the question comes down to is being able to put on custom roms? Depending circumstances you can unlock the boot loader and then install any custom rom (modified OS made for that specific phone, you cant just put anything it has to be made for this phone etc..)
Next question if you can live without going through that (different roms) and want to stick with stock (whats already on the phone) and just want root, then the my opinion would be to just redo everything then re-root it fresh.
Theres a program called Odin that you would use and you would need the stock file to which is currently on your phone and you would need to download it (the file is usually about over a GB in size) and you would need to do that. However telling you how to do that here while its simple this is something you need to read and learn about. Its just like finding tweaks and tips on windows. There's a EXCELLENT help section here and I HIGHLY recommend you read and read more and more. Its like potato chips you cant eat just one. Good luck.
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
Maybe the problem is that I don't know how to properly ask for what I want/need. First off, I am new, so let's pretend I know nothing about modding phones. Second, what I am trying to achieve is the following:
Marshmallow OS or newer (I have lollipop and I highly dislike it)
Complete removal of all AT&T software/bloatware from my M8
Ability to try out different ROMs (are those the same thing as operating systems?) like cyanogenmod.
Those are the highlights to my endgame.
I have found there are several steps to this, and it seems like each step has at least one prerequisite or sub-step and I get overwhelmed when reading up on how to achieve the above goals. Feels like I'm doing taxes for a poorly run business. Apparently I need TWRP on my phone. No clue why or what it does. In order to install it, I need to have root access or a previous version of TWRP already installed, or I need to install the SDK tools package, and from that, only install fastboot and adb. Then after that I need to already have some type of drivers on my PC for that to be useful. Like I said, it is overwhelming to someone who does not know all of the lingo. Especially when I know that if I mess up at certain intervals, I could very well turn my phone into a shiny paperweight or small cocaine tray. Anywhere I have read up on this, when it says download/install _______, I cannot determine whether that means download/install on my PC, or on my phone, bc it doesn't specifically say what goes where in every instance. To make matters more difficult, I do not have an internet connection other than on my phone. Anything that needs to go on my PC, I have to download it to my phone first, then transfer it over, then install it. I asked once for a step by step tutorial or a link to one, and I was given something that was just as confusing as what I have already found. These tutorials seem to be written for ppl who know a lot by ppl who know a lot. I am not one of those ppl. I am a green noob, still wet behind the ears. I apologize in advance for not knowing, but I am just not at the level where I can guess which things go where and If I temporarily render my phone unusable, I won't be able to easily go online to find the fix, nor will I be able to download anything else, if needed. Would greatly help me if I had a list of ingredients needed before I begin, and a sequence, much like a recipe for a cake. Again, I apologize for not knowing, and I'm sure all of you reading this were, at one point, uneducated on the matter. Thank you for any advice and/or reading my TL/DR post.
See my responses below, in red font:
Damagj said:
Apparently I need TWRP on my phone. No clue why or what it does. In order to install it,
TWRP is a custom recovery, and what that is, is explained in "that" thread I linked you to: https://forum.xda-developers.com/showthread.php?t=2744194
Think of TWRP as a kind of small installer program and backup/recovery tool. You need it to flash custom ROMs, and you can also use it to backup the current ROM. It's not used within the Android OS, but rather you can boot into it separately. Which is obviously handy, if for whatever reason you can't boot to Android OS, and need to "recover" (restore the OS).
I need to have root access or a previous version of TWRP already installed, or I need to install the SDK tools package, and from that, only install fastboot and adb. Then after that I need to already have some type of drivers on my PC for that to be useful.
Don't go by the install instructions on the TWRP website, they are not device specific (to the M8) and may misguide you (every Android device has it's own nuances).
To install TWRP, you need to unlock the bootloader. The bootloader is "locked" by default, which by definition means you cannot install a custom recovery. The following is a good step-by-step guide to unlock the bootloader and install custom recovery. Note, that you do not need to root, in order to install TWRP, or flash a custom ROM. So stop before you get to the step of root (flash SuperSU). Also, the version of TWRP you install should be current (3.1) or alternately 2.8.7 (which is a known "old reliable) version).
https://forum.xda-developers.com/showthread.php?t=2799796
Like I said, it is overwhelming to someone who does not know all of the lingo. Especially when I know that if I mess up at certain intervals, I could very well turn my phone into a shiny paperweight or small cocaine tray.
No, you actually can't. Your fear of bricking the phone (permanent damage) is unfounded. As with s-on, this phone is nearly impossible to brick. The phone is fully recoverable even if you screw up; since for what you describe, you are only touching a limited number of partitions (system which is the OS, and recovery). As long as you don't mess with "critical" partitions like hboot and radio, you can't actually brick this phone. And those partitions are actually protected, and you can't modify them even if you wanted, unless you s-off. So all the more reason to stay s-on, as I described in the other thread you posted in here: https://forum.xda-developers.com/showpost.php?p=74107487&postcount=100
To make matters more difficult, I do not have an internet connection other than on my phone. Anything that needs to go on my PC, I have to download it to my phone first, then transfer it over, then install it.
but I am just not at the level where I can guess which things go where and If I temporarily render my phone unusable, I won't be able to easily go online to find the fix, nor will I be able to download anything else, if needed.
That part is difficult. While possible, doing what you describe is somewhat risky with no other device for internet. At some point, it's almost inevitable for anyone tinkering these phones, that something will go wrong. Either you forget a step, or you can't boot for no mistake of your own, at all. Even having done this stuff for years, it still happens to be, once in a while. It just happens. So without a way to ask for help, or download files, you can get stuck in a bad jam. You'll need to have some backup plan, even if it's a friend or family, letting you use their computer as a last resort.
Click to expand...
Click to collapse
Stick with it. Keep reading up, and trying to learn the basic terms, concepts, tools, and methods. I know it seems overwhelming, but it will all start to make sense. You really can't (and shouldn't) try doing these things, until you have some basic understanding. You wouldn't ask someone to tell you how to tear the engine out of a car, without knowing how any tools work, or what any of the parts of the car are called.
I would also suggest you refer to my (AT&T M8) index thread. It has a lot of links and basic info, you may find useful: https://forum.xda-developers.com/showthread.php?t=2751432
Hello, until now I avoided to root my device (SGP612 / Stock Marshmallow), because I did not want to risk to lose the drm-keys or do other damage.
Besides that, there some apps, which will not run on rooted devices as netflix (at least I suppose so).
Now working on Tasker and other tools the demand of root is increasing more and more. But still I want to take it restrained and looking for a way to limit the root via ADB. I'm not sure, if that is possible, but I think, that would be a good compromise. Online I found a huge amount of guides and threads "how to root", but all of them, at least it looks like that, ending with an unlocked bootloader, TPRP, SuperSU and so on. I did not read all of them, because that would take years and these guides may also be outdated or even worse incorrect.
Therefor I'm here to ask you about yours assessment.
My main goal would be to:
- Make a full backup
- Protect the DRM-Keys and other irreversible stuff
- No app should be able to detect that the device has been rooted respectively modified on system-level
- Void a reset of the current setup
- Install some apps to system via adb and grant some permissions, uninstall few oem-apps
- Tweak a few settings via adb
Is that possible? And if so, are there some good and simplified guides, which I should read?
Wrong forum. This is for Z3 Compact phone. What you want is https://forum.xda-developers.com/z3-tablet-compact
You can root the phone without unlocking the bootloader, so I would assume that you can do the same with the tablet. You have to flash with an older ROM/kernel first, though, but it is doable.
temporary2010 said:
Wrong forum. This is for Z3 Compact phone. What you want is https://forum.xda-developers.com/z3-tablet-compact
You can root the phone without unlocking the bootloader, so I would assume that you can do the same with the tablet. You have to flash with an older ROM/kernel first, though, but it is doable.
Click to expand...
Click to collapse
I will ask the moderation to move my thread, thanks for the hint.
That sounds complicated to flash an older ROM, especially if no suitable instructions are known to me.
BTW. I prefer to stay at stock.
I am pretty sure you posted in the right forum. Everything you mention is possible, except making a full backup. I wouldn't know how without root or twrp. You can backup your TA partition with a special tool to save your drm keys. It uses the 'dirty cow' exploit so you may need to downgrade first (which wipes your data).
I think root via ADB requires a custom rom. You need to unlock your bootloader, which wipes all data. Alternatively, you can root your device with Magisk. It can hide itself from detection for a set of apps that you select.
M1chiel said:
I am pretty sure you posted in the right forum. Everything you mention is possible, except making a full backup. I wouldn't know how without root or twrp. You can backup your TA partition with a special tool to save your drm keys. It uses the 'dirty cow' exploit so you may need to downgrade first (which wipes your data).
I think root via ADB requires a custom rom. You need to unlock your bootloader, which wipes all data. Alternatively, you can root your device with Magisk. It can hide itself from detection for a set of apps that you select.
Click to expand...
Click to collapse
The thread has been moved by now, so that should be ok.
But still, I do not want any custom-rom. My experience with such on other devices in the past was very frustrating and a waste of time. Had always stability issues on driver-level and other misbehavior. On one samsung device I tested around ten or more roms and all of them was quite ****ty...
And until now it sounds like, I need to install a custom before I even can start to make backups and such. But I want a backup of the status quo, to which I could always rollback, if things gets ugly.
I like the current stock, is a good and stable base, a few tweaks and it would be perfect for me. Of course, I did not test any customs on my current device to be able to make some substantiated conclusion on that but I'm to distrustful to follow this path, especially not when there is no way back.
I miss any imagination what is possible and what is not, or what effect a particular measure entails. Therefor I can't estimate the accuracy of any guide and there are hundreds of them out there, and it looks like the approach is sometimes different. I started reading some of them, but stopped it because I could not retrace the content.
Can you recommend a good guide, which could work out for me and whats the name of the tool to backup the drm-keys? Thanks...
Check here for the TA backup https://forum.xda-developers.com/cr...rsal-dirtycow-based-ta-backup-t3514236/page47
I am very happy with this rom, the developer recently issued a Pie alpha (which I haven't tried yet)
https://forum.xda-developers.com/z3...m-aicp-android-ice-cold-project-o8-1-t3731197
There's a guide for rooting + recovery @ https://forum.xda-developers.com/z3...to-rooted-lollipop-locked-bootloader-t3083980
Be sure you follow the instructions very carefully, since you are flashing (the system partition) with the ROM from a Z3 phone.
The process is similar to the Z3 phones:
- flash to an older ROM
- root
- install custom recovery
- using custom recovery, flash with a prerooted, updated ROM
No need to unlock bootloader and no need for custom ROMs.
Asides from that, I don't know how to do the rest of the stuff in your list.
(I'm debating on getting a used Z3t, which is why I'm researching root possibilities .)
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