Stuck in mi logo screen after installing supersu - Xiaomi Redmi Note 4 Questions & Answers

I had unlocked bootloader and installed twrp on my device. But after flashing supersu my phone is not booting anymore. It gets stuck on the second mi logo screen (the screen with 'powered by android' caption). After going through similar posts here, I tried flashing unSu and boot.img, but neither methods worked. My device is Redmi Note 4 SD running stable MIUI 9.5 global rom. My data is backed up so I dont mind losing it, just need the phone to boot up. Any help is greatly appreciated.
Thanks in advance.

You need to flash lazyflasher after installing TWRP to prevent bootloop if you are using MIUI. https://www.androidfilehost.com/?fid=529152257862700328
Also nobody is using SuperSU these days, stick with Magisk as root solution.

k3lcior said:
You need to flash lazyflasher after installing TWRP to prevent bootloop if you are using MIUI. Also nobody is using SuperSU these days, stick with Magisk as root solution.
Click to expand...
Click to collapse
I had done that too, forgot to mention it. I finally just wiped everything and flashed pixel experience. I'll try using magisk. Thanks

did it work , my is also the same condition what process didi you use , please help m
searingmaw said:
I had done that too, forgot to mention it. I finally just wiped everything and flashed pixel experience. I'll try using magisk. Thanks
Click to expand...
Click to collapse
please tell me how did you get out of it , i am also stuck at same problem with mi + powered by android screen

Related

CM 14 won't Boot. Tried Flashing it multiple times!

1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Check the bootloader compatibilty of these roms, if they r for the mm bootloader it ll not boot untill u upgrade ur bootloader, check the threads from wer u hv downloaded this...
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Exodusche said:
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Click to expand...
Click to collapse
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
check out this thread http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
I use Oxygen_14_OTA_18_all but there's a couple files posted on the bootloader upgrade threads that allow you not too flash the whole firmware just the partions you need to upgrade.
i am having same issue i was on oxygenos 3.1.3 firmware when i started to flash nogut roms every nogut rom works except cm. i flashed official cynogenmod 14.1 thinking that problem must have been solved but it wont boot it just shows oneplus logo. i have waited for 30 minutes but nothing happened if something worked out for you please tell me.
Well I've looked around XDA for soultion and this is it.
CM 14 has some Kernel problems, so only what you have to do is just install new kernel as Arsenic or Black Reactor kernel
I was running the new bootloader on cm13 nightlies and couldn't get it to boot either.
Even after a full wipe and reflash with v7 gapps
Gave up in the end and went back to the last cm13 Nightly
flash arsenic kernel after flashing rom and gapps it will boot. Read the posts in ashwin's official cm 14.1 thread.
Flash Black Reactor (recommended) or Arsenic Kernel.
The zip files that you have for CM are the unofficial ones. So I guess they're from Sarthak Narang. Or at least one of them. Those ROMs require the older bootloader to function. So if you have the newer bootloader, it won't work.

Installing any new cynogenmod/mokee ROM always fails

Hi, I am trying to install cynogenmod or mokee rom and the device always gets stuck at cyno/mokee logo. it never goes beyond that. tried to wait for half an hour(waited for one hour twice).
Here is what I am doing:
I used TWRP but it wasnt working so i installed CWM, in both the recoveries I was wiping everything except sd card storage as my zip files were in the card. after that i flashed zip files(ROM & GAPPS). after that i rebooted to system. Am I doing it wrong? I am currently on 4.4.4 stock rom. Need help.
Thank you.
No one to help?
How can TWRP not work on your device? Install again TWRP via adb.
Flash latest twrp 3.0.2 and try
rian_tama said:
How can TWRP not work on your device? Install again TWRP via adb.
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash latest twrp 3.0.2 and try
Click to expand...
Click to collapse
The problem wasn't with the recovery and I wasn't doing anything wrong. It was really too bad to know that the rom version I was installing had a bootloop bug in it. So I had tried two previous versions but they too had the same bug. And unfortunately I tried CONTINUOUSLY for two long days to install those same bugged ROMS as if God has put me in frustration mode. Tech fooled me right, lol.
Grab the November 8 version of Cyanogemod. There are issues with the newer updates.

huawei p8 lite no os installed

Hello. Today i tried to root my phone for the first time. Everything seemed okay after a few minutes and i was browsing through TWRP and wiped my system. Right now im stuck on the Huawei logo in the beginning, because i have no OS installed. I tried to install several Emui versions via sd-card but nothing happened. I rly need help.
Sonimbreti said:
Hello. Today i tried to root my phone for the first time. Everything seemed okay after a few minutes and i was browsing through TWRP and wiped my system. Right now im stuck on the Huawei logo in the beginning, because i have no OS installed. I tried to install several Emui versions via sd-card but nothing happened. I rly need help.
Click to expand...
Click to collapse
Please use the help section of your device Forum here:
https://forum.xda-developers.com/p8lite/help
You either need your stock rom with the huawei flash tool (whatever they use) or you flash a custom rom with twrp, which should be easy to find on your device specific forum (section android development)
Good luck
Sent from my OnePlus 2 using XDA Labs

Phone rebooting / shutting down randomly

I did the following:
Unlocked bootloader
Installed twrp recovery
Flashed lazy flasher
Flashed rr pie rom
Flashed gapps nano
flashed magisk
My phone began restarting randomly once or twice a day.
I thought magisk was the culprit and flashed magisk uninstaller. Didn't solve the issue. Same happened with Pixel exp CAF and crDroid. On AOSP Extended it shuts off randomly instead of restarting. Now back to Pixel CAF cause reboot is better than shutting down.
I'm using latest version of twrp and roms.
How do I fix this. Pls help.
Edit: added magisk
Edit 2: mentioned gapps
SaraKumar said:
I did the following:
Unlocked bootloader
Installed twrp recovery
Flashed lazy flasher
Flashed rr pie rom
flashed magisk
My phone began restarting randomly once or twice a day.
I thought magisk was the culprit and flashed magisk uninstaller. Didn't solve the issue. Same happened with Pixel exp CAF and crDroid. On AOSP Extended it shuts off randomly instead of restarting. Now back to Pixel CAF cause reboot is better than shutting down.
I'm using latest version of twrp and roms.
How do I fix this. Pls help.
Edit: added magisk
Click to expand...
Click to collapse
There's no need to use Lazy Flasher and that's probably a reason why your phone is broken.
And why didn't you flash GApps?
Noter2017 said:
There's no need to use Lazy Flasher and that's probably a reason why your phone is broken.
And why didn't you flash GApps?
Click to expand...
Click to collapse
Thank you for replying.
Twrp was replaced by stock recovery everytime after I installed the rom zip and restarted the phone.
Someone had suggested lazy flasher in the forum. I don't know what it does but it fixed the problem. Is there a way to remove it? And will the recovery problem come back again if I remove it?
Sorry I forgot to mention gapps, I flashed nano after every rom except Pixel CAF(built in gapps).

Magisk bootloop

Dear all,
I have read quite few post about this issue. I have installed magisk and my phone has booted. After installing a magisk module it asked me to reboot. I did it. I ended up stucking in bootloop. I opened TWRP again and Installed a custom global rom (without factory reset) So it healed my phone. Root access has gone and my phone was working again with Al my settings and files. What can I do differently to get my Xiaomi rooted? Btw.... After flashing magisk zip, I also installed lazy flasher and I deleted cache.
Thank you very much in advance for any suggestions or solutions.
Which magisk modules? Compatible problem maybe...
Is that maybe ur fix
https://forum.xda-developers.com/mi-8/help/install-magisk-bootloop-t3824481
He solved it. Read the his first post to the end...
joke19 said:
Which magisk modules? Compatible problem maybe...
Is that maybe ur fix
https://forum.xda-developers.com/mi-8/help/install-magisk-bootloop-t3824481
He solved it. Read the his first post to the end...
Click to expand...
Click to collapse
Dear Joke 19,
First of all thank you for the answer. At the beginning I tried v17. After booting there was a message saying that I need to install at least v18. So I flashed v19. I booted my phone I opened magisk and it was running. But at the first reboot I stuck in boot loop.
Thanks,
Attila
Attilagubanyi said:
Dear Joke 19,
First of all thank you for the answer. At the beginning I tried v17. After booting there was a message saying that I need to install at least v18. So I flashed v19. I booted my phone I opened magisk and it was running. But at the first reboot I stuck in boot loop.
Thanks,
Attila
Click to expand...
Click to collapse
I have read through the whole post. I have seen this quote... ("And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!")
Unfortunately I have not found the solution to be able to use rot access, be able to install modules and do not stuck in bootloop...

Categories

Resources