Using Nexus Toolkit and tried manually doing it in ADB.
I keep getting
FAILED (REMOTE FLASH WRITE FAILURE)
Over and over again. Halp? I looked it up and it seemed like some people had success in locking the device again for RMA, no such luck here
Rebel908 said:
Using Nexus Toolkit and tried manually doing it in ADB.
I keep getting
FAILED (REMOTE FLASH WRITE FAILURE)
Over and over again. Halp? I looked it up and it seemed like some people had success in locking the device again for RMA, no such luck here
Click to expand...
Click to collapse
You need to unlock it first.
Rebel908 said:
Using Nexus Toolkit and tried manually doing it in ADB.
I keep getting
FAILED (REMOTE FLASH WRITE FAILURE)
Over and over again. Halp? I looked it up and it seemed like some people had success in locking the device again for RMA, no such luck here
Click to expand...
Click to collapse
boot into fastboot mode and run:
Code:
fastboot oem unlock
this will wipe all data but its needed and not hard to get everything back.
after that, download the google stock image from here: https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz for the wifi only version and here https://dl.google.com/dl/android/aosp/razorg-kot49h-factory-49789b24.tgz for the mobile version.
if you have linux, google provides scripts in order to flash them.
goldflame09 said:
boot into fastboot mode and run:
Code:
fastboot oem unlock
this will wipe all data but its needed and not hard to get everything back.
after that, download the google stock image from here: https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz for the wifi only version and here https://dl.google.com/dl/android/aosp/razorg-kot49h-factory-49789b24.tgz for the mobile version.
if you have linux, google provides scripts in order to flash them.
Click to expand...
Click to collapse
Tried, fastboot hung at oem unlock, wouldn't do a damn thing. and tried to manually flash factory images via adb as well, same results.
Rebel908 said:
Tried, fastboot hung at oem unlock, wouldn't do a damn thing. and tried to manually flash factory images via adb as well, same results.
Click to expand...
Click to collapse
does this mean however that you can get the fastboot screen to show up?
goldflame09 said:
boot into fastboot mode and run:
Code:
fastboot oem unlock
this will wipe all data but its needed and not hard to get everything back.
after that, download the google stock image from here: https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz for the wifi only version and here https://dl.google.com/dl/android/aosp/razorg-kot49h-factory-49789b24.tgz for the mobile version.
if you have linux, google provides scripts in order to flash them.
Click to expand...
Click to collapse
goldflame09 said:
does this mean however that you can get the fastboot screen to show up?
Click to expand...
Click to collapse
Yeah I can get fastboot to show up. I've already set it off for RMA though.
Rebel908 said:
Yeah I can get fastboot to show up. I've already set it off for RMA though.
Click to expand...
Click to collapse
oh alright well good luck with it and hope you get a new functioning one
Related
Hi everyone.
After installing an OTA update my Nexus 5X entered in logo bootloop. The USB debugging is off and now I cant boot the phone to enable it.
He is still with OEM LOCK. I've tried the following steps:
- fastboot oem unlock -> says the oem unlock is not allowed
- fastboot flash ... -> device is locked cannot flash images
- OTA rescue https://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view -> success install, still bootloop
I can enter in bootloader normally, but any fastboot modify operation (format, flash, erase) i got that fkin message "device is locked"
Any idea how can i solve it? It may just be enabling USB debugging without boot up the phone or recovery to factory image. I have no data on it, I can delete/wipe anything.
FASTBOOT MODE
PRODUCT_NAME - bullhead
VARIANT - bullhead LGH790 16GB
HW VERSION - rev_1.0
BOOTLOADER VERSION - BHZ11b
BASEBAND VERSION - M8994F-2.6.33.2.06
CARRIER INFO - N/A
SERIAL NUMBER - xxxxxxxxxxxxxxxxxxxxxxx
SIGNING - production
SECURE BOOT - enabled
DEVICE STATE - locked
RECOVERY MODE
google/bullhead/bullhead
6.0/MDA89E/2296692
user/release-keys
Thanks a lot, sorry poor english, I´m brazilian.
try this to unlock
fastboot flashing unlock
to lock
fastboot flashing lock
@ricardolipka maybe try this:
http://forum.xda-developers.com/showthread.php?t=3251740
Sent from my SM-G930V using Tapatalk
Access recovery. Use ADB push command to push ota or custom ROM. Be careful to push bullhead ROM.
@jamelnassar "fastboot flashing unlock"
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.006s
@PiousInquisitor
My windows 10 not recognize my device in COM/USB ports as the photo. The N5X boot in download mode but is not recognized by windows. I tried on two different computers, multiple versions of LG driver.
@freq_ency
I cant use adb for push, just work when I select "Apply update by ADB". At this when I check "ABD devices" got this
List of devices attached
01a13ee8d892bf8c sideload
Any other tips?
This is giving me a big headache, spend hours trying to find a way to recover it.
How a simple OTA update can do this ****?
ricardolipka said:
@jamelnassar "fastboot flashing unlock"
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.006s
@PiousInquisitor
My windows 10 not recognize my device in COM/USB ports as the photo. The N5X boot in download mode but is not recognized by windows. I tried on two different computers, multiple versions of LG driver.
@freq_ency
I cant use adb for push, just work when I select "Apply update by ADB". At this when I check "ABD devices" got this
List of devices attached
01a13ee8d892bf8c sideload
Any other tips?
This is giving me a big headache, spend hours trying to find a way to recover it.
How a simple OTA update can do this ****?
Click to expand...
Click to collapse
Yeah fine! Your device is shown in PC monitor nah. Just sideload the update. If it says denied, just try using adb push. If didn't work you have go by tot file.
freq_ency said:
Yeah fine! You devices are shown in PC monitor nah. Just sideload the update. If it says denied, just try using adb push. If didn't work you have go by tot file.
Click to expand...
Click to collapse
I've tried all OTA update via sideload, still bootloop.
https://developers.google.com/android/nexus/ota#ryu here I got the updates, also tried the android N update, not good too.
Have you tried to wipe cache in recovery? If that doesn't work try a factory reset in recovery, but that will wipe your device so be forewarned.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Have you tried to wipe cache in recovery? If that doesn't work try a factory reset in recovery, but that will wipe your device so be forewarned.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for answer, yes both didnt work too. Several times tried...
ricardolipka said:
Thanks for answer, yes both didnt work too. Several times tried...
Click to expand...
Click to collapse
I hate to say this but I think your only option is to warrantee the device. I see you're from Brazil so that might be a problem.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I hate to say this but I think your only option is to warrantee the device. I see you're from Brazil so that might be a problem.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
It's a big problem to me. But I'll keep trying kkkk
Thanks =D
ricardolipka said:
It's a big problem to me. But I'll keep trying kkkk
Thanks =D
Click to expand...
Click to collapse
I thought it might be a problem. With a locked bootloader you're limited to using the stock recovery to sideload the ota or a factory reset. There really aren't any other options.
Sent from my Nexus 9 using XDA Free mobile app
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
I did see one user say he sideloaded a custom Rom in the stock recovery. I ready don't believe him but it's worth a try.
Sent from my Nexus 9 using XDA Free mobile app
Help！i can‘t flash anything into my tablet. fastboot failed, remote: unsupported comm
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Sway327 said:
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Click to expand...
Click to collapse
Are you sure that you can't reboot in twrp ..did you already try to do it manually ?
anyway if you want go back stock and you aren't able to use again NRT you need to flash manually a factory image from Google .Here is a the link with instructions ;
https://developers.google.com/android/nexus/images
if fastboot flash doesn't work you probably have fastboot locked.
brando56894 said:
if fastboot flash doesn't work you probably have fastboot locked.
Click to expand...
Click to collapse
Thanks mate. Do you know how to unlock fastboot?
ilpolpi65 said:
Are you sure that you can't reboot in twrp ..did you already try to do it manually ?
anyway if you want go back stock and you aren't able to use again NRT you need to flash manually a factory image from Google .Here is a the link with instructions ;
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks mate. Thanks for your reply. I tried mini ADB tool to flash it and got same result.
FAIL remote: unsupported command
Sway327 said:
Thanks mate. Thanks for your reply. I tried mini ADB tool to flash it and got same result.
FAIL remote: unsupported command
Click to expand...
Click to collapse
Are you able to get back into system? If so, run this command with an active ADB connection.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Sway327 said:
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Click to expand...
Click to collapse
Hi, I was wondering if you were able to fix your tablet. I have this problem right now and haven't found any way of fixing it.
NYCHitman1 said:
Are you able to get back into system? If so, run this command with an active ADB connection.
Click to expand...
Click to collapse
Hi. I was wondering if you know how to fix this only through fastboot. I get the same "remote: unsupported command" message when flashing partitions and "remote: image verification failed" when using "fastboot boot twrp.img" command. Right now, I have no recovery and cannot boot to system. Locking and reunlocking bootloader doesn't change a thing and I do have the latest drivers.
viii_xvi said:
Hi. I was wondering if you know how to fix this only through fastboot. I get the same "remote: unsupported command" message when flashing partitions and "remote: image verification failed" when using "fastboot boot twrp.img" command. Right now, I have no recovery and cannot boot to system. Locking and reunlocking bootloader doesn't change a thing and I do have the latest drivers.
Click to expand...
Click to collapse
Did you get your tablet to work? I have the same problem
qAnAthemA said:
Did you get your tablet to work? I have the same problem
Click to expand...
Click to collapse
No, I haven't gotten it to work. As far as I know, there is only one way to fix it and it involves opening up the tablet, as per this post.
viii_xvi said:
No, I haven't gotten it to work. As far as I know, there is only one way to fix it and it involves opening up the tablet, as per this post.
Click to expand...
Click to collapse
Have you tried to ask Google for a USB bootable recovery + ZIP file ?
I've gotten my Google Pixel 2 XL in a bootloop. When I use Toolkit to flash Factory Stock Image I get "your device is not set" then it goes back to the main menu.
I'd download factory image, extract it and run flash-all.bat
SSJMarkelous said:
I've gotten my Google Pixel 2 XL in a bootloop. When I use Toolkit to flash Factory Stock Image I get "your device is not set" then it goes back to the main menu.
Click to expand...
Click to collapse
This should help you
https://www.google.com/amp/s/www.androidexplained.com/pixel-sideload-update/amp/
ne0ns4l4m4nder said:
I'd download factory image, extract it and run flash-all.bat
Click to expand...
Click to collapse
it says failed.
mackentosh said:
This should help you
https://www.google.com/amp/s/www.androidexplained.com/pixel-sideload-update/amp/
Click to expand...
Click to collapse
nope it didnt work as well. =(
SSJMarkelous said:
it says failed.
Click to expand...
Click to collapse
I would suggest following the instructions listed on Google's site. You can also download the factory images from the same place: https://developers.google.com/android/images
I've bootlooped my phone as well (Google variant, not Verizon) and was able to restore it using the url I included above. One tip though: Back up your userdata (/sdcard) first. flash-all will wipe your userdata. Originally, I tried to restore the factory image by disabling 'wipe', but it wouldn't boot until I included 'wipe'
(I've never used toolkit though so I can't help you with that app.)
Edit: my flashing tool has been moved to it's own post:
[TOOL] Deuces Bootloop-Recovery & Flashing Script
SSJMarkelous said:
it says failed.
Click to expand...
Click to collapse
Did you unlock_critical?
When using flash-all it flashes the bootloader too. As far as I can tell you need to "fastboot flashing unlock_critical" before running "flash-all".
Deuces said:
Try my script: https://forum.xda-developers.com/showthread.php?p=74503983#post74503983
Click to expand...
Click to collapse
Didn't work.
r0adki111 said:
Did you unlock_critical?
When using flash-all it flashes the bootloader too. As far as I can tell you need to "fastboot flashing unlock_critical" before running "flash-all".
Click to expand...
Click to collapse
Tried and it didn't work.
So far i can only access fastboot, recovery mode, and if i do regular boot up it will get stuck at "google".
SSJMarkelous said:
So far i can only access fastboot, recovery mode, and if i do regular boot up it will get stuck at "google".
Click to expand...
Click to collapse
It's better if you give us specifics step-by-step on what you're doing and let us know if there are any steps where you're getting an error on, so we can help to better troubleshoot what you're doing wrong.
fastboot and bootloader mode is all you need. You should be running flash-all from bootloader, not recovery mode. Did you look at the url I posted earlier? Did you update your Android SDK files to the latest version?
Edit: my flashing tool has been moved to it's own post:
[TOOL] Deuces Bootloop-Recovery & Flashing Script
Without fail, when running the latest twrp, I get an error when flashing different rom zips. It's always the same error during step 1 and sometimes during step 2. I am on slot A when flashing the room, by the way.
The error just says it can't flash, there is no error code or description or anything like that.
When I was able to flash a rom, I tried to reboot into B for the vendor image, but none of my files were viewable, only folders with numbers and letters.
I'm confused, and I'm not a noob. I came from the regular Pixel and I was able to flash no problem.
stevew84 said:
Without fail, when running the latest twrp, I get an error when flashing different rom zips. It's always the same error during step 1 and sometimes during step 2. I am on slot A when flashing the room, by the way.
The error just says it can't flash, there is no error code or description or anything like that.
When I was able to flash a rom, I tried to reboot into B for the vendor image, but none of my files were viewable, only folders with numbers and letters.
I'm confused, and I'm not a noob. I came from the regular Pixel and I was able to flash no problem.
Click to expand...
Click to collapse
Is this when you fastboot into twrp, or do you have twrp already installed? Have you tried disabling screen lock before you enter twrp? And I assume you've run both bootloader unlocking commands as well?
This is when using skipsoft.
Do I need to run the critical flashing command manually or something? The reason I ask is because I'm not sure skipsoft does that.
I'd love to be able to flash alll this stuff without even using twrp but I'm not sure that's possible.
So I boot twrp, wipe and flash the ROM. But it fails right there. Is there a step I'm missing?
I do know how to flash individual images thru fastboot by the way, like when going to stock. Here is where I did do the critical flash command.
No I haven't tried to disable screen lock.
stevew84 said:
This is when using skipsoft.
Do I need to run the critical flashing command manually or something? The reason I ask is because I'm not sure skipsoft does that.
I'd love to be able to flash alll this stuff without even using twrp but I'm not sure that's possible.
So I boot twrp, wipe and flash the ROM. But it fails right there. Is there a step I'm missing?
I do know how to flash individual images thru fastboot by the way, like when going to stock. Here is where I did do the critical flash command.
No I haven't tried to disable screen lock.
Click to expand...
Click to collapse
Typically you need to have fully unlocked the bootloader with these 2 commands...
fastboot flashing unlock
and.....
fastboot flashing unlock_critical
Especially the critical, or else you won't be able to flash any roms. I don't know if skipsoft will do this. I know the Deuces scrip will. To find out what is/isn't unlocked run.....fastboot getvar all....
Then you'll know. If you have to unlock critical, which I think you will, it'll wipe your phone completely. So backup your files and such before you do :good:
Any manual methods that work? I mean to flash the roms.
stevew84 said:
Any manual methods that work? I mean to flash the roms.
Click to expand...
Click to collapse
I believe there is, but I can't find what it is. I think it's adb push (name of file) or adb sideload through twrp, butI could be wrong. Either way, you first need to be sure your fully bootloader unlocked before you can flash anything.
Badger50 said:
I believe there is, but I can't find what it is. I think it's adb push (name of file) or adb sideload through twrp, butI could be wrong. Either way, you first need to be sure your fully bootloader unlocked before you can flash anything.
Click to expand...
Click to collapse
Ok I almost forgot.
When I first unlocked the phone I was able to flash Nitrogen, both the ROM and twrp. But when I rebooted recovery to get to slot B, all I saw were various numbered and lettered folders. Looked like registry folders for Windows.
stevew84 said:
Ok I almost forgot.
When I first unlocked the phone I was able to flash Nitrogen, both the ROM and twrp. But when I rebooted recovery to get to slot B, all I saw were various numbered and lettered folders. Looked like registry folders for Windows.
Click to expand...
Click to collapse
Well that changes things a little. You at least have unlocked one partition then. And you can update factory images via fastboot? If so, then your fully unlocked. So you've got a twrp decryption error on slot B. You may want to disable screen lock security, and try again. You could also try fastbooting into twrp as well with screen lock also disabled.
Thanks. I'll try that out later.
But after I was unable to get into Nitrogen, I flashed stock manually and tried it all over. From this point I kept getting error after error in twrp.
After the errors, I got the Device is Corrupt screen, and freezing on the Google splash. From there I'd have to again start all over.
stevew84 said:
Thanks. I'll try that out later.
But after I was unable to get into Nitrogen, I flashed stock manually and tried it all over. From this point I kept getting error after error in twrp.
After the errors, I got the Device is Corrupt screen, and freezing on the Google splash. From there I'd have to again start all over.
Click to expand...
Click to collapse
Again, run the.....fastboot getvar all....and see what you get :good:
Thanks.
Badger50 said:
Again, run the.....fastboot getvar all....and see what you get :good:
Click to expand...
Click to collapse
Alright. I'm all unlocked and I disabled any sort of screen lock. I'm trying to flash Nitrogen now and seeing what happens...
and it failed again. I'm at a loss, I've never experienced this before.
The error is "updater process ended with ERROR: 1. Error installing zip........
Trying again because why the hell not. Maybe I'l try another TWRP version.
stevew84 said:
Alright. I'm all unlocked and I disabled any sort of screen lock. I'm trying to flash Nitrogen now and seeing what happens...
and it failed again. I'm at a loss, I've never experienced this before.
The error is "updater process ended with ERROR: 1. Error installing zip........
Trying again because why the hell not. Maybe I'l try another TWRP version.
Click to expand...
Click to collapse
Are you using the latest twrp from here? https://dl.twrp.me/taimen/
Also, you might want to try fastbooting the factory image with the -w removed from the flash-all.bat file to slot B. Then fastboot into twrp and try again. You will not lose any data by doing this.
Badger50 said:
Are you using the latest twrp from here? https://dl.twrp.me/taimen/
Also, you might want to try fastbooting the factory image with the -w removed from the flash-all.bat file to slot B. Then fastboot into twrp and try again. You will not lose any data by doing this.
Click to expand...
Click to collapse
I've read up on how to flash stock images without formatting data, but how would one flash directly to a particular slot? The only way I know how to get into a slot is through TWRP, but aren't there adb commands for this as well?
stevew84 said:
I've read up on how to flash stock images without formatting data, but how would one flash directly to a particular slot? The only way I know how to get into a slot is through TWRP, but aren't there adb commands for this as well?
Click to expand...
Click to collapse
In fastboot mode run...fastboot --set-active=a or b...
In your case select b.
Then, fastboot reboot bootloader
Now your on slot b, and can fastboot the factory image :good:
Badger50 said:
In fastboot mode run...fastboot --set-active=a or b...
In your case select b.
Then, fastboot reboot bootloader
Now your on slot b, and can fastboot the factory image :good:
Click to expand...
Click to collapse
Jesus christ. I'm in a cmd window right now, with the latest platform tools installed.
I ran the command just as you typed, (I'm in bootloader, bootloader version tmz20j by the way). Also, my bootloader version has changed a couple of times during all of this. It was tmz20bb, then tmz12g when I flashed the latest June image...now it's this 20j version.
Anyway, this is what I'm typing and this is what I get in return:
fastboot --set-active=b
fastboot: error: Device does not support slots
I'm at a real loss, obviously this damn device supports slots.
EDIT: OK hold on, when I flashed the June image bootloader version, ran the slot command in ADB, I was able to navigate to the right slot.
Little update.
Followed this guide:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Rebooted into slot a and the touch screen stopped working. So now I'm going back to stock yet again. Just leaving it that way for now I can't deal with this crap.
stevew84 said:
Little update.
Followed this guide:
https://forum.xda-developers.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175
Rebooted into slot a and the touch screen stopped working. So now I'm going back to stock yet again. Just leaving it that way for now I can't deal with this crap.
Click to expand...
Click to collapse
Fwiw, after you flash a rom and twrp, if it doesn't boot up, go back to twrp and flash the rom and twrp again. Flashing roms or taking OTA's automatically switches slots on you. Always best to keep screen lock disabled until you are done.
Badger50 said:
Fwiw, after you flash a rom and twrp, if it doesn't boot up, go back to twrp and flash the rom and twrp again. Flashing roms or taking OTA's automatically switches slots on you. Always best to keep screen lock disabled until you are done.
Click to expand...
Click to collapse
Thanks.
Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices
motcher41 said:
Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices
Click to expand...
Click to collapse
How did you get to DP3? Did you enroll in the beta program?
Badger50 said:
How did you get to DP3? Did you enroll in the beta program?
Click to expand...
Click to collapse
yes and weirdly using a factory image on my Mi A1 gave no error
motcher41 said:
yes
Click to expand...
Click to collapse
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:
Badger50 said:
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:
Click to expand...
Click to collapse
i would but i am currently soft bricked. have access to bootloader only
even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc
motcher41 said:
even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc
Click to expand...
Click to collapse
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.
but are they all the same target as the .img name
Badger50 said:
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.
Click to expand...
Click to collapse
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too
motcher41 said:
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too
Click to expand...
Click to collapse
Hey, as long as it worked your good. Welcome :good:
Yeah my format userdata may have been off. I was going by memory from my 6p. P2XL might be different. Sorry.