Database Users

[HOW-TO] Fix 5 vibrate and black screen

Here was my situation: when trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so I decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way I think makes the most sense, but read all of what I wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what I needed to do and bringing all of their minds together in one place.
The Process
First thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
UPDATE: To clarify: fastboot is a completely separate (although closely related) piece of software from adb. If you do not have "fastboot.exe", download it from http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/ and follow the instructions there. Or, you can just download the full sdk from google which should include adb and fastboot. I recommend the second option, but my hard drive can take the hit. (thanks BonzTM)
UPDATE: If you get an error saying "The Program can't start because AdbWinApi.dll is missing from your computer" you need to copy that file from platform-tools to tools, then it should work (thanks Jester1614).
If you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
Disclaimer
Note: This is what I experienced with my amoled incredible; in no way do I take responsibility for anything you do. If you try to blame me for bricking your phone I will enjoy a hearty laugh while salting my soup with your tears.

Worked great for me and saved me from the hassle of needing a new phone.
THANK YOU!

goblue13579 said:
here was my situation: When trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so i decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way i think makes the most sense, but read all of what i wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what i needed to do and bringing all of their minds together in one place.
the process
first thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
if you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
disclaimer
note: This is what i experienced with my amoled incredible; in no way do i take responsibility for anything you do. If you try to blame me for bricking your phone i will enjoy a hearty laugh while salting my soup with your tears.
Click to expand...
Click to collapse
u saved my life/phone i love u son

Perfect Solution!
Thanks Thanks Thanks +1

So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb

sofocused715 said:
So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb
Click to expand...
Click to collapse
Actually you can download it from the link I provided in my post to the xda page for it (http://forum.xda-developers.com/showthread.php?t=833953). Scroll to the bottom of the first post and in the attached files there is a version that works. That's what I did, and then you can run the usb fixing commands. Then it's just reboot, re-root, and restore.
Hope this helps.

This thread needs more attention.

This needs to be stickied(sp?) and maybe added to the Development section where it would most likely be looked for first.
If I've helped you, hit the thanks button!

As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.

goblue13579 said:
As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.
Click to expand...
Click to collapse
I re-worded your OP and posted it on another forum. I did credit you though. You are now famous.

Cool, thanks!

I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.

brando56894 said:
I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.
Click to expand...
Click to collapse
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.

doug piston said:
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.
Click to expand...
Click to collapse
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol

wildstang83 said:
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol
Click to expand...
Click to collapse
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.

Thank you goblue13579, wildstang83 and Doug Piston! My phone is totally functional once again.
Odd timing how the problem happened only 2 days ago on my phone, and coincidentally, a fix was hashed out in the same time period after all this time of it being unfixable.
I owe you all a beer! Thanks again!

doug piston said:
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.
Click to expand...
Click to collapse
Yea bud, even I use adb so much that I keep forgetting that there's emulators to use. Its just one of those things we never think about.

Even though it was really more dumb luck and excessive googling that got me to this solution, thanks! I'm glad my compilation has helped so many people. And honestly, it's the least I can do for all the help and goodies I've gotten from these forums and developers.
Happy modding!

What if the devise isn't rooted?

Let the phone sit for an hour with the battery out. Put the battery in after that, should be good
Sent from my 2.3.5 Incredible Obsession

Idiot (me) finally rooted from .29!

I finally did it. Didn't have to unlock, rollback the firmware, ADB, or anything too drastic. So happy.
I used this method here.
http://forum.xda-developers.com/showthread.php?t=1706588
*My biggest hurdle was getting the drivers installed before using that method. Then I figured out if you use the Asus Pad PC Suite it installs the drivers. Can download it here if you're as incompetent as me (Under Utilities). Exit out Asus Sync in your system tray before attempting the method above. And I'm probably not the guy to ask for any help if you got problems or questions.
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
I installed OTA RootKeeper afterwards.
Thanks XDA. Thanks sparkym3.

I think you should give yourself more credit.

GJ

thanks man!
-Bang

supersoulfly said:
*My biggest hurdle was getting the drivers installed before using that method. Then I figured out if you use the Asus Pad PC Suite it installs the drivers.
Click to expand...
Click to collapse
This works indeed, but you must stop ASUS sync if it's running. If you don't, the version of ADB packaged with ASUS Sync is different from the one in the zip file and you'll get a whole lot of lines with "adb server is out of date, daemon started successfully" which mess with the script.
Once I stopped the Sync thing from systray and verified in task manager, the script ran like a charm.
So, another TF300 with .29 WW rooted, thanks to the people involved in making this possible

all this confused me way too much but luckily for me i had help (well i say help he did it all via teamviewer lol) from thing o doom he is a star

I used this method too on my 29.WW,thx guys

just confirming, even thought the method is in the transformer prime section, it works for the TF300T?
Thank you

jakelikescake123 said:
just confirming, even thought the method is in the transformer prime section, it works for the TF300T?
Thank you
Click to expand...
Click to collapse
Ummmm.....I think I confirmed it, in the first post.

supersoulfly said:
Ummmm.....I think I confirmed it, in the first post.
Click to expand...
Click to collapse
im the idiot
thanks

No problems getting the drivers install but rooting fails because it appears that adb cannot see the device.

lightiv said:
No problems getting the drivers install but rooting fails because it appears that adb cannot see the device.
Click to expand...
Click to collapse
May not be the issue, but it's happened to me several times rooting & ROMing phones - plug the cable into a rear USB port that's on the motherboard. The USB ports on the front of the case don't always work for some reason. The front of my case has 6 ports and I can only get reliable phone connections on 2 of them. Down right squirrely!

ID10T Error on My Part
Turn out to be an ID10T error on my part. I had DroidExplorer running from when I rooted my cellphone. I finally ran across a post that made reference to it and killed the process. It took all of 30 seconds to root once I killed the process.

[Q] S4 stuck on Downloading mode..pls help

Hi guys, Last night I accidently unplugged my phone while installing ClockWORKMOD recovery. Now when I boot my device it is stuck on the Downloading screen. I tried everything including the posts here but the Odin software doesn't see my phone and removing the battery and reinstalling does nothing. I even wiped the phone and factory reset via the clockwork... No Luck. It will not install the Crash ROM either. I get error 7.
It seems like I bricked the phone but I know there is always a way back to life. At least I hope. Any help guys would be great.
thxs
Carlo

shpack said:
Hi guys, Last night I accidently unplugged my phone while installing ClockWORKMOD recovery. Now when I boot my device it is stuck on the Downloading screen. I tried everything including the posts here but the Odin software doesn't see my phone and removing the battery and reinstalling does nothing. I even wiped the phone and factory reset via the clockwork... No Luck. It will not install the Crash ROM either. I get error 7.
It seems like I bricked the phone but I know there is always a way back to life. At least I hope. Any help guys would be great.
thxs
Carlo
Click to expand...
Click to collapse
You need to properly install the correct drivers on your PC. There should be no reason that ODIN doesn't see your phone if they are installed correctly. A quick search of the forums should get you the proper drivers to install. You can also try Kies emergency recovery, but it is hit and miss. Good luck.

+1 if you can get into download you can Odin. Use the usb ports in the back of the pc. You might have to use a different computer also. For the life of me I can't get Odin on my pc to recognize the device but I have no problem with my laptop.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Wow, didn't we just fix this problem like 2-3 threads ago, IN THIS FORUM?

TheAxman said:
Wow, didn't we just fix this problem like 2-3 threads ago, IN THIS FORUM?
Click to expand...
Click to collapse
That's the thing, these exact same types of threads just keep rolling through one after the other...people don't search and they don't read. That's the reason they are in the situation they are in to begin with and it seems they just don't learn.
Fortunately, the AT&T S4 forum has come far enough along that the sticky threads and the threads like your guide can be linked for these people to put a little time into finding a solution for themselves. Most of them don't like it (they want it done for them), but if it is all they get, they will finally have to do something the right way on their own.
Actually, a few people are thankful for being pointed in the right direction, but most are still pissed because it means they have to do what they should have done in the first place...follow XDA rules, use the search function, and read. If you don't do everything for them and hand it to them on a plate they call you names and say you are a ****, unhelpful, etc... I just laugh about it because it becomes clear why their phone is F'ed up in the first place. The thing is, sometimes you just can't help people. Just every now and then, someone comes along that needs help and is willing to do things the right way.

You can NOT have kies drivers and samsung drivers loading at the same time, I do not use kies at all, and my pc has NEVER gave me a issue yet using odin, including in my G3 days. uninstall that worthless kies and proceed. If you have to use kies, load it as needed then remove it.
And as always with the lovely microsoft windows, after you un-install anything you have to reboot, for it to work properly.
Linux is my BUD!

i pay if some1 can unbrick my phone

i want help from some1 experienced to help me unbricking my phone

collisiion said:
i want help from some1 experienced to help me unbricking my phone
Click to expand...
Click to collapse
What happened what model pro 3 do you have.
Sent from my LEX727 using xda premium

mchlbenner said:
What happened what model pro 3 do you have.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
my phone only vibrates i cant turn it on, i have x720 model

collisiion said:
my phone only vibrates i cant turn it on, i have x720 model
Click to expand...
Click to collapse
Do you have fastboot working?
What is the last thing you flashed?
Sent from my LEX727 using xda premium

mchlbenner said:
Do you have fastboot working?
What is the last thing you flashed?
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
do u think you can help me? it is better to speak in teamspeak or something

If all you can access is fastboot, then check this guide out: https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
Your device has a QFIL file you can use to resurrect it. Also, provide us with information, like what you were doing before you bricked your device, and so on. Can't help you without knowing your basic situation.

sk8223 said:
If all you can access is fastboot, then check this guide out: https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
Your device has a QFIL file you can use to resurrect it. Also, provide us with information, like what you were doing before you bricked your device, and so on. Can't help you without knowing your basic situation.
Click to expand...
Click to collapse
i had a MIUI rom from a chinese forum for a few days and it was very stable and fluid, but when the battery ran out my phone shut down and I cant turn it on anymore. i tried to charge it for a few hours and it didnt turn on. only vibrates. I tried qfil unbrick method. it said success but i still cant turn it on, only vibrates.. my pc recognizes the phone but i dont know what do do.

collisiion said:
i had a MIUI rom from a chinese forum for a few days and it was very stable and fluid, but when the battery ran out my phone shut down and I cant turn it on anymore. i tried to charge it for a few hours and it didnt turn on. only vibrates. I tried qfil unbrick method. it said success but i still cant turn it on, only vibrates.. my pc recognizes the phone but i dont know what do do.
Click to expand...
Click to collapse
Well, you should have mentioned the situation in your first post. Sounds like a hardware issue. Never ever ever let a lithium-ion battery, like those in smartphones, drop to less than 5%. Never let them run out to less than 1% either. That's a surefire way to destroy a battery.
Plug your phone in using a certified USB-C cable (NOT the original LeEco cable that came with your phone) and wait a couple of days. It may begin charging after a while. But since you let the battery deplete to 0%, you might have to replace it.

sk8223 said:
Well, you should have mentioned the situation in your first post. Sounds like a hardware issue. Never ever ever let a lithium-ion battery, like those in smartphones, drop to less than 5%. Never let them run out to less than 1% either. That's a surefire way to destroy a battery.
Plug your phone in using a certified USB-C cable (NOT the original LeEco cable that came with your phone) and wait a couple of days. It may begin charging after a while. But since you let the battery deplete to 0%, you might have to replace it.
Click to expand...
Click to collapse
really? i didnt know that. is it possible to replace a battery on this phones? do you think i can still revive it?

collisiion said:
really? i didnt know that. is it possible to replace a battery on this phones? do you think i can still revive it?
Click to expand...
Click to collapse
Yeah, it should be pretty easy. Before doing that, look through this sub-forum for similar issues. A couple people here had the same issue--they let their battery drain to zero and wanted to revive their phones. I don't know if they managed to or not.
Just look for a Pro3 disassembly guide on Google. It's not hard. The Pro3's interior is similar to other LeEco phones, like the Le 2.
And Google is your friend. Google your issues instead of immediately making a thread here or wherever. This is a common issue on Android.

sk8223 said:
Yeah, it should be pretty easy. Before doing that, look through this sub-forum for similar issues. A couple people here had the same issue--they let their battery drain to zero and wanted to revive their phones. I don't know if they managed to or not.
Just look for a Pro3 disassembly guide on Google. It's not hard. The Pro3's interior is similar to other LeEco phones, like the Le 2.
And Google is your friend. Google your issues instead of immediately making a thread here or wherever. This is a common issue on Android.
Click to expand...
Click to collapse
i didnt know man, im sorry.. i thought it was really dead. thanks for your help

Can you get your phone into fastboot?
Let your phone for 5 hours then push down power button and connect to USB.
Never let your battery go under 15% especially a pro 3.
Your not first to have this problem and posting this issue is alright!
Sent from my LEX727 using xda premium

mchlbenner said:
Can you get your phone into fastboot?
Let your phone for 5 hours then push down power button and connect to USB.
Never let your battery go under 15% especially a pro 3.
Your not first to have this problem and posting this issue is alright!
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
thanks man i thought it was something worse than this, im going to investigate

collisiion said:
thanks man i thought it was something worse than this, im going to investigate
Click to expand...
Click to collapse
Let us know how you fix it, so other people that has same issue can read this, ok ?

Sweden.33 said:
Let us know how you fix it, so other people that has same issue can read this, ok ?
Click to expand...
Click to collapse
ok no problem

collisiion said:
thanks man i thought it was something worse than this, im going to investigate
Click to expand...
Click to collapse
You battery is not necessarily dead, you phone is just hard bricked, the symptoms you are having is exactly what happened to a friends phone and we were able to revive it. Just following the steps in the unbrick guide. https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340 If you check the last post you will see that someone just recently unbricked their phone.
Worst case there are services for repairing a bricked phone:
I have attached my notes below: The information came from multiple post by various people and my own research combined. Its unedited, I had planned on posting a more polished guide. So I am just copy pasting what I have so far. But the methods listed definitely works unless you do in fact have a hardware issue.
This Thread dedicated to unbricking The Leeco variants X720 and X727
These instructions may not work if you flashed with wrong firmware and you are stuck in Qualcomm Mode 9008.
* I plan to create a post that will share these thorough instructions with the public.
* After spending over an hour typing all of this out for you. I found this video that you can use a companion tutorial to walk your through the steps visually. https://www.youtube.com/watch?v=iN9Ce3hKlRA
* While there are s a couple of differences. For example, The person in the video is flashing a different phone.Most of the steps are the same.
https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340
1. Download Flash 2( Tool) here: https://mega.nz/#!ex5nmQxB!qXLIg3wpeQwuiTShdOz_DEStXFiKUPfSoXNLjomn4ag
2. Download the Qfil file for Lex Pro 3 file here: https://mega.nz/#!BJ52CApB!8lFCesula...e=DonanimHaber
3. Make sure you place and run this file from the root of your PC I.E : C:/
4. Do not unzip, when selecting it needs to stay a zip file
5. Keep these files. In case you ever need them again and if it works for you.
Instructions
* QFIL mode: Press on vol+ and vol- simultaneously while holding power
* Alternate way to get into edit mode ( Press vol+ and vol- while plugging usb into pc. enter in edl mode.
* Then start flash one
* Advance option Get HSCT
* Flash Type: Flash dead phone
* To Flash Developer Rom: rename of rom to 1.zip
* After completing the flash press and hold the power-button down for 30+ seconds and the phone will vibrate
* Release the power-button, it will vibrate again after 10-20 seconds*
After you have performed all of the steps
* Your Le Pro 3 will have the temporary repair version of EUI.
* The phone may not boot automatically.
* Press and hold the Power Button for two minutes or longer.
* iIt will leave the QFIL Mode, and will vibrate continuously for 20 seconds or longer.
* The phone could take as long as 15 minutes to start.
* Immediately you will notice that part of your storage is missing.
*
* Restore the storage back to default by going to Backup/Restore in Settings and Factory Resetting the Phone with the "Format Virtual SD Card" Option selected.
* *Next install the latest Official EUI download EUI 21S ( do mot load anything above this)
* Rename the file to Update.zip and place on OTG drive or into phone storage using file manager.
* Go to check for update and click hamburger icon in top corner and select you Update.zip file to upgrade
* If it doesn’t work retry steps,, If you have an issue from here let me know, also let me know if it works.
Worst Case after restoration attempt to resolve size issue.
* if you still have a problem install Twrp and Flash via TWRP install.,
* Wipe EVERYTHING... and flash the ROM using a usb Flash Drive and after mounting USB OTG Storage.*
* To Flash TWRP simply shut down the phone and By Keeping the Volume Down Button Pressed Hit the Power Button to Enter the Fastboot Mode.*
* flash TWRP Recovery...
* Boot into TWRP Recovery...
* Restart TWRP Recovery... I
* insert the USB Flash Drive
* Using USB OTG Adapter... and flash the ROM using the Install Tab in TWRP Recovery.
Addendum:
As far as I know the X725, has the exact hardware requirements as the X720 and X727 and many parts suppliers list hardware components being compatible with all three devices.*
Have you tried removing and reinstalling Qualcomm drivers, turning off firewall and antivirus, reinstalling and rebooting? Sometimes the most basic steps are the solution.
Here is a link that might provide additional things to try:*http://www.androidbrick.com/unbrick-...usb_dload_edl/
Stock Rom and drivers can be found here:*https://devsjournal.com/download-let..._Pro_Stock_ROM
I will look around and see if I can help you find anything else that may be useful.
BTW, the X720 and X727 are pretty much the same phone so it doesn't matter, it can be easily fixed. At this most my X727 thinks its a X720 because I just flashed a newly released X720 test Rom.*
Here is a link to a Stock Rom that will not ask for a key and the drivers can be found here as well.*https://devsjournal.com/download-let..._Pro_Stock_ROM*( This should definitely work I know that several people have used this file recently with success)
I will look around and see if I can help you find anything else that may be useful.
_____________________________________________________________________________________
Addendum:
Re: Instructions for unbricking your phone
Okay so you were able to download the files but Windows is not recognizing the file. Okay, I read the message in the middle of being focused on something else and misunderstood,thinking that you couldn't download it.*
So It seems that Windows has damaged the file or Qfil installation.
1. Do you have more then one copy of the file? Here is an alternative copy:*https://androidfilehost.com/?w=files&flid=244213
2. You will need to uninstall and reinstall Qfil
If you are on Windows 10, you will need to turn off antivirus, and all the block-ware that Microsoft has installed within Defender which may delete files or neuter files that it doesn't like. Perhaps this is what happened to your Qfil installation? ( I have a new laptop and dealt with this issue recently attempting to install Viper Audio mods for PC) So unfortunately, you may also need to uninstall and reinstall Qfil, ensure that you install as admin.
Go through your settings and make sure under apps >>apps and features>> the dropdown box installing apps and turn off installing apps from store only.
Go to Apps & features in Settings.
Under “Installing apps,” there is a drop-down menu with three options: make sure “Allow apps from anywhere” is on.
Although the Qfil tool is used universally to repair all Qualcomm boards. Windows 10 may cause issue and disable functions that allow root level changes to your attached device. Yes, this will flag Windows Defender
Defender
* Open Windows Defender Security Center from your Start menu, desktop, or task-bar.
* Click on the App and browser control button on the left side of the window.
* Check Off in the Check apps and files section.
* Make sure that Defender and any other antivirus or malware blocker is turned off.
* Unfortunately, from now on you will always need to turn these things off if you are installing drivers or programs that did not come from Windows store.
* Make sure all defender settings are toggled off.
* Turn off the controlled folder access .
Worst case: Other potential ways to resolve
This sucks ( If you will never use it otherwise) but you may even need to enable developer mode
https://docs.microsoft.com/en-us/win...or-development
You can return everything back to normal after you unbrick your phone.
The link below explains how to resolve additional potential issues caused by the Microsoft OS,
https://flashfiletool.com/qualcomm-usb-driver-download*The full setup option, on this page will download all drivers ( download only if needed) for all supported phones.
Hopefully, this finally resolve it for you. I am keeping notes. So once this is resolved. We can provide some updated cohesive steps to help other people that have the same

OP6T won't boot

Hi all,
I'm facing a really strange & annoying issue ... I'm running latest OOS version, unlocked bootloader, TWRP installed, root via Magisk. & substraturm theming.
I uninstalled all my overlays, rebooted my phone and boom, here the deal : my phone won't boot at all.
I tried to press the power button for something like 30sec, nothing, not even a vibration.
I tried to reboot in recovery/fastboot via the volume keys + power button, nothing happens.
I tried to charge the phone, maybe I was running out of battery..? Nevertheless, nothing happens ...
I tried to reboot into recovery via `fastboot boot twrp-xxx.img`, but fastboot can't detect my phone as it stay totally powered off....
Anyone get a idea about the how to fix it & how it happend ? It's really annoying as I'm in travel and I don't get any extra phone ...
Thanks all
edit: Ho yeah, I'm running linux & I don't have access to any windows computer

hard brick mode, try msm download tool

edsmat said:
hard brick mode, try msm download tool
Click to expand...
Click to collapse
Thanks for your reply, I was about to try that.
But after letting my phone cool down for 1h or so; I tried to press ALL the buttons in the same time for 1min or so and guess what, my phone rebooted ... No idea why ...
Where are the custom rom :crying:

allen2398 said:
Thanks for your reply, I was about to try that.
But after letting my phone cool down for 1h or so; I tried to press ALL the buttons in the same time for 1min or so and guess what, my phone rebooted ... No idea why ...
Where are the custom rom :crying:
Click to expand...
Click to collapse
You don't want a custom ROM. Fingerprint sensor doesn't work under custom ROMs at the moment.
Also trying to charge with the phone off with Magisk installed will give the perception of a brick.
You will need to jump through hoop to get the device to boot again.
Don't ever try to charge with the phone off with Magisk.

tech_head said:
You don't want a custom ROM. Fingerprint sensor doesn't work under custom ROMs at the moment.
Also trying to charge with the phone off with Magisk installed will give the perception of a brick.
You will need to jump through hoop to get the device to boot again.
Don't ever try to charge with the phone off with Magisk.
Click to expand...
Click to collapse
strange that

tech_head said:
You don't want a custom ROM. Fingerprint sensor doesn't work under custom ROMs at the moment.
Also trying to charge with the phone off with Magisk installed will give the perception of a brick.
You will need to jump through hoop to get the device to boot again.
Don't ever try to charge with the phone off with Magisk.
Click to expand...
Click to collapse
What are you talking about. I charge all the time with my device powered off and I always have magisk installed and never got the perception of a brick like you describe it. And custom rom are all extremely stable for this device fp is the only issue and it's got work being done and its already working on custom in the test groups on telegram. And they is always face unlock which is better than fp anyways.

se7ensde said:
What are you talking about. I charge all the time with my device powered off and I always have magisk installed and never got the perception of a brick like you describe it. And custom rom are all extremely stable for this device fp is the only issue and it's got work being done and its already working on custom in the test groups on telegram. And they is always face unlock which is better than fp anyways.
Click to expand...
Click to collapse
With Magisk charging with power off will cause the phone to stop at the "you phone corrupt" screen.

tech_head said:
With Magisk charging with power off will cause the phone to stop at the "you phone corrupt" screen.
Click to expand...
Click to collapse
LMAO no it won't. Like I said earlier I do this all time with no issues. You have something weird going on with your device.

se7ensde said:
LMAO no it won't. Like I said earlier I do this all time with no issues. You have something weird going on with your device.
Click to expand...
Click to collapse
Actually not. With the latest, I guess one or two releases of Magisk this is now fixed. Magisk forces something other than a normal boot from a patched image. My Essential had the charging while off for a year and this phone up until I installed the latest release.
So you are correct current version of Magisk does not cause the issue.

Another thing which is strange.
Since that bug yesterday I can't connect my phone to the computer to browse the internal DD.
Instead my file explorer (on the computer) display me a unknown dir in which I've got some sh script & window exe (I think they're there to install the op drivers).
No one get a idea of the why & how to fix it to go back to the OG behavior ?

allen2398 said:
Another thing which is strange.
Since that bug yesterday I can't connect my phone to the computer to browse the internal DD.
Instead my file explorer (on the computer) display me a unknown dir in which I've got some sh script & window exe (I think they're there to install the op drivers).
No one get a idea of the why & how to fix it to go back to the OG behavior ?
Click to expand...
Click to collapse
That's odd.... It sounds like a driver issue with your computer more than anything. BUT, do you get an option to change to file transfer mode from your pull down menu? I had an issue where it wouldn't even give me that option, and what actually worked for me was to plug my 6T into a USB 2.0 port on the BACK of my computer. Try these things out.
---------- Post added at 05:56 AM ---------- Previous post was at 05:56 AM ----------
Also, about the magisk charging thing? I've never tried to charge my phone while it was off with magisk installed, but that just sounds...... Weird!

allen2398 said:
Another thing which is strange.
Since that bug yesterday I can't connect my phone to the computer to browse the internal DD.
Instead my file explorer (on the computer) display me a unknown dir in which I've got some sh script & window exe (I think they're there to install the op drivers).
No one get a idea of the why & how to fix it to go back to the OG behavior ?
Click to expand...
Click to collapse
I have the extra same issue after the latest stable update....

H4X0R46 said:
That's odd.... It sounds like a driver issue with your computer more than anything. BUT, do you get an option to change to file transfer mode from your pull down menu? I had an issue where it wouldn't even give me that option, and what actually worked for me was to plug my 6T into a USB 2.0 port on the BACK of my computer. Try these things out.
---------- Post added at 05:56 AM ---------- Previous post was at 05:56 AM ----------
Also, about the magisk charging thing? I've never tried to charge my phone while it was off with magisk installed, but that just sounds...... Weird!
Click to expand...
Click to collapse
Yes I get the option to change to file transfer mode. My computer only got USB 3.0 port, I'll try to connect it to a 2.0 when I'm back from my trip. Thx for the tips 
 @loganville did you try the 2.0 trick ?

allen2398 said:
Yes I get the option to change to file transfer mode. My computer only got USB 3.0 port, I'll try to connect it to a 2.0 when I'm back from my trip. Thx for the tips
@loganville did you try the 2.0 trick ?
Click to expand...
Click to collapse
Yeah for sure! Report back when you get back and let us know if any of this worked! :good:

H4X0R46 said:
Yeah for sure! Report back when you get back and let us know if any of this worked! :good:
Click to expand...
Click to collapse
Just came back; and what a oddly thing :
- usb2 work on windows
- usb3 work on windows
- can't test usb2 on linux
- usb3 doesn't work on linux
I'll investigate the web about that

allen2398 said:
Just came back; and what a oddly thing :
- usb2 work on windows
- usb3 work on windows
- can't test usb2 on linux
- usb3 doesn't work on linux
I'll investigate the web about that
Click to expand...
Click to collapse
Odd. Yeah these newer Android devices are just weird like that! I've been told the Pixel devices are just as finicky as the 6T and I'm sure others out there are as well! Glad you're able to get a connection on Windows though! [emoji106]

After 2 month or so I think I found the reason of the bug : tremble !
The bug occured since I did the last oxygenos update (at the time) - maybe it came from the fact that the update was installed on the second partition !
I gonna try to make the new oxygenos update (which will be installed on the first partition) to ensure that. I'll come back here once it's done !

It was that ! After a update to the last OOS (which was installed on partition A) I can finally access my internal storage from a usb 3 on linux