My oneplus 6 after the latest android 11 update recently crashed it reboots automatically without entering to the OS and shows QUALCOMM DumpCrash Mode there are still some data i didn't backup yet. is there any way to back up my data
-usb debugging not turned on
Did you ever manage to boot after applying the update? Or did it go straight into crash dump mode?
agent_07 said:
My oneplus 6 after the latest android 11 update recently crashed it reboots automatically without entering to the OS and shows QUALCOMM DumpCrash Mode there are still some data i didn't backup yet. is there any way to back up my data
-usb debugging not turned on
Click to expand...
Click to collapse
Flash stock recovery first from Fastboot . And do not wipe anything. Just reinstall OOS and boot. That should help.
[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates
As OnePlus doesn't always provide download links for all of for their Oxygen OS ROMs & OTA update zips, we mirrored them on AndroidFileHost and put the links in one post so that they're easy to find. This is not a support thread for issues you...
forum.xda-developers.com
facing the same issue yesterday updated to android 11 , after boot went into crash dump mode , tried n number of msm tools . not able to boot it up, i can boot to fastboot mode though
MoresM said:
Did you ever manage to boot after applying the update? Or did it go straight into crash dump mode?
Click to expand...
Click to collapse
yes after update it was fine for a week
MITHUN7888 said:
facing the same issue yesterday updated to android 11 , after boot went into crash dump mode , tried n number of msm tools . not able to boot it up, i can boot to fastboot mode though
Click to expand...
Click to collapse
if you found any was pls inform me
MITHUN7888 said:
facing the same issue yesterday updated to android 11 , after boot went into crash dump mode , tried n number of msm tools . not able to boot it up, i can boot to fastboot mode though
Click to expand...
Click to collapse
If you flash old TWRP on Android 11 it will go to Crash Dump Mode. Suggest doing a clean install of Android 11 or use Nebrassy TWRP and reinstall OOS11. Other TWRP's have already been repacked to latest version to carter Android 11.
agent_07 said:
if you found any was pls inform me
Click to expand...
Click to collapse
i tried nearly 10-15 msm tools all were success but when booted up same message " Qualcomm crash dump mode" the thing is my bootloader was locked . i couldn't flash twrp or flash fastboot rom's to revive my phone...gave my device to oneplus authorized service center they said i need to get my motherboard replaced which costs 24,050 for 256gb variant.. currently i have asked them to replace the motherboard , as motherboard for my variant was not available i need to wait 10 more days to get it fixed .
UPDATE: if u have ur bootloader unlocked search for how to get out of qualcomm crash dump mode using fastboot roms.
if not look out for a local mobile repair center which does chip level repairs and ask them to reball ur phone ram and cpu, theres a 50/50 chance ur device might boot up.
mm_rajesh said:
If you flash old TWRP on Android 11 it will go to Crash Dump Mode. Suggest doing a clean install of Android 11 or use Nebrassy TWRP and reinstall OOS11. Other TWRP's have already been repacked to latest version to carter Android 11.
Click to expand...
Click to collapse
my device bootloader was locked , had no twrp installed , after updating to os11 directly went into crash dump mode .
MITHUN7888 said:
my device bootloader was locked , had no twrp installed , after updating to os11 directly went into crash dump mode .
Click to expand...
Click to collapse
I don't know who is that Mahaaan who said it's a Motherboard fault. Crash Dump Mode is an error while loading with the Firmware. This can be fixed with MSM tools. Try this step if you cannot fix with MSM tool.
Safe Mode Procedure :
Hold the Power Button Until Android Starts to Boot Up.
As Soon as Android Starts Booting Up, Let Go of the Power Button.
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons.
Continue Holding Both Volume Buttons Until Android is Fully Booted.
If successful, backup your phone, and do a full factory Erase All Data reset of Android.
See if that helps.
like many even i too ugraged my op6 to oo11.1.1.1, rooted was running well for a week till i encountred face crash dump mode error
Stupid thing i did was instead of flashing fastboot oos 10.3.8 i tried to flash msm 10.3.8 which didnt solve crash dum and also locked my BL.
now nonof the msm could solve crash dump nor we can unlock BL bz we cant toggle OEM in Dev option,
i discussed with @L0ND0NB0Y regarding this, his suggestion would be to take a backup of oos10.3.8 config partation of a working rom, then use edl to flash it on affected op6, by that way we can unlock bootloader and flash fastboot rom.
we need to fide a working op6 and back config which @L0ND0NB0Y can guide us. if it works he ll creat a post to solve crashbump and BL locked issue.
if this wont work, we may need to wait for msm oos11 file.
update : managed to solve crash dump by flashing msm international 5.1.5 but ended up getting black screen with white notification light, if my op6 had BL unlocked all i had to do is to boot stock/twrp recovery and factory wipe.
How to resolve the issue . I got the same issue 1 week after SW upgrade . Nothing is fixing the issue
Jagadish-ravi said:
update : managed to solve crash dump by flashing msm international 5.1.5 but ended up getting black screen with white notification light, if my op6 had BL unlocked all i had to do is to boot stock/twrp recovery and factory wipe.
Click to expand...
Click to collapse
exactly describes what I have encountered the last few days. MSMDownloadTool works fine for 5.1.5, 5.1.11, 9.0.8, 10.3.0 and 10.3.8 (10.3.0 and 10.3.8 with new driver, ends in crash dump where I startet). Currently no solution in sight?
I have the strong feeling this error is correlated with the update to android 11. Going back to a previous recovery.img might initiate the qualcomm crashdump mode error on boot.
Seems to be worth a try to restore android 11 via MSMDownloadTool. Did not find a file for that. Anyone?
Another way out of the horror seems to be getting get unlock ability to 1.
https://forum.xda-developers.com/t/...stuck-in-fastboot-mode.4135563/#post-83153239
Last case is to modify the devcfg binary and flip the lock bit and reflash through EDL
Click to expand...
Click to collapse
I've got no idea on how to do that. Anyone?
I've contacted OP support. They answered i should send the phone in for repair.
Currently I am issuing a repair order.
My oneplus went to crashdump mode on Oct 21st... Really shocked to see many users reporting this issue.. Tried to revive it using msm tool , but ended up with crashdump mode even after successful flashing
I also got the same issue , the funny thing is i was still on android 10 , i havent even updated to android 11 .
cpr437 said:
I also got the same issue , the funny thing is i was still on android 10 , i havent even updated to android 11 .
Click to expand...
Click to collapse
That is some terrible news. I thought I'd be able to keep safe from this nonsense by staying on 10.
even in bootloader unlocked state its same
I brought op6 motherboard which had OOS 11 running.
I tried to downgrade to oos10 via fast boot, gave crash dump.
flashing other versions fastboot rom gave same error again n again
can't boot twrp, stock recovery non works,
flashing recovery stock or twrp gave "no such partation error"
next I would try reballing ram my old MB try n see if it works.
or should wait for OOS11 MSM flash file.
Update: OnePlus charges 307,67€ for the repair of their own fault. Game over for the phone and OnePlus. We will both change the manufacturer.
cpr437 said:
I also got the same issue , the funny thing is i was still on android 10 , i havent even updated to android 11 .
Click to expand...
Click to collapse
Same here bro.. My phone was on stock android 10...
Related
Project Spectrum for F1 is released on the official oppo forum. This is a official rom based on Android M AOSP. It Does include some color os features:-
1. Screen-off Gestures:
Project Spectrum now supports double tap to wake up/turn off the screen, draw a circle to open the camera app and custom a gesture to open an application.
This feature is turned off by default, to use it please enable it in Settings -> Accessibility -> Screen-off gestures
After you've added a custom gesture to delete or modify it please swipe the item left
2. ColorOS Camera
The Camera app ported from ColorOS is supporting the following plugins: Beautify, Filters, Panorama, HDR, GIF, Double exposure and Expert Mode
3. ColorOS Photos
The Photos app is a simplified version from ColorOS with key features needed to work properly with the Camera App
4. Beautiful Wallpapers
We've carefully selected some beautiful wallpapers from ColorOS as preset wallpapers for you
5. OTA package support
For future Project Spectrum versions OTA package will be available along with the full wipe package.
This is still in Beta. F1 Project Spectrum V1.0i Beta released now. Please follow the below link for download and instruction:-
http://community.oppo.com/en/forum.php?mod=viewthread&tid=46517&extra=
For any update and all oppo f1 official downloads follow this link:- http://community.oppo.com/en/forum.php?mod=oppo_category&fid=301
Project spectrum is a pure AOSP and it is safe to use as a daily driver but I am still waiting for CM13.
There is plenty of action here
https://github.com/CyanogenMod/android_device_oppo_f1f
Hope it will be released soon
Project Spectrum ended up bootlooping on my wife's F1. It also seems to have problems with Google Play services.
I'd just exercise a bit of caution if you're going to use this as a daily driver based on my experience.
Also has SD card detections issues, no matr how many tyms reinserted it stil wont detect
UPDATE: i had dis issue last month so i reverted back to color os , but todiah i again instaled spectrum and the SD card bug is gone, sd works fine now
mikeysteele said:
Project Spectrum ended up bootlooping on my wife's F1. It also seems to have problems with Google Play services.
I'd just exercise a bit of caution if you're going to use this as a daily driver based on my experience.
Click to expand...
Click to collapse
Can I ask how you fixed the boot loop issue? I picked up an F1 on Thursday from Optus and installed Spectrum, decided to return to ColorOS this morning, so followed instructions on Oppo website and downloaded the file etc. then when the phone attempted to install ColorOS, it started boot looping and the black screen where it shows the install process. I don't know what to do since it has been doing it for two hours now (boot loops to that screen each time is 'starts' itself again.
Local Optus store where I purchased the phone advised they cannot help me and referred me to OPPO, so I am sitting back at home with no idea what I should do (my phone has not been rooted or anything).
Thanks
o0xx0o said:
Can I ask how you fixed the boot loop issue? I picked up an F1 on Thursday from Optus and installed Spectrum, decided to return to ColorOS this morning, so followed instructions on Oppo website and downloaded the file etc. then when the phone attempted to install ColorOS, it started boot looping and the black screen where it shows the install process. I don't know what to do since it has been doing it for two hours now (boot loops to that screen each time is 'starts' itself again.
Local Optus store where I purchased the phone advised they cannot help me and referred me to OPPO, so I am sitting back at home with no idea what I should do (my phone has not been rooted or anything).
Thanks
Click to expand...
Click to collapse
I just did exactly what you attempted - flashed ColorOS back on. Mine is the optus variant too. Which version of ColorOS are you trying to flash?
mikeysteele said:
I just did exactly what you attempted - flashed ColorOS back on. Mine is the optus variant too. Which version of ColorOS are you trying to flash?
Click to expand...
Click to collapse
It was the latest version from the link that Ricky supplied in the OPPO forum. I cannot do anything with the phone. It just brings up the message on the screen each time the phone is turned on:
Updating, please wait
Don’t uninstall the battery or do other operations!
Estimated time remaining is 3 minutes
I have spoke to OPPO Australia (very unhelpful) who advised that I need to plug the phone into the computer and turn it on (which I did) and it still does the same thing. The consultant has referred me back to OPTUS to send the phone off for warranty. I've had the phone less than 48 hours.
Sorry to hear that man. I'm not sure what that could be. Have you made sure the download wasn't corrupted by comparing the MD5?
mikeysteele said:
Sorry to hear that man. I'm not sure what that could be. Have you made sure the download wasn't corrupted by comparing the MD5?
Click to expand...
Click to collapse
As instructed by OPPO technical support, I went to the Optus store who advised that they will send it off next week for assessment by their technicians.
Does it work for F1 Plus or just normal F1??
my phone is f1f unlocked TWRP recovery
I installed this rom all working fine .. but I lost recovery
now i can't install any roms
and i can't install any recovery
i had the same issue. After flashing the spectrum beta I decided to go back to stock. then when I flashed the file that was given by that Ricky guy my phone started to bootloop then. i tried a file which I downloaded from the oppo website it wont flash its saying that my system has been modified. install failed. i think that Ricky guy wants us to be stuck with the firmware he made so when we want to go back to stock colorOS he will ask for money.
I ask you how to restore the official original android 5.1.1 because my current recovery model is twmp 3.0.2.0
help with recovery
I have f1f and i flashed official project spectrum. I wanted to root my phone and i tryed to flash twrp and it didnt work and i soft bricked my phone so i have no recovery. So i had to get the boot.img and use fast boot to unbrick my phone. Now i turn my phone on by vol down and power. I have no recovery.
I need help getting stock recovery back because customs recoverys dont exist for project spectrum. Help please
Jamie_oppo said:
I have f1f and i flashed official project spectrum. I wanted to root my phone and i tryed to flash twrp and it didnt work and i soft bricked my phone so i have no recovery. So i had to get the boot.img and use fast boot to unbrick my phone. Now i turn my phone on by vol down and power. I have no recovery.
I need help getting stock recovery back because customs recoverys dont exist for project spectrum. Help please
Click to expand...
Click to collapse
Open the project spectrum update zip with 7zip(or similar) and drag and drop the recovery.img from project spectrum into your fastboot folder them put your phone into fastboot mode and connect to pc. Open fastboot folder in cmd line and type fastboot flash recovery recovery.img (if recovery .img name is wrong then replace with correct name). This should put back project spectrum recovery so you can flash back to official colouros from there.
If this doesn't work I suppose I could right a fastboot script that will flash back to colouros.
MiniBlu said:
Open the project spectrum update zip with 7zip(or similar) and drag and drop the recovery.img from project spectrum into your fastboot folder them put your phone into fastboot mode and connect to pc. Open fastboot folder in cmd line and type fastboot flash recovery recovery.img (if recovery .img name is wrong then replace with correct name). This should put back project spectrum recovery so you can flash back to official colouros from there.
If this doesn't work I suppose I could right a fastboot script that will flash back to colouros.
Click to expand...
Click to collapse
i did what you said. These are all the img in project spectrum. recovery.img, recovery_4_4, recovery_4_3 , reserve 4 img and boot.img. so i tryed using fastboot for all of them. None of the recovery ones give back my recovery it just bricks my phone and cant turn on. So i then have to do fastboot flash recovery boot.img and my phone turns on. So i cant get my recovery back and i have to flash boot.img just to turn in on and from then on i have to hold vol down and power to turn phone on . for some reason recovery.img does nothing just bricks phone
may i ask that why am i not able to flash back to stock ROM for f1f using the same stock recovery?? and now i am even not able to connect my phone through adb! can somebody help me
help with recovery
droid man said:
may i ask that why am i not able to flash back to stock ROM for f1f using the same stock recovery?? and now i am even not able to connect my phone through adb! can somebody help me
Click to expand...
Click to collapse
If u can see the image thats whats in project spectrum. boot.img reserve4.img and when i try to get my recovery ( because atm i dont have a recovery) i use fastboot flash recovery reserve4.img and it says remote size to large. can any1 please help and try and get my stock recovery back please
Can it root?
Can it root?
CAN SOMEONE PLEASE MAKE A RECOVERY FOR PROJECT SPECTRUM. BECAUSE THE TWRP FOR F1F IS FOR 5.1.1 AND WE CANT FLASH IT. I DONT KNOW HOE TO MAKE RECOVERIES BECAUSE IM A BEGINNER. many people have no recovery because they tried to flash twrp after the flash to spectrum. This would solve soooo many peoples problems
Hello,
So here is my problem.
My phone is stuck on this mode and I can't do anything. When I reboot it keeps showing the crashdump mode.
What I've done is that I unlocked the bootloader and did "fastboot boot twrp-3.2.3.0-enchilada.img", it showed the crashdump, so I tried "fastboot flash boot ..." instead.
Now it's stuck and I don't know how to solve my problem.
Please I need some help here, don't know how to get my phone working.
EDIT: I've managed to get rid out of this but my phone is in the booting screen (the red dot with the 2 whites) forever. I can access to the Fastboot, what should I do ?
Try looking for the unbrick tool/guid in the forums. That should fix it.
I managed to get my phone work again.
The problem was I flashed a non-boot image.
So in the CrashDump Mode, press (while phone not plugged) Volume Up + Power to go to Fastboot.
Boot a working TWRP, install official OTA and now everything is fine. Looks like the normal TWRP doesn't work on oxygen so I installed the blu spark one.
Looks like the normal TWRP doesn't work on oxygen
Click to expand...
Click to collapse
You just need to check latest version, before you do something to your firmware.
I have the same problem. OEM unlocking is not turned on on my device. I have used several versions of oos using MSM tool but no luck.
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
Hi
Was having trouble with phone and then did a restore back to saved version
However now the phone is stuck on Fast boot mode It gives the options to start in below
Bootloader
Recovery Mode
Power Off
START
However whatever I choose it keeps going into FastBoot mode with menu below
Product name
Variant
Bootloader version
Baseband Version
Serial Number
Secure Boot - Yes
Device State unlocked
I have tried power off an then press power and volume up and down and keeps booting into fastboot mode
I have connected it to PC and PC not picking it up
Tried rebooting with power cable plugged in and same issue stuck in fastboot
Has anyone got any solutions otherwise I have to send it to OP7 for repair
I guess if you can boot twrp and flash Magisk it will boot.
Or use msmtool to restore your phone to oos9 or oos10 formating data and erase your stuff
I don't know how you restored your phone into a "stable" version maybe you used the twrp for Android 11?
You need to provide more information about the state of your phone
RokCruz said:
I guess if you can boot twrp and flash Magisk it will boot.
Or use msmtool to restore your phone to oos9 or oos10 formating data and erase your stuff
I don't know how you restored your phone into a "stable" version maybe you used the twrp for Android 11?
You need to provide more information about the state of your phone
Click to expand...
Click to collapse
Thats the problem I cannot boot to anything except Fastboot. Gives option to boot to recovery but when I select it boots back into Fastboot
I was on Android 10 and having issues with phone connected to PC not picking it up etc and cables, drivers etc was working ok as have OP5 and could pick up that
Tried everything and nothing worked and also was not getting push notifications so could not purchase online
So last resort was to revert back to back up over 1 month old. Did that and for what ever reason phone booted back to fastboot and PC still wont pick it up so cannot even connect via adb
I restored it using TWRP and now everything I try just not working and looking at sending it back to OP to get it to factory reset as I cannot even do that
funkyirishman said:
Thats the problem I cannot boot to anything except Fastboot. Gives option to boot to recovery but when I select it boots back into Fastboot
I was on Android 10 and having issues with phone connected to PC not picking it up etc and cables, drivers etc was working ok as have OP5 and could pick up that
Tried everything and nothing worked and also was not getting push notifications so could not purchase online
So last resort was to revert back to back up over 1 month old. Did that and for what ever reason phone booted back to fastboot and PC still wont pick it up so cannot even connect via adb
I restored it using TWRP and now everything I try just not working and looking at sending it back to OP to get it to factory reset as I cannot even do that
Click to expand...
Click to collapse
That backup was from an older version of OOS?
In this point if you can't boot twrp the only safe way is using msmtool
RokCruz said:
That backup was from an older version of OOS?
In this point if you can't boot twrp the only safe way is using msmtool
Click to expand...
Click to collapse
No it was Android 10 pretty sure
Ok downloaded MSM tool just trying to figure out how to use it so checking that
Otherwise its going back to OP as under Guarantee and nothing I need on it Pics backed up but will come back with Android 11 if they can fix it
Android 10 but which version? It's not recommended to downgrade.
In msmtool are the instructions, download the correct msmtool for your device.
Not sure what version think it was the last one ???
Have msm tool and installed cert but now getting Package image not exist when I run the MSM download tool?
What was the file size of the MSM tool. Does it have the .ops file included over 2gb
justencase6 said:
What was the file size of the MSM tool. Does it have the .ops file included over 2gb
Click to expand...
Click to collapse
It was the zipped file and has Guacamole_21_O.07_190512.ops which is over 2kb
Installed the drivers but could not get it working
Phone on its way to one plus repair shop in Poland to get checked and repaired hopefully and will come back non rooted and with Android 11 installed
Now hopefully they can fix it but think I will leave it as is with Android 11 until possible TWRP and new roms come on board for Android 11 dont want to feck it up more
Thanks for the help
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.