Related
This rom is compiled from source from cm-13 tree by me. https://github.com/LineageOS/android/tree/cm-13.0
This rom is built for BLU Life One X2 Mini (L0130UU)
This rom allows adb to run as root, but mounting system rw will cause kernel panic and forced shutdown.
I don't use any root other than adb root.
This rom is my daily driver, I have used Lineageos on my phone since my first build, I have no problems with rom, however your mileage may vary.
What works
Camera
Fingerprint
SIM
Data
GPS
Audio
Video Playback
Sensors
Led
known issue
FM radio doesn't work
ideals are welcome.
below are two roms, main difference is toolchain stock toolchain verses UBERTC toolchain, you decide which you prefer.
download rom
https://www.androidfilehost.com/?fid=889964283620760376
Current Rom
Rom is built using GCC: (UBERTC-4.9.x) toolchain
Kernel is built using (UBERTC-5.4.1) toolchain
Older rom version
this version using google stock toolchain
download rom
https://androidfilehost.com/?fid=889964283620759752
device tree
https://github.com/vampirefo/android_device_blu_Life_One_X2_Mini
vendor tree
https://github.com/vampirefo/android_vendor_blu_Life_One_X2_Mini
kernel source
works great so far - what version of gapps do you use?
I installed the arm64 6.0 micro version from http://opengapps.org/ and have been getting crashes now randomly thru-out on menu's in the settings and on the first app I installed "spotify" Have you had any better luck?
cyrusharding said:
works great so far - what version of gapps do you use?
Click to expand...
Click to collapse
open_gapps-arm64-6.0-nano-20171005.zip
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
When I install the ROM with gapps I get errors in the set up process - it says "google services stopped" and then when I try to install software from playstore it gives another error and the apps wont install.
I am using the upside down TWRP 3.1, it seems when I wipe and even format there is still data on the drive - any ideas, do you think its an error because I'm not doing it from adb sideload?
cyrusharding said:
When I install the ROM with gapps I get errors in the set up process - it says "google services stopped" and then when I try to install software from playstore it gives another error and the apps wont install.
I am using the upside down TWRP 3.1, it seems when I wipe and even format there is still data on the drive - any ideas, do you think its an error because I'm not doing it from adb sideload?
Click to expand...
Click to collapse
No ideal, might be wrong TWRP.
Sent from my Life One X2 Mini using Tapatalk
vampirefo said:
No ideal, might be wrong TWRP.
Sent from my Life One X2 Mini using Tapatalk
Click to expand...
Click to collapse
What process do you use for wiping / formatting prior to install?
cyrusharding said:
What process do you use for wiping / formatting prior to install?
Click to expand...
Click to collapse
My device isn't encrypted, I use fastboot to format data, system, cache the first time, then use TWRP from then on.
I use my own version of TWRP, I am not familiar with the version you use, from reading that is an earlier version later version are better.
Sent from my Life One X2 Mini using Tapatalk
vampirefo said:
My device isn't encrypted, I use fastboot to format data, system, cache the first time, then use TWRP from then on.
I use my own version of TWRP, I am not familiar with the version you use, from reading that is an earlier version later version are better.
Sent from my Life One X2 Mini using Tapatalk
Click to expand...
Click to collapse
what adb command do you use for format? thanks for following (updated to the newest recovery that is "right side up"
Edit: I am thinking my root is not working for some reason... Unsure how to fix. I flash magisk from TWRP but it doesnt look like it takes when I run a rootchecker
Looks very promising, I will attempt to flash this tonight. I ran the ported version of lineage OS for a good 6 months before it one day started boot looping (which others have reported as well for that version) . Been running the latest Drax for the mini since then (thank goodness for backups) but am starting to miss a lot of the features from Lineage. Have you had any luck getting the FM radio app to work? If not I would be happy to take a look at it when I flash it later on.
cyrusharding said:
what adb command do you use for format? thanks for following (updated to the newest recovery that is "right side up"
Edit: I am thinking my root is not working for some reason... Unsure how to fix. I flash magisk from TWRP but it doesnt look like it takes when I run a rootchecker
Click to expand...
Click to collapse
I only use SuperSU for root, no ideal about other root method.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
ieatgravity said:
Looks very promising, I will attempt to flash this tonight. I ran the ported version of lineage OS for a good 6 months before it one day started boot looping (which others have reported as well for that version) . Been running the latest Drax for the mini since then (thank goodness for backups) but am starting to miss a lot of the features from Lineage. Have you had any luck getting the FM radio app to work? If not I would be happy to take a look at it when I flash it later on.
Click to expand...
Click to collapse
I haven't looked at FM radio, I would say it doesn't work, On mtk devices source had to be patched for radio to work, I am using unpatched LineageOS source.
The source takes so long to download and sync, I won't patch it just for FM radio.
If you want to work on FM radio, that's up to you, just isn't important to me.
Anyway good luck.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
vampirefo said:
I only use SuperSU for root, no ideal about other root method.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
Click to expand...
Click to collapse
how do you do supersu for root instead of magisk?
cyrusharding said:
how do you do supersu for root instead of magisk?
Click to expand...
Click to collapse
i got it working, but had to install supersu instead of magisk from @ http://www.supersu.com/download
seems like quickcharge isnt working with my 2.0 adapter, otherwise running smoothly.
spotify install crashes and causes a boot loop....
anyway I can help with version testing of updates?
cyrusharding said:
anyway I can help with version testing of updates?
Click to expand...
Click to collapse
I ordered a different phone today, blue tank phone, water is killing my phones, plus the battery life isn't enough to last all day, I have no way to charge phone at work.
Sent from my blu Life_One_X2_Mini LineageOS 13 Tapatalk
Thanks for building this! Just wondering if builds are actively being maintained for Life One X2 Mini.
Also wondering if there are any plans to maintain this ROM? Thanks!!
Is it possible to post a link to the kernel sources you used?
Thanks
srgrusso said:
Is it possible to post a link to the kernel sources you used?
Thanks
Click to expand...
Click to collapse
The source is from Blu ftp server, I don't currently have the source as I removed it from my computer to make room for kernel source for tank, that's my current phone.
https://forum.xda-developers.com/showthread.php?t=3716454
Sent from my Tank Xtreme Pro using Tapatalk
Edit: Update!
See My Guide: [Guide] Pixel 3 XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + September 2018 Security Patch
Doubtful being that the article's date is from May...
jrac86 said:
Doubtful being that the article's date is from May...
Click to expand...
Click to collapse
Edit: OP updated!
Fake News...
It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Sent from my Pixel 2 XL using Tapatalk
bxlegend said:
It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Click to expand...
Click to collapse
Some think the link is "clickbait."
I thought if you installed MM only, you could patch a boot.img with MM. Are you saying that when you install MM it does it without intervention?
Last time I did it you had to get a boot image, transfer it to the device, MM can then patch it, you transfer it back to a PC, flash in fastboot.
Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.
the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too
kachaffeous said:
Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.
Click to expand...
Click to collapse
Edit: OP updated
TheUndertaker21 said:
the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too
Click to expand...
Click to collapse
Edit: OP updated.
I'm curious what the new Titan security chip will do for rooting and custom rooms. Sounds like something that if done right it can be flashed, but it could present a roadblock depending on how it was implemented.
Images are up.
Sent from my taimen using XDA Labs
---------- Post added at 08:01 PM ---------- Previous post was at 07:12 PM ----------
Current boot patch doesn't work. John will have his phone today.
https://twitter.com/topjohnwu/status/1052993970303889418
Sent from my taimen using XDA Labs
I found this out the hard way
Thought I bricked my phone; black screen. Finally after holding down the power button for a second it said boot incompatible or something in the bootloader. There was a new message I hadn't seen before on a Pixel bootloader. (It also says "button combo" in that message area if you use the buttons to get to bootloader.)
Current boot patch doesn't work.
Click to expand...
Click to collapse
No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.
Factory images are up
Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
northmendo said:
No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.
Click to expand...
Click to collapse
I think I can still cancel my order but I''m hopeful it wont come to that.
Archangel said:
Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
Click to expand...
Click to collapse
Root will come. Give it time
Same tried patching boot.img, fails to boot. Reflashing stock boot.img fixes it. Never really looked at the sizes before, but the patched_boot.img is roughly half the size of the stock boot.img
I am starting this thread for us users and experiences while using Android Q. What works, what doesn't. I am not a dev. I am a user. Not here to bash anyone if something doesn't work. @topjohnwu just got root released for this last night.
So one thing I found which I am sure will fixed soon is
SD MAID not working.
Afwall is working.
Systemui tuner working
Button mapper working
I am sure as we go on and they will all work great. But like I said this is just a post what you found thread. If something does work, post it. If something doesn't, post it. Even if someone needs something like an apk. Ask and shall receive. This is a time of helping each other. Not flaming and bashing. Thank you to everyone that has read this and thank you to all the great devs out there and thank you to us users that can exchange information peacefully.
Is it still not possible to write to /system?
w0rdie said:
Is it still not possible to write to /system?
Click to expand...
Click to collapse
Same here. I would think the File Explorer devs would have to update to support Q?
Quickswitch is not working, back button did not work for me with it installed
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
I am using a custom kernel so I didn't try to root the stock boot image. But it seems other people are rooting the stock boot image. I would hope they can help you. If I get around to it, I will try and root the stock boot image to see if it works. Someone should be able to help. Custom kernel roots just fine
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL
Eudeferrer said:
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin
so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kevdog98 said:
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin
Click to expand...
Click to collapse
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked
i42o said:
so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked
Click to expand...
Click to collapse
Custom kernel. Singular is a go. That's what I'm running. I didn't have to flash both slots. That doesn't make sense at all. I am going to get my lazy ass off the veranda and flash the rooted boot image.
Edit: I have Pie in my inactive slot and QBeta 4 in my active slot. If that makes any sense to you guys?
What's the problem? Flashed to active slot only.
Your doing something wrong if you can't root the stock boot image
When I originally rooted Q I did it ota patch inactive slot. Bootlooped. I just went to factory recovery and wiped data. Has worked ever since. I believe mine was looping to modules not being compatible with Q yet. Also if you grab the Q image and pull the boot image. You can patch it that way too. With Q, it is finicky with apps because of isolated storage. Which is weird because zarchiver still sees all files but amaze only sees root directory. Files app I noticed is saying some files I have are folders and not disk images. Zarchiver says it right still. Fastboot -w to manually remove all data too. Sometimes Titan m drive can cause weird things that is why I go to stock recovery and wipe it that way, wipes the Titan m drive too.
Did anybody already try to flash ainur sound mod and can report if it's working? For me the main reason to unlock bootloader again and start root procedure on Q...
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Same problem here. Already posted the issue at the Magisk thread.
alex1301 said:
Same problem here. Already posted the issue at the Magisk thread.
Click to expand...
Click to collapse
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304
Golf c said:
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304
Click to expand...
Click to collapse
Yeah, updated everyhting before getting started.
alex1301 said:
Yeah, updated everyhting before getting started.
Click to expand...
Click to collapse
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.
S8rooted&tooted said:
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.
Click to expand...
Click to collapse
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.
alex1301 said:
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.
Click to expand...
Click to collapse
Click on advanced settings. And make sure when you did patch it, it wasn't checked. It should not be now with 10. With pie it is. Q will not work with it checked. It will double check system to the other partition. And the slot with magisk doesn't match the untouched slot.
Is anyone aware of a LineageOS build for the Pixel 3a?
I am aware that it doesn't exist yet. Does that help?
edufur said:
I am aware that it doesn't exist yet. Does that help?
Click to expand...
Click to collapse
That answers it
Not Official (yet); however...
wijewkyoc4gu8krwf4igg said:
That answers it
Click to expand...
Click to collapse
While an official version of Lineage 17 is not available, the GSI/Treble version should work for the Pixel 3/3a/4 (including XL versions of all three), since all three lines are Treble-ready by design. (I have the GSI Lineage 17 image waiting to test over Bird Weekend.)
Here are my personal builds:
Pixel 3a: https://updater.invisiblek.org/sargo
Pixel 3a XL: https://updater.invisiblek.org/bonito
Notes:
On the bottom of the respective pages is a recovery you can fastboot boot in order to adb sideload the rom. These are auto-built on Sunday mornings in addition to when I decide I want a new build. The built in updater works and will pull and install my new builds seamlessly in android. Gapps are included (no I will not make builds without gapps, don't ask me). I really don't plan to support these, so dont PM/email me or anything about them. You're on your own. I run them on my personal device (bonito) so you can be pretty sure things will work fine. Make sure you've gone to official android 10 before trying to go to this as there are bootloader changes that you definitely need. Data wipe is needed, these are signed with my own private keys and will not be compatible with anyone else's builds.
I'll give these a test
invisiblek said:
Here are my personal builds:
Pixel 3a: https://updater.invisiblek.org/sargo
Pixel 3a XL: https://updater.invisiblek.org/bonito
Notes:
On the bottom of the respective pages is a recovery you can fastboot boot in order to adb sideload the rom. These are auto-built on Sunday mornings in addition to when I decide I want a new build. The built in updater works and will pull and install my new builds seamlessly in android. Gapps are included (no I will not make builds without gapps, don't ask me). I really don't plan to support these, so dont PM/email me or anything about them. You're on your own. I run them on my personal device (bonito) so you can be pretty sure things will work fine. Make sure you've gone to official android 10 before trying to go to this as there are bootloader changes that you definitely need. Data wipe is needed, these are signed with my own private keys and will not be compatible with anyone else's builds.
Click to expand...
Click to collapse
I'll test these, as I went back to the latest stock 10. The issue I had was with the latest stock 9 and TWRP; the combo refused to boot with Magisk 20 - so NOT fun).
invisiblek said:
Here are my personal builds:
Pixel 3a: https://updater.invisiblek.org/sargo
Pixel 3a XL: https://updater.invisiblek.org/bonito
Notes:
On the bottom of the respective pages is a recovery you can fastboot boot in order to adb sideload the rom. These are auto-built on Sunday mornings in addition to when I decide I want a new build. The built in updater works and will pull and install my new builds seamlessly in android. Gapps are included (no I will not make builds without gapps, don't ask me). I really don't plan to support these, so dont PM/email me or anything about them. You're on your own. I run them on my personal device (bonito) so you can be pretty sure things will work fine. Make sure you've gone to official android 10 before trying to go to this as there are bootloader changes that you definitely need. Data wipe is needed, these are signed with my own private keys and will not be compatible with anyone else's builds.
Click to expand...
Click to collapse
Is it correct to assume that there should be official builds once these are merged or is there anything still remaining?
PGHammer said:
I'll test these, as I went back to the latest stock 10. The issue I had was with the latest stock 9 and TWRP; the combo refused to boot with Magisk 20 - so NOT fun).
Click to expand...
Click to collapse
I got it working by extracting the boot.img from the lineageos zip file using payload_dumper and patching with magisk. Using the stock boot.img from google does not work properly(although it did kinda boot for me but without the touchscreen working).
Lightsword1942 said:
Is it correct to assume that there should be official builds once these are merged or is there anything still remaining?
Click to expand...
Click to collapse
No, because I have no intention of being an official maintainer anymore.
Lightsword1942 said:
I got it working by extracting the boot.img from the lineageos zip file using payload_dumper and patching with magisk. Using the stock boot.img from google does not work properly(although it did kinda boot for me but without the touchscreen working).
Click to expand...
Click to collapse
By the way, I upload the boot.img for each build as well. If you're in to doing all this magisk stuff you can always grab the boot.img for the rom by appending ".boot.img" to the end of the rom's download url. Saves you a step at least...
invisiblek said:
No, because I have no intention of being an official maintainer anymore.
Click to expand...
Click to collapse
Is that pretty difficult with the state of the LineageOS project right now for this device? I might be willing to give it a shot, I have a lot of embedded Linux experience(I maintain a number of buildroot packages) although not much on the android side.
Flashing Help
hi - i flashed the latest factory image on my phone.. and having issues trying to get this ROM installed.
I downloaded the Recovery image from your page and via 'Fasboot Mode' and getting the below error message.
I am able to get Magisk installed but getting the same message with phone being rooted. Am I doing something wrong?
C:\Users\xxx\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot boot sargo-recovery-eng.img
Sending 'boot.img' (65536 KB) OKAY [ 1.521s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed
invisiblek said:
Here are my personal builds:
Pixel 3a: https://updater.invisiblek.org/sargo
Pixel 3a XL: https://updater.invisiblek.org/bonito
Notes:
On the bottom of the respective pages is a recovery you can fastboot boot in order to adb sideload the rom. These are auto-built on Sunday mornings in addition to when I decide I want a new build. The built in updater works and will pull and install my new builds seamlessly in android. Gapps are included (no I will not make builds without gapps, don't ask me). I really don't plan to support these, so dont PM/email me or anything about them. You're on your own. I run them on my personal device (bonito) so you can be pretty sure things will work fine. Make sure you've gone to official android 10 before trying to go to this as there are bootloader changes that you definitely need. Data wipe is needed, these are signed with my own private keys and will not be compatible with anyone else's builds.
Click to expand...
Click to collapse
faheem5 said:
hi - i flashed the latest factory image on my phone.. and having issues trying to get this ROM installed.
I downloaded the Recovery image from your page and via 'Fasboot Mode' and getting the below error message.
I am able to get Magisk installed but getting the same message with phone being rooted. Am I doing something wrong?
C:\Users\xxx\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot boot sargo-recovery-eng.img
Sending 'boot.img' (65536 KB) OKAY [ 1.521s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed
Click to expand...
Click to collapse
I'm getting this same error when trying to boot the recovery.
I actually even tried unzipping the ROM zip, unloading payload.bin, and flashing the images manually. It says my device is not unlocked (it is..) when I get to the system IMG in fastbootd mode. So I don't know how people are getting these, or the recovery, to work. Can someone help me out? Thanks
My process to install it based on https://forum.xda-developers.com/es...lineageos-16-0-appears-to-live-t3939150/page7 and user 12paq for showing me the link.
1) Reboot to bootloader
2) sudo fastboot set_active a
3) sudo fastboot flash boot_a bonito-recovery-eng-3.img
4) Wipe data/factory reset
5) sudo adb sideload lineage-17.0-20191201-UNOFFICIAL-bonito.zip (this will only go to 47%, which I read is normal.)
6) reboot
I successfully installed the rom. thanks so much!
but is it possible to root for it??
sumsum0818 said:
I successfully installed the rom. thanks so much!
but is it possible to root for it??
Click to expand...
Click to collapse
Yes root is possible if you patch and flash the boot image
https://github.com/blekreleases/bon...-17.0-20191208-UNOFFICIAL-bonito.zip.boot.img
---------- Post added at 11:43 AM ---------- Previous post was at 11:33 AM ----------
If anyone has Android Auto in their car, wireless preferred but try the wired. I tried to hook mine up and the phone froze. Tried several times but it works on Stock. On the latest 12-08 bonito.
Meowdib said:
Yes root is possible if you patch and flash the boot image
---------- Post added at 11:43 AM ---------- Previous post was at 11:33 AM ----------
If anyone has Android Auto in their car, wireless preferred but try the wired. I tried to hook mine up and the phone froze. Tried several times but it works on Stock. On the latest 12-08 bonito.
Click to expand...
Click to collapse
thanks for the great help:good:
WHen I flash boot recovery the recovery mode disappears and therefor no option to sideload rom???
---------- Post added at 10:53 PM ---------- Previous post was at 10:52 PM ----------
sumsum0818 said:
I successfully installed the rom. thanks so much!
but is it possible to root for it??
Click to expand...
Click to collapse
How did u get it to work>> still failing for me. If i flash recovery, then the recovery mode is not available anymore..no adb sideload is possible?
---------- Post added at 10:54 PM ---------- Previous post was at 10:53 PM ----------
sumsum0818 said:
I successfully installed the rom. thanks so much!
but is it possible to root for it??
Click to expand...
Click to collapse
How did u get it to work>> still failing for me. If i flash recovery, then the recovery mode is not available anymore..no adb sideload is possible?
oranget said:
WHen I flash boot recovery the recovery mode disappears and therefor no option to sideload rom???
---------- Post added at 10:53 PM ---------- Previous post was at 10:52 PM ----------
How did u get it to work>> still failing for me. If i flash recovery, then the recovery mode is not available anymore..no adb sideload is possible?
---------- Post added at 10:54 PM ---------- Previous post was at 10:53 PM ----------
How did u get it to work>> still failing for me. If i flash recovery, then the recovery mode is not available anymore..no adb sideload is possible?
Click to expand...
Click to collapse
i just flash boot the recovery image first, then erase user data, you can reboot to recovery mode
i thought you should try to boot from the stock november patch first as i failed when i boot from the december patch
Simple install/update instructions
These are the steps I used, which worked flawlessly (I'm on Sargo). Hopefully this simplifies the process for anyone who wants to use this or is having trouble.
Prerequisites:
ADB, Fastboot, and Drivers (https://forum.xda-developers.com/showthread.php?t=2588979)
LineageOS Rom and Recovery (https://forum.xda-developers.com/showpost.php?p=81048663&postcount=5)
Unlock phone:
Go to Settings > About Phone, then tap "Build Number" until it says you are a developer.
Next go to Settings > System > Developer Options and enable the option "OEM Unlocking".
Connect phone to pc, and boot into fastboot. (With the phone off hold Volume Down and Power buttons.)
From the windows console enter "fastboot oem unlock" and your phone will become unlocked.
Install Rom:
Connect phone to pc, and boot into fastboot. (With the phone off hold Volume Down and Power buttons.)
From the windows console enter "fastboot boot <recovery_filename>.img" and you will enter recovery.
From recovery choose "Apply Update from ADB" and in the windows console enter "adb sideload <rom_filename>.zip"
When it has completed choose "Reboot System Now" and the install will be complete.
Special thanks to invisiblek for making these builds available to us!
I notice the full ROM has separate recovery image.
Is there any way to develop TWRP from the recovery?
I never have knowledge to make one unfortunately
mingkee said:
I notice the full ROM has separate recovery image.
Is there any way to develop TWRP from the recovery?
I never have knowledge to make one unfortunately
Click to expand...
Click to collapse
Because of dynamic partitions, TWRP is useless actually. You can boot it but that's all, you can't flash anything.
Running the same issue on Pixel 4XL. Any device that boots on 10 or higher at the moment. No update since October 2019...
vache said:
Because of dynamic partitions, TWRP is useless actually. You can boot it but that's all, you can't flash anything.
Click to expand...
Click to collapse
Any further news on this?
Would love to make a backup before attempting to root with Magisk
jharkness316 said:
Any further news on this?
Would love to make a backup before attempting to root with Magisk
Click to expand...
Click to collapse
There's an easy way to revert
Download a full ROM and extract boot.img and patch one and keep another ad backup
mingkee said:
There's an easy way to revert
Download a full ROM and extract boot.img and patch one and keep another ad backup
Click to expand...
Click to collapse
How can I extract the boot.img and patch it before I flash it to the phone?
Finally how can I flash the boot.img to the phone?
Sorry to sound like an idiot. I have rooted a phone before ( Moto X Pure )
and it worked well.
This phone tho is newer and uncharted territory for me. There were programs and such for the X Pure
when i did it. This seems to be a command (adb) process only.
Finally, is there a different logo.img I can use ( I assume this is the boot animation file)
jharkness316 said:
How can I extract the boot.img and patch it before I flash it to the phone?
Finally how can I flash the boot.img to the phone?
Sorry to sound like an idiot. I have rooted a phone before ( Moto X Pure )
and it worked well.
This phone tho is newer and uncharted territory for me. There were programs and such for the X Pure
when i did it. This seems to be a command (adb) process only.
Finally, is there a different logo.img I can use ( I assume this is the boot animation file)
Click to expand...
Click to collapse
ROM is zip format
You need to get the lastest ADB for windows to have fastbootd support
adb reboot fastboot
fastboot reboot fastboot
Fastbootd is like recovery and flashing command is same
Found the TWRP has support for One Action, Vision, and Zoom
Are these mainly the same phone with camera and battery changes as well as some software changes?
Can one of these not be used for Hyper?
If things go awry, can a factory flash from stock rom fix issues?
---------- Post added at 08:01 AM ---------- Previous post was at 08:01 AM ----------
Found the TWRP has support for One Action, Vision, and Zoom
Are these mainly the same phone with camera and battery changes as well as some software changes?
Can one of these not be used for Hyper?
If things go awry, can a factory flash from stock rom fix issues?
Vache, the only dev we have, made a port today. It's in the roms section...