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).
Related
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.
Hi there. I'm using Redmi Note 3 SD from quite some time. I've officially unlocked the bootloader and flashed many custom as well as MIUI Roms from time to time. But recently I'm facing a problem. I'm trying some Nougat based Roms but facing a weird problem. After flashing Rom when the phone boots up and setup screen comes than while setting up the phone screen crashes in some certain point and it starts from the beginning, it won't past the setup screen. I tried many Roms like NOS, AEX, Lineage but facing the same problem. I've used Nougat based Rom previously but was not facing this issue, it only started when i tried to flashed newer build. Am I doing something wrong. Please I need urgent help so any help will be highly appreciated.
Are u trying to flash the 7.1.2 based rom with 7.1.1 gapps.If yes then first flash the rom and boot, there will be no setup wizard this time and then flash the gapps
ShivamTiwari said:
Are u trying to flash the 7.1.2 based rom with 7.1.1 gapps.If yes then first flash the rom and boot, there will be no setup wizard this time and then flash the gapps
Click to expand...
Click to collapse
I tried without Gapps too but at a point when it ask install from backup or start as a new device it crashes no matter whichever option I choose. Any idea whats the reason. Thanks
rjrulz007 said:
I tried without Gapps too but at a point when it ask install from backup or start as a new device it crashes no matter whichever option I choose. Any idea whats the reason. Thanks
Click to expand...
Click to collapse
Well in that case, I have no idea.Sorry bro,wait for someone else to reply.
rjrulz007 said:
Hi there. I'm using Redmi Note 3 SD from quite some time. I've officially unlocked the bootloader and flashed many custom as well as MIUI Roms from time to time. But recently I'm facing a problem. I'm trying some Nougat based Roms but facing a weird problem. After flashing Rom when the phone boots up and setup screen comes than while setting up the phone screen crashes in some certain point and it starts from the beginning, it won't past the setup screen. I tried many Roms like NOS, AEX, Lineage but facing the same problem. I've used Nougat based Rom previously but was not facing this issue, it only started when i tried to flashed newer build. Am I doing something wrong. Please I need urgent help so any help will be highly appreciated.
Click to expand...
Click to collapse
try clean flashing.
download latest gapps first
in case u get bootloop, download this- unlock_bootloader.zip
clean dalvik+data+system+cache,
then flash firmware+rom+unlock_bootloader.zip+gapps
(i'm using twrp 3.1.0.0 official by TheStrix, never faced such problem. follow my method mentioned above)
rjrulz007 said:
Hi there. I'm using Redmi Note 3 SD from quite some time. I've officially unlocked the bootloader and flashed many custom as well as MIUI Roms from time to time. But recently I'm facing a problem. I'm trying some Nougat based Roms but facing a weird problem. After flashing Rom when the phone boots up and setup screen comes than while setting up the phone screen crashes in some certain point and it starts from the beginning, it won't past the setup screen. I tried many Roms like NOS, AEX, Lineage but facing the same problem. I've used Nougat based Rom previously but was not facing this issue, it only started when i tried to flashed newer build. Am I doing something wrong. Please I need urgent help so any help will be highly appreciated.
Click to expand...
Click to collapse
Flash by formating (not wipe) in twrp
Try clean install. Wipe data and system after backing up.
If that doesn't work, Check if any software is making that issue. In my case, not exactly same, but was stuck on boot after flashing super su.
When i tried to flash twrp using flashify. It didn't work for me. My recovery not working anymore. Fastboot not detecting my phone. What to do now to flash recovery??
Try using BeansGapps
I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Don't flash a different kernel, just try RR first, boot and make sure it works.
Once that is done, then you can try flashing the kernel and see if everything works. If it doesn't, you have your answer.
Most custom ROMs are also builded just for their kernel so if u flash custom kernel then there is chance that ROM will not work as u expected. Just think about it when you are installing a custom kernel.
Today I did flash lite mode rom . It boots up but touch was not working...nothing was flashed even gapps.
Sometimes the recovery twrp too does not work.,touch lost. Now i suspect something wrong with the hardware.
But no issues with miui roms...Thats what makes me wonder
did you do it on the computer?
sibikallikkat said:
I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Click to expand...
Click to collapse
You may want to try installing Radon Kernel. I've got an aftermarket display which also didn't work with a custom rom (Lineage OS), but after flashing Radon Kernel it worked flawlessly. You may want o try Radon 5.0 as I'm having trouble with 5.1.
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
I have a problem. I install a custom kernel like Franco, Englezos etc. but once I install it the ROM boots but after a few seconds it freezes and then reboots. This happens with Siberia and RR 9.0, I did a clean flash when I flashed both.
Does anyone know what could be causing this and how to fix it?
My device is encrypted but I was able to install custom kernels using Siberia but now it just doesn't work.
Thanks in advance.
I know it sounds dumb, but have you tried rebooting a few more times?
I just flashed Ethereal kernel on PE and on the first boot my device froze up and crashed, but when I rebooted again it now works absolutely fine.