Database Users

[SOLVED] Can't boot, can't boot recovery, oem locked, usb debugging disabled

Happened when I was updating twrp:
I downloaded the .img from their website, booted into my older version of twrp, went to flashing pressed the butting in the bottom right corner, selected the file and selected 'recovery'
Said it was successful, so I rebooted, then it wouldn't do anything anymore except for fastboot.
1. Can't boot into recovery
2. Can't boot normally
3. USB debugging disabled
4. oem locked
Only thing I can enter is fastboot.
I followed this guide, but no luck on my end.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.

passion8059 said:
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
Click to expand...
Click to collapse
It's no use because oem is locked. That means I can't flash anything.

toolbox should still help you unlock bootloader again

Just use the Qualcomm factory restore image to return the phone to original shape of things.

passion8059 said:
toolbox should still help you unlock bootloader again
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pitrus- said:
Just use the Qualcomm factory restore image to return the phone to original shape of things.
Click to expand...
Click to collapse
I have no idea how I would do this without being able to flash anything.

Do you mean that the Qualcomm download program also crashes like fastboot? Sounds like you either have some problems with your windows installation or perhaps you haven't searched for and downloaded the Qualcomm restore if your still trying to flash the ordinary way instead of the emergency way.

Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys

Theevilsocks said:
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Click to expand...
Click to collapse
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc

Redjax said:
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Click to expand...
Click to collapse
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.

Theevilsocks said:
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Click to expand...
Click to collapse
Literally JUST finished with this guide, and my OP2 is alive again! I was going to come back and post. Thanks for the link.
Anyone trying to use this guide without success:
There's one very important step I somehow missed. You MUST disconnect your phone, hold the power button for ~15-20 seconds until it's off, and hold the Volume+ button, THEN plug it back in. Your computer will make the "device connected" sound, but the screen will stay black. THIS IS OK! That means you're in a special recovery, which is where you need to be for the tool.
I also installed the certificate file in the folder I downloaded, then rebooted (it did not work before a reboot, but did work after).
So, the steps:
1. Download the files, make sure your signature signing for drivers is off.
2. Install the trusted certificate, then the driver.
3. Reboot PC
4. Power off phone (hold power for 15-20 secs), hold volume+, then connect through USB (wait for device connected sound, screen on phone will still be black)
5. Run the tool (I ran as admin, not sure if that's required)
6. Weep with joy that you finally found a solution that works.

adb/fastboot

Hey guys,
Back May when dp3 came out, I went ahead and installed it. Now I'm stuck without a working twerp because I'm encrypted. Problem is I can get dab to work when the phone is on but cant connect to it from bootloader. I'm using the same pc from when I first rooted it...so I know that end is ok. Here's what I've done so far.....I've uninstalled all other drivers and have installed and checked with googles usb driver and clockwork mod universal drivers. I've used usbdeviw to make sure I had no conflicts there. I've tried all usb ports and different cables. I'm using win10, sdk is system wide, everything is up-to-date.

jaysway said:
Hey guys,
Back May when dp3 came out, I went ahead and installed it. Now I'm stuck without a working twerp because I'm encrypted. Problem is I can get dab to work when the phone is on but cant connect to it from bootloader. I'm using the same pc from when I first rooted it...so I know that end is ok. Here's what I've done so far.....I've uninstalled all other drivers and have installed and checked with googles usb driver and clockwork mod universal drivers. I've used usbdeviw to make sure I had no conflicts there. I've tried all usb ports and different cables. I'm using win10, sdk is system wide, everything is up-to-date.
Click to expand...
Click to collapse
One more way to confirm is by connecting your device to another PC, and check if fastboot works while your device is in bootloader mode, and adb, when your device is booted in the operating system.

DJBhardwaj said:
One more way to confirm is by connecting your device to another PC, and check if fastboot works while your device is in bootloader mode, and adb, when your device is booted in the operating system.
Click to expand...
Click to collapse
It wont work on my desktop either...same story. I have not done any of the steps i listed though either. Did all that on my laptop and no dice.

jaysway said:
It wont work on my desktop either...same story. I have not done any of the steps i listed though either. Did all that on my laptop and no dice.
Click to expand...
Click to collapse
While it is booted in the operating system, can you get it connect through MTP?

DJBhardwaj said:
While it is booted in the operating system, can you get it connect through MTP?
Click to expand...
Click to collapse
Yes

jaysway said:
Yes
Click to expand...
Click to collapse
Weird. Did you try switching to a different cable?

DJBhardwaj said:
Weird. Did you try switching to a different cable?
Click to expand...
Click to collapse
Yep....still no dice. I feel as if I've exhausted all my known options. Not sure where to go from here.

jaysway said:
Yep....still no dice. I feel as if I've exhausted all my known options. Not sure where to go from here.
Click to expand...
Click to collapse
So while in operating system, and USB debugging enabled, you cannot detect it through the "adb devices" command?

DJBhardwaj said:
So while in operating system, and USB debugging enabled, you cannot detect it through the "adb devices" command?
Click to expand...
Click to collapse
Yes I can

This is while phone is on, usb debug enabled.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And while in bootloader

xx

jaysway said:
This is while phone is on, usb debug enabled.
And while in bootloader
Click to expand...
Click to collapse
ADB doesn't work in the bootloader, only in recovery and booted in Android. You must use "fastboot" <command>, like "fastboot devices" while in the bootloader.
Sent from my Nexus 5X using Tapatalk

jaysway said:
This is while phone is on, usb debug enabled.
And while in bootloader
Click to expand...
Click to collapse
Mate you are doing it wrong here. ADB only operates when Android is loaded into the operating system or when sideloading. While in the bootloader, you need to operate over fastboot. So the right command command would be:
Code:
fastboot devices

Ya just realized. I'm a dumb ass.

jaysway said:
Ya just realized. I'm a dumb ass.
Click to expand...
Click to collapse
No one is. It's a phase we all have gone through. :good:

Nexus 4 - wiped internal storage & pc wont recognize phone so stuck in recovery mode

Nexus 4 - wiped internal storage & pc wont recognize phone so stuck in recovery mode
before i start, i would like to say that my last experience with android phone, rooting and other stuff related to android was last october 2013. please bear with me
i posted this exact texts below before before i gave up on my nexus 4. now after 2 years, im ready to get frustated again. so here it is
----------
my problem started after i updated to oct 7 cm10.3 nightly. my pc and my mbp cant read my nexus storage.
searched for this problem and found some few n4 users that experienced this but my main problem is there is no android device listed on my device manager.
i checked for all possible solutions:
- uninstall driver on device manager and reconnect the phone to install the driver automatically (but theres no android device listed)
- changed the storage settings as to connect to mtp
- restore factory settings and wipe data
- tried different data cables
- changed my rom from cm to pa
- restart phone
- push adb but device not found (but my pc doesnt recognize my phone)
- turned on/off usb debugging (still cant read)
then out of frustration, i wiped my storage data completely
so now, i cant flash any roms, no files found on system
i cant push adb because my pc cant find my phone even in recovery and device manager, even in USBDeview
but the unit is till charging
i sent it to lg and they said the board was the problem and the replacement was expensive so i gave up and bought another phone
----------
google released pixel and i began to miss my n4 so tried to recover it
the condition is the same 2 years ago. placed it in storage after got frustrated
so anyone has an idea?

If the phone is recognized in fastboot mode, flash TWRP, boot into TRWP, mount storage, copy a custom ROM to the phone, and flash from TWRP.
As an alternative, you can flash a stock Google ROM if fastboot commands are working.

Hey!
Maybe it's just a minor "hardware problem". Did you check if there is any lint between the micro usb connector-plate and the back (see attachment)? Mine caught dirt and lint over time. With a thin but sturdy piece of plastic I could remove the dirt again, and suddenly all my cables started to work again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

thank you audit13 and smeee_again for your replies. ill look into both of it!

Phone should be recognized in Bootloader mode anyway, try different drivers, then fastboot flash stock and re-root
Optionally, boot into recovery, connect cable and go to mount options then mount usb storage, put any ROM in storage and flash it, the trick is it shouldn't require specific drivers as storage via recovery shouldn't use MTP but generic USB connection (like pendrive) as far as I know.

If you don't want to root and install a custom recovery just download and fastboot the Fake Nexus ROM which will give you a stock experience really easily and also it will be Nougat . Check out the thread for how to install it, it's really easy.

LG G2 - secure booting error after installing SuperSU

Hi guys.
Is my case here is still got hope? ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The only reason is the wrong version of SuperSu. Maybe I use custom made SuperSu for OnePlus 3T.
Before I flashed that SuperSu Zip file using TWRP there is no such problem. Only after flash SuperSu cause this issue .. ?
Before this flash, LG G2's is a new fresh install custom LineageOS for LG G2. Everything is OK. Only no root access. TWRP already installed.
LG G2 still can go to Download Mode as shown by holding the power button and connect USB cable to PC. But the problem is the PC & laptop cannot install the required driver properly. I think I've tried installed/reinstall all the suggested drivers but to no avail.
I even cannot enter the recovery mode using the key combination. When the phone is power on, it will continue to show that Boot certification verify alert.. Ermm ...
Just now just praying PC / laptop can detect and use tools installed on my computer to get to boot into the recovery mode. But is it still possible?
Or this totally means that I will never can use my LG G2 anymore?
Thanks guys.

try to put the ROM via tot aver if you accept it
---------- Post added at 12:17 AM ---------- Previous post was at 12:16 AM ----------
mie_shariff said:
Hi guys.
Is my case here is still got hope?
The only reason is the wrong version of SuperSu. Maybe I use custom made SuperSu for OnePlus 3T.
Before I flashed that SuperSu Zip file using TWRP there is no such problem. Only after flash SuperSu cause this issue ..
Before this flash, LG G2's is a new fresh install custom LineageOS for LG G2. Everything is OK. Only no root access. TWRP already installed.
LG G2 still can go to Download Mode as shown by holding the power button and connect USB cable to PC. But the problem is the PC & laptop cannot install the required driver properly. I think I've tried installed/reinstall all the suggested drivers but to no avail.
I even cannot enter the recovery mode using the key combination. When the phone is power on, it will continue to show that Boot certification verify alert.. Ermm ...
Just now just praying PC / laptop can detect and use tools installed on my computer to get to boot into the recovery mode. But is it still possible?
Or this totally means that I will never can use my LG G2 anymore?
Thanks guys.
Click to expand...
Click to collapse
try to put the ROM via tot aver if you accept it

wtf same thing happend to me

This happened to me too once.
Security error normally means that you should have flashed bumpboot.zip after supersu.zip.
You should still be able to get into TWRP (PWR+Down until Logo appears, then Up+Down).
Some LG drivers seem to miss something. Try older versions or alternative generic ADB drivers.
TOT method always worked for me in the end.

Install SRK Tools to fix boot partition. After that, you could enter in download mode easily.
Edit: LinageOS have your exclusively SuperSU. Next time, install the proper version in lineageOS Website. That problem happen to me, same problem...

Thanks to all.
But whatever fix you suggested, first the laptop/PC needs to detect the phone and install the driver correctly first right?
That is where I'm stuck now.
Even my office laptop also have the same problem, cannot install the driver properly.
Any help?
Thanks.

Williknot said:
Install SRK Tools to fix boot partition. After that, you could enter in download mode easily.
Edit: LinageOS have your exclusively SuperSU. Next time, install the proper version in lineageOS Website. That problem happen to me, same problem...
Click to expand...
Click to collapse
Thanks.
I've already downloaded this before.
But I could not find the option you mentioned.
Can you please guide me more details.
And if the laptop still cannot recognized my LG G2 properly, can I still proceed?
Thank you.

Latest status at my office laptop...
I have tried numerous drivers but to no avail.
Any help?
Thank you.

I mananged to get into this when I let the phone boot with a totally blank and black screen...
Any help with SRK Tools in this case?
Thank you.

Thank you so much guys.
Yes this SRK Tool is really amazing - https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
I can now get back into recovery mode and most importantly my computer can detect my phone!! Thanks a lot.
But now it seems that my Lineage OS has become corrupted and I don't think I want to install it anymore because the display is very poor in brightness.
So my next question is with such condition ie improper Lineage OS installation on the phone right now, how do I get back to the latest stock OS.
How do I start?
Thank you so much for the help.

After flashing SuperSU do as @MB525 suggests, flash Boot Image Bumper/ bumpboot-v1.0-blastagator-signed.zip
http://www.gregtwallace.com/lgg2-projects/miscellaneous/
This needs to be done with Magisk too.

Same thing happen to me

mie_shariff said:
Thank you so much guys.
Yes this SRK Tool is really amazing - https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
I can now get back into recovery mode and most importantly my computer can detect my phone!! Thanks a lot.
But now it seems that my Lineage OS has become corrupted and I don't think I want to install it anymore because the display is very poor in brightness.
So my next question is with such condition ie improper Lineage OS installation on the phone right now, how do I get back to the latest stock OS.
How do I start?
Thank you so much for the help.
Click to expand...
Click to collapse
use lgup to flash the stock rom and ready in LG firmware:fingers-crossed::fingers-crossed:

Need some help for a bricked pure

I have not touched this phone in a year, so forgive me if im rusty.
I embarked on a project of compiling slimroms 7.1.2 for this device a year ago, and made a rom that made it onto the device. Now, Here is my mistake. At the time when i built the rom, the nougat bootloader for this device was not out yet(i think, as my bootloader is on a0.4d aka dated 2016-11-30) Giddy that i had finally built a custom rom that worked, i hurriedly flashed the device through the recovery(twrp at the time) and thats when the issues happened. The device will not charge past 1 percent, and in an effort to fix, without knowing that my outdated bootloader was the issue, i decided that installing stock recovery was the best option. BIG MISTAKE. as i now cannot flash anything in recovery. i keep getting signature verification failures and what not.
With that backstory out of the way, here is my issue. I cannot flash anything in fastboot, because when i connect the device to windows i get
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Yes i have updated the drivers and when i install the motorola drivers manually i get this:
Code:
This device cannot start. (Code 10)
A request for the USB device descriptor failed.
this is the single most thing that is keeping me from reviving this device. I have tried using linux, but the device just doesnt show up. I have tried multiple usb cables. so i know thats not the issue. any help would be very appreciated.
UPDATE: i have done some digging around and no loader files are working. (using a 32gig class 10 microsd). Also, It is on stock recovery so i cannot flash anything other than stock images, which if i am correct, none are recovery flashable, only the otas are. When i try to flash an ota it doesnt work because it is expecting stock apps in system, which are not there since i am on a slimrom rom.
TLDR: i have stock bootloader and recovery, (24.49-18-8/4) but have a non rooted slimrom 7.1.2 which shows up in windows as get device descriptor failed(unknown device). if there was a way to root slimrom 7.1 without usb and with stock recovery that would help alot.

Have you tried the method to revive the phone in Qualcom mode (error 9008)?

mr_5kool said:
Have you tried the method to revive the phone in Qualcom mode (error 9008)?
Click to expand...
Click to collapse
Can you link me to a thread that has that info please?
When I am in bootloader and hit the power button on the qcom option my phone just boots into the slimroms option with no change in the USB side

Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860

mr_5kool said:
Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Click to expand...
Click to collapse
So my issue is worse than that. It shows up on the computer as "device descriptor get failed" so I am unableble to use that method unless I can force it into qdloader mode

Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA

mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
When i try to install this driver, it says that it is incompatable for my device
I will try again when i get home tomorrow though

mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
Alright, When i try to install this driver i get this
View attachment 4594365
And this is the error i have on any machine
View attachment 4594369

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!

mr_5kool said:
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!
Click to expand...
Click to collapse
its quite alright. i think that i bricked the phone while trying to use an unsupported bootloader, therefore bricking the mainboard
Its noones fault but my own, so i will chalk this one up to a loss lol