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
Related
Intro-
This is the stock kernel for the T-Mobile SM-P607T Samsung Note 10.1 (2014 Edition) with the following additional features:
Multiple flavors for SELinux preference
CIFS kernel support
NFS kernel support
Force Fast Charge support
Download Options-
Enforcing ONLY - http://files.zpivot.com/sm-p607t/p607t-zstock-kernel-enforcing-only-1.2.37.tar.md5
SELinux stock behavior, always enforcing
Permissive OPTIONAL - http://files.zpivot.com/sm-p607t/p607t-zstock-kernel-permissive-optional-1.2.37.tar.md5
SELinux mode can be change with setenforce command
Permissive ONLY - http://files.zpivot.com/sm-p607t/p607t-zstock-kernel-permissive-only-1.2.37.tar.md5
SELinux always permissive
Install-
Reboot into download mode
Open ODIN
Add the kernel file downloaded from link above to AP section
Click start!
How to mount cifs/smb shares-
REQUIREMENTS:
root
busybox
ability to read and follow directions
custom kernel with cifs support (ie the kernel above)
INSTRUCTIONS:
Open a terminal emulator or adb shell
Code:
su
Code:
mkdir /mnt/shares/*share_name*
Code:
busybox mount -t cifs -o username=guest,unc=\\\\*server_ip*\\*share_name*,ip=*server_ip* *server_ip*/*share_name* /mnt/shares/*share_name*
NOTES:
Make sure you replace *server_ip* in the instructions above with the ip address of your server, and *share_name* with the name of your shared folder.
You must mount your shares outside of /storage and /mnt/sdcard for all applications to have access. I have provided a public tmpfs for creating mount points at /mnt/shares.
---Your samba share will now be accessible by all programs/apps under the /mnt/shares directory on root.
How to use Force Fast Charge-
DISPLAY FORCE FAST CHARGE INFO:
Open a terminal emulator or adb shell
Code:
cat /sys/kernel/fast_charge/info
ENABLE FORCE FAST CHARGE MODE:
Open a terminal emulator or adb shell
Code:
su
Code:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
SET CUSTOM FORCE FAST CHARGE LEVELS:
Open a terminal emulator or adb shell
Code:
su
Code:
echo 2 > /sys/kernel/fast_charge/force_fast_charge
Code:
echo 1000 > /sys/kernel/fast_charge/usb_charge_level
Code:
echo 2100 > /sys/kernel/fast_charge/ac_charge_level
NOTES:
Force Fast Charge will be disabled by default
When setting custom levels for usb and ac force fast charge, use one of the available values listed when using the display info command above (in the examples I used the max values)
Additional info:
Code:
/*
* Forced Fast Charge - SysFS interface :
* --------------------------------------
*
* /sys/kernel/fast_charge/force_fast_charge (rw)
*
* 0 - disabled (default)
* 1 - substitute AC to USB
* 2 - use custom mA configured through sysfs interface (see below)
*
* /sys/kernel/fast_charge/ac_charge_level (rw)
*
* rate at which to charge when on AC (1.0A/h to 2.1A/h)
*
* /sys/kernel/fast_charge/usb_charge_level (r/w)
*
* rate at which to charge when on USB (0.460A/h to 1.0A/h)
*
* /sys/kernel/fast_charge/wireless_charge_level (r/w)
*
* rate at which to charge when on WIRELESS (0.650A/h to 1.2A/h)
*
* /sys/kernel/fast_charge/failsafe (rw)
*
* 0 - disabled - allow anything up to 2.1A/h to be used as AC / USB custom current
* 1 - enabled - behaviour as described above (default)
*
* /sys/kernel/fast_charge/ac_levels (ro)
*
* display available levels for AC (for failsafe enabled mode)
*
* /sys/kernel/fast_charge/usb_levels (ro)
*
* display available levels for USB (for failsafe enabled mode)
*
* /sys/kernel/fast_charge/wireless_levels (ro)
*
* display available levels for WIRELESS (for failsafe enabled mode)
*
* /sys/kernel/fast_charge/version (ro)
*
* display fast charge version information
*
* /sys/kernel/fast_charge/info (ro)
*
* display complete fast charge configuration in human readable format
*
*/
Changelog
v1.0 - Initial release
v1.1 - Added Enforcing only version (build 21)
v1.2 - Added Force Fast Charge support (build 37)
Thanks/Credits-
mkasick - CIFS/NFS empty mount patch - http://forum.xda-developers.com/showthread.php?t=2106480
blue cat - permissive only patch - http://forum.xda-developers.com/galaxy-note-10-2014/development/kernel-stock-selinux-permissive-kernel-t3232814
chad0989 - force fast charge initial work - http://forum.xda-developers.com/galaxy-nexus/verizon-develop/kernel-patch-devs-force-ac-fast-charging-t1524020
faux123 - force fast charge extensions
yank555-lu - force fast charge note 3 port
Just a question - do you know how to add charging at different voltages? It drives me crazy that our tab can only charge at 1.8V, no more, no less.
Sent from my LG-H818 using Tapatalk
itsita said:
Just a question - do you know how to add charging at different voltages? It drives me crazy that our tab can only charge at 1.8V, no more, no less.
Sent from my LG-H818 using Tapatalk
Click to expand...
Click to collapse
I do not know how to adjust the voltage used for charging. Although you did give me an idea to implement the force fast charging kernel mod. I am currently building a test release with the added patches... let the experiments begin!!!
Updated OP
Okay, I have updated the OP and added a new version with the force fast charge mod in place. I have only done minor testing to make sure the code was functional. I would suggest that you perform your own testing as your mileage may vary depending on the charging equipment you are using.
oneleft.ak said:
Okay, I have updated the OP and added a new version with the force fast charge mod in place. I have only done minor testing to make sure the code was functional. I would suggest that you perform your own testing as your mileage may vary depending on the charging equipment you are using.
Click to expand...
Click to collapse
Thanks! Ill test and post results
Sent from my SM-P605 using Tapatalk
I am getting "md5 error! invalid binary " while adding the kernel file through odin..
plz guide
i have 607T with 5.1.1
tabi304 said:
I am getting "md5 error! invalid binary " while adding the kernel file through odin..
plz guide
i have 607T with 5.1.1
Click to expand...
Click to collapse
This will happen when you change the filename before attempting to flash or if the download completed with errors. Make sure you are trying to flash the file from one of the download links in the OP.
oneleft.ak said:
This will happen when you change the filename before attempting to flash or if the download completed with errors. Make sure you are trying to flash the file from one of the download links in the OP.
Click to expand...
Click to collapse
hmm i'm getting the invalid binary message as well,
tried different odins and different files (didn't change the name or anything..)
I also tried different odin versions but no success
File server error
tabi304 said:
I also tried different odin versions but no success
Click to expand...
Click to collapse
I see what you mean, it appears my file server is altering the file size upon upload.... I am looking into it right now- Will update this thread once it has been corrected.
UPDATE:
Okay, turns out it was the ftp program(FileZilla) I was using to upload the files to my file server. The files have been restored correctly and I have personally tested all three of the links by downloading from my file server and flashing in ODIN.
Thanks for the heads up guys and please let me know if you run into any further issues--
itsita said:
hmm i'm getting the invalid binary message as well,
tried different odins and different files (didn't change the name or anything..)
Click to expand...
Click to collapse
Maybe now you can finally get the chance to test the force fast charge options!!!
Is this kernel valid for P605 too? Surely not, but just asking....
How do you root the P607T? Also, whats the difference (in laymens terms) between the 3 versions?
Worked well thank you
Set my levels to this - hopefully it speeds up the charge a little
Fast charge mode : 2 - Use custom mA on AC and USB
Custom AC level : 2100mA/h
Custom USB level : 1000mA/h
Custom Wireless level : 650mA/h
Failsafe mode : 1 - Failsafe active (default)
Valid AC levels : 1000 1100 1200 1300 1400 1500 1600 1700 1800 1900 2000 2100
Valid USB levels : 460 500 600 700 800 900 1000
Valid Wireless levels : 650 800 900 1000 1100 1200
I flashed the kernel from here, and followed the steps, when i go to check /sys/kernel/fast_charge/info to see if it worked, all i get is permission denied.
no matter what kernel ive used in the past on this tablet ive gotten "permission denied" like trying to set up linux deploy or linux on android. I am rooted, I am using a Permissive kernel, Busy Box installed. So what gives?
Can this be used in P605 ? TY !!
Istarth said:
Can this be used in P605 ? TY !!
Click to expand...
Click to collapse
Yes. It was also the kernel inside Pyrana v27.
zombie thread warning*
So as i understand it, you can use kernels for older roms on newer releases right?
So for example, im trying out an unofficial lineage os rom, and it does not have fast charge support baked in, nothing through kernel auditor or 3c toolbox that can be changed. Could I flash this kernel and add support to the rom that way? The dinosaur charging speeds on this thing is really inconvenient if I ever forget to charge it overnight.
Please, links down.
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?
Returning to oreo GUIDE
We are going to speak about Returning to oreo for Samsung J4 PLUS .
Requirements
- Any archive decompress tool .
WINDOWS : Winrar & 7zip .
LINUX : U can use shell or any archive decompress tool .
ANDROID : Zarchiver .
- Custom recovery .
- LZ4 Tool .
WINDOWS : Here .
LINUX : Package name is liblz4-tool .
ANDROID : Use termux app , pkg update ; pkg install lz4 .
- Oreo stock rom .
Code:
U CAN'T FIND IT FREE ON MOST SITES OR IT WAS DELETED FROM OTHER SITES .
BUT I FOUND THIS SITE PROVIDES STOCK ROM FOR FREE AND WITHOUT SIGN IN , BUT DOWNLOADING SPEED IS SLOW :
[URL="https://samfrew.com/"][COLOR="Red"]SITE LINK[/COLOR][/URL] .
- Patience .
Lets start steps
A - Preparing . . .
Download oreo stock rom .
Unzip stock rom zip .
Rename AP ( tar.md5 to tar ) .
Decompress AP ( system - boot - vendor) & CSC ( odm only ) tar files in a dir (eg work) . ( WINDOWS : 7ZIP )
Decompress lz4.zip in previous dir ( WINDOWS ONLY)
Open cmd ( WINDOWS ) or console ( LINUX ) or termux ( ANDROID , but if u face issue try to move files to termux home dir using com.android.documentsui app , it is in any android system ) in previous dir .
Open as root or administrator write this :
Code:
- lz4 -d system.img.ext4.lz4 --no-sparse . ( [COLOR="red"]WINDOWS : lz4.exe [/COLOR])
Then delete system lz4 compressed file .
- lz4 -d -m *.lz4
Then delete all lz4 compressed file .
Rename all img.ext4 to img .
Copy all ( system - vendor - boot - odm ) img to your phone .
B - Installing . . .
- Reboot recovery
- Wipe data , system , vendor .
- From custom recovery teriminal or adb shell , go to img saved location ( using cd command ) :
Code:
- simg2img odm.img odm.raw
- dd if=odm.raw of=/dev/block/bootdevice/by-name/odm
- Install system .
Notice : With twrp , Better to reboot recovery .
- Install boot , vendor .
- Install custom kernel . (if u want)
- Install security disable stuff :
J6+ J4+ disable encryption : here .
Disable all pie security : here .
- Install magisk .
C - Waiting until it boot . . .
- Done phone booted . :good:
Thanks
• @ashyx for Twrp & J6+ J4+ disable encryption .
• @SebaUbuntu for custom recoveries .
• me for writing this thread .
• @topjohnwu for magisk .
Indonesia region try this mirror https://drive.google.com/file/d/1lGxg2R5HJiBRWvNy1uMBKd-RJ56u49Gt/view
Credit nanda.id
Can I lock the bootloader after this?
btw thanks so much for this guide, I've always wanted to downgrade...
this phone has been flashed with unauthorized software, meh.
If you're running Pie, stay there and be happy.
blackhawk said:
If you're running Pie, stay there and be happy.
Click to expand...
Click to collapse
my touchscreen didn't work after updating to the latest one
How to fix this phone has been flashed with unauthorized software
i have not working face and fingerprint unlock..
nick D1256 said:
i have not working face and fingerprint unlock..
Click to expand...
Click to collapse
i cant register it
zawarud0 said:
this phone has been flashed with unauthorized software, meh.
Click to expand...
Click to collapse
Install medusa Kernel
Hello. I have J6+ and followed all the steps carefully but I have the problem of
"your device has been flashed with unauthorized firmware and is locked"
what can I do? I really want an Android 8 or 8.1 custom ROM
PREREQUISITE
- adb enabled [developer options]
- root [Magisk/SU]
- original /vendor partition [flashed with official update/firmware]
- File/Root Explorer
- adb for Windows [Minimal ADB and Fastboot, provided]
- UKA [Unpacker Kitchen for Android] - Send me a PM
- USB cable always connected
Reserved
You can do the same steps for the other logical partitions [system & product]
At the end you do :
System
tune2fs -L / /data/local/UnpackerSystem/system.new.img
tune2fs -O ^read-only /data/local/UnpackerSystem/system.new.img
tune2fs -O ^has_journal /data/local/UnpackerSystem/system.new.img
adb shell
su
dd if=/sdcard/system.img of=/dev/block/dm-2
(just copy/past to avoid errors !)
Reboot your phone right away !
Product
must be renamed vendor because the Magisk Module still doesn't support this name yet ... just rename it vendor.img before taking any action ... and after creating your image, do :
tune2fs -L product /data/local/UnpackerSystem/vendor.new.img
tune2fs -O ^read-only /data/local/UnpackerSystem/vendor.new.img
tune2fs -O ^has_journal /data/local/UnpackerSystem/vendor.new.img
NOW you can rename it product.img
adb shell
su
dd if=/sdcard/product.img of=/dev/block/dm-0
Reboot your phone right away !
"Houston, we have problem!"
Now what? Is this only for MIUI users? I have flashed Nusantara ROM right now...
Also it is possible, that you can create "default" RW images for surya, upload them somewhere on cloud (one RW system please! medium rare, thank you ... 12.0.7 is fine for me...)
... but anyway, thanks for your hard work...
BTW @brigudav already created flashable RW vendor for Surya, can that be done also for system?
jeryll said:
"Houston, we have problem!"
View attachment 5232079
Now what? Is this only for MIUI users? I have flashed Nusantara ROM right now...
Also it is possible, that you can create "default" RW images for surya, upload them somewhere on cloud (one RW system please! medium rare, thank you ... 12.0.7 is fine for me...)
... but anyway, thanks for your hard work...
BTW @brigudav already created flashable RW vendor for Surya, can that be done also for system?
Click to expand...
Click to collapse
Check your Mount Namespace Mode in Magisk Manager
No it's not only for miui, it's for all roms ! (btw i'm on LOS 17.1 ... and i never used MIUI)
Yes, you can do that for the 3 logical partitions ... this tutorial is for all devices with dynamic paritition aka super.img (not limited to poco x3 nfc !!!)
I will put a clean vendor.img later (with RW enabled and AVB-Verity Disabled)
I will put a modded version of Magisk 20.4 too if someone would use it (like me)
janhammer504 said:
Check your Mount Namespace Mode in Magisk Manager
No it's not only for miui, it's for all roms ! (btw i'm on LOS 17.1 ... and i never used MIUI)
Click to expand...
Click to collapse
- thanks for the answer, but I must say I'm unable to continue, because I'm unable to install UKA module on A11 ROM
- regardless of Mount Namespace Mode - I checked all three - with reboot - result is the same
- I'm also unable to install magisk 20.4 on A11 ROM - and with v21.0 or higher - UKA will not install
- so Id say this guide is for now useable only for A10 users
- I will test A10 ROM in a few days
- maybe there is a problem with my phone, but I reflashed full recovery version of latest MIUI before flashing custom rom together with encryption disabler, so my super partition should be cleaned up
- so using unencrypted storage could be another problem for this to work?
jeryll said:
- thanks for the answer, but I must say I'm unable to continue, because I'm unable to install UKA module on A11 ROM
- regardless of Mount Namespace Mode - I checked all three - with reboot - result is the same
- I'm also unable to install magisk 20.4 on A11 ROM - and with v21.0 or higher - UKA will not install
- so Id say this guide is for now useable only for A10 users
- I will test A10 ROM in a few days
- maybe there is a problem with my phone, but I reflashed full recovery version of latest MIUI before flashing custom rom together with encryption disabler, so my super partition should be cleaned up
- so using unencrypted storage could be another problem for this to work?
Click to expand...
Click to collapse
Hi, flash an official MIUI for your device.
Do the dirty job and save your vendor.img
Reflash your rom !
(i have already uploaded a clean vendor.img here)
I close this thread too since a lot of features have been added to this work ... and since there are many disrespectful developers-like around who steal my work and give no credit !
Check my custom vendor thread to learn more about this work !
If you have any question, send me a PM, i will check first if you are not a troll : if you get no answer from me, then understand by yourself !
@janhammer504 Hi. For the sake of the community it's always sad to see someone taking their work from XDA.
If you've got issues with other people using your work without credit here on XDA you can always reach out to someone on the moderator team for help. Or better yet, one of us on the Developer Relations team. We can help you solve any disputes and make sure you get proper credit.
You can find a list of moderators here:
https://docs.google.com/document/d/1lK5rP103OL3StU3q9iqwX9LU_k8XABeSQIAT3EHCqgM/pub
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Bugs:
- you tell me
G9 Play - Ilitek (Work)
G9 Play - Himax (Dead)
G9 Play - Goodix, Chipone (untested)
G9 Power - Novatek (Work)
G9 Power - Focaltech (Untested)
E7 Plus - goodix,himax,chipone (Untested)
Install guide (Might not work):
To flash:
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity flash vbmeta_a vbmeta.img
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
To boot:
Code:
fastboot boot twrpname.img
Download:
GUAMP: MEGA
CEBU: MEGA
GUAM: soon
Reccomended ADB and Fastboot binaries:
platform-tools
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/100Daisy/android_device_motorola_guamp
Kernel source: prebuilt (for now)
Join our device chat in Telegram !
no link xda will remove anyways
gitdaisy applause circle:
https://t.me/GitDaisyShitposting
Donations:
paypal.me/100Daisy
Credits:
I want to say a big thanks to the testers @borraz
Hi! not work touchscreen in HImax.
condor323 said:
Hi! not work touchscreen in HImax.
Click to expand...
Click to collapse
contact me on Telegram @GitDaisy
Congratulations on your work. @GitDaisy this is the most complete TWRP for guamp I have used so far.
I have a Chipone touchscreen and your ROM titled twrp-3.5.2_10-guamp-270420211220... did not work for me.
However, I managed to get it to work by adding the following lines to the /system/bin/load-modules.sh:
Code:
#!/system/bin/sh
# two new lines
firmware_path=/vendor/firmware/ICNL9911.bin
flash_path=/sys/chipone-tddi/cts_firmware
insmod /vendor/lib/modules/chipone_tddi_mmi.ko
...
# wait extra time just in case
wait 3
# new line
echo $firmware_path > $flash_path/update_from_file
# wait extra time just in case. Not sure if necessary
wait 3
...
exit 0
It is a step I saw in another 'load modules' shell script that updates the firmware by updating the sysfs update_from_file chipone entry
I hope it helps other owners of this fabulous Moto G9 Play phone
jarchig said:
Congratulations on your work. @GitDaisy this is the most complete TWRP for guamp I have used so far.
I have a Chipone touchscreen and your ROM titled twrp-3.5.2_10-guamp-270420211220... did not work for me.
However, I managed to get it to work by adding the following lines to the /system/bin/load-modules.sh:
Code:
#!/system/bin/sh
# two new lines
firmware_path=/vendor/firmware/ICNL9911.bin
flash_path=/sys/chipone-tddi/cts_firmware
insmod /vendor/lib/modules/chipone_tddi_mmi.ko
...
# wait extra time just in case
wait 3
# new line
echo $firmware_path > $flash_path/update_from_file
# wait extra time just in case. Not sure if necessary
wait 3
...
exit 0
It is a step I saw in another 'load modules' shell script that updates the firmware by updating the sysfs update_from_file chipone entry
I hope it helps other owners of this fabulous Moto G9 Play phone
Click to expand...
Click to collapse
I will cover that issue in next release, then i will focus on bringing one image for all bengal devices released with A10 (G30 has vendor_boot and dt seems to not be compatible and kernel may be not compatible too)
currently i need to ship different prebuilts for all devices
Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...
Mauricio Oliveira said:
Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...
Click to expand...
Click to collapse
@Mauricio Oliveira , you have the correct smartphone model (guamp). It is the same as mine.
However, there are several touchscreen variants and your application (cpu-z) does not show which variant you have.
Can you install the 'Device Info HW' application? Your touchscreen will show in the 'General' tab.
Mauricio Oliveira said:
Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...
Click to expand...
Click to collapse
Another way to find out your touchscreen manufacturer is by connecting to your mobile using the ‘adb shell’ command.
From your desktop, run:
Code:
adb shell
and then
Code:
getevent
the command will show output like the following:
Code:
guamp:/ # getevent
add device 1: /dev/input/event2
name: "chipone-tddi"
add device 2: /dev/input/event0
name: "qpnp_pon"
add device 3: /dev/input/event1
name: "gpio-keys"
In this case, ‘chipone-tddi’ is the touchscreen manufacturer.
ok, obrigado pelo feedback .
Hello everyone on the forum... Thanks again my friend jarchig. I noticed that my screen variant is the same as yours... Read in your posts that you have successfully added commands to enable it. Could you teach step by step how to do this?
Thank you in advance.
I have a guamp device and I want to install this recovery.
Where can I find the vbmeta.img file for the device? It seems that the MEGA link only have twrp-3.5.2_10-guamp-270420211220-unofficial.img image.
It is possible to install AOSP, or image from https://mirrors.lolinet.com/firmware/moto/guamp/official/ right now? It seems do not exist LineageOS or other roms yet for this device.
did twrp work for anyone?
piperoman said:
I have a guamp device and I want to install this recovery.
Where can I find the vbmeta.img file for the device? It seems that the MEGA link only have twrp-3.5.2_10-guamp-270420211220-unofficial.img image.
It is possible to install AOSP, or image from https://mirrors.lolinet.com/firmware/moto/guamp/official/ right now? It seems do not exist LineageOS or other roms yet for this device.
Click to expand...
Click to collapse
I see that nobody respond to you...
I use the image from the link that you share, specifically RETLA. You must download the zip file, decompress it and you can see the vbmeta.img file
GitDaisy said:
contact me on Telegram @GitDaisy
Click to expand...
Click to collapse
it doesn't work for me too, the himax touchscreen ,guamp version, can you help me?
If the android version is 11 how does it work? mine has android 11 sorry i think there is no solution for me