Database Develop

phone bricked

Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware

oudric said:
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
Click to expand...
Click to collapse
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.

internetpilot said:
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
Click to expand...
Click to collapse
can you please tell me steps i am so afraid to do anything to my phone now and i think my problem is same as yours
i downloaded 6.0.0 (MRA58R) and i used option in toolkit flash stock it gave me an error
"failed (data transfer failure (unknown error))

Its not so easy to brick nexus, but make sure you don't lock bootloader before your phone is working right. You can find the guide how to flash it on XDA.
You will need to flash the missing files by hand.

I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again

oudric said:
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
Click to expand...
Click to collapse
You don't need to move the files to the platform-tools folder.
Go to Nexus 6 General > Sticky rol-up thread > Adb and fastboot. What is it?
This will tell you how to set up and use adb or fastboot properly.

[ROM] TMO Z2 Force 27.1.3 FlashAll (October 2018 Version)

UPDATE 11-9-18: I have updated the FlashAll with the October edition of version 27.1.3. Yes, they updated the ROM but kept the same version number lol.
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from https://mirrors.lolinet.com (thank you!), unzipped it, used root junky's script to convert it (thank you!) and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Downloads
1. Updated October Flashall https://drive.google.com/open?id=1PczvmaVv19c91iOGhpNmhmfKyvDkz-ob (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall into a folder called "TMO Moto z2 force 27.1.3 flashall" Open a command prompt in the folder it created. Connect your phone to your computer via ADB.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit. This does not wipe user data.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above (if you use recovery).
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
Not Rooted and want to wipe everything?
Run flashall_erase.bat. It will boot into fastboot mode, update the partitions, and wipe everything.
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.

texasaggie1 said:
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from @xiyl (thank you!), unzipped it and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south.
Downloads
1. Flashall https://drive.google.com/open?id=1HK2zssCGlPTD5m2A_SAD-RjrQDfmZMTR (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall. It will create a folder called "NASH_TMO_27.1.3" Open a command prompt in the folder it created.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance,
Click to expand...
Click to collapse
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.

kendallgreen said:
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
Click to expand...
Click to collapse
Sorry! It was late and I linked to the wrong thing. ? Try it now please.

texasaggie1 said:
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from @xiyl (thank you!), unzipped it and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Downloads
1. Flashall https://drive.google.com/file/d/1JKu5S7xvy8xvyCodLEt7olr8czP_8FUm/view?usp=drivesdk (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall. It will create a folder called "NASH_TMO_27.1.3" Open a command prompt in the folder it created.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.
Click to expand...
Click to collapse
I downloaded and unzipped the new NASH_TMO_27.1..3. I added the AdbWinApi.dll and AdbWinUsbApi.dll and got the flashall_then_recovery.bat to run. I didn't install the TWRP installer or Magisk but rebooted to recovery and then system. After several restarts due to unlocked bootloader warning, it came back to build number OCXS27.1.2 kernel [email protected]#1 Fri Apr 20 09:21:27 CDT 2018. Android security level May 1, 2018. Android version 8.0.0 However, all of my apps were retained except Messaging .

kendallgreen said:
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
Click to expand...
Click to collapse
kendallgreen said:
I downloaded and unzipped the new NASH_TMO_27.1..3. I added the AdbWinApi.dll and AdbWinUsbApi.dll and got the flashall_then_recovery.bat to run. I didn't install the TWRP installer or Magisk but rebooted to recovery and then system. After several restarts due to unlocked bootloader warning, it came back to build number OCXS27.1.2 kernel [email protected]#1 Fri Apr 20 09:21:27 CDT 2018. Android security level May 1, 2018. Android version 8.0.0 However, all of my apps were retained except Messaging .
Click to expand...
Click to collapse
So try it again but this time just do the regular flashall.bat. it should work this time.
It sounds like you are installing this to slot a but your phone is running in slot b. If doing it this way doesn't fix it just look on here for the command to switch your phone from one slot to another.

success. I tried the flashall.bat and got the system updated to 27.1.3. I noticed that when I fastboot --set-active=_a, I had 27.1.2 and with --set-active=_b, I had to restart the phone because it was stuck at the unlocked bootloader warning. thanks.

kendallgreen said:
success. I tried the flashall.bat and got the system updated to 27.1.3. I noticed that when I fastboot --set-active=_a, I had 27.1.2 and with --set-active=_b, I had to restart the phone because it was stuck at the unlocked bootloader warning. thanks.
Click to expand...
Click to collapse
awesome! The whole a/b partition thing can be quite annoying

great job man glad someone did this i was about to try thanks

worked great but i reflashed remove encryption oreo also i didnt know if it was a necessary was being safe you made it easy no fastboot lol great work

My Fellow Texan.....
THANK YOU.
My phone has been in a weird limbo for months. I was on AOSIP ROM but it wasn't rooted, I couldn't use any moto mods and I couldn't install anything because TWRP wasn't installed and it wouldn't let me install it, either. I now have TWRP, but it's showing no baseband. So I'm gonna attempt to fix that but I'm already in a better place than I was. Thanks again, brother.

if you need baseband its easy to fix i had the same issues i was testing kernel its eas fix if you need i can help fix ive bricked and tried everything works easy check last post put on this https://forum.xda-developers.com/z2-force/development/pantheon-kernel-alpha-t3805977

My Tmo box is rooted, presently running the original 27.1 release.. I've been getting the OTA update notifications for 27.1.2.
Do we know if I can skip 27.1.2 and jump straight to the 27.1.3 release? I'd love to be able to do this flash-all and put the update notifications to bed for a while.

dismembered3po said:
My Tmo box is rooted, presently running the original 27.1 release.. I've been getting the OTA update notifications for 27.1.2.
Do we know if I can skip 27.1.2 and jump straight to the 27.1.3 release? I'd love to be able to do this flash-all and put the update notifications to bed for a while.
Click to expand...
Click to collapse
It should be fine to skip revisions.

StonedYoda said:
My Fellow Texan.....
THANK YOU.
My phone has been in a weird limbo for months. I was on AOSIP ROM but it wasn't rooted, I couldn't use any moto mods and I couldn't install anything because TWRP wasn't installed and it wouldn't let me install it, either. I now have TWRP, but it's showing no baseband. So I'm gonna attempt to fix that but I'm already in a better place than I was. Thanks again, brother.
Click to expand...
Click to collapse
If you are on tmobile, flashing the firmware flashall from the aosip thread to get baseband back.

mookiexl said:
If you are on tmobile, flashing the firmware flashall from the aosip thread to get baseband back.
Click to expand...
Click to collapse
If that doesn't work let me know. It should though. You may have to re-root after his suggestion

I'd been avoiding updates because I just didn't want to deal with rooting again and restoring data, etc. This was great!

(bootloader) slot: not found this is what I get with every fastboot command.

I was having the same issue... I was on 27.1.2 and kept getting notified to update, but it kept failing. I'm rooting with Magisk (16.0 initially but then up to 17.1) and it wouldn't update. Thanks to this thread, I ran the flashall_then_recovery.bat and it worked a treat!!! Thank you TexasAggie!

TWRP Installer link is down
The link to the TWRP installer is timing out when loading and comes up with an error message. Is it possible to install the 27.3 update using adb and then flash magisk in the temp twrp? Thanks for your work bro!
UPDATE:
I tried and now I'm stuck in bootloop. I can still get to twrp using adb and did a wipe but it's still stuck in loop land. Do I need to be rebooting in TWRP from slot A or B? This is my first phone that has dual partitions and I am a bit confused by it. Any suggestions? THANK YOU!!
UPDATE:
Tried your flashall update a second time and it worked with no bootloop issue, was able to flash magisk and obtain root again too.

climbhigh77 said:
The link to the TWRP installer is timing out when loading and comes up with an error message. Is it possible to install the 27.3 update using adb and then flash magisk in the temp twrp? Thanks for your work bro!
UPDATE:
I tried and now I'm stuck in bootloop. I can still get to twrp using adb and did a wipe but it's still stuck in loop land. Do I need to be rebooting in TWRP from slot A or B? This is my first phone that has dual partitions and I am a bit confused by it. Any suggestions? THANK YOU!!
UPDATE:
Tried your flashall update a second time and it worked with no bootloop issue, was able to flash magisk and obtain root again too.
Click to expand...
Click to collapse
Glad to hear that!

[bounty] Requesting root + twrp for US version moto z3 play

$50 available via the crypto currency of YOUR choice.
Request: root. Tethered root is ok. Magisk systemless safteynet passing persistent root via zip flashing using persistent twrp is preferred, naturally.
This phone is AMAZING. Also the one sold from motorola.com is bootloader unlockable. The Amazon one is not.
To verify: if you got your z3 play from carrier or Amazon it is not bootloader unlockable.
If you bought from Motorola.com it is bootloader unlockable.
Battery without Moto mod is the best I have ever seen. Screen is amazing. Microsd slot, this is a really good feature. This is what my s9 plus should have been. No bloatware. I only want root for systemwide adblocking. (Adguard systemstore certificate)
With the Moto battery mod you can't run out of battery in a day. It's the best. Hopefully we will get unofficial custom rom someday so I can use Xposed and microg. You would be surprised how much telemetry even "stock like" roms have.

tomkleeeb said:
$50 available via the crypto currency of YOUR choice.
Request: root. Tethered root is ok. Magisk systemless safteynet passing persistent root via zip flashing using persistent twrp is preferred, naturally.
Click to expand...
Click to collapse
An attempt was already made. Using the firmware image someone linked here, I attempted to build and flash a TWRP for the Z3 Play I bought from Best Buy.
The result was a hard brick. Device would no longer power on. (Never seen this before, so it was definitely worth documenting for the TWRP chat)
Got a replacement Z3 Play, rebuilt TWRP but booted the firmware. Hard hang. Tried booting just the boot.img from the firmware image... also a hard hang.
So the software that we have now is not compatible with the Z3 Play.
Root and TWRP will come easily once we have an official image for the phone. It's unlocked, that's usually the hard part. Just gotta wait for Motorola to release the files or source first.

twelfth said:
An attempt was already made. Using the firmware image someone linked here, I attempted to build and flash a TWRP for the Z3 Play I bought from Best Buy.
The result was a hard brick. Device would no longer power on. (Never seen this before, so it was definitely worth documenting for the TWRP chat)
Got a replacement Z3 Play, rebuilt TWRP but booted the firmware. Hard hang. Tried booting just the boot.img from the firmware image... also a hard hang.
So the software that we have now is not compatible with the Z3 Play.
Root and TWRP will come easily once we have an official image for the phone. It's unlocked, that's usually the hard part. Just gotta wait for Motorola to release the files or source first.
Click to expand...
Click to collapse
Can you dump boot.img from the same devise, then fastboot boot boot.img?
If that works...
Could you then use magisk to add systemlessly root to the boot image
Then fastboot boot patched boot.img for tethered root?
This thread shows dumping partitions
https://forum.xda-developers.com/showthread.php?t=2450045

tomkleeeb said:
Can you dump boot.img from the same devise, then fastboot boot boot.img?
Click to expand...
Click to collapse
Not without root.
tomkleeeb said:
This thread shows dumping partitions
https://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Also from that thread:
TheThread said:
Pr-requirement:
- Rooted device.
Click to expand...
Click to collapse
You need root to get boot.img from a device to build TWRP.
or.
You need firmware images to be released by Motorola to build TWRP with the boot.img they release.
or.
You need source.
No way around it.

twelfth said:
You need source.
No way around it.
Click to expand...
Click to collapse
I made a thread on their official forums. https://forums.lenovo.com/t5/Moto-Z...this-phone-D/m-p/4176309/highlight/false#M200
This may seed things along.

if you boot into bootloader and run fastboot getvar all you'll see that our firmware is based on LA.UM.6.2.r1-07200-sdm660.0
so this should be our (incomplete) kernel source
https://source.codeaurora.org/quic/la/kernel/msm-4.4/tag/?h=LA.UM.6.2.r1-07200-sdm660.0
search for LA.UM.6.2.r1 on https://wiki.codeaurora.org/xwiki/bin/QAEP/release and you'll see all the updates we're missing since march

frantisheq said:
if you boot into bootloader and run fastboot getvar all you'll see that our firmware is based on LA.UM.6.2.r1-07200-sdm660.0
so this should be our (incomplete) kernel source
https://source.codeaurora.org/quic/la/kernel/msm-4.4/tag/?h=LA.UM.6.2.r1-07200-sdm660.0
search for LA.UM.6.2.r1 on https://wiki.codeaurora.org/xwiki/bin/QAEP/release and you'll see all the updates we're missing since march
Click to expand...
Click to collapse
I posted on GitHub asking for source.
Anyone wanna bump it?
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165

i have patched boot.img for 1929-8 using magisk manager apk from magisk 16.7.
not tested, i have locked bootloader.
if you have unlocked bootloader you can try "fastboot boot patched_boot.img" first without flash to see if it even boots. if it does you can try to flash it, extract magisk 16.7 zip and install apk from common folder.
https://drive.google.com/open?id=1n7Wf8ekChsDIUFmya0yFIRFQ581EIQxZ
if you brick your device you're on your own.
also i have sent boot.img to TWRP Builder, hopefully guys there can make a port from it.

frantisheq said:
i have patched boot.img for 1929-8 using magisk manager apk from magisk 16.7.
not tested, i have locked bootloader.
if you have unlocked bootloader you can try "fastboot boot patched_boot.img" first without flash to see if it even boots. if it does you can try to flash it, extract magisk 16.7 zip and install apk from common folder.
https://drive.google.com/open?id=1n7Wf8ekChsDIUFmya0yFIRFQ581EIQxZ
if you brick your device you're on your own.
also i have sent boot.img to TWRP Builder, hopefully guys there can make a port from it.
Click to expand...
Click to collapse
I have 1929-4 and unlocked the bootloader, tried it all, it's useless. (I used the boot of course from my version) Also I tried to port twrp but beyond the splash screen with the inscription twrp it did not work, and my knowledge in programming is almost equal to 0.

thought so. stock boot.img should boot with locked bootloader and it didn't.
ok i'll try to capture OTA url when it's available.

And yet I managed to get the root of the right through the magic and actually boot it. It was necessary in the magic to choose options for patch boot as far as I remember with encryption related, and it worked out))

frantisheq said:
thought so. stock boot.img should boot with locked bootloader and it didn't.
ok i'll try to capture OTA url when it's available.
Click to expand...
Click to collapse
Moto asked what version I need.... What version do we need to build root? https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165

this looks looks like a bad joke. we don't even need to ask them, there's GPL

frantisheq said:
this looks looks like a bad joke. we don't even need to ask them, there's GPL
Click to expand...
Click to collapse
I don't know. I just want root.
I think they can get away with it because source is available upon request, but no one requests it. I am surprised their GitHub doesn't have 1000s of people clamoring for source code for root. This thing is on my short list of phones. Op6/6T would be my next choice but I like microsd more than I like root friendly warrenty.

tomkleeeb said:
I don't know. I just want root.
I think they can get away with it because source is available upon request, but no one requests it. I am surprised their GitHub doesn't have 1000s of people clamoring for source code for root. This thing is on my short list of phones. Op6/6T would be my next choice but I like microsd more than I like root friendly warrenty.
Click to expand...
Click to collapse
Try to boot from my boot (fastboot boot root.boot.img) and if the system boots,you will see in the manager of magics that you already have the root rights, then you can safely flash this boot to yourself (fastboot flash boot root.boot.img) and it will be your root. But twrp recovery I can not yet port unfortunately.(And of course you need to have a bootloader unlocked)
https://drive.google.com/file/d/1wwD4J3DN4sYqfD1hOe0uApHC9tgqKIfu/view?usp=drivesdk

Willy33 said:
Try to boot from my boot (fastboot boot root.boot.img) and if the system boots,you will see in the manager of magics that you already have the root rights, then you can safely flash this boot to yourself (fastboot flash boot root.boot.img) and it will be your root. But twrp recovery I can not yet port unfortunately.(And of course you need to have a bootloader unlocked)
https://drive.google.com/file/d/1wwD4J3DN4sYqfD1hOe0uApHC9tgqKIfu/view?usp=drivesdk
Click to expand...
Click to collapse
Have to buy the phone first lol.
No root = no buy
I just like the idea of the ga!epad controller mod $79.99
Android has no good game controller

kernel source should be released by tuesday
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165#issuecomment-415027775

i have paid to download firmware for XT1929-8 and unlocked the bootloader.
the bad news, boot.img patched with Magisk won't boot, it just reboots.
the good news, stock boot.img worked so my phone works.
the best news, treble ResurrectionRemix system img for ARM64 a/b with gapps and su just booted up
https://forum.xda-developers.com/pr...pment/gsi-resurrection-remix-o-6-1-0-t3811299
i'm going to try pixel experience later
EDIT: sound works, dual sim works, wifi works, fingerprint works, navigation bar needs to be enabled in settings, battery moto mod seems to be not charging, unable to change display brightness
pixel experience won't boot (maybe it will, it's because i have downloaded a version instead of a/b). i'm back to stock ROM
EDIT2: got root working.
not sure if it's needed but i have used Magisk Manager from https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json
installed the apk
set up that URL as custom Update Channel in Magisk manager settings
patched boot.img with "Preserve force encryption" and "Preserve AVB2.0/dm-verity" checked
patched boot.img for xt1929-8 can be downloaded here https://drive.google.com/open?id=11CJ65ojDZmCQVZGSHXicfFSMaenFHiiv
now where is that $50? my donation button still works
EDIT3: got boot.img with working TWRP, but it won't boot Android just TWRP.
if you'd like to try fastboot flash boot_a recovery.img and choose recovery in bootloader menu.
be sure to have boot.img backup before flashing because it won't boot Android and TWRP is unusable as it is, it can't even mount data.
https://drive.google.com/open?id=1C3lcyK3y4RL1Ep56wqWpfw0VWIHuhiO0

Absolutely all the same thing I did with my 1929-4 three days ago ... with twrp the same situation unfortunately ...

i was able to flash magisk and boot.img so it works. still don't know why it won't boot android.
device/motorola/beckham - https://drive.google.com/open?id=1KQ8KFthPJzr1VXt41F9N7O7fY8IRzcb6

Help installing on Android 10 on Pixel 3axl

I posted this on GitHub but not sure which is the right place to post. Mods feel free to delete whichever one is inappropriate.
I don't think there is an issue with Magisk, however I am having trouble.
I just got my P3aXL brand new from Google. Here are the steps I took once I got my phone:
I updated to the latest October security patches using stock Android.
Once it was on the latest, enabled OEM unlocking inside android.
Rebooted to bootloader and unlocked.
Booted back into Android, setup my account.
Installed latest magisk manager (7.3.5)
Downloaded October system image (bonito-qp1a.191005.007).
Extracted boot.img from the large zip file
Copied boot.img to phone.
Inside magisk manager, clicked install, selected boot.img from phone.
Copied magisk_patched.img from download directory on phone back to my PC.
Rebooted to bootloader and ran fastboot flash boot magisk_patched.img.
From fastboot, ran fastboot reboot
At this point the system bootloops like 3 or 4 times, then stays in bootloader mode saying no valid boot slot. I can fix it by reflashing the factory image (removing the -w from flash-all.bat).
Not sure where to go from here.
I am on the latest version of the sdk tools (v29).
Any help debugging this issue would be great!
I am not new to rooting at all, so I'm comfortable with almost any tool/command line things I can try.

Question Fixed - Root help

It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!

jcunwired said:
It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!
Click to expand...
Click to collapse
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.

lewmur said:
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.
Click to expand...
Click to collapse
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip

jcunwired said:
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip
Click to expand...
Click to collapse
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?

lewmur said:
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?
Click to expand...
Click to collapse
Because I was in ADB and like you said, what difference does it make?

jcunwired said:
Because I was in ADB and like you said, what difference does it make?
Click to expand...
Click to collapse
The difference is that your post said you installed Magisk and used it to patch the boot.img and it didn't work. Then the edit said you solved it by using adb to sideload magisk and that solved the problem. I'm still trying to understand how it did.