Hi, I have a Mi2S with unified partitions. I was using CM12, and MIUI 8.2 without problems for the last years.
Yesterday (with official miui 8.2 developer) the phone turns off. When I switch on, boots the android system, i see the android logo, and all the boot animations but at the end of the boot process, when the lock screen should be viewed, the phone turns off by itself again.
I tried fastboot miui, cyanogenmod, and many different roms installed with many methods with different wipes, and partitions, and the problem persists.
TWRP 3.1 works fine, and I can boot into recovery, and do things there.
No idea what to do....
This propably comes too late, but I had the same problem last new year's eve. I ordered a new battery and now everything has been working like a dream.
Related
Hey there! I was updating my version of Paranoid Android and my kernel and it seemed fine at first but It yield some odd problems. I went into Clockworkmod recovery and Flashed my rom and kernel I then proceeded to wipe my cache and dalvik cache. I have done this many times before on many devices. I encountered a problem when I rebooted for the second time, I got the Android is updating apps display and I continued to get it every time I booted. The device would also randomly turn off when the screen dimmmed. I proceeded to set out and fix it. Here are the steps I took and the problems it caused.
Flashed stock rom-would not boot properly
Flash RESET kernel-I messed up and though this was a real kernel, my problems escalated from here.
Flashed stock rom and recovery.
Flashed reset kernel and then real kernel-Still had problems.
Flashed stock rom
My problems from all this accumulated somewhat and I can barely boot into fastboot. I get weird static screens and weird white noise sounds. It does not always let me boot into android and will get to the google logo 1 out of ten tries.
These is really unnerving and I have no clues whats what.
Note: I am using Faux123's kernels and his reset kernel.
Thanks a lot for any help!!!
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
schmidty455 said:
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
Click to expand...
Click to collapse
Omni clearly states that it is an alpha, so you mileage may vary considerably.
Sounds kernel related. Have you tried just reflashing the kernel and seeing if it'll boot after that. Or trying a different kernel?
Thanks for the reply! I actually just fixed the problem on my own. I used Odin to flash a newer version of TWRP and then flashed omni, and it looks like everything is working just fine. I read a few people saying that they were having issues flashing kit kat roms with older versions of recovery, so I figured it was worth a shot.
Been having this problem with the latest 4.4 kitkat roms, (GE & AOSP)
when i was back on my old bootloader (whatever it shipped with) and modem (XXUEMJ5) i would always get a random force shutdown when just using my phone through daily use, it would either:
A) Boot for a short time with several apps having lost all their data (such as usernames and passwords). Then shortly after shutdown again into a constant bootloop. (Upon entering Recovery the phone would display 0% battery)
B)Shutdown into a bootloop only recoverable by wiping the /data partition or reflashing the rom (or any other rom).
So then i heard good news from the new bootloader and modem from the XXUFNA5 Leaks throughout the forums and decided to flash them and also test the leaked TW rom. Being me the rom was laggy as hell and i quickly reverted back to Jamal's 4.4 RC 1.1
Unfortunately the force shutdown bootloop problem continued but when it would shutdown i could plug the phone into a power source and boot without problems? not very convenient if you ask me.
just recently i flashed Brood's AOSP pre-RC4 which was working fine until i was signing into some apps then it force shutdown and as i tried to boot the phone went to "Updating apps 1 of 1" and then instantly shut down again.
I went into recovery and wiped /data, /cache and Dalvik then rebooted, the phone would reach the final stage of booting (just before the lockscreen shows) and would reboot and repeat the process all over again.
I went to flash a different rom so i could atleast have a working phone for the day and upon fully wiping, etc. the phone would not boot and continue the reboot process. i suspected a bootloader problem so i reflashed the bootloader and roms now boot. im guessing the bootloader was corrupted somehow and i think the process will just repeat itself.
Anyone got any ideas? I'm stumped and frustrated as the process of setting my phone back up every day is getting extremely boring.
Hey everyone, hope you are all having a great day.
I am facing an issue with my Redmi 2 Prime(2014818), everything was working fine.A few days back I was on official AICP rom which was super smooth and stable thanks to the devs ...after a couple of days,every time I reboot/turn on the Phone.the boot animation used to freeze for 2-3 seconds and the phone rebooted,but this time the phone rebooted smoothly without any hiccups.I thought this was an Issue with the bootloader or modems, however I ignored it and went ahead and flashed another ROM..but again the Rom got stuck on boot animation and reboot and this kept repeating, so I decided to re flash miui via fastboot in order to reflash all the partitions.later on installed TWRP and flashed latest AOSPE yesterday and again the same problem shows up(boot animation freezes in initial 5 seconds and reboot, and repeat...)
I've tried removing both the sim cards before turning it on and the phone boots up fine, but the problem is-I turn off and re insert ANY or BOTH of the sims,the rom goes into a bootloop again in the exact same way,and as we all know,we need to remove the battery before removing or inserting the sim card so I cant insert the sim with the phone turned on.
This is the only device I have and miui is awfully slow(eg-after minimizing whatsapp,launcher takes atleast 3 seconds to load the app drawer again!!),feels like a 4 year old samsung phone even after removing many system apps and i cant buy any other phone atleast till june end and my exams are coming.(been using this for 20 months now).
So, if anyone here could help me out I would really appreciate it People!!feel free to suggest me anything which might be of help with this.
P.S-I am on the lollipop bootloader and the fastboot file I flashed was Redmi 2 Prime Global Stable fastboot rom,the latest one.
feel free to ask me further questions regarding this
Signing Off.
-Faiz
my device 1Gb version i tried lolipop bootloader for volte and faced same issue...but custom rom booted up with no problems...flash twrp and lineage os firmware then try custom roms..or if u want stock flash xiaomi.eu
1)xiaomi.EU ROM
2)Tesla
3)lineage
4)flash latest miui from xiaomi.EU and then flash custom ROM.
tried flashing xiaomi .eu latest stable rom,and then tried aicp.same problem,also tried official RR rom,phone boots with RR but reboots during setup wizard
i always have this problem whenever i flash a custom rom.. so, i flash miui 7 based on lollipop and then root it and then flash rr rom via twrp by just cleaning the cache and dalvik.. i did all this with the sim on.. and then it boots up fine.. well, just give it a try by flashing an miui 7 lollipop rom...
thanks for the suggestion,tried this but still wont work..even tried flashing bootloader and modem etc. same issue,tried other roms also...
really fed up of this,can it be possible that theres a problem with the SIM itself..as bootup is perfectly fine without any sims inside.
Issue fixed after swapping sims,Mods please close this Thread.
It's happened to me before, but eventually gets solved by itself. Now, however, with the advent of the Stock Oreo release I want to backup my phone ASAP.
I have tried with several different versions of TWRP and I also tried leaving it overnight and it still didn't boot. Any hints on what's going on?