Custom roms cause bootloop upon restart - Oppo Find 7 and 7a

I have used custom roms in the past, mostly nameless and omni, using LVM storage, but there's one problem I'm experiencing with it and that happens for me just about every time now, and that is a bootloop. Every time I'm settled with a rom, so in the first hour I have rebooted it several times and no problems occured.
But after a few day's my battery will run out or get low and I switch batteries, that's where the bootloop happens.
The bootloop is unrecoverable, so dirty flashing the system again or factory wipe does not work, the system+data partition needs to be wiped to be able to use my phone again. I'm now on COS 2.1.5i (agianst my will) because on that rom, I don't encounter that issue..
My question is, what could cause this problem? Does anyone else experience this problem?

Related

[Q]Have to Clear Cache and Dalvik Cache after every power off

So I am having a really strange problem recently with my phone, was wondering if I should unroot and return it or if it is something I am doing wrong. Basically what it boils down to is if I power my phone off from the menu or pull the battery, etc. upon powering back up it just Hangs on the HTC Evo 4G white splash screen indefinitely. I have let it sit as long as 15 mins without booting before, having seen this before in the past I know not to panic now but I just reboot into Recovery and wipe my cache and dalvik cache every time I reboot and my phone reboots back into sense in no time at all.
I know this is not normal, is there something I can do to troubleshoot this problem or is this is a sign of hardware failure?
ernbrdn said:
So I am having a really strange problem recently with my phone, was wondering if I should unroot and return it or if it is something I am doing wrong. Basically what it boils down to is if I power my phone off from the menu or pull the battery, etc. upon powering back up it just Hangs on the HTC Evo 4G white splash screen indefinitely. I have let it sit as long as 15 mins without booting before, having seen this before in the past I know not to panic now but I just reboot into Recovery and wipe my cache and dalvik cache every time I reboot and my phone reboots back into sense in no time at all.
I know this is not normal, is there something I can do to troubleshoot this problem or is this is a sign of hardware failure?
Click to expand...
Click to collapse
I've never seen that before. Interesting. What rom are you currently using? Do you have an unusually large amount of apps installed? The first thing I would do, is make a nandroid backup of your current setup, and then do a full wipe and flash a format all.zip, then reflash a different rom. Or just simply restore a nandroid of a known good setup, and see if the problem persists. If it stops, I'd say it was something specific to the rom/kernel/setup that you were running before. If it continues happening on a clean install of a different rom, then I'd probably unroot, restore to stock, and then see if the problem continues. If it does, take it to Sprint. If it stops, and everything is fine, re root it and start over. That's just what I would do, but I've never been presented with an issue such as that.
I appreciate the advice, I'm running Sprint Lovers right now been running it for a few months now, I don't have an unusual amount of apps installed but I did notice that the problem seemed to start occuring when I changed the Kernel. I will try your advice and see if that fixes the problem. I've been wanting an excuse to try the new Gingersense rom anyways.
ernbrdn said:
I appreciate the advice, I'm running Sprint Lovers right now been running it for a few months now, I don't have an unusual amount of apps installed but I did notice that the problem seemed to start occuring when I changed the Kernel. I will try your advice and see if that fixes the problem. I've been wanting an excuse to try the new Gingersense rom anyways.
Click to expand...
Click to collapse
If it started happening right after you swapped out the kernel, that could be the culprit. If you want to try the gingersense rom, I'll all for it, and will tell ya that they ran super incredibly smooth for a factory rom. However, if you don't feel like changing roms just yet, maybe try a different kernel. I'd be suspect of that, if the problem started shortly after changing to a different kernel. I say try out a gingersense rom, you shouldn't be disappointed (unless your phone still hangs at the splash screen upon reboot, lol).

Unexpected Reboots

Hello,
It seems that my G925T has some problems with soft reboots. I don't know exactly what the problem might be, maybe you can help me troubleshot.
So I have followed up all the things a normal user might do like:
soft reset, hard reset, odin stock rom flashing, smart switch disaster recovery, disabling certain apps, going to safe mode, cleaning cache, resetting cache and dalvik, but nothing. Flashing a different custom rom, custom kernel but still problem remains.
Even after following up with all these steps, my phone still reboots unexpectedly while I use it and even i don't use it. An average is that my phone gets these unexpected reboots like everyday. Maybe 3 time a day, or maybe next day. It seems like soft reboot.
For an some addition information my phone is IMEI repair, but everything is fine, i can get updates as i am currently on the official stock ROM.
Currently I am on latest update DOJC.
What do you think it might be the problem ?
Has soft reboots to do with IMEI repair ?
Is there anyway i can troubleshot this ?

Getting bootloops after rebooting for being laggy

Hi all, I would like to have some feedback if some of you is experiencing the same issue as I am. My N5X is running Stock Marshmallow (latest release) and it's rooted (SuperSU v2.71) with Xposed (latest version for arm64).
Every now and then (usually with an uptime more than 80 hours) the device becomes very laggy and my usual solution for eliminating the lag is rebooting. It would be the ideal solution if only the device wasn't remaining stuck in bootloop after rebooting.
For now the only "solution" I have found is doing a factory reset from TWRP, after performing a backup of /data. Uninstalling from recovery Xposed or simply wiping cache/dalvik or even flashing separately the stock images (boot, cache, system, vendor) did nothing without a factory reset.
The first times I got bootloops on the device I knew why it was happening (one time I modified build.prop forgetting to change the permissions, another time a similar thing but with the transfer of an app in /system), but these kinds of bootloop remain a mistery for me.
It also occurred without Xposed installed and with both stock and ElementalX kernel.
A peculiar thing I noticed while in TWRP is that the Cache was displayed occupying 0 MB. Might it be related to this issue?
Now, I know now that I should probably reboot more often, but I still would like to know why this happens because it's being very annoying doing the restore procedure every damn week.
And so, while doing my research, I wanted to have some feedback from those of you who had similar issues with a similar setup.
Thanks and cheers!
A new kind of problem occurred. This time Telegram wasn't connecting to the net and so I rebooted. And BOOM, stuck at the boot animation (the four colored points) for no apparent reason.
If I only wiped Dalvik and Cache in recovery, the phone would go past the boot animation, but after the Android logo, it would display only a black screen.
This time, before doing a factory reset, I flashed via fastboot boot, cache, system and vendor, hoping that could solve something for the future.
I have no idea why this is happening. After the new reset, I will try to limit the modifications to /system by not installing Stericson's Busybox and GSam Root Companion app, but I'm still wandering in the dark. It looks like my 5X is possessed.
Please, if you have any sort of feedback or insight, I will gladly listen.
Update: today I had no issues but I rebooted anyway. Result: stuck at bootanimation.
As you English speakers say:"F*ck this sh*t, I'm out".
Yeah, I decided that I'm done with the stock ROM and decided to flash PureNexus ROM in the hope that the **** up I was doing with the stock ROM will never happen again.
Maybe now the mods can close this thread.

Random reboot on custom roms

My T-M G3 reboots randomly when i use a custom rom (LA, Mokee, RR ...etc), is it a hard or soft probleme?
Probablymind it's a soft problem.
¿Have you tried to boot into android without the sim card?
If you have ,you can try wiping the battery stats deleting some files.
And if the problem isn't solved you can try installed first the v10 OF and later wipe and install the rom at least it works for me.
And the last option is change the battery, but isn't 100% probably

Random Reboots on Custom Roms

I have no idea what causes this as when I take logs it does not happen at all... But this has definitely happened numerous times while I'm daily driving a custom rom. The same thing happens when on Android Pie and 10.
I've had no reboots at all when using stock rom. Any ideas would be appreciated.
Attached are the screenshot of some logs and it might not help at all.
Log File
Here is the log file till the phone reboots by itself
Started to happen to me too
It started to happen to me too, and it is happening across factory resets, full wipes and stock and custom ROMs.
I think the hardware is starting to fall ...

Categories

Resources