Related
I've installed MultiROM on my Nexus 5 device and i've had it for a while and never had a problem with it. Until now. I decided to wanted to have my OmniROM in place of CM11 and I accidentally copied the secondary to primary slot in TWRP. Now whenever I try to boot up into CM11, it gives me the error code "Kexec-hardboot support required to boot this ROM. Use kernel with kexec-hardboot support." I have no idea what this mean and I'd really like for it to get fixed asap. If you can help, please do asap. Thanks in advance!
Doctor Ogg said:
I've installed MultiROM on my Nexus 5 device and i've had it for a while and never had a problem with it. Until now. I decided to wanted to have my OmniROM in place of CM11 and I accidentally copied the secondary to primary slot in TWRP. Now whenever I try to boot up into CM11, it gives me the error code "Kexec-hardboot support required to boot this ROM. Use kernel with kexec-hardboot support." I have no idea what this mean and I'd really like for it to get fixed asap. If you can help, please do asap. Thanks in advance!
Click to expand...
Click to collapse
I know it's been a while, but for anybody who may need this...
What happens is that MultiROM needs the primary ROM to have a kernel patched with kexec to work its magic. Most stock and quite a few custom ROM kernels don't have it, so it needs to be installed.
Fortunately, the MultiROM application (available here as an apk or in the Play Store) is here to automate all this. Your device must be rooted for it to work, but if you've already used it once I guess you know how to do it again (note OmniROM isn't rooted by default).
If anything, please refer to MultiROM original post. Most of its workings are explained there. To quote it:
Tasssadar said:
Installation
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
Click to expand...
Click to collapse
Cheers
Multiboot for Sony Xperia Z1 Compact
How its look -> http://i58.tinypic.com/35346bt.png
How to install boot menu
download bootmenu_amami.rar, extract folder "bootmenu" to the your internal storage
put boot.img or kernel.elf to the mainrom folder, make sure thats the same kernel like your primary rom (aka main rom)
download bootmenu.img from attachment, flash bootmenu.img using fastboot commnd: fastboot flash boot bootmenu.img
Click to expand...
Click to collapse
Since your bootmenu folder no contain settings.ini (you runing bootmenu at a first time), settings.ini will be created easily. You need to complete main step aka main rom creation:
(mainrom creation)
reboot into bootmenu, chose "patch rom package", navigate to the bootmenu folder on your internal storage, navigate to the mainrom folder, select mainrom.zip package (make sure boot.img or kernel.elf is the same like your current main rom kernel, and make sure boot.img is in folder mainrom), select mainrom.zip and click "yes". Main rom will be added into boot menu entry. Now reboot again into boot menu and you will see new menuentry, chose these menu to boot into your primary rom!
(other roms creation - you can do only if you completed main rom step)
reboot into bootmenu, chose "patch rom package", principe is a bit diferent than main rom step (we have 3 steps):
(step 1): make sure seccond rom package is on your external storage ...see this post -> http://forum.xda-developers.com/showpost.php?p=52830021&postcount=45
(step 2): chose rom zip you want to patch, patch them
(step 3): reboot again into boot menu (new rom entry will be displayed), select these rom to boot, on led blinking press to boot into cwm, now you are in cwm of these rom, now navigate to the same folder where is your package, you will find zip with appended name "patched.zip", chose these patched zip to install trought these recovery, you are done!
Click to expand...
Click to collapse
WARNING:
there is possibility for your partitions of the main rom to get overwriten if multiboot.sh fail to patch these rom you going to patch, just to let you know! Two click solution is in testing stage so there is probably a lot of bugs! I am not responsible if you lost your private data! So guys if you willing to help, I am waiting. Things need to be improved in multiboot.sh !
Click to expand...
Click to collapse
Source code of the my bootmenu project
https://github.com/munjeni/bootmenu_z1_and_z1c
Public License for BOOTMENU and for my Auxiliary Work
You can Distribute my source without my Permissions. Distribution should include my XDA name 'munjeni' and Link to this 'BOOTMENU' thread in your Credits sections/About sections and Properly Visible to Human Eyes. If you use our source and have them modified, you need to make them public to everyone!!! If you not propertly use my source and you not give proper credit, and you not share your modified source code which is based on my source code, I will find you and I will report your post!
Click to expand...
Click to collapse
No doubt, I'm really interested in multi boot,
I have tried it on my XU and it was awesome:laugh:
munjeni said:
Hallo, just to reserve our thread for something that you will like for sure! I have plan to port my old project to our device, more info you can see here -> http://www.xda-developers.com/android/xperia-boot-menu-ported-to-the-xperia-p-in-preview-form/
First thing - I will port them, thats for sure! Next thing - will try to integrate all things into boot menu (look into tutorial thread to see how it working) to make all things easy to all as possible, first of all I need to get more free time! Soon when I get one free day I will give you beta version! By now whant to see your opinions! Do you have interest in multiboot??? Let me know first!
Click to expand...
Click to collapse
I'm flashoholic,like to test everything, multiboot sounds nice
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
Would this for example allow to have stock and cm11 both installed and easily switch between those 2? If yes then im totally up for it
Sounds definitely awesome!
Progress... Boot menu beta done, having problem with kexec, seems kexec not working. Will try with stock kernel since cm kernel probably have no working kexec.
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
munjeni said:
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
Click to expand...
Click to collapse
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
XperienceD said:
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
Click to expand...
Click to collapse
I'm sorry but I do not know what you're talking about! Plese be more clear!
munjeni said:
What? Plese be more clear
Click to expand...
Click to collapse
tap2wake
CABL
XperienceD said:
tap2wake
CABL
Click to expand...
Click to collapse
Sorry mate but our thread is related to the multiboot and not to the kernel things, you can open a new thread for your problem, sorry!
munjeni said:
Sorry mate but our thread is related to the multiboot and not to the kernel things
Click to expand...
Click to collapse
Oh, given that a boot.img is actually a kernel I thought it might be something you could implement whilst working on it.
munjeni said:
you can open a new thread for your problem, sorry!
Click to expand...
Click to collapse
They're not problems they are suggestions.
New version is out!
Changelog:
- all isues with kexeced kernel solved (missed modile data, wifi, bluetooth...etc)
- black theme
Enjoy!
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
munjeni said:
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
Click to expand...
Click to collapse
I'm planing on trying tomorrow, I'll try and give some feedback
Solved! Will give you soon cm11 in multiboot!
munjeni said:
Solved! Will give you soon cm11 in multiboot!
Click to expand...
Click to collapse
Well then I shall wait until you do so Thank you for your effort:fingers-crossed:
Done and CM11 is booted sucesfully from sdcard By now have only one problem which I have experienced last year on my multiboot for Xperia Go, I have solved them on Xperia Go but unable to find a thread how I got fixed them solved, problem now on Z1C is these seccondary rom runing from sdcard is very slow like was a year ago on Xperia Go, if some one found my post where I have fixed that please give me a link. I don't know if there is something related to the tune2fs parameters since I forgot how I got them fixed. Every idea is welcome!
Maybe this
http://forum.xda-developers.com/showpost.php?p=44945343&postcount=24
http://forum.xda-developers.com/showpost.php?p=44969886&postcount=36
http://forum.xda-developers.com/showpost.php?p=44979190&postcount=47
Yes seems 3.th post related to tune2fs and journal_data_writeback to cache and data giving better performance. Stil noticed some lags, probably because my 8gb old sdcard is so slow Will try to boot from internal storage, maybe it will give better performance or at least maybe an 64gb class 10 sdcard can solve lag problems? What you think guys?
This mod for CM11 on moto_msm8960 brings back the classic sdcard mount we know from devices like the Nexus One.
No more cluttering of /data with files which should go to sdcard.
Features:
- External sdcard mounted as /sdcard
- Internal memory fully available for /data
Installation:
- Have a nandroid backup of /boot and /system at hand if something goes wrong
- Simply flash the zip over your existing CM11 installation
- Wipe data is not necessary but will help if you have problems.
Deleting only the data of the concerned apps should be sufficient. (Only apps storing data on sdcard are effected)
- Files which were on the emulated sdcard can be found at /data/media/0. This is also the location where you have to put your zip files to be able to flash them with OpenRecovery.
Method:
Adjusting of following CM11 files to be in line with Nexus One example configuration according to:
http://source.android.com/devices/tech/storage/config-example.html
boot.img
- init.qcom.rc
- fstab.qcom
framework-res.apk
- storage_list.xml
See my github for details: https://github.com/S-I-M-O-N/android_device_motorola_moto_msm8960
Disclaimer:
This was developed and tested on a Photon Q but should work on all moto_msm8960 devices with CM11.
I cannot be held responsible if anything goes wrong while using this mod.
Thank you to everyone this work is based on: Cyanogenmod team for providing CM11, Google for providing Android and everybody else
Download
I will try to keep this thread updated and provide a flashable zip for the latest CM11 snapshot.
See attachment at the bottom.
Regards,
Simon
Downloads for:
cm-11-20140609-SNAPSHOT-M7-moto_msm8960.zip
cm-11-20140708-SNAPSHOT-M8-moto_msm8960.zip
cm-11-20140916-SNAPSHOT-M10-moto_msm8960_jbbl.zip cm-11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl.zip
cm-11-20141112-SNAPSHOT-M12-moto_msm8960_jbbl.zip
Cool, Thank you
Any updated version for CM11 M8 build?
I am downloading M8 right now. Expect an update within the next days.
Until then it should be relative safe to flash the M7 sd-mod over CM11 M8, you will just miss the updates concerning the kernel and framework.
EDIT: Well, it's not. Stuck in Boot. Stay tuned for an update.
S-I-M-O-N said:
I am downloading M8 right now. Expect an update within the next days.
Until then it should be relative safe to flash the M7 sd-mod over CM11 M8, you will just miss the updates concerning the kernel and framework.
EDIT: Well, it's not. Stuck in Boot. Stay tuned for an update.
Click to expand...
Click to collapse
Yeah..I've tried it over M8 and my phone stucked in bootloop. Thanks for your work. I've missed my sdcard as primary storage since JellyBean days. I'm glad I can use my 32gb sdcard usefully.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Download for M8 added.
S-I-M-O-N said:
Download for M8 added.
Click to expand...
Click to collapse
Thanks a lot..Downloading it now.
Hmm so I'm guessing the likelihood of this working on nightly builds isn't good?
You could give it a try.
Nandroid backup boot and system, then flash the mod.
If it screws up, just go back and restore boot and system.
Apart of that I think we should wait a few days to see if we get a moto_msm8960_jbbl M9 build. If yes I will, make the patch for it. If no, I will pick the latest nightly.
After reading that we won't get a M9 build I made an update for nightly 20140814.
It seems the ramdisk is growing and abootimg was already complaining that it was too large. I had to delete copyrights and disclaimers to squeeze out some bytes. I hope that this trend does not continue, otherwise I need to find other means to bild the boot.img.
Regards
Simon
Please...!
A new version.
The M10 CM is out now for the Photon Q!
S-I-M-O-N said:
After reading that we won't get a M9 build I made an update for nightly 20140814.
It seems the ramdisk is growing and abootimg was already complaining that it was too large. I had to delete copyrights and disclaimers to squeeze out some bytes. I hope that this trend does not continue, otherwise I need to find other means to bild the boot.img.
Regards
Simon
Click to expand...
Click to collapse
Download for M10 added. Have fun!
Download for M11 added. Enjoy!
Are there any issues with this mod when flashing a new ROM? Say you're going from a snapshot build to a newer snapshot build, or even from a snapshot build to to a stable build?
Flashing a new ROM will overwrite the mod. So you are using the emulated sdcard on internal memory. Apps which stored data on the sdcard will not find their data, just like when you install the mod the first time.
Nevertheless if you stick to CM11 snapshots for which the mod has been adapted and you flash another release, just flash the mod for this release while you are still in recovery and you will have no problems.
Made the mistake of installing a nightly restored my backup. But can't get the classic sdcard back. Have re flashed no joy. Is there a way to get it back, with out doing a clean install?
Did you create the backup including the mod?
Did you restore system and boot?
Did you try to just flash CM11 M11 + MOD for M11?
Do you have bootloops?
YDid you create the backup including the mod?
No
Did you restore system and boot?
Not sure about the boot, will check.
Restored backup m11 and flashed sddcard mod.zip.
Do you have bootloops?
No
Might be a mute point.
The restore is eating my battery!
Doing a clean m10 updating to m11 Now.
Will install sdcard mod and see how it goes.
Thanks.
I should know here in the next 15 min.
OK!
With out flashing sdcard mod after m11 installed I now have
4 gig.
My guess is my back up was not m11 or JB bootloader?
Thanks for the fast reply!
The PQ has no KK bootloader, so every (working) ROM for the PQ is based on the JB bootloader.
As long as you haven't modified your /system after updating to M11 and flashing gapps and sdcard_mod, you should be fine by just do the same again.
But it's always risky, from a nightly to a snapshot. Downgrades are also risky and might not work.
You might just wait until M12 comes out and use your backup to restore it.
M12 is here
New member, had to post it in this section.
This is a test version of MultiROM.
WARNING
It is DANGEROUS to flash MultiROM to your device. It can cause data loss. If you have important files on your phone, NEVER try to do that.
Introduction
MultiROM is a boot manager that allows you to flash multiple roms into the device.
This port for Polaris is based on Tasssadar's work and Vasishath's modification. It seems to work fine now.
You can refer to Vasishath's original post for installation guide.
Reference Links:
[XDA Thread] https://forum.xda-developers.com/poco-f1/development/multirommiui-custom-roms-gsi-t3868734
[Github][MultiROM] https://github.com/ARTI5T/multirom
[Github][Modified-TWRP] https://github.com/ARTI5T/android_bootable_recovery
Download link is below.
Notes:
* You can use MultiROM only with decrypted devices.
* Flash a patch to disable force encryption after flash a ROM with force encryption.
* Don't manually encrypt your data in any ROMs.
* If you want to flash treble GSI, choose A-only images.
** Flashing A/B GSI is theoretically possible if you flash it to a secondary ROM which supports system-as-root. (NOT TESTED)
* Unfortunately, until now, we cannot update a secondary ROM with treble GSI. Now you can update a secondary ROM with system.img.
* Always backup your file before flashing. Especially boot.img or boot partition.
* Be careful with your lockscreen password. You can only set password in either primary ROM or secondary ROMs. Refer to vasishath's thread for more details.
* Not all ROMs are compatible with MultiROM.
* Android 10 can be flashed as a primary ROM. If you have an android 10 ROM as primary, you need an android 9 boot.img and vendor.img in case you have GSIs based on android 9.
Known issue:
* Sometimes touch in TWRP or MultiROM boot screen doesn't work. If you are in TWRP, just reboot. If you are in boot screen, you can also reboot or use volumn +/- instead.
* If you want to uninstall MultiROM, you may need to flash the stock boot.img (In case it can't boot). So please backup your boot.img before flashing.
* Still some bugs with system/vendor compatibility verification. If you meet such errors, please flash a "base firmware" (e.g., MIUI) first, and then flash your zip in "List ROMs".
* In some rare cases, flashing a zip in secondary ROMs may cause primary ROM damage.
This port is only for DECRYPTED device. Don't flash if your device is encrypted.
Please BACKUP before you flash MultiROM.
We're not responsible for any loss caused by this modification.
Download link:
[Google Drive] https://drive.google.com/drive/folders/1C2d3GQT5WVsw83XU6J5qA_oJOYMxyXNX?usp=sharing
Update Log:
28-01-20: Support Android 10 as secondary ROMs. Fix bugs which in some cases cause error 7 when flashing.
17-08-19: Add "Install system.img/vendor.img" in "List ROMs".
16-08-19: Add "skip compatibility verify". Fix some small bugs.
15-08-19: Merge omnirom 3.3.1 source code.
14-08-19: Initial release
Tested on:MIUI11(Android10);ArrowOS(Android 10);LOS17;Flyme8(Android9)
Fantastic. Will try it tomorrow morning and report. Looking forward to it!
I'm having some issues with flashing error for the secondary ROMS. I always get a different error, but from what I can see, they are "outdated" TWRP errors.
Primary ROM is RR. Appears to work.
When I flash a secondary ROM I get:
Pixel3: Zip Treble compatability error. Invalid zip file format.
Arrow: Zip Treble compatability error. Invalid zip file format.
Downloading a few other roms to test, but probably the same error
Any solution?
edit:
Started completely over from scratch. Completely wiped data, installed latest vendor/firmware/ etc...
Still have the same issue, but different flashing error:
With pixel3rom
"string resource 'zip_compatible_err' not found.
Using default value.
ZIP Treble compatibility error!
invalid zip file format.
And then it just aborts.
With arrow OS:
Zip treble compatibility error
invalid zip file format
And then it just aborts.
Firipu said:
I'm having some issues with flashing error for the secondary ROMS. I always get a different error, but from what I can see, they are "outdated" TWRP errors.
Primary ROM is RR. Appears to work.
When I flash a secondary ROM I get:
Pixel3: Zip Treble compatability error. Invalid zip file format.
Arrow: Zip Treble compatability error. Invalid zip file format.
Downloading a few other roms to test, but probably the same error
Any solution?
Click to expand...
Click to collapse
Yes, the recovery is outdated (version 3.2.3-0). Vasishath's repository hasn't been updated yet. You can try to delete compatibility.zip in the zip file and see if it works. I've only tested some old Roms (RR treble, pixel experience) and they worked fine. I will also try to merge new features from official TWRP. BTW, I am just an amateur developer so maybe it will take some time or even not possible.
__ART1st__ said:
Yes, the recovery is outdated (version 3.2.3-0). Vasishath's repository hasn't been updated yet. You can try to delete compatibility.zip in the zip file and see if it works. I've only tested some old Roms (RR treble, pixel experience) and they worked fine. I will also try to merge new features from official TWRP. BTW, I am just an amateur developer so maybe it will take some time or even not possible.
Click to expand...
Click to collapse
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Okay. I'll try to update my code. Perhaps a looooooong time
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Now you can try the new recovery.img with version 3.3.1 and let me know the result. It may fix that issue (haven't tested yet myself)
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Just remove the asserts lines in updater scripts. That would do it.
Sent from my Pixel 3 using Tapatalk
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Click to expand...
Click to collapse
It always happened to me with multirom and dualbootpatcher. You have to delete locksettings files in data/system directory...
paulojorjealmeida said:
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Click to expand...
Click to collapse
Go to /data/system and delete all *.key files.Now you should get in without typing any password.
Lucas_Maximiliano said:
Go to /data/system and delete all *.key files.Now you should get in without typing any password.
Click to expand...
Click to collapse
Thanks men
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
Thanks men
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Alô,thats its not de solucion,i sink,but you now how to fix the pin problem
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
Alô,thats its not de solucion,i sink,but you now how to fix the pin problem
Click to expand...
Click to collapse
If you have the password problem, go to vasishath's thread and download a patch to clear password.
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Kripton_ said:
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Click to expand...
Click to collapse
Install fw+vendor 9.7.25.eu,for me resolve the problem
Sent from my [device_name] using XDA-Developers Legacy app
Kripton_ said:
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Click to expand...
Click to collapse
Are you sure your are using MIX2S Polaris? Not Mi8 or Poco F1 or MIX3?
It works fine on my device,I use Android Q gsi for internal,the MIUI is secondary.the problem is higher version of MIUI couldn't boot,it just reboot to recovery after "mix" logo on MIUI stable 10.3.4.0.
Writesin said:
It works fine on my device,I use Android Q gsi for internal,the MIUI is secondary.the problem is higher version of MIUI couldn't boot,it just reboot to recovery after "mix" logo on MIUI stable 10.3.4.0.
Click to expand...
Click to collapse
Did you boot any version of MIUI successfully? Could you try another version to see if it can boot? It can sometimes be the ROM's problem. If it still fails to boot, please tell me the version that can boot and the version which can't boot. But I am a student so maybe not too much time on debugging.
After many hours of trial and error, I now understand how to get RR and Lineage to boot with latest firmware updates. NO MORE BLINKING BLACK/GREY SCREEN!
Tested with Resurrection Remix 16.1 and Lineage 15.1 (Oreo)
Simply flash the boot and vendor images to their corresponding partitions using fastboot. Find the proper images from this Tmobile firmware,. https://androidfilehost.com/?fid=11410963190603878004 This method preserves IMEI and Baseband.
Nano/pico gapps work as well. HideProps magisk module can set your fingerprint to Moto E5 Play and get around that unregistered Google sh**. I edit /vendor/etc/fstab.qcom myself with vi and inside TWRP terminal shortly after flashing vendor partition. I do this because zips and other copies held me up. All I change is forceencrypt to encryptable in the data line of the fstab. Magisk 19.3 patches for verity. Another thing I do is move /vendor/lib/libeffects.so to /vendor/lib/soundfx/libeffects.so. Doing this will keep music/audio from studdering when screen is off. Last thing, TWRP 3.3.1 formats data as ext4 by default. We want to format with f2fs or you get corrupted data messages at boot. Happy flashing!
##
I find the earliest of these metro pcs firms have a working vendor image.
https://mirrors.lolinet.com/firmware/moto/james/official/Metropcs/
I got bluetooth working today, and lots of clues where I found the fix...
####Bluetooth
Now that I can set it up from a clean install, here's the basics for Bluetooth...
You'll need files from the stock system image. You can use a backup to get these or also use simg2img with dd and 7zip, I'll make a zip installer when I have more time.
1. Copy the following files, from stock image directory "/system/etc/" to the "/vendor/etc/" directory on device
mixer_paths* (14 files)
audio_* (5 files)
media_profiles* (3 files)
Edit the file /system/etc/ld.config.26.txt
add this text to the very end of line 61 :/system/${LIB}/vnd-sp/hw
You're done! If you did everything as described, and it doesn't work, check the permissions of the files you add to vendor partition with other xml files in same directory. I did mine on the device while running, it worked in place, without rebooting device. The GSI system is new to me, however the "Same Proccess HAL(hardware abstraction layer)" voodoo can likely be configured correctly to fix screen and port other GSIs' to our device.
Any chance of getting lamens terms step by step instructions on how to do this? That is the model I have and really liked those roms when I tried unsuccessfully to make them work last year.
edit: 9/21 6pm
I think it's because mine is TMO variant.
Mattswad said:
Any chance of getting lamens terms step by step instructions on how to do this? That is the model I have and really liked those roms when I tried unsuccessfully to make them work last year.
Click to expand...
Click to collapse
Trying based on this now. I'll update you.. been trying for TOO LONG lol it's almost the same time you posted 2 days ago!
---------- Post added at 04:12 AM ---------- Previous post was at 03:45 AM ----------
I've been up all night trying to get either one to work.. I think I came close but I am stuck at a looping blank screen.
If you could step through a bit more for us? I'd REALLY love to have lineageOS on it.
mrbox23 said:
After many hours of trial and error, I now understand how to get RR and Lineage to boot with latest firmware updates. NO MORE BLINKING BLACK/GREY SCREEN!
Tested with Resurrection Remix 16.1 and Lineage 15.1 (Oreo)
Simply flash the boot and vendor images to their corresponding partitions using fastboot. Find the proper images from this Tmobile firmware,.
Nano/pico gapps work as well. HideProps magisk module can set your fingerprint to Moto E5 Play and get around that unregistered Google sh**. I edit /vendor/etc/fstab.qcom myself with vi and inside TWRP terminal shortly after flashing vendor partition. I do this because zips and other copies held me up. All I change is forceencrypt to encryptable in the data line of the fstab. Magisk 19.3 patches for verity. Another thing I do is move /vendor/lib/libeffects.so to /vendor/lib/soundfx/libeffects.so. Doing this will keep music/audio from studdering when screen is off. Last thing, TWRP 3.3.1 formats data as ext4 by default. We want to format with f2fs or you get corrupted data messages at boot. Happy flashing!
Click to expand...
Click to collapse
I have the Metro PCS version
Moto e5 Play XT1921-3
Mattswad said:
I have the Metro PCS version
Moto e5 Play XT1921-3
Click to expand...
Click to collapse
Ahh That is excellent news. I am about to take a focus supplement, and dive into trying again I'll let you know. I found a few more of MrBox23's posts and I think I MAYBE onto something.... wish me loads of luck. If it works for me I THINK it should work for you, but you might need to start with a diff image than me, or use a different boot and vendor img than I will.. not sure if I can help you find those files or not..
I'll be back later to update what I find.
Sorry I haven't been on for awhile. I'll go ahead and post my working vendor and boot images. On Google drive for download. Doing this will trash your speaker if you play music very loud at all, expect that. I do not understand how to fix it. Other than that it's a daily driver. I have been asked about encryption this and that.. You have to modify fstab.qcom within vendor partition. Also the TWRP for this device will format your data partition as ext4 while the ramdisk and init stack are configured for f2fs(if you try and boot with ext4 data, you get corrupted/encrypted data message). You have to change data partition back to f2fs in TWRP every time you format that partition. Or you could modify the TWRP image like I did to fix it permanent.
Files will be uploaded soon, make sure you understand what's involved before getting into this. I'll answer questions best I can, but this is for those who are dediced and willing to get down on some bootloops to figure it out, especially if you're not used to this sort of thing. Some magisk modules will cause bootloops, do those one at a time and gapps separately. I seriously recommend taking apart the firmware from OP and focus on getting to the aosp boot animation, THEN take care of verity/root and fstab. You're formatting data partition anyway you might as well successfuly backport the graphics first.
Vendor image TWRP backup, put this on its own with boot image. I keep it as vendor_fixed for easy reference. The fstab is already patched if you use mine.
Boot image TWRP backup, it is patched with magisk (19.4 likely) install magisk on your own anyhow. KEEP YOUR ORIGINAL VENDOR/BOOT PARTITIONS! There's stuff in there that you might want later on. Like the /vendor/etc/wifi folder for example or the pieces from the original ramdisk.
Vendor and boot with md5 sums to verify integrity.
https://drive.google.com/folderview?id=1-2KO_iRFTjLv6pyx-7Qmhi8kWZBpVIWD
Wipe everything, including internal storage(after backing up a working system).
Format data partition back to f2fs in advanced wipe options.
Get LineageOS 15.1 beta or RR you can find these here on XDA.
Flash Lineage zip its the old style zip install that copies idividual files, not an image, the boot image it installs needs to be replaced per instructions that follow.
Or flash RR system image from official repository link is found here on XDA.
If you flash a system image with TWRP you'll need to reboot back into recovery right after and resize the system partition in advanced wipe options or your system partion will be incorrect size afterwards, if flashing system with fastboot(recommended) then skip the resize instruction.
After you have a system installed, restore the vendor and boot images from the link. A good approach would be to backup your existing boot/vendor as a pair, then replace originals with downloaded images.
The first time I got this to work, I used fastboot to flash partitions, like this.... I followed instructions within Metro PCS firmware(one of those xml files has the fastboot commands, including some oem options that specify a particular mode) Then i flashed ...RR system, followed by boot/vendor images from firmware referenced in OP. I finished that with fastboot -w option, that was when it worked for me. I dealt with the fstab and boot verity patching AFTER I first saw the default Android boot animation. Once you see that plain white "android" with the slow moving left to right animation, your in. From what I can tell our device needs the older kernel within the boot image and the libs/binaries from the vendor image to get the screen working correctly. Your trading your working speaker, for a working screen. I have attempted to find exactly what it is that's different between the two, but it's over my head. Overall it's relatively stable, go easy with magisk modules, some of them will cause kernel panic(bootloop) use a recovery based magisk tool to disable offending module if this happens. Sometimes the device will not boot normally, usually this means the cache was erased(its okay) for whatever reason and I wait it out, otherwise I restore the vendor_fixd backup I made. I have not had gone back to stock ROM, however I have had to flash the vendor partition to get it booting, usualy happens if i flash a module or when updates break substratum theme.
Good luck!
Oh email me for quick response, within reason.
mrbox24 at gmail
Bonus screenshot and the TWRP 3.1.1 I modified with correct data format. If you have an sdcard with second partition it will show up as "linux" named after the chroot partition from mine.
Screenshot shows LSM kernel found here, yes it works.
mrbox23 said:
The first time I got this to work, I used fastboot to flash partitions, like this.... I followed instructions within Metro PCS firmware(one of those xml files has the fastboot commands, including some oem options that specify a particular mode) Then i flashed ...RR system, followed by boot/vendor images from firmware referenced in OP. I finished that with fastboot -w option, that was when it worked for me.
.
Click to expand...
Click to collapse
thank you for this! (and the files)
questions...
1.) Your files in your zip extract as boot.emmc.win and vendor_image.emmc.win ...
Should we rename them to boot.img and vendor_image.img before flashing?
2.) Is your file TWRP-3.1.1_JAMES_T_f2fs-data.img already fixed to format data as f2fs?
3.) where is the option in Twrp to backup vendor and boot images?
I'm almost ready to dive in...
aka.bugle said:
thank you for this! (and the files)
questions...
1.) Your files in your zip extract as boot.emmc.win and vendor_image.emmc.win ...
Should we rename them to boot.img and vendor_image.img before flashing?
2.) Is your file TWRP-3.1.1_JAMES_T_f2fs-data.img already fixed to format data as f2fs?
3.) where is the option in Twrp to backup vendor and boot images?
I'm almost ready to dive in...
Click to expand...
Click to collapse
Yes TWRP is fixed for f2fs data, also the correct version is 3.3.1 latest for device.
Those files are ready to be RESTORED, not flashed in TWRP. You would replace files in an existing backup with those. I have a fresh backup made from from the earliest metro pcs firmware. I am about to upload. What device do you have?
mrbox23 said:
Yes TWRP is fixed for f2fs data, also the correct version is 3.3.1 latest for device.
Those files are ready to be RESTORED, not flashed in TWRP. You would replace files in an existing backup with those. I have a fresh backup made from from the earliest metro pcs firmware. I am about to upload. What device do you have?
Click to expand...
Click to collapse
Cool. thanks.. So far I have three, 1921-2 At&t (new, prepaid, bootloader unlockable so far, daily phone), an xt1921-5 unlocked bootloader, sim locked to sprint, so far been unable to get another rom to boot, and an xt1921-3 metropcs Gsm unlocked, boot loader unlocked, and now booted to lineage 15.1 thanks to you and phh. Wifi works, and gapps go seem to not crash, I did the register a non-stock rom hoop jump with google. Camera nothing but gray or crashes. Everytime it boots, clock time is wrong. haven't really tested much yet.
Really want to be able to get camera functioning, and test an At&t sim in it before switching it to my daily device. I read that the camera fix was committed to 15.1 but I'm lost as how to apply those patches even if I could find them.
aka.bugle said:
Cool. thanks.. So far I have three, 1921-2 At&t (new, prepaid, bootloader unlockable so far, daily phone), an xt1921-5 unlocked bootloader, sim locked to sprint, so far been unable to get another rom to boot, and an xt1921-3 metropcs Gsm unlocked, boot loader unlocked, and now booted to lineage 15.1 thanks to you and phh. Wifi works, and gapps go seem to not crash, I did the register a non-stock rom hoop jump with google. Camera nothing but gray or crashes. Everytime it boots, clock time is wrong. haven't really tested much yet.
Really want to be able to get camera functioning, and test an At&t sim in it before switching it to my daily device. I read that the camera fix was committed to 15.1 but I'm lost as how to apply those patches even if I could find them.
Click to expand...
Click to collapse
I think those patches are applied at source code level. meaning it would be in a future release. My camera works running Resurrection Remix, on xt-1921-3 try copying [email protected] from stock /system/lib/hw to /vendor/lib/hw, making sure to keep permissions same as others in vendor/lib. im willing to read logs, does your att run lineage? if so, does bluetooth work?
I make custom scripts and have a custom build.prop, for example this.....
resetprop 'media.camera.ts.monotonic' 0
resetprop 'persist.camera.HAL3.enabled' 1
resetprop 'audio.deep_buffer.media' true
Those three lines are saved to a file called mediafix.sh in /data/adb/service.d to be ran at boot. it helps with media and camera issues. As well as a one line file called led-chg.sh
echo battery-charging > /sys/class/leds/charging/trigger
Which turns on the light, otherwise never used, in front of phone when charging.
I think it's important to use a/the real fingerprint from an e5 device along with other properties. To get the best out of the hardware and least error messages during boot. I go through logcat/dmesg and attempt to fix what's broken, like the camera on lineage(works without trouble on rr remix btw). I used hidepropsconf module at first and a sprint fingerprint, but later began using the one found in info.txt of firmware zip.
ill post my work in progress build.prop(hosting it with new vendor and boot images on gdrive) which noticeably improves overall performance and lends to less log errors, or lags and crashes.
I find the vendor/boot firmware here(oldest 2018) https://mirrors.lolinet.com/firmware/moto/james/official/Metropcs/ to work best. Audio is completely a loss though. My speaker is blown now and no Bluetooth unless running stock, not even the headphone jack works. All sound comes from the one speaker, even with headphones plugged in I'm at a loss with that issue.
I also modify the boot image. turns out the 1921-3(possibly others?) uses the sdk26 8.0 android ld(library config) instead of the ld.config.27.txt that matches its sdk level. in fact if i try to force the 27 lib config, the gray/black screen comes back. it boots up, i know because my charger light comes on, but no screen. Anyhow i change the os level in boot config to 8.1.0, this gets me to where i am now with only bluetooth(mixerpath/lib issues i suspect) and a couple missing ui features due to what i imagine originate from missing whitelists in /system/etc/permissions xml files.
Another thing of note is how i spoof the mac adress for wifi, this(and other things) is done by modifying the kernel command line config in boot.img. my second e5 play xt-1921-3 has a broken screen, and serves exclusively as a wifi-repeater, captive-portal, and ssh server/tunnel. i spoof the busted screen wifi mac, with an old device mac address that is still registered on xfininity wifi network. it repeats that connection to my other devices. very efficiciently at that. with 3+MiB/s average. it took some hacking but after i found out the oem partition on this device can be formatted, and removed from the ramdisk/system all together, without consequence(not to lineage, bootleggers, or rr remix that is) and be re-purposed to whatever else. its roughly 700MB in size perfect for a debian chroot with my custom wifi repeater and misc servers. running in its own dedicated internal(FAST)partition. This device, and its kernel level mac spoofing with the now almost phased out WCNSS qualcom configurable wifi firmware, is incredible. the busted screen one has been on every day non stop functioning as a repeater, router with captive portal, and dhcp service, for almost two months. it automatically connects to wifi, kills the android zygote/system server, kills its backlight and starts up a hotspot and sshserver/captive portal, all without cell service, and without any interaction.
Anyway, new mpcs files up soon.....
mrbox23 said:
I think those patches are applied at source code level. meaning it would be in a future release. My camera works running Resurrection Remix, on xt-1921-3 try copying [email protected] from stock /system/lib/hw to /vendor/lib/hw, making sure to keep permissions same as others in vendor/lib. im willing to read logs, does your att run lineage? if so, does bluetooth work?
###bugle added### my Att is an xt1921-2, can't even unlock the bootloader... But 30 bucks isn't bad for a new screen and a new speaker. ###
Another thing of note is how i spoof the mac adress for wifi, this(and other things) .
Anyway, new mpcs files up soon.....
Click to expand...
Click to collapse
Years ago, I used to compile Gentoo to run on some archaic hp tablets... Now I just run Linux mint on somewhat newer hardware. This gave me a limited skillset to get an old Moto mb300 running with gingerbread and CyanogenMod. Everything worked, had them for over 4-5 years, just started really messing up over the summer. Miss the real keyboard.
Thanks so much for the tips and insights. It'll take some time to absorb everything in your post.
aka.bugle said:
Years ago, I used to compile Gentoo to run on some archaic hp tablets... Now I just run Linux mint on somewhat newer hardware. This gave me a limited skillset to get an old Moto mb300 running with gingerbread and CyanogenMod. Everything worked, had them for over 4-5 years, just started really messing up over the summer. Miss the real keyboard.
Thanks so much for the tips and insights. It'll take some time to absorb everything in your post.
Click to expand...
Click to collapse
My first "Android" phone was the HTC HD2 wich was actually a Windows phone that can boot linux from the sdcard. I came across it while learning how to get linux booting on laptops. I was fascinated with booting a mini linux on a portable device. I learned about Android and linux in that way, at the same time. Kernel, ramdisk, java machine, broadband cellular modem, and wifi radio in my pocket. I abandoned windows entirely, to this day lol
Right you are! @mrbox23 ... I've got camera on RRemix on the metro 1921-3!
I'm gonna put the lineage/no camera issue on the back burner for when I try to use your older boot/vendor img trick (boot Lineage 15.1) on the unlocked 1921-5.
(I only have a 1Mb/s dsl connection here, takes about 4-5 hours for a 1 gig file to dl)
So, for the Metro 1921-3, I can't find libeffects.so or even the soundfx folder to copy into. (studder fix)
Your script 2 files for media/camera and charge led, other than making them executable (0755? 0700?) will they be called (without any other mod) being in /data/adb/service.d ?
I think it's important to use a/the real fingerprint from an e5 device along with other properties. To get the best out of the hardware and least error messages during boot. I go through logcat/dmesg and attempt to fix what's broken, like the camera on lineage(works without trouble on rr remix btw). I used hidepropsconf module at first and a sprint fingerprint, but later began using the one found in info.txt of firmware zip.
Click to expand...
Click to collapse
I pulled one out of my Att phone that is a james xt1921-2 but has a locked bootloader, all stock ... I used #getprop ro.build.fingerprint.. not sure if i should use this, or wait to see your build.prop...
ill post my work in progress build.prop(hosting it with new vendor and boot images on gdrive) which noticeably improves overall performance and lends to less log errors, or lags and crashes.
Click to expand...
Click to collapse
All the best to you and yours in 2020. Meeeerrrry eXksMix, hic up'
Yes to service.d with those three. I ditched the camera ones though, footej or another camera is nice. Im close to figuring out what the vndk library thing.
hosting current prop setups, between resetprop in service.d and modifying build prop. other goodies too. I turned oem partition into swap space, and added permissions to priv-app xml's enabling more RR features, like hold back to kill app.
mrbox23 said:
Yes to service.d with those three. I ditched the camera ones though, footej or another camera is nice. Im close to figuring out what the vndk library thing.
hosting current prop setups, between resetprop in service.d and modifying build prop. other goodies too. I turned oem partition into swap space, and added permissions to priv-app xml's enabling more RR features, like hold back to kill app.
Click to expand...
Click to collapse
mediafix line 2... set or resetprop?
1 resetprop 'media.camera.ts.monotonic' 0
2 setprop 'persist.camera.HAL3.enabled' 1
what are these last lines in mediafix for?
16 resetprop net.dns1 1.1.1.1
17 resetprop net.dns2 1.0.0.1
and i'm guessing the deb.sh is for your wifi repeater? swap space in oem?
how is mpcs.prop called? where is its proper folder?
can you host a copy of libeffects.so ?
@mrbox23 Bluetooth working! check.
aka.bugle said:
@mrbox23 Bluetooth working! check.
Click to expand...
Click to collapse
something I just noticed here recently is that's all the audio output now. I can't test cellular calls, Hangouts only works when i restore that vendor path Back to where it was. My camera broke again to. I want to reach out to phh here or github.
Well that's a big bug, sorry. I've reverted the metro 1921-3 to stock for now, but on the positive side, I tried using your older boot/vendor imgs trick on the 1921-5 (Sprint)... and success! it boots Lineage 15.1 and bluetooth works, I haven't tried using the GSM Att Sim yet and still no camera, (I haven't tried your other camera recommendations yet.) One step closer for the 1921-5.