Hey folks,
I have rooted (magisk) OnePlus 8 phone with Android 11, w/o TWRP recovery. I'm trying to replace kernel with one of blue_spark, here's what I'm doing
1. Download zip file from https://github.com/engstk/op8/releases/tag/r112
2. Extract and unpack Image.gz
3. Unpack Magisk patched boot.img to /tmp (magiskboot unpack boot.img)
4. Replace kernel with unpacked Image (cp Image /tmp/kernel)
5. Repack boot.img (magiskboot repack boot.img boot-new.img)
6. Boot with boot-new.img (fastboot boot boot-new.img)
And here is when I'm getting into "QUALCOMM CrashDump Mode"
The same result if I build kernel from sources. Repacking boot.img with original kernel works, so problem is unlikely in magiskboot.
I'm trying to figure out the problem, but without kernel logs it's troublesome. Any ideas?
Thanks.
Hm... It looks like, I also have to update DTB. After that device boots successfully. Seems a bit strange to me. What's the difference in supported devices between blu_spark and stock kernel?
Ok, turned out AVB was enabled in the original device tree:
fsmgr_flags = "wait,slotselect,avb";
Switching it off fixes boot process.
Related
This may seem an already (10 times) solved question, but I'm unable to boot my Mogo G with a custom boot.img instead of the one flashed on the device.
The phone is an XT1032, currently running KitKat 4.4.4, and I use the latest SDK tools.
I download the stock firmware from sbf.droid-developers.org/phone.php, where I choose RETAIL-FR_FALCON_KLB20.9-1.10-1.24-1.1_cid7_CFC_1FF_SVC.xml.zip
I extract the boot.img file using standard unzip tools, and the zImage and initrd.img files using abootimg
Code:
adb reboot-bootloader
The phone reboots and gets to the fastboot menu
Code:
fastboot boot zImage initrd.img
The console output seems right:
Code:
creating boot image...
creating boot image - 6975488 bytes
downloading 'boot.img'...
OKAY [ 0.336s]
booting...
OKAY [ 0.244s]
finished. total time: 0.580s
The device tries to reboot, but stops at the first "M Powered by Android" splash screen
I wait one minute
I hard reboot the device by holding the power button
The device reboots, but has to pass an unusual step, "Updating Android/Optimization application ..."
I'm quite sure the same method was successful a few months ago, so what has since changed:
The device's firmware was upgraded from 4.4.3 to 4.4.4
The SDK tools were upgraded from ? to 23.0.2
I don't remember whether the firmware was available as a tar.gz or a xml.zip file, but I think it was a tar.gz, and I'm near certain I then used the SDK provided fastboot tool. Today, the firmware is available as an xml.zip file, and I think I have to use the Motorola specific fastboot tool (anyway I've tried both, for identical results)
Could anyone point me toward what I'm missing or doing wrong ?
Thanks.
Why did u extract the boot.img?
Maybe wrong kernel?
And whats about the kernel modules of your custom kernel?
sub77 said:
Why did u extract the boot.img?
Click to expand...
Click to collapse
I simply want a basic way to boot a custom initial ramdisk, without flashing it to the device. So I download the stock firmware archive, unzip it, extract the initial ramdisk (initrd.img) from the boot image, modify it, and repack it using abootimg.
And then:
Code:
fastboot boot zImage initrd.img
For me, this command conform to both the SDK provided fastboot and the Motorola specific one shows in it's help message:
Code:
boot <kernel> [ <ramdisk> ]
I'm not sure anymore of the above command's correctness:
Some information may be missing, as when you expand the boot image (boot.img) you get three files : a kernel (zImage), an initial ramdisk (initrd.img), but also some metadata (in bootimg.cfg); and this metadata is lost when I use "fastboot boot zImage initrd.img". I may try to give this information using additional fastboot options
I even suspect that a few months ago, I used fastboot with a full boot.img image as parameter, though this does not seem to fit the help message above
sub77 said:
Maybe wrong kernel?
And whats about the kernel modules of your custom kernel?
Click to expand...
Click to collapse
As I told you, I'm not currently working on the kernel, and I'm testing with _unmodified_ kernel image (zImage) and initial ramdisk (initird.img), as extracted by "abootimg -x".
Again, any idea is welcome.
I have compiled a kernel based on arter97's (arter97 kernel Q branch on github) source code, that boots after the Android 10 update.
You may download the boot.img here and it comes pre-rooted.
https://gofile.io/?c=rnrqeR
Boot it with fastboot:
fastboot boot boot.img
After boot, open the Magisk Manager app, and click "install" to install magisk on your original Android 10 because we just booted the boot.img temporarily.
However, I would recommend that you use this boot.img as it is ultra-optimized, nevermind that the kernel version is "4.14.148-omghax-r30-g00c3703790a1", I just shared the one I use personally without building a new one.
1. Disable RAM Boost (This kernel removed the code for it to make it faster)
Code:
Settings->System->Ram Boost->Off
2. Reboot to bootloader
3. Install the boot.img:
Code:
fastboot flash boot boot.img
Good luck!
If anyone requests instructions to build this kernel yourself, feel free to post a request and I will share the instructions.
Hi,
It reboots to fastboot here.
Thank you.
This worked for me.
While I was trying to install GApps for Lineage OS 18.1 on my Nokia 7.2, I always lost my wi-fi. This is apparently due to flashing TWRP as boot image, which replaces the stock boot messing with wi-fi as the boot image has thee kernel.
Although, I did figure it out, it took me three days to get a proper solution from multiple sources. Here, I will explain how to install Lineage OS 18.1 on Nokia 7.2 with Gapps and Magisk. This can be applied to other ROMs as well. I am assuming you are on stock firmware.
Requirements:
Any custom ROM without GApps
vbmeta file
vendor image
Gapps zip file of your choice
platform-tools
twrp image
magisk file
payload dumper tool
Preperation:
The wifi stops working because we change the boot image. To prevent this, we must flash the boot image of the rom after we are done with our work with TWRP
For this, we ,ust get the boot image for the ROM. As this is not available readily, we must extract it from the ROM zip
Install latest python on your pc
Get the payload dumper tool from the link given below. Extract the contents into the root directory of python. It should be in C:\Users\USER-NAME\AppData\Local\Programs\Python\Python <version number>
Extract the ROM zip into any folder. Copy the payload.bin file and paste it in the folder where you put the payload dumper tool
Open a command prompt in the python root folder and type
Code:
python -m pip install -r requirements.txt
Then type
Code:
python payload_dumper.py payload.bin
After it finishes, go to the folder named Output inside the python folder. Here there will be a file named boot.bin. Rename this as lineage_boot.bin and paste it into the platform tools folder
Installation:
Download the twrp image, rename it to twrp.img and place it in the platform-tools folder. Connect your phone to the computer, switch on usb debugging on your phone.
Open command shell in the platform-tools folder and type
Code:
adb reboot bootloader
. In the bootloader, type
Code:
fastboot flash boot_b twrp.img
.
Next, type
Code:
fastboot --set-active=b
and then reboot to recovery using volume buttons and selecting using power button
In TWRP swipe to allow modifications. Copy your ROM and vendor image files to your SD Card. Now, click wipe, format data and type yes. Go back to home screen and the press install. Select your ROM file and install it. Sometimes it is required to flash vendor image. In that case flash that too. This step is required for Lineage OS 18.1
Now on the twrp home screen, tap on reboot. At the bottom, the current slot should be B. Tap slot A. THis changes the active slot to A. Now go back and tap on bootloader, this should boot you to the bootloader.
Take your vbmeta.img file and place it in the platform tools folder. Now, while in the bootloader mode, type,
Code:
fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
Next type
Code:
fastboot flash boot_a twrp.img
and boot to recovery using volume buttons
Now, press install in TWRP and select install and install the GApps file and reboot to bootloader
Next, in the bootloader type
Code:
fastboot flash boot_a lineage_boot.img
. Now start your phone. You should have lineage os with GApps
Installing Magisk:
Copy the lineage_boot.img into your phone. Download magisk.apk file from the link given below
Install the magisk app and open it. If it asks for additional setup select no. Beside the magisk option select install. Under options, if Recovery Mode is selected, deselect it and click next.
Now click on Select and patch a file under method. Select the lineage_boot.img
The patched image will be saved in downloads folder. Rename this file to lineage_magisk.img and copy it to the platform tools folder on your computer. Reboot your phone to bootloader mode
On your computer in the command window opened in the platform tools folder, type,
Code:
fastboot flash boot lineage_magisk.img
Reboot and you will have a rooted lineage os with GApps
Files:
Lineage OS 18.1 and vbmeta.img
TWRP
vendor
NikGApps
Payload Dumper tool
platform tools
Magisk
Guides that I Followed:
Extracting boot.img from ROM zip
Installing magisk using patched boot image
Credits:
Raghu varma for Lineage OS 18.1 port and twrp
Providers of the guides mentioned above
Hi @Ujwal2000 thanks for the guide.
I am using the stock android 10 rom and magisk patch method.
This also leads to non working wifi and magisk does not recognize that its installed.
Which steps of your guide apply to the stock rom?
i do not need gapps nor twrp I guess I only wanted to root the stock rom with magisk.
For stock, use this guide. They maintain a repository if patched boot images
Guide - How to root the Nokia 7.2 and Nokia 6.2 using Magisk
Nokia 7.2 and Nokia 6.2 come with an unlockable bootloader. The thing that compliments unlocked bootloader best is root access. So, this guide will help you in rooting the Nokia 7.2 or Nokia 6.2. You have a choice between Magisk patched boot images and TWRP recovery. I’d recommend going the...
www.techmesto.com
@Ujwal2000 , can you please look at my posting here? Thank you.
after fallowing the steps(except installing lineageOS with twrp flash everything was encrypted even tough i have the bootloader unlocked, managed to install it via adb sideload) the wifi doesnt work at all. When i try to turn it on is switches off on its own. Do anyone know a fix?
i had problem with latest version of python (3.10), version 3.7 was working for me
It was modified from latest stock kernel of WearOS 2.
Features:
[OC] Overclocked to 1.8Ghz
[Magisk] Magisk v23.0 pre-installed
How To Use :
Reboot to fastboot
You are supposed to try it first in order to make sure it is suitable to your system by using
Code:
fastboot boot boot.img
If your test is passed, you could input the command below to flash it
Code:
fastboot flash boot boot.img
Enjoy
Download Link: MEGA
Cannot get it to work on my W200, stuck on LG logo and heating up considerably
Xspeed said:
Cannot get it to work on my W200, stuck on LG logo and heating up considerably
Click to expand...
Click to collapse
Sorry for having forgotten that the fstab in the ramdisk was modified in order to support the system partition which had been formatted to ext4 by myself.
You could use magiskboot to edit the boot.img by yourself. Just replace the kernel and kernel_dtb by the one unpacked from the stock boot.img and then repack the image file.
Prebuilt magiskboot can be checked here: https://github.com/TeamWin/external_magisk-prebuilt/tree/android-11/prebuilt
If available, I will reupload the correct version in several month.
If I run
Code:
fastboot boot twrp.img
Spoiler
TWRP
my 7Pro boots into TWRP
But if I run
Code:
fastboot boot lineagerecovery.img
Spoiler
Lineage Recovery
it boots the ROM; I think because this image file include a Kernel but the TWRP img file not.
I would like to get the same behavior of TWRP img file with Lineage Recovery img file.
So, presuming I'm right, there is any way to make a recovery.img file, extracting it from a boot.img file?