Related
As the title reads, I am stuck in a bootloop I guess coming from uninstalling more system apps than was probably wise.
I tried to flash via Mi Flash but I get a "can't flash a locked phone" error.
I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too).
What options do I have?
Much appreciated,
Ultimatum
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
have you tried to re-install the Driver? make sure that you only use win 64 bit for flashing, many issues occurred when you try to flash using win 32 bit
I am using Windows 10 64 bit. Moreover, I have installed ADB drivers separately (although these seem to come with the Mi Flash utility too).
I think it's intended behavior not to be able to flash via Fastboot with the bootloader locked? I was hoping to be able to restore via Mi PC Suite but it can't seem to see the phone, although the computer does and Mi Flash does too.
try using Mi PC Suite, http://en.miui.com/thread-92720-1-1.html, After Mi PC Suite is installed, make sure that your phone is in fastboot mode, connect your phone to a computer, and select the correct ROM file to flash
"I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too)."
For some reason, Mi PC Suite is not detecting the phone.
Ultimatum99 said:
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
Click to expand...
Click to collapse
Hello there,
I faced the same situation, but unfortunately in download mode, the phone is not detected in MiFlash, it detected as QHSUSB_BULK in Windows. Phone is detected while in fastboot and normal mode, but not in download mode. Do you have any idea what to do?
I expect this is a driver issue, but I can't figure out what.. I'm using Windows 64 bit, disabled driver signature enforcement, and installed all driver from MiFlash installation (there were 3 of driver notification prompt).
noersetiawan said:
Hello there,
I faced the same situation, but unfortunately in download mode, the phone is not detected in MiFlash, it detected as QHSUSB_BULK in Windows. Phone is detected while in fastboot and normal mode, but not in download mode. Do you have any idea what to do?
I expect this is a driver issue, but I can't figure out what.. I'm using Windows 64 bit, disabled driver signature enforcement, and installed all driver from MiFlash installation (there were 3 of driver notification prompt).
Click to expand...
Click to collapse
You need to update QHSUSB_BULK to the Qualcomm driver.
Device Manager > Select QHSUSB_BULK > Update Driver Software > Find manually the location of the driver, most likely: C:\Program Files (x86)\Xiaomi\MiPhone\Qualcomm\Driver
The driver should now appear as Qualcomm something, and Mi Flash should be able to see the phone.
Does this work?
Ultimatum99 said:
You need to update QHSUSB_BULK to the Qualcomm driver.
Device Manager > Select QHSUSB_BULK > Update Driver Software > Find manually the location of the driver, most likely: C:\Program Files (x86)\Xiaomi\MiPhone\Qualcomm\Driver
The driver should now appear as Qualcomm something, and Mi Flash should be able to see the phone.
Does this work?
Click to expand...
Click to collapse
Hi,
Thank you for the help. Unfortunately it doesn't work straight away, fortunately this leads me to the right direction, after I tried to point the driver to Xiaomi directory, a window dialog says the driver is 32 bit thus noninstallable for my PC, then I looked around for 64 bit driver for Qualcomm, installed it. I can finally install the driver but the phone is detected as unknown USB device, after removing it from Device Manager, restarted my PC, and tried again, it's still the same, on the third try it finally detected properly. It's working now, thank you very much.
Really weird why did MiFlash comes with noninstallable driver.
Ultimatum99 said:
As the title reads, I am stuck in a bootloop I guess coming from uninstalling more system apps than was probably wise.
I tried to flash via Mi Flash but I get a "can't flash a locked phone" error.
I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too).
What options do I have?
Much appreciated,
Ultimatum
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
Click to expand...
Click to collapse
My 3s prime is locked bootloader, developer option off, oem disable thus not able to flash as device is in bootloop.
Garu8 said:
My 3s prime is locked bootloader, developer option off, oem disable thus not able to flash as device is in bootloop.
Click to expand...
Click to collapse
you have to flash in edl mode not fastboot so google on how to take redmi 3s into edl mode then you can flash the rom in locked bootloader.in redmi 3 we use volume up and volume down and power button.press all three at the same time and it will take u to edl mode.screen becomes all black but if you plug it to ur computer and press refresh in miflash then it will show as com 10 or 20.thats for redmi 3.maybe redmi 3s has the same steps
jokerpappu said:
you have to flash in edl mode not fastboot so google on how to take redmi 3s into edl mode then you can flash the rom in locked bootloader.in redmi 3 we use volume up and volume down and power button.press all three at the same time and it will take u to edl mode.screen becomes all black but if you plug it to ur computer and press refresh in miflash then it will show as com 10 or 20.thats for redmi 3.maybe redmi 3s has the same steps
Click to expand...
Click to collapse
I have already tried to switch to edl mode using cmd with "fastboot oem edl" command but it enter bootloop. It happen because oem is locked alongwith usb debugging as I didn't unlock developer option.
Garu8 said:
I have already tried to switch to edl mode using cmd with "fastboot oem edl" command but it enter bootloop. It happen because oem is locked alongwith usb debugging as I didn't unlock developer option.
Click to expand...
Click to collapse
then you should buy a usb cable which has a button in it which forces xiaomi devices to boot into edl mode.i forgot its name but i think you can google to find it
jokerpappu said:
then you should buy a usb cable which has a button in it which forces xiaomi deveot into edl mode.i forgot its name but i think you can google to find it
Click to expand...
Click to collapse
I believe you are talking about dfc a.k.a deep flash cable. I have searched alot I couldn't find it on any e-commerce site except alibaba which doesn't ship at my place. Can yousuggest any seller or website if you ever came across selling dfc cable? Deep flash method is the only last resort for my problem other than sending phone to service centre. Could you suggest any website to make dfc cable manually?;as I have searched youtube but non of the method mentioned in it seemed liable to me.
Garu8 said:
I believe you are talking about dfc a.k.a deep flash cable. I have searched alot I couldn't find it on any e-commerce site except alibaba which doesn't ship at my place. Can yousuggest any seller or website if you ever came across selling dfc cable? Deep flash method is the only last resort for my problem other than sending phone to service centre. Could you suggest any website to make dfc cable manually?;as I have searched youtube but non of the method mentioned in it seemed liable to me.
Click to expand...
Click to collapse
i saw it on ebay also.i think that seller will ship worldwide to any country.
here is the link
http://www.ebay.com/sch/i.html?_fro...le.TRS0&_nkw=xiaomi+deep+flash+cable&_sacat=0
You don't need deep flash cable use button combo to put in edl mode. From device manager update driver for QHSUSB_BULK. \After that reboot pc with driver signature disabled, then open mi flash and phone should be recognised. Just found the thread I used to remove vendor rom.
http://en.miui.com/thread-254606-1-1.html
JUST MAKE SURE YOU DOWNLOAD THE ROM FOR YOUR DEVICE!:crying:
jazz452 said:
You don't need deep flash cable use button combo to put in edl mode. From device manager update driver for QHSUSB_BULK. \After that reboot pc with driver signature disabled, then open mi flash and phone should be recognised. Just found the thread I used to remove vendor rom.
http://en.miui.com/thread-254606-1-1.html
JUST MAKE SURE YOU DOWNLOAD THE ROM FOR YOUR DEVICE!:crying:
Click to expand...
Click to collapse
As I have already said edl mode won't work since developers option was not activated as edl requires oem activated. I had already tried all the methods.
By the way thanks to u all at xda as I have successfully flashed new rom using deep flash cable method...
Nexus 10 rooted in a bootloop
Hi folks! I'm a newbie with this stuffs so I'll do my best to explain the issue. I've recently rooted my Nexus 10 with Nexus root toolkit 2.1.9( I believe). All was fine until I turn it off and back on. Now I'm in a bootloop. I could use the Unroot+flash command but my windows 7 won't detect the device. It only detect it when my tablet is connected and turn off. In that case shows as MTP. Can anyone help me reinstalling the driver or else? Thank you
Novice12 said:
Hi folks! I'm a newbie with this stuffs so I'll do my best to explain the issue. I've recently rooted my Nexus 10 with Nexus root toolkit 2.1.9( I believe). All was fine until I turn it off and back on. Now I'm in a bootloop. I could use the Unroot+flash command but my windows 7 won't detect the device. It only detect it when my tablet is connected and turn off. In that case shows as MTP. Can anyone help me reinstalling the driver or else? Thank you
Click to expand...
Click to collapse
Hi,
This is Redmi 3 section. The correct section for your device is here. Please explain your issue there. Good luck!
Sent from my Redmi 3 using XDA Labs
Unbrick Xiaomi Redmi 3s prime with unlocked boot loader
Hi all,
I've a Xiaomi redmi 3s prime with rooted and unlocked bootloader. I tried unrooting from SuperSu and the phone is in bootloop now. I had TWRP recovery mod installed and a nandroid back up in my phone. But, I can't even enter the recovery mode now. Fast boot is working. Please help me to unbrick it without losing the data or recover the nandroid back up at least.
Thanks!!
Ultimatum99 said:
As the title reads, I am stuck in a bootloop I guess coming from uninstalling more system apps than was probably wise.
I tried to flash via Mi Flash but I get a "can't flash a locked phone" error.
I also tried to connect to Mi PC Suite on Fastboot but it doesn't recognize the phone as connected (although the PC itself does and Mi Flash did too).
What options do I have?
Much appreciated,
Ultimatum
SOLUTION:
Download latest Fastboot ROM and decompress
Download and install MiFlash
Open MiFlash
Shut down the phone
Power on with Power + Vol Up.
Download Mode
Connect phone to computer, let it install the drivers if necessary
Refresh MiFlash, phone should show up (for me, Device showed as COM 10)
Browse the ROM
Tick Flash all except data and storage
Advanced > clear nvflash_all.bat
Flash
Enjoy!
Credit goes to Robertmvp
Click to expand...
Click to collapse
look
you got bootloop and its very very different from brick
update your title
I tried to flash the developer rom from here http://forum.xda-developers.com/redmi-note-3/how-to/miui-8-6-6-236-0-1-redmi-note-3-t3404890
MIUI8 DEV Release ROM :6.11.3 fastboot version but apparently used an old miflash tool version .
While trying to flash I got the "miflash not enough storage is available to process this command" error.
Now I cant start my phone, cant go into fastboot and Miflash does not recognize the phone, when I connect to pc, the notification light blinks red like if it was in edl mode but the flash utility does not recognize the device.
Booting into fastboot mode does not work, restarting normally also does not work
Which version of MiFlash are you using now? I use 2016.08.30.0
I think you only need proper drivers installed, also install MiPcSuite and adb universal drivers (i have all this) if its blinking red, then it must be in edl mode...your computer does not recognise it...
Check this : en.miui.com/thread-235865-1-1.html
These kinds of posts remind me of what we risk modind our device. Try on another computer, there may be issues with .net framework or something.
redminote3 said:
Which version of MiFlash are you using now? I use 2016.08.30.0
I think you only need proper drivers installed, also install MiPcSuite and adb universal drivers (i have all this) if its blinking red, then it must be in edl mode...your computer does not recognise it...
Check this : en.miui.com/thread-235865-1-1.html
Click to expand...
Click to collapse
I am using the same version right now,before I used an older one when I got the error.
I think I installed all the drivers, I will try to install them again including the mipcsuite.
But should I not be able to restart or boot into fastboot mode regardless whether the phone is recognised by my pc?
Also it was recognised in the beginning but not anymore.
redminote3 said:
Which version of MiFlash are you using now? I use 2016.08.30.0
I think you only need proper drivers installed, also install MiPcSuite and adb universal drivers (i have all this) if its blinking red, then it must be in edl mode...your computer does not recognise it...
Check this : en.miui.com/thread-235865-1-1.html
Click to expand...
Click to collapse
So I installed the drivers again and my phone is recognized in device manager as Qualcomm HS-USB diagnostics 900e, I still dont see it in miflash and therefore cannot flash.
Try running edl.bat and then refresh miflash to see if its recognised as COM10
redminote3 said:
Try running edl.bat and then refresh miflash to see if its recognised as COM10
Click to expand...
Click to collapse
Should I create this file or where can I find it?
Any kind of help would be appreciated, because if nothing else works I will have to try the modified wire method.
I already opened the back cover to disconnect the battery for a while, didn't help, still cannot boot into fastboot.
If your phone is already in edl mode, what will wire method do for you?
Running edl.bat will require phone to be in fastboot mode.
Try this: half insert the usb cable, hold power+ both vol buttons and then fully insert the cable. Try this multiple times. This should force your phone into edl state if it already isn't... The use miflash to do the job.
I have a file through which u can enter edl mode using fastboot..if u Want I can share
I did the same mistake earlier and got stuck..adb couldn't recognize my device and was not able to enter edl mode...so I used fastboot mode to enter edl mode through a file provided on an XDA thread forum.xda-developers.com/android/software-hacking/guide-how-to-reboot-to-edl-fastboot-t3394292
hitesh1792 said:
I have a file through which u can enter edl mode using fastboot..if u Want I can share
Click to expand...
Click to collapse
The problem is I cant enter fastboot mode, I am apparently already in edl mode but miflash does not find the phone.
zsajak said:
The problem is I cant enter fastboot mode, I am apparently already in edl mode but miflash does not find the phone.
Click to expand...
Click to collapse
Did u update the Qualcomm driver??
hitesh1792 said:
Did u update the Qualcomm driver??
Click to expand...
Click to collapse
Yes, the device is also recognized by my pc as Qualcomm HS-USB diagnostics 900e, but not visible in Miflash, I tried several different versions
zsajak said:
Yes, the device is also recognized by my pc as Qualcomm HS-USB diagnostics 900e, but not visible in Miflash, I tried several different versions
Click to expand...
Click to collapse
R u using this MIFLASH tool??
en.miui.com/thread-281979-1-1.html
hitesh1792 said:
R u using this MIFLASH tool??
en.miui.com/thread-281979-1-1.html
Click to expand...
Click to collapse
Yes I tried this , also I tried the 201608 version
zsajak said:
Yes I tried this , also I tried the 201608 version
Click to expand...
Click to collapse
Can u give me a screenshot of what message does MIFLASH displays..
hitesh1792 said:
Can u give me a screenshot of what message does MIFLASH displays..
Click to expand...
Click to collapse
No message, its just absolutely empty , no device recognized.
zsajak said:
No message, its just absolutely empty , no device recognized.
Click to expand...
Click to collapse
What's your computer's OS? 32 bit or 64 bit?
hitesh1792 said:
What's your computer's OS? 32 bit or 64 bit?
Click to expand...
Click to collapse
64bit win 7
Is there a through way to cleanly remove all drivers including adb drivers? I hope its some kind of driver problem
I tried reinstalling the qualcomm driver in device manager but it didnt do anything.
zsajak said:
64bit win 7
Is there a through way to cleanly remove all drivers including adb drivers? I hope its some kind of driver problem
I tried reinstalling the qualcomm driver in device manager but it didnt do anything.
Click to expand...
Click to collapse
To recognize your device ur PC needs adb drivers...those get automatically installed once you connect your phone to your PC in normal mode or in fastboot mode...if you right click on my computer then click manage under device manager u will see android device under which it is written android debub interface...which means your device is recognized...
Help me guys.. My RN4 mtk 3/64 MIUI Global 8.0.3.0 unlockbootloader suddently dead.. No led, no vibrate. My pc detect as mtk usb port..but connection not stable
.. Connect-disconnect repeatly. And SPFT can't work.. Can't format, can't readback, can't flash.. Always stuck at 100% red bar and ERROR : STATUS_DA_HASH_MISMATCH for rom miui 8 china or global stable.. And ERROR : STATUS_EXCEED_NUM_MAX for rom global dev and china dev..please give me solution :crying::crying:
Thanks..
Can you get into the bootloader to use fastboot? Does that much work? If not, you may be in trouble
Also, are you positive you have the MTK driver installed correctly? I remember there being driver verification issues with Win10.
smokinjoe2122 said:
Can you get into the bootloader to use fastboot? Does that much work? If not, you may be in trouble
Also, are you positive you have the MTK driver installed correctly? I remember there being driver verification issues with Win10.
Click to expand...
Click to collapse
Can not enter fastboot or recovery mode .. I am using win 7 64bit .. And for the mtk driver I've tried to install repeatedly from various sources and in various ways but the result is the same.
arilevint said:
Help me guys.. My RN4 mtk 3/64 MIUI Global 8.0.3.0 unlockbootloader suddently dead.. No led, no vibrate. My pc detect as mtk usb port..but connection not stable
.. Connect-disconnect repeatly. And SPFT can't work.. Can't format, can't readback, can't flash.. Always stuck at 100% red bar and ERROR : STATUS_DA_HASH_MISMATCH for rom miui 8 china or global stable.. And ERROR : STATUS_EXCEED_NUM_MAX for rom global dev and china dev..please give me solution :crying::crying:
Thanks..
Click to expand...
Click to collapse
If your repeatedly getting disconnect/reconnect I would suggest you use another USB cable or USB port because that's not normal.
If not then it may be a driver/PC issue.
Sent from my Redmi Note 4 using Tapatalk
Wilderone said:
If your repeatedly getting disconnect/reconnect I would suggest you use another USB cable or USB port because that's not normal.
If not then it may be a driver issue.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Ok..I'm going to buy a new cable.
Still unresolved. I try memory test SPFT can run normally. Device manager detects as MediaTek DA vcom usb .. But if I format or flashing error message appears again .. STATUS_DA_HASH_MISMATCH.
Perhaps try downloading different firmware if you're getting a hash error?
I still think getting into fastboot is important...Since Official MIUI doesn't have a real recovery, you're better off installing TWRP and seeing if you can do something from within recovery.
arilevint said:
Still unresolved. I try memory test SPFT can run normally. Device manager detects as MediaTek DA vcom usb .. But if I format or flashing error message appears again .. STATUS_DA_HASH_MISMATCH.
Click to expand...
Click to collapse
Is your Rn4 a mtk device or snapdragon device???? Please check.
If it is mtk then u would require scatter file along with correct firmware.
And if it is a snapdragon device, u can flash most of the things through bootloader mode.
Hope it helps.
subodhverma21 said:
Is your Rn4 a mtk device or snapdragon device???? Please check.
If it is mtk then u would require scatter file along with correct firmware.
And if it is a snapdragon device, u can flash most of the things through bootloader mode.
Hope it helps.
Click to expand...
Click to collapse
Im sure my device xiaomi redmi note 4 mediatek 3/64gb with logo china mobile in back casing.
arilevint said:
Im sure my device xiaomi redmi note 4 mediatek 3/64gb with logo china mobile in back casing.
Click to expand...
Click to collapse
Working with MTK devices is bit tricky.
though you will get success, i Hope
If you are sure that your device is MTK, then ofcourse your bootloader mode will not work. So try to adopt this solution:
1. Get SPFlash Tool, the latest one. http://spflashtool.com/
2. Get MediaTek USB VCOM drivers. http://spflashtool.com/
3. Now most important Get your Original Firmware along with the Scatter file. The SPflashtool only recognizes the scatter file. So you need ROM along with scatter file.
check this link and follow the instructions http://en.miui.com/thread-370620-1-1.html
check your ROM if it is here. Only Use the correct firmware for your devices otherwise you may do a permanent damage to your device. http://en.miui.com/download-309.html#454
Hope it helps.
Hi i have the same problem, spft always give me an error, i cannot enter in fastboot or recovery, did you solve the problem?
have you flashed preloader or had you selected "Format all and Download"? If not, or maybe yes,, try to flash custom cust.img and just plug in your phone without holding vol-down button. Also make sure that you disable driver signature enforcement. Anyway it sounds scary as I reflash my fastboot firmware on SP Flash Tool ocasionally after using twrp.
---------- Post added at 06:14 PM ---------- Previous post was at 06:12 PM ----------
If it doesn't work,, have a motherboard replacement
hello i managed to flash with sp flash tool but after flashing it is not charging and couldnt be powered on. i have held the power button for more than 20 secs
jr1945 said:
hello i managed to flash with sp flash tool but after flashing it is not charging and couldnt be powered on. i have held the power button for more than 20 secs
Click to expand...
Click to collapse
go to help at care centre buddy it look like a serious problem
subodhverma21 said:
Working with MTK devices is bit tricky.
though you will get success, i Hope
If you are sure that your device is MTK, then ofcourse your bootloader mode will not work. So try to adopt this solution:
1. Get SPFlash Tool, the latest one.
2. Get MediaTek USB VCOM drivers.
3. Now most important Get your Original Firmware along with the Scatter file. The SPflashtool only recognizes the scatter file. So you need ROM along with scatter file.
check this link and follow the instructions
check your ROM if it is here. Only Use the correct firmware for your devices otherwise you may do a permanent damage to your device.
Hope it helps.
Click to expand...
Click to collapse
i stuck in (Vol -) ,( Vol - and power button )and plug in USB. red bar not appear in SP tool, why it happen? please help
chimouw said:
i stuck in (Vol -) ,( Vol - and power button )and plug in USB. red bar not appear in SP tool, why it happen? please help
Click to expand...
Click to collapse
are you able to go to VCOM mode?
you have to go to VCOM mode in the MTK device to use the SP Flash Tool.
1. Install Vcom drivers from internet.
2. Phone will get detected. Then the SP Flash Tool will Run
Hope it helps.
subodhverma21 said:
are you able to go to VCOM mode?
you have to go to VCOM mode in the MTK device to use the SP Flash Tool.
1. Install Vcom drivers from internet.
2. Phone will get detected. Then the SP Flash Tool will Run
Hope it helps.
Click to expand...
Click to collapse
I finally installed mediatek driver but it didn't give any progress, btw test point can work??
chimouw said:
I finally installed mediatek driver but it didn't give any progress, btw test point can work??
Click to expand...
Click to collapse
Do you have the scatter file?
where did you get the scatter file?
Which SPF tool are you working with?
Download the latest SPFT and then try.
hope it helps.
subodhverma21 said:
Do you have the scatter file?
where did you get the scatter file?
Which SPF tool are you working with?
Download the latest SPFT and then try.
hope it helps.
Click to expand...
Click to collapse
I has scatter file from en. Miui /a-234 with codename nikel, I used spf tool the latest version.
Otherwise, my phone can not detected in my pc, neither unknown device or Vcom statuse. How should I do again? With test point or DFC can work??
Really my phone is Deep Death, before DD I flashed with snap dragon rom, result is DD
chimouw said:
I has scatter file from en. Miui /a-234 with codename nikel, I used spf tool the latest version.
Otherwise, my phone can not detected in my pc, neither unknown device or Vcom statuse. How should I do again? With test point or DFC can work??
Really my phone is Deep Death, before DD I flashed with snap dragon rom, result is DD
Click to expand...
Click to collapse
Have patience, it should not be problem.
Is your battery removable?
If yes, take it out. Unplug usb.
Plug usb again with battery out. Press -vol to detect vcom driver.
Most important , adb driver or usb debugging mode should not be enabled. Otheewise the vcom drivers will not install.
Once vcom mode works. SPFT will work on its own.
Hope it helps.
Hello, guys.
Recently, I've tried to root a Cubot Power 4G following a guide I found online. I probably should have been more catious about it, cause now the phone is stuck on a bootloop. I tried to install a custom recovery to try and fix this, but as there was no official twrp for Cubot, I once again downloaded something that was probably shady. Thus, now the phone is stuck on bootloop, won't access recovery mode, is now turned off because battery gave out, but if I try to connect it to the pc, it will start to bootloop again. I cannot access adb, or at the least I don't know a way to, since it keeps bootlooping and I have no way to access a recovery mode(since there's no one, or at the least, if there is, it's faulty). What can I do here?
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
jwoegerbauer said:
@Giordyman
Re-flash phone's Stock ROM by means od MTK Flash Tool. You have to install the Mediatek VCOM drivers before on your Windows computer, if not done yet.
Click to expand...
Click to collapse
I did! Or so I think... The moment I connect it to the pc, it starts bootlooping and so the pc cannot actually connect there
Bootloop is a situation where you cannot get into the "normal" Android system. Take note that as soon Android logo is shown on phone's display Android kernel got successfully initialized, ADB & Fastboot are ready.
Hey, I need Some help ASAP, I am in a Big trouble. So The whole scenario is that I decided to install the Paranoid Android 11 in my Mi A3 and After Unlocking the Bootloader, I changed the Boot Slot from A to B and Flashed the Twrp file ( to the boot ) and Pressed the Power and Volume down Button, The Phone turned off and is not turning on Not Even the Fastboot Logo, Its Bricked. (Here are some additional Points Which you Should Know, 1. I checked the ports on my Computer and It was Showing Qualcomm HS-USB QDLoader 9008 So I think the phone is in EDL mode. 2. I tried to Flash Mi A3 Stock Firmware using Miflash and It was Showing Error "Cannot receive hello Packet") The Phone is my Daily Driver and If anyone can, Please help me Fix this.
Even I got the same issue after downloading the latest Android 11, then got rectified the Mobile through the nearest service center.
Globally many people experienced the same issue.
Now it is ok !
use qfile and service rom
set up in ufs mod
plug off battery and connct usb with short test point
load files 0/1/2/3/4/5 and
elprfesor said:
use qfile and service rom
set up in ufs mod
plug off battery and connct usb with short test point
load files 0/1/2/3/4/5 and
Click to expand...
Click to collapse
could you explain it more?
I also dead briked my phone after install a11 and used qfil to flash some stuff in edl mode using test points,
I recommend using the right qualcomm driver 32 or 64 bits like your OS and also reboot after install driver,
I don't recommend open the back painel bcs even u doing it right it don't close well after bcs lose stickiness,
If u can just go to a service, they can manage with this better then u.
Same here. Even opened the back cover to touch the EDL points.
Tried getting out of that mode by flashing to stock ROM using the Mi Flash Tool as I'm getting a weird error, `Input string was not in the correct format`. even when using the very same input as I've seen on a YouTube Tutorial & I had also tried it out on the very same version of Flash Tool (and still got the error)