Heyy. Could you help me with this.
So I installed LineageOS 17.1 some weeks ago on my G928F Samsung Galaxy s6 edge+. And have a little problem. My phone is stuck in a bootloop. My phone shutdown because it didn't have battery left. I put the phone to charge and when I tried to power on the phone it just went in a bootloop. I tried several things to make my phone come back. The closest I get was that my boot animation started. But it just went off and again in the bootloop. I tried to wipe cache and dalvik cache. I tried to install boot.img file from the custom Rom zip file. Also I tried to change the boot animation but I can't see the /system/media folder. And I don't want to lose my data. Other detail, I don't want to dirty flash LineageOS 17.1 every time my phone shutdown because there's no battery left. Could you help me?(Sorry my bad English, I'm from Spain)
Nevermind
No problem. I already installed the stock Rom. Because some of important things that the stock Rom has the LineageOs 17.1 don't and that way I make sure that I won't have problems again.
Related
Hi guys,
I have the standard note III 9005 and I had always installed CFWs on it.
I wanted to update to newer 6.0.1 Roms (had 6 roms before) but I seem to have a VERY annoying bug:
I tried to install Temaseks rom and resurrection rom but I had huge issues with it. I got bootloops although I got the newest 3.0.2.0 Team Win Recovery Project
I installed rom, GAPPS (correct version of course 6.0.1) , install rom again then delete cache and then it worked on both roms.
So a simple "install rom, GAPPS, then clean cache" didnt work. I tried to install multiple times until I got the installation! YAY! BUUUT!
Here is the fun part:
If I restarted the phone acidentally or on purpose I got stuck in a bootloop. After that the phone was unuseable again so the installation was useless.
Only solution is to completely wipe and reinstall and experiment with the order of installation until it works!
I did install STOCK rom because I was so freaked out and then went with ODIN the complete rooting guide for clean rooting, but still problem exists.
I tried two other roms but the problem was that while flashing the phone restarted automaticly and then TWRP said no installed rom? ???
Huge thanks for helping me!
New info:
I was able to make the rom work. I restarted and got stuck into bootloop!
I could boot normally after deleting dalvik cache!
But after rebooting I got into bootloop. Tried deleting cache again but this time it never booted properly.
How can I avoid by always deleting dalvik whenever I have to restart my phone (if battery dies or purpose)?
PPS: Stock Rom flash works flavlessly. I am waiting in stock rom until I find a proper solution :"(
Suggest you read the roms faqs and Q&A particularly with regard to TWRP .
I'm trying to flash my Galaxy Tab 4 10.1 3G (SM-T531) to the ROM Lineage 14.1 (lineage-14.1-20170309-0134-UNOFFICIAL-matisse3g).
But after flashing and rebooting my tablet get stuck on a screen with Samsung Logo and two messages on the top:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: Kernel
I've researched a lot and tried a lot of different things, but same result. If I go back to the stock firmware it works just fine.
The procedure a adopted was:
1- Reset to factory defaults on the stock firmware
2- Install TWRP (twrp-3.1.0-0-matisse) through Odin
3- Wipe Dalvik Cache, Cache, System and Data
4- Flash Lineage (lineage-14.1-20170309-0134-UNOFFICIAL-matisse3g)
5- Flash Stock GApps 7.1 (open_gapps-arm-7.1-stock-20170825)
6- Wipe Dalvik Cache
7- Reboot
My main intention on installing this new firmware is because the latest available firmware for my tablet on Brazil is 4.4.2 and I can install a lot of apps (including WhatsApp).
Does anyone can suggest or help me?
Thanks!
that message is normal...
I know... But my tablet is on this screen for almost 45 minutes... I believe that is not normal...
How could I solve it?
Anyone?
I had a similar issue trying to flash crdroid which is LOS 14 based. I wound up skipping step 6 and it worked. Could try redownloading the ROM though
Problem stills, any more tips?
After flashing the tablet stills on Samsung logo, but emits sounds when clicking on Volume Up, Volume Down, Home Button, Power Button... As it is responding normally but the screen keep stuck on Samsung logo.
Hi... any more tips?
Old but, anyone solved this? I tried Android 9 and 11, TWRP 3.6
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
Hello,
I have an i9505 LTE International version (jflte) for about 4,5 years, working perfectly with the latest LineageOS until yesterday when my phone suddenly shut off itself (as like as I removed the battery). I tried then to turn it on again but restarted itself after the LineageOS logo appeared. I thought there was something wrong with the OS, so I've booted to recovery TWRP to flash the same OS again. The strange thing is that TWRP stopped flashing at +/- 20% freezing itself. After that I was not able to boot to recovery anymore.
I removed the battery, SIM card and microSD for about three hours. Tried again only with the battery and was able to install LineageOS again. After booting with the fresh installed LineageOS (I formatted the /system /data /cache partitions) the system was very unstable and slow. After 10 seconds the screen went completely pink and it shut off again and never came up (showing me the boot logo and rebooting - bootloop).
I removed the battery again and tried to flash, after one day, with odin the stock firmware. I had no issues while flashing but the OS won't boot. Therefore I flashed the TWRP to the recovery partition and it doesn't work. After 10 minutes without the battery I am able to boot TWRP but when I try to, for example, copy the logs to /data TWRP freezes and I cannot do anything else but hard reboot.
Someone knows what's going on here? Could the eMMC be seriously damaged/corrupted?
The strange thing is that, without the battery for 10 minutes plugged in, I am able to boot to TWRP and navigate through the menu - although after trying to format the /data and /cache partitions TWRP freezes. After a reboot I cannot boot to recovery anymore (it remains stuck on the samsung logo screen with the RECOVERY BOOTING and Set Warranty Bit: recovery headings.
My fathers old S4 has a similar issue, https://forum.xda-developers.com/galaxy-s4/help/s4-i9505-wont-past-screen-boots-t3810088
It seems so strange, I'm currently trying to get the files left on the phone safely of but it crashed when trying to do so and now I can't enter recovery.
But I'm trying to troubleshoot it as good as possible without risking loosing the files, and the strange this is that many S4s seems to have problems with the fact that it is a random restart and then goes into bootloop. But the thing that worries me the most is the fact that you were running Lineage while my father was running stock TouchWiz based on 5.0.1. That leads me to believe that this is a hardware issue, I'm considering unscrewing it and try to troubleshoot it. Going to get my hands on my fathers old extra batteries for his S4 tommorow, will see if that makes a difference.
Did you wipe the /data partition after flashing the stock rom? I had the same issue... After flashing LOS, my phone is bootlooping randomly and i tried to flash stock rom. ODIN does not wipe the data partition after flashing the original stock samsung firmware so the OS can`t boot due incompatible data( The lineage os data with android 7.1.2 is not compatible with lollipop). Try to flash the stock rom again, wait until your device restarts to the robot and hold the vol up+home+on/off to get into stock recovery. Perform a factory reset and then restart. You have to wait a bit (maybe 10 min)
So at some point when wiping/flashing LOS 15.1 something got messed up & it just keeps rebooting before the boot screen loads. It doesn't matter what I flash now, it does the same thing, all except for the firmware file from Updato. That booted into 7.1.1 (though it took a while), I tried flashing LOS after but it still goes right back to the reboot loop. Any help would be much appreciated.
[edit]
So I found a full backup & got that restored using TWRP 2.8.7.0, that booted up only to tell me to put my sim card in, no clue where that is, never used it (used tablet). I flashed 3.2.3, LOS 15.1 & 16.0 so far, neither will boot, they just get stuck on the boot screen. LOS 14.1 just reboots before the boot screen.
I've tried to use the Bootimage Debug Addition patch from here to grab some logs but it doesn't seem to be working, any help would really be appreciated.
So I take it I'm just out of luck then?