Just bought a Mi A2 Lite, but instead of the expected Android One, i have Lineage OS in it.
That by itself wouldn't be a problem, i wanted to install LineageOS on my phone for a long time, but never got myself to do the whole rooting process.
My problem is, i bought this one with the only purpose of playing PokemonGO and Ingress, both of which doesn't currently run on it, which seem to be related to my device failing SafetyNet test.
Anybody have any idea how should i proceed? Maybe re-locking the Bootloader is enough or do i have to fully root it? If so, how do i do it?
Extra info:
Bootloader seems to be unlocked, but doesn't seems to be rooted.
IMEI from box, phone (using *#06#) and back of the phone are the same, and all of them check as being an Mi A2 lite on mi.com.
Pulling it's build.prop it gives:
ro.product.name=daisy and
ro.product.device=daisy_sprout
But doing "fastboot getvar all" i got:
"product:sakura" so it might be a Redmi 6 pro.
Returning is not an option, since it's not damaged i can only trade for another of the same model, which the shopkeeper showed me at least 2 more with the same OS, so fixing this one would be the easier solution.
Chambs said:
Just bought a Mi A2 Lite...
But doing "fastboot getvar all" i got:
"product:sakura" so it might be a Redmi 6 pro.
Returning is not an option, since it's not damaged i can only trade for another of the same model, which the shopkeeper showed me at least 2 more with the same OS, so fixing this one would be the easier solution.
Click to expand...
Click to collapse
You bought a Mi A2 Lite and got a Redmi 6 Pro. This alone is reason enough to withdraw the purchase and to get your money back. If the shop knows that he sells counterfeit devices, I personally would even think about taking legal actions
And don't relock the bootloader while any custom rom or rooted stock is installed , you would brick your device.
thorin0815 said:
You bought a Mi A2 Lite and got a Redmi 6 Pro. This alone is reason enough to withdraw the purchase and to get your money back. If the shop knows that he sells counterfeit devices, I personally would even think about taking legal actions
And don't relock the bootloader while any custom rom or rooted stock is installed , you would brick your device.
Click to expand...
Click to collapse
I live in Brazil, we don't have official Xiaomi stores, we get the phones from importers that prolly bought it in Paraguay or such.
I can't return it because it's not damaged and i tried to trade for another A2, but all the A2 Lite there and even of neighbor stores had the same LineageOS in it.
Chambs said:
I live in Brazil, we don't have official Xiaomi stores, we get the phones from importers that prolly bought it in Paraguay or such.
I can't return it because it's not damaged and i tried to trade for another A2, but all the A2 Lite there and even of neighbor stores had the same LineageOS in it.
Click to expand...
Click to collapse
Of course you can return a fraud device without any other reason.
I wonder if they actualy found a way to flash the daisy firmware to a Redmi 6 Pro or if they just spoofed the build.prop of a Redmi 6 Pro's LineageOS. You can check if you have daisy's or sakura's partition table from adb (no need to use su for that):
Code:
adb shell "ls /dev/block/by-name |grep -e boot -e system -e vendor"
If you have a Mi A2 Lite firmware, you shoud have a/b slots for each partition like this :
Code:
aboot_a
aboot_b
boot_a
boot_b
system_a
system_b
vendor_a
vendor_b
Otherwise in the Redmi 6 Pro case it should give this :
Code:
aboot
boot
system
vendor
If you're actually on a A2 Lite firmware, you can just clean flash the stock and you'll be on a Mi A2 Lite; but if it's Sakura's firmware, it has rollback protection and you have no way to actually go to a Mi A2 Lite FW, and in this case I don't know how they did with the IMEIs. Here, if you have actually no way to return the phone, to fix safety net, you would need to install TWRP and correctly install magisk (the Redmi 6 Pro one ofc) and eventually correctly install LineageOS without all the daisy bs.
GDFI said:
I wonder if they actualy found a way to flash the daisy firmware to a Redmi 6 Pro or if they just spoofed the build.prop of a Redmi 6 Pro's LineageOS. You can check if you have daisy's or sakura's partition table from adb (no need to use su for that):
Code:
adb shell "ls /dev/block/by-name |grep -e boot -e system -e vendor"
If you have a Mi A2 Lite firmware, you shoud have a/b slots for each partition like this :
Code:
aboot_a
aboot_b
boot_a
boot_b
system_a
system_b
vendor_a
vendor_b
Otherwise in the Redmi 6 Pro case it should give this :
Code:
aboot
boot
system
vendor
If you're actually on a A2 Lite firmware, you can just clean flash the stock and you'll be on a Mi A2 Lite; but if it's Sakura's firmware, it has rollback protection and you have no way to actually go to a Mi A2 Lite FW, and in this case I don't know how they did with the IMEIs. Here, if you have actually no way to return the phone, to fix safety net, you would need to install TWRP and correctly install magisk (the Redmi 6 Pro one ofc) and eventually correctly install LineageOS without all the daisy bs.
Click to expand...
Click to collapse
By doing
Code:
adb shell "ls /dev/block/by-name |grep -e boot -e system -e vendor"
i got an error saying that the folder didn't exist, but by exploring the folders a little and doing
Code:
adb shell "ls /dev/block/bootdevice/by-name |grep -e boot -e system -e vendor"
I got:
Code:
aboot
abootbak
boot
system
vendor
So i guess It's actually a Redmi 6 Pro?
Chambs said:
Code:
adb shell "ls /dev/block/bootdevice/by-name |grep -e boot -e system -e vendor"
I got:
Code:
aboot
abootbak
boot
system
vendor
So i guess It's actually a Redmi 6 Pro?
Click to expand...
Click to collapse
Yep, it's definitely a Redmi 6 Pro.
Related
Dear all,
When looking at the recent HTC Hero update firmware released from HTC i was curious to why they had included adb.exe and fastboot.exe in the upgrade program, so I started looking into this. Basicly I made replacement tools for adb.exe and fastboot.exe that simulated the behavior of a phone to be on the safe side.
From this session I learned two things. First of all we can upgrade the rom.zip via both OSX, Linux and Windoze. Secondly there is a special boot mode called oem-78 which enabled RUU bootloader mode.
Some other notes also is that my bootloader was delivered with factory hboot version 1.76.0007, but even with this bootloader while in RUU mode the bootloader does not seem to check signature when trying to boot cm-hero-recovery.img. It crashes on boot tought, but this seems to be another way in for booting unsigned images...
Another interesting note is that my device was factory programmed with firmware 2.73.751.4, while the upgrade released yesterday is 2.73.405.5.
This is the resulting log from what the ARUWizard is actually doing.
I did not investigate futher after fastboot flash zip rom.zip, so there might be more needed to do after this, so proceed with caution if you want to try this.
Code:
# Get list of attached devices
$ adb devices
# Check battery power for detected device.
$ adb -s <SN> shell cat /sys/class/power_supply/battery/capacity
# Get current firmware version.
$ adb -s <SN> shell getprop ro.build.description
# Reboot into bootloader with RUU mode enabled.
$ adb -s <SN> shell reboot oem-78
# Check if device is is disconnected from usermode
$ adb devices
# If not present any more, check via fastboot
$ fastboot devices
# If detected, check if in RUU mode
$ fastboot -s <SN> getvar boot-mode
# If mode returns RUU, start the upgrade by erasing cache
$ fastboot -s <SN> erase cache
# Upload rom.zip file and flash
$ fastboot -s <SN> flash zip rom.zip
Best regards,
Exion
Diator said:
I am in Taiwan, i bought the Hero 1 week ago and the default firmware is 2.73.751.4
Click to expand...
Click to collapse
Same here. I bought mine a few days ago in Taiwan. This is the new version where they ship 1 extra microSD that is 8GB class 6 (as well as the old 2GB card). The handset itself is standard HTC Hero white, but the firmware is Chunghwa telecom branded.
I have attached my build.prop file which should give most info regarding this firmware for those interested.
Best regards,
Exion
So I'm on the M5s Plus and Android Pay doesn't work.
Does Pay work on the Mi5s?
When attempting to add a card, error says:
Android Pay can't be used
Google is unable to verify that your device or the software running on it is Android compatible
MIUI Global 8.0.1.0
Check your version again, there is no 8.0.1.0. Official release is 8.0.10.0, "global custom rom" is 8.0.10.0.0. If you have the second one, there it probably doesn't work because your bootloader is unlocked.
If you indeed have the rare original Chinese/English ROM, then go into settings -> connections -> NFC and there somewhere (I sadly don't yet have the phone) you have to switch from MI Pay to the other possible setting. Then it should work.
hey thanks for the input. Am definitely on 8.0.1.0 here.
i tried your suggestion and switched the nfc pay method but that didn't help so it must be detecting something in the rom. this is rather curious
Oohh you're a Plus user, didn't read that when I replied the first time. Yeah there the software releases are different. Your SIM card is payment enabled? I needed a new sim card when I tried this the last time here, but not with Android Pay, as we don't have that yet here.
Anyway found this: http://en.miui.com/forum.php?mod=viewthread&tid=402053&extra=&highlight=android+pay&page=2
Sounds like there is a bug in the new Global Release of MIUI official
Here the official manual on how to enable it: http://en.miui.com/thread-405166-1-1.html
I have Mi5s plus on same Global Rom. I had to lock boot loader for android pay to work.
Sent from my iPad using Tapatalk
How to relock the bootloader? I try to use "fastboot oem lock" to relock the bootloader. After reboot the phone, the bootloader is still unlock. What's wrong? I am using Xiaomi Mi 5s.
You can relock in miflash, but I don't know if that works without flashing it.
I compared the two .bat files (flash_all.bat and flash_all_lock.bat) and the difference is this:
fastboot %* flash userdata %~dp0images\userdata.img || @ECHO "Flash userdata error" && exit /B 1
fastboot %* erase devinfo || @ECHO "Erase devinfo error" && exit /B 1
I don't exactly know what those commands do, so I wouldn't execute them!
The .sh file has those differences:
fastboot $* erase devinfo
if [ $? -ne 0 ] ; then echo "Erase devinfo error"; exit 1; fi
So for me it looks like the erase devinfo file is the re-lock command, not sure why that should do it tough.
In MiFlash you could try this command flash_all_except_storage.bat. That would flash your phone again, but should not delete your apps and data, but I'm not entirely sure
I also tried to use flash_all_lock.bat to flash the global ROM. After flashing the ROM successfully, the unlock status shown by "fastboot oem device-info" is true also. I think the boot loader is also unlocked, and I can't pass the CTS profile test so that I can't use Android Pay.
patoberli said:
You can relock in miflash, but I don't know if that works without flashing it.
I compared the two .bat files (flash_all.bat and flash_all_lock.bat) and the difference is this:
fastboot %* flash userdata %~dp0images\userdata.img || @ECHO "Flash userdata error" && exit /B 1
fastboot %* erase devinfo || @ECHO "Erase devinfo error" && exit /B 1
I don't exactly know what those commands do, so I wouldn't execute them!
The .sh file has those differences:
fastboot $* erase devinfo
if [ $? -ne 0 ] ; then echo "Erase devinfo error"; exit 1; fi
So for me it looks like the erase devinfo file is the re-lock command, not sure why that should do it tough.
In MiFlash you could try this command flash_all_except_storage.bat. That would flash your phone again, but should not delete your apps and data, but I'm not entirely sure
Click to expand...
Click to collapse
That's weird. I unlocked my phone (to be able to flash global rom) and then flashed it with the lock option and it passes the CTS test.
Chinese stable rom(MIUI 8.0.22) not working with android pay and octopus card
Hello my friends,
today i will show you how to rebrand your device credits @Pretoriano80 @LastStandingDroid @mankindtw @Atarii and all the others from P20 Lineup Telegram :good::good::good:
DONT TRY TO REBRAND L29 to L09 or vice versa will brick or have problems !
1.Unlock Your Bootloader via Huawei Site
2.Root your P20 with Patched Ramdisk https://forum.xda-developers.com/huawei-p20/how-to/magisk-root-t3777612
3.Get the Stock Firmware Files you want to use from Firmwarefinder or other Source and rename the files
update_data_full_public.zip -> update_data_public.zip
update.zip -> update.zip
update_full_EML-L29_hw_eu.zip -> update_all_hw.zip
4.Copy them via MTP to your internal memory
5.Boot into fastboot mode and flash no check recovery from @Atarii / @mankindtw find it here (https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085)
fastboot flash recovery_ramdisk recovery_ramdisk_BKL-L04_nocheck.img
6.Install Magisk Manager
7.Download oeminfo binary file https://mega.nz/#!X0AjASKS!KvXMfbtd8S3kPNZZO1Lm6bKHDyXGqXlBi0SDZdzJwfo copy to internal memory
8.Boot into Android System enable adb debbuging in developer settings.
9.copy oeminfo to internal memory
10.adb shell
11.su
12.accept the prompt at your P20
13.mkdir /data/local/tmp
14.mv /sdcard/oeminfo /data/local/tmp
15.cd /data/local/tmp
16.chmod +x oeminfo
17. ./oeminfo EML-L29 C432 hw/eu
18. mkdir /data/update/HWOTA
cd /sdcard/
19.mv *.zip /data/update/HWOTA
20.Paste recovery command:
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_all_hw.zip" >> /cache/recovery/command
exit
21.adb reboot recovery
22.Phone will reboot and starts to install and Rebrand your Phone
Please always use the same Region C432 for Brand and Firmware Files
THX for the TuT....
Have you a source for the Stockrom?
Wait some times good things are coming
Work for me. Big Thx
Nice, thanks.
crucky said:
Hello my friends,
today i will show you how to rebrand your device credits @Pretoriano80 @LastStandingDroid @mankindtw @Atarii and all the others from P20 Lineup Telegram :good::good::good:
DONT TRY TO REBRAND L29 to L09 or vice versa will brick or have problems !
1.Unlock Your Bootloader via Huawei Site
2.Root your P20 with Patched Ramdisk https://forum.xda-developers.com/huawei-p20/how-to/magisk-root-t3777612
3.Get the Stock Firmware Files you want to use from Firmwarefinder or other Source and rename the files
update_data_full_public.zip -> update_data_public.zip
update.zip -> update.zip
update_full_EML-L29_hw_eu.zip -> update_all_hw.zip
4.Copy them via MTP to your internal memory
5.Boot into fastboot mode and flash no check recovery from @Atarii / @mankindtw find it here (https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085)
fastboot flash recovery_ramdisk recovery_ramdisk_BKL-L04_nocheck.img
6.Install Magisk Manager
7.Download oeminfo binary file https://mega.nz/#!X0AjASKS!KvXMfbtd8S3kPNZZO1Lm6bKHDyXGqXlBi0SDZdzJwfo copy to internal memory
8.Boot into Android System enable adb debbuging in developer settings.
9.copy oeminfo to internal memory
10.adb shell
11.su
12.accept the prompt at your P20
13.mkdir /data/local/tmp
14.mv /sdcard/oeminfo /data/local/tmp
15.go to /data/local/tmp
16.chmod +x oeminfo
17. ./oeminfo EML-L29 C432 hw/eu
18. mkdir /data/update/HWOTA
19.mv *.zip /data/update/HWOTA
20.Paste recovery command:
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_all_hw.zip" >> /cache/recovery/command
exit
21.adb reboot recovery
22.Phone will reboot and starts to install and Rebrand your Phone
Please always use the same Region C432 for Brand and Firmware Files
Click to expand...
Click to collapse
go to /data/local/tmp
sh: go: not found
chmod +x oeminfo /data/local/tmp
chmod: oeminfo: No such file or directory
---------- Post added at 10:19 PM ---------- Previous post was at 10:13 PM ----------
mrrib said:
Work for me. Big Thx
Click to expand...
Click to collapse
how work it for u? :/ i have errors :/
go to /data/local/tmp
sh: go: not found
chmod +x oeminfo /data/local/tmp
chmod: oeminfo: No such file or directory
Elizage2015 said:
go to /data/local/tmp
sh: go: not found
chmod +x oeminfo /data/local/tmp
chmod: oeminfo: No such file or directory
---------- Post added at 10:19 PM ---------- Previous post was at 10:13 PM ----------
how work it for u? :/ i have errors :/
go to /data/local/tmp
sh: go: not found
chmod +x oeminfo /data/local/tmp
chmod: oeminfo: No such file or directory
Click to expand...
Click to collapse
Thats don´t work. I have install Rootexplorer and copy the data manual in the directorys.
Sorry for my bad english
my mistake fixed it
crucky said:
my mistake fixed it
Click to expand...
Click to collapse
hey, can u help me??? i want to rebrand P20 Pro by that method after command adb reboot recovery it reboots in TWRP and does not start install
You dont need TWRP -.- you have to flash no check recovery !
How can I lock the BOOTLOADER again, except for the next FASTBOOT lock?
Hi,
About this step,
"17. ./oeminfo EML-L29 C432 hw/eu"
What if i want to change to C636, do i need to change the "C432" to C636" ?
Thanks.
correct but you also need C636 stock firmware !
Rebrand worked perfectly to get root, from Phh AOSP rom with root, disabled. I lost my backups by being to enthousiastic with wiping
What about warranty? If I will use this method on my p20 and for example everything will be working, but I will broken my phone. The warranty will be working in this particular case? Thanks
MrSkitter said:
What about warranty? If I will use this method on my p20 and for example everything will be working, but I will broken my phone. The warranty will be working in this particular case? Thanks
Click to expand...
Click to collapse
Of course there would be no warranty if you rebrand your phone
MrSkitter said:
What about warranty? If I will use this method on my p20 and for example everything will be working, but I will broken my phone. The warranty will be working in this particular case? Thanks
Click to expand...
Click to collapse
otonieru said:
Of course there would be no warranty if you rebrand your phone
Click to expand...
Click to collapse
It actually depends on your local law. Hardware failure is always covered where i live. They can however bill me a service charge if the phone get's delivered with non standard ROM. So if i'm able to restore it to the standard ROM, they can't even charge me the service fee.
can someone back up oeminfo.bin file from p20 pro?
hello .sir huawei p20 user problem
crucky said:
Hello my friends,
today i will show you how to rebrand your device credits @Pretoriano80 @LastStandingDroid @mankindtw @Atarii and all the others from P20 Lineup Telegram :good::good::good:
DONT TRY TO REBRAND L29 to L09 or vice versa will brick or have problems !
1.Unlock Your Bootloader via Huawei Site
2.Root your P20 with Patched Ramdisk https://forum.xda-developers.com/huawei-p20/how-to/magisk-root-t3777612
3.Get the Stock Firmware Files you want to use from Firmwarefinder or other Source and rename the files
update_data_full_public.zip -> update_data_public.zip
update.zip -> update.zip
update_full_EML-L29_hw_eu.zip -> update_all_hw.zip
4.Copy them via MTP to your internal memory
5.Boot into fastboot mode and flash no check recovery from @Atarii / @mankindtw find it here (https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085)
fastboot flash recovery_ramdisk recovery_ramdisk_BKL-L04_nocheck.img
6.Install Magisk Manager
7.Download oeminfo binary file https://mega.nz/#!X0AjASKS!KvXMfbtd8S3kPNZZO1Lm6bKHDyXGqXlBi0SDZdzJwfo copy to internal memory
8.Boot into Android System enable adb debbuging in developer settings.
9.copy oeminfo to internal memory
10.adb shell
11.su
12.accept the prompt at your P20
13.mkdir /data/local/tmp
14.mv /sdcard/oeminfo /data/local/tmp
15.cd /data/local/tmp
16.chmod +x oeminfo
17. ./oeminfo EML-L29 C432 hw/eu
18. mkdir /data/update/HWOTA
cd /sdcard/
19.mv *.zip /data/update/HWOTA
20.Paste recovery command:
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_all_hw.zip" >> /cache/recovery/command
exit
21.adb reboot recovery
22.Phone will reboot and starts to install and Rebrand your Phone
Please always use the same Region C432 for Brand and Firmware Files
Click to expand...
Click to collapse
hello i bought huawei p20 from china. now im using phone in turkey i want to make my phone global i m having some problem with some app. is chiness and hi voice is chinese if i load L29 to my phone may i use like global eu versions.im not good about this subject.please help me my phone is eml-al00
ENSSML said:
hello i bought huawei p20 from china. now im using phone in turkey i want to make my phone global i m having some problem with some app. is chiness and hi voice is chinese if i load L29 to my phone may i use like global eu versions.im not good about this subject.please help me my phone is eml-al00
Click to expand...
Click to collapse
Hello
If you want an European rom the firmware to download is C432, for global Asian (with playstore) it's C636 (both with the L29)
I have a redmi note 5 pro with a gyroscope accelerometer sensors problem , looking in the forums, I saw that many advised to flash the file persist.img to the partition /dev/block/mmcblk0p27 to solve the problem, once it was done, the phone went into bootloop :crying:, when i made more research , I realized that for the redmi note 5 pro, the partition persist is not in the same partition, and it was here /dev/block/mmcblk0p53 and /dev/block/mmcblk0p54 for the persistbak.
Now seeing that the persist.img file is 4.58 MB, so it corrupted all partitions /dev/block/mmcblk0p27, /dev/block/mmcblk0p28, /dev/block/mmcblk0p29, /dev/block/mmcblk0p30, and /dev/block/mmcblk0p31
So I need your help to recover these partitions namely: dip, ddr, toolsfv, devcfgbak, devcfg
This is possible via the twrp terminal with the commands:
dd if=/dev/block/mmcblk0p27 of=/sdcard/dip.img
dd if=/dev/block/mmcblk0p28 of=/sdcard/ddr.img
dd if=/dev/block/mmcblk0p29 of=/sdcard/toolsfv.img
dd iif=/dev/block/mmcblk0p30 of=/sdcard/devcfgbak.img
dd if=/dev/block/mmcblk0p31 of=/sdcard/devcfg.img
thanks for your help :highfive:
I pm'd you
I have the same problem, have u find any solution?
I got same problem, i was pushed persist.img using twrp, and now my redmi note 5 stuck on bootloop. Even though i flashed it successfully using mi flash or twrp. Now i have no idea what to do
look at this thread
https://forum.xda-developers.com/re.../tutorial-fix-sensors-wifi-bluetooth-t3823622
Persist problem whyred
manethon said:
I have a redmi note 5 pro with a gyroscope accelerometer sensors problem , looking in the forums, I saw that many advised to flash the file persist.img to the partition /dev/block/mmcblk0p27 to solve the problem, once it was done, the phone went into bootloop :crying:, when i made more research , I realized that for the redmi note 5 pro, the partition persist is not in the same partition, and it was here /dev/block/mmcblk0p53 and /dev/block/mmcblk0p54 for the persistbak.
Now seeing that the persist.img file is 4.58 MB, so it corrupted all partitions /dev/block/mmcblk0p27, /dev/block/mmcblk0p28, /dev/block/mmcblk0p29, /dev/block/mmcblk0p30, and /dev/block/mmcblk0p31
So I need your help to recover these partitions namely: dip, ddr, toolsfv, devcfgbak, devcfg
This is possible via the twrp terminal with the commands:
dd if=/dev/block/mmcblk0p27 of=/sdcard/dip.img
dd if=/dev/block/mmcblk0p28 of=/sdcard/ddr.img
dd if=/dev/block/mmcblk0p29 of=/sdcard/toolsfv.img
dd iif=/dev/block/mmcblk0p30 of=/sdcard/devcfgbak.img
dd if=/dev/block/mmcblk0p31 of=/sdcard/devcfg.img
thanks for your help :highfive:
Click to expand...
Click to collapse
Hi, I had the same problem but i had copied the persist.img file to /dev/block/mmcblk0p53. Even my phone's stuck in boot loop or sometimes boots to recovery after an unsuccessful boot. On flashing a rom like havoc 2.2, i waited for its boot animation to get over for 1 hour, but still didnt boot. Please help
hello,
I have phone which do not support any kind of recovery like twrp or cwm.
Xiaomi Redmi Note 8 2021 arm64 a/b with project treble support.
i have succesfully installed and booted GSI on my Xiaomi Redmi Note 8 2021. With help of the DSU Sideloader.
I have installed GSI without gapps (google apps) so i can manualy pick gapps minimalisic set.
I have tried flash gapps directly from the phone with Ex Kernel Manager but it is giving me message "No space left on device"
My big question is if you can resize GSI system partition without TWRP? since Note 2021 does not support recovery, if yes how?
Or can you actually set bigger system partition than system image with this command ? --el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
(following manual steps for gsi installation)
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
what would be number for 20GB size in this command? --el KEY_USERDATA_SIZE 8589934592 how i can write it correctly?
i have enough space to assign big userdata partition.