Custom GSI firmware [Global/EU]

Search This thread
By:
Advanced…
Y

YaAlex

Member
May 25, 2018
27
21
Odessa
zyxrhythm said:
System as root is completely different from 'A' and 'A/B' based on the link you have provided. And is irrelevant to my quest to know more about this new 'A and A/B' stuff. The link I have provided on my previous post stills stands, A and A/B is basically 'partitioning scheme' implemented on devices.

If @YaAlex say we have a separate partition for recovery on 7A - then 7A could be an A (still tentative).

BUT according to the link you have provided, and the question you have quoted "Why should I use GSI for A/B devices to some A-only devices?"

--> we need to flash A/B to 7A because we are working with Android 9 (PIE)
Click to expand...
Click to collapse
Its all because Google's new requirements and stuff
We are A only system as root
As most cheap phones with 16gb emmc launched on pie

---------- Post added at 07:32 AM ---------- Previous post was at 07:29 AM ----------
regularfanb0y said:
Have you flashed permmisiver.zip?
Click to expand...
Click to collapse
Of course, otherwise you will have bootloop on bootanimation.
 
zyxrhythm

zyxrhythm

Senior Member
Jun 24, 2013
62
17
Solano, Nueva Vizcaya
zyx.digital
YaAlex said:
Its all because Google's new requirements and stuff
We are A only system as root
As most cheap phones with 16gb emmc launched on pie
Click to expand...
Click to collapse

That settles it then - 7A is A.

And basically, A and A/B are partitioning schemes.

And the reason why we flash A/B on our 'A' 7A is because we are working with PIE.

---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
regularfanb0y said:
Curious but the BitGapps that is linked in the first post is for arm64 (link: https://forum.xda-developers.()com/android/software/arm64-bitgapps-pie-9-0-0-t3828515)

but this is the BitGapps for arm32 (link: https://forum.xda-developers.()com/android/software/arm-bitgapps-variants-t3959373)

which one we really use? i thought our device is an arm32 right? so why arm64 is linked in the first post?
Click to expand...
Click to collapse

Get gapps here: https://opengapps.org

Choose:
-ARM not ARM 64
-9.0
-pico (or whatever you want)
 
Last edited:
regularfanb0y

regularfanb0y

Senior Member
Oct 2, 2017
69
4
Roxas
zyxrhythm said:
Try This.

1. Download ( TWRP.zip, Magisk.zip, boot.img, GSI-ROM.img, vbmeta.img, permissiver.zip),

best to put TWRP.zip, Magisk.zip, boot.img, GSI-ROM.img, permissiver.zip on your external SD card (make sure the SD card formatted to FAT32).

And I suggest: have all/multiple of the boot.img in this thread for experimentation ( the multiple variants of TWRP as well - try em out ), and have multiple GSI.'img' on the SD card.

2. On your computer (As per OP) using 'fastboot' flash TWRP.img.
(You can skip the flashing of boot.img - you can use TWRP to flash it)

3 . Reboot to TWRP

4. On TWRP :
Wipe > Format Data > yes
Wipe > Advanced Wipe
put a check on
/System
/Dalvik/ART Cache
/Cache
> Swipe to Wipe
5 . back to the Main Menu of TWRP > Reboot > Recovery

6. Install > boot > select a boot.img > swipe to flash
7 . back to the Main Menu of TWRP > Reboot > Recovery

8. Install > system > select a GSI.img > swipe to flash
9 . back to the Main Menu of TWRP > Reboot > Recovery

10. Install > Magisk.zip > swipe to flash

11. back to the Main Menu of TWRP > Reboot > Bootloader

12 on fastboot (Bootloader): as per OP flash vbmeta.img then reboot (IDK if this is a must, I flashed this only once, I have tried about 5 GSI roms now without flashing it again)

-If you end up on recovery loop :
flash GSI.zip again via TWRP to /system:
back to the Main Menu of TWRP > Reboot > System

-If you end up on a Logo loop (The phone reboots on some ROM then boots the system correctly - allow the phone to reboot at least 3x before declaring it is on a Logo Loop):
you flashed the wrong GSI variant (use Arm32 Binder 64 variant)

-If you end up on a 'fastboot loop':
reflash the whole rom via xiaomi flashtool

-If wifi and sd card access does not work well:
reboot to recovery and flash permissiver.zip
Click to expand...
Click to collapse

when can you flash gapps? after everything?
 
E

extab

Member
Oct 6, 2019
19
15
zyxrhythm said:
And the reason why we flash A/B on our 'A' 7A is because we are working with PIE.
Click to expand...
Click to collapse

No. If that was true, there would be no Pie GSI images for aonly devices. But they do exist, like Phhusson's system-arm-aonly-gapps-su.img.xz. The reason why we flash A/B on our 'A' 7A is because we are system-as-root. Google's requirement is that all devices delivered with Pie (not to be confused with "upgraded to Pie") must be system-as-root. So another (less precise) explanation why we flash A/B on our 'A' 7A is that it was shipped with Pie.
 
E

extab

Member
Oct 6, 2019
19
15
zyxrhythm said:
Not sure if "How to certify a device for GSI " on OP is also what the zip from YaAlex on #237 is trying to resolve.
Click to expand...
Click to collapse
These are two different ways to resolve the certification problem. The OP suggests to register your modified device with google. On the other hand, the zip from YaAlex on #237 copies build properties from the vendor partition, so it pretends that the device is not modified.
 
zyxrhythm

zyxrhythm

Senior Member
Jun 24, 2013
62
17
Solano, Nueva Vizcaya
zyx.digital
extab said:
No. If that was true, there would be no Pie GSI images for aonly devices. But they do exist, like Phhusson's system-arm-aonly-gapps-su.img.xz. The reason why we flash A/B on our 'A' 7A is because we are system-as-root. Google's requirement is that all devices delivered with Pie (not to be confused with "upgraded to Pie") must be system-as-root. So another (less precise) explanation why we flash A/B on our 'A' 7A is that it was shipped with Pie.
Click to expand...
Click to collapse

"The reason why we flash A/B on our 'A' 7A is because we are system-as-root." >>>>> "Thing that started with PIE" '

On the article you have posted : "Android 9 must use "system-as-root". >>>> "Android 9 is PIE right"

IDK what your point is, really - you seem to be confused. I understood the article you have posted.

'--> we are working with "PIE".' -- are we not?'
-- or GSI really is "Gingerbread Super Ice cream sandwich"
-- oh so now I get it, the GSIs we are working with in this thread are for JB KK MM NOUGAT OREO or 10 or perhaps super beta of 11 and 12 , glad to know. I'll be noting that. Thanks.

Don't worry if I will be "working" with Android 10+ / Android 8- in the future I'll triple quote it in the post for you.

---------- Post added at 09:24 AM ---------- Previous post was at 09:22 AM ----------
extab said:
These are two different ways to resolve the certification problem. The OP suggests to register your modified device with google. On the other hand, the zip from YaAlex on #237 copies build properties from the vendor partition, so it pretends that the device is not modified.
Click to expand...
Click to collapse

Good to know. Coz I did not try that zip yet from @YaAlex. Thanks for the clarification.
 
Last edited:
regularfanb0y

regularfanb0y

Senior Member
Oct 2, 2017
69
4
Roxas
Tried flashing pixel experience without flashing GApps.

Problems are theres not much google apps and there is no gboard, gallery app and music app, forced me to sideload it. Stock camera quality is bad (?), videoplayback and videos by camera are buggy. Battery life is also noticeably draining faster compared to stock MIUI, also theres not much customization present but its a really smooth rom.

have anyone here tried AEX?

EDIT:
Flashed MSM_Xtended-201900828-a64-ab.img.xz, boots up with no major problems but no gapps. flashing OpenGAPPS-arm32-pico results in error because of the lack of space in system partition. An attempt to flash 32bit BitGApps results in a classic bootloop (no signs of booting up stuck in msm extended loading screen).

If someone can link a proper GApps it would be great!
 
Last edited:
J

jimbojumbo12

Member
Oct 19, 2019
5
0
YaAlex said:
Use miui 10 base
Gsi on miui11 base is broken
Click to expand...
Click to collapse

Is this also why I'm having "google play something" spamming the **** out of my notifications regarding my device not being "registered with google play protect" ? ( I can't recall the exact notification, I flashed stock after some 5 minute of not knowing what to do about those corners"
 
E

extab

Member
Oct 6, 2019
19
15
regularfanb0y said:
If someone can link a proper GApps it would be great!
Click to expand...
Click to collapse
There are several guides in this thread how to flash gapps, but my impression is that nobody really flashed them. I think I tried most of these guides and none of them worked for me (e.g., I succesfully resized the system partition when it was too small, flashed gapps, rebooted successfuly, but gapps were not working). Searching through this thread I could not find a single report on successful flashing gapps. Some people reported having gapps, but it seems that in all cases they were already installed in the gsi image. For me the most stable version was Phhusson's AOSP 9.0 system-arm32_binder64-ab-gapps-su.img.xz - here I did not complain about gapps, but it had other issues (with safetynet: I could not use my banking app).

I would love to hear a report on successful flashing GApps.
 
  • Like
Reactions: boody shaban
Y

YaAlex

Member
May 25, 2018
27
21
Odessa
extab said:
There are several guides in this thread how to flash gapps, but my impression is that nobody really flashed them. I think I tried most of these guides and none of them worked for me (e.g., I succesfully resized the system partition when it was too small, flashed gapps, rebooted successfuly, but gapps were not working). Searching through this thread I could not find a single report on successful flashing gapps. Some people reported having gapps, but it seems that in all cases they were already installed in the gsi image. For me the most stable version was Phhusson's AOSP 9.0 system-arm32_binder64-ab-gapps-su.img.xz - here I did not complain about gapps, but it had other issues (with safetynet: I could not use my banking app).

I would love to hear a report on successful flashing GApps.
Click to expand...
Click to collapse
I always succeeded in flashing gapps
Flash gsi, go to wipe, advanced wipe, select system only, tap on Repair or change filesystem, then on Resize, and swipe to confirm
Then flash OpenGapps arm 9.0 pico/nano
 
E

extab

Member
Oct 6, 2019
19
15
YaAlex said:
I always succeeded in flashing gapps
Flash gsi, go to wipe, advanced wipe, select system only, tap on Repair or change filesystem, then on Resize, and swipe to confirm
Then flash OpenGapps arm 9.0 pico/nano
Click to expand...
Click to collapse

Thanks, but this is exactly what I did. Which gsi image did you use? Which device (global/eu/...)? Maybe I'll give it another try
 
zyxrhythm

zyxrhythm

Senior Member
Jun 24, 2013
62
17
Solano, Nueva Vizcaya
zyx.digital
MDV106 said:
Not me. All gsi's I used work fine.

Ive been daily driving AOSP 9 with MicroG for over a month now and faced zero problems. Ita now my work phone and the battery lasts 3 days.
Click to expand...
Click to collapse

Does the screen lock work?

---------- Post added at 12:31 AM ---------- Previous post was at 12:06 AM ----------
regularfanb0y said:
Tried flashing pixel experience without flashing GApps.

Problems are theres not much google apps and there is no gboard, gallery app and music app, forced me to sideload it. Stock camera quality is bad (?), videoplayback and videos by camera are buggy. Battery life is also noticeably draining faster compared to stock MIUI, also theres not much customization present but its a really smooth rom.

have anyone here tried AEX?

EDIT:
Flashed MSM_Xtended-201900828-a64-ab.img.xz, boots up with no major problems but no gapps. flashing OpenGAPPS-arm32-pico results in error because of the lack of space in system partition. An attempt to flash 32bit BitGApps results in a classic bootloop (no signs of booting up stuck in msm extended loading screen).

If someone can link a proper GApps it would be great!
Click to expand...
Click to collapse

I have used Descendant with flashed pico Gapps. for 3 days now.
BTW the screen flickers, UI elements acting up and are gone - flashing the patch 10.2.25 from mais14, permissiver and the adb code for brightness issue on OP

Just use the descendant ROM posted on previous posts.

Sadly all ROMs I have flashed so far cannot set a PIN, pattern or password lock. Even the stock MIUI ROM .

---------- Post added at 12:37 AM ---------- Previous post was at 12:31 AM ----------
regularfanb0y said:
I've flashed 3 different GSI ROMs already and all of them cant detect my headset/headphones. Is anyone facing this problem?
Click to expand...
Click to collapse

The problem on my 7A is always SD card access.
ROMS cannot mount my 3 partition SD card .
And this is sometimes resolved by the permisser.zip on OP.

Though I always see the 20:... wifi mac - wifi and hotspot seem to work.

Did not experience any issues with the headphone port.
 
You must log in or register to reply here.

Similar threads

D
[Guide][Redmi 7A] TWRP, Root with Magisk, Custom ROM [GSI][Pie]
Replies
54
Views
73K
S
sleffy
J
[GUIDE][REDMI 7A] Root with Magisk on Miui 11.0.7 Global
Replies
19
Views
15K
immortal_jerk
immortal_jerk
D
[Guide] [GSI] Install Lineage OS 17.x [Q] Redmi 7A
Replies
6
Views
6K
M
mYXiao
Tupolef
[Guide][REDMI 7A][Linux][LineageOS] Full guide from stock to Custom LineageOs 18.1
Replies
24
Views
11K
D
dj-fiorex
D
[boot.img] Patched boot.img files & patching tool
Replies
56
Views
32K
Tupolef
Tupolef

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 16
    X
    xontax
    UPDATE 10/16/19


    I don't know why the development on XDA for redmi 7a is unbelievable lazy, but this is what I stole from 4pda!

    1.Unlock the bootloader if you have not already done so.
    2. Download vbmeta.img file (4 KB),
    Download patched_boot_10.2.5EU.img,
    https://filehorst.de/d/cFqIgsev,
    2a For patched boot 10.2.6. Global Download
    https://filehorst.de/d/cBeCunfm
    2b. For patched boot 10.2.5. Global Download
    https://filehorst.de/d/cDpHyAId
    3. Download recovery
    Code: 
    [URL="https://filehorst.de/d/cHyobAcd"]TWRP 3.3.1-1003 LRTeam[/URL]
[URL="https://filehorst.de/d/crqywBxx"]TWRP 3.3.1-1003-DX mod[/URL]
[URL="https://filehorst.de/d/cbvACbwB"]TWRP 3.3.1-1[/URL]

    4. Drop the vbmeta file into the adb folder. Next, rename the patched boot file to boot.img and paste it with recovery into the adb folder
    Code: 
    fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot

    For patched boot but generally for the launch of custom firmware on our phone, say thanks YaAlex3

    5. Reboot the phone by holding "volume + and power" the phone will reboot into TWRP
    6. Flash Magisk
    7. Download the GSI firmware. NEED A64 A / B . no other will do.
    https://xdaforums.com/project-treble/trebleenabled-device-development
    GSI Firmware (A64 A/B):
    • AOSP 9.0 v119 (special instruction: search for boot fix and flash certification)
    • Descendant 4.0.1
    • DotOS
    • EvolutionX
    • PE Plus
    • MSM Extended
    • /e/
    • PixelExperience
    • ViperOS 6.5
    • LineageOS
    And download and upload the Attached file Permissiver_v4.zip file (1.1 MB)

    8. Unpack the downloaded firmware, you should get a file with the extension .img We
    upload it to the USB flash drive. This can be done without leaving the recovery by simply connecting the phone via cable.
    9. Make the Data format, wipe System, Davlik / Cache
    8a. Install attached no-verity-encrypt-ysl to stay encrypted (optional)
    10. Select Install img below - select the firmware file - select System
    9a. If you like Gapps, Install BiTGApps Pie 9.0.0 (optional)
    https://xdaforums.com/android/software/arm-bitgapps-variants-t3959373
    11. Flash Permissiver_v4.zip
    12. Go back, select reboot - to the bootloader
    13. In the adb folder, launch the console by holding the Shift button on the keyboard and right-clicking in an empty area, select the
    line to open the command window.

    We enter the fastboot flash vbmeta and then fastboot reboot
    Code: 
    fastboot flash vbmeta vbmeta.img 
fastboot reboot
    Everyone is now waiting for the phone to turn on (at first it will reboot it's normal)
    Note: vbmeta can also be flashed before the start of the whole action, as you wish.
    Note 2: If suddenly there is no memory card, you can wipe System, flash everything and format the latest date.

    Important Notes (FAQ)

    [ROOT]Video recording fix:
    put
    media.camera.ts.monotonic=0
    to /vendor/build.prop

    [ROOT] Fix brightness
    Turn on USB debugging, run the terminal \ cmd on the PC, write
    Code: 
    adb shell 
su 
setprop persist.sys.qcom-brightness $ (cat / sys / class / leds / lcd-backlight / max_brightness)

    Rejoice.

    How to certify a device for GSI
    Important: If you are at the initial setup stage, you must complete it. If notifications about the need for certification interfere, disable them.
    We need to find our GSF Device-ID
    1. Download the application
    2. Copy “Google Service Framework (GSF) there.”
    3. Go here , paste and click the button.

    Or Just flash this zip and you are good to go
    https://drive.google.com/file/d/1DTGpGrcjweZbN9wUdSSq8uQTmgxf0aD2/view
    View
    4
    M
    MDV106
    mais 14 said:
    You'll most probably lose ALL your data your phone. Please use with extreme caution!
    we not responsible for anything that may happen to your phone by installing any custom ROMs

    first of all check if enabled ARB protection.

    check miui rom version and if is global international or global eu something like PCMEUXM 10.2.5 or indian vers.

    1. Unlock the bootloader with miu unlock tool
    2. Download recovery and vbmeta.img file download from first post
    3. Download patched_boot {if you need root } *for the time being only 10.2.5 glopal eu and 10.2.5 glopal intern/nal rom don't use for another version because you will have problems with wifi sim card and brick. for all other versions skip this steps.

    https://drive.google.com/file/d/1cGbHxuKgppaUE4Ik8zBzpcEzIDU21E-Z/view?usp=sharing
    https://filehorst.de/download.php?file=cFqIgsev

    4.rename the patched boot file to boot.img{skip if dont need root} and paste it with recovery into the adb folder
    Reboot the phone by holding "volume - and power" the phone will reboot bootloader

    Fastboot flash recovery recovery.img
    fastboot flash boot boot.img
    fastboot reboot
    { holding "volume + and power" the phone will reboot into TWRP}

    5. Unpack the downloaded firmware
    6. Make the Data format, wipe System, Davlik / Cache
    7. Select Install img below - select the firmware
    file - select System
    8. reboot recovery flash open gapps arm 9 pico
    {if need} only aosp rom
    9. reboot recovery flash the last magisk for root {skip if dont need root}
    10. flash permissiver v4 zip download from first post
    11. Go back, select reboot - to the bootloader
    12. Drop the vbmeta file into the adb folder and flash vmbeta with
    fastboot flash vbmeta vbmeta.img
    fastboot reboot

    For this solution, say thanks to YaAlex3.xontax

    Fix the 泥evice is not Certified by Google https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-errorhttps://

    tested gsi rom aosp pie by phhusson with gapps
    or vanilia
    dotos vanilia arm 64-a/b
    pixel expiriance plus arm 64-a/b
    aosp 9 with micro g project { thanks mdv106}
    Click to expand...
    Click to collapse

    Thanks for the updated solution.

    Just a note: The AOSP 9 Rom with microG also needs to be arm32binder64-a/b. A link to the Rom is available somewhere in this thread.

    I am using it as my daily driver. It is the most stable one I have tried so far and is very fast and light with incredible battery life. i have Magisk and EdXposed installed with no issues in performance. Its been close to 2 days with a single charge and my battery just went under 70%. See screenshot below.
    View
    4
    M
    mais 14
    Only gsi rom Aosp 9 pie system arm 32 -binder 64 by phhusson

    Working and working without any problem with open gapps magisk . thanks xontax for flash
    instructions.
    View
    4
    zyxrhythm
    zyxrhythm
    Installing Descendant

    For those interested in running descendant ROM on their 7A and wants to know how I made it work:

    First thing first: You will need your computer for 3 things:
    1. Flashing the stock firrmware
    2. Flashing TWRP
    3. Fixing the brightness issue: ( cant dim the brightness ).

    The Procedure:
    Using your PC:
    1. Flash the stock 10.25 ROM - https://xiaomifirmwareupdater.com/miui/pine/
    using the flashtool - https://www.xiaomiflash.com/download/ ( dont forget to turn off "clean and lock" )
    2. Flash TWRP (LR Team) - from OP - https://filehorst.de/download.php?file=cHyobAcd

    Using TWRP:
    3. Wipe : ---System ---Dalvik/ART Cache ---Cache
    4. Flash patched 10.25 boot.img - https://drive.google.com/file/d/1sNHNeKnLlZZUjeC06Efd-l8MCeueLMQI/view?usp=sharing
    and vbmeta.img - https://xdaforums.com/attachment.php?attachmentid=4816700&d=1567931119
    5. Flash system.img (Descendant ROM) https://androidfilehost.com/?fid=6006931924117932459
    6. Reboot back to recovery
    7. Flash Magisk ( I used Magisk 19.4 back then) https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
    8. Flash permissiver.zip - from OP- https://xdaforums.com/attachment.php?attachmentid=4816701&d=1567931295
    9. Flash Open Gapps (ARM - pico - 9.0) - https://opengapps.org/
    10. Flash YaAlex's zipped fix for google certification - https://drive.google.com/file/d/1DTGpGrcjweZbN9wUdSSq8uQTmgxf0aD2/view
    11. Reboot to System

    Important! After attempting to reboot to system and you end up going back to recovery,
    On TWRP - Go to 'Wipe' - select 'Format Data' - type yes then swipe - once the format is completed Reboot to System

    12. Once Descendant has booted - on Magisk Manager look for the "Riru Core" "Riru EdXPosed" and "Safety Patch" flash them, then reboot.
    13. Download and Install the xposed apk - https://androidfilehost.com/?fid=11410963190603845164

    Using your PC:
    14. Enable USB debugging (should be enabled by default ) Connect your phone to PC and execute the following as per OP
    adb shell
    su
    setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)

    Done..
    View
    3
    M
    MDV106
    Confirmed working ROMS:
    AOSP with gapps: https://github.com/phhusson/treble_...v119/system-arm32_binder64-ab-gapps-su.img.xz
    AOSP without gapps: https://github.com/phhusson/treble_.../system-arm32_binder64-ab-vanilla-nosu.img.xz
    dotOS without gapps: https://sourceforge.net/projects/do...4_ab-UNOFFICIAL-20190918-0616.img.xz/download

    All of the above roms are arm32_binder64 for A/B devices. Nothing else will boot. do not bother with A only roms, they dont work.
    View

New posts