Related
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, SafetyNet updates,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this TUTORIAL/GUIDE
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you a lot.
*/
This Tutorial/Guide is to install Magisk in Sony Xperia M4 Aqua. Tested in E2303
You need UNLOCKED BOOTLOADER and this TWRP (Download TWRP 3.2.1-0) (https://forum.xda-developers.com/m4-aqua/development/recovery-twrp-touch-recovery-3-1-1-0-t3636920).
Steps:
0.Remove any other root (SuperSU or Magisk) and Xposed. Make sure you have stock Sony Kernel.
1.Download BootBridge-Magisk-v14-M4A.zip
2.Boot TWRP (Volume DOWN + Power).
3.Flash BootBridge-Magisk-v14-M4A.zip
4.Reboot to system and update Magisk Manager (if needed)
5.Check "Preserve AVB 2.0/dm-verity", update to latest Magisk using "Direct Install", reboot and check SafetyNet.
6.(Optional) Install Systemless Xposed (don't forget Xposed Installer) and reboot. It takes 5 min to boot. (Android 6.0 = SDK 23) (https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268).
Systemless Xposed does not pass SafetyNet!!!
Thanks to:
@AdrianDC (BootBridge)
@dani020110 (TWRP for M4 Aqua)
@osmank3 (Steps to get Magisk v15.x working)
@topjohnwu (Magisk and Systemless Xposed Framework)
@rovo89 (Original Xposed Framework)
Google (Android)
Sony (Xperia M4 Aqua)
Me @YoshiX007 (Tutorial)
Old steps
Download Center
SuperSU: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Suhide: http://forum.xda-developers.com/apps/supersu/suhide-t3450396
Latest RootSwitch in first two posts (1.3.3.2 at writing time): https://www.asus.com/zentalk/tw/thread-173542-1-1.html
Minimal Fastboot: https://drive.google.com/file/d/0B7sssTaAqVsscWdRWVBaU05NWjA/view?usp=sharing Mirror: http://vlctv.webcindario.com/Xperia/MINIFASTBOOT.rar
Boot 26.3.A.0.131
Boot for E2303 (rename it to boot.img): https://goo.gl/PBXtNe
Boot for E2306 (rename it to boot.img): https://goo.gl/8sKHZ1
Boot for E2312 (rename it to boot.img): https://goo.gl/XYeqe2
Boot for E2333 AND E2363 (rename it to boot.img): https://goo.gl/ZzHOhL
Boot for E2353 (rename it to boot.img): https://goo.gl/IZRzKM
Boot 26.3.A.1.33
Boot for E2303 (rename it to boot.img): https://goo.gl/mVuWcu
Boot for E2306 (rename it to boot.img): https://goo.gl/2Z3NuK
Boot for E2312 (rename it to boot.img): https://goo.gl/6H9fiV
Boot for E2333 (rename it to boot.img): https://goo.gl/fhdVVW
Boot for E2353 (rename it to boot.img): https://goo.gl/8atYQm
Boot for E2363 (rename it to boot.img): https://goo.gl/ZsUupP
(OPTIONAL) If you want xposed
Material Design Xposed Installer: http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Xposed Framework 86.2 CheckMod https://drive.google.com/file/d/0B7sssTaAqVssc05GTVl1enJQb1U/view?usp=sharing
This Tutorial/Guide is for root and install Xposed in Sony Xperia M4 Aqua :highfive:
You need UNLOCKED BOOTLOADER.
Tested only in E2303 26.3.A.1.33 with Xposed installed, you need UNLOCKED BOOTLOADER.
It is easy
Resumed steps:
0.(If you have Magisk installed or you used this tuto before the update) Flash Magisk Uninstaller to get a clean start and flash latest Sony stock ROM.
1.Download needed files : your boot.img, minifastboot, (optional(xposed, xposed installer)) ,SuperSU and RootSwitch (Search in download center)
2.Flash your corresponding boot from Download Center and Start TWRP with volume UP (YES UP, NO DOWN).
3.1 Flash SuperSU ZIP.
3.2 Flash Suhide ZIP
4.1 Reboot and install RootSwitch 1.2.4
4.2 Reboot, disable root in RootSwitch and check SafetyNet.
5. Go away and play PoGO.
(Optional)
6. Go TWRP, clean dalvik/art cache, flash Xposed ZIP and install DVDandroid's Material Design Xposed Installer.
Explained Steps:
0.(If you have Magisk installed or you used this tuto before the update) Flash Magisk Uninstaller to get a clean start and flash latest Sony stock ROM.
1.Download (Search in download center) and copy:
TO PC:
MiniFastboot, (Search in download center)
To MINIFASTBOOT folder:
Your boot.img from download center
TO ExtSD:
SuperSU and RootSwitch. (Xposed Framework, Material Design Xposed Installer)
2.1. Flash boot (fastboot):
Code:
Go to MINIFASTBOOT folder and boot into fastboot mode, type in the shell:
fastboot devices
fastboot flash boot boot.img
fastboot reboot
2.2 Start TWRP Recovery: WITH VOLUME UP
Code:
2.2.1 Power off
2.2.2 Power on
2.2.3 When the yellow led lights and press volume UP and wait
3. Install ZIPs
Code:
3.1 Install SuperSU+Suhide
3.2 Reboot system
(It is going to take some time)
4.1 Install RootSwitch
4.2 Reboot, check "Stop all su daemons", disable root in RootSwitch and check SafetyNet.
(Optional) 4.3 Go TWRP, clean dalvik/art cache, flash Xposed ZIP and install DVDandroid's Material Design Xposed Installer.
5 ??????????
6. :victoryrofit!!!!!!!!:victory:
Thanks to:
@99poison victory:advise about every update :good
shakalaca from Asus Developer Club (RootSwitch)
@Chainfire (SuperSU, Suhide, Systemless Root...)
@osm0sis (Android Image Kitchen)
@DVDandroid (Material Design Xposed Installer)
@PiSpecialist (Base boot.img)
@topjohnwu (Systemless Xposed Framework)
Sony (Xperia M4 Aqua)
Google (Android,ADB and Fastboot)
Me @YoshiX007 (Tutorial and remodded kernels)
Little FAQ, Changelog (very very simple) + Attached screenshot
FAQ
Q:Sony updated firmware
A:Update via FlashTool and follow from step 1.
Q:It is in bootloop (After Magisk install)
A:Flash stock boot with FlashTool and try again.
Q:It is in bootloop (After Xposed install)
A:If it dures more than 10 min, force a reboot. If doesn't work, clean dalvik cache in TWRP.
Q:I have a 0 folder in internal storage
Ao NOT erase it and reboot.
Q:SafetyNet doesn't pass
A:Make sure Xposed is not enabled/installed and Magisk is updated.
Q:It isn't here
A:Ask here
v1 19-Sep_19-09_>
First tuto ------>_/
v2 10-Oct_10/10 ______________>
Update tuto and boot.img ------>_/
v3 11-Oct_11/10________________________________________________ _____________>
Add a screenshot, fix problems, erase warning as suhide is updated and and Magisk is not more necessary.----->_/
v4 14-Oct_14/10________________________________________________ ________>
Change root method, remove xposed in tuto and add resumed steps.------------------------->
v5 17-Oct_17/10________________________________________________ ________>
Change root method, add xposed in tuto and add an F.A.Q.------------------------------------->
v6 24-Oct_24/10________________________________________________ ________>
Fix some typos, rewrite title, new kernels and reorder steps-------------------------------------->
v7 26-Oct_26/10________________________________________________ ________>
Minor edits,update RootSwitch link (thanks @99poison) and change to goo.gl links--------------------------------->
v8 02-Jan_02/01________________________________________________>
Complete rework and method updated (HAPPY 2018!!)------------------------------ >
After installation, I get a message that the su binary files are out of date
In Magisk I have a phone that is a non-rooted (switches are locked), and there is installed frameworks Xposed
How to fix it ?
I have Xpeira M4 Aqua E2303
EDIT : ALL WORKS Thanks Bro
sorry, what mean android pay for it? i can't understand
Android Pay is a payment system based on NFC https://www.android.com/pay/
It is available in USA,UK,Singapore and Australia.
Thank you for your post! My son has a E2303 now with installed [Rom][6.0.1][e23xx][UB]prerooted stock xperia m4 aqua. But he can't use pokemon witch he kind of demands . Well so as the father that I am I have promised him I would look in to it. Well what do we need to do to get back to Sony stock ROM. I could only find FTF files for 5.0, and also I dont have a windows computer, only linux. Is there any .zip files with the original system on that kan be flashed thru twrp?
Ex
Use XperiFirm to download MM rom and flash it via FlashTool. It has CDA 1293-7731/Customised CH/26.3.A.0.131.
Enter the following lines once per computer:
$ sudo apt-get install mono-complete
$ sudo cert-sync /etc/ssl/certs/ca-certificates.crt
$ sudo certmgr -ssl -m https://software.sonymobile.com
(Enter Y when asked, you should be asked to do so twice)
Enter the following line to launch XperiFirm:
$ mono XperiFirm.exe
Click to expand...
Click to collapse
Can't install phh's root or xposed on E2306. Flashing goes fine, but magisk manager says they are not installed.
EDIT: I was using with DOWN twrp instead of UP, now everything works.
MrOrry said:
Can't install phh's root or xposed on E2306. Flashing goes fine, but magisk manager says they are not installed.
Click to expand...
Click to collapse
When you are in TWRP can you find bootlog-magisk.txt or fstab.kanuti in the File Explorer?
YoshiX007 said:
When you are in TWRP can you find bootlog-magisk.txt or fstab.kanuti in the File Explorer?
Click to expand...
Click to collapse
I can see the fstab.kanuti but not the magisk one. Eventhough in teh cache folder I see some magisk.log files. Also since I tried to use the e2303 boot image I am having LTE speed problems, I tried to fix it by flashing stock images and the boot image for e2306 In this post.
You are in wrong recovery (both are TWRP).
1.Turn off your phone
2.Turn it on
3.When you can see a yellow led press volume UP button and find bootlog-magisk.txt
PD: It is in / folder
Work fine on E2363 , boot take almost 20 minutes here but no problem after that , thank you
Not working on My E2312. I flashed to stock ftf file and installed recovery and flashed boot.img. And then, I did Wipe cache and dalvik, flashed Magisk Zip, phh's SuperUser ZIP and xposed systemless zips. Flashing is fine and seem no error. After install Magisk Manager APK and phh's SuperUser apk, I opened Magisk Manager apk and it displayed Boot version: Magisk v6, Root Status : Unrooted, selinux status: Enforcing and can't use root toggle. Please help me!
YoshiX007 said:
You are in wrong recovery (both are TWRP).
1.Turn off your phone
2.Turn it on
3.When you can see a yellow led press volume UP button and find bootlog-magisk.txt
PD: It is in / folder
Click to expand...
Click to collapse
Oh. I can't belive how I missed it, now magisk, xposed and root mounting works. Thank you!
How's the performance? And will you be posting any (frequent maybe?) updates (OTA)
@99poison Can you try this boot? https://drive.google.com/file/d/0B7sssTaAqVssd0cxUUpXc2JZV28/view?usp=sharing @JakeMini123 Performace should be like PiSpecialist's root boot.img. About OTAs I can't understand you but all magisk updates should work.
YoshiX007 said:
@99poison Can you try this boot? https://drive.google.com/file/d/0B7sssTaAqVssd0cxUUpXc2JZV28/view?usp=sharing @JakeMini123 Performace should be like PiSpecialist's root boot.img. About OTAs I can't understand you but all magisk updates should work.
Click to expand...
Click to collapse
Finally, it working for me. Problem is TWRP recovery ( I entered wrong twrp by pressing volume down + power button).
Problem solve >> I flashed your modified boot.img and Power off phone. To enter your twrp recovery, when Power on, I pressed volume up button when light is yellow color and I did your procedures. Now, my phone is system-less and root is also OK.
Thank you so much,
99poison
BTW, Pokemon working only when Xposed system-less is disabled otherwise it can't work with Magisk.
i cannot enter to the fastboot mode in the e2306. could you explain me how could I do it? I tried to flash magisk with the traditional TWRP, but my phone doesn't start, so I had to repair it using sony companion.
Try to flash your boot.img via FOTA-TWRP(normal recovery).
First put Magisk-E2306.img in your EXTERNAL SD.
When you are in TWRP main menu, go to Install, select Install Image, go to your external sd, press Magisk-E2306.img, select Flash BOOT and reboot
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device (and all of your apps and settings are the same)
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again ( to be sure ) - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
10. make TWRP backup when needed
11 IF YOU WANT TO UPDATE TO B02 : use this methode https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
EDIT : when you want to get rid of the bootscreen which states that you have an unlocked bootloader, follow this procedure (very easy )
https://forum.xda-developers.com/showpost.php?p=71444728&postcount=496
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
raystef66 said:
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
Click to expand...
Click to collapse
I'm on stock B29, rooted, unlocked bootloader.
Been avoiding updates, but this looks promising to keep root.
Think it will work for me? Forgot to mention I have 3.0.4 twrp
HTC55555 said:
I'm on stock B29, rooted, unlocked bootloader.
Been avoiding updates, but this looks promising to keep root.
Think it will work for me?
Click to expand...
Click to collapse
Don't know exactly.
For G users the latest update before 7.0 was the B10. Therefore B10 is the necessary flash before G users can flash N
As long as you keep TWRP running ( as far as i know do not wipe system etc...therefore i mentioned earlier to not wipe anything) and your latest backup, you can always restore it.
Hmm... I did this a week ago and forgot to flash SuperSU. Messed up big time... Axon7tool gives the what() error, but people say that even if it successfully flashes the recovery, the stock recovery remains there.
So I need the inverse process... any idea how?
Choose an username... said:
Hmm... I did this a week ago and forgot to flash SuperSU. Messed up big time... Axon7tool gives the what() error, but people say that even if it successfully flashes the recovery, the stock recovery remains there.
So I need the inverse process... any idea how?
Click to expand...
Click to collapse
Perhaps this will help : https://forum.xda-developers.com/showpost.php?p=71444519&postcount=494
unplug usb when you give command to flash twrp recovery, otherwise it always reflashes stock recovery....
Hope that helps
Thanks for the reply! I'll have to figure out how to make axon7tool work now. Much appreciated
Dear raystef66!
I'm on Resurrection Remix now-2017G (it is 7.1.1 based).I would like to have a stock 7.1.1.Can i just do the steps in your post 1,without flash b10, just flash
7.1.1 stock bootstack, system and Super SU?Would it working solution, to go from Resurrection Remix to stock 7.1.1 on 2017g?And will be twrp still prsent after those steps?
Thanks in advance!
ValVK said:
Dear raystef66!
I'm on Resurrection Remix now-2017G (it is 7.1.1 based).I would like to have a stock 7.1.1.Can i just do the steps in your post 1,without flash b10, just flash
7.1.1 stock bootstack, system and Super SU?Would it working solution, to go from Resurrection Remix to stock 7.1.1 on 2017g?And will be twrp still prsent after those steps?
Thanks in advance!
Click to expand...
Click to collapse
IMO you have to flash b10 too. Would do no harm though as long as you don't fully wipe system to keep twrp. As long as you keep a backup of twrp you can always go back. In worst case you have to flash twrp again in edl axon7tool.
@ValVK I flashed B03, then B08, then B10, and THEN B01, like any normal update. That because I don't know if B10 is only an incremental update
But after you flash the stock system, remember to root! You'll lose TWRP otherwise
Thanks all for responces! If i will go that way-flash in Twrp b08, then b10 and then Nuga, what should i wipe first in Twrp-all inclusive System, or just Factory reset? And if i will go that way, should my Twrp still intakt? (I would like avoid to Flash Twrp again, seems bit risky for me).
I had the official bootloader unlock but it broke the com.android.phone process on 7.1.1.
They are working on getting it fixed and once fixed will make the root publicly avialble.
The official root works on b10 marshmallow and is very easy to install.
@ValVK o sorry, I only flashed B03 :silly:
You should flash B03 THEN update via the native sdcard update on mifavor
raystef66 said:
Hi All,
To those who are interested in a safe flash to 7.1.1 from a stock B08 (or other version) rooted and unlocked BL :
First all thnx to @djkuz , @tron1, @iNaruX and all the others
1. First backup your device with TWRP. Put backup safely on SD in case you need it.
2. I did flash the latest TWRP 3.1.0.0 to my device. I used ADB Fastboot command (as you know) : fastboot flash recovery ....img
and fastboot reboot - done!
3. Make sure you have the following files on your SD :
* B10 flashable bootstack and stocksystem (from @djkuz)
https://mega.nz/#!xsAHyaJR!cro7nzJ1p6SA-St6vFJXS6SXRPf0KKRCSpDpxmz1Vro
https://mega.nz/#!5toCkJ7D!R6u-6dyVSbQRMqdHh_jQI-MKtlo-ORGJ-Yn7HvMuARk
* the 7.0 leaked bootstack and stocksystem (from @tron1)
https://www.androidfilehost.com/?fid=745425885120713802
https://www.androidfilehost.com/?fid=673368273298937254
* the 7.1.1 idem
https://www.androidfilehost.com/?fid=817550096634754697
https://www.androidfilehost.com/?fid=529152257862711840
* the SuperSU-v2.79-201612051815.zip
https://www.androidfilehost.com/?fid=385035244224405790
This steps i performed ( maybe other methods are better but with these steps i had no problems at all)
4. boot into TWRP
5. i did not WIPE anything (to keep my Apex launcher and all my settings and apps)
6. flash B10 bootstack and then system
7. reboot system - you will have the 'unlock system boot sreen' (no problem) - after 5 sec it will boot - all your apps are relaunched - you now have B10 on your device (and all of your apps and settings are the same)
8. reboot again in TWRP - flash 7.0 bootstack and system - flash also the SU2.79 before reboot - reboot system - your device reboots twice on logo - apps are being updated - you will boot ok and you have 7.0 !
9. reboot again into TWRP and flash 7.1.1 - flash SU2.79 again ( to be sure ) - reboot system - you have a clean boot - in my case the system asked with what launcher (APEX in my case) i had to start (choose yours) - you now have 7.1.1
10. make TWRP backup when needed
EDIT : when you want to get rid of the bootscreen which states that you have an unlocked bootloader, follow this procedure (very easy )
https://forum.xda-developers.com/showpost.php?p=71444728&postcount=496
So far i'm having no issues. Installing apps etc is much more fluent and quick - switching between apps is faster - gps and other stuff working like a charm (so far)
Battery stats : keeping you updated
ENJOY !
Click to expand...
Click to collapse
Hi, I am on the stock rom 7.0 nougat for the A2017G.
Can I just flash the leaked rom 7.1.1 for a2017g model??, I have no root, total stock.
Oliver Aa said:
Hi, I am on the stock rom 7.0 nougat for the A2017G.
Can I just flash the leaked rom 7.1.1 for a2017g model??, I have no root, total stock.
Click to expand...
Click to collapse
I suggest you wait for the 7.1.1 OTA update when you're not rooted etc.
I flashed through twrp the package made by tron1 for android 7.1.1 , the bootstack and supersu to make sure i have root install at the first boot but for some reason supersu framework gets deleted. I tried flashing supersu package multiple times and it gets deleted after boot up . How could i fix this ?
S0wL said:
I flashed through twrp the package made by tron1 for android 7.1.1 , the bootstack and supersu to make sure i have root install at the first boot but for some reason supersu framework gets deleted. I tried flashing supersu package multiple times and it gets deleted after boot up . How could i fix this ?
Click to expand...
Click to collapse
Did you follow my steps ? From which version did you come ? Were you already rooted....
Perhaps flash SU 2.79 (!) in edl mode and when it is resetting for a reboot, unplug your phone before it can reboot. You get a black screen. Just press Vol+/Power and when you see ZTE logo you release. Normaly you should/can enter TWRP.
But normaly my guide should work if you were rooted, BL unlocked and on stock ROM (B08 or earlier). I do not know which steps you already performed so it's just gessing.
What you guys think??
I want to know if I update my phone to this version, can I continue using xposed
Hello, can someone create TWRP files from the new B02 image?
Gesendet von meinem ZTE A2017G mit Tapatalk
@raystef66
I have a question:
Can step 8) be skipped? (flash 7.0=A2017GV1.1.0B01 bootstack and system, flash SU2.79).
Since in step 9) we will flash immediately 7.1.1B01=A2017GV1.2.0B01 bootstack and system, and flash SU2.79.
I guess step 8) is harmless, but not necessary. Is it true? Or are there other reasons for this?
Also maybe you could at end of this guide add a link to your another guide
https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
which continues the upgrade to 7.1.1B02=A2017GV1.2.0B02 keeping TWRP, unlock, fastboot and root?
Thank you.
dnlilas said:
@raystef66
I have a question:
Can step 8) be skipped? (flash 7.0=A2017GV1.1.0B01 bootstack and system, flash SU2.79).
Since in step 9) we will flash immediately 7.1.1B01=A2017GV1.2.0B01 bootstack and system, and flash SU2.79.
I guess step 8) is harmless, but not necessary. Is it true? Or are there other reasons for this?
Also maybe you could at end of this guide add a link to your another guide
https://forum.xda-developers.com/axon-7/how-to/guide-a2017g-install-b02-root-fb-t3590852
which continues the upgrade to 7.1.1B02=A2017GV1.2.0B02 keeping TWRP, unlock, fastboot and root?
Thank you.
Click to expand...
Click to collapse
IMO step 8 can not be skipped due to the fact you have to have 7.0 first. Could be wrong, but then again, it only last for a minute or so
I will ad the link to upgrade B01 to B02.
Thnx !
ps : did you get B02 with my method ? Pls post on thread if succeeded - thnx !
Official TWRP For Moto G5 Cedric
Post 1 - Instructions
Post 2 - FAQs
For full details and notes see
Official TWRP for Cedric Site
For TWRP news change logs etc see
TWRP Official Site
Instructions
For non rooted and rooted phones
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Download Official TWRP Image
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button)
Connect phone to PC
Open a command prompt where you have fastboot and the TWRP image file located
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed)
To permanently flash twrp replacing stock recovery
Code:
fastboot flash recovery recovery.img
To only boot to twrp temporarily keeping stock recovery
Code:
fastboot boot recovery.img
Select recovery using the volume keys and power button to select
Now read important notes section For Stock Rom Users at the end of this post and the FAQs in the 2nd post
Note for Windows 10 users who use the powershell and not cmd
The command will become
Code:
./ fastboot flash recovery recovery.img
Or
Code:
./ fastboot boot recovery recovery.img
For rooted phones only
If you are already rooted you can upgrade your TWRP version using the official TWRP app
Download TWRP App
Select Cedric as your device
Download the TWRP image
Select the TWRP to flash
Now read the FAQs in the 2nd post
Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing Magisk zip which will disable it for you
Source Code
TWRP 32bit For Cedric Github Source
TWRP 64bit For Cedric Github Source
XDA:DevDB Information
[Official] TWRP 3.5.2_9-0 Moto G5 Cedric [32/64bit Roms], Tool/Utility for the Moto G5
Contributors
TheFixItMan, JarlPenguin
Source Code: https://github.com/TeamWin/android_device_motorola_cedric
Version Information
Status: Stable
Current Stable Version: TWRP 3.5.2_9-0
Stable Release Date: 2021-04-05
Created 2017-11-03
Last Updated 2021-04-05
FAQs
Q - Does the official twrp version support 64bit roms?
A - Yes - as of version 3.4.0-1
Q - I get error 255 when trying to flash a rom
A - You are using a 32bit twrp version. Please update to the latest 64bit version
Q - Can I use the 64bit version on 32bit roms?
A - Yes the 64bit version supports both 64bit & 32bit roms
Q - Does the official twrp version support treble rom?
A - Yes - as of version 3.4.0-1
Q - Does this recovery support decryption of data
A - Yes on all current 32/64bit roms - If you swap roms you will need to format data first to remove encryption before flashing the new rom then you can encrypt again
Q - My phone keeps booting to recovery on restart and can only be started normally through the bootloader
A - First try removing your SD card and see if your phone boots - If that doesn't work see This Post
Q - Where is the disable dm-verity zip?
A - You can download it Here
or old version can be found Here
Q - Where is the Magisk zip
A - See Magisk Thread
You may need to manually install the magisk manager app apk depending on which rom you are using
Q - It says "image not signed or corrupt" when I flashed image
A - This is normal as the image is not signed by Motorola
Q - When restoring backup I get an error starting Extracttarfork
A - Sometimes you need to format data before restoring backup - In fastboot mode enter the command
fastboot erase userdata
This will format all data on internal storage (pictures music documents downloads etc) so backup first!
Reserved
Thanks
Happy to hear that we got the official twrp support
I have a cedric device. I unlocked my bootloader. Then through fastboot i tried to install twrp-3.1.1-0-cedric.img.
But it says "image not signed or corrupt".
As on the other threads, they said that to directly go into recovery mode ignoring other things. But that did not work. It said "no command".
Please help with flashing twrp.
Edit- It worked after 5-6 attempts.
aashaydesh said:
I have a cedric device. I unlocked my bootloader. Then through fastboot i tried to install twrp-3.1.1-0-cedric.img.
But it says "image not signed or corrupt".
As on the other threads, they said that to directly go into recovery mode ignoring other things. But that did not work. It said "no command".
Please help with flashing twrp.
Click to expand...
Click to collapse
It will always say that because the image is not signed by Motorola
As long as it says write OK at the end
The easiest way is to type
fastboot flash recovery then drag the recovery image into the terminal window - this will automatically complete the rest of the command
I'll also write a note for Windows 10 users who use the power shell
You need to put ./ first
Just to let everyone know about encryption on oreo roms
If you have previously encrypted your phone you must remove encryption before flashing an oreo rom by doing format data from the wipe menu (different from wipe data) & booting the phone fully to check encryption has been removed
You can then flash the oreo rom
After flashing this rom you can encrypt the phone again if you want
Encryption is fully supported
My TWRP (official) can decrypt data of lineageos 15 rom (32bit) as Iv just tested it
bootloop to recovery and SD-ext
I went through all this procedure of unlocking and installing twrp yesterday. As I nearly experienced a heart attack, I would like to kindly ask you to expand your Q/A-section for the mental safety of my fellow G5 users.
If you follow each step, you still can run into the bootloop-to-recovery trouble. My system was formatted with an SD-card as extended internal memory, and I formatted everything exept SD-ext, which I might have done. Clearing the misc partition had no success until I removed the SD-card, and rebooted TWRP.
So basically my recommendation is: remove your SD-card before the procedure.
Happy flashing and thank you for your guide.
TheFixItMan said:
FAQs
Q - My phone keeps booting to recovery on restart and can only be started normally through the bootloader
A - See This Post
Click to expand...
Click to collapse
No-New-Phone said:
I went through all this procedure of unlocking and installing twrp yesterday. As I nearly experienced a heart attack, I would like to kindly ask you to expand your Q/A-section for the mental safety of my fellow G5 users.
If you follow each step, you still can run into the bootloop-to-recovery trouble. My system was formatted with an SD-card as extended internal memory, and I formatted everything exept SD-ext, which I might have done. Clearing the misc partition had no success until I removed the SD-card, and rebooted TWRP.
So basically my recommendation is: remove your SD-card before the procedure.
Happy flashing and thank you for your guide.
Click to expand...
Click to collapse
Added to Faq and guide
Hi, sorry if this is a silly question, but just thought I'd ask to be on the safe side... Is it safe to flash TWRP 3.2.0 that is now available for cedric through the TWRP app or would it be better to give it a miss for now?
RaddingtonBear said:
Hi, sorry if this is a silly question, but just thought I'd ask to be on the safe side... Is it safe to flash TWRP 3.2.0 that is now available for cedric through the TWRP app or would it be better to give it a miss for now?
Click to expand...
Click to collapse
Should be fine - changelog on twrp site
New twrp version available
What's new in 3.2.0-0:
Allow restoring adb backups in the TWRP GUI (bigbiff)
Fix gzip backup error in adb backups (bigbiff)
Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)
Better support for installing Android 8.0 based zips due to legacy props (nkk71)
Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)
Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)
Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)
v2 fstab support (Dees_Troy)
Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)
Various other minor bugfixes and tweaks
Boot
Twrp 3.2 problem not shutdown phone always restart system
Go twrp and shutdown always restart system.Use Android 8 Oreo Rom
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
TheFixItMan said:
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Click to expand...
Click to collapse
Thanks a lot for maintaining cedric, you are king man
I unlocked the bootloader and flashed the twrp on my friends Moto g5 and after that if I restart it boots up to recovery only. I did all that's said in the xda forums and still the problem exists.i then wiped away all partitions and installed lineage 14.1. even now the problem exists. After lots of trying I found that going to bootloader and pressing start boots the phone normally. But it's tough to to it always he has to power on the phone. Can someone help me solve this problem
Sent from my Motorola Moto G 2014 using XDA Labs
ProGamer02224 said:
I unlocked the bootloader and flashed the twrp on my friends Moto g5 and after that if I restart it boots up to recovery only. I did all that's said in the xda forums and still the problem exists.i then wiped away all partitions and installed lineage 14.1. even now the problem exists. After lots of trying I found that going to bootloader and pressing start boots the phone normally. But it's tough to to it always he has to power on the phone. Can someone help me solve this problem
Sent from my Motorola Moto G 2014 using XDA Labs
Click to expand...
Click to collapse
Read the faq!
Nice
Thanks Men
Does it have support for 64 bit roms?
I'm a noob, excuse me if this is a stupid question
its not a stupid question but an obvious one
since you are new I will write cliff note steps in order for you to understand better
1. unlocking bootloader (needs miui permission 72 hours waiting time (it can be more) ~ verifying Sim to Miui account ~ enabling oem unlock under developer options
2. flashing Twrp ! ( you need Minimal Adb & fastboot 1.4.2 ~ in order to either BOOT temporarily in twrp (recovery) or flash Recovery to POCO
3. booting in to twrp (power+ VolumeUP button ~! hold until you see Twrp logo)
4. assuming you are in MIUI10, flash magisk19.3.zip, Magisk not only root your device, infact in order to do so, it will first disable dm-verity!
5. now device is rooted
HOWEVER!!!
if this is NOT WHAT YOU ARE ASKING
then there is a file called Lazyflasher.zip , if you flash this in twrp, it should disable dm-verity
more ?
use AIK (kitchen) or Super Kitchen to EXTRACT the kernel image in to differen files and alter settings in fstab and/or ramdisk and REPACK your kernel again in to .img file
YasuHamed said:
its not a stupid question but an obvious one
since you are new I will write cliff note steps in order for you to understand better
1. unlocking bootloader (needs miui permission 72 hours waiting time (it can be more) ~ verifying Sim to Miui account ~ enabling oem unlock under developer options
2. flashing Twrp ! ( you need Minimal Adb & fastboot 1.4.2 ~ in order to either BOOT temporarily in twrp (recovery) or flash Recovery to POCO
3. booting in to twrp (power+ VolumeUP button ~! hold until you see Twrp logo)
4. assuming you are in MIUI10, flash magisk19.3.zip, Magisk not only root your device, infact in order to do so, it will first disable dm-verity!
5. now device is rooted
HOWEVER!!!
if this is NOT WHAT YOU ARE ASKING
then there is a file called Lazyflasher.zip , if you flash this in twrp, it should disable dm-verity
more ?
use AIK (kitchen) or Super Kitchen to EXTRACT the kernel image in to differen files and alter settings in fstab and/or ramdisk and REPACK your kernel again in to .img file
Click to expand...
Click to collapse
thanks for replying. so by flashing magisk I'm disabling dm-verity on the kernel, right? again thanks for helping me out
Ashiq.makkar said:
thanks for replying. so by flashing magisk I'm disabling dm-verity on the kernel, right? again thanks for helping me out
Click to expand...
Click to collapse
Ashiq.makkar said:
thanks for replying. so by flashing magisk I'm disabling dm-verity on the kernel, right? again thanks for helping me out
Click to expand...
Click to collapse
yes i am on poco f1 using custom rom
in twrp
1. flash vendor firmware https://mirror.akhilnarang.me/MIUI/beryllium/beryllium-9.6.27-9.0-vendor-firmware.zip
2. flash the custom rom
3. flash GAPPS ( opengapps.org) take ARM64>9.0>Micro package
4. i flash Optimus Drunk kernel 26aug19.zip (optional)
5. MAGISK19.3.zip flashable
6. clean delvik/cache and REBOOT
however if you are in MIUI10 just perform step 5&6
first REBOOT may go in to BOOTLOOP but eventually MIUI10 will boot.
HOWEVER ALWAYS TAKE BACKUP!
YasuHamed said:
yes i am on poco f1 using custom rom
in twrp
1. flash vendor firmware https://mirror.akhilnarang.me/MIUI/beryllium/beryllium-9.6.27-9.0-vendor-firmware.zip
2. flash the custom rom
3. flash GAPPS ( opengapps.org) take ARM64>9.0>Micro package
4. i flash Optimus Drunk kernel 26aug19.zip (optional)
5. MAGISK19.3.zip flashable
6. clean delvik/cache and REBOOT
however if you are in MIUI10 just perform step 5&6
first REBOOT may go in to BOOTLOOP but eventually MIUI10 will boot.
HOWEVER ALWAYS TAKE BACKUP!
Click to expand...
Click to collapse
thank u so much.did exactly what u said.and everything works fine
64-bit Base Package For GSI Redmi 7A
Flashing instructions ?
• Boot to recovery
• Flash given zip file (Downloads section)
• Wipe system
• Flash any arm64 GSI of your choice to system image
• Format data, wipe cache
• Flash gapps, magisk, etc...
• Boot to system, congrats you're on arm64.
Changelog:
- Fixed camera service crashing.
- Gcams can now run on Enforcing mode.
- Swap is disabled by default in favor of ZRAM.
- Fixed more services crashing that just filled up the logcat.
- Changed to Global for better overlay compatibility
- ViperFX now works in Enforcing mode where as before it would be unstable.
- Camera doesn't take as long to launch now.
Old Changes (from previous vendor/post):
• Fix bt audio, cleanup audio configs
• Add exfat fix
• Fix headphones
• Fix video recording
• Enable pseudo-gyro (emulated gyroscope from miui)
Downloads :
Base
mirror link
Bugs ?
• VoLTE doesn't work (fix: https://t.me/Redmi7AUpdates/98)
Things to point out:
- As mentioned on the previous release, Pie and Amber/Erfan based GSIs can't boot on Enforcing mode, in which case the Permissiver v5 zip from #permissiver is necessary.
- The FM Radio fix found in notes doesn't work anymore, use this instead (http://www.mediafire.com/file/wgnysvjo362yuco/FM_Radio-Fix.zip/file) and flash through Magisk.
- If you are having any camera related issues then switch to Permissive mode.
-Fixed some stuff and made a new one.
-Sadly, upgrading directly from the old one isn't possible and formatting data is required, I tried to make it upgradable but with no success.
*Currently using Havoc os 3.8"
And credits to telegram redmi 7a team and for the developers who work so hard for this project I do not own this work
Join here need telegram app on windows and android and dont forget to like my post https://t.me/PineOfficial
just flash permissiver to make wired headphone work
for me blissrom arm64 is smooth with face unlock unless u use android 9 as base firmware to have encryption or else u cant add password
daizu said:
just flash permissiver to make wired headphone work
for me blissrom arm64 is smooth with face unlock unless u use android 9 as base firmware to have encryption or else u cant add password
Click to expand...
Click to collapse
True, use MIUI A9 base to get encryption working on TWRP.
No chance to get this working on MIUI?
iagm12 said:
No chance to get this working on MIUI?
Click to expand...
Click to collapse
theres no way and also memeUI sucks
Custom Roms GSIs are better
edit:
there is new a update bluetooth already fix and other bugs..
iagm12 said:
No chance to get this working on MIUI?
Click to expand...
Click to collapse
You could try to use this on a MIUI GSI ported from the Redmi 8 maybe, but I don't know if it would work completely.
Maybe Erfan's GSI builds? https://mirrors.lolinet.com/firmware/gsi/MIUI/
---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------
Also, not to nitpick, but my username is different in XDA.
https://forum.xda-developers.com/redmi-7a/how-to/redmi-7a-arm64-kernel-t4134381
I'm the kernel dev.
---------- Post added at 03:29 PM ---------- Previous post was at 03:24 PM ----------
Also, I'm going to try out Ubports if I can. It would be interesing to see if it would work because of the Q vendor.
Great Work, congrats <3
i have ask helios developer (maintainer of helios gsi) to resize the gsi of redmi 8 (redmi 8 has 3.5 gb raw image that cant be flash easy to our phone which has only 3gb)
"Flash any arm64 GSI of your choice to system image" i dont know what is this, but can u give me yours?
all using just twrp to flash?
How did you root your device? Im currently on MIUI 11.0.3 Q and there's no TWRP or any magisk rooting files/guide that is updated.
Good work btw. If you can share your rooting method and TWRP this can be an ALL IN ONE guide. Many thanks!
EDIT: Its working right now, but thing is I cant flash anything from internal storage, it shows weird letters (encrypted). Its Pitch Black Recovery 3.0. How did you solve this?
regularfanb0y said:
EDIT: Its working right now, but thing is I cant flash anything from internal storage, it shows weird letters (encrypted). Its Pitch Black Recovery 3.0. How did you solve this?
Click to expand...
Click to collapse
Had the same situation here on my 7A with TWRP, i also couldn't transfer the files via file Explorer from Windows to the 7A
because of the encryption (the copy and paste window doesn't do anything and disapears after a while).
Solution to this is:
Format Data > Yes
[Warning - outdated - OP has replaced the fw+vendor file 11.0.3 to 11.0.11]
Explaning some stuff about GSI basics
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i had all the needed files to give it a try.
Instructions how to get from some sort of a corrupt status xy --> StockRom
Because i did some testing with Rom's i needed a "starting point" = this means unlocked Bootloader, Stock Rom V11.0.3, recovery installed
This was necessary for me to find out what step causes problems and also to "reset" the boot.img if i used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status "xy" back to "starting point":
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
go to recovery by holding Vol-Up & Power
-->my starting point to testing different settings...
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section [Warning - outdated - OP has removed this file]
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead [EDIT: app doesnt work because of errormessage]
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
As already mentioned the FM Radio fix doesn't work, if you skip it LOS boots perfectly
another bug: No other color of the Notification LED than white
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
mYXiao said:
I had some troubles getting this running, but finally i made it
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i theoretically had all the files to give it a try.
But i had to flash Stock Rom for many times because i wanted to start from the same starting point so i could find out what step causes the problem
and also to "reset" the boot.img if i had used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status back to "my starting point" = this means unlocked Bootloader, Stock Rom V11.0.3 and recovery installed
[ beginning of loop
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
] end of loop -> my starting point to testing different settings...
go to recovery by holding Vol-Up & Power
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
I found out that the FM Radio fix doesn't work here, if you skip it LOS boots perfectly
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
Click to expand...
Click to collapse
Whats the FM radio GSI zip for?
List of GSIs I've tried on 11.0.3 64 bit
Boots:
Havoc OS (Camera and Screenrecording bug)
Bliss Q (Camera and Weird cutted corners)
Bootleggers (Camera, Weird cutted corners and Brightness cant adjust)
Evolution X (Camera and Brightness cant adjust)
LOS 17 (Camera)
Dont boot:
N/A
Anyone here have a fix for camera, Brightness, Screenrecording and weird cut corners?
regularfanb0y said:
Whats the FM radio GSI zip for?
Click to expand...
Click to collapse
If i boot LOS 17 without the FM radio GSI zip the default FM Radio App which should be preinstalled isn't. flashing the zip fixed that.
regularfanb0y said:
Anyone here have a fix for camera, Brightness, Screenrecording and weird cut corners?
Click to expand...
Click to collapse
All i can say is that i tested Camera, Weird cutted corners and Brightness and Screenrecording on LOS 17 based on 11.0.3 64 bit . Everything works so far
PS: Can you please edit your quote so only the lines you refer to getting repeated? thx
does it work with the feature ： wireless fm radio？
so you can play sky children of light with this or games 64 bit based?
mYXiao said:
I had some troubles getting this running, but finally i made it
If this GSI stuff is also new to you like it is to me:
When working with GSI it's important to understand that the version which is currently running on your device, lets say V10.2.5 for example,
has the same version of your patched boot image (actually the boot image is build to fit for the currently running version i guess)
In this Thread the Base (11.0.3 Q FW) must have the same Version as the currently running version.
At the beginning i didn't know how this should work out because in all the other GSI Rom guides there is a patched boot image file in use
but if you want to use this Base (11.0.3 Q FW) there is no V11.0.3 GLOBAL patched boot image file to use?, just russia.
(see https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305 link in download section)
but then i read somewhere that the boot img also/always is part of the stock image and then i saw that the actual stock image from c. mi. com homepage is V11.0.3.
the second thing that doesn't made sense to me was: does Base (11.0.3 Q FW) mean you only can run Android 10 on it and why are there "higher versions" like Base (11.0.7 P FW) for the older Android P?
but anyway i theoretically had all the files to give it a try.
But i had to flash Stock Rom for many times because i wanted to start from the same starting point so i could find out what step causes the problem
and also to "reset" the boot.img if i had used a patched one
So this was my loop i did everytime to get from some sort of a corrupt status back to "my starting point" = this means unlocked Bootloader, Stock Rom V11.0.3 and recovery installed
[ beginning of loop
Enter Fastboot mode (Vol-Down & Power)
Install Stock Rom "pine_global_images_V11.0.3.0.QCMMIXM_20200717.0000.00_10.0_global" from c .mi .com homepage by using the software "MiFlash 2020.3.14.0"
(if you use MiFlash for the first time go to Driver --> install & wait for weird message.)
(it's important to use the V11.0.3.0. if you want to run the "64-bit Base Package For GSI Redmi 7A")
if your bootloader is unlocked at this moment choose "clean all" at the bottom of MiFlash instead of "clean all and lock".
("clean all" always ends with the error "error: Not catch checkpoint (\$fastboot -s .*lock), flash is not done" but you can ignore this one)
After install Stock Rom is finished let the device boot to system
if you already have a unlocked bootloader and you used "clean all" option you can now shut down the device and then enter Fastboot mode (Vol-Down & Power)
if you used "clean all and lock" with a previous unlocked bootloader you can quickly unlock it again by entering Fastboot mode and using the "Mi Unlock" software for Windows.
if your bootloader was never unlocked before you now have to do the complete process:
enable the developer options, go to "Mi unlock status" and register/LOGIN ON YOUR DEVICE into Mi-Account, install "Mi Unlock" software on PC and then you can unlock it.
anyways, if your bootloader is unlocked - shut down the device and then enter Fastboot mode (Vol-Down & Power)
[not flashing boot.img, already mentioned why not ]
use fastboot to flash vbmeta.img
vbmeta file
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use fastboot to flash recovery.img
TWRP recovery
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305] end of loop -> my starting point to testing different settings...
go to recovery by holding Vol-Up & Power
Wipe Dalvik / ART cache, System, Data, Cache.
Format Data > Yes
Do not wipe Internal Storage!
copy the following files to the devices sdcard:
Base (11.0.3 Q FW) - fw_vendor_pine_64bit-rel_11.0.3MI.zip File from download section
"lineage-17.1-20200808-UNOFFICIAL-treble_arm64_bvN.img" (thats the one i've used but any arm64 GSI of your choice should work)
link in Download section at: https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Permissiver v5:
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
FM Radio fix: [EDIT: dont use this because LOS bootscreen will stuck in a flickering loop]
https://forum.xda-developers.com/redmi-7a/how-to/guide-install-lineage-os-17-x-redmi-7a-t4142305
use FM-Radio_(GSI).zip instead
https://forum.xda-developers.com/attachment.php?attachmentid=4937895&d=1580288989
worked for me, thanks @dmitrypershin2015
Flash fw_vendor_pine_64bit-rel_11.0.3MI.zip aka "Base (11.0.3 Q FW)"
Wipe system
Flash any arm64 GSI of your choice to system image
Reboot to Recovery
Flash Magisk (optional) (not tested here)
Flash Permissiver v5
Flash GApps (optional) (not tested here)
If you get 'insufficient space' error, first resize System partition.
Flash FM-Radio_(GSI).zip
Reboot system and enjoy.
I found out that the FM Radio fix doesn't work here, if you skip it LOS boots perfectly
Somewhere in the Forum there is a link to Permissiver v4 instead of v5, cant say if v4 works fine but v5 does
Click to expand...
Click to collapse
I have two redmi 7a phones, and I tried both. The first one worked the first try, but the second one does not let me install the gapps, I get error code 70 don't have enough space, I tried to resize system but I get an error and if I try again it works but when starting the phone it stuck in the logo (I already installed FM radio gsi). I don't understand why that happens
Jak08 said:
so you can play sky children of light with this or games 64 bit based?
Click to expand...
Click to collapse
I would also wish to know this, will this allow arm64 apps to run? this is a new one to me ? didn't know this was even possible