Related
CM Installation Problems
I posted this last night on the CM forums and have had one responder but thought this might reach a wider audience. I'm copying and pasting the OP and I'll try to include as much info as possible.
Hi,
I'm fairly new to flashing etc. New as in this was the first time I tried it. I'm fairly tech savvy, I just haven't flashed a custom rom before.
I followed all the instructions on the CM wiki for the S5 (AU).
Long story short, every step in those instructions worked perfectly once I accounted for my own errors or misunderstandings. Flashed the TWRP recovery just fine. There were problems with ADB not working when the phone was in recovery mode (discovered it's something to do with win 8 and above) so I just rebooted into stock rom (where ADB worked) and used adb push to copy the files to sdcard. Everything went swimmingly until the actual CM installation. I followed the instructions and did the factory reset, went to install and the installation took something like 10 mins before I started to wonder how long it was meant to take. Little bit of googling got me more worried, after about 20 I pulled the battery, back into recovery and went into Wipe again. Cleared Dalvik, cache, system all manually and then did the factory reset option on top of that just to be thorough. Installation is still taking forever. It's currently been around 20 minutes. Some posts I've read say rooting is required but that installation article specifically says rooting is neither required nor recommended. I've no idea where to turn now. I can't use ADB to copy a stock firmware back on as it doesn't work in recovery mode, nor can I try the klte or kltedev versions (don't think they're meant for this model anyway). It's just stuck on "flashing file 1 of 1" - the last thing in the log is "Patching system image unconditionally..." I'm running windows 10, not that that should make any difference.
Any help would be hugely appreciated.
Update: After about 40 mins I pulled battery again and thought I'd try booting normally and seeing what it does. Just sits at "Samsung Galaxy S5" splash screen.
TL;DR/Extra info:
Galaxy S5 G900I (AU) Vodafone
Was running Lollipop 5.0 as per Vodafone OTA update
Using instructions on the CM wiki page for the GS5 (AU) I flashed TWRP using Heimdall with no errors. ADB would not work in download/recovery (couldn't see device) so booted phone into stock ROM and used ADB push to copy the CM file to sdcard root. Note: I don't have an sd card, it's internal storage. Rebooted into recovery, tried to flash CM, it sat on installation screen for about 20 mins. Tried 3 times, leaving it for 40 mins, still nothing. Stock OS has been wiped so I can't get back into that, and because ADB doesn't work I can't reflash recovery from scratch, can't copy a new download of CM on, can't copy the stock ROM to flash. ADB Sideload just tries to run and fails. Currently trying to get ADB working. Running Win 10, device stopped showing up in device manager or Zadig at this point. Restarted PC, ran Zadig again, it saw device, reinstalled driver, now shows up in device manager under USB Devices as MSM8960 (so not under Portable Devices as it once did). Note: the safely remove icon in system tray showed "Galaxy S5 (Phone name)" before I ran Zadig again, now it shows MSM8960.
Help
Reflashed TWRP with Heimdall. Didn't change a thing.
After the biggest headache of my life I got ADB working in TWRP. Had to modify the .inf of the google usb driver that the SDK installs and add the hardware ID of the device in recovery mode. Apparently the ID changes when in recovery so the driver doesn't recognise it anymore. Success!
I downloaded the nightly from 30/09, renamed it update.zip so the filename was simpler, pushed it with ADB to sdcard and am now trying to install it. So far same issue, but at least I can push files to the phone now. It definitely seems to be an issue with the install process.
Update: Still same issue. New zip, new build, reflashed recovery and still hangs on install. Would trying ClockWorkMod be worth it rather than TWRP?
When sideloading the ROM and viewing command prompt on the PC everything works fine until it hits 90% and then it stops suddenly and stays there. During the TWRP factory reset it also says unable to mount system several times if that's any help
I've now tried flashing Philz Touch and given that a go. Factory reset/wiping seemed to run with less of a hitch but still exactly the same deal, gets to "patching system unconditionally" when installing CM and just sits there, progress bar doesn't even fill up a bit. I'm stumped.
Yesterday I wanted to update my Nexus 4 to the latest nightly cm-13.0-20160221-NIGHTLY-mako.zip using the built-in update tool. The old build was cm-13.0-20160209-NIGHTLY-mako.zip.
But after hitting reboot, the screen went off and on repeatedly (just plain black). I let it like this for the night. In the morning it was still turning the screen on and off. I was able to reboot to the bootloader. Apparently, the update deleted TWRP and installed Cyanogenmod Recovery. I re-flashed twrp.img, and now I'm stuck there: booting ALWAYS goes to TWRP (or the bootloader), I can't boot the system anymore. I tried re-flashing the old nightly, retried the new one, tried sideloading an even newer one (cm-13.0-20160222-NIGHTLY-mako.zip), wiped cache, wiped data - nothing helped.
What can I do to unbrick my phone?
Do u have a back up to your stock Rom or any other Rom aside from CM?
Flash back to stock and start over with twrp, cm, and gapps.
I just flashed back to stock, the problem persists: bootloop, the lying android with a red warning sign is showing up very briefly, then it reboots.
My first attempt to go go back to stock was manually. Now I tried again using the Nexus Root Toolkit. (Note: both time I flashed build LMY48T
After it finished flashing, the error message (lying android with red warning sign) appeared again, but this time it stayed - no bootloop anymore.
Then I rebooted into revovery mode, and there was some output:
Code:
Finding update package...
Opening update package...
E:unknown volume for path [/storage/emulated/0/cmupdater/cm-13.0-20160221-NIGHTLY-mako.zip]
E:failed to map file
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
So, despite all flashing, apparently it is STILL looking for the - now missing - cm13 update. Where is this coming from? There must be some flag somewhere, some config file or whatever.
So, after the next reboot, the ominous boot parameters seem to be gone - I'm on a fresh 5.1.1, build LMY48T.
I'm still curious what happened here. I guess the whole flashing wasn't necessary, I just needed to get rid of the malicious boot parameter. Maybe a file or a file system was readonly?
Any idea how this happened?
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
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
I attempted to install Lineage OS on my Pixel C. When I attempt to sideload Lineage OS, I get an error that says "Updater process ended with signal: 7" and it acts like I have no system image installed and just keeps boot-looping. I tried to flash back to stock, but I keep getting an error that says "error: Cannot generate image for userdata". I have re-downloaded all of the images, and retried over and over again, to no avail. Any advice is appreciated!
Well, I finally got my tablet to boot again. I extracted the factory image and individually flashed each component (boot, cache, recovery, vendor, system - in that order) and I'm back to a clean install of the stock android. I went back and flashed twrp (successfully), and tried to sideload Lineage again per the instructions on their website, and got the same result. If I can't figure this out, I may be going back to just stock android.
Is it your first attempt at a custom rom?
Have you flashed a recent kernel, bootloader is unlocked etc?
edit: lol, last reply was from May..
Hey, I guess I haven't been on here in a while, and never saw your reply to this. It is not my first attempt at a custom rom. Bootloader is unlocked, and kernel is up to date (or was in May). I ended up staying on stock android since I had no trouble getting it to work. Best I can recall, I think I read that there was a conflict between TWRP and the kernel version I was on. Around the same time, I tried to flash LineageOS to my Essential PH-1, and had similar issues, and ended up just staying with stock android. I've been flashing custom roms since cyanogenmod was available on my Nexus One (I think that was on cupcake), and while I'm not an expert, I'm pretty comfortable with the process, so I went back to my Moto N6, and was able to flash LineageOS to that without a problem. I know that the Pixel C and PH-1 both have the whole A/B slot architecture, and I wonder if I wasn't managing that correctly, but I've gone through a couple of custom roms on my Pixel C over the years without having that problem, so I just don't know. Right now I'm fine with stock (rooted) Android, but the bug is sure to bite me again soon, so we'll see what happens then.
I recently downgraded to Lineage 15.1 (official) from 16 and had some issues.
Short story to make it work was; installed the April version of the official factory/ota image like you did to overcome version conflicts.
(booting to TWRP.img after getting to the correct recovery menu by pressing power+volume up).
In TWRP; As the \data folder was encrypted I had to format that first (advanced wipe) and used adb to push files to \sdcard.
I flashed the Lineage 15.1 zip, gapps and Magisks before rebooting.
As that build enforces encryption of \data at first boot you may need to use "default_password" to load TWRP with access to \data in the future.
Hope this helps