Hi
Last night my phone accidentally drop then its not boot up as it show only boot logo of onepus so I decided to reflash the phone I successfully install driver of ORT co 9008 then detect then unbrick or flash using this all steps completes successfully then I remove phone from PC and start or switch on phone but its won't on even as before it was showing the oeplus logo as saw before and new its comport detecting and gone in device manager.
Thnx pls help
lokeshbhati1987 said:
Hi
Last night my phone accidentally drop then its not boot up as it show only boot logo of onepus so I decided to reflash the phone I successfully install driver of ORT co 9008 then detect then unbrick or flash using this all steps completes successfully then I remove phone from PC and start or switch on phone but its won't on even as before it was showing the oeplus logo as saw before and new its comport detecting and gone in device manager.
Thnx pls help
Click to expand...
Click to collapse
Obviously people are reading this. We don't know what to say, probably because most of us suspect the phone's fall broke something. If the fall did *not* break something in the phone, maybe using TWRP to attempt flashing a rom will work. Do you have TWRP installed? If not, use your computer (and Odin) to do so. Make sure to REBOOT IMMEDIATELY to recovery (TWRP, that is). Unplug phone from computer, replug phone into computer again. It should be recognized. Copy a rom of your choosing to the "download" directory on the phone. Then "factory wipe" the phone. (Do NOT wipe "internal storage"). Flash the rom (and gapps if this is a custom rom). Reboot. And here's hoping it works!
How can i install or go custom recovery After successful flash its not show adb or oneplus device not boot on,no bootloader,not show anything.dear
lokeshbhati1987 said:
How can i install or go custom recovery After successful flash its not show adb or oneplus device not boot on,no bootloader,not show anything.dear
Click to expand...
Click to collapse
But flash was not successful. Is the phone showing any sign of life? Charging icon on screen when cable is plugged in? Anything? I fear you have broken it.
No sign of life only heating when connected to charger or USB in computer only show Qualcomm port 9008 in pc when I press both volumes+power button
shonkin said:
Obviously people are reading this. We don't know what to say, probably because most of us suspect the phone's fall broke something. If the fall did *not* break something in the phone, maybe using TWRP to attempt flashing a rom will work. Do you have TWRP installed? If not, use your computer (and Odin) to do so. Make sure to REBOOT IMMEDIATELY to recovery (TWRP, that is). Unplug phone from computer, replug phone into computer again. It should be recognized. Copy a rom of your choosing to the "download" directory on the phone. Then "factory wipe" the phone. (Do NOT wipe "internal storage"). Flash the rom (and gapps if this is a custom rom). Reboot. And here's hoping it works!
Click to expand...
Click to collapse
shonkin said:
But flash was not successful. Is the phone showing any sign of life? Charging icon on screen when cable is plugged in? Anything? I fear you have broken it.
Click to expand...
Click to collapse
No sign of life only heating when connected to charger or USB in computer only show Qualcomm port 9008 in pc when I press both volumes+power button
Related
I tried searching thoroughly, but nothing matched my problem and no solution worked. I hope someone out there can help me with this:
My vibrant had TMO's Froyo with Team Whiskey's Bionix V and Dragon voodoo OC v3.1 kernel
I used clockwork 2.5.1.3 to flash Bionix V 1.2 with voodoo.
I didnt disable voodoo (first time i ever did that, being told that I didnt need to by friends and numerous forums.)
Phone rebooted, showing Dragon's logo, then a strange split-second blip occured and I was back into clockwork red. I tried rebooting and the same thing happened.
Now, my phone reboots only into clockworkmod red (can still access clockwork green by "apply sdcard:update.zip").
Cannot odin because usb is no longer working for some reason (which means I cannot adb either).
I can only access download mode through clockwork 2.5.1.3 (advanced ->Reboot to Download Mode).
when I plug in to recharge, it shows the battery with the loading circle in the center, then the phone reboots to cwm red.
After getting frustrated, I foolishly started applyig all wipes and attempted to install all zip files i had. all files say E:cant mount yadda yadda.
I'm at a total loss. I dont think I bricked because the phone turns on and I can access red and green clockwork.
Please, someone help...I dont wanna throw the phone from the roof only to get a hardware locked one from TMO's warranty, lol.
dsilver981 said:
I tried searching thoroughly, but nothing matched my problem and no solution worked. I hope someone out there can help me with this:
My vibrant had TMO's Froyo with Team Whiskey's Bionix V and Dragon voodoo OC v3.1 kernel
I used clockwork 2.5.1.3 to flash Bionix V 1.2 with voodoo.
I didnt disable voodoo (first time i ever did that, being told that I didnt need to by friends and numerous forums.)
Phone rebooted, showing Dragon's logo, then a strange split-second blip occured and I was back into clockwork red. I tried rebooting and the same thing happened.
Now, my phone reboots only into clockworkmod red (can still access clockwork green by "apply sdcard:update.zip").
Cannot odin because usb is no longer working for some reason (which means I cannot adb either).
I can only access download mode through clockwork 2.5.1.3 (advanced ->Reboot to Download Mode).
when I plug in to recharge, it shows the battery with the loading circle in the center, then the phone reboots to cwm red.
After getting frustrated, I foolishly started applyig all wipes and attempted to install all zip files i had. all files say E:cant mount yadda yadda.
I'm at a total loss. I dont think I bricked because the phone turns on and I can access red and green clockwork.
Please, someone help...I dont wanna throw the phone from the roof only to get a hardware locked one from TMO's warranty, lol.
Click to expand...
Click to collapse
You should be able to Odin..try these steps
Remove battery and put it back in (to make sure phone is powered off)
Disconnect USB from phone and Open Odin
While holding both Volume buttons...insert USB back into phone
Phone should boot into Download mode
Odin that sh*t
I did all that, i dont get the COMM port in Odin, so I did "adb devices", and got "list of devices attached" with no list. When I insert the USB cable, I dont even hear the usual windows tone acknowledging the new device. This leads me to believe that the USB on the phone is not working. tried it with 2 different cables on 2 different phones using all USB ports.
dsilver981 said:
I did all that, i dont get the COMM port in Odin, so I did "adb devices", and got "list of devices attached" with no list. When I insert the USB cable, I dont even hear the usual windows tone acknowledging the new device. This leads me to believe that the USB on the phone is not working. tried it with 2 different cables on 2 different phones using all USB ports.
Click to expand...
Click to collapse
do you have the correct drivers? try installing the drivers from this thread
http://forum.xda-developers.com/showthread.php?t=728929
and try again
I've used odin in mid Jan, so I know the drivers are up to date.
Here's what will freak you out even more. if I remove the battery while the phone is plugged in (to the wall or to the computer), the phone shuts off. BUT, if the phone is off with the battery in and I plug the phone (again, to wall or comp), the battery indicator with loading circle shows up. before I know how much battery I have left, the phone automatically boots into red cwm without me touching anything. I can post a video on youtube if it will help at all.
dsilver981 said:
I've used odin in mid Jan, so I know the drivers are up to date.
Here's what will freak you out even more. if I remove the battery while the phone is plugged in (to the wall or to the computer), the phone shuts off. BUT, if the phone is off with the battery in and I plug the phone (again, to wall or comp), the battery indicator with loading circle shows up. before I know how much battery I have left, the phone automatically boots into red cwm without me touching anything. I can post a video on youtube if it will help at all.
Click to expand...
Click to collapse
i see
did you make a Nandroid prior to flashing??
I did, but I get:
E: Can't mount /dev/block/mmcblk0p1 (or /dev/bloc
k/mmcblk0)
(Device or resource busy)
Can't mount /sdcard
Do you think I royally screwed my phone?
dsilver981 said:
I did, but I get:
E: Can't mount /dev/block/mmcblk0p1 (or /dev/bloc
k/mmcblk0)
(Device or resource busy)
Can't mount /sdcard
Do you think I royally screwed my phone?
Click to expand...
Click to collapse
No not really
i've seen worse get recovered
Getting Odin to work is your best bet
you say the phone can go into download mode...but if Odin can't recognize it then there's 1 of 2 things goin on:
1. The correct drivers are not installed
2. You arent using the up-to-date Odin
Odin is the way to go, I used odin and got the stock vibrant files from google, it is not a rom its the original stock vibrant files
Sent from my SGH-T959 using XDA App
Ok,
reinstalling driver v1.3.450.0 from the link you sent me.
using Odin 1.7
Its not that odin cant recognize, its that the usb appears to not be working except to show the empty battery with the loading circle. I'll try again, and make a video so you can see whats going on.
Try rebooting your computer also. Sometimes when my computer will not connect to my phone a reboot fixes the problem.
Just to re-itterate.
After you have re-installed drivers, reboot your PC.
Then open Odin up.
Then pull your battery on you phone, put it back in, hold only the volume buttons and plug the usb cable in. (Just in case, take out SD CARD and SIM card, older version of odin didn't like those being in either)
Load PIT and JFD stock rom.
Flash.
Double check the following.
You need to make sure ODIN is already up and running first. Also make sure that you are not using a USB extender or HUB as odin often does not like those. If you are using a desktop, plug the cable directly into the USB port in the back of the PC.
If you are using a LT, try different ports as not all USB ports provide full power on all laptops.
The PC reboot is important. I have seen ADB get stuck in the background and nothing works right. Let us know how it goes.
I can tell you that you are not completely bricked. As long as you are getting into CWM you are still ok.
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
herghost said:
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
Click to expand...
Click to collapse
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
jombo2323 said:
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
Click to expand...
Click to collapse
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
herghost said:
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
Click to expand...
Click to collapse
you are 100% positive you did EXACTLY what i said?
I have no idea what went wrong
That's the problem with toolkits though. People don't know what they're doing and when something goes wrong you don't know how to fix it!! I understand where toolkits come from, but they are only useful if you know what happens in the background when you click on a button.
Thread Moved
Thread belongs in Q&A. Not the Dev Forum
Post moved.
MD
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
erica_renee said:
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
Click to expand...
Click to collapse
You Star
Put me on the right track, my PC was basically assuming that it was my S3, in the end I removed everything with samsung in it from the registry, uninstalled all the drivers then tried again, correctly showing as a nexus and not a samsung
Hi
As many people here i've encountred a problem with fota while being using a rooted ROM (g.lewarne ROM)
Now my phone is bricked. I can't go into recovery nor Download mode. I only have the LG logo for moments with error: secure booting error!
cause: boot certification verify
When i plug my phone it is not recognized in the hardware manager. I've already installed Drivers.
All i have in the hardware manager is a new hard under name QHSUSB_BULK that needs driver.
I have just one hope to get my phone alive, by reconizing it again by my computer, then maybe i can go under download mode.
I've tried everything but nothing could work without download mode.
PS: I've made a hard reset, which was maybe a silly decision.
By the way, after installing the OTA my phone went into CWM Recovery, it was detectable by adb, i used adb to reinstall TWRP, then i used command
"adb reboot download" instead of "adb reboot recovery", then i had never seen the CWM recovery again, only the mentioned above error.
After few seconds my phone screen goes black but the phone is still on since i can see light at the corners of the phone.
and it is not reachable by adb.
It makes me crazy now.
once i plug it to the computer it gives me plenty drives to format and one drive with only one folder inside called image, only readable, with many files inside.
Could you please help me to get my phone alive?:crying:
I own an LG G2, i recently got this phone yesterday from a person on craiglist. Don't worry i didn't pay him i gave him my older phone i dont use anymore. SO This phone is practically stuck in Firmware Update (As i read that post) , i spent about a day and half figuring it out and what happens is that.
I CAN get into recovery its TWRP v2.7.0.0 by Turning off the phone first and then Holding Vol UP, Power, Vol Down at the same time until the LG Logo comes up and then i am still holding them down, and it says Recovery Mode please wait and bam TWRP.
But heres the problem i can't mount my OTG and i can't ADB Sideload. So what do i do from here?? this guy rooted this phone and soft bricked it i think? and he wiped the phone but i also did when i had the chance and wiped it completly via recovery.
The only way i got into "Download Mode" / "Firmware Update" was to take the back cover off and unscrew a few screws on the side and unclip the battery for a few seconds and then plugged it back in and then I held the VOl UP button and plugged my USB into the phone and the other end is in my PC. My phone says "Download Mode please wait" and then prompted with the Firmware Update screen. BUT my pc doesnt detect the phone whatso ever and i've already installed drivers and etc from this forum ( http://forum.xda-developers.com/showthread.php?t=2432476 ) its the 2015 method that i downloaded.
so what do i have to do, i havent tried using different usb cables, the port seems fine to be plugged in since in TWRP it says 84+ so i meant its charging right? help me out guys idk what else to do or flash or anything.
IAmTechFreq said:
I own an LG G2, i recently got this phone yesterday from a person on craiglist. Don't worry i didn't pay him i gave him my older phone i dont use anymore. SO This phone is practically stuck in Firmware Update (As i read that post) , i spent about a day and half figuring it out and what happens is that.
I CAN get into recovery its TWRP v2.7.0.0 by Turning off the phone first and then Holding Vol UP, Power, Vol Down at the same time until the LG Logo comes up and then i am still holding them down, and it says Recovery Mode please wait and bam TWRP.
But heres the problem i can't mount my OTG and i can't ADB Sideload. So what do i do from here?? this guy rooted this phone and soft bricked it i think? and he wiped the phone but i also did when i had the chance and wiped it completly via recovery.
The only way i got into "Download Mode" / "Firmware Update" was to take the back cover off and unscrew a few screws on the side and unclip the battery for a few seconds and then plugged it back in and then I held the VOl UP button and plugged my USB into the phone and the other end is in my PC. My phone says "Download Mode please wait" and then prompted with the Firmware Update screen. BUT my pc doesnt detect the phone whatso ever and i've already installed drivers and etc from this forum ( http://forum.xda-developers.com/showthread.php?t=2432476 ) its the 2015 method that i downloaded.
so what do i have to do, i havent tried using different usb cables, the port seems fine to be plugged in since in TWRP it says 84+ so i meant its charging right? help me out guys idk what else to do or flash or anything.
Click to expand...
Click to collapse
I think the methods leave out that you need to change your phone to com port 41 on device manager > ports in order to be detected. Then you need to unplug it and reconnect to computer when the program shows waiting for device, with the phone in download mode already.
Also, to get to recovery you hold vol down and power, when the LG logo comes up release power and hold it again until the reset screen comes up.
To get to download mode you turn the phone off then hold up while plugging the USB cord in with it connected to pc... This launches download mode.
Sent from my LG-VS980 using XDA Free mobile app
Yoinx said:
I think the methods leave out that you need to change your phone to com port 41 on device manager > ports in order to be detected. Then you need to unplug it and reconnect to computer when the program shows waiting for device, with the phone in download mode already.
Also, to get to recovery you hold vol down and power, when the LG logo comes up release power and hold it again until the reset screen comes up.
To get to download mode you turn the phone off then hold up while plugging the USB cord in with it connected to pc... This launches download mode.
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Well you see man , I cant change anything in Device Manager since my phone isn't being detected. It didn't install drivers fully fully since my phone isnt recognized. Even in TWRP or "Download Mode/ Firmware Update" Nothing happens no drivers installing or anything even but it does boot it up to that point....and its just normal boot up i see the LG logo and my led goes from green to blueish in a smooth transition and it doesnt stop until i turn it off. The method i got into recovery is holding all those buttons down its not a problem for me to get into it. I also have another problem it doesn't seem to want to mount my usb otg by samsung.
what do i do
So i tried the otg route but I can't mount it. I have everything connected and once I go into recovery to mount usb-otg, nothing happens.
I just need some way to get a ROM.zip in my phone
Computer does not recognize my phone.
Stuck at LG logo unless I enter recovery.
Sideload doesnt work.
OTG doesnt work.
I've tried at least 4 different guides with no luck.
Why don't you manually install drivers from online?
ive tried
tzzeri said:
Why don't you manually install drivers from online?
Click to expand...
Click to collapse
ive tried that already and it doesnt list anything from the LG folder.
I realized the phone will say start the adb sideload feature. so, when i put the "abd sideload file.zip" command on my pc i just wait a few minutes and it says daemon not running on port 5037 and then start successfuly and then error :device not found.
it can seem to reognize my device wether its in recovery, or download mode or fastboot mode.
Try again in other pc that has never been conected to an LG Phone before. It can perfectly be a conflict with drivers installed in the OS.
I've tried man
AFter i cleaned the usb port in one of the chats or forums, i waited a day ovbiously without turning on the phone and cleaned the usb port with alchohal and a q tip and i plugged my phone into my computer and my PC detected something but it only says "Unknown Device" everytime no matter what pc i use it says that. nothing else. but before that none of my pcs would detect theirs a phone plugged in at all.
IAmTechFreq said:
AFter i cleaned the usb port in one of the chats or forums, i waited a day ovbiously without turning on the phone and cleaned the usb port with alchohal and a q tip and i plugged my phone into my computer and my PC detected something but it only says "Unknown Device" everytime no matter what pc i use it says that. nothing else. but before that none of my pcs would detect theirs a phone plugged in at all.
Click to expand...
Click to collapse
Might be a problem with the cord
Sent from my Motorola DynaTAC using XDA Free mobile app
tzzeri said:
Might be a problem with the cord
Sent from my Motorola DynaTAC using XDA Free mobile app
Click to expand...
Click to collapse
No there is no problem with your USB cord or port. You need to do following steps.
http://forum.xda-developers.com/showthread.php?t=2432476
https://www.youtube.com/watch?feature=youtu.be&v=g01Pa7cgdSM&app=desktop
Please let me know if you succeed.
All credit goes to #bender_007
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
both volume buttons + plug the wire doesn't work?
senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
I have exactly the same problem, could you solve it? I'm very worried about my phone
ale0796 said:
I have exactly the same problem, could you solve it? I'm very worried about my phone
Click to expand...
Click to collapse
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
senny22 said:
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
Click to expand...
Click to collapse
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
ale0796 said:
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
Click to expand...
Click to collapse
Really glad I could help