Database Info

Operation not permitted

Subject line pretty much sums it up. I've been to loads of GUIs and walkthroughs - in the end my device remains locked down. I have TWRP as my recovery and a rooted version of the stock CM11S. I have my debugging on. My computer has permission with it set to remember my choice. I've dabbled in both OSX and Windows adb. The goal is to go back to stock EVERYTHING. I'm going to send it back.
Please help.

Lol you told us everything except for which operation is not permitted.
Transmitted via Bacon

Flashing pretty much anything via fastboot. When I 'fastboot oem unlock' the system isnt formatted or anything. Is it because my recovery isnt stock? I've tried restoring stock recovery, but after it loads once, a reboot just goes into TWRP again. I dont understand.

Xephrey said:
Flashing pretty much anything via fastboot. When I 'fastboot oem unlock' the system isnt formatted or anything. Is it because my recovery isnt stock? I've tried restoring stock recovery, but after it loads once, a reboot just goes into TWRP again. I dont understand.
Click to expand...
Click to collapse
If you don't have the stock recovery installed, isn't your bootloader unlocked already? What happens when you issue these commands?
Code:
fastboot devices
Code:
fastboot oem device-info
Transmitted via Bacon

timmaaa said:
If you don't have the stock recovery installed, isn't your bootloader unlocked already? What happens when you issue these commands?
Code:
fastboot devices
Code:
fastboot oem device-info
Transmitted via Bacon
Click to expand...
Click to collapse
C:\Users\Chris\Desktop\android-sdk-windows\platform-tools>fastboot devices
97e265f5 fastboot
and
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s

What about the question I asked?
Transmitted via Bacon

Oh sorry. Yeah, that's where things get weird. It's locked now, but I guess I was able to get it unlocked long enough to get TWRP injected. Not sure when / how it locked.

So you don't know at what point this started happening?
Transmitted via Bacon

I don't.

Usually there's a catalyst for things like this, without knowing the catalyst it's difficult to troubleshoot.
Transmitted via Bacon

Well shoot.

Come to think of it, I think I may have typed in oem lock at one point and then unlock promptly thereafter.

Solution
Great news! I've solved the issue. I used OnePlus One Toolkit by @manudroid19
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
I tried the Experimental Method or #2 to unlock the bootloader. Then you're given the option of downloading TWRP. At first I thought that was lame cause I already had that installed - that's what I was trying to get away from. But I finally understood that I had the option of running that recovery off of my PC by initiating fastboot mode on my One, then typing 'fastboot boot <local path of TWRP.zip I just downloaded>'. And from there I was able to sideload the unlock / tamper toggler as made available here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Sideload actually completed successfully! I had tried sideload before with every attampt ending in red-text failure. I then went into fastboot mode on my One and flashed stock recovery. Then I used OnePlus One Toolbox v2 by @inthiaano:
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
Because it had stock CM11S as an option. This was also the toolbox I used to flash stock recovery earlier cause I couldn't find it anywhere else. After I flashed that, I did the fastboot boot <local TWRP> sideload unlock toggler again to achieve:
DUN DUN DUN DUUUNNNNN...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
Factory reset and return-ready. FINALLY!
So happy. Now I can get my money back and buy an Nvidia Shield 2 instead.

I need help unlocking & flashing an recovery, I tried everything!

Hello XDA Developers,
I have unlocked, installed recoveries and ROMs alot in the past with my older phone, but I cannot seem to get it to work on the OnePlus One.
I just figured out that my device is actually unlocked now using the command: 'fastboot oem device-info':
"
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
"
But I cannot seem to flash a custom recovery, this is what happens when I try. I successfully uploads the img file to my phone, when I clear the cache, reboot and start the recovery, I get the Cyanogenmod Recovery, again!
When I shut down my phone after flashing the recovery, then boot directly into recover my phone stays stuck at the oneplus (powered by andriod screen)
Can someone help me with this?
My devices and current rom:
Windows 10 running on an MacBook Air (smooth af)
OnePlus One A0001: Cyanogen OS: 12.1.1-YOG7DAS2k1
Buildnummer: LMY48Y
Kernel: 3.4.76-cyanogenmod-g9220ae3
Smallband: DI.3.0.c6-00241-M8974AAAAANAZM-1
I hope I gave you guy's enough information and I hope someone can give me some advice on how to tackle this issue. I need TWRP installed so I can flash custom roms and kernels!
Thanks!

when you flash recovery you get OKAY result ? use twrp 2.8.6.0 not above to flash correctly modem firmware (i'm using latest cm nightly recovery and works good too)
Code:
fastboot devices
see your device ?
if yes
Code:
fastboot flash recovery recovery_file.img
should works

bastard79 said:
when you flash recovery you get OKAY result ? use twrp 2.8.6.0 not above to flash correctly modem firmware (i'm using latest cm nightly recovery and works good too)
Code:
fastboot devices
see your device ?
if yes
Code:
fastboot flash recovery recovery_file.img
should works
Click to expand...
Click to collapse
Thanks for your quick support, I finally figured it out. Some devices have this issue, if someone has this issue they should disconnect usb cable after flashing recovery, turn off the device, hold down the volume down button first, then hold down the power button for a few seconds, then wait until you get booted into recovery. It will then prompt to disable the recovery security that cyagonmod enables.
I am able to flash roms now!

Please Help with Bricked Xoom?

Hi all,
I've exhausted all my resources in trying to get this tablet to work. It might be hard bricked if that's even possible. Just a little back ground on what happened. The device was running very slow after 3yrs of using wingray (wifi MZ604?) [ROM][4.4.4] OmniROM - Wingray - bigPart. Anyway it's from Verizon and it only has wifi. But as I said, it was running very slow so I figured i'd flash back to stock ROM. The stock ROM flash fine and it was pretty responsive. Then this where everything went to sh!*.. I received an update notification, it updated, rebooted and the tablet is stuck on Dual Core M boot screen. I have tried to restore by flashing OmniROM - Wingray - bigPart and RDS back to stock ROM, both stuck on Dual Core M boot screen.
I spent over 48 man hours reading through the forums on how to unbrick this tablet. Unlocking the botloader and pushing twrp big part and flashing a custom ROM, to using One Click Tool made by XxLordxX to try to get it back to stock and installing Omni ROM. None of which seam to work. It always ends up stuck on Dual Core M boot screen until it runs out of battery charge. There is no way I can get into any type of recovery.
I have access to the following items:
- fastboot
- RDS
I don't have access to the following:
- bootloader
- ADB
- default or custom recovery
If anyone can assist, I would really appreciate it.
Edit: if it helps, this is what i extracted from the device in fastboot
Code:
(bootloader) version-bootloader: 1045
(bootloader) product: xoom-cdma
(bootloader) secure: yes
(bootloader) model: MZ600
(bootloader) memory-info: 0x303:0x5454:0
(bootloader) mid: 001
(bootloader) version: 0.4
(bootloader) serialno: redacted
(bootloader) version-baseband: CDMA_N_03.1A.71P
(bootloader) version-baseband-2:
(bootloader) battery-status: 61%:7.729V:0.9731A:33.62C
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
all: Done
Thanks

download twrp img file and use fastboot to upload the recovery? "fastboot flash recovery twrp-3.0.x.x-xxx.img" just gotta find which twrp you want. by the by, I just flashed the files from here and now I am getting a boot screen instead of stuck at bootloader like you ;
https://www.dropbox.com/sh/1fxrnv2ce8fyjyn/AABHGMZcGCYBYqtDSvMMpXC-a?dl=0
Which is from here - give the man props! https://forum.xda-developers.com/motorola-xoom/general/roms-motorola-xoom-t3602655

Unfortunately any twrp recovery I flash with fastboot doesn't allow me into recovery. Without recovery I can't flash those archives. Very annoying. But thanks for the heads up. I guess the main priority is to get a working recovery.
Sent from my iPhone using Tapatalk

Change the usb cable. I'm not joking, that might be the problem!
If that doesn't work, use RSD lite to flash the original ROM (the SBF file, you will find it on the internet). Make sure to flash the corresponding SBF to your tablet.

vlad_popescu47 said:
Change the usb cable. I'm not joking, that might be the problem!
If that doesn't work, use RSD lite to flash the original ROM (the SBF file, you will find it on the internet). Make sure to flash the corresponding SBF to your tablet.
Click to expand...
Click to collapse
Yea I believe you about the USB cable but unfortunately this was a hand me down and the original cable was lost.
I've tried all the SBF files I can get my hands on and it still gets stuck on the M logo screen and I can't get into recovery mode. I can list all the sbf files I've tried. They are still stored on my NAS.

Hello nomadman,
Check a zip from this thread according to your Xoom model version and area:
https://forum.xda-developers.com/showthread.php?t=1049485
Unzip the file. And do these commands to boot your rom:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
Use this method to your own risk. I think it should work, but... I suppose it is your only chance to have stock rom again.

Thanks @Manuallama. I will give this a shot since I don't really have a choice. Before I flash I usually fastboot clear those boot, user, and system. We do this when I get home from work. Cheers
Sent from my iPhone using Tapatalk

installing TWRP and rooting Asus Zenpad 10 (Z300m)

THIS THREAD IS NO LONGER UNDER DEVELOPMENT, FOR FUTURE UPDATES PLEASE HEAD HERE.
Flashing TWRP and Rooting the Asus Zenpad 10 (Z300M)
CREDIT: Diplomatic, JustShaun, and Flukester69 all made this possible. But really if anybody needs an applause, it's Diplomatic. If you wish to thank him you can do so here.
IMPORTANT! READ BEFORE CONTINUING!
Nobody here is responsible if you mess up your tablet! This is your decision and yours alone! Yes, this will void your Warranty! The below is based on the success of our own testing. We suggest reading this multiple times if necessary, before attempting. Ask questions if you are unsure, I'm sure someone will try and help.
Things you'll need:
- Windows computer / possibly Linux if you are savvy enough.
- Z300m with Android 7 (check if there's updates, if so, reboot tablet when done.)
- USB Cable (the one that came with it, or one you are sure works)
- MediaTek VCOM Preloader Drivers (I will explain further below) (Win10 installed drivers work too)
- Z300m Scatter File
- TWRP 3.1.1 image
- SP Flash Tool 5.1532
- SP Flash Tool 5.1548 or later (latest is 5.1720 at the time of this writing)
- Magisk Manager (Beta 13 works)
or
- TWRP 3.1.1 Recoveryasboot
Create a temp folder on your desktop and throw all the above downloads in there.
MTK Driver Install - Pre-Flashing Procedure:
Turn your tablet OFF and plug it in to your computer, Windows should recognize the device and download the drivers. You should be able to manually search through device manager (Turn on Hidden devices might be necessary). When the drivers have been downloaded feel free to unplug the tablet again.
You'll want to make sure the drivers are installed properly. A quick way to test,
Open Device Manager by either searching for it or running 'devmgmt.msc'
Turn on hidden devices.
Expand the 'Ports (COM & LPT) section
If the drivers are installed properly you should see 'MediaTek PreLoader USB VCOM Port (COM*)'
Good enough, if that worked. If not, check your device manager and figure out your driver issue.
Backing Up:
Open the SPFL (latest) dir and open option.ini in any text editor, you'll want to change "[ReadBack] ShowByScatter=false" from false to true and save your changes.
Load into flash_tool.exe.
Change the download-agent from MTK_AllInOne_DA.bin to DA_PL.bin - This is located under the SPFL dir.
Add the Scatter-loading file which should have been downloaded previously.
Head into the Readback tab and you should see 'Preloader, pgpt, proinfo ect...'. Check all of these boxes and click Read Back
Make sure the tablet is turned off and then plug it into your computer. Bar goes red, yellow and then done. Green Checkmark.
It's safe to unplug the USB from the tablet now and you can close the Flash Tool
Flashing TWRP:
It's up to you to backup your tablet. You should, but the tablet technically should reset if anything fails. Another choice that is up to you alone.
Again, Make sure your tablet is powered off and NO USB plugged in. This is basically the same procedure as backing up, except you're using the Download tab instead of Readback.
Extract SP-Flash-Tool-v5.1532.00 and Launch flash_tool.exe.
Change the download-agent from MTK_AllInOne_DA.bin to DA_PL.bin - This is located under the SP-Flash-Tool-v5.1532.00 dir.
Add the Scatter-loading file which should have been downloaded previously.
Look down the list you see Recovery line, click on the right side, point it to the TWRP.img you downloaded. (Make sure this line is only checked.)
Click the Download button and THEN plug in the USB cable to your tablet. Bar goes red, yellow and then done. Green Checkmark.
It's safe to unplug the USB from the tablet now and you can close the Flash Tool
Alternative method that does not require SP Flash Tool, scatter file, etc.
Unlock the bootloader: Download the Asus unlock tool for your tablet here and run it. (It's an APK from ASUS. When done you reboot tablet, you will see a message Your Device Cannot be Trusted..., you're unlocked.)
Download twrp-recoveryasboot-3.1.1-0-z300m.img.
Make sure you have fastboot/adb installed on your PC. Put your tablet in fastboot mode by holding Volume Up and Power, then selecting Fastboot Mode from the menu, and connect to PC.
Run this command to do a tethered boot of TWRP
fastboot boot twrp-recoveryasboot-3.1.1-0-z300m.img​
This will boot but will not install TWRP. You may be able to do whatever you need in this environment. But it is recommended to install TWRP to your flash ROM, and proceed from there.
To flash TWRP from TWRP, go to Install -> Install Image. Select the twrp-3.1.1-0-z300m.img file you downloaded earlier (not the twrp-recoveryasboot*.img file). Select Recovery, then swipe to flash.
Reboot to Recovery
[TWRP first launch]
Now press and hold both the Volume Up and Power button at the same time. Tablet will show a list so let go of the buttons.
Use the Up volume now to select Recovery and press Down volume to select. Tablet should reboot into TWRP. (takes 10-15 seconds)
A dialogue will show in TWRP stating that there is a chance Recovery will be restored (the Asus one) so slide across to keep TWRP.
Mounting /system in read/write mode could be potentially hazardous, this is patched at your own risk.
***NOTE: You will need to boot into the recovery immediately after flashing, failing to do so will result in the Android OS reflashing its stock recovery. If you are concerned about which recovery is installed I would suggest using 'adb reboot recovery' to minimize risk.
[ROOTING]
Put the Magisk flash file on a working micro sdcard and pop it in your device. (this won't get deleted and can be accessed by TWRP)
Don't reboot yet, we need to flash Root (you should have Magisk img/zip on your micro sd inserted in tablet)
Assuming you are familiar with TWRP, Install the Magisk Manager.
When this is done, reboot your tablet to System with TWRP.
We've tried to make this guide as helpful as possible, read this thread and the Z380 thread as there may be new things learned, past experiences of others that could help you.
Enjoy your Rooted Tablet!

Thanks! Any chance of instructions for us using Linux?
Maybe we'll get LineageOS for this soon!

New TWRP Image March 4, 2018
Up to date precompiled kernel from firmware WW-5.3.19
Up to date TWRP/AOSP sources, including TWRP 3.2.1-0
Unified image that may be flashed to recovery or boot partitions, or be used for tethered boot
Guide and downloads on my new TWRP thread
Upgrade Installation
Copy the new image file to your tablet, then use your existing TWRP to Install->Install Image the .img file to Recovery. Then reboot to recovery.
Mandatory step: after trying this release out, you must come back here and post whether it works or not.
(Source code on my Z380M thread.)

Good job ! It's more than anyone else has managed to do so far

justshaun said:
In order to navigate through TWRP you will need to attach the OTG cable and mouse to your tablet, it doesn't currently have any touchscreen functionality. Reboot into the system and make sure to patch your OS.
Click to expand...
Click to collapse
After looking at kernel logs and old source code, it seems like the touchscreen driver is intentionally disabled from working in recovery mode. If we had updated kernel sources, this could be fixed easily.
QwertyChouskie said:
Thanks! Any chance of instructions for us using Linux?
Click to expand...
Click to collapse
Try the Linux flavor of SP Flash Tool?

Wow this is quite the process and twrp with no touch screen? Plz post your success to raise confidence of others like me. Last f'ng tablet I ever buy from Asus. Let's also not forget you will be stuck on this release forever afterwards.
Sent from my P00C using Tapatalk

how do you unroot tablet after this process?

Flukester69 said:
Wow this is quite the process and twrp with no touch screen? Plz post your success to raise confidence of others like me. Last f'ng tablet I ever buy from Asus. Let's also not forget you will be stuck on this release forever afterwards.
Click to expand...
Click to collapse
You can try the Asus unlock tool to be able to flash with fastboot and not worry about SP Flash Tool. At least one person got it work on the Z380M. And you can always unroot/restore original boot & system images to be able to upgrade the firmware. Also, it's kind of unfair to rate a company poorly for not supporting your hacks, especially since this tablet is basically unbrickable AFAIK.
MihaiA7X said:
how do you unroot tablet after this process?
Click to expand...
Click to collapse
Restore the original boot image if you only have systemless root. And also the system image if you've modified it.

diplomatic said:
You can try the Asus unlock tool to be able to flash with fastboot and not worry about SP Flash Tool. At least one person got it work on the Z380M. And you can always unroot/restore original boot & system images to be able to upgrade the firmware. Also, it's kind of unfair to rate a company poorly for not supporting your hacks, especially since this tablet is basically unbrickable AFAIK.
Click to expand...
Click to collapse
I'll give it a try at some point man, not sure about the unbrickable part, $hit happens. Do you have a reference for the guy with the 380 that flashed via fastboot? that would be the preferable method for me really.
---------- Post added at 10:20 PM ---------- Previous post was at 10:01 PM ----------
What is Magisk? Is it really needed? If TWRP is installed with the Flashtools can I not just flash SuperSU with TWRP? If you could clarify?
When I tried the command to flash recovery I got the following...
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13958 KB)...
OKAY [ 0.445s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.452s

What I meant by unbrickable was that you can use SP Flash Tool to talk directly with the SoC. That gives you low-level access to the flash ROM without depending on any software on it. So for example, if your bootloader or partition table is messed up, something that would brick most devices, you can flash those in without needing to get into the bootloader. I'm not 100% sure this is possible, but I'm pretty confident it is.
This is the post where the guy unlocked the bootloader. But I'm not sure he used fastboot to flash. TBH, FlashTool is not that complicated. Most of that stuff in the guide has to do with backing up your flash memory. If you wanna skip that part, that's up to you. You can just go ahead and use Flash Tool 5.1532 with the scatter file and the right download-agent to flash the recovery. BTW, you can follow that thread as well. Whatever applies to the Zenpad Z380M usually applies to the Z300M too.
Magisk is another root manager like SuperSU. SuperSU seems to have compatibility problems with this tablet. (I have not tried either.)

diplomatic said:
What I meant by unbrickable was that you can use SP Flash Tool to talk directly with the SoC. That gives you low-level access to the flash ROM without depending on any software on it. So for example, if your bootloader or partition table is messed up, something that would brick most devices, you can flash those in without needing to get into the bootloader. I'm not 100% sure this is possible, but I'm pretty confident it is.
This is the post where the guy unlocked the bootloader. But I'm not sure he used fastboot to flash. TBH, FlashTool is not that complicated. Most of that stuff in the guide has to do with backing up your flash memory. If you wanna skip that part, that's up to you. You can just go ahead and use Flash Tool 5.1532 with the scatter file and the right download-agent to flash the recovery. BTW, you can follow that thread as well. Whatever applies to the Zenpad Z380M usually applies to the Z300M too.
Magisk is another root manager like SuperSU. SuperSU seems to have compatibility problems with this tablet. (I have not tried either.)
Click to expand...
Click to collapse
Thanks for clearing that up... Ok I can use the 5.1532, I get that part but I don't get this part...
6. Make sure the tablet is turned off and then plug it into your computer
Click to expand...
Click to collapse
then
Click download at the top and plug in your tablet while it's still off. Assuming all goes well, the 'Download Flash' section at the bottom should be sitting on 100% and you should have a lovely green tick on your screen.
Click to expand...
Click to collapse
So when I press Download button in flash tool, the tablet needs to be OFF? Like powered off completely? Because nothing happens other than seeing the untrusted device (cuz it's unlocked) and the battery charging display.

Flukester69 said:
So when I press Download button in flash tool, the tablet needs to be OFF? Like powered off completely? Because nothing happens other than seeing the untrusted device (cuz it's unlocked) and the battery charging display.
Click to expand...
Click to collapse
Yeah, completely off. Have you installed the Mediatek USB port drivers? Where does it say untrusted device?
So after you unlocked it, have you tried fastboot flash? And you also don't need to use the 5.1532 version. I think the latest one will work too. The 1532 is just the NSA courtesy version.

diplomatic said:
Yeah, completely off. Have you installed the Mediatek USB port drivers? Where does it say untrusted device?
So after you unlocked it, have you tried fastboot flash? And you also don't need to use the 5.1532 version. I think the latest one will work too. The 1532 is just the NSA courtesy version.
Click to expand...
Click to collapse
Installed is whatever Win10 installed. I didn't try other drivers because adb / fastboot appear to work but I can try some other drivers.
Whenever I boot the tablet, it says untrusted device because the bootloader is unlocked. It says, booting in 5 seconds.
I do a fastboot reboot bootloader and I see it says fastboot ready at the bottom of the screen. When I type fastboot devices, it says my device in the list.
I tried fastboot flash recovery recovery.img if that's what you're asking (didn't work, so that's why I went with the software)

So just to be clear, you were getting 'FAILED (remote: download for partition 'recovery' is not allowed)' AFTER you've unlocked the bootloader?
If it's not being detected by SP Flash Tool, then something's wrong with your driver installation. Remember, those Mediatek USB drivers are not the same ones your ADB and/or Fastboot drivers. Check your Device Manger, under Ports, for a device called "MediaTek PreLoader USB VCOM (Android)". You have to check View->Show Hidden Devices to see it when your device is disconnected. You might have to right click and Update Driver Software to fix it.

diplomatic said:
So just to be clear, you were getting 'FAILED (remote: download for partition 'recovery' is not allowed)' AFTER you've unlocked the bootloader?
If it's not being detected by SP Flash Tool, then something's wrong with your driver installation. Remember, those Mediatek USB drivers are not the same ones your ADB and/or Fastboot drivers. Check your Device Manger, under Ports, for a device called "MediaTek PreLoader USB VCOM (Android)". You have to check View->Show Hidden Devices to see it when your device is disconnected. You might have to right click and Update Driver Software to fix it.
Click to expand...
Click to collapse
I got the failed with the fastboot command not the flash tool. I'll try and install the mediatek special drivers you are most likely right that they differ from the sdk provided ones. Reading other threads I understand the flash tool a bit more too. I'll do a bit more work on it and provide feedback. Thanks for your help diplomatic.
Sent from my P00C using Tapatalk

No, I know the message is from fastboot... I'm asking if you have tried fastboot flash with your bootloader UNLOCKED. Because that message indicates that your bootloader was locked when you ran it.

diplomatic said:
No, I know the message is from fastboot... I'm asking if you have tried fastboot flash with your bootloader UNLOCKED. Because that message indicates that your bootloader was locked when you ran it.
Click to expand...
Click to collapse
Well I ran the bootloader unlock tool I downloaded from Asus and ran it so I assumed it's unlocked. I tried to install drivers (latest I could find) but Windows 10 (64-bit) says I have latest installed. I checked device manager and when my tablet is off and I connect it I see the drivers(3) become active for a few seconds and then they turn off. Seems to me something is not working with this process. If you look below it seems to indicate to me the bootloader is unlocked.
Here is info
Code:
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
G7NPCV038358ANK device
C:\adb>fastboot devices
G7NPCV038358ANK fastboot
C:\adb>fastboot flash recovery c:\adb\twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13958 KB)...
OKAY [ 0.444s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.453s
C:\adb>fastboot getvar all
(bootloader) max-block-size: 0x80
(bootloader) check-fastboot-version: 1
(bootloader) sofia_support: 1
(bootloader) continuous: 1
(bootloader) flash-all-depart: 1
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:ADF: 2000000
(bootloader) partition-type:ADF: ext4
(bootloader) partition-size:APD: 6400000
(bootloader) partition-type:APD: ext4
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:asus_nvm: 100000
(bootloader) partition-type:asus_nvm: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: c800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: dfc00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:secro: ff7000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: ff7000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: ff7000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:persist: 2000000
(bootloader) partition-type:persist: ext4
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: ASUS8163_EW_380
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.112s
C:\adb>
---------- Post added at 11:21 PM ---------- Previous post was at 10:33 PM ----------
diplomatic said:
No, I know the message is from fastboot... I'm asking if you have tried fastboot flash with your bootloader UNLOCKED. Because that message indicates that your bootloader was locked when you ran it.
Click to expand...
Click to collapse
LOL! OK. I figured $h.. out... The problem was this...
The device must be OFF and DISCONNECTED and ONLY connected when you hit the download button. The reason is, the driver shuts off if there is no data transferring. Very important detail. I am guessing this is what the issue was and why the flash tool was not working. Now I probably got old crap drivers by forcing them through Windows Troubleshooter to override signature verification. So anyway I tried flashing anyway and it failed. I suspect because I overrided good drivers with old ones. You can see what I got here.
https://ibb.co/mwkHFv

Whoa, that's kind of unexpected that fastboot would not let you flash even though it's unlocked. And the latest SPFT is not letting you download either. It says it's unlocked but it's acting like it's locked. But you're really close....
That S_SECURITY_SECURE... (6045) message is just the Flashtool's version of fastboot not allowed error (locked bootloader). So you still have to use 5.1532 to flash it. That's all.
I will post a signed image of TWRP to see if that will work for you.

diplomatic said:
Whoa, that's kind of unexpected that fastboot would not let you flash even though it's unlocked. And the latest SPFT is not letting you download either. It says it's unlocked but it's acting like it's locked. But you're really close....
That S_SECURITY_SECURE... (6045) message is just the Flashtool's version of fastboot not allowed error (locked bootloader). So you still have to use 5.1532 to flash it. That's all.
I will post a signed image of TWRP to see if that will work for you.
Click to expand...
Click to collapse
OK That worked with the 5.1532 and I booted to recovery and TWRP is there. Woohoo! Thanks for the continued help! I was getting frustrated. Not like the first device I flashed/rooted etc...
Disconnecting of the tablet until after Download button was one, the next the version of SP Flash.. cool. Making progress.
So you say SuperSU don't work... Magick one works though but installs crap, then you could use sysuninstaller to remove the crap...? Think I read that somewhere. Ok I'll read up anyway, kinda curious why SuperSU
wont work or has problems.
Also know that I removed all the MTK (older) drivers using USBDeview and then rebooting my tablet and going through all the modes, fastboot etc.. the drivers eventually all the Windows certified re-installed (the MS ones). So no need to download drivers either I guess.
Edit: this is a 1 time deal apparently. I had twrp installed but as I didn't have supersu 2.82 downloaded I rebooted out of recovery. Next attempt to go to recovery resulted in "Erasing" so I lost all my apps and had to setup my tablet all over again. Oh well, guess I know what to do now. Try again tomorrow.

All right, good job, man! :good: I'm sure our discussion will clarify the process for others...
As for root, someone else should help you out. I have not put root on my tablet. All my hacks and mods are done through TWRP.
I'm still surprised that the unlocked bootloader did not let you flash it.
---------- Post added at 12:02 AM ---------- Previous post was at 12:00 AM ----------
Flukester69 said:
Edit: this is a 1 time deal apparently. I had twrp installed but as I didn't have supersu 2.82 downloaded I rebooted out of recovery. Next attempt to go to recovery resulted in "Erasing" so I lost all my apps and had to setup my tablet all over again. Oh well, guess I know what to do now. Try again tomorrow.
Click to expand...
Click to collapse
Oh come on, how could you miss that big red text in the OP?

[STOCK FIRMWARE][WINDOWS][OUTDATED] How to upgrade and clean wipe from Stock Android 10 to Stock Android 11 without OTA [Retail USA Channel]

NOTICE : As of June 15, 2022 you no longer NEED this method as the OTA for Android 11 has been released. This is here for those who don't get the OTA or need an upgrade from a clean reset manually using only the RSA tool.
Credits to : morpheus092511 over on the Lenovo Forums for tricking the Moto Tool into installing the stock firmware, and Chepr29 from the Lenovo Forums for the fastboot method that doesn't require the tool.
In fastboot on your PC after your extract the Android 11 firmware and have your device in recovery mode enter the following commands (back up your data this will clean wipe it!) :
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot erase userdata
fastboot erase carrier
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
1. BACK UP ANY IMPORTANT FILES OR INFORMATION! DON'T FORGET TO BACK UP YOUR TWO FACTOR AUTHENTICATION CODES AS WELL! This method can be done with other firmwares, but I have only tested a clean wipe upgrade from stock Android 10 to 11 RETUS on the Motorola One Ace 5G (Unlocked from Amazon) and can't comment on other firmwares.
2. Windows ONLY! DOWNLOAD THE RSA software from Motorola that allows you to recover, backup, or flash stock firmware to your device.
https://download.lenovo.com/lsa/Releases/Rescue_and_Smart_Assistant_v6.1.1.9_signed_setup.exe
3. DOWNLOAD the retail Android 11 firmware for the Motorola One Ace 5G (Kiev) Retail USA / Unlocked from here :
https://mirrors.lolinet.com/firmware/moto/kiev/official/RETUS/XT2113-2_KIEV_RETUS_11_RZK31.Q3-45-16_subsidy-DEFAULT_regulatory-DEFAULT_R8_CFC.xml.zip
4. Go to C:\ProgramData\RSA\Download\RomFiles and extract the .zip folder here. You may need 7Zip, or WinRAR to do so. I recommend 7Zip as it's open source and free without nag popups.
https://www.7-zip.org/a/7z2107-x64.exe
5. Connect your phone to the PC via USB-C and shut it off. Hold volume down, and power on at the same time until the recovery screen shows.
6. The RSA software will detect your proper "latest" firmware automatically in fastboot mode, allow it time to download and wait until it's done, give it some time after it hits 100.00% because the program will begin decompressing and unzipping the stock firmware, but it will NOT tell you this, keep that in mind!
7. Under the same directory in Step 4, you should now have two folders. One that says 10 and 11 with almost the same naming convention, delete ALL of the files in the folder that RSA downloaded (the 10 folder), and copy and paste all of the files from (the 11 folder), but LEAVE the name of the folder the same as what it was when RSA downloaded it, don't change the name or you'll either have to re-name it back, or re-download the firmware once more and let it extract.
8. Go back to the RSA program and hit the yellow "Rescue" button. Don't touch your phone and leave it alone! All data will be erased and it will begin flashing the firmware from Android 11 without a single issue. If you have PIN or password locked your phone previously, upon first boot up Android will ask you for your previous device PIN before you can begin setting up the device initially.
NOTE : This should preserve your warranty, mine expired a few months ago and I haven't been able to confirm this 100% because of this. (we waited a LONG time for this update!) Since the process does NOT require your bootloader to be unlocked or modified in anyway whatsoever, I do NOT see how you could possibly void the warranty. As of this writing, I have NEVER attempted to even unlock my bootloader for stability purposes, and because rooting isn't a concern to me on this device. In fact, to my knowledge you are NO LONGER able to unlock the bootloader on Android 11, so proceed with caution if this is something you require! There may be a 3-day wait of being connected to the Internet before you are allowed to use the OEM Unlock function, please keep that in mind if this is an issue.
Since it is stock firmware, there are no functionality issues to be concerned with. Calling, 5G, camera, Bluetooth, NFC and other basic sensors and extra functionality work 100% to my knowledge after testing most functions myself for the better duration of a day, even my Fossil Gen 6 Android Wear 2.0 (updating to 3.0 soon) watch is functioning flawlessly over WiFI and Bluetooth with the new update.

Please note this method is now outdated, as the OTA has been released for Android 11.

TheLastSidekick said:
Please note this method is now outdated, as the OTA has been released for Android 11.
Click to expand...
Click to collapse
It does work though, for anybody needing (or just wanting) to recover from a blown system without having to wait for a Rescue download.
Also it's a bit irritating that 95-9 for RETUS never got uploaded to lolinet. And now since 11 is released, that's all you can get through RSA, because it INSISTS on upgrading the phone to the latest version.
(Edit/Add) I would just like to have 95-9 handy for emergency reflashing if ever needed, but now I can't get my hands on it anywhere . . . except on that "easy" website and I don't really trust it 100%.
NOTE: I just flashed an 11 upgrade (manually via fastboot) and there was only 0-9 sparsechunk files. No super.img_sparsechunk.10 to be found, either the file or in the servicefile.xml . . . ? This was specifically the KIEV_RETAIL_RZK31.Q3_45_16_subsidy_DEFAULT_regulatory_DEFAULT_R8_CFC.xml firmware . . .

Moondroid said:
It does work though, for anybody needing (or just wanting) to recover from a blown system without having to wait for a Rescue download.
Also it's a bit irritating that 95-9 for RETUS never got uploaded to lolinet. And now since 11 is released, that's all you can get through RSA, because it INSISTS on upgrading the phone to the latest version.
(Edit/Add) I would just like to have 95-9 handy for emergency reflashing if ever needed, but now I can't get my hands on it anywhere . . . except on that "easy" website and I don't really trust it 100%.
NOTE: I just flashed an 11 upgrade (manually via fastboot) and there was only 0-9 sparsechunk files. No super.img_sparsechunk.10 to be found, either the file or in the servicefile.xml . . . ? This was specifically the KIEV_RETAIL_RZK31.Q3_45_16_subsidy_DEFAULT_regulatory_DEFAULT_R8_CFC.xml firmware . . .
Click to expand...
Click to collapse
Yeah the whole thing is strange the way the way each firmware is slightly a different size between what is evidently the same Retail build.

Actually, there's an easier method using RSA rescue.
You can grab boot.img for rooting.

mingkee said:
Actually, there's an easier method using RSA rescue.
You can grab boot.img for rooting.
Click to expand...
Click to collapse
I was using Rescue tool for this, may I please ask you how you were able to grab the boot.img? Thank you in advance!
Also, for those wondering if using the method above if OTAs will continue to update the answer is 100% YES confirmed.

TheLastSidekick said:
I was using Rescue tool for this, may I please ask you how you were able to grab the boot.img? Thank you in advance!
Also, for those wondering if using the method above if OTAs will continue to update the answer is 100% YES confirmed.
Click to expand...
Click to collapse
After rescue, check C:\Program Data\RSA\Download\romfiles\
Check Kiev folder