Database Users

[Q]New kernel refuses to boot, how to get a rescue?

OK, this mat have been asked many time, but none of the thread I found applies to my case.
My device is Nexus 7 16Gb Wifi, the internal ROM is stock 4.1.2 (I cannot use 4.2.2 because of a backward compatibility issue for an app I have to use)
The recovery is the latest TWRP 20030227 version, with MultiROM bootloader 4.18. An armhf raring build of Ubuntu is also installed in the internal sdcard and all have worked fine until I tried to flash a alternative kernel.
The new kernel I flashed is the M-kernel mr1.1. I flashed it by booting into recovery and chose to install the M-kernels zip file from there. After I have got a kernel flash successful message I chose to reboot system. Then the weird thing began: at first the device seems to be booting because I saw the usual Google logo and then it turned into the boot animation with a colorful cross in the middle of the screen. But then on nothing seems to follow. The boot animation persists forever. I hve also noticed that during the initial boot it somehow skipped the step of choosing ROMs as usual (because I have Ubunto installed), so I also lost the choice of booting into Ubuntu.
I have to press the power button for more than 10 seconds to power off the device. Then I tried to boot into fastboot mode and recovery mode, both works file, so it still looks not bad. I have kept a copy of my working patched kernel which is kernel_kexec_41-2.zip. Booting into recovery and using the command
adb push kernel_kexec_41-2.zip /sdcard/
I managed to copy this zip into the device. Then, once again, I tried to flash this old kernel by installing it in the recovery. The installation exited with a success. However, when I tried to reboot the device, it is still stuck on the boot animation screen. No choose ROM screen either. So, I am totally lost. Can anybody give some hint on where I was doing wrong and how can I get my device working again without totally reflashing a stock rom and loosing all data I have installed previously? Many thanks.

Any helps please.

Let me update the situation. Tried to wipe cache/Dalvik and reflash the kernels (both the original and the newly downloaded omega3 kernel, both changed nothing -- always stuck in the boot animation. Tried MultiROM->Advanced->Inject curr.boot.sector, the screen allowing to choose rom reappeared and from there Ubuntu boots correctly. However, If the internal ROM is chosen in that screen, the device reboots and stuck in the boot animation screen again.

How about if you make a backup?
Then - no matter what follows - no matter what experiments you do - you can always restore just the /data partition. Or any of the other partitions.
Frankly, you should have done it already, but nothing is stopping you from doing it now.
Backups give you power - and freedom - to experiment with very few risks.
good luck.

Thanks! I didn't realize that I can still make a backup even the system is already broken. Did the backup for the data partition and reflashed the stock rom, it now boots ok. Even though I still lost the desktop configuration and the Ubuntu installation.

instanton said:
Thanks! I didn't realize that I can still make a backup even the system is already broken. Did the backup for the data partition and reflashed the stock rom, it now boots ok. Even though I still lost the desktop configuration and the Ubuntu installation.
Click to expand...
Click to collapse
Had it happened that you still had a bootloop after dirty-flashing /system and/or boot (without doing the custom recovery "factory reset" wipe of /data exclusive of /data/media), a backup can still save your bacon: it can be restored and then manually:
- all system app related /data/data/ and /data/app-lib/ folders removed
- all system app updated .apks in /data/app/ deleted
- wipe dalvik-cache
This leaves all market apps and their data intact while starting from scratch from with the base ROM's system apps. Probably doing that reduces the chances of boot loops.
UID mismatch troubles can still occur if you are coming from a "debloated" ROM and dirty-flashing something like a stock ROM (where there are more system apps than in the prior ROM which generated the /data partition); but I think that TWRP's "fix permissions" should take care of that.
But anyway - backups give you flexibility.

Oneplus2 Stuck on Animation

I have a US Oneplus2 that is stuck on the animation when it boots. I can get into TWRP and Fastboot, latest TWRP works and can also use an older version that I had.
I made a TWRP backup that I pulled off onto another computer. I then installed OOS 3.5.1 (I think) to do some testing. Once I was done testing, I decided I wanted the latest lineage as my backup was a 6 month old version of the latest at that time. I used TWRP to wipe the data, cache, and system to then install the latest Lineage 14.1 11/24/17 and gapps mini and micro (tested both). It gets to the lineage boot animation and the ball goes back and forth forever. I have left it over night and it's still going. I have rebooted the device, installed lineage several times, moved to 12/1/17 today with the same results.
After messing with it for hours and days, I decided to just put the TWRP backup back on the phone and then update from there. Well... my custom animation is load but the animation is also going forever.
Looking for some help on what might be wrong with the phone, thanks.

Make sure everything is formatted as ext4 and update firmware to 3.6.1 just to rule it out.
I would use the latest twrp.
I go to format tick all the boxes and clear everything then go to reboot > recovery. Once back in twrp copy the ROM and gapps across from pc install ROM and gapps together, wipe cache and dalvik reboot.

I'm in the process of doing that now.
The TWRP that I'm using is 3.1.1-0 which looks to be the latest. I am working with OOS 3.5.8 but will look at downloading 3.6.1. I am working to get Lineage 14.1 on there once everything is stable.
I ran into another weird is when using the qualcomm recovery tool:
My method is to enable ADB, enable OEM Unlock, enable Advanced Reboot.
Reboot into fastboot
Fastboot oem unlock: is successful
Fastboot reboot
I then go through renabling ADB and Advanced Reboot, OEM Unlock is still enabled.
I then reboot into fastboot
Fastboot flash recovery twrp-3.1.1-0-oneplus2.img
This completes successfully and then I fastboot reboot.
I have tried several times to get into TWRP but I keep getting the stock recovery.
I have tried to reflash recovery but nothing ever changes.
Is there possibly something wrong with the OEM unlock that says it was successful?
How do I go about troubleshooting this?

Ok, I fixed that and install OOS 3.6.1 and then was able to install TWRP 3.1.1-0.
I then wanted to install Lineage 14.1:
I then formatted Cache, System, Data, Dalvik... everything but internal. Should I wipe internal as well?
I copied over linage 14.1 and open_gapps for the same build micro.
I now am back to getting the Lineage Boot animation.
Thanks for helping since I'm trying to get Lineage to boot.

cyrus104 said:
Ok, I fixed that and install OOS 3.6.1 and then was able to install TWRP 3.1.1-0.
I then wanted to install Lineage 14.1:
I then formatted Cache, System, Data, Dalvik... everything but internal. Should I wipe internal as well?
I copied over linage 14.1 and open_gapps for the same build micro.
I now am back to getting the Lineage Boot animation.
Thanks for helping since I'm trying to get Lineage to boot.
Click to expand...
Click to collapse
Internal doesn't really matter to be honest, did you check they data and system are formatted as ext4.
It is in twrp advanced wipe options.
Did it ever boot ?

I did doubt check the data and system are formatted as ext4.
I let it sit for 3-4 hours and didn't see any progress.

Try a different rom. There are a lot of lineage based roms around.

I tried that and am getting the same results. Even if I flash a full TWRP backup from a time when I had it known to be working it happens.

I've tested this with 3 different roms now. My latest attempt has been to update TWRP to 3.2.1 and then install lineage 14.1 20171208. I also tested with Paranoid and Carbon because they were near the top of my list not because I know anything about them.
The phone just never gets past the boot animation. If I reboot to recovery is there a log I can pull to see what the issue is?
Thanks

Would like to see if anyone has any thoughts. If I run OOS I can use the phone but as of right now I can't use any other rom.
Is there any advanced fastboot or wipes that can be done to get it to boot. Is there any type of debugging that will show me what's happening when it tries to boot.

Just trying to bump this, I really need a way to debug this problem. Besides running OOS, I have a feeling this device is bricked and the mega unbrick guide doesn't work.
Also looks like if I try to put Kali on top of the base 3.5.8, the phone goes into the animation loop. So any change after OOS on the device puts it into an animation loop.
Is there a way the system or boot locked? Even thought I can TWRP anything onto the phone without errors.

Hey!
I've got the same issue it seems, phone just sticks to boot animation when flashing any other ROM than OOS 3.6.1.
Any update?
EDIT :
problem was with the persist.img
Flashed a different firm file and it was resolved

cyrus104 said:
I have a US Oneplus2 that is stuck on the animation when it boots. I can get into TWRP and Fastboot, latest TWRP works and can also use an older version that I had.
I made a TWRP backup that I pulled off onto another computer. I then installed OOS 3.5.1 (I think) to do some testing. Once I was done testing, I decided I wanted the latest lineage as my backup was a 6 month old version of the latest at that time. I used TWRP to wipe the data, cache, and system to then install the latest Lineage 14.1 11/24/17 and gapps mini and micro (tested both). It gets to the lineage boot animation and the ball goes back and forth forever. I have left it over night and it's still going. I have rebooted the device, installed lineage several times, moved to 12/1/17 today with the same results.
After messing with it for hours and days, I decided to just put the TWRP backup back on the phone and then update from there. Well... my custom animation is load but the animation is also going forever.
Looking for some help on what might be wrong with the phone, thanks.
Click to expand...
Click to collapse
OOS does not refuse to boot if a mountable partition is corrupt. This is not the case with lineage. If a mountable partition is corrupt and the corresponding fstab entry does not allow lineage to format and somehow mount it then init never proceeds
Try flashing this file: https://glassrom.botstack.host/firmware/oos-3.6.1-firmware-signed.zip and try again
Note that this file reboots the device after the flash is done so don't use twrp queue to flash this file. Flash this file last
---------- Post added at 17:45 ---------- Previous post was at 17:34 ----------
Alternatively this is a method I don't recommend to beginners because they accidentally give twrp logs to devs without realising it
You can get logs by making the forcing the device to "crash" through the power button
Here's how it's done: you boot the non-booting ROM and wait for about a minute. Then press power + volume down while it's on the bootanimation. You have to hold it until you see the oneplus logo and boot to twrp
TWRP's kernel will recover the last booted kernel's log from ram and place it in /sys/fs/pstore
First you have to open the log yourself to check if it's valid. The file is console-ramoops-0. All other log files in that location are invalid for your specific issue
Now for an ordinary user this is hard. They can't tell if the log is a recovery log or a ROM log. Since we're dealing with official lineageos we assume selinux would be enforcing
You want to search for this string "permissive=1". On Linux just do cat console-ramoops-0 | grep "audit" (quotes are part of the command)
If you're on windows then you can download Linux and get the logs. Stop bothering me
If you see the string "permissive=1" in the log you have accidentally fetched a recovery log
Go back and boot again and wait for about a minute if selinux is permissive
The string should read
"permissive=0"
That means selinux is enforcing and this is indeed a ROM log
Send this log here

Hello,
Was this problem ever solved? I am experiencing the very same thing with every single ROM i have tried so far. TWRP is installed, I can install all ROMS but when I try to boot the phone, it just won't get passed the booting animation.
Thank you

[Q] phone keep booting into recovery

so i just doing a clean install of the beta 3 rom, i did follow the instruction that written in the thread but some how after installing the update when i'm about to reboot into system it keeps rebooting into the recovery. so i decided to clean wipe and re-flash the rom, and some how it says that there's no rom installed. i've tried to install other custom rom like, LOS 15 and Liquid Remix, but it's still the same, keep booting to recovery and showing that there's no rom installed. plz help...

Go to twrp > wipe > format data > yes
Then transfer oos OB 3 to your phone, use adb push command is better than copy paste(not sure why because sometimes i copy pasted into phone, sometime it bootloop or storage not recognised)
Flash it, then flash magisk 15.2. then reboot. It should work fine. Unless you use a not compatible twrp version.

thanks for ur solution before, but can u tell me the compatible twrp is, cuz i'm using the twrp 3.2.1 by blu spark and it keeps booting into recovery

You need to flash no verity zip. If you are decrypted.

"You need to flash no verity zip. If you are decrypted. "
Thanks god for this comment, use about 2 hours digging around forums and re-flashing, wiping, trying diffrent TWRPs, different roms. And when I found this comment I just isntalled the zip and it worked within 10 seconds.

Bootlooped after install of Lineage, twice!

Hey all,
Phone is new to me, t-mo version. Did the international conversion, unlocked the bootloader, installed TWRP 3.3.1.1.img. All with minimal issues. Installed the 20200121 nightly of LOS successfully, but it powered off a few minutes after getting through the setup menu. Bootlooped. I may have gotten it out of the bootloop with the vol up+down trick from the msmdownloadtool trick, or something, cause I got the screen to turn off and left it for the night.
Tonight, the phone was totally dead, but I was able to start over with the (patched) msmtool I used initially. All good. Went through the same steps and got TWRP and LOS installed. This time I used last nights nightly 20200123. All set for a minute, before it bootlooped again.
Here's some details that might be useful:
The phone powered off after unplugging it. This is when the bootloop started, I can't be sure it was after dissconnecting each time, but at least the last time. The battery was >80%. I also managed to get it to boot into LOS after the most recent bootloop, for a few minutes, and it powered off without being connected or disconnected. So probably not related.
I did a system wipe, along with the format, as recommended in the LOS installation steps from them
The system wipe maybe wasn't a good idea??
I tried to sideload LOS.zip, which seemed to work fine according to my terminal, but it warned me that I had no OS installed when I went to reboot. So I adb pushed LOS and installed. I got the same no OS warning, but rebooted anyway this time. LOS started up fine, for a few minutes, before powering off and then looping.
Could I have 2 instances conflicting??
Nothing else installed yet, not root, magisk, or anything yet.
I shut it down this time with a vol up + power, which worked. I'm done for tonight, but I would appreciate any ideas on what may be causing this so I can give it a third go tomorrow.
Thanks!

try this
BeansBeanson said:
Hey all,
Phone is new to me, t-mo version. Did the international conversion, unlocked the bootloader, installed TWRP 3.3.1.1.img. All with minimal issues. Installed the 20200121 nightly of LOS successfully, but it powered off a few minutes after getting through the setup menu. Bootlooped. I may have gotten it out of the bootloop with the vol up+down trick from the msmdownloadtool trick, or something, cause I got the screen to turn off and left it for the night.
Tonight, the phone was totally dead, but I was able to start over with the (patched) msmtool I used initially. All good. Went through the same steps and got TWRP and LOS installed. This time I used last nights nightly 20200123. All set for a minute, before it bootlooped again.
Here's some details that might be useful:
The phone powered off after unplugging it. This is when the bootloop started, I can't be sure it was after dissconnecting each time, but at least the last time. The battery was >80%. I also managed to get it to boot into LOS after the most recent bootloop, for a few minutes, and it powered off without being connected or disconnected. So probably not related.
I did a system wipe, along with the format, as recommended in the LOS installation steps from them
The system wipe maybe wasn't a good idea??
I tried to sideload LOS.zip, which seemed to work fine according to my terminal, but it warned me that I had no OS installed when I went to reboot. So I adb pushed LOS and installed. I got the same no OS warning, but rebooted anyway this time. LOS started up fine, for a few minutes, before powering off and then looping.
Could I have 2 instances conflicting??
Nothing else installed yet, not root, magisk, or anything yet.
I shut it down this time with a vol up + power, which worked. I'm done for tonight, but I would appreciate any ideas on what may be causing this so I can give it a third go tomorrow.
Thanks!
Click to expand...
Click to collapse
(BASE STOCK ROM)
OnePlus6TOxygen_41_OTA_063_all_2001032024_215eea3f e7c64e37.zip (BETA4)
whatever the rom requires(10.3.0) however the Q beta 4 works just fine, havent found any real bugs / newer security patches etc.
(CUSTOM ROM)
Latest rom that will work with BASE and TWRP decryption
(latest TWRP )
twrp 3.3.1-31 zip
(Latest)
Magisk Canary . Zip
(Latest)
open_gapps - Q
(Latest)
custom compatible kernel
(Latest)
NanoDroid - with con/fig read alter installation notes
(&)
India_Fake_Partition_Deleter
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE / U WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MYNE)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
From dirty or clean system - to - clean flash
in cmd type
fastboot boot twrp.img
Install twrp installer.
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!)
install OOS(BETA4).zip / TWRP installer
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
Flash TWRP installer
- - reboot to recovery - -
Flash Magisk
BOOT UP System
- - reboot back to recovery - -
Choose Reboot Option / (CHANGE YOUR SLOT) / Back / Reboot Recovery
Flash Magisk.
Reboot system
SETUP ROM
/////////////////////////////////////\OPTIONAL/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
- - REBOOT TO RECOVERY - -
----------------------------------------------------------------------------------------------------
STEP *( .=./ )*
Flash GAPPS
Flash India_Fake_Partition_Deleter
Flash NanoDroid (With prefered pre-configured setup/overlay/apps files placed)
Flash Custom Kernel
Re-Flash Magisk again
Click - WIPE DALVIK & Reboot system right after
------------------------------------------------------------------------------------------------------
- - REBOOT TO RECOVERY - -
Choose Reboot (CHANGE YOUR SLOT TO THE OPPOSITE SLOT)
- - REBOOT BACK TO RECOVERY - -
REPEAT STEP " *( .=./ )* "
-------------------------------------------------------------------------------------------------
GAME OVER
1up
THIS is EXTENSIVE but will work for any particular rom setup for a/b devices based on Q
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
just follow install guide download latest linageos and gapps from open gapps. and latest magisk and after flash gapps if you cannot sign into a google account then you need to factory reset both slot in system settings menu and then just reinstall magisk and kernel settings modules etc
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
just switch slots in cmd or via twrp and reboot system and factory reset wipe all via the settings in the booted system, not twrp

I'm a little slow..
I got the phone back to factory with the msmtool, so I'm ready to do this! I get the general idea, but for a few of these, can you ELI5. Thanks so much for taking the time to help me out.
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE / U WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MYNE)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
From dirty or clean system - to - clean flash
in cmd type
fastboot boot twrp.img
Install twrp installer. Do I just find the zip in the file structure in twrp and install? I'm at this step in twrp and I don't see how to install it. Previously I had `adb push twrp.img /storage/` so that I had a file I could find and install. If it's already there just from `fastboot boot twrp.img`, I can't seem to find it.
--solved this by pushing the twrp-intaller.zip to /storage, and then installing. It did the expected installation to both a/b
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
I went to `mount` and checked all the boxes. Then went back to `wipe advanced` and checked all those boxes. Now I'm stuck at the fastboot screen and can't boot or start. :crying:
I can't do a `fastboot boot twrp.img either. Any suggestions before I blow it away with the msmtool again??????
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!) How was I doing it wrong? Or do you mean that these steps just now are the only mounting that should be done?
install OOS(BETA4).zip / TWRP installer What command should I use to move it from my pc to the phone? `adb push .zip storage` ?
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer Do it twice, exactly the same? Is this so it's on both slots?
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage. What command should I use for copying? Like above `adb push <files> storage`?
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
[/COLOR]just follow install guide download latest linageos and gapps from open gapps. and latest magisk and after flash gapps if you cannot sign into a google account then you need to factory reset both slot in system settings menu and then just reinstall magisk and kernel settings modules etc
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
just switch slots in cmd or via twrp and reboot system and factory reset wipe all via the settings in the booted system, not twrp
Not sure what you mean by this part here. I wasn't planning on installing gapps. I'm confused about the reseting both slots. Is the idea that I did the install twice above, so that it's on both a/b slots and I'd have to reset both if there's a problem?
Click to expand...
Click to collapse

Custom ROM works perfectly, after a reboot, bootloops

The title says it all, i have been using a custom ROM (Havoc OS) and the LolZ kernel with magisk, it works perfectly but as soon as i restart the system. it bootloops and i have to keep restoring, re installing and so on until it finally works.
Does anyone have an idea of what might be going on?
device: Samsung Galaxy Note 3 SM-N9005 hlte
Even more info incase you need it:
Steps to create problem for me:
Install Havoc OS
Install LolZ kernel
Install Magisk
Boot and use
Restart
(problem comes)
Steps to fix (Before):
Install Havoc OS
Get rid of remainders of magisk for lolz kernel
Install LolZ kernel
Install Magisk
Restore Data partition
Reboot to System
Right now nothing is working, ill try another way and update this
also, i noticed that instead of storage being in
/storage/emulated/0
its now in
/sdcard
according to twrp
Ok this should be the actuall way excluding ALL ways:
1. Reboot to cause the issue lol
2. Go to recovery (twrp recommended)
3. repair the system partition and data partition.
4. Shut down then connect to cable.
5. Let it boot, if it dosent boot to kernel and goes to recovery, try reformatting, 6. restoring, dont touch what you dont want lost etc then start from step 3 (If it goes to charging anim, ignore this step)
6. Let the charge animation play
7. after the screen turns off / you know the charging animation played
8. Boot via power button
9. Works!
Now i really feel a tiny bit better when rebooting my phone XD
If it bootloops after step 8, try reformatting, wiping, repairing, restoring etc-