9

Question - P7P cant get past bootloader after Magisk patch failure | XDA Forums

 2 years ago
source link: https://forum.xda-developers.com/t/p7p-cant-get-past-bootloader-after-magisk-patch-failure.4580553/#post-88475093
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Question P7P cant get past bootloader after Magisk patch failure

stslimited84

Senior Member
Dec 13, 2014
Hey,

I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:

When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot

When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)

I'm at a loss on how to correct the problem at this point. I've tried Pixelflasher but that fails also (I'm assuming from the same errors).

Any help is greatly appreciated as I'm without a phone until I fix this

Thanks in advance!!!!!
Last edited: Today at 1:39 AM
Hey,

I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:

When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot

When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)

I'm at a loss on how to correct the problem at this point. I've tried Pixelflash but that fails also (I'm assuming from the same errors).

Any help is greatly appreciated as I'm without a phone until I fix this

Thanks in advance!!!!!

I would suggest using PixelFlasher (from this sub-forum) with 33.0.3, you should be able to revive your phone.

schmeggy929

Recognized Themer
Hey,

I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:

When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot

When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)

I'm at a loss on how to correct the problem at this point. I've tried Pixelflash but that fails also (I'm assuming from the same errors).

Any help is greatly appreciated as I'm without a phone until I fix this

Thanks in advance!!!!!

I would go with Pixel Flasher. pretty simple program with a lot of options. Patching Magisk and a few clicks to install firmware.

stslimited84

Senior Member
Dec 13, 2014
I would suggest using PixelFlasher (from this sub-forum) with 33.0.3, you should be able to revive your phone.
Thanks for the response.

As i mentioned in the OP, I tried pixelflasher and it does not work. I believe its experiencing the same issues since its just UI executing the commands essentially.

stslimited84

Senior Member
Dec 13, 2014
I would go with Pixel Flasher. pretty simple program with a lot of options. Patching Magisk and a few clicks to install firmware.
I tried pixel flasher with no success
I tried pixel flasher with no success

Where are you getting your platform tools? Please tell me it's not a minimal adb thing and/or not from the android developers site...?

stslimited84

Senior Member
Dec 13, 2014
Where are you getting your platform tools? Please tell me it's not a minimal adb thing and/or not from the android developers site...?
using the standard kit from https://developer.android.com/tools/releases/platform-tools

weirdly enough, I've seen "sparse" or "partition" errors happen to members who ended up getting it working by changing the USB cord!

I might re-download platform tools (r33.0.3 of course), place it in a different location, and try there again. And/or re-download the factory firmware image but make sure to compare the checksums and make sure you're not trying to flash corrupted images...
*don't forget to remove the "-w" or your device will be wiped...

Hey,

I screwed up when patching the boot image for magisk on the latest stock rom update. I've attempted to reinstall the factory image but experience two different errors depending on which version of platform tools im using:

When I use 33.0.3 i get this error: fastboot: error: device requires partition vendor kernel boot which is not known to this version of fastboot

When i use 34.0.1 i get this error: Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)

I'm at a loss on how to correct the problem at this point. I've tried Pixelflasher but that fails also (I'm assuming from the same errors).

Any help is greatly appreciated as I'm without a phone until I fix this

Thanks in advance!!!!!

Go over to the Pixel Flasher thread and submit a support.zip. Maybe badabing can help diagnose.

Reactions: Fishawy

stslimited84

Senior Member
Dec 13, 2014
weirdly enough, I've seen "sparse" or "partition" errors happen to members who ended up getting it working by changing the USB cord!

I might re-download platform tools (r33.0.3 of course), place it in a different location, and try there again. And/or re-download the factory firmware image but make sure to compare the checksums and make sure you're not trying to flash corrupted images...
*don't forget to remove the "-w" or your device will be wiped...
I've downloaded both several times but ill try a new location. At this point, I dont care if the device is wiped, I just need it working. i can restore the apps from backups.

stslimited84

Senior Member
Dec 13, 2014
I was able to fix it by using the android flash tool in chrome. It was the only thing that would overcome the errors. Phone is up and running again.

Reactions: Fishawy

I was able to fix it by using the android flash tool in chrome. It was the only thing that would overcome the errors. Phone is up and running again.

Glad you got it sorted.


report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK