Until now I used a LOS 14.1 with GApps and I decided now to upgrade to lineage-17.1-20200530-nightly-m8d-signed.zip by flashing TWRP 3.3.1-0 and install the rom afterwards.
Everything worked fine except of problems with SD card (Failed to initialize).
But after a several reboots my device got stuck in a bootloop I don't know what has gone wrong - I just have installed apps and customized some settings.
This problem also occurs every time I recover a backup with TWRP.
I did some trials with:
- Flashing 10 different recovery images from TWRP 2.8.1-0 to 3.3.1-0
- Installed Lineage 16.0 and 17.1. Could not find any downloads for 14.1!?
I have also tried installing multiple mokee builds: Same behavior! And other users have similar problems with their devices. So this does not belong to m8d devices only and also not only to lineage but maybe to AOSP!?
I have flashed only TWRP and lineage - not the firmware. And i have exactly done formating as described in the installing-instructions: Formating and wiping system and cache. But additionally I have tried many variants.
I'm not an expert, but I have a look in the dmesg.log and did not find anything interesting.
I have compared a log of a new and fresh installed LOS 17.1 (with NO bootloop) with a damaged (bootloop) LOS.
Info:
I've noticed a repeating and very quied sound like "knock, knock" while got stock in bootlop..!?
---
Now I have installed crDroidAndroid-9.0-20190315-m8d-v5.2 and this works well (e.g. recovering backups) except of smaller issues (as i found so far):
- can't get screen rotation working
---
What I don't understand:
Lineage 16 (based on Android 9) fails, but crDroid (based on Android 9, too) works!?
Is this a matter of a too old firmware? Can't find a new one for my S-ON device:
- modelid: 0P6B64000
- cidnum: HTC__102
Thanks,
Marco
happens the same to me following this post https://forum.xda-developers.com/htc-one-m8/general/rom-lineageos-16-0-htc-one-m8eye-t4081877 and the TWRP by @HarshDB is not working, that goes to the stock recovery menu, I tried another TWRP but that rom doesn't work
raisonier said:
happens the same to me following this post https://forum.xda-developers.com/htc-one-m8/general/rom-lineageos-16-0-htc-one-m8eye-t4081877 and the TWRP by @HarshDB is not working, that goes to the stock recovery menu, I tried another TWRP but that rom doesn't work
Click to expand...
Click to collapse
That TWRP is only for M8_Eye and not for regular M8 or M8 dual sim.
Which one do you have?
Related
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc, does anyone know what the problem could be?
Have you flashed the latest firmware? If not, I think this is why due to you being on a very old version (6.0.1) and as you are not flashing official OxygenOS you are not getting the newest firmware.
Download and flash the latest firmware here:
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Pick the right one for the ROM you are flashing (For Freedom OS installing firmware Open Beta 14 - Firmware + Modem under 7.1.1 should be good.)
Note: After you have flashed the firmware the next time you reboot the phone it will appear to not turn on for a few seconds, this is normal while it updates, don't worry
Let me know if you have any questions
I tried to flash my Wileyfox Swift 1 to Lineage today, from its Android 7.0 rom.
I downloaded twrp-3.1.1-crackling.img and lineage-14.1-20170703-nightly-crackling-signed.zip.
I then followed the instructions on the Lineage OS site for a Wileyfox Swift to the letter to get the Lineage rom flashed (with the one exception being I also "wiped" Internal Storage, along with Cache, System and Data partitions). I didn't try to install, or want to install, the Google Apps.
Everything worked exactly as expected, right down to the absolute final step in the guide. When I chose to Reboot, then System, I just found myself back in the bootloader. No matter what I do, I just keep booting back up to this. I still have full access to recovery mode, but I just can't load an OS or get past the bootloader screen when I restart.
I have an old Cyanogen mod I have been able to revert to in the mean time, but I'm struggling to understand what I did wrong here. Can anyone provide any help/suggestions?
I tried again this afternoon and everything appears to have worked. I've loaded Lineage OS successfully and everything is working well. I'm still not sure what happened the first time, but all is good now.
I had the same issue. After installing an old CM13 release (with TWRP), turning everything off and then start from scratch with LOS 14.1, everything worked. It seems that CM13 does have a side effect that is needed for LOS 14.1.
Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
ZeitgeistGlee said:
Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
Click to expand...
Click to collapse
Try this:
https://forums.oneplus.com/threads/...-3-3t-and-go-back-completely-to-stock.456232/
ZeitgeistGlee said:
Hey all,
Bit of a weird one here that has me scratching my head.
I went to do a clean install of Oxygen OS 5.0.8 (the only one I can find on the OP site for the OP3) yesterday coming from rooted LineageOS 15.1 and the phone was stuck in a bootloop for well over an hour. I force rebooted it into recovery (which was still TWRP as opposed to OOS recovery), wiped everything tried installing OOS again (fresh download) and got the same result. Little bit of a panic then began to set in but as I could still boot into Recovery and Bootloader I wasn't too worried.
On a whim I downloaded the latest LineageOS 15.1 nightly and GApps, wiped everything and flashed and lo and behold it worked fine. Happy to have a working phone again I said I'd leave things alone for the rest of the day.
Assuming that it was just weird bug or whatever I tried installing OOS 5.0.8 again this morning (redownloaded again just to be safe) and I'm now 30 minutes into another bootloop.
Anyone have any ideas?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Read his second post. Wrong TWRP version may lead to this. 3.2.3.1 encryption issues.
Is had the same issue, i ended up with a fastboot installation. Al is working again.
Hi,
I m using Lineage 16 (20190813 111617)build on my HTC 10 (European model) I wanted to to try Pixel Experience with full wipe, format. But after flashing the ROM could not connect with WiFi. So could not continue with setup. Therefore after re-boot with TWRP I did following :
1) Restored all data except System and System image.
2) Then re-booted and device opened without any problem. However, HTC 10 could not detect SIM card and having error phone dialer.
I have replaced the SIM, re-booted the phone, wipe and factory reset. None of them helped. So I have again restored the Lineage again.
Then I had attempt to flash other 9,0 ROMs such as XenonHD, AOSİP 9.0. But all of them had stacked on boot-loop logo. I hope you can help to resolve above problem so I can enjoy to taste those ROMs on my beloved HTC 10.
Many thanks in advance.
I recently upgraded the Motorola One Action LOS4M to the latest 4-7-2022 build and, after the typical LineageOS loading screen (which lingered an abnormal amount of time), it shut off on its own and was sent to the LineageOS Recovery saying the ROM was "corrupt," and to do a factory reset to possibly fix it. After trying that a few times (including a TWRP advanced wipe), I get the same result of being sent back to the recovery with the same message installing the Official ROM from LOS4M official site. Anyone else having this problem with this build, and any of the recent Official LineageOS builds (not the 'for MicroG' builds) so we can tell where the issue is? The previous build (3-21-2022) still works fine so had to downgrade to get the phone to work.
You should try the new 19.1 build and see if it works.
From reading the wiki, you should use "MindTheGapps".
If you're not looking to do that, isn't a way to use MicroG "rootless" (without flashing it)?
This could be a bug, as none of the builds are stable (nightly).