I have the kernel log if anyone wants to take a look at it
Related
Does anyone know if there are scripts that run at boot and shutdown, and where are they?
I get this error then a few more lines scroll on, then it shutsdown. This is with generic-sdimage... cwm 3.0.2.1. I can't boot into recovery either by holding down the "N" when powering up. I have to use Rom Manager. I have seen the thread on a cwm "fixer" but things change so fast and that post is pretty old. Any else seen this modprobe error?
I know that you can change the moboot default option but I was curious if it was possible to skip the boot select screen completely and boot straight into Cyanogenmod? I have no reason to boot into WebOS and can boot into recovery via the power option inside Android. It just adds polish to just see the boot splash first when the device is switched on plus it saves a few seconds of waiting around.
Thanks!
I think you could set timeout to 0.
Unfortunately, that just turned off timeout all together.
Anyone have any other ideas?
You could try deleting moboot but I don't recommend it. Might work, might break things.
Sent from my SPH-L710 using Tapatalk 2
Please mind that if your ROM becomes unbootable and you can't boot straight to the recovery, it will be more problematic to fix.
However, I think it is possible. There's a possibility to set the next image to be booted by a text file on the boot partition. I don't remember the exact name and content, but this way android makes the moboot reboot straight to the recovery. Moboot reads the file, boots the desired image and deletes the file. So you would need to create such file for booting the android image and make that file somehow permanent. I don't think changing permissions would be enough, but you could recreate it every (re)boot by some script.
I was going to point out the same thing pojir said above me. Sure, you could boot into recovery from CM9 but if you cant boot into CM9 and are stuck in a boot loop or something, then what? Just set the timer to 1 second and have it boot to CM9 by default. It shouldn't be a big problem to wait 1 second before booting begins.
As most of you know that twrp takes a longer time to load on f2fs this is due to some bug but today we caught a new issue when I decided to unlock the bootloader and flash twrp to use lineageos o.o but but it got stuck at splash screen so I decided to go the #twrp for support at first they said it normal so I waited for an hour it was still stuck ? okay wtf ?
so lets investigate
Code:
<Dees_Troy> we're talking about the 3T, right?
<jcadduono> <11>[19700220_12:31:55.318574]@0 init: no such service 'qseecomd'
<jcadduono> WTTTTTTTTTTTTTF.
<jcadduono> that would certainly explain why its waiting forever
<jcadduono> oh i see
<jcadduono> androidboot.hardware=unknown
<jcadduono> your bootloader is not sending CMDLINE from aboot image
<Zenn> is this normal?
<Zenn> possible my bootloader is something new from oneplus?
<jcadduono> no, it is absolutely not
<jcadduono> flash 4.0.2 full OTA from twrp thread in oneplus stock recovery
jcadduono> maybe theres a fastboot command that enables/disables cmdline, try fastboot oem cmd_show
<jcadduono> and paste output on gist
<jcadduono> fastboot oem cmd_show
<Zenn> waiting for device
<jcadduono> you have to go into bootloader mode, ex. adb reboot bootloader
<Zenn> FAILED
while a temporary way was found to got me booting
Code:
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
if you encounter any issue please hope onto #twrp or contact @jcadduono
Code:
18<jcadduono18> i submit more question to oneplus on what flag causes this to happen and proper way to disable it
@Sultanxda @franciscofranco @koenkk @ujwal.p @apascual89
another issue to bring to light is when I previously thought there was an issue with Ext4 and recommended everyone to flash that fstype swap zip.
the issue experienced was the "reboot" buttons causing TWRP to crash and restart rather than reboot. this was actually due to the addition of the TWRP app installer!
this commit fixes it: https://gerrit.omnirom.org/#/c/21661/
as you can see, what's happening is that /data/app didn't exist on an empty data partition, and so the DIR* was NULL, but there was no NULL check before readdir was called on it. This caused a NULL ptr exception and crashed TWRP when looking for the TWRP app.
you can get past this by simply disabling the "ask to install twrp app" option in the settings page
there should not be any FS corruption, but that was a worry I had initially due to TWRP crashing from this problem and creating multiple sdcard mountpoints over each other. this issue should be fixed soon too...
credits to @mad-murdock for finding this one for me
I'm in need of assistance in getting my Pixel 5a back up and running. I was running GrapheneOS with a locked bootloader so I'm limited on what I can do to fix it. Last week I got an OTA update and after that I started getting random boot loops, but then after about 10 restarts my phone would work, it got to the point where it would boot to the login screen but then restart as soon as I try and login. I tried to do a factory reset and get the following error:
"ERROR: recovery: [libfs_mgr]Unable to enable ext4 verity on /dev/block/by-name/metadata because /system/bin/tune2fs is missing - Formatting /data... - Formatting /metadata... - Wiping Ttan M... - ERROR: libnos_datagram: can't send spi message: Try again (I get this line 25 times)
I have tried to sideload the latest OTA update from GrapheneOS, after that I got it to boot to the start screen (like setting up the phone for the first time) I can sometimes get a few screens into it before it restarts and starts boot looping again.
It seems to me that my file system is corrupt or I'm missing the file it says in the error above "tune2fs", how can I check my filesystem or fix the missing/corrupt file?
I have posted this on GrapheneOS's forum and have gotten little to no help and I have always received excellent help here with my older phones.
Any help/advice is greatly appreciated, as of right now I have a useless device.
Thanks