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
Related
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
Introduction
This is an UNOFFICIAL TWRP port for UMIDIGI F1 that works properly with encrypted /data partition in official ROM. I am aware that the UMIDIGI F1 already has TWRP built for it, but none of them seem to have decryption working properly. In fact, every single TWRP, even official ones, for any MT6771 device, seem to have non-functional decryption support. Through some digging I managed to fix decryption at least for UMIDIGI F1, so here is my version of TWRP for the device.
Known Bugs
- Screen may flash on the password-input UI. Anything else is fine though.
This TWRP has been tested with official ROM and my LineageOS 17 port (https://forum.xda-developers.com/android/development/unofficial-lineageos-17-0-umidigi-f1-t3997827) and it works fine.
This is UNTESTED on the F1 Play. ONLY TESTED on regular F1.
Why Bother
Because security matters. Using a cheap device should not mean giving up security, and more importantly, privacy.
Instructions
1. Unlock bootloader
2. Enable ADB debugging in system
3. Execute "adb reboot bootloader" while having your phone connected to PC
4. Execute "fastboot flash recovery <your_downloaded_recovery>.img"
5. Reboot phone while holding Volume Up + Power buttons
Note: The official ROM may overwrite the recovery, so you may need to re-flash the recovery if this behavior isn't prevented either by TWRP or manually.
Downlaods & Sources
20191103: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191103-twrp
- Fixed issues with Magisk and OpenGAPPS
20191102: https://github.com/PeterCxy/android_device_umidigi_F1/releases/tag/20191102-twrp
Device Tree: https://github.com/PeterCxy/android_device_umidigi_F1/tree/twrp-9.0
Modified TWRP (Required for decryption to work): https://github.com/PeterCxy/android_bootable_recovery
Updated to 20191103
I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img
This works good on my F1,
But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.
mrmazak said:
I appreciate your sharing this. I have added "system_image emmc" to the fstab file, so I can flash and backup the system.img
This works good on my F1,
But I tried to make this decrypt work for my other phone with 6771(Bold N1), but couldn't find all same files added to recovery/root from stock firmware.
Click to expand...
Click to collapse
Those files are extracted from vendor.img, but it can be different on different devices, e.g. keymaster version might be different. Also you will need to patch them using `patchelf` to make them use `/sbin/linker64` instead of `/system/bin/linker64`
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Shadow Of Leaf said:
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Click to expand...
Click to collapse
on other releases, no change was needed to boot on both. I would try as is first.
as long as you have working sp flash tool in case of issue.
mrmazak said:
on other releases, no change was needed to boot on both. I would try as is first.
as long as you have working sp flash tool in case of issue.
Click to expand...
Click to collapse
Cause i test it without changes , it reboot to system
I think because they have different kernels
I am unable to install twrp.
When I run the "fasthboot flash recovery" command, cmd aparace "waiting for de ice" and nothing happens on my phone ...
Am I doing something wrong?
no fastboot response
for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.
probably something stupid I'm doing wrong, will keep trying...
tarvoke said:
for some reason (most likely pilot error, lol) the phone doesn't show when I do "fastboot devices" - even though the F1's screen shows "fastboot mode" in very tiny letters on the bottom-left.
probably something stupid I'm doing wrong, will keep trying...
Click to expand...
Click to collapse
You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.
Try installing:
- https://androidmtk.com/download-15-seconds-adb-installer
- https://androidmtk.com/download-mtk-usb-all-drivers
- https://www.androidweblog.com/download-mediatek-usb-vcom-drivers/
Start the process from device on using adb commands to always allow access to the pc. I mean:
Code:
adb devices
and then if device is detected you will see a screen warning to "always allow...." then tap on yes; this suppress future conflicts, then
Code:
adb reboot bootloader
while on fastboot follow with
Code:
fastboot devices
SubwayChamp said:
You can operate from adb/fastboot folder and device can stay on fastboot mode but if drivers were not properly installed then no connection with pc.
Click to expand...
Click to collapse
thanks!
adb was already working (is how I made the thing reboot to bootloader, and yes I did tell it to permanently accept the computer I'm using.
this is on linux, so the drivers shouldn't be a problem... although SMH I never put USB IDs into the udev rules. which is interesting, because regular adb already worked fine without it - I have had phones in the past that some did, some did not, require the computer to know about vendor/hardware ID.
(and I know that the adb USB IDs are usually different than the ID for fastboot, as well.)
like I said, pilot error lol. but thank you again for the reply!
I have done the following:
Enabled Developer Options
Enabled USB Debugging
Enabled OEM Unlocking
Unlocked the bootloader with:
Code:
adb reboot bootloader
fastboot flashing unlock
Rebooted and Enabled USB Debugging again.
Then after downloading your recovery
Code:
adb reboot bootloader
fastboot boot ~/Downloads/recovery.img
But nothing happened.
I rebooted and thought I would try flashing
Code:
adb reboot bootloader
fastboot flash recovery ~/Downloads/recovery.img
It just paused on the boot screen saying "Your device has been unlocked and can't be trusted".
If I reboot then try to go direct to recovery:
Code:
adb reboot recovery
I end up with the broken android screen and "No command"
What am I missing?
opticyclic said:
I have done the following:
Enabled Developer Options
Enabled USB Debugging
Enabled OEM Unlocking
Unlocked the bootloader with:
Code:
adb reboot bootloader
fastboot flashing unlock
Rebooted and Enabled USB Debugging again.
Then after downloading your recovery
Code:
adb reboot bootloader
fastboot boot ~/Downloads/recovery.img
But nothing happened.
I rebooted and thought I would try flashing
Code:
adb reboot bootloader
fastboot flash recovery ~/Downloads/recovery.img
It just paused on the boot screen saying "Your device has been unlocked and can't be trusted".
If I reboot then try to go direct to recovery:
Code:
adb reboot recovery
I end up with the broken android screen and "No command"
What am I missing?
Click to expand...
Click to collapse
While in fastboot the first you should do is see if device is detected by pc with
Code:
fastboot devices
It looks like something is wrong with your path, I ever avoid path copying or moving the file/image to the adb/fastboot directory but anyway if you don´t want to do it you can copy the path from the bar where your recovery file is allocated, for example, if the file is in Downloads directory like it seems actually is, no matter what unit/drive you are in you can set an absolute value to avoid errors, look at this example: C:\Users\your_user\Downloads
If your device is detected then you can flash the recovery as you were trying to do it with
Code:
fastboot flash recovery recovery.img
and then you can reboot directly to it without need to reboot to system previously and this will prevent TWRP from being overwritten, with
Code:
fastboot boot recovery.img
hmm, so when I checked the udev rules, it already had one for MTK/mediatek - and the USB vendor is '08ed' in fastboot as well as in regular adb, so it wasn't a problem with udev/plugdev.
which I guess may mean the lunix generic android drivers for fastboot might be... "lacking" - I'll have to scrounge up a win7 laptop and try the recommended windows drivers.
SubwayChamp said:
...
It looks like something is wrong with your path, I ever avoid path copying or moving the file/image to the adb/fastboot directory but anyway if you don´t want to do it you can copy the path from the bar where your recovery file is allocated, for example, if the file is in Downloads directory like it seems actually is, no matter what unit/drive you are in you can set an absolute value to avoid errors, look at this example: C:\Users\your_user\Downloads
...
Click to expand...
Click to collapse
I don't think it was anything to do with the path as it output the file transfer size.
I think it was a combination of the following:
I wasn't pressing the right combinations of buttons after flashing.
i.e. holding VOL UP and pressing POWER on the screen saying "Your device has been unlocked and can't be trusted".
Rebooting might (?) have been reverting the recovery.
I was originally trying this on the firmware that was shipped 2019012414 but after flashing 2019090418 with SPFlashTool I had more success.
I also able to reboot to recovery directly after flashing with fastboot with the following:
Code:
fastboot oem reboot-recovery
Whichever was the key I can now reboot to recovery from adb too.
:good:
Your twrp eliminates fingerprint authentication.
I discovered something interesting, your twrp only works on my device, no other twrp works, but when I install it, I lose my fingerprint, it doesn't work at all.
Simply put, I must choose between the fingerprint or the root.
LyrielAlk said:
No other twrp works, but when I install it, I lose my fingerprint, it doesn't work at all.
Simply put, I must choose between the fingerprint or the root.
Click to expand...
Click to collapse
Try to clean flash last vendor build with spflash tool. First boot need stock recovery.
You don't need custom recovery to achieve root.
Maybe give a try to SNwriter (I never needed it though and can't help here).
Both of those twrp are not sticking. I have flashed with spoken flash tool v5 1944 win and I fastboot cmd with the same results.
Thanks
Gracias for this master ?
good
Shadow Of Leaf said:
hello
im willing to port your amazing twrp to our phone UMIDIGI F1 Play and i need permission to do it ???
thanks
Click to expand...
Click to collapse
good idea
I am looking for help as I cannot find anything on the Internet.
Situation:
I have rooted Pixel with December updates. I thought that it is high time to update it to February security updates.
I was trying to use OTA update and according to instruction ( https://developers.google.com/android/ota ) I should reboot to Recovery mode.
I am using Windows 10 x64.
Problem:
In Recovery mode I cannot connect via adb to phone. I am getting:
C:\WINDOWS\system32>adb devices
List of devices attached
0B041JEC216220 unauthorized
What is strange is fact that before I restarted to Recovery I had no problem and I even used adb to reboot to Recovery using below commands:
C:\WINDOWS\system32>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
0B041JEC216220 device
C:\WINDOWS\system32>adb reboot recovery
Tried solutions:
1. Removing adb keys on PC and Phone not helping.
2. Revoking USB debugging authorizations
3. Disabling / enabling USB debugging
4. Removing LeMobile ADB driver and installing official from https://developer.android.com/studio/run/win-usb
Any ideas what I can do next?
Are your platform tools up to date? You should be on 30.0.5.
Do you have a fastboot connection?
You could always remove the -w with a text editor and flash-all with the factory image
Edmontonchef said:
Are your platform tools up to date? You should be on 30.0.5.
Click to expand...
Click to collapse
Yes, I have the newest one.
Edmontonchef said:
Do you have a fastboot connection?
You could always remove the -w with a text editor and flash-all with the factory image
Click to expand...
Click to collapse
Yes, I have and I thought about it too, but I was afraid about such "dirty" flash. It seems that there is no other way, so I will try it and let know if adb is fixed after flash.
I did flash without -w and for adb in Recovery mode the same situation. At least I have updated ROM and it seems that everything works. Thanks!
I'm having the same issue...
TomekUser said:
I did flash without -w and for adb in Recovery mode the same situation.
Click to expand...
Click to collapse
you did what?
man, i miss the times where anyone could update his google phone without being a developer
When you download the stock rom from Google website and unpack the zip file, you will find there script flash-all.
In side that script one of the last commands has -w flag. If you don't want to wipe your user partition you can remove it, save the script and run it to flash the new stock.
ok, worked for me but lost root
narf0815 said:
ok, worked for me but lost root
Click to expand...
Click to collapse
Because you flashed stock rom - no surprise here. Patch boot.img with magisk or take the one which are published on forum and flash it one more time.
the one from here?
[Tutorial] Unlock Bootloader, get root and valid Safetynet
04/09/21 v2 Just install this Module via magisk manager: https://forum.xda-developers.com/attachments/hardwareoff_1-1-zip.5058405/ which is mentioned by this thread...
forum.xda-developers.com
narf0815 said:
the one from here?
[Tutorial] Unlock Bootloader, get root and valid Safetynet
04/09/21 v2 Just install this Module via magisk manager: https://forum.xda-developers.com/attachments/hardwareoff_1-1-zip.5058405/ which is mentioned by this thread...
forum.xda-developers.com
Click to expand...
Click to collapse
I don't have time to read whole thread to verify it. For sure you can find version matching your system version here:
[Stock/Rooted Boot Images] Pixel 4a [NOV 02]
We have stock factory boot images, I'm only posting the latest builds. The rooted android 10 images are rooted with latest Magisk 20.4 The rooted 11 images are rooted with latest Magisk Canary 4e0a3f5e You will still need to install the...
forum.xda-developers.com
i'm on p5 (wasn't even aware this is a p4a thread ) and i was able to patch the boot.img from stock image. thanks!
TomekUser said:
I did flash without -w and for adb in Recovery mode the same situation. At least I have updated ROM and it seems that everything works. Thanks!
Click to expand...
Click to collapse
did you find a solution for the original problem in the end?
i flashed the complete firmware then as well, just as you did, but i’m still curious as to why my devices (our devices) remain "unauthorized" in stock recovery. tried all of the mentioned solutions as well, no luck, perfectly "authorized" in the os itself, as well as in fastboot mode, just not in recovery ..
frank93 said:
did you find a solution for the original problem in the end?
i flashed the complete firmware then as well, just as you did, but i’m still curious as to why my devices (our devices) remain "unauthorized" in stock recovery. tried all of the mentioned solutions as well, no luck, perfectly "authorized" in the os itself, as well as in fastboot mode, just not in recovery ..
Click to expand...
Click to collapse
No, I did not
TomekUser said:
No, I did not
Click to expand...
Click to collapse
after a bit of research (by which i mean google/trial/error) i now feel VERY dumb, but let me share my results with you - for what it’s worth, and maybe it is/was the same problem for you:
apparently to sideload an OTA the device in recovery does NOT have to show "authorized"! (tried everything (creating new keys, checking the local key against the device-key manually, etc) and still it said "unauthorized".)
it turns out i tried to get the authorized-status on the screen where the android robot fell down and said "no command", so kinda "before" the actual recovery mode! get out of that screen (holding power button long, pressing vol-up short, letting go the power button) to get into the "menu" mode of recovery. still unauthorized, yes. then/there choose "sideload via adb" until the device says "waiting for input .." or something, and - TADAA - "adb devices" now tells you "sideload" next to the device id (instead of "unauthorized"). which is not only correct and "as expected", but actually works (for me) for sideloading an OTA!
mind blown, more or less. all the time i tried to get it "authorized" before checking if the actual OTA needs that anyway.
Try adb kill-server
Then adb start-server
fastboot reboot bootloader
Fastboot Devices
She should be authorized
frank93 said:
after a bit of research (by which i mean google/trial/error) i now feel VERY dumb, but let me share my results with you - for what it’s worth, and maybe it is/was the same problem for you:
apparently to sideload an OTA the device in recovery does NOT have to show "authorized"! (tried everything (creating new keys, checking the local key against the device-key manually, etc) and still it said "unauthorized".)
it turns out i tried to get the authorized-status on the screen where the android robot fell down and said "no command", so kinda "before" the actual recovery mode! get out of that screen (holding power button long, pressing vol-up short, letting go the power button) to get into the "menu" mode of recovery. still unauthorized, yes. then/there choose "sideload via adb" until the device says "waiting for input .." or something, and - TADAA - "adb devices" now tells you "sideload" next to the device id (instead of "unauthorized"). which is not only correct and "as expected", but actually works (for me) for sideloading an OTA!
mind blown, more or less. all the time i tried to get it "authorized" before checking if the actual OTA needs that anyway.
Click to expand...
Click to collapse
Sir you have no clue how much it is helpful for everyone like me who were scratching their heads on this error.
frank93 said:
after a bit of research (by which i mean google/trial/error) i now feel VERY dumb, but let me share my results with you - for what it’s worth, and maybe it is/was the same problem for you:
apparently to sideload an OTA the device in recovery does NOT have to show "authorized"! (tried everything (creating new keys, checking the local key against the device-key manually, etc) and still it said "unauthorized".)
it turns out i tried to get the authorized-status on the screen where the android robot fell down and said "no command", so kinda "before" the actual recovery mode! get out of that screen (holding power button long, pressing vol-up short, letting go the power button) to get into the "menu" mode of recovery. still unauthorized, yes. then/there choose "sideload via adb" until the device says "waiting for input .." or something, and - TADAA - "adb devices" now tells you "sideload" next to the device id (instead of "unauthorized"). which is not only correct and "as expected", but actually works (for me) for sideloading an OTA!
mind blown, more or less. all the time i tried to get it "authorized" before checking if the actual OTA needs that anyway.
Click to expand...
Click to collapse
your a life saver. I was totally stuck in recovery for updating ota of pixel 6 pro.
A simple solution is to unplug usb cable from phone.
kill the adb server: adb kill-server
restart the server: adb start-server
boot your phone into recovery mode.
select update using ADB.
once is ask for the package plug your phone back into the usb
type: adb devices.
Its should show your device and state sideload instead of unauthorized...
then type: adb sideload (package name.zip)
Hope this helps...
just hold Vol- during boot, login in safe mode, plug cable, authorize, profit. you can also simply reboot in full root mode afterwards as magisk already sorted out the problem.
-> all modules are disabled for your convenience, no need to delete and reinstall modules, just tick box again to reenable
-> phone is an airplane mode for your convenience, so that you don't leak some info w/privacy plugins temporarily off
I got the similar issue
> adb devices
abcdefgh device
> adb reboot fastboot
> fastboot reboot recovery
> adb devices
abcdefgh unauthorized
Do you know how to fix the device unauthorized in recovery mode?
As the title says, I have no OS and only have fastboot available.
I unlocked the bootloader and pushed TWRP 3.5.1_10-Nebrassy so that I could root with Magisk.
fastboot boot twrp.img
All went well to that point. Then I tried to flash TWRP.
fastboot flash recovery twrp.img
Then I had no OS. I tried to download the latest stock ROM, 11.2.9.9.LE25DA.
https://www.oneplus.in/support/softwareupgrade/details?code=PM1617074715494
I extracted the payload.bin and successfully flashed the files to fastboot.
https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Then I try to boot into fastbootd to install the other files.
fastboot reboot fastboot
Once in fastbootd, I have to choose a language from (I presume) Mandarin, Cantonese, and English. I choose English.
Then it says "fastbootd" across the top, but the cmd window is unresponsive, "< waiting for any device >"
I have to choose Advanced, or Exit.
I choose Advanced.
I have to choose "Reboot to fastboot," "Reboot to recovery," or "Ver 2.0"
I choose Reboot to fastboot because there is no recovery.
cmd is responsive, but I'm in fastboot, not fastbootd.
I try to flash the remaining files.
fastboot flash abl abl.img
I get the following message from the cmd window.
FAILED: <remote: 'Flashing is not allowed for Critical Partitions'>
fastboot error: error: Command failed
Obviously, because I'm not in fastbootd. Except I can't get a responsive cmd prompt in fastbootd.
I have also tried to flash TWRP again. It does not flash. I can push it over and it will boot up, but the touch screen is not responsive, so I have to hard reset to get back to fastboot.
fastboot boot twrp.img
So, at this point, all I have is fastboot and a bootloop.
Would someone please either direct me to a forum where this has been addressed (that I have obviously missed in my search), or please advise how to proceed? I would very much appreciate whatever guidance anyone can offer.
DoktorNo said:
As the title says, I have no OS and only have fastboot available.
I unlocked the bootloader and pushed TWRP 3.5.1_10-Nebrassy so that I could root with Magisk.
fastboot boot twrp.img
All went well to that point. Then I tried to flash TWRP.
fastboot flash recovery twrp.img
Then I had no OS. I tried to download the latest stock ROM, 11.2.9.9.LE25DA.
https://www.oneplus.in/support/softwareupgrade/details?code=PM1617074715494
I extracted the payload.bin and successfully flashed the files to fastboot.
https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Then I try to boot into fastbootd to install the other files.
fastboot reboot fastboot
Once in fastbootd, I have to choose a language from (I presume) Mandarin, Cantonese, and English. I choose English.
Then it says "fastbootd" across the top, but the cmd window is unresponsive, "< waiting for any device >"
I have to choose Advanced, or Exit.
I choose Advanced.
I have to choose "Reboot to fastboot," "Reboot to recovery," or "Ver 2.0"
I choose Reboot to fastboot because there is no recovery.
cmd is responsive, but I'm in fastboot, not fastbootd.
I try to flash the remaining files.
fastboot flash abl abl.img
I get the following message from the cmd window.
FAILED: <remote: 'Flashing is not allowed for Critical Partitions'>
fastboot error: error: Command failed
Obviously, because I'm not in fastbootd. Except I can't get a responsive cmd prompt in fastbootd.
I have also tried to flash TWRP again. It does not flash. I can push it over and it will boot up, but the touch screen is not responsive, so I have to hard reset to get back to fastboot.
fastboot boot twrp.img
So, at this point, all I have is fastboot and a bootloop.
Would someone please either direct me to a forum where this has been addressed (that I have obviously missed in my search), or please advise how to proceed? I would very much appreciate whatever guidance anyone can offer.
Click to expand...
Click to collapse
Try:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Thank you for the reply.
The device is already unlocked, but I did as you suggested and tried both commands.
For both attempts I got the following message:
FAILED <remote : ' Device already : unlocked!'>
Fastboot: error: Command failed.
@DoktorNo you don't flash twrp that way anymore. You have to boot into twrp, then flash from inside twrp itelf.
So
fastboot boot twrp.img
Then once twrp starts up, go to the advanced tab, and flash the recovery.
mx597turbo said:
@DoktorNo you don't flash twrp that way anymore. You have to boot into twrp, then flash from inside twrp itelf.
So
fastboot boot twrp.img
Then once twrp starts up, go to the advanced tab, and flash the recovery.
Click to expand...
Click to collapse
Great suggestion, except when I boot into twrp, I cannot use the touch screen. So twrp will boot, but it is not responsive. Any thoughts on how to make that work? Then I'd be nearly set.
Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota
XxBigBuckxX said:
Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota
Click to expand...
Click to collapse
I haven't tried it. I'll give it a go when I'm home this evening and post my results.
DoktorNo said:
I haven't tried it. I'll give it a go when I'm home this evening and post my results.
Click to expand...
Click to collapse
Also, are you using the most updated version of twrp for the 9/9 pro? I'm sure you are, but just checking.
mx597turbo said:
Also, are you using the most updated version of twrp for the 9/9 pro? I'm sure you are, but just checking.
Click to expand...
Click to collapse
Great question and worth asking. I used twrp 3.5.1_lemonade-Nebrassy.
3.5.1-lemonadep-Nebrassy
Since there's no OS, there is no interface with the touchscreen, so I can't interact with it in that way. I can sideload twrp but then it's just an image on the screen.
There is a newer one TWRP-3.5.2-lemonadep-Nebrassy. If your unable to use twrp to flash or sideload MSM Tool is pretty simple. Use the original cable and put it EDL mode and run it.
DoktorNo said:
Great suggestion, except when I boot into twrp, I cannot use the touch screen. So twrp will boot, but it is not responsive. Any thoughts on how to make that work? Then I'd be nearly set.
Click to expand...
Click to collapse
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.
mx597turbo said:
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.
Click to expand...
Click to collapse
This works , mouse and keyboard
XxBigBuckxX said:
Does the msm tool not work for you? I have to use the one plus 9 pro in version to restore mine.. And you can try sideloading the ota
Click to expand...
Click to collapse
Msm will not download from the link you provided. GDrive scans the .exe and dll files before download and says there is a virus, so I am only able to download the other half of the files.
XxBigBuckxX said:
There is a newer one TWRP-3.5.2-lemonadep-Nebrassy. If your unable to use twrp to flash or sideload MSM Tool is pretty simple. Use the original cable and put it EDL mode and run it.
Click to expand...
Click to collapse
Got the new twrp. Still no touch screen.
mx597turbo said:
Just a thought, as I am unable to test. What if you plugged a usb mouse into the phone using an A to C adapter? May be worth a try, but not sure if twrp has mouse support. I have an adapter somewhere - If I find it, I'll let know know if this works.
Click to expand...
Click to collapse
I will have to buy an adapter.
Here , that was more of a guide. List of unbrick tools select your proper one from here. If you get errors try the One Plus 9 Pro IN version as that what worked with nothing else for a lot of people including me.
DoktorNo said:
Msm will not download from the link you provided. GDrive scans the .exe and dll files before download and says there is a virus, so I am only able to download the other half of the files.
Click to expand...
Click to collapse
Last thing you will need is the driver, here is the signed Microsoft version.
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
I Find it easier to have push start on msm tool at this point
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them. and it should connect and flash.
XxBigBuckxX said:
Here , that was more of a guide. List of unbrick tools select your proper one from here. If you get errors try the One Plus 9 Pro IN version as that what worked with nothing else for a lot of people including me.
Click to expand...
Click to collapse
Downloading now. I'll try this and report back. Thanks.
DoktorNo said:
Downloading now. I'll try this and report back. Thanks.
Click to expand...
Click to collapse
Okay and you might have to try it power cycle it a few times trying to get into edl mode especially if you do not already have working drivers. But windows update will pull working drivers as well if your not sure how to use a .cab file. There are guides everywhere even video if if you need. I've tested some weird things on the 7t pro McLaren and 9 pro and msm tool has always brought them back.
hj
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.