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.

i probably hard bricked a1 open for any ideas ( only launch in edl mode)

Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
{
"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"
}

onursewimli said:
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
Click to expand...
Click to collapse
Oh, I know that feeling of having bricked one beloved device or at least thinking it is bricked. So I did some new year's digging for you and maybe found a way to help.
Assuming your bootloader is still unlocked and it is really the EDL mode (at least it sounds a lot like it reading the info you have provided) you should have still some good chances.
Please follow this tutorial found here: http://en.miui.com/thread-294318-1-1.html
And for flashing the firmware you are looking for, please have a look at my thread over here, which leads you to the best suited download package of version 7.12.19, that I could find:
https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
So give it a go, good luck & please provide your feedback here.
Maybe it can help others too
Edit: I guess the part which is probably the most important is the qualcomm driver

hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.

onursewimli said:
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
Click to expand...
Click to collapse
Did they fixed it? Without any cost?

I'm having an issue with my G Pad 7 (LG-LK430)

Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
{
"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"
}
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help

arksoother said:
Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help
Click to expand...
Click to collapse
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54

rahimali said:
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54
Click to expand...
Click to collapse
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.

arksoother said:
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.
Click to expand...
Click to collapse
Can you not even boot into bootloader/fastboot or TWRP/recovery?
You should be able to boot to recovery by following the steps shown here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/recovery-mode/
You could also try and boot into safe mode and try and use the magisk manager to uninstall magisk - howto here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/safe-mode/

okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?

arksoother said:
okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?
Click to expand...
Click to collapse
somebody else apparently had the same experience although on a different LG device -> https://forum.xda-developers.com/lg-spirit/help/help-fastboot-error-loading-keystore-t3430163
So it seems that fastboot commands may have been disabled which means you can't interact with the device in fastboot mode whatever you do.
If nothing else works, you could try and re-flash stock ROM if you can manage to get into download mode.
Best of luck!

EDL Mode HD1925

So, I'm trying to use the MSM Tool trick to oem unlock my phone from another thread, and I can't seem to keep my phone in EDL Mode. I have the Qualcomm drivers properly installed--when I get it to go into EDL mode, my device manager properly recognizes it as "Qualcomm HS-USB QDLoader 9008," but it only seems to want to stay in EDL mode for a few seconds, then it boots back up. I've tried doing this through adb and by holding volume + and - and plugging in the cord--both methods, same result. Anyone have any suggestions? I greatly appreciate your feedback!

I always power off my phone. Then hold both volume buttons down and plug it in. MSM tool sees my phone and hit start.

which Qualcomm drivers you installed ? because my phone is not connecting with MSM tools ....

I'm having the same issues. Anyone find a fix?

Charles: said:
I'm having the same issues. Anyone find a fix?
Click to expand...
Click to collapse
I installed twrp recovery software to go into EDL mode after that all works fine and connected

Zain ul Abedin said:
I installed twrp recovery software to go into EDL mode after that all works fine and connected
Click to expand...
Click to collapse
Which TWRP?? Did you load it via Fastboot and use Fastboot commands? Are you A11? Which Qualcomm drivers?

I basically forget that , but search about it . And install TWRP in your phone

otoyayamaguchi said:
So, I'm trying to use the MSM Tool trick to oem unlock my phone from another thread, and I can't seem to keep my phone in EDL Mode. I have the Qualcomm drivers properly installed--when I get it to go into EDL mode, my device manager properly recognizes it as "Qualcomm HS-USB QDLoader 9008," but it only seems to want to stay in EDL mode for a few seconds, then it boots back up. I've tried doing this through adb and by holding volume + and - and plugging in the cord--both methods, same result. Anyone have any suggestions? I greatly appreciate your feedback!
Click to expand...
Click to collapse
I think it's supposed to only last for a few seconds. Pull up the MSM Tool and pay attention to the "Status of Connection" field for any of the COM lines in the MSM Tool. When you connect, it should say "Connected" for one of those lines. If that happens at all, then you're good to proceed. Make sure you have TMO selected in the drop-down, click "Enum" once you plug in your device, then click Start. Try to do this quickly. Let me know if this helps.

I am having the same problem with my 7T Pro McLaren, the pc recognizes it but msm tool does not, someone has already found the way
{
"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 had the same issue. One easy fix is switching from a USB 3.0 port to USB 2.0 port. The other method that worked for me is a little more of a process.
1) Have MSM open
2) Connect phone to PC
3) Power phone off
4) Then, the moment it powers down, hold the vol +, -, & power button
5) Keep holding it. Your PC will make a sound notifying you that it's detected the phone, but you want to keep
holding the buttons until you hear it being detected for the second time.
6) Release buttons.
Hopefully that makes it stay in EDL mode for you.

I wrote on this somewhere, but you can try having the program open and placed at the right settings, then move quickly once the phone is in EDL mode. Not ideal but worked for me. Once the process begins it won't exit out of EDL mode in my experience.

hii, from most tutorial i have seen so far, the com number is show in the msm tool upon starting the program, most the two msm tools i have tried so far dont show com number... and its not detecting my phone.

Galaxy Tab S5e - in bootloop - help needed

Dear crowd, I need support with my Samsung Galaxy Tab S5e/SM T-725 (it is my first Samsung device).
I unlocked it and tried flashing it (with Odin3). This was not successful and now I do not manage to get the device to boot into the Download Mode anymore.
The device does not switch on anymore - only with charging cable connected. In this case it turns on and off eternally showing the below screenshot.
Connecting a USB-C cable while pressing combinations of Power+ any volume key combination does not lead to any result. Only pressing Power+VolumeUp+VolumeDown brings is for a little moment to the screen where I chose to unlock the device, bot after one secons it turns off again being in bootloop subsequently.
SmartSwitch as indicated on the screenshot below does not do anything as the device is constantly turning off again.
Does anyone have a clue how to convince the device to finally allow me flashing TWRP and a custom ROM in this situation?
Advice is more than welcome!.
{
"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"
}

ralxx said:
Dear crowd, I need support with my Samsung Galaxy Tab S5e/SM T-725 (it is my first Samsung device).
I unlocked it and tried flashing it (with Odin3). This was not successful and now I do not manage to get the device to boot into the Download Mode anymore.
The device does not switch on anymore - only with charging cable connected. In this case it turns on and off eternally showing the below screenshot.
Connecting a USB-C cable while pressing combinations of Power+ any volume key combination does not lead to any result. Only pressing Power+VolumeUp+VolumeDown brings is for a little moment to the screen where I chose to unlock the device, bot after one secons it turns off again being in bootloop subsequently.
SmartSwitch as indicated on the screenshot below does not do anything as the device is constantly turning off again.
Does anyone have a clue how to convince the device to finally allow me flashing TWRP and a custom ROM in this situation?
Advice is more than welcome!.
View attachment 5423645
Click to expand...
Click to collapse
This warning screen is still download mode. Try flash stock rom via Odin.
Chosse exact firmware, when start flashing you will see the white bar below that text.

Unfortunately, it does not work as the device switches off too quickly. Odin3 then just reports failure.
I wonder if there is a way to prevent the device from switching off so quickly.
dangtoi1993 said:
This warning screen is still download mode. Try flash stock rom via Odin.
Chosse exact firmware, when start flashing you will see the white bar below that text.
Click to expand...
Click to collapse

ralxx said:
Unfortunately, it does not work as the device switches off too quickly. Odin3 then just reports failure.
I wonder if there is a way to prevent the device from switching off so quickly.
Click to expand...
Click to collapse
so sorry, mine stuck at warning sreen so i can easy flash back.
If your tab fast switches off then maybe it got bootloader damaged, you need research flash by Qualcomn flash tool like QFIL, flashsing for Qualcomn chipset device when it in QDLoader 9008 mode.