Rooting and flashing Pixel rom - Xiaomi Mi A1 Questions & Answers

Hi,
I have had my A1 since it first came out and thinking of rooting and flashing Pixel OS on it now. I am currently in latest Android 9 and in Malaysia.
I read up some of the other threads about rooting and flashing rom but there seem to be alot of conflicting instructions and alot of ways to root which is making it very confusing for me now.
Any kind soul can point me the most reliable way to root and flashing Pixel rom?
Thanks in advance

The way I did it is unlocking bootloader and then booting twrp via fastboot. From there you can easily install magisk, custom ROMs, kernels, and other modifications.
Remember that if you want to be able to boot to recovery without using a PC you'll need to flash a twrp installer

Related

Unlock Bootloader without wipe? Root? 6.0

Hello,
I am looking for a smooth method to lock and unlock the bootloader on my Nexus Player. Although being it is not a phone I guess I could just leave it unlocked... I am also looking for the best current method to root the Nexus Player on 6.0. I have been searching but I keep coming across guides for lollipop.
Thank you in advance!
Unlock/root guides are similar. They are the same except for the files used.
For Android M - i use fugu-mra58k. Use Chainfire's beta-supersu-v2.51 and it requires custom boot img, can be found on his tread http://forum.xda-developers.com/apps...ellow-t3219344. There is supersu2.52 but im not sure if it will have issues. My NP was already unlocked so I just flashed factory,moved supersu2.51 zip, boot into bootloader and flash twrp and CF's custom boot.img. At this point DO NOT restart NP, just boot it into twrp and flash supersu (you'll need otg+mouse attached). reboot and you should be good to go.

Any root method for C432B380?

I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
SteadyDisorder said:
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
Click to expand...
Click to collapse
Well, ask for unlock code - that's the first step.
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Makishima said:
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Click to expand...
Click to collapse
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Moemen Shahawy said:
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Click to expand...
Click to collapse
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Makishima said:
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Click to expand...
Click to collapse
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Moemen Shahawy said:
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Click to expand...
Click to collapse
I restored a backup of the boot partition I had made when I first flashed TWRP which seems to have deleted Magisk, the app told me it was not installed (even though I see now a Magisk folder in data...) and then flashed Super SU, but I still can't delete system apps and having trouble with Viper*. But maybe it's not SU's fault. I don't know. I flashed v2.79, I previously had trouble with the newest versions.
Also, I had not activated the Hide function, I think.
*It is driving me crazy! Why does it not work? Supposedly I am root, I even deleted the system apps with the file managers but when I exited and reentered the folder they were there again. What is going on?... Wait... Is this normal, is it because it is system-less root?
To root any nougat fw:
1)unlock bootloader. You have to get unlock code from huawey and then in fastboot mode do: "fastboot oem unlock yourcode"
2)flash twrp recovery, i suggest you the hassan's recovery https://www.androidfilehost.com/?fid=745425885120756473
3)in fastboot mode do "fastboot flash recovery nameoftherecovery.img
4)reboot in recovery and flash this supersu
It is the 2.82 for emui 5 without loop mount,is perfect for p9lite https://www.androidfilehost.com/?fid=817550096634776377

zenfone 3 with oreo 8.0: unlock, instal TWRP & custom ROM?

I've already unlocked, installed TWRP and custom ROMS on several devices, so i know about fastboot, ADB, USB drivers for my device.
But with zenfone3 it's still pretty confusing for my brains so please be patient with me and explain the following:
I have a new zenofone 3 updated to stock oreo 8.0 already by OTA and i want to unlock, instal TWRP/Root and a oreo custom ROM.
In some guides for unlocking in this forum i read about flashing a RAW image before unlocking. Is this really necessary? If so: what for?
And then after unlocking i read about installing stock OREO again. hmm...
Please could somebody post here short necessary steps for my zenfone 3 with stock oreo 8.0 to instal a custom ROM OREO 8.1 on my device?
Thanks a lot in advance!
nicky-xda said:
I've already unlocked, installed TWRP and custom ROMS on several devices, so i know about fastboot, ADB, USB drivers for my device.
But with zenfone3 it's still pretty confusing for my brains so please be patient with me and explain the following:
I have a new zenofone 3 updated to stock oreo 8.0 already by OTA and i want to unlock, instal TWRP/Root and a oreo custom ROM.
In some guides for unlocking in this forum i read about flashing a RAW image before unlocking. Is this really necessary? If so: what for?
And then after unlocking i read about installing stock OREO again. hmm...
Please could somebody post here short necessary steps for my zenfone 3 with stock oreo 8.0 to instal a custom ROM OREO 8.1 on my device?
Thanks a lot in advance!
Click to expand...
Click to collapse
1) There are 2 ways to unlock
Official- This method is very easy (just download the bootloader unlock apk to unlock but this method will void warranty and you will not get any OTA Updates
Unofficial- This method is safe too, but it requires to flash RAW files (this method retains warranty and you will get OTA Updates)
The reason why you should flash Oreo RAW because Factory RAW can only boot FASTBOOT and touch screen will not work.
Just follow my steps and you can install custom ROM without any issues.

Is TWRP Necessary in order to change rom?

Hello everyone.
I made some test in installing some custom roms in some old devices always avoiding to install TWRP permanently on the drive (i used it in boot mode and then adb listen in TWRP and adb command from PC).
I've done this in order to preserve the stock recovery mode.
I decided to install pixel experience as my default rom in my redmi note 7 and i noticed that this rom will use OTA updates so i'm asking you if i should install TWRP (or other recovery images) permenently in order to make it work properly.
Another question that i have revolves around Magisk, is this tool needed in order to make pixel experience work fine?
BTW i don't understand why TWRP does not officially support RN7 lol (eventually i'll use a porting or another recovery )
Thank you everyone
First, sorry for not answering your main question but I'm more intrigued as to how you can flash a custom rom without using a custom recovery like TWRP. Also, is it possible to permanently install TWRP? How you do this?
Second, Magisk is not needed for the rom but allows some other customizations, fixes and root access.
you need some kind of custom recovery that supports your phone, its what allows you to install roms. There are a few out there such as TWRP, organge fox, etc. Chose whatever you like that has good support for your device.

Pixel 4 issue rooting and installing custom rom

I would like to root and install custom rom on pixel 4 android 12 hoping someone can help me as I’m pretty new to rooting devices. I would like to make my device as secure as possible with a custom rom. I’m not sure if I’m meant to root the device before installing recovery (twrp) and rom or vice Versa. I was able to successfully root it with magisk and when I installed the recovery and rom it got stuck in boot loop. My device has a/b partition and I think that may be the issue. I’m not sure if I’m meant to have it on same partition or if it can be separate.
If some one can give me some advice would be much appreciated

Categories

Resources