Related
Team Win Recovery Project 2.x, or twrp2 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.
TWRP 3.2.1 Changelog: https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
Installation instructions: Use the official TWRP app (requires root), available here and here. If you already have TWRP installed, you can also download the latest available img and flash it from recovery.
DOWNLOAD (palman): https://dl.twrp.me/palman/
DOWNLOAD (v500): https://dl.twrp.me/v500/
More info: https://twrp.me/devices/lggpad83.html
Warning: builds for v500 require kitkat bootloader. If you are stuck on Lollipop bootloader, check this post.
Device source (palman): https://github.com/TeamWin/android_device_lge_palman
* The kernel in palman source is from 5.1 official build (source found here).
Device source (v500): https://github.com/TeamWin/android_device_lge_v500
* The kernel in v500 source is based on cm-14.1 sources.
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the LG G Pad 8.3
Contributors
fefifofum, Dees_Troy, bigbiff
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2015-06-15
Last Updated 2017-12-10
Thanks very much for this! Great work! That is really nice that there is now official support for awifi/v500.
I assume the images are bumped?
Are the kernel sources for official twrp using your kernel sources?
Sources
This is the device repo for awifi/v500: https://github.com/TeamWin/android_device_lge_v500
The kernel in awifi/v500 repo was compiled from here, which is V50030A based.
This is the device repo for palman/v510: https://github.com/TeamWin/android_device_lge_palman
The kernel in palman/v510 repo is from 5.1 official build.
So, now we should be able to just flash the .img file directly within TWRP to update.
Deltadroid said:
So, now we should be able to just flash the .img file directly within TWRP to update.
Click to expand...
Click to collapse
Yes!
The repo for v510 is going to be renamed since it doesn't need to follow the "cyanogen" way, which is using the model name instead of the device name. That's why there is a little confusion with the names v500/awifi and v510/palman. The GPE repo will be named palman (which is the correct way) and the non GPE repo will stay as v500 (it should be called awifi), since almost every custom rom uses "cyanogen" way. If we wanted the non GPE to be named correctly we would need the devs of every custom rom to add an assert to their boardconfig so both, v500 and awifi, would be valid at installation time. It's just one line change.
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
luisbraz said:
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
Click to expand...
Click to collapse
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
aidfarh said:
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
Click to expand...
Click to collapse
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
fefifofum said:
Why would you need to backup recovery partition?
Click to expand...
Click to collapse
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
fefifofum said:
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
Click to expand...
Click to collapse
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
aidfarh said:
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
Click to expand...
Click to collapse
Old versions will still be available to download, so if a new version had issues you could always download and install an older version. No need to backup recovery I guess...
luisbraz said:
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
Click to expand...
Click to collapse
We don't need loki anymore, you just need to be on kitkat bootloader.
luisbraz said:
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
Click to expand...
Click to collapse
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
fefifofum said:
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
Click to expand...
Click to collapse
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
luisbraz said:
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
Click to expand...
Click to collapse
Glad to hear that! It seems the app TWRP manager cannot reach the new servers where official builds of TWRP are, so it's better not to use the app installation method to avoid installing old versions.
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
bokoy said:
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
Click to expand...
Click to collapse
I guess V50010B bootloader is what you need, but then you will probably have brightness issues while using this recovery.
New version
TWRP 2.8.7.0 released.
fefifofum said:
TWRP 2.8.7.0 released.
Click to expand...
Click to collapse
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
D4xel said:
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Click to expand...
Click to collapse
This one is official (without the quotes), doesn't require loki and is adapted to kitkat bootloader backlight. The other one you mention is adapted to jellybean bootloader backlight and requires loki. Just install the one that fits your needs.
cianz94 said:
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
Click to expand...
Click to collapse
You have the install instructions on the first post. You can also download the image and flash it with THIS APP.
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.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
Direct device link
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP for Shield Portable, Tool/Utility for the Nvidia Shield
Contributors
Steel01
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Created 2016-06-01
Last Updated 2016-05-31
Well, I finally bit the bullet and took official maintainership of the Shield devices for TWRP. So, here's the pure upstream release. It's sideways due to lack of rotation support, but it should have every feature any other TWRP supported device does. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
Steel01 said:
Well, I finally bit the bullet and took official maintainership of the Shield devices for TWRP. So, here's the pure upstream release. It's sideways due to lack of rotation support, but it should have every feature any other TWRP supported device does. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
Click to expand...
Click to collapse
I'm pretty sure there's a sideways TWRP theme. I recall using it to get it to display properly on molly (Google's ADT-1 Developer Kit).
Have you tried setting the TWRP theme like this? :
Code:
TW_THEME := landscape_hdpi
r3pwn said:
I'm pretty sure there's a sideways TWRP theme. I recall using it to get it to display properly on molly (Google's ADT-1 Developer Kit).
Have you tried setting the TWRP theme like this? :
Code:
TW_THEME := landscape_hdpi
Click to expand...
Click to collapse
Yeah, the only thing that changes is the aspect ratio, not the orientation.
Thank you! Thank you!
Just updated to 110, and installed TWRP you posted. All went perfect.
Just FYI, sometimes when I flash a new TWRP recovery, it doesn't take the first time, so I just flash it a few times, then test to see if it took, if it didn't take, I flash a few times more until it finally flashes.
Is there a specific key combo you can use to go right into recovery? Right now, I boot into the bootloader by pressing and holding the back, home and nvidia buttons till it boots into the bootloader, then I select recovery to go into TWRP. Just wanted to know if there's was a key combo to go directly into recovery.
Thanks again for providing and posting the latest TWRP for the Portable!!
Hello, quick question. I have a previous version of TWRP installed and want to update to the new one.
Is it possible to apply the OTA to 110 with this TWRP or do I need the stock bootloader?
If I need the stock one, does anyone have a link to it? I didn't make a backup, unfortunately
No need to apply the ota, download the recovery image from Nvidia and fastboot flash blob, boot, and system. You'll lose any modifications to system (such as root) as expected, but that's easy enough to restore.
https://developer.nvidia.com/shield-open-source
But there's no real reason not to update twrp. The older multirom based version has screen rotation, but that's no big deal. And the newer updates have current selinux policies, so they'll be much less likely to cause issues with newer android versions (for those using CM13 and hopefully 14 sometime soon).
Steel01 said:
No need to apply the ota, download the recovery image from Nvidia and fastboot flash blob, boot, and system. You'll lose any modifications to system (such as root) as expected, but that's easy enough to restore.
https://developer.nvidia.com/shield-open-source
But there's no real reason not to update twrp. The older multirom based version has screen rotation, but that's no big deal. And the newer updates have current selinux policies, so they'll be much less likely to cause issues with newer android versions (for those using CM13 and hopefully 14 sometime soon).
Click to expand...
Click to collapse
Ah, I didn't know nvidia published those files like that. That's actually really great!
I'm all up to date now, including the latest TWRP
Hmm I tried TWRP 3.1 from the TWRP website and the touch interface doesn't work. Also, 3.0.2 seems to have problems mounting and wiping data?
Meh, okay. I saw a similar touch problem on a local twrp build. I've requested that the build be removed from the official site. I'll look into the problem when I have time.
Haven't had any trouble on 3.0.2 myself. Did you enable encryption or adopted storage in your ROM?
Great, thanks!
I didn't enable encryption, and it was the latest stock rom. I'm not really sure what happened. It just seemed to be having trouble mounting and wiping a few partitions on the stock system rom, so I flashed the 3.0.0.0 TWRP from the multirom. I seem to recall that having issues wiping too though. However, now that I've flashed LineageOS onto the system partition, I don't get any errors with 3.0.0.0 anymore. I haven't updated to 3.0.2.0 to see if the errors are gone in that build (nor do I want to wipe anything at this point).
As I wrote in the LineageOS thread, I had the same problem with touchscreen. I was hoping to solve the non working touchscreen problem during Aroma OpenGapps install.. is there any hope it gets solved? I think it would be very useful to be able to choose exactly what to install on the Shield, considering its little system partition.
Hmm, seems 3.1.0.0 and 3.1.1.0 don't work on the Shield Portable. After the first start no touch gesture is recognized. If you connect a USB mouse you can get past this...
But after a new start to the recovery everything you select results in "wipe factory settings" - which I assume you won't
PS: Landscape would be nice.
astuermer said:
Hmm, seems 3.1.0.0 and 3.1.1.0 don't work on the Shield Portable. After the first start no touch gesture is recognized. If you connect a USB mouse you can get past this...
But after a new start to the recovery everything you select results in "wipe factory settings" - which I assume you won't
PS: Landscape would be nice.
Click to expand...
Click to collapse
I too have this issue. Seems they messed up screen as portrait mode.
I see the problem with touch on the newer builds. Would have sworn I had at least one of those removed due to issue, but it apparently came back. Looking into updating all the internal files for 7.1. Working on testing and fixing that right now. The problem is that the touch screen userspace is trying to start before selinux is set to permissive by twrp. So, I have to make sure everything is labelled correctly and that's causing issues. If I'm lucky, I'll be uploading a test build later today. But as with all this type of work, I can't 100% guarantee anything.
astuermer said:
Landscape would be nice.
Click to expand...
Click to collapse
The rotation code no longer exists, it was deemed too slow and hacky. I have to set it up in portrait or not at all, unfortunately.
Edit:
So, not having much luck with making it play nice on default settings. Here's a build with selinux explicitly disabled and touch works as expected. As I have time, I will continue to work on this and get it upstreamed. For the moment, use this 3.1.1 build.
twrp-3.1.1-0-unofficial-roth.img
Finally got around to pushing updates to official twrp. So if you've had issues in the past, please try again. Should be easier to test and fix stuff now that I've got all that pushed.
Side Note: This is fully a 7.1.1 recovery and build. Blasted recovery from N works better than the roms themselves...
Some updates have been pushed for this. 3.2.1.0 has been release as of a few hours ago. If any issues are found, please report.
When trying to flash the 2018-02-11 LineageOS nightly with 3.2.1.0, I get the following error;
Code:
Updating partition details...
...done
Full SELinux support is present.
Installing zip file '/sdcard/lineage-13.0-20180211-nightly-roth-signed.zip'
Checking for digest file...
Skipping Digest check: no Digest file found
Verifying zip signature...
Zip signature verified successfully,
[B]This package is for device: roth; this device is .[/B]
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-13.0-20180211-nightly-roth-signed.zip'
Updating partition details...
...done
The flash does not proceed beyond this point - apparently can't identify the device type (see bolded text above). If I repeat the process using version 3.1.1-2 or version 3.0.2.0 it works fine, though.
Let me know if you'd like me to pull any logs etc
Update: A working solution is listed below for reference.
A detailed tutorial for encrypted and rooted Nougat OOS users on how to flash Oreo OxygenOS without running into the infamous boot loop issue.
Step 1: Remove all fingerprint & pin from the device
Step 2: Backup everything on your PC/Laptop
Step 3: Reboot the device to TWRP bootloader
Step 4: Using a PC/Laptop, flash Blu_Spark TWRP via ADB command
Step 5: Reboot device to TWRP
Step 6: Wipe dalvik, cache, system & internal partition
Step 7: Format device
Step 8: Copy Oreo Rom & no_verity_mod file onto your device
Step 9: Flash Oreo under TWRP
Step 10: Flash TWRP again
Step 11: Reboot to recovery again
Step 12: Flash Magisk Beta for root (I used Magisk beta 14.5)
Step 13: Flash no_verity_mod file
Step 14: Reboot into Oreo Oxygen OS
Your device is now decrypted, rooted and running the latest stable Oreo OxygenOS build.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Seeing as a couple of forum members have messaged me regarding the official update of Android Oreo, I would like to make a proper discussion thread for it.
I just want to make it clear that HatRiGt has made an outstanding effort by making a tutorial thread. -> ([OFFICIAL] [Stable Oreo 8 ] Oxygen OS 5.0 Update [Tutorial-Root] [Mirror] by HatRiGt)
With that said, I believe the title is somewhat misleading. Since a lot of members are under the impression that this Oreo update will be a simple and straightforward process like all previous Nougat updates, except for it's not.
Stock OxygenOS
Rooted with Magisk v14
TWRP Recovery
Device already encrypted
Almost everyone with the device configuration listed above has run into some sort of serious issues, such as boot loop, file system decrypted/corrupted, or a complete data loss.
So far, it seems like the few groups of members that have managed to update their device without any data loss are either users that have flashed the Oreo Beta rom, or users with a non-rooted & stock recovery device. Almost everyone else is facing some form of issues.
I understand that some people have suggested that rooted users should first format the internal storage, before proceeding with the Oreo update. I personally feel that it is an inconvenient method of OS update, since many of us have a huge collection of photos, media files and app settings etc... to worry about.
The purpose of this thread is to address the aforementioned problem for rooted OOS users and to come up with a solution, so that everyone can enjoy this latest stable release of Android Oreo.
Any comments or thoughts are welcomed.
Maybe a stupid idea, but I am a bit noobish in this. Running stock 4.5.15, rooted, K2 TWRP and Magisk.
Is it not an option to just flash stock recovery (via ADB or Root Toolcase), then remove/deinstall Magisk and use the OTA update? After that flash Blue Spark via ADB, reflash Magisk and be good to go?
Unfortunately this is my daily driver company phone so I haven't the time to experiment with it at the moment.
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Malcol13 said:
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Click to expand...
Click to collapse
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
DionysosD said:
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
Click to expand...
Click to collapse
I saw the same thing. Unable to copy the zip file until I did the full wipe, which means no chance of recovering what was on it, but I'm cutting my losses.
I'm now stuck on the configuration stage, it's just sitting on "Just a sec..." for forever it would seem. Trying to update on Christmas day was a bad decision.
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
fards said:
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I had the same idea, encrypted, rooted (no system modifications) and running twrp, I flashed stock OP5 recovery, and updated through the ota and ended up in a bootloop.
I did a nandroid to a usb before updating, but I still lost all internal storage files
so...the no verity is only for decrypted users right?
fards said:
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
igoorsoouza said:
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
Click to expand...
Click to collapse
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Are you sure flashing Open beta2 won't compromise the internal storage? I bet no one affords to loose previous photos, apps, settings, etc without full backup.
I've triyed this. All good till i flash 5.0 & Magisk & no verity....
Hello there and Merry Christmas.
I faced to this issue too, fortunately before to update to Oreo. I made a full backup of my data.
My OP5 was running under Oxygen OS 4.5.15 Nougat 7.1.1
Rooted with Magisk V14.5
TWRP Blue_Spark 3.1.1
First I have updated my TWRP to Blue_Spark 3.2
And then I've installed Oreo Oxygen OS 5.0 from TWRP with the full zip.
After the update, my op5 has been bricked and locked on blank black screen with a blue led.
To unbrick my phone I used a tiers softwate to install Hydrogen OS first.
After that I could installed TWRP Blue_Spark 3.2 and then flash to the full zip Oreo Oxygen OS 5.0
My OP5 works as well but...
Right now I'm blocked, Google who usually sends an SMS, does not offer me. Only the authentificatorator or the security code. : /
Be careful, print a Google code to access your account when you go to install Oreo.
I'm waiting for Google to do the right thing.
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
1) What is that "no-verity" file?
2) Isn't the regular TWRP 3.2.0 good with Oreo?
MadCow809 said:
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Click to expand...
Click to collapse
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
BenSow said:
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
Click to expand...
Click to collapse
I think it's possible to flash the Oreo Beta without a full wipe. And yeah, I've got way too much stuff on my device, so I can't afford to wipe my storage.
MadCow809 said:
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
Click to expand...
Click to collapse
I never suggested either.
Oneplus don't test using twrp or using root.
Their prescribed ota route, as pretty much every other OEM, is unmodified system partition using stock bootloader.
Twrp or root will affect those and can cause bootloops.
Obviously there's a chance with so much diversity in installs that there can be an issue arises.
raboliot said:
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515
Read it all.
I have a Encrypted phone and I was able to recover all.
Actually I was able to restore my Nandroid backup.
I was running Sultan's latest version of CM which was discontinued somtime last year. So, I decided I should upgrade to the latest Sultan Lineage OS version. I updated TWRP to the most current version, took a Backup of the system using the new TWRP (so I could restore back to a working phone). I also downloaded the Sultan version of Lineage OS (and this is where my mistakes began). I accidentally downloaded the incorrect version for the OnePlus 1 and not for the OnePlus 3T. I should have done this from a computer and not from the browser on my phone to prevent this mistake.
So, in TWRP, I cleared cached and the system partition, then tried to install the Sultan Lineage OS. TWRP correctly told me that it was the wrong version for my phone. Okay, no problem. Then, my fallback also failed. I tried to restore the image that I had backed up of my working phone and the image loads properly. However, when the phone is rebooted, it is stuck in a bootloop. I can get into TWRP and the bootloader, but that's all I can do.
What are my options now?
(1) Can I use adb fastboot to copy over the correct version of Sultan's Lineage and go to that?
(2) Why is my recovery image not working?
I essentially have a phone that seems to be bricked. I hope that this is not the case. Any help is greatly appreciated.
weaponG said:
I was running Sultan's latest version of CM which was discontinued somtime last year. So, I decided I should upgrade to the latest Sultan Lineage OS version. I updated TWRP to the most current version, took a Backup of the system using the new TWRP (so I could restore back to a working phone). I also downloaded the Sultan version of Lineage OS (and this is where my mistakes began). I accidentally downloaded the incorrect version for the OnePlus 1 and not for the OnePlus 3T. I should have done this from a computer and not from the browser on my phone to prevent this mistake.
So, in TWRP, I cleared cached and the system partition, then tried to install the Sultan Lineage OS. TWRP correctly told me that it was the wrong version for my phone. Okay, no problem. Then, my fallback also failed. I tried to restore the image that I had backed up of my working phone and the image loads properly. However, when the phone is rebooted, it is stuck in a bootloop. I can get into TWRP and the bootloader, but that's all I can do.
What are my options now?
(1) Can I use adb fastboot to copy over the correct version of Sultan's Lineage and go to that?
(2) Why is my recovery image not working?
I essentially have a phone that seems to be bricked. I hope that this is not the case. Any help is greatly appreciated.
Click to expand...
Click to collapse
1. You can either sideload the correct version in TWRP and ADB. Or fopy the file to your internal storage using TWRP and ADB or by enabling MTP in TWRP (under Mount menu) and then flash it. Don't forget to do a factory reset in TWRP as you're changing ROMs.
2. What partitions were included in your backup?
If boot, data, and system were included then I have no idea why restoring it didn't work.
And, when you say "most current version of TWRP" do you mean version 3.2.1-0 from https://dl.twrp.me/oneplus3/ or something else?
Sent from my OnePlus3T using XDA Labs
BillGoss said:
1. You can either sideload the correct version in TWRP and ADB. Or fopy the file to your internal storage using TWRP and ADB or by enabling MTP in TWRP (under Mount menu) and then flash it. Don't forget to do a factory reset in TWRP as you're changing ROMs.
2. What partitions were included in your backup?
If boot, data, and system were included then I have no idea why restoring it didn't work.
And, when you say "most current version of TWRP" do you mean version 3.2.1-0 from https://dl.twrp.me/oneplus3/ or something else?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
(1) I was successfully able to download the proper Sultan Lineage OS version for OnePlus 3T. I have copied that and the latest firmware sited in this link:
https://forum.xda-developers.com/on...t/op3-op3t-unofficial-lineageos-14-1-t3588696
(2) The following partitions were included: Boot, Data (excl. storage), Recovery, System, System Image, EFS. It is unknown as to why recovery failed.
(3) The version is Team Win Recovery Project (TWRP) 3.2.1-0
weaponG said:
(1) I was successfully able to download the proper Sultan Lineage OS version for OnePlus 3T. I have copied that and the latest firmware sited in this link:
https://forum.xda-developers.com/on...t/op3-op3t-unofficial-lineageos-14-1-t3588696
(2) The following partitions were included: Boot, Data (excl. storage), Recovery, System, System Image, EFS. It is unknown as to why recovery failed.
(3) The version is Team Win Recovery Project (TWRP) 3.2.1-0
Click to expand...
Click to collapse
Oh wow. I had to apply the Firmware Update, and now I am running Sultan's Lineage. This is truly exciting. The animated splash/intro screen is still occurring on the phone. This should be great. Thanks so much for your kind assistance.
Unofficial Lineages OS for Razr HD (xt926_jbbl)
This is only for JBBL do NOT try on KKBL
I am not responsible for bricked devices, loss of data, dead SD cards,
* loss of hair, 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, everyone will laugh at
* you and I will deny any wrong doing or responsibility.
Procedure
NB: You must format your Data and Cache partitions as F2FS
Download the latest PICO or NANO GApps from OpenGapps
Backup your internal SD Card, off of the device eg USD or Hard Disk
Boot to TWRP
Make a nandroid backup, and ensure this backup is not on the device itself
Format your data partition and cache partition to F2FS (do NOT post for instructions on how
to do this on this thread!)
Wipe Cache , System & Dalvik-Cache
Flash the ROM Zip
Flash Gapps ARM -> 7.1
Wipe cache and dalvic
Done - Reboot to [System]
Wait...
lineage-14.1-20200214-UNOFFICIAL-xt926_jbbl
Security patch level Feb 05, 2020
Changelog https://www.lineageoslog.com/14.1
Download rom and recovery here: https://www.androidfilehost.com/?w=files&flid=304892
Known issues:
You tell me
XDA:DevDB Information
Unofficial Lineage 14.1 XT926_JBBL, ROM for the Motorola Droid RAZR HD
Contributors
Wheels564
Source Code: https://github.com/wheels564
Thanks go out to the Lineage team for maintaining Nougat roms
Also thanks to Metalor for his source work which this rom is based on
And DiamondJohn for his tutorial on building TWRP from source
ROM OS Version: 7.x Nougat
ROM Firmware Required: JBBL
Based On: Lineage
Version Information
Status: Nightly
Created 2020-02-18
Last Updated 2020-02-18
Reserved
Reserved again
Wow, twrp 3.1.1, impressive. I really didn't think that we could get it up that high. Good work! And feel free to try a higher twrp version (minimal manifest 8.1 does give you twrp 3.3.1 )
Btw, decompiled your recovery. Not sure where you have your twrp flags, but whatever board config file they are in, add in TW_EXCLUDE_SUPERSU := true , as magisk is the replacement to supersu
palmbeach05 said:
Wow, twrp 3.1.1, impressive. I really didn't think that we could get it up that high. Good work! And feel free to try a higher twrp version (minimal manifest 8.1 does give you twrp 3.3.1 )
Btw, decompiled your recovery. Not sure where you have your twrp flags, but whatever board config file they are in, add in TW_EXCLUDE_SUPERSU := true , as magisk is the replacement to supersu
Click to expand...
Click to collapse
Minimal manifest from Lineage only goes to nougat. The rest of twrp is on Omni. I have to rebrand everything to Omni and there are other changes that need to be made for it to build. It's gonna take some time and I don't have a lot of it right now. BTW I have twrp working on mb886 but you have to use a mouse. I got lineage 13 to install on it but am having trouble with 14.1.
palmbeach05 said:
Wow, twrp 3.1.1, impressive. I really didn't think that we could get it up that high. Good work! And feel free to try a higher twrp version (minimal manifest 8.1 does give you twrp 3.3.1 )
Btw, decompiled your recovery. Not sure where you have your twrp flags, but whatever board config file they are in, add in TW_EXCLUDE_SUPERSU := true , as magisk is the replacement to supersu
Click to expand...
Click to collapse
Just compiled a new recovery. Check and see if thats what you want. My main computer is compiling a rom right now.
Sorry for a novice question. Can I install the TWRP image in my xt907 TWRP on my xt926.
yoshkapundrick said:
Sorry for a novice question. Can I install the TWRP image in my xt907 TWRP on my xt926.
Click to expand...
Click to collapse
If you have JBBL you can use the TWRP from the link to androidfilehost. It's specifically made for the xt926 but only if you have jelly bean boot loader and not Kit Kat boot loader.
Wheels564 said:
If you have JBBL you can use the TWRP from the link to androidfilehost. It's specifically made for the xt926 but only if you have jelly bean boot loader and not Kit Kat boot loader.
Click to expand...
Click to collapse
I have a jbbl. But can I directly install the image file while in the TWRP that I currently have which is the jbbl for the 907 version 3.1.1 or do I have to side load it again. Sorry for the basic questions i am a novice.
Wheels564 said:
Just compiled a new recovery. Check and see if thats what you want. My main computer is compiling a rom right now.
Click to expand...
Click to collapse
I don't have the ahd available right now, its in a box somewhere, but i will test as soon as i can. I can still look at it by decompiling the img though.
If you grab up omni's android_bootable_recovery and replace it with what you have in your local directory, it should work. For fun, i've taken out my old droid x and did a swap like that and it worked. Like i said, just passing along some ideas/advice.
yoshkapundrick said:
I have a jbbl. But can I directly install the image file while in the TWRP that I currently have which is the jbbl for the 907 version 3.1.1 or do I have to side load it again. Sorry for the basic questions i am a novice.
Click to expand...
Click to collapse
Unless you change recovery to the xt926_jbbl version you will get error 7. Recovery is looking for the assert line in the rom zip file which prevents people from flashing the wrong rom. There's plenty of threads here that guide you how to flash recovery. Once you flash recovery and rom your phone will show as Razr HD and screen resolution will be correct. Also HDMI out will work.
Using minimal ADB and Fastboot
Make sure recovery image is in adb and fastboot folder
1. Rename twrp image to recovery.img
2. "Adb reboot bootloader"
3. "fastboot flash recovery recovery.img
4. "fastboot reboot"
Leave out quotes
yoshkapundrick said:
I have a jbbl. But can I directly install the image file while in the TWRP that I currently have which is the jbbl for the 907 version 3.1.1 or do I have to side load it again. Sorry for the basic questions i am a novice.
Click to expand...
Click to collapse
OMG OMG can you say TWRP 3.3.1-0 for the xt926_jbbl and xt907_jbbl? You were right!! New life for these old devices? I made one to test on the xt907. I did a backup and all seems well. I'll try the version for the xt926 when i get off work and post it on androidfilehost. Kudos
Wheels564 said:
OMG OMG can you say TWRP 3.3.1-0 for the xt926_jbbl and xt907_jbbl? You were right!! New life for these old devices? I made one to test on the xt907. I did a backup and all seems well. I'll try the version for the xt926 when i get off work and post it on androidfilehost. Kudos
Click to expand...
Click to collapse
Would a comparison to Lazarus be inappropriate on XDA LOL ?
twrp3.3.1.0 xt926_jbbl
Recovery "twrp3.3.1.0 xt926_jbbl wheels564" is up on androidfilehost.
Recovery here: https://www.androidfilehost.com/?fid=4349826312261727895
Flashed the TWRP image directly over my JBBL for xt907 version 3.1.1 with no problems. Then flashed rom and similarly no problems.
---------- Post added at 11:37 PM ---------- Previous post was at 10:38 PM ----------
Minor point, camera a no go using open camera and other camera apps.
yoshkapundrick said:
Flashed the TWRP image directly over my JBBL for xt907 version 3.1.1 with no problems. Then flashed rom and similarly no problems.
---------- Post added at 11:37 PM ---------- Previous post was at 10:38 PM ----------
Minor point, camera a no go using open camera and other camera apps.
Click to expand...
Click to collapse
Your right, I'll have to find out where it went. It's still on the Feb 06 version (Jan 5 security patch date)
I must say that your rom is very nimble like DiamondJohn's roms. It is a very big deal when you are dealing with 1GB of ram.
I have other old devices (like a Motorola Xoom) with custom roms that are problematic with 1GB of ram.
Thank you very much
New build up
lineage-14.1-20200222-UNOFFICIAL-xt926_jbbl
Link: https://www.androidfilehost.com/?fid=4349826312261729680
Changelog:
Added missing camera wrapper
Clean flash only, dirty flash will not restore missing camera app.
If you use Open Camera a dirty flash does restore it's functionality.
New build up
lineage-14.1-20200226-UNOFFICIAL-xt926_jbbl
Changelog:
NFC fixes
Link: https://www.androidfilehost.com/?fid=4349826312261732779