I mean they charge customers for a board replacement so that's clearly what they're doing. I'm sure they turn around and refurbish the board and use it for the next phone that comes in but out of warranty bricks that I've seen people complain about always mentioned Google charging them for a board replacement. It's very well possible that Samsung doesn't give Google access to their tools seeing how Google is a leaky faucet and everything ends up in public hands.
I’ll update you how mine goes
Interesting experience. But it’s really dumb that there’s no way to re-flash to stock with locked bootloader…
Are you using the command
fastboot flash init_boot <nameofpatchedinit_boot.img>?
Had to ask, I know you're posting in Pixel 7 Pro thread, just making sure, your device is Pixel 7 / 7 Pro?
Can you please issue the command
fastboot --versionMake sure you don't have any other/older versions of adb/fastboot on your computer and only the latest Platform Tools.
You had a typo earlier on
, instead of .
Please provide the out of these commands
adb --version
fastboot --version
where adb
where fastboot
dirOk you have a really old version in your path which is being picked up.
where adb and where fastboot so that I could tell your where is it being picked up from.
I know what your problem is, I'm trying to be helpful here, but I find it that you are either unwilling or unable to provide the information you're being asked.
where commands
Never just reset your phone and lock the booloader! ALWAYS FLASH FACTORY IMAGE FIRST! Then relock bootloader. For future reference!
Yeah
Thanks. It was in one of the XDA's manuals, and I first did and then thought that I've just killed it
This is exactly why this thread and the other thread not by @roirraW "edor" ehT should be closed because they're incomplete. This one even had the wrong Magisk flashing method for weeks before it was fixed.
forum.xda-developers.com
Depends on how you're applying.
You must be a mind reader, I was in the process of adding Disabling Verity and Verification to the OP.
github.com
I know what your problem is, I'm trying to be helpful here, but I find it that you are either unwilling or unable to provide the information you're being asked.
where commandsI assume you are talking about updating the Magisk version within the Magisk app (via direct install)? If so, Magisk does have the ability to find and patch the init_boot.img. Support for that was added back in March of last year.
github.com
I would add to it that doing it to both slots assures that the inactive slot does not have anything non stock on it.
