I'm on the official build of LOS 14.1. I've tried flashing other ROMs on Nougat but i bootloop on every single one. I clean flash too. I make sure to wipe everything besides internal storage. I had an older version of TWRP . it was like version 2.8 or something but i just updated it to 3.2.1.0 and it still doesnt let me flash ROMs. I tried flashing Oreo based ROMs and it does the same thing. I've only been able to successfully run the official LOS 14.1, and CM 13.1 (havent tried 14.1). I've tried different variants of LOS on 14.1 and 15.1. Is there something that i'm missing? if it helps i found my old OPO and havent used it since january 2016. I decided to try out new ROMs but they're not booting. Any help? Thanks.
Related
I have wiped the data, cache, dalvik cache and system partition and format them to ext4 (recovery TWRP 3.0.3-2 by TugaPower). After that I have flashed the ROMS and the mini GApps. Then when I tries to boot, and it takes more then 20 minutes to boot (and the OS still doesn't booted).
I tried the unofficial LineageOS, RR 5.8, AICP but I stuck in bootloop in every Nougat ROM. The Marshmallow version of each is working, just the Nougat have bootloop issues.
Only the AOSP Nougat for OnePlus One succeeded to boot...
How can I solve this? Why all the CM14 based ROMs are not booting in my phone?
I'm having the exact same issue. Tried Lineage and Tugapower. Had to revert back to Sultan's CM13.
I tried with nano gapps for cm14.1 & pico gapps for tuga 13.1 works fine.
ppp99 said:
I have wiped the data, cache, dalvik cache and system partition and format them to ext4 (recovery TWRP 3.0.3-2 by TugaPower). After that I have flashed the ROMS and the mini GApps. Then when I tries to boot, and it takes more then 20 minutes to boot (and the OS still doesn't booted).
I tried the unofficial LineageOS, RR 5.8, AICP but I stuck in bootloop in every Nougat ROM. The Marshmallow version of each is working, just the Nougat have bootloop issues.
Only the AOSP Nougat for OnePlus One succeeded to boot...
How can I solve this? Why all the CM14 based ROMs are not booting in my phone?
Click to expand...
Click to collapse
nuuro said:
I'm having the exact same issue. Tried Lineage and Tugapower. Had to revert back to Sultan's CM13.
Click to expand...
Click to collapse
I had a similar problem with all the ROMs you mentioned failing to boot too when coming from CM13. What worked for me was to first flash a nightly from this thread.
http://forum.xda-developers.com/oneplus-one/development/lineageos-unofficial-nightly-t3528587
Afterwards I was able to flash and boot into AICP and TugaPower. Don't know if it will work for you guys, but give it a try.
I have the following installed:
[url]https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670[/URL]
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
-Snowrider- said:
I have the following installed:
https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
Click to expand...
Click to collapse
Try the following :
-uninstall magisk using uninstaller(available in magisk forum)
-clear system,data,cache,dalvik
-install only the rom with out gapps
if it boots properly then you can install the gapps later or else if u find flashing gapps is causing the bootloop then use an older version and double check the compatibility.
if still not just try out another nougat rom
Thanks for the suggestion.
I tried your steps with the latest stable slimrom 7.1.2, lineage 14.1 and carbonrom 5.1 and I am still seeing the same issue. I was able to clean install the lineage 15.1 beta I linked to though in addition to restoring my backup as I have done before. I might try to clean install a different 8.1 (AOSP for example) and see if that one works. This will help narrow down if the issue is caused by 8.1 in general or specifically something that the lineage 15.1 beta has done.
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
CedArctic said:
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
Click to expand...
Click to collapse
This is what I ended up doing and it did the trick. Thank you for the suggestion.
They made a wiki on Beryllium (https://wiki.lineageos.org/devices/beryllium) and some other links to the official build (https://download.lineageos.org/beryllium) but they removed it.
I don't know what was the reason.
They rolling out the Lineage 16 PIE on couple devices like Oneplus 5/5T, Huawei P20 Pro, Xiaomi Mi Note 3, etc. (https://www.androidpolice.com/2019/...1-oneplus-phones-galaxy-s5-and-other-devices/)
wasn't released it failed but it is expected to succeed soon.
bower1994 said:
wasn't released it failed but it is expected to succeed soon.
Click to expand...
Click to collapse
Thank you for the response, out of curiosity, what was failed in the latest official build?
https://gitlab.com/LineageOS/builder/android/pipelines/49950700/builds
Yesterday all builds failed on that user/server
#### build completed successfully (01:34:25 (hh:mm:ss)) #### Guess we can expect a build in a few hours?
The nightly is available now
The inital nightly build seems to be broken, at least for me. Can't boot into system.
Same here, installed via adb sideload. system displays the boot animation for a while, then I end up in recovery every time.
tiantnait said:
Same here, installed via adb sideload. system displays the boot animation for a while, then I end up in recovery every time.
Click to expand...
Click to collapse
I tried again, this time flashing the 9.2.25 vendor firmware instead of 9.3.1, LOS flash also via sideload. It's working now!
no problems here.. clean flash, flashed firmware 9.2.25, los official nightly, pico gapps and magisk 18.2, wipe cache/dalvik and reboot. it runs awesome
Strel0ka said:
I tried again, this time flashing the 9.2.25 vendor firmware instead of 9.3.1, LOS flash also via sideload. It's working now!
Click to expand...
Click to collapse
No luck here. I also tried flashing 9.2.25 first (had 9.2.21 before). Still same boot loop. Must be something else.
(magisk, no google services, encrypted fs, not a clean install [update from UNOFFICAL 20190220])
going back to UNOFFICAL build works fine for now...
tiantnait said:
No luck here. I also tried flashing 9.2.25 first (had 9.2.21 before). Still same boot loop. Must be something else.
(magisk, no google services, encrypted fs, not a clean install [update from UNOFFICAL 20190220])
going back to UNOFFICAL build works fine for now...
Click to expand...
Click to collapse
So you performed a dirty flash of official LOS over unofficial LOS? That's like dirty flashing NOS over LOS. If you want to switch over to the official branch, I highly recommend starting from scratch.
My current setup is official LOS with microg + magisk and Encryption, no issues so far.
Yep.. Official build is on!
Hi,
i'm trying to build Q for this Clark, anyone want to test?
If yes, pm me on Telegram (@DarkDroidDev)
EDIT: Join telegram group @clarkdev for beta testing or see development
Hi, i'm in!
DarkDroidDev said:
Hi,
i'm trying to build Q for this Clark, anyone want to test?
If yes, pm me on Telegram (@DarkDroidDev)
Click to expand...
Click to collapse
Link?
i 'm in too..
Link?
@DarkDroidDev already sent the DM from telegram
Выложите пожалуйста √17
Development resumed, who want to see progress or help with testing, feel free to join telegram group
@clarkdev
Any chance you could provide links without telegram?
Not looking to add another messenger that I'll forget I have in 6 months lol
Maybe you are also interested in my efforts to bring clark to 17.1
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/lineage-17.1
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1
Additional patches: https://gist.github.com/chrmhoffmann/dd232f142dcde4c590a659e85944f7a4
The above trees are not supposed to remain stable, I do force pushs until clean and uploadable to lineage (if ever).
Very early testbuild: https://www.androidfilehost.com/?fid=4349826312261826984
Credits go mainly to the lineage community and their commits on gerrit, and of course: hashbang, randomblame and highwaystar - esp for the camera headers .
I'd also be interested but don't use Telegram
ac2323 said:
I'd also be interested but don't use Telegram
Click to expand...
Click to collapse
has anyone tried chrmhoffmann's rom yet (post #10)? I'm interested to see if it boots and how stable it is. Also he's openly sharing his source code.
Nice.
Wheels564 said:
has anyone tried chrmhoffmann's rom yet (post #10)? I'm interested to see if it boots and how stable it is. Also he's openly sharing his source code.
Click to expand...
Click to collapse
Yes, working nice.
@DarkDroidDev Hey, how did you extract the proprietary blobs? The instruction says that one needs to have an installable zip of LineageOS for clark, or already have the device runnning the LOS. I tried to extract it just from my stock Moto X Style with the script and it did something, but I'm not sure if it's going to work.
Edit: I'm also interested in testing the 17.1 build, since the one I'm trying to build following the instruction is 14.1 and actually it fails because of lack of some vendor files :/ But I'm also not interested in joining Telegram
Edit: Oh, I missed the @chrmhoffmann post!
hi, chrmhoffmann. thank you for your work.
chrmhoffmann said:
Maybe you are also interested in my efforts to bring clark to 17.1
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/lineage-17.1
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1
Additional patches: https://gist.github.com/chrmhoffmann/dd232f142dcde4c590a659e85944f7a4
The above trees are not supposed to remain stable, I do force pushs until clean and uploadable to lineage (if ever).
Very early testbuild: https://www.androidfilehost.com/?fid=4349826312261826984
Credits go mainly to the lineage community and their commits on gerrit, and of course: hashbang, randomblame and highwaystar - esp for the camera headers .
Click to expand...
Click to collapse
Hi, chrmhoffmann. Thank you for your work. I previously tested your 20200718 upgrade. I have installed the same date recovery and the latest magisk20.4. Unfortunately the system will not start. I also tried wipe system wipe cache wipe data and reinstalled it again, but it still didn't work.
I cannot find any kind of forum for @DarkDroidDev . I also can't find a forum for @chrmhoffmann but I found the andoridfilehost link for him with his builds.
https://androidfilehost.com/?a=show&w=files&flid=313335
I did a lot of trial and error and I notice that he is posting his own Lineage recovery which through Googling I find is apparently most use for updating a ROM. I am using the latest Clark TWRP 3.4.0-0 and once you install your first LOS17 you can no longer flash an updated build because TWRP seems to be unable to wipe an android 10 build.
@chrmhoffman has LOS Recovery builds that do allow you to update his LOS17 to a new build. His latest LOS recovery is named recovery.img from 8/19/20. LOS Recovery is not very functional and likewise does not even have the option to wipe. The only way I have been able to wipe these LOS builds is to flash back to stock Android 7 Moto ROM and start over fresh. I am using NPHS25.200-23 which is the last Moto ROM for Clark. I have found flashing back to stock is a good practice when moving to a new ROM and I am getting much better with practice so it is not so onerous.
So here's what I do to flash the initial working version of LOS 17 on my Clark. I have found you can use any of his builds. Thus you can start with his latest build 20200715.
Flash stock Android 7 using fastboot
Flash TWRP using fastboot
Flash 20200715 build and latest Android 10.0 Open Gapps with TWRP
This is pretty much the standard old way that we always do. Now if you want to update 20200715 with either a clean or a dirty flash when he drops a new build you cannot use TWRP to do this because you can't wipe. If you want to clean flash a new build you will have to start over with stock. If you want to update with a dirty flash then you will need LOS Recovery. Easiest way is to flash the LOS Recovery image with TWRP but you can also fastboot flash it.
Flash LOS Recovery
Update ROM from LOS Recovery.
I have been able to flash Magisk from Stock and it seems to work fine but I have not tried yet to see how LOS Recovery handles Magisk. I am looking for help from anyone with more experience than I have to explain this better and most importantly find out where discussion is happening. The ROM works beautifully and so far much better than @randomblame ROM. No boot problems, WiFi tether works great, camera is better. So far it is great. So give it a try.
kb8no said:
I cannot find any kind of forum for @DarkDroidDev . I also can't find a forum for @chrmhoffmann but I found the andoridfilehost link for him with his builds.
https://androidfilehost.com/?a=show&w=files&flid=313335
I did a lot of trial and error and I notice that he is posting his own Lineage recovery which through Googling I find is apparently most use for updating a ROM. I am using the latest Clark TWRP 3.4.0-0 and once you install your first LOS17 you can no longer flash an updated build because TWRP seems to be unable to wipe an android 10 build.
@chrmhoffman has LOS Recovery builds that do allow you to update his LOS17 to a new build. His latest LOS recovery is named recovery.img from 8/19/20. LOS Recovery is not very functional and likewise does not even have the option to wipe. The only way I have been able to wipe these LOS builds is to flash back to stock Android 7 Moto ROM and start over fresh. I am using NPHS25.200-23 which is the last Moto ROM for Clark. I have found flashing back to stock is a good practice when moving to a new ROM and I am getting much better with practice so it is not so onerous.
So here's what I do to flash the initial working version of LOS 17 on my Clark. I have found you can use any of his builds. Thus you can start with his latest build 20200715.
Flash stock Android 7 using fastboot
Flash TWRP using fastboot
Flash 20200715 build and latest Android 10.0 Open Gapps with TWRP
This is pretty much the standard old way that we always do. Now if you want to update 20200715 with either a clean or a dirty flash when he drops a new build you cannot use TWRP to do this because you can't wipe. If you want to clean flash a new build you will have to start over with stock. If you want to update with a dirty flash then you will need LOS Recovery. Easiest way is to flash the LOS Recovery image with TWRP but you can also fastboot flash it.
Flash LOS Recovery
Update ROM from LOS Recovery.
I have been able to flash Magisk from Stock and it seems to work fine but I have not tried yet to see how LOS Recovery handles Magisk. I am looking for help from anyone with more experience than I have to explain this better and most importantly find out where discussion is happening. The ROM works beautifully and so far much better than @randomblame ROM. No boot problems, WiFi tether works great, camera is better. So far it is great. So give it a try.
Click to expand...
Click to collapse
From what I've seed Darkdroiddev removed Clark from his Github so I assume he is no longer working on this phone and this thread is probably dead. Randomblame hasn't posted since February. chrmhoffmann's thread https://forum.xda-developers.com/mo...opment/unofficial-lineage-17-1-clark-t4123077 actually has a link to official Lineage gerrit which means we are well on our way to becoming official Lineage again. Meanwhile I'll keep posting LOS 14.1 for MMBL until we get there.
I'm having a redmi 6A (codename: cactus) device. I decided to install a custom rom to boost the performance of the device. Since there weren't much options of official builds for the device, I chose to try a unofficial build.
Here's the telegram group i found that rom on :Redmi 6A Official Updates
I chose the Octavi OS build from it.
As usual I unlocked the bootloader, installed twrp custom recovery and ready to flash the zip file.
Btw, here's the zip file I flashed : Octavi OS zip
I wiped all the necessary options and flashed the zip without flashing magisk(coz I don't prefer to root). After restarting, the miui logo came but the rom won't booted ever since waiting for hours, so I reverted back to stock.
But after few weeks, I again planned to flash the same build but with magisk file.. And surprisingly enough, the rom logo came and it booted without hassle.
But I wanted to know the exact reason for the former, so I can report it to the dev and he might fix it..
Thanks for your time to read my this sh*t here, any reply would be appreciated .