{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lineage OSAbout Lineage OS:
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
Warning:
This ROM will not work on devices that have not installed the O bootloader and appropriate modem package below. Any failure in this process could lead to an unrecoverable bricked device.
Instructions:
Attention! The bootloader needs to be unlocked!
1. Install the Universal O bootloader and your model specific modem. Download
2. Update your version of TWRP. Download
3. Perform a backup of your current ROM. (optional)
4. Wipe system,data and cache (optional) [Needed if coming from another rom!; always good to avoid bugs]
5. Install the ROM. Download or Download Unofficial builds
6. Install GApps. (optional) [Recommended -> Open GApps (arm64) (8.1)]
7. Reboot.
What is CAF?
Code Aurora, a Linux Foundation Collaborative Project, hosts tested open source software code needed to provide upstream enablement for innovative, performance optimized, network connectivity and related ecosystems to support system on a chip (SoC) products. It also serves as a staging area for open source code that is submitted to various upstream projects such as the Linux kernel and Android. CAF also mirrors key upstream projects for use by the community.
Sources, Changes, & Wiki:
Source | Changes | Axon 7 Wiki | Lineage OS
Credits:
@Unjustified Dev
@DrakenFX
XDA:DevDB Information
[OFFICIAL] LineageOS 15.1 for ZTE Axon 7, ROM for the ZTE Axon 7
Contributors
OrdenKrieger, Unjustified Dev, DrakenFX, tdm
Source Code: https://github.com/LineageOS/android_kernel_zte_msm8996/tree/lineage-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: O bootloader + region modem
Based On: LineageOS
Version Information
Status: Nightly
Created 2018-06-05
Last Updated 2018-10-14
Reserved
If anyone gets the red warning at the start, this over TWRP or with adb debugging enabled, should fix it. This is also only needs to be done once.
Code:
[COLOR="Red"]THIS MAY WIPE YOUR DATA![/COLOR]
adb reboot "dm-verity enforcing"
* Alternative you can short/once press the power button to continue the boot process.
Holy moly, this comes out of nowhere, is this fantasy
omg. ♥
This supports dual Sim?
---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------
OrdenKrieger said:
If anyone gets the red warning at the start, this over TWRP or with adb debugging enabled, should fix it. This is also only needs to be done once.
Code:
[COLOR="Red"]WARNING THIS MAY WIPE YOUR DATA![/COLOR]
adb reboot "dm-verity enforcing"
Click to expand...
Click to collapse
Do not get how you do this over TWRP?
Raffikie said:
This supports dual Sim?
---------- Post added at 10:07 PM ---------- Previous post was at 10:06 PM ----------
Do not get how you do this over TWRP?
Click to expand...
Click to collapse
Open an adb terminal on your pc, connect an usb cable and paste
Code:
adb reboot "dm-verity enforcing"
Dual sim should work but I couldn't test since I only use 1 sim card.
Maybe in Terminal in TWRP
Hille2001 said:
Maybe in Terminal in TWRP
Click to expand...
Click to collapse
That would be just
Code:
reboot "dm-verity enforcing"
Don't know why but my phone just bricked after flashing this. I flashed it the same way like I did with all Oreo roms. My steps:
_Wipe data/system/cache/dalvik.
_Flash the Universal bootloader and A2017G modem from the link in OP.
_Flash Lineage OS 15.1
_Flash micro Gapps
_Wipe dalvik/cache
_Reboot
My phone stuck at the screen saying that my device is corrupted, I cannot boot back into TWRP also. Any idea ?
*Edit: I got it back to TWRP, will try again
ortolan said:
Don't know why but my phone just bricked after flashing this. I flashed it the same way like I did with all Oreo roms. My steps:
_Wipe data/system/cache/dalvik.
_Flash the Universal bootloader and A2017G modem from the link in OP.
_Flash Lineage OS 15.1
_Flash micro Gapps
_Wipe dalvik/cache
_Reboot
My phone stuck at the screen saying that my device is corrupted, I cannot boot back into TWRP also. Any idea ?
*Edit: I got it back to TWRP, will try again
Click to expand...
Click to collapse
This over pc adb terminal
Code:
adb reboot "dm-verity enforcing"
or this inside of TWRP
Code:
reboot "dm-verity enforcing"
OrdenKrieger said:
If anyone gets the red warning at the start, this over TWRP or with adb debugging enabled, should fix it. This is also only needs to be done once.
Code:
[COLOR="Red"]WARNING THIS MAY WIPE YOUR DATA![/COLOR]
adb reboot "dm-verity enforcing"
Click to expand...
Click to collapse
Is there an instance where this has to be applied again? If you reinstall the bootloader, for example?
Cablespider said:
Is there an instance where this has to be applied again? If you reinstall the bootloader, for example?
Click to expand...
Click to collapse
Probably or if you install stock again, I think that will be enabled again, but any other ROM shouldn't touch that state.
The "in call audio/speakerphone" bug has been fixed by the way, if anyone wonders.
I have flashed it successfully and am running it now. I will add all my apps and what not and see how it goes.
Really excited for your experiences with this ROM and if you would prefer it over the ZTE Oreo Beta by Nfound in case some.of you are running that rn. ?
Can someone tell me if HDR+ on the modded Google cam works or not? Also the AKM DAC?
Hi I have a2017 Chinese model running v3.0b11, MiFavor 5.2 should I still install the Universal bootloader and modem to be on the safe side
jungle35 said:
Can someone tell me if HDR+ on the modded Google cam works or not? Also the AKM DAC?
Click to expand...
Click to collapse
HDR+ works and the DAC always worked in headphone use case. Even on 14.1.
FuzzyDunlop9 said:
Hi I have a2017 Chinese model running v3.0b11, MiFavor 5.2 should I still install the Universal bootloader and modem to be on the safe side
Click to expand...
Click to collapse
Yes.
So I was having FC issues with just the Google App. I downloaded Gapps again and reinstalled Gapps. Now I get stuck at the LOS boot animation. I am trying to get back into TWRP but I am not sure of the key combo since the whole "press the power key in 30secs" thing at the bootloader screen. Thank you.
-EDIT-
Got back into TWRP. I hit the volume keys after the power button message. Then I picked recovery from the bootloader menu. Then I have to hit the power button on the next go around and it goes into TWRP.
Related
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Main Highlights
✪ MTP support
✪ Can flash stock os Images
✪ Backup/restore works with any os
✪ Restore your old twrp backup
✪ Optimized and faster
✪ Build On A29 Pre Built Kernel By Realme
✪ Full compatible with color os
ScreenShots
Download Link:
https://mega.nz/#!5gYnjQSB!YhC_ZTHuopwwP50LxTvJ1VOq4zYSfG0LAudWr6gatUA
Code:
Bugs
:GSI Flashing Has Some Issues
:If You Finds Any Other Bug Then Report Me
Credits;
AnuragRai(Developer)
Hamza(Tester)
RK(Tester)
Jatin(Tester)
MKS(RM2p Dev,Always Supported Me)
And Whole Realme Tester Team
XDA:DevDB Information
TWRP[UNOFFICAL]-BETA-BUILD-[12-03-2019], Tool/Utility for the Oppo Realme 1
Contributors
anurag rai, hamza
Version Information
Status: Beta
Current Beta Version: 01
Beta Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12
Flashing Guide
Code:
[CENTER]
:adb reboot bootloader
:fastboot flash recovery recoveryname.img
:reboot phone manually ,not from fastboot
:After phone boots up,power off it
:Press Power Button+Volume UP &Down For Approx 20 seconds
:After You Are Inside Of Twrp,do this
:Wipe-Format Data-Yes And reboot manually by power off the device
:And Press Power Button+Volume UP & Down
:Flash Magisk And Reboot [/CENTER]
Caution
Code:
:Never Reboot directly to recovery by adb or fastboot commands as it will cause soft brick,
:always manually reboot
Reserved
Thankyou bro..
Finally we are getting working twrp recovery for rm 1:highfive: keep up the good work mate
anabhi said:
Finally we are getting working twrp recovery for rm 1:highfive: keep up the good work mate
Click to expand...
Click to collapse
Bro can you help me with fixing reboot to recovery issue
anurag rai said:
Flashing Guide
Code:
[CENTER]
:Wipe-Format Data-Yes And reboot manually by power off the device
:And Press Power Button+Volume UP & Down
:Flash Magisk And Reboot [/CENTER]
Caution
Code:
:Never Reboot directly to recovery by adb or fastboot commands as it will cause soft brick,
:always manually reboot
Click to expand...
Click to collapse
After wiping data and turning off. My phone wont boot. I doesnt even show the logo. Please help.
It's Working ! Thanks Alot Mate.:victory:
awesome work bro.. thnks a lot u r too fast..
Why wiping data ? Also if we wipe data then won't it take time to setup the device after that only we could reboot. And I just need to put some some apps into system, I dont want to flash magisk. Can I just boot into recovery once using fastboot boot twrp.img command /
Awesome man!??
svsexodia said:
Why wiping data ? Also if we wipe data then won't it take time to setup the device after that only we could reboot. And I just need to put some some apps into system, I dont want to flash magisk. Can I just boot into recovery once using fastboot boot twrp.img command /
Click to expand...
Click to collapse
Yes you can
manavkush said:
Flashing Guide
Caution
After wiping data and turning off. My phone wont boot. I doesnt even show the logo. Please help.
Click to expand...
Click to collapse
Charge it bro
Realme 1 - Treble Rom
'TREBLE', let's talk about it.
Realme 1 supports treble, we have unlocked bootloader, a working TWRP, and several Treble Roms available, so why haven't anyone tried flashing a Treble Rom yet on Realme 1? Those are the only things we need to flash a Treble Rom on this device right? Am I missing something?
I don't have a backup phone nor do we have official firmware for Realme 1 to recover from soft brick, so I am not willing to risk my device yet. If someone else could do it instead I would appreciate it a lot.
P.S. Someone should start a pinned thread for 'Realme 1 - Treble Roms'
johndoe5 said:
'TREBLE', let's talk about it.
Realme 1 supports treble, we have unlocked bootloader, a working TWRP, and several Treble Roms available, so why haven't anyone tried flashing a Treble Rom yet on Realme 1? Those are the only things we need to flash a Treble Rom on this device right? Am I missing something?
I don't have a backup phone nor do we have official firmware for Realme 1 to recover from soft brick, so I am not willing to risk my device yet. If someone else could do it instead I would appreciate it a lot.
P.S. Someone should start a pinned thread for 'Realme 1 - Treble Roms'
Click to expand...
Click to collapse
I've Flashed Phh's GSI Treble Roms.All Of Em Seems To Work Fine But Volte Is Not Working On Any Of Em So I Had To Switch Back To Stock. I Tested AOSP 9.0,RR 9.0 And Lineage 8.1:silly:
It's_Shawn said:
I've Flashed Phh's GSI Treble Roms.All Of Em Seems To Work Fine But Volte Is Not Working On Any Of Em So I Had To Switch Back To Stock. I Tested AOSP 9.0,RR 9.0 And Lineage 8.1:silly:
Click to expand...
Click to collapse
Which TWRP did you use?
And where can I find the stock firmware?
johndoe5 said:
Which TWRP did you use?
And where can I find the stock firmware?
Click to expand...
Click to collapse
That Time I Didn't Use Any Recovery,I Used Fastboot Commands
Hey I successfully installed TWRP recovery but I didn't flash magisk yet. But even now there is a message in status bar saying "Rooting of your phone has been detected. Tap to fix" and that screen is showing me to install 2.1GB OTA update. Idk what is happening I never faced such thing in any of my earlier phone while twrp flashing . What is this ? Can I install the update ? And why is it showing. Will there be possible bootloops if I install the update or willI I still be having TWRP or stock recovery get flashed. Please answer so i can proceed with my choice.
5s4rnv33r said:
Hey I successfully installed TWRP recovery but I didn't flash magisk yet. But even now there is a message in status bar saying "Rooting of your phone has been detected. Tap to fix" and that screen is showing me to install 2.1GB OTA update. Idk what is happening I never faced such thing in any of my earlier phone while twrp flashing . What is this ? Can I install the update ? And why is it showing. Will there be possible bootloops if I install the update or willI I still be having TWRP or stock recovery get flashed. Please answer so i can proceed with my choice.
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...l-method-root-realme-1-install-t3908030/page3
try the solution written in soham028 's post.
it worked for me and updating os will remove root.
vikas2316 said:
https://forum.xda-developers.com/re...l-method-root-realme-1-install-t3908030/page3
try the solution written in soham028 's post.
it worked for me and updating os will remove root.
Click to expand...
Click to collapse
Updating OS will remove root but will it also remove TWRP ???
One more question I followed all the steps correctly (including wiping data) but from TWRP I can't mount DATA.
---------- Post added at 10:01 PM ---------- Previous post was at 09:13 PM ----------
After wiping data if I just reboot to TWRP recovery then I can mount the DATA but once I have started the phone and set it up then again I boot into TWRP recovery and when I try to mount DATA I am not able to do so. Can't mount /data invalid argument. Please suggest something.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Backups works
- Flash Rom works
- Sdcard works
Download:
TWRP
To Flash the TWRP:
Code:
fastboot flash recovery twrp-RMX1971-20191017.img
Then reboot in TWRP manually.
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/thesprintster/device_realme_RMX1971/commits/android-9.0
Precompiled Stock Kernel in use
Credits:
Thanks to other testers for the tests and the support
Created 2019-10-17
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA:DevDB Information
[RECOVERY][3.3.1-14][RMX1971]Unofficial TWRP for Realme 5 Pro (Stable), Tool/Utility for the Realme 5 Pro
Contributors
thesprintster, mauronofrio
Source Code: https://github.com/thesprintster/device_realme_RMX1971/commits/android-9.0
Version Information
Status: Stable
Created 2019-10-17
Last Updated 2019-10-17
Reserved
Why is there 3.3.1-9 in the download and 3.3.1-14 in the title? Did you share accidentally an older version or mistake in title?
greenys' said:
Why is there 3.3.1-9 in the download and 3.3.1-14 in the title? Did you share accidentally an older version or mistake in title?
Click to expand...
Click to collapse
mistake in title
thesprintster said:
mistake in title
Click to expand...
Click to collapse
Ah, I see. Thank you.
Edit.: You accidentally edited the title wrong. Noe it's 3.3.1-19 instead of 3.3.1-9.
Thanks dev for recovery. My phone has been trapped in bootloop after flashing magisk 20.0 . I have twrp back-up in my sd card and I'm restoring backup again. I was flashing to install titanium plus and vanced YouTube
Amot00 said:
Thanks dev for recovery. My phone has been trapped in bootloop after flashing magisk 20.0 . I have twrp back-up in my sd card and I'm restoring backup again. I was flashing to install titanium plus and vanced YouTube
Click to expand...
Click to collapse
How did you flash magisk? I mean first you gotta unlock bootloader. Did you successfully use in-depth test.
will try it soon..
On screen shot its lineage os.. ?
How to unlock the bootloader on Realme 5 Pro?
I mean there's no any tutorial to unlock it yet.. I found some tutorials on google but it doesn't look trusted..
Mustn't we unlock it first then eventually can install twrp ?
jijoejoe123 said:
will try it soon..
On screen shot its lineage os.. ?
Click to expand...
Click to collapse
Yes! I definitely need it!
New build guyz, fixed external sd card mounting. Link in 1st post.
Aizenmas said:
How to unlock the bootloader on Realme 5 Pro?
I mean there's no any tutorial to unlock it yet.. I found some tutorials on google but it doesn't look trusted..
Mustn't we unlock it first then eventually can install twrp ?
Click to expand...
Click to collapse
Go through : https://www.youtube.com/watch?v=FyEEmaaQZh8
Finally , a good news
Failed backup system image (size 5GB).. how to do?
thesprintster said:
New build guyz, fixed external sd card mounting. Link in 1st post.
View attachment 4847759
Click to expand...
Click to collapse
After bootloader unlock and following instructions it says failed to mount system_root and can't flash anything. Especially not lineage os, opengapps and magisk.
greenys' said:
After bootloader unlock and following instructions it says failed to mount system_root and can't flash anything. Especially not lineage os, opengapps and magisk.
Click to expand...
Click to collapse
Yes, this twrp is junk
i can not flash rom lg16 or stock rom ( stock rom convert opzip to zip) ,devices bug mount system_root
I got bootloop after install Rom Lineage, how to fix it?
29y6145 said:
Yes, this twrp is junk
i can not flash rom lg16 or stock rom ( stock rom convert opzip to zip) ,devices bug mount system_root
Click to expand...
Click to collapse
-----------------------------
TWRP flashing and LenageOS installation REALME 5 pro/Q
1)make sure that your bootloader is unlocked.
you can vist this link https://c.realme.com/in/post-details/1184734239149522944 OR
this youtube video
for referance
2)after you have a unlocked bootloader, download the neccessory files required in your PC
===>platform tools (fastboot files) link: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
===>TWRP recovery img . link: https://drive.google.com/drive/folders/1_pRUK4bj74N6xErkpFLr--2GoKyGxUtl
===> vbmeta img . link: https://drive.google.com/file/d/1kq9rV3eF8rYAUwmUvXo-8vttYIhVcQCb/view
===>Leneage OS for realme 5 pro . link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
3) once you have all the files
flash the vbmeta.img with fastboot..
COMMAND : fastboot flash vbmeta vbmeta.img
4) after that flash the recovery
COMMAND: fastboot flash recovery twrp-RMX1971-20191018.img
5) after that reboot into recovery by pressing the volume button on your phone and see " reboot recovery" in a red font
and press power button when u see that.
--.OPTIANAL AND RISKY step {IF YOU WANT TO BOOT INTO COLOROS AFTER INSTALLING TWRP, FLASH THE TWRP RECOVERY IMG AS BOOT ,i dont know this work in new twrp.but worked for me(fastboot flash boot twrp-RMX1971-20191018.img )}
6)after u successfully get the twrp menu make a backup of your whole system(all partitions) in case something goes wrong and move the backup into a lap or memory card
7)install the LenageOS and gapps . and reboot into fastboot mode and do step 3 again but this time flash vbmeta.img from this link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
8) wipe the whole data partition
9) reboot normally.
IN CASE YOU ARE STUCK IN THE RECOVERY MODE OR FASTBOOT MODE FEEL FREE TO CONTACT ME @azharsalim135
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
DnZX said:
I got bootloop after install Rom Lineage, how to fix it?
Click to expand...
Click to collapse
For non indian version Need seperate twrp to flash lineage.. It will be available soon. Dev working on it
working instal magisk in stock rom?
puturaya20 said:
working instal magisk in stock rom?
Click to expand...
Click to collapse
Dont try to install in stock rom.. I heard ita giving problems.. Backup stock before trying..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Back camera
Front camera
Audio
Sensors
Flash
GPS
VoLTE
Known issues :
Selinux permissive
Report with logcat if found any
Instructions :
Download the latest build
Reboot to recovery
Make sure you're using stock unmodified vendor.
Wipe data, cache, system ( Don't wipe vendor )
Flash the latest build and GApps
Reboot
Downloads :
Unofficial Builds : Click Here
Source :
Device tree
Kernel tree
Credits :
@SagarMakhar for his work on Realme X
Thanks to all testers who helped in testing
XDA:DevDB Information
[ROM][RMX1971][9.0.0][UNOFFICIAL] LineageOS 16.0, ROM for the Realme 5 Pro
Contributors
thesprintster, SagarMakhar
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP
Based On: Lineage OS
Version Information
Status: Stable
Created 2019-10-18
Last Updated 2019-10-18
Screenshots:
Changelog:
20191018: Initial build
20191109: Here
20191116: Here
Amazing job brother
using as daily driver from last 2 weeks ^_^
Everything Works perfect , Stable ROM :fingers-crossed::laugh:
note :
Keep ambiance display (Always-on display) off ( because our touch drivers are outdated ;p touch doesn't work after booting device, need to press power button on and off to get touch working and with ambiance display on screen doesn't sleep so touch won't work ;p so simple keep it off ;p )
this should get fixed in upcoming builds so relax
yog12 said:
Amazing job brother
Click to expand...
Click to collapse
have you tried it?
---------- Post added at 05:43 AM ---------- Previous post was at 05:34 AM ----------
thesprintster said:
Screenshots:
View attachment 4847829 View attachment 4847831 View attachment 4847833 View attachment 4847835 View attachment 4847837
Changelog:
20191018: Initial build
Click to expand...
Click to collapse
how about the camera quality? is it similar?
:silly: Yeaaaay... gonna try soon..
will try today..
Good job bro
iam flashing bug failed to mount '/system_root'
my devices realme Q
what is the purpose of vbmeta.img?
star.vest2 said:
what is the purpose of vbmeta.img?
Click to expand...
Click to collapse
Do you need to flash this vbmeta.img as well or just the rom?
Touch is not working
thesprintster said:
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Back camera
Front camera
Audio
Sensors
Flash
GPS
VoLTE
Fingerprint
Known issues :
Selinux permissive
Report with logcat if found any
Instructions :
Download the latest build
Reboot to recovery
Make sure you're using stock unmodified vendor.
Wipe data, cache, system ( Don't wipe vendor )
Flash the latest build and GApps
Reboot
Downloads :
Unofficial Builds : Click Here
Source :
Device tree
Kernel tree
Credits :
@SagarMakhar for his work on Realme X
Thanks to all testers who helped in testing
XDA:DevDB Information
[ROM][RMX1971][9.0.0][UNOFFICIAL] LineageOS 16.0, ROM for the Realme 5 Pro
Contributors
thesprintster, SagarMakhar
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP
Based On: Lineage OS
Version Information
Status: Stable
Created 2019-10-18
Last Updated 2019-10-18
Click to expand...
Click to collapse
touch is not working.
it was working initially then screen became irresponsive on reboot
Karan Yuvraj Singh said:
touch is not working.
it was working initially then screen became irresponsive on reboot
Click to expand...
Click to collapse
U have to flash it again.. Turn of ambient diaply immediately after booting.. There is some.problem with that..
How is it, is there any serious bug in this rom?
How is the camera quality? Can i still use the wide angle lens as well? How if i wanna go back to Color Os? Vooc still working?
mfauzanalg said:
How is it, is there any serious bug in this rom?
How is the camera quality? Can i still use the wide angle lens as well? How if i wanna go back to Color Os? Vooc still working?
Click to expand...
Click to collapse
Can't even flash lineage os with the twrp recovery provided by the same guy. I'm stuck in recovery now and can't flash a single thing for system_root cannot be mounted invalid anrgument. Don't try this.
greenys' said:
Can't even flash lineage os with the twrp recovery provided by the same guy. I'm stuck in recovery now and can't flash a single thing for system_root cannot be mounted invalid anrgument. Don't try this.
Click to expand...
Click to collapse
Hmmm, so what can you do noww to repair it? I rlly want aosp rom on my device (( i dont like color os (
Karan Yuvraj Singh said:
touch is not working.
it was working initially then screen became irresponsive on reboot
Click to expand...
Click to collapse
jijoejoe123 said:
U have to flash it again.. Turn of ambient diaply immediately after booting.. There is some.problem with that..
Click to expand...
Click to collapse
WIll address it in next build
greenys' said:
Can't even flash lineage os with the twrp recovery provided by the same guy. I'm stuck in recovery now and can't flash a single thing for system_root cannot be mounted invalid anrgument. Don't try this.
Click to expand...
Click to collapse
Some Non indian firmware devices are facing trouble while flashing. I have to inspect it
JominatorX said:
Do you need to flash this vbmeta.img as well or just the rom?
Click to expand...
Click to collapse
i don't know the author included it in the download page, so i'm asking
star.vest2 said:
i don't know the author included it in the download page, so i'm asking
Click to expand...
Click to collapse
-----------------------------
TWRP flashing and LenageOS installation REALME 5 pro/Q
1)make sure that your bootloader is unlocked.
you can vist this link https://c.realme.com/in/post-details/1184734239149522944 OR
this youtube video
for referance
2)after you have a unlocked bootloader, download the neccessory files required in your PC
===>platform tools (fastboot files) link: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
===>TWRP recovery img . link: https://drive.google.com/drive/folders/1_pRUK4bj74N6xErkpFLr--2GoKyGxUtl
===> vbmeta img . link: https://drive.google.com/file/d/1kq9rV3eF8rYAUwmUvXo-8vttYIhVcQCb/view
===>Leneage OS for realme 5 pro . link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
3) once you have all the files
flash the vbmeta.img with fastboot..
COMMAND : fastboot flash vbmeta vbmeta.img
4) after that flash the recovery
COMMAND: fastboot flash recovery twrp-RMX1971-20191018.img
5) after that reboot into recovery by pressing the volume button on your phone and see " reboot recovery" in a red font
and press power button when u see that.
--.OPTIANAL AND RISKY step {IF YOU WANT TO BOOT INTO COLOROS AFTER INSTALLING TWRP, FLASH THE TWRP RECOVERY IMG AS BOOT ,i dont know this work in new twrp.but worked for me(fastboot flash boot twrp-RMX1971-20191018.img )}
6)after u successfully get the twrp menu make a backup of your whole system(all partitions) in case something goes wrong and move the backup into a lap or memory card
7)install the LenageOS and gapps . and reboot into fastboot mode and do step 3 again but this time flash vbmeta.img from this link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
8) wipe the whole data partition
9) reboot normally.
IN CASE YOU ARE STUCK IN THE RECOVERY MODE OR FASTBOOT MODE FEEL FREE TO CONTACT ME @azharsalim135
thanks man i managed to boot after i flashed the vbmeta, but any lockscreen method doesn't work. And i forgot to backup the color os so i can't get back to it. Any ideas how to flash magisk? @jijoejoe123
jijoejoe123 said:
-----------------------------
TWRP flashing and LenageOS installation REALME 5 pro/Q
1)make sure that your bootloader is unlocked.
you can vist this link https://c.realme.com/in/post-details/1184734239149522944 OR
this youtube video
for referance
2)after you have a unlocked bootloader, download the neccessory files required in your PC
===>platform tools (fastboot files) link: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
===>TWRP recovery img . link: https://drive.google.com/drive/folders/1_pRUK4bj74N6xErkpFLr--2GoKyGxUtl
===> vbmeta img . link: https://drive.google.com/file/d/1kq9rV3eF8rYAUwmUvXo-8vttYIhVcQCb/view
===>Leneage OS for realme 5 pro . link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
3) once you have all the files
flash the vbmeta.img with fastboot..
COMMAND : fastboot flash vbmeta vbmeta.img
4) after that flash the recovery
COMMAND: fastboot flash recovery twrp-RMX1971-20191018.img
5) after that reboot into recovery by pressing the volume button on your phone and see " reboot recovery" in a red font
and press power button when u see that.
--.OPTIANAL AND RISKY step {IF YOU WANT TO BOOT INTO COLOROS AFTER INSTALLING TWRP, FLASH THE TWRP RECOVERY IMG AS BOOT ,i dont know this work in new twrp.but worked for me(fastboot flash boot twrp-RMX1971-20191018.img )}
6)after u successfully get the twrp menu make a backup of your whole system(all partitions) in case something goes wrong and move the backup into a lap or memory card
7)install the LenageOS and gapps . and reboot into fastboot mode and do step 3 again but this time flash vbmeta.img from this link:https://drive.google.com/drive/folders/1wa4bllIa6WgH1STAszdxC_xkBTEHDSiT
8) wipe the whole data partition
9) reboot normally.
IN CASE YOU ARE STUCK IN THE RECOVERY MODE OR FASTBOOT MODE FEEL FREE TO CONTACT ME @azharsalim135
Click to expand...
Click to collapse
Nothing changes. Still can't flash a thing from twrp. Error: 7, failed to mount /system_root (invalid argument)
Code:
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is this?
An AOSP based ROM, with gapps included and gesture support (pocket, hand wave, pickup).
Based on Android 10.0
Bugs:
voLTE - currently broken, working with Phh to get it up and running, absolutely no ETA, if you need voLTE, use any of the other roms
Steps:
1. Use latest CosmicDan treble TWRP
2. Re-partition to treble layout if you haven't done so yet
3. Flash vendor.img, system.img and a treble supported kernel (you can use mine or any of the other treble kernels on tissot xda)
4. Wipe data if coming from any other rom(!)
5. Flash Rom (No need for gapps, do not flash them, they are included!)
6. Reboot and wait for setup wizard to come up (may take 2-3 minutes)
7. Reboot to twrp and flash magisk (optional)
8. Reboot
Downloads: Link
Thanks to @Ranjan for IMS.apk
@phhusson for his work on GSI (donate to this man, he works on dozens of devices)
@flex1911 for his help bringing 9.0 kernel source for tissot
Oreo team (you all know who you are,@cosmicdan for twrp, @ghpranav for treble vendor source)
Enjoy!
P.S.
I am not going to add any custom features from other roms so please don't comment about that, feel free to flash any other GSI with this vendor/kernel if you want other features.
Source: https://github.com/aosp-tissot
kernel source: https://github.com/aosp-tissot/android_kernel_xiaomi_msm8953-1
Credit to @flex1911 for the original work on the kernel
XDA:DevDB Information
[GSI][ROM][10.0][AOSP+GAPPS][04/08/20], ROM for the Xiaomi Mi A1
Contributors
sooti, phhusson, flex1911, Ranjan
Source Code: https://github.com/aosp-tissot
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Treble
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2020-05-07
Created 2019-11-05
Last Updated 2020-08-04
Changelog:
04/08/20:
* Added option to close annoying suggestions in settings (like we could in pie)
* August security patch
08/07/20:
* Fixed voLTE, no more crashes from SMS
07/07/20:
* July Security patch
28/06/20:
* Remove voLTE apk being installed by default, caused crashes for some users
21/06/20:
* Added voLTE support for all qcom devices
02/06/20:
* Rebased device tree and changed gapps to GMSEXPRESS (what OEMs get from google)
* June security patch
* Small other fixes
07/05/20:
* May security update
* Some Phh treble fixes and settings
* Updated kernel to 4.9.222
09/02/20:
* Feb security patch
25/01/20:
* Jan security patch
* Updated to latest 4.9 source for kernel
07/11/19:
* Fixed DRM
06/11/19:
* Fixed bootloop by disabling forced FDE encryption
* Fixed secure adb not being enabled
05/11/19:
* Initial release
* November security patch
* Up-streamed latest 4.9 kernel source from android
sooti said:
Changelog:
05/11/19:
* Initial release
* November security patch
* Up-streamed latest 4.9 kernel source from android
Click to expand...
Click to collapse
TUTORIAL WITH NO SENSE, what to flash, when? I flashed 1.boot 2.vendor 3.system image 4.kernel, reboot and bootlop
How to flash this?
GabiML said:
TUTORIAL WITH NO SENSE, what to flash, when? I flashed 1.boot 2.vendor 3.system image 4.kernel, reboot and bootlop
How to flash this?
Click to expand...
Click to collapse
There's no order.
EDIT: BOOT IMG is the Kernel
zurik said:
There's no order.
EDIT: BOOT IMG is the Kernel
Click to expand...
Click to collapse
And at step with FLASH ROM, what to flash because before it said to flash vendor sistem and boot.
Now, i flashed vendor then system then boot and reboot, again bootlop. Is it working at all?
GabiML said:
And at step with FLASH ROM, what to flash because before it said to flash vendor sistem and boot.
Click to expand...
Click to collapse
Wipe Data, System, Dalvik and Vendor (Be sure your phone repartitioned to support treble).
Flash System, Vendor and Boot.
After the 1st boot, you can flash Magisk too (Optional)
zurik said:
Wipe Data, System, Dalvik and Vendor (Be sure your phone repartitioned to support treble).
Flash System, Vendor and Boot.
After the 1st boot, you can flash Magisk too (Optional)
Click to expand...
Click to collapse
NOT WORKING, i did it. Bootlop. Have you some screenshots with it?
GabiML said:
NOT WORKING, i did it. Bootlop. Have you some screenshots with it?
Click to expand...
Click to collapse
Format Data tried?
GabiML said:
NOT WORKING, i did it. Bootlop. Have you some screenshots with it?
Click to expand...
Click to collapse
What do you mean "bootlooped"?
It might reboot the first time to encrypt data
Here it begins. Thanks sooti
I'm from AOSPExtended Pie..
Step i do :
1. Trebelized with CosmicDan TWRP
2. Wipe System, Data, Internal, Vendor.
3. Flash Vendor.img
4. Flash System.img
5. Flash Boot.img
6. Format Data then Yes
7. Reboot TWRP
8. Flash System.img again..
9. Reboot System
First boot it's make reboot when showing mi logo then second boot i'm stuck at mi Logo..
Any step i miss? or i do wrong step?
Please advice.. Thanks..
donnebanget said:
I'm from AOSPExtended Pie..
Step i do :
1. Trebelized with CosmicDan TWRP
2. Wipe System, Data, Internal, Vendor.
3. Flash Vendor.img
4. Flash System.img
5. Flash Boot.img
6. Format Data then Yes
7. Reboot TWRP
8. Flash System.img again..
9. Reboot System
First boot it's make reboot when showing mi logo then second boot i'm stuck at mi Logo..
Any step i miss? or i do wrong step?
Please advice.. Thanks..
Click to expand...
Click to collapse
Do you have logs? Did you wait long enough?
sooti said:
Do you have logs? Did you wait long enough?
Click to expand...
Click to collapse
i Thinks i wait 10 to 15 minutes..
I am not sure how to get logs..
But that a correct step i do?
donnebanget said:
i Thinks i wait 10 to 15 minutes..
I am not sure how to get logs..
But that a correct step i do?
Click to expand...
Click to collapse
Did you follow 6th. step?
just in case, "wipe" and "format" data aren't the same thing.
Some ROMs show "Enter code" screen (i.e.PixelExperience), while others just bootloop (i.e. EvolutionX), both for the same reason, an encrypted device.
However, try to do all steps again to be sure.
KaaMyA said:
Did you follow 6th. step?
just in case, "wipe" and "format" data aren't the same thing.
Some ROMs show "Enter code" screen (i.e.PixelExperience), while others just bootloop (i.e. EvolutionX), both for the same reason, an encrypted device.
However, try to do all steps again to be sure.
Click to expand...
Click to collapse
Thanks for advice, i'll try again..
Update : Using Flex Vendor and boot normaly but SIM Card not detected forgot my room have bad signal.. :laugh::laugh:
Is the look and feel the same as the 9.0 version? Like same camera etc?
donnebanget said:
Thanks for advice, i'll try again..
Update : Using Flex Vendor and boot normaly but SIM Card not detected forgot my room have bad signal.. :laugh::laugh:
Click to expand...
Click to collapse
Weird, maybe encryption has issues? I'll test it tomorrow and upload a change if needed, flex vendor is missing some commits
sooti said:
Weird, maybe encryption has issues? I'll test it tomorrow and upload a change if needed, flex vendor is missing some commits
Click to expand...
Click to collapse
And when starting phone have warning "There's an internal problem with your device. Contact your manufacturer for details."
- Google Play Device not certified
- Chrome sometimes freeze
donnebanget said:
And when starting phone have warning "There's an internal problem with your device. Contact your manufacturer for details."
- Google Play Device not certified
- Chrome sometimes freeze
Click to expand...
Click to collapse
Ya that's because your on flex vendor, if you flash other people's vendor I can't help you
sooti said:
Ya that's because your on flex vendor, if you flash other people's vendor I can't help you
Click to expand...
Click to collapse
Aaah, okaay my bad..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : http://download.lineageos.org/voyager
SemcCamera addon : https://androidfilehost.com/?w=files&flid=305730
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][voyager][10] LineageOS 17.1, ROM for the Sony Xperia XA2
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2020-04-21
Last Updated 2020-04-21
[ protip: These builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261777345 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
6. Flash https://androidfilehost.com/?fid=4349826312261712574
7. Profit?
Hey Luk,
thanks for working on this great phone.
I sadly got some problems while installing your release on a H4413 (DUAL SIM).
I come from Sailfish OS and flashedH4413 50.2.A.0.400 Customized_NOBA via EMMA.
After that I follow the instructions from the linage install page.
It all seems to work but after I do a "adb reboot" the phone starts to go into a bootloop flashing
the Sony Logo and then for just sec a generic Android Logo after that it goes to a blank screen.
Whats strange is that after the initial flash of the lineage build twrp shows the there is no os installed warning
and sometimes it shows the install twrp app screen both times the result is the same. Bootloop.
Do you have any hint how to go from here? (After restore through emma the phone works normal again)
best cecja
twrp version: twrp-3.3.1-1-voyager
lineage version: lineage-17.1-20200427-nightly-voyager-signed
cecja said:
Hey Luk,
thanks for working on this great phone.
I sadly got some problems while installing your release on a H4413 (DUAL SIM).
I come from Sailfish OS and flashedH4413 50.2.A.0.400 Customized_NOBA via EMMA.
After that I follow the instructions from the linage install page.
It all seems to work but after I do a "adb reboot" the phone starts to go into a bootloop flashing
the Sony Logo and then for just sec a generic Android Logo after that it goes to a blank screen.
Whats strange is that after the initial flash of the lineage build twrp shows the there is no os installed warning
and sometimes it shows the install twrp app screen both times the result is the same. Bootloop.
Do you have any hint how to go from here? (After restore through emma the phone works normal again)
best cecja
twrp version: twrp-3.3.1-1-voyager
lineage version: lineage-17.1-20200427-nightly-voyager-signed
Click to expand...
Click to collapse
Ask me again on irc; I don't like guessing on forums.
cecja said:
twrp version: twrp-3.3.1-1-voyager
lineage version: lineage-17.1-20200427-nightly-voyager-signed
Click to expand...
Click to collapse
Bootloop here too, from SFOS.
Back to Omnirom, no problem.
Thanks.
magullo said:
Bootloop here too, from SFOS.
Back to Omnirom, no problem.
Thanks.
Click to expand...
Click to collapse
Same to you, if you join irc I may be able to help.
OK I wanted to try LineageOS 17.1 and was able to flash it successfully on voyager H4493. Here's what I did:
1. Used newflasher to flash 50.2.A.3.22-R3B. I had deleted the mentioned above files. Also newflasher asked if I wanted it flashed to both slots and I pressed y. As such, it was n enter, n enter and y enter.
2. Did not do item 6 above.
3. From twrp recovery 3.3.0-0 I flashed LineageOS 17.1 and after pressing reboot system - I pressed do not install twrp. I booted successfully into the system.
4. Again from twrp, I flashed gapps - again pressed do not install twrp.
5. Issue with Google service - I reset the phone from settings.
6. Success!
7.At the moment restoring my apps and stuff
hamirali said:
OK I wanted to try LineageOS 17.1 and was able to flash it successfully on voyager H4493. Here's what I did:
1. Used newflasher to flash 50.2.A.3.22-R3B. I had deleted the mentioned above files. Also newflasher asked if I wanted it flashed to both slots and I pressed y. As such, it was n enter, n enter and y enter.
2. Did not do item 6 above.
3. From twrp recovery 3.3.0-0 I flashed LineageOS 17.1 and after pressing reboot system - I pressed do not install twrp. I booted successfully into the system.
4. Again from twrp, I flashed gapps - again pressed do not install twrp.
5. Issue with Google service - I reset the phone from settings.
6. Success!
7.At the moment restoring my apps and stuff
Click to expand...
Click to collapse
Skipping step 6 was kinda silly from your end. Newflasher only flashes few partitions to both slots rather than all of them, making this /feature/ almost useless.
LuK1337 said:
Skipping step 6 was kinda silly from your end. Newflasher only flashes few partitions to both slots rather than all of them, making this /feature/ almost useless.
Click to expand...
Click to collapse
Most definitely your assessment is correct, since you are the expert. What would be your advice? Should I perform step 6 now anyway? Especially since I don't seem to have any issues as yet. Thanks!
hamirali said:
Most definitely your assessment is correct, since you are the expert. What would be your advice? Should I perform step 6 now anyway? Especially since I don't seem to have any issues as yet. Thanks!
Click to expand...
Click to collapse
I guess just to be safe, yes.
LuK1337 said:
I guess just to be safe, yes.
Click to expand...
Click to collapse
Done!
LuK1337 said:
I guess just to be safe, yes.
Click to expand...
Click to collapse
Just a query, I have downloaded and flashed a version which is no longer appearing on LineageOS voyager page. Should I flash now the one which is appearing (an earlier version) or should I just wait for a newer version, whenever it is available? Thanks in advance.
hamirali said:
Just a query, I have downloaded and flashed a version which is no longer appearing on LineageOS voyager page. Should I flash now the one which is appearing (an earlier version) or should I just wait for a newer version, whenever it is available? Thanks in advance.
Click to expand...
Click to collapse
Wait for newer one.
LuK1337 said:
Wait for newer one.
Click to expand...
Click to collapse
When will a new one come?
EmmJottAah said:
When will a new one come?
Click to expand...
Click to collapse
This year.
LuK1337 said:
This year.
Click to expand...
Click to collapse
Perfect:good:
LuK1337 said:
This year.
Click to expand...
Click to collapse
I just wanted to report a somewhat minor issue just for record purposes.
When I try to restart my device, it gets stuck at the LineageOS logo. I have then have to enter into twrp recovery and reboot to system.
I don't restart that often and otherwise all works fine, so not much of an issue for me.
H4493 Voyager
LineageOS 4.30.2020
hamirali said:
I just wanted to report a somewhat minor issue just for record purposes.
When I try to restart my device, it gets stuck at the LineageOS logo. I have then have to enter into twrp recovery and reboot to system.
I don't restart that often and otherwise all works fine, so not much of an issue for me.
H4493 Voyager
LineageOS 4.30.2020
Click to expand...
Click to collapse
It's a magisk related issue that I can't reproduce here... Also booting to lineage recovery is supposedly enough too.
LuK1337 said:
This year.
Click to expand...
Click to collapse
Nooooooooooooo!!!!!!!!!!!!!!!!! .... (waits impatiently)
LuK1337 said:
It's a magisk related issue that I can't reproduce here... Also booting to lineage recovery is supposedly enough too.
Click to expand...
Click to collapse
Reporting an issue: H4493 Voyager updated to the latest version lineage-17.1-20200529-nightly-voyager.
Cannot seem to make any calls - No service - requests to turn off airplane mode to make calls. However, the airplane mode is infact already off.
Also, strangely enough (for me at least) I can receive calls and sms.
I (maybe stupidly) thought it might be installation error, so I flashed the latest version from recovery - reinstalled everything.
No luck.
Should I not be able to sort it out, I will have to revert back to my previous version. What would you advise?