Hello,
To preserve battery life, I have enabled that my OnePlus shuts off at night and boots up in the morning so that I can hear my alarm clock.
But every now and then, I miss my alarm because the phone fails to boot properly, and instead it boots into recovery. I'm then greeted to the following screen:
Boot reason : init_user0_failed
Unable to parse kernel log. For more debug information,
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
https://imgur.com/Qplapb2
If I reboot it's fixed, but it's quite frustrating since it comes back every now and then.
Bootloader: unlocked
Rooted: yes, Magisk stable
Magisk modules:
Busybox for Android NDK
MagiskHide Props Config
OOS Native Call Recording Enabler
Systemless Hosts
Kernel: EX Kernel
Recovery: stock recovery
I tried to use the "adb pull /mnt/vendor/op2/rbr_log" command, but I got "adb: error: failed to stat remote object '/mnt/vendor/op2/rbr_log': Permission denied"
Anyone knows what the cause could be and how to fix it?
My device will randomly boot into recovery mode but only if I power off/restart. I can't figure out why
State.of.mind said:
My device will randomly boot into recovery mode but only if I power off/restart. I can't figure out why
Click to expand...
Click to collapse
Does your phone also has any of the same characteristics? Like the same custom kernel, also rooted with magisk, etc?
ziedje said:
Does your phone also has any of the same characteristics? Like the same custom kernel, also rooted with magisk, etc?
Click to expand...
Click to collapse
I have Magisk installed and I use Omega Kernel. I don't get the same error but at random times it boots into recovery mode.
State.of.mind said:
I have Magisk installed and I use Omega Kernel. I don't get the same error but at random times it boots into recovery mode.
Click to expand...
Click to collapse
I have not experienced the issue anymore since the latest Magisk update. You too?
ziedje said:
I have not experienced the issue anymore since the latest Magisk update. You too?
Click to expand...
Click to collapse
Are you using beta or stable?
State.of.mind said:
Are you using beta or stable?
Click to expand...
Click to collapse
Stable
I have the same issue, did you ever end up fixing it?
Stick with the stock kernel, the others offer very little in my experience.
Not to mention that I find it odd that you would need your phone to do this?
Besides the fact that you could need your phone in an emergency, you should only be losing 1-2% overnight anyway, pop it on DND or even airplane mode and you're done..
Just seems unnecessary I'm my opinion.
If you have to have this script running then maybe try with stock kernel.
Related
i just installed this kernel
http://forum.xda-developers.com/showthread.php?t=1804374
and since then, i have had multiple problems. multiple things force close, programs dont load, everything hands (like when i hit power off, it just hangs with the circle then everything freezes up and i have to hold power button for 15 - 20 secs to turn off device).
cannot get into recovery - everytime i try to from bootloader it hangs at the google page and if i try to get into from rom manager, rom manager doesnt even load
does anyone have any suggestions?
thanks in advance!
bump.. since i changed the post.
joshtb86 said:
i just installed this kernel
http://forum.xda-developers.com/showthread.php?t=1804374
and since then, i have had multiple problems. multiple things force close, programs dont load, everything hands (like when i hit power off, it just hangs with the circle then everything freezes up and i have to hold power button for 15 - 20 secs to turn off device).
cannot get into recovery - everytime i try to from bootloader it hangs at the google page and if i try to get into from rom manager, rom manager doesnt even load
does anyone have any suggestions?
thanks in advance!
Click to expand...
Click to collapse
Have you tried flashing the stock kernel via fastboot?
comminus said:
Have you tried flashing the stock kernel via fastboot?
Click to expand...
Click to collapse
can you link me to it? the only one I can find is from another post and it includes init.d support.
thanks!
fck.. this is not good. I tried using wugs toolkit and flashed the stock kernel with init.d support but it got messed up somewhere after it installed a temporary recovery and now it boots straight into recovery and I cannot boot into the actual tablet. I just flashed the stock 4.1.2 rom here
http://forum.xda-developers.com/showthread.php?t=1929270
and still cannot boot into the tablet its booting straight to recovery
can anyone help?
joshtb86 said:
fck.. this is not good. I tried using wugs toolkit and flashed the stock kernel with init.d support but it got messed up somewhere after it installed a temporary recovery and now it boots straight into recovery and I cannot boot into the actual tablet. I just flashed the stock 4.1.2 rom here
http://forum.xda-developers.com/showthread.php?t=1929270
and still cannot boot into the tablet its booting straight to recovery
can anyone help?
Click to expand...
Click to collapse
Flash back to stock http://forum.xda-developers.com/showthread.php?t=1907796
comminus said:
Flash back to stock http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I think I was able to flash the factory stock image because I finally got it to boot, but its in the "android is upgrading" phase, so I will post after if this worked or if I tried the above.
thanks!
now it is intermittently booting up and intermittently booting straight into recovery.
I believe ive fixed it. I booted back into the OS 3 times and no booting into recovery. thanks!
joshtb86 said:
I believe ive fixed it. I booted back into the OS 3 times and no booting into recovery. thanks!
Click to expand...
Click to collapse
I'm having the same issue now after flashing faux's kernel. You had to reflash a stock image from the toolkit to fix it?
VanillaG0rilla said:
I'm having the same issue now after flashing faux's kernel. You had to reflash a stock image from the toolkit to fix it?
Click to expand...
Click to collapse
yes except it took multiple multiple times to work and actually stick. i thought i had it and it was booting fine and it is booting fine now, but my performance is abysmal. its like 25% of what it was.
i have no poewr because of hurricane sandy (on coimputer at work) so i cant even use it or update it. i am strongly considering OEM relocking the tablet and starting over from scratch. performance is almost back to the lag we had before 4.1.2 was released.
Hello,
I have tried searching but haven't been able to find a similar issue for any android devices (amazing right?). My nexus 7 will not respond to any soft reboot. From power menus to terminal to factory reset (yes including from ROM recovery and the like). It will reboot from the 10second press, but as we know that is pretty ineffective considering the nexus 7 has that bug where you can't access recovery from boot loader. I have tried connecting to a PC to force recovery, Nada.
So now I am out of idea. Also, for the next 2 weeks I don't have a PC, only a gnex and nexus 7...
Any help appreciated.
update your bootloader and recovery, that bug has been fixed. what rom are you running, every single reboot/power off option works here.
I can't update it without being able to reboot. And I know its not a common issue.. hense why I ask for help... I am not reporting a issue, I am asking for ideas... thanks for the tremendous comprehension though
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
MatAuc12 said:
I can't update it without being able to reboot.
Click to expand...
Click to collapse
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
MatAuc12 said:
Oh, I forgot an important bit of info. It started happening after a kernel update (to fauxs latest) and now most programs that require root will be laggy or crash. And every 10sec reboot I do, apps "optimize" every time and every action, including downloaded files are missing since the last boot. (ie, I am always at the exact same point of the first boot after the kernel flash)
Click to expand...
Click to collapse
let the battery die and power itself off, then charge it. flash another kernel for sure.
simms22 said:
let the battery die and power itself off, then charge it. flash another kernel for sure.
Click to expand...
Click to collapse
I did let it die for cold boot and again, understanding my problem means since I can't initiate a reboot or get into recovery I cannot flash anything
BillGoss said:
Are you saying that you can't get into fastboot by long-hold power and then hold vol down as soon as the device restarts?
Sent from my HTC Desire S
Click to expand...
Click to collapse
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
MatAuc12 said:
Exactly. That is extremely strange behavior and complexes me even more than a soft brick even though the device works
Click to expand...
Click to collapse
boot pressing volume down while pressing the power button into the bootloader, flash a different kernel via fastboot. you can flash franco kernel in fastboot, since it is in boot.img form, or extract the stock boot.img from a stock rom and fastboot flash that. ive had similar behaviors with test kernels, faux forgot something in the kernel. then download and flash the newest bootloadee to fix your recovery from bootloader bug.
Try simms22 approach first.But if you can't get into fastboot and you can boot into the ROM- then you could try rewriting the boot.img. Get the boot.img/kernel you want and use the dd command to write it.
Warning: you can do serious damage with the dd command.
If you need some help with this, let me know. But I accept no responsibility if things go terribly wrong.
Sent from my Nexus 7
I had flashed CM10 but forgot to reboot into fastboot and boot the CM10 kernel. As the thing was bootlooping, I was able to successfully do an adb reboot recovery, completely skipping using a USB keyboard and pressing Ctrl - Print Screen - I key combination normally used to get to recovery. Apparently at some point, even if the rom isn't booting, the kernel somehow starts adb. Anybody else have any luck with this or know any reason why this even worked? If this is the normal way for android to boot, maybe it would be possible to still get into recovery even if we flash a different kernel.
hecksagon said:
I had flashed CM10 but forgot to reboot into fastboot and boot the CM10 kernel. As the thing was bootlooping, I was able to successfully do an adb reboot recovery, completely skipping using a USB keyboard and pressing Ctrl - Print Screen - I key combination normally used to get to recovery. Apparently at some point, even if the rom isn't booting, the kernel somehow starts adb. Anybody else have any luck with this or know any reason why this even worked? If this is the normal way for android to boot, maybe it would be possible to still get into recovery even if we flash a different kernel.
Click to expand...
Click to collapse
Interesting I wonder if its repeatable? I guess its will be hard to test unless you already messed up, nobodys gonna mess up on purpose just to try this out without a hardware recovery option but maybe someone who messes up on accident will report back here on what they found out.
Wasn't able to repeat it on the Ouya kernel with CM ROM installed but it seems to work all the time if you get a boot loop in CM10 kernel and CM ROM. I'm still not feeling safe enough to actually flash the CM kernel, so I am still using fast boot to boot the kernel from a laptop.
On a side note, I do have xbmc set up as my launcher and have list of working skins that can launch android apps from. Once I figure out how to get the crazy CPU usage I am getting worked out I plan to make a guide for a full media center.
Hello, this is my first post here and I have searched for a similar post or issue but have been unsuccessful finding anything.
Please forgive me if I have posted in the wrong area, missed a solution somewhere and/or have not explained anything correctly/clearly.
My Nexus 7 (2012) (I installed Cyanogen on it (and updated it once) through their installer and it has run perfectly for months) started rebooting randomly one morning. I turn it on and it seems to be normal, then it will suddenly reboot. The time between reboots varies ranging from 30 seconds to a few minutes. I can not install or update any apps and any settings changed are reset back to what they were previously upon reboot. I have tried a factory reset and while it appears to wipe everything (all caches and data) when I reboot it is the same as before the reset (I also receive this message (after all other processes are complete) during the data wipe "E: unknown volume "/sdcard/.android_secure" "). I am able to turn on developer options but then the random reboot occurs and it is turned off. I have plugged it to my computer and see it listed, but can not access anything on it.
My intention is to wipe it using my computer (fastboot?) but I am at a standstill due to the rebooting and being unable to turn on developer options.
Any ideas or suggestions would be greatly appreciated.
Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.
kcipopnevets said:
Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.
Click to expand...
Click to collapse
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.
pdn190 said:
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.
Click to expand...
Click to collapse
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?
kcipopnevets said:
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?
Click to expand...
Click to collapse
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.
pdn190 said:
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.
Click to expand...
Click to collapse
You can always try. Also make sure you check md5 before flashing, that may explain why stock didn't flash correctly.
And I still can't get anything to work. Most recently I tried using wugfresh and EVERYTHING works except when it writes bootloader.img at the start. I feel like I am close but then it reboots back to cyanogen. lol
Hi Guys,
i have spent the last week looking around for information and i cant find a fix, wondering if people could help please!
Im a long time user of custom roms, have had customs on the HTC Hero, S3 and now my S4... and i had the CM12.1 nightlies installed, running TWRP and the CF AUto Root.
It ran perfectly for a few weeks or so, even with the OTA updates you get.
I woke up the other morning to the phone misbehaving so i thought i would check and now i dont have Root access at all. Super SU, TWRP and even root checker all confirm no root access.
I have wiped the phone, reinstalled root, then TWRP and then the latest CM12.1 nightly and whilst it boots into the OS, i still dont have root.
Can anyone assist please? no root seems to cause hell!
You have a big misconception about rooting a custom rom.
CF auto-root is ONLY for stock TW rom. It's should NOT be used with CM or ANY other custom rom.
Root is standard in CM, it's only disabled. It can be enabled trough devoloper options.
- To enable Developer options go in Settings->About device and press "Build number" for 7 consecutive times.
- Then go in Developer options and enable root.
After that you can install SuperSu from the playstore (but it's not required). It would recommend it though.
Lennyz1988 said:
You have a big misconception about rooting a custom rom.
CF auto-root is ONLY for stock TW rom. It's should NOT be used with CM or ANY other custom rom.
Root is standard in CM, it's only disabled. It can be enabled trough devoloper options.
- To enable Developer options go in Settings->About device and press "Build number" for 7 consecutive times.
- Then go in Developer options and enable root.
After that you can install SuperSu from the playstore (but it's not required). It would recommend it though.
Click to expand...
Click to collapse
Hi Lennyz,
rookie mistake from my point eh!
i have just checked root options in dev options and it has 'Root Access' set to Apps and ABD and it still doesnt work?
noodles249uk said:
Hi Lennyz,
rookie mistake from my point eh!
i have just checked root options in dev options and it has 'Root Access' set to Apps and ABD and it still doesnt work?
Click to expand...
Click to collapse
I'ts possible that that is caused by flashing cf auto root.
- Wipe /system (you don't need a full wipe). You can the option somewhere in TWRP.
- Reflash the rom you are on.
- Enable root in developers settings.
- Install supersu from the playstore.
Have you actually tried reinstalling SuperSU? Or force updating the libraries?
I'm having the same issue. But without root, I can't even go into recovery. What should I do to wipe the system and flash the same rom? Please help, thanks.
2080722 said:
I'm having the same issue. But without root, I can't even go into recovery. What should I do to wipe the system and flash the same rom? Please help, thanks.
Click to expand...
Click to collapse
Root is nothing to do with the recovery. Won't stop you from booting into it if you don't have root
Cannot boot into recovery anymore (in CM 12.1)
DSA said:
Root is nothing to do with the recovery. Won't stop you from booting into it if you don't have root
Click to expand...
Click to collapse
Thanks for your help. I'm still quite new to the rooting/flashing ROM thing. The reason I ask that question was I cannot boot into recovery anymore. I tried using the following three ways, 1) holding volume up, center home and power - it still boots back to normal boot; 2) The advanced boot option in CM12.1 used to have the option of booting into recovery, but it's gone now; 3) Using the Cyanogen Update from CM12.1 to run the update within the About Phone section of settings.
Is there another way to boot into recovery? Or, do you think there is something wrong with the CM 12.1? Thanks again.
With the phone switched off, press and hold volume up/power...ignore home button its not needed
Let go when you see blue writing in top left
If that fails, then we can take it from there
DSA said:
With the phone switched off, press and hold volume up/power...ignore home button its not needed
Let go when you see blue writing in top left
If that fails, then we can take it from there
Click to expand...
Click to collapse
I just followed your instruction. I saw the blue writing in top left, then it vibrated once and went back to boot into the regular OS. What should I do next?
Thanks.
2080722 said:
I just followed your instruction. I saw the blue writing in top left, then it vibrated once and went back to boot into the regular OS. What should I do next?
Thanks.
Click to expand...
Click to collapse
hmm... maybe you are holding down the buttons for a little too long...try releasing when you see the samsung logo start appearing
Ok, that worked, thanks. I was back in recovery.
But then when I tried to flash the zip file of the same ROM again, I got an error message saying that the ROM is for certain models: jfltexx, i9505, GT-i9505 etc. and that my device is jfltecan.
My device is a Canadian Rogers Galaxy S4 (SGH-i337M). Initially, I used the CM 12.1 ROM for jfltexx to flash and then the model name in settings became GT-i9505. Also in setting, it's showing the CyanogenMod version as "12.1-20150426-NIGHTLY-jfltexx. So, how can I fix that?