Hey everyone,
My OP2 is soft-bricked AND it's locked; I didn't root it or even enable developer on the advanced settings.
I've spent the better part of today trying all possible fixes (fastboots, ADB, Firstaid, save_brick_mini/qualcomm & windroid tools) to no avail mainly because the phone is locked; so I can't erase or replace the important files or install TWRP
Currently, the phone only opens to the 1+ logo screen or fastboot screen; no recovery mode/menu, nada
All help is appreciated on how to unlock the phone/bootloader through Windows (without prior enabling/unlock from phone) and possibly save muh preshus from the dim future at the scrapyard
Thanks
Related
Hello,
I am writing this thread for a friend of mine. He owns a Z1 - stock ROM, locked bootloader.
Today it started looping and I tried to fix it (telling him over a chat what to do). It goes through the bootanimation and then dies or while optimizing apps, or while starting them.
What we tried:
1) Wipe cache
2) Factory reset
3) adb sideload the current official CM onto it
Nothing helped, the error stays the same. We also tried this http://forum.xda-developers.com/showpost.php?p=64458076&postcount=4 but it never really recognised the phone (despite using the correct drivers and following the procedure) - it did not appear under ports (Windows 10?).
Is there any other way to unlock this goddamn phone? My Androids so far had an easily unlockable bootloader via fastboot. This would have, too, but in order to unlock the bootloader via fastboot you first have to allow this in the developer settings - which we can not reach due to the loop.
If you know some way to get a working ROM onto it, we would be very happy. In the end we will end up unlocking the bootloader and flashing another Recovery and ROM anyway. We only need some way to achieve this. I expect the way to do this will be the QPST thingy. Any ideas why it did not recognise the phone? He does not own a PC with another OS than Win10...
Thanks in advance for your help,
Moritz
EDIT: Looks like the sideload did work - after tens of reboots it finally succeeded and bootet straight into the ROM.
Took a lot of attempts, strangely.
Proceeding to unlock it
Mine does the same boot loop on CM13. After tons of different tries to fix it, i think it could have something to do with my fingerprint sensor which is not working anymore.
Maybe there is some kind of hardware malfunction and android crashes while initializing that piece of hardware.
I have an issue I'm hoping someone can help me with. I'll try to keep it brief.
I rooted my phone, successfully, but in the process the phone app mysteriously disappeared, not sure why. I download the stock apk's from 'theandroidsoul.com/download-lg-v20-stock-apps/, and dropped the phone app into the system app directory, set the permissions, and rebooted. Yes, I know that was probably pretty stupid to try.
Anyway, I can't access the UI as the constant, endless crash caused by com.android.phone. Phone OS is done, so I attempted to get into recovery, re-flash, no big deal.
In previous LG phones, to access recovery via the hardware buttons, you had to go through a menu that made it appear your phone would be factory reset, but wouldn't, and bring you to TWRP after selecting 'yes'. Except with the V20, it actually does reset your phone. USB debugging, disabled now!!
So I can't find out how the hell to access recovery from the hardware, USB debugging is disabled so I can't adb push recovery files, can't access UI, and every fastboot command I run returns 'remote:unknown command', probably due to the USB debugging authorization being revoked.
I know I got myself into this mess, I tinkered too much, and I realize it was an amateur move.
My question is, how can I get out of this? Can't use LG flashtool as I don't have relevant .dll. Can't access recovery (so far; I've tried 50x). Can anyone help? Do I just need to wait for LG to release TOT / KDZ files?
One clarification - when I select the option to factory reset via the hardware button menu - TWRP actually performs the wipe. So its on there. It just resets it and reboots. I can't get into TWRP!
Im having the same problem. "encryption unsuccessful" on white screen. dont know what to do or where to go from here.
All we need is the .dll file for the V20 so we can flash the TOT with the LGUP tool. Until then I think we're out of luck.
Bricked stuck on white encryption error corruption
Messed up. Bricked lg v20 h18. Hopefully someone can help us.
Hi Team,
Couple of days back i manually restarted My lenovo zuk z1 device and since then it is in endless boot loop, and i am severly constrained on multiple counts which are:
1. USB debugging disabled, and now there is no way for me to enable it, therefore cannot use adb commands.
2. OEM unlock is disabled, therefore bootloader is locked, i have tried unlocking it using fastboot command , but it fails for obvious reasons.
3. Using stock ROM , never flashed/updated either ROM or Recovery .
Things i can do or have done are :
1 . i can access cyanogen recovery and therefore i can reboot to bootloader as well .
2. i can manually power down the phone using recovery menu.
3. i have factory reset phone multiple time and it still reboots and optimizies apps and then again repeats it continuoulsy.
4. i have tried qfil but it only recognizes my device for very short moment, it starts the download and fails at "converting to etl mode" , therefore flashing with qfil is also not working for me.
I am not sure if i have any more options left at my disposal, please help me get out of this mess.
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Same problem
Same thing happened to me. Same day as you. I can get fastboot but not adb but since the device is locked I can't flash. I've only had the phone about 6 months so I contacted customer support and they offered to replace the phone.
It might be a known issue because they didn't even try to address the fact that I could get fastboot connected but not adb. They just offered to replace.
Thanks for the info! I am -at least in this case- unfortunately an early adopter. I bought two essentials at the beginning of the pre-release.
Essential support checked my serial number and said the phone was out of warranty.
Has anyone been able to force the Essential into EDL mode to recover that way? It looks like you have to latch one of the USB pins to ground, or 5V, but I haven't found any detailed instructions on how to make this work on the essential...
Thanks again
Justin
I'm sure things have changed and I'm wrong, but if you can get into the fastboot menu can't you just cycle through the options until you get to recovery and then flash an official release from Essential?
I may be thinking of LG or something but this should be possible as long as it's newer than the current software installed because it will see it as an official update and allow the flash.
Thanks but unfortunately, when I try and do that, the phone just does the same thing, it hangs forever on the initial boot screen white Android text with the circle/square logo...
That's why I've been looking into the more direct hardware version of forcing the phone into EDL mode, which is supposed to be possible with all Qualcomm based phones.
I've just not found the time yet to find a USB-C cable I'd be happy to cut in half and short the pins on! Which is why I was hoping someone might have tried this with an essential before to know if it was successful before I start trashing good cables
Thanks again for your reply!
JB
justinbaird said:
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Click to expand...
Click to collapse
I have the exact same problem,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cannot flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you
Hello,
I have an Asus Zenfone Max Pro M1 device. Few hours back, it shutdown suddenly:crying: and i cannot reboot it. What all i tried are:
1) When i try to Restart, it shuts down after showing asus logo.
2) When i try to access Recovery Mode by pressing Volume Down and Power Button, it shuts down after showing asus logo.
3) I can Only Access CSC FASTBOOT MODE. But no Developer options enabled.
NB: Please note that Developer options is disabled and usb debugging is OFF.:crying:
All tutorials on web says i need to reinstall rom for wich i need to unlock bootloader which will eventually delete my data.
Can someone help me on how i can get my datas back in this situation?
You can't unlock bootloader until you enable OEM unlock in developer options, so there is no method to get your data. You need to wipe
Same problem.... not able to unlock bootloader
Also fastboot rom,qfill failed to repair this problem
Having the same problem. Did anyone figured out what the issue might be or how to proceed? If I would lose the phone, it'll hurt, but not critical. But at least the data ...
Thank you