Related
I download the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
was the INIT.D HACK installed correctly?
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
I don't know what to do now.
thanks
you need to either toggle safe system off, or flash a ROM to use for safe system, and then flash the init.d hack
and my suggestion is to flash CM7 or Monster, Mav, SD3, Liberty, Etc. Im on CM7, works very nice http://hash-of-codes.blogspot.com
thanks MrJudylicious,
but sorry don't know how to do it...
this is my first android phone i just follow the steps that Chaoticweaponry told on the other topic:
"1: Root your Droid 3 using the 1 click root method (search around XDA/Google)
2: Download Safestrap from Hashcode's website. - USE BOOTSTRAP IF YOU'RE ON STOCK/NON-SAFESTRAP ROMS
3: Install the .apk file using AppInstaller from the Android Market.
4: Start Safestrap (or similar) and allow superuser permissions - then install recovery.
5: Get Download All Files from Android Market.
6: Download the init.d hack.
7: Turn your phone off.
8: Press m + power, scroll down to BP Tools (volume down key) and select it (volume up key)
9: Scroll down to install zip from SD card (select using power button)
10: Go to internal sd card - downloads folder.
11: Find the init.d file, and install it.
12: Reboot the device (go to main menu on safestrap (or similar) recovery)
13: Done."
I don't know what is flash a ROM...
so the init.d hack is not working?
as I said, I put system safe on and installed complete.. then it won't boot I don't know why..
so I put system safe off and it booted.
can you tell me what to do step by step please?
i'm thankful
Pedro
ps: I got one app called "droid3bootstrap" but idk if it will serve.
if you can, tell me what I need to download and what I should do...
sorry for the inconvenience
thanks
I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d
MrJudylicious said:
I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d
Click to expand...
Click to collapse
Thanks a lot MrJudylicious,
but what is this 'CM7 11-16 build'? what will it do on the phone?
I just wanted to install INIT.D HACK because I read that saves battery.
cm7 is a stripped down very functional, very fast operating system. if you want stock, you can visit his hash-of-codes.blogspot.com and under android downloads you can download the stock 5.6.890 /root + superuser ( http://goo.gl/3bTpJ ). you cannot flash to teh main system with safestrap, but you can with bootstrap. you could have issues installing more than one *strap, which is why i suggested you keep safestrap.
it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?
pedroramos said:
it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?
Click to expand...
Click to collapse
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.
ChaoticWeaponry said:
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.
Click to expand...
Click to collapse
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil
pedroramos said:
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil
Click to expand...
Click to collapse
This is why this didn't work
You install safestrap, it allows you to install roms to your /preinstall directory (directory for windows users ^^). You don't install a rom but install the init.d files to /preinstall and then try to boot off /preinstall (because safestrap is enabled). Obviously that wont work because when your phone boots it looks for system files in /preinstall but all that's there is the init.d hack.
You uninstalled safestrap, installed koush' and then installed the init.d files to /system which your phone actually runs off. At that point the init.d is correctly installed.
Another option(the one that people are telling you here) is to install safestrap, enable safestrap, install your rom to the safestrapped system and then install your init.d hack on top of the rom you just installed which is also correct.
it's 2 different ways to do the same thing slightly differently(although with the second method you basically have 2 /systems). I hope this helps clear up your confusion.
I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.
pedroramos said:
I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.
Click to expand...
Click to collapse
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
You can test that this works on your roms by flashing and then checking for a ".ItWorks" file in /data partition. If you are using ES File Explorer or similar you will need to be sure to allow it to show hidden files, otherwise you won't see this file.
Click to expand...
Click to collapse
In his development thread. This might work for you.
Willis111 said:
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
In his development thread. This might work for you.
Click to expand...
Click to collapse
I opened root explorer and there was a ".itworks"(with a medal of sheriff) on /data partition
you said that safestrap won't change my system because it install the ROM in a different partition and the boot is made by there.
doesn't bootstrap happen the same? bootstrap overwrite the original system?
a case:
I used bootstrap and suppose that I want to unflash the init.d.. how can I do it?
thanks a lot
I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?
pedroramos said:
I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?
Click to expand...
Click to collapse
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.
calash said:
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.
Click to expand...
Click to collapse
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..
It works 4 me
pedroramos said:
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..
Click to expand...
Click to collapse
Ok, so right now it sounds like you are using the basic Clockwork Mod recovery, identified by the installed Droid 3 Bootstrap from the market/downloaded. In this case you do not have a backup from before the change you applied (Side note: Backups are also called nandroid backups. They are the same, just a different term).
If you wanted to remove the init.d hack it would be a bit more difficult at this point. Not impossible but you may end up losing all your data. It depends on if the changes the init.d hack made are well documented or not. It is a fairly safe hack so I would not worry too much about it at this point.
For your reference the bootstrap you installed, also called Clockwork Mod, and SafeStrap do nearly the same thing, providing you with the menu at the very beginning when you power on the device and allows you to flash (what you did to install the init.d have), backup, and some other neat features.
The big difference is that SafeStrap allows you to have two operating systems, also called Roms, on the phone. These are identified as Safe and non-Safe. non-safe is whatever OS (or Rom, the terms mean the same on our phones) you start with while the Safe is a new install that you do in the same way as you flashed the init.d have.
As you work with it more you will get the hang of the various terms and software packages. For now you should be in good shape, even without a stock backup. We have ways to get back to a pure stock image if that needs comes up, just check the threads in the development forum for more information.
Hi all !
I'm new to custom kernel building, and after fairly long searches across the net, I still have some questions. About initramfs first, how do I build an initramfs image compatible with my kernel ? Which files should absolutely be included ? Any (Android-oriented) documentation on this ? I'm able to unpack a zImage and extract the corresponding initramfs, but should I modify some of the files before including them in my custom kernel (besides the modules) ?
Also, as far as I understand, the recovery image is included in the initramfs. If I want to change the recovery (to CWM, say), how should I do : nothing else than changing recovery related files ?
Then, I have found that there is the j4fs.ko module that is included in the Samsung stock kernels I've seen (KK9 and LB1). However, when I compile my kernel from the Samsung's sources, I do not get that module (and I don't find any corresponding sources). Any idea where I could find them, and if j4fs is necessary ?
Thank you !
how to update Kernel ?
Anyone ?
Hello There.
First of all, is it possible to install both PAC-man 4.3 ROM and SlimBeam 4.3 using MultROM?
If Yes, how to do this correctly/what am I doing wrong?
I have TWRP 2.6.0.0 and MultROM installed. Tried different combinations and nothing work.
I'm not much into this stuff, so as far as I could go I have investigate the issue of kernels and kexec, but as I said, my knowledge stopped on knowing that there is such thing, and secondary ROM can be installed with different, separated kernel.
Thanks for interest.
I thought that it would be helpful if I write what combination/order of instalation gives what result, so here it goes:
1. Installing SlimBeam, and then PAC: E: Error executing update binary in zip 'tmp/mr_update.zip'
2. Installing PAC, and then SlimBeam: Installation complited correctly, secondary system(SlimB) loading forever with PAC boot animation - probbably because of kernel?
3. Installing PAC and then SlimBeam with seperated cernel: (In Multiroom when booting SlimB) Error Kexec-hardboot support required to boot this ROM...
In this case I'm guessing that patching this kernel could help, but it's superadvanced for me
noone1101 said:
Hello There.
First of all, is it possible to install both PAC-man 4.3 ROM and SlimBeam 4.3 using MultROM?
If Yes, how to do this correctly/what am I doing wrong?
I have TWRP 2.6.0.0 and MultROM installed. Tried different combinations and nothing work.
I'm not much into this stuff, so as far as I could go I have investigate the issue of kernels and kexec, but as I said, my knowledge stopped on knowing that there is such thing, and secondary ROM can be installed with different, separated kernel.
Thanks for interest.
I thought that it would be helpful if I write what combination/order of instalation gives what result, so here it goes:
1. Installing SlimBeam, and then PAC: E: Error executing update binary in zip 'tmp/mr_update.zip'
2. Installing PAC, and then SlimBeam: Installation complited correctly, secondary system(SlimB) loading forever with PAC boot animation - probbably because of kernel?
3. Installing PAC and then SlimBeam with seperated cernel: (In Multiroom when booting SlimB) Error Kexec-hardboot support required to boot this ROM...
In this case I'm guessing that patching this kernel could help, but it's superadvanced for me
Click to expand...
Click to collapse
The kernel of your primary ROM needs to support kexec. I don't think this is true for the pac nor the slim kernel. You will have to flash a custom kernel on your primary ROM.
Dexxon said:
The kernel of your primary ROM needs to support kexec. I don't think this is true for the pac nor the slim kernel. You will have to flash a custom kernel on your primary ROM.
Click to expand...
Click to collapse
Exactly.
Idk either how it looks like with pac as secondary, because of such mentioned problems.
I am on a good way to finding right kernel for that and trying to flash it, and test if it works.
Ty for reply.
noone1101 said:
Exactly.
Idk either how it looks like with pac as secondary, because of such mentioned problems.
I am on a good way to finding right kernel for that and trying to flash it, and test if it works.
Ty for reply.
Click to expand...
Click to collapse
Your Problems consists of 3 things:
1. U need a kernel with Kexec-Support for the primary Rom to be able to boot secondary rom with other kernel. If u use same kernel for both rom, u dont need a kernel with Kexec-Support
2. To flash the kernel for secondary rom, u need a repacked kernel with ramdisk from destination rom, anykernel wont work, cause u cant flash it on secondary. It writes with "dd" direct to partition and this is wrong way for secondary Rom. So u have to choose a repacked kernel for secondary...
3. The script in most install.zips for 4.3 roms contains symlinks written over more than one line. These scripts wont work with multirom installer (TWRP MultiRom), so u have to modify script, extract from zip, write all symlinks and all other commands (which are broken into more than 1 line) in 1 line and copy back into zip. Install will work now (modification is for "Error executing update binary in zip 'tmp/mr_update.zip').
Bogeyof said:
Your Problems consists of 3 things:
1. U need a kernel with Kexec-Support for the primary Rom to be able to boot secondary rom with other kernel. If u use same kernel for both rom, u dont need a kernel with Kexec-Support
2. To flash the kernel for secondary rom, u need a repacked kernel with ramdisk from destination rom, anykernel wont work, cause u cant flash it on secondary. It writes with "dd" direct to partition and this is wrong way for secondary Rom. So u have to choose a repacked kernel for secondary...
3. The script in most install.zips for 4.3 roms contains symlinks written over more than one line. These scripts wont work with multirom installer (TWRP MultiRom), so u have to modify script, extract from zip, write all symlinks and all other commands (which are broken into more than 1 line) in 1 line and copy back into zip. Install will work now (modification is for "Error executing update binary in zip 'tmp/mr_update.zip').
Click to expand...
Click to collapse
the alternative to problem 3 is to install a rom, do a backup, install the rom you want and restore a backup as second rom. thats how i did it, noob-way
Quick summary, I can not:
mount -o remount,rw /system in normal mode even with root permission. Error is "Device busy"
modify files in /system in twrp and keep it persistent. It somehow roll back to the stock state after reboot into normal mode.
I'm a long-time linux user, and fairly familiar with rooting in pre-nougat versions. My previous phone is Oneplus-X in LineageOS-14, and I could do whatever I like with the system partition. Recently I received a P9 as present. I updated the rom to B377 and flashed OldDroid's TWRP-3.1.0+phh su. But I can not find a way to modify the /system partition. I need to change a lot of things, like /system/etc/hosts, adding apk into /system/priv-app, etc.
Could someone help?
ccaappton said:
Quick summary, I can not:
mount -o remount,rw /system in normal mode even with root permission. Error is "Device busy"
modify files in /system in twrp and keep it persistent. It somehow roll back to the stock state after reboot into normal mode.
I'm a long-time linux user, and fairly familiar with rooting in pre-nougat versions. My previous phone is Oneplus-X in LineageOS-14, and I could do whatever I like with the system partition. Recently I received a P9 as present. I updated the rom to B377 and flashed OldDroid's TWRP-3.1.0+phh su. But I can not find a way to modify the /system partition. I need to change a lot of things, like /system/etc/hosts, adding apk into /system/priv-app, etc.
Could someone help?
Click to expand...
Click to collapse
Hopefully this might help:
1. revert back to unmodified boot image (in TWRP flash from here[/URL or restore your backup from the unmodified boot image] , leave anything else untouched (especially TWRP 3.1.0-0 for EMUI 5)
2. flash this [URL="https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102"]SuperSU image in TWRP (read the comments in the post please ... single bootloop ... then everything is ok and rooted)
3. install JRummy's BusyBox from Google Play (Stephen's won't work)
You are done and good to modify /system.
Note: resulting earthquakes, thunderstorms and spring floods from this work are solely under your own responsibility :laugh:
hakaz said:
Hopefully this might help:
1. revert back to unmodified boot image (in TWRP flash from here[/URL or restore your backup from the unmodified boot image] , leave anything else untouched (especially TWRP 3.1.0-0 for EMUI 5)
2. flash this [URL="https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102"]SuperSU image in TWRP (read the comments in the post please ... single bootloop ... then everything is ok and rooted)
3. install JRummy's BusyBox from Google Play (Stephen's won't work)
You are done and good to modify /system.
Note: resulting earthquakes, thunderstorms and spring floods from this work are solely under your own responsibility :laugh:
Click to expand...
Click to collapse
1. I did a backup of boot partition before phh root, so should be able to restore the backup, instead of download the boot partition from others?
2. Is systemless supersu binaries need be individualized for every phone? Can I download systemless supersu from somewhere more semi-official? I'm not exactly comfortable installing zips from random links. ()
Ad 1. Till now rooting on our P9 works through injection of the su mounting routine into the kernel in boot section (if using a modified kernel + su installation or modifying the kernel during su installation itself doesn't make a difference). So any su installation modifies the boot section and you mess things up if you try to install another su on top of the other. Therefore reverting to the original boot image is mandatory before installation of another su.
Ad 2. The su is compiled against different platforms​ not phones (in our case arm64). So @Chainfire has the different platform variations in his package. The "shady" package in our case is basically the v2.79 stable version of 12/20 2016 (you can unpack both packages and compare them against each other, they are bit for bit equal) but has an P9 specific injection routine to modify the kernel. After installation you have pure su v2.79 stable on board - not more, not less.
Sorry, "normal" SuperSU packages won't work due to lacking the kernel modification (phh uses a modified kernel instead you have to flash separately on P9).
Cheers!
hakaz said:
Ad 1. Till now rooting on our P9 works through injection of the su mounting routine into the kernel in boot section (if using a modified kernel + su installation or modifying the kernel during su installation itself doesn't make a difference). So any su installation modifies the boot section and you mess things up if you try to install another su on top of the other. Therefore reverting to the original boot image is mandatory before installation of another su.
Ad 2. The su is compiled against different platforms​ not phones (in our case arm64). So @Chainfire has the different platform variations in his package. The "shady" package in our case is basically the v2.79 stable version of 12/20 2016 (you can unpack both packages and compare them against each other, they are bit for bit equal) but has an P9 specific injection routine to modify the kernel. After installation you have pure su v2.79 stable on board - not more, not less.
Sorry, "normal" SuperSU packages won't work due to lacking the kernel modification (phh uses a modified kernel instead you have to flash separately on P9).
Cheers!
Click to expand...
Click to collapse
Thanks buddy! I flashed systemless supersu, and stucked in infinite bootloop(it is only once in your post), probably because my model is EVA-AL00. I have to restore the previous boot.img.
ccaappton said:
Quick summary, I can not:
mount -o remount,rw /system in normal mode even with root permission. Error is "Device busy"
modify files in /system in twrp and keep it persistent. It somehow roll back to the stock state after reboot into normal mode.
I'm a long-time linux user, and fairly familiar with rooting in pre-nougat versions. My previous phone is Oneplus-X in LineageOS-14, and I could do whatever I like with the system partition. Recently I received a P9 as present. I updated the rom to B377 and flashed OldDroid's TWRP-3.1.0+phh su. But I can not find a way to modify the /system partition. I need to change a lot of things, like /system/etc/hosts, adding apk into /system/priv-app, etc.
Could someone help?
Click to expand...
Click to collapse
Same here with Oneplus 3T.
I just posted in another post (Google Pixel).
There I just guess it was a new encription way, now Im sure, all three devices with Android 7.1.1.....
Hi, I am trying to make some kind of "pre-Magisked" kernel, so that, when I flash that kernel already contains the necessary files to Magisk Superuser, avoiding the need to flash Magisk after each kernel flash.
I know the current script patches the ramdisk image when installing it, but I cant see which changes are executed exactly. Tried some of them resulting in bootloop
So, is there a way to create a pre-Magisked kernel or, at least, integrate basic files and later manually install Magisk Manager APK? There was a way to do it in Nougat with SuperSU which doesnt work with Oreo anymore...
bamsbamx said:
Hi, I am trying to make some kind of "pre-Magisked" kernel, so that, when I flash that kernel already contains the necessary files to Magisk Superuser, avoiding the need to flash Magisk after each kernel flash.
I know the current script patches the ramdisk image when installing it, but I cant see which changes are executed exactly. Tried some of them resulting in bootloop
So, is there a way to create a pre-Magisked kernel or, at least, integrate basic files and later manually install Magisk Manager APK? There was a way to do it in Nougat with SuperSU which doesnt work with Oreo anymore...
Click to expand...
Click to collapse
No its not possible to have a pre magisk'd kernel as magisk sets up files in /data/adb which you cannot do later on otherwise magisk will be non functional, you must flash the zip after wiping your data.