Database Info

[Q] Xoom Stuck On M and DualCore Screen (NOT ROOTED)

Hello there,
I have recently received a Motorola Xoom MZ604 Wifi with the problem described above.
Things I have already tried:
1. Factory Reset
2. Pressing every button combination long press on power button etc etc..
3. Unlocking the device - Putting Custom Recovery (All of them)
4. Acessing adb and fastboot - Flashing stock ROM back onto it from the Stock Images from XDA
5. Try Rooting it (no luck) USB Debugging is required for rooting and I cannot access the USB Debugging option since the Xoom doesn't boot up.
Is there anything else I could try or maybe I'm doing something wrong?

BUMP
Also tried to do the SBF/RSD Format But still no luck, the RSD said it has PASSED but the Xoom still won't boot up - the Motorola logo stays for about 6 seconds and then disappears and loops again.

Qll I can suggestion is to preform the steos from motodev to unlock your device.
Then use fastboot to flaahing the imgs.
Again all the steps and imgs are at motodev.
If yoi follow that to the letter and it still hangs/loops at the "M" then I would say one or more of the partitions are corrupt which is basically the end of that tablet...without physically repairing it

runandhide05 said:
Qll I can suggestion is to preform the steos from motodev to unlock your device.
Then use fastboot to flaahing the imgs.
Again all the steps and imgs are at motodev.
If yoi follow that to the letter and it still hangs/loops at the "M" then I would say one or more of the partitions are corrupt which is basically the end of that tablet...without physically repairing it
Click to expand...
Click to collapse
If i try unlocking the device through motorola website then in fastboot I get this error "FAILED (remote: (00120000))
finished. total time: 0.245s"

slazzenger said:
If i try unlocking the device through motorola website then in fastboot I get this error "FAILED (remote: (00120000))
finished. total time: 0.245s"
Click to expand...
Click to collapse
What reads out on the tablet?

runandhide05 said:
What reads out on the tablet?
Click to expand...
Click to collapse
"Failed to process command error (0x120000) that's after the
"fastboot oem get_unlock_data" command from motorola website in order to get the unlock code

slazzenger said:
"Failed to process command error (0x120000) that's after the
"fastboot oem get_unlock_data" command from motorola website in order to get the unlock code
Click to expand...
Click to collapse
Use fast boot command
"fastboot oem unlock"
The xoom specific instructions should be followed. The get unlock data is for newer devices

runandhide05 said:
Use fast boot command
"fastboot oem unlock"
The xoom specific instructions should be followed. The get unlock data is for newer devices
Click to expand...
Click to collapse
Oh I thought that the unlock from motorola website was different from the fastboot oem unlock. I've already tried doing that and flashing all the images - still no luck :<

Shield tablet wont boot beyond fastboot menu :'(

I hope you guys can help me, i have been wandering around blogs forums to find a fix to this issue but to no avail. I got my replacement tablet about a few month ago. I decide to keep the old one and install custom rom on it. The old one is still usable now, but the replacement tablet is dead to me. One day i restart the repl tablet and it just stucked at the fastboot menu. When i choose to go into recovery mode. Nothing happened except a blink of message said that cold linux booting failed. So i try to unlock bootloader to flash it using adb command. Now it wont let me unlock boot loader giving me an error same as the guy here ( i cant paste an outside link here, google : Shield Tablet (LTE) won't boot beyond fastboot, fastboot OEM)
Ps : sorry for bad english im from Malaysia and also im tech newbie

flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.

DreadApex said:
flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.
Click to expand...
Click to collapse
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter

RaybenBB said:
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter
Click to expand...
Click to collapse
Hi,
The "fastboot oem unlock" command don't work?

Elpatii said:
Hi,
The "fastboot oem unlock" command don't work?
Click to expand...
Click to collapse
Nope, also cant detect device using adb devices command. Tried same command in the other shield tablet, work just fine. Its not driver problem.
Tried fastboot oem unlock, and somehow it ask me on the shield to unlock or not, choose unlock and this error occured
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 3.736s

Maybe that you can flash the stock image from NVIDIA (https://developer.nvidia.com/shield-open-source)

Elpatii said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse

RaybenBB said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse
I think that's the best solution for now!

Bricked Google Pixel 3 XL

Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?

pech_alive said:
Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?
Click to expand...
Click to collapse
You can get to fastboot but not recovery?

Yeah if you can get to fastboot then unlock the bootloader and flash the factory image

Tulsadiver said:
You can get to fastboot but not recovery?
Click to expand...
Click to collapse
I can enter fastboot, but when I press to enter Recovery Mode the screen goes black and that's it, nothing happens, same when I press Start.
I can't unlock it because I get an error: failed (remote: 'flashing unlock is not allowed')

Was it 100% stock when you relocked it?
Sent from my crosshatch using XDA Labs

I would open the stock recovery on the PC and try flashing the factory image from there.

ridobe said:
Was it 100% stock when you relocked it?
Click to expand...
Click to collapse
It was 100% stock when I relocked it.
krabman said:
I would open the stock recovery on the PC and try flashing the factory image from there.
Click to expand...
Click to collapse
I tried that but this is what returns to me:
flash-all.bat
Sending 'bootloader_a' (8489 KB) OKAY [ 0.310s]
Writing 'bootloader_a' FAILED (remote: 'Fastboot command (flash is not allowed when locked')
Finished. Total time: 0.867s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.054s
Sending 'radio_a' (71148 KB) OKAY [ 1.834s]
Writing 'radio_a' FAILED (remote: 'Fastboot command (flash is not allowed when locked')
Finished. Total time: 2.084s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.054s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-4852902
Baseband Version.....: g845-00010-180619-B-4850223
Serial Number........: **********
--------------------------------------------
Checking product OKAY [ 0.060s]
Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse

I seem to remember from my Pixel (original) days that there was some trick to re-locking the bootloader or you would encounter issues.
You might consider searching the original Pixel's subforum here at XDA for that thread and see if the suggestions in it apply to you.
I think this might be the thread.
Read through it to see if anything can help you.
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615

"Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit..."
The bootloader on your device is pre-release? Not sure at all, love to get some schooling on where that bootloader came from. Where did you get the phone? From the Ukrainian with the stolen batch from Foxconn? Wow, I am getting Alex Jones like too quick or what? Lol
Sent from my Pixel 3 XL using Tapatalk

MArtyChubbs said:
"Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit..."
The bootloader on your device is pre-release? Not sure at all, love to get some schooling on where that bootloader came from. Where did you get the phone? From the Ukrainian with the stolen batch from Foxconn? Wow, I am getting Alex Jones like too quick or what? Lol
Click to expand...
Click to collapse
A friend of mine bought this phone from a website similar to eBay.
The software was stock.

pech_alive said:
Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?
Click to expand...
Click to collapse
Of course when in recovery it's all black. You have to hold vol up and power then menu pops up.

Since it's already a brick, try fastboot flashing unlock_critical
Sent from my Pixel 3 XL using Tapatalk

lucky_strike33 said:
Of course when in recovery it's all black. You have to hold vol up and power then menu pops up.
Click to expand...
Click to collapse
If the Andorid Robot picture appears, pressing the Power key and click Volume Up once will bring up the menu, however, his screen is black..? I get the robot, but yet to see a black screen. Good tip cuz that may be his way out of this mess.
Regarding the older bootloader, wouldn't the newer bootloader in the current factory image upgrade it? OR (put my custom made tinfoil hat on now) Google has blocked the stolen phones from firmware updates or bricks them..? Toots and Farts, you're screwed. (Taking hat off now)
I've always unlocked my pixels right away (lucked out on my VZW Pixel XL) and haven't encountered BL mismatch unless downgrading locked BL from other manufacturers.
There were at least 120 stolen phones sold prior to launch and unless you bought it from Google or an authorized carrier, I am suspicious..?
superchilpil said:
Since it's already a brick, try fastboot flashing unlock_critical
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
But, wouldn't he need to Go to Developer Options and enable OEM unlocking first?

superchilpil said:
Since it's already a brick, try fastboot flashing unlock_critical
Click to expand...
Click to collapse
People have already done this on working Pixel 3 XL's and all it did was returned an error.

I've gota a vague recollection of needing to format before flashing the image in this situation. Anyone confirm our deny?

MArtyChubbs said:
If the Andorid Robot picture appears, pressing the Power key and click Volume Up once will bring up the menu, however, his screen is black..? I get the robot, but yet to see a black screen. Good tip cuz that may be his way out of this mess.
Regarding the older bootloader, wouldn't the newer bootloader in the current factory image upgrade it? OR (put my custom made tinfoil hat on now) Google has blocked the stolen phones from firmware updates or bricks them..? Toots and Farts, you're screwed. (Taking hat off now)
I've always unlocked my pixels right away (lucked out on my VZW Pixel XL) and haven't encountered BL mismatch unless downgrading locked BL from other manufacturers.
There were at least 120 stolen phones sold prior to launch and unless you bought it from Google or an authorized carrier, I am suspicious..?
But, wouldn't he need to Go to Developer Options and enable OEM unlocking first?
Click to expand...
Click to collapse
True, that didn't occur to me. But since it was unlocked prior it may still be unlockable.
bp328i said:
People have already done this on working Pixel 3 XL's and all it did was returned an error.
Click to expand...
Click to collapse
Being a possible dev unit it might not error out with said command. At least that was my thought process. Doesn't hurt to try anyway? If it fails, it fails. Can't hurt to try.
Sent from my Pixel 3 XL using Tapatalk

I just soft bricked my PXL3; this means access only to fastboot ( is under warranty ) and you can get it back with fastboot flashing unlock critical then flash the factory image i don't get it why you can't

I thought flashing unlock critical was p2xl and not applicable to p3xl? And was your bootloader relocked prior to softbrick?
Sent from my Pixel 3 XL using Tapatalk

Update your adb tools on your computer and try flashing stock images again. Then reboot.

Help, i'm dealing with an issue too, everything was working fine, rooted with magisk , turned off my phone to charge, it reached 100% turned it back on, and it won't boot up, I see the G logo with a grey loading bar white background screen it does this for a few minutes and it reboots and gives me a screen that says "can't load android system. Your data may be corrupt. If you continue to get this message you may need to perform a factory data reset and erase all user data stored on this device" . I don't want to do a factory reset? WTH is going on here.
The last major change i did is install greenify4magisk but i didn't enable it (unchecked in magisk screen)
Help!
Edit: How do i do rescue OTA?

Question [Solved] Re-locking bootloader - no fastboot commands working

Hi everyone.
I´ve decided today that I want to re-lock my bootloader on Lenovo P11 tablet and I discovered no fastboot commands work on that.
I installed clean version of ROM from Lenovo Rescue and Smart Assistant (TB_J606L_S120217_210805_ROW) but still nothing works.
Normally i reboot to Fastboot and try "fastboot flashing lock" but i recieve:
< waiting for any device >
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
When i try others like "fastboot oem lock" i recieve:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Does anyone has any advice what can I do to relock bootloader?

1. enable developer option
2. enable oem unlock in developer option
3. boot to fastboot mode and run
fastboot flashing lock

Thanks @ong14 for your reply but as you can see above I already tried that...

If you're on chinese firmware, try "fastboot oem unlock-go".

Sadly I get this response for this command:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Is it possibly because of version of my ADB and Fastboot tools? I downloaded many versions (lastly directly from Android Studio) but it didn´t fix anything. @ong14, could you possibly upload the tools you are using?

Sorry for my last reply, it should be "fastboot oem lock-go".
AFAIK, if you're on global rom, use this "fastboot flashing lock".
And if you're on chinese rom, use this "fastboot oem lock-go"
I'm using an old minimal adb and fastboot.

It is totally OK, I am grateful that you are trying to help me at all.
I will try your old adb and fastboot tools and see what happens.
Sadly I don´t have much hope. I am on global rom and command "fastboot flashing lock" resulted only in:
"
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
"
I will keep you posted about my progress and what else I tried.

Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!

kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
My guy, you are brilliant. I wonder why the change from oem to flashing was done and were you getting sent to that fastbootd menu too? This worked for my 2020 Moto Edge and I don't know how much longer I would have needed without you.
Thanks.

kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
Install RSA from Lenovo also works, and you can run rescue if you want to go back to 100% bone stock

kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
Where and how do you get the drivers for this tablet? For some reason I'm stuck in (what I think) is the exact same screen on my tablet. It says fastboot... in the lower left hand corner and you can hear the disconnect chime come from my laptop every few seconds. I punch in fastboot devices and it's stuck in limbo, no error codes or anything.

BakedinRC said:
Where and how do you get the drivers for this tablet? For some reason I'm stuck in (what I think) is the exact same screen on my tablet. It says fastboot... in the lower left hand corner and you can hear the disconnect chime come from my laptop every few seconds. I punch in fastboot devices and it's stuck in limbo, no error codes or anything.
Click to expand...
Click to collapse
Did you check device manager?

I didn't think I had to, when I plug in the tablet it pops up with the name and everything.

I'll try the Motorola drivers, is that going to solve the fastboot stuck screen?

Where do I go about getting the Motorola drivers?

hey mate. i had problem. now my Xiaoxin Tablet Pro 2021 having widevine L3 even i already lock the BootLoader and Stock Rom. how do i get Widevine L1 ?

kure94 said:
Well, sadly, still nothing. I tried everything I could think of. I even tried different PC, flash rom with QFIL even with stock bootloader. I still get the same response.
Did anyone else run into this problem?
Edit: After further investigation it seems that I shouldn´t be in the fastboot mode but in the bootloader mode. There i should try "fastboot flashing lock".
Sadly, I see my P11 in device manager only as unrecognized Android device and no drivers seem to change that. Tablet also isn´t visible in the "adb devices" or the "fastboot devices"
Does anyone pls have working drivers or should I continue trying fastboot mode?
Edit2: OMG, I finally solved it. Yes, i shouild be trying to lock the bootloader from the bootloader mode from the start. After I booted to bootloader mode, installed Lenovo USB drivers (https://www.mediafire.com/file/1bzfblquyofokgi/LenovoUsbDriver_v1.1.34.zip/file) and it finally worked!
Click to expand...
Click to collapse
what did u do after installing the usb drivers?...can u pls explain in detail?....actually im facing the same problem again and again

me too can't figure it out, very sad

Question Bricked after multiple restarts. Bootloader locked. Stuck in fastboot

Hi everyone,
Tried getting some help via other sites but no luck, decided to come here to the experts.
My Pixel 7 pro had an issue where if you would push harder on the screen it would restart, it's a HW issue from what I understand.
Pushing the screen in multiple locations trying to find out exactly where is the point it triggers the restart lead to multiple restarts which bricked the phone.
Now my phone goes into fastboot and whenever i try to go into recovery mode or rescue mode it just cycles back into the fastboot.
I have tried multiple suggestions via connecting the phone to PC in order to fix it or rewrite the rom but I always get the error that my bootloader is locked (it's true i never unlocked it from Dev mode, not even sure i have USB debugging on).
Sending the phone to warranty is not an option, i bought it while on vacation and i live in a unsupported country.
If anyone has any idea how to fix this I would greatly appreciate it. I'm adding here a photo of the screen.
Also things that i have tried until now:
-Draining the phone completely and charging it back
-Sideload rom via ADB (Errors out with : Setting current slot to 'a' FAILED (remote: 'command (set_active is not allowed when locked')
fastboot: error: Command failed)
-Chrome flash utility/pixel rescue
Multiple people have pointed out that i don't need the bootloader unlocked to flash OEM ROM but the errors im getting about the bootloader being locked says otherwise.
Thanks again to anyone taking their time to read this post!

geo91 said:
Hi everyone,
Tried getting some help via other sites but no luck, decided to come here to the experts.
My Pixel 7 pro had an issue where if you would push harder on the screen it would restart, it's a HW issue from what I understand.
Pushing the screen in multiple locations trying to find out exactly where is the point it triggers the restart lead to multiple restarts which bricked the phone.
Now my phone goes into fastboot and whenever i try to go into recovery mode or rescue mode it just cycles back into the fastboot.
I have tried multiple suggestions via connecting the phone to PC in order to fix it or rewrite the rom but I always get the error that my bootloader is locked (it's true i never unlocked it from Dev mode, not even sure i have USB debugging on).
Sending the phone to warranty is not an option, i bought it while on vacation and i live in a unsupported country.
If anyone has any idea how to fix this I would greatly appreciate it. I'm adding here a photo of the screen.
Also things that i have tried until now:
-Draining the phone completely and charging it back
-Sideload rom via ADB (Errors out with : Setting current slot to 'a' FAILED (remote: 'command (set_active is not allowed when locked')
fastboot: error: Command failed)
-Chrome flash utility/pixel rescue
Multiple people have pointed out that i don't need the bootloader unlocked to flash OEM ROM but the errors im getting about the bootloader being locked says otherwise.
Thanks again to anyone taking their time to read this post!
Click to expand...
Click to collapse
Are you trying to sideload the full OTA? You can do that with a locked bootloader. Maybe you were trying to sideload the factory image instead?

Lughnasadh said:
Are you trying to sideload the full OTA? You can do that with a locked bootloader. Maybe you were trying to sideload the factory image instead?
Click to expand...
Click to collapse
Hi there! Yes i remember downloading a file from the link you provided. Got it under ""cheetah" for Pixel 7 Pro " file 13.0.0 (TQ2A.230405.003.E1, Apr 2023).
Issue is, following the instructions, it says i should go into recovery mode but recovery mode does not open for me it just goes back to fastboot screen (the pic i provided). It also mentions there that i shouldhave USB debugging turned on and i don't think it's on...

geo91 said:
Hi there! Yes i remember downloading a file from the link you provided. Got it under ""cheetah" for Pixel 7 Pro " file 13.0.0 (TQ2A.230405.003.E1, Apr 2023).
Issue is, following the instructions, it says i should go into recovery mode but recovery mode does not open for me it just goes back to fastboot screen (the pic i provided). It also mentions there that i shouldhave USB debugging turned on and i don't think it's on...
Click to expand...
Click to collapse
Did you double check to make sure it was the OTA file and not the Factory Image file?
You don't need USB Debugging enabled to sideload a Full OTA. Recovery mode allows for a couple of commands without having that enabled, including sideloading an OTA.
Do you see the Android robot when you try to get into recovery mode? If so, do you then press Power + Volume Up and then release Volume Up?

Forget USB-Debugging! You don't need that. Neither in fastboot mode nor in recovery. It's only mentioned to boot from system to recovery via ADB. So, it doesn't effect you. In fastboot mode USB-Debugging isn't recognized by your device/USB port.
If you can't boot into recovery the device must be send to a repair station. Are you really sure that recovery isn't accessible?

If volume button selection isn't working to get into recovery mode, I wonder if executing the fastboot reboot recovery command to get into it might work...
*you shouldn't need to have an unlocked bootloader to run that fastboot command, right?
also, OP confused me at the outset; he mentioned "Sideload rom via ADB" but also "fastboot: error: Command failed)" -- I've only sideloaded an OTA years ago without issue so I can't recall, but as the selection/name implies, isn't it supposed to be an ADB command, not a fastboot command (therefore, why is it a fastboot error?)?

simplepinoi177 said:
If volume button selection isn't working to get into recovery mode, I wonder if executing the fastboot reboot recovery command to get into it might work...
*you shouldn't need to have an unlocked bootloader to run that fastboot command, right?
also, OP confused me at the outset; he mentioned "Sideload rom via ADB" but also "fastboot: error: Command failed)" -- I've only sideloaded an OTA years ago without issue so I can't recall, but as the selection/name implies, isn't it supposed to be an ADB command, not a fastboot command (therefore, why is it a fastboot error?)?
Click to expand...
Click to collapse
adb sideload ota_name.zip
that is
Sébastien.

5.1 said:
adb sideload ota_name.zip
that is
Sébastien.
Click to expand...
Click to collapse
right?
so would that output "fastboot: error: Command failed" in any instance?
I doubt it, but for all I know, when running the "adb sideload" command, it also calls a fastboot command when applying it (sort of how "fastboot update" executes a bunch of command protocols like to automatically reboot after applying)...?

5.1 said:
adb sideload ota_name.zip
Click to expand...
Click to collapse
but OP is stuck in fastboot mode.

WoKoschekk said:
but OP is stuck in fastboot mode.
Click to expand...
Click to collapse
simplepinoi177 said:
If volume button selection isn't working to get into recovery mode, I wonder if executing thefastboot reboot recoverycommand to get into it might work...
*you shouldn't need to have an unlocked bootloader to run that fastboot command, right?
Click to expand...
Click to collapse
thoughts?

simplepinoi177 said:
thoughts?
Click to expand...
Click to collapse
the problem seems to be kernel related since he can't access recovery and/or system. A/B devices only use 1 Kernel for both. The recovery is merged into the boot.img and has no own partition with an own kernel.
Full firmware can't get flashed with a locked bootloader.
Full OTAs need the recovery due to payload.bin which depends on update-engine. So, OTAs need a shell environment.
The mentioned error output "set_active is not allowed when locked" shows that OP tried to flash an OTA. A full firmware won't change the slot by executing fastboot update UPDATE.ZIP. In this case fastboot uses the active slot to flash the firmware.
It's not possible to flash anything in fastboot mode + locked bootloader => device must be send to a repair station.
fastboot reboot recovery: If it's possible to execute this command (not all devices support that) it will do the same as hardware keys do. But it's worth a try.

WoKoschekk said:
Full OTAs need the recovery due to payload.bin which depends on update-engine. So, OTAs need a shell environment.
The mentioned error output "set_active is not allowed when locked" shows that OP tried to flash an OTA. A full firmware won't change the slot by executing fastboot update UPDATE.ZIP. In this case fastboot uses the active slot to flash the firmware.
Click to expand...
Click to collapse
Trying to understand better (don't mean to hijack the thread, but also I'm sure this will be helpful info to OP)...but is "set_active" called when sideloading OTA? I wouldn't think it would from an adb command ("apply OTA via adb")...
You mention "flash an ota" vs. sideload that's why; unless i'm getting confused by semantics...
If so, can it be concluded that the OP was mistakenly trying to flash the OTA instead of "sideloading" like he claimed (which is only done in recovery mode, correct? unless, again, semantics) as fastboot commands were executed instead of adb?
WoKoschekk said:
fastboot reboot recovery: If it's possible to execute this command (not all devices support that) it will do the same as hardware keys do. But it's worth a try.
Click to expand...
Click to collapse
@geo91, looks like if you can figure this, this might we worth a try....

simplepinoi177 said:
but is "set_active" called when sideloading OTA? I
Click to expand...
Click to collapse
My question: Do you find such a command in the flash-all.sh script inside a full firmware? It's not clear what update-engine really does. It doesn't follow any shell script.

simplepinoi177 said:
OP)...but is "set_active" called when sideloading OTA?
Click to expand...
Click to collapse
Here are the corresponding lines in the AOSP from the master branch of update-engine:
Java:
if (!result.success) {
LOG(ERROR) << "Unable to set the active slot to slot " << SlotName(slot)
<< ": " << result.errMsg.c_str();
}
return result.success;
source: https://android.googlesource.com/pl...heads/master/aosp/boot_control_android.cc#127

MOD TRANSLATION
"How can it be solved? I'm having the same problem with Google Pixel 7 Pro"
********************************************
كيف يمكن حلها؟ أواجه نفس المشكلة مع Google Pixel 7 Pro
omar qaissy, Greetings, and welcome to XDA. As a friendly reminder, we ask all members to please post in English as stipulated by Forum Rule 4 (quoted below) -- that you just agreed to when you first registered your account. Please consider this when you are creating a post in the future. Feel free to include your original message under the English message if you wish. If you do not know English, I encourage you to use any of the resources in the quote below. Your post has been translated as a one-time courtesy.
Thank you for your cooperation, and have a good one!
simplepinoi177 FSM (Forum Specific Moderator)
XDA Developers Forum Rules said:
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ , https://www.babelfish.com/ or https://fanyi.baidu.com/#auto/en or use one of your choice.
Click to expand...
Click to collapse