I haven't rooted a phone for a long time. If I do, lineage is what I would want. I would assume we will get it at some point?
Related
I was trying to install Lineage OS on my Nextbit Robin. I have never done this before, which is why I messed it up. I install TWRP and unlocked my bootloader, but I did not put the Lineage OS ROM.zip file into my internal memory. Sideloading isn't working, and since Nextbit has been bought by Razer, the official stock ROMs don't work, etc. I need help in installing an OS (stock is fine). If you could also guide me through installing Lineage OS, that would also be appreciated.
Thanks!
Let me know if you need more info.
MyerFire said:
I was trying to install Lineage OS on my Nextbit Robin. I have never done this before, which is why I messed it up. I install TWRP and unlocked my bootloader, but I did not put the Lineage OS ROM.zip file into my internal memory. Sideloading isn't working, and since Nextbit has been bought by Razer, the official stock ROMs don't work, etc. I need help in installing an OS (stock is fine). If you could also guide me through installing Lineage OS, that would also be appreciated.
Thanks!
Let me know if you need more info.
Click to expand...
Click to collapse
Why do you use sideloading ?
Just boot into TWRP , go to mount and select enable MTP.
Then connect your phone to your PC and transfer the lineage os zip file ?.
There are unfortunately no ROMs specifically for this device yet, but has anyone tried to use a generic treble ROM on this device?
Thanks in advance
I have tried several treble ROMs, the majority don't even boot. Lineage os worked but was buggy. The more stable one was Havoc, if I remember correctly.
I was interested in the Q developer ROM but it didn't work. I'm back to the stock pie Rom, since there is no Netflix HD support on those treble roms.
gtaadicto92 said:
I have tried several treble ROMs, the majority don't even boot. Lineage os worked but was buggy. The more stable one was Havoc, if I remember correctly.
I was interested in the Q developer ROM but it didn't work. I'm back to the stock pie Rom, since there is no Netflix HD support on those treble roms.
Click to expand...
Click to collapse
Hi Mate, I've been trying to flash a working GSI rom but had no success so far(have an SM-T830). In the past have built ROMs for Tab A 10.1 and flashed them many times with TWRP and Odin so I just cannot understand am I retarded to not being able to flash a working one or what? Have managed to put TWRP 3.3.0.0 and TWRP 3.3.0.1 on the device. Have tried my own arm64_aonly image first. Then an original AOSP one, then a Lineage OS version, at the moment I am just downloading Havoc. The result (apart from the havoc) was always the same. The flashing went through successfully and when I rebooted into system the very fist image came up and boot looped from there. I am always able to go back to TWRP and try another image or through odin can restore the factory image but none of the GSI images seem to be working. So, here is my question. As you managed to get a Lineage and Havoc working, can you tell by looking at it what am I doing wrong please:
1.: OEM unlock
2.: TWRP install with odin
3.: Boot straight into TWRP to prevent being overwritten
4.: TWRP: format data
5.: Flash system image (arm64_aonly)
From here have tried so many things like,
- booting straight into system
- booting back to recovery
- flashing the force_decryptor or how the hell is that called
- formatted data again as the decryptor suggests
The result was always the same, boot looped from the very first image. It seems like that the image is not getting flashed and even if TWRP says was flashed right it is just not there. I'm literaly pulling my hair as it was so easy and straight forward with the Tab A 10.1, but with this ….. thanks for your answer in advance
anyone have any luck with treble GSIs? i can only get arrowos to boot and even then i cant install gapps.
droidbot1337 said:
anyone have any luck with treble GSIs? i can only get arrowos to boot and even then i cant install gapps.
Click to expand...
Click to collapse
I used AOSP 9.0 and LineageOS 16 with OpenGApps Pico and both work but are very buggy.
After hours of trying to figure this out myself i ended up finding two ROMs that work for me. I was running stock Android 9 with september's security updates when testing these out:
Roms that i tried, that did NOT work:
BlissOS
ArrowOS
Lineage16
The ROMs that DID work for me were:
phunsson's Treble Experimentations
microG ufOfficial
The only 2 bugs that i've seen so far have been a small graphical glitch of quickettings not staying within the bounds of the pulldown and MTP not working at all. These are both present in both ROMs (The microg ROM uses phhusson's rom as the base). Neither of these bother me all that and i'm very happy to be able to move to microg and not have all the google/samsung bloat hogging my tablet and constantly trying to ping their motherships.
Here's a great list of Generic System Image (GSI) ROMs that you can click scroll through and try downloading and flashing to your device to see if you have any luck.
My process of installing phunsson's GSI ROM:
Reboot to TWRP,
Do a factory reset (Wipe > "Swipe to Do Factory Reset")
Install Image
Reboot
Took about a minute and a half displaying the bootanimation before it got to the home screen for the first time. If it's loading for more than 5 minutes then that ROM definitely isn't going to work with your device.
Hope this helps someone out there trying to get away from their bloated Samsung One UI.
motomotomotoG said:
After hours of trying to figure this out myself i ended up finding two ROMs that work for me. I was running stock Android 9 with september's security updates when testing these out:
Roms that i tried, that did NOT work:
BlissOS
ArrowOS
Lineage16
The ROMs that DID work for me were:
phunsson's Treble Experimentations
microG ufOfficial
The only 2 bugs that i've seen so far have been a small graphical glitch of quickettings not staying within the bounds of the pulldown and MTP not working at all. These are both present in both ROMs (The microg ROM uses phhusson's rom as the base). Neither of these bother me all that and i'm very happy to be able to move to microg and not have all the google/samsung bloat hogging my tablet and constantly trying to ping their motherships.
Here's a great list of Generic System Image (GSI) ROMs that you can click scroll through and try downloading and flashing to your device to see if you have any luck.
My process of installing phunsson's GSI ROM:
Reboot to TWRP,
Do a factory reset (Wipe > "Swipe to Do Factory Reset")
Install Image
Reboot
Took about a minute and a half displaying the bootanimation before it got to the home screen for the first time. If it's loading for more than 5 minutes then that ROM definitely isn't going to work with your device.
Hope this helps someone out there trying to get away from their bloated Samsung One UI.
Click to expand...
Click to collapse
Did AOSP 10.0 work for you? I haven't been able to get it to boot. Strangely AOSP 9 and LOS 16 are the only ones I've had luck with.
@last1youlove whoa! You got LOS to work? What kind of magician are you? That one never booted for me. The only ROM I got working was ArrowOS and it has a few bugs. I really want to get HavocOS to work but it's a no-go!
droidbot1337 said:
@last1youlove whoa! You got LOS to work? What kind of magician are you? That one never booted for me. The only ROM I got working was ArrowOS and it has a few bugs. I really want to get HavocOS to work but it's a no-go!
Click to expand...
Click to collapse
Strange, How did you go about installing it?
last1youlove said:
Did AOSP 10.0 work for you? I haven't been able to get it to boot. Strangely AOSP 9 and LOS 16 are the only ones I've had luck with.
Click to expand...
Click to collapse
I have not. I just really wanted an AOSP based ROM and i had gotten to the point where i had reflashed the stock firmware 3 times through ODIN because I messed up 1 thing or another. So once i got a functional ROM that worked great I just decided to stick to it. Also I don't think Android 10 has Xposed support yet, and i need that in order to enable Signature Spoofing for MicroG's FakeStore.
I never had problems when restoring TWRP-Backups on my Galaxy Note 3 SM-N9005 while running lineageOS 16 (rooted with Magisk).
During the last weeks I quite often (approx. 7 times!) installed lineageOS 17.1 - which runs without any problems.
It's even possible to backup the current state with TWRP (either twrp-3.4.0-1-hlte or twrp-3.5.0_9-0-hlte)
BUT:
As soon as I RESTORE a TWRP-Backup, my phone doesn' t boot normal again - and ends up in Download Mode. This means that...
... I either have to restore an old lineageOS 16-Backup (I still can start TWRP using POWER, Vol+, Home)
... or have to debrick the phone by using Odin to flash Stock ROM (plus Stock Recovery)
Someone out there with any ideas?
stefmail said:
I never had problems when restoring TWRP-Backups on my Galaxy Note 3 SM-N9005 while running lineageOS 16 (rooted with Magisk).
During the last weeks I quite often (approx. 7 times!) installed lineageOS 17.1 - which runs without any problems.
It's even possible to backup the current state with TWRP (either twrp-3.4.0-1-hlte or twrp-3.5.0_9-0-hlte)
BUT:
As soon as I RESTORE a TWRP-Backup, my phone doesn' t boot normal again - and ends up in Download Mode. This means that...
... I either have to restore an old lineageOS 16-Backup (I still can start TWRP using POWER, Vol+, Home)
... or have to debrick the phone by using Odin to flash Stock ROM (plus Stock Recovery)
Someone out there with any ideas?
Click to expand...
Click to collapse
Maybe this can help
[ROM][I9190/I9192/I9195/L520/R890][Unofficial][10.0.0] LineageOS 17.1 for S4 Mini
Android 10 is here! Took a while, but here's Lineage 17.1 builds, based on Android 10. Everything should work AFAIK, but let me know if something doesn't. If you run into problems installing Gapps, you might need an updated TWRP build. It needed...
forum.xda-developers.com
kurtn said:
Maybe this can help
[ROM][I9190/I9192/I9195/L520/R890][Unofficial][10.0.0] LineageOS 17.1 for S4 Mini
Android 10 is here! Took a while, but here's Lineage 17.1 builds, based on Android 10. Everything should work AFAIK, but let me know if something doesn't. If you run into problems installing Gapps, you might need an updated TWRP build. It needed...
forum.xda-developers.com
Click to expand...
Click to collapse
Do you think the mentioned zip-file would do for my Galaxy Note 3 SM-N9005 too? (I would hate to end up with a hard-bricked phone this time...)?
The fix_rootfs_label.zip/file does the trick for me too!
(strange thing that neither problem nor solution are mentioned sowewhere at the TWRP-website...)
Thank you!
By the way: having moved to lineage 17.1 by clean install Ifound that the name of all my new TWRP-Backups-files are beginning with "1970-01-..."
(not to bad a problem, but still leading to some confusion if one wants to restore the right backup...)
Any ideas about that?
I have been working on this project all day. First i had giga issues unlocking my phone, after 3, i had success (this was more a Xiaomi thing)
I have managed to use XiaoMoTools V2 to get Lineage 19.1 on the phone, but how do i go about getting Gapps onto it?
I have googled, but most say, install it at the same time as the OS, but i cant get that to work? Im a slight loss right now?
I got it working.
See, now I have decided to switch back to the main os, but i dont know how to do it. Help