I decided it was finally time to upgrade to the newer LineageOS 17.1 branch nightlies from my previous installation of 16, rebooted to recovery and sideloaded lineage-17.1-20201013-nightly-enchilada-signed.zip onto it from https://download.lineageos.org/enchilada .
After doing so it appears the recovery successfully updated, it has a new purple skin it didn't have before, however the actual ROM won't start. Instead it goes to fastboot mode and asks whether I want to Start/Restart/Recovery/etc, but I can only get into fastboot or recovery mode.
I've tried flashing older nightlies, but even with 20200922 the issue was still there. I did notice there was a ton of updates in that specific release so I wonder if anything is broken in there.. unfortunately that's also the oldest available nightly so without compiling my own there's no way I can test whether older ones are functional, unless someone here has an older version available perhaps.
I did notice doing adb sideload only makes it go to 47% before the phone goes to installing it, however maybe that's normal, I haven't used it in a while so I don't know for sure. I tried using ADB to push an image onto /tmp, however the new recovery only seems to have 'Apply from ADB' as option so I can't actually install it from there.
Does anyone have any ideas I could try, or perhaps an older LineageOS nightly from before 09-22 laying around somewhere? Any help or suggestions much appreciated!
PPS: Of course I forgot to mention but I also did a factory reset, but that did not help. unsure what else to try besides compiling a rom myself or trying other roms from the forums here, though I'd very much prefer having LineageOS..
I found the reason. I had to install the official Oneplus 6 ROM first, probably to get the right vendor binaries/kernel modules/drivers.
This is what I did:
- fastboot boot TWRP ( TWRP can be found here https://twrp.me/oneplus/oneplus6.html )
- wipe -> advanced wipe -> all the things (technically optional but if you want to get rid of GApps etc this is needed)
- adb sideload official OnePlus 6 'Oxygen' ROM ( https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727 )
- reboot, fastboot boot TWRP
- run the 'copy partitions' zip from https://androidfilehost.com/?fid=8889791610682929240 to copy Oxygen to the other A/B partition
- Install latest build from https://download.lineageos.org/enchilada
- reboot, optionally boot TWRP again and install GApps, also optionally install TWRP, reboot, enjoy.
PS: Please note that after this you shouldn't switch A/B partition without first flashing another nightly or something over it, i.e fastboot boot twrp and install latest lineageos again, otherwise you'll end up booting the vanilla Oxygen rom
Related
I saw an ancient Nexus S in a random drawer in my house. I figured It would be perfect for working out with since I have a Note 5 and it's a little big to carry around. I intended to use it for running only with endomodo. When I booted I noticed Cyanogen mod was installed. It booted up just fine but there was no play store. So like an idiot, I decided to just download the latest play store APK and install it. The app installed but crashed. I rebooted and now I'm stuck in a boot loop. Any help would be greatly appreciated!
You could boot to the recovery system, here you might be able to access all files, and you could try to remove the wrong apk. Alternatively just install the latest nightly version of CyanogenMod from April 2016, thus overwriting your operating system. Then install "gapps" for Kitkat (Android 4.4). There should be instructions on the CyanogenMod website or in this forum about which ones are valid. Make sure they are suitable for Android 4.4.4. You could also consider updating the recovery, if you like, before doing anything else. The latest working version is TWRP 2.8.7. Keep in mind that the device's nickname is "crespo", and do not install any binary that was built for any other device.
Perhaps it would also be sufficient to just reinstall the gapps using the recovery system. Make sure the gapps match the Android version.
So what would I do (brute force method)?
- Start device in recovery mode.
- Check recovery version. If it's not TWRP 2.8.7.0, install this one using the fastboot method, i.e. start device to bootloader, download TWRP to computer, install adb and fastboot on the computer and use the "fastboot" method to install the Recovery system (must be "twrp-2.8.7.0-crespo.img").
- Start TWRP
- Make a factory reset of the device
- Use computer to download latest CM nightly "cm-11-20160410-NIGHTLY-crespo.zip" and copy it to the device.
- Use computer to download suitable gapps package and copy it to the device
- Use TWRP to install both CM and gapps.
Hello,
I'm trying to install lineage-15.1-20180918 on my new (second hand) Google Pixel (sailfish). It came with Android 7.1.0 (NDE63H, Oct 2016) pre-installed.
No mater what I try to do, after installing Lineage zip file, I always get a warning saying that there is no OS. When I try to reboot to System, I am stuck in a boot loop between a screen saying that I should lock the bootloader and another one displaying the Google logo.
General information about device and softwares used
I run Debian on the PC that is used for the install, adb (v 1:7.0.0+r33-1) and fastboot (v 1:7.0.0+r33-1) are installed.
I got the Lineage zip from there (the shasum is good).
I got the TWRP image from there (v 3.2.3-1).
What I did
I followed the official howto there.
I have unlocked the bootloader, can boot into the TWRP recovery.
TWRP is launched via
Code:
fastboot boot twrp-3.2.3-1-sailfish.img
I did "Format Data", then "Advanced Wipe" (selected everything and wiped).
Then
Code:
adb push lineage-15.1-20180918-nightly-sailfish-signed.zip /sdcard/
(Note that I first tried to sideload both this zip and the suaddon one, given that it didn't seem to work, I wiped everything out again and went with the adb push method)
And, finally, went back to the "Install" menu, selected the zip and launched the install process (without checking the "Verify signature checkbox").
I managed to restore the initial backup created with TWRP, the system booted normally. I then tried a LOS install again and got stuck into a boot loop again.
Problem
At the end of this process, when offered with a swipe gesture to reboot, there is a warning saying that no OS is installed. Swiping to reboot leads to the reboot loop described above.
Any idea on what I can do to fix this issue?
Huge thank you in advance!
Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.
post-mortem said:
Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.
Click to expand...
Click to collapse
I did not. But there were other issues as well (I used outdated version of adb and fastboot), I followed the instructions there (due to the stupid rule for new users, I can't post a direct link to it) old.reddit.com/r/LineageOS/comments/9h0aqy/cant_install_lineage15120180918_on_a_google_pixel/e6nbqg6/ and it worked
Today I downloaded the latest nightly (lineage-16.0-20200123-nightly-I01WD-signed) and did a backup of System, Data, and Boot before flashing it. After rebooting, the LineageOS boot animation loops continually. It also overwrote TWRP with the LineageOS recovery (which I didn't realize was automatically part of the zip. I'm still not accustomed to A/B slot devices without recovery partitions). I can still fastboot into a good version of TWRP that correctly prompts me for my PIN for decryption, so I tried restoring from my backup. The restore seems to finish without problems, but upon rebooting the LineageOS boot animation still doesn't finish. My data/media is still intact and backed up separately, so I can start from scratch if absolutely necessary, but I was hoping there's some easy steps I can try before resorting to that. Let me know if I need to include more information.
EDIT:
I think I got it taken care of, although I don't know exactly why it worked. Here's what I did:
1. Flash the new LOS image I downloaded using fastboot TWRP
2. Boot to newly installed LineageOS recovery mode
3. Flash the same LOS image again from LineageOS recovery
4. Fastboot TWRP again without trying to start system yet
5. Re-flash the old version of OpenGapps I've been using (from Nov 2019 or something)
6. Reboot system
So i tried updating my phone and rerooting but as soon as i flashed the patched image something got corrupted and its only been pain now for the last few hours. Ive been super irresponsible in not backing up my phone away from the phone so I would rather not lose everything by flashing the factory image so anything and everything helps. for context it booted into 11 fine but as soon as I touched fastboot and the latest .img files is when stuff started going south.
edit: fixed the issue another way but an answer for that question would be nice to finally have on the internet.
I'm not very clear about what you did... The regular Magisk OTA process is:
1. Uninstall Magisk.
2. Install the OTA (do not reboot).
3. Install Magisk (after OTA).
The more involved process I've used (when the Magisk backup isn't valid) is:
1. Fastboot flash the vanilla boot.
2. Fastboot boot the patched boot.
3. Install the OTA (do not reboot).
4. Install Magisk (after OTA).
If you are doing a fastboot flash or boot you need to make sure the image you are using exactly matches your system. Which is especially important for the initial install. If you boot the wrong image, rebooting will fix it. If you flash the wrong image you have to flash the right image to fix it. That's why Magisk install has you fastboot boot and install from Magisk manager, less chance of a permanent issue
If you were going from Android 10 to 11 with Magisk 20, that will be a problem.
To answer the question in the title... You cannot access user data from fastboot. But you can probably fastboot boot TWRP and use that to access your data. I've done that before, but not on this phone.
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
a1291762 said:
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
Click to expand...
Click to collapse
It does depend on what's on the device because recovery is no longer its own partition. It's part of the kernel (boot.img). This unofficial TWRP was built against Android 10. And the entire partition layout changes around with the upgrade from 10-11. So it is just not valid and won't boot.
cmstlist said:
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
Click to expand...
Click to collapse
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Cant get ADB in recovery mode, but works in live mode, and so does fastboot
On my Rooted Pixel 4a, I can use: Fastboot - I flashed the latest update firmware as well as the rooted boot image ADB Over WiFi - This is the most comnon way I connect for ADB ADB While the Android OS is running What I cannoit get woirking is...
forum.xda-developers.com
Can you see what I a doing differently or have missed that made it work for you?
on a side note...
cmstlist said:
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Click to expand...
Click to collapse
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
DiamondJohn said:
...snip...
on a side note...
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
just came across this post, which may help explain why TWRP is problematic for our device. But the thread did hint about running twrp from fastboot. (Post by cmstlist)
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com
DiamondJohn said:
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
As a software developer that's been doing embedded Linux for 20 years, it saddens me that I haven't got past app development for Android
I'd love to help get TWRP going for the Pixel 4a but probably I'd get nowhere. I can certainly test TWRP builds though. My Pixel 4a is my daily driver but it's unlocked and rooted and I've got a solid off-device backup so I'm relatively fearless with hacking
DiamondJohn said:
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Click to expand...
Click to collapse
I was not saying you can execute arbitrary ADB commands in stock recovery. However if you have a full OTA zip and can get into stock recovery, you can choose the option on-device to flash an update over ADB according to Google's instructions. This will only work with a signed official OTA zip. But if you happen to have corrupted your stock ROM to an unbootable state, it is a possible path to get it back to bootable so you can access the contents.
Hello there,
I have some sort of a problem (although my phone is still working.. yet)
I recently flashed my OnePlus 6 with LineageOS 19.1 (coming from OxygenOS 11.1.2.2).
I flashed "copy_partitions.zip" first and then the official LineageOS 19.1 ROM without GApps,
but because I wanted to use some features, which needed at least the presence of Google Services, I flashed the "LineageOS for microG" (19.1) ROM.
Which worked like a charm.. besides I was very unhappy because of the lack of customization regarding color-theming and the changes made to the QuickSettings of Android 12 in general..
So I thought I could clean flash LineageOS 18.1 / ("Lineage for microG") to get the old theming back..
So what I did was installing the official custom LineageOS recovery from 18.1 (because microG had none for 18.1),
hit "Factory Reset" and afterwards applied the Lineage 18.1 zip over adb.
A message "Update package is older than the current build, expected a build newer than timestamp [...] but package has timestamp [...] and downgrade not allowed" along with the Question to install anyway appeared right after sideloading it to the phone.
I decided to hit "Yes" because I don't needed to backup any data from the phone and wanted to wipe clean anyways... (which I thought I did with "Factory Reset)
So I installed and afterwards rebooted to recovery to flash Magisk aswell..
After rebooting to system then, the phone entered the fastboot loop.
No matter what I do, it still doesn't boot to system after installing 18.1 from LineageOS recovery (also tried with the newest microG recovery from 19.1).
I also known you would wipe system, cache and data (and maybe vendor aswell) prior to a clean custom ROM flash (via TWRP)..
So flashed TWRP 3.6.2 (latest) for enchilada and tried to wipe my system, vendor and cache, but didn't manage to find "system" or "cache" on the advanced wipe menu, so I formatted and wiped data and wiped vendor.
Then installed LOS 18.1 via TWRP also..
But same problem - fastboot only.
also after my TWRP journey, sometimes when flashing the LOS recovery and booting it, a message appears on screen:
Failed to bind mount /mnt/staging/emulated/media/0 [...]
The thing is, I can install LOS 19.1 (microG) without any problems and it would boot,
but I just want to downgrade and I found no guide for my device (or any with ramdisk and A/B slots)..
And there is also no link to MSMDownloadTools for Android 10 (because onepluscommunityserver.com is offline)..
The links from this post and some other posts I found aren't working anymore..
- Is there a way to go back to LineageOS 18.1? What would be the intended way (not doing a downgrade but flashing clean)?
- Is my phone softbricked somehow? (partitions broken or corrupt?)
- Is it a firmware problem?
(I am on security patch from November 2021)
But I don't know what exactly happened to my firmware when flashing Lineage 19.1 over OOS 11.1.2.2
This is my first post as it is my first Android phone/flashing experience in general.. so I hope I got everything right from all I found out until now..
I really appreciate any help / even if it is just saying I messed up and need to go EDL mode... (if it truly is the case)
Thanks in advance.
You people are great!
o/