Develop Bugs

Bricked Pixel C?

Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?

I used Nexus Root Toolkit when I got semi-bricked.

Use erase Command on flashboot for data and system then do flash_all again

As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78

NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.

Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)

hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...

hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!

d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.

cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?

hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip

d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.

d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"

hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106

d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.

hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.

Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.

how to unlock bootloader????

im getting the pixel 2xl tomorrow from google. .. i want unlock bootloader . could someone that has success unlocking boatloader, please make a quick step by step guide for windows.
i have latest ADB installed in windows.

Should be the same as the XL. Go into fastboot and type in:
fastboot flashing unlock
fastboot reboot

first go to developer settings and check oem unlocking

Same as the Pixel 1...

ok... i thought i read it was different somewhere. i been trying to find post.

in google site they have an extra line https://developers.google.com/android/images#taimen
''
If necessary, unlock the device's bootloader using one of the following methods:
If you are updating a Nexus or Pixel device that is manufactured in 2015 or later, run this command:
fastboot flashing unlock
For some devices, for example, Pixel 2 XL, the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command:
fastboot flashing unlock_critical
"
what is this unlock critical thing

abogrhen said:
in google site they have an extra line https://developers.google.com/android/images#taimen
''
If necessary, unlock the device's bootloader using one of the following methods:
If you are updating a Nexus or Pixel device that is manufactured in 2015 or later, run this command:
fastboot flashing unlock
For some devices, for example, Pixel 2 XL, the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command:
fastboot flashing unlock_critical
"
what is this unlock critical thing
Click to expand...
Click to collapse
http://www.androidpolice.com/2015/1...become-common-for-many-devices-in-the-future/
The critical unlock goes a step further and allows users to flash custom bootloaders, which are usually only necessary for removing certain security restrictions or occasionally for adding special features.
Click to expand...
Click to collapse
Huh...

subhumanderelict said:
http://www.androidpolice.com/2015/1...become-common-for-many-devices-in-the-future/
Huh...
Click to expand...
Click to collapse
thanks
so critical only for flashing other bootloader
which is something i never heard before

Can anyone confirm whether running fastboot flashing unlock_critical will wipe your device? I've already run fastboot flashing unlock, which of course does wipe the device, but now I need to know if this new command will do so as well. EDIT: After reading over that android police link, this appears to be nothing new so I doubt this will be required on the Pixel XL 2 now in order to have root since it wasn't required for the 6P or the OG Pixels. This could have changed with the new Pixels, so we'll have to figure out if the critical command is actually needed.

do you think the critical unlock would work against magisk in anyway? I just want to unlock so i can root and get adaway, but use magisk when available to still have android pay and netflix

Mr. Steve said:
Can anyone confirm whether running fastboot flashing unlock_critical will wipe your device? I've already run fastboot flashing unlock, which of course does wipe the device, but now I need to know if this new command will do so as well. EDIT: After reading over that android police link, this appears to be nothing new so I doubt this will be required on the Pixel XL 2 now in order to have root since it wasn't required for the 6P or the OG Pixels. This could have changed with the new Pixels, so we'll have to figure out if the critical command is actually needed.
Click to expand...
Click to collapse
i say
don't flash the unlock_critical
no one mention that it is needed
if in the future you need it (oh well backup and do it )
---------- Post added at 06:37 PM ---------- Previous post was at 06:31 PM ----------
fergdizzle9090 said:
do you think the critical unlock would work against magisk in anyway? I just want to unlock so i can root and get adaway, but use magisk when available to still have android pay and netflix
Click to expand...
Click to collapse
i "think"
the unlock_critical is not needed for now
you only need it is flashing a custom bootloader
but for anything else you don't need it
root- recovery -roms - oem update - original bootloader
at least that what the dev google site says

I'm still waiting for the TWRP boot loader to be ready for 2XL. Seeing that I'm probably getting the phone either the end of this week or next week, we still have time.

FYI...you don't have to unlock your bootloader to achieve root. You can still root a phone and have a locked bootloader. Unlocking the bootloader is to allow custom recovery flashing, such as TWRP. Personally, TWRP is a must for me and I always unlock my phone.

js042507 said:
FYI...you don't have to unlock your bootloader to achieve root. You can still root a phone and have a locked bootloader. Unlocking the bootloader is to allow custom recovery flashing, such as TWRP. Personally, TWRP is a must for me and I always unlock my phone.
Click to expand...
Click to collapse
how do you plan on rooting with a locked bootloader? I don't believe this is possible on the Pixel/Pixel 2.

ztotherad said:
how do you plan on rooting with a locked bootloader? I don't believe this is possible on the Pixel/Pixel 2.
Click to expand...
Click to collapse
Yeah, I guess you're right. It depends on the phone and root method. If you're using SuperSU or magisk you'd have to unlock the bootloader. IDK. Just forget everything I said. LOL

js042507 said:
Yeah, I guess you're right. It depends on the phone and root method. If you're using SuperSU or magisk you'd have to unlock the bootloader. IDK. Just forget everything I said. LOL
Click to expand...
Click to collapse
it'd be pretty awesome if someone found a way to root with a locked bootloader. I believe the S8/Note 8 has been rooted with a locked bootloader, now only if this was somehow brought into the world of the pixel. lol.

https://www.androidexplained.com/pixel-unlock-bootloader/

abogrhen said:
i say
don't flash the unlock_critical
no one mention that it is needed
if in the future you need it (oh well backup and do it )
---------- Post added at 06:37 PM ---------- Previous post was at 06:31 PM ----------
i "think"
the unlock_critical is not needed for now
you only need it is flashing a custom bootloader
but for anything else you don't need it
root- recovery -roms - oem update - original bootloader
at least that what the dev google site says
Click to expand...
Click to collapse
Unlock_critical is needed to even flash stock bootloader's. To flash 8.1 preview I had to unlock_critical to update the boatloader to even get passed. It's a required check.
Sent from my Pixel 2 XL using Tapatalk

bryantjopplin said:
Unlock_critical is needed to even flash stock bootloader's. To flash 8.1 preview I had to unlock_critical to update the boatloader to even get passed. It's a required check.
Click to expand...
Click to collapse
Does unlock_critical also wipe the device like regular bootloader unlock?

Jexx11 said:
Does unlock_critical also wipe the device like regular bootloader unlock?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 6 using Tapatalk

fastboot unlock vs fastboot unlock critical

When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...

Az Biker said:
When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...
Click to expand...
Click to collapse
Only if you want to update the bootloader. That's the only thing I can see that critical does.
Sent from my Pixel 2 XL using Tapatalk

I believe unlock_critical is necessary if you want to be able to flash updates manually..

"For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical
If you are updating an older device, run this command:
fastboot oem unlock "
Above quote is from Google Factory Image page.

thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!

Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:

Badger50 said:
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:
Click to expand...
Click to collapse
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel

Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:

Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck

Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?

Wickidmasshole said:
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck
Click to expand...
Click to collapse
This is why I asked the question. I wasn't sure if doing the basic unlock prior to the critical unlock would be an issue.
I'm running the critical unlock when I get home tonight (I want to be able to update the bootlader in the future), I'll let you know what I run into, if anything.

Az Biker said:
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?
Click to expand...
Click to collapse
Didn't use any toolkits, just these 2 guides....
https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176 https://forum.xda-developers.com/pixel-2-xl/how-to/guide-magisk-root-snoke-kernel-t3701930
....and didn't run into any problems at all. My P2XL is just humming right along. The battery on this thing is phenomenal! Takes me a good 2 days to knock it down to 10% :good:
Now we just need some TWRP to get Beans up and running :good::good:

Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.

iamjimmy said:
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.
Click to expand...
Click to collapse
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:

Badger50 said:
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:
Click to expand...
Click to collapse
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Sent from my [device_name] using XDA-Developers Legacy app

slaydog said:
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Click to expand...
Click to collapse
This one :good:

Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!

marbertshere said:
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!
Click to expand...
Click to collapse
I've unlocked the ordinary bootloader first, then the bootloader_critical without any problems :good:

I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?

jaybird779 said:
I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?
Click to expand...
Click to collapse
The bootloader_critical unlock has to be performed only if you want to flash the bootloader (e.g. when you flash a factory image), but, if you want to perform all the other operations, such as rooting, kernel flashing, etc., you have to unlock the ordinary bootloader, too.
So, these are the two Fastboot commands:
fastboot flashing unlock_critical (for bootloader flashing, you've already performed this)
fastboot flashing unlock (for all the other operations)
The request which appears on your phone, when you enter these two commands, is the same, and you have to allow the bootloader unlock in both cases :good:

Question Relock without MSM Tool

Is there no easy way to relock the bootloader without using the MSM Tool (which I've never done)? I relocked it in the normal way, fastboot oem lock, but that resulted in a "device is corrupt and will not boot" error. I unlocked it and it's fine, but... I want to re-lock it.

dmarden said:
Is there no easy way to relock the bootloader without using the MSM Tool (which I've never done)? I relocked it in the normal way, fastboot oem lock, but that resulted in a "device is corrupt and will not boot" error. I unlocked it and it's fine, but... I want to re-lock it.
Click to expand...
Click to collapse
On OOS? Run a full local upgrade to whatever your current version is and try again

Yeah, it was just running stock firmware... Ok, so full local upgrade and try fastboot oem lock again?
Worth a try I guess, thanks!!!

The local update is running now, hope it works since the MSM Tool gives me a "failed to start" "because of a side by side configuration" error... lol. Sheesh, never experienced trouble relocking a device before.

dmarden said:
Yeah, it was just running stock firmware... Ok, so full local upgrade and try fastboot oem lock again?
Worth a try I guess, thanks!!!
Click to expand...
Click to collapse
Just factory reset once and then lock from fastboot > fastboot OEM lock > Select Yes to confirm and the device will lock the bootloader and reboot into OS

No dice... same error... what the heck?!

Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.

null0seven said:
Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.
Click to expand...
Click to collapse
It wouldn't let me install the downgrade APK (maybe because it is not on A12), but I am downloading the downgrade/rollback package and will try it.

null0seven said:
Try a downgrade rom. This will wipe all in your phone & then re-lock.
The rom must be for your model/region.
Click to expand...
Click to collapse
No dice... I presume because it's an older version it needs that APK.

Ok... this is resolved, even if I don't know how. I literally just tried it a third time and it worked. *shrug*
Thanks to those that responded.

dmarden said:
Ok... this is resolved, even if I don't know how. I literally just tried it a third time and it worked. *shrug*
Thanks to those that responded.
Click to expand...
Click to collapse
This is how I always did it

General ROOT RED MAGIC 8 PRO V3.18

ROOT RED MAGIC 8 PRO V3.18​Your device must be bootloader unlocked
To unlock bootloader enable oem unlock in developer options and usb debugging
Then type the command: adb reboot bootloader
Or access fastboot with hardware key: Power + volume down
Once in fastboot type the following command to unlock:
fastboot flashing unlock
fastboot flashing unlock_critical"
Access fastboot then type the command:
fastboot flash init_boot_a magisk_patched-25200_3.18UN.img
fastboot reboot
Done
You check if the correct active slot is a, if it is b just change the command a with b
Only use for V3.18 version I have not tested other versions
Note: Absolutely do not patch the boot file, you will have a continuous boot error​

Root Done

The backups with just ommiting the B slots is 12.7 gb so i cant personally help you with that. Have you tried flashing the OTA's boot.img (might even try boot_a.img) and init_boot.img while slot A is selected? Not the magisk modded files either.

mcfizzlestag said:
The backups with just ommiting the B slots is 12.7 gb so i cant personally help you with that. Have you tried flashing the OTA's boot.img (might even try boot_a.img) and init_boot.img while slot A is selected? Not the magisk modded files either.
Click to expand...
Click to collapse
i flashed those 2 files but still can't boot the phone, go to logo then turn off the screen, can only go to fastboot and recovery, i sideload 47% it gives error
If you are rooted, please help me, I will send you coffee donate, please help me, full backup

I Pm'd you the backups now that i am at home, hopefully they help

Im at a stand still with this. I have already fastboot flashing unlock_critical as you can see in which it states Device already unlocked but whether I am in bootloader and fastboot I get Flashing is not allowed in a lock state. Any help from some else that ran into this or has knowledge on it?
Thanks
Update. Fixed the issue. Add the step of "fastboot flashing unlock" before "fastboot flashing unlock_critical"

If You can flash a GSI, It'd be a decisive factor in getting people to buy this phone. The company should be paying you to do this, but they're probably too greedy to make a bigger profit

I've successfully flashed a few A13 GSIs but screen lock is a still a problem and so far calls and messaging doesn't work normally.

I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance

Muriyata said:
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Click to expand...
Click to collapse
yes, you can return warranty

Muriyata said:
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Click to expand...
Click to collapse
Well once you unlock bootloader it clearly says warranty: void in fastboot so it probably is very easy to detect

edzchen said:
Well once you unlock bootloader it clearly says warranty: void in fastboot so it probably is very easy to detect
Click to expand...
Click to collapse
In that case, why op said that the warranty can still be returned after relocking the bootloader?
As you see, it is very connfusing... Some guys say yes, some others not. :s

edzchen said:
I've successfully flashed a few A13 GSIs but screen lock is a still a problem and so far calls and messaging doesn't work normally.
Click to expand...
Click to collapse
Could you please tell me the steps to flash A13 GSI roms. Thanks.

[email protected] said:
Could you please tell me the steps to flash A13 GSI roms. Thanks.
Click to expand...
Click to collapse
Unlock bootloader
Reboot into fastboot
Flash system with the GSI.img

Mr.PvT said:
i flashed those 2 files but still can't boot the phone, go to logo then turn off the screen, can only go to fastboot and recovery, i sideload 47% it gives error
If you are rooted, please help me, I will send you coffee donate, please help me, full backup
Click to expand...
Click to collapse
I have the same problem with my phone. Could you please tell me if you know find the solution to this. Thanks.

[email protected] said:
I have the same problem with my phone. Could you please tell me if you know find the solution to this. Thanks.
Click to expand...
Click to collapse
inbox me

Mr.PvT said:
inbox me
Click to expand...
Click to collapse
How can I inbox you?

Oh no... Can this be fixed?

Stusick said:
View attachment 5862143View attachment 5862145View attachment 5862147
Click to expand...
Click to collapse
Did you follow the instructions correctly, this error may have you flashed the wrong boot file, right?

Mr.PvT said:
Did you follow the instructions correctly, this error may have you flashed the wrong boot file, right?
Click to expand...
Click to collapse
Yes, I unlocked the bootloader first.
Then I flash boot and an error occurred.
Did I get a brick or is there hope?)