Related
# This file is automatically generated by FMegantara.
# Do not modify this file -- YOUR CHANGES WILL BE ERASED!
#
# This file must be checked in Version Control Systems.
#
# To customize properties used by the Ant build system use,
# "comment on box", and override values to adapt the script to your
# project structure.
# Project target.
# target=iLuminouss Inc.:iLuminouss APIs:666
This MIUI V5 has been ported from Huawei G520, and now support ota update from me via dropbox link. The ROM include updater.apk for check OTA Update from huawei g520. But, do not update from there it just for check. the official update just from me via dropbox link.
Click to expand...
Click to collapse
Download ROM :
MIUI V5 4.1.14 - http://d-h.st/BIc
Download OTA Update via DB :
MIUI V5 4.1.21 - OTA Patcher - https://www.dropbox.com/s/nv2cetyeloid42l/Patcher-MIUI5_4.3.21.zip
Additional Patch Update Fix Some Problem :
Additional Patch Update - https://www.dropbox.com/s/f6u1s9fqhir5uta/Additional_Patch-MIUIV5_4.3.14_4.3.21.zip
How To Install ROM :
Download ROM.zip from link and save on sdcard
Go to CWM (Recovery Mode) or TWRP
Wipe data, Wipe Cache, Wipe Cache Partitions
Install ROM.zip from sdcard
Wipe data & wipe cache
Reboot
How to install OTA Update :
Download OTAUpdate.zip from link and save on sdcard
Go to CWM (Recovery Mode)or TWRP
Install OTAUpdate.zip
Reboot
Changelog by me :
MIUI V5 Version 4.1.14
Support OTA Update via DB
Lag Fixer
New Entropy by kernel script
Credits :
Iluminouss Fams
Reza Rivani
Fajrin Ca
Muhammad Rizky
Official MIUI v5 changelog :
changelog 4.3.21 :
http://en.miui.com/thread-17481-1-1.html
changelog 4.3.14 :
http://en.miui.com/thread-16908-1-1.html
Click to expand...
Click to collapse
any fix for dual signal bars???
petrukgrinder said:
# This file is automatically generated by FMegantara.
# Do not modify this file -- YOUR CHANGES WILL BE ERASED!
#
# This file must be checked in Version Control Systems.
#
# To customize properties used by the Ant build system use,
# "comment on box", and override values to adapt the script to your
# project structure.
# Project target.
# target=iLuminouss Inc.:iLuminouss APIs:666
Download ROM :
MIUI V5 4.1.14 - http://d-h.st/BIc
Download OTA Update via DB :
MIUI V5 4.1.21 - OTA Patcher - https://www.dropbox.com/s/nv2cetyeloid42l/Patcher-MIUI5_4.3.21.zip
Additional Patch Update Fix Some Problem :
Additional Patch Update - https://www.dropbox.com/s/f6u1s9fqhir5uta/Additional_Patch-MIUIV5_4.3.14_4.3.21.zip
How To Install ROM :
Download ROM.zip from link and save on sdcard
Go to CWM (Recovery Mode) or TWRP
Wipe data, Wipe Cache, Wipe Cache Partitions
Install ROM.zip from sdcard
Wipe data & wipe cache
Reboot
How to install OTA Update :
Download OTAUpdate.zip from link and save on sdcard
Go to CWM (Recovery Mode)or TWRP
Install OTAUpdate.zip
Reboot
Changelog by me :
MIUI V5 Version 4.1.14
Support OTA Update via DB
Lag Fixer
New Entropy by kernel script
Credits :
Iluminouss Fams
Reza Rivani
Fajrin Ca
Muhammad Rizky
Click to expand...
Click to collapse
any fix for dual signal bars?????
---------- Post added at 10:45 AM ---------- Previous post was at 09:53 AM ----------
petrukgrinder said:
# This file is automatically generated by FMegantara.
# Do not modify this file -- YOUR CHANGES WILL BE ERASED!
#
# This file must be checked in Version Control Systems.
#
# To customize properties used by the Ant build system use,
# "comment on box", and override values to adapt the script to your
# project structure.
# Project target.
# target=iLuminouss Inc.:iLuminouss APIs:666
Download ROM :
MIUI V5 4.1.14 - http://d-h.st/BIc
Download OTA Update via DB :
MIUI V5 4.1.21 - OTA Patcher - https://www.dropbox.com/s/nv2cetyeloid42l/Patcher-MIUI5_4.3.21.zip
Additional Patch Update Fix Some Problem :
Additional Patch Update - https://www.dropbox.com/s/f6u1s9fqhir5uta/Additional_Patch-MIUIV5_4.3.14_4.3.21.zip
How To Install ROM :
Download ROM.zip from link and save on sdcard
Go to CWM (Recovery Mode) or TWRP
Wipe data, Wipe Cache, Wipe Cache Partitions
Install ROM.zip from sdcard
Wipe data & wipe cache
Reboot
How to install OTA Update :
Download OTAUpdate.zip from link and save on sdcard
Go to CWM (Recovery Mode)or TWRP
Install OTAUpdate.zip
Reboot
Changelog by me :
MIUI V5 Version 4.1.14
Support OTA Update via DB
Lag Fixer
New Entropy by kernel script
Credits :
Iluminouss Fams
Reza Rivani
Fajrin Ca
Muhammad Rizky
Click to expand...
Click to collapse
Gapps pls.................
Just use Google installer or http://goo.im/gapps/gapps-jb-20130301-signed.zip
You can also download my light Gapps version should work either on miui. Its located in my signature under work.
Goodluck:fingers-crossed:
And petruk for the dual signal bars watch this video:
https://www.youtube.com/watch?v=VYl1BosJBVA
Correct my if i'm wrong, is this phone (K-Touch Titan S100) same model (a.k.a) with BLU Studio 5.3 S (USA) and N1 (Taiwan)?
Hey , this is a small tool -you can call it patch - to compress kernel / recovery ramdisk .
Why this tool ?
Simply some devices have little space for kernel / recovery like samsung galaxy star which has about 10MBs for kernel/recovery .
How to use :
You must first activate LZMA support for ramdisks in kernel Go to your kernel config file then change this
Code:
# CONFIG_RD_LZMA is not set
TO
Code:
CONFIG_RD_LZMA=y
Clone the tool under device/vendor_name/device_name.
Add those line to your BoardConfig.mk file .
Code:
# LZMA compression for recovery's & kernel ramdisk....
BOARD_CUSTOM_BOOTIMG_MK := device/vendor_name/device_name/custombootimg.mk
BOARD_CANT_BUILD_RECOVERY_FROM_BOOT_PATCH := true
Enjoy .
Note :
This tools is used while you building any ROM/Kernel/Recovery from source .
This tool should work with any device .
LZMA compression takes more time to decompress than GZIP but When I tested it didn't take more than 1 or 2 more seconds to decompress .
You won't be able to decompress boot.img or recovery.img using boot-repacker or unpack tool for linux as you will get an error because those tools won't be able to decompress ramdisks for recovery or kernel -boot-repacker only gives you kernel zImage- and If you want to edit anything in ramdisk you will need to build it again from source !!!
This tool derived from
http://review.cyanogenmod.org/#/c/96227/
http://review.cyanogenmod.org/#/c/118533/
Results using this tool :
Before :
Kernel ramdisk : 1.1 MB (1,117,760 bytes) .
recovery ramdisk : 4.2 MB (4,158,392 bytes) .
Total kernel.img : 9.1 MB (9,111,552 bytes) .
Total recovery.img : 12.2 MB (12,152,832 bytes) .
After :
Kernel ramdisk : 579.3 kB (579,257 bytes) .
recovery ramdisk : 2.7 MB (2,736,844 bytes) .
Total kernel.img : 8.6 MB (8,572,928 bytes) .
Total recovery.img : 10.7 MB (10,731,520 bytes) .
Something to discuss :
Maybe you find that these compress is not enough to save up the space or you maybe find this is very suitable for you , In my case it was useful in some aspects and not in others .
I tried to use LZMA compression for kernel zImage it self and it was pretty good (8 MBs to 2.9 MBs) but the problem that the kernel wasn't loaded so It themes that the bootloader of my device hate LZMA compression or anything else I didn't figure it out so If you find anyway to run and support LZMA compression for kernel please kindly let me know .
Download :
LZMA compression tool
Credit :
Andreas Blaesius
Dan Pasanen
LehKeda (ME )
Neat idea. How do I implement this into a ROM? I see boot.img and recovery.img tutorials but nothing for ROM.
RatchetPanda said:
Neat idea. How do I implement this into a ROM? I see boot.img and recovery.img tutorials but nothing for ROM.
Click to expand...
Click to collapse
You mean compress system.img with LZMA ? if yes , no you can't .
LahKeda said:
You mean compress system.img with LZMA ? if yes , no you can't .
Click to expand...
Click to collapse
Do you think you could modify TWRP so it could handle zips zipped using LZMA instead of just plain deflate? It'd be very useful to get 300-500mb zips down to 200-350mb
RatchetPanda said:
Do you think you could modify TWRP so it could handle zips zipped using LZMA instead of just plain deflate? It'd be very useful to get 300-500mb zips down to 200-350mb
Click to expand...
Click to collapse
It won't reduce the actual size of the ROM it will reduce the zip file size -you will have to download/upload 200 to 300 mb instead of 300 to 500 mb- so it isn't useful that much as you can compress rom zip file before uploading then decompress it again after downloading .
BTW ... Is it good to replace device default bootloader with another one ? and Is there any way to backup it ?
LahKeda said:
It won't reduce the actual size of the ROM it will reduce the zip file size -you will have to download/upload 200 to 300 mb instead of 300 to 500 mb- so it isn't useful that much as you can compress rom zip file before uploading then decompress it again after downloading .
BTW ... Is it good to replace device default bootloader with another one ? and Is there any way to backup it ?
Click to expand...
Click to collapse
Yes that's what I mean is reducing the zip file size, I don't care about the size of the ROM. You probably can on Nexus devices since they are developer friendly however I do not know about other devices.
RatchetPanda said:
Yes that's what I mean is reducing the zip file size, I don't care about the size of the ROM. You probably can on Nexus devices since they are developer friendly however I do not know about other devices.
Click to expand...
Click to collapse
Messing with recovery mechanism doesn't theme so much fair while you can do it by any other file compressor
LahKeda said:
Messing with recovery mechanism doesn't theme so much fair while you can do it by any other file compressor
Click to expand...
Click to collapse
What I'm saying is TWRP cannot currently handle flashable zips using anything other than plain Deflate so it would need modifying to support zips zipped using LZMA2 or Deflate64 for example.
RatchetPanda said:
What I'm saying is TWRP cannot currently handle flashable zips using anything other than plain Deflate so it would need modifying to support zips zipped using LZMA2 or Deflate64 for example.
Click to expand...
Click to collapse
that's theme a little bit interesting .....maybe I'll look into it .
The Problem
TLDR: In Oreo ROMs, i.e. Android 8.0/8.1, DualBoot Patcher no longer works, as patched ROMs/kernels will get stuck on Android logo screen(for the Axon 7, it's the 'ZTE, POWERED BY android' screen), and never boot up.
In Oreo(Android 8.0/8.1), Google introduced a new function to fstab, which is early mounting specific partitions. The purpose was so that Android can boot up faster, by ensuring that essential partitions like /system and /vendor are mounted first and the boot process will not be held back by delays in non-essential things like setting up apps. More details can be found here. So the important changes that affect DualBoot Patcher are: 1) There's an important file 'fstab.qcom', which lists all the partitions that Android can use, that got shifted from the '/' directory(the root partition/ramdisk, Android 7.x and below) to the '/system/vendor/etc' directory(in Android 8.x) 2) In addition, another file 'init.qcom.rc', once found in the '/' directory too(in Android 7.x and below), is now shifted to '/system/vendor/etc/init/hw' directory(in Android 8.x) 3) Because of 1), 'init.qcom.rc' now believes that 'fstab.qcom' is in '/system/vendor/etc' and not '/', and so it asks Android to read 'fstab.qcom' from '/system/vendor/etc' 4) In the 'fstab.qcom' file, there are entries for all partitions except /system(and /vendor for Treble devices). For these 2 partitions, they are now found in the dtb(short for Device Tree Binary). How does this affect DualBoot Patcher? 1) DualBoot Patcher expects that 'fstab.qcom' is still in '/' directory(correct me if I'm wrong), so it fails to find this file in Android 8.x ROMs/kernels 2) DualBoot Patcher expects that '/system' is still defined in 'fstab.qcom', which is not the case. Below are the exact changes that Google made(in the case of our Axon 7), note the red parts(the changes):
fstab.qcom(the strike means those lines are now removed/gone)
Code:
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults defaults
[STRIKE][COLOR="red"]/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,discard wait[/COLOR][/STRIKE]
init.qcom.rc
Code:
on fs
wait /dev/block/platform/soc/${ro.boot.bootdevice}
symlink /dev/block/platform/soc/${ro.boot.bootdevice} /dev/block/bootdevice
mount_all [COLOR="Red"]/vendor/etc/fstab.qcom[/COLOR]
dtb(converted into dts with dtc)
Code:
fstab {
compatible = "android,fstab";
vendor {
compatible = "android,vendor";
dev = "/dev/block/platform/soc/7464900.sdhci/by-name/vendor";
type = "ext4";
mnt_flags = "ro,barrier=1,discard";
fsmgr_flags = "wait";
status = "disabled";
};
[COLOR="red"]system {
compatible = "android,system";
dev = "/dev/block/platform/soc/624000.ufshc/by-name/system";
type = "ext4";
mnt_flags = "ro,barrier=1,discard";
fsmgr_flags = "wait";
status = "ok";
};[/COLOR]
};
The Solution
There are 3 changes to make for each ROM/kernel: 1) Edit fstab.qcom, dtb and init.qcom.rc 2) Add fstab.qcom and init.qcom.rc back into the ramdisk(i.e. edit the ramdisk) 3) Delete '/system/vendor/etc/fstab.qcom' and '/system/vendor/etc/init/hw/init.qcom.rc'. There are 2 ways you can do this, either manually, or with my script(Work in progress, my sincere apologies)
Method 1: Manually modify ROM and kernel
Files you will need:
Note: the 'files.zip' attached below contains 'dtc', 'magiskboot', 'mkbootimg', 'unpackbootimg'. Extract it to get these files. Feel free to scan them for viruses, I assure you they are clean and not viruses for sure
- boot.img you want to patch
- init.qcom.rc, fstab.qcom from the ROM you are patching
- magiskboot binary(found in /data/magisk or /data/adb/magisk if you installed magisk, otherwise download the one attached below)
- dtc binary(download the one attached below)
If you are patching Hellsgate or Schwifty, you also need:
- unpackbootimg, mkbootimg(attached below)
- Image.gz-dtb(from the flashable zip of the kernel)
Note: You also need a boot.img, but this will be from the ROM you are flashing/have flashed(extract from the ROM zip)
Preliminary step: Prepare the files
- Before you start, I would recommend copying all the files into a directory where you can chmod/execute binaries. I personally recommend '/data/local/tmp', or '/cache'(anywhere in /cache is fine). The guide below assumes that all these files are in the same directory. Also, chmod all the binaries, for example, do this in your working directory:
Code:
chmod 0755 *
- Also, I would recommend backing up 'fstab.qcom' and 'init.qcom.rc'
Additional Step: If you wish to patch kernels like Hellsgate and Schwifty
- First, unpack your ROM's stock kernel:
Code:
./unpackbootimg -i boot.img
- Then, repack the kernel as a Hellsgate/Schwifty kernel:
Code:
./mkbootimg --kernel Image.gz-dtb --ramdisk boot.img-ramdisk.gz --cmdline "androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] androidboot.selinux=permissive buildvariant=userdebug" --base 80000000 --pagesize 4096 --kernel_offset 00008000 --ramdisk_offset 01000000 --second_offset 00f00000 --tags_offset 00000100 --os_version 8.1.0 --os_patch_level [COLOR="red"]2018-06[/COLOR] --hash sha1 --output ./boot-new.img
- Note: For the red part in the above command, adjust for the month that your desired kernel is released. E.g. If your desired kernel was released in 2018 June, you put '2018-06', while if it was released in 2018 July, you put '2018-07', and so on.
- From now on, take note that everytime I mention 'boot.img', for you, it will be 'boot-new.img'(I'll bold each one that you have to change to 'boot-new.img')
Step 1: Unpack the boot.img
Code:
./magiskboot --unpack [COLOR="red"]boot.img[/COLOR]
- Now you get 3 additional files: 1) kernel(not editing this) 2) ramdisk.cpio(gonna edit this) 3) dtb(also editing this)
Step 2: Decompile the dtb
Note: dtb is a BINARY so don't open it with a text editor
Code:
./dtc -I dtb -O dts -o dt.txt dtb
- Another note: It will probably give you a lot of warnings, but it's harmless so just ignore them(I've edited multiple kernels and tested them myself, no bugs so far)
Step 3: Edit the decompiled dts
- Open the created 'dt.txt' with a root text editor(I use Simple Explorer, you can use FX file explorer, or ES file explorer)
- Search for this word:
Code:
/system
. You should find this line:
Code:
dev = "/dev/block/platform/soc/624000.ufshc/by-name/system";
- Remove the entire chunk quoted below:
Code:
system {
compatible = "android,system";
dev = "/dev/block/platform/soc/624000.ufshc/by-name/system";
type = "ext4";
mnt_flags = "ro,barrier=1,discard";
fsmgr_flags = "wait";
status = "ok";
};
- Take note that you will have to remove 1 '};'(at the bottom of the above quote), nothing more, nothing less
Step 4: Recompile the dtb
Code:
./dtc -I dts -O dtb -o dtb1 dt.txt
- Again, it might give you a lot of warnings but just ignore them
- Also, rename the new dtb so that magiskboot will compile this new dtb into your modified kernel:
Code:
mv dtb dtb.bak
Code:
mv dtb1 dtb
Step 5: Edit fstab.qcom
- Open 'fstab.qcom' file with a root text editor
- Add the following red line, below the line about '/recovery', above the line about '/data':
Code:
/dev/block/bootdevice/by-name/recovery /recovery emmc defaults defaults
[COLOR="red"]/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,discard wait[/COLOR]
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,nodiratime,data_flush wait,check,encryptable=/dev/block/bootdevice/by-name/cryptkey,quota,formattable[/CODE]
- Save the 'fstab.qcom' file
Step 6: Edit init.qcom.rc
- Open 'init.qcom.rc' with a root text editor
- Look for this line:
Code:
mount_all /vendor/etc/fstab.qcom
- Change it into this line:
Code:
mount_all [COLOR="red"]/fstab.qcom[/COLOR]
- Save the 'init.qcom.rc' file
Step 7: Modify kernel ramdisk
-First do:
Code:
./magiskboot --cpio ramdisk.cpio 'add 0640 fstab.qcom fstab.qcom'
- Then do:
Code:
./magiskboot --cpio ramdisk.cpio 'add 0750 init.qcom.rc init.qcom.rc'
Step 8: Create a new, DBP-compatible boot.img
Code:
./magiskboot --repack [COLOR="red"]boot.img[/COLOR]
- You will get a new boot.img, named 'new-boot.img'
Step 9: Install the modified kernel
- First, flash the boot.img(using TWRP or Flashify or another tool)
- Then, delete these 2 files:
Code:
/system/vendor/etc/fstab.qcom
and
Code:
/system/vendor/etc/init/hw/init.qcom.rc
- Note: Make sure you do not reboot after installing boot.img and before deleting the above 2 files
That's it! If you completed all the steps above properly, you should have a working DBP-compatible boot.img that you can put in a flashable zip and patch with DualBoot Patcher
if you don't know how to make a flashable zip to install your modified boot.img, you can use the one I attached below(named 'flashable-kernel-template.zip'). What you have to do is download it, then extract it and make a new zip containing your modified boot.img(basically, create a new zip with the 'META-INF' folder from my zip and your 'boot.img'. The zip automatically deletes
Code:
/system/vendor/etc/fstab.qcom
and
Code:
/system/vendor/etc/init/hw/init.qcom.rc
so you won't need to do this yourself
Note: If you are using my flashable zip, note that you have to rename your modified 'new-boot.img' to 'boot.img' before you compress it into a new flashable zip. Otherwise you will get an error when flashing in recovery
Note 2: Avoid using the flashable zip template for non-modified kernels, it can render your ROM unable to boot!
Method 2: Work in Progress
Method 2: Use my automated script
Please do leave feedback on whether this guide is clear, and also if any of the steps are not working for you! Happy Dualbooting
Sources:
Github Problem Discussion
Problem Solution
Reserved 1
Reserved 2
This is going to be useful. Personally I just want to run custom O as primary and N as a secondary. Mainly because O doesn't have properly working Daydream and for a couple of games that aren't compatible anymore with O. If I'm only trying to attach LOS14.1 as secondary I wouldn't need to patch anything extra O from this guide? Though I can't install the patched ROM it gives an error.
Edit: Oops missed reading from the old guide the primary ROM needs to be stock. I guess I need to patch then. Do I need Linux to do all the editing?
Infy_AsiX said:
This is going to be useful. Personally I just want to run custom O as primary and N as a secondary. Mainly because O doesn't have properly working Daydream and for a couple of games that aren't compatible anymore with O. If I'm only trying to attach LOS14.1 as secondary I wouldn't need to patch anything extra O from this guide? Though I can't install the patched ROM it gives an error.
Edit: Oops missed reading from the old guide the primary ROM needs to be stock. I guess I need to patch then. Do I need Linux to do all the editing?
Click to expand...
Click to collapse
Actually yeah, if your custom O is primary you don't need to patch it(the kernel, I mean)! You still need to patch the ROM so that it doesn't wipe /system when you OTA update your custom O, which means you need an unpatched custom O stock kernel flsshable zip(sorry for the mouthful). But if you don't OTA update then no need The last I tried, using stock ROM as secondary worked for me though? Didn't find any issues. But I might just be lucky, be careful if you try that.
As for your last question, nope all these commands are meant for Terminal Emulator app on an Android phone! Just use the binaries in the attached files.zip, they are all compiled for Android and do not work on Linux desktops. All the best If you need help just ask here!
haoyangw said:
Actually yeah, if your custom O is primary you don't need to patch it(the kernel, I mean)! You still need to patch the ROM so that it doesn't wipe /system when you OTA update your custom O, which means you need an unpatched custom O stock kernel flsshable zip(sorry for the mouthful). But if you don't OTA update then no need The last I tried, using stock ROM as secondary worked for me though? Didn't find any issues. But I might just be lucky, be careful if you try that.
As for your last question, nope all these commands are meant for Terminal Emulator app on an Android phone! Just use the binaries in the attached files.zip, they are all compiled for Android and do not work on Linux desktops. All the best If you need help just ask here!
Click to expand...
Click to collapse
Figured out the error after dual boot patch on LOS14.1 was my mistake in modifying the update-script incorrectly. Nothing to do with N/O/this guide. However now I tried installing it to data slot so dirty flashing and restoring the system partition won't be complicated. The issue is trying to boot primary it vibrates five times at ZTE logo and goes to recovery. Trying to switch to primary in dualbootutilities gives an error something like (from memory) data/media/0/boot.img cannot be found. I guess DBP installed even on data changes the structure of boot and primary on O doesn't fit so can't boot. Just want your advice, it probably means patching O when O is primary is necessary then?
Infy_AsiX said:
Figured out the error after dual boot patch on LOS14.1 was my mistake in modifying the update-script incorrectly. Nothing to do with N/O/this guide. However now I tried installing it to data slot so dirty flashing and restoring the system partition won't be complicated. The issue is trying to boot primary it vibrates five times at ZTE logo and goes to recovery. Trying to switch to primary in dualbootutilities gives an error something like (from memory) data/media/0/boot.img cannot be found. I guess DBP installed even on data changes the structure of boot and primary on O doesn't fit so can't boot. Just want your advice, it probably means patching O when O is primary is necessary then?
Click to expand...
Click to collapse
Oh you mean you flashed custom O, and after that you flashed you N data slot ROM? You're partially right, if you flash your data slot ROM after a non-patched ROM, you'll have the data slot kernel installed i.e. the LOS 14.1 stock kernel, which cannot boot an O ROM. This is because DBP works by storing multiple kernels on your /data/media/0/Multiboot folder, when you 'switch ROMs' actually what happens is DBP flashes the kernel of the ROM you're switching to. Obviously a N kernel cannot boot an O ROM so you cannot boot. Unfortunately, DBP only stores kernels that you flash with patched zips(i.e. if you flash a DBP-patched ROM/kernel zip, only then will DBP store the kernel in its custom Multiboot folder). So because you didn't patch your O primary ROM, its kernel is not saved and you cannot use DBPUtilities. What you can do is either make your own non-patched kernel zip file for your O ROM's stock kernel that you flash everytime you want to switch to primary, or you patch your primary ROM and then you can use DBPUtilities. However B01 kernel has a slightly different precedure for adding DBP support that this guide doesn't explain(I'm sorry) I'll update it when I find time. Don't follow this guide to patch B01! It won't boot, I tried But I know what changes to make when modifying a B01 kernel don't worry
lost this post when I pressed reply. This RR-O Kranoner 20180511 has the fstab.qcom and init.qcom.rc still on root / directory. But patching only DBP patching hellsgate kernel after having LOS14.1 on data slot 1 still has the same issue. Alternatively installing the mod boot.img allows primary to boot but after using DBP utilities to switch to data slot 1 (onscreen says success) the data slot 1 gets stuck on ZTE logo with 5 vibrates instead. Even tried flashing the final Beastmode 14.1 kernel DBP patched to data slot 1 after switched, five vibrates to recovery.
Lost Magisk install after step nine. Just reinstalling it is fine. Did you forget the flashable zip template by the way?
Infy_AsiX said:
lost this post when I pressed reply. This RR-O Kranoner 20180511 has the fstab.qcom and init.qcom.rc still on root / directory. But patching only DBP patching hellsgate kernel after having LOS14.1 on data slot 1 still has the same issue. Alternatively installing the mod boot.img allows primary to boot but after using DBP utilities to switch to data slot 1 (onscreen says success) the data slot 1 gets stuck on ZTE logo with 5 vibrates instead. Even tried flashing the final Beastmode 14.1 kernel DBP patched to data slot 1 after switched, five vibrates to recovery.
Lost Magisk install after step nine. Just reinstalling it is fine. Did you forget the flashable zip template by the way?
Click to expand...
Click to collapse
Oh hmm did you install the right version of Hellsgate for your data slot 1? I think LOS 14.1 needs a very old version(R2.1? I think). I'm not sure about beastmode kernel though, I'm sorry And thanks for the reminder about the zip template, o dear I forgot about it I'll upload it now!
haoyangw said:
Oh hmm did you install the right version of Hellsgate for your data slot 1? I think LOS 14.1 needs a very old version(R2.1? I think). I'm not sure about beastmode kernel though, I'm sorry And thanks for the reminder about the zip template, o dear I forgot about it I'll upload it now!
Click to expand...
Click to collapse
Sorry that post was worded poorly due to rushed recalling. I meant RR-O primary had Hellsgate kernel patched by this guide, which shouldn't be necessary as the two issue ROM files are still on root directory (patching with DBP instead didn't work as I posted before)? Still had to install the mod boot.img to manage to boot but then data slot 1 LOS14.1 won't boot. I was going to try patching with this guide the kernel I intend for LOS14.1 but it's lacking the image.gz-dtb file, I'd only patched it with DBP and that should be enough as it's an N ROM. I guess I could use an older hellsgate suited to N but Beastmode was updated til a little later so I'd prefer it.
Thanks for the zip template. Just checking, it's not actually needed if I can just install the modded boot.img directly in TWRP anyway?
Infy_AsiX said:
Sorry that post was worded poorly due to rushed recalling. I meant RR-O primary had Hellsgate kernel patched by this guide, which shouldn't be necessary as the two issue ROM files are still on root directory (patching with DBP instead didn't work as I posted before)? Still had to install the mod boot.img to manage to boot but then data slot 1 LOS14.1 won't boot. I was going to try patching with this guide the kernel I intend for LOS14.1 but it's lacking the image.gz-dtb file, I'd only patched it with DBP and that should be enough as it's an N ROM. I guess I could use an older hellsgate suited to N but Beastmode was updated til a little later so I'd prefer it.
Thanks for the zip template. Just checking, it's not actually needed if I can just install the modded boot.img directly in TWRP anyway?
Click to expand...
Click to collapse
Oh you're right, if the 2 files are still present you don't have to patch using this guide. Just checking, what version of hellsgate are you using for primary? And yes you're right! N ROMs/kernels don't have to be patched with this guide for DBP I'm not very sure why you can't boot and get the 5 led flashes though
As for your last question, you're right no need this zip in you install using TWRP.
haoyangw said:
Oh you're right, if the 2 files are still present you don't have to patch using this guide. Just checking, what version of hellsgate are you using for primary? And yes you're right! N ROMs/kernels don't have to be patched with this guide for DBP I'm not very sure why you can't boot and get the 5 led flashes though
As for your last question, you're right no need this zip in you install using TWRP.
Click to expand...
Click to collapse
The last B32+10 hellsgate v3.0. Dunno but the guide did manage to allow primary to boot whereas it wouldn't before. Both N hellsgate and beastmode are lacking the image.gz-dtb so I can't patch them. I guess I'll try stock next, I really wanted KCAL to use on Daydream tho ::crying:. If that fails I might try stock N as primary when I'm about to clean flash update O.
Infy_AsiX said:
The last B32+10 hellsgate v3.0. Dunno but the guide did manage to allow primary to boot whereas it wouldn't before. Both N hellsgate and beastmode are lacking the image.gz-dtb so I can't patch them. I guess I'll try stock next, I really wanted KCAL to use on Daydream tho ::crying:. If that fails I might try stock N as primary when I'm about to clean flash update O.
Click to expand...
Click to collapse
Oh dear I'm sorry to hear Just checking are you using LOS 14.1 builds from 2018? I might know what's wrong
haoyangw said:
Oh dear I'm sorry to hear Just checking are you using LOS 14.1 builds from 2018? I might know what's wrong
Click to expand...
Click to collapse
yeah latest official
Sent from my Xperia Z3C using XDA Labs
Infy_AsiX said:
yeah latest official
Click to expand...
Click to collapse
Oh I probably should add this in the OP, Nougat builds with 2018 Security patch level behaves the same way as Oreo ROMs, they also have the init.qcom.rc and fstab.qcom in /system. So I would believe that latest LOS 14.1 also needs the exact same patching method as Oreo(if you can check and confirm this that'll be great). I haven't analysed the Nougat hellsgate and beastmode kernels so I'm not sure how to patch them, I'll let you know asap when I find out something. Sorry about the mistake, I didn't realise there's still a Nougat ROM being regularly updated
Great thanks for the guide and mods. Sorry for the late follow up, it did take awhile to get working. After some confusion and trouble with figuring out how some O ROMs still don't use the early mount method. While N ROM and kernels don't in fact need patching by this guide. Also B12 can't be dual booted with any N ROMs due to bootstack incompatibility (flashing bootstack after a DBP install doesn't seem to take effect to help). My target kernel was Hellsgate 3 for B32+10, which oddly needed fstab.qcom modded per guide but not init.qcom.rc all despite the kernel being for non early mount ROMs. Yes really, after all of that figured out, I got it working!
I'm glad to report it works as intended with the right setup. Now with B12 ROMs currently all affected by the wired audio cpu extra 50% load bug, using B32+10 is a working fallback. The trade off being apparently dual-sim issues (reported by some as present, some not), no GCam HDR support and improper hi-res audio support (though hi-fi DAC was already working and hi-res is debatably useless). In any case if dual booting O with N is desired B32+10 is the latest supported available with above stated differences. This is the only way presently for using a stable-ish O ROM and N's fully functioning Daydream and a couple of AAA games deprecated after N such as Fahrenheit: Indigo Prophecy and Jade Empire. Now I can also play around testing Kranoner's N Vertex EAS supported ROM and kernel.
I've attached the B32+10 Hellsgate 3 modded per this guide using Kranoner's 180511 RR-O for anyone interested in getting it straight working without the mess. A few pointers. The zip still needs needs to be patched to primary/secondary/whatever chosen slot before use. Magisk has to be reinstalled after installing the modified kernel, primary Magisk zip does not need DB patching. Using secondary slot, to fill up like huge wasted space 6GB system partition is smart if you're not installing many apps.
Sent from my ZTE Axon 7 using XDA Labs
////[removed]////
Tried this with my device and it didn't work. Alcatel Tetra with 8.1 Stock. Runs GSI images up to 10. MT6739 SOC. Doesn't boot if you simply remove the entry. Couldn't even change ro to rw and have it boot. I was able to remove verify and that was about it. I was able to get the fstab and init file migrated back to ramdisk and it booted once i modified the init file to point to the right locations. I got DBP supporting my treble device properly. The last step is to figure out how to disable/remove the system early mount. This topic seems dead but I figure it's worth a try. I've been working on this Project on and off for 2+ months now and would really like to hit paydirt.
you do realize this is an Axon7 thread , yes?
mrrocketdog said:
you do realize this is an Axon7 thread , yes?
Click to expand...
Click to collapse
I'm Sure he's not lost .
U realize this is a place Dev's take ideas from each other and try to port it to other devices Right?
PHP:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
FEATURES
. The first, the one and the only custom vendor for dynamic partition in the world : I challenge you all to show me who did it before !
. If you find any custom rom with similar work since the first release of this one : it is just a copied and a stolen work [fake Google roms +++] !!!
. Compatible with all regions / basebands / firmwares / device variants
. Works with All AOSP/CAF based ROMs [10] & [11], Experimental, Official & Unofficial [TESTED]
. May works on fake Google roms but i don't take any responsibility
. Mount RO/RW available with no bootloop after reboot ! [Magisk/SU required]
. SafetyNet passed
. Full test passed : audio, ril, wifi, bt, fm radio, camera, sensors, fp scanner, nfc, ...
. All known hardware issues on custom roms are fixed : camera, wifi, bt, hdr playback, chrome ... and overheating !
. Custom Kernel with stock zImage [untouched +++]
IMPORTANT !
. NO firmware change is needed from the user side, so don't repeat this question many times ... just read up again !
. Formatting /data is required when you flash this vendor the first time +++
. Never go back to the previous versions due to the possible build.fingerprint change [Old releases are automatically removed] +++
. Dirty Update : always delete with file/root explorer or in TWRP this folder :
/data/property and reboot
You must delete these files & folders in /product partition from your custom rom
[File/Root explorer needed] :
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx
&
/product/vendor_overlay/29/etc/wifi
/product/vendor_overlay/29/overlay
& finally
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_huaxing_fhd_video_mode_dsi_panel.xml
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_tianma_fhd_video_mode_dsi_panel.xml
Already included in this vendor ... and since i'm the original author !
[ OPTIONAL ]
If you have the madness and the paranoia with security like Google, you can still relock /vendor again to the stock RO state ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.zip again !
How to [terminal or adb shell] :
su
tune2fs -O verity /dev/block/dm-1
*******
!!!
MIUI Users : sorry for you, but this is for custom ROMS " ONLY "
TROLLS & NOOBS, stay away ... Please !
!!!
Prerequisite:
POCO X3 NFC = surya
POCO X3 [no NFC] = karna
No matter where you live : india, china, russia, europe, usa or africa ... !
Kernel Source [Prebuilt] : Here
Created : 2021-02-27
Latest Update : 2021-03-21
DOWNLOAD
RESERVED for "Changelog"
Update : [2021-03-21] Highly Recommended !
- overlay folder [/vendor] : secure & total remove ... R.I.P forever !
You can now remove it from here too ... with no issue :
/product/vendor_overlay/29/overlay
[As always : no /data formatting is required if done in the previous builds !]
Update : [2021-03-20]
fix compatibility with all custom roms [10] & [11] +++ :
- build : preserve AVB structure [R/W still available in root mode]
- tune2fs : restore some stock feature flags [dir_index, huge_file, extra_isize]
- fstab [kernel & vendor] : small update
- vendor selinux : property_contexts fix
- build.prop : clean-up
Update : [2021-03-18]
clean-up & rework from scratch :
. all audio config [over 20 files +++]
. all media_codecs config
. new mixer_paths
[=> Exclusive]
- true resampling fix : r.i.p audio crackling and all audio issues in UX, Dialer, emulators ... etc [forever]
- improve audio & camera recording
- audio/video playback [Speaker, Headphones & BT] : Hi-Fi quality, loud & noiseless
[but first, you must delete these files with your File/Root Explorer:
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx]
Update : [2021-03-12]
- move to global 12.0.8.0 as firmware base [boot & vendor]
- ramdisk :
. disable mi_thermald and re-enable again thermal-engine
[on all custom roms : mi_thermald breaks the proximity sensor & suspend service in deepsleep => avoid hand wave gesture & AOD to work properly !]
. clean up & update
- vendor_selinux : add more camera permissions in property_contexts
- media_codecs : remove unused .xml
- ueventd.rc : rework from scratch
Update : [2021-03-07]
- ramdisk :
. update cpuset & schedtune settings
. improve memory multitasking
. make that "damn" fingerprint truly responsive
. enable UFS powersaving
. some clean-up & disable MIUI audio service
- media_profiles :
. rework from scratch
. add slow motion profile support : up to 1080p/120 fps & 720p/960 fps
. front video camera : add 4K support
- build.prop :
=> update parameters for : camera, ril, performance, playback ... and more
Update : [2021-03-05]
- rework from scratch : init.qcom.sh & init.qcom.post_boot.sh
- ramdisk : clean-up and add init.qcom.power.rc
. fix CPU instability : set 300 mHz as CPU minimum frequency for all cores / update schedutil governor parameters
. cpu_boost : improve touch responsiveness
. add built-in display power saving [for both huaxing & tianma panels]
- vendor permissions : rebuild from scratch / fix wronlgy settled paths (by Xiaomi) in some qti.xml
- camera : rework from scratch ISO/lowlight config
- remove dummy hbtp folder ... since there is no binary to load or device specific config
- targetconfig : update CoreCtlCpu to [0,6]
- build.prop : clean up and move NFC parameters to build_surya.prop
- [Bonus] : Wi-Fi signal improved (x2) !!!
. 2.4 Ghz : 144 => 300
. 5 GHz : 433 => 866
[but first, you must delete this folder, with your File/Root Explorer :
/product/vendor_overlay/29/etc/wifi ]
Update : [2021-03-01]
- update msm_irqbalance.conf
- update audio_effects.conf & remove audio_effects.xml
- universal vbmeta & vbmeta_system added
Update : [2021-02-27]
- initial release
- rework all build.prop (vendor & odm) from scratch
- debloated from unused MIUI folders, files & configs
- Kernel :
. enforcing selinux by default
. workqueue enabled in cmdline => better dynamic refresh rate handling by the CPU & stellar deep-sleep
. fstab reworked from scratch
the image you made is for enable rw or not?
my phone is poco x3 nfc surya
janhammer504 said:
To make things clear :
POCO X3 NFC = surya
POCO X3 (no NFC) = karna
No matter where you live (india, china, russia, europe, usa or africa) ... Choose the right vendor.img for your device !
[Both images were tested by me]
Click to expand...
Click to collapse
please share the surya image
aallii2 said:
please share the surya image
Click to expand...
Click to collapse
check the DOWNLOAD link up !
janhammer504 said:
check the DOWNLOAD link up !
Click to expand...
Click to collapse
tnx bro i'm downloading n i'll test
its not working after restart didnt boot n just go to recovry
aallii2 said:
its not working after restart didnt boot n just go to recovry
Click to expand...
Click to collapse
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!
janhammer504 said:
PREREQUISITE
- adb enabled (developer options)
- root (Magisk/SU)
- adb for Windows (Minimal ADB and Fastboot, provided)
- USB cable always connected
LIVE Flashing :
adb shell
su
dd if=/sdcard/vendor.img of=/dev/block/dm-1
View attachment 5232189
Reboot your phone right away ... then use your File/Root Explorer to test the mount RO/RW option and reboot again to check that there is no bootloop !
(Optional)
If you have the madness and the paranoia with security like Google, you can still re-enable AVB/Verity again ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.img again !
tune2fs -O verity /dev/block/dm-1
Check the full tutorial here to build your own custom vendor ... if you want !
DOWNLOAD
Click to expand...
Click to collapse
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
i use adb shell because terminal is too small for me, and for making tutorial.
the benefit ??? well there are a bunch of fixes to do in /vendor... check here for example
(the images i provided are clean with no modification, so i let developers or users doing their own modifications)
janhammer504 said:
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!
Click to expand...
Click to collapse
india 12.0.9
magisk 21.4
jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found
aallii2 said:
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found
Click to expand...
Click to collapse
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
now i cant install any rom :
updater process ended with error 7
pls help
aallii2 said:
now i cant install any rom :
updater process ended with error 7
pls help
Click to expand...
Click to collapse
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell
janhammer504 said:
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell
Click to expand...
Click to collapse
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !
aallii2 said:
india 12.0.9
magisk 21.4
Click to expand...
Click to collapse
wtf man, you should pick vendor.img from karna folder not surya !
janhammer504 said:
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !
Click to expand...
Click to collapse
i installed 12.0.7.0 global with magisk 22.0 then flashed vendor.img v12.0.7.0 but when restarted it stucked n i pressed power .phone boot but root explorer can't mount rw n just added shell in magisk
Hi there
I had some problems booting into Recovery and ERecovery. It would always stay endless in the Warning screen where it says that the Device is unlocked.
I run into it because of TWRP not Formating Data properly.
https://dl.twrp.me/anne/
twrp-3.5.1_9-0-anne.img14.6M 2021-03-13 15:27:54 ESTtwrp-3.5.0_9-0-anne.img13.2M 2020-12-27 21:03:29 EST
This Versions get stuck at:
Code:
Formatting Data using mkfs.f2fs...
Done
After it beeing stuck I could usually reach erecovery and wipe . But at one point it wouldn't work and I couldn't reacht the two and also couldn't stop the device from endless starting after shutting down.
I tried to flash several images from this one: https://androidhost.ru/1nfK
After flashing odm.img I could access the reflashed Stock Recovery and E-Recovery.
Update: Erasing Data with fastboot also works.
Note: It would show Google instead of Huawei at startup and in fastboot FRP:Unlocked doesn't show anymore after flashing odm.img
Else:To reach erecovery or twrp recovery I retried often to hold power and volume up when the device is turned off. It then vibrates two times when it works. I hat sometimes to try for 10 Minutes to reach one of the to.
I unlocked with PotatoNV. The phone can be opened quite comfortable with a straight package plastic like from a cabel or electric device and a hairdrier.
Update: I can actually not format Data with any of these TWRPs. This was working before flashing the odm or maybe an other image.
twrp-3.5.1_9-0-anne.img14.6M 2021-03-13 15:27:54 ESTtwrp-3.5.0_9-0-anne.img13.2M 2020-12-27 21:03:29 ESTtwrp-3.4.0-1-anne.img13.2M 2020-09-26 14:58:13 EDTtwrp-3.4.0-0-anne.img13.2M 2020-08-21 17:03:57 EDT
I could format with adb shell:
anne:/etc # mkfs.f2fs /dev/block/mmcblk0pXX
F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is enabled
Info: No support kernel version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 106086400 (51800 MB)
Info: zone aligned segment0 blkaddr: 512
Info: [/dev/block/mmcblk0p57] Discarding device
Info: Secure Discarded 0 MB
Info: Overprovision ratio = 0.880%
Info: Overprovision segments = 459 (GC reserved = 235)
Info: format successful
benaep said:
I can actually not format Data with any of these TWRPs.
Click to expand...
Click to collapse
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly NOT recommended do 'wipe data' runnig stock ROM , it may brick the phone).
Use recommended TWRP:
Recommended and tested TWRP Recovery
EMUI 8 Stock ROMs: 3.2.1-0 by pretoriano80 (with data decryption on Android 8 ) https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw EMUI 8 Custom ROMs: 3.2.1.0 by Catuva21...
forum.xda-developers.com
-Alf- said:
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly NOT recommended do 'wipe data' runnig stock ROM , it may brick the phone).
Use recommended TWRP:
Recommended and tested TWRP Recovery
EMUI 8 Stock ROMs: 3.2.1-0 by pretoriano80 (with data decryption on Android 8 ) https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw EMUI 8 Custom ROMs: 3.2.1.0 by Catuva21...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the direction Alf. So for the Newest Linage OS build that would be:
Pie Custom ROMs:
3.4.0-0-emui9_eR
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
right?
benaep said:
Thanks for the direction Alf. So for the Newest Linage OS build that would be:
Pie Custom ROMs:
3.4.0-0-emui9_eR
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
right?
Click to expand...
Click to collapse
If you want to flash LOS from TWRP (idk why, but it's your choice), use 3.2.1 by pretoriano80 (wiping etc.) After installing custom ROM, you can replace 3.2.1. with 3.4.0.0-emui9_eR.
-Alf- said:
If you want to flash LOS from TWRP (idk why, but it's your choice), use 3.2.1 by pretoriano80 (wiping etc.) After installing custom ROM, you can replace 3.2.1. with 3.4.0.0-emui9_eR.
Click to expand...
Click to collapse
Hi Alf
Thanks for the reply. Very gratefull for this. I'm trying since Weeks to get this running.
I just want a phone with minimal Google. I had /e/ but I didn't find a build and back in the days linage would be fine.
You think there is something which makes more sense?
benaep said:
I just want a phone with minimal Google
Click to expand...
Click to collapse
Then install "v" variant , e.g.
LOS 17.1-unoff.
https://sourceforge.net/projects/treblerom/files/LOSQ/2020.10.17/losq-v224-201017-arm64-bvN.img.xz/download
LOS 18.1-unoff.
https://sourceforge.net/projects/treblerom/files/LiR/2021.03.18/lir-v302-210318-arm64-bvZ.img.xz/download
and install opengapps - pico, nano, micro... , what suits you.
-Alf- said:
Then install "v" variant , e.g.
LOS 17.1-unoff.
https://sourceforge.net/projects/treblerom/files/LOSQ/2020.10.17/losq-v224-201017-arm64-bvN.img.xz/download
LOS 18.1-unoff.
https://sourceforge.net/projects/treblerom/files/LiR/2021.03.18/lir-v302-210318-arm64-bvZ.img.xz/download
and install opengapps - pico, nano, micro... , what suits you.
Click to expand...
Click to collapse
Yo Alf
Thanks for the Links to the Image files. I would never have found them myself. I tried now a few hours to make them run.
Formating and Wiping works with 3.2.1 by pretoriano80
I tried both images, but am not shure. I get an invalid zip file error when I copy it on the device. Sideload doesn't work. No connection or Success or Success 00.00 X.
I make it a zip on linux with --> unxz --> img2simg --> Create Zip Directory wit xarchiver.
I tried different combinations of this. First I forgot about simg and just made a zip out of the img.
Code:
/tmp/recovery.log: 1 f...57322 bytes in 0.010s)
~ >>> adb sideload /home/bni/Downloads/losq17.zip
adb: failed to read command: Success
~ >>> adb sideload /home/bni/Downloads/losq17.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
~ >>> adb pull /tmp/recovery.log /home/bni/Downloads/recovery.log
/tmp/recovery.log: 1 f...59228 bytes in 0.007s)
Code:
~ # twrp install /image/LOS17_SIMG.zip
Installing zip file '/image/LOS17_SIMG.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Invalid zip file format!
Error installing zip file '/image/LOS17_SIMG.zip'
Done processing script file
benaep said:
I get an invalid zip file error when I copy it on the device.
Click to expand...
Click to collapse
Of course, it is not a flashable .zip file.
You have to install it as image file, unpack .zip package, transfer exctracted .img file to the SD card. In TWRP go to Install , select Install image, choose lineage .img file , mark "system image" and flash.
If you need to do a factory reset , first replace TWRP with stock recovery and perform factory reset in recovery.
Or, flash Lineage.img in fastboot,without TWRP, wipes, errors etc. (make sure to have the stock recovery flash) - https://forum.xda-developers.com/t/losq-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543