After rooting I can easily get /system with root explorer. But how can I dump the kernel?
In another thread I learned the kernel is located in /dev/block/bml4. What's the method to dump it?
Related
Hi All,
Seems like there is a lack of information on how to create pre-rooted system images for those with unlocked bootloaders.
There is a new .146 firmware available now but we're still waiting for it to be rooted.
I had messaged Bin4ry previously and he had provided a rough guide. I do not have a X10 nor the knowledge to create a custom yaffs2 tool. So I'm sharing the info here and hope one of you can help with this:
Okay here is what to do:
Grab another SE Handset and unyaffs your system.img to it's system partition in recovery mode, after that connect with adb to recovery and change the system. When you done all your changes use nandroid to backup the modded system.
I used a X10 for that.
The problem is that SE is using a special yaffs2 format. If you want to use mkyaffs/unyaffs you have to change it to special SE-format. How they use yaffs is determined in their kernel sources, i'm tooooo lazy to create a custom mkyaffs for SE phones. but now you know what to look for, maybe you create one ?
Regards
Bin4ry
Originally Posted by sbong
Hi Bin4ry,
while creating the rooted system.img files for Arc, you mentioned that you used a different method instead of "unyaffs, edit files, mkyaffs"
Can you share what is the method you used to add in the files into system.img?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
thanks for your sharing. I like it
I want to have this——"unyaffs, edit files, mkyaffs"
and，thank Bin4ry
Hi, I'm pretty inexperienced when it comes to Acer devices, although I've successfully installed roms on my Samsung Galaxy Player. I've been reading around and everyone's saying that you have to delete or rename the recovery-from-boot.p from my Acer a500 before flashing a recovery, but it never gives me permission to write in the /system folder. I have root and I'm using ES file explorer (although i tried basically every other root explorer). I can read / write in every other folder but just not the /system folder. What can i do? Thanks~
ryukiri said:
Hi, I'm pretty inexperienced when it comes to Acer devices, although I've successfully installed roms on my Samsung Galaxy Player. I've been reading around and everyone's saying that you have to delete or rename the recovery-from-boot.p from my Acer a500 before flashing a recovery, but it never gives me permission to write in the /system folder. I have root and I'm using ES file explorer (although i tried basically every other root explorer). I can read / write in every other folder but just not the /system folder. What can i do? Thanks~
Click to expand...
Click to collapse
If you have root (which you can download a root verify app from the market), then in ES Explorer, you must set the /system to R/W.
If you can't change to R/W, then you only have half root, and need to fastboot a modified boot.img (kernel) that has the security removed. This of course depends on if you have the v8 bootloader installed.
Basically, to get the full luxury of everything, you need to have the V8 unlocked bootloader, install CWM, Without booting to the OS, boot into recovery and install one of the custom roms. Some of them are stock with the bloat removed (also the recovery.p and install.recovery.sh removed).
Check the sticky threads and you'll find several methods for doing this. But remember, get and write down your UID number before installing anything.
MD
Moscow Desire said:
If you have root (which you can download a root verify app from the market), then in ES Explorer, you must set the /system to R/W.
If you can't change to R/W, then you only have half root, and need to fastboot a modified boot.img (kernel) that has the security removed. This of course depends on if you have the v8 bootloader installed.
Basically, to get the full luxury of everything, you need to have the V8 unlocked bootloader, install CWM, Without booting to the OS, boot into recovery and install one of the custom roms. Some of them are stock with the bloat removed (also the recovery.p and install.recovery.sh removed).
Check the sticky threads and you'll find several methods for doing this. But remember, get and write down your UID number before installing anything.
MD
Click to expand...
Click to collapse
In order to get full root, is it okay if i re-root the device again? I can't seem to install the v8 bootloader to work..
Hi, I'm trying various kernels on my rom.
Therefore I'd like to backup my existing kernel.
I know TWRP can easily do this.
However for information I'd like to know manual adb method, or terminal commands.
Or is there a Zip file which I can run to automate the process
why not just keep the kernel zip file in your storage?
as a hobby, i test kernels, trinity kernel to be exact. i probably have 20-30 kernels in my storage at all times. when im want to run my favorite again, i just reflash it. i cant imagine why id want to back up a kernel.
I believe the next step for the Droid Turbo are system images.
With MofoRoot, the next goal is to create a system image that is lollipop 5.1 and has root.
I've only flashed system images that were created up to this point but I'd be interested in learning how to take apart a system image and go as far as changing/manipulating it have wifi tether and root. Anyone have any good suggestions on where to start learning?
I plan to collect what I discover in this thread.
windraver said:
I believe the next step for the Droid Turbo are system images.
With MofoRoot, the next goal is to create a system image that is lollipop 5.1 and has root.
I've only flashed system images that were created up to this point but I'd be interested in learning how to take apart a system image and go as far as changing/manipulating it have wifi tether and root. Anyone have any good suggestions on where to start learning?
I plan to collect what I discover in this thread.
Click to expand...
Click to collapse
You will need a different kernel to work with a 5.1 or 5.0 system image. We cannot flash a kernel with this method yet just system images.
Right, so the only thing we can do are modified "roms" based on stock. Can't flash recovery or kernel since those are on separate partitions.
This tool, yaffy, might be of some help. I'm downloading it now to see if it works...
timmyk465 said:
This tool, yaffy, might be of some help. I'm downloading it now to see if it works...
Click to expand...
Click to collapse
Not going to work. You need to mount an ext4 image which is not what that tool is designed for. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Ekkoria said:
Not going to work. You need to mount an ext4 image. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Click to expand...
Click to collapse
I'd definitely be interested in a guide. I just wish there was a tool for windows that would work.
You can do it on windows but it's way easier on Linux.
I'm gonna get Linux back up and running and see what I can cook up.
Ekkoria said:
Not going to work. You need to mount an ext4 image which is not what that tool is designed for. I'm currently doing so by using Linux and mounting the image as a loop device. I can create a guide for doing so if there's demand.
Click to expand...
Click to collapse
All I want to do is build a flashable img with a modified hosts file. I've found a guide for mounting the image as a loop (which Ive done....) the issue Im running into is changing permissions to be able to actually edit the file once its mounted.
Guess I'll read more and keep tinkering..
ntxct said:
All I want to do is build a flashable img with a modified hosts file. I've found a guide for mounting the image as a loop (which Ive done....) the issue Im running into is changing permissions to be able to actually edit the file once its mounted.
Guess I'll read more and keep tinkering..
Click to expand...
Click to collapse
Open your file manager as root, then open the file.
---------- Post added at 11:49 PM ---------- Previous post was at 11:44 PM ----------
I wrote up and posted a quick guide (which probably sucks) for this purpose.
Guys, I'm sorry but I have an obtuse question.
There have been a handful of mods that modify your ROM using Magisk systemless root. As I understand, Magisk roots without touching the /system folder to keep from breaking SafetyNet. Is that correct?
I ask because I know Arise4Android has a Magisk compatible zip you can flash that modifies your mixer_paths_taska.xml file as part of the installation. I'm trying to implement the permanent high impedence mod by modifying the mixer_paths_tasha.xml file and I obviously can't because I have no R/W access to the /system/etc folder.
Does anyone know a way to modify this file by either flashing a zip or otherwise?
Thanks much, everyone!