recently got a hard brick oneplus one (A0001) from my friend.
After trying several times I finally installed the correct driver on win 10 pc and save it out of the hardbrick status using the Color OS method.
but now it won't boot into any os at all. It won't even boot into recovery. Everytime I boot it up, it just stays at the black screen with white 1+ logo there.
I have tried to install TWRP, or reflash cm11s, cm13 on the phone... none of them could get it out of the 1+ logo.
I can't get into recovery at all even after flash twrp successfully via fastboot.
Please let me know if there is other way to get out of the soft brick, no recovery, no os status.
Thank you.
Is the bootloader unlocked properly. If so and its still not working I would try a complete factory reset as there is an image on the forums for it. The if that works look at twrp after. I suggest the tuga version though.
Shinobi_warrior said:
Is the bootloader unlocked properly. If so and its still not working I would try a complete factory reset as there is an image on the forums for it. The if that works look at twrp after. I suggest the tuga version though.
Click to expand...
Click to collapse
Yes, both line on bootloader show "ture ".
I have flash several cm builds via fastboot but none of them works for me.
I also flash twrp but still can't boot into twrp either.
Would you mind point me to the TUGA version? I have been hanging around xda and oneplus forum last couple days but still no luck.
https://www.androidfilehost.com/?w=files&flid=50417
Should use the -5 version it could possibly be your computer have you tried a different one? Maybe its a driver related issue?
":TWRP_3.1.1-5-TugaPower.img"
laofan said:
recently got a hard brick oneplus one (A0001) from my friend.
After trying several times I finally installed the correct driver on win 10 pc and save it out of the hardbrick status using the Color OS method.
but now it won't boot into any os at all. It won't even boot into recovery. Everytime I boot it up, it just stays at the black screen with white 1+ logo there.
I have tried to install TWRP, or reflash cm11s, cm13 on the phone... none of them could get it out of the 1+ logo.
I can't get into recovery at all even after flash twrp successfully via fastboot.
Please let me know if there is other way to get out of the soft brick, no recovery, no os status.
Thank you.
Click to expand...
Click to collapse
The TWRP which you tried is latest official one,right?
Shinobi_warrior said:
https://www.androidfilehost.com/?w=files&flid=50417
Should use the -5 version it could possibly be your computer have you tried a different one? Maybe its a driver related issue?
":TWRP_3.1.1-5-TugaPower.img"
Click to expand...
Click to collapse
thanks, let me try this one.
Mr.Ak said:
The TWRP which you tried is latest official one,right?
Click to expand...
Click to collapse
I was using twrp 3.1.1.0 bacon.img. No luck.
laofan said:
I was using twrp 3.1.1.0 bacon.img. No luck.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Did you try using this? Although,it is based on colour os restore tool,it flashes cm11s instead of colour os through usb-debugging port method(ofcourse,not fastboot).
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Did you try using this? Although,it is based on colour os restore tool,it flashes cm11s instead of colour os through usb-debugging port method(ofcourse,not fastboot).
Click to expand...
Click to collapse
I did that already.. No luck. Still on 1+ logo
laofan said:
I did that already.. No luck. Still on 1+ logo
Click to expand...
Click to collapse
I'm afraid it's hardware issue then.
Related
I have long been a user of CM11 on my OPO, but today I wanted to install a custom ROM. As the guide says here I was required to update to CM12.1 beforehand. The updates seem to have overwritten TWRP with Cyanogen Recovery, but whenever I try to flash TWRP back onto my device it always boots back to CM recovery when I boot recovery.
I have followed this guide to attempt to re-flash custom recovery and re-root my device but I seem to have hit a brick wall.
I used the following commands:
*fastboot flash recovery recovery.img
*fastboot reboot
Click to expand...
Click to collapse
I have disabled CM recovery protection in developer options with no luck. I have also tried older versions of TWRP to no avail.
Can anyone advise me how to get around this problem? Any help is appreciated.
I had this problem when I first tried rooting the phone. Some said that you had to reboot directly to recovery after you had flashed TWRP and then it should presist, but that didn't work for me. The solution that worked (at least for me) was flashing it with a toolkit.
LittleConfucy said:
I had this problem when I first tried rooting the phone. Some said that you had to reboot directly to recovery after you had flashed TWRP and then it should presist, but that didn't work for me. The solution that worked (at least for me) was flashing it with a toolkit.
Click to expand...
Click to collapse
Thanks for your reply. Sorry, I'm a bit out of the loop these days. Could you elaborate on what toolkits I could use?
jayalex said:
Thanks for your reply. Sorry, I'm a bit out of the loop these days. Could you elaborate on what toolkits I could use?
Click to expand...
Click to collapse
http://www.wugfresh.com/brt/
LittleConfucy said:
I had this problem when I first tried rooting the phone. Some said that you had to reboot directly to recovery after you had flashed TWRP and then it should presist, but that didn't work for me. The solution that worked (at least for me) was flashing it with a toolkit.
Click to expand...
Click to collapse
this is true, i had to do that... when done flashing TWRP reboot to recovery, no OS
jayalex said:
I have long been a user of CM11 on my OPO, but today I wanted to install a custom ROM. As the guide says here I was required to update to CM12.1 beforehand. The updates seem to have overwritten TWRP with Cyanogen Recovery, but whenever I try to flash TWRP back onto my device it always boots back to CM recovery when I boot recovery.
I have followed this guide to attempt to re-flash custom recovery and re-root my device but I seem to have hit a brick wall.
I used the following commands:
I have disabled CM recovery protection in developer options with no luck. I have also tried older versions of TWRP to no avail.
Can anyone advise me how to get around this problem? Any help is appreciated.
Click to expand...
Click to collapse
A quick search would have uncovered a dozen or so threads detailing how to overcome this problem in the very q&a section that you've posted in. Then there's the FAQ thread that's stuck at the top:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Then there's my guide stuck in the general section:
http://forum.xda-developers.com/showthread.php?t=2839471
I have the same problem, unfortunately most of the suggested fixes in the Q/A sections and all the threads do not help me.
Here is a detailed explanation of what is going on:
http://forum.xda-developers.com/oneplus-one/help/installing-custom-recovery-cm12-1-5-1-1-t3232611
If I power down the phone, after flashing recovery, and boot it with power+volume it stays on the OPO logo, screen goes black and reboots again - and if I do not hold the volume button it boots into the normal OS. If i keep holding the volume button the OPO logo keeps appearing and it keeps going to black and reboots again and again.
Michiel0211 said:
I have the same problem, unfortunately most of the suggested fixes in the Q/A sections and all the threads do not help me.
Here is a detailed explanation of what is going on:
http://forum.xda-developers.com/oneplus-one/help/installing-custom-recovery-cm12-1-5-1-1-t3232611
If I power down the phone, after flashing recovery, and boot it with power+volume it stays on the OPO logo, screen goes black and reboots again - and if I do not hold the volume button it boots into the normal OS. If i keep holding the volume button the OPO logo keeps appearing and it keeps going to black and reboots again and again.
Click to expand...
Click to collapse
Have you tried flashing a different version of TWRP or another recovery?
Heisenberg said:
Have you tried flashing a different version of TWRP or another recovery?
Click to expand...
Click to collapse
Thank you for all your responses. I made a thread over on /r/cyanogenmod too and found a solution.
I run the following commands instead:
fastboot flash recovery twrp-2.7.6.0-bacon.img
fastboot boot twrp-2.7.6.0-bacon.img
Click to expand...
Click to collapse
This booted into TWRP. Reboot prompted me to install SuperSU. Recovery now boots to TWRP. I'd link the thread but can't as a new user. Hopefully this method works for others too.
Heisenberg said:
Have you tried flashing a different version of TWRP or another recovery?
Click to expand...
Click to collapse
jayalex said:
Thank you for all your responses. I made a thread over on /r/cyanogenmod too and found a solution.
I run the following commands instead:
This booted into TWRP. Reboot prompted me to install SuperSU. Recovery now boots to TWRP. I'd link the thread but can't as a new user. Hopefully this method works for others too.
Click to expand...
Click to collapse
I have tried multiple versions of TWRP and different recoveries - all to no avail. I have no idea what I am doing wrong and I'm certainly not green at this!
Michiel0211 said:
I have tried multiple versions of TWRP and different recoveries - all to no avail. I have no idea what I am doing wrong and I'm certainly not green at this!
Click to expand...
Click to collapse
Did you try using the fastboot boot command instead like I did above?
I'll give it a shot next time I get. Hope it works.
Michiel0211 said:
I'll give it a shot next time I get. Hope it works.
Click to expand...
Click to collapse
Cool, let us know how it goes :good:
Michiel0211 said:
I have tried multiple versions of TWRP and different recoveries - all to no avail. I have no idea what I am doing wrong and I'm certainly not green at this!
Click to expand...
Click to collapse
Try doing what the poster directly above you did.
I finally managed to get it working by downloading the latest version of TWRP (2.8.3.0) and (if it helped) using the command 'format cache'.
It doesnt stick, but atleast it works.
When my phone was running, it turned to black screen somehow. I was like "hmm, what is going on?" So i thought its time to install new cm, new rom.
I installed new CM13 by using TWRPv2.8.6.0, and it said "Successful". But when I reboot, it automatically goes to TWRP screen and cannot boot OS.
I did try to install different cm, rom, but its not working at all. Still keep going to TWRP screen.
Please help me out!
Try reflash twrp and clean flash of rom
Be sure boatlaoder is unlock
memooo_shakal said:
Be sure boatlaoder is unlock
Click to expand...
Click to collapse
It's not a problem of bootloader
As for OP: side load another zip from PC
I don't know if twrp is working. Because accourding to the CM download page, they have their own recovery.
Try their CMRecovery.
Download: cm-13.0-20160402-NIGHTLY-bacon-recovery.img
sha1: ec635a224e90049b085e7adbe0d0ed0b2fe6266f
Click to expand...
Click to collapse
You can always flash twrp back.
verde90 said:
When my phone was running, it turned to black screen somehow. I was like "hmm, what is going on?" So i thought its time to install new cm, new rom.
I installed new CM13 by using TWRPv2.8.6.0, and it said "Successful". But when I reboot, it automatically goes to TWRP screen and cannot boot OS.
I did try to install different cm, rom, but its not working at all. Still keep going to TWRP screen.
Please help me out!
Click to expand...
Click to collapse
Make sure that your volume button is not broken
Can you boot to fastboot? With buttons combination?
Yesterday my phone died for no reason, and i've been trying everything i can to restore it...
What heleped me a little was the QFIL software, and downloading with it the Color OS.... the problem is that i can't access the fastboot, and the recovery boot only lets me wipe cache and data...
anyone knows how to acces the fast boot??? or is there a way to install CM12 and TWRP with QFIL??
I really need to preserve some data already in the phone, so i havent risked the chance to wipe everything...
xchikyx said:
Yesterday my phone died for no reason, and i've been trying everything i can to restore it...
What heleped me a little was the QFIL software, and downloading with it the Color OS.... the problem is that i can't access the fastboot, and the recovery boot only lets me wipe cache and data...
anyone knows how to acces the fast boot??? or is there a way to install CM12 and TWRP with QFIL??
I really need to preserve some data already in the phone, so i havent risked the chance to wipe everything...
Click to expand...
Click to collapse
If you're able to boot into recovery,why not in fastboot(vol+ + power)? That's strange.Also it is really a matter of doubt that you'll be able to save your data if you're not able to boot into fastboot mode.
Did you tried to flash another twrp recovery with Twrp?
Mr.Ak said:
If you're able to boot into recovery,why not in fastboot(vol+ + power)? That's strange.Also it is really a matter of doubt that you'll be able to save your data if you're not able to boot into fastboot mode.
Did you tried to flash another twrp recovery with Twrp?
Click to expand...
Click to collapse
i installed a mix of color OS + CM13 and getting into recovery and then advanced lets me reboot into fastboot, which is good... i installed TWRP, but the section with the "slide to confirm" in my phone is damaged (screen not working there) so.... i need to see how to flash everything via fastboot that it's what's been working for me...
any help witht his? tutorials everywhere list only how to install TWRPand then installing OS from there, which is impossible for my device
xchikyx said:
i installed a mix of color OS + CM13 and getting into recovery and then advanced lets me reboot into fastboot, which is good... i installed TWRP, but the section with the "slide to confirm" in my phone is damaged (screen not working there) so.... i need to see how to flash everything via fastboot that it's what's been working for me...
any help witht his? tutorials everywhere list only how to install TWRPand then installing OS from there, which is impossible for my device
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
If you want to save your internal,dont do the "userdata" command.
Mr.Ak said:
If you're able to boot into recovery,why not in fastboot(vol+ + power)? That's strange.Also it is really a matter of doubt that you'll be able to save your data if you're not able to boot into fastboot mode.
Did you tried to flash another twrp recovery with Twrp?
Click to expand...
Click to collapse
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
If you want to save your internal,dont do the "userdata" command.
Click to expand...
Click to collapse
thank you very much... i'lll try and comment the results
I'm getting this error in the fastboot while trying to flash system
FAILED: (remote: data too large)
xchikyx said:
I'm getting this error in the fastboot while trying to flash system
FAILED: (remote: data too large)
Click to expand...
Click to collapse
Are you using original USB cable? Try it a few more times by rebooting into fastboot mode again.
Mr.Ak said:
Are you using original USB cable? Try it a few more times by rebooting into fastboot mode again.
Click to expand...
Click to collapse
yes, i am using original cable...
and it keeps showing the data too large
UPDATE:
I installed this https://forum.xda-developers.com/showthread.php?t=2317790 and seems to be working
xchikyx said:
yes, i am using original cable...
and it keeps showing the data too large
UPDATE:
I installed this https://forum.xda-developers.com/showthread.php?t=2317790 and seems to be working
Click to expand...
Click to collapse
I'm glad it worked.
But I didn't thought that It was a driver issue as you were able to do other commands just fine but anyways the good thing is ,it worked.:fingers-crossed:
Mr.Ak said:
I'm glad it worked.
But I didn't thought that It was a driver issue as you were able to do other commands just fine but anyways the good thing is ,it worked.:fingers-crossed:
Click to expand...
Click to collapse
yeah, now i need to find a way to install the Gapps... i need a) another recovery that doesnt use the bottom part of the screen (so, no TWRP) ; b) gapps in a IMG file
any idea?
xchikyx said:
yeah, now i need to find a way to install the Gapps... i need a) another recovery that doesnt use the bottom part of the screen (so, no TWRP) ; b) gapps in a IMG file
any idea?
Click to expand...
Click to collapse
Cos13.1.x already has Gapps mate.Btw,im wondering how you use bacon with broken touch? Screen mirroring to PC?
Just FYI,lcd+digitizer replacement doesn't cost much and even you can replace it at home.I did myself a few months ago.
Mr.Ak said:
Cos13.1.x already has Gapps mate.Btw,im wondering how you use bacon with broken touch? Screen mirroring to PC?
Just FYI,lcd+digitizer replacement doesn't cost much and even you can replace it at home.I did myself a few months ago.
Click to expand...
Click to collapse
its not all the screen, just the bottom inch....
and i use it rotating it 180º, which had worked fine for over half a year now... i bought and replaced a screen once, but it only lasted 11 days...
anyway... if cos13.1.x has gapps, why does it stays in the boot logo forever? :/
xchikyx said:
its not all the screen, just the bottom inch....
and i use it rotating it 180º, which had worked fine for over half a year now... i bought and replaced a screen once, but it only lasted 11 days...
anyway... if cos13.1.x has gapps, why does it stays in the boot logo forever? :/
Click to expand...
Click to collapse
You mean it didn't booted? FYI,Gapps has nothing to do with rom booting,they are optional.
First boot can usually take 20-30 mins.
Mr.Ak said:
You mean it didn't booted? FYI,Gapps has nothing to do with rom booting,they are optional.
First boot can usually take 20-30 mins.
Click to expand...
Click to collapse
oh, so it takes longer than what i let it... i'lltry again
What QFIL software did you use? Similar thing happened to mine
Sent from my A0001 using Tapatalk
clevebb said:
What QFIL software did you use? Similar thing happened to mine
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
QFIL 1.0.0.2
It worked fine letting me enter fast boot...,
however i havent been able to make the phone work again... it doesnt pass the boot logo
I have oneplus one 64gb but when I was trying to reset my phone it went into brick state. now with the help of my friend I installed a new rom in it but now it is showing 16gb memory. please guide in this regard
Gakhar123 said:
I have oneplus one 64gb but when I was trying to reset my phone it went into brick state. now with the help of my friend I installed a new rom in it but now it is showing 16gb memory. please guide in this regard
Click to expand...
Click to collapse
pretty sure he installed the userdata_16g instead of userdata_64g
and i'm not even an expert hahaha
can you tell me which OS he installed and how? i really want to recover my phone
Hello guys. I need your help badly.
I am using Galaxy Grand Prime smg530h
The problem is when I push the power button, my phone automatically boots to recovery mode which is Twrp, yeah I was my only problem last time. I guess I wipe something using twrp, my phone says "NO OS INSTALLED" . Then I googled some ways to fix so I installed a custom rom using twrp. I though my problem was solved but still when I turn on my phone it automatically boots recovery. I googled again and did something. But a big problem shows up, When I turn on my phone, it boots automatically to twrp but after the samsung logo flashes, black screen appears. Its just blank but the my phone black light is on and I think im on twrp since everytime I touch the screen it vibrates.
Please help me
Htxenuj said:
Hello guys. I need your help badly.
I am using Galaxy Grand Prime smg530h
The problem is when I push the power button, my phone automatically boots to recovery mode which is Twrp, yeah I was my only problem last time. I guess I wipe something using twrp, my phone says "NO OS INSTALLED" . Then I googled some ways to fix so I installed a custom rom using twrp. I though my problem was solved but still when I turn on my phone it automatically boots recovery. I googled again and did something. But a big problem shows up, When I turn on my phone, it boots automatically to twrp but after the samsung logo flashes, black screen appears. Its just blank but the my phone black light is on and I think im on twrp since everytime I touch the screen it vibrates.
Please help me
Click to expand...
Click to collapse
Have you tried to re-install everything including your recovery? Perhaps even your bootloader or try to flash your ROM manually from fastboot or adb.
RAZERZDAHACKER said:
Have you tried to re-install everything including your recovery? Perhaps even your bootloader or try to flash your ROM manually from fastboot or adb.
Click to expand...
Click to collapse
Hmm. Can you show me a guide sir? On reinstalling? 'cos I dont know what to do since I am stuck on a blank screen.
Htxenuj said:
Hmm. Can you show me a guide sir? On reinstalling? 'cos I dont know what to do since I am stuck on a blank screen.
Click to expand...
Click to collapse
There is already a guide available for how to flash stock rom, which you can check out here. You can get the stock rom from sammobile, the official samsung firmware resource which you can check out here.
Good luck!
Edit: You can then try to reflash twrp and if it doesn't work, post about it in the twrp thread for your device.
RAZERZDAHACKER said:
Have you tried to re-install everything including your recovery? Perhaps even your bootloader or try to flash your ROM manually from fastboot or adb.
Click to expand...
Click to collapse
Samsung doesn't use fastboot, they use download mode and flash with Odin. Be familiar with these kinds of specifics about a device if you're going to give advice, otherwise you might tell someone something very wrong unintentionally.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Samsung doesn't use fastboot, they use download mode and flash with Odin. Be familiar with these kinds of specifics about a device if you're going to give advice, otherwise you might tell someone something very wrong unintentionally.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Adb: Recover > Update from ADB
Fastboot: Boot to download mode > fastboot access on most devices (confirmed on my S4)
RAZERZDAHACKER said:
Adb: Recover > Update from ADB
Fastboot: Boot to download mode > fastboot access on most devices (confirmed on my S4)
Click to expand...
Click to collapse
adb works on Samsung, fastboot does not.
Sent from my SM-S903VL using Tapatalk
RAZERZDAHACKER said:
Have you tried to re-install everything including your recovery? Perhaps even your bootloader or try to flash your ROM manually from fastboot or adb.
Click to expand...
Click to collapse
How can I boot to Download mode since I am stuck at blank screen?
Htxenuj said:
How can I boot to Download mode since I am stuck at blank screen?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=gYA3ZMlDO3Q
Htxenuj said:
Hello guys. I need your help badly.
I am using Galaxy Grand Prime smg530h
The problem is when I push the power button, my phone automatically boots to recovery mode which is Twrp, yeah I was my only problem last time. I guess I wipe something using twrp, my phone says "NO OS INSTALLED" . Then I googled some ways to fix so I installed a custom rom using twrp. I though my problem was solved but still when I turn on my phone it automatically boots recovery. I googled again and did something. But a big problem shows up, When I turn on my phone, it boots automatically to twrp but after the samsung logo flashes, black screen appears. Its just blank but the my phone black light is on and I think im on twrp since everytime I touch the screen it vibrates.
Please help me
Click to expand...
Click to collapse
i have 2 of this devices,they all go to same trouble,never show twrp. no change no picture just blank (seems grey into black)
Suryo75 said:
i have 2 of this devices,they all go to same trouble,never show twrp. no change no picture just blank (seems grey into black)
Click to expand...
Click to collapse
It fix by using cwm, twrp is not compatible with twrp especially g530h which is has xxu based
Suryo75 said:
It fix by using cwm, twrp is not compatible with twrp especially g530h which is has xxu based
Click to expand...
Click to collapse
Can you help with a working link for CWM for 530H? I cant seem to find anything apart from TWRP
dv8ted said:
Can you help with a working link for CWM for 530H? I cant seem to find anything apart from TWRP
Click to expand...
Click to collapse
Just visit link with quote cwm for g530h
dv8ted said:
Can you help with a working link for CWM for 530H? I cant seem to find anything apart from TWRP
Click to expand...
Click to collapse
CWM is a dead project, it is no longer supported, that is why you are only finding TWRP. If you want custom recovery, use TWRP, it is a much better recovery than CWM anyway.
Sent from my LGL84VL using Tapatalk
dv8ted said:
Can you help with a working link for CWM for 530H? I cant seem to find anything apart from TWRP
Click to expand...
Click to collapse
try this
Is their any solution to use twrp on g530h xxu based?
On flashing many custom roms through cwm, their is nothing on screen but gray broken lines.
Please help if anyone have it's solution.
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.