I have this device and i m loving it but after miui update, it does not connect to computer..no matter whatever i have done including usb debugging,power cycles,reinstalling drivers,mtp,ptp mode. However, when connected to pc, i can hear the connection sound..moreover, softwares like mobogenie,moborobo does recognize the device and connects..even miui suite does not connect..it says enable usb debugging whereas it already has been..plz extend your expertise and help
imurreflection said:
I have this device and i m loving it but after miui update, it does not connect to computer..no matter whatever i have done including usb debugging,power cycles,reinstalling drivers,mtp,ptp mode. However, when connected to pc, i can hear the connection sound..moreover, softwares like mobogenie,moborobo does recognize the device and connects..even miui suite does not connect..it says enable usb debugging whereas it already has been..plz extend your expertise and help
Click to expand...
Click to collapse
Have you tried EDL mode and reflashing Stable MIUI 8 there? Whole different driver, whole different mode.
Crossvxm said:
Have you tried EDL mode and reflashing Stable MIUI 8 there? Whole different driver, whole different mode.
Click to expand...
Click to collapse
Can you please explain what EDL mode is
.i m from India so not sure if reflashing the device will avoid warranty and OTA updates
imurreflection said:
I have this device and i m loving it but after miui update, it does not connect to computer..no matter whatever i have done including usb debugging,power cycles,reinstalling drivers,mtp,ptp mode. However, when connected to pc, i can hear the connection sound..moreover, softwares like mobogenie,moborobo does recognize the device and connects..even miui suite does not connect..it says enable usb debugging whereas it already has been..plz extend your expertise and help
Click to expand...
Click to collapse
imurreflection said:
Can you please explain what EDL mode is
.i m from India so not sure if reflashing the device will avoid warranty and OTA updates
Click to expand...
Click to collapse
EDL mode is Xiaomi's official way to flash on our locked bootloader. It is the only way we can go from Stable to Developer, or recover our device without unlocking the bootloader. It doesn't void the warranty since it is not a modification, nor root, nor a custom rom.
In short, EDL mode for us locked bootloader users (Redmi Note 3, Mi Max, etx) is fastboot mode. If you have owned an older Xiaomi device before the locked bootloader, you probably remember how we can get into Fastboot mode or Recovery mode via the Power + Volume Down or Volume up button combination while powered off. Locked bootloader doesn give us access to those, and instead, we must use Volume Up + Volume Down + Power button combination at the same time while our device is off in order to get into EDL mode (the phone will vibrate, but the screen will stay black and will be detected differently on Windows).
Crossvxm said:
EDL mode is Xiaomi's official way to flash on our locked bootloader. It is the only way we can go from Stable to Developer, or recover our device without unlocking the bootloader. It doesn't void the warranty since it is not a modification, nor root, nor a custom rom.
In short, EDL mode for us locked bootloader users (Redmi Note 3, Mi Max, etx) is fastboot mode. If you have owned an older Xiaomi device before the locked bootloader, you probably remember how we can get into Fastboot mode or Recovery mode via the Power + Volume Down or Volume up button combination while powered off. Locked bootloader doesn give us access to those, and instead, we must use Volume Up +at Volume Down + Power button combination at the same time while our device is off in order to get into EDL mode (the phone will vibrate, but the screen will stay black and will be detected differently on Windows).
Click to expand...
Click to collapse
Hey, thats great info.. Thanks a lot.. I was able to get the issue resolved. I found that thete was an issue with MTP driver.. I reinstalled it and PC immediately recognized it.. Thanks again for your help
Related
Hello,
I tried to flash my phone from global 8.0.3.0 stable to 8.2.4.0MAGCNDL China Stable. Miflash said flashing was successfull, but then I started my phone and was on a bootloop.
I cannot access edl mode via deep flash cable anymore, it´s just loading. My phone isn´t unlocked that´s why i can´t flash over fastboot. I already tried to the recover mode and downloaded a chinese version of Mi Pc Suite. It detects my device but when I try to recover it switches for like 3 secs to the right screen but then immediately switchs back to the first screen (connect device).
One thing i´ve noticed is there is an option to choose a xiaomi ota file, what is that, because I can´t find anything.
Is there any hope for my phone?
Not good, you shouldent even try to flash china stable(you can but why). so, i think you should enter EDL with testpoints, or you can try do hard reset, maybe this will work.
use this method and then flash your mi5s with stable global.
http://en.miui.com/thread-310325-1-1.html
Download Mi PC suite china version then enter recovery mode and connect the phone to pc,let it make the update and your done.
mezutelni said:
Not good, you shouldent even try to flash china stable(you can but why). so, i think you should enter EDL with testpoints, or you can try do hard reset, maybe this will work.
Click to expand...
Click to collapse
Thanks for your reply, how can I hard reset my device? And I watched a yt video for tespoints , is it the same procedure as with the mi5 ?
hzare2611 said:
use this method and then flash your mi5s with stable global.
Click to expand...
Click to collapse
I got a Edl cable, but I can´t get into edl.
XMoDuLeSx said:
Download Mi PC suite china version then enter recovery mode and connect the phone to pc,let it make the update and your done.
Click to expand...
Click to collapse
Not working, it just stops immediatly the process, if I press recover
Then u need to connect the phone via USB 2 not 3 and install the correct driver's. The phone must be detected Android adb interface
XMoDuLeSx said:
Then u need to connect the phone via USB 2 not 3 and install the correct driver's. The phone must be detected Android adb interface
Click to expand...
Click to collapse
I´ve installed all drivers and it´s connected to a usb 2 port. Phone is in Device Manager under "Kedacom USB Device/Android ADB Interface"
if you cannat connect the phone as edl,you should give it to mobile repaire center and they fix it with boot boxes for you.
Thanks for all your help guys, I finally recovered my phone and I´m on Lineage OS now.
So I bought a redmi note 5a(prime) from a local retailer nearby. I was careless and didnt check the phone.After opening the phone at my home , its not booting up at all and retailer says you bricked the mobile and its against warranty.I didnt even use it once.Please help if anything can be done. No repair shop has been able to fix the problem.Any help or information will be highly appreciated.
Shaurya9008 said:
So I bought a redmi note 5a(prime) from a local retailer nearby. I was careless and didnt check the phone.After opening the phone at my home , its not booting up at all and retailer says you bricked the mobile and its against warranty.I didnt even use it once.Please help if anything can be done. No repair shop has been able to fix the problem.Any help or information will be highly appreciated.
Click to expand...
Click to collapse
Have you try using edl method?
But at least can you access fastboot first, using power off + volume down
If you could, then it can boot into edl mode using tools provided from the internet, there are many of them
And flash fastboot firmware using MI flash or Qualcomm Flash Image Loader (QFIL)
voidGlyph said:
Have you try using edl method?
But at least can you access fastboot first, using power off + volume down
If you could, then it can boot into edl mode using tools provided from the internet, there are many of them
And flash fastboot firmware using MI flash or Qualcomm Flash Image Loader (QFIL)
Click to expand...
Click to collapse
No, I tried but nothing happens.I can't enter fastboot and nothing appears other than that logo. I think the device is completely bricked and I don't think I can fix this.Thanks for your time.
Shaurya9008 said:
No, I tried but nothing happens.I can't enter fastboot and nothing appears other than that logo. I think the device is completely bricked and I don't think I can fix this.Thanks for your time.
Click to expand...
Click to collapse
Because I have another xiaomi device before, and it also get into penguin logo, and I can assure that my device has no installed os too
But because most of xiaomi phone chipset is Qualcomm, and Qualcomm device has edl mode, to flash image
And sure with my bricked device (stuck in penguin logo), I still able to access edl mode
But it was my old phone, not Redmi Note 5A, and I'm searching for how to enter edl mode on Note 5A, the process is you must use test point inside the device
Other than that, I don't know though
But if for my old phone (Redmi 2 Prime) the procedure is press volume down, then insert USB cable that connected to pc, then I can start to flash using QFIL
voidGlyph said:
Have you try using edl method?
But at least can you access fastboot first, using power off + volume down
If you could, then it can boot into edl mode using tools provided from the internet, there are many of them
And flash fastboot firmware using MI flash or Qualcomm Flash Image Loader (QFIL)
Click to expand...
Click to collapse
you can reflash ROM by using EDL method which you have to shortcircuit some pins to enter EDL, it is pretty easy if you have the tools. After reflashing it, reboot and it should be okay.
nayefhaidir said:
you can reflash ROM by using EDL method which you have to shortcircuit some pins to enter EDL, it is pretty easy if you have the tools. After reflashing it, reboot and it should be okay.
Click to expand...
Click to collapse
Oh yeah I forgot about this too, this is the most useful one
I also saw some people do with test point
Because I don't have any experience to do that, so I didn't do, as it needs to crack open the phone
Few days ago i flashed the Twrp recovery and yesterday i decided to remove it. I locked OEM and it bricked(take a loot at the picture).
The problem is that i can't enter in download mode since i bought it. To flash TWRP, I had to use adb command to reboot the tablet in download mode, but now, bricked, there is no way to use adb.
I had many Samsung devices, so i know how to enter in download mode , in this case power volume + volume -.
Does anyone know some kind of software that when you connect tablet with PC, tablet will enter in download mode?
I think that warranty is voided, so i just don't want to go to a samsung service center.
The picture: https://1drv.ms/u/s!Aitd6zSfsnM-gcghBLfHxmBH1vQ5CQ
jinglei207 said:
Few days ago i flashed the Twrp recovery and yesterday i decided to remove it. I locked OEM and it bricked(take a loot at the picture).
The problem is that i can't enter in download mode since i bought it. To flash TWRP, I had to use adb command to reboot the tablet in download mode, but now, bricked, there is no way to use adb.
I had many Samsung devices, so i know how to enter in download mode , in this case power volume + volume -.
Does any know some kind of software that when you connect tablet with PC, tablet will enter in download mode?
I think that warranty is voided, so i just don't want to go to a samsung service center.
The picture: https://1drv.ms/u/s!Aitd6zSfsnM-gcghBLfHxmBH1vQ5CQ
Click to expand...
Click to collapse
You forgot to unlock OEM vin dev mode indeed. The only way to get ride about it is to reinstall stock with Odin. I'm really surprised you can't natively go in download mode with hardware buttons. Have you also tried with buttons with your tab connected to an electrical plug?
You can't enter recovery mode either?
Kholargol said:
You forgot to unlock OEM vin dev mode indeed. The only way to get ride about it is to reinstall stock with Odin. I'm really surprised you can't natively go in download mode with hardware buttons. Have you also tried with buttons with your tab connected to an electrical plug?
You can't enter recovery mode either?
Click to expand...
Click to collapse
yes, i have tried many times. Those Volume buttons work in system.
Kholargol said:
You forgot to unlock OEM vin dev mode indeed. The only way to get ride about it is to reinstall stock with Odin. I'm really surprised you can't natively go in download mode with hardware buttons. Have you also tried with buttons with your tab connected to an electrical plug?
You can't enter recovery mode either?
Click to expand...
Click to collapse
I don't know why but after i tried with cmd with "fastboot reboot", i am able to use 3 buttons to enter into download mode. Thank you any way.
Good thing. I advise you to use Samfirm.exe to get the file to flash with Odin. It's depreciated but still works 100% fine.
Hello, I had the problem similar to yours. in practice I have an unlocked OEM S4 tab and Magisk 18.0 installed come on, only that my problem was that I suddenly used the device my device lost the root rights. Then I restarted and reinstalled with TWRP Magisk 18 I restarted in System and everything was ok! yesterday I started reading my message (photos you uploaded on OneDrive) How did you solve it? I have read the discussion but I do not understand how you shave the command .. I see that I can not go into download mode or recovery mode, help me I'm not a newbie so just explain to me how did you use Fastboot? Thanks again
Kholargol said:
Good thing. I advise you to use Samfirm.exe to get the file to flash with Odin. It's depreciated but still works 100% fine.
Click to expand...
Click to collapse
My tab wont go into download mode or recovery yet it makes noises but no display so i dont know if im in download mode or not also what csc to choose in samfirm below the model number please. Thank you.
jack allen said:
My tab wont go into download mode or recovery yet it makes noises but no display so i dont know if im in download mode or not also what csc to choose in samfirm below the model number please. Thank you.
Click to expand...
Click to collapse
I "quite accidentally" discovered that the physical key combo of POWER + VOL UP + VOL DOWN got me out of the "Security Error ...) state and into Download mode and I could then flash a Stock ROM using Odin...oh my...what a panic I got into after trying for hours on end to get the device into Download...Smart Switch app couldn't detect the device at all for me to run a recovery...
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
I did that to an HTC U11 once - Never got it recovered, had to toss it...
Never dared relock a bootloader since...
I had the same thing happen to me.
The only thing that worked for me is to boot recovery and wipe system. Good luck
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
i have the same problem let me know if you figure out a way around this !
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
I had this issue as well, but you better not have messed with the sensitive partitions without a backup, otherwise there's no way to repair it.
razercortex said:
For all of you having this issue, simply use the msm for your respective device by unplugging your phone, select power off, enter edl mode with cable plugged in and run the tool. I know another solution, but please PM me if this one doesn't work.
Click to expand...
Click to collapse
i cannot figure out how to run the msm tool properly it always throws an error message
KidSudo6969 said:
i cannot figure out how to run the msm tool properly it always throws an error message
Click to expand...
Click to collapse
what is the error message? Maybe you dont have the correct one.
Jhoopes517 said:
So, I soft bricked my TMO OP9P. I can still access Fastboot but can't access anything else. After leaving fastboot, when the phone is rebooting, I just get a black screen.
On plugging it in, It shows up in ADB as unauthorized, and with no prompts to authorize, I can't get any further.
Any ideas?
Click to expand...
Click to collapse
Here is the msm tool
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Jhoopes517 said:
This was fixed via MSM. But I had another issue come up where MSM doesn't work.
Click to expand...
Click to collapse
What do you mean doesnt work? What did it do?
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Aleena1217 said:
its not responding at all. no boot loop, no logo, no nothing. just a blackscreen no matter how long i charge it or hold the buttons down.
Click to expand...
Click to collapse
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Aleena1217 said:
after installing driver it recognized it in EDL mode. Im also JUST seeing that this is for the 9 and not the 9 pro. im guessing thats the issue? ii cant believe i missed that
Click to expand...
Click to collapse
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
ekin_strops said:
Yes, it's for the Pro, but the procedure is the same. A good thing is that EDL works. Now just grab the MSM Tool for your model and flash it.
Click to expand...
Click to collapse
thank you so much. msm is downloading now. while I have you, do you have a link for the 9 pro conversion files? id really like to get that xpan update finally...
ekin_strops said:
Did you try booting your phone into EDL mode? Hold down both the volume buttons, and while holding them down, plug in the USB cable (Connect with the PC). If you're on Windows, check the device manager in the control panel, and check if the PC recognized the phone (you might need to install the drivers too).
Click to expand...
Click to collapse
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Aleena1217 said:
im sorry i just realized i jumped in the middle of a different thread. This happened while trying to flash tmobile oneplus 9 pro to global firmware and after trying to enter recovery mode. Im guessing it happened because the files are for one plus 9, so im looking for the files for a 9 pro conversion but only am finding msm tool downloads for conversion instead of flashbin files.
Click to expand...
Click to collapse
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
ekin_strops said:
Before I jump to conclusions, could you explain exactly which model you have and what is your goal?
Click to expand...
Click to collapse
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Aleena1217 said:
i have the le 2127 from tmobile because i didnt know any better. i dont want to root or do anything crazy. I just want to be able to flash to global or eu firmware so i can upgrade as oneplus releases the updates and not be a year behind on tmobiles schedule. I have the sim and bootloader unlocked successfully. I started to flash to the one plus 9 firmware because i somehow missed that it did not say pro. So now my phone in unresponsive except for QDL 9008 mode. MSM tool recognizes it and begins to update it but then gets a param preload "device not image match" message in red and stops. So once i figure out how to get past that and get this set to factory, i want to properly flash it to global or eu, whichever is available, and upgrade it to the latest version.
Click to expand...
Click to collapse
Are you getting the mismatch on the global/eu MSM or are you trying to flash back to stock T-Mobile? You're getting a mismatch because you're most likely using the wrong version of a firmware (msm).
So I downloaded pixelos and wished to revert to stock miui, i was using the miflash tool and in the first few seconds my usb disconnected. Then i could not exit fastboot no matter what I pressed. I've tried to flash miui again but am getting the error "data transfer error" and "data transfer time unknown". I could really use the help. Thank you
This kind of crap happened to my Redmi K30 Pro as well. The only difference is that mine did not turn on anymore after I tried to restart it. Both Recovery Mode and Fastboot are unaccessible.
I think there's always a risk going from a custom rom back to miui, specially so when using fastboot.
If u can access EDL mode either via touch point or EDL Usb cable, do that and try flashing the MIUI again through Mi-Flash. Make sure you're using the same MiAccount and hope they will flag it as authorized, otherwise you'll be forced to take it to a service center and have the whole motherboard replaced.
You can also use QFIL but that's a unreliable tool and it always spouts out Sahara error messages.
iceman0826 said:
This kind of crap happened to my Redmi K30 Pro as well. The only difference is that mine did not turn on anymore after I tried to restart it. Both Recovery Mode and Fastboot are unaccessible.
I think there's always a risk going from a custom rom back to miui, specially so when using fastboot.
If u can access EDL mode either via touch point or EDL Usb cable, do that and try flashing the MIUI again through Mi-Flash. Make sure you're using the same MiAccount and hope they will flag it as authorized, otherwise you'll be forced to take it to a service center and have the whole motherboard replaced.
You can also use QFIL but that's a unreliable tool and it always spouts out Sahara error messages.
Click to expand...
Click to collapse
I am not familliar with EDL mode, any tutorials you know to get into that? I really appreciate it.
Google is your bestfriend. If ur going with touch point method, know that it will void the warranty as you'll have to open it and short the pins, to invoke EDL mode.
EDL cable is advisable so try that first and follow the instructions that came with the package. It's a cable with a button.
iceman0826 said:
Google is your bestfriend. If ur going with touch point method, know that it will void the warranty as you'll have to open it and short the pins, to invoke EDL mode.
EDL cable is advisable so try that first and follow the instructions that came with the package. It's a cable with a button.
Click to expand...
Click to collapse
And once im in EDL mode, do i just have to try the miflash tool again?
Also can i try get TWRP again and try boot a rom from there, could that be possible?
If u can access the recovery mode then try that first.
For EDL mode, yes you have to use MiFlash for this. Make sure you're using the same Mi Account that you've used when you unlocked the bootloader and do not remove the device from the Mi Account. This way, it will recognized it as authorized and it will flash successfully.
iceman0826 said:
If u can access the recovery mode then try that first.
For EDL mode, yes you have to use MiFlash for this. Make sure you're using the same Mi Account that you've used when you unlocked the bootloader and do not remove the device from the Mi Account. This way, it will recognized it as authorized and it will flash successfully.
Click to expand...
Click to collapse
Okay I've managed to get TWRP installed, any idea what to do from here?
I'm sure you're knowledgeable in flashing, and knows how to use google. I'm sure u also know that accessing TWRP is a good sign and u can now access fastboot or EDL via adb from there.
iceman0826 said:
I'm sure you're knowledgeable in flashing, and knows how to use google. I'm sure u also know that accessing TWRP is a good sign and u can now access fastboot or EDL via adb from there.
Click to expand...
Click to collapse
I've only flashed one custom rom so not too knowledgable, I would probably try to get a miui recovery file and transfer it to my phone and then install from twrp. I think that would work
Also i cant decrypt my data despite entering the only pin I have ever used