Hi everyone,
I am trying to install Lineage and am having some problems.
The flashing process does not complete for Lineage 18.1. With TWRP, the flashing process stays at 95% completion for over an hour. With Lineage Recovery (18.1), the flashing process hangs at "Patching vendor image unconditionally".
Rebooting the phone manually after flashing hangs, the device then only boots to a black screen with a blue indicator LED and the vibration motor runs for about three seconds.
Other versions of Lineage can be successfully flashed (17.1, 16), but do not boot, and exhibit the same black screen / blue LED boot issue.
I have also reflashed the stock image, which successfully booted. I then tried a completely clean wipe and reflash of Lineage (version doesn't matter), and the black screen / blue LED boot problem reappears. Even flashing Lineage "dirty" after a successful reflash of the stock OS results in the same black screen / blue LED boot problem.
All file hashes were checked beforehand to ensure a proper download. I have checked in TWRP that all partitions are EXT4 and not F2FS. The phone was running stock Android 7 (latest version) before unlocking the bootloader. I have also wiped the vendor partition, but this did nothing either. The problem occurs regardless of sideloading or loading the file from the SD card.
Other people are having the same issues (flashing process not completing for Lineage 18.1, other versions of Lineage having the black screen / blue LED boot loop issue.)
Can anyone offer any help?
Cheers,
mmx
After days of experimenting, I found a solution that lets me use at least Lineage 17.1.
The fix is to manually flash boot.img in fastboot AFTER flashing the Lineage install .ZIP in TWRP / Recovery.
The boot.img must be extracted from the Lineage .ZIP file.
Then it is flashed as such in fastboot / bootloader:
fastboot flash boot boot.img
However, Lineage 18.1 still does not install.
After this, I had the problem that the user data partition was inaccessible with Lineage 17.1.
I could not save any files to the user partition nor install any apps.
The fix was:
fastboot format:ext4 userdata
This probably was enough, but I couldn't tell because I got impatient that I was stuck at the Lineage startup logo for more than a couple of minutes.
So I booted into TWRP and formatted the user data partition as F2FS then as EXT4.
After a reboot, and a long wait at the Lineage boot logo, I was able to setup the phone and access the user data partition.
What was strange is that the partition already was formatted as EXT4 when I had the access issue.
I find it very off that just reformatting the partition fixed the issue..
Related
Hello,
I am having a problem where my phone is only, as far as I can tell, willing to boot into recovery. From the system, doing a normal reboot ends up in recovery, from powered off it goes into recovery, rebooting from recovery to system ends up back in the recovery, and the fastboot menu's "Continue" option goes reboots to recovery. The only way I can get into the system is to boot via fastboot -- i.e.,
Code:
fastboot boot boot.img
Where boot.img is the one packaged with the rom I am currently running.
This is not convenient because I need to connect it to a computer!
Is there some way to tell the bootloader to not boot recovery by default?
I have tried simply flashing the boot.img from above with:
Code:
fastboot flash boot boot.img
Which doesn't have any noticeable effect.
I suspect I broke something last night kicking around. I flashed the Open Beta 10 Modem & Firmware, then flashed the Open Beta 10 recovery, before changing my mind and installing TWRP 3-28 and Resurrection Remix v5.8. Somewhere in there, fastboot -w got run, but I don't think I did anything else potentially destructive.
Thanks for reading!
Hmm... Try install boot into recovery partition and recovery into boot? I know it's sound like a joke, but it will probably help you while u wait for a beter solution or just solution to repair that problem.
Anyway - maybe try flash old MM firmware?
A solution for me...
For anyone who rolls along and sees this in the future, my fix was:
0. Take a backup of sdcard AND data -- Step 2 will wipe data and sdcard without asking
1. Download the official recovery for the OnePlus 3
2. Use fastboot to boot (I didn't even have to flash) the official OnePlus 3 recovery AGAIN: WARNING: This step wipes all data without asking for confirmation!!!
I have now installed TWRP-3.0.4.0 and Resurrection Remix v5.8.1-20170202 and everything seems to be working just fine.
Thanks to @sylviohneto for finding this fix here: https://forum.xda-developers.com/oneplus-3/help/critical-bootloader-boot-recovery-fresh-t3530283
I had same problem so for that just take nandroid backup of data and while in turn copy it to pc and any other backup of data you need then format all the partions and reinstall rom and restore data... And if your lock screen have security then check Google you will have to delete a file called locscreen.db from file manager in twrp to access your phone
I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue
Flashing a lower version and then the 28 version back helped me... Had the same problem
jaganmohans said:
I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue
Click to expand...
Click to collapse
1 ) flash stock recovery and sideload full zip of 3.2.8 oxygen os
2) boot to system
3) reboot to stock recovery
4) sideload full zip of 4.0.1
5) boot to system
6) boot to bootloader and flash twrp -28 recovery (adb fastboot flash)
7) after flashing boot to twrp recovery from bootloader
8) flash SU SR2 v2.79 and boot to system
Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh
I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.
Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.
Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards
I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.
Hello.
Tried flashing older stock rom via TWRP.
TWRP installed fine, worked fine, flashed vbmeta, still everything worked.
Downloaded ROM, put it into the sd card, went into twrp, formatted data, rebooted into twrp again, wiped Dalvik/ART cache, cache, system, vendor and internal memory, tried flashing, gave error 7, with "mkdir folder file not existing or whatever". In twrp i went into terminal, made a directory /cache/recovery, tried flashing, worked. Wiped dalvik and when i tried to reboot, the backlight turns on for a split moment and then it turns off.
Recovery does the same, and fastboot lights up the screen with the image of fastboot but it turns off. Plugging it with the usb makes it so it repeatedly turn on backlight and off again.
What does this mean? Device dead? Any help?
Thank you.
Maybe try flashing a custom rom
With what tools if I may ask? Any advice you can give me?
Fastboot doesn't stay on like it should, the screen just flashes the fastboot picture and it restarts again. Recovery does the same.
Try following bliss rom guide with installation of twrp
Trying to do anything with ADB tools just gives me a "< waiting for any device >".
I'm sure there's other ways of flashing twrp
VirusWar said:
Hello.
Tried flashing older stock rom via TWRP.
TWRP installed fine, worked fine, flashed vbmeta, still everything worked.
Downloaded ROM, put it into the sd card, went into twrp, formatted data, rebooted into twrp again, wiped Dalvik/ART cache, cache, system, vendor and internal memory, tried flashing, gave error 7, with "mkdir folder file not existing or whatever". In twrp i went into terminal, made a directory /cache/recovery, tried flashing, worked. Wiped dalvik and when i tried to reboot, the backlight turns on for a split moment and then it turns off.
Recovery does the same, and fastboot lights up the screen with the image of fastboot but it turns off. Plugging it with the usb makes it so it repeatedly turn on backlight and off again.
What does this mean? Device dead? Any help?
Thank you.
Click to expand...
Click to collapse
i think it's dead
-when the twrp gave you the error you should log it
-you should format data after flashing a rom ,not before (and only few roms require it)
your only option is flash VBMETA then TWRP again and see if it work
use the unofficial twrp : (3.3.10)
https://forum.xda-developers.com/re...ecovery-unofficial-twrp-xiaomi-redmi-t3997267
You should have formatted data partition after flashing the rom(not manually create those folders). You would be okay.
Any solution?
Hello,
I have a strange problem with Galaxy A5 2017 after installing twrp + lineage 18.1. I will explain the problem in sub points.
1) in January on stock software I installed (according to instructions from XDA forum) root, twrp (via ODIN) and bypass with memory decryption. Then I installed Lineage 18.1, Gapps, Magisk and debloater on it to remove unnecessary apps.
2) The phone worked fine until mid-April. Some update was installed and the phone died.
3) The phone wouldn't boot up after the update and only the TWRP logo was looping (logo kept flashing).
4) the phone couldn't boot up, but after I found the only way to get the system to boot up was to enter command "adb reboot bootloader" from windows console. The system booted, but after another reboot unfortunately it was the same thing - the TWRP logo was looping.
5) I managed to upload Lineage Recovery via ODIN, but unfortunately this didn't change anything. Phone was booting to recovery only (but it was working). I tried to update via ADB Sideload from recovery - also without success. Interestingly, the only way to fix it was to fully format with the system partition from recovery and re-upload the system. This worked, and Lineage booted into the android interface, but on the next reboot I unfortunately only had the Lineage loading logo visible for 10-15 minutes - then a reboot into recovery. I had to repeat the formatting and re-upload the system.
6) Interestingly, when I used the combination - lineage recovery, full format, twrp 3.6.1 (via ODIN) - TWRP booted normally and I could install LineageOS. The system would only boot once, and after the next reboot the TWRP logo would loop again.
7) The last problem I noticed is that if I load Lineage system, gaaps package and magiska via TWRP or Lineage Recovery, the system will never boot - either it will loop the logo (if using Lineage Recovery) or the phone will not load the system, it will reset and loop the TWRP logo indefinitely (if using TWRP recovery).
Does anyone know a solution how to restore the phone? Will it still work or for example NAND memory is dead and nothing can be done? Best regards