{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Baa's Android Kitchen
Auto Porting Tool for MT6580 Kernel 3.18.19
Porting Method From Nana Iyke Quame
Download Link: drive.google.com/open?id=0BwNegVZnDr-QMVhNYktTUWhBSkU
Requirements:
Must have any text editor to edit build.prop and updater-script
How to use:
REMEMBER TO EXTRACT THE TOOL IN C:\ TO AVOID SCRIPT ERRORS.
1.Place the stock boot.img,system.img, and the rom you want to port to the dedicated folder.
2.Open the tool and select option 1. Wait for it to finish and then go back to the main menu.
3.After option 1 has finished gathering the needed files, select option 2, then select what type of porting method you want to apply.
AOSP BASIC - ports etc\firmware and mdbb only (Preferable if you just want to boot the rom then fix bugs later.)
AOSP FULL - ports bin, ports etc\firmware and mdbb, ports lib, ports vendor (Porting method with bug fixes applied, but can sometimes cause loop in some roms)
CM-BASED BASIC - ports etc\firmware and mdbb only (Preferable if you just want to boot the rom then fix bugs later.)
CM-BASED FULL - ports etc\firmware and mdbb and ports lib ((Porting method with bug fixes applied, but can sometimes cause loop in some roms)
3. After porting method is applied.Go back to the menu and select option 3, then manually edit the build.prop and updater script to your liking.
4. After you have finished editing, select the build option. After building, move the rom zip to your phone then flash
Note:
1.Make sure to place all files in their needed directories for script to successfully locate your files and proceed without errors
2.You have to manually edit build.prop and updater-script values based on your liking and needs.
3.Only use the delete all dependencies option after you have finished/ have flashed the ported rom because it will also delete the file you have finished building.
I hope you like my simple tool I have put many hours to make this
If you have something to add in this tool feel free to suggest and help.
I made it using Notepad++ for batch scripting and Quincy 2005 for C language codes
If you feel that I have helped you and you liked my tool feel free to donate, it will greatly help my studies Just inbox me, I dont have paypal atm still 17
Screenshots:
Proof: Lineage OS 13 Auto Ported with this tool
Special thanks to:
Nana Iyke Quame, droidpeepz, darkcyanidedevs, mt6580 development and porting, xda-developers, 4pda
LOS 13 is Android 6? how i port LOS rom to Blu Vivo 5 Mini?
Related
Hello guys,
I have been inspired by broodplank and his tools and have written a small gui for ADB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With this tool you are easily able to use some of the very powerfull functions of adb.
For instance you can read and save logcat,DMesg and build.prop
Also you can reboot your phone to System,recovery or bootloader
Remote Install APKs
and if you are using a I9001 you also can install the recovery direct from your PC²
(I read the ro.product.model to determinate phone, so this has to be GT-I9001, it will not work with certain versions of BioHazard roms as this has changed the ro.product.model information)
New in Beta 3 is the posibility to directly choose one of "build in" recoveries that will come with adb-helper
Requirements:
Windows XP or higher
Microsoft Dot Net Framework 4
Installed Driver to connect Phone in Debugmode (For I9xxx it is Samsung Kies)
How to Use:
Download Setup Here:
http://sourceforge.net/projects/adbhelper/files/setup-adb-helper_Beta 3.zip/download
Install the Tool into a folder of your choise.
Use it !
credits:
broodplank1337 for his windows tools that inspired me to do this
bashlnx for the port of clockworkmod recovery 5
Arco68 for the port of clockworkmod recovery 6
czobor for the port of touchversion of clockworkmod recovery 6
dbx4 for the TWRP Recovery
Changelog:
Beta 3:
-ADB-Helper comes now as a Setup
-possibility to choose from 6 "buildin" recoveries to flash to your I9001 (or choose an custom *.img file for it)
Beta 2:
-Optical changes (Tabbed layout)
-Device Detection (by build.prop)
-Special function for I9001 : Flash Recovery from Image-file (adb push + dd)
Beta 1: Initial Release
Sourcecode Beta 1: http://sourceforge.net/projects/adbhelper/files/ADB-Helper_Beta1_Source.zip/download
Screenshots:
In Testing.. ADB is such a great tool and now with your GUI its useable for Newbees too.
Good job! I like to see more tools (not only the ones of myself ;p)
New Version available:
new function for I9001 user:
Remote install new recovery by img-file
and some more changes(look 2nd post)
New Version available
New in Beta 3:
-Now comes with setup
-build in recoverys for easy use of "flash recovery"
Root access
Martin_Ro said:
Hello guys,
I have been inspired by broodplank and his tools and have written a small gui for ADB
With this tool you are easily able to use some of the very powerfull functions of adb.
For instance you can read and save logcat,DMesg and build.prop
Also you can reboot your phone to System,recovery or bootloader
Remote Install APKs
and if you are using a I9001 you also can install the recovery direct from your PC²
(I read the ro.product.model to determinate phone, so this has to be GT-I9001, it will not work with certain versions of BioHazard roms as this has changed the ro.product.model information)
New in Beta 3 is the posibility to directly choose one of "build in" recoveries that will come with adb-helper
Requirements:
Windows XP or higher
Microsoft Dot Net Framework 4
Installed Driver to connect Phone in Debugmode (For I9xxx it is Samsung Kies)
How to Use:
Download Setup Here:
http://sourceforge.net/projects/adbhelper/files/setup-adb-helper_Beta 3.zip/download
Install the Tool into a folder of your choise.
Use it !
credits:
broodplank1337 for his windows tools that inspired me to do this
bashlnx for the port of clockworkmod recovery 5
Arco68 for the port of clockworkmod recovery 6
czobor for the port of touchversion of clockworkmod recovery 6
dbx4 for the TWRP Recovery
Click to expand...
Click to collapse
Do i need root access to function this software from my pc ?
Hello everyone..
In my tutorial here, I want to show newbies how to create their own flashable zip file to flash by recovery mode (CWM)...
Now installing your mods become easier and faster
Needed tools for newbies:
1) Download your desired template:
Template - for auto-perm-fix kernel support.zip
Template - for non auto-perm-fix kernel.zip
more details is down there!!
2) WinRAR or 7-zip program installed in your computer.
3) Auto-ZIP-Signer patch in case your kernel needs it
4) Cup of hot tea!!!
Which template should I use?
It depends on kernel you are using whether it supports auto permission fix or not (most of custom kernels support this feature)..
To know if you are using kernel with auto permission fix or not, boot into recovery mode and check if you have fix permissions option or not (usually under advance). If your kernel has fix permissions option, then use Template - for auto-perm-fix kernel support.zip otherwise, use Template - for non auto-perm-fix kernel.zip.
What will happen if you use wrong template?
If your kernel supports auto permission fix feature and you used Template - for non auto-perm-fix kernel.zip, nothing will go wrong (so don't worry!!) but the flashing process will take unnecessary longer time for fixing permissions!!.
If your kernel doesn't support auto permission fix feature and you used Template - for auto-perm-fix kernel support.zip, then you might need to fix permissions of the flashed mod manually or to add extra permissions line in updater-script (not advised for newbies)
How is it working?
Open the template zip file by WinRAR or 7-zip (don't extract!! Just open)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now what you need to do is just to drag & drop your modded file into its corresponding destination inside the zip file.
Copy your finished zip file to your external SD card.
Boot into recovery mode and flash your file... Now you can treat yourself the cup of tea.. you deserve it
Extra step:
If you are using stock kernel that needs varification key from flashable zip file, then you need to use Auto-ZIP-Signer to sign your finished zip file.
First copy your finished zip file from previous step and open ZIP Auto-Signer folder (download from above).
Now paste your zip file in "put-zip-to-sign-here" folder and run the script patch.
Now go to "Finished" folder and copy "Signed.zip" into your external SD card.
Boot into recovery mode and flash your signed file
Simple and noob proof tutorial, I hope it will help you all new xda members
Hey everyone, in this guide I will show you how you can get 24bit audio processing on your beloved rosy.
Keep in mind that I WILL NOT provide a bunch of files for you to change within your root, because audio xml's changes a lot and its hard to keep track for me as to which files will work and which won't. So rather, I will provide a way for you to edit those files on your own.
Requirements:-
1. Rooted with Magisk
2. A File manager (ex. MiX) with root permission granted
3. Note Editor (You can use MiX note editor)
4. Terminal Emulator like Termux to test if the method worked or not
5. Some Common Sense
ROMs I tested this on:-
1. LOS by Pulkit
2.RevengeOS by Pratyakshm
3.PixelExperience
4.AOSP11 by Pulkit
This method should also work on:-
1. Any Android 10 based ROM
I cannot say about android 9 or the version's before that because i never tested them, however if someone is willing to do that, let me know in the post replies and make sure you follow the guide.
Before we start, MAKE SURE TO BACKUP YOUR OLD FILES IN CASE ANY PROBLEMS ARISES LIKE BOOTLOOP'S.
So the steps are as Follow:-
1. Open up MiX or any of the file manager that you have then head over to /vendor/etc .
2. In there, find "audio_policy_configuration.xml" .
3. Take backup of this file and then open "audio_policy_configuration.xml" .
4. Under <mixPort="primary output"> profile name would be written as "AUDIO_FORMAT_PCM_16_BIT" change this string to "AUDIO_FORMAT_PCM_24_BIT_PACKED" .
5. Follow the same process as given in Step 4 for <mixPort = "raw"> , <mixPort = "deepbuffer"> and <mixPort = "direct pcm"> .
6. Scroll down the section of <device_port> and replace the string shown above for <Wired_Headset>, <Wired_Headphones>,<BT_SCO>,<BT_SCO_Headset>,<Line>.
- - Refer to the Screenshot Attached below, That will be enough for you to understand it properly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6.This step is only for people who also have the file audio_policy.conf in vendor/etc directory.
>> under primary > outputs , change format to "AUDIO_FORMAT_PCM_24_BIT_PACKED" for primary, raw & deep_buffer. [Screenshot attached below]
6. Save the file and put it back in /vendor/etc and give chmod 0644 [-rw-r--r--] .
7. Reboot your device.
- - At this point if your Phone doesn't boot, use TWRP to replace the new file [edited] with the Old one [unedited] file and message me on telegram @bancelhub so that I could look into the matter.
PROFIT!
How to check if it's working.
1. Open up termux with su.
2. Type "dumpsys media.audio_flinger"
3. AudioOut_D and AudioOut_1D should show "AUDIO_FORMAT_PCM_24_BIT_PACKED" as HAL Format. [Refer to Screenshots Attached]
Hope this guide was good enough, this was the first guide I wrote on xda. You might have noticed that I only explained how to do this on one device tree, Pulkit one's, since his dt is public I used it to show this experiment. You can try it on other ROM's based on other DT's but your procedure may vary, mildly. let me know your experience on telegram!
Happy Editing!
Awesome !!
Thanks for detailed guide :good:
Nice Guide ,Working
stayboogy_Officially
I'm back!!!
And in case you haven't heard or seen mine handle, I'm an expert level dev, and I don't care anything of your opinions or needs or wants, and I build for me and people like me who are expert users and/or just want plain Android without all the branding and garbage of all the other developers out there.
**This is just the beginning of my return to the dev scene.**
***I'm not offering support, never will, neither will I ever respond to questions about additions, upcoming plans, release dates, or reply to any questions for help about anything***
****If you can't read directions, or don't know how to install, THEN STAY AWAY BECAUSE YOU WILL GET NO HELP FROM ME!****
This is my build of AOSP 12 for the Pixel 5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[source]
default.xml - platform/manifest - Git at Google
This is straight from Google's Sources [-b android-12.0.0_r3]
Build 1 -- Basic Build for all Future Builds
Future Builds -- TBD / will have MODS ONLY that are necessary and approved by me alone for a Simple, Clean, Usable Device
Download:
[Build1 = 98 parts, hjsplitted, 10mb each basically]
[keep checking for completed upload--slow upload speeds on my dev device right now]
[either download the git as a zip from github
OR
download each file separately from github]
[get it here]
[rooting instructions below install]
>>> XXXXX <<<<
Install:
1) JOIN PARTS WITH "hjsplit" (possibly unnecessary but here for official way)
2) extract with 7zip
3) bootloader unlocked
4) reboot to bootloader
5) install.bat
6) Enjoy
or
6) After Rooting - Optionally Add Gapps, [MicroG incompatible for now], and Enjoy
How to Root:
1) Download Magisk and patch the original boot.img from my build
2) copy patched boot.img and vbmeta.img from my install zip to a location on pc
3) reboot to bootloader
4) fastboot --disable-verity --disable-verification flash vbmeta /path/to/my/original/vbmeta.img
5) fastboot flash boot /path/to/your/patched/boot.img
6) fastboot reboot
7) Enjoy!
Mod Edit: Link removed
I don't recommend anyone install this to their device until OP shows his source code/repos for the kernel and ROM.
He forked from this repo: https://github.com/nvllsvm/pixel5-aosp-builder
And only changed two lines in the readme to show changes to his fork: https://github.com/stayboogy/Staybo...mmit/1c5719b2eba5ec8c1e201306a9d2ab1120b0b2b1
Again, I would not install this at all to any device until his sources are provided.
rooting instructions added
the only bug found thus far is the Camera bug which will remove the app from app drawer but will still be available via double press of power button.
I'm working on it...
MOD ACTION:
Thread closed pending compliance by OP.
Hello,
I have a pixel 6a with Android 13. I'm trying to start a hello world service/daemon that just loops at boot.
From what I've been reading, it seems like I have to add a rc file to /system/etc/something(?). I tried to add a rc file to it, but it's read-only
So it seems like I have two choices. Download a factory image, unpack system.img, mount it, add a rc file, repack it, and flash it or add cpio file to boot.img like Magisk.
Am I understanding this right or is there a simpler way?
Thanks!
Look inside here:
[GUIDE] How To Add Init.d Support to Your Kernel & Rom
What is init.d ? Init.d is a feature which allows you to run brunch of scripts at boot . Thats really useful while you want to set values which reset at boot or run/do any thing at every boot or install tweaks , engines and.... There are some...
forum.xda-developers.com
jwoegerbauer said:
Look inside here:
[GUIDE] How To Add Init.d Support to Your Kernel & Rom
What is init.d ? Init.d is a feature which allows you to run brunch of scripts at boot . Thats really useful while you want to set values which reset at boot or run/do any thing at every boot or install tweaks , engines and.... There are some...
forum.xda-developers.com
Click to expand...
Click to collapse
looks like a very old guide, though...
Will it work with newer Android versions (e.g: 13)?
Take note that the Android platform consists of the Linux kernel and the Android API Framework.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When a mobile device gets powered o then as 1st thing the Linux kernel gets loaded and its code gets processed - and not the Android framework, hence at this time it's irrelevant what Android OS version - what gets loaded and its code gets processed after boot-up is completed - is present on moile device.
jwoegerbauer said:
Look inside here:
[GUIDE] How To Add Init.d Support to Your Kernel & Rom
What is init.d ? Init.d is a feature which allows you to run brunch of scripts at boot . Thats really useful while you want to set values which reset at boot or run/do any thing at every boot or install tweaks , engines and.... There are some...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the guide!
But will it work on Android 13 though?
I know boot.img for Android 13 no longer contains system stuff