Database Users

Having an impossible time flashing CM11 rom, been at it for hours please HELP

This used to be easy.
After 8 hours yesterday I think I managed to root the phone. CWM/TWRP will not install. At all, under any method. Rom manager, goo manager, I now get this stupid message that says that "an application attempted to access something unauthorized and has been blocked" over and over.
Just trying to flash CM11 rom. Guess I need to learn how to sideload or something? I physically can't get my phone to recovery mode other than the stock Android, which does not have the "flash zip from sdcard" option.
For the love of god help me. My phone stopped working around 2 pm yesterday and I seriously can't believe I'm about to be going into day 2 of this, so rather than drive myself crazy i'm going to wait for help

bump please help should be simple

Hi,
Please, don't panic! Panic is your worst enemy . First, give a good read here: http://forum.xda-developers.com/showthread.php?t=2419762. Then try again . It's very likely Knox is blocking your TWRP/CWM installation, that's why you receive this message.
All the best,
~Lord

XxLordxX said:
Hi,
Please, don't panic! Panic is your worst enemy . First, give a good read here: http://forum.xda-developers.com/showthread.php?t=2419762. Then try again . It's very likely Knox is blocking your TWRP/CWM installation, that's why you receive this message.
All the best,
~Lord
Click to expand...
Click to collapse
thanks
knox is disabled
root is gained
su is installed
rom manager and goo manager installed
when i downloaded the CM rom from goo manager and try to install it, the phone restarts in download mode and just sits there...

Damani311 said:
thanks
knox is disabled
root is gained
su is installed
rom manager and goo manager installed
when i downloaded the CM rom from goo manager and try to install it, the phone restarts in download mode and just sits there...
Click to expand...
Click to collapse
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord

XxLordxX said:
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord
Click to expand...
Click to collapse
tried flashing four different CWM tars, all are failing.

XxLordxX said:
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord
Click to expand...
Click to collapse
tried flashing four different CWM tars, all are failing.
also trying to flash TWRP
its just all failing on the install

Hi,
Please post your installation issue on the Galaxy S4 Help Thread there might be someone better than me to help you there. Also are you sure you're flashing the right files and using the right method? Did you try another USB Cable? Did you try another Odin version? It all can contribute to the fail.
~Lord

XxLordxX said:
Hi,
Please post your installation issue on the Galaxy S4 Help Thread there might be someone better than me to help you there. Also are you sure you're flashing the right files and using the right method? Did you try another USB Cable? Did you try another Odin version? It all can contribute to the fail.
~Lord
Click to expand...
Click to collapse
its the official samsung cable. and yes i tried others
tried other versions of odin as well
and different versions of both twrp and cwm
its crazy i tells ya xD

If it fails to flash true Odin, then you are doing something wrong.
- Different pc
- Reinstall drivers
- Different cable
- Different usb port
- Make sure kies is not running in the background
What are you running? Windows 8? Try a windows 7 pc.
Post the details of the error you are getting.
Also when the flash goes succesfull, but you still don't have a custom recovery, then uncheck auto-reboot.

can someone please link me to a guaranteed working version of a flashable recovery for odin ?
I know its a lot to ask but I've actually gone through almost that entire list you listed
tried diff cables
no kies runnning
on windows 7
drivers been installed twice
maybe i should try the other port, but in case that doesnt work can anyone just link me? sorry i've just never had this much problems with this, must be b/c of the new security knox update or w/e in oct of last year. Last June I did all this in about 15 minutes....

I had the same trouble with the knox crap yesterday, the only way I could get it rooted and/or with custom recovery was to use the Cyanogen windows installer, then when CM booted I then rebooted into recovery and installed a different rom from there. :good:

dwarfer66 said:
I had the same trouble with the knox crap yesterday, the only way I could get it rooted and/or with custom recovery was to use the Cyanogen windows installer, then when CM booted I then rebooted into recovery and installed a different rom from there. :good:
Click to expand...
Click to collapse
that's crazy
so where do i find this windows installer? i'm just trying to put CM on there so I suppose this would work

Hi i know youve already said said its officail cable but im saying try another different s4 cable. Because when i was installing recovery or anything it wouldnt let me (i thought i had original white s4 cable) but then i got my dads cable (hes gt s4) and it worked instantly. These fake cables are at large and its very very difficult to tell if its original.
Also like previous guy said using a different computer/laptop also helps i know because ive flashed my phones since day 1.
GL and plz let me know if u managed to fix it another way as its always good to try new options when others fail.

189cutter said:
Hi i know youve already said said its officail cable but im saying try another different s4 cable. Because when i was installing recovery or anything it wouldnt let me (i thought i had original white s4 cable) but then i got my dads cable (hes gt s4) and it worked instantly. These fake cables are at large and its very very difficult to tell if its original.
Also like previous guy said using a different computer/laptop also helps i know because ive flashed my phones since day 1.
GL and plz let me know if u managed to fix it another way as its always good to try new options when others fail.
Click to expand...
Click to collapse
alright it'd be awesome if someone can post a link to the files the work, for sure.
CM windows installer
CWM odin tar file
TWRP odin tar file

Damani311 said:
alright it'd be awesome if someone can post a link to the files the work, for sure.
CM windows installer
CWM odin tar file
TWRP odin tar file
Click to expand...
Click to collapse
http://www.cyanogenmod.org/ then click the start button and follow the instructions.
It will get you to download the installer (or http://dist01.slc.cyngn.com/CMInstaller.msi?t=1403660099360) the click it to run, It may download an update for itself, then it will download recovery, operating system, gapps, then start to install everything. About 300mb altogether.
That way you don't need the tar files, just search on this sight for flashable from recovery for the recovery files you want. (I use the touch versions myself).

dwarfer66 said:
http://www.cyanogenmod.org/ then click the start button and follow the instructions.
It will get you to download the installer (or http://dist01.slc.cyngn.com/CMInstaller.msi?t=1403660099360) the click it to run, It may download an update for itself, then it will download recovery, operating system, gapps, then start to install everything. About 300mb altogether.
That way you don't need the tar files, just search on this sight for flashable from recovery for the recovery files you want. (I use the touch versions myself).
Click to expand...
Click to collapse
thanks, but naturally this would be too easy
says: "not supported on your device"
a freaking S4 AT&T! what the ****?

From what I've read AT&T have locked bootloaders. Glad I have an unlocked Australian version!

Yeah so if anyone can still find a way to help me that'd be awesome. Wasted two days already and rather not be stuck with stock

Damani311 said:
Yeah so if anyone can still find a way to help me that'd be awesome. Wasted two days already and rather not be stuck with stock
Click to expand...
Click to collapse
So do you have an AT&T phone? If you do, you are in the wrong section of the forum.

[Q] Bricked S5 Exynos Variant....

Hi XDA!!
I am experiencing problems on my Samsung Galaxy S5 Exynos variant (SM-G900H).
It has been soft-bricked. I can clearly say so as it can boot into stock recovery and in download mode, but not in stock 4.4.2.....
It has been bricked due to following the steps mentioned in this thread : s health and xposed
Many videos on youtube ask the viewer to flash stock Samsung Firmware from sammobile.com using odin in download mode.
I have a problem even there.... all versions of odin get stuck on initializing......
Tried on all USB ports.... Kies closed..... basically done everything everybody wrote on XDA.
Any new bright ideas would be appreciated....
Thanks in advance!!:good::good:

skb_twiz said:
It has been soft-bricked. I can clearly say so as it can boot into stock recovery and in download mode,
Click to expand...
Click to collapse
You need to do more reading. A lot more.
You clearly haven't tried everything yet. Nor are you are bricked if you can boot into recovery mode. It sounds like you have messed up the system files preventing a normal boot.
Odin is the most common way of recovering. Use Odin 3.09, ensure that you have disabled anti virus, malware amd firewall software and do not have intensive programs running in the background. If necessary use a different computer.
Flash a full stock firmware, ideally the same version as the current firmware on your phone. But in any event, not an older version and matching your current CSC /carrier /baseband. And you ought to make the effort to find the correct PIT file and flash it at the same time. This insures that you don't have any lingering partition corruption. A forum search will explain all about PIT files. And someone probably has a thread with the actual files too.
It will work. In the worst case, you will just need to find a different PC.
.

fffft said:
You need to do more reading. A lot more.
You clearly haven't tried everything yet. Nor are you are bricked if you can boot into recovery mode. It sounds like you have messed up the system files preventing a normal boot.
Odin is the most common way of recovering. Use Odin 3.09, ensure that you have disabled anti virus, malware amd firewall software and do not have intensive programs running in the background. If necessary use a different computer.
Flash a full stock firmware, ideally the same version as the current firmware on your phone. But in any event, not an older version and matching your current CSC /carrier /baseband. And you ought to make the effort to find the correct PIT file and flash it at the same time. This insures that you don't have any lingering partition corruption. A forum search will explain all about PIT files. And someone probably has a thread with the actual files too.
It will work. In the worst case, you will just need to find a different PC.
.
Click to expand...
Click to collapse
You seriously think that I don't mean it when I said that I had tried everything?? All steps you mentioned have been tried before I read your reply... Anyways, going on a different PC helped... apparently Odin is quite moody.... If it decides it is not going to run on a PC, it simply will get stuck on initialization... hence the solution is to find a PC which has run Odin before... It will work on that PC definitely!!! If you can't find one, try running on all PC's in your vicinity (friend's, family etc). There will be one that can run Odin...
And by the way, I clearly said my phone is "soft-bricked"... It means that I can boot only into recovery or download... not android... so my friend, you are quite wrong in saying that my phone isn't bricked...
Sent from my SM-G900H using XDA Free mobile app

skb_twiz said:
You seriously think that I don't mean it when I said that I had tried everything?? All steps you mentioned have been tried before I read your reply... Anyways, going on a different PC helped... apparently Odin is quite moody.... If it decides it is not going to run on a PC, it simply will get stuck on initialization... hence the solution is to find a PC which has run Odin before... It will work on that PC definitely!!! If you can't find one, try running on all PC's in your vicinity (friend's, family etc). There will be one that can run Odin...
And by the way, I clearly said my phone is "soft-bricked"... It means that I can boot only into recovery or download... not android... so my friend, you are quite wrong in saying that my phone isn't bricked...
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
Did you try a data factory reset/clear the caches in recovery and reboot and go one from there?

gee2012 said:
Did you try a data factory reset/clear the caches in recovery and reboot and go one from there?
Click to expand...
Click to collapse
Yes... but to no avail... anyways... like I said above, flash the stock firmware in download mode again using Odin... If Odin gets stuck, try it on a different PC...
I will not recommend anyone to do data factory reset as
(1) It won't do anything that helps you
(2) If you don't reset your phone, you can still retain your apps and settings after flashing the stock firmware again!!
<i>LOL, here I am, posting solutions to my own problem!!</i>

same
skb_twiz said:
Yes... but to no avail... anyways... like I said above, flash the stock firmware in download mode again using Odin... If Odin gets stuck, try it on a different PC...
I will not recommend anyone to do data factory reset as
(1) It won't do anything that helps you
(2) If you don't reset your phone, you can still retain your apps and settings after flashing the stock firmware again!!
<i>LOL, here I am, posting solutions to my own problem!!</i>
Click to expand...
Click to collapse
I am an exynos man, and have fewer options and waiting for better prospects OR 6 months of purchase to pass before tinkering. Anyway I appreciate u posting the solutions you found for your own problem. See you have gained a THANKS point from me.

suchiqaz said:
See you have gained a THANKS point from me.
Click to expand...
Click to collapse
I have thanked you for thanking me...
For everyone else, this thread will remain open forever even though my S5 is back up and running...
This thread is now no longer limited to the Exynos variant... All are welcome...
Any problem regarding unbricking any S5 can be discussed here and I will try my best to help you...
Sent from my Reborn GALAXY S5

Le pro 3 x720 brick?

Hi, since yesterday I have a big problem with my le pro 3, while charging the phone suddenly turned off. The system did not want to turn on, so I went into recovery (TWRP) and tried to format and upload a new rom, unfortunately during the flashing, a blue screen appeared. When changing the kernel, the flashing of the rom was done, but with the installation of the gapps it hung. I tried to install another rom, but it also spilled, with this addition, that I can not enter recovery, because artifacts appear or reboots.. Only fastboot works. With it, I tried to flash the kernel, recovery, but it did not do anything. I also used (TOOL ALL in ONE) and uploaded the stock rom, but the phone still does not work. Do you know what else could help, or is buying a new phone? Thanks for help

If you can use fast boot, your phone is not hard bricked. A brick is when you can not do anything , you will have a black screen and a red blinking light if a usb cable is connected.
Try pushing Twrp ( newest version) to the phone. If that is successful boot to recovery, fully wipe your phone, reboot to recovery and install you Rom> Gapps, and Magisk. I would suggest initially flashing Lineage 15.1. Once your phone is restored, flash whatever you would like.
If it doesn't work try another cable, or another port, or another computer. Computer needs to be up to date and you may need to temporarily disable antivirus, if the All in One tool isn't working its likely that your computer is blocking the install. especially if you are using Windows 10. All the program to be open within your firewall settings. Make sure its up to date and use AIO to update android drivers and adb.

I'm not giving anything, I still can't get into recovery

miichus said:
I'm not giving anything, I still can't get into recovery
Click to expand...
Click to collapse
Click reply to the person you are talking to otherwise, they will not receive a notification of your response.
Next, if you expect some help, be courteous, to people spending their own limited free time to help with your self created issue by clicking the thank you button.
Finally read this link: https://forum.xda-developers.com/showpost.php?p=76947769&postcount=4

tsongming said:
Click reply to the person you are talking to otherwise, they will not receive a notification of your response.
Next, if you expect some help, be courteous, to people spending their own limited free time to help with your self created issue by clicking the thank you button.
Finally read this link: https://forum.xda-developers.com/showpost.php?p=76947769&postcount=4
Click to expand...
Click to collapse
The operation in flashone goes well, but it still does not help. System and recovery does not boot, only fastboot

miichus said:
The operation in flashone goes well, but it still does not help. System and recovery does not boot, only fastboot
Click to expand...
Click to collapse
What does the log say?
if you are getting no errors at at and can only boot to fastboot try the All in One tool or use the QPST method to unbrick. Also, some posted versions of Qfil are corrupted. Did you use the version that I provided a link for?

tsongming said:
What does the log say?
if you are getting no errors at at and can only boot to fastboot try the All in One tool or use the QPST method to unbrick. Also, some posted versions of Qfil are corrupted. Did you use the version that I provided a link for?
Click to expand...
Click to collapse
For the second time I tried to use flashOne and the phone started up. When entering the pin code, the phone was stuck again. When I wanted to reboot, I could only enter fastboot again.

miichus said:
For the second time I tried to use flashOne and the phone started up. When entering the pin code, the phone was stuck again. When I wanted to reboot, I could only enter fastboot again.
Click to expand...
Click to collapse
For the second time I tried to use flashOne
Click to expand...
Click to collapse
Okay sure, I provided you with a link to the correct files to use. I.E Flash 2.0 and le_zl1_qfil_ufs_fix.zip
Twice you have mentioned that you are using flash One, when you should be using flash 2.0
What Pin code?
Your pin error sounds like you are either using the old Qfil ( its corrupted, and never worked for anyone. ) Or the technician repair rom did not complete. There will be a log file on the PC from Flash 2, not the phone, is port 9008 open in device manager?
There should be no pin code, if qfil was installed, all of your data would be wiped, did you encrypt the phone with 3rd party software?
Are also using the wrong version of Qfil?
Review these additional steps
https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121

tsongming said:
Okay sure, I provided you with a link to the correct files to use. I.E Flash 2.0 and le_zl1_qfil_ufs_fix.zip
Twice you have mentioned that you are using flash One, when you should be using flash 2.0
What Pin code?
Your pin error sounds like you are either using the old Qfil ( its corrupted, and never worked for anyone. ) Or the technician repair rom did not complete. There will be a log file on the PC from Flash 2, not the phone, is port 9008 open in device manager?
There should be no pin code, if qfil was installed, all of your data would be wiped, did you encrypt the phone with 3rd party software?
Are also using the wrong version of Qfil?
Review these additional steps
https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Click to expand...
Click to collapse
I am using flashone 2.0 and flashing from your link, the file "le_zl1_qfil_ufs_fix.zip". Port 9008 is open. After three flash in 2.0 flash, I could enter recovery, but when flashing custom rom, a blue screen appeared.

Not enough information, did you follow all of the steps? You can't just flash a Rom after unbricking.
To be clear
You restored the phone, booted into the system, turned on developer options, checked oem unlocking, booted into recovery, and did a factory reset to repair the storage as outlined in my instructions link?
Then booted into the system again, turned on developer options, checked oem unlocking, checked that storage is accurate?
From this point you start over, if your storage issue isn't fixed you will get a blue screen.
After you have perform those steps you should be able to use the all in one tool to check that the bootloader is unlocked, install the latest TWRP, compatible Rom, Gapps and latest magisk.
If you still have issues after all of that. No doubt, its hardware related. It could be one part or several parts. Time to buy a new phone.
Sent from my Pixel XL using XDA Labs

tsongming said:
Not enough information, did you follow all of the steps? You can't just flash a Rom after unbricking.
To be clear
You restored the phone, booted into the system, turned on developer options, checked oem unlocking, booted into recovery, and did a factory reset to repair the storage as outlined in my instructions link?
Then booted into the system again, turned on developer options, checked oem unlocking, checked that storage is accurate?
From this point you start over, if your storage issue isn't fixed you will get a blue screen.
After you have perform those steps you should be able to use the all in one tool to check that the bootloader is unlocked, install the latest TWRP, compatible Rom, Gapps and latest magisk.
If you still have issues after all of that. No doubt, its hardware related. It could be one part or several parts. Time to buy a new phone.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
Once we managed to load the system, which hung up after 3 seconds and the whole situation started again. Failed to reload the system or enter recovery. I did all the steps in turn. After the system startup I did not even manage to enter the settings, because it has already hung up and restarted.

miichus said:
Once we managed to load the system, which hung up after 3 seconds and the whole situation started again. Failed to reload the system or enter recovery. I did all the steps in turn. After the system startup I did not even manage to enter the settings, because it has already hung up and restarted.
Click to expand...
Click to collapse
That sucks!
Its either that the partitions are inaccurate or you have hardware problems.
If its partitions, its not something that I have experience with. However, I did find this link; which has instructions for resolving partition issues using the MiniTool Partition Wizard and HDD Raw Copy Tool. https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html

tsongming said:
That sucks!
Its either that the partitions are inaccurate or you have hardware problems.
If its partitions, its not something that I have experience with. However, I did find this link; which has instructions for resolving partition issues using the MiniTool Partition Wizard and HDD Raw Copy Tool. https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html
Click to expand...
Click to collapse
Hi tsongming Where do I get this files ???
* prog_emmc_firehose_8936.mbn (I think for our x720 has to be prog_emmc_firehose_8916.mbn)
* rawprogram0.xml
* patch0.xml
I have seen this procedure on different sites but none of them provide this files
I hope you can help me
Thanks in advance

mavelino said:
Hi tsongming Where do I get this files ???
* prog_emmc_firehose_8936.mbn (I think for our x720 has to be prog_emmc_firehose_8916.mbn)
* rawprogram0.xml
* patch0.xml
I have seen this procedure on different sites but none of them provide this files
I hope you can help me
Thanks in advance
Click to expand...
Click to collapse
They should download automatically, if you follow the instructions on those previous Links . The instructions should show which folders the files are located in.
Luckily, I saved these files the last time I de-bricked someones phone.
Here is the link to my Google Drive: https://drive.google.com/open?id=1mjvi_FR4Xh9QfSg6imMLduQ6p3zP2e_u
See the Thanks button: Click it, send cash or both.

tsongming said:
They should download automatically, if you follow the instructions on those previous Links . The instructions should show which folders the files are located in.
Luckily, I saved these files the last time I de-bricked someones phone.
Here is the link to my Google Drive: https://drive.google.com/open?id=1mjvi_FR4Xh9QfSg6imMLduQ6p3zP2e_u
See the Thanks button: Click it, send cash or both.
Click to expand...
Click to collapse
Noup they do not download automatically (I followed the instructions), I tried flashone tool procedure in a windows 7 computer and did not work (I already tried this a lot of times on to differente laptops with windows 10), I have not tried the qfil procedure because I do not have the files I mentioned before. Please if you have them upload them (* prog_emmc_firehose_8996.mbn* rawprogram0.xml* patch0.xml)
Thanks in advance

mavelino said:
Noup they do not download automatically (I followed the instructions), I tried flashone tool procedure in a windows 7 computer and did not work (I already tried this a lot of times on to differente laptops with windows 10), I have not tried the qfil procedure because I do not have the files I mentioned before. Please if you have them upload them (* prog_emmc_firehose_8996.mbn* rawprogram0.xml* patch0.xml)
Thanks in advance
Click to expand...
Click to collapse
All I have is in the link you just responded to.
if that doesn't work try unpacking the Qfil and and see if you can just extract them.
I will look further when I get back home.

i also have an bricked LEX 3 Pro . i bought it as an X722 but of cause iam not shure . could also be an X720. i can not find the difference.
so Phone has only fastboot.
when i plug in usb cable it just reboot every 10 sec . no charging sreen appears
i flash Qfil, but not helped it stay the same

so installed a rom but upon start up nothing is working please help

I see my second screen panel long press settings and nothing no luck.
twrp starts then closes can't even type USB debug when tapping settings

am I s.o.l ?

Which rom did you install
Twrp verison?
Device variant?
In addition to rom what did you flash?

Which rom did you install alpha omega oreo
Twrp version?latest (not fully sure)
Device variant?995
In addition to rom what did you flash? i removed stuff like 3min batt and Verizon stuff ..since I don't have cell service atm

i95swervin said:
You need to follow the instructions I specified in the rom thread.
Click to expand...
Click to collapse
Yeah, My dumbass thought it was ok to remove said apps.

If all else fails, you could always use LGUP to restore your device as long as you're able to get into download mode

tech_infinity said:
If all else fails, you could always use LGUP to restore your device as long as you're able to get into download mode
Click to expand...
Click to collapse
Can you provide a link of the stuff or steps needed.
This thread https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732 or something else?

Download mode did work.
I downloaded LGUP and VS995 oreo KDZ flashed it got the KDZ file from https://lg-firmwares.com/downloads-file/17008/VS99520c_01_1110_ARB00.kdz if anyone is interested. So that being said don't debloat or remove apps unless you know what you're doing and you also have backups made for your phone.

Device not detecting in Adb devices but gets detect in fastboot devices

Hi, everyone I tried to flash a new recovery on X00T but before I did this I Wiped all the data except internal storage. I Flashed the new recovery (completely forget about there being no OS) I rebooted to recovery and ignored the no OS message as the device rebooted I came on a black screen even the fast boot mode screen was black. I had no idea what to do so I tried to install the old TWRP from power shell/Adl so I could have a recovery and then install Custom rom again from recovery.
But there when I try to flash a file with command
-> Fastboot flash Recovery ....(..= file name)
It is shown completed on pc but on android even after rebooting I can't get anything except the black screen. This is what I get when I enter the following commands
-> fastboot devices
My devices number is shown
but if I type.
-> adl devices
My device is not shown.
But when I press the recovery buttons on device adl devices Is able to recognise device as a recovery screen device.
And the extra bonus on this is when I try to flash rom or fimware from adl. It says unable to read zip file.
So can anyone tell me if there is a way to fix this unable to read zip file problem. (I have tried uninstalling and reinstalling drivers from device manager & tried installing 64 bit files also)
Is there a command to flash rom from recovery. Or any way to fix this black screen
Thanks to everyone for reading any advice would be really helpful at this time.

Try using Asus Flash Tool to flash stock ROM

Tianhe said:
Try using Asus Flash Tool to flash stock ROM
Click to expand...
Click to collapse
Thanks for helping, Will surely try it. Can you please provide the link from where i can download flash tool?

Xda user 101 said:
Thanks for helping, Will surely try it. Can you please provide the link from where i can download flash tool?
Click to expand...
Click to collapse
I am not sure if posting external links (except hosting sites) is permitted. A simple google search or search within XDA will give you the results. In case you face difficulty, PM me.

Try to use this adb
If it still doesn't get detected, maybe use usb hub.
I wrote a thread guiding people on how to install stuff and my experience (issues) that is similar to yours. Not sure if my thread will help ya though

Vysair said:
Try to use this adb
If it still doesn't get detected, maybe use usb hub.
I wrote a thread guiding people on how to install stuff and my experience (issues) that is similar to yours. Not sure if my thread will help ya though
Click to expand...
Click to collapse
Bro tried as you said but didn't worked but finally found a solution. Now device is on and working again.

If anyone else face this issue I followed this thread https://forum.xda-developers.com/as...uide-revert-to-stock-rom-lock-t3798420/page46
It worked on my phone it is on again. Will have to root again but learned my lesson will never try new twrp when there is no os installed. :laugh:

thanks you Tianhe and Vysair for your advice for solving the issue.