Related
I just wanted to point out that I have been able to boot some treble GSI on my device from different roms like AOSP, RR, ArrowOS in the treble section of XDA and some of them boot fine, but I have found some issues:
PHH PIE GSI doesn't like magisk it breaks wifi and mobile data once magisk is flashed
PHH Oreo AOSP GSI I do not remember any issues besides being too stock for my liking
RR GSI It has so many options almost comparable to what a Venom Rom would be for HTC devices
TWRP it is not able to read encryption on any of this GSIs
AOSP Oreo I don't remember if the other variants GSIs does not read exFAT formatted MicroSD (works on PIE GSI)
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
I would like more users to share their experience here with GSIs
the steps I took to flash this
1. make sure you download an arm64 AB GSI image from your favorite ROM
2. go to TWRP wipe section wipe system, Dalvik cache data & internal
3. go to TWRP wipe section format data, type yes
5. restore stock Vendor.img and stock Boot.img
6. flash GSI
7. reboot & enjoy
first boot might take awhile it encrypts the device, thi is the part that makes TWRP not being able to decrypt data since TWRP decrypts Qualcomm Encryption on our device but no stock android encryption this part it is possible to fix by TWRP team and it will probably come in later
Thanks for sharing. I was planning on trying out a GSI this weekend and see how it goes. Glad it works!
I forgot to save the stock vendor and stock boot file I need these two files Can you help
emrince said:
I forgot to save the stock vendor and stock boot file I need these two files Can you help
Click to expand...
Click to collapse
https://forum.xda-developers.com/u12-plus/how-to/collection-htcu-u12-ruu-firmware-t3794664/page24
Read the OP there
I tried to boot the RR img, no dice.
Backed up modified rom on slot b
Switched to slot a in TWRP, supposedly empty
Wiped system, data, cache, dalvik
Flashed prior stock vendor img and boot img
Flashed RR ab arm64 su gapps Img
Rebooted slot a
Bootloop
Interestingly, after looking 3 times, my phone booted back to slot b by itself back to stock, back up restored just fine
I realize I didn't wipe factory reset with yes
Finally got RR to to boot! It's a very finicky process. I think my problem was I kept trying to "dual" boot, Viper in one slot and the GSI in the other. Turns out it just has to be in the active slot, regardless of which slot you switch to in TWRP. Maybe that's obvious for some. This a/b partition business sure has a learning curve.
Anyway, things I noticed on RR: Lots of customization as usual for RR, very fast and smooth, screen brightness is on max all the time regardless of slider or auto brightness, and I couldn't make phone calls but texting worked. Everything else seemed to work fairly well. I love the fling navbar....on to the next one.
I'm not sure if anyone else is trying the GSI's, this doesn't seem to be a very active thread. So far I have only been able to boot RR 8.1 GSI. I have tried multiple other images without any success. I think the reason I didn't get data and calls didn't work on RR is that I am on Verizon and the HTC u12 does not have CDMA radios. Volte calling was not available on the rom. Oh well. I'm excited for the upcoming developments in the Viper forum. If anyone knows a fix for data on verizon with the GSI's, I'm all ears. Thanks
Anybody successful in making one of this ROMs a daily driver?
Sent from my HTC U12+ using XDA Labs
Resurrection Remix 8.1 is pretty stable if you are on a gsm network. I popped in a Tmobile sim card and it was pretty solid. There are some minor annoyances like the inability to adjust the brightness (always on full), though decreasing screen pixels makes it more dim, vendor mismatch message on boot, and no volte or wifi calling. There may be some other small things like with the camera and bluetooth but I didn't keep it for long as I am on Verizon and don't get data. I could see using it as a DD though. There are probably ways to fix the annoyances I mentioned.
Have any of you tested this version of RR on U12+?
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
For example, face recognition, 4k camera mode, slow motion recording, 3D sound, AudioFocus, bokeh mode etc.?
regards
q
@JEANRIVERA Is i't there any working Android P GSI rom?
Just can't wait anymore HTC for P update =)
nomaj said:
@JEANRIVERA Is i't there any working Android P GSI rom?
Just can't wait anymore HTC for P update =)
Click to expand...
Click to collapse
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
So.. i will missing root? and fixes for google sotre etc ?
JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
I have problem with install ArrowsOS, i have still bootlops.. It's probably related to a / b boot, how to fix this? Twrp say "No OS installed", i set wipe system,data,cache next i flash vendor, boot and system file, i made a mistake?
JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
@JEANRIVERA
Is't this update helpping us?
2019.3.28 Magisk v19.0
https://forum.xda-developers.com/showpost.php?p=79216305&postcount=50https://forum.xda-developers.com/showpost.php?p=79216305&postcount=50
mientus25 said:
I have problem with install ArrowsOS, i have still bootlops.. It's probably related to a / b boot, how to fix this? Twrp say "No OS installed", i set wipe system,data,cache next i flash vendor, boot and system file, i made a mistake?
Click to expand...
Click to collapse
Hey, I'm having the same problem. Did you work out a solution to get any GSI to boot on your U12?
SilentAchiever said:
Hey, I'm having the same problem. Did you work out a solution to get any GSI to boot on your U12?
Click to expand...
Click to collapse
I tried to find a solution for 12 hours and nothing came of it
I's dual sim working on GSI roms?
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
mientus25 said:
I tried to find a solution for 12 hours and nothing came of it
Click to expand...
Click to collapse
1. make sure you download an arm64 AB GSI image from your favorite ROM
2. go to TWRP wipe section wipe system, Dalvik cache data & internal
3. go to TWRP wipe section format data, type yes
5. restore stock Vendor.img and stock Boot.img
6. flash GSI
Did you flashed GSI rom from point 6?
Yes, i follow this instruction and twrp say "OS no installed".
mientus25 said:
Yes, i follow this instruction and twrp say "OS no installed".
Click to expand...
Click to collapse
Check this... wiping
"for GSI it is better to wipe from stock recovery "
Hello fellow XDA members and flashaholic people! This is a guide about flashing sGSI or GSI (semi-GSI) Android Pie images on VINCE.
This guide is for VINCE only! Please don't try it on WHYRED it may work or it may not.
First you need to treble enabled custom recovery. I suggest OrangeFox V8.1 https://forum.xda-developers.com/redmi-note-5/development/official-orangefox-recovery-project-t3807479
You can either flash it via TWRP or extract zip and flash recovery img by fastboot method.
Second you need treble enabled custom Oreo ROM, I suggest Cardinal-AOSP as it's vendor.img works flawlessly. https://forum.xda-developers.com/redmi-note-5/development/rom-cardinalaosp-t3774232
And third step includes the GSI image. You can find several GSI's here; https://forum.xda-developers.com/project-treble/trebleenabled-device-development
After downloading .zip file from any ROM you wanted extract it to get its system image and move it into the either internal storage or SD card. [SYSTEM IMAGE ONLY NEEDED]
I tried Pixel Experience 9.20 and Havoc OS 9.18 builds both booted without issues.
Please note that you need GApps package for ROM's (Except PixelExperience) you can find them here; https://opengapps.org/ Suggested package is Nano one. But if you want more you can go for bigger packages. I always use Mini version of it.
Steps to get Pie working on our device:
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
PLEASE KEEP IN MIND I DO NOT DEVELOPING ABOVE GSI IMAGES OR HELPING TO DEVELOP. IF YOU HAVE ANY BUGS TO REPORT PLEASE REPORT IN PROPER FORUM POST. I CAN HELP ABOUT INSTALLATION ONLY.
Ah, and there is few screenshots i'll share (Pixel Experience 9.0):
Don't need to flash p lag fix, volte fix and other stuff?
Ritik17 said:
Don't need to flash p lag fix, volte fix and other stuff?
Click to expand...
Click to collapse
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)
bdogan1912 said:
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)
Click to expand...
Click to collapse
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?
moralesnery said:
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?
Click to expand...
Click to collapse
In few hours of usage i did not encountered very-serious level bugs. Battery was fine and didn't seemed like to draining. Bluetooth and WiFi had no issues for me either. Only VoLTE doesnt works and as may you know thats global issue on it. Did not faced any mem-leaks or running out of memory problems, with freshest install it used up to 1.3 GB mem and with some apps like social ones it went up to 1.6 to 1.9 GB but ROM was overall butter smooth without single lag or freeze. No FCs either, GPS works i guess it was enabled by default on fresh install as usual but since im not using the GPS that much i did not tested it fully though.
As you can guess those are still experimental/beta builds could have issues that i did not encounter. But overall was very fine for me. I'd keep it but it kinda messed "about phone" settings as it goes manufacturer and model both goes by unknown or phh-treble. It's very natural since i installed as GSI image but still bothered me.
Almost forgot; In Havoc OS settings goes direct crash if you touch battery in settings. PE works fine but it has problems with Dark theme beign not applied correctly. Also i did not used or tried substratum or its themes.
Thank you for your instructions. I wanted to install a GSI 9.0 ROM since Pie came out, but other threads with instructions were too complex or convoluted that I thought it was harder.
I would like to make some clarifications on your steps:
* I used the unofficial PixelExperience 9.0 GSI image, as you said. It feels and behaves almost exactly as the official PixelExperience build for our device, but with nicer interface. The image is HERE. Just as a sidenote, the System image comes with DPI = 360, things look a bit too big. To make it look like MIUI or the official PixelExperience build for vince, a dpi of 390 should be set (this can be done from settings > System > Developer Settings > Minimal Width, under the "draw" section).
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
* At this step, I had to make "Format Data", and only then reboot to recovery again, and make the wipes to all other partitions. Without rebooting the wipes weren't possible (it was showing errors while trying to mount partitions). VENDOR PARTITION SHOULD NOT BE WIPED
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
At this point, you must check that the hardware works correctly. Touch, screen, audio, BT, wifi, RIL, LTE or whatever you use. If something doesn't work at this point, it won't work after installing the GSI image.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
* In OrangeFox, at this point before flashing the GSI's .img file, the recovery asks for the type of image. For noobs and careful people, "System Image" must be selected before proceeding.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
* When installing Magisk through recovery, the framework will be installed, but the APK won't appear in the app list. It must be downloaded separately from https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.0/MagiskManager-v6.0.0.apk
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Cast and mirror screen are broken. After choosing a screen to share the phone's screen to, SystemUI will crash. Apps with cast capabilites won't detect Chromecast devices (the cast button won't appear).
Thank you for your help
moralesnery said:
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Thank you for your help
Click to expand...
Click to collapse
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?
Can't Show the Image File
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.
GizPrime said:
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.
Click to expand...
Click to collapse
This is the correct link, you don't downloaded gsi file (I did the same thing, currently running Havoc 9 ):
https://sourceforge.net/projects/havoc-os/files/arm64aonly/
sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie
Biggest thanks to you as i was in dilemma to try the PE 9.0.
However, the stock camera is so dark so i installed Camera2API, resulting the camera app FC, installed the crashfix Gcam apk i found somewhere in this thread not so long ago to no avail, the camera is still broken. Anyone having the issue ?
TIPS: I tried both Dark Ages and Genom Kernel, the brightness is crazy, i think its the late display driver provided within it: the brightness level is scaled incorrectly, with the 50% on MIUI is 0% in PE, and 50% in PE is equal to 100% of MIUI (the max brightness is at 50% and sliding all over to the right does nothing); clean flashed the whole thing and not using custom-installed kernel at all.
HungNgocPhat said:
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?
Click to expand...
Click to collapse
MagiskHide Props Config" its a module that replaces the ROM's fingerprint with a certified one. This way you get ctsProfile: true and basicIntegrity: true, thus passing SafetyNet. This combined with MagiskHide allows me to use some apps that rely on SafetyNet.
After flashing the Treble-enabling ROM (Cardinal OS) you can install GSI system images based on Oreo or Pie.
Is hotspot working in PIE GSI?
dahrel22 said:
sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie
Click to expand...
Click to collapse
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!
Wyneg said:
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!
Click to expand...
Click to collapse
seems like i need to do a format data in recovery. but right now i cant afford to loose all my files in internal storage. once i back up all my file then i will do the format data.
i wish there is some way to decrypt my storage without formatting
btw, i got my storage encrypted because i flashed miui stable rom
it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem
And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?
moralesnery said:
And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?
Click to expand...
Click to collapse
If you do same wipes what you did to flash GSI it's totally ok
expextors said:
it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem
Click to expand...
Click to collapse
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.
soyti2x said:
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.
Click to expand...
Click to collapse
i tried on havoc it doesn't work what your gsi you used ? i can't open hotspot because always off when turn on
Hi. I have a MTK6739 which came with the "GO" version of Android (1GB ram). It came with Oreo, and it is GSI compatible (Arm with A only).
I recently wanted to give some GSI images a try and tried to flash AOSP. I tried to flash the system image using fastboot and also SP Flash Tool (of MTK). Both gave me the same error:
FAILED (remote: sparse image size span overflow.)
After getting this error, i reset my phone and my default system is still there, so nothing is being written to the system partition. I thought maybe treble AOSP images are larger than my phone's system partition but when i checked, the default system img of my phone is actually larger than the GSI images (I have also tried a "go" version of a gsi image with the same outcome).
What is my problem here please?
PS: My bootloader is unlocked.
What version of Android did your phone come with? If it's 8.X, then you have what is called Treble Legacy, which from what I am experiencing is sorta buggy. Do you have TWRP installed? It will help to have it, for a number of reasons. When a flash fails on mine, it typically wont boot the OS but rather just boot into TWRP, which makes it easy to simply kick it back in fastboot or do a wipe of a partition.
My BV5500 is GSI Enabled (Legacy) and even though it supports Treble, images won't load with TWRP even though it has Treble support. What images that do run have to be flashed with fastboot. I did use MTK tools to flash a few partitions again, but for the most part I use TWRP/Fastboot.
Mine also has the same behavoir as yours, you flash a ROM and /system is empty! (Or unchanged) So def a bug somewhere.
Chaos Storm said:
What version of Android did your phone come with? If it's 8.X, then you have what is called Treble Legacy, which from what I am experiencing is sorta buggy. Do you have TWRP installed? It will help to have it, for a number of reasons. When a flash fails on mine, it typically wont boot the OS but rather just boot into TWRP, which makes it easy to simply kick it back in fastboot or do a wipe of a partition.
My BV5500 is GSI Enabled (Legacy) and even though it supports Treble, images won't load with TWRP even though it has Treble support. What images that do run have to be flashed with fastboot. I did use MTK tools to flash a few partitions again, but for the most part I use TWRP/Fastboot.
Mine also has the same behavoir as yours, you flash a ROM and /system is empty! (Or unchanged) So def a bug somewhere.
Click to expand...
Click to collapse
Mine came with Android 8.1. Unfortunately my device doesn't have TWRP. In my situation, the flash fails but the phone still boots to its original OS. So nothing is overwritten. What i didn't do however is that i didn't "wipe" the partition before flashing the gsi image. And why should i anyway? The default flashing software of MTK (SP Flash Tool) doesn't even have a wipe option. It just overwrites to the partition. I never had to wipe the old rom to flash the stock rom before, it happened automatically.
Did you have any success with any of the gsi images that you have tried?
twilightened said:
Mine came with Android 8.1. Unfortunately my device doesn't have TWRP. In my situation, the flash fails but the phone still boots to its original OS. So nothing is overwritten. What i didn't do however is that i didn't "wipe" the partition before flashing the gsi image. And why should i anyway? The default flashing software of MTK (SP Flash Tool) doesn't even have a wipe option. It just overwrites to the partition. I never had to wipe the old rom to flash the stock rom before, it happened automatically.
Did you have any success with any of the gsi images that you have tried?
Click to expand...
Click to collapse
Yes, XenonHD and AOSP GSI 8.1 Oreo "Go" work. Also, Lineage and RessurectionRemix work but are very slow. This is in part to Gapps.
In the end, I used AOSP GSI 8.1 Oreo "Go", which was designed for 1GB RAM devices, and since it's been tweaked to run on slow hardware, it runs plenty fast.
On my BV5500 I would often have trouble getting a flash to function. Sometimes I would have to use SP Flash to restore stock boot and stock recovery, and then it would boot, complain of corruption, ask me to wipe, then kick me back into fastboot, where I would flash the rom and twrp.
Sometimes when I tried to flash a ROM that had worked previously it would say it finished but the partition would be empty.
As regards to wiping, perhaps its a bug but I found that my chances of flashing were better if the system partition was wiped prior to flashing.
Oh, one more thing: when I flash these ROMS, they all are sparse images and send data in small chunks. At least when done via fastboot. Perhaps try a different ROM or re-download the ROM, it's possible it's corrupt. Worth a shot.
Chaos Storm said:
Yes, XenonHD and AOSP GSI 8.1 Oreo "Go" work. Also, Lineage and RessurectionRemix work but are very slow. This is in part to Gapps.
In the end, I used AOSP GSI 8.1 Oreo "Go", which was designed for 1GB RAM devices, and since it's been tweaked to run on slow hardware, it runs plenty fast.
On my BV5500 I would often have trouble getting a flash to function. Sometimes I would have to use SP Flash to restore stock boot and stock recovery, and then it would boot, complain of corruption, ask me to wipe, then kick me back into fastboot, where I would flash the rom and twrp.
Sometimes when I tried to flash a ROM that had worked previously it would say it finished but the partition would be empty.
As regards to wiping, perhaps its a bug but I found that my chances of flashing were better if the system partition was wiped prior to flashing.
Oh, one more thing: when I flash these ROMS, they all are sparse images and send data in small chunks. At least when done via fastboot. Perhaps try a different ROM or re-download the ROM, it's possible it's corrupt. Worth a shot.
Click to expand...
Click to collapse
Thanks for the reply. I will try wiping first and flashing after that. Let's see if it is gonna work.
PS: By the way, these images come as img.xz format. I first unpack them and get the img. Am i doing it wrong? Should i just flash the img.xz images?
twilightened said:
Thanks for the reply. I will try wiping first and flashing after that. Let's see if it is gonna work.
PS: By the way, these images come as img.xz format. I first unpack them and get the img. Am i doing it wrong? Should i just flash the img.xz images?
Click to expand...
Click to collapse
No, you are doing it correctly. I think they compress them to save bandwidth.
just need to resize that partition
twilightened said:
Hi. I have a MTK6739 which came with the "GO" version of Android (1GB ram). It came with Oreo, and it is GSI compatible (Arm with A only).
Click to expand...
Click to collapse
Which device? Please tell.
I have also Blackview A20 (go).
Flash stock with spflash. Only for stock
Let it reboot. reset. Allow it to reboot once again. Check everything GPS/wifi/bt. Enable ON
Do not connect to Google accounts. not needed.
Enable adb
Charge at least 90% - some devices will NOT flash and silently ignore.
fastboot erase system
fastboot flash system gsi.img
fastboot reboot
If it asks you a password, just type anything. Then it will ask you reset phone. Say OK.
all done
Note always check the sha1sum or md5sum of GSI. Despite having
kusti420 said:
just need to resize that partition
Click to expand...
Click to collapse
Excuse me, I'm new to this, would you have a tutorial? I have several phones that would help
kusti420 said:
just need to resize that partition
Click to expand...
Click to collapse
how can i resize the partition pls?
Dear Comunity,
I decided to make the step to alternative roms due to MIUI has an unacceptable privacy policies and bloatware, i decided to flash the last OFFICIAL version of LINEAGE OS microG.
Almost everything works fine with one exception the 4G-LTE-3G apparently does not work and i'm unable to use internet whithout wifi.
The easy way for me could be re-flash stock rom, but before that i would like to fix it by flashing a stock vendor.img via fastboot, the last stock rom comes with a zip for propietary flashing tool of xiaomi, inside the zip we can find the following files among others:
vendor.new.dat.br
vendor.patch.dat
vendor.transfer.list
There is anyway to flash this via custom recovery? can we make a vendor.img out of this?
Your help is allways apreciate, i hope after fixing this more users can solve the same issue on their phones.
Merry Christmas to all of you.
Working on this https://github.com/danielmmmm/dat2img
Hi guys,
I know custom ROMs are made of AOSP. However, it's not very clear to me why do they also have lower quality signal compared to stock ROMs. In the same area where I usually got 4G (not great signal, but still 4G), now I only get 3G.
Is there a reason for this? Aside from "it's not made by the manufacturer". Yeah, I know that, but why exactly isn't the same quality...? What makes it slightly worse?
Also, is there anything can do to improve reception?
arsradu said:
Hi guys,
I know custom ROMs are made of AOSP. However, it's not very clear to me why do they also have lower quality signal compared to stock ROMs. In the same area where I usually got 4G (not great signal, but still 4G), now I only get 3G.
Is there a reason for this? Aside from "it's not made by the manufacturer". Yeah, I know that, but why exactly isn't the same quality...? What makes it slightly worse?
Also, is there anything can do to improve reception?
Click to expand...
Click to collapse
Exactly what you said: "It's not made by the manufacturer". Proprietary blobs are extracted from the device, creating vendor image while building AOSP and modifying vendor partition it when installing a zip.
I don't think there's anything to improve, until someone makes a kernel or a vendor image.
(flashing original vendor lead to bootloop on my phone, probably because encryption?)
However, you can try downloading stock ROM and flash stock vendor, but make sure to not have your device encrypted (I did not try on a non-encrypted device).
georg3_ said:
Exactly what you said: "It's not made by the manufacturer". Proprietary blobs are extracted from the device, creating vendor image while building AOSP and modifying vendor partition it when installing a zip.
I don't think there's anything to improve, until someone makes a kernel or a vendor image.
(flashing original vendor lead to bootloop on my phone, probably because encryption?)
However, you can try downloading stock ROM and flash stock vendor, but make sure to not have your device encrypted (I did not try on a non-encrypted device).
Click to expand...
Click to collapse
I've noticed this with stock ROMs as well, when they weren't dedicated for that specific region... So...I'm guessing it's probably the same here. AOSP includes some files to make the ROM work...but not dedicated files for each region.
By the way, can you please, guide me how should I do this? It's been a really long time since I've done stuff like this. Android has changed a lot.
I already have the ROM at hand, downloaded via RSA. But it's Android 11, since that's the last ROM that Motorola released for this phone.
So that part is done. What next? )
Also, any idea if this method should also bring back VoLTE and VoWIFI? Or it's not that simple?
arsradu said:
I've noticed this with stock ROMs as well, when they weren't dedicated for that specific region... So...I'm guessing it's probably the same here. AOSP includes some files to make the ROM work...but not dedicated files for each region.
By the way, can you please, guide me how should I do this? It's been a really long time since I've done stuff like this. Android has changed a lot.
I already have the ROM at hand, downloaded via RSA. But it's Android 11, since that's the last ROM that Motorola released for this phone.
So that part is done. What next? )
Also, any idea if this method should also bring back VoLTE and VoWIFI? Or it's not that simple?
Click to expand...
Click to collapse
EDIT: Newer OS than vendor shouldn't make a problem.
Newer vendor than OS does.
Extract the ROM, there should be vendor.img in there, and there are 2 methods for this:
1. TWRP method
Install, Install Image, select your vendor image set it to flash as vendor image, and swipe to flash.
2.Fastboot method
Open a terminal/command prompt in the extracted ROM folder, and type
Code:
fastboot flash vendor vendor.img
That should do it.
georg3_ said:
Older OS than vendor shouldn't make a problem.
Older vendor than OS does.
Extract the ROM, there should be vendor.img in there, and there are 2 methods for this:
1. TWRP method
Install, Install Image, select your vendor image set it to flash as vendor image, and swipe to flash.
2.Fastboot method
Open a terminal/command prompt in the extracted ROM folder, and type
Code:
fastboot flash vendor vendor.img
That should do it.
Click to expand...
Click to collapse
Alright. So....I can't use Android 11 vendor, extracted from stock ROM, if I'm currently on PixelExperience based on Android 12, right?
arsradu said:
Alright. So....I can't use Android 11 vendor, extracted from stock ROM, if I'm currently on PixelExperience based on Android 12, right?
Click to expand...
Click to collapse
Stau bine pe engleza daca e )
I translated it wrong, i meant it would be fine to flash it
Buun. Thank you, kind sir. Will try it then and let you know.
georg3_ said:
Stau bine pe engleza daca e )
I translated it wrong, i meant it would be fine to flash it
Click to expand...
Click to collapse
I'm getting bootloop, too...
I tried to flash the rom, flash Disable_Dm-Verity_ForceEncrypt.zip (should disable encryption...unless I'm missing something). But after flashing vendor.img from stock Android 11, I can't boot anymore. I also tried wiping data after that, but no luck.
arsradu said:
I'm getting bootloop, too...
I tried to flash the rom, flash Disable_Dm-Verity_ForceEncrypt.zip (should disable encryption...unless I'm missing something). But after flashing vendor.img from stock Android 11, I can't boot anymore. I also tried wiping data after that, but no luck.
Click to expand...
Click to collapse
Probably not an encryption related issue, guess we can't fix anything.