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")
Related
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Atomschlumpf said:
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Click to expand...
Click to collapse
how old is the device?
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Atomschlumpf said:
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Click to expand...
Click to collapse
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Atomschlumpf said:
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Click to expand...
Click to collapse
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Mr.Ak said:
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Click to expand...
Click to collapse
No, I didn't. I tried the USB Drivers I had already installed, the drivers that came in the package and the QPST Tool suggested in the thread on both my and my girlfriends laptop. But if it doesn't work on ADB/fastboot I probably can't use it anyway since my only two options are having the phone on the fastboot screen or having it constantly reboot....
At this point I'm just really, really frustrated and have sorta accepted it's very likely a hardware issue
I'm with the same problem. In my case, the tool does recognize and shows green after the end but when i try to boot, it only shows the boot logo.
I can enter in fastboot and trying the command "fastboot continue" the brightness goes up, but nothing else
already tried various tools, back to stock, qualcomm , and none worked, so can i throw it out of the window?
Edit: can't enter in recovery, and unlike the op, my phone doesn't reboot (at least i didn't notice it)
So I unlocked the bootloader no problem. TWRP no problem, then something happened with the magisk flash. Phone tried to boot, as normal, then it went to recovery, then to a boot loop. I can get it to the fastboot screen, but ADB won't recognize the phone, I have chased around different USB drivers for two hours, thrown every command at it that I can think of, but nothing is working. Any suggestions? I literally picked the phone up (bought off of swappa locally), drove home and bricked it lol.
edit: The phone is recognized by my computer, just not ADB.
jerseymk2 said:
So I unlocked the bootloader no problem. TWRP no problem, then something happened with the magisk flash. Phone tried to boot, as normal, then it went to recovery, then to a boot loop. I can get it to the fastboot screen, but ADB won't recognize the phone, I have chased around different USB drivers for two hours, thrown every command at it that I can think of, but nothing is working. Any suggestions? I literally picked the phone up (bought off of swappa locally), drove home and bricked it lol.
edit: The phone is recognized by my computer, just not ADB.
Click to expand...
Click to collapse
So you put the phone in fastboot mode and ADB won't recognize the phone? That is normal, ADB works when the phone is booted normally. In fastboot mode you only use fastboot commands.
Fastboot devices
Just need to "fastboot flash boot boot.img" with the stock boot.img.
jsauder2 said:
Just need to "fastboot flash boot boot.img" with the stock boot.img.
Click to expand...
Click to collapse
Sorry I work for the railroad and was away for the last few day. I am aware of that, the issue I was facing was that the phone was not communicating with the laptop when I booted fastboot. I was able to get it this morning after about what felt like 900 attempts. I knew what needed to be done, I was having severe connectivity issues, I played the game of switching cables, switching usb ports etc... finally it had connectivity. Thank you again for your help though.
So here is what happened, I installed TWRP on my device and completely wiped my phone so I can install bootleggers OS and Gapps on my Pixel 2 Walleye. But I accidentally booted into Boot slot B on twrp and now the only thing the device can boot into is the bootloader mode, recovery and download mode is completely useless, It gives me either operation denied error or Error slot unbootable. The worst part is no computer will recognize my pixel in device manager at all. Mac computer will not detect it either. Ant tips on how to fix this? And again my I have all drivers installed and platform tools are up to date. And devices bootloader is unlocked.
Anything helps!
RomBetaTester said:
So here is what happened, I installed TWRP on my device and completely wiped my phone so I can install bootleggers OS and Gapps on my Pixel 2 Walleye. But I accidentally booted into Boot slot B on twrp and now the only thing the device can boot into is the bootloader mode, recovery and download mode is completely useless, It gives me either operation denied error or Error slot unbootable. The worst part is no computer will recognize my pixel in device manager at all. Mac computer will not detect it either. Ant tips on how to fix this? And again my I have all drivers installed and platform tools are up to date. And devices bootloader is unlocked.
Anything helps!
Click to expand...
Click to collapse
Did you use the same USB cable each time? If yes try different ones, even if it seems to work with other devices. On your PC go to device manager, then view and then hidden devices. Remove anything that has to do with Android. Then try connecting your device. Does an andriod driver show up after you've connected your device?
I have tried 3 different cables. But will try another one
RomBetaTester said:
I have tried 3 different cables. But will try another one
Click to expand...
Click to collapse
Did you go to view, hidden files in device manager and delete all Android drivers? And if you did, did anything show up after connecting your device?
I am having a similar issue after trying to flash the March update. During the script, the System image failed to transfer completely. I tried again using deuce flash all script, and it got a little further (4/5) with the System image but ultimately failed. Things got worse when my computer stopped recognizing the phone. Now I can't even try anything else because there is no communication, similar to OP. I have tried three different computers, three different cables, and have tried deleting Android related drivers in the device manager. No luck, unfortunately. I tried installing USB drivers from Google which also did not help. I welcome any other ideas of what to try next and appreciate any help.
EDIT: I solved the problem by draining the battery completely. In order to drain the battery, I first left the barcode screen on until eventually just the battery image is displayed on-screen when pressing power. Then eventually there will not be enough power to light up the screen at all, but the LED indicator will blink red while holding the power button. Now, I set up my phone such that the power button was held pressed down and left it there until the LED stopped blinking. Now that the power is completely drained, I could successfully get my computer to recognize it! I followed the steps in this post:
https://forum.xda-developers.com/showpost.php?p=78726736&postcount=13
EDIT2: I should also note that the system image didn't flash successfully the first time and I had repeat step 12 which is flashing the update. Luckily it worked the second time!
I had something similar happen. Held down power for about 10 seconds or so until the phone vibrated, then it was recognised by the computer. Then flash stock image
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
ricky56789 said:
I had something similar happen. Held down power for about 10 seconds or so until the phone vibrated, then it was recognised by the computer. Then flash stock image
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
Click to expand...
Click to collapse
Man you just saved me =)
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 :-\
hi everyone,
recently my phone died because a stupid mistake i made. i rooted it for i while and it was all good. ( i used magisk )
i had an new update to download and i downloaded it but not installed it yet.
the mistake i made is that i selected an option in magisk ( install to inactive slot after ota )
normally i install the ota update after that and it would boot up normally with magisk installed.
this time i forgot to install the update because i was bussy that day. so i have bootloop now.
so not i big deal was the first thing i thought. ( just use fastboot and use fastboot --set-active=a
but the problem is fastboot wont work anymore. the pc wont recognize my device anymore ( before all of this it was recognized just fine and i used fastboot more then once )
i also tryed to use msmdownloadtool but it wont boot to edl mode aswell ( pc wont recognize it either ) i used 2 different pc;
when i try to boot the phone youll see the op logo and then a black screen, when i puss the power button it says on the screen power off and restart. if youll do nothing it will reboot and do it all over again.
can someone please help me?
- cant use fastboot / recovery
- already wiped all data / cache
- edl mode wont start ( i know that the screen will stay black but msmdownloadtool wont find anyting and pc neither )
-re installed drivers etc
im really frustated that a stupid mistake this little caused so many problems. lol
I'm in the same situation in another device. If i solve my problem i will notify you
Try to use edl cable
I've found that I sometimes have to reinstall the bootloader driver.
If Device Manager on your PC shows the phone when you plug it in, even though you can't use fastboot commands, then reinstalling the driver may help.
Have a look at https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/ which has lots of screenshots.