Related
Hello guys, I'm new around here.
This happened the day before yesterday, I had RRemix 6.1 installed on my phone, all of a sudden, mid use, most of the apps stopped responding and nothing was working, so I shut the phone down. Then when I tried to turn on the phone, it wouldn't get past the RRemix loading screen. I waited for a while, then I tried getting into TWRP recovery. In that, the TWRP logo would come then it would suddenly switch to loading the RRemix.
As the RRemix wouldn't open up, I tried flashing MIUI10 global beta through the fastboot method using MiFlash Tool, the flash wouldn't complete so I flashed it manually using fastboot commands through CMD. Then the phone just switched off completely, the display doesn't show a single thing. After a while, randomly, while it was connected to my PC, the red LED started blinking and in Device Manager the device was detected as "Qualcomm HS-USB QDLoader 9008". I searched around and found that this was supposed to be EDL mode.
So, I fired up MiFlash Tool again and tried flashing MIUI10 Global Beta onto it, it returned a message that the flash was successful. The phone is supposed to automatically boot up after the flash according to Xiaomi, but my phone didn't. Now what can I do ? I tried flashing the MIUI9 Stable release too, but even that didn't work.
Thanks a lot.
thereelaman said:
Hello guys, I'm new around here.
This happened the day before yesterday, I had RRemix 6.1 installed on my phone, all of a sudden, mid use, most of the apps stopped responding and nothing was working, so I shut the phone down. Then when I tried to turn on the phone, it wouldn't get past the RRemix loading screen. I waited for a while, then I tried getting into TWRP recovery. In that, the TWRP logo would come then it would suddenly switch to loading the RRemix.
As the RRemix wouldn't open up, I tried flashing MIUI10 global beta through the fastboot method using MiFlash Tool, the flash wouldn't complete so I flashed it manually using fastboot commands through CMD. Then the phone just switched off completely, the display doesn't show a single thing. After a while, randomly, while it was connected to my PC, the red LED started blinking and in Device Manager the device was detected as "Qualcomm HS-USB QDLoader 9008". I searched around and found that this was supposed to be EDL mode.
So, I fired up MiFlash Tool again and tried flashing MIUI10 Global Beta onto it, it returned a message that the flash was successful. The phone is supposed to automatically boot up after the flash according to Xiaomi, but my phone didn't. Now what can I do ? I tried flashing the MIUI9 Stable release too, but even that didn't work.
Thanks a lot.
Click to expand...
Click to collapse
Buy a new one or wait till miui 10 release
yohen_auroville said:
Buy a new one or wait till miui 10 release
Click to expand...
Click to collapse
i.e. I should buy a new phone ?
thereelaman said:
Hello guys, I'm new around here.
This happened the day before yesterday, I had RRemix 6.1 installed on my phone, all of a sudden, mid use, most of the apps stopped responding and nothing was working, so I shut the phone down. Then when I tried to turn on the phone, it wouldn't get past the RRemix loading screen. I waited for a while, then I tried getting into TWRP recovery. In that, the TWRP logo would come then it would suddenly switch to loading the RRemix.
As the RRemix wouldn't open up, I tried flashing MIUI10 global beta through the fastboot method using MiFlash Tool, the flash wouldn't complete so I flashed it manually using fastboot commands through CMD. Then the phone just switched off completely, the display doesn't show a single thing. After a while, randomly, while it was connected to my PC, the red LED started blinking and in Device Manager the device was detected as "Qualcomm HS-USB QDLoader 9008". I searched around and found that this was supposed to be EDL mode.
So, I fired up MiFlash Tool again and tried flashing MIUI10 Global Beta onto it, it returned a message that the flash was successful. The phone is supposed to automatically boot up after the flash according to Xiaomi, but my phone didn't. Now what can I do ? I tried flashing the MIUI9 Stable release too, but even that didn't work.
Thanks a lot.
Click to expand...
Click to collapse
Try flash an older stable rom from miui and hope one boots so u can use phone or flash again to another rom. Download a few different ROMs try them all maybe one is bound to boot up
Test point Only then you can recover your phone.
Gabitozero said:
Test point Only then you can recover your phone.
Click to expand...
Click to collapse
I don't exactly understand what you mean, if I got it into EDL, what's the point of Test Point method, and I don't really understand what the Test point method does.
It will be real helpful of you to explain that to me..
Thanks.
Test point are two point in the mother board.
If you communicate the two points with a wire the phone enters in bootloader mode and you can flash the rom again.
(google test point redmi note 4 and you will get a full imaged guide)
Only for snapdragon version.
I did it succesfully one year ago.
magnus48 said:
Test point are two point in the mother board.
If you communicate the two points with a wire the phone enters in bootloader mode and you can flash the rom again.
(google test point redmi note 4 and you will get a full imaged guide)
Only for snapdragon version.
I did it succesfully one year ago.
Click to expand...
Click to collapse
I did try that, but my phone already shows up as the "Qualcomm HS-USB QDLoader 9008" so it didn't really make any difference, the flashing was successful and the phone still didn't start.. Is there anything else that I can try ?
Install miui 9 with flashtool and it should be fine,
https://sourceforge.net/projects/firmware-global-mido/
Tell me if it worked :good:
BK said:
Install miui 9 with flashtool and it should be fine,
https://sourceforge.net/projects/firmware-global-mido/
Tell me if it worked :good:
Click to expand...
Click to collapse
When I downloaded that, WinRar showed a message that the file was corrupt.
And how do I flash this Firmware using Mi Flash Tool?
Thanks.
Try
Did you try to flesh recovery through ADB?
Alfonso13 said:
Did you try to flesh recovery through ADB?
Click to expand...
Click to collapse
My ADB was turned off, and my device won't turn on, how am I supposed to try that?
Thanks..
Do you try this?
https://forum.xda-developers.com/redmi-note-4/how-to/guide-how-to-edl-flashing-redmi-note-4-t3795831
Alfonso13 said:
https://forum.xda-developers.com/redmi-note-4/how-to/guide-how-to-edl-flashing-redmi-note-4-t3795831
Click to expand...
Click to collapse
That method only works if I could access fastboot, sadly I can't..
same issue i got some days before i removed the back case and remove the battery connection and flashed miui 10 beta without battery connect from mi flash tool i got my same issue but the benefit is fastboot file is recovered after that i flashed orange fox r7 then format all data then install miui10 from orange fox after that phone is booted successfully but persist issue is there (cant receive calls, notification bar not available) but after that i download the miui10 from miui updater (setting-About Phone-System Update-Download Updates) after download the rom flashed from updater reboot the device and success! try this method may be it will works for you also
wont turn on
hey, did u resolve ur problem here? i have redmi 4 prime and stuck in edl mode now.
and samae as your problem here, always success but my phone wont to turn on again, i try every solution in this forum and other. the result still same til now, 3 days already and still same. please help me, before my mom kill me cause this phone wont turn on.
sorry for bad english
hi everyone, so i am having an issue with my xiaomi mi a1. I rooted the device in order to install the pixel 3 g-cam, yesterday i tried to unroote it and to lock its bootloader but as i was doing this, the system was destroyed. i flashed the device and got it working, the my GF tried unrooting it from magisk app and i dont kow what happened it appeared th co command symbol. I flashed it again and everything was normal util the mi screen appeared and then the android one logo show. the next thing that happended was the advise of corruption, the mi screen and android logo. again and again so on so forth. i've flashed the device, several times and nothing changes. i've locked and unlocked the bootloader, and nothing. I even tried stock recovery options but resuts in the same. what esle can I
do ?
I may be late but something like this happened to me as well.
I got my phone bricked and because I was in school the phone was stuck on booting screen for a long time. When I got back the phone's battery was dead. I put it on the charger and it wasn't doing anything, all of a sudden it starts to blink red light (sign it's in edl mode) I don't quite remember if I got into the fastboot and then flashed miui 9 beta with a pc through the miui application idk what it's called and after the installation was over it worked. It could be a problem with not being in the right mode (as I said previously it's either edl or fastboot) or it could be because of a problem with that miui version
Maybe Anti-Roll back problem?
While trying to set up a new boot animation, I came across an error which prevented my phone form booting up into the OS and instead showed me the Fastboot screen every time. I tried reflashing twrp, as well as flashing another boot animation into it. While reflashing TWRP for the third time (I didn't really know what to do so I just hoped it would work eventually), it seems like it corrupted some of my phone data, meaning preloader and I believe some other stuff. The phone now won't boot at all, and also isn't getting recognized by SPFlashTool. While plugging it into my PC I can still hear the "connected" and "disconnected" sound though.
Any ideas on what I could do?
I know its kinda late but
Have you tried using adb or fastboot and check if your device is recognized with the adb devices command?
noah_bfn said:
Have you tried using adb or fastboot and check if your device is recognized with the adb devices command?
Click to expand...
Click to collapse
I don't know how to do it But I'm having the same problem the screen is black , can you guys help me ?
Your phone sounds like it is soft bricked.
emersonsamuel said:
I don't know how to do it But I'm having the same problem the screen is black , can you guys help me ?
Click to expand...
Click to collapse
Your phone sounds as though it is soft bricked. It can be brought back to life.
Follow here to un-brick your device:
https://forum.xda-developers.com/android/general/ulefone-power-5-twrp-root-project-treble-t3943714
Loyal_Guardian said:
While trying to set up a new boot animation, I came across an error which prevented my phone form booting up into the OS and instead showed me the Fastboot screen every time. I tried reflashing twrp, as well as flashing another boot animation into it. While reflashing TWRP for the third time (I didn't really know what to do so I just hoped it would work eventually), it seems like it corrupted some of my phone data, meaning preloader and I believe some other stuff. The phone now won't boot at all, and also isn't getting recognized by SPFlashTool. While plugging it into my PC I can still hear the "connected" and "disconnected" sound though.
Any ideas on what I could do?
Click to expand...
Click to collapse
Just use the spflashtool. Try multiple times and try my updated guide. Make sure you installed the drivers properly AND USE A GOOD CABLE. I had some hard times flashing with spflashtool, but it was just the cable.
Guys, I installed the ROM Pixel Experience. This one:
https://forum.xda-developers.com/mi-pad-4/development/rom-pixelexperience-t3878616
I am having a huge issue with this rom. I installed it and it works fine, however, since it doesn't support USB, I decided to install the MIUI stock rom back. Well, in order to do that, you have to have the device in FASTBOOT mode.
When I go to the prompt and type fastboot devices, I get a result, showing that my computer can detect the device.
However, every time I am in FASTBOOT mode, after 30 seconds (exactly!) it reboots. So, I am afraid to start flashing it and then the device reboots and my installation gets corrupted.
Any ideas on how to solve this? I just need the FASTBOOT mode to last as long as necessary for me to install the older room back.
Can you explain what you mean by "Doesnt support USB"?
And the fastboot issue is definitely weird. That should not be happening. Does this happen when the device is plugged in only? What happens if the device is not plugged to the computer?
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
UnequalB said:
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
Click to expand...
Click to collapse
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
UnequalB said:
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Click to expand...
Click to collapse
You can flash the TWRP image through fastboot and then boot to it through commands.
UnequalB said:
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
Click to expand...
Click to collapse
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
SubwayChamp said:
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
You can flash the TWRP image through fastboot and then boot to it through commands.
Click to expand...
Click to collapse
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
SubwayChamp said:
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Click to expand...
Click to collapse
Weirdly enough the error i got was not listed here..
SubwayChamp said:
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
Click to expand...
Click to collapse
This method doesn't work either since the phone won't stay off for more than 7 seconds.
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
UnequalB said:
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
Click to expand...
Click to collapse
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
UnequalB said:
Weirdly enough the error i got was not listed here..
This method doesn't work either since the phone won't stay off for more than 7 seconds.
Click to expand...
Click to collapse
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
UnequalB said:
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
Click to expand...
Click to collapse
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
SubwayChamp said:
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
Click to expand...
Click to collapse
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
UnequalB said:
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
Click to expand...
Click to collapse
Well, if you interrupted the process, that's not good at all. The only you can do is keeping trying it, if your motherboard was not damaged.
hi guys i am DELTIERO from the Philippines did you allready solve the problem?
If not yet done message me on my facebook page https://www.facebook.com/del.villalobos.1/
and i will help you im here veltech san carlos negross occidental phil
Help please! I flashed a gapps zip file using flashify on my infinix smart 5 x657 (Running on lineageos gsi android 12) then the phone just went off. and it not turning on. but it shows the charging indicator light when i connect it to power.
I've tried disconnecting the battery still nothing
what possible solution is there for this?
Hi everyone into this post thread.
We all know that converting chines ace 2 to oxygen os has some issues. We are trying our best to fix such issues, therefore trying different techniques. I had the same issue too, i read one post that flashing ocdt.img of 11R ll fix the issue, therefore, i took step to do it. After flashing 2487 ocdt.img, i restarted bootloader to normal. Phone booted, but still gets black, flicking and then goes black. I tried to restart it with keys, and phone wont detected by pc, even the bootloader was unlocked and usb debugging was enabled too. I tried enough to start in fastboot mode. But nothing, then i forcely start into EDL mode, and it deteceted. I purchased official authentication key to flash it back to coloros 13. The official tool failed to flash with error that image and product code mismatched and i loss money. Now dont know if i purchase a other authentication or wait for the developers to figure out issue.i have a complete flash tool logs, which is very useful for the developer.
Because in the stock image, they have made tachtis to keep users afftected and pay them to bring the devices back.
Pro opinion and fix is needed for everyone affected by this.
you need to flash china version (Ace2) ocdt.img again in your phone
make sure you have unlocked bootloader ( i know you have black screen). then go to fastboot and flash this file.
download file
power off ...
power on +( vol - )
connect cable
then in cmd write
fastboot flash ocdt ocdt.img
you have not orher way .. only this way can work 100%.
in OFP we have not OCDT image . so do not waste your time and money
I had tried enough to boot into fastboot, but phone dont boot, and dont know even this is booting or not due to black screen, i only know theat attaching cable vibrate the phone but it wont detected. Tried combination keys to boot i to bootloader, but no luck. I keep phone as it is to see if battery get drain and ensure that its power off and will try afternoon.
Thanks forsharing stock ocdt for this model.i would request you to kindly rename the file to this specific model, so people know about it. The flashing way is a same.
you need to keep all 3keys togather...
after 15sec it will go to EDL mode.. connect cable
after that ..
keep power + (vol- ).. after 15 sec it will go to fastboot
I face the same issue, I did wrong that FLASHING 11 (not 11 R) OCDT.IMG, The after-sales staff were unable to restore my phone, so they directly gave me a new one.