Hi there everyone!
Yesterday, I installed lineage 14.1 on my Nexus 5X. I'm googly eyes over it.
Today I see an update notification for a new nightly build.
Which prompts my questions:. Should these be installed on a phone that's my daily driver or should I stick with a version if it's working well for me?
If the answer is yes, should I be performing a backup each time prior to updating or are they pretty mundane affairs?
I imagine after reading this thread, it goes without saying that I'm not savvy to the ways of phone modding and I've learned to ask before I break.
Thanks for your time!
schwim said:
Hi there everyone! Yesterday, I installed lineage 14.1 on my Nexus 5X. I'm googly eyes over it. Today I see an update notification for a new nightly build. Which prompts my questions:. Should these be installed on a phone that's my daily driver or should I stick with a version if it's working well for me? If the answer is yes, should I be performing a backup each time prior to updating or are they pretty mundane affairs? I imagine after reading this thread, it goes without saying that I'm not savvy to the ways of phone modding and I've learned to ask before I break. Thanks for your time!
Click to expand...
Click to collapse
Updating (aka Dirty Flashing) is not requirement and is always a decision that is, purely, up to you.
I, personally, have to look at it with a grain of salt based on what, in fact, was Patched, Fixed, Updated, etc... All based on the LineageOS Changelog for the device.
Lets take my primary device (Galaxy S3 - d2vzw) for example...
I go to the following is just one very helpful LineageOS Changelog website for the 14.1 releases:
https://www.lineageoslog.com/14.1/
Then i select my device (d2vzw) and select the release date as follows:
https://www.lineageoslog.com/14.1/d2vzw#201705151125
Then you'll see the color coding where, obviously, the red lettering indicates the highest importance. You can also select, individually, what each one of them entails exactly within Lineage's Gerrit Code (which is a type of Github).
Then you just make an educated decision based on what your findings.
Nobody can tell you if you should update the Nightly. It's all up to you and the above is just a way to help you make that decision.
Also, if you decide to update over the current Nightly and have SuperSU installed. You will need to open SuperSU after the update and it will ask you for SuperSU to install the binaries so be sure to select YES/OK.
This is because any LineageOS Nightly updates you make will undo a few minor changes SuperSU had made when it was installed before and just needs to apply those changes back for SuperSU to operate properly.
I did my best to help you out via text.
I wish you the best of luck!
"Live Long and Prosper..."
~Ambassador S'chn T'gai Spock
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
Thanks very much for your help, Ibu,
Can I ask if you backup prior to updating to a new nightly or are they like OEM rom updates on phones that aren't unlocked or rooted where they are expected to just work?
Ibuprophen said:
Updating (aka Dirty Flashing) is not requirement and is always a decision that is, purely, up to you.
I, personally, have to look at it with a grain of salt based on what, in fact, was Patched, Fixed, Updated, etc... All based on the LineageOS Changelog for the device.
Click to expand...
Click to collapse
schwim said:
Thanks very much for your help, Ibu, Can I ask if you backup prior to updating to a new nightly or are they like OEM rom updates on phones that aren't unlocked or rooted where they are expected to just work?
Click to expand...
Click to collapse
That's a very good question @schwim!
This is more of a personal preference as it's not a requirement.
Actually, I very rarely perform an update to the ROM and always base this decision, solely, on a "case by case" basis.
As an FYI... Updating a ROM is most commonly known as "Dirty Flashing".
Before I even update a ROM (dirty flash), do a fresh install of a ROM or test out certain Apps/flashable zips i, personally, make a full backup in TWRP to my external MicroSD before hand. This is so i can recover from anything that may impact the performance of the device itself.
Also, if i have to recover/restore from the TWRP backup, allot of individuals state that you need to wipe everything before hand but, I don't. Before restoring a backup in TWRP, I just perform a factory reset, then perform the restoration of the TWRP backup. It isn't perfect but, hasn't failed me yet.
*** Please Note: I don't perform a Factory Reset before Backing in TWRP... Only if I'm Restoring a TWRP Backup. And, though i don't endorse performing a TWRP Restore from Nougat back to Marshmallow... I've been successful, personally, doing so following the same steps. And IMPORTANTLY, no guarantees of 100% success 100% of the time... Since I'd, personally, have averaged TWRP restoring to be successful approx. 95% +/- of the time.
Don't worry about asking me any further questions as i do encourage it and i will answer as best as I can and will be honest if I am guessing, sure about or don't know the answer.
I call it "Provoking/Probing the Process of Thought!" and I've ALWAYS told others that "You don't have to take my word for it... Do some research in support of or against my advice"
"Live Long and Prosper..."
~Ambassador S'chn T'gai Spock
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
Hi there and thanks a bunch for your help!
I noticed this morning that the autocheck displayed both available nightly updates. Are these updates the type that you have to be update all of them incrementally or would just updating the latest available bring you up to date?
Related
Greetings,
Firstly, sorry for the noob question, but I recall that the snapshot versions of CM had their own custom recovery (CM Recovery) that could be updated via OTA together with the ROM itself for stability reasons. I haven't seen this on any other ROM and I'd like to ask if Lineage will have it's own recovery the same way CM did or not.
I particularly liked the feature because it allowed me to factory reset the phone without needing twrp (even though i'm not sure that the rom having it's own recovery has to do with being able to factory reset the same way stock roms do).
Once again, sorry for my "noobishness" and thank you to all who took their time to read this
Why not TWRP ?
We learn by asking - welcome to the club. Anyway, if there is a TWRP or Philz or an existing CM recovery for your device, why not just load one of them? I've never had a problem with the interaction between TWRP and CM, so I assume that will hold for the Lineage build(s) as well. That even includes my clumsy hacks of TWRP to get it onto unsupported devices. It seems to be remarkably robust and forgiving, and since a recovery really doesn't do a whole lot in comparison to a complete ROM, difficult to go far wrong. If there's no TWRP for you device, as long as you have the same processor there are VERY useful guides out here for porting it. The more the hardware you've got is similar to something that already works, the easier it is to do this. I frankly assumed I would brick everything I tried but so far I've been 100% successful - proof of blind luck. Oh yeah, it REALLY helps to have a stable working ROM image to revert to if your efforts to do this go South. That 100% success rate is after a few: "whew, glad I had this to go back to" moments along the way. :cyclops:
Good Luck !!
nezlek said:
We learn by asking - welcome to the club. Anyway, if there is a TWRP or Philz or an existing CM recovery for your device, why not just load one of them? I've never had a problem with the interaction between TWRP and CM, so I assume that will hold for the Lineage build(s) as well. That even includes my clumsy hacks of TWRP to get it onto unsupported devices. It seems to be remarkably robust and forgiving, and since a recovery really doesn't do a whole lot in comparison to a complete ROM, difficult to go far wrong. If there's no TWRP for you device, as long as you have the same processor there are VERY useful guides out here for porting it. The more the hardware you've got is similar to something that already works, the easier it is to do this. I frankly assumed I would brick everything I tried but so far I've been 100% successful - proof of blind luck. Oh yeah, it REALLY helps to have a stable working ROM image to revert to if your efforts to do this go South. That 100% success rate is after a few: "whew, glad I had this to go back to" moments along the way. :cyclops:
Good Luck !!
Click to expand...
Click to collapse
Actually, i have twrp on my phone and i love it, but i'm aiming to pass along this device to my elders that are not as tech sawy as i am. Só i wanted to give'em something functional, and there's where CM recovery saved me - everytime they need to factory reset their CM flashed phone they won't even need to enter bootloader to do it! I just hope it will be possible to do the same with LineageOS.
PS: i tried to do a factory reset from the settings menu with twrp on my phone and it didn't work. The phone remained exactly the same, just as if i hadn't done anything.
PS2: i know that twrp offers a factory reset option on it's menu but it would be hard to teach them how to use the recovery.
Or, if the devs intend to make a "Lineage Recovery" for whatever other reasons, i'd be curious to know them as well :good:
Thanks for the answer ?
well .....
"Actually, i have twrp on my phone and i love it, but i'm aiming to pass along this device to my elders that are not as tech sawy as i am. Só i wanted to give'em something functional, and there's where CM recovery saved me - everytime they need to factory reset their CM flashed phone they won't even need to enter bootloader to do it! I just hope it will be possible to do the same with LineageOS. "
I guess the magic question would be "how often are they going to be using it?" In the case of TWRP, the periodic (weekly or monthly) backup is about as blind simple as it can get - even I can do it without too much concentration
As for points of entry, CM / Lineage can easily be set to reboot to the recovery mode, whatever you use. It's down there in Developer Settings - piece of cake. Once done, tell TWRP to reboot to the System. a second piece, a la mode.
Good Luck.
It will be nice if Lineage produce their own recovery as CM .
In my case with Oppo R5 there isnt any recovery availaible yet to flash LineageOS
Existing TWRP and CM recoveries are useless
NO, but there are lots of options for the Honor 5X which seems to be very similar. Maybe you could port one of those? WHY, specifically, are they "useless" ?? If you would care to itemize what you tried and how they failed, maybe we could help.
nezlek said:
NO, but there are lots of options for the Honor 5X which seems to be very similar. Maybe you could port one of those? WHY, specifically, are they "useless" ?? If you would care to itemize what you tried and how they failed, maybe we could help.
Click to expand...
Click to collapse
Thanks for your response. With cm recovery we are getting signature verification failure. When we flash existing twrp recovery for our devise the phone stuck in oppo logo. Furthermore I don't have the knowledge to port recovery and our community is short of developers
Sent from my R5 using XDA-Developers Legacy app
mermigas said:
Thanks for your response. With cm recovery we are getting signature verification failure. When we flash existing twrp recovery for our devise the phone stuck in oppo logo. Furthermore I don't have the knowledge to port recovery and our community is short of developers
Sent from my R5 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Seems to be a somewhat common occurrence among octa-core devices, although I have more experience with MTK chipsets. In many cases they are still using the quad-core versions of code in their stock recoveries. Curiosity question: do you also find that the stock recovery mysteriously replaces the TWRP you just installed after it fails? Some MTK devices appear to stash a hidden copy of the stock recovery away and do this for (to) you. Not fun. :crying:
Does anyone know a custom ROM that has it's own recovery? I've been searching but haven't found anything yet.
I'm in doutbt that such rom even exists after CM got out of the picture since it was the only one that had it's own recovery..
A lineageOS specific custom recovery would be good, mainly because TWRP versions greater than 2.8 cause several banking and security apps to fail because they think the device is rooted even if its not. Many of these apps, like blackberry uem client (formerly known as GFE) falsely detect root simply because of something that TWRP has done in versions after 2.8 and this has nothing to do with unlocked bootloader flags. While lineageOS without the root addon passes safteynet now, in future it will be good if lineage has its own recovery rather than a third party recovery like TWRP.
Plus it would be nice to have one integrated system without the need to maintain/update two different pieces of software. It would just be cleaner, but that is a matter of taste.
Sent from my Nexus 9 using Tapatalk
I saw somewhere that they had plans for this but, after they've completed most/all the ROM releases.
I can't remember where I read it but, i do know that their still working on releases for more devices.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************
It is literally necessary, because recoveries depend on kernels, and currently TWRP use binary kernels in the repository (github:TeamWin/android_device_xiaomi_lithium) which may render it unusable due to kernel mismatch. Why not compile our own kernel when we have source code, and why not use the same kernel in the recovery? The best solution is to collect them together, under an unified organization.
test123321123123213 said:
It is literally necessary, because recoveries depend on kernels, and currently TWRP use binary kernels in the repository (github:TeamWin/android_device_xiaomi_lithium) which may render it unusable due to kernel mismatch. Why not compile our own kernel when we have source code, and why not use the same kernel in the recovery? The best solution is to collect them together, under an unified organization.
Click to expand...
Click to collapse
That is the dumbest thing you could imagine. Mainly when soo many different things effect the kernel. Also the kernel that you flash for the OS is not the same as what is needed in recovery.
Also cm recovery was the cause for many bricked devices. They have become more of a laughing g stock to android the miui, which is saying a lot. Many thing Los and Xiaomi should Tema up to make the ultimate joke device.
nezlek said:
We learn by asking - welcome to the club. Anyway, if there is a TWRP or Philz or an existing CM recovery for your device, why not just load one of them? I've never had a problem with the interaction between TWRP and CM, so I assume that will hold for the Lineage build(s) as well. That even includes my clumsy hacks of TWRP to get it onto unsupported devices. It seems to be remarkably robust and forgiving, and since a recovery really doesn't do a whole lot in comparison to a complete ROM, difficult to go far wrong. If there's no TWRP for you device, as long as you have the same processor there are VERY useful guides out here for porting it. The more the hardware you've got is similar to something that already works, the easier it is to do this. I frankly assumed I would brick everything I tried but so far I've been 100% successful - proof of blind luck. Oh yeah, it REALLY helps to have a stable working ROM image to revert to if your efforts to do this go South. That 100% success rate is after a few: "whew, glad I had this to go back to" moments along the way. :cyclops:
Good Luck !!
Click to expand...
Click to collapse
It sounds like you have a lot of luck in this area, I spent ages looking for a TWRP porting guide but couldn't quite find one that worked. Would you be able to get me a link to a good TWRP porting guide for a octa-core Samsung?
Cheers
Hi,
I have TWRP 3.1.1 installed on my LG G4 (h815). My current OS is Lineage, but I always have a backup of the stock rom on my sd card, so that I can switch between Stock Rom and Lineage whenever I want.
When I have the stock rom installed and boot into TWRP, the date and time is correct.
But when I have LineageOS installed and boot into TWRP, the time is wrong and I'm somewhen in 2015.
My backups include the partitions: System, Data, Boot
So I restored them separately to find out, which partition "holds the date and time". It is the Data partition. When I have Lineage installed and restore my Data partition from the Stock Rom, my time in TWRP is correct again. So for some reason, the time of the Data partition of LineageOS is wrong. I checked the time in Lineage, but there it is correct set. It is only wrong in TWRP.
Any idea how I can correct the time on my Lineage Data partition?
Bleuzen said:
Hi, I have TWRP 3.1.1 installed on my LG G4 (h815). My current OS is Lineage, but I always have a backup of the stock rom on my sd card, so that I can switch between Stock Rom and Lineage whenever I want...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within one of the following threads that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3442424
https://forum.xda-developers.com/showthread.php?t=3166384
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Ibuprophen said:
I don't have this device but, your best bet is to post this question within one of the following threads that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3442424
https://forum.xda-developers.com/showthread.php?t=3166384
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I don't have the problem anymore. I updated LineageOS from the latest official build to the latest unofficial testing build for BUGBASH-498.
As a side effect, this build also fixed my time and date problem in TWRP. So it was a bug of LineageOS, which is fixed now.
Anyway, thanks for you reply
I've noticed the same issue with the time in TWRP on my LG G4.
How interesting that this was fixed for you by the same code change that hopefully when merged will also allow nightly updates to be released again for the h811 I have.
Exabyter said:
I've noticed the same issue with the time in TWRP on my LG G4.
How interesting that this was fixed for you by the same code change that hopefully when merged will also allow nightly updates to be released again for the h811 I have.
Click to expand...
Click to collapse
We won't get new official nightly builds until this bug got fixed:
https://jira.lineageos.org/browse/BUGBASH-498
Until than, you can use my unofficial build, if you want:
https://forum.xda-developers.com/lineage/general/temporary-unofficial-builds-h815-t3721909
I have OP3T with latest official TWRP. Date and time is incorrect but i can change on twrp on the terminal however after reboot it will jump back to the incorrect one. Any idea to fix it?
I was succesfully pulling out the build.prop but when i try to edit on my PC just can not find the date and time line...
I installed an unofficial OFFICIAL nightly build of LineageOS 14.1 on an S4 i19505, following the lineage wiki guide for jfltexx devices (not allowed to post a direct link as I'm a new user) - installed via Samsung's "Download mode". It went smoothly, and I have been using it more or less without issue for the last week. Yesterday I was prompted for an OS update, dated the 17th, to replace the current one from the 10th. I clicked the download/install button and followed the on-screen instructions. However, when it arrived at TWRP it did not automatically install, and when I tap "install" and browse to /data/data/org.lineageos.updater/app_updates there is no image or zip file there.
I'm looking for advice on how to sort out this particular update, but also ideally to fix it so that it automatically updates successfully in future - if I have to download the file manually and then update it manually, that's quite a nuisance.
I don't have that much past experience with CM/LineageOS so I may be doing something obviously wrong, if so I'd love to hear it!
alcoer said:
I installed an unofficial nightly build of LineageOS 14.1 on an S4 i19505, following the lineage wiki guide for jfltexx devices...
Click to expand...
Click to collapse
I don't have this variant but, your best bet is to post this question within the following Unofficial LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3520456
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
alcoer said:
I installed an unofficial nightly build of LineageOS 14.1 on an S4 i19505, following the lineage wiki guide for jfltexx devices (not allowed to post a direct link as I'm a new user) - installed via Samsung's "Download mode". It went smoothly, and I have been using it more or less without issue for the last week. Yesterday I was prompted for an OS update, dated the 17th, to replace the current one from the 10th. I clicked the download/install button and followed the on-screen instructions. However, when it arrived at TWRP it did not automatically install, and when I tap "install" and browse to /data/data/org.lineageos.updater/app_updates there is no image or zip file there.
I'm looking for advice on how to sort out this particular update, but also ideally to fix it so that it automatically updates successfully in future - if I have to download the file manually and then update it manually, that's quite a nuisance.
I don't have that much past experience with CM/LineageOS so I may be doing something obviously wrong, if so I'd love to hear it!
Click to expand...
Click to collapse
A unofficial LOS normally has no built in OTA updater. Maybe yours has downloaded an official nightly. You will find it in /data/lineageos_updates
Oops, it isn't the unofficial build, it's the one from lineageos org/jfltexx . Does that change anything? Thanks anyway.
alcoer said:
Oops, it isn't the unofficial build, it's the one from lineageos org/jfltexx . Does that change anything? Thanks anyway.
Click to expand...
Click to collapse
That changes everything. Try to install up-to-date twrp. Maybe that does the automatic update. Otherwise just flash the downloaded zip, wipe cache and dalvik and reboot system.
kurtn said:
That changes everything. Try to install up-to-date twrp. Maybe that does the automatic update. Otherwise just flash the downloaded zip, wipe cache and dalvik and reboot system.
Click to expand...
Click to collapse
TWRP is only a week old, so could it really be that? I'd also kind of like to know what the problem is before doing the manual OS update or I'll likely be here again in a week...
No, the auto-updater doesn't work with the S4.
You need to download on your computer, then transfer to the SD card. Do a dirty install from TWRP after that.
Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally.
Unfortunately, I lost the radio signal: no SIM detected! What do you recommend? Can I flash the previous build without encrypt / decrypt issues on partition phone?
I'm on nougat firmware, S-OFF.
Thanks in advance,
Robe
Some details might help .....
RobeStar said:
Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally.
Unfortunately, I lost the radio signal: no SIM detected! What do you recommend? Can I flash the previous build without encrypt / decrypt issues on partition phone?
I'm on nougat firmware, S-OFF.
Thanks in advance,
Robe
Click to expand...
Click to collapse
It might be useful to know more specifics about the device we are talking about ? Did you make a COMPLETE Nandroid backup (e.g. with TWRP) before you tried flashing the new image, etc.... What was on it before? What did you (not) wipe prior to attempting the install.... SPECIFICALLY, one could ASSUME a previous LOS build, but assumptions are often dangerous. Also, shouldn't lose the IMEI absent a serious glitch. You CAN blow it away if you wipe the area in TWRP but that would lead to a hope that you also backed it up first. If you CAN, restore what was there before all of this unhappiness began and try again ? Good Luck.
nezlek said:
It might be useful to know more specifics about the device we are talking about ? Did you make a COMPLETE Nandroid backup (e.g. with TWRP) before you tried flashing the new image, etc.... What was on it before? What did you (not) wipe prior to attempting the install.... SPECIFICALLY, one could ASSUME a previous LOS build, but assumptions are often dangerous. Also, shouldn't lose the IMEI absent a serious glitch. You CAN blow it away if you wipe the area in TWRP but that would lead to a hope that you also backed it up first. If you CAN, restore what was there before all of this unhappiness began and try again ? Good Luck.
Click to expand...
Click to collapse
Hi nezlek! You're right: here some useful answer.
Device we are talking about ? HTC 10
Did you make a COMPLETE Nandroid backup ? No... :silly:
What was on it before? lineage-14.1-20180411-nightly-pme-signed.zip
When OTA update has been notified, I installed using the rom tool (not twrp). During the update procedure it stopped in twrp, so I just restarted to system. Then I noticed that the radio did not work anymore...
PS: it's more safer to flash the new build in twrp or continue to use system rom ota update?
Ouch
RobeStar said:
Hi nezlek! You're right: here some useful answer.
Device we are talking about ? HTC 10
Did you make a COMPLETE Nandroid backup ? No... :silly:
What was on it before? lineage-14.1-20180411-nightly-pme-signed.zip
When OTA update has been notified, I installed using the rom tool (not twrp). During the update procedure it stopped in twrp, so I just restarted to system. Then I noticed that the radio did not work anymore...
PS: it's more safer to flash the new build in twrp or continue to use system rom ota update?
Click to expand...
Click to collapse
FIRST - Always better (in my book) to flash with TWRP. Others my have different experiences and opinions but it has never let me down.
You predicament is, in a word, not good. If I were you, I would first try re-flashing the previous Lineage build via TWRP. Unfortunately you are probably going to lose some data in all of this. If anything works well enough to backup your system and data partitions, do that first and move that to removable storage and remove it so it is SAFE. Maybe you have Titanium Backup and can do some of the pieces you need ?? Boot into TWRP and re-flash the build file that was on it before this all started. If that "dirty" flash doesn't give you anything useful, try wiping cache, davlik, etc... and repeating (a full factory reset). If THAT fails, download the zip file(s) - LOS, su-add-on, gapps, etc... and pretend you are doing it for the first time (maybe even wipe data and system but then, your stuff is GONE without a backup). But at this point, what have you got to lose? ASSUMING you get things back to a proper working condition, only then do a complete backup and ponder starting over again. The radio, who knows? Losing the IMEI info is much more of a problem since carriers will often not like that. I know it is trivially easy to restore IMEI data on an MTK device, but yours I have no personal knowledge of. There ARE places that will apparently do it for you if you do a little judicious web searching and are willing to part with a little cash for it, but SOMEBODY out here on XDA has to know how to do it for what you have.
And I'm NOT going to say somebody told you so, but they did. NEVER do this sort of thing without a backup in hand or a willingness to wave goodbye to whatever you have installed on or done to a device. I spend not more than 10 minutes a week doing a Nandroid of devices I use regularly. It has saved me a hell of a lot more time than that the very few times I've needed it. So, with apologies for rubbing salt in the wound, it is always better to have 'em and not need 'em than to need 'em and not have 'em
One thing is pretty certain. Most of us rarely repeat this sort of thing. Good Luck.
Can someone flash My phone without my pin
Even though I encrypted it???
RobeStar said:
Hey guys,
I just upgraded htc 10 to the latest official version of lineageos, but the installation got stuck in recovery and then I restarted normally....
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3528508
If all else fails, and you don't receive any responses from the above thread, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device as well.
https://forum.xda-developers.com/showthread.php?t=3527639
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Yesterday, installing OTA and going from 20191008 to 20191010 destroyed my IMEIs on my Moto X4 payton.
Any idea why this happened?
Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
mkhcb said:
Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
Click to expand...
Click to collapse
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
scott.hart.bti said:
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
Click to expand...
Click to collapse
I came from the OnePlus realm and owned the OPO + OP5T. My parents had the OPO and currently have the 7 Pro. I have been beyond spoiled with TWRP.
Needing a computer to flash and update + keep flash is a pain in the butt... Plus the uninstall Magisk, update, then flash method has never worked for me and 2x I lost all my data + pictures.
mkhcb said:
I came from the OnePlus realm and owned the OPO + OP5T. My parents had the OPO and currently have the 7 Pro. I have been beyond spoiled with TWRP.
Click to expand...
Click to collapse
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
scott.hart.bti said:
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
Click to expand...
Click to collapse
Well if you want to lose the inactive dev title, I 100% will support that . I know many people would appreciate it!
i'd certainly spend my money for a twrp!
I hate adb and hate having to connect my pixel (or any other phone) to a pc for install whatever i want
TWRP was a thing when phones had SD card slots. It still would be nice, however, just not as handy as it were then. ;-)
scott.hart.bti said:
Haha I hear ya. I know there were a few devs over in the OnePlus forums that were fantastic with bringing twrp functionality to those devices. I'm wondering if anyone on the OnePlus 10 is working on it yet. Can't be that much different once someone gets it working and posts the source code (obviously the device source would be different), but beyond that should be similar. I've really been getting the itch to start playing around with things again lately. Need to find a decent rig to setup with Ubuntu before that can happen.
Click to expand...
Click to collapse
I'm coming straight from S5 and can say even with Source Code available it's really hard to see functional updates.
Aroma Installer support was lost for about 5 years. Then an interested developer finally came up and fixed it but didn't want to maintain it, but still it became official ipdate for device tree not unofficial. However the next two updates after it (as far as I know there haven't been more) by an official maintainer skipped all the fixes he did (Aroma Installer support is just the most important). So TWRP for S5 is back to be bugged like for last 5 years and I don't expect it to get fixed ever again.
So no: even if source is available, you can't expect to have good TWRP support.
I'm quite shocked about the S20 development: It's a flagship phone only 2 years old but Stock based development is down to one ROM and one kernel actively maintained, Vanilla Android (based) ROM is not there only LOS based (okay this is Vanilla based in the end, but itself modified and all the ROMs start from this one) and as this one is still not bug free, all depending ROMs are not bug free.
Back in the active days of S5 you had 3-5 Stock ROMs active, AOSP, AOKP and than Cyanogen (based) ROMs available, quite a lot. And Samsung was always hated for their undocumented changes that gave developers quite the headache and reverse engineering was needed a lot. I think GSI should make development easier compared to S5 or has Custom Android development gone down at all?
scott.hart.bti said:
Honestly I don't even remember the days of using twrp anymore as it's been so rare on devices the past couple years. I have to admit I do miss the interface/functionality without relying on a computer. I'd be willing to throw in a few bucks.
Click to expand...
Click to collapse
Huh? My Samsungs and Oneplus had TWRP, it's not rare just not on Pixel
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
But maybe by now, someone has made it for Android 12 in general and I just haven't heard about it, who knows. I used it some on my Pixel 1, but I really haven't missed it.
Edit: There are several TWRP-related threads in this section, and here's some news I shared a month after I got my Pixel 6 Pro:
[General] TWRP 3.6.0 major parts rewritten from scratch to support Google's Android 11 changes, so they are hopeful for a much quicker Android 12 release
So it took them quite a while to get Android 11 support in general.
cpufrost said:
TWRP was a thing when phones had SD card slots. It still would be nice, however, just not as handy as it were then. ;-)
Click to expand...
Click to collapse
Use a USB C to USB A dongle. Works like a charm and also works in TWRP.
TWRP is still being worked on from what I just checked, but they have no ETA when it'll be finished. There's a status page on Zulip with more info, but I'm not signing up for it.
TWRP 3.6.1 Released
TWRP 3.6.1 is out now for most currently supported devices.
twrp.me
mkhcb said:
Use a USB C to USB A dongle. Works like a charm and also works in TWRP.
Click to expand...
Click to collapse
True, I forgot about those. I even have a 128GB tiny Sandisk USB drive that is USB C native that does work so there's that.
roirraW edor ehT said:
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
But maybe by now, someone has made it for Android 12 in general and I just haven't heard about it, who knows. I used it some on my Pixel 1, but I really haven't missed it.
Edit: There are several TWRP-related threads in this section, and here's some news I shared a month after I got my Pixel 6 Pro:
[General] TWRP 3.6.0 major parts rewritten from scratch to support Google's Android 11 changes, so they are hopeful for a much quicker Android 12 release
So it took them quite a while to get Android 11 support in general.
Click to expand...
Click to collapse
yes
namely the fold 3 - however with samsung devices, encryption needs to be disabled for TWRP to work and be able to access the data partition and thus make and store nand backups of userdata etc.
Firstly it transpred that disabling encryption broke a whole range of samsung and google things such as samsung Dex mode and even downloading attachments from gmail.
Then it transpired that data backups were not being sucecssful (although system partition backups were still possible)
In the end it wasn't worth it and the Dev moved over to pixel 6 pro lol
roirraW edor ehT said:
Question: Has any Android 12 device had TWRP made for it yet? Last I had heard, several months back, anyway - none had. Anyone wanting to tackle TWRP for any specific Android 12 device would first have to tackle getting it to work on any Android 12 device in general.
Click to expand...
Click to collapse
It was only officially ported to Android 11 in November 2021, so I doubt there's any official A12 builds yet.
I think reliance on TWRP has dwindled over the past few years due to slow releases, dev's releasing ROM's that are flashable with fastboot, kernels being flashable while online, and most root mods moving towards systemless Magisk modules.
I mainly used TWRP to do an image backup of my phone before doing anything "dangerous". I really hate having to before each monthly update in the hopes something doesn't go wrong that will cause me to have to wipe my phone. With TWRP, I could do an image backup, screw something up, and be back up and running right where I was in a matter of minutes.
Am I missing something here? Is there another way to do a full image backup and restore it quickly? I have Titanium Backup but using that to backup each individual app and it's data, transfer that backup off the phone, then if I have to wipe the phone, I have to copy everything back, then do a restore of each app, will take literally hours!
What's the quickest way to do an image backup if not TWRP?
Thanks,
Dave
Dataman100 said:
Am I missing something here? Is there another way to do a full image backup and restore it quickly?
Click to expand...
Click to collapse
There has "always" (very, very long time) been a way to do image backups manually using ADB, however, it's unreliable - the only reason TWRP or other recoveries were slightly more reliable was that they could "verify" the backup and ensure that what it sees in the partition is indeed what is backed up.
With the ADB commands, you might not find out your backup isn't good until you restore it, and that's no help.
I still found TWRP backups to be hit and miss, at least six years ago when I was still using it.
Dataman100 said:
I have Titanium Backup but using that to backup each individual app and it's data, transfer that backup off the phone, then if I have to wipe the phone, I have to copy everything back, then do a restore of each app, will take literally hours!
Click to expand...
Click to collapse
I switched to Swift Backup and I don't even backup locally as most of my 512 GB of space is filled with music. I have it backup to my Google Drive directly. It's slower to restore stuff from the cloud, but at least they aren't taking up precious space, and I know wiping the phone won't cause me to lose my backups.
FYI, you can set up cloud backups in Titanium Backup as well, or tell it to do that manually. In TB's case, the cloud backups don't replace the local backups, but I have used them before just in case I have to wipe. I've been away from Titanium Backup long enough that I don't recall if TB restores could be done from the cloud, however (unlike Swift Backup, which can restore directly from the cloud). TB's method is probably closer to your manual copy the files back method, so only slightly an improvement as you can schedule the TB cloud backups to happen automatically.
roirraW edor ehT said:
There has "always" (very, very long time) been a way to do image backups manually using ADB, however, it's unreliable - the only reason TWRP or other recoveries were slightly more reliable was that they could "verify" the backup and ensure that what it sees in the partition is indeed what is backed up.
With the ADB commands, you might not find out your backup isn't good until you restore it, and that's no help.
I still found TWRP backups to be hit and miss, at least six years ago when I was still using it.
I switched to Swift Backup and I don't even backup locally as most of my 512 GB of space is filled with music. I have it backup to my Google Drive directly. It's slower to restore stuff from the cloud, but at least they aren't taking up precious space, and I know wiping the phone won't cause me to lose my backups.
FYI, you can set up cloud backups in Titanium Backup as well, or tell it to do that manually. In TB's case, the cloud backups don't replace the local backups, but I have used them before just in case I have to wipe. I've been away from Titanium Backup long enough that I don't recall if TB restores could be done from the cloud, however (unlike Swift Backup, which can restore directly from the cloud). TB's method is probably closer to your manual copy the files back method, so only slightly an improvement as you can schedule the TB cloud backups to happen automatically.
Click to expand...
Click to collapse
Thanks! Yeah, I was aware of all those options. It's still a very manually intensive and time consuming process with either Swift or TB to the cloud.
I came to the P6P from an LG V30s which had TWRP. Right before any major update, (OS, Magisk, etc). I'd do a quick full image backup to the SD card. It took about 20 mins max. Then I'd perform whatever update task, and if it boot looped, or soft bricked, I'd immediately reboot into TWRP and restore. I remember having to do that at least twice on the LG. Each time the backup restored properly and I was up and running again in 20 mins or less. There's no current backup/restore process for the Pixel that even comes close. Titanium even lets you restore individual apps/data from a TWRP backup image. You don't have to restore the entire thing. Which I'd done several times on the LG.
It's a shame. One of the reasons I chose the P6P was because I thought with it's popularity, it wouldn't take long for TWRP to be available. It may not be as valuable or necessary as it was in the past for it's flashing functions, but it certainly would be very useful, (to me anyway) for it's image backup function.
I'd definitely chip in for a TWRP bounty. For the backup alone.
Dataman100 said:
Thanks! Yeah, I was aware of all those options. It's still a very manually intensive and time consuming process with either Swift or TB to the cloud.
Click to expand...
Click to collapse
I have Swift backup to the cloud automatically every night at ~2 AM whenever the battery is at 50% or more. I never have to do anything for that manually. That way, if I'm going to do something dangerous, there's that much less I have to worry about.
I think I used to have Titanium Backup sync to the cloud nightly on a schedule also, besides having it do a scheduled new backup beforehand.
I only actually ever restore select app data - I always start with the Google Cloud restore, and then probably just a few apps that don't use Google Cloud backup, so I manually restore the data for those apps as I come across them in normal use. I never do like I used to do in Titanium Backup and do a restore all.
Dataman100 said:
I came to the P6P from an LG V30s which had TWRP. Right before any major update, (OS, Magisk, etc). I'd do a quick full image backup to the SD card. It took about 20 mins max. Then I'd perform whatever update task, and if it boot looped, or soft bricked, I'd immediately reboot into TWRP and restore. I remember having to do that at least twice on the LG. Each time the backup restored properly and I was up and running again in 20 mins or less. There's no current backup/restore process for the Pixel that even comes close. Titanium even lets you restore individual apps/data from a TWRP backup image. You don't have to restore the entire thing. Which I'd done several times on the LG.
It's a shame. One of the reasons I chose the P6P was because I thought with it's popularity, it wouldn't take long for TWRP to be available. It may not be as valuable or necessary as it was in the past for it's flashing functions, but it certainly would be very useful, (to me anyway) for it's image backup function.
I'd definitely chip in for a TWRP bounty. For the backup alone.
Click to expand...
Click to collapse
Nice. It is definitely good to have options.
mkhcb said:
Wouldn't it be cool to just download the monthly updates and then flash it without a computer and follow that by flashing root instantly? I miss the good ol' TWRP day. We should all pitch in for a TWRP bounty. What do you folks think about that?
Click to expand...
Click to collapse
Yeah if the p6pro gets official lineage os would even be cool to have lineage recovery
Just a thought.