Related
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.
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
NOTE: IF YOU DON'T WANT TO USE MAGISK THEN JUST FOLLOW STEPS FROM 1 to 7 WITHOUT STEP 6a
<strike>asd </strike>
A lot of Mi Max 2 users have problem with Dual Boot Patcher. You can pass installation step, but if you want to boot into secondary ROM the phone just vibrate and boot into recovery?
If your answer is "YES" then this guide is for you and it also contain how to get fully working Magisk (optionaly)
What is causing crash? It's encryption on internal storage.
What you have to do:
1) Boot into recovery
2) Make a backup of /system /data /boot on SD Card (it's important to make it on sd card!)
3) Wipe internal storage (it will erase all of your data including photos, music etc.)
4) Restore your backup and boot to your ROM
5) Install Dual Boot Patcher,go to ROM tab -> press 3 dots and press "Update ramdisk" and choose "Reboot now" It causes bootloop for some users and its only necessary for "App sharing" feature but it doesn't work properly on our device, so don't update RAMDISK and go to next step
6) Patch your ROM and install it as secondary on /system or on /data partition - it's your choice. I have MIUI and LOS installed on /system partition and it has still 1.7 GB of free space there
6a) Patch Magisk_v12.zip (see attachment) as a zip for secondary ROM and flash it
7) Select your secondary ROM in ROM list and reboot.
From now on everything what is below we will do on secondary ROM
8) Install Dual Boot Patcher.
9) Install magisk.apk (see attachment)
10) Open Magisk Manager
11) Go to Modules-> press "+" button -> search for Magisk_v15.3.zip -> hold your finger on it -> press "Open". Wait for installation end. Now press close button. Don't restart
12) Open Dual Boot Patcher -> confirm for change current kernel
13) Reboot and voila! You have fully working secondary ROM with Magisk!
English is not my native language. If there are any eye-bleeding language mistakes then send me PM with corrected text. Thanks!
reserved
so if i wanna install 3rd rom. i have to wipe internal again ?
phuocrose said:
so if i wanna install 3rd rom. i have to wipe internal again ?
Click to expand...
Click to collapse
No! It's just for decrypct internal storage. No need to wipe internal again
it worked and the 2nd rom booted correctly then i added magisk 15.3 and set kernel .. the next boot the phone boots to the primary rom and stuck at bootanimation
when checking from recovery it appears that data partition cant be read and twrp asks for password
i managed to format and restore a backup
but what exactly caused this ??
Hi, I tried to follow each step as described but after clicking 'reboot' in the dual boot patcher app it just reboots to TWRP and I can't boot into the os anymore..... Anyone having the same issue?
kalawy said:
it worked and the 2nd rom booted correctly then i added magisk 15.3 and set kernel .. the next boot the phone boots to the primary rom and stuck at bootanimation
when checking from recovery it appears that data partition cant be read and twrp asks for password
i managed to format and restore a backup
but what exactly caused this ??
Click to expand...
Click to collapse
Thread updated. Try to follow steps again. I have removed updating ramdisk step because it causes random bootloops
Benoît Lagasse said:
Hi, I tried to follow each step as described but after clicking 'reboot' in the dual boot patcher app it just reboots to TWRP and I can't boot into the os anymore..... Anyone having the same issue?
Click to expand...
Click to collapse
Dirty flash your current ROM and don't update ramdisk. Thread updated. If it boot then go to dual boot patcher and set kernel for your primary rom, if it asks
Unable to boot in primary os
Well thank you so much for this post
I followed all step carefully did same as written
Didn't keep miui as primary,
ISSUES
I went to Recovery fresh install of superior os
Did Backup , Wipe ,and restore now rebooted
Installed DBP Patch Miui 11 ROM and I thought that there's no enough storage in my system partition so flashed it in data slot )))
Switched to Miui 11 everything worked fine!
But I'm unable to boot in my primary superior os
FOA I were unable to switch ROM to superior then I updated kernel and ramdisk switched successfully but still
I can't boot to my primary superior os Everytime I reboot I boot into Miui 11 -
Using
Mi Max 2 (oxygen)
How To Flash Roms with the Ridiculous Slots... yep. You're a rookie again because these things are going to drive you onto a drunken crazy bender... You'll probably wake up in Mexico married to someone you've never met and tied in with the Chicago Mob in debt for a quarter million. THIS IS WHAT WORKS FOR ME. I do the same thing Every time and have done this wrong so many times I've lost count.
Note number 1...
You have or know how to use adb and fastboot basics... if not... Of not Google the Adb and fastboot set up for your devices and/or PC/Laptop etc... There are a lot of forums and Q&A on setting this up to get fastboot cmds running. You should be familiar regardless and at least have the stock flashall.bat for a Google Stock IMG JUST IN CASE. I am assuming everyone is already at the install for TWRP and is working with 3.2.0-0 only. You cannot flash roms without it. Any other version for 8.1 will NOT work at this time...
Note number 2...
Roms will vary. Some may include the vendor image and you don't need to flash it. Some may include gapps and you don't need to flash those... Some may include everything and have you flash to slot_a and that is all. In other words do what the OP says, they built it. They know what's in it and how it works.
Here's the trick... It doesn't mean you can't do these in any other way but you will NOT get stuck if you follow some simple rules...
Roms only flash while in Slot_A
Gapps only Flash in Slot_B
Kernels only flash in Slot_B
Magisk only flash in Slot_B
IMG Flash to Slot_B
TWRP 3.2.0-0 ONLY
TWRP 3.2.0-0 to either slot
Do NOT EVER Flash anything other then TWRP, Rom Gapps and Vendor until GOING through first boot. Yes you can but it increases your issues.
Always always always double check between every install the status of your Overlays folder. Before every rom install Mount System then Go to File Manager and Delete that folder from Slot B before you boot to Slot A to flash the rom. This can hold Data from Magisk and Mods that get all tore up Everytime... It also happens when you reflash Magisk or dirty flash a rom. I'm going to put together a fresh flash below and I'll get into that a little later.
So from stock Google image...
Clean flash... MAKE SURE YOUR LOCKSCREEN IS OFF... No fingerprint set up... Not a pin set up... No pattern set up. If your more secure than swiping up to open your screen your not getting in to TWRP 3.2.0-0 decrypted.
Either... Reboot recovery (you'll be in slot B) if you already have TWRP installed....
Or....If you're just booting TWRP for the first time...from bootloader you fastboot boot (not flash really the terminology is BOOT) TWRP-3.2.0-0-marlin.img (you'll be in slot B)
Read your bootloader screen or go to TWRP 3.2.0-0 Reboot menu to find out which slot you're in.
FLASHING YOUR FIRST ROM...
note... Most are going to require before flashing your coming from stock. Just do it. At least the initial install... Dirty flash or clean flash after that without going back to stock but you don't have to flash the stock image.
Ready... You're in slot b remember...in order here...
- Wipe Data System Cache
- Flash TWRP 3.2.0-0 the ZIP
This is why you can't have your lockscreen on... If you didn't listen just go back to your bootloader and start over with the flash-all.bat. Sorry but I warned you... You can't get anything to flash at this point because you can't decrypt 3.2.0-0.
- Go to MOUNT then make sure your system box is checked
- Go to ADVANCED and then File Manager and make sure you have no overlay folder. If you do... click on it and hit delete from the options on the bottom portion of TWRP.
- HIT HOME and Go to the actual reboot menu choice (Not the swipe reboot system)
-Click on slot_A and then reboot back into recovery. ...NOTE... I usually don't use the reboot recovery option.(reboot recovery seems wonky and doesnt work for me all the time) I reboot system and just hold volume down until I hit the bootloader and the choose recovery in the bootloader options...
You ARE in Slot A now... Right... You can Double check in the bootloader or TWRP in the reboot menu.
- if you really really really like to wipe you can wipe Data system and cache in Slot_A... I never do from slot_a but to each their own.
- Flash rom and flash TWRP 3.2.0-0. Nothing else.
- Reboot back to recovery again.
You ARE in slot B. Yep automatically... When a rom is flashed it goes to the opposite slot. And reboots you there on the next recovery reboot so DO NOT GO change your slot to B unless an OP actually directs you to do so.
So... We're in slot B
- Flash Gapps and Vendor... nothing else until after you boot up.
Yeah yeah... You want to be rooted... Well boot up first and we'll hopefully be able to walk through that too.
Your booted up. Go to your development options and double check to make sure USB Debugging is enabled... Really whatever, you're really pretty safe if you have Your fastboot drivers and they must be installed because you installed TWRP to get this far so if something goes wrong from here we can still always do the flash-all.bat so your phone shouldn't implode and brick out.
Reboot recovery. Yep you're in slot B... You should now always boot recovery to slot_b unless you mess something up and get stuck in a loop. I've seen it but couldn't duplicate. It was always me flashing out of order.
GAINING ROOT... MAGISK INSTALL
- Choose the zip, flash and reboot.
Nothing further needed, make sure it's compatible with 8.1 and at least 15 to 16 are Oreo compatible. Easy right.
Well even when I'm updating... the wonderful Overlay folder can get jacked. I'm pretty sure I've heard it laugh at me as I stuck in bootloop after bootloop... If you delete the overlay folder anytime BEFORE you update to the next version of Magisk you'll be ok
UPDATING MAGISK...
So if you're on 15.3 and you want to get to 16.0 without getting stuck or having issues on boot.
- Reboot from Rom to recovery... You WILL always be in slot B by default.
- Go to Mount
- Mount System
- Go to Advanced and then File Manager, find your Overlay folder.
- Click on the overlay folder
- Click Delete
- Hit Home
- Flash your updated Magisk 16.0
MAGISK AND KERNEL
To get Magisk and a kernel going can give you to madness. It gets a little tricky. But honestly devs have really really improved the process. If you're rooted already most you can flash reboot into the rom reboot to recovery again and then do this again...
- Reboot from Rom to recovery... You WILL always be in slot B by default.
- Go to Mount
- Mount System
- Go to Advanced and then File Manager, find your Overlay folder.
- Click on the overlay folder
- Click Delete
- Hit Home
- Flash your updated Magisk 16.0
For the most part the current kernels do not blow out your Recovery anymore however some do. In fact the only one I know that will is Noexezshades. Probably spelled that wrong but you'll catch my drift if you read his OP.
SERIOUSLY YOU BETTER ALREADY HAVE BOOTED INTO YOUR ROM FOR THE FIRST TIME.. You'll hate your life if you set this up during your initial install.
INSTALLING KERNEL WITH MAGISK
- Reboot Recovery (hahaha. Ha. You turned your fingerprint scanner on... Reboot and turn it back off)
- Flash Magisk
- Reboot
I know... right now you're saying WTF... I didn't flash the kernel. This is just a fail safe... Points in Any Kernel need Root to install... I haven't had issues but really probably because I always flash Magisk first.
If you already had Magisk installed start here.
Now we're going to Flash the kernel. It's going to unroot you so we'll just immediately install Magisk I recommend always installing Magisk after a kernel because it also Patches the boot otherwise there are times when patching the boot.img is required however I believe most DEVs have surpassed that FOR MOST KERNELS.
- Reboot recovery (Dang. You forgot to turn off your fingerprint sensor again, sorry life's rough turn off your lockscreen again)
- Flash kernel
- Reboot system
- Reboot recovery (you might lose TWRP however every Newer version I'm using--- unless noted by the OP--- is working at present)
- DON'T flash Magisk... No dont flash Magisk. If you were following along you can see you need to go delete the overlay folder before you flash Magisk it will almost always go bad at this point if you don't delete the overlay folder
- Flash Magisk
- Reboot.
Hopefully you learned what's happening now in the background. I try to explain things from a user level and do this as part of my daily work every day. I don't understand things unless someone tells me what's going on along the way and keeps me partially entertained...
Talk amongst yourselves or don't post Anything. The goal is to take the issues out of the day to day so the devs aren't getting the questions.
I'm gonna have to read this post a couple of times to get the hang of it. I'm kind of a newbie.
Great post. Thank you for the write up. Helps to understand twrp when dealing with two partitions
When I understand it correctly, for a ROM installation I need to select slot a. (Standard for me). And slot b for Kernel installation and others.
But why my twrp installation was broken? After installation I can't boot to the system and unable to start the recovery, so I must flash the complete system images from Google.
Gesendet von meinem Pixel XL mit Tapatalk
Just for clarity, the OP mentions TWRP-3.0.2-0 a couple times. It should be 3.2.0-0.
Nice write-up.
Sent from my Pixel XL using Tapatalk
pkelly517 said:
Just for clarity, the OP mentions TWRP-3.0.2-0 a couple times. It should be 3.2.0-0.
Nice write-up.
Click to expand...
Click to collapse
It'd be neat if I could edit my post from the XDA app. My screen and back glass broke... then the earpiece blew out so I was awaiting parts and haven't been online
I need to go away from the option of even flashing TWRP at kernel install. As everyone updates their kernels... I see it starts a looping issue now. Everything else is solid.
overlay folder
I am not grasping what the "overlay folder" refers to. What folder do i need to delete any time i flash magisk? I really appreciate the detail in the steps of this guide.
-Happy Feet- said:
When I understand it correctly, for a ROM installation I need to select slot a. (Standard for me). And slot b for Kernel installation and others.
But why my twrp installation was broken? After installation I can't boot to the system and unable to start the recovery, so I must flash the complete system images from Google.
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Hey Happy feet.
From the beginning
Reboot recovery from stock.
Wipe data, system, and dalvik
Flash TWRP installer.zip after your wipe
Delete your overlay folder if you were rooted previously.
This is at Advanced/ File Manager/click on overlay and then hit delete.
Hit the HOME button in TWRP
Click on slot A and then reboot recovery
Back in recovery now IN SLOT A
Flash ROM
Now flash TWRP installer.zip again
Reboot recovery... Benzo ROM includes everything so you'd just be rebooting at this point into the Rom so read and reread the OP you downloaded from.
Flash Gapps (if needed for your ROM some have them built in)
After you flash the gapps if needed... then flash vendor (assuming it required from the dev who made the rom (like Benzo ROM has the vendor built in))
You do not have to flash TWRP at this point and can reboot directly into the Rom. If it doesn't boot or you hit a bootloop you did something out of order from the above, or there is something wrong with the Rom itself.
Second part... When I say Flash TWRP I mean the TWRP installer.zip there are 2 different files. The marlin-fastboot image and the Marlin Installer.zip. so if you flashed Twrp-3.2.0-0-marlin.img that is not enough... You have to have the twrp installer.zip downloaded on your internal storage to flash through TWRP and you no longer need to fastboot flash.
ROMs absolutely will erase your TWRP installer.zip and you need to reflash TWRP installer.zip before you reboot after you flash your ROM.
Sorry if I over explained it, not trying to make you feel like you don't know what you're doing, it's just very different than the old school installs.
Mikkey81 said:
Hey Happy feet.
From the beginning
Reboot recovery from stock.
Wipe data, system, and dalvik
Flash TWRP installer.zip after your wipe
Delete your overlay folder if you were rooted previously.
This is at Advanced/ File Manager/click on overlay and then hit delete.
Hit the HOME button in TWRP
Click on slot A and then reboot recovery
Back in recovery now IN SLOT A
Flash ROM
Now flash TWRP installer.zip again
Reboot recovery... Benzo ROM includes everything so you'd just be rebooting at this point into the Rom so read and reread the OP you downloaded from.
Flash Gapps (if needed for your ROM some have them built in)
After you flash the gapps if needed... then flash vendor (assuming it required from the dev who made the rom (like Benzo ROM has the vendor built in))
You do not have to flash TWRP at this point and can reboot directly into the Rom. If it doesn't boot or you hit a bootloop you did something out of order from the above, or there is something wrong with the Rom itself.
Second part... When I say Flash TWRP I mean the TWRP installer.zip there are 2 different files. The marlin-fastboot image and the Marlin Installer.zip. so if you flashed Twrp-3.2.0-0-marlin.img that is not enough... You have to have the twrp installer.zip downloaded on your internal storage to flash through TWRP and you no longer need to fastboot flash.
ROMs absolutely will erase your TWRP installer.zip and you need to reflash TWRP installer.zip before you reboot after you flash your ROM.
Sorry if I over explained it, not trying to make you feel like you don't know what you're doing, it's just very different than the old school installs.
Click to expand...
Click to collapse
Thanks for your help, great explained for an pixel Beginner.
Gesendet von meinem Pixel XL mit Tapatalk
beezza said:
I am not grasping what the "overlay folder" refers to. What folder do i need to delete any time i flash magisk? I really appreciate the detail in the steps of this guide.
Click to expand...
Click to collapse
Go to TWRP.
Open Mount and click to Mount System
Open Advanced and then choose File
If you find a folder in your root named 'overlay' tap on it (select it) and then click on delete.
If it's not there.... great. You've probably never rooted. It'll cause some bootloops once in a while, sometimes it doesn't matter. It's more important to do this at the point of flashing a room because you most likely will not get a fresh install to boot up if you're rooted.
Quick Note: This file carries over Magisk root data and gets messy as you update Magisk or reflash it.
I tried installing latest magisk on android "P" and was on Slot-B and it wouldnt install, error...
changed to slot-A and then it installed..
Magisk v16.3 (1630)
Thanks for info. good stuff i am new to pixel coming for my old friend nexus 6
just fyi I downloaded and flashed twrp-3.2.1-2-marlin before reading this and just happen the passcode thing for me is not a problem. Had to enter it twice the first time using twrp but now just once. works fine.
I don't give nearly enough appreciation where it's due but I gotta hand it to you... By far the best guide ever! Thank you!
Very good details and advice. I'm having far else problems by following these steps. Thanks for all your work.
commenting here to save this for future.
thank you OP!
hoping this thread is still alive. . . is there a recommended factory image to restore to? do i need to flash the factory on both slots? is it best to flash -the factory system.img on a particular slot? In the end which slot to --set_active=?
And how do the SLOTS come into play for doing a TWRP backup and doing a TWRP restore ?
Hi,
I need some expert advise on installing Lineage OS 14 or 15 in my ZE550KL. A little background about my phone. It always got the ASDF error..unable to mount error when trying to upgrade firmware. I always have to revert to the 1531 firmware and then upgrade to the latest firmware. Since the phone is now past its prime, I felt like experimenting with new ROMs. But whatever OS I install with TWRP, it always gets stuck in the first boot. The Lineage or the other OS boot animation never stops. I have probably done 5-8 installs of Lineage OS, each time trying something new, however I always got stuck with the boot up animation. I have tried installing with different versions of TWRP, deleted Dalvik after installing, deleted everything except external SD card before installing Lineage, installed different versions of Gapps, not installed GAPPs at all and just rebooted with Lineage installed. I have tried different versions of Lineage OS. Whatever I did, the phone always got stuck during the first boot up. I have observed the boot up animation after each installation, and every time waited for at least 30 mins to 1 hour and saw nothing happening, except the Lineage bootup animation. Please help.
fixitsam said:
Hi,
I need some expert advise on installing Lineage OS 14 or 15 in my ZE550KL. A little background about my phone. It always got the ASDF error..unable to mount error when trying to upgrade firmware. I always have to revert to the 1531 firmware and then upgrade to the latest firmware. Since the phone is now past its prime, I felt like experimenting with new ROMs. But whatever OS I install with TWRP, it always gets stuck in the first boot. The Lineage or the other OS boot animation never stops. I have probably done 5-8 installs of Lineage OS, each time trying something new, however I always got stuck with the boot up animation. I have tried installing with different versions of TWRP, deleted Dalvik after installing, deleted everything except external SD card before installing Lineage, installed different versions of Gapps, not installed GAPPs at all and just rebooted with Lineage installed. I have tried different versions of Lineage OS. Whatever I did, the phone always got stuck during the first boot up. I have observed the boot up animation after each installation, and every time waited for at least 30 mins to 1 hour and saw nothing happening, except the Lineage bootup animation. Please help.
Click to expand...
Click to collapse
Any assistance will be appreciated. Let me know if I have posted in a wrong thread.
Hi I'm not an expert, but try this following steps I hope it works.
1.) Remove your sdcard
2.) backup everything in Internal Memory
3.) download the latest TWRP recovery @ twrp.me
4.) install flash it to your recovery partition.
5.) goto advance wipe then do an advance partition repair
# perform repair at this Mount points
# /system
# /cache
# /data
# /dalvik-cache
# /ASDF
6.) reboot again to recovery (not necessary)
7.) perform a clean install on your desired rom.
7.5) goto advance settings and copy logs.
8.) reboot simultaneously with this command
8.5) open cmd/terminal and run adb logcat > {YOUR_PATH}/logcat.log e.g.
9.) pray it works.
If its still unsuccessful,
Paste your logs here for those who might get interested in your case. They can't help you if they don't know what is happening inside.
christian.arvin said:
Hi I'm not an expert, but try this following steps I hope it works.
1.) Remove your sdcard
2.) backup everything in Internal Memory
3.) download the latest TWRP recovery @ twrp.me
4.) install flash it to your recovery partition.
5.) goto advance wipe then do an advance partition repair
# perform repair at this Mount points
# /system
# /cache
# /data
# /dalvik-cache
# /ASDF
6.) reboot again to recovery (not necessary)
7.) perform a clean install on your desired rom.
7.5) goto advance settings and copy logs.
8.) reboot simultaneously with this command
8.5) open cmd/terminal and run adb logcat > {YOUR_PATH}/logcat.log e.g.
9.) pray it works.
If its still unsuccessful,
Paste your logs here for those who might get interested in your case. They can't help you if they don't know what is happening inside.
Click to expand...
Click to collapse
Thanks for the respinse. Will try these steps and post logs