Hey, I'm new to android modding and I decided to reinstall lineage os by doing wipe and flashing the rom again, and now it still asks for password, when I enter it, it's stuck in bootloop.
EDIT: Ok, I managed to flash stock but, I'm still interested, when I'll use Lineage OS, how can I reinstall it if I see a problem?
Long story short, all you really need to fully wipe your device according to the instructions. Did you flash GApps before booting System? You should also read through the dedicated LOS thread here.
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 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
I found out about dc unlocker and unlocked bootloader. Installed twrp and wiped data/dalvic/system as said in the thread . Tried to flash havoc os. It flashed successfully but It didn't boot. After that I tried to install lineage os 15.1 and omni, none of them booted. I have access to erecovery twrp and fastboot. I can flash all of the os's successfully but none of them boot. I would like to get any os working rn since this is my main phone which I didn't back up because I was stupid. I tried to install magisk on the first time I tried installing Havoc and one guy said it could be the reason why it doesn't boot. That same guy also said that it could be the encryption preventing boot but I have no idea how to decrypt anything. Any hint's are appreaciated.
luimu said:
I found out about dc unlocker and unlocked bootloader. Installed twrp and wiped data/dalvic/system as said in the thread . Tried to flash havoc os. It flashed successfully but It didn't boot. After that I tried to install lineage os 15.1 and omni, none of them booted. I have access to erecovery twrp and fastboot. I can flash all of the os's successfully but none of them boot. I would like to get any os working rn since this is my main phone which I didn't back up because I was stupid. I tried to install magisk on the first time I tried installing Havoc and one guy said it could be the reason why it doesn't boot. That same guy also said that it could be the encryption preventing boot but I have no idea how to decrypt anything. Any hint's are appreaciated.
Click to expand...
Click to collapse
Had the same problem yesterday, just follow this guide:
h ttps://forum.xda-developers.com/honor-7x/development/mod-decrypt-data-emui-8-t3765403
For me, it made the trick.
I actually solved it by doing format data in twrp instead of just wiping it.
Hi guys,
I have unlocked the bootloader of my S5e (T720) installed Magisk and TWRP. Wiped the unit and installed Gapps + Lineageos 17.
That said: I keep booting into TWRP...
How to make the unit boot in Lineageos please?
Thanks
Seems like something went wrong with the OS installation. I would advise that you reinstall the OS again.
Did you ever find a solution to this? I am in pretty much the same situation but I didn't use magisk cause I didn't want to root. I tried flashing lineage 16 and 17 after wiping system, data, vendor etc.. I always just seem to end up looping back into TWRP. Not really sure what I'm doing wrong, I do always get the warning asking me to press the power button to continue as I'm not running official software and have an unlocked bootloader so maybe there is some security feature that's still preventing me from getting in? If anyone could offer any help I'd appreciate it a lot, I'm very new to all this.
Yelnat said:
Did you ever find a solution to this? I am in pretty much the same situation but I didn't use magisk cause I didn't want to root. I tried flashing lineage 16 and 17 after wiping system, data, vendor etc.. I always just seem to end up looping back into TWRP. Not really sure what I'm doing wrong, I do always get the warning asking me to press the power button to continue as I'm not running official software and have an unlocked bootloader so maybe there is some security feature that's still preventing me from getting in? If anyone could offer any help I'd appreciate it a lot, I'm very new to all this.
Click to expand...
Click to collapse
Wiping System and Vendor? Why did you do that? That is likely why it doesn't boot. You will likely need to go back to stock to put those back and start over. I've found on these any deviation from the instructions below it's not going to work.
LOS Install Instructions
Magisk worked for me, but on this particular device I've found mods have to be flashed from Magisk afterwards from Magisk and not in TWRP like I do on other devices.
OhioYJ said:
Wiping System and Vendor? Why did you do that? That is likely why it doesn't boot. You will likely need to go back to stock to put those back and start over. I've found on these any deviation from the instructions below it's not going to work.
LOS Install Instructions
Magisk worked for me, but on this particular device I've found mods have to be flashed from Magisk afterwards from Magisk and not in TWRP like I do on other devices.
Click to expand...
Click to collapse
I only deviated when it didn't work, Ironically I fixed the issue by wiping literally everything via TWRP and then trying to reinstall lineageOS. I did have a problem with it taking hours to boot the first time, but I found that I had to install lineageOS without gapps, then reboot into TWRP and flash gapps afterwards. Strange Issue but all is well that ends well I suppose.
Did you guys get a solution for this? I am in the same situation. I have the ROM and Gapps on the external card, and although I installed it again, I am still stuck in this bootloop.
Hello everyone, I'm trying to flash Havoc os 3.0 alongside with BitGaps, but it always ends up in a bootloop (I always wait one hour in the "android" boot screen). My device is the A205G with Android 10. I successfully flashed TWRP using the guide posted here in xda (also flashed magisk), then I flashed Havoc and BitGaps (wiping dalvik, cache, data and system first and then doing a factory reset), but ended up in a bootloop after rebooting to system. In a second try after reinstalling Android 10 stock rom I followed the steps shown in a youtube video (can't post link since I'm a new user) with no luck (still getting a bootloop). In a third try I just flashed the stock rom, then flashed twrp with odin and tried to flash Havoc without flashing Magisk at any moment, still bootloop. Any ideas or suggestions on what could be wrong? I've only flashed one device before with a custom rom so I'm not an expert in this area, any help will be appreciated.
Downgrade phone to Android 9, later flash twrp, then install system and Gapps.
GamingMichu said:
Downgrade phone to Android 9, later flash twrp, then install system and Gapps.
Click to expand...
Click to collapse
Thank you so much! Worked perfectly.
No problem bro. If you have problems, write to me, I will try to help.