cool 1 /LeRee LE3 drive image - Coolpad Cool1 Questions & Answers

Hi guys.
After many attempts I've done it - I bricked phone. As you probably guessed it was Cool 1 from LeEco.
My current situation is moderately positive, I haven't used hammer... yet .
Now, status of the phone is hard bricked but with possibility to go into download mode by making contraction on USB cable.
Unfortunately, to go forward I need drive image which i didn't make before flashing (yes, shame on me )
I tried to find it by Google and on XDA, but without success.
So, anyone have such image I would be very grateful for sharing it.

qqrykq said:
Hi guys.
After many attempts I've done it - I bricked phone. As you probably guessed it was Cool 1 from LeEco.
My current situation is moderately positive, I haven't used hammer... yet .
Now, status of the phone is hard bricked but with possibility to go into download mode by making contraction on USB cable.
Unfortunately, to go forward I need drive image which i didn't make before flashing (yes, shame on me )
I tried to find it by Google and on XDA, but without success.
So, anyone have such image I would be very grateful for sharing it.
Click to expand...
Click to collapse
Use this instead..
https://androidfilehost.com/?w=files&flid=215465
Download twrp for EUI from that link and flash it using Miflash tool.. You should be able to boot to twrp recovery and flash rom from there

dmilz said:
Use this instead..
Download twrp for EUI from that link and flash it using Miflash tool.. You should be able to boot to twrp recovery and flash rom from there
Click to expand...
Click to collapse
Thanks dmilz. I will try this next weekend.

Related

SM-N910F HARD brick! Desperate and running out of ideas..?!

Hi guys!
I would just like to start by apologizing for making another thread about a bricked note4, however I have read about so much I don't know which advice to go with anymore. I'm also a complete novice when it comes to this.
So long story short, my note 4 started playing up and lagging, eventually not turning back on at all. After endless attempts using odin and flashing what I seemed to have thought was the right firmware, it whittled down to about 1 in 5 attempts of trying to enter download mode (using the buttons) on the phone actually working. Now its completely bricked...no power, no download mode, nothing!
Just like to reiterate, I'm a complete novice,sorry if I'm not making sense, my knowledge doesn't go further than articles and google!
I have tried using kies to recover my phone and it cant recognize it...
I have read about using adb to get my phone into download mode, but I couldn't understand the explanation given well enough to use it...
I bought a 16gb micro sd card and have tried writing an unbrick image to it but I get no response off my phone, also tried another file, possibly sdc? cdc? cant quite remember, but that failed too.
I don't even know if the files I'm using are correct, I got them from a forum on here.
I'm at a loss!
The only hope I have left is if someone is able tell me if any steps I have tried are correct, and possibly provide me with the correct unbrick image?
Also, when I plug my phone into my computer via usb, there is a noise that sounds but nothing else happens, don't know if these means anything. As far as I'm aware I also have correct drivers installed.
Sorry about the long explanation!
Any help is greatly appreciated!
Thanks in advance.
Lucy.
Only logical result from your explanation is you have a hardware problem.
I dont think you are gonna be able to solve it with software...
Time for service visit i guess..
Turkawa said:
Only logical result from your explanation is you have a hardware problem.
I dont think you are gonna be able to solve it with software...
Time for service visit i guess..
Click to expand...
Click to collapse
Thanks for the reply!
I hope that's not the case forgot to mention,when I plug my phone into a computer and go into device manager, it shows qhsusb_bulk...if this means anything to you?
Lucyhenn123 said:
Thanks for the reply!
I hope that's not the case forgot to mention,when I plug my phone into a computer and go into device manager, it shows qhsusb_bulk...if this means anything to you?
Click to expand...
Click to collapse
Nope.. I have no idea.. Sorry
Try the sd recovery method .
First you can try to flash the pit partion .
You can find that on xda .
Just search for note 4 pit files.
Download the n910f pit file with correct csc.
TRY flashing via download mode.
Try flashing .
Use this guide for using sd card to get into download mode if you cant access download mode
There is a method for http://cloud.tapatalk.com/s/57e756f41dc6e/read me for brick fix.txt
Reporting via N910G

Mi Flash Error Discussion

Discussion on problems faced by Miflash tool.
*So when used for the first time I was able to unlock phone without any problem.
*But after that when I used it for second time to unbrick my phone I was constantly getting errors like not enough memory,some errors like x800000 blah blah...
*I almost went through every solutions mentioned in miui forum and XDA...But I was unable to get it working...
So if anyone faced any problem like that comment your problem below..
Aftef a lot of research I was able to find a solution for that..
Hopefully it will be shared with you all as soon as possible. I have to finish touching up some final things..
As soon as I finish the work I will be releasing alpha version..
Will update the thread when I release it
Waiting for the solution.
https://chat.whatsapp.com/H3jQvVgU5MZCRrlOFqSlIG
My Redmi Note 3 Qualcomm Whatsapp Group
Murshad007 said:
Waiting for the solution.
https://chat.whatsapp.com/H3jQvVgU5MZCRrlOFqSlIG
My Redmi Note 3 Qualcomm Whatsapp Group
Click to expand...
Click to collapse
Hopefully I was able to make alpha version of the software...worked fine for me on fastboot mode..want some testers
Edit..was able to boot up successfully..once confirmed by some testers I will release stable one
I experienced that "Not enough memory" thing. What I did was I used the latest MiFlash tool (restarted my PC first).
exce1ia said:
I experienced that "Not enough memory" thing. What I did was I used the latest MiFlash tool (restarted my PC first).
Click to expand...
Click to collapse
Yeah I faced it many time...not enough memory, buffer size0000 error blah blah blah...hopefully I was able to develop an app for to unbrick via fastboot... tried by me 2 times worked smooth but need some testers
Mi Flash & Nougat
Hi, if you want I'm ready to test your alpha version!
I have a dead Mi5 Pro (updated to xiaomi.eu Nougat rom) that my pc only reads as Qualcomm_9008.
I already tried many many posted potential solutions but my phone is still dead!
At this point, I HOPE that the problem is that latest MiFlash (30.aug.2016) is not so compatible with Nougat and I can't flash any ROM!
Waiting for your news!
Thank you very much
cleo1986 said:
Hi, if you want I'm ready to test your alpha version!
I have a dead Mi5 Pro (updated to xiaomi.eu Nougat rom) that my pc only reads as Qualcomm_9008.
I already tried many many posted potential solutions but my phone is still dead!
At this point, I HOPE that the problem is that latest MiFlash (30.aug.2016) is not so compatible with Nougat and I can't flash any ROM!
Waiting for your news!
Thank you very much
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/development/mi-fastboot-unbrick-tool-2-0-t3538614
Already released...
Edit use manual method..
No fastboot
adithyan25 said:
https://forum.xda-developers.com/redmi-note-3/development/mi-fastboot-unbrick-tool-2-0-t3538614
Already released...
Edit use manual method..
Click to expand...
Click to collapse
Thanks mate, but NOWAY to Fastboot here! My Mi5 is completely dead and I think in EDL because my pc can recognize it as Qualcomm device.
cleo1986 said:
Thanks mate, but NOWAY to Fastboot here! My Mi5 is completely dead and I think in EDL because my pc can
recognize it as Qualcomm device.
Click to expand...
Click to collapse
Try pressing vol down+pwr... If you see light blinking while connected to PC,that means you are in edl..
We are working on a tool that can flash through edl, the last tool was for fastboot unbrick...
In order to make sure you are in edl.connect phone to PC,open miflashtool and click refers..
If it shows something like COMXX (XX will be num) its in edl..u can flash stock rom via flashtool then
Already TRIED
adithyan25 said:
Try pressing vol down+pwr... If you see light blinking while connected to PC,that means you are in edl..
We are working on a tool that can flash through edl, the last tool was for fastboot unbrick...
In order to make sure you are in edl.connect phone to PC,open miflashtool and click refers..
If it shows something like COMXX (XX will be num) its in edl..u can flash stock rom via flashtool then
Click to expand...
Click to collapse
I already tried many times to flash in EDL via miflash but I have error 0x000..., hello packet, etc etc
PLEASE LET ME KNOW WHEN YOU HAVE EDL Tool!
Thank you very much
Ok so I have managed to brick my device pretty good (recovery seems gone), but I can get to FASTBOOT, and from there, followed a guide to get to EDL..
So now I got the mi flash tool to flash the 7.25 image as described by this guide :
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
No errors, but I don't think it worked because when the device reboots, it still can't seem to try and load a kernel (it goes black real quick). I am hoping it that the other unmentioned fields need populating etc..
Are there instructions on how to do a complete flash from EDL anywhere ?
Rapalax said:
Ok so I have managed to brick my device pretty good (recovery seems gone), but I can get to FASTBOOT, and from there, followed a guide to get to EDL..
So now I got the mi flash tool to flash the 7.25 image as described by this guide :
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
No errors, but I don't think it worked because when the device reboots, it still can't seem to try and load a kernel (it goes black real quick). I am hoping it that the other unmentioned fields need populating etc..
Are there instructions on how to do a complete flash from EDL anywhere ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/how-to/fix-bootloop-redmi-note-3-recovery-edl-t3521297
This will work for a complete clean flash via edl
Yep.. I managed to do something similar with a newer FB ROM and the modded twrp so there is less chance to relock my BL.
Thanks for providing the post.. it makes me feel more comfortable knowing that this info is available in case I need it again

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

Hard bricked,only vibrates

Hello guys,i was trying to flash LOS and after many tries i hard bricked my phone.At start,screen wasnt turning on and phone vibrated sholtly every 1 sec.I did EDL and then flashed different roms but still phone just vibrates but for a bit longer.When i do EDL it gets recognised by pc.Also when i flash a rom before i try to boot,if i connect it to power the led is blinking.
I dont want to be this guy who opens a thread that has opened many times,but i couldnt figure out a solution whatsoever.Thanks in advance.
Did you try downgrade from pie to oreo? Can you enter fastboot mode?
I bricked my phone too. Nothing worked for me. I hope you have more luck.
How it got bricked? Did you read the whole tutorial ?
emiljano539 said:
How it got bricked? Did you read the whole tutorial ?
Click to expand...
Click to collapse
I tried to flash from a video in youtube and didnt work.My system was deleted so i tried flashing different roms,it let me flash stock android and when i rebooted it just vibrated.Looks like the first vibration is the same as when the phone boots and the rest are a bit longer.
degen1997 said:
I tried to flash from a video in youtube and didnt work.My system was deleted so i tried flashing different roms,it let me flash stock android and when i rebooted it just vibrated.Looks like the first vibration is the same as when the phone boots and the rest are a bit longer.
Click to expand...
Click to collapse
Does it let you to boot into twrp now? If yes try to flash the stock rom via twrp there is a version which you flash directly with twrp
emiljano539 said:
Does it let you to boot into twrp now? If yes try to flash the stock rom via twrp there is a version which you flash directly with twrp
Click to expand...
Click to collapse
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.
degen1997 said:
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.
Click to expand...
Click to collapse
Check it :https://forum.xda-developers.com/showpost.php?p=75711835&postcount=2
I hope it helps
degen1997 said:
Sadly it doesnt,i can flash roms though with edl mode and miflash,maybe i haven't tried the correct one yet?Do you know which rom i need to flash for stock android 7 with mi flash?I've seen that other people have had the same problem but dont know if anyone managed to get through it.
Click to expand...
Click to collapse
I was one of them. I was lucky though and got a new phone from the dealer. I followed all the threads with the same issue. Never saw one user who was able to solve it.
XtraWater said:
I was one of them. I was lucky though and got a new phone from the dealer. I followed all the threads with the same issue. Never saw one user who was able to solve it.
Click to expand...
Click to collapse
I was thinking about flashing a Rom because im in stock now only rooted... But you guys scared me
emiljano539 said:
I was thinking about flashing a Rom because im in stock now only rooted... But you guys scared me
Click to expand...
Click to collapse
I recommend you to read a lot about flashing custom ROMs before trying to do it.
LineageOS has a pretty explicit installing tutorial.
If you can get into fastboot mode there is hope.
Remember that you must have the bootloader unlocked.
my thread
emiljano539 said:
How it got bricked? Did you read the whole tutorial ?
Click to expand...
Click to collapse
Hi everyone, I have rooted Mi A1 (pie), I have a hard brick. but fixed, when flashing Rom with TWRP, my phone cannot receive the partition / 'cache', when root receives the message: error: 28, I need help, thank you very much

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.

Categories

Resources