Hello everyone,
after unlocking my bootloader (on a Realme 5 Pro) to install TWRP and custom ROM, I am now stuck at trying to make fastboot do anything.
No matter which fastboot command I try, the phone won't execute it. I instantly get a "FAILED" and "(No error)" returned and the phone exits fastboot, showing some logo with a chinese message, as well as "press any key to shutdown" in the top left corner.
The only excpetions to that behaviour:
1. "fastboot devices" works as expected and recognizes the phone.
2. "fastboot boot [path to TWRP .img file]" sometimes gets stuck at "downloading boot.img..." indefinitely, sometimes it fails like all the other commands
3. "fastboot flash recovery [path to TWRP .img file]" gives an instant "FAILED", but the error message is "requested download size is more than max allowed"
I've tried re-locking and unlocking the bootloader, when unlocked both colorOS and fastboot recognize the bootloader as being unlocked.
I have no clue what to try at this point, hopefully someone can help me out?
Same problem here.
Mine is Realme 3 pro with the new version of realme UI, RMX1851, C.04, I have unlocked bootloader without downgrading it to color os 6, but now I cannot flash twrp in my device. After going into fastboot mode, after applying the commands, it says "FAILED" (remote: GetVar variable not found) and sometimes directly "ERROR"
The fix was an incredibly easy one, but I only found it/got the idea through a lot of googling... simply used a different PC (that I never used adb and fastboot with before), let windows search for drivers online, and BAM, it works!
Hopefully this will help someone in the future.
If you don't have more than one PC, I guess the best bet would be uninstalling all adb and fastboot related drivers.
Related
Hey folks,
i have a problem with my shieldtablet. The fastboot doesn't work properly. I cannot load anything via "fastboot flash blablabla.img". Minimal ADB and Fastboot just shows "waiting for device" and if i check the devices via "fastboot devices" is just shows nothing but the normal command prompt.
Then i did a mistake and flashed the twrp 3 version with an older one, so i am unable to enter the recovery-mode. If i chose Recovery Mode via bootloader (or if i restart the tablet into recovery mode) it has a short bootloop and then after some trials it starts normal into Blisspop.
How could i flash this without the fastboot? Is there any trick i could use?
The tablet is unlocked. I had several custom-roms installed. Currently Blisspop 6.4 without playstore.
That looks like your PC is not seeing your tablet. Boot into fastboot mode, connect it to your PC and look in Windows device manager for the device.
Thanks a lot! ADB worked fine on Win10. Last time I flashed the recovery was on my old Win7-System. It seems, that the Upgrade deleted just the fastboot drivers.
One last question: is it normal, that if i chose the fastboot protocoll entry on the bootloader, that it restarts the bootloader?
Yes, that's normal. The menu entry is redundant because when you see it you are in fastboot mode already.
Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John
JR44 said:
Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John
Click to expand...
Click to collapse
After fastboot flashing TWRP, type the command below.
adb reboot recovery
Sent from my SM-S767VL using Tapatalk
Thanks for reply but ONLY boots into the stock android 8 recovery and will not boot into twrp
tried various methods and each time adp says flashed recovery (tried it with different names recovery.img twrp.img etc)
and shows data transferred on 'phone screen.
BUT your suggestion and all those on the various websites but will still not boot into the custome recovery
and although I am used to working on Samsung 'phones, this one beats me! Eveb fulll factory reset 3 times!
TWRP is recovery-20181231-0237.img from multiple sites.
I do not know how to find if the recovery has actually been installed or something is stopping it running.
Just tried again in case:-
ANDROID RECOVERY
OUKITEL /WP2/WP2
8.0.0/o00623/1532584305
user/release-keys
use vol.....
hen usual list+-
reboot system now
reboot to bootloader
etc etc
no TWRP
'Phone does show "strange condition - unlocked bootloader - device can not be trusted" on each boot,
so everything else seems fine.
Spent 5 hours on this! Was going to use super su but could use magisk instead IF I can get to the
recovery stage!
rgds
JR44 said:
Sorry, can not find any threads her on this
New Oukitel WP2 Android 8
Unlocked bootloader using ADB
ran "fastboot flash recovery WP2.img" and computer said finished
'phone said OK!
Tried "fastboot recovery" BUT all the 'phone will display is ==> fastboot mode in micro writing bottome left of screen
Tried volume up/power - nothing volume down/power - after warning about unlocked bootloader
bot into STANDARD Android 8 boot menu.
Having unlocked many Samsung 'phones, this is confusing me!
Also, after this how do you actually root the 'phone (or is twrp the root kit) as super SU reports
unrooted telephone.
Any clues gratefully accepted
Thanks
John
Click to expand...
Click to collapse
JR44 said:
Thanks for reply but ONLY boots into the stock android 8 recovery and will not boot into twrp
tried various methods and each time adp says flashed recovery (tried it with different names recovery.img twrp.img etc)
and shows data transferred on 'phone screen.
BUT your suggestion and all those on the various websites but will still not boot into the custome recovery
and although I am used to working on Samsung 'phones, this one beats me! Eveb fulll factory reset 3 times!
TWRP is recovery-20181231-0237.img from multiple sites.
I do not know how to find if the recovery has actually been installed or something is stopping it running.
Just tried again in case:-
ANDROID RECOVERY
OUKITEL /WP2/WP2
8.0.0/o00623/1532584305
user/release-keys
use vol.....
hen usual list+-
reboot system now
reboot to bootloader
etc etc
no TWRP
'Phone does show "strange condition - unlocked bootloader - device can not be trusted" on each boot,
so everything else seems fine.
Spent 5 hours on this! Was going to use super su but could use magisk instead IF I can get to the
recovery stage!
rgds
Click to expand...
Click to collapse
After flashing TWRP, you can't let the device boot to any other mode, you have to boot directly to recovery. If you allow the device to boot into any mode other than recovery, it will revert back to stock recovery. The only way to keep TWRP is to boot directly into TWRP immediately after flashing.
Try this, flash the TWRP file using the fastboot flash recovery (name of file) command. Then, after it flashes, try using this command:
fastboot boot recovery (name of your specific file)
This may allow you to boot into TWRP and keep TWRP recovery so that you can boot into it at any time after that.
Sent from my SM-S767VL using Tapatalk
Thanks for reply but does not work...
WP2 has already had bootloader unlocked developer options and adb commands, including an automatic wipe of 'phone.
Then without touching anything else, the follwoing have been entered from a clean boot of 'phone and Win7. twrp.img file is named "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
issue command> adb reboot bootloader
computer response OK
'phone shows "fastboot" in miniscule text
issue command> "fastboot flash recovery recovery.img"
computer says> "target reported max download size 134217728 bytes"
then
"sending 'recovery' (15010kb)"
then
"OKAY [0.65 seconds}"
then
"writing 'recovery'..."
then
"finished. total time 1.06 s"
'phone says "transmission ok then a checksum"
after a wait
issue command> "fastboot boot recovery.img"
computer says "downloading 'boot.img'"
then
"OKAY 0.64 s"
then
"booting....."
then OKAY 0.47s"
then
"finished"
'Phone boots into normal logo then to a NORMAL STARTUP - NOT to any bootloader
argh!!!
adb devices returnes OUKIWP2000015176
Any clues as to what is wrong or what I am missing!
cheers
John
UK
JR44 said:
Thanks for reply but does not work...
WP2 has already had bootloader unlocked developer options and adb commands, including an automatic wipe of 'phone.
Then without touching anything else, the follwoing have been entered from a clean boot of 'phone and Win7. twrp.img file is named "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
twrp file is "recovery.img" in same directory as adb etc (C:\ for testing)
issue command> adb reboot bootloader
computer response OK
'phone shows "fastboot" in miniscule text
issue command> "fastboot flash recovery recovery.img"
computer says> "target reported max download size 134217728 bytes"
then
"sending 'recovery' (15010kb)"
then
"OKAY [0.65 seconds}"
then
"writing 'recovery'..."
then
"finished. total time 1.06 s"
'phone says "transmission ok then a checksum"
after a wait
issue command> "fastboot boot recovery.img"
computer says "downloading 'boot.img'"
then
"OKAY 0.64 s"
then
"booting....."
then OKAY 0.47s"
then
"finished"
'Phone boots into normal logo then to a NORMAL STARTUP - NOT to any bootloader
argh!!!
adb devices returnes OUKIWP2000015176
Any clues as to what is wrong or what I am missing!
cheers
John
UK
Click to expand...
Click to collapse
I don't know, I'll keep looking, if I find anything useful, I'll post it.
Sent from my SM-S767VL using Tapatalk
Still not working
If anyone else is reading this post I am still unable to flash the twrp recovery
downloaded from http://www.mediafire.com/file/cp6cw164fse2bpa/Oukitel_WP2_twrp.rar/file
Every time I try the flash commands it looks like it has sent to device - only takes 0.5 seconds and
'phone says received.
Unable to boot into recovery twrp - always comes back with stock android 8 recovery OR an error
message about can not open.
Any more suggestions please as annoying! OR is there adifferent twrp recovery out there I can
]use with Odin? or Magiisk?
Many thanks
john
JR44 said:
If anyone else is reading this post I am still unable to flash the twrp recovery
downloaded from http://www.mediafire.com/file/cp6cw164fse2bpa/Oukitel_WP2_twrp.rar/file
Every time I try the flash commands it looks like it has sent to device - only takes 0.5 seconds and
'phone says received.
Unable to boot into recovery twrp - always comes back with stock android 8 recovery OR an error
message about can not open.
Any more suggestions please as annoying! OR is there adifferent twrp recovery out there I can
]use with Odin? or Magiisk?
Many thanks
john
Click to expand...
Click to collapse
Odin is for Samsung devices only. You can't use Odin on your device.
Sent from my SM-S767VL using Tapatalk
Am I the only one not being able to run Fastboot commands on the ROG 5?
I can connect with Fastboot fine and the device is identified but every command I try to run returns an error/denied on the Remote end (i.e from the device end). Simple read example: "Fastboot oem device-info" returns Remote: "Command not supported in default implementation", same with many others. Trying to flash TWRP to recovery_a (or b) returns "Remote: Unknown File or Directory". Tried everything I can think of. Does anybody have any good ideas for fixing this? Thanks in advance.
A lot of the _a partitions are only available by entering userspace fastboot (fastboot reboot fastboot) and that is a quick and easy way to soft brick.
twistedumbrella said:
A lot of the _a partitions are only available by entering userspace fastboot (fastboot reboot fastboot) and that is a quick and easy way to soft brick.
Click to expand...
Click to collapse
I soft bricked it once already but managed to get out of it. But I can't even do simple read commands let alone flashing anything, all Fastboot commands are sent to the device but return a Remote rejected/error. I also suspect the bootloader may still be locked despite having run the ASUS unlock tool and seeing the unlock warning on boot (I have no way of confirming). I may have to ask ASUS for some help...
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
Hey guys, I need help flashing my Google pixel 2. It was off for a couple of months and now when I am trying to start it, its not booting without putting it on charge and even then it only shows the battery icon then the google icon and restarts (So a bootloop). But when I press and hold the power button and volume down key, it goes in the fastboot mode ( the one where all device information is shown with an Android Logo) (Pic att).
If I select Download mode, it just shows operation denied and if I select recovery mode then it goes to bootloop again. Also as far as I remember when I last used the phone, the usb debugging was turned off so please suggest what to do from here.
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Alekos said:
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Click to expand...
Click to collapse
Hey thanks for the update man. I know I should have kept atleast oem unlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
mayankggrwl said:
Hey thanks for the update man. I know I should have nlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
Click to expand...
Click to collapse
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Alekos said:
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Click to expand...
Click to collapse
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
mayankggrwl said:
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
Click to expand...
Click to collapse
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Alekos said:
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Click to expand...
Click to collapse
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
mayankggrwl said:
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
Click to expand...
Click to collapse
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how the op in that thread above fixed his Pixel 2 with Skipsoft tool. His Device state said Locked in his screenshot on his post.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
edit--try these commands
fastboot erase system
fastboot erase data
fastboot erase cache
Alekos said:
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how those users in the thread flashed the bootloader image since I didn't think you could if the device state is locked, but worth a try.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
Click to expand...
Click to collapse
Okay great !! Thanks for these. Ill go through that thread and will see if any of the listed methods work. Will also try that software. In a rush so will try these later on and then ill update you.