As title say, my phone wont boot (stuck on boot animation) after accidentally change GPU governor, I already tried dirty flash, clean flash ROM, try different ROMs, flashing firmware, but nothing is working. Now I'm downloading offical MIUI firmware and planning to flash it with MiFlash, but before I try that is there any way around to fix it?
Oh, this is my dmesg https://pastebin.com/wdg8A5Vf
arshy said:
As title say, my phone wont boot (stuck on boot animation) after accidentally change GPU governor, I already tried dirty flash, clean flash ROM, try different ROMs, flashing firmware, but nothing is working. Now I'm downloading offical MIUI firmware and planning to flash it with MiFlash, but before I try that is there any way around to fix it?
Oh, this is my dmesg https://pastebin.com/wdg8A5Vf
Click to expand...
Click to collapse
are you using redwolf recovery? or did you use kernel adiutor to change it? if you used redwolf then, try setting it to interactive
Related
Im tired of installing many ROM's and 2 different Recovery, some "cant open .zip" and having boot problems, and in other recovery, it can install roms, but other aslo cant open .zip, and also having boot problems,
Im really tired of reflashing stock ICS Fw then root, install Recovery again, after failing installing ROMs.. its too long to reflash, root, install recovery,, its waste my time and having headache after failing installing ROMs for almost a week
Is there any fast solution or what would you do after you fail installing ROMs and cant boot? even do you can enter recovery? what proper should do next? would you also reflash again stock ICS then root and install recovery?
or any other fast way solution..
Please help
Root and install recovery onto your device. Enter recovery and make a nandroid back up of your device. Flash your new rom and reboot the device. If you boot loop or the rom doesn't work or even if you just don't like it, enter recovery (may have to remove the battery to restart a boot cycle) and use your nandroid back up to restore your device.
Before flashing the new rom, you should make sure that the kernel is compatible with the one that is already on your device. If it isn't compatible, you will also want to flash the new kernel using fastboot/flashtool, and not recovery. Also make sure you have a back up of your rom's current kernel so you can flash the original kernel, if you decide to go backwards.
justmpm said:
Root and install recovery onto your device. Enter recovery and make a nandroid back up of your device. Flash your new rom and reboot the device. If you boot loop or the rom doesn't work or even if you just don't like it, enter recovery (may have to remove the battery to restart a boot cycle) and use your nandroid back up to restore your device.
Before flashing the new rom, you should make sure that the kernel is compatible with the one that is already on your device. If it isn't compatible, you will also want to flash the new kernel using fastboot/flashtool, and not recovery. Also make sure you have a back up of your rom's current kernel so you can flash the original kernel, if you decide to go backwards.
Click to expand...
Click to collapse
Thanks I think that what im looking for.. the Nandriod backup..
gota way to find that now and how to install
Thanks a lot!
Hmmm...the most easiest way it to unlock your bootloader first...then flash custom kernel...this can help you skip rooting and installing recovery again and again if something goes wrong cause all custom kernel is pre-rooted and got recovery by default....
next you need to find which custom roms you want to flash...some custom roms have their own kernel or flash any custom kernel that is compatible with the roms....
remember, custom kernel is important cause if you flash the wrong kernel, you might get bootloop after flashing the roms....
Pusak Gaoq said:
Hmmm...the most easiest way it to unlock your bootloader first...then flash custom kernel...this can help you skip rooting and installing recovery again and again if something goes wrong cause all custom kernel is pre-rooted and got recovery by default....
THANKS! I have a plan now to unlock my BL
thanks for that info
Click to expand...
Click to collapse
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.
I am on Aosp 6.0.1 all of a sudden it rebooted and stuck at boot animation. no matter what i do it will not get past that thing.I have this problem from long time in many roms after using 10-15 days this problem arises.
flash Fastboot Rom
You may have to do a reflash of the ROM, i'm assuming you have a custom recovery installed? You can try flashing over top of your existing installation.
goofball2k said:
You may have to do a reflash of the ROM, i'm assuming you have a custom recovery installed? You can try flashing over top of your existing installation.
Click to expand...
Click to collapse
Happened with me. Try booting in twrp and reboot to system
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.
[SOLVED]
Recently I've installed Oreo AOSP, I wanted to return flashing from TWRP but stucks on bootanimation, I tried with XGen but the problem persists
Also I tried through flashhtool but the program it doesn't detect my phone, also I tried with Emma, the process was completed correctly but when I boot up the phone the custom ROM is there
Im going to try flashing the Loire kernel through TWRP, at least I want to move to LineageOS
Flash a stock based custom rom (XGEN or Persian Rom) - dirty or clean /system is your choice. If you want extra then flash the clean patched kernel in the rooting thread (we actually don't need this)
Note that the phone won't boot properly and will bootloop, but now the phone will be recognize as F5121/22 in flashtool so you can flash the rom as normal.
n0k0m3 said:
Flash a stock based custom rom (XGEN or Persian Rom) - dirty or clean /system is your choice. If you want extra then flash the clean patched kernel in the rooting thread (we actually don't need this)
Note that the phone won't boot properly and will bootloop, but now the phone will be recognize as F5121/22 in flashtool so you can flash the rom as normal.
Click to expand...
Click to collapse
Already I solved the problem, i flashed the AOSP kernel in Existenz N, then I can boot as usual, however thanks for your answer