I've been trying to find a stock-vendor based custom ROM for my phone so that ANX works perfectly fine. I've tried many OSS based ROMs but portrait mode wasn't working on any of those ROMs.
You can use any GSI rom. They are delivered as an image of the system partition that can be flashed directly to the system partition through recovery or through fastbootd.
But this firmware method is usually used in the absence of a firmware version specifically for the device, since no one can guarantee full operability of universal firmware.
Related
Hi
First a little history...
I recently got an OPX with the intention of installing Sailfish OS on it. So first I need to get CM 12.1 installed. Following the instructions here I flashed TWRP using fastboot, but the version of TWRP provided at the link would not find any system partitions on my device and therefore could not be used to flash any images. Newer versions of TWRP would simply not load.
Eventually, using the stock OPX recovery, I managed to upgrade Oxygen OS to the latest version. I then flashed the latest version of TWRP (3.1.1-1) again and it worked! It found my devices partitions and I could flash ROMs with it. But, it wouldn't flash CM 12.1. Something about a trustzone incompatibility...
So I got the idea to try and downgrade Oxygen OS, which I did via TWRP. But then TWRP stopped working... and here is my problem.
I'm now stuck in a situation where:
- I can access fastboot
- The only versions of TWRP which work (e.g. 3.0.2-0) fail to find my system partitions, and therefore can't be used to flash ROMs
- The stock recovery also seems to fail to find the system partitions (clicking on "install locally" does nothing), so I can't use that to flash ROMs either
So I really need to get a working image on my phone somehow... but how?? Is it possible to do this via fastboot only?
Cheers!
Is your bootloader unlocked? TWRP cannot see system partitions if so.
I unlocked it originally... but since then I have installed a new ROM (Oxygen OS 2.x). Would this overwrite the bootloader? Do I need to unlock again? I think I must be using the old OOS bootloader now...
I think you can see if it's unlocked if you boot into bootloader, connect to pc and write on cmd "fastboot devices".
Whenever you switch between android 5.0 roms and 6.0 and further you have to first use the correct recovery from oneplus, only then you can flash the correct twrp and the adequate roms
My bootloader is unlocked. I cannot flash a new ROM via recovery, because none of the recovery images (stock, TWRP) can see my system partitions (I don't know why). At this stage I would just like to know if there is a way to flash a stock ROM/recovery/bootloader via some other method (fastboot, or a special tool), so I can restore my phone back to factory state. I don't care about losing data. Thanks.
EDIT: Just to clarify, I believe this is my current situation (please correct me if something doesn't make sense):
- OOS has two different bootloaders, 2.x and 3.x.
- The phone originally had OOS 2.x on it. None of the TWRP images I installed recognized my system partitions, so I couldn't flash with TWRP.
- After re-installing the stock recovery (which happened automatically when I booted to the stock ROM), I was able to upgrade to OOS 3.x via stock recovery. Now recent TWRP versions were working (I assume because upgrading to OOS 3.x updated the bootloader too), and were recognizing my system partitions.
- Using a new version of TWRP (3.1.1-1), I re-flashed an older version of OOS 2.x again. I think this was my mistake, because I think this downgraded the bootloader to 2.x again. Now none of the TWRP versions recognize my system partitions, so I cannot flash ROMs.
- I have re-flashed the stock recovery from the OnePlus website, but not even this allows me to flash ROMs. The symptoms look like in TWRP, i.e. that it fails to recognize my system partitions. So I am stuck with no way to flash ROMs, or upgrade the bootloader.
Hey guys, I'm a bit new to the world of custom ROMs, so apologies if I come across as an idiot.
First of all let me start of with saying that I know a bit about installing custom ROMs because I've been experimenting installing custom ROMs on my old Moto G (2013). So far I've successfully installed RR, LOS and AOSP extended as well has rooting it with SuperSu (just so I could change fonts on LOS), without any problems. So I know the basic 3-steps like, 1. Unlock bootloader, 2. install twrp, 3. backup, wipe(system, data, cache, dalvik ) and finally install. I assumed installing custom ROMs on every device would be the same.
But then, I've been viewing these forums a lot just to get more info and learn more about stuff. I've come across threads like this one (https://forum.xda-developers.com/redmi-note-4/help/unable-to-install-resurrection-remix5-8-t3673989), where people are unable to install roms and are suggested to install the developer rom using MiFlash tool, which I don't know anything about. And this isn't the first time I'm seeing such threads. I've seen t least 2 other threads like this but I can't link them because I can't find them.
So my question is:
Will the method I use to install custom ROMs on my Moto G work the same way on my RN4? or do I really to to follow other steps to install these ROMs?
Yes, that method will work.
Flashing with MiFlash is needed when you mess things up and you want to restore the phone to the original state. MiFlash is basically an automated method to flash via fastboot, a GUI for fastboot.
In some phones, there are some particular partitions that contains "drivers" to make the device works. These "drivers" (it's truly called firmware) needs to be updated to make the phone works with latest Android versions. The latest firmware is found on latest official developer ROMs and unofficial Xiaomi.eu ROMs.
Many custom ROMs like LOS an RR needs the latest firmware installed to work properly, but they don't include it in their .zip files, so that's why I suggest to flash the latest developer ROM before installing a custom ROM. This way all the partitions will be updated before, and the custom ROMs will find the latest firmware and will work fine.
You can also find the firmware as a flashable .zip (to flash before the custom ROMs .zip) in this thread:
https://forum.xda-developers.com/re.../firmware-firmware-update-2017-08-04-t3651537
(you can find the newest version in the last posts of the thread).
Hello!
Just received my Umidigi A3 - MT6739.
Firmware is Android 9, latest release: N Android 9.0 V1.3_20190610 ROM
I would like to flash a custom recovery (TWRP) and flash a custom ROM - like Lineage OS or Stock Android.
This is not the first time I root and flash an android device, however I am having difficulties finding the right files.
I tried to install custom TWRP recovery both through ADB tool and with SP flash tool.
I initially unlocked the OEM and bootloader using ADB tools, then I tried to flash a TWRP recovery image I found online but it turned out to be for Android 8.1 and not Android 9.
The phone switches on and boots normally - however I still don't have a custom recovery nor the possibility to install a custom ROM.
Here's a list of threads I already looked at and tested:
community.umidigi.com/forum.php?mod=viewthread&tid=2962&highlight=twrp
getdroidtips.com/twrp-recovery-umidigi-a3/
unofficialtwrp.com/twrp-recovery-root-umidigi-a3/#Download_Files
romprovider.com/2019/01/umidigi-a3-twrp-root/#How_to_Install_twrp_Recovery_on_UMIDIGI_A3
Did anyone who has the same phone manage to do such?
Thanks!
A3 TWRP Recovery
Hi,
It sounds like you have tried all the available options and since I have Android 8.1 mine is not the same. I can tell you that just in case you haven't seen this page yet, it may help, as it worked perfectly for me.
community.umidigi.com/forum.php?mod=viewthread&tid=17376&extra=page%3D1
David
ccampolo said:
Hello!
Just received my Umidigi A3 - MT6739.
Firmware is Android 9, latest release: N Android 9.0 V1.3_20190610 ROM
I would like to flash a custom recovery (TWRP) and flash a custom ROM - like Lineage OS or Stock Android.
This is not the first time I root and flash an android device, however I am having difficulties finding the right files.
I tried to install custom TWRP recovery both through ADB tool and with SP flash tool.
I initially unlocked the OEM and bootloader using ADB tools, then I tried to flash a TWRP recovery image I found online but it turned out to be for Android 8.1 and not Android 9.
The phone switches on and boots normally - however I still don't have a custom recovery nor the possibility to install a custom ROM.
Here's a list of threads I already looked at and tested:
community.umidigi.com/forum.php?mod=viewthread&tid=2962&highlight=twrp
getdroidtips.com/twrp-recovery-umidigi-a3/
unofficialtwrp.com/twrp-recovery-root-umidigi-a3/#Download_Files
romprovider.com/2019/01/umidigi-a3-twrp-root/#How_to_Install_twrp_Recovery_on_UMIDIGI_A3
Did anyone who has the same phone manage to do such?
Thanks!
Click to expand...
Click to collapse
I found some TWRP for that mobile, and inserting a GSI ROM is easy, I have everything in my telegram group t.me/umidigi_es
All GSi I have tested are running into bootloop. Does anyone has get GSI or any Android9 or 10 custom rom running on A3 ?
Hater Snapdragon said:
I found some TWRP for that mobile, and inserting a GSI ROM is easy, I have everything in my telegram group t.me/umidigi_es
Click to expand...
Click to collapse
But your telegram group is silent
Hey guys, I'm trying to install LineageOS GSI (arm64 A/B) on my Mi A3 and seem to be having some trouble getting the GSI to actually boot successfully.
I have already done my research both on XDA and elsewhere online, yet most threads focused on the device seem to be of little to no use and/or filled with spam replies that only serve to confuse people looking into this.
A quick note regarding the aforementioned threads:
I don't mean to sound disrespectful to the community, but honestly, bashing somebody over why they'd rather install anything but your own fav piece of software is completely ridiculous.
Without further ado, my case goes as follows:
I'm starting fresh with the latest stock firmware, after having unlocked my bootloader ofc (critical too), I've successfully installed TWRP, wiped, installed the system image and yet after rebooting I'm just greeted with good ol' Fastboot, at which point I either directly flash the stock firmware and try again or wipe my data and whatnot (through TWRP, if reinstalled) and still end up with Fastboot.
Therefore, I have to ask you guys:
Has anyone previously successfully installed any GSI rom on the Mi A3?
Did you flash the system img while on stock firmware or a previously flashed custom rom (ie Pixel Experience)?
Is there any need for any special patch similar to the ones used for MIUI based Xiaomi phones?
Did you face any other issues while trying to flash a GSI?
My intention is to eventually install microG using Nanodroid.
Thanks for asking. I was trying to flash Havoc, crDroid and MSM-Xtended Android 10 GSIs but I can't boot the phone.
I have flashed lots of GSIs in the past, but this is really intriguing me, I can't boot on Mi A3. Wiping or formatting data does not solve, neither Permissiver or Disable Dm-verity zips did the job... :crying:
I successfully bootet the LineageOS GSI yesterday. I was not coming from stock though. I think this process should work assuming you already bootet to TWRP:
1. flash the GSI image to system partition using TWRP
2. flash the TWRP installer to keep your recovery
3. (not sure if needed) flash no fde patch
4. optional: flash some other stuff like Magisk and gapps
5. wipe data and dalvik
I think it rebooted to recovery on my first try but worked after flashing everything again. I probably made some mistake on my first attempt but just make sure to try again before giving up.
Also there's this tutorial but it's not at all what I did to get it working:
https://forum.xda-developers.com/mi-a3/how-to/tutorial-flash-custom-rom-mi-a3-t3977169
ABOUT VERSIONS OF kvt:
2.x is if you're coming from stock Oreo or Pie
3.x seems to be only for stock Pie (otherwise networks don't work) - Oreo modem still has to be flashed though
There is a guide for GSI, but it is outdated, no longer maintained and all links are dead. That's why I'm creating this up to date guide.
If you do not know, what is Project Treble and GSIs, google it first. Proceed only if you know what are you doing. This guide is only for those, who know what is bootloader, fastboot, recovery and TWRP. If you don't, learn that first. There are many guides (for example guides for rooting and Magisk) UNLOCKED BOTLOADER REQUIRED
Guide
1) Download needed files:
- treble recovery: https://mega.nz/#F!b8RgGQCa!48TRsDcJFpaAGNOcc9Fb-A?GxR2TCAA
(this is my mirror, as original links are dead, don't know who is the original developer)
- kvt (find lastest version here) https://androidfilehost.com/?w=files&flid=303096&sort_by=date&sort_dir=DESC (developer deivesj)
(this allows GSI to work on Moto Z2 Play with some of it's stock features like fingerprint gestures, device gestures, pass safety-net and more)
- if you want to use Android 9.0 Pie based ROMs and older, you might want to use V7 kvt instead:
https://mega.nz/#!7w5V1KpQ!uoCMqynn5D83trvZ6uXY30S8b9rLiBlXf1JTeMYQ0rc
- if you are coming from stock Android 9.0 Pie ROM, you will need modem from Android 8.0 Oreo
https://mega.nz/file/mxhxXCaI#nJpdQ3nPnc6urkYP8vLrVb_vc_7EsnXK7MXw3U1xohw
- you may need stock recovery https://mega.nz/#!XphFEIxK!yNdHJSakfO90K1ua92SODoqd85nvwRi7h65EA8RkOuI
-GSI of your choice (links below)
transfer kvt to your phone to external microSD, keep the rest in your PC
1) go to fastboot mode (power+volume up simulaneously)
2) flash treble recovery (using fastboot command: fastboot flash recovery 'filename.img')
3) boot to recovery and wipe system, data, cache
Note: after boot to recovery, touchscreen doesn't work. Turn screen off and on to make it work!
4) in recovery, flash kvt zip. It will guide you through
5) reboot back to bootloader
6) flash chosen GSI as system image (fastboot flash system 'filename.img')
7) if you are coming from stock Pie, flash Oreo modem (fastboot flash modem NON-HLOS.bin)
reboot
Note: If you are coming from stock ROM, decryption may fail. The easiest way is to temporarily flash stock recovery. After decryption fails, it will prompt you to reboot and format data. TWRP can't do it, but stock recovery can. After you are booted, you can flash TWRP again.
Where to get GSIs:
the biggest list is here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
For Z2 Play, always download arm64 version and Aonly
There is a folder with ported stock ROMS (MIUI, Samsung, Moto...) on mirrors.lollinet but they do not work on Z2 Play. I also tried various stock ROM ports from other sources and they did not work. Custom ROMs fork fine.
Magisk:
Standard Magisk versions may not work. If you get bootloop, after installing Magisk, flash uninstaller. Then you can try phusson's version:
leodexe said:
Updates:
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
Click to expand...
Click to collapse
Ask if something isn't clear.
updated treble
Updates:
KVT 2.6: https://androidfilehost.com/?fid=8889791610682867863
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
I am currently using Pixel Experience Plus (Android 10) GSI, I installed it with latest KVT 2.6 and most stuff works out of the box. If you come from Stock Pie you need to flash the modem file from Stock Oreo to get proper audio during calls, as the modem from Android 9 gets bugged on Custom ROMs breaking the audio during calls. http://www.mediafire.com/file/q8nbpybxc8mjyew/NON-HLOS-Z2P-STOCK-8-OREO.7z/file
Confirmation
Mate can u confirm whether this kvt fix the screen flickering issue when there are more than 3 notifications in the status bar and does it have fingerprint gestures enabled???
lordfinix said:
Mate can u confirm whether this kvt fix the screen flickering issue when there are more than 3 notifications in the status bar and does it have fingerprint gestures enabled???
Click to expand...
Click to collapse
I don't use fingerprint gestures so I can't tell you about that. Also I had experiencing some crashes and reboots with this GSI lately, so I will try with another one once I can access internet to download anothet GSI.
CONFIRMED
i confirm it by flashing the flickering issue is gone and the gestures works as well this is by far the most stable KVT released kudos to developers
There are new versions of kvt available. Check the updated first post for link to deivesj's last files.
I did not experience any flickering or other graphical glitches with the new (2.X) versions of kvt (unlike the old v8 one).
Fingerprint gestures work, but not in all gsis
leodexe said:
Updates:
KVT 2.6: https://androidfilehost.com/?fid=8889791610682867863
Magisk 20.x: https://sourceforge.net/projects/expressluke-gsis/files/Extras/phh-magisk-ten/
I am currently using Pixel Experience Plus (Android 10) GSI, I installed it with latest KVT 2.6 and most stuff works out of the box. If you come from Stock Pie you need to flash the modem file from Stock Oreo to get proper audio during calls, as the modem from Android 9 gets bugged on Custom ROMs breaking the audio during calls. http://www.mediafire.com/file/q8nbpybxc8mjyew/NON-HLOS-Z2P-STOCK-8-OREO.7z/file
Click to expand...
Click to collapse
Thanks, I will update the guide
Could someone please give me a mirror of kvt v2.6? androidfilehost is terribly slow...
Hello,
Seem to have lost my network after flashing the pixel experience gsi from stock. imei missing as well. Any help?
It may be problem with modem.
What was your stock ROM? 8.0 or 9.0?
What version of kvt did you use? 2.x or 3.x?
How install?
how is the modem installed?
It's explained in the guide, step 7.
Wrongly flashed modem may cause WiFi, Bluetooth and SIM not to work
Kvt link is down. But you can use LineageOS with treble support now