Database Info

HELP - Multirom - Ubuntu Touch -Stable 13 Fail !!!!

Hi,
I was trying to install Ubuntu Touch (Stable 11 & 13) alongside my Resurrection Remix (M-6.0.1) [May 24 Release] internal ROM.
Followed all the steps mentioned in Multirom v33b, installed latest TWRP, Kernel (6.0.x) & recovery.
The UT build (Stable 11 & 13 - tried separately) downloads and installs successfully. Yet on selecting from Multirom Grub/bootloader it reboots and gets stuck at Oneplus boot screen, never boots into Ubuntu Touch.
Anyone tried it, faced such issues and fixed....
Your help will be much appreciated.
Cheers

bump

mandrax.prime said:
Hi,
I was trying to install Ubuntu Touch (Stable 11 & 13) alongside my Resurrection Remix (M-6.0.1) [May 24 Release] internal ROM.
Followed all the steps mentioned in Multirom v33b, installed latest TWRP, Kernel (6.0.x) & recovery.
The UT build (Stable 11 & 13 - tried separately) downloads and installs successfully. Yet on selecting from Multirom Grub/bootloader it reboots and gets stuck at Oneplus boot screen, never boots into Ubuntu Touch.
Anyone tried it, faced such issues and fixed....
Your help will be much appreciated.
Cheers
Click to expand...
Click to collapse
There is a problem with the latest recovery. Flash this recovery 'TWRP_multirom_bacon_20160221-01.img' from multirom recovery folder and it'll get installed without any errors

TRIED!!
sandesh780 said:
There is a problem with the latest recovery. Flash this recovery 'TWRP_multirom_bacon_20160221-01.img' from multirom recovery folder and it'll get installed without any errors
Click to expand...
Click to collapse
TRIED MANY OTHER BUILDS OF MULTIROM TWRP!!
NO USE..still the same issue..
but on using too old builds will not allow us to install ubuntu...
it says "update recovery and multirom to install ubuntu!!"

I can confirm using TWRP_multirom_bacon_20160221-01.img solves the issue. Thank you very much @sandesh780

XT926 from 4.1.1 to LineageOS 14.1

I do not understand how to do what I want to do. I want to install the custom ROM LineageOS 14.1. Here's where I am stuck.
In trying to install the xt926/spyder 14.1 nightly build from 6.30.17 using ROM Manager, I get the following error message E3004: This package is for device: cdma_spyder; this device is xt926. It seems the error message states I am trying to install it on the wrong phone, so the install is aborted. But I do have an xt926 that I'm trying to install to. I posted on the Lineage site. I was told "don't use rom manager or clockworkmod they haven't been supported in years; also make sure you're using the latest TWRP for the correct device. The "this is device xxxx" is based on what the recovery says it is." I do not know which old TWRP I can use. In ROM Manager it states my current recovery is ClockworkMod 6.0.4.4. What's wrong with my recovery? The installer says I have an xt926, so why did it really fail? I'm wondering if I need the KKBL (KitKat bootloader), and the lack of that is why it really failed. If so, I do not understand from reading the posts how to get the KKBL. I read where I felt some were stating there was a small window to be able to get it and still root. I read about just flashing the BL, but then some said to never do that. Can someone please help me? TIA
Current -
OS: android 4.1.1 / 9.1.41xt926.verizon.en.us
Bootloader unlocked
Rooted
Baseband version: vanquish_bp_100700.210.64.05p
Kernel version: 3.0.31-g59a8475
System modifications: android 4.1.1 / 9.1.41xt926.verizon.en.us
Goal -
LineageOS 14.1 (Nougat)
Bootloader unlocked
Rooted

retalger said:
I do not understand how to do what I want to do. I want to install the custom ROM LineageOS 14.1. Here's where I am stuck.
In trying to install the xt926/spyder 14.1 nightly build from 6.30.17 using ROM Manager, I get the following error message E3004: This package is for device: cdma_spyder; this device is xt926. It seems the error message states I am trying to install it on the wrong phone, so the install is aborted. But I do have an xt926 that I'm trying to install to. I posted on the Lineage site. I was told "don't use rom manager or clockworkmod they haven't been supported in years; also make sure you're using the latest TWRP for the correct device. The "this is device xxxx" is based on what the recovery says it is." I do not know which old TWRP I can use. In ROM Manager it states my current recovery is ClockworkMod 6.0.4.4. What's wrong with my recovery? The installer says I have an xt926, so why did it really fail? I'm wondering if I need the KKBL (KitKat bootloader), and the lack of that is why it really failed. If so, I do not understand from reading the posts how to get the KKBL. I read where I felt some were stating there was a small window to be able to get it and still root. I read about just flashing the BL, but then some said to never do that. Can someone please help me? TIA
Current -
OS: android 4.1.1 / 9.1.41xt926.verizon.en.us
Bootloader unlocked
Rooted
Baseband version: vanquish_bp_100700.210.64.05p
Kernel version: 3.0.31-g59a8475
System modifications: android 4.1.1 / 9.1.41xt926.verizon.en.us
Goal -
LineageOS 14.1 (Nougat)
Bootloader unlocked
Rooted
Click to expand...
Click to collapse
The spyer is the old razor xt912 not the razor hd xt926 the xt926 is the vanquish. your flashing xt912 firmware on an xt926 device.

SOLVED
OGdroidster said:
The spyer is the old razor xt912 not the razor hd xt926 the xt926 is the vanquish. your flashing xt912 firmware on an xt926 device.
Click to expand...
Click to collapse
Oh! Thank you so much for the help.

retalger said:
Oh! Thank you so much for the help.
Click to expand...
Click to collapse
Sure your welcome

Has anyone managed to get Lineage OS 14.1 working on the xt926? I was able to flash it through TWRP along with opengapps 7.1 and it boots but either System UI or Setup is constantly crashing meaning i'm unable to proceed past setup.

drkdeath5000 said:
Has anyone managed to get Lineage OS 14.1 working on the xt926? I was able to flash it through TWRP along with opengapps 7.1 and it boots but either System UI or Setup is constantly crashing meaning i'm unable to proceed past setup.
Click to expand...
Click to collapse
To get 14.1 working you need to use RSDLite to flash back to 4.1.2 Jelly Bean (https://www.androidfilehost.com/?fid=24269982087011677), then install TWRP for the Photon Q (https://twrp.me/devices/motorolaphotonq.html) then use the official nightly builds for the Photon Q posted on the Lineage website. Open Gapps ARM 7.1 nano works best for me.
That said, you won't be able to use your main mic for phone calls, only speakerphone. I have yet to find a rom/recovery/firmware combination that will allow fully functional phone calls with anything above 4.4. This isn't a problem for me as this is a toy without a sim card in it, what some people call a toilet phone. It sits in my bathroom vanity and comes out when I forget one of my main devices. Other than that I play with it once every few months to see how far the development community has pushed it.

thunder2132 said:
To get 14.1 working you need to use RSDLite to flash back to 4.1.2 Jelly Bean (https://www.androidfilehost.com/?fid=24269982087011677), then install TWRP for the Photon Q (https://twrp.me/devices/motorolaphotonq.html) then use the official nightly builds for the Photon Q posted on the Lineage website. Open Gapps ARM 7.1 nano works best for me.
That said, you won't be able to use your main mic for phone calls, only speakerphone. I have yet to find a rom/recovery/firmware combination that will allow fully functional phone calls with anything above 4.4. This isn't a problem for me as this is a toy without a sim card in it, what some people call a toilet phone. It sits in my bathroom vanity and comes out when I forget one of my main devices. Other than that I play with it once every few months to see how far the development community has pushed it.
Click to expand...
Click to collapse
I tried this last weekend but was getting constant force closes from System UI so i gave up and went back to the MokeeOS build.

Thanks @thunder2132. After fumbling about, I finally got this working:
- In TWRP, wiped cache, data & system
- Reflashed 4.1.2 factory image
- I used fastboot manually and followed the recipe in the XML file. The gpt and tz images can't be downgraded, and I did not wipe userdata [not wiping this was probably a mistake])
- Rebooted to system with sim card
- Powered off
- Booted into bootloader/fastboot and flashed TWRP
- `fastboot reboot-bootloader` (in an attempt to keep the phone from trying to boot into system again)
- Booted into TWRP, flashed LOS & OpenGApps Nano
- Tried to reboot into system and failed
- Booted into TWRP, "Format Data"
- Rebooted into system, waited, profited
Now I'd like to figure out why I can only use ADB over the network. >:| It doesn't show up at all over USB, neither in LOS nor TWRP.
PS: Later I wiped system, reflashed LOS, and flashed OpenGApps *Pico*. No issues yet.

polyzen said:
Thanks @thunder2132. After fumbling about, I finally got this working:
- In TWRP, wiped cache, data & system
- Reflashed 4.1.2 factory image
- I used fastboot manually and followed the recipe in the XML file. The gpt and tz images can't be downgraded, and I did not wipe userdata [not wiping this was probably a mistake])
- Rebooted to system with sim card
- Powered off
- Booted into bootloader/fastboot and flashed TWRP
- `fastboot reboot-bootloader` (in an attempt to keep the phone from trying to boot into system again)
- Booted into TWRP, flashed LOS & OpenGApps Nano
- Tried to reboot into system and failed
- Booted into TWRP, "Format Data"
- Rebooted into system, waited, profited
Now I'd like to figure out why I can only use ADB over the network. >:| It doesn't show up at all over USB, neither in LOS nor TWRP.
PS: Later I wiped system, reflashed LOS, and flashed OpenGApps *Pico*. No issues yet.
Click to expand...
Click to collapse
Nice! I'm glad you got it working.

what do you mean with reflashed factory image 4.1.2?

I was on Resurrection Remix for the Razr M and now flashed LOS from this thread because of connectivity problems and I hoped it is a problem of RR. But unfortunately I still just have Edge connection, no 3G or 4G. Does anyone know how to fix that? There were no problems under 4.1.
Edit: I went back to 4.1.2 and wanted to start from zero but now on 4.1.2 there's only Edge connection as well :/

[FAQ][Discussion]LineageOS 15.1 by abhishek987 [ask your questions HERE]

Because LineageOS 15.1 by @abhishek987 thread is bloated by questions anwsered before or not dev related - ask and discuss here - to debloat main thread.
How to flash Lineage 15.1:
!NEW AND THE ONLY RECOMMENDED METHOD!​
You must be on Oreo. Before flashing delete all your saved fingerprints and screen locks.
1. Reboot to bootloader (Bootloader must be unlocked)
2. fastboot boot recovery-xx.img (in ADB)
-> Grab official recovery from here: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
3. Wipe System/Data/Cache/Dalvik
4. Flash Lineage & TWRP Installer zip
-> Grab TWRP installer from the link above
5. Reboot to recovery using TWRP Recovery (In TWRP go to Reboot -> recovery)
6. Flash Gapps/MicroG (opengapps.org -> platform ARM64 -> Android 8.1 + Variant [IMO pico is your best pick])
7. Flash Magisk [latest] if you want ROOT (I bet you want!)
-> Grab Magisk from here: http://tiny.cc/latestmagisk
8. Reboot to System
How to update from previous build:
If you don't have permament TWRP, just follow the method above.
If you have permament TWRP:
Delete all your previous fingerprints (just for safety)
Boot to TWRP
Wipe Data/Cache/Dalvik (wiping is optional - but clean flash is always encouraged)
Flash Lineage ROM zip file
Flash Magisk
Flash Gapps/MicroG
Reboot
KNOWN BUGS:​* No bugs right now! Enjoy bug-free rom!
If you have signal stability issues, try this:
Dial *#*#4636#*#*
Go to Phone information
Set Preferred Network Type from Unknown to LTE or WCDMA only
WHAT IS WORKING:​* Everything else
LINEAGE BUILD CHANGELOG:
Code:
[FONT="Arial"]
[B]Most recent build (24.03.2018):[/B]
Fixed portrait mode
Enabled hal3 camera by default
Added doze
Lineage upstream
[B](22.03.2018): [/B]
Fixed double tap to wake (should only work for focaltech panel)
Rebased kernel to latest oreo source drop
Enabled cpusets
Lineage upstreams
[B](13.03.2018): [/B]
Fixed verity issue (builds now can be flashed without magisk)
Fixed Live Display
Fixed Substratum
Fixed ril issues
Lineage Upstream changes
[B](08.03.2018): [/B]
Fixed notification light (should work in call cases now)
Fixed slow charging
Fixed deep sleep issue
Added navbar toggle
Fixed goodix fingerprint issue (should work for all and all 5 fingerprint should be registered now)
Lineage Upstream changes
[B](06.03.2018): [/B]
Fixed led light
Added fingerprint gestures
Fixed Bluetooth name
Fixed battery capacity
Lineage upstream changes[/FONT]
Have fun with LOS!

Q&A
What does NIGHTLY mean?
Nightlies are automatical builds (every few days), so it mean you will have frequent updates, recent Lineage changes will be present in a rom. Also fixes and new stuff will come faster!
How I can go back to stock?
Grab Mi A1 tool from here: https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857.
Install it in your PC, enable USB Debugging on your phone, plug phone to PC
Click Flash Stock ROM button
Click Download ROM and wait
Click FlashAll. Your phone will reboot to fastboot and it will start to flash stock
[You will loose all your data, so backup is encouraged]
Do I need to downgrade to Nougat before flashing?
Not anymore It's advised to flash from Oreo
After update my FP don't work, wat to do?!
Make a clean flash using method from OP. If clean flash won't help, try: https://forum.xda-developers.com/mi-a1/development/xiaomi-mi-a1-tissot-firmware-flashable-t3759886
Is Dolby working on Lineage 15.1? How to install it?
Just download Magisk module and enjoy!
My mobile signal is unstable. Is there a way to fix it?
Yes, see a workaround from OP
Why Selinux is permissive, not enforcing?
In unofficial builds Selinux is permissive. If the build goes official, it will have Selinux set to enforcing. Don't worry, just wait for official version!
Is this rom stable enough to be a daily driver?
Depends what you need. Check buglist - if these bugs don't bother you - it can surely be a daily driver
When new build will be avaible?
Don't ask for ETAs. Developers are working hard (in their free time!) to fix a bugs - we just need to wait patiently.

Some users are experiencing wifi issues (myself included). How can i fetch the log?
Steps to reproduce: Turn off bluetooth. wait a moment... wifi will start dropping connection a lot. To fix, just turn on BT again.

Headphones do not work.

Headphones are working!
By the way. I found a bug. The equalizer don't work correct. Everytime when you skip a song you must tap the bass regulator again in the equalizer app. When you don't do it, it plays without bass.

konradit said:
Headphones do not work.
Click to expand...
Click to collapse
Everything fine here, try to reflash

Installed and used for 24 hrs with no apparent problems. No fingerprint bug.
All the other bugs reported in OP exists.
Returned to Stock since I found it a bit smoother.
I will wait for a more stable official build
Good work so far

still

rasputine said:
still
Click to expand...
Click to collapse
Are you using the deadman twrp? I got that using other TWRP versions.

goofball2k said:
Are you using the deadman twrp? I got that using other TWRP versions.
Click to expand...
Click to collapse
Yes I'm using deadman's twrp

rasputine said:
Yes I'm using deadman's twrp
Click to expand...
Click to collapse
Did you reboot after doing the data wipe?

Can I install LOS 15.1 without flashing magisk? I have tried this and had bootloop before any lineageos bootlogo

radogost said:
Because LineageOS 15.1 by @abhishek987 thread is bloated by questions anwsered before or not dev related - ask and discuss here - to debloat main thread.
How to flash Lineage 15.1: ​There's a few working methods. First, most popular one:
....
Third, last one:
Boot to the recovery (same recovery as method above)
Wipe system and cache ( data is optional if your are on Oreo)
Check which partition you are on (A or on partiton B)
Flash the rom on one of the partitions
Flash the twrp installer zip
link: http://www.mediafire.com/file/338o7cl72z52rzz/twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester.zip
Reboot back to the recovery
Switch to the second partition
Flash GAPPS/MicroG and Magisk
Reboot
Click to expand...
Click to collapse
Sorry to pick this up again but the last method implies that TWRP will be installed permanently as default recovery, right? I was successfull only with the first method however I always end up in LOS recovery when try to enter recovery with Vol-up+Power after everything is installed.
I'm sure we all agree that this whole recovery mess needs to be sorted out quickly. Even experienced users are hitting snags and flood the board with questions .

goofball2k said:
Did you reboot after doing the data wipe?
Click to expand...
Click to collapse
Yes sir

i face the same issue with any methond i am using.
in some cases i am unable to install all the zips and in another case i am unable to install only magisk(error 1)
i followed exactly the steps.
any suggestions?

I'm not sure why the issues. I followed the steps in the OP, except I didn't flash TWRP, I just boot to it temporarily.
I did the following:
Flashed 7.11.18 ROM using MiFlash.
Booted into the ROM, set it up minimally.
Rebooted to fastboot, unlocked bootloader
booted temporarily to deadman TWRP, wiped system/cache/dalvik/data (just to be sure it is completely clean)
rebooted and then booted back into deadman TWRP
flashed LOS.
rebooted and then booted back into deadman TWRP
Flashed gapps and magisk.
rebooted to OS.

hey guys! If you are in STOCK OREO you need to downgrade to NOUGAT FIRMWARE version 7.11.18 because DEADMAN'S TWRP will NOT WORK PROPERLY in STOCK OREO! DEADMAN'S TWRP is made ONLY to WORK ON NOUGAT rom that's why you get those errors!

Flashed from 8.1.10 without any problems...

ZSL mode of gcam doesn't work..
Can somebody tell me how to disable hardware navigation keys?
---------- Post added at 01:47 PM ---------- Previous post was at 01:47 PM ----------
ZSL mode of gcam doesn't work..
Can somebody tell me how to disable hardware navigation keys?

t0per666 said:
hey guys! If you are in STOCK OREO you need to downgrade to NOUGAT FIRMWARE version 7.11.18 because DEADMAN'S TWRP will NOT WORK PROPERLY in STOCK OREO! DEADMAN'S TWRP is made ONLY to WORK ON NOUGAT rom that's why you get those errors!
Click to expand...
Click to collapse
Tornado95 said:
Flashed from 8.1.10 without any problems...
Click to expand...
Click to collapse
Hmm so which one is telling the truth? ??
Sent from my Xiaomi Mi A1 using XDA Labs

Youtube keeps stopping on RROS 6.1.0 kirin- official

I am running the beta 2 of RROS downloaded from the openkirin.net website. Every thing works fine and is smooth. However when I tried to go into settings in the YouTube app, the app stopped working. So I rebooted and tried again. Same result. Until now, this has been only happening in YouTube and in no other app (for now). Is there any fix for this or is this a bug? Thanks for your help.
Also a few other questions. How can I root this room like what TWRP and Magisk to use? If I want to change ROMs to LineageOS what should I do? What's the best custom kernel and how to install.
Edit. If there is an updated version of this build available how can I get that. Do I have to flash through TWRP? Because in the OTA update tab in customizations, it says can't check update. So far loving this ROM.
Also what's the main difference between LineageOS and RROS? Which one is better?

Reboot Twrp and try to clean cach or dalvikcach

Twro isn't compatible with open Kirin builds

[solved] Reboot to twrp when installing latest lineage16

Hello
Strange think for me, maybe not for you
I switch from carbon 8 and came back to lineage 16.
I'm not able to achieved installation with latest lineage 16, lineage microG or lineage17. Flashing the new rom works well, but after lineage home screen, the phone reboot to recovery.
With an lineage16 old version from 03/2019,install is ok and phone boot well.
I've suspected an old twrp version, but I'm on 3.3.1.0.
Any idea ?
thank you

it's the same with an old twrp version 3.2.

Ok, solved. You shouldn't install twrp as an app before rebooting to new os version.