Database Develop

PRA-LX1 Bricked (Command not allowed, package info failed)

My device: PRA-LX1 (Dual SIM version)
Got bricked. I was installing Google APPS on EMUI (Dumb) and it just kept on looping and restarting.
I decided to try the rescue zip and when I successfully restore it, it boots back to TWRP after I reboot to system.
My recoverys: TWRP (installed on recovery2) and Stock EMUI Recovery (installed on recovery)
Bootloader: Unlocked
Fastboot: Command not allowed
Thanks in advance for your reply.

Hello, is the FRP status on fastboot mode LOCKED or UNLOCKED
if it's UNLOCKED then you can unbrick it using fastboot to flash boot.img system.img and do a full wipe of your data partition.

RAR1991 said:
Hello, is the FRP status on fastboot mode LOCKED or UNLOCKED
if it's UNLOCKED then you can unbrick it using fastboot to flash boot.img system.img and do a full wipe of your data partition.
Click to expand...
Click to collapse
I already booted, that's good news!
Now I've got a problem. The famous unbrick guide everyone uses - the firmware is buggy for me.
Fingerprint scanner doesn't work - camera doesn't work and audio doesn't work.
I think this is a problem with the firmware as they are more models of the PRA-LX1?
Btw, how do I find mine?
Thanks
My model is the Europe unlocked dual sim one

NetfariousIntent said:
I already booted, that's good news!
Now I've got a problem. The famous unbrick guide everyone uses - the firmware is buggy for me.
Fingerprint scanner doesn't work - camera doesn't work and audio doesn't work.
I think this is a problem with the firmware as they are more models of the PRA-LX1?
Btw, how do I find mine?
Thanks
My model is the Europe unlocked dual sim one
Click to expand...
Click to collapse
try to download the right version for your phone from firmware finder and flash it using fastboot

RAR1991 said:
try to download the right version for your phone from firmware finder and flash it using fastboot
Click to expand...
Click to collapse
Oh, I think I have picked the right version, now I get the Update.app, how can I flash it now?
I'm such a noob, thank you for your answer.

NetfariousIntent said:
Oh, I think I have picked the right version, now I get the Update.app, how can I flash it now?
I'm such a noob, thank you for your answer.
Click to expand...
Click to collapse
you have to use Huawei update extractor to extract system.img boot.img recovery and recovery2 then flash them with fastboot
PS: Make a backup before trying anything
https://forum.xda-developers.com/showthread.php?t=2433454

thank you

RAR1991 said:
you have to use Huawei update extractor to extract system.img boot.img recovery and recovery2 then flash them with fastboot
PS: Make a backup before trying anything
https://forum.xda-developers.com/showthread.php?t=2433454
Click to expand...
Click to collapse
Only system, boot, recovery and recovery2?
What about modem, vendor, etc...?
Thanks

NetfariousIntent said:
Only system, boot, recovery and recovery2?
What about modem, vendor, etc...?
Thanks
Click to expand...
Click to collapse
in all tutorials that's all what they mentioned and you can't flash vendor.img from fastboot I've tried that but it returns (Command not allowed) I'm trying to convert vendor.img to flashable TWRP backup using Imgtool but I can't figure out how it works yet

RAR1991 said:
in all tutorials that's all what they mentioned and you can't flash vendor.img from fastboot I've tried that but it returns (Command not allowed) I'm trying to convert vendor.img to flashable TWRP backup using Imgtool but I can't figure out how it works yet
Click to expand...
Click to collapse
Hi, I've tried to flash my firmware. Now It bootloops for a while and then restarts and bootloops agian.
I guess I'm very unlucky.
Thanks

NetfariousIntent said:
Hi, I've tried to flash my firmware. Now It bootloops for a while and then restarts and bootloops agian.
I guess I'm very unlucky.
Thanks
Click to expand...
Click to collapse
I'm experiencing the same thing right now with my PRA-LA1 and the only way that I found to make it works is to install a TWRP recovery and root it. But I have a lot of bugs after that I've already created a thread for that if someone can help
[Help] Bugs after rooting PRA-LA1

Stuck in Oneplus logo. Can't access recovery. Fastboot working.

Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.

Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.

rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.

Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?

rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can

Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS

rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear

Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here

rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway

Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!

rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..

nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working

Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?

pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer

Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.

przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.

Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.

redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)

Broken camera. Bootloader unlocked on .202

I unlocked bootloader on Pie, .202 fw.
My camera preview is broken but I can take pictures.
Unable to find any fix for this. Isn't camera suposed to work when unlocking on pie?

Mustach said:
I unlocked bootloader on Pie, .202 fw.
My camera preview is broken but I can take pictures.
Unable to find any fix for this. Isn't camera suposed to work when unlocking on pie?
Click to expand...
Click to collapse
Are you sure you unlocked the bootloader on PIE .202?
BTW.
You could try the twrp camerafix together with the vbmeta parameters.

MartinX3 said:
Are you sure you unlocked the bootloader on PIE .202?
BTW.
You could try the twrp camerafix together with the vbmeta parameters.
Click to expand...
Click to collapse
100% I did. I tried camera fixes for twrp, also I tried magisk modules that are supposed to fix it. Nothing happened.
As it goes for the vbmeta parameters. I did change the parameters when flashing twrp. Maybe I did something wrong. I have no idea. 1st time rooting a Sony. Had one plus and huawei before.
Just to make sure. Can ypu point me to the right camera fix twrp zip and tell me wxactly what to do with vbmeta in case I did it wrong.
Thanks in advance man. Love your work.

Mustach said:
100% I did. I tried camera fixes for twrp, also I tried magisk modules that are supposed to fix it. Nothing happened.
As it goes for the vbmeta parameters. I did change the parameters when flashing twrp. Maybe I did something wrong. I have no idea. 1st time rooting a Sony. Had one plus and huawei before.
Just to make sure. Can ypu point me to the right camera fix twrp zip and tell me wxactly what to do with vbmeta in case I did it wrong.
Thanks in advance man. Love your work.
Click to expand...
Click to collapse
Thank you
Oh, just follow the TWRP instructions and everything is fine
And the camerafix is bundled in the twrp tar.gz file
Eerrm. Did you test the camera without the camerafix too?
Because since you unlocked it After .126 you should not need it and it should break your camera preview until you flash the vendor.sin via newflasher again.

MartinX3 said:
Thank you
Oh, just follow the TWRP instructions and everything is fine
And the camerafix is bundled in the twrp tar.gz file
Eerrm. Did you test the camera without the camerafix too?
Because since you unlocked it After .126 you should not need it and it should break your camera preview until you flash the vendor.sin via newflasher again.
Click to expand...
Click to collapse
Ok so now I flashed vendor with newflasher and rebooted, black camera preview. Then i went to change vbmeta parameters and flash camerafix, rebooted, Black preview. I don't even know what to do anymore.

Mustach said:
Ok so now I flashed vendor with newflasher and rebooted, black camera preview. Then i went to change vbmeta parameters and flash camerafix, rebooted, Black preview. I don't even know what to do anymore.
Click to expand...
Click to collapse
That's disgusting [emoji848]
Hmm, another approach would be to downgrade to Oreo and apply xperifix und a selinux permissive patch.

MartinX3 said:
That's disgusting [emoji848]
Hmm, another approach would be to downgrade to Oreo and apply xperifix und a selinux permissive patch.
Click to expand...
Click to collapse
Downgraded to oreo via flasher and I tried to install twrp. I install it. I flash magisk. and system won't boot. UGH.

Mustach said:
Downgraded to oreo via flasher and I tried to install twrp. I install it. I flash magisk. and system won't boot. UGH.
Click to expand...
Click to collapse
Did you wiped userdata?
(TWRP or userdata.sin)

MartinX3 said:
Did you wiped userdata?
(TWRP or userdata.sin)
Click to expand...
Click to collapse
yeah. keeps bootlooping on sony logo.

Mustach said:
yeah. keeps bootlooping on sony logo.
Click to expand...
Click to collapse
Did you use the OREO TWRP, the kernel installer.zip and the twrp installer.zip?

MartinX3 said:
Did you use the OREO TWRP, the kernel installer.zip and the twrp installer.zip?
Click to expand...
Click to collapse
yeah. forgot the kernel. Reinstalled the firmware, flashed twrp, kernel, and twrp.
Bootloops.
Turned it off. Tried to turn it on, now it says "Your device is corrupt. It can't be trusted and wont boot"
EDIT***
Cleared user data now that message is gone, but it still loops.

Mustach said:
yeah. forgot the kernel. Reinstalled the firmware, flashed twrp, kernel, and twrp.
Bootloops.
Turned it off. Tried to turn it on, now it says "Your device is corrupt. It can't be trusted and wont boot"
Click to expand...
Click to collapse
And did you flash magisk too?

MartinX3 said:
And did you flash magisk too?
Click to expand...
Click to collapse
Ofcourse

Mustach said:
Ofcourse
Click to expand...
Click to collapse
So you did exactly the steps in the instructions, full wiped your phone and used the kernel installer as first zip?

MartinX3 said:
So you did exactly the steps in the instructions, full wiped your phone and used the kernel installer as first zip?
Click to expand...
Click to collapse
hahah yes . stupid phone geez...

Mustach said:
hahah yes . stupid phone geez...
Click to expand...
Click to collapse
Hmmmm.
Does Oreo run without TWRP?
(And you didn't forget both vbmeta parameters?)

MartinX3 said:
Hmmmm.
Does Oreo run without TWRP?
(And you didn't forget both vbmeta parameters?)
Click to expand...
Click to collapse
it runs oreo without twrp. I didn't forget any parameters.
So I did th following:
Installed Oreo, booted it once to make sure it works.
flashed twrp.img
flashed vbmeta.img
rebooted to twrp.
flashed kernel, flashed twrp installer
rebooted to twrp.
flashed magisk.
reboot.
Bootloop.

Mustach said:
it runs oreo without twrp. I didn't forget any parameters.
So I did th following:
Installed Oreo, booted it once to make sure it works.
flashed twrp.img
flashed vbmeta.img
rebooted to twrp.
flashed kernel, flashed twrp installer
rebooted to twrp.
flashed magisk.
reboot.
Bootloop.
Click to expand...
Click to collapse
Hmmm, I am feeling lost.
Which device do you use?

MartinX3 said:
Hmmm, I am feeling lost.
Which device do you use?
Click to expand...
Click to collapse
XZ2 H8216

Mustach said:
XZ2 H8216
Click to expand...
Click to collapse
That's very weird, this device is confirmed to work. @Pandemic , do you have any clue?

XZ2 H8296 will not root.

Hi all. I have been trying to twrp and root my XZ2 for a week now with no success. I have the H8296 variant that came with the HK firmware but I messed that up so bad I had to fully flash another FW, specifically H8296_9.0_52.0.A.11.32_India. I'm in the USA but this was the latest FW I can find to download. I was unable to flash the US h8266 FW or any h8266 FWs...
Anyway, this is where I am at, stock FW as said above, android 9. I've followed every tutorial I can find on how to twrp and root. I can get to twrp no problem then after magisk is flashed all I get is boot loops. Something that is not mentioned anywhere is the very first option twrp asks about. "keep filesystem read only" or something along those lines. No where in any of the tutorials say what to do here. I've tried both options with no luck. I'm just at my wits end and feel like there's something wrong with my hardware. I've been rooting android since the droid 1 days, so this isn't new to me.
Any help would be greatly appreciated.
Thanks
(BTW I am on linux)

My H8296 is happy.
And the H8266 firmware did run fine too.
(Got delivered with hong Kong or Taiwan firmware)

MartinX3 said:
My H8296 is happy.
And the H8266 firmware did run fine too.
(Got delivered with hong Kong or Taiwan firmware)
Click to expand...
Click to collapse
What are you using to to flash to H8266? I've tried many versions of the xperia flasher and keep getting the "wrong device" error. I still cant even get root. Only bootloops.... Any advice based from my previous post?

darkreaper476 said:
What are you using to to flash to H8266? I've tried many versions of the xperia flasher and keep getting the "wrong device" error. I still cant even get root. Only bootloops.... Any advice based from my previous post?
Click to expand...
Click to collapse
I used xperifirm and newflasher from XDA.

MartinX3 said:
I used xperifirm and newflasher from XDA.
Click to expand...
Click to collapse
Same.. Newflasher was giving me an error. I finally got it to flash the latest H8266 tonight! So I went ahead and tried to install TWRP and root again following your post. I got to "Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img" then when rebooting back into TWRP its stuck on the Teamwin logo even after running " fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" again as specified. The phone still boots into android amazingly, so thats nice. lol
Any tips for when stuck at this point?
Thanks!

darkreaper476 said:
Same.. Newflasher was giving me an error. I finally got it to flash the latest H8266 tonight! So I went ahead and tried to install TWRP and root again following your post. I got to "Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img" then when rebooting back into TWRP its stuck on the Teamwin logo even after running " fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" again as specified. The phone still boots into android amazingly, so thats nice. lol
Any tips for when stuck at this point?
Thanks!
Click to expand...
Click to collapse
There is a "News" entry in the TWRP thread.
But nice to hear, that you finally got the H8266 firmware on your phone!

MartinX3 said:
There is a "News" entry in the TWRP thread.
But nice to hear, that you finally got the H8266 firmware on your phone!
Click to expand...
Click to collapse
Yes, I've read this post in geat detail many times looking for where I messed up haha. I did read the "dont flash TWRP" thing and thought it meant dont flash twrp from fastboot XD. OK, well I'll try and flash Magisk from the "fastboot boot twrp" and see if it bootloops like always.
EDIT: IT WORKED! Finally have a rooted stock rom. What a week. lol

darkreaper476 said:
Yes, I've read this post in geat detail many times looking for where I messed up haha. I did read the "dont flash TWRP" thing and thought it meant dont flash twrp from fastboot XD. OK, well I'll try and flash Magisk from the "fastboot boot twrp" and seeif it bootloops like always.
Click to expand...
Click to collapse
xD
Only fastboot boot will work for sure

MartinX3 said:
There is a "News" entry in the TWRP thread.
But nice to hear, that you finally got the H8266 firmware on your phone!
Click to expand...
Click to collapse
Hello Sir i need Your Help
My Phone Model H8296
i am Flash by this Model H8296 CONVERT TO H8266
Flash Done this File (H8266_Customized+CE1_1313-3193_52.0.A.3.84_R2B)
Android version 9.
Sir android 9 ROOT Possible ?
Now How To Flash TWRP & Root ?
please Help Me

[email protected] said:
Hello Sir i need Your Help
My Phone Model H8296
i am Flash by this Model H8296 CONVERT TO H8266
Flash Done this File (H8266_Customized+CE1_1313-3193_52.0.A.3.84_R2B)
Android version 9.
Sir android 9 ROOT Possible ?
Now How To Flash TWRP & Root ?
please Help Me
Click to expand...
Click to collapse
I use a H8296 with H8266 firmware as well.
Android 8 and 9 did work.
Android 10 is the newest stock.
Please use a newer Android with a custom rom.
Please follow the instructions.

Question Remote: partiotin (init_boot) not found [SOLVED]

Hi guys, just sideloaded the march OTA.
I was rooted and unlocked, but trying to reroot is getting difficult, i cannot flash the magisk_patched.img. Tried the classic " fastboot flash init_boot etc" but I get "FAILED (remote: partition (init_boot) not found).
Could you help me with that

What version of Platform Tools are you using?

r33.0.1
V0latyle said:
What version of Platform Tools are you using?
Click to expand...
Click to collapse

Dudeany said:
r33.0.1
Click to expand...
Click to collapse
Have you tried a different USB cable?

V0latyle said:
Have you tried a different USB cable?
Click to expand...
Click to collapse
Yes, the thing is, that I can see the device connected and adb tries to push the .img but that fails.
Ps. Just updated the platform tools and tried the same command init_boot with no result.
But trying "flash boot etc" was successful for "boot_b", but magisk is still not installed

Dudeany said:
Yes, the thing is, that I can see the device connected and adb tries to push the .img but that fails.
Ps. Just updated the platform tools and tried the same command init_boot with no result.
But trying "flash boot etc" was successful for "boot_b", but magisk is still not installed
Click to expand...
Click to collapse
ADB 33.0.3 is recommended due to issues with 34.0+.
Init_boot is the correct image to patch to root the Pixel 7.
What mode is your device in? Bootloader? Fastbootd?

V0latyle said:
ADB 33.0.3 is recommended due to issues with 34.0+.
Init_boot is the correct image to patch to root the Pixel 7.
What mode is your device in? Bootloader? Fastbootd?
Click to expand...
Click to collapse
Ok, I've downgraded to 33.0.3, I'm in bootloader mode.
Now I get a new message "warning: skip copying init_boot_b image avb footer (init_boot_b partition size: 8388608, init_boot_b image size: 67108864)

I think I solved it, I've patched the wrong .img
Gonna report as soon as I have time to check

Dudeany said:
I think I solved it, I've patched the wrong .img
Gonna report as soon as I have time to check
Click to expand...
Click to collapse
Make sure you're using the correct firmware, too. Panther for Pixel 7, Cheetah for Pixel 7 Pro. I believe the boot/init_boot images are similar but just to be safe...

V0latyle said:
Make sure you're using the correct firmware, too. Panther for Pixel 7, Cheetah for Pixel 7 Pro. I believe the boot/init_boot images are similar but just to be safe.
Click to expand...
Click to collapse
Solved, it actually was that i patched boot.img instead of init_boot.img, so the size difference.
Thank you very much for your help and time