Post flashing LOS 15.1-20181022 (skipped a few nightlies prior to it, as I usually do), I noticed persistent heating of the phone even when idle. So I tried flashing lineage-15.1-20181015 and lineage-15.1-20181008, however the issue continued so I tried to flash lineage-15.1-20180924 (wiped delvik / cache as before) but now my phone is stuck in screen lock loop. When I enter the PIN, screen goes blank and comes back as if it just woke up from sleep. There is nothing wrong with PIN entered. It shows the regular wrong PIN message with any other value instead of going blank.
Now when I try to use 'ADB sideload', 'ADB reboot fastboot' or 'ADB reboot recovery' commands as it shows the device is unauthorized.
The exact message is -
"error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device."
Restarting adb server is no help. Can I make a recovery from here, if possible with LOS otherwise resetting back to CM
I'd appreciate any help
Please note:
- USB debugging is enabled. It shows on the lockscreen as well and device is recognized but ADB keeps showing unauthorized
- I can not force boot into fastboot as my volume rocker is broken
Related
I am stuck on the Decyption screen where it says "To start Android, enter your password". I have seen a few threads about this issue but they managed to solve the issue by reflashing or re-unlocking the bootloader. However, I am unable to do any of these things.
I have been on ViperOneM8 for quite a long time now and everything was working fine. I unlock my screen by swiping up on the screen while the screen is off. Felt the vibration to unlock but the screen stays blank. Had to force reboot it to make it work again. A few days later, this exact same issue happened again, but before I was able to reboot the device, it rebooted on its own and went into the said decryption screen. I enter a random word for password and it says, password is correct but data is corrupted; must factory reset to use phone.
Alright, so I have factory reseted, nothing happened. It wiped my data and sd card, same decryption screen.
I've used the bootloader to flash a stock android, I remember it succeeded but restarted to the same screen.
I've used twrp to re-flash multiple roms, all succeeded, restarted to same thing.
I've wiped data, full wipe, you name it, restarted to same thing. Once it reboots it would show the ViperOne boot, so something isn't wiping.
I even went into the phone's data and manually deleted everything in internal storage with my pc, restarted the phone, same thing. Checked the internal storage again, everything that was there got restored.
I've used adb and fastboot to push data, same thing. I've used the dottat .exe installer, goes through the entire process, reboots... same thing.
I've tried reflashing another recovery, success, but it boots into the same recovery.
I've tried doing the SuperCID and going through htcdev to unlock the device again, but it fails when pushing the key. SuperCID also resets whenever I restart the device. I've tried locking the bootloader with fastboot but that fails.
One thing I couldn't do is boot into the RUU mode. 'fastboot oem rebootRUU' doesn't seem to work for me. It reboots the device but boots up and goes into the decryption screen.
When I try the 0P6BIMG with bootloader, it seems to restart before completing the installation now. But I remember it went through successfully before, but still boots into the decryption screen.
It seems like no matter what I do, the phone restores itself to the previous state that it's in. That or nothing is actually affecting the data.
I am at a lost of what to do. I feel like maybe it's a damaged hardware but at the same time I am unsure. Anybody have any suggestions at all?
kyuuku said:
I am stuck on the Decyption screen where it says "To start Android, enter your password". I have seen a few threads about this issue but they managed to solve the issue by reflashing or re-unlocking the bootloader. However, I am unable to do any of these things.
I have been on ViperOneM8 for quite a long time now and everything was working fine. I unlock my screen by swiping up on the screen while the screen is off. Felt the vibration to unlock but the screen stays blank. Had to force reboot it to make it work again. A few days later, this exact same issue happened again, but before I was able to reboot the device, it rebooted on its own and went into the said decryption screen. I enter a random word for password and it says, password is correct but data is corrupted; must factory reset to use phone.
Alright, so I have factory reseted, nothing happened. It wiped my data and sd card, same decryption screen.
I've used the bootloader to flash a stock android, I remember it succeeded but restarted to the same screen.
I've used twrp to re-flash multiple roms, all succeeded, restarted to same thing.
I've wiped data, full wipe, you name it, restarted to same thing. Once it reboots it would show the ViperOne boot, so something isn't wiping.
I even went into the phone's data and manually deleted everything in internal storage with my pc, restarted the phone, same thing. Checked the internal storage again, everything that was there got restored.
I've used adb and fastboot to push data, same thing. I've used the dottat .exe installer, goes through the entire process, reboots... same thing.
I've tried reflashing another recovery, success, but it boots into the same recovery.
I've tried doing the SuperCID and going through htcdev to unlock the device again, but it fails when pushing the key. SuperCID also resets whenever I restart the device. I've tried locking the bootloader with fastboot but that fails.
One thing I couldn't do is boot into the RUU mode. 'fastboot oem rebootRUU' doesn't seem to work for me. It reboots the device but boots up and goes into the decryption screen.
When I try the 0P6BIMG with bootloader, it seems to restart before completing the installation now. But I remember it went through successfully before, but still boots into the decryption screen.
It seems like no matter what I do, the phone restores itself to the previous state that it's in. That or nothing is actually affecting the data.
I am at a lost of what to do. I feel like maybe it's a damaged hardware but at the same time I am unsure. Anybody have any suggestions at all?
Click to expand...
Click to collapse
Sounds like you have one of the few that have been popping up where the entire phone becomes write protected.
Before running the ruu run the following fastboot commands.
Fastboot oem task 28
Fastboot oem task 29
If any errors re-run the command.
Then run ruu.
dottat said:
Sounds like you have one of the few that have been popping up where the entire phone becomes write protected.
Before running the ruu run the following fastboot commands.
Fastboot oem task 28
Fastboot oem task 29
If any errors re-run the command.
Then run ruu.
Click to expand...
Click to collapse
I tried those commands and it looks successful, but once I rebootRUU it would just reboot and load to the decryption screen again.
I also tried the 0P6BIMG method after those commands, no luck.
kyuuku said:
I tried those commands and it looks successful, but once I rebootRUU it would just reboot and load to the decryption screen again.
I also tried the 0P6BIMG method after those commands, no luck.
Click to expand...
Click to collapse
Sounds like your phone did end up write protected. You need a new motherboard.
The ones I have seen like this don't even allow you to lock the boot loader or turn s back on either.
dottat said:
Sounds like your phone did end up write protected. You need a new motherboard.
The ones I have seen like this don't even allow you to lock the boot loader or turn s back on either.
Click to expand...
Click to collapse
Ahh that's too bad. It was what I expected though.
Thank you anyway for the help!
Hello everyone,
After an OTA updates on phone, the phone phone got struck on "NO command" screen, but after some research i am able to get into bootloader.
Tried below solutions but failed:
1.Tried a factory reset, after this it restarted the device on struck on ERASING screen...waited for a long time it got into the loop of erasing mode.
2. tried fastboot options but no luck..
In fastboot screen it shows DEVICE IS LOCKED Status code: 0
Tried to unlock the phone with the unlock code but it says "Allow OEM enable" on the developer settings option but i cant as it got struck on fastboot screen...
Any help can be much appreciated.Thank you
mahi515 said:
Hello everyone,
After an OTA updates on phone, the phone phone got struck on "NO command" screen, but after some research i am able to get into bootloader.
Tried below solutions but failed:
1.Tried a factory reset, after this it restarted the device on struck on ERASING screen...waited for a long time it got into the loop of erasing mode.
2. tried fastboot options but no luck..
In fastboot screen it shows DEVICE IS LOCKED Status code: 0
Tried to unlock the phone with the unlock code but it says "Allow OEM enable" on the developer settings option but i cant as it got struck on fastboot screen...
Any help can be much appreciated.Thank you
Click to expand...
Click to collapse
Do the factory reset again, and just let it sit until it finishes which can be 20 minutes or more, some users have even claimed it takes an hour but I have never seen that personally... although you only really needed to clear the cache partition but it is too late for that now.
Hi there,
I did a recent reinstall of LineageOS (Lineage 18.1 - 20210501) on Xiaomi's Poco F1. I chose to encrypt the device after the installation.
Now, I am faced with a strange error, when I reboot the phone it will come to the interface where I can enter the decryption passcode, but immediately shut down. (A white overlay appears with "Powering off" or similar.) This happens, when the phone is running on battery or connected to power. Only, when the phone is connected to my computer (with ADB running in the background, but no idea if that is the cause) will it power on. The phone decrypts fine in TWRP in any case. (TWRP shows me a pattern input field instead of a passcode field, but I can use the shell to decrypt it.)
My question is: What should I do from here? Should I do a full backup, flash the device with a different nightly build and hope for the best? Or is there a way to troubleshoot this?
In principle I could also carry my PC with me at all times to be sure, but I would like to avoid that .
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
rraphrr said:
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
Click to expand...
Click to collapse
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
muhammad42620 said:
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
Click to expand...
Click to collapse
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
rraphrr said:
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
Click to expand...
Click to collapse
These phones get emmc errors. Common issue with this device
Hello everyone,
So I have a rare issue. I have a OnePlus 6. Today, it started to act really weird. It became so slow that even swiping on home screen with no apps opened takes like a minute to register. I forced power off the device. When powering on again, it seemed like it take around 10 minutes or so to boot. Again, extremely slow. I tried everything from restarting and clearing app cache while in the system itself but no luck.
So, next thing I booted to recovery mode, typed my pin, and cleared system cache and settings. It started to progress until just a tiny bit left before the end of the progress bar, and it got stuck again. Kept like this for a long time. I had to force power off the device again. Now, when I try to power on the device, it launches into Recovery Mode. I tried my pin but it wouldn't decrypt and looks like the device is no longer recognizing it. I tried a couple of "default passwords" but it wouldn't work either. It only gives the option to "Forget Password?" Which should wipe everything off the phone. The only other mode it launches into is Fastboot Mode. I'm using Stock everything and Device State is Locked. I'm not sure where to go from here.
Now my question is, is there any way I can open my device again without losing data? Maybe some way I can pull files using adb in that state then factory reset? Or maybe someway I can bypass Recovery Mode and boot again? I have important data that I can no longer access if the only way to fix this is by wiping everything!
Can anyone help? Much appreciated in advance.
When a phone permanently boots into Recovery mode then either Android OS is corrupted - for whatever reason - or phone's bootloader is misconfigured.
If phone is accessible by either ADB or Fastboot you can try to exit Recovery mode by forcing phone to boot into Android OS ( Normal mode AKA System ) by applying the related ADB and/or Fastboot command.