Hi All,
I had Lineage 14.1 ROM on my Nexus 9.
I wanted to use Xposed framework for a project which does not work with 7.0+.
Hence I want to go back to 6.0 ROM.
I have tried 3 different 6.0 ROMs so far, all of which resulted in bootloop.
Just now I flashed 14.1 Lineage OS again and it boots up just fine.
Can anybody tell me what I'm missing here? I'm using TWRP recovery 3.1.1-0
pikudroid said:
Hi All,
I had Lineage 14.1 ROM on my Nexus 9.
I wanted to use Xposed framework for a project which does not work with 7.0+.
Hence I want to go back to 6.0 ROM.
I have tried 3 different 6.0 ROMs so far, all of which resulted in bootloop.
Just now I flashed 14.1 Lineage OS again and it boots up just fine.
Can anybody tell me what I'm missing here? I'm using TWRP recovery 3.1.1-0
Click to expand...
Click to collapse
Gotta wipe everything, including internal storage, factory reset. Also the vendor and bootloader for 6.0
madbat99 said:
Also the vendor and bootloader for 6.0
Click to expand...
Click to collapse
Can you elaborate on that? What exactly do you mean?
pikudroid said:
Can you elaborate on that? What exactly do you mean?
Click to expand...
Click to collapse
If you are going back to 6 with a custom ROM, you also need to flash the vendor image from that version of Android as well. Just download the factory image of 6.0 from Google's factory image page, then extract the zip, then extract the zip that's in there. In those files will be a vendor.img. put it in the tablet somewhere you can find it (like download folder) or on USB stick or wherever you're putting the ROM zip you're flashing. When flashing ROM and gapps also install vendor image to vendor partition. TWRP has the option to flash image files.
This is something needed on 64 bit Android devices.
Bootloader has to be installed with fastboot, but come to think, I don't think you have to downgrade bootloader. Pretty sure having the newer bootloader is fine. Vendor should match the version of Android you're using though.
madbat99 said:
If you are going back to 6 with a custom ROM, you also need to flash the vendor image from that version of Android as well. Just download the factory image of 6.0 from Google's factory image page, then extract the zip, then extract the zip that's in there. In those files will be a vendor.img. put it in the tablet somewhere you can find it (like download folder) or on USB stick or wherever you're putting the ROM zip you're flashing. When flashing ROM and gapps also install vendor image to vendor partition. TWRP has the option to flash image files.
This is something needed on 64 bit Android devices.
Bootloader has to be installed with fastboot, but come to think, I don't think you have to downgrade bootloader. Pretty sure having the newer bootloader is fine. Vendor should match the version of Android you're using though.
Click to expand...
Click to collapse
Thanks a lot. Flashing vendor.img worked for me.
pikudroid said:
Thanks a lot. Flashing vendor.img worked for me.
Click to expand...
Click to collapse
Glad it helped. Hope I didn't over-explain, lol
Hello,
I just ordered my X820 for dirt cheap (€136). I wanted to ask you about the routine of getting custom ROMs up and running.
From what I understand the procedure is the following:
1. Activate USB debugging and OEM unlocking
2. Go to fastboot and use OEM unlock
3. Fastboot flash recovery TWRP.img
4. Boot into TWRP and format data????
5. Wipe system, caches, data, blah blah
6. Sideload lineage.zip, gapps.zip and magisk.zip eventually
7. Profit
Is this procedure correct? On my other (Xiaomi Redmi Note 3) phone I skipped formatting data and it still worked.
I don't need the stock ROM backup, lineage is the main reason I purchased this device.
I would fastboot TWRP before flashing it and do a full backup. You may need it at some point to fix fingerprint sensor or camera or return the phone to factory state in case of a warranty claim.
The procedure you describe is right, but no need to format data.
popoyaya said:
I would fastboot TWRP before flashing it and do a full backup. You may need it at some point to fix fingerprint sensor or camera or return the phone to factory state in case of a warranty claim.
The procedure you describe is right, but no need to format data.
Click to expand...
Click to collapse
I saw a guide where it says I should boot into TWRP (yes, boot into TWRP, via fastboot) and do a backup from there... Than actually install TWRP and other zips. So I'll do that, thanks.
Heyyo, formatting data is a good step because EUI ROM does some odd data partitioning and prevents custom ROMs from fully utilizing the data partition unless they do format data (it could show up as only 30GB available instead of closer to 54GB since the system partition takes a chunk of the 64GB and so on).
Also, I'd recommend OmniROM over LineageOS. LOS 14.1 is pretty good but OmniROM is more stable and has SafetyNet Google Certification without the need for Magisk hide and potentially Universal SafetyNet fix module.
If you want a ROM with similar environment to LOS 14.1 but with further enhancements to EAS, vendor and device tree? I'd recommend SlimRoms as it has a lot of good tweaks. SlimRoms does require Magisk Hide and for some they also require Universal SafetyNet fix module.
Ps. For some sideloading doesn't work but this does:
adp push nameoffile.zip /sdcard
Which copies the zip to the root of the sdcard folder.
Psps. once you flash a custom ROM you will want to flash an updated modem firmware as it fixes the fingerprint reader when the device sleeps for Nougat and experimental Oreo ROMs.
I recommend either the Chinese 26s 05.09 stable one here
https://yadi.sk/d/woKdrlRrv8yhr/Китай
And some also say developer 466D works better for them so experiment as you wish
https://yadi.sk/d/woKdrlRrv8yhr/Для разработчиков
ThE_MarD said:
Heyyo, formatting data is a good step because EUI ROM does some odd data partitioning and prevents custom ROMs from fully utilizing the data partition unless they do format data (it could show up as only 30GB available instead of closer to 54GB since the system partition takes a chunk of the 64GB and so on).
Also, I'd recommend OmniROM over LineageOS. LOS 14.1 is pretty good but OmniROM is more stable and has SafetyNet Google Certification without the need for Magisk hide and potentially Universal SafetyNet fix module.
If you want a ROM with similar environment to LOS 14.1 but with further enhancements to EAS, vendor and device tree? I'd recommend SlimRoms as it has a lot of good tweaks. SlimRoms does require Magisk Hide and for some they also require Universal SafetyNet fix module.
Ps. For some sideloading doesn't work but this does:
adp push nameoffile.zip /sdcard
Which copies the zip to the root of the sdcard folder.
Click to expand...
Click to collapse
Thanks for the valuable info. I appreciate OmniROM, and SlimRom, and basically everyone that has contributed with a line of code. But I'm more of a LineageOS guy, I like the official Lineage stuff.
You say that on the official TWRP adb sideload doesn't work??? Edit: Oh I see, I will try, if that fails I will use push, thanks again.
ThE_MarD said:
I recommend either the Chinese 26s 05.09 stable one here
https://yadi.sk/d/woKdrlRrv8yhr/Китай
And some also say developer 466D works better for them so experiment as you wish
https://yadi.sk/d/woKdrlRrv8yhr/Для разработчиков
Click to expand...
Click to collapse
After I get the device out of the box I will update to the latest available update from the EUI updater, then I will proceed to install custom ROMs. On my other device doing that update updates the firmware as well, is this the case with this device?
Happy Hepatitis said:
After I get the device out of the box I will update to the latest available update from the EUI updater, then I will proceed to install custom ROMs. On my other device doing that update updates the firmware as well, is this the case with this device?
Click to expand...
Click to collapse
Heyyo, yes they do as they include the firmware files.
Updating to one of the latest EUI versions requires upgrading to the same locale version.
If your phone is an x820 (it'll say on the back of the device) then Chinese 26s is the official latest but there is a leaked 28s.
If your device is a x829 like mine? They come with EUI 5.8.016s which is a modified vendor version that blocks updating even via the update.zip method... So that one you would be screwed and would need to unlock bootloader and then try either fastboot or TWRP flashing a different version of EUI ROM.
Sadly the LeEco official servers were down last I checked but there is a thread in the guides section that has links to the latest versions and I think Google drive backup links too.
I think x821 might be the India model but I could be wrong. If so then their latest is EUI 19s
ThE_MarD said:
Heyyo, yes they do as they include the firmware files.
Updating to one of the latest EUI versions requires upgrading to the same locale version.
If your phone is an x820 (it'll say on the back of the device) then Chinese 26s is the official latest but there is a leaked 28s.
If your device is a x829 like mine? They come with EUI 5.8.016s which is a modified vendor version that blocks updating even via the update.zip method... So that one you would be screwed and would need to unlock bootloader and then try either fastboot or TWRP flashing a different version of EUI ROM.
Sadly the LeEco official servers were down last I checked but there is a thread in the guides section that has links to the latest versions and I think Google drive backup links too.
I think x821 might be the India model but I could be wrong. If so then their latest is EUI 19s
Click to expand...
Click to collapse
It's a X820 4GB RAM 32GB storage version, I ordered it from geekbuying.
Happy Hepatitis said:
It's a X820 4GB RAM 32GB storage version, I ordered it from geekbuying.
Click to expand...
Click to collapse
Ah cool! You should be lucky then and not be stuck on one of those vendor ones like my x829.
The easy way to tell is in your settings you will have an update checker. My x829 did not and wouldn't let me try the recovery update.zip method.
So you'll want to get the EUI ROM latest for your phone and then rename it to update.zip and place it into the root of your sdcard (/sdcard) and then boot to recovery and there should be a selection for "update from file".
https://forum.xda-developers.com/le-max-2/how-to/le-max-2-official-stock-firmware-links-t3433761/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOUR WARRANTY WILL BE VOID
I AM NOT responsible for anything that may happen to your phone while attempting to follow this guide.
You are doing so at your own risk, and you take full responsibility for your decisions and actions.
You are not to blame me or XDA, or any of it's respected developers.
Anyways, now that that is out of the way. Those of us who have been in the Axon 7 forums know that information is quite scattered about. So it can be difficult for any newcomers to find everything they need before making any leaps or dives with their device. This guide’s purpose is to centralize the quickest and easiest steps to follow in order to get Treblized and to get on a stable Pie GSI build that can be used as a home base before experimenting further with other ROMs and/or GSIs.
Even if you are not satisfied with the Havoc Pie GSI, your device will still be in an optimal state to try the latest Oreo 8.1 ROMs, such as LOS 15.1 or DotOS 2.5, or to try any of the other Pie GSIs in the Treble forums.
Things you will sacrifice:
No VOLTE
No Encryption
No Dolby
No Daydream
No AK4490 DAC (will default to AK4491)
Camera Flash out of sync (Use OpenCamera for flash shots)
Not able to set password for Hotspot (Open connection only)
Again, if you don't find using a Pie GSI worth these sacrifices after trying it out, you can easily move to an Oreo ROM like LOS 15.1 or DotOS 2.5, which have more functioning features.
----------------------------------------
DOWNLOAD
----------------------------------------
(NOTE: The below setup will be fluid as discussion in this thread finds more stability with newer vendor builds and newer HavocOS 2.0 GSI builds)
After completion of this guide, your device will be setup with the following (might as well download everything):
Oki's TWRP 3.2.3.0 Lab's Mod v1.3
B20 Bootstack by DrakenFX - Modified by Verequies (Splash or NoSplash)
Oreo Modem (U, G, or Chinese)
DotOS 2.5 boot.img (This also contains the DotOS vendor, if you wish to use it)
LOS 15.1 vendor (20181110) build
HavocOS 2.0 Pie GSI (20181027) build - NOTE: Most GSIs are provided compressed. You must extract the .img file from the downloaded file.
Your preferred GApps ( https://opengapps.org/ ) (ARM64, 9.0, Micro or below only)
Also download OrdenKrieger's TWRP 3.2.3.0, going to need it handy to flash the vendor img.
And the NFC_Hotspot Fix by Kountry83 (You will need this for almost every GSI you try)
----------------------------------------
FAQ
----------------------------------------
WHATS UP WITH THE BOOTSTACKS?
The bootstacks that are currently available for the Axon are somewhat of a mess, if not careful, you can easily brick your device.
For Pie GSI setups, I recommend the B20 bootstack by DrakenFX that has been modified by Verequies, Splash version.
Verequies has asked that I also link the NoSplash version in case some users have issues with the Splash version, but many testers have had no problems with the Splash version on this setup.
Unlike the DrakenFX B20 bootstack, these modified versions do not flash the modem, so there is no need to flash modem again when switching between them. Sometimes will need to Unlock Password in TWRP when switching though, it will say not recognized.
Splash
Ability to have Read/Write access in system.
Nice three logo splash screen, replacing bootloader warning screen.
No bootloader warning screen means not able hit volume button during boot to get menu for Recovery, Fastboot, etc.
Which also means you will have to use power button + volume up combo to enter Recovery, or reboot to recovery from the ROM.
No EDL three button combo.
Can't charge without booting system or TWRP.
NoSplash
Read Only access in system. (Which will break Magisk)
Ugly bootloader warning screen.
Able hit volume button during boot to get menu for Recovery, Fastboot, etc.
Able to use EDL three button combo.
Allows offline charging without booting into system.
WHY EDL?
Starting out with Oki’s LOS 15.1 EDL package just makes it easier for everyone. It’s easier for you because there will be less steps needed to get treblized, which will also mean less room for error. It’s easier for me because it makes for a much shorter guide, and it’s easier to find answers to issues if we all started on the same page. However, if there are enough requests, I’ll make a longer guide without the use of EDL.
If you are already treblized you won’t necessarily need to EDL (in most cases), but if you run into issues please don’t comment until you’ve tried starting with first step.
----------------------------------------
GUIDE
----------------------------------------
STEP 1:
Please follow Oki’s Easy Guide to EDL LOS15.1
IT IS IMPORTANT TO FOLLOW EVERY STEP
Try not to boot into system while going through the steps if possible, but it’s ok if you do.
You can use @djkuz Axon 7 EDL Tool, instead of MiFlash, if you are more familiar with that.
Also, in step 12, it states to format to F2FS, but I recommend to format to EXT4 for the best compatibility with GSIs. As a precaution, to make sure your partitions will read correctly, format the partitions to F2FS per the instructions, then format them back to EXT4.
You can always test if F2FS works for you later.
Thank you @Oki for this wonderful starting point for new Treble users.
CONGRATULATIONS - You are now TREBLIZED and should never have to do Step 1 again.
STEP 2:
Once done with Oki’s guide, stay in TWRP
Wipe Dalvik, Cache, Vendor, System and Data.
Flash the bootstack you chose.
Flash the appropriate modem for your variant.
CONGRATULATIONS - You should never have to flash those again, unless changing bootstack for whatever reason.
STEP 3:
In TWRP make sure System and Vendor partitions are mounted.
Flash the DotOS Vendor flashable.
(It doesn’t have DotOS in the file name, so it should be named something like “Vendor_Flashable_GSI…”)
In TWRP go to Install and in the bottom right select Install Image
Now we flash the Havoc GSI image you extracted, selecting the System partition.
DO NOT BOOT TO SYSTEM - We need to use OrdenKrieger’s TWRP 3.2.3.0 to flash the LOS 15.1 vendor.img
(If you wish to use the DotOS vendor, you can skip to Step 5. You will still need to reboot to Recovery, so don't skip that.)
STEP 4:
Flash TWRP 3.2.3.0 to Recovery partition and then reboot to Recovery
You should now be in TWRP 3.2.3.0
Flash the LOS 15.1 vendor.img to the Vendor partition
DO NOT BOOT TO SYSTEM - We need to restore Oki’s TWRP and flash GApps.
STEP 5:
Flash Oki’s TWRP 3.2.3.0 Lab’s Mod to Recovery partition and then reboot to Recovery
You should now be in Oki’s TWRP 3.2.3.0 Lab’s Mod
Flash GApps
Make sure System and Vendor are mounted
Flash the NFC_Hotspot Fix
NOW BOOT SYSTEM
I will wait here while you setup your device.
DONE? GOOD. Lets set up Magisk and pass SafetyNet
STEP 5:
At this time I recommend Magisk 17.2
Find it, download it, and flash it in TWRP
Once booted, in Magisk search for the module “MagiskHide Props Config” and install it.
Then search for BusyBox module by Osmosis and install it.
Reboot
Using a terminal app (not in TWRP) like Termux, type “su”
Grant root privileges
Then type “props”
You should be greeted with a menu
Select 1 to Edit fingerprint
Select F to Pick a Certified fingerprint
Then follow the menu to select ZTE and Axon 7
Then yes and yes to reboot.
Everything should be good to go now. ENJOY!!
To add just a few more options to your setup without overdoing it with a heavy launcher, I highly recommend:
Lean Launcher Optimized
I will surely be adding to this guide and modifying it as the situation evolves. So feel free to give me any input on how to improve it.
----------------------------------------
THANKS
----------------------------------------
Thanks to @raystef66 and all of the testers in the [SUMMARY][PIE] BEST PIE ROMS to TRY thread, as well everyone in the "Axon7 (s)GSI trebleSHOOT" Telegram group, for testing, "trebleSHOOTing" and reporting your findings.
Thanks to @Oki again for his easy guide and LOS 15.1 EDL package.
Thanks to @Unjustified Dev for uploading separate vendors for us GSI users, and for all of the work he's done on LOS and his help in the LOS threads.
Thanks to @Verequies for creating the two modified versions of @DrakenFX 's B20 bootstacks, and of course @DrakenFX for his B20 and B12 bootstacks.
Thanks to @SaintZ93 for his work on DotOS and for providing a flashable for boot and vendor only.
Thanks to @SaintZ93 and @Skrem339 for their great work on the Schwifty kernel.
And thanks to @hundeva for his work on Lean Launcher.
----------------------------------------
GUIDE EDIT LOG
----------------------------------------
11/22 - Updated that it is optional to stay with DotOS vendor and skip a step.
11/30 - Changed Step 1 to recommend EXT4 for best compatibility. Also to format from EXT4 to F2FS, then back to EXT4, to avoid internal storage error some are getting.
12/10 - Props Config module now requires BusyBox module, updated Step 5.
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
JKSurf said:
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
Click to expand...
Click to collapse
Please make sure you redownload Ordens TWRP. There are two of them with the same name out there. The one I linked should allow you to see Vendor partition. I should list this step as optional, as the DotOS vendor works, Ive just found the LOS vendor to show improvement personally. I also wanted to teach how to flash vendor.img, as there is only one way atm, using Ordens TWRP.
The vendor setup in this guide is all based off LOS sources, so any issues LOS is having that are vendor related will carry over to this setup. Sorry.
Really nice guide, sadly I just flashed but one thing that I like is that you try to explain why you choose what you choose and I would really like if you could elaborate more on that for example why DotOS boot image and kernel or why LOS 15.1 vendor.
And also is there a way for me (or anyone on havoc), already on havoc but got there differently, to painlessly migrate to your setup?
I am using this gsi for a week and I like it a lot. It has better battery life than LOS 16 right now and you can customise so much.
And btw for me daydream works normally and I installed the ported pixel camera with night sight, which seems to work normal, too.
Mousman said:
Really nice guide, sadly I just flashed but one thing that I like is that you try to explain why you choose what you choose and I would really like if you could elaborate more on that for example why DotOS boot image and kernel or why LOS 15.1 vendor.
And also is there a way for me (or anyone on havoc), already on havoc but got there differently, to painlessly migrate to your setup?
Click to expand...
Click to collapse
I found minor things to work better with the LOS vendor, such as GPS locking and Bluetooth not freezing display data in my car. Of course this can vary from user to user. And my preference changes as well when I find improvements with other vendors.
The DotOS vendor flashable is provided as it's the easiest way to get an up to date vendor. Otherwise you would have to download and flash an entire ROM, or extract the boot.img from that ROM, or modify the install script. Unjustified didn't provide the LOS vendor in combo with the boot.img, so the DotOS flashable is the best option as of now.
If you're already on the Havoc GSI, then you can just flash the bootstack, wipe vendor, flash DotOS vendor flashable, flash LOS vendor.img if you want (using Ordens TWRP), flash Magisk. Then boot.
It will feel like a dirty flash, but it's not, thanks to Treble.
Please do a full backup before doing so, as I think if your vendor partition was created differently, pulled from data, it might not work.
Kleva94 said:
I am using this gsi for a week and I like it a lot. It has better battery life than LOS 16 right now and you can customise so much.
And btw for me daydream works normally and I installed the ported pixel camera with night sight, which seems to work normal, too.
Click to expand...
Click to collapse
I don't use Daydream, I only know what was reported by others. If more people want to test and report that it's working, I'll gladly remove it from the sacrifices.
EBeatFLA said:
I don't use Daydream, I only know what was reported by others. If more people want to test and report that it's working, I'll gladly remove it from the sacrifices.
Click to expand...
Click to collapse
Re. sacrificing encryption, I thought LOS 15.1 vendor supports it. Is that not enough?
In other words, do you need vendor + system + rom for encryption to work? Or just system + rom? Or...?
Thx for all your work.
piet8stevens said:
Re. sacrificing encryption, I thought LOS 15.1 vendor supports it. Is that not enough?
In other words, do you need vendor + system + rom for encryption to work? Or just system + rom? Or...?
Thx for all your work.
Click to expand...
Click to collapse
This particular setup will sacrifice encryption. Getting encryption on a GSI would be another path. The TWRP and bootstack options we have for our device play a part in why I find encryption to be a mess right now, and chose to move forward without it.
I'm kinda having issues flashing LOS 15.1 vendor.img. I flashed Ordens TWRP, the one you provided but I do not get an option to flash to vendor partition when I choose to flash that LOS 15.1 vendor.img
g0dzstar said:
I'm kinda having issues flashing LOS 15.1 vendor.img. I flashed Ordens TWRP, the one you provided but I do not get an option to flash to vendor partition when I choose to flash that LOS 15.1 vendor.img
Click to expand...
Click to collapse
JKSurf said:
Thanks for the guide!
On step 4, The vendor partition doesn't show up on orden's twrp. You probably already know you can't flash with Okis twrp. Skipped this step and it booted anyway.
Don't beat me up about this but for those of us with the 50% battery bug, it happens with this method.
Click to expand...
Click to collapse
OMG guys, so sorry, was linking to the wrong TWRP. Link updated. It's not on AFH, so if you don't trust it's a legit link and want to check, it's the same link in the LOS16 op.
Thanks for testing.
Did everything from guide, but it seems like i don't have access to internal storage in havoc os and still accesible in twrp. Any suggestion what i did wrong?
Reakleases said:
Did everything from guide, but it seems like i don't have access to internal storage in havoc os and still accesible in twrp. Any suggestion what i did wrong?
Click to expand...
Click to collapse
Make sure to follow all of the steps in Oki's guide. Also, if you used the NoSplash bootstack, that might be it. But I'm pretty sure it's a missed step in his guide.
did everything again without success, but something of that helped, tried chmod 755 on root directory and fix contexts.
Really nice guide, thanks!
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
juniorD said:
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
Click to expand...
Click to collapse
Make sure system and vendor are mounted before flashing.
juniorD said:
Having an issue flashing the DotOS vendor file. Getting the error 7. Edited the file with Notepadd ++ and took out the assert line and deleted the empty line. Resaved and recompressed zip and tried to flash and still getting the error. Followed all the steps to this point no issues.
Click to expand...
Click to collapse
Wrong bootstack,flash bootstack again!
Also i read in previous post,people are not wiping correctly the system with clean flash
Predatorhaze said:
Wrong bootstack,flash bootstack again!
Also i read in previous post,people are not wiping correctly the system with clean flash
Click to expand...
Click to collapse
Thanks for the reply.
I flashed the bootstack in the EDL package uploaded in the guide using MiFlash went through fine. Also did a clean wipe of everything and formatted my Internal Storage before I flashed the package.
---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------
EBeatFLA said:
Make sure system and vendor are mounted before flashing.
Click to expand...
Click to collapse
Yup did that and checked a second time to make sure I did. They were mounted.
---------- Post added at 07:52 AM ---------- Previous post was at 07:51 AM ----------
EBeatFLA said:
Make sure system and vendor are mounted before flashing.
Click to expand...
Click to collapse
Yup did that and checked a second time to make sure I did. They were mounted.
Hi,
I've been out the custom rom game since Lollipop and feel very much like a N00b again.
I flashed the latest stable PIE miui through TWRP then flashed a few custom roms to test. Got hit with the whole encryption merry go round and managed to somehow stop this by flashing one of these disableencrypt zips I believe. I have no idea if this will happen again and I am scared my internal data will get encrypted again. how do I permanently disable this?
I also have the following error what have i done wrong, do i need to fix this and what effect does it have on my Poco:
ANDROID SYSTEM
Your vendor image does not match the system. Please flash the PKQ1.180729.001 vendor image for your device.
Any guidance would be much appreciated,=.
gmengass said:
Hi,
I've been out the custom rom game since Lollipop and feel very much like a N00b again.
I flashed the latest stable PIE miui through TWRP then flashed a few custom roms to test. Got hit with the whole encryption merry go round and managed to somehow stop this by flashing one of these disableencrypt zips I believe. I have no idea if this will happen again and I am scared my internal data will get encrypted again. how do I permanently disable this?
I also have the following error what have i done wrong, do i need to fix this and what effect does it have on my Poco:
ANDROID SYSTEM
Your vendor image does not match the system. Please flash the PKQ1.180729.001 vendor image for your device.
Any guidance would be much appreciated,=.
Click to expand...
Click to collapse
1- First of all encryption is by default in pie so you have to flash DfE every time you update or install a ROM and also in case of updating vendor or firmware . DfE has to installed after the ROM installation otherwise storage will get encrypted and only option would be left for decryption is format
2- For vendor mismatch flash vendor for here
https://downloads.akhilnarang.me/MIUI/beryllium/
prabh98 said:
1- First of all encryption is by default in pie so you have to flash DfE every time you update or install a ROM and also in case of updating vendor or firmware . DfE has to installed after the ROM installation otherwise storage will get encrypted and only option would be left for decryption is format
2- For vendor mismatch flash vendor for here
https://downloads.akhilnarang.me/MIUI/beryllium/
Click to expand...
Click to collapse
thanks for the information,
1. Do I still have to flash Dfe every time I do an OTA update on custom roms?
2. What affect does the vendor mismatch have? will this format my data?
gmengass said:
thanks for the information,
1. Do I still have to flash Dfe every time I do an OTA update on custom roms?
2. What affect does the vendor mismatch have? will this format my data?
Click to expand...
Click to collapse
1- yes
2- no
Hello, I am newbie yet so I am asking if anyone can explain the vendor's use, and what do I get from installing them.
Thank you for your time
Now almost roms here includes custom vendor. So you need firmware only.
https://xiaomifirmwareupdater.com/vendor/beryllium/
And here's custom rom installation process
Flash rom
Flash firmware
Gapps(optional)
Dfe(if you don't want it to be encrypted)
Magisk(optional)
That's it. No need to know more.
nasos_Gr said:
Hello, I am newbie yet so I am asking if anyone can explain the vendor's use, and what do I get from installing them.
Thank you for your time
Click to expand...
Click to collapse
Miui decided to use MODIFIED VENDOR IMAGE hence POCO F1 gets a modified vendor image for Android Pie-based Project Treble GSIs
what was the impact?
custom roms couldn't be flashed (booted) if you don't flash the modified vendor image from twrp
even today when most of the roms have their own vendor you still need to flash the vendor+firmware (atleast)
Developer Akhil Narang started collecting all releases at
https://mirror.akhilnarang.me/MIUI/beryllium/
currently I am using 9.6.27-9.0 which is working best for me, 10.3.6 image made my batter drainage high (atleast i noticed)
I am on HAVOC2.8 and this is how i did it
1. flashed TWRP 3.3.1 unofficial (download it from HERE ) ref Reference - as official twrp has TOUCH driver issues. this one worked with me very well
2. I wiped /data, /system then
3. flashed VENDOR.zip from HERE
4. FLASHED CUSTOM ROM (i use HAVOC2.8)
5. FLASHED DFE HERE - REFERENCE
6. FLASHED GOOGLE APPS ( GAPPS.ORG) ( ARM64>9.0MicroPackage)
7. Flash Kernel ( OPTIONAL- havoc uses shadow kernel , i feel optimus drunk kernel is better, battery and 4g connectivity) even Franco Kernel is very good
8. FLASHING MAGISK19.3
9. when i was on havoc2.7, by using MIGRATE, it made flashable zip of my APPS+DATA, stored in internalStorage, and now I will FLASH that file., Mine size goes to 2gb you can get it from HERE
10. WIPE CACHE/DELVIK
11. REBOOT
fire reboot may go in to bootloop and then second reboot may take a while and finally you should see Pixel Setup asking google accounts and info etc
-----------------------
extraa
once after you finish setup! don't RESTORE APPS from PLAYSTORE, (download only license apk, in my case I have purchases many apps from playstore and saperate license info is always appear in intial setup! SELECT THOSE ONLY)
ONCE playstore is DONE downloading all your selected (fewer) apps, and MAGISK ROOT is working...... put device on AIRPLANE MODE
FROM DROP DOWN Notification panel, CLICK MIGRATE, and it will prompt you what do you wana restore from your previouce ROM to newly flashed HAVOC ..APPS+SETTINGS+PERMISSION+DATA etc - migrate restoration may take upto 30 mins,
once done, uninstall from system and reboot device!
REMEMBER I DONOT RECOMEND MIGRATE TRICK FOR WHATSAPP, it doesn't work properly and NOTIFICATION ISSUES with BLANK DP observed by me whenever I forcely re-instated whatsapp by migrate!
Martensite said:
Now almost roms here includes custom vendor. So you need firmware only.
https://xiaomifirmwareupdater.com/vendor/beryllium/
And here's custom rom installation process
Flash rom
Flash firmware
Gapps(optional)
Dfe(if you don't want it to be encrypted)
Magisk(optional)
That's it. No need to know more.
Click to expand...
Click to collapse
I understand but I have installed some custom Roms without finding vendor image and still it works perfect.
And do I need to install this image every time I flash a new ROM?
Thanks
nasos_Gr said:
I understand but I have installed some custom Roms without finding vendor image and still it works perfect.
And do I need to install this image every time I flash a new ROM?
Thanks
Click to expand...
Click to collapse
Flashing custom roms will not wipe anything, so the vendor is still there. And firmwares too.