Related
## Disclaimer and acknowledgements
All your actions with your phone are at your own risk;
## Intro
Hey,
I propose a tutorial to root Wileyfox Storm with lastest SuperSu Binary, but you can flash zips too ^^
Wileyfox storm's stock recovery has a signature verification, so you can't flash SuperSu 2.46, but with long work i got custom cyanogen recovery with no signature verification ;D
## Tutorial
Step 1 : Unlock bootloader !!!! It will erase All Data So backup first !!!!
- Go to settings>about phone and tap a few times on build number to unlock dev options
- Go to Dev options and check OEM Unlock and reboot bootloader (volume +)
- Type "fastboot devices" and if it appear type "fastboot oem unlock" and press y
Step 2 : Flash Custom Recovery
- Reboot Bootloader
- type "fastboot devices" if it appear type "fastboot flash recovery C:\..\kipper-custom-recovery.img"
- Wait the flash process and reboot recovery (volume -)
- Now Flash SuperSu-2.46.zip
Step 3 : Enjoy !!
## Download
Super Su : SuperSu-v2.46_signed.zip
Custom Recovery : kipper-custom-recovery.img
Corrected link to recovery?
Hi,
The custom recovery link is to the supersu file as well. Can you post the corrected link?
Thanks
Sorry xD
Thanks, I haven't had time to try compiling the Cyanogen Recovery for the Storm myself yet.
The above recovery image worked for me using fastboot boot xxx thus leaving the stock recovery intact.
F:\downloads\kipper>fastboot boot kipper-custom-recovery.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
OKAY [ 3.082s]
finished. total time: 3.758s
Wileyfox Storm (Kipper) - 12.1-YOG4PAS3MG
SuperSu and Busybox successfully installed.
Thanks.
No prob i'm happy, i've done it myself ^^
Phone wont boot pasted the Cyanogen logo
Thanks for taking the time and effort to share this. It's really appreciated.
However, I'm a bit stuck.....
bobslesbricoleurs said:
## Tutorial
Step 1 : Unlock bootloader !!!! It will erase All Data So backup first !!!!
- Go to settings>about phone and tap a few times on build number to unlock dev options
- Go to Dev options and check OEM Unlock and reboot bootloader (volume +)
- Type "fastboot devices" and if it appear type "fastboot oem unlock" and press y
Step 2 : Flash Custom Recovery
- Reboot Bootloader
- type "fastboot devices" if it appear type "fastboot flash recovery C:\..\kipper-custom-recovery.img"
- Wait the flash process and reboot recovery (volume -)
- Now Flash SuperSu-2.46.zip
Step 3 : Enjoy !!
Click to expand...
Click to collapse
I got as far as flashing the recovery. One it said it was finished I didn't know how to reboot the Bootloader so I rebooted the phone. On booting the android graphic came up and said 'Erase' or 'Erasing'. It then went to the Cyanogen logo and won't proceed any further.
So, presumably its important to get the su flashed onto the device. However, I dont know how to do this. I have the su.zip on my c: drive... How do I flash it onto my storm device?
P.s. is the failure to boot down to SU or has something borked???
Thanks in advance!
codeclinic said:
Thanks for taking the time and effort to share this. It's really appreciated.
However, I'm a bit stuck.....
I got as far as flashing the recovery. One it said it was finished I didn't know how to reboot the Bootloader so I rebooted the phone. On booting the android graphic came up and said 'Erase' or 'Erasing'. It then went to the Cyanogen logo and won't proceed any further.
So, presumably its important to get the su flashed onto the device. However, I dont know how to do this. I have the su.zip on my c: drive... How do I flash it onto my storm device?
P.s. is the failure to boot down to SU or has something borked???
Thanks in advance!
Click to expand...
Click to collapse
The first boot after wiping takes a few minutes so do be sure that you are waiting long enough, otherwise sounds like something borked.
Are you able to boot back to recovery by holding volume down while powering up?
If so you should try clearing cache and wiping.
You can also try restoring to stock CyanogenOS images : https://cyngn.com/support
If just installing the stock recovery the image can be extracted from the fastboot zip.
There is now also a CyanogenMod nightly build, you can try flashing the recovery from there instead (there is also the nightly Cyanogen build if you are feeling brave): https://download.cyanogenmod.org/?device=kipper
There is a separate download for the recovery image.
Flashing su is not required to boot after flashing the custom recovery.
However to flash it, first copy the SuperSu zip onto the phone (for simplicity use the main memory not the SD card), either download directly onto phone, copy from computer when connected as a usb device or transfer using adb. From the custom recovery you can then select Apply Update and browse to the SuperSu zip file.
codeclinic said:
Thanks for taking the time and effort to share this. It's really appreciated.
However, I'm a bit stuck.....
I got as far as flashing the recovery. One it said it was finished I didn't know how to reboot the Bootloader so I rebooted the phone. On booting the android graphic came up and said 'Erase' or 'Erasing'. It then went to the Cyanogen logo and won't proceed any further.
So, presumably its important to get the su flashed onto the device. However, I dont know how to do this. I have the su.zip on my c: drive... How do I flash it onto my storm device?
P.s. is the failure to boot down to SU or has something borked???
Thanks in advance!
Click to expand...
Click to collapse
Did you unlocked bootloader before?
Envoyé de mon Wileyfox Storm avec XDA Forums
bobslesbricoleurs said:
Did you unlocked bootloader before?
Envoyé de mon Wileyfox Storm avec XDA Forums
Click to expand...
Click to collapse
Yes, i followed all the instructions. I even tried doing it with the 'fastboot boot' method. But still no luck.
In the end I did a factory reset from the recovery and rebooted. I'm now able to get into android normally.
However, if i go back to recovery and try to flash the su binaries, it fails with the output sayings something about the signature of the package.
Any ideas?
codeclinic said:
Yes, i followed all the instructions. I even tried doing it with the 'fastboot boot' method. But still no luck.
In the end I did a factory reset from the recovery and rebooted. I'm now able to get into android normally.
However, if i go back to recovery and try to flash the su binaries, it fails with the output sayings something about the signature of the package.
Any ideas?
Click to expand...
Click to collapse
If you are getting messages about the signature then you are probably running the stock recovery again,
Go back to the bootloader and use fastboot to boot or flash the customer recovery above or cyanogen recovery again.
You can also grab an unsigned version of SuperSu from the developer : https://download.chainfire.eu/696/supersu/
miSAKe said:
If you are getting messages about the signature then you are probably running the stock recovery again,
Go back to the bootloader and use fastboot to boot or flash the customer recovery above or cyanogen recovery again.
Click to expand...
Click to collapse
I figured / hoped that was the case. I'll give it another shot tonight.
miSAKe said:
You can also grab an unsigned version of SuperSu from the developer
Click to expand...
Click to collapse
Are there any pros/cons of using the unsigned version over the signed one? If not, is it not better to use the unsigned version and not bother with the flashing of the recovery?
Thanks
Maybe i'll try later to port philz to this phone ^^
Is it possible to relock the bootloader again?
I've successfully managed to install the custom Cyanogen recovery, and CyanogenMod on my WF Storm this afternoon. I largely did this by following the instructions posted previously - unlocking bootloader, installing CM recovery image with fastboot, then installing CM12.1-kipper from recovery.
I did encounter some problems - namely that the nightly version of the CM recovery (cm-12.1-20151120-NIGHTLY-kipper-recovery.img ) just did not seem to work, despite reportedly being installed OK - Whenever I tried to install anything in recovery mode, it came up with "failed to verify whole-file signature" or similar errors. Strangely I was able to overcome this by using fastboot to boot from the image of it downloaded to my PC, and installing the CM ROM that way; initially it came up with an error about filesystems being incompatible, but after erasing all data, it seemed to go on OK.
I installed the openGAPPS aroma version (allows you to choose which GApps to install interactively) and used the ARM-64 version. Initially, I had the problem with the recovery and couldn't install it, so finally decided to install the cyanogen recovery linked to above in one of the first posts (kipper-custom-recovery.img) rather than from the nightlys. This seemed to solve the problem, about signature errors and I tried to install GApps. The first time I tried this (after going through and selecting what to install from the huge list), it seemed to start OK then said there was not enough space on the device - which seemed very odd indeed. I rebooted and tried again, this time with a few less GApps selected, and it seemed to work fine. I think it was just some kind of a glitch the first time, because there is plenty of space left.
During the first boot after installing the GApps, the systemUI crashed, the screen went black and it was not looking good. Following another reboot though, it seemed to be OK, and I am very happily now using the Storm with CyanogenMOD and root access. I've now installed the dozens of extra apps I use, from the play store, and so far, everything is working well.
Of course, I haven't checked evreything yet, but the camera, phone, 4G LTE, tethering, google account etc. all seem to be working very well.
I hope this info might be of help to anyone looking to get CM12.1 going on their WFStorm. If you get signature errors, just make sure you try installing a different CM recovery!
A huge thanks to earlier posters, and everyone who's worked on getting a version of CM for the Storm. Peace-out,
Neon
nsam1 said:
I've successfully managed to install the custom Cyanogen recovery, and CyanogenMod on my WF Storm this afternoon. I largely did this by following the instructions posted previously - unlocking bootloader, installing CM recovery image with fastboot, then installing CM12.1-kipper from recovery.
I did encounter some problems - namely that the nightly version of the CM recovery (cm-12.1-20151120-NIGHTLY-kipper-recovery.img ) just did not seem to work, despite reportedly being installed OK - Whenever I tried to install anything in recovery mode, it came up with "failed to verify whole-file signature" or similar errors. Strangely I was able to overcome this by using fastboot to boot from the image of it downloaded to my PC, and installing the CM ROM that way; initially it came up with an error about filesystems being incompatible, but after erasing all data, it seemed to go on OK.
I installed the openGAPPS aroma version (allows you to choose which GApps to install interactively) and used the ARM-64 version. Initially, I had the problem with the recovery and couldn't install it, so finally decided to install the cyanogen recovery linked to above in one of the first posts (kipper-custom-recovery.img) rather than from the nightlys. This seemed to solve the problem, about signature errors and I tried to install GApps. The first time I tried this (after going through and selecting what to install from the huge list), it seemed to start OK then said there was not enough space on the device - which seemed very odd indeed. I rebooted and tried again, this time with a few less GApps selected, and it seemed to work fine. I think it was just some kind of a glitch the first time, because there is plenty of space left.
During the first boot after installing the GApps, the systemUI crashed, the screen went black and it was not looking good. Following another reboot though, it seemed to be OK, and I am very happily now using the Storm with CyanogenMOD and root access. I've now installed the dozens of extra apps I use, from the play store, and so far, everything is working well.
Of course, I haven't checked evreything yet, but the camera, phone, 4G LTE, tethering, google account etc. all seem to be working very well.
I hope this info might be of help to anyone looking to get CM12.1 going on their WFStorm. If you get signature errors, just make sure you try installing a different CM recovery!
A huge thanks to earlier posters, and everyone who's worked on getting a version of CM for the Storm. Peace-out,
Neon
Click to expand...
Click to collapse
Wich open gapps you need ? mini, micro, full ?
Hi,
I used the aroma version of GApps, which has the interactive graphical installer so you can choose whichever apps you want. I am sure Nano and Pico etc. are all fine, I just wanted to install a lot of GApps.
I downloaded from here: http://opengapps.org/?api=5.1&variant=nano
It is set to nano by default but I chose aroma. Make sure you select the correct architecture (ARM64) and android 5.1 (if you are using kipper).
Best of luck,
Nsam
https://youtu.be/b6XUFmHoY4U
I upload it just wait 1 Hr
bobslesbricoleurs said:
https://youtu.be/b6XUFmHoY4U
I upload it just wait 1 Hr
Click to expand...
Click to collapse
All looks good I seem to have a slight problem with one bluetooth device, but I need to look in to it more before I say it is a problem with kipper. Other bluetooth devices work fine
keep up the good work
Nsam
Hei it has been the second day running nightly built of CM12.1, and so far its been great never had serious issues. I just noticed that the proximity sensor distance when call is engage is set to very near like 1cm. If the phone goes further the screen lights on and gets activated.
Nightly most of time runs well, apart from "Not Responding" whatsapp every once in a while. Battery life is average almost the same stock CM. Call gets cut/muted at the middle of the conversation, not sure if the network or the phone has it. Hopefully there will be a TWRP soon for the device as NANDroid backup is very important when using nightly. Thanks for all the devs.
[CONFIRMED] Confirm my Oreo to Marshmallow to 6.01 Resurrection Remix plan & commands
Hey folks,
I'm buying a Nexus 6P 128GB running OREO this afternoon. I'm a 6P newbie.
Am in a rush as I'm driving out to Dallas tonight and need it for the trip.
My Pixel XL's GPS died.
This is a last minute/rush thing, so I haven't had time to research.
0) Unlock bootloader if not already done
1) Do a factory wipe from Security settings
2) Reboot to Bootloader.
3) flashall.bat the 6.01 factory image (angler-mtc20l-factory-b7864fdb)
4) Log into phone and then reboot to bootloader.
5) fastboot flash recovery twrp-3.1.1-0-angler.img
6) Reboot to recovery
7) Wipe cache/dalvik/data
8) Install rom.zip (ResurrectionRemix-M-v5.7.4-20161008-angler.zip)
9) Flash GAPPs.
10) Boot to ROM and log in.
Yes, I did read the ROM thread directions (copied below).
But since I'm new to 6P, I wanted to make sure there is nothing funky I'm not aware of or missing. Thanks!
varund7726 at Resurrection Remix said:
- Make sure you have updated your device with the Latest Vendor IMAGE
- Download the latest build
- Download Gapps
- Take a nandroid backup
- Recommended - Full wipe and factory reset
- Flash ROM using latest TWRP 2.3.x Recovery
- Flash Gapps
Click to expand...
Click to collapse
All this is assuming your phone is rooted already. Flashing everything manually rarely works properly for me since my computer doesn't always detect it for some reason.
I use skipsoft tool kit which works for noobs and more advanced users
If it is rooted, letting the factory image run from start to finish will reset recovery and might unroot your phone.
you could manually install the parts and skip recovery so it doesnt have to be reinstalled. however you wouldn't be here if you knew how.
I'd tell you the order but I dont have a factory image to open and see the flashall bat instructions.
To find out the order. Right Click flashall.bat > edit. From here it will tell you the order it is going to flash everything. If you can follow it. flash everything except recovery, as this will allow you to boot into recovery after the install is complete. My only warning for this is that this method has worked moving up the update chain. so 6.0 to 7.0 etc. I havent tried it downgrading, let alone you are going from 8.0 to 6.0 so dont take my word for it being successful. If it does load follow the rest of the steps below. If it doesn't boot to recovery, you'll have to find one the works for 6.0 or reinstall twrp
wipe,
load custon rom,
gapps
boot. (confirm you can boot to initial install screen)
Then add kernal
If not.
Install factory
Root phone,
load recovery,
wipe,
load custon rom,
gapps
boot. (confirm you can boot to initial install screen)
Then add kernal
Okay, all done.
The steps I listed in my OP worked perfectly.
I just had to add "recovery" to my command "fastboot flash twrp.....".
So that it reads "fastboot flash recovery twrp...."
I knew this, I just forgot it for a minute.
But there was no weirdness. Pretty straightforward. :good:
I'm now on RR 6.01 and gonna start looking for my favorite Exposed modules that aren't available on Nougat yet (or ever).
Thanks for trying to help, StarRavier.
Hello community!
First of all, I feel I have to apologize to you all since I know I have clogged the forum with a lot of requests of help about upgrading my smartphone... They are scattered all over the place so I have decided to gathered in a definitive one.
I have edited this post to make it a comprehensive guide for all the people who want to upgrade their HUAWEI P8 LITE ALICE from the stock Android 5.0.1 to the Resurrection Remix N v5.8.5. Before go any further I want you to read the following disclaimer:
PLEASE PLEASE PLEASE READ THIS!!
I am not a developer. I am not a programmer. I have been greatly helped by the user Botar230 so, unfortunately, I cannot help you in case of problems. I myself had problems and had to ask for help. The only thing I can say is to be always polite and try to explain, as best as you can, what's going on.
I will try to be as much clear as possible here but keep in mind that english is not my native language so it is possible that I might mistaking something. My apologize. I am not responsible for any damage you may do to your mobile and I am not responsible to any data loss it may occur. You should ALWAYS do a backup before proceeding. ALWAYS.
I've decided to flash Resurrection Remix N v5.8.5. because it is pre-rooted with Magisk.
BEFORE start to upgrade your mobile, read all this post twice and be sure to understood all the things I have written here. Check the links, check if you have the correct files, check if your mobile is fully charged, check if the bootloader is unlocked, check if you have the right ADB files and drivers downloaded and installed. Please do it BEFORE you start everything.
Done? Everything is fine? So, here we go!
GOAL: Moving from stock Android 5.0.1 to Resurrection Remix N v5.8.5.
MY MOBILE: Huawei P8 Lite ALICE (ALE-L21) unbranded single SIM - Build number: BalongC50B311 - Kernel 3.10.61-gcd3fde7 - EMUI 3.1
BOOTLOADER STATUS: unlocked, checked via ADB
The build number and the kernel number might differ. You should check them carefully and search around this forum how to proceed properly. Also, I totally don't know what to do if you have a double SIM phone. Sorry.
These are the files I have downloaded and put on the MicroSD before starting the whole process:
b895_update.zip
open_gapps-arm64-7.1-nano-20180702
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
The file TWRP_3.1.1-0_ALICE_BL.img have to be put in the same directory where adb.exe is since you will flash it via adb command: fastboot flash recovery TWRP_3.1.1-0_ALICE_BL.img once you have entered in fastboot mode AND you have checked that your bootloader is unlocked.
Now, the next steps that worked for me are:
install TWRP_3.1.1-0 via ADB
Factory reset (Wipe -> Swipe to wipe)
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload as suggested by Botar230. I find myself comfortable to use ADB.)
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload
Flash RR-N-v5.8.5-20180302-alice-OpenKirin) via TWRP AND at the same time...
Flash Open Gapps via TWRP. You HAVE TO USE THE ARM64 - 7.1 VERSION!!!
Reboot your device. It is done! :good:
NOTE!! Updating the phone to b895 will take really a lot of time. Seriously. It might be scary but it's ok. It will update EMUI too.
NOTE!! When you install TWRP via ADB, the TWRP_3.1.1-0_ALICE_BL.img file MUST BE in the same directory where the adb.exe file is.
At this point, everything should be fine, working and squeaky clean!
The ROM is pre-rooted with Magisk and that's pretty cool!
At this point I think my brief tutorial is over. If you find out something important missing or wrong, please point it out! It will help other people! Thank you!
Some links about ADB that I found quite useful:
How to Install TWRP Recovery via Fastboot On Any Android Device
How to Use ADB & Fastboot Commands with your Android Device
ADB Shell
Once again I have to thank the immense patience of BOTAR230 and all the people that worked so hard to make everything possible: I mean the guys (and gals? Maybe, I don't know... ) behind the Resurrection Remix ROM, behind the TWRP project and the Open Gapps and the many more I probably forgot! Thanks everyone!
DaGreatAssyr said:
Hello community!
First of all, I feel I have to apologize to you all since I know I have clogged the forum with a lot of requests of help about upgrading my smartphone... They are scattered all over the place so I have decided to gathered in a definitive one.
Next, I am quite insecure on all the steps so I will try to make a comprehensive list and keep it updated hoping it will help all the Huawei P8 Lite ALICE users that will do the same process I am about to do. Let's proceed!
GOAL: Moving from stock Android 5.0.1 to OpenKirin's MoKee
MY MOBILE: Huawei P8 Lite ALICE (ALE-L21) unbranded single SIM - Build number: BalongC50B311 - Kernel 3.10.61-gcd3fde7 - EMUI 3.1
BOOTLOADER STATUS: unlocked, checked via ADB
Now, the next steps would be to root the mobile. My wild guess are
install TWRP_3.1.1-0_ALICE_BL via ADB
install Magisk to root Android 5.0.1
At this point I am not perfectly sure if those steps are right AND if Magisk is the right choice to root Android 5.0.1 on my mobile. Are there other ways to do that?
Once the device is rooted, the next steps should be:
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed)
install again TWRP_3.1.1-0_ALICE_BL via ADB
install again Magisk to root Android 6.0
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
That's the theory. I've used SR5-SuperSU-v2.82-SYSTEMMODE but it bricked the phone after I updated to Android 6.0 and the user Botar230 told me that it is no longer updated and used and suggested me to use Magisk instead.
The files I have are:
b895_update.zip
open_gapps-arm-7.1-stock-20180626.zip
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
pa_alice-7.3.1-EOL-20180203.zip
TWRP_3.1.1-0_ALICE_BL.img
Previously, I have updated my device to Android 6.0 and installed TWRP 3.1.1-0 and everything went really good. When I tried to root the phone with SuperSU-v2.82, it bricked. Now the phone is restored to its initial conditions, brandless.
I have read THIS POST but it's pretty old and most of the link there are not working anymore.
So, if someone is kindly willingly to give me a hand (yeah, another one, I know... ) on this subject, I'd really appreciate it. Again.
Thanks in advance!
Click to expand...
Click to collapse
I didn't fully understand you, so I'll write a quick guide how to move from stock android 5.0.1 to any other custom ROM (I've read that you already unlocked your bootloader and flashed twrp so I'll skip those two)
First of all, use this version of TWRP.
1. Boot into TWRP
2. Factory reset (Wipe -> Swipe to wipe)
3. Flash B896 update (B895 is fine too)
4. Flash TWRP (Install -> Select image -> Recovery)
5. Flash a custom ROM of your choice
6. Flash Open GAPPS (I recommend flashing NANO version)
7. (Optionally) Flash Magisk if your custom ROM isn't pre-rooted (if unsure, check the root status before flashing)
Fun fact: You don't need to put every file on SD card to flash it. You can also use sideload
Botar230 said:
I didn't fully understand you, so I'll write a quick guide how to move from stock android 5.0.1 to any other custom ROM (I've read that you already unlocked your bootloader and flashed twrp
Click to expand...
Click to collapse
Hello Botar230! At the present time, I only unlocked the bootloader.
No TWRP installed so far.
Thank you for adding some steps I have missed (like the factory reset and the GApps! :good: )!!
The TWRP version I have is the same you suggested me so this is fine!
Yes, now that I think about, nearly all the custom ROM are pre-rooted and there's an option to switch the root in the setting panel but I will check it eventually.
I have make corrections in my list after your suggestion:
install TWRP_3.1.1-0_ALICE_BL via ADB
Factory reset (Wipe -> Swipe to wipe)
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload)
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk
The files I have are:
b895_update.zip
open_gapps-arm-7.1-stock-20180626.zip (I will not use these)
open_gapps-arm-7.1-nano-20180630.zip (I will use these one! )
RR-N-v5.8.5-20180302-alice-OpenKirin.zip
pa_alice-7.3.1-EOL-20180203.zip
TWRP_3.1.1-0_ALICE_BL.img
Everything looks good now. Btw you don't need to flash nano gapps exclusively, it's just a matter of your personal preference which one you choose.
Sent from my LG-K220 using XDA Labs
Botar230 said:
Btw you don't need to flash nano gapps exclusively, it's just a matter of your personal preference which one you choose.
Click to expand...
Click to collapse
To be honest, I don't know what to choose between all the options I have seen on the website. Let's say that if the installation works properly it's a matter of seconds to make a backup and try another Gapp. For the moment I will follow your suggestion.
That's what I have done so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload DONE AND OK!
Everything is working fine so far but I am a little bit nervous about these one. I will take a deep breathe and I will proceed right now. I can flash the ROM and the Gapps with TWRP, right? I am mostly sure about but a confirm could ease my fear of bricking the phone again... :silly:
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk
DaGreatAssyr said:
To be honest, I don't know what to choose between all the options I have seen on the website. Let's say that if the installation works properly it's a matter of seconds to make a backup and try another Gapp. For the moment I will follow your suggestion.
That's what I have done so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideloadDONE AND OK!
Everything is working fine so far but I am a little bit nervous about these one. I will take a deep breathe and I will proceed right now. I can flash the ROM and the Gapps with TWRP, right? I am mostly sure about but a confirm could ease my fear of bricking the phone again... :silly:
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin)
Flash open_gapps-arm-7.1-nano-20180630
Check whether the ROM is rootable and eventually flash Magisk
Click to expand...
Click to collapse
Yes, everything is correct.
Sent from my LG-K220 using XDA Labs
Botar230 said:
Yes, everything is correct.
Click to expand...
Click to collapse
First of all, thank you for your immense patience!!
That's what happened so far:
install TWRP_3.1.1-0_ALICE_BL via ADB DONE AND OK!
Factory reset (Wipe -> Swipe to wipe) DONE AND OK!
update the device with b895_update to get Android 6.0 and EMUI 4 (by putting b895_update on the SD card and flash it via TWRP previously installed or via sideload) DONE AND OK!
install again TWRP_3.1.1-0_ALICE_BL via ADB or via sideload DONE AND OK!
install pa_alice-7.3.1-EOL-20180203 (or RR-N-v5.8.5-20180302-alice-OpenKirin) DONE AND OK!
I had to install the open_gapps-arm64 since the system required the ARM64 but apart that...
Flash open_gapps-arm64-7.1-stock-20180630.zip DONE BUT NOT OK! - I've tried to install the NANO and the STOCK Gapps but every time I got the same error message on TWRP: "failed to mount data: operation not supported on transport endpoint". Google Play and all the Google apps cannot connect: the Google error message is always the same: "couldn't sign in". I've double checked the login and they work both on my PC and on the other phones so I'm sure they are correct. Now I'm searching what kind of error it is but I'm not finding much infos about. Plus, there is the warning message saying that "Google Play services has stopped" and it keeps popping on the screen.
Check whether the ROM is rootable and eventually flash Magisk NOT DONE YET but it seems that it is not pre-rooted.
I am searching the web to understand what's going on here.
It's probably because the custom ROM that you've chosen uses f2fs file system on /data partition instead of ext4. Try to do this:
Boot to TWRP -> Wipe -> Advanced wipe -> Choose Data -> Repair or change file system. From here you can see if the file system of /data is ext4 or f2fs. If it's f2fs, then click Change file system and choose ext4.
Before doing all of this, you should flash b895 again, do a factory reset, flash twrp, flash your custom ROM, change /data file system, and finally gapps so there will be no conflicts between old and new gapps.
Hello again!
Sorry for the silence, got some busy day but here I am.
Before doing what you told me, I've tried to do a backup with TWRP and I've been flooded with error messages:
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to recreate /data/media folder
Unable to mount storage
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to mount /data/media/TWRP/.twrps
And, of course, the backup process failed.
At this point I cannot do anything with TWRP.
I cannot backup, cannot flash a ROM or a ZIP.
The phone works fine, it boots and I got no problems. I can boot it via ADB too.
I'm really scared it will brick or loop sooner or later. I am keeping it turned off and wait for any other advice before proceeding since it would be quite pesky to restart from scratch again....
Following your directions I've seen that the data file system is ext3.
DaGreatAssyr said:
Hello again!
Sorry for the silence, got some busy day but here I am.
Before doing what you told me, I've tried to do a backup with TWRP and I've been flooded with error messages:
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to recreate /data/media folder
Unable to mount storage
failed to mount '/data' (Operation not supported on transport endpoint)
Unable to mount /data/media/TWRP/.twrps
And, of course, the backup process failed.
At this point I cannot do anything with TWRP.
I cannot backup, cannot flash a ROM or a ZIP.
The phone works fine, it boots and I got no problems. I can boot it via ADB too.
I'm really scared it will brick or loop sooner or later. I am keeping it turned off and wait for any other advice before proceeding since it would be quite pesky to restart from scratch again....
Following your directions I've seen that the data file system is ext3.
Click to expand...
Click to collapse
Don't worry, it won't brick. Maybe the internal storage is encrypted. In order to remove encryption, go to Wipe -> Format data.
Hello Botar230! Something funny (in a very positive way) happened! I did as you told me: I booted in recovery mode and went to WIPE -> FORMAT DATA.
Then I considered to install the other ROM I had, RR-N-v5.8.5-20180302-alice-OpenKirin and it has been the best idea I could have!!! :laugh:
After I formatted the data, I rebooted in recovery mode and checked that the problems where all disappeared and they actually did. Then I flashed the OpenKirin ROM and the Nano Gapps you told me.
SURPRISE SURPRISE the OpenKirin ROM is pre-rooted with Magisk 15.3 and the installation, this time, went perfectly fine without any trouble! Plus, Magisk updated to the latest version, the 16!
As I promised, I will now update my first post on how to upgrade my mobile phone hoping it will be useful for someone else but first I want to enjoy my brand new phone!
And, of course, I want to thank you for all the support you gave me in these days! You have been really patient and kind! I am really sorry I cannot help you back since (as you have noticed...) I am not much of an expert so all I can give you is my gratitude and thankfulness! THANK YOU 1000 TIMES BOTAR!! :highfive:
You're welcome. Have a nice day! :highfive:
Sent from my LG-K220 using XDA Labs
Just picked one of these up last week, and it has no restrictions on unlocking the bootloader. Boots AOSP 8.1 Phh-Treble almost perfectly. The boot animation was missing, but the wifi, bluetooth, and camera all seem to work just fine.
It doesn't seem to boot AOSP 9, though. Something about keymaster version mismatches, it seems like.
izzy84075 said:
Just picked one of these up last week, and it has no restrictions on unlocking the bootloader. Boots AOSP 8.1 Phh-Treble almost perfectly. The boot animation was missing, but the wifi, bluetooth, and camera all seem to work just fine.
It doesn't seem to boot AOSP 9, though. Something about keymaster version mismatches, it seems like.
Click to expand...
Click to collapse
Make sure that Your kernel is using same security patch date as GSI. I think Phh GSI is supposed to adjust itself to any security patch but if it's not happening then open system.img (Phh Pie) and check security patch. Then use Android Image Kitchen (AIK) to unpack stock boot image and go to.. I literally forgot the name of that folder lol.. there should be 2 folders, ramdisk and something else. So open that "something else" folder then edit oslevel and change security patch to the one that's in Phh Pie.
Now flash image-new.img and system.img and Phh Pie should boot now :fingers-crossed:.
whats the default os version on these puppies ?
Could someone post steps to unlock/root? I've not used a custom ROM since KitKat. The default B&N software is trash.
senselocke said:
Could someone post steps to unlock/root? I've not used a custom ROM since KitKat. The default B&N software is trash.
Click to expand...
Click to collapse
I unlocked the boot loader of the Nook Tablet 10.1”, I installed Project Treble 8.1.0 and Project Treble 9.0, they both had WiFi connection problems.
I installed the most recent version of PHH's Pi GSI and it works flawlessly, even boots up quire quickly after the initial flash. To my knowledge everything works, boot animation, bluetooth, wifi, all of it. Very simple process, just unlock bootloader, get the GSI, flash, and go. Painless, simple, and flawless thus far.
I'm a huge noob to flashing and the thought of bricking scares me, but I'm trying to setup a guide I just don't have the gal to actually test it. I want to backup everything, rom and recovery included and be able to put everything back to stock I just don't know if TWRP works with it. If this is wrong, someone please correct me and I'll edit this post.
1. open developer options via tapping build in about tablet until it opens. Enable usb debugging and oem unlock.
2. install 15 second adb onto your pc, plug your tablet in via usb and with it off, hold volume up and power to go into recovery. select "reboot into bootloader". you'll see "fastboot enabled" on the bottom left of the screen. In a command prompt run "fastboot devices" to make sure its there (you should see a string of numbers popup) then run "fastboot oem unlock". on the tablet you'll see a "do you want to unlock your bootloader?" press volume up for yes. then "fastboot reboot" to go back to your tablet.
3. google for "frama root" and put it on the root of your sdcard. Use the boromir or whichever until root is successful. (you'll probably have to reboot)
4. (the part I'm not sure will work) install twrp manager from the play store and backup everything to your sdcard. partitions, etc.
5. get a gsi image, put it on your SD card, boot into twrp and flash.
To go back to stock
restore your twrp backup, run frama root to unroot your tablet, use adb and fastboot to run "fastboot oem lock" to lock the bootloader and uncheck the stuff in dev options .
I picked up one of these things a few months ago. I'm thinking about unlocking the bootloader, rooting it, etc. I did some work on previous Android versions (think KitKat), but 8.x is pretty new to me.
Regarding TWRP -- someone needs to actually port it for this device. At least that is how it worked prior to 8.x. I haven't seen one for the BNTV650 so far. Looks like the "Flash GSI without TWRP" steps apply.
alyxnsac said:
I installed the most recent version of PHH's Pi GSI
Click to expand...
Click to collapse
Which one? AOSP 9 I presume, but can you confirm? I'm getting one of these babies and the first thing I will do is to try to install a good, alternate ROM on it (I never use the manufacturer's ROM if I can avoid it).
Got a second Redmi 7A, I'm 99.99% certain it came with *global* 10.2.5 PCMMIXM (it was what ordered, and saw it too, pretty certain), decided to let it upgrade OTA, it picked 11.0.6 OTA, and it came to:
MIUI Global 11.0.6 PCMEUXM (notice the EU there), which, I'm assuming from this url: https://mirom.ezbox.idv.tw/en/phone/pine/
to be this one:
Code:
Redmi 7A – EEA Stable ROM
Lstest V11.0.6.0.PCMEUXM(History)
MIUI 11
Android 9.0
Update at 2019-10-31 19:05:57
Changelog Expand Official Link
Recovery miui_PINEEEAGlobal_V11.0.6.0.PCMEUXM_bcc90ca1df_9.0.zip
Filesize 1.5G
MD5 bcc90ca1df89a4f3d8cc7b9705a70d83
which is a bit confusing, it says Global, but has "EU" in the name.. in any event, flashed TWRP as per:
https://xiaomifirmware.com/guides-and-tips/how-to-install-twrp-and-magisk-root-on-redmi-7a/
choose the LRTeam version:
Code:
2a3296af05267160cba2891bff446203 TWRP-3.3.1-1003-REDMI7A-CN-wzsx150.img
seemed newest, all is great, it boots into TWRP recovery.. Next, trying to get Magisk on it, got the manager apk installed 7.4 all fine, it says 20.1 needs to be installed so...
unzipped the boot.img from above zip file, it has this md5, this is original , unmodified boot.img:
Code:
036d1b6c5a99e9417f8d3e98d5718368 boot_Global_V1106PCMEUXM.img
following this guide: https://romprovider.com/2019/01/create-pre-rooted-patched-boot-img-magisk/
Magisk successfully patched the boot.img on the same phone (running 11.0.6) and got this file:
Code:
dad219422c9302a460d4d2370adafb4f magisk_patched_Global_V1106PCMEUXM.img
transferred to PC, attempted to flash:
Code:
c:\XiaomiADB\bin>fastboot flash boot magisk_patched_Global_V1106PCMEUXM.img
target reported max download size of 535822336 bytes
sending 'boot' (14914 KB)...
OKAY [ 0.470s]
writing 'boot'...
OKAY [ 0.190s]
finished. total time: 0.665s
c:\XiaomiADB\bin>fastboot reboot
rebooting...
finished. total time: 0.003s
Phone boots fine, however, magisk still says it needs to be installed...
in developer's options, the USB debugging is enabled, and boot loader is definitely unlocked, it says on splash screen and the OEM Unlocking is greyed out and says "bootloader already unlocked".
Also, attempted to flash boot image from within TWRP, selecting the above boot.img file and selecting the boot partition, flashes OK, however, after normal reboot, as if nothing happened, phone boots, but magisk is NOT installed (no root).
Is there anything missing in these steps? does anyone have a correctly patched 11.0.6 image with magisk in it from an 7A phone?
Only thing that appears as an "error" are these family of cmds to unlock boot loader:
Code:
fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.004s
however, i think that is normal/expected, since the bootloader is already unlocked.. able to flash twrp, etc.
Thanks so much for any ideas...
Stormy.
Forgot to mention that attempted to install Magisk 20.1 zip file downloaded by the app, from within TWRP, attached screenshot of how that looks like all seems okay but after reboot it still says that magisk needs to be installed... Very strange..
Appreciate any thoughts..
Stormy
noticed in above screenshot that it detected a patched boot image so decided to try installing the
v20.1 Magiskk zip file with the stock Boot, the install results in a screenshot, after reboot it still says that magisk has to be installed.!
also attaching screenshots showing the device is unlocked as well as USB debugging and OEM unlocking are all there.
Should this be posted in The magisk forum or is this something specific to the 7A? Or my steps?
How to debug further?
Attempted with the other TWRP image TWRP_v3.3.1-1_all.img, same results also reinstall the magisk manager 7.4 and same results....hmm.. maybe the OTA update took wrong ROM version. (EU and not pure Global)?...
Digging a bit more, found this pretty cool tool: https://www.xiaomitool.com/V2/latest called: "XiaoMiTool V2 ", which basically automated (almost) Everything !! Tried to do TWRP, as well as Magisk, it too followed similar steps I did, all automatically, rebooting, patching, etc. but outcome is still same, when phone boots normally, Magisk Manager says that Magisk 20.1 needs to be installed...
Then tried to flush miui_PINEGlobal_V11.0.4.0.PCMMIXM_674ed79f0b_9.0.zip using that tool, it said all is OK, phone rebooted , wiped all, but it still runs the EU version for some reason.. Now trying to find the path to "downgrade" from 11.0.6 to 11.0.4, or switch from EU to Global.. maybe that's the source of all issues, not sure what else to try
Reporting progress, to keep track of what was attempted. So, decided to WIPE all and start with 11.0.4 Global fresh, from TWRP, wiped everything, to the point it said "no OS installed, are you sure u want to reboot" it rebooted into fastboot, then downloaded the 11.0.4 Global .tgz and flashed, phone booted OK this time into 11.0.4 Flashed TWRP, and then attempted to flash Magisk via both routes, one by patching the boot.img from the .tgz and flashing, all using the Phone (to avoid any PC/driver/adb issues). The flashing worked fine, but upon reboot, Magisk Manager claimed that Magisk is not installed. Second try was to flash the stock boot.img, then flash magisk zip file, did that for v20.1, v19.4 and 19.3, each time from stock boot.img, and reboots to test, none of them showed that magisk is installed...
all this time, usb debugging is enabled despite most work done on the actual redmi 7A phone itself.
Then uninstalled magisk manager 7.4, and tried with 7.2, but that doesn't change much since any action there wants to update to v7.4..
next step will wipe again, and go for the Global 10.2.5... if that doesn't work then I really don't know what can be going on...
If anyone does have a 7A with MIUI 11 with a properly patched boot.img, would love to try it... all my patching attempted booted fine, but none showed that Magisk is installed... finding it hard to think it's a magisk bug, more likely some MIUI 11, lets see how 10 works out...
Stormy
OK, some success! so, wiped ALL again, to the point of no-OS installed; phone only boots into fastboot (brick), using flash_all.sh from 10.2.5 fastboot Global ROM flashed entire phone and it booted OK.
btw, not easy to find 10.2.5 now, as places already updated links to 11.0.x..
Once in 10.2.5, tried to patch Magisk in all possible ways (twrp or patching boot.img on phone the flashing from Windows10/PC) as also described in this thread few weeks ago:
https://forum.xda-developers.com/showpost.php?p=80498891&postcount=179
but it did NOT work, well, the procedure appeared OK, no errors and when booting, it says magisk needs to be installed.
The only thing that works is the provided boot global .img file [size 14.5 MB (15,269,888 bytes)], as soon as this one is flashed, via phone/twrp or PC, then the magisk is correctly detected.
Very mysterious, why only that boot.img is working on my 7A phones.. maybe there's an additional step, to "sign" or fix the boot.img before it can be flashed?
now took a full TWRP backup, and will try to move to 11.0.4 see if magisk is retained, and if not, if possible to re-gain it.. if not, then, will restore from TWRP backup.
Any thoughts welcomed..
Stormy.
Did not manage to get it working with MIUI 11 yet, so backed to MIUI 10.2.5.. all is fine there.
Noticed that TWRP did not "stick", flash but after normal boot, it came back to original recovery. I think this is b/c of Verify Boot in android Pie/9.. so I *think* what helped here is to flash a vbmeta.img from first post of this thread:
https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820
Even after flashing this, and even in 10.2.5, patching the STOCK 10.2.5 from the phone using Magisk 20.1 and installing using TWRP did not work, not sure if this is a bug in magisk or what, but only way to get root was using the provided boot.img as described above. I'll keep using 10.2.5 for now. feel free to add any ideas here , maybe one day will get more time and a spare phone to try MIUI 11
Stormy.
hey , I have the same problem. I noticed you mentioned 'sign', what should I sign what things? and how to sign?
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
depaul9999 said:
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
Click to expand...
Click to collapse
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible.
Click to expand...
Click to collapse
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
depaul9999 said:
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
Click to expand...
Click to collapse
I've read that the 16GB version of the Redmi 7A is possible to put a micro SD card and format it as internal storage and that was the reason I've bought it, although I'm not yet sure because I'm waiting to buy a microSD card, it's still on the way.
I want to root it because of privacy reasons and that's the only reason. For now I'm using a VPN to block 99% of the google and xiaomi apps, etc. to the internet this way I got some privacy. I have unlocked the phone too so I did uninstalled several apps from the system using the PC.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
Click to expand...
Click to collapse
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
stormy1777 said:
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
Click to expand...
Click to collapse
Well, if you say so... If you're right then I got the wrong Redmi 7A model. It came with the EU version of the miui.
I already knew the tutorial in the link you gave, but that seems very complicated and I do not really know what's going on there so it's better I do not try it. And if I followed that tutorial I would have to flash the phone again with the miui 10, because I have the 11 now. I already wasted many hours trying to root the phone and I had to flash the rom about 4 times because the phone became bricked. Anyway the tutorials I've followed were not the one in the link above and all the other ones I've tried did not work and yet they claim it does, specially using magisk only, without TWRP.
I'll wait for an easier method than the one you shared, if that will ever happen. For now I just use a VPN, it's the closest thing to root I have found, to deny system and apps permission to the internet.
Thank you
In case you're not aware, there are scripts to flash the entire phone automatically, I've done that 10's of times BEFORE putting the phone into "production" use, root was a _must-have_,phone's now heavily used, so can't toy with it much, unless forced to (see below), i may get another phone to play with, but not much TIME to justify it...
Was getting tired of typing:
Code:
:/ # pm list packages|grep xyz
followed by:
:/ # pm uninstall -k --user 0 com.google.android.apps.tachyon
Success
Decided to give some "highly-rated" app a try, it claims to be able to remove system apps: "System app remover (root needed)":
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_US
Took a full TWRP backup, installed, all seems great.. remove, goes to recycle bin, ok.. now, lets REBOOT..
Opps.. phones goes into FASTBOOT... OK!! that's what the backup is for.. go into TWRP, flush SYSTEM, CACHE, DATA, reboot, again, we're in Fastboot, and this time no RECOVERY boot is possible, just goes into FASTBOOT directly.. much like i've described in this thread:
https://forum.xda-developers.com/showpost.php?p=80509823&postcount=111
so, TWRP on phone doesn't help much, took the TWRP backup from SD Card to PC (since phone can only do fastboot at this point), thought it would be easy/possible to fastboot flash all the TWRP into the phone from PC, however, that is NOT simple, since TWRP breaks files, one must concatenate them before flashing..
I was not in the mood, nor did i think a huge change took place, it was just something silly that app did. hmm.. here, i can't exactly explain what took place, but a sequence of flashing of boot.img recovery.img and vbmeta.img all from STOCK and the TWRP backup, was "all it took" to recover the phone fully..
After about 30+ flashes and reboots it came to life much like the last boot, went into that APP again, tried to RESTORE the apps, it failed, and a reboot again, went into FASTBOOT! twrp was there, again, tried recovery, this time only SYSTEM, again, phone lost recovery, and went into, fastboot only... and.. again, sequence of flashing from fastboot, i can tell that vbmeta (Verify Boot) takes a *major* role in this version/device, if something is not right, it just reverts things or decides to go into fastboot.
I saw it work once, so was not going to give up and wipe/start fresh.. kept trying..
I think the app somehow made "direct" modifications to the system partition without proper interface, and thus ruined the "signature" or encryption, otherwise not sure how it could trash the phone so badly..
in any event, after long struggles, flashing the LATEST did _not_ work, it's almost as if the phone had to be taken back to original setting, let it boot into recovery, then reboot again, and flash things in steps, not all at once, at least based on this experience. I know it's silly, b/c in Android 6 I've restored/cloned phones all the time using TWRP directly from phone.. not sure, it does not work on my 7A's...
eventually, phone booted, with 10.2.5 magisk/boot.img (no root, since it did not recognize magisk), then fastboot flashed the canary boot.img, and got root.
anyways, point is, it was pretty ugly, and I'm not complaining, just saying this is pretty complicated stuff, it's a miracle that this even works
keep up the great work everyone, if i can help in any way, let me know...
All this is on Global phone, I don't have an EU/ROM/phone, so can't help u directly, but someone may have a root boot.img EU boot, that's really the key, and the vbmeta.img of course as for MIUI11? so what if that's what you have, it can be flashed, it's a matter of choice, flash to miui 10.2.5 and get root, or try to do it on MIUI11, or, let it be and use w/o root.. which was not an option for me
good luck.
Stormy.
btw, the magisk/patching boot.img did not work for me, and was reported in that same thread:
https://forum.xda-developers.com/showpost.php?p=80560039&postcount=206
MDV106 said that both EU and global boot.img were posted in that thread, and i agree i used one of them, not sure exactly which, but definitely it was the Global, not the EU. and i think it's not goot to mix up.. if u have an EU, stick with it, it might impact Wifi or similar "regional" things..
Same problem, but it works on mokee
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
boody shaban said:
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
Click to expand...
Click to collapse
Thanks for this data point, yeah, root was/is also possible with MIUI 10.2.5, I'm sure other ROMs can root pretty easily.. the "goal" of this thread is to somehow figure how to do it on MIUI 11 so we can take the security updates and still retain rootness
working root redmi 7a
Working root for Redmi 7a
thank you stormy1777 - it is your tutorial, I only put it together. It is the only tutorial that works
links unavailable due to site rules:
google for: ROM v10.2.5. global V10.2.5.0.PCMMIXM/pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global_efb78ff9c3.tgz
google for: patched boot v10.2.5. under: xiaomifirmware (dot) com how-to-install-twrp-and-magisk-root-on-redmi-7a
google for: TWRP: under: androidweblog(dot)com xiaomi-redmi-7a-root-install-twrp-recovery I took the version 3.3.1.-0
google for Magisk: Magisk-v20.1.zip
Install in fastboot mode and with Mi Flash Tool
flash: pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global
option: clean all
wait until the mobile phone is fully installed (will reboot automatically)
copy Magisk into the root directory on your phone
restart in fastboot mode (volume down + power button)
on PC:
rename twrp file to recovery.img
rename boot file to boot.img
copy boot.img and recovery.img on the PC in the directory, where adb drivers are
open power shell on the PC in the directory, where adb drivers are
type in the power shell window:
fastboot flash recovery recovery.img
Enter
then type in the power shell window
fastboot flash boot boot.img
Enter
then hold volume up + power button until it 2x starts and vibrates, then wait, it opens in TWRP
type install, find Magisk.zip in the phone root directory a flash
restart into system
done