Hello! i have used the search tool to see if there is a custom recovery for my device but i am unable to find any. I found TB-X103F custom twrp but im unsure about trying it!.
I may be rather early as this tablet only recently came out.
Lenovo X 104F- 1 GB RAM
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
Care to share any links?
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
kpfx said:
Since Lenovo/Motorola added our E10 / TB-X104F to the recovery tool I decided to play around with hacking apart this awesome and terrible table. Long-story-short... you can unlock it using the normal FASTBOOT commands. A MAGISK modified BOOT.IMG does work which gave me full root access to the tablet. If people are interested I'll write up a guide... but a little bit of research on MAGISK and grabbing the Lenovo recovery tool will be your first step if starting from scratch.
Next step is getting a recovery image. I'm currently looking into getting this tablet into the TWRP BUILDER queue, but at the time of this writing their queue is full.
UPDATE: Just saw the TWRP BUILDER team has had everything on hold for over a month now. Guess I'll need to see about building this locally in my free time.
Click to expand...
Click to collapse
I've been looking for one also and was gonna see about working on one
Artarun said:
I own the same tablet , found also a solution to root it . Just to try other Custom ROMs you do not need to root it ....it is project TREBLE compatible ! This means that you can , with fastboot and ADB , install various GSI images )
ATTENTION : this method does not allow you to go back easily to the factory ROM !!! If you wish to do so, you need to root your Tab and make a full backup with one of the solutions described here in XDA ! Titanium or so .
I have installed Lineage 15 (Oreo 8) on my device and it runs without any problem ......Custom ROMs based on Pie make still some issues ! Be aware , that for one or other reason on my tablet i can install only ROM that is less than 1 GB after unzip !!!
Click to expand...
Click to collapse
I can attest to this, I flashed the last Resurrection Remix Oreo GSI (12/21/18) and a (Magisk) rooted kernal I got from firmware (Lenovo MOTO Smart Assistant). And so far everything seems to be working fine.
So I also flashed resurrection remix pie gsi... it works as well... only thing is it doesn't come with gapps... and without twrp i can't flash a gapps package. The resurrection remix I used was the final oreo build... zt has gapps pre-installed... you have to register the device with google because it is not certified... but after that everything seem good. One thing to mention is both the oreo and pie builds are "go edition" so some features are missing because of that... one in particular I noticed is notification access for 3rd party apps... go edition devices don't have that feature
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
44Guest said:
Do either of you all have a step-by-step guide to rooting the device and installing either the Lineage or RR ROM?
Also, what works and what doesn't on the tablet afterwards?
Click to expand...
Click to collapse
Use Lenovo MOTO Smart Assistant to repair your tablet (you wont actually repair tablet, just using to get firmware)
Follow steps to get to download the firmware (it will save to ProgramData folder, its hidden folder... in widows anyway)
Take the boot image (boot.img) from firmware folder and transfer to storage on tablet
Instal magisk manager and use to patch the boot image you transfered from computer
Transfer patched boot image back to computer
Download the latest oreo gsi for resurrection remix or lineage
Use fastboot to unlock bootloader
Use fast boot to flash gsi
Use fastboot to flash patched boot image
Google anything you need help with...
I used the resurrection remix oreo also because there is a build that has gapps pre-installed... the pie version works but doesn't have gapps pre-installed and without twrp I couldn't find a way to install them
After tablet boots up install magisk manager and you will be rooted
You will need to register your device with google because it will not be certified... that was a pain to get done even though the process is pretty straight forward
So far only "issues" I have encountered are not actually issues they are due to the fact that the resurrection remix gsi is android "go edition" I haventr tried lineage because I like the customization options that resurrection remix offers
Here is the magisk patched boot image I made so you can skip that part...
https://www.mediafire.com/download/x4d3xp8w3e8bw3g
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
4niner4 said:
Just to confirm the sequence of events (and thank you for the magisk-altered file):
1. Move magisk-modified boot image to the tablet.
2. Download latest version of Lineage OS or RR; move that file to the tablet as well
3. DL magisk manager APK and move that to the tablet as well
3. Boot the tablet into Bootloader and flash the new OS file first
fastboot flash recovery file.img
4. Then flash the boot.img altered by magisk
fastboot flash recovery boot.img
5. Reboot the tablet (will it load with the new ROM?)
6. Install magisk manager
Questions on the flashing:
A: Do you flash the .img and the ROM through fastboot shell command on your computer or do you install them in recovery mode?
Click to expand...
Click to collapse
So you want all files on the computer at first...
When you unlock bootloader it will wipe the tablet.
Flash the the gsi image then the magisk patched boot image using fastboot (there are instructions on xda regarding flashining gsi... you have to wipe system before flashing)
After tablet reboots to resurrection remix move the magisk manager apk to the tablet and install it... open magisk manager and you should have magisk installed giving you root and so much more.
Before you attempt this make sure you familiarize yourself with all the steps... search google/xda.
Also... I will say this... I tried to just root the tablet first but it wouldn't boot after so I tried to fix it using the Lenove tool and it failed... flashing the resurrection remix gsi with the patched boot image saved me from a lot of headache and wasted time... I would prefer if it was not a "go edition" rom but its still better than stock.
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
4niner5 said:
Sorry, more follow-up questions:
1. My bootloader is unlocked. It did not wipe the device (I used the "developer options" in the "Settings" menu to do it. Fastboot indicates the bootloader is unlocked. Do I need to redo unlocking the bootloader? For what it's worth, all my attempts to flash everything with my presumably unlocked bootloader have been unsuccessful.
2. Where did you find a .gsi of Lineage OS 15 for the Lenovo TB-X104F? I cannot find one.
Thanks
Click to expand...
Click to collapse
Make sure you fastboot flash unlock and fastboot flash unlock_critical. Just look an here for the links for lineage gsi. It flashes just fine and is super easy. I have resurrection remix on my 104f. I'm trying to compile twrp for it right now but hard to do with kids lol also if you use the lenovo tool you can download the recovery files which has boot recovery and all that in it and you can use magisk to patch the boot.ing and then copy that to the Lenovo tool and replace the stock boot img then recover it and you now have a working patched boot.img. I went through the same thing
Any Luck?
Any luck with that twrp? I'm willing to test it out...
Would like to be able to use the resurrection remix pie rom with gapps. So I can hopefully give some helpful feedback... one warning I am an amateur at anything beyond using fastboot and some adb commands, but I can learn pretty quick if i have the time to spend...
Another warning I have a sub-par windows pc to work with (and its the wife's) it prob can't run Linux in VM.
Disable "go edition" in Resurrection Remix Oreo
Using root explorer...
Navigate to /system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Navigate to /sbin/.magisk/mirror/system
Copy build.prop to internal storage
Navigate to where you saved copy of build.prop
Edit build.prop that you copied to internal storage...
Find ro.config.low_ram=true and change to ro.config.low_ram=false
Save and exit file
Copy edited build.prop back to /sbin/.magisk/mirror/system (make backup of original and overwrite with edited one)
Set permissions to owner read write (rw-------)
Reboot
This allowed me to set notification access again (its disabled in "go edition")
Hey guys, I'm trying to follow the steps in this thread to install Resurrection Remix Pie on the tablet using fastboot but whenever I try to flash a ROM to the system partition I get a (remote: size too large) error.. Does anyone know why this could be? I've tried using flags like -S, I've wiped the partitions and I don't know what else I can try. I have tried with Lineage, AOSiP and RR GSIs.
Thanks.
I cant get this to work.. What version of RR or Lineage OS works with tb-x104f?
up..................
I got the final version of rr oreo running fine... no luck with the latest rr pie unfortunately...
Anyone know if this is an A or AB device?
Related
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
Installing Stock Oreo 8.1.0 on Nexus 6P with Root
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.
dave457 said:
(snipped)
Click to expand...
Click to collapse
Couple thoughts:
1) Please replace every reference of "bootloader" with "boot." Bootloader is entirely different from the boot (kernel). Know the difference if you're going to provide instructions. Using these words interchangeably will cause new users to brick their device because they flashed the bootloader.img when they rarely need to install this. You only flash an image to its similarly named partition on the phone, bootloader does not equal boot.
2) You do not need a custom kernel to get root on Oreo. Your post is misleading. Magisk roots the stock boot image just fine.
3) TWRP will persist between reboots with just the stock boot image rooted with Magisk.
4) TWRP works when you are encrypted. I am unsure why you have a hangup with TWRP and encryption. Are you referring to File Based Encryption which can only be enabled through Developer Options?
5) Why are you making people install a 4 core version of TWRP? If they do not have the BLOD, why force people to use a version of TWRP they do not need?
Sent from my Nexus 5X using Tapatalk
Could you point me in the direction of a beginners guide for this process? I do know it does have a TWRP partition, I do not know which version. My Kernel is 3.10.73- Elemental X4.05 and my baseband in angler 03.78. Any and all help is appreciated.
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.[/QUOTE]
Nice thanks man
---------- Post added at 04:42 PM ---------- Previous post was at 04:38 PM ----------
jam_09 said:
Could you point me in the direction of a beginners guide for this process? I do know it does have a TWRP partition, I do not know which version. My Kernel is 3.10.73- Elemental X4.05 and my baseband in angler 03.78. Any and all help is appreciated.
Hey jam_09
I will help you Install 8.1 oreo
First tell me which career are you using? Is your current rom a career specific or a global one check and tell me .. and I'll instruct on what to do further
Click to expand...
Click to collapse
dave457 said:
Installing Stock Oreo 8.1.0 on Nexus 6P with Root
This is a quick guide on how to install and root stock Oreo 8.1.0 on a Nexus 6P.
The main problem I came across was trying to find a modified bootloader for Oreo 8.1.0, so instead I replaced the stock kernel with ElementalX-N6P-6.01 kernel. This alleviated the need for a modified bootloader. The reason this is required (or a modified bootloader) is to prevent the stock rom from replacing the custom recovery with the stock recovery on every boot. In addition, there is a need to remove the forced encryption of the data partition that is used in MM, Nougat and Oreo. Installing ElementalX kernel resolved both of these issues plus several other benefits including colour calibration plus plenty more.
This is not a beginner’s guide so I will assume you have the correct drivers and SDK tools installed on your PC (or Mac). Perform the following:
1. Enable USB Debugging (Developer Options)
2. Allow OEM Unlock (Developer Options)
3. Boot into download mode and unlock the bootloader with fastboot oem unlock
Downloads
1. Download the official stock firmware, currently “8.1.0 (OPM5.171019.014, Jan 2018, Softbank)” from here https://developers.google.com/android/images
2. Download “twrp-3.2.0-0-angler-4core.img” from https://androidfilehost.com/?fid=745849072291692306
3. Download “ElementalX-N6P-6.01.zip” from https://elementalx.org/devices/nexus-6p/
4. Download Magisk (Latest version) from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Method
Have your phone switched on.
1. Within the downloaded stock firmware file there is a “flash-all.bat” file. Run this batch file. The phone will reboot into bootloader mode and flash the stock image.
2. When finished reboot the phone and finish the setup. No need to set up too much at this point as it will all be erased again shortly. Now you’re on stock rom 8.1.0. Again,ensure the following:
Enable USB Debugging (Developer Options)
Allow OEM Unlock (Developer Options)
At the moment the data partition is encrypted (default with Oreo, Nougat and MM) and this is not good for TWRP or rooting, so this needs to be changed.
5. Boot the phone into download mode, connect to your PC and flash TWRP
fastboot flash recovery twrp-3.2.0-0-angler-4core.img
6. Boot your phone into recovery. TWRP will now load but will ask for a password because the data partition is encrypted. Press “Cancel” in TWRP.
7. Slide the bar to allow modification to the system partition when asked by TWRP.
8. To decrypt the data partition, go to Wipe > Format Data and enter “Yes” in the provided field. It should not take more than a few seconds and then reboot into recovery again. This time it will not ask for a password and you should have access to the storage area of the phone from your PC.
9. Remain in TWRP and copy “ElementalX-N6P-6.01.zip” from your PC to the phone and install it.
10. While still in TWRP, install Magisk.
11. Wipe Cache/Dalvik cache and the reboot into the system.
Extras
• Check the colour calibration within ElementalX
• Viper4Android can be installed via Magisk downloads. Use the version for Magisk 15. It works.
Click to expand...
Click to collapse
dumb question but wanted to check
My bootloader is already unlocked, but if I do the other steps, any data I have on the phone now will be lost correct?
storo1975 said:
dumb question but wanted to check
My bootloader is already unlocked, but if I do the other steps, any data I have on the phone now will be lost correct?
Click to expand...
Click to collapse
Yes because later in the process you are going to wipe the data partion to get rid of the encryption this will erase everything on your phone it is like doing a factory rest.
---------- Post added at 09:31 PM ---------- Previous post was at 09:23 PM ----------
I don't know alot about the newer versions of Android like 6 7 8 but I know I read that if you don't root the first time you install twrp then the stock recovery will over write twrp when you reboot. And I also read that magisk modifies the system img in order to hid root. so you can still use gpay and Netflix and pass the safety net check. So I think installing the custom kernel is an extra step that is not nessesary but on the other hand you get certian perks with a custom kernel. Again I don't know much about the newer modding community so o don't know how stable elementalx is. Without installing it I won't know. I have tried dozens of kernels some were spectacular like those from faux others not so much. Also keep in mind to ur technically not on stock rooted version of Android if you have a custom kernel. It no longer is stock software.
Thank you so much for this thread. I was actually about to make one asking how to get back to stock. I used to love flashing the phone all the time, but it got to the point where I never did anything with customization and got bored of it, so I'd rather just be on stock these days.
hi sorry but how to flash the ziP? through TWRP?
Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
jbonlinea said:
Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
Click to expand...
Click to collapse
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
I am using pixel experience 8.1 oreo rom in my redmi notr 4.and i have also install google canera mod.mgcmod5.i have done all the settings but ehen i am trying to take puctures its force closing and lagging..need solution..
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
After every OTA update do I need to re-flash everything?
ÀnkanKoley said:
After every OTA update do I need to re-flash everything?
Click to expand...
Click to collapse
If RedWolf succeeds OTA survival, then there is no need. But after OTA if RedWolf is replaced by stock recovery, then yes you'll have to flash everything once again. Refer RedWolf thread for more details on OTA survival.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
jbonlinea said:
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
Click to expand...
Click to collapse
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
What would broke on miui camera?
amnher said:
What would broke on miui camera?
Click to expand...
Click to collapse
The HDR mode.
ArK96 said:
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
Click to expand...
Click to collapse
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone
jbonlinea said:
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone pen
Click to expand...
Click to collapse
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
ArK96 said:
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
Click to expand...
Click to collapse
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
jbonlinea said:
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
Click to expand...
Click to collapse
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
ArK96 said:
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
Click to expand...
Click to collapse
Thank you very much !
jbonlinea said:
Thank you very much !
Click to expand...
Click to collapse
No problem.
ArK96 said:
No problem.
Click to expand...
Click to collapse
hum, :silly:
the link you sent for adb do not work
jbonlinea said:
hum, :silly:
the link you sent for adb do not work
Click to expand...
Click to collapse
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
ArK96 said:
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
Click to expand...
Click to collapse
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
jbonlinea said:
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
Click to expand...
Click to collapse
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
ArK96 said:
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
Click to expand...
Click to collapse
Hi dude
I'm almost done but back to square 0, with blinking black screen at boot !
No crisis, I can still go to redwolf recovery, as well as fastboot.
How it happend ?
In magisk manager (on miui) I checked what modules were available in the download panel, and tried "Google Pixel 2 Experience" or something similar.
On reboot, the mi logo is displayed, then I have a black screen blinking on and off, without mi logo, just black, on and off
I thus wanted to unistal the mod with magisk module uninstaller, but the install fails and return that "magisk is not installed" and "magisk is required for this mod"
So I obviously couldn't try to uninstall the supposed failing module
I thus rebooted in redwold and installed magisk from redwolf (the included release), things went well
However, I still cant install magisk module uninstaller, getting the same error as above.
I took my chance and try to re-install magisk from the zip filed I downloaded, the install process was successfull, but I still can't install magisk mod uninstaller, and the black screen issue persist.
Lastly, I took my chance and try to re-install lazy flasher, the install process was successfull, but the black-screen issue persist.
To be honest, I'm a bit sctuck now.
What may be the right procedure to solve this problem ?
Am I screwed and do I have to reflash a whole rom ?
If so Should I do it from redwolf, and how ?
Or should I do it from the pc with fastboot, and how ?
Thanks for your directions
ps: i was interested by pixel 2 experience module as at it was written that it was compatible with mido and provides camera2api, which might have been a nice combo.
ps 2 : I also did installed dolby as you suggested, it worked but the demo crashed to app
ps 3 : I also did installed youtube vaccant, but I couldn't see any new app and my original youtube still had add and couldn't play in the back... not sure it reveals something on the effectiveness of magisk...
Hi,
I am trying to put lineage on my Redmi Note 9 Pro.
However, I am getting the following message when I open Magisk Manager.
Attestion Failed | basicIntegrity CHECK | ctsProfile NOT CHECK | evalType HARDWARE
I tried follow a tutorial on youtube to fix it, however I cannot Link it. It was with the app Terminal Emulator.
Is it still possible to install lineage? If yes, how? If now, can I still return to my phone as normal?
Kind regards,
Q
@Qurbey
It's not required to install Magisk before it comes to install a Custom ROM as Lineage OS. All what is needed is
that phone's boot-loader got suceesfully unlocked - that in most cases will void OEM's / Carrier's warranty -
obtaining a copy of a Custom Recovery like TWRP matching at 100% your phone
obtaining a copy of Lineage OS ROM that at 100% is matching your phone
having the ADB / Fastboot drivers matching your phone installed
jwoegerbauer said:
@Qurbey
It's not required to install Magisk before it comes to install a Custom ROM as Lineage OS. All what is needed is
that phone's boot-loader got suceesfully unlocked - that in most cases will void OEM's / Carrier's warranty -
obtaining a copy of a Custom Recovery like TWRP matching at 100% your phone
obtaining a copy of Lineage OS ROM that at 100% is matching your phone
having the ADB / Fastboot drivers matching your phone installed
Click to expand...
Click to collapse
Thanks jwoegerbauer.
The boot-loader is unlocked with miflash_unlock.exe
I used following tutorial and software to flash TWPR and Root. Should I have not rooted the phone and only flashed TWPR? I am getting lost in all the vocabulary.
https://www.youtube.com/watch?v=PSNe0WkmV6c&t=313s
I am planning to download this version of Lineage.
https://forum.xda-developers.com/redmi-note-8-pro/development/rom-lineageos-17-1-t4072137
Is there a tutorials you would recommend to execute this step? I prefer a video, since I am new to this.
Will I be able to install all software on this phone, or not any more because of my previous actions?
Qurbey said:
Thanks jwoegerbauer.
The boot-loader is unlocked with miflash_unlock.exe
I used following tutorial and software to flash TWPR and Root. Should I have not rooted the phone and only flashed TWPR? I am getting lost in all the vocabulary.
https://www.youtube.com/watch?v=PSNe0WkmV6c&t=313s
I am planning to download this version of Lineage.
https://forum.xda-developers.com/redmi-note-8-pro/development/rom-lineageos-17-1-t4072137
Is there a tutorials you would recommend to execute this step? I prefer a video, since I am new to this.
Will I be able to install all software on this phone, or not any more because of my previous actions?
Click to expand...
Click to collapse
As I can see you modded / hacked your phone in a way that is completely unnecessary in order to flash a Custom ROM.
To be honest, I can't tell you whether this Lineage OS is the correct one.
If a ROM gets flashed, then you're free to install any user-app of your choice on it.
jwoegerbauer said:
As I can see you modded / hacked your phone in a way that is completely unnecessary in order to flash a Custom ROM.
To be honest, I can't tell you whether this Lineage OS is the correct one.
If a ROM gets flashed, then you're free to install any user-app of your choice on it.
Click to expand...
Click to collapse
I have removed the app Terminal Emulator.
But now my phone is locked again. It is not bricked. However I cannot acces twpr recovery any more.
Should I unlock it again? Is that with the 168 hours waiting time agian or not?
Then flash Twrp, without rooting.
Install Lineage
Thanks.
@Qurbey
By installing TWRP you have deleted phone's Stock Recovery. Means now you can no longer flash the original Stock ROM in order to then re-start flashing Lineage OS. It was your decision.
Don't have the phone in question, hence can't help you any further.
jwoegerbauer said:
@Qurbey
By installing TWRP you have deleted phone's Stock Recovery. Means now you can no longer flash the original Stock ROM in order to then re-start flashing Lineage OS. It was your decision.
Don't have the phone in question, hence can't help you any further.
Click to expand...
Click to collapse
Thanks, jwoegerbauer.
That is unfortunate. There is no workaround this? Does this mean I am stuck with the xiaomi interface forever?
Would you advice to remove Magisk from the phone?
@Qurbey
My last 2 cents here ( I no longer participate this thread ):
Get rid off of all mods/hacks you made to phone's Android, will say restore phone's Stock ROM by means of MIUI Flash tool.
Then do NOT install TWRP, but simply boot into it - via FastBoot driver
Finally flash Lineage OS via TWRP
jwoegerbauer said:
@Qurbey
My last 2 cents here ( I no longer participate this thread ):
Get rid off of all mods/hacks you made to phone's Android, will say restore phone's Stock ROM by means of MIUI Flash tool.
Then do NOT install TWRP, but simply boot into it - via FastBoot driver
Finally flash Lineage OS via TWRP
Click to expand...
Click to collapse
Thanks for all the help.
Hello all,
It's a long time that's i haven't post a thread here but i have a question.I have a Poco with MIUI Global 9.6 Stable (9.6.25.0) for ROM with a Android Version 8.1.0 OPM 171019.011 with root acces, unlocking bootloader and TWRP 3.3.0-0 installed.
I would upgrade my phone to something "newer" (A ROM with Android 12 if possible) and conserv the root access and my apps.
I have read that now ,we should have 3 files to do that (firmware,system and vendor) to make a wipe and install new ROM with TWRP.
So my question:
-Is it possible to upgrade Android 8.1.0 to Android 12 witn a new ROM? (i have read something about kernel in Android12 but haven't understand all)
-Have i missed some steps or just download files,boot TWRP,wipe and install newer ROM+firmware and vendor appropriate is good?
-Which ROM do you recommend?
Thanks for the previous answers.
devil1 said:
Hello all,
It's a long time that's i haven't post a thread here but i have a question.I have a Poco with MIUI Global 9.6 Stable (9.6.25.0) for ROM with a Android Version 8.1.0 OPM 171019.011 with root acces, unlocking bootloader and TWRP 3.3.0-0 installed.
I would upgrade my phone to something "newer" (A ROM with Android 12 if possible) and conserv the root access and my apps.
I have read that now ,we should have 3 files to do that (firmware,system and vendor) to make a wipe and install new ROM with TWRP.
So my question:
-Is it possible to upgrade Android 8.1.0 to Android 12 witn a new ROM? (i have read something about kernel in Android12 but haven't understand all)
-Have i missed some steps or just download files,boot TWRP,wipe and install newer ROM+firmware and vendor appropriate is good?
-Which ROM do you recommend?
Thanks for the previous answers.
Click to expand...
Click to collapse
It's not possible to switch from stock ROM to custom without doing clean install. You will have to root again.
First update to latest Official Stock ROM, then take backup of your files to your PC or to SDCard (if you have one) , flash to latest Official TWRP and check my POCO F1 Ultimate Collection & Guides. You can find everything there. I have awarded recommended ROMs in my collection.
Feel free to ask if you have any question regarding the guides.
Thanks for the answer.I have begin to read your guides.
If i understand good,it's not possible to conserv my root,unlock bootloader and twrp when i upgrade to android 12? Automaticaly i should root again my phone and restore with titanium backup my files,contact,....?
devil1 said:
Thanks for the answer.I have begin to read your guides.
If i understand good,it's not possible to conserv my root,unlock bootloader and twrp when i upgrade to android 12? Automaticaly i should root again my phone and restore with titanium backup my files,contact,....?
Click to expand...
Click to collapse
First you need to take backup of your files to PC or External SDCard.
Then you should update to latest version of MIUI via OTA if it's possible or via TWRP (you can use the stock recovery rom to do it via twrp). (You can also use my guides for clean install stock rom)
Then you should unlock your bootloader if it's not already unlocked.
Then flash latest Official TWRP.
Then flash latest firmware (not vendor) just to make sure you are on the latest. (You should be on latest firmware after updating to the latest MIUI version)
Then Wipe everything + format data according to my guides and flash the ROM you want. If you choose A12 Pixel Experience or crDroid keep in mind that these ROMs use their own recovery because these are encrypted by default ROMs and TWRP can't handle the decryption of A12 encrypted ROMs yet. So to make OTA updates and that stuff work correctly devs of these ROMs decide to use their own recovery which can handle the decryption of encrypted roms and as result to make OTA update work fine. Check the installation instructions of these roms in their threads. (Afterwards you can use adb sideload to flash stuff using these recoveries)
After that, flash Magisk since you want root.
Then you can restore titanium backup if you want.
OK i follow your instruction.Thanks
Hello retrial,
I have now updating my phone to MIUI Global 12.0.3 Stable with Android Version 10QKQ1.My phone is not yet rooted and now he is encrypted.The recovery is now Mi-Recovery 3.0
I have unlock again my bootloader.
Now to follow your instruction,i should flash the latest TWRP.
I have take TWRP-3.6.0_9-0-berylium in your guide.
I think i should do Fastboot Method because i'm now in Mi-Recovery?i'm right?
No problem with the encryption?
Thanks.
i have find this video.This is not the good phone but i think that the installation is the same:
devil1 said:
Hello retrial,
I have now updating my phone to MIUI Global 12.0.3 Stable with Android Version 10QKQ1.My phone is not yet rooted and now he is encrypted.The recovery is now Mi-Recovery 3.0
I have unlock again my bootloader.
Now to follow your instruction,i should flash the latest TWRP.
I have take TWRP-3.6.0_9-0-berylium in your guide.
I think i should do Fastboot Method because i'm now in Mi-Recovery?i'm right?
No problem with the encryption?
Thanks.
Click to expand...
Click to collapse
Yes use Fastboot Method to flash TWRP. No problem with encryption.
After that follow my clean install custom rom guide to flash the ROM you want. Also please check the instructions in the threads of ROMs you want to flash. A12 crDroid and PE use their own recoveries.
Basically tell me which ROM you want to flash to help you exactly with steps.
Hello retrial,
i have a problem to install TWRP-3.6.0-9-0 on my pocophone.Everything working fine but in step 8 of your guide,i can't find my twrp.img that i have copied in 2 different case to test :
8. Boot into Recovery by typing in cmd: fastboot boot <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly and write the full path of it, check the example below).
This command will not flash permantly the recovery, it will just temporary boot into it and afterwards you will flash permantly the twrp.img you copied into your Internal Storage or SDcard in recovery partition.
For example: fastboot boot C:\Users\Retrial\Desktop\twrp-3.5.2_9-0-beryllium.img
Have you an idea to why i cannot find my twrp.img in the boot mode?
devil1 said:
Hello retrial,
i have a problem to install TWRP-3.6.0-9-0 on my pocophone.Everything working fine but in step 8 of your guide,i can't find my twrp.img that i have copied in 2 different case to test :
8. Boot into Recovery by typing in cmd: fastboot boot <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly and write the full path of it, check the example below).
This command will not flash permantly the recovery, it will just temporary boot into it and afterwards you will flash permantly the twrp.img you copied into your Internal Storage or SDcard in recovery partition.
For example: fastboot boot C:\Users\Retrial\Desktop\twrp-3.5.2_9-0-beryllium.img
Have you an idea to why i cannot find my twrp.img in the boot mode?
Click to expand...
Click to collapse
Send a screenshot what you type in cmd and where you have the twrp.img
Or you mean you can't find it in your device while you are booted on TWRP?
i cannot find the twrp.img in my device.The step 8 of your tutorial.
I have copied the files but cannot find it in the cases.I have take TWRP-3.6.0-9-0
The link of the files: https://eu.dl.twrp.me/beryllium/twrp-3.6.0_9-0-beryllium.img.html
devil1 said:
i cannot find the twrp.img in my device.The step 8 of your tutorial.
I have copied the files but cannot find it in the cases.I have take TWRP-3.6.0-9-0
The link of the files: https://eu.dl.twrp.me/beryllium/twrp-3.6.0_9-0-beryllium.img.html
Click to expand...
Click to collapse
Are you sure you select Install Image?
ok i have download an other twrp.img and this time it's ok.i can go to the end of the tutorial but when i reboot my device mi-recovery 3.0 come back.I have tried 2 times but all the time mi-recovery3.0 come back
Have you an idea?
Should i take a additional command like in the video i have send you in the thread "fastboot flash recovery"?
devil1 said:
ok i have download an other twrp.img and this time it's ok.i can go to the end of the tutorial but when i reboot my device mi-recovery 3.0 come back.I have tried 2 times but all the time mi-recovery3.0 come back
Have you an idea?
Should i take a additional command like in the video i have send you in the thread "fastboot flash recovery"?
View attachment 5549731
Click to expand...
Click to collapse
I have all the steps on my guide. Please read it carefully. It boots back to mi recovery because you haven't flash TWRP yet just booted into. After boot into TWRP u need to flash twrp in recovery section so it will stay after reboot.
Please read the steps.
Download portable Minimal ADB and Fastboot and latest Official TWRP recovery.
Open cmd from minimal adb and fastboot and write:
fastboot boot and the path you have TWRP.
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.0_9-0-beryllium.img
Then proceed with the rest steps in my guide. Connect ur device to pc while u are booted into TWRP and copy TWRP.img to your device. Then in TWRP press Install Image and select the twrp.img u just copied into ur device. Select recovery and done.
I have made a video to show you what happened (sorry for the bad quality and the moove) :
I think a video is easyest to understand my problem.For information my bootloader is unlock and usb debugging ok.
devil1 said:
I have made a video to show you what happened (sorry for the bad quality and the moove) :
I think a video is easyest to understand my problem.For information my bootloader is unlock and usb debugging ok.
Click to expand...
Click to collapse
Hmm strange, probably of MIUI. Anyway since you are going to flash custom rom, when u flash twrp in recovery go back and select wipe and wipe everything (read my clean install guide), go back press format data type yes, and then reboot to TWRP.
EDIT: I just saw u rebooted to system. That's not what we want. Press reboot to recovery.
i reboot first to bootloader after have flash the twrp.img in recovery.That's only the second time that i reboot to system to use the normal mode of the phone and reboot after to recovery mode to show you that mi recovery is back.
devil1 said:
i reboot first to bootloader after have flash the twrp.img in recovery.That's only the second time that i reboot to system to use the normal mode of the phone and reboot after to recovery mode to show you that mi recovery is back.
Click to expand...
Click to collapse
The TWRP flashed correctly. You overlap it again by pressing reboot to recovery from MIUI updater.
Don't do that...do the combination to boot to TWRP after flashing it. Power+Volume Up.
And continue with clean install steps in my guide to flash custom rom.
In my guide I write nowhere to boot to MIUI and press from MIUI Updater reboot to recovery, please stick to my guide and you will be fine.
Poco f1 update not