Guys. Not first time I install lineage and open gaps. Some time ago I already had lineage after original ROM on my A510f.
I wanted to update Lineage becouse something happens with system. I used TWRP, andsame system installed great but later have a problem with all opengapps (arm) instalation. Maybe not instalation because all goes OK, but after rebooting phone can not start and trying to ask for account. Nothing works. All version of OG checked on 17.1 and 18.1 and different TWRP. Have no idea what I make wrong or what happens, but still this same problem. I wiped all what was possible in TWRP and OG installed from SD. System ok, OG - not. Help.
Related
SOLVED: TWRP 3.0.3 uploaded by sub77 on androidfilehost doesn't properly recognize devices. I flashed the older 3.0.2-8 and it works fine and let me able to flash matisselte rom. Anyway, I flashed crdroid but It's stuck on boot animation.
Hello everybody,
I recently bought a secondhand Galaxy Tab 4 SM-T535. It has the android stock rom 5.2 and I wanted to flash a CM or any custom rom to speed it up a bit and remove all pre-installed apps. I did flash TWRP through Odin and it works fine, then I copied Gapps for 7.1 pico versión and crDroid custom rom based on LineageOS 14.1 and nougat 7.1 for matisselte aka Tab 4 SM-T535. I followed instructions (that are pretty the same for every custom rom) so I wiped dalvik, cache, system and data, then I flashed (tried to) crDroid 14.1 zip and... TWRP says something like: unable to flash zip, it is for device matisselte but this is matissewifi. Wtf?! So, ok. I thought I'm blind and I got the wrong version, I downloaded the matissewifi version, tried to flash again and it did flash. Then I flashed Gapps and rebooted, now it goes directly in download mode and says Could not boot normally... What is happening? I also tried CM 14.1 for matissewifi, it flashes but can't boot and I'm unable to flash the matisselte version. Why?
it is for sure the LTE tablet, I read it in settings and info in the android stock rom and it has a sim slot, so it can't be the wifi one.
Thank you in advance for any reply. Let me know if you need more informations. Thanks.
P. S. I already searched in the forum and didn't find any similar case.
Hi,
has anybody found a solution...?
seen too late.....
"SOLVED: TWRP 3.0.3 uploaded by sub77 on androidfilehost doesn't properly recognize devices. I flashed the older 3.0.2-8 and it works fine and let me able to flash matisselte rom. Anyway, I flashed crdroid but It's stuck on boot animation. "
So glad you posted this because I had failed in all my attempts and had tried a few TWRP versions but not that one, which worked perfectly with Lineage 14.1.
Hey,
there are already three different Lineageos (microg) 16 builds. But after I am flashing one of them, my Xiaomi Mi A1 boots into complete darkness/ black screen. Any idea what are doing wrong?
Workflow:
boot twrp recovery.img
flash lineage 16 (microg) e.g. lineage-16.0-20190409-microG-tissot.zip
reboot system
-> black screen
When I reflash 15.1 (lineage-15.1-20190313-microG-tissot.zip) everything works as expected! Any idea?
Flash latest stock Pie and then 16 LOS.
Maybe the problem is the recovery. What recovery do you use?
Similar upgrade and failed Lineageos 15.1 install
Never_Sm1le said:
Maybe the problem is the recovery. What recovery do you use?
Click to expand...
Click to collapse
Hello and good day! I'm planning to follow a similar upgrade path on a HTC M10 running Android 8.0 via Lineageos 15.1 install. Lineageos 15.1 installs with no errors in TWRP, device is rebooted, Lineageos logo crosses screen for several minutes, and device returns to TWRP recovery instead of starting phone. After the second re-install, I installed the OEM boot.img and same outcome. Any suggests how to proceed next?
[email protected] said:
Hello and good day! I'm planning to follow a similar upgrade path on a HTC M10 running Android 8.0 via Lineageos 15.1 install. Lineageos 15.1 installs with no errors in TWRP, device is rebooted, Lineageos logo crosses screen for several minutes, and device returns to TWRP recovery instead of starting phone. After the second re-install, I installed the OEM boot.img and same outcome. Any suggests how to proceed next?
Click to expand...
Click to collapse
You should post this in the HTC M10 section or the LOS 15.1 thread for your phone. The solution works here may not work for your phone.
Gudiance appreicated.
Guidance is appreciated and will do. Thanks. Danny.
Hi, I'm on LineageOS 14.1 Optimized by JDCTeam.
However I'm not able to install the latest Magisk.
Is it just not possible anymore because you need fastboot to install a patched boot.img?
I tried flashing through the regular way as a .zip file (just renaming the magisk apk into .zip) in TWRP 3.2.x.x. Also tried flashing the patched boot.img file from the rom through TWRP.
But whenever I flash it and reboot, everything force closes.
Any help on that?
Latest TWRP, latest LineageOS version (18.1), latest Magisk here. I have no issues with flashing Magisk in TWRP. In fact, I have lately had to dirty flash LineageOS then Magisk in TWRP, as a standard update in LineageOS via its updater causes a bootloop.
Fortunately this isn't my main device so....
In your case, I would update to the latest LineageOS as the version you have is really old. Updating may help.
Strephon Alkhalikoi said:
Latest TWRP, latest LineageOS version (18.1), latest Magisk here. I have no issues with flashing Magisk in TWRP. In fact, I have lately had to dirty flash LineageOS then Magisk in TWRP, as a standard update in LineageOS via its updater causes a bootloop.
Fortunately this isn't my main device so....
In your case, I would update to the latest LineageOS as the version you have is really old. Updating may help.
Click to expand...
Click to collapse
Thanks for the reply, but I want to stay on Android 7 Nougat, so maybe it's in fact not possible anymore. But maybe somebody else has an idea.
crysen said:
Thanks for the reply, but I want to stay on Android 7 Nougat, so maybe it's in fact not possible anymore. But maybe somebody else has an idea.
Click to expand...
Click to collapse
Check my S4 Unified Collection & Guides. You will find everything you need.
Hi everyone,
I wanted to load a custom rom on my op2. I am not using it anymore and it still got cyanogenmod on it. I tried Lineage 18.1 but got "Error 1 - Error installing zip file".
I tried another TWRP version but same results. After that I tried OxygenOS 14 OTA, this one installed fine but i still can't install lineage neither 17.1 nor 18.1.
How can I fix this?
Okay got it working now.
First I had newest TWRP but no rom and got error 1.
Than I tried older TWRP without rom - error 1
Installed stock OS + old TWRP - error 1
updated TWRP + stock os installed and it worked.
Hi I have firstly upgraded the official firmware on a Shield Android TV 2015 (Foster) to version 11 Android TV OS then i decided I hate it so I flashed twrp worrked fine got Lineage 17.1 Android 10 on it now but I add Gapps from open Gapps versions ARM x64 nano or pico it doesn't matter which I add if you add any Gapps then it won't boot into the Lineage OS it just sits in a seemingly semi-brick state only ever providing the boot animation circles only it never passes although the system is working to pickup adb otherwise it would be a full brick.
Can someone help literally point out what I need to do to get it working with play store please.
My assumption is it requires a custom Gapps not regular Gapps as is the case with some os's sometimes but i cannot find links to try for anything other than stock Gapps.
Have you installed GApps before initial boot ?