Related
I'm stuck at the very first image that appears on Orange Boston and i can't boot normally and i can't enter recovery mode either :|.
I flashed Cyanogen mod 6.1.0 RC4 this morning.Everything went well till i installed Adobe Flash Player 10.1.I rebooted my phone i realised that my wireless couldn't find my wi-fi network that was right next to the phone .The phone was laggier to.Then i turned it off.And wen i turned it back it would be stuck.And even the recovery mode is stuck before it even starts up (.
With my luck in life i doubt they would believe me with a lame excuse at Orange.If any of you know a good way to start at least the recovery mode so i can back-up my previous rom them please help.I'm very Desperate i tried a lot of things.
B42iso said:
I'm stuck at the very first image that appears on Orange Boston and i can't boot normally and i can't enter recovery mode either :|.
I flashed Cyanogen mod 6.1.0 RC4 this morning.Everything went well till i installed Adobe Flash Player 10.1.I rebooted my phone i realised that my wireless couldn't find my wi-fi network that was right next to the phone .The phone was laggier to.Then i turned it off.And wen i turned it back it would be stuck.And even the recovery mode is stuck before it even starts up (.
With my luck in life i doubt they would believe me with a lame excuse at Orange.If any of you know a good way to start at least the recovery mode so i can back-up my previous rom them please help.I'm very Desperate i tried a lot of things.
Click to expand...
Click to collapse
what kind of phone and recovery image do you have? I'll try to help, but just out of curiosity, did you post this in YOUR phone's forum Q&A section?
It's Gigabyte Codfish and it's named Orange Boston.It has alot of names around the world like 20 or 30 :|.The Recovery image is the latest Clockworkmod Recovery since i had to use it for Cyanogen.
Sadly my Phones not listed anywhere in the forum.
The thing is everything started to lag and my wi-fi started malfunctioning after I installed Adobe Flash Player 10.1 and after 1 Reboot and 1 power-off then turn-ons it stopped.
My phone has 2 boot images.The first one's with orange sqares and the second one is the Orange Logo/Cyanogenmod Logo depending on what i flashed,but it stops at the first one with the orange squares.
This happens at the Recovery mode to.If i could at least start the recovery mod i would re-flash my old os and then fix the rest of the problems.
B42iso said:
It's Gigabyte Codfish and it's named Orange Boston.It has alot of names around the world like 20 or 30 :|.The Recovery image is the latest Clockworkmod Recovery since i had to use it for Cyanogen.
Sadly my Phones not listed anywhere in the forum.
The thing is everything started to lag and my wi-fi started malfunctioning after I installed Adobe Flash Player 10.1 and after 1 Reboot and 1 power-off then turn-ons it stopped.
My phone has 2 boot images.The first one's with orange sqares and the second one is the Orange Logo/Cyanogenmod Logo depending on what i flashed,but it stops at the first one with the orange squares.
This happens at the Recovery mode to.If i could at least start the recovery mod i would re-flash my old os and then fix the rest of the problems.
Click to expand...
Click to collapse
ok, so firstly (and don't be offended) you should never ever ever flash a rom that isn't supported in a forum for your phone! second, try holding volume down and power and see if you get the bootloader/fastboot and pm me/reply here again. third, why did you flash rc4 (not yet "stable") and WHAT PHONE IS IT FOR?
Nothing happens and it says nothing at startup so Volume down + power isn't the right one for mine.I know the recovery mode (camera button+volume up+power) and something i'm not sure what it is but it says exit ftm mode (camera buton+volume down+power).
Well i used rom manager and it's for my phone the Z71 phone models that includes mine too.exit FTM mode does the same thing it shows the same image at the start and only writes a little text at the top left saying "exit FTM mode".
I'm not offended I'm really angry at myself so np.And RC4 is way more stable then RC1 cause RC1 drained my battery very fast.Adobe FLash player 10.1 has to be the culprit.My phone started to act strange only after i installed it.Before it worked like a miracle with RC4.Maybe another method would be to reset the apps in the internal memory but i guess that requieres recovery mode too...
I got it!The fastboot mode for me is Volume down+End Call+Power.
It's showing the same image at the beggining BUT the usb is recognised .This means with some Command Prompt magic we might be able to restore the previous Clockwork mod recovery cause the original does not have any special options and i can't really use my backup.
It's night time here I'll await your reply,I'll be here after school.This could help alot of people cause i heard about this kind of problem before but no explanation was given on how to solve it.
B42iso said:
I got it!The fastboot mode for me is Volume down+End Call+Power.
It's showing the same image at the beggining BUT the usb is recognised .This means with some Command Prompt magic we might be able to restore the previous Clockwork mod recovery cause the original does not have any special options and i can't really use my backup.
It's night time here I'll await your reply,I'll be here after school.This could help alot of people cause i heard about this kind of problem before but no explanation was given on how to solve it.
Click to expand...
Click to collapse
well, that's good. just to clarify, you have gained access to fastboot right?
also, you never answered what phone the rc4 you flashed was for, so, what phone was it for?
here is a link to adb (command prompt) - which is again for cdma hero's, so the guide may be off a little, but see if it helps... http://forum.xda-developers.com/showthread.php?t=690362
I said it's for Z71 phone types.It's a group of .... how do i say....no name phones or not so famous phones that includes mine to.Rom Manager automatically downloads the right version for my phone.I already looked up what's "Z71 phones" on the cyanogen forums. I'm not sure if fastboot works properly i've never seen it before on this phone,but the usb cable is recognised and that means it has to work.I'll look at the guide now...
I plugged in the device in to a fresh laptop withouth drivers.It said "Android Sooner Single ADB Interface".On my pc it's recognised cause i had the software tools programe installed when i made the official update and it installed the drivers by itself.
I'm still trying to get adb list my device cause it's not appearing .Probably wrong drivers?
Edit: Beside this tutorial you gave me looks like one that works with a normal working phone.There's a part that asks fo USB Debugging enabled.It was enabled before it crashed and never started again but i doubt it counts now.
Edit: Never mind i'm stupid it's right under the first post .
God my phone scared the crap out of me :|.After playing with fastboot and trying to get is listed in adb devices,which is stupid cause i had to type fastboot devices instead.I plugged it out for a little time it turned off and id didn't show a thing after i plugged it back now it's frozen with a dark orange low battery icon.It's probably dead low.I'll wait for it.Ps: I've never seen that battery icon :| so i pray it's not another nuisance problem to deal with.
Edit:Now that i think of it.... it was around 35% battery and after the incident i used it un-plugged to trying to get something started.
Here's the real guide by the same guy for fastboot: http://forum.xda-developers.com/showthread.php?t=532719.
YEEEEYYYY!!!!
Rejoice Brothers and Sisters.Thx to GOD, il Duce's support with help and for giving me strenght to not be depressed i made it .
Ok so I entered Fastboot mode and started command prompt.Connected my device to my pc and i showed command prompt the directory of adb for me it was
"B:\android-sdk-windows\tools" i copied from my sd card my nandroid backup files for my old ROM and i put them inside the tools folder.Then i did the following in Command Prompt:
these should take some time and you have to do them 1 by 1
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
After reboot don't be scared like i was :| it's only stuck for a litle time because it's the first start up after the flash. That's all ^^.
Credits: il Duce,brandenk,nephron and Me for broking,experimenting and fixing my phone.
B42iso said:
Rejoice Brothers and Sisters.Thx to GOD, il Duce's support with help and for giving me strenght to not be depressed i made it .
Ok so I entered Fastboot mode and started command prompt.Connected my device to my pc and i showed command prompt the directory of adb for me it was
"B:\android-sdk-windows\tools" i copied from my sd card my nandroid backup files for my old ROM and i put them inside the tools folder.Then i did the following in Command Prompt:
these should take some time and you have to do them 1 by 1
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
After reboot don't be scared liek i was :| it's only stuck for a litle time because it's the first start up after the flash. That's all ^^.
Credits: il Duce,brandenk,nephron and Me for broking,experimenting and fixing my phone.
Click to expand...
Click to collapse
COOL glad you got it working! I don't really know how I helped, sounds like you did most of the work, but glad I could help
Warning! You were right that ****ing ROM is 1 of the culprits ^^.I couldn't help myself but to try it withouth Adobe Flash player.It lasts as long as you don't power-off and then trun your phone back on.
So this is confirmed.I'm too lazy to report this to Cyanogen u.u... or should I?
Well i succesfully restored my phone again.SO guys with Z71 phones out there don't use Cyanogen 6 RC4 YET,cuase you amy end up like me .
I reported this to Cyanogen.Btw I would laugh hard if this became a famous tutorial lol.
Hi I tried using the method to upgrade my motorola greco xt502 (z71, boston orange clone) to CyanogenMod 6 V6.1.0-RC4 for z71 and now cant even boot into clockworksmod recovery. it says entering recovery with motorola icon and stuck there.Please Help .
nand backup please
B42iso said:
Rejoice Brothers and Sisters.Thx to GOD, il Duce's support with help and for giving me strenght to not be depressed i made it .
Ok so I entered Fastboot mode and started command prompt.Connected my device to my pc and i showed command prompt the directory of adb for me it was
"B:\android-sdk-windows\tools" i copied from my sd card my nandroid backup files for my old ROM and i put them inside the tools folder.Then i did the following in Command Prompt:
these should take some time and you have to do them 1 by 1
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
After reboot don't be scared like i was :| it's only stuck for a litle time because it's the first start up after the flash. That's all ^^.
Credits: il Duce,brandenk,nephron and Me for broking,experimenting and fixing my phone.
Click to expand...
Click to collapse
happy for you, i have the same problem but i have no nand backup, i'm a noob, can you please upload a nand backup on mediafire or something like that?
saybron said:
happy for you, i have the same problem but i have no nand backup, i'm a noob, can you please upload a nand backup on mediafire or something like that?
Click to expand...
Click to collapse
Sorry man... this was ages ago, i don't have the files anymore, if I do have them then it's on my old desktop that's in another town and I won't be going there soon, cause i have university here.
thanks
B42iso said:
Sorry man... this was ages ago, i don't have the files anymore, if I do have them then it's on my old desktop that's in another town and I won't be going there soon, cause i have university here.
Click to expand...
Click to collapse
No problem, thanks man!
Hi
so the problem started like this
i had my nexus 5 rooted and it was good
then i decided to unroot the device , so i searched i found this kingo root app , and by mistake tried to root my device
it did not work as the app said , so i ignored the app , and kept using my phone like normal , but then my phone shuts down cuz of battery
no problem , i connected it to the charger , but then it keeps on boot loop , it wont boot , and i tried to flash it but i cant
also when i go to bootloader and then recovery mode , it says no command found
PS : the only time my PC can see my nexus in USB debugging mode is when its in boot loop​
khird said:
Hi
so the problem started like this
i had my nexus 5 rooted and it was good
then i decided to unroot the device , so i searched i found this kingo root app , and by mistake tried to root my device
it did not work as the app said , so i ignored the app , and kept using my phone like normal , but then my phone shuts down cuz of battery
no problem , i connected it to the charger , but then it keeps on boot loop , it wont boot , and i tried to flash it but i cant
also when i go to bootloader and then recovery mode , it says no command found
PS : the only time my PC can see my nexus in USB debugging mode is when its in boot loop​
Click to expand...
Click to collapse
How are you trying to flash your phone? Is it through the factory images here: https://developers.google.com/android/nexus/images ? This is usually the easiest way to flash the factory images, but your phone may not work with these in the state it is right now.
As for the "no command found", that is normal behavior for stock recovery. In fact, there isn't much you can do with the stock recovery and you may be used to a custom recovery like TWRP or CWM.
What I would try is to enter recovery mode, where the dead Android appears. Then, hold the volume up and power button for about three seconds. After this, you can let go of the volume up, while still holding the power button. After a while, commands should appear and you can try a factory reset, or maybe a simple cache wipe might work for you.
If that still doesn't work, flash the factory images from the link I sent while on the "no command page". In that state, your phone should be recognized by the computer and you should be able to flash properly. You may have to install adb on you computer and drivers if that isn't already done.
Best of luck!
Hi,
SITUATION : I just had a big problem with my OP6. First of all, I was on Oreo stock Rom and I decided to upgrade to Pie by flashing .zip via TWRP. Everything goes well, but after some days of use and for some reasons I wanted to roll-back to Oreo and I flashed the downgrade .zip but this time via Local upgrade. Again, everything goes well but when trying to flash TWRP via Fastboot, I used "fastboot boot TWRP.img" and phone booted into it. Then, BEFORE flashing the TWRP.zip file I accidentally changed the slot (b to a) and rebooted to system.
PROBLEM : Now, the device is stucked on a black screen with withe notification LED on, and whatever the situation. Bootloader isn't accessible anymore. None of the buttons combination work properly. I don't know what to do. I looked for MSM software but do I need to access Bootloader to use it ? It's possible to power off the device (white LED turn off), but nothing more.
Thanks for any future advices
power off ur device !!!
open msm software and connect ur phone through usb and press up volume + power button and u will see it getting connected to the msm software and leave it till ur phone starts booting ito OOS 5.1.5
Here is the Link to the MsmDownloadTool V4.0:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
With this Tool, you get your Phone working again.
StandBrik said:
Hi,
SITUATION : I just had a big problem with my OP6. First of all, I was on Oreo stock Rom and I decided to upgrade to Pie by flashing .zip via TWRP. Everything goes well, but after some days of use and for some reasons I wanted to roll-back to Oreo and I flashed the downgrade .zip but this time via Local upgrade. Again, everything goes well but when trying to flash TWRP via Fastboot, I used "fastboot boot TWRP.img" and phone booted into it. Then, BEFORE flashing the TWRP.zip file I accidentally changed the slot (b to a) and rebooted to system.
PROBLEM : Now, the device is stucked on a black screen with withe notification LED on, and whatever the situation. Bootloader isn't accessible anymore. None of the buttons combination work properly. I don't know what to do. I looked for MSM software but do I need to access Bootloader to use it ? It's possible to power off the device (white LED turn off), but nothing more.
Thanks for any future advices
Click to expand...
Click to collapse
I hope u fixed it by now, but if you still haven't fixed it yet, you can go back to slot b by using this commands "fastboot --set-active=B" without the quotes
Because I messed up my slot a, so i used that command to boot using slot b and it worked. So, if the problem is with your slot a and everything with your slot b is fine, then you just need to change to slot b with that command and all should go well :highfive:
just noticed that you're having a problem accessing the bootloader. First, make sure your device is not connected to your pc or anything. Then, whether your device is off or stuck in that black screen, just hold vol up and power off at the same time and wait until it eventually boots into the bootloader mode.
Problem solved with MSM software. Thanks everyone. If someone has the same issue. Just download MSM software and use the following guide :
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
It is actually quite impossible to totally hardbrick a device like this one.
Cheers
Glad to hear that.
Just in case i got into that problem, could you lead me to the files you downloaded since the ones in that link seem to be for OnePlus 5
In my situation, I have a black screen, and a fixed blue LED.
I want to put the LineageOS ROM, but it's impossible, even though it performs the installation of the ROM correctly, when you restart it that happens, and then it doesn't even let you install or start the TWRP again.
It only remains to use MSMDownloadTool, to return to the Stock rom.
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.
Naveenthemi said:
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.
Click to expand...
Click to collapse
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?
Fcyrp Zip Need to Flash After Flash any Custom Rom
And Come in Telegram Official Group For Any Support of Redmi Note 7 Pro https://t.me/Rn7proGlobal
zhou111 said:
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?
Click to expand...
Click to collapse
Yes it's hardbricked for sure! But are you sure MiFlash doesn't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...
Naveenthemi said:
Yes it's hardbricked for sure! But are you sure MiFlash doens't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...
Click to expand...
Click to collapse
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.
zhou111 said:
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.
Click to expand...
Click to collapse
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)
Naveenthemi said:
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)
Click to expand...
Click to collapse
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.
zhou111 said:
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.
Click to expand...
Click to collapse
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too
Naveenthemi said:
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too
Click to expand...
Click to collapse
I entered the command says waiting for device. how do you flash with adb?
zhou111 said:
I entered the command says waiting for device. how do you flash with adb?
Click to expand...
Click to collapse
Oh that means ADB isn't recognizing it.
There isn't much we can do if ADB doens't recognize it!
Did you look up for Service Centres?
zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.
hackeroid said:
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.
Click to expand...
Click to collapse
He/She said the phone doesn't boot into Fastboot either so that's very unlikely to work :-\
I've bought this phone about a year ago, I installed Xiaomi.eu (one of the first stable releases for my device) right after and I've never had any problems, but lately I've been experiencing some issues like ghost touch, apps and even the phone itself crashing often, etc. I was thinking about flashing stock rom again but I've never done it, in fact I haven't used fastboot and recovery at all since I first flashed Xiaomi.eu rom.
I was using my phone like normal today and shortly after opening an app (nothing special, it was just YT Vanced) my phone turned off started a bootloop, I've tried entering recovery mode and fastboot but when I try I just see the Fastboot logo and then the phone reboots, in this short period of time with the Fastboot logo my pc recognizes my phone is connected but in device manager it says there are no drivers installed for it, and adb doesn't show anything in the list of connected devices.
You need to install adb drivers
tabun1994 said:
You need to install adb drivers
Click to expand...
Click to collapse
I had them but for some reason it wasn't picking up on the USB port I was using, I switched port now and I'm trying to flash with MiFlash but it keeps rebooting even after I hit "flash" on the program, and adb still isn't working even though now the device is recognized in device manager ("Bootloader Interface")