Hello!
I had recently gotten a Xiaomi Redmi Note 6 Pro brand new, and its been working fine for a while, but recently I ran into an issue: Namely, it often refuses to turn the screen on. The phone still makes sounds, it can receive calls, hell, it can even play music with no issue whatsoever, other than the fact that the screen itself appears dead. Once in a while the display turns on, and it works perfectly fine for as long as the screen is on, if I turn off automatic sleep, it can just run indefinitely like it usually would. When turning the phone off and back on, there are no boot animations, just a blank screen (sometimes they do appear, however rarely and I haven't noticed a pattern as to when they actually work as intended).
I figured it was an issue with MIUI 11, specifically 11.0.2.0, so I decided to flash a custom ROM. When attempting to enter fastboot mode, I am greeted by a blank screen, identical to the one that is present while booting up, but ADB recognizes the device just fine and I managed to unlock the bootloader despite no visual feedback from the device itself (I did manage to load into a fastboot mode with the Soviet android logo thing, but that was once, and it would revert back to being blank after 10 seconds). It had done a factory reset, and the problem persisted, it took me a good 5 minutes of spamming the power button for the screen to come back on, and the issue wasn't solved. I flashed official TWRP recovery on the unlocked device, and the ADB console reported the flashing as successful, however I have no way of accessing the bootloader or the recovery. (Not even the stock recovery would work, i tried that before I even touched the bootloader, it would just boot to system with a blank screen, and the phone would remain on, however largely unusable).
Now, I am a complete noob for these things, this is my first thread here, and I have no idea what could be causing the issue. Would flashing an older MIUI 10 stock ROM via MiFlash fix the issue? Or is this some sort of a hardware problem, although it doesn't seem that way as the phone was never dropped or exposed to the elements. I tried leaving it to completely discharge and then fully recharge, however that did precisely nothing. If you could look into this issue and help me find a solution, it would be greatly appreciated!
Thanks in advance!
Hey!
I think you should flash stock ROM from the Flash tool selecting clean_all_and_flash from fastboot mode
Nitin Rai said:
I think you should flash stock ROM from the Flash tool selecting clean_all_and_flash from fastboot mode
Click to expand...
Click to collapse
Hey, thanks a lot for replying!
That's what I thought I'd have to do, but I have a question: should I flash the MIUI 10 ROM or 11? Would downgrading it like that cause any issues? The only MIUI 11 ROM available on Xiaomi site is the OTA update that caused the issue. Also, in the meantime I managed to get into proper fastboot with ADB commands and flashed an AOSP extended Android 10 ROM, the issue is still there but I can now consistently get into TWRP either by an ADB terminal or by rebooting into recovery directly from the ROM with the power menu. I had downloaded an MIUI 10 recovery ROM from the Mi Community forums, can I flash that through TWRP or would it be safer to use MiFlash to flash the fastboot ROM? Do I have to flash the stock recovery before using the tool or will it just work with the TWRP already present on the device?
TacticalDisadvantage said:
Hey, thanks a lot for replying!
That's what I thought I'd have to do, but I have a question: should I flash the MIUI 10 ROM or 11? Would downgrading it like that cause any issues? The only MIUI 11 ROM available on Xiaomi site is the OTA update that caused the issue. Also, in the meantime I managed to get into proper fastboot with ADB commands and flashed an AOSP extended Android 10 ROM, the issue is still there but I can now consistently get into TWRP either by an ADB terminal or by rebooting into recovery directly from the ROM with the power menu. I had downloaded an MIUI 10 recovery ROM from the Mi Community forums, can I flash that through TWRP or would it be safer to use MiFlash to flash the fastboot ROM? Do I have to flash the stock recovery before using the tool or will it just work with the TWRP already present on the device?
Click to expand...
Click to collapse
No, I had downgraded from 11 before when I didn't had the miui 11 rom.zip I had miui 10 as backup. There is a thread for that anti rollback thing you can see that for more information. I would recommended you to go with the latest one if you are going to download or just flash the old one if you already have it
Here is the link for the anti rollback: https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
Related
Hello all,
2 days ago when on vacation i decided to temper around with my OnePlus one that i recently bought (have bought the Chinese version but it was already rooted and had cyanoged mod on it)
All was fine until i decided to flash Paranoid Android and i posted a question here, about how to bypass the always apearing CyanogenMod Simple Recovery tool.
After trying what everyone suggested and not getting result i had 1 last thing that someone suggested:
http://forum.xda-developers.com/showthread.php?p=54717885
If you still have not fixed this issue, for some reason when I was flashing my recovery it would NOT work for the life of me until I changed the name of the custom recovery file to 'recovery.img'. Everytime I flash (for example) openrecovery-twrp-blah-bacon.img it would say success, but it kept rebooting into CM fastboot mode.
Click to expand...
Click to collapse
I misunderstood and i renamed the .zip file from paranoid sources into recovery.img and flash (Kernel) it via some app from play store, i thin it was TRWL
Now my phone is stuck into loading faze and the only thing i can do is enter Fastboot mode.
I tried to do a:
fastboot erase cache
But it did not work, its still stuck in loading and will not do anything.
Could you help me out ? I have a really bad feeling i just lost my phone due to hurrying and not having a pc around to read more.
You can try to fastboot flash recovery(original or proper one that works) but I don't know the exact commands.
In the first case where your recovery would not switch from CM to TWRP/CWR was because you had "Update CM Recovery" enabled in Developer Options. If you ticked that off, then it would have replaced CM Recovery. Its confusing yeah.
So wait... you renamed the .zip to a .img? Thats not good. But at least you can enter fastboot mode so thats at least something. Is your bootloader still unlocked? Are you able to boot into recovery mode? Try fastboot boot <name-of-recovery-for-twrp>.img and see if you can get into recovery.
If you can then perform a wipe and then enable adb sideload within TWRP and then type,
adb sideload <name-of-zip>.zip and then after its done sideloading, reboot
Thanks for the answer.
I managed last night out of 10 flash resets to get the Custom Recovery Tool to booth up.
I was about to give up when i saw it boot and i immediately flashed the CM .zip i had on the phone from last time.
I even managed to get Paranoid android to flash and im very happy.
Thanks for the help
vidockq said:
Thanks for the answer.
I managed last night out of 10 flash resets to get the Custom Recovery Tool to booth up.
I was about to give up when i saw it boot and i immediately flashed the CM .zip i had on the phone from last time.
I even managed to get Paranoid android to flash and im very happy.
Thanks for the help
Click to expand...
Click to collapse
I'd appreciate it if we helped give us a thanks.
Sent from my One using Tapatalk
So a while ago I moved from CM11s to CM12. However, even though I opted not to install CM Recovery it did anyway -.-, thus now I am unable to flash over it with twrp no matter how much I flash it. I have tried flashing it and using a tool from the OPO Forums. Can anybody help me? I need to get Oxygen OS since CM12 has changed my battery life for the worse and has even dropped my calling quality.
Mauricio2015 said:
So a while ago I moved from CM11s to CM12. However, even though I opted not to install CM Recovery it did anyway -.-, thus now I am unable to flash over it with twrp no matter how much I flash it. I have tried flashing it and using a tool from the OPO Forums. Can anybody help me? I need to get Oxygen OS since CM12 has changed my battery life for the worse and has even dropped my calling quality.
Click to expand...
Click to collapse
Please follow Guide #2 of http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Flash TWRP version 2.8.6.0
After the command fastboot flash recovery.... Dont run the next command disconnect the phone and put it off. Press power and volume down and you will go into twrp
Sent from my A0001 using Tapatalk
I had the same problem and I tried to do various sequences of powering of and go in recovery mode (how all tutorial said) and nothing happens. After I used a Toolkit developed by WugFresh (if I remember correctly), you must only click "Recovery" and it'll install automatically the last TWRP for OPO (or you can choose one).
did you turn off "Update Cyanogen recovery" in developers options?
I have been running with Nolimit ROM since early on. On Sunday I decided to try Franken. All seemed to go well with the flash but the phone would boot into the red screen. I shut it off and it refused to turn back on. I let it charge overnight and tried to turn it on the next morning. Nada. I did notice that it was showing a device under ports. After doing some searching, I found the tool that OnePlus uses to recover from the hard brick. Installed using the tool and it completed successfully. Upon reboot it would just hang at the initial splash screen. Doing more research I found the Hydrogen OS recovery and tried that. Again, I see the H2OS splash screen but it never boots. I can get into Fastboot and Recovery and have tried clearing everything. Before I go back to the Oxygen OS, is there anything else I can do or is it RMA time?
BTW, the bootloader is now locked, a side effect from using the OnePlus recovery tool.
I almost forgot... because the OS won't boot, It won't allow OEM unlock. Trying to unlock the bootloader gives a failed for remote access.
Thanks in advance.
You can't boot locked with a non-stock recovery. The bootloader won't allow it.
Maybe try running the unbrick tool again. Sorry, if you can get to recovery, you don't need the unbrick tool. You should be able to adb push the full OS to your phone and flash it in recovery.
The stock recovery does not provide a way to flash. At least I don't see anything
Thread closed as OP request.
Have some experience in flashing Rom's in my time but tried to flash Carbon Rom on my 6 yesterday and got myself into a pickle.
Unlocked and installed TWRP Blue Spark and Root using the Toolkit.
When I was back in Twrp I installed the Rom and TWRP again and rebooted.
That's where the problem started. When it rebooted into TWRP I could not find where the GAPPS was. The directory structed seemed very strange. SDCARD was there but nothing in it. Could not find the user directory at all.
Carbon would not come out of bootloop.
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Only the MSM unbrick tool helped me out.
Can someone see what I did wrong here in not being able to find the gapps?
Thanks
K
divvykev said:
Have some experience in flashing Rom's in my time but tried to flash Carbon Rom on my 6 yesterday and got myself into a pickle.
Unlocked and installed TWRP Blue Spark and Root using the Toolkit.
When I was back in Twrp I installed the Rom and TWRP again and rebooted.
That's where the problem started. When it rebooted into TWRP I could not find where the GAPPS was. The directory structed seemed very strange. SDCARD was there but nothing in it. Could not find the user directory at all.
Carbon would not come out of bootloop.
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Only the MSM unbrick tool helped me out.
Can someone see what I did wrong here in not being able to find the gapps?
Thanks
K
Click to expand...
Click to collapse
Likely the phone was encrypted
divvykev said:
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Click to expand...
Click to collapse
For me this happened a few times, including when I tried to 'fastboot boot' a wrong image or some latest bluespask Twrps. This is the state when the the phone has hung trying to execute something. The remedy is to hold the power button pressed for something like 10 seconds and the phone will switch off (this is a hardware feature so shlould not fail). After that I go to fastboot normally - press volUp+Power for a few seconds till the fastboot message. Also, make sure that you are not charging, as this seems to have prevented me going to fastboot once.
My Poco X3 Pro was running in Pixel experience plus custom ROM. My pixel experience recovery was gone. so i installed TWRP recovery. but my phone got stuck in bootloop while installing magisk via TWRP then I tried to flash MIUI 14 fastboot rom using mi flash tool but failed again and again. I also tried to flash directly using platform tools. but it doesn't work. after then I flashed Pixel experience recovery via fastboot and then installed Pixel experience ROM this time my phone started. but when I power off the device and tried to on it again it stuck in bootloop. then I again installed Pixel experience ROM and turned my phone on. but I'm afraid that if I turn off my phone will again stuck in the bootloop. how can I fix this?
Shahriar566 said:
My Poco X3 Pro was running in Pixel experience plus custom ROM. My pixel experience recovery was gone. so i installed TWRP recovery. but my phone got stuck in bootloop while installing magisk via TWRP then I tried to flash MIUI 14 fastboot rom using mi flash tool but failed again and again. I also tried to flash directly using platform tools. but it doesn't work. after then I flashed Pixel experience recovery via fastboot and then installed Pixel experience ROM this time my phone started. but when I power off the device and tried to on it again it stuck in bootloop. then I again installed Pixel experience ROM and turned my phone on. but I'm afraid that if I turn off my phone will again stuck in the bootloop. how can I fix this?
Click to expand...
Click to collapse
Pixel with magisk and modules?
No I was just installing magisk via TWRP
try installing magisk via image patching, works for me everytime. Magisk creator himself warn against using TWRP to flash magisk.zip
I was asking how to fix bootloop. My device is on but if I power off it will go to bootloop again then I will have to flash Pixel experience again. My problem is bootloop not installing magisk
Shahriar566 said:
I was asking how to fix bootloop. My device is on but if I power off it will go to bootloop again then I will have to flash Pixel experience again. My problem is bootloop not installing magisk
Click to expand...
Click to collapse
Tried flash official MIUI recovery ROM with TWRP?
Tried official MIUI fastboot rom not recovery
Shahriar566 said:
Tried official MIUI fastboot rom not recovery
Click to expand...
Click to collapse
Put the fastboot ROM in C drive directly, then go into the folder, find the "flash_all.bat" to flash it under fastboot mode.
Don't use Mi-Flash.
Can try the recovery flashing method with TWRP.
Check if you still got mobile SIM card working, with the original intact IMEI.
I tried "flash_all.bat" but after clicking it runs for 1 sec then disappear
Shahriar566 said:
I tried "flash_all.bat" but after clicking it runs for 1 sec then disappear
Click to expand...
Click to collapse
Rename the folder name shorter, like "ROM."
Phone needs to be in Fastboot mode, before running that flash_all.bat.
There could be some issue connecting your phone with the PC. Could be driver issue, permission issue, AMD CPU issue and/or other reasons.
Try TWRP to flash the recovery ROM would be easier.
Remember to "Format data" in TWRP.
Yeah I know the rules . I did it several times with no issue . And I have all the drivers installed in the PC.
Actually I'm afraid of power off the phone cuz if I power off it will go to the bootloop again then I again have flash pixel experience.
I just want to know does this ever happen that my phone is totally ok and if I power off it will go to bootloop?
Shahriar566 said:
Yeah I know the rules . I did it several times with no issue . And I have all the drivers installed in the PC.
Actually I'm afraid of power off the phone cuz if I power off it will go to the bootloop again then I again have flash pixel experience.
I just want to know does this ever happen that my phone is totally ok and if I power off it will go to bootloop?
Click to expand...
Click to collapse
This had happened to me rarely that the phone failed to start, stuck on the booting logo and self-boot again, then it booted correctly on the 2nd boot.
Don't know if your phone is totally ok or not, since there are cases that had the CPU ball issues. To make sure, it's better to find Xiaomi/Redmi/Poco official repair center and or customer service.
Even if the phone is out of warranty, could still ask for a phone hardware checkup, with some fee needed.
Thanks for the advice
pl1992aw said:
This had happened to me rarely that the phone failed to start, stuck on the booting logo and self-boot again, then it booted correctly on the 2nd boot.
Don't know if your phone is totally ok or not, since there are cases that had the CPU ball issues. To make sure, it's better to find Xiaomi/Redmi/Poco official repair center and or customer service.
Even if the phone is out of warranty, could still ask for a phone hardware checkup, with some fee needed.
Click to expand...
Click to collapse
Actually today I rebooted my device and it went to bootloop but after showing it's boot logo 3 or 4 times it started.
What do you think about it?
Shahriar566 said:
Actually today I rebooted my device and it went to bootloop but after showing it's boot logo 3 or 4 times it started.
What do you think about it?
Click to expand...
Click to collapse
Unknown reason. Don't know if it's ROM issue or hardware issue.
Can try downgrade to old firmware versions.
Can also try older ROM versions.