Related
Q&A for [EXP][DEV] Lollipop for Xperia Z
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [EXP][DEV] Lollipop for Xperia Z. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Good start
Had no problems installing via fastboot. Very nice and smooth, but needs some google play sevice files, so to test properly. Unable to call out - APN settings look okay, but signal icon on status bar has exclamation mark (?). SOme sort of recovery would be invaluable.
My Q&A: not definitive, but hopefully this will ease question duplication
I've decided to update this post to be an informal Q&A-link-list in the desperate hope that people will come across it before asking the same questions again and again. Look here to see if your question has already been answered. If you think something needs to be added to this post, then post it in thread.
INFO CURRENT AS OF ~1AM UTC 13 Nov 2014.
There are two versions of the Xperia Z Lollipop rom: one by thomas, and one by pabx. Installation instructions differ in places between the two, as do the prerequisites. I will list note when they are different.
How do I install?
Prerequisites:
An unlocked bootloader. If not unlocked, see 'Bootloader unlocking' below
The fastboot and adb command line tools. For more on them, see 'Adb and Fastboot' below
Additional prerequisites for thomas's version if you want gapps or SuperSU:
A kernel including a recovery: I suggest HodorKernel
The SuperSU update package
A Gapps package (such as these ones suggested a while back by @_infected). If you find these gapps don't work for you, but find others that do, then post in the thread so this can be updated.
If you have the prerequisites, then you can continue. Note that installation will wipe your phone completely, including the internal SD.
PABX's version: downloads and installation instructions can be found here.
Thomas's version: see this post.
Regarding Root
Pabx's build doesn't support root. If you need root, use Thomas's build.
Regarding recovery
Thomas's build doesn't include a recovery. Pabx's includes CWM recovery.
If you need a recovery on thomas's, you'll need to temporarily flash a boot image which includes a recovery. That would be the HodorKernel I suggested earlier.
To temporarily add a recovery to Thomas's build, take the following steps:
Enter fastboot by unplugging the USB, powering the device off, and holding the up volume button when plugging in a USB cable connected to your PC. The light on your phone will turn red, then blue. When it is blue, your phone is in fastboot mode.
On your PC, extract the HodorKernel zip file, and locate the boot.img
Flash the boot.img using the following command: fastboot flash boot boot.img
Unplug the USB cable
Press the power button
When the indicator light on your phone turns on, press the volume-down button repeatedly. You will eventually enter recovery. For some reason, you may need to touch the screen (rather than the power button) to actually turn the screen on once the recovery has loaded
Do what you need to do with the recovery (e.g. flash, etc)
Power off the device (I believe the option is in the 'reboot' menu)
Go back into fastboot (i.e. hold up volume, plug in, etc)
Flash the original boot.img from thomas's rom
Unplug USB
Boot
Bootloader unlocking
Unlocking your bootloader allows you to install unofficial ROMs on your Xperia Z. See here for how to unlock. Read the warnings.
this adb tutorial and this guide to fastboot. You can download these tools for Mac here and Windows here. If you're having problems with Windows, particularly Windows 8, look here.
If the links don't work, go find links that do and post them here. I can then update these links.
This isn't the fastboot or adb Q&A thread. If you don't understand how to use fastboot and adb, this isn't the place to ask. XDA is scattered with more guides than I can point a pointy thing at for fastboot and adb.
Post-original post:
EDIT: Don't use the GApps I've mentioned. They kind of work, but are pretty flakey for the XZ.
EDIT 2: PABX has posted a new build, but more importantly also some GAPPS. (http://www.blinkenlights.ch/ccms/android/yuga-l.html)
However, the GAPPS are a .tgz which means (I think) they can't be flashed using recovery. Thus, you'll more or less need to follow the procedure in this post.
NOTE: you only need to flash them using the procedure below if you are not using PABX's build. If you are, then you just need to follow the installation instructions on his page.
An alternative set of gapps linked by _infected is https://www.androidfilehost.com/?w=files&flid=20902
(_infected's post is http://forum.xda-developers.com/showpost.php?p=56623436&postcount=314)
Original post:
I've used the GApps from here: http://forum.xda-developers.com/google-nexus-5/orig-development/illusionrom-lollipop-lrx21m-t2929192
Because there is no recovery (that I know of) you have to manually copy them on using ADB, but once they are on you can create an account, access the play store, and thus install the other Google apps.
(I have barely tested them, though)
To install thees Gapps, I did the following (in brackets is description, don't enter it. Number is sequence of events, don't enter it.
1. adb shell (open a shell)
2. su (become root user)
3. mount -o rw,remount /system (make the /system file system writeable)
4. mkdir /tmp/gapps (make a directory to put the gapps in temporarily without losing the file system privileges on them)
5. chmod 777 /tmp/gapps (make the /tmp/gapps folder writeable to all)
6. exit (leave su)
7. exit (leave adb shell)
8. Unzip the file downloaded from the link above
9. adb push /system /tmp/gapps (push the gapps /system folder to the temp directory we created)
10. adb shell (back to the shell on the phone)
11. su (root again)
12. chown -R root.root /tmp/gapps (change ownership of all the gapps file to root)
13. cp -r /tmp/gapps/* /system/. (copy the gapps files into the /system partition file system)
14. exit (leave su)
15. exit (leave adb shell)
16. adb reboot (reboot device)
17. ???
18. Profit!!!
I'm not certain all these steps are necessary, and I'm writing them from memory not as I do them but I am pretty sure they are correct.
---------- Post added at 05:52 AM ---------- Previous post was at 05:26 AM ----------
By the way, GPS seems to work fine. Getting a good lock (4m accuracy) outdoors.
cant install gapps
i cant boot into my recovery to install gapps
is the adb way supposed to work in fastboot mode? since it says device not found
please help me get my gapps installed
Thanks in advance
xixhxix said:
i cant boot into my recovery to install gapps
is the adb way supposed to work in fastboot mode? since it says device not found
please help me get my gapps installed
Thanks in advance
Click to expand...
Click to collapse
EDIT: look at Post 3 (http://forum.xda-developers.com/showpost.php?p=56536436&postcount=3) for a link to PABX's most recent gapps and a (rough) procedure to install them. If you are using Thomas's builds, read on.
If you're trying to flash a zip-based set of GAPPS, then follow the instructions below *but using your own GAPPS package, not the one I've linked). If you *want* to flash a zip-based set of GAPPS but don't have them, then you can grab them from this post by _infected: http://forum.xda-developers.com/showpost.php?p=56623436&postcount=314.
Original post:
Hi,
The ADB way you do in normal mode (i.e. when the phone is running), not in fastboot mode, but there is a better way (which I will describe below).
I am now using these GAPPS and they seem to be working well.
http://forum.xda-developers.com/goo.../gapps-google-apps-flashable-package-t2930260
The better way to install the GAPPS (compared to my ADB method above)
1. Install the rom (using fastboot) and start it up once.
2. Shut down and go back into fastboot mode
3. Download HodorKernel (http://forum.xda-developers.com/xperia-z/orig-development/kernel-hodorkernel-t2865648)
4. Extract the HodorKernel ZIP, and flash the boot.img (fastboot flash boot boot.img)
5. Reboot and go into recovery (pressing down on the volume while booting)
6. Sideload the Gapps linked above
7. Power off (in TWRP, 'reboot'/'power off')
8. Go back into fastboot mode
9. Reflash the lollipop boot.img (fastboot flash boot boot.img)
10. Reboot
12. Do a happy dance
Note: other kernels may well work; I just used Hodor because I had it lying around.
Note 2: #9 is not an optional step. You *must* reflash the original boot.img or your rom will not work.
how did you guys managed to install gapps?
Pablosch23 said:
how did you guys managed to install gapps?
Click to expand...
Click to collapse
easy pizzy
download doom kernel
fastboot via adb
boot recovery
flash zip
go to advance
turn off phone
fast boot 5.0 boot
done
No
chauhanjayc said:
hi all
its been almost 12 hrs last night near 10:00 PM i had CM12 installed and here are my results .
00000000 LAGS(GOD FATHER OF PROJECT BUTTER)
1.5 Free RAM all the time :laughrunning all the gapps like gmail, map, location, google now, hangout, sync, and other...)
no huge battery drops(testing on going)
crystal clear sound in calls
NOOOOOOOOOOOOO HEATINGGGG:victory:
super fast installation of any apps
and much much much moreeeeeeeeee:victory:
check this out
Click to expand...
Click to collapse
How did u fix calling bug bro
Nd is audio bug fixed
iKillCypher said:
@pabx and @thomas1991_12
what blobs are you guys using cause sony seems to have their own blobs for AOSP (strange)
http://forum.xda-developers.com/showpost.php?p=56540160&postcount=25
Click to expand...
Click to collapse
I'm using the 283 blobs: https://github.com/adrian-bl-yuga/yuga-blobs-a806
vpn client on android L
Hey there, I live in a country where most of the websites are filtered by the government and it seems like I cant get any of the vpn clients apps to be working on this Android L build such as the "hotspot shield" or "psiphon", I hardly logged in to my google account and cant get my contacts to be synced. Any supposed solutions?
so no one is going to help me!!????
Thanks
I followed your guide and it worked perfectly for me. Though I used a different boot.img with recovery.
I guess older boot.img with custom recoveries should all work then.A BIG THANKS
---------- Post added at 02:51 PM ---------- Previous post was at 02:46 PM ----------
xixhxix said:
so no one is going to help me!!????
Click to expand...
Click to collapse
Great contributors are there to help in every step of the way.Big ups to pabx,R:goodejeev and the others
xixhxix said:
so no one is going to help me!!????
Click to expand...
Click to collapse
What do you want, magic? Right now the device can't transmit mobile data: I am not sure that VPN clients not working is going to stack up as top priority.
First, you need to be more clear about what you tried. What specific clients did you try? Did you try Cyberghost? Did you try ProXPN? Did you try using a generic OpenVPN client as well as VPN-specific apps?
Re: Google contact syncing: it isn't clear whether you're saying that it isn't syncing because the VPN isn't working, or it isn't syncing at all. Be specific.
If you want a fully functional phone right now, don't use Lollipop builds. If you want to use Lollipop, then accept that some things will be broken and either work out how to fix them and tell others, or report the issue and live with the fact that it takes time for people to test and respond.
thanks anyway
vo4LG said:
What do you want, magic? Right now the device can't transmit mobile data: I am not sure that VPN clients not working is going to stack up as top priority.
First, you need to be more clear about what you tried. What specific clients did you try? Did you try Cyberghost? Did you try ProXPN? Did you try using a generic OpenVPN client as well as VPN-specific apps?
Re: Google contact syncing: it isn't clear whether you're saying that it isn't syncing because the VPN isn't working, or it isn't syncing at all. Be specific.
If you want a fully functional phone right now, don't use Lollipop builds. If you want to use Lollipop, then accept that some things will be broken and either work out how to fix them and tell others, or report the issue and live with the fact that it takes time for people to test and respond.
Click to expand...
Click to collapse
I dont think I asked for such an answer, thanks for your attitude but any way I'll answer your questions so that maybe somebody could help me
First you could say I've already tried every possible way of a proxy
second, according to google contacts syncing its because that server is already blocked here so you cant sync those except if you got a working vpn (although I found a way to get them, but not with the normal sync way)
actually the main purpose of my post was reporting that this vpn stuff isn't working so that they even try fixing it
Is there a flashable zip or something for this?
Or something to flash this without wiping internal sdcard?
Help!!
I have already install this rom and working for one day .
it is awesome .
but today battery less then 2% and i plug the power quickly and the red led light for 1hour and cannot power on or even reboot the devices when the power didn't plug .
i try to use adb/fastboot to reboot the devices but nothing happen the red light still light and no display
how can i fix it?
.zip compile?
Why there aren't a .zip file (easier to flash for me) of this rom?
Sorry for my bad english.
How can I install Gapps?
How can I flash Gapps? I can't reboot in recovery.
gapps
Pleaseeeeee
Anyone give me a link of working gapps.
leonso26 said:
I have already install this rom and working for one day .
it is awesome .
but today battery less then 2% and i plug the power quickly and the red led light for 1hour and cannot power on or even reboot the devices when the power didn't plug .
i try to use adb/fastboot to reboot the devices but nothing happen the red light still light and no display
how can i fix it?
Click to expand...
Click to collapse
__________________
and i finally use all the battery until the red led light goes on . and plug and power and let it to charge and it working now.
All CM13 and RR releases we have so far are using pretty old China Dev MIUI v.6.6.30 as base not even listed on Xiaomi Downloads anymore. This as some of us know is the cause of all bugs we've had with these custom ROMs and were fixed by replacing vendor files from newer MIUI versions. On top of that some helium users cannot reboot to recovery from Android, phone doesn't power off... things like that... which most likely is due to using the wrong hydrogen kernel in this builds. Some users including me are experiencing no data going thru on good connection... Not gonna even mention VoLTE etc. So we still have bugs...
The vendor files and kernel that comes from MIUI as base are the main part that makes the hardware working flawlessly with the Android OS. These files are proprietary files with closed code, we can't change them so we have to rely on whatever Xiaomi do to optimize device performance. But we can choose which version to use and that is my goal here... Test and find the best set that works with custom ROMs.
Here we go... I have been testing the latest Global MIUI as base for two days now and so far haven't seen any issues at all. That doesn't mean no bugs... More time and testing is needed. But at least they are not any worst than what we are using now.
The common sense and logic is(fixed bugs proved that) vendor files and kernel from latest stable Global MIUI for the particular device should have more bug fixes and optimizations for the world out of China(I hope)... So using the best of my knowledge I compiled these two sets for:
HYDROGEN:
Based on latest Mi Max official Global MIUI v.8.0.1 (miui_MIMAXGlobal_V8.0.1.0.MBCMIDG_3657fef420_6.0.zip)
Download: vendor-base801MG_update-HYDROGEN.zip
HELIUM:
Based on latest Mi Max Prime official Global MIUI v.8.0.3 (miui_MIMAX652Global_V8.0.3.0.MBDMIDG_2da4c7e9db_6.0.zip)
Download: vendor-base803MG_update-HELIUM.zip
These packages are not recovery flashable zips!!! Keep reading for install instructions!
The install will get all vendor proprietary files I know of, firmware and kernel properly updated for the device code. Let's hope we get the better and latest from Xiaomi...
INSTALL INSTRUCTIONS:
MAKE TWRP BACKUP OF SYSTEM AND BOOT PARTITIONS BEFORE ANYTHING TO REVERS CHANGES IF YOU NEED TO!!!
The installation process is a little bit involving due to replacing the kernel in the actual installed boot.img in your device. I can't supply universal updated boot.img because they might be different from one release to another. I want to update what you already have. Did my best to make it user-friendly as I can without coding special app or something. Thanks to this guy whoever he is for the boot.img tools https://github.com/xiaolu/mkbootimg_tools.
Follow the steps and you should be fine:
1. Download the appropriate zip for your device code and unzip it to the root of your internal storage. You should end up with /sdcard/vendor_update folder;
2. Open your favorite terminal emulator app and execute the following commands one at a time pressing ENTER after each line:
Code:
su
hit ENTER
Code:
cp /sdcard/vendor_update/vendor-updater.sh /data/local/tmp/
hit ENTER
Code:
chmod 777 /data/local/tmp/vendor-updater.sh
hit ENTER
Code:
sh /data/local/tmp/vendor-updater.sh
hit ENTER
Alternatively you can USB connect your phone to computer and run the same commands from adb shell.
For HYDROGEN users:
That's all you have to do. The script will update your kernel and automatically will reboot phone to recovery and update vendor files so save your work before running the commands!
For HELIUM users:
Due to that can't reboot recovery bug you have to reboot manually by holding POWER and VOLUME+ buttons or fastboot method... The vendor zip will be flashed automatically and phone reboots back to system. If not, install /sdcard/vendor_update/vendor_update-HELIUM.zip manually and that's it.
Simple stuff if you decide to test these packages...
To verify update you should see kernel and baseband versions in About Phone changed like in the attached hydrogen screenshot. I can't test helium so they might be a little different. Check WiFi also... If you can turn it on and works all is good...
Helium users see if you can reboot to recovery from Advanced Power Menu, check if you can Power OFF your phone etc... the usual bugs.
Let see if these updates change anything for good or bad.
Happy testing!:good:
EDIT: Looks like 3G bug is still present in latest MIUI modem files. Flash CM_3G_fix.zip and keep the rest of the update if 3G bug is back.
Thanks a lot.
You are welcome!
Please guys lets not quote the whole OP... It takes so much screen...
No success
Maybe my fault on terminal.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
No success
Maybe my fault on terminal.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Maybe not... Give me a mnute...
That's what happens when you code unix script on windows and forget to convert it.
@JulianJenner
EDIT: FIXED(i think)...Try now and let me know it works or not!? Helium feedback appreciated...
I'm enthusiastic.
But I do not understand it.
I did what you said.
I used a terminal emulator from Play Store I just copied your text.
JulianJenner said:
I'm enthusiastic.
But I do not understand it.
I did what you said.
I used a terminal emulator from Play Store I just copied your text.
Click to expand...
Click to collapse
Did you redownload the fixed zip? Do you have the "/sdcard/vendor_update" folder with the files in it?
Make sure you copy text line by line hitting ENTER after each one!!! That's 4 lines... su... cp... chmod... sh...
Hydrogen works for me... Can't test helium unfortunately...
Terminal running successfully.
Phone reboot.
But my BB and Kernel version did not changed...
Yours Mon Aug 29
Mine Wed Jun 29
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
No. I will download again. A.S.A.P.
---------- Post added at 11:18 PM ---------- Previous post was at 11:01 PM ----------
Working.
It was my fault.
"...line by line hitting ENTER after each one..."
Firstly I did not understand it.
I pressed Enter after at the end once...
Click to expand...
Click to collapse
Phew... I thought I screwed up again...
Run this in terminal emulator:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Upload /sdcard/boot.img somewhere... I will update kernel and you will flash it... Let see if version changes. Maybe Xiaomi haven't updated helium kernel yet!? But it is definitely different from the hydrogen latest one byte by byte...
Baseband was probably already updated if you are running ajsmsg78's RR.
I did.
Upload...
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
I did.
And now?
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Go to sdcard and you will find boot.img in there, upload it somewhere and give me the link...
Ok. I see. Upload.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
JulianJenner said:
Ok. I see. Upload.
小米Max*全网通版*3GB/64GB*银色 Resurrection Remix 5.7.3
Click to expand...
Click to collapse
Just checked helium kernel with hex editor and the date is Fri Sep 2 23:22:31 CST...
Have no idea why it didn't update since script did not throw any error, right? Did the phone reboot to recovery and flashed the vendor zip?
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
Did the phone reboot to recovery and flashed the vendor zip?
Click to expand...
Click to collapse
NOPE!
OK. I think solved.
Ran script again in adb shell.
And when phone try to reboot recovery.
Stopped it.
Reboot in Fastboot mode.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
JulianJenner said:
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
NOPE!
Where is this vendor zip ( okay, I find it. vendor_update-HELIUM.zip)? Can I flash it from TWRP?
I have stock recovery, I used TWRP from Fastboot mode 'fastboot boot recovery.img' command...
Click to expand...
Click to collapse
Yes you can but first kernel has to get updated or wifi won't work.
And thats not the point... I want to see why script did not do the job but I will debug it with someone else...
Here is updated kernel link removed
Download it to /sdcard/boot_updated.img and run this in terminal:
Code:
su
hit enter
Code:
dd if=/sdcard/boot_updated.img of=/dev/block/bootdevice/by-name/boot
hit enter
After that reboot to recovery and flash that vendor_update-HELIUM.zip
Post versions, please...
OK. I think solved by myself.
Ran script again in adb shell.
And when phone tried to reboot recovery.
I stopped it with buttons.
Reboot in Fastboot mode with buttons.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
JulianJenner said:
Mister-Master! There is: http://www.mediafire.com/file/62bqqlrajr76kz6/boot.img
NOPE!
OK. I think solved.
Ran script again in adb shell.
And when phone try to reboot recovery.
Stopped it.
Reboot in Fastboot mode.
Type 'fastboot boot recovery.img'
Phone booted in TWRP
And your update installed successfully.
Thanks a lot!
Click to expand...
Click to collapse
Aaah, I got it... that can't reboot recovery bug for helium ... I will change script to not boot automatically and let helium users boot to TWRP manually and it will flash vendor zip automatically. Didn't get that bug under consideration.
Thank you for opening my eyes Hate when I can't test things...
This is mine, helium, seems it has been success, I use the one you posted at the first.
@nijel8... your work is a hard work!
I am proud to be working with you.
laolang_cool said:
This is mine, helium, seems it has been success, I use the one you posted at the first.
Click to expand...
Click to collapse
Great...:good: Seems like you don't suffer from hydrogen kernel.
[GUIDE] OOS v4.0.3 ---> FLASH & ROOT STOCK -OR- CUSTOM ROM WITH EASE & CORRECTLY
If you think that I need to add more information to this guide, please post your request. I'm not able to guess what you want from me to add to this guide.
Thank you!
INTRODUCTION:
This guide is mainly for users who tried flashing OxygenOS v4.x.x the easy and short way (like in post #9 in this thread), which had issues in the process.
I covered the most common issues with flashing OOS v4.x.x in this guide. However, you can use this guide to flash OxygenOS (latest Stable and Beta versions)
and root them OR flash your custom ROM. Just follow the instructions.
Now, you ask “why I decided to write this guide?”. Well here’s my story:
I had FreedomOS v1.7 with Google apps installed (including Dialer and Contacts from OpenGApps), encrypted, official twrp (v3.0.2-1), Xposed (v3.1.1), framework (v87),
AdAway v3.2, YouTube AdAway and SuperSU v2.79 (stable). Also, stock kernel, no Dolby ATMOS or A.R.I.S.E apps.
So, when OOS v4.0 came out, I waited for FreedomOS v2.0 to come out too. Once it did, I downloaded the ROM, OpenGApps, modified twrp .28 and started
the flashing process (I backed up my data first).
First, I flashed twrp .28 (had no problems booting into it), and clean flashed FOS v2.0. I selected “Yes” in “Pin/Pattern backup in data partition”, so I wouldn’t have issues with encryption. I selected the regular apps (for OOS to work properly) and installed the OS.
When it was done, I rebooted the device to the OS. I was confused with the new “dm-verity” message popping from nowhere, but the OS booted successfully.
When I rebooted to the twrp (to install OpenGApps), it asked for a password. I couldn’t enter the right password, because it wouldn’t accept any and it blocked
my access to my internal storage.
I started panicking, looking for answers, and I was afraid that I bricked my phone. However, after some research, I calmed down. I realized that my bootloader was still working and could roll back to OOS v3.2.8 (with stock recovery), which I did. From there I flashed FOS v1.7 and waited for more information about the new Nougat update for OnePlus 3.
Now, I’m using Stock OygenOS v4.0.3 with Stock Kernel (see FAQ #16) and so far, no issues (no dm-verity message or password upon entering modified twrp).
I tried to repeat the dm-verity issue and fixed it (see FAQ #6). I was so frustrated that no one posted a proper guide on how to fix these issues, or they were too advanced. I didn’t want to mess around with the core of the system too much. Therefore, I decided to post a simple-to-follow guide.
DISCLAIMER & IMPORTANT:
I am not responsible for any damages done by this guide. You are tinkering with your phone and held responsible for that. This is not an advanced guide. Therefore, I will refer you to the advanced guides when needed. Furthermore, this guide is based on the issues that I and other users encountered while
flashing OOS v4.x.x ------------>***BACK UP PERSONAL DATA BEFORE PROCEEDING ANY FURTHER***
This guide is intended for owners of OnePlus 3. But, after some poking in OnePlus 3T forums, you can use this guide. The only differences the OnePlus 3T
have are a newer processor, newer front camera and a different color from OnePlus 3. Make sure to use the appropriate tools (Stock recovery, TWRP,
OxygenOS v4.0.3, etc.) for OnePlus 3T. Again, I will not be responsible for any damages caused by this guide.
Please follow this guide to get rid of: dm-verity, encrypted twrp, encrypt or decrypt your device (as OnePlus 3 comes encrypted by default), change your file system from EXT4 to F2FS (vice versa as well). Also, flash a Marshmallow or Nougat Stock OOS (Stable or Beta versions), root them OR unroot your device, OR flash a custom ROM.
As far as I know, tested and read in forums, Android v6.0.1 (OxygenOS v3.x.x) supports only EXT4 file system, and Android v7.0 (OxygenOS v4.x.x) supports both EXT4 and F2FS file systems. However, F2FS is recommended for Android v7.0 (OxygenOS v4.x.x). When you perform, a full factory reset in OxygenOS v4.x.x, the file system changes from EXT4 to F2FS. ONLY “Data (userdata)” is affected by this. If you want to go back to Marshmallow, OxygenOS v3.x.x will change your file system from F2FS to EXT4 when you sideload it.
OxygenOS v4.0.3 still comes with some issues, bugs, and some rooting services are not fully supported yet (i.e. Xposed for Nougat). Luckily, OnePlus released kernel sources of Nougat, and we need to wait a little longer for Xposed and other rooting services to be supported. Therefore, I advise staying away from it,
for a little while, until those issues are fixed, and new ones don’t pop up. Also, until rooting apps are fully supported. Follow OnePlus community forums and
XDA forums for updates, troubleshooting, and solutions for your issues. MAKE SURE TO BACK UP YOUR PERSONAL DATA, time to time.
Before posting questions or issues or requests, check FAQ and posts in this thread. Thank You!
WHAT WILL YOU NEED?
You don't need to download everything in this section, only what you prefer to roll with.
ADB drivers installed on your computer (I have version 1.0.32 installed)
Unlocked bootloader (if you haven't done it yet, follow this guide: https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733)
DiskInfo app from the Play Store:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=en
OxygenOS v3.2.8 OTA:
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
OxygenOS v4.0.3 OTA:
https://www.androidfilehost.com/?fid=457095661767136075 OR http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
*** Download speeds might be slow. Be patient. ***
OxygenOs Beta 11 (Nougat):
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_11/
Stock Recovery v2.0 (compatible with OOS v3.x.x and OOS v4.x.x):
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Official TWRP (v3.0.2-1 for OxygenOS v3.x.x ; v3.0.3-0 for OxygenOs v4.x.x):
https://twrp.me/devices/oneplusthree.html
Unreleased Official TWRP v3.0.4-1 for Nougat (OxygenOS v4.x.x): *** Recommended for Nougat ***
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Unofficial TWRP (v3.0.3-0 for LineageOS v14.1):
https://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
Modified TWRP v3.0.3-x blu_spark v16 from @eng.stk:
https://forum.xda-developers.com/devdb/project/dl/?id=23082
SuperSu v2.79 (Stable):
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
OpenGApps (latest version):
http://opengapps.org/
Your desired custom ROM (I tested FreedomOS v1.7 and v2.3 and v2.4-CE, Experience ROM v10.1 [Stable and Beta 11], LineageOS v14.1):
https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348 (FreedomOS - Stable [v1.7 - OOS v3.2.8 ; v2.3 - OOS v4.0.2])
https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-ce-1-7-t3470660 (FreedomOS - Beta [v2.4-CE - OOS Beta 11])
https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259 (ExperienceOS - Stable and Beta 11 [v10.1])
https://forum.xda-developers.com/oneplus-3/development/rom-cyanogenmod-14-1-oneplus-3-t3496850 (LineageOS v14.1 - based on Andriod v7.1.1)
Code:
[I][SIZE="4"][B] * I'LL BE USING OOS v4.0.3, OFFICIAL UNRELEASED TWRP v3.0.4-1 AND FreedomOS
v2.3 AS AN EXAMPLE FOR THIS GUIDE. OTHER VERSIONS OF OOS AND TWRP
(PROVIDED) ARE APPLICABLE TO BE USED IN THE GUIDE (ONLY WHAT I TESTED).
[COLOR="Red"][I] * If you don't have dm-verity issue, file system change issue or password
upon entering TWRP, then go to Section C (FLASHING YOUR CUSTOM ROM)
-OR- Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT).
* If you do have dm-verity issue, file system change issue or password upon
entering TWRP, then continue to Section A (DM-VERITY).[/I][/COLOR]
[/B][/I][/SIZE]
A - PROCEDURE (DM-VERITY):
Code:
[I][SIZE="4"][CENTER][B]***** Check FAQ #5 before proceeding any further! *****[/B][/CENTER][/I][/SIZE]
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery recovery_op3.img” to flash Stock Recovery of OxygenOS.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into recovery by holding Volume Down (-) and Power button down for a few of seconds.
Now, for some people, it will ask a password. If not, continue to #9 and ignore #8. If it asks you to enter a password to decrypt your data, choose “Forgot password” and let it erase all your data and let it reboot. (MAKE SURE YOU BACKED UP YOUR PERSONAL DATA BEFOREHAND). Most likely, it will reboot to the OS, so boot it to recovery again. Go to #10.
For those who doesn’t have to enter a password, press “English”. Press “Wipe data and cache” > “Erase everything (Music, pics, etc.)” > “This cannot be undone, continue?”. Moreover, let it wipe your data. Most likely, it will reboot to the OS, so boot it to recovery again. Go to #10.
Code:
[CENTER][I][SIZE="4"][B]AT THIS POINT IF YOU HAD DM-VERITY ERROR/ISSUE, IT SHOULD BE FIXED AND GONE.
IF IT STILL APPEARS, DON'T WORRY IT WILL BE GONE AFTER #12
IT CAME BACK TO ME ONE MORE TIME, BUT I GOT IT FIXED.
***** Check FAQ #6 for more information *****[/B][/I][/SIZE][/CENTER]
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash OxygenOS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot and you have OxygenOS v4.0.3!
Sign-in into your Google account and Download the “DiskInfo” app from the Play Store. Launch it, and press “Data (userdata)”. You should see:
- Encrypted: yes
- Decrypted block device: /dev/block/dm-1
- Mount point: /data
- File system: f2fs
A. If you see that it is in F2FS file system format, proceed to Section C (FLASHING YOUR CUSTOM ROM) OR Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT).
B. However, for some people (for some reason) it does not happen. You would see that your file system format (for userdata) is still on EXT4. Don’t be frustrated. A little bit more work needed to be done. Therefore, go to Section B (CHANGING FILE SYSTEM FORMAT AND ENCRYPTING OR DECRYPTING YOUR DEVICE). It will solve that problem.
Code:
[I][SIZE="4"]* Your phone needs to be encrypted by default. It comes like that from the
manufacturer. See the following links:
1. [url]https://forums.oneplus.net/threads/encrypted-oneplus-3.452572/page-2[/url]
2. [url]http://www.androidpolice.com/2015/10/19/android-6-0-will-finally-require-manufacturers-to-enable-full-disk-encryption-by-default-on-new-devices/[/url]
3. [url]http://arstechnica.com/gadgets/2015/10/android-6-0-re-implements-mandatory-device-encryption-for-new-devices/[/url]
4. [url]https://source.android.com/security/encryption/[/url]
5. [url]http://www.howtogeek.com/141953/how-to-encrypt-your-android-phone-and-why-you-might-want-to/[/url]
6. [url]http://www.extremetech.com/mobile/216560-android-6-0-marshmallow-makes-full-disk-encryption-mandatory-for-most-new-devices[/url]
[/I][/SIZE]
B - PROCEDURE (CHANGING FILE SYSTEM FORMAT AND ENCRYPTING OR DECRYPTING YOUR DEVICE):
Go to: Settings > Security & fingerprint > Encryption (located at the bottom). Make sure it says “Encrypt phone (Encrypted)”. To make sure
you will need to do a factory reset.
Now go to: Settings > Backup & reset > Factory data reset. In “Optional” select “Erase internal storage” and press “RESET PHONE”. Confirm by pressing “ERASE EVERYTHING”.
It will reboot to Stock Recovery and wipe your data. When it’s done, it will reboot to the OS.
Again, download the “DiskInfo” app from the Play Store. Launch it, press “Data (userdata)”. Now you should see (it wouldn’t show “Encrypted: yes” at all):
- Mount point: /data
- File system: f2fs
Now go to: Settings > Security & fingerprint > Encryption (located at the bottom). Make sure it says “Encrypt phone” and that you can press it. (DON’T ENCRYPT YOUR PHONE WITH THAT OPTION)
Now you successfully changed your file system to F2FS and decrypted your phone!
Code:
[I][SIZE="4"] * With Official TWRP v3.0.3-0 and modified TWRP v3.0.3-x v16 (from [user=3873953]@eng.stk[/user])
you are able to use the phone in encrypted mode, password request at
boot up and with Stock or rooted OOS v4.0.3 (Also, I tested it myself).
* Therefore, I will ask you to encrypt the phone back again. Proceed with
the following instructions:
[CENTER]***** Check FAQ #9 for more information *****[/CENTER][/I][/SIZE]
Reboot to Stock recovery v2.0
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash Oxygen OS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot your device. Now you back to being encrypted and “userdata” was changed successfully to F2FS file format on Stock Oxygen OS v4.0.3!
Go to Section C (FLASHING YOUR CUSTOM ROM) to properly flash your custom ROM. *** IT’S YOUR CHOICE ***
OR Go to Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT) to remain in stock, root or unroot. *** IT’S YOUR CHOICE ***
C - PROCEDURE (FLASHING YOUR CUSTOM ROM):
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery twrp-3.0.4-1-oneplus3.img” to flash Official Unreleased TWRP v3.0.4-1.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into the TWRP by holding Volume Down (-) and Power button down for a few of seconds.
It takes a little bit more time to boot to blu_spark’s, Official and Unofficial TWRPs. Be patient.
Code:
[I][SIZE="4"] * The “PASSWORD UPON ENTERING TWRP” should not be an issue any longer (only
if you followed the whole guide). It is caused by the TWRP being modified
(has an issue with encryption), not being officially released and fully
supported for the Nougat update. Versions “.28”, “.22” and “.19” are known
for that issue. Therefore, DO NOT USE THEM. If one of them works for
you, then use it at your own risk.
[CENTER]***** Check FAQ #9 for more information *****
[/CENTER][/I][/SIZE]
Press “Wipe” > “Advanced Wipe”, and select “Dalvik / ART Cache”, “System”, “Data” and “Cache”. Then swipe “Swipe to Wipe” for a clean flash.
After it’s done, go back to the main menu. Press “Install” and look for your desired custom ROM and press on the zip file to install it.
* I used FreedomOS v2.3 as an example and I didn't have any battery drain issues. (For more information, see FAQ #10)
D - PROCEDURE (FLASHING AND ROOTING STOCK OOS OR UNROOT):
Code:
[I][SIZE="4"][COLOR="Red"][I] * If you don't have dm-verity issue, file system change issue or password
upon entering TWRP, then go to #1.
* If you came from having dm-verity issue, file system change issue or
password upon entering TWRP (solved by using Procedure A and/or B),
then go to #12.
[/I][/COLOR][/I][/SIZE]
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery recovery_op3.img” to flash Stock Recovery of OxygenOS.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into recovery by holding Volume Down (-) and Power button down for a few of seconds.
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash OxygenOS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot and you have OxygenOS v4.0.3!
A. UNROOT - At this point, if you want to unroot and go back to completely stock, then use this guide: https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/
*** Most of the procedures for unrooting you have already done. Only locking bootloader is left. Good Luck! (YOU CAN STOP HERE)
B. ROOT - Continue to #13
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery twrp-3.0.4-1-oneplus3.img” to flash Official Unreleased TWRP v3.0.4-1.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into the TWRP by holding Volume Down (-) and Power button down for a few of seconds.
It takes a little bit more time to boot to blu_spark’s, Official and Unofficial TWRPs. Be patient.
Connect you OnePlus 3 to your computer and copy the SuperSU v2.79 (Stable) to your device.
Pick up your phone. From the main menu, press “Install” and look for the SuperSU v2.79 (Stable zip file). Press it to install the root and after it's done, reboot to the OS.
That's it! Everything should be working properly
(except the bugs and issues on OxygenOS Nougat update).
ENJOY!
CREDITS:
@NevaX1 --------------> For FreedomOS ROM
@jamal2367 -----------> For ExperienceOS ROM
@cpt.macp ------------> For in depth dm-verity remover guide
@Adithya R -----------> For in depth file system formating from EXT4 to F2FS guide
@eng.stk --------------> For modified TWRP that supports F2FS file format
@LELBOT --------------> For in depth dm-verity remover and file system formating from EXT4 to F2FS guides
@Naman Bhalla ------> For in depth bootloader unlocking, flashing TWRP, rooting, nandroid backup guide
@calvinistmac --------> For providing an unroot for OnePlus 3 guide
@Nishidh --------------> For providing OxygenOS v4.0.3 and Beta 11 OTA download links
@jcadduono ----------> For providing Official TWRP
@dianlujitao ----------> For providing Unofficial TWRP and LineageOS 14.1 ROM
@th3g1z ---------------> For providing an easy solution for Dm-verity issue
--------------------------> OnePlus Community and XDA forums for providing with issues, solutions and requests
FAQ (Q&A):
Q: I can’t boot into TWRP! What to do?
A: Try using the previous TWRP or Stock Recovery.
[*]Q: I can’t boot into the OS! What to do?
A: Most likely some of the OS files are damaged or executed incorrectly. Try flashing or sideloading the OS again.
[*]Q: I can’t transfer files to my OP3 after wiping Internal storage OR Data folder/s in TWRP! What to do?
A: Don’t panic. Reboot to TWRP. It will create a folder so you can transfer files again.
[*]Q: I got an error sideloading the OS. Why is that?
A: Sometimes it occurs when the USB cable is wiggled side to side (the process stops at 92% with an error). Try again without touching
or moving the USB cable and the phone. Alternatively, it could be that USB debug is not enabled (not sure about that).
[*]Q: Is there an alternative way to get rid of dm-verity issue?
A: One simple command-line (enable) in bootloader can solve it. Check this post: https://forum.xda-developers.com/showpost.php?p=70698410&postcount=112
Otherwise, check this thread: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685 This guide uses the .28 twrp
(NOT RECOMMENDED, BUT USE TWRP FROM @eng.stk) to use Stock Recovery, which I think is a bit more complex.
OR: https://forum.xda-developers.com/showpost.php?p=70415499&postcount=33
My guide uses only bootloader, Stock Recovery and TWRP from @eng.stk. Either way, they are the same guides.
[*]Q: The "dm-verity issue" came back after flashing OTA of stock OOS v4.0.2 via the TWRP! What to do?
A: Simply follow "Section A" instructions until #13. After you sideloaded the OTA it will be gone. It happened the second time when I tried to
flash the OTA via TWRP. Therefore, don't flash OTA of stock OOS v4.x.x via TWRPs. Only via Stock Recovery v2.0
I got it fixed only after sideloading the OTA via Stock Recovery v2.0 (Check post #29 for more information)
If it still doesn't work check this thread and read it thoroughly: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-t3539129
For more information, read FAQ #12
[*]Q: Your guide to change file format doesn’t work, OR I want to change “Cache” and “System” to F2FS as well. What to do?
A: Simply go to this link and at your own risk: https://forum.xda-developers.com/oneplus-one/general/guide-formatting-ext4-to-f2fs-losing-t3352116
Furthermore, @cpt.macp mentioed in post #34 in this thread that "/system and /cache need not to be f2fs . Oneplus Supports only /data
as f2fs and nothing else ."
[*]Q: I can’t log in into Snapchat after a clean flash of my desired custom ROM or after rooting my device. How to fix this?
A: I had the same issue, and it doesn’t occur to everybody. Before DIRTY flashing (wiping System, Cache and Dalvik only) the custom ROM
-OR- rooting your device, install Snapchat and log into it (on stock OOS v4.x.x). It might be a SuperSU (root) issue with Snapchat
(they enforced their security with rooted devices).
Also, OnePlus 3 has an issue with on-screen navigation bar. So, disable it in the "Buttons" menu until OnePlus fixes the glitch/bug.
[*]Q: Why did you choose TWRP v15 from @eng.stk -OR- Official TWRP v3.0.3-0 -OR- Unofficial TWRP v3.0.3-0?
A: They all work with the phone being encrypted, requesting a password on bootup to the OS and support F2FS file system.
.28 – had issues with encryption and F2FS file system, but for some users it works wonders.
.22 and .23 – I did not test, but I have read that .23 worked (decrypted).
.19 – Tested and solved the password issue, but had a mouse pointer in the middle of the TWRP (wasn’t a big deal). Worked in decrypted mode.
P.S. The official TWRP has issues with the name of the device. If you encounter those issues, then let the developer of the ROM
you're using know about it. So, he could fix it (it's a small fix). OR use TWRP v15 from @eng.stk. Unofficial TWRP is to be used
with LineageOS 14.1 & Experience v10 ROMs. Also, here is the reason why: https://forum.xda-developers.com/showpost.php?p=70593986&postcount=53
Also, Official TWRP v3.0.2-1 doesn't support Nougat. Therefore, you won't be able to boot to this TWRP. Don't use it for Nougat.
[*]Q: I am experiencing a battery drain. Why?
A: Facebook was the main issue for that, but it is now fixed (some users said that it still exists). I use Freedom OS v2.2 and no
issues so far with the battery. I got 5 hours SOT (Screen On Time) with 45% left (on the first day), and 5½ hours SOT with 26%
battery left (on the second day). Now, I think the OS is balanced because I get almost 8 hours of SOT. Try looking for a solution
in the forums. Also, disable mobile data when using WIFI and vise versa. Furthermore, battery life may vary with the applications
you use on a daily basis, screen brightness, how much and long you touch the screen, etc. (See the attached thumbnails)
[*]Q: I am experiencing issues with the Play Store app (It’s stuck on downloading). Is there a fix?
A: When you first launch it, it tries to update itself. It will crash 1-2 times. After that, everything works just fine. Also, uninstall or don’t
install Truecaller app (well known to cause this issue). It was fixed in OOS v4.0.2, but some users still experience this issue.
In addition, if nothing works, then try uninstalling the Play Store app and reinstall it via OpenGApps. For those who are not rooted,
try finding the Play Store app via the web (install it under your own risk, as I'm not responsible for the damages).
[*]Q: Why do you use stock recovery to sideload the OS?
A: First of all, you’re going to sideload OTA of Oxygen OS, which you can’t flash in the TWRP (some people can and you might get dm-verity
issue). Secondly, the stock recovery is simple and easy to use. Thirdly, If you flash the OTA from the official TWRP, you will get a dm-verity
message. Besides, OnePlus provided only with "OTA" zips and not "signed flashable" zips.
THE DM-VERITY ISSUE (CHECK THE FOLLOWING SOURCES FOR MORE INFORMATION):
https://www.xda-developers.com/qualcomm-maintains-its-dedication-to-security-with-secure-boot/ ; https://www.xda-developers.com/stri...r-correction-to-come-with-android-7-0-nougat/ ;
https://source.android.com/security/verifiedboot/ ; https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-t3539129 ;
https://forum.xda-developers.com/showpost.php?p=70574596&postcount=34 ; https://forum.xda-developers.com/showpost.php?p=70622726&postcount=97 ;
https://forum.xda-developers.com/showpost.php?p=70622760&postcount=98 ; https://forum.xda-developers.com/showpost.php?p=70622849&postcount=102 ;
https://forum.xda-developers.com/showpost.php?p=70622999&postcount=104
[*]Q: What if I want to go back using Oxygen OS v3.2.8 (Andriod v6.0.1) or custom ROMs based on it?
A: Simply instead of using Stock Oxygen OS v4.0.2 OTA in this guide, use Stock Oxygen OS v3.2.8 OTA.
It will bring back EXT4 file system and you can use Xposed.
[*]Q: After clean flashing my Custom ROM in TWRP, I get the following message: "No OS Installed. You Sure You Want
To Reboot". What to do?
A: Try dirty flashing your Custom ROM. (Source: https://forum.xda-developers.com/showpost.php?p=70622460&postcount=5291)
[*]Q: Android System WebView is disabled in the Play Store. When I try to enable it, it won't do anything. Unless I tap
it rapidly and it's still in disabled mode. What to do?
A: No need to worry here. It is normal due to Chrome being the new WebView in Android Nougat.
(Sources: http://www.androidpolice.com/2016/07/20/google-explains-chrome-will-become-webview-android-7-0/ AND https://productforums.google.com/forum/#!topic/nexus/Ni35XW6eRR0
https://www.reddit.com/r/GooglePixel/comments/5ayh5d/android_system_webview_not_enabled/ AND https://www.reddit.com/r/Nexus6P/comments/57t1hw/android_system_webview_keeps_disabling/)
[*]Q: Should I flash a custom Kernel (ElementalX or Blu_spark) on a custom ROM?
A: You can, but you might have CPUs being on max load and overheating issues (it's not caused by the kernel itself).
They work best, and only, if you have stock OOS v4.0.2 installed and rooted with SuperSU v2.79 Stable. Yes, for some
users the custom kernels work. But, for some they won't, due to firmware issues. You can try them on your Custom
ROM, but it's not guaranteed to work. The developers of FreedomOS and ExperienceOS solved this issue.
**Some users found a solution by setting SELinux to Permissive mode instead of Enforced.
I do not recommend setting your SELinux in Permissive mode! (as well as the developer of ElementalX)!
For more information, check this thread: https://forum.xda-developers.com/oneplus-3/how-to/potential-fix-cpu-battery-drain-aosp-t3543369
Also, check these articles: https://www.xda-developers.com/onep...ng-of-selinux-to-permissive-mode-in-fastboot/ ; https://www.xda-developers.com/onep...lus-33t-bootloader-vulnerability-in-next-ota/
[*]Q: I'm getting the error (cannot read "image.zip") when trying to sideload Stock OOS. Why and how to fix this?
A: For some reason, the thread added a space in the OOS file name. If you copy the file name for Stock OOS v4.0.2 from this thread,
make sure it doesn't have spaces in it (-OR- in any other file -OR- in the console).
** Also, make sure to enable USB Debugging in Developer Options.
** Follow these guidelines separately (if the first one doesn't work, use the second or third guideline):
Reinstall OnePlus Drivers using the attached zip (OnePlus_USB_Drivers_Setup.zip) and try again. In addition,
make sure your file name is not ending with ".zip.zip" or written like that in the console.
Bootup to your OS and connect the phone to the computer (make sure to choose transfer files mode).
Copy Stock OOS v4.0.2 OTA zip to the device and reboot to recovery. Select "Install from Internal Storage",
look for the OTA file and install it.
Read the following threads/posts/articles: https://forum.xda-developers.com/showthread.php?t=1990405&page=2 ;
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ ; https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/ ;
https://www.reddit.com/r/oneplus/comments/504qgv/adb_cannot_read_error/ ; https://www.androidexplained.com/fix-cannot-read-sideload-update/ ;
https://forum.xda-developers.com/android/general/guide-how-to-adb-to-push-pull-files-t3372710
[*]Q: Every second song in Google Play Music gets skipped. What to do?
A: Make sure to disable AdAway, then reboot the device. Everything should come back to normal.
P.S. I will add more questions and answers if they get repeated in the forums, or the issue can be solved.
Updates & News:Updates:
January 14th, 2017 ---> Reverted modified TWRP v3.0.3-x v12 from @eng.stk back to v3.0.2-0 v11
(Reason: https://forum.xda-developers.com/showpost.php?p=70556176&postcount=2540)
January 15th, 2017 ---> Added an introduction section; Modified sections A, B and C for more fluent and easier guidelines; Added one more Q&A
January 20th, 2017 ---> Added Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT) ; Modified sections A, B and C ; Modified FAQ (Q&A)
and added more Q&A ; Updated to OOS v4.0.2, Beta 11, Official TWRP v3.0.3-0, Unofficial TWRP v3.0.3-0, Modified TWRP v14 from blu_spark ;
Modified Intoduction, "Disclaimer & Inportant" and "What will you need?" sections.
January 23rd, 2017 ---> Updated to latest Modified TWRP v3.0.3-x blu_spark v15 from @eng.stk
January 25th, 2017 ---> Added Unreleased Official TWRP v3.0.4-1 for Nougat ; Minor updates to the guide and FAQ.
February 9th, 2017 ---> Added and updated the thread with OxygenOS v4.0.3 ; Added one more FAQ and a new story
February 10th, 2017 ---> Updated to latest Modified TWRP v3.0.3-x blu_spark v16 from @eng.stk
News:
January 14th, 2017 ---> Oxygen OS v4.0.2 coming next week! Confirmed.
(Sources: https://forums.oneplus.net/threads/4-0-2-in-works-roll-out-by-next-week-confirmed.488348/ AND https://twitter.com/OnePlus_ITA/status/819200734067617792 AND
http://www.androidsage.com/2017/01/14/oneplus-3-and-3t-oxygen-os-4-0-2/)
January 15th, 2017 ---> We as a community of developers and users, urge OnePlus to release kernel sources by complying with GPLv2.
(Source: https://www.xda-developers.com/xda-developers-urges-oneplus-to-comply-with-gplv2-and-release-kernel-sources/)
January 18th, 2017 ---> OnePlus said that OxygenOS 4.0 doesn’t use a Debug Kernel
(Source: https://www.xda-developers.com/oneplus-oxygenos-4-0-doesnt-use-a-debug-kernel/)
January 20th, 2017 ---> Seems like OnePlus released Kernel Sources for OnePlus 3/3T. Finally!
(Sources: https://www.xda-developers.com/oneplus-releases-android-nougat-kernel-sources-for-the-oneplus-33t/ AND https://github.com/OnePlusOSS/android_vendor_qcom_thulium/commits/oneplus/QC8996_N)
January 20th, 2017 ---> The Best ROMs, Kernels, and Mods for the OnePlus 3
(Source: https://www.xda-developers.com/oneplus-3-best-stuff/)
January 21st, 2017 ---> Remap your phone’s hardware buttons with "Button Mapper" app
(Source: https://www.xda-developers.com/xda-...an-app-to-remap-your-phones-hardware-buttons/)
January 21st, 2017 ---> How to move Chrome’s address bar to the bottom without a visual bug?
(Source: https://www.xda-developers.com/psa-...ar-to-the-bottom-no-longer-causes-visual-bug/)
January 22nd, 2017 ---> Enable this Chrome Flag to Lock Rotation in Fullscreen Videos
(Source: https://www.xda-developers.com/enable-this-chrome-flag-to-lock-rotation-in-fullscreen-videos/)
January 22nd, 2017 ---> Deeply Integrated Progressive Web Apps (WebAPKs) are Live for Chrome on Android
(Source: https://www.xda-developers.com/deep...-apps-are-already-live-for-chrome-on-android/)
January 25th, 2017 ---> Open Betas updates are paused for a month for OnePlus 3/3T due to Chinese New Year
(Source: https://forums.oneplus.net/threads/...s-3-and-3t-will-be-paused-for-a-month.492623/)
January 25th, 2017 ---> Security Analysts Identify a Trojan that Quietly Purchase Apps, a Rootkit that takes over your Device,
and Ransomware that Locks your Device
(Source: https://www.xda-developers.com/secu...device-and-ransomware-that-locks-your-device/)
January 28th, 2017 ---> An update from @rovo89 about developing Xposed for Nougat
(Source: https://forum.xda-developers.com/showpost.php?p=70773752&postcount=41)
February 1st, 2017 ---> OnePlus got caught red-handed in Benchmark cheating and came clean
(Sources: https://www.xda-developers.com/benc...ght-red-handed-and-what-theyve-done-about-it/ ; http://www.androidauthority.com/oneplus-meizu-just-got-busted-benchmark-cheating-746640/)
February 9th, 2017 ---> Two Critical OnePlus 3/3T Bootloader Security Flaws Discovered, One Patched and Other being Addressed
(Source: https://www.xda-developers.com/two-...overed-one-patched-and-other-being-addressed/)
Very easy to follow guide. I ended up at B8 "Now you successfully changed your file system to F2FS and decrypted your phone!". I would like my phone to be encrypted, but if I do it through the OS, TWRP does not accept my password for the data partition?
Thanks so much, mate. This is a really good job which is gong to help to many people
Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+
Hi, i have oxygen os 4.0.1 rooted and twrp v11 bluspark...But its normal when i deletet some file i dont see immeditely the free space unti i reboot the phone...this happened sometimes and sometimes not...Its a bug?
I have flash as you post, when flash done i check file system by diskinfo, it displayed "userdata not mounted". how do i fix it. plz help me. thank you very much.
Lol this is just what I did:
1. Flash latest @eng.stk TWRP, swipe to allow modifications
2. Wipe system, data, cache
3. Install 1.4GB 4.0.1 zip
4. Wipe dalvik and cache
5. On Mount, check Mount /system as read-only
6. Reboot to system
You now have stock 4.0.1 system, kernel, and recovery.
7. Boot to recovery. TWRP is overwritten by the OOS 4.0.1 recovery.
8. Wipe everything. /data is now f2fs
Optional: flash TWRP, swipe to allow modifications, and do not check Mount /system as read-only to keep it.
No issues at all.
Sent from my OnePlus 3 using XDA Labs
Thank you! Solved my problem with Dm-Verity. Do you think, for the future *4.0.2* update or whatever number will be, that we will be able to flash OTA via TWRP or we'll need stock recovery? Only full zip with TWRP?
You might want to change that TWRP v12 back to v11. Eng.stk found some issues with v12 and pulled it.
And great guide BTW ?
Sent from my OnePlus 3 using Tapatalk
Greetings ?,
After reading this guide i just need to ask several thinks to make clear.
Recently my brothers give me his op3 as he changes to op3t ; . I want to change the phone font and afaik its to impossible to do so without root.
Im currently on 4.0 ; will this guide applicable on my phone ? Or is there a way to change font without root. Thanks in advance
laupuy said:
Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+
Click to expand...
Click to collapse
I cant't download it from that thread v12 - says file might have been deleted.
mit2nil said:
I cant't download it from that thread v12 - says file might have been deleted.
Click to expand...
Click to collapse
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs
VincentJoshuaET said:
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs
Click to expand...
Click to collapse
Yup my bad. I was on first page and just used reply button. Never mind.
Answers to your concerns:
I apologize for the late response. I was doing a bit of research to answer all of your questions.
Thank you for your patience!
jackiass said:
Very easy to follow guide. I ended up at B8 "Now you successfully changed your file system to F2FS and decrypted your phone!". I would like my phone to be encrypted, but if I do it through the OS, TWRP does not accept my password for the data partition?
Click to expand...
Click to collapse
Seems like "sideload"ing OOS v4.0.1 didn't change your file system, correct?
I would recommend to start over. When you are done B7, "sideload" OOS v4.0.1 to encrypt the device again. After that's done, continue to section C.
Crazyhat said:
Thanks so much, mate. This is a really good job which is gong to help to many people
Click to expand...
Click to collapse
You're welcome!
Thank you!
I tried very hard on gathering the right information and doing the testing on my OP3.
I almost got it bricked because of OOS v4.0.0, so I decided to post an easy to follow guide.
laupuy said:
Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+
Click to expand...
Click to collapse
Thank you very much! I have updated the thread.
UPDATE: Reverted back to v11 due to data corruption issues.
playerboys10 said:
Hi, i have oxygen os 4.0.1 rooted and twrp v11 bluspark...But its normal when i deletet some file i dont see immeditely the free space unti i reboot the phone...this happened sometimes and sometimes not...Its a bug?
Click to expand...
Click to collapse
I think it's not normal and you should see an immediate change in your free space.
I couldn't find any information about that.
Your best options are to follow this guide (if you didn't already) AND/OR post this issue in OnePlus 3 community forums.
yohan_xda said:
I have flash as you post, when flash done i check file system by diskinfo, it displayed "userdata not mounted". how do i fix it. plz help me. thank you very much.
Click to expand...
Click to collapse
Did you "sideload" stock OOS in stock recovery OR flash custom ROM via TWRP (I think this one)?
Also, where did you stop (section and number)?
VincentJoshuaET said:
Lol this is just what I did:
1. Flash latest @eng.stk TWRP, swipe to allow modifications
2. Wipe system, data, cache
3. Install 1.4GB 4.0.1 zip
4. Wipe dalvik and cache
5. On Mount, check Mount /system as read-only
6. Reboot to system
You now have stock 4.0.1 system, kernel, and recovery.
7. Boot to recovery. TWRP is overwritten by the OOS 4.0.1 recovery.
8. Wipe everything. /data is now f2fs
Optional: flash TWRP, swipe to allow modifications, and do not check Mount /system as read-only to keep it.
No issues at all.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Yes, that might be the easy way when you have no issues. But, this guide deals with common issues (dm-verity, twrp password etc.) users face when they tried to update to OOS v4.0.x
If you'll face these issues in the future, you'll know where to find the related guide to fix them.
Hurizen said:
Thank you! Solved my problem with Dm-Verity. Do you think, for the future *4.0.2* update or whatever number will be, that we will be able to flash OTA via TWRP or we'll need stock recovery? Only full zip with TWRP?
Click to expand...
Click to collapse
You are very welcome!
You could flash OTA via TWRP (full size zip and not the small 40mb zip), but I'm afraid that it might "break your root" (you wouldn't have it anymore). It can be fixed by flashing SuperSU.
Technically, you could dirty flash (wipe System, Cache and Dalvik only) the new OTA. If you would have issues after dirty flashing, post your bugs/issues, and most likely you would have to clean flash the OTA.
Give it a try (backup your personal data and dirty flash) or wait for user feedback on the new OTA.
VincentJoshuaET said:
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs
Click to expand...
Click to collapse
Thank you for replying back to him! I appriciate it!
mit2nil said:
I cant't download it from that thread v12 - says file might have been deleted.
Click to expand...
Click to collapse
I appologize about that. I have updated the thread.
Explorer23 said:
You might want to change that TWRP v12 back to v11. Eng.stk found some issues with v12 and pulled it.
And great guide BTW
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
With a bit of delay, I've put back the link to v11.
Thank you, and I hope it helped you!
dinesh7208 said:
Greetings ,
After reading this guide i just need to ask several thinks to make clear.
Recently my brothers give me his op3 as he changes to op3t ; . I want to change the phone font and afaik its to impossible to do so without root.
Im currently on 4.0 ; will this guide applicable on my phone ? Or is there a way to change font without root. Thanks in advance
Click to expand...
Click to collapse
Personally, I don't mess around with fonts. But, this guide will be applicable for rooting your phone.
Check the following threads for the fonts: https://forum.xda-developers.com/oneplus-3/help/change-font-t3426785
https://forum.xda-developers.com/oneplus-3/help/how-to-change-font-one-plus-3-t3434351
https://forum.xda-developers.com/android/themes/fonts-flashable-zips-t3219827
https://forum.xda-developers.com/oneplus-3/help/cb7-custom-fonts-t3509759
I hope they help.
I wish I had found this guide before but never mind. I was following original rooting guide by Naman on my OP3 running stock OOS 4.0.1. I used twrp v28 of blue spark and as observed by many I ended up in encryption issues and couldn't take nandroid backup so I didn't proceed.
Now, it seems it has been fixed with latest twrp (v11) by blue spark. My /data partition is already f2fs and cache is /ext4.
What steps should I follow to get back correct recovery and hopefully root as well? I am hoping that I do not need to sideload 4.0.1.
mit2nil said:
I wish I had found this guide before but never mind. I was following original rooting guide by Naman on my OP3 running stock OOS 4.0.1. I used twrp v28 of blue spark and as observed by many I ended up in encryption issues and couldn't take nandroid backup so I didn't proceed.
Now, it seems it has been fixed with latest twrp (v11) by blue spark. My /data partition is already f2fs and cache is /ext4.
What steps should I follow to get back correct recovery and hopefully root as well? I am hoping that I do not need to sideload 4.0.1.
Click to expand...
Click to collapse
I've had all of the issues in this guide. So, I decided to post one because nobody posted in-depth guide to deal with OOS v4.0.1
Also, TWRP v28 has issues with encryption being on and F2FS issues too. It caused all of my problems. I was a bit lucky to find TWRP v19 (had a mouse pointer in the middle of the TWRP, no big deal). It worked with EXT4 and F2FS file systems but wasn't perfect due to working only in decrypted mode.
It seems like you don't have any issues. Am I correct? (No password request in TWRP, dm-verity message)
If you don't, go to section "C - PROCEDURE (FLASHING YOUR CUSTOM ROM)".
About file system - leave it be. Only "/data" should be F2FS, "/Cache" and "/System" as EXT4. To much work to change them to F2FS and TWRP formats them to EXT4 when you wipe them.
dbabaev21 said:
I've had all of the issues in this guide. So, I decided to post one because nobody posted in-depth guide to deal with OOS v4.0.1
Also, TWRP v28 has issues with encryption being on and F2FS issues too. It caused all of my problems. I was a bit lucky to find TWRP v19 (had a mouse pointer in the middle of the TWRP, no big deal). It worked with EXT4 and F2FS file systems but wasn't perfect due to working only in decrypted mode.
It seems like you don't have any issues. Am I correct? (No password request in TWRP, dm-verity message)
If you don't, go to section "C - PROCEDURE (FLASHING YOUR CUSTOM ROM)".
About file system - leave it be. Only "/data" should be F2FS, "/Cache" and "/System" as EXT4. To much work to change them to F2FS and TWRP formats them to EXT4 when you wipe them.
Click to expand...
Click to collapse
I do have both issues DM verity message as well as encryption issue. I just stopped doing any further changes and decided to keep using phone as it after I hit password encryption issue with TWRP as I couldn't take nandroid backup.
mit2nil said:
I do have both issues DM verity message as well as encryption issue. I just stopped doing any further changes and decided to keep using phone as it after I hit password encryption issue with TWRP as I couldn't take nandroid backup.
Click to expand...
Click to collapse
Then start from the beginning.
I was scared to death that I bricked my phone, but managed to get out quickly.
LAST PERSONALLY Verified as working and "stable"*: GAPPS, 8/19 GAPPS
First and foremost, I'm simply compiling this for the OnePlus 6 and am making some small tweaks to include Opengapps and not only Go Apps in the builds.
The parent for this by phhusson can be found at [Resurrection Remix] [Unofficial] [2018-05-19] Phh-Treble
Next the most important information where to get the most current build of the ROM: Google Drive
For now I suggest the version ending in -go such as: 'rr_6_1_180616_system-arm64-ab-go.img.xz' as the '-gapp' is in development, I expect a number of builds over the next few days as I finally the build scripts and then the rate to tapper off to every two weeks or as there are changes that seem to warrant it, I'm not building nightly for no reason, as RR 6.1 is reasonable stable at this time.
Note: Attached (build.sh) is the build script currently being used, it is a work in progress. and will be updated in case you more regular builds. You will need 12GB of Ram Ubuntu 16.04+ (I'm using 18.04 now, but I started with 16.04) and at least 360GB (SSD recommended) to build, and upto 6 hours for the initial run and then 2 for ever additional run.
Many thanks to phhusson for allowing me to post this based off of his work.
Changes, when I have something to report. Not all build will:
The 7/7 build includes a number of patches recommended by DocRambone.
Overlay support to force Apps fullscreen, Under Display->Advanced
Some cleanups to the UI for the round corners
Better LED support
The 7/8 build is the same as 7/7, but includes July security patches, I built it in order to match the official release.
The 7/24 build is again to match the official release
The 8/19 build is again to match the official release, note regression in status bar height I'm looking into.
Second post: will have details on what is working and not
Third Post: will have full instructions on installation, backup restore based on my experiences
* Stable is relative, for me if I consider it usable from day to day it is stable.
As of 8/11/2018
In the GAPPS version
Working:
Fingerprint
Camera (Front and Back) + Flash (Also got the OnePlus Camera working*)
Speaker
Wifi (Some cut outs seen, this is not unique to this ROM and is dependent on the access port some are worse than others, no clue why)
Bluetooth
GPS
Brightness
Slider for Notifications as of 6/18 build
Mobile Data/Voice (tested dual SIMM is working)
Google Apps
Root (using magisk 16.3), told but have not personally tested that 16.4 without changes works as well
Ambient (works serious effect on battery see next post)
Full Screen Aspect Ratio Display->Advanced 7/07/2018 build+
More fully functional LED Improved for at least mounting USB sticks in 7/7 build
USB Host - Fixed for at least mounting USB sticks in 7/24 build
Bluetooth Phone audio is on the local headset. - Fixed in 7/24 build
Seems working NFC working 5.1.11 Vendor and Boot, not working with previous to 5.1.9 Vendor and Boot I have nothing to connect to to fully test
Not Working:
The Notch hides content (need to wait for P)
Unknown:
Camera Quality: I do little with the camera and am no photographer, so I can say nothing about quality, only it installed and took pictures
VaSU# said:
volte kinda works you can receive messages and calls and can send messages but cant call "out"
Click to expand...
Click to collapse
Please let me know if anything is missing, or needs to be added
Instructions to flash, backup ...
WARNING: With 5.1.8 I had no WIFI, so I suggest sticking to 5.1.6 to 5.1.7 FOR THE MOMENT
Instructions to flash, backup ...
Total time required about 90 minutes
Pre-Reqs:
First and foremost:
Start with at least 5.1.6 (or greater, as of writing 5.1.7 was the lastest), there are Treble fixes in 5.1.6 we need.
Second
verify you have a good USB cable (the Red one shipped with the phone is best)
Three
download the oneplus drivers and abd
- USB Drivers: OnePlus 6 USB Drivers for Windows
- ADB/Fastboot: ADB/Fastboot latest mini
Install both to your local system
Four
Download the latest TWRP (get both the img and zip files)
TWRP for OnePlus 6
Five
Download the files(Treble OP6 Files 5.1.6) from:
GUIDE] How to flash Treble roms on OnePlus 6
Extract and keep: vbmeta.img (if you are on 5.1.X where is the boot version you can keep the boot.img as well, if not discard).
Six
Download the lastest Oxygen OS ZIP and bootloader from:
[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates
As of writing this is:
5.1.6 full image: OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip
5.1.6 boot: OnePlus6Oxygen_22_OTA_010_all_1806070151_boot.img
Seven
Download Device ID:
Device+ID APK
Eight
Download Magisk for Treble:
Magisk modified for treble
Since as of 6/2018 the default magisk does not support Treble we need a special version I suggest: Magisk-v16.3-factory-faizauthar12-20180406.zip as teh latest I could find with support.
Nine
Recommended download fastboot installable 5.1.6 (or latest build):
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Ten
Include Overlay/Ambient Display.
Download APK at: [Overlay] Enable Night Light, Auto-Brightness, Ambient Display & more on Treble ROM
Eleven
OnePlus Camera:
OnePlus Camera APK's
Finally
Download RR 6.0 for Treble compiled after 7/08/2018:
Either download the gapps or go version (gapps is still a work in progress when I wrote this)
ROMs Google Drive
Getting Ready:
WARNING: you will loss all data on your phone, backup anything you want or need, first.
Make sure you can get to fastboot (enable "Advanced Reboot" in developers options and make sure that you can enter on a reboot by pressing volume-down and power at the same time)
Make sure you are on 5.1.6+ (5.1.6 was the latest firmware upon writing this)
Remove Any security you have set (just to be safe)
Reboot to fastboot (bootloader)
run:
Code:
fastboot oem unlock
"You will be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection, allow your device to reboot"
Backup EFS
If you have not already I'd recommend backing up EFS (to do so you need to be rooted, or else use TWRP):
Preferred, if rooted simply open a terminal and run:
Code:
su
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
Copy these files someplace safe!
If not rooted reboot to fastboot (bootloader):
Ensure that the latest twrp is in the same directory as fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot) and run (3.2.1 was the lastest as of writing this):
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select backup
select only EFS and Modem
enter a meaningful name
swipe to backup
click "Reboot System" -> "Do not Install" for TWRP if asked.
You can now locate the backup under /storage/TWRP/BACKUPS and move it to a safe location off the phone.
Backup the Phone
Recommended if you care: Backup your entire phone using TWRP as well:
Ensure that the latest twrp is in the same directory as fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot) and run (3.2.1 was the lastest as of writing this):
- fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select backup
Select Everything except EFS and Modem
enter a meaningful name
swipe to backup
click "Reboot System" -> "Do not Install" for TWRP if asked.
You can now locate the backup under /storage/TWRP/BACKUPS and move it to a safe location off the phone.
Installing RR:
Finally we are ready to install RR (or any other Treble ROM), on the OnePlus 6. You will need a build from 6/7/2018 or later to have the required Vender-Hal to be present.
You will need to locate and install the AB version for the OnePlus 6.
Note: I'm using RR from 6/13 as the base for the guide: system-arm64-ab-gapps.img
SEE FIRST POST FOR CURRENT DOWNLOAD LOCATION I compiled this using phhusson's (Orginial Build Scripts)
instructions and a bit of setup on Linux. However most Treble base ROM's should work so long as they are from after 6/7/2018 in a similar manor.
* Remember this will wipe your device and you will loss all data *
First
boot in to fastboot (bootloader):
We need to go back to TRWRP and wipe internal storage and data to be safe, as the -w option to do so when flashing is not working for me.
- fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select Wipe
Advanced Wipe
Select Cache, Data and "Internal Storage"
Swipe to Wipe
Click back until you are at the main menu
Click on Reboot
Click on Bootloader -> "Do not Install" for TWRP if asked.
Second
Flash the new ROM:
Flash vbmeta.img to remove validation
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
To be safe flash a default boot image (5.1.6 in this case)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Next reboot into recovery (you need to do this with volume down +Power, or selecting from bootload):
In stock recovery select English
Select Wipe Data and Cache
Reset system settings->yes->done
Wipe Cache->Yes->done
Erase everything->Thiscan not be undone, continue->done
back
Advanced
Reboot to fastboot->Reboot to fastboot
Now flash a the new ROM:
- fastboot flash system_a system-arm64-ab-gapps.img
- fastboot flash system_b system-arm64-ab-gapps.img
Three
reboot:
Code:
fastboot reboot
You will see the "andorid" boot screen (this is different that the Oxygen one) and being the first boot it could take a while. If you see no boot screen or it does not boot (give 10 minutes), then you likely need to repeat these steps again. If you boot into RR then continue.
You may get a Vender image mistake error ignore it it only appewars on boot.
Skip the Setup by clicking all four corners top left->top right->bottom right->bottom left (it my take more than one try), at this point you have no networking, that is what we want.
Suggestion make backup here as you have a working OS! -- Instructions to follow
Four
Move over required files: You now have RR installed and working:
Enable developer mode and then enable Advanced Reboot
Then copy over gapps-nano, Device+ ID.apk, magisk-manager apk and magisk installer zip to the phone
To get the magisk manager you need to extract it from the zip as I cloud not get the normal one to install. Extract the zip: Magisk-v16.3-factory-faizauthar12-20180406.zip copy common\magisk.apk to the phone
Five
Deal with: "Play Services not Certified by Google":
Install Device+ID (APK downloaed above) and Open
Once done open the second line shows the GSF ID for this device
Android Register GSF
Login using a gmail account (I suggest the one you use for the playstore)
Enter the GSF in the field, now we wait about 5 to 10 minutes for it to propigate
Reboot the phone as we want paly services to start fresh
First add a wIFI network.
Critical do not let any apps update until you have registered playstore, so if you see a notification saying downloading, select and click pause. Doing so with the updated 6/17 paystore resulted in a black screen where you would enter your password, no know work around other than reset if this happens.
click on playstore it should now start
Now login to your account and you should be go (it may take more than one attempt no idea why).
Now enable the update if previously paused
Update all Apps from the playstore before continuing, this may take a while give it 10 minutes
Optional: If you want remove Device+ID now (but I leave it as it is an easy way to get information).
You now have a working Playstore, if you have hung downloads then you may need to clear the cache for play services and the playstore I assume the unregistered might be the cause of them getting messed up.
Five
Install magisk:
Ensure you copied magisk zip and also the magisk manager apk to your phone, do not open, but click Done
Install the magisk manager, by locating the file in filemanager and selecting it.Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Install
Select the magisk zip from the filesystem and flash
clear cache
Reboot->System (If asked about installing TWRP swipe to install)
Allow the phone to fully boot
Suggested: Reboot the phone
Suggested: disable checks for updates as 5.7 does not work with this build.
Root is now setup.
Six
Installer th onPlus camera:
Many people want the one plus camera, copy the apk downloaed above to the phone.
Open and install via a file manager
Seven
resize Data (as it will be only 11GB), the partitioon will be larger, depending on your devide se we will use TWRP and resize2fs to grow it.
Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Advanced->Terminal
Code:
resize2fs /dev/block/sda17
Reboot System
Eight
Recommended, make a backup of your hard work:
Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select backup
Select Everything except EFS and Modem (as I'm unsure exactly which you need)
enter a meaningful name
swipe to backup
click "Reboot System" -> Swipe to reboot
Once back in RR copy the backup off the phone
Eight
Start using your OnePlus 6 with RR 6.0, rooted and with GAPPS
Nine
Upgrading:
Upgrading is simply replacing the system partitions and only these paritions (tested going from 6/13->6/16->6/17 builds)
Boot into fastboot (advanced reboot options)
Now flash the new system files:
- fastboot flash system_a new_system-arm64-ab-gapps.img
- fastboot flash system_b new_system-arm64-ab-gapps.img
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select Wipe
Advanced Wipe
Select Cache (and only Cache)
Swipe to Wipe
Reboot System
Ten
Restoring a Backup from TWRP
*This is a work in progress I can not work out how to do so safely*
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select Restore
Select the backup
Select Everything (other than EFS and Modem!)
Got to the main menu
Select Wipe
Advanced Wipe
Select Cache (and only Cache)
Swipe to Wipe
Reboot Fastboot
Eleven
Night Light, Ambient Display, requires Root:
My suggestion is not to do this if you care abut battery as I've seen major drain (even with Ambient display disabled, testing this).
Copy the apk downloaded framework-res__auto_generated_rro.apk to /vendor/overlays
Code:
mount -o rw,remount -t ext4 /vendor
cp <location of file> /vendor/overlay
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
Reboot
Comments:
TWRP does not boot if flashed onto RR (the TWRP logo appears but it will not boot), this is currently only go to protect you from using the OnePlus Recovery and messing up RR. Flashing TWRP does not affect booting into RR.
TWRP DOES handle encryption without an issue, even a wrong first pin is not an issue
TWRP making a backup of Treble ROM, backup everything for now: Data, Boot, System, System Image, Vendor, Vendor Image.
If you have problems with hung downloads from the Playstore: Pending hung PlayStore
Wifi can be flaky (appearently this is a more general issue as even stock had some issues, I fixed them by only using either 2.4 or 5Mhz wireless, if I had both active I had constant disconnects.
Worst case, to recovery, back to Oxygen 5.1.6 if you end up in a boot loop stuck booting to rtecovery, etc:
- flash-all.bat
Reboot into recovery (you need to do this with volume down +Power, or selecting from bootload):
In stock recovery select English
Select Wipe Data and Cache
Reset system settings->yes->done
Wipe Cache->Yes->done
Erase everything->This can not be undone, continue->done
back
Advanced
Reboot to fastboot->Reboot
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Copy the Oxygen full ROM back to the phone
Code:
adb push OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip /sdcard
In TWRP
Install
Select OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip
Go back to the root and select Advanced Wipe
Select Wipe
Advanced Wipe
Select Cache, Data and "Internal Storage"
Click on Reboot->Recovery (select Do not Install)
English
Wipe Cach and Data
Wipe Everything
Reboot
The phone will reboot same as the day it was made
If it does not then please refer to:
Mega Unbrick Guide for A Hard Bricked OnePlus 6
Note: Always boot fully at least once (I suggest twice and the first one is configuring android) before trying any steps above again.
Best of Luck, see a typo let me know
ERIC
thank you for this
[emoji102][emoji102][emoji102][emoji102][emoji102]
Sent from my ONEPLUS A6003 using Tapatalk
Thank you for putting so much hard work on this. Really much appreciated, will give it a try.
Might be a noob question, but due to treble, is the camera quality the same with the OnePlus app?
saintxseiya said:
Might be a noob question, but due to treble, is the camera quality the same with the OnePlus app?
Click to expand...
Click to collapse
No.
Great rom, I especially like the fact that I can choose to install without gapps (prefer fdroid). One thing that is missing is ambient display, hopefully it will be fixed sooner or later.
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Abaddon said:
No.
Click to expand...
Click to collapse
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
same quality here
Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
Never said anything about results, only that it could be installed and works, (takes pictures), personally I do little with the camera and am not photographer, but it can be installed (link above) and installed.
Updated the working to remove any confusion.
Maibol said:
same quality here
Click to expand...
Click to collapse
Could you post some comparison pics? Including portrait shots.
Would be awesome.
saintxseiya said:
Could you post some comparison pics? Including portrait shots.
Would be awesome.
Click to expand...
Click to collapse
sorry bro celebrating today with the family too much beer .....
So seeing this not even a month after the release of the op6 makes me happy and hopeful that we get a fully working RR-OS for the OP6 in the near future !
Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
because Oneplus doesnt release blobs for camera
Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
It will never be the same as OOS stock. Because aside from there is no device tree provided by OnePlus, they will never release the camera blobs due to licensing issues. Once we get a stable and proper gcam port. It'll be better than the stock OOS cam or close
is a beautiful Rom, will there be an adaptation for twrp? I have to use the gapps, because at the go version Wear OS does not work. and in the gapp version would be nice if the smartbar was running. Unfortunately, the kill app does not work ( I can not use xposed, then my bank app will not work anymore
unix2208 said:
is a beautiful Rom, will there be an adaptation for twrp? I have to use the gapps, because at the go version Wear OS does not work. and in the gapp version would be nice if the smartbar was running. Unfortunately, the kill app does not work ( I can not use xposed, then my bank app will not work anymore
Click to expand...
Click to collapse
TWRP not for now as treble is build as an image, but you should be able to flash using twrp just switch to img (though I have not tested that).
The GApps version is posted the 6/18 is working great, see second post.
As for Banking I'm unsure if any Treble based ROM passed the checks, as with or without root, as they appear as unsigned.
As for smartbar, I'll give it a try when I get a chance, as I do not use it personally.
ERIC
So safetynet won't pass?
This version of TWRP works on both the TB-X605F (wifi) and TB-X605L (LTE). It does not work for the TB-X605FC/FL (Tab M10 FHD Rel).
Warning: this TWRP is for the Lenovo Smart Tab M10 with the Snapdragon 450 (SDA450) chipset. This image will not work for the second gen M10 (TB-X606F/L), which use a Mediatek SOC. See this thread.
For the M10 HD (TB-X505F/L), see this thread. For the TB-X505X, see this thread.
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.
*/
Possible issues with TB-X605L
If the latest version of TWRP for TB-X605F doesn't work for your TB-X605L model, try version 3.4.0-0 from twrp.me.
Installation
TWRP for this device is officially supported. You can download it from twrp.me or in the TWRP App (from the PlayStore). Installation instructions are included on twrp.me.
It is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download magisk.zip to your MicroSD or OTG device. Get the latest Magisk zip file here.
if your bootloader is already unlocked, go to step 4. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot oem unlock-go
fastboot reboot
flash the twrp image:
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
if you haven't loaded Magisk yet, go to step 6. If you have already loaded Magisk, you can just reboot and you're finished:
Code:
fastboot reboot
adb reboot recovery
load Magisk (step one): reboot to recovery. Do not reboot into the system, because it will over-write TWRP with stock recovery. If that happens, go back to step 4 and start again. When you issue the reboot command (below), you have to immediately press the button combination to reboot to recovery (TWRP). Here are the steps:
issue the reboot command:
Code:
fastboot reboot
immediately press and hold all three buttons (Pwr+VolUp+VolDown). The tablet might reboot twice. Release all the buttons when you see the TWRP screen, or hear your PC acknowledge that ADB is connected.
load Magisk (step two): flash Magisk. In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the back button to go back to main TWRP screen.
select "Reboot" then "System"
if the Magisk Manager app wasn't automatically loaded, you can get it here.
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
02/03/2022 - TWRP 3.6.1_9: new TWRP release
23/11/2021 - TWRP 3.6.0_9: new TWRP release
01/01/2021 - TWRP 3.5.0-0: new TWRP release
21/11/2020 - TWRP 3.4.0-1: new official version with SPL patch
19/11/2020 - promoted security patch level to 2099-12-31. No need to worry about SPLs ever again.
02/09/2020 - promote security patch level to 2020-08-01 for TB-X605F_S210208_200807_ROW
06/08/2020 - officially supported
31/07/2020 - upgrade to TWRP 3.4.0-0
- data decryption working (security patch 2020-04-01)
- landscape mode (by popular demand)
- add more partitions to Backup options
15/01/2020 - reverted to API 28 (Android Pie)
- renamed "sdcard1" to "external_sd"
- changed [ro.build.incremental.version] in preparation for OTA #4
24/11/2019 - fixed date/time & EDL reboot mode
- dropped back to API 27
20/11/2019 - initial commit (API 28) - encryption/decryption not working
Downloads
official
TWRP for X605F: twrp.me
Source code
github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-9.0
github.com/TeamWin/android_device_lenovo_X605F (official)
github.com/Yahoo-Mike/recovery_device_lenovo_X605F (unofficial)
FAQ
See the third post for answers to some FAQs like:
Will this TWRP work with other M10 and P10 devices?
Why is my "Data" partition empty (0 MB)?
how do I root my device?
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
The amazing work of @Chaser42, @Long_Sam and others to get this project started.
XDA:DevDB Information
X605F Recovery, Tool/Utility for the Lenovo Thinkpad Tablet
Contributors
Yahoo Mike, Chaser42
Source Code: https://github.com/TeamWin/android_device_lenovo_X605F
Version Information
Status: Testing
Created 2019-11-19
Last Updated 2022-05-22 (v3.6.1 and warning for TB-X605L)
Encryption/Decryption
When you load the stock ROM, it creates and automatically encrypts the data partition. If you are not using the correct TWRP version, the data partition might be empty (0 MB). This is because TWRP failed to decrypt the data partition.
If your data partition is 0MB in TWRP, make sure you have loaded the latest version of TWRP (Nov 2020 or newer). Older builds required the security patch levels to match on TWRP and your system.
If you want to remove encryption completely, then you can use the dm-verity-forceencrypt tool. @turboperson123 has put together some instructions to remove encryption. If you've already loaded TWRP, then you only need to follow steps 6 and 7 from that post. @turboperson123 's method uses @Zackptg5 's Universal DM-Verity, ForceEncrypt, Disk Quota Disablers tool to remove encryption and dm-verity.
FAQs
Can I use this TWRP on other M10 and P10 tablets?
There are quite a few variants of these Tabs that use the Snapdragon 450 (SDM450) chipset:
TB-X605F (Tab M10 wifi) - tested working this TWRP
TB-X605L (Tab M10 LTE) - tested working with TWRP ( thanks @alexupsa )
TB-X705F/L (Tab P10) - no. Use the twrp available on this thread.
For the TB-X505F/L (M10 HD) see this post.
NOTE: the TB-606F/L (M10 2nd gen), TB-X605FC (M10 FHD) use different chipsets, so this TWRP won't work.
Why is my "Data" partition 0MB?
See the second post in this thread.
What should I backup?
Short answer: everything.
But the bare minimum might include:
System Image
Vendor Image
Firmware/Modem
Persist
Data
Cache
Boot
How do I root my device?
To root your device, here are the instructions for the:
X705F (thanks to @Chaser42)
X605F/L - follow steps 6 & 7 in the OP above. If you don't want to load TWRP, then try something like @Long_Sam's patched boot.img method.
X505F/L - follow the "step by step guide" in the OP above. Just make sure you use twrp for X505F (not for X605F).
How do I load OTAs with TWRP?
Note: if you ran the dm-verity-forceencrypt tool to unencrypt your /data, then the steps below will not work.
select "uninstall" in the Magisk Manager app. If MM doesn't reboot the system, then reboot - this will re-install stock recovery.
install the OTA (either in the system or using stock recovery).
re-flash TWRP (for the new security patch level)
re-install Magisk
TB-X605L working properly. Thank you!
TB-X605L working properly. Thank you!
Yahoo Mike said:
This is a work in progress. Volunteer testers are very welcome.
Click to expand...
Click to collapse
Wow...
That's really huge...
As we say here : "Monsieur, chapeau bas !"
Long_Sam
Lenovo has released quite a few variants of the Tab M10 now. I'm not sure this TWRP will work on all of them.
There are now even variants of a variant !
Code:
[B]M10[/B] with SDM-450 models: X605F (wifi) & X605L (LTE)
[B]M10 HD[/B] with SDM-429 models: X505F (wifi), X505L (LTE) & X505X (LTE Bands 1,2,3,4,5,7,8,20,38,40)
[B]M10 FHD[/B] with SDM-450 models: X605FC (wifi) & X605LC (LTE)
The M10 I have is shipped with a Snapdragon 450 (SDM-450) chipset & Hardware Code 63. But I see on their US site that Lenovo are now putting the SDM-429 in the X605. This might cause a problem with TWRP. I'm not sure if the kernels will be compatible.
The TWRP I've posted is for the X605F/L SDM450 (HW=63). I might need to compile a different TWRP for the SDM429 versions of the X605 & the X505.
If your X605 or X505 shipped with the SDM429, can you let me know if this TWRP works ? I need to know the Hardware Version, CPU and Hardware Code. Hardware Version and CPU are in System->About. The Hardware Code is in brackets after the S/N on the sticker on the back of the tablet, eg S/N Hxxxxxxx (63).
If you have an X605FC/LC, let me know if this TWRP works. I think it will, but I want make sure.
I have one with the 429 TB-X505F SD429 HW71 If i get some time today I might be bale to try it. I'll post soon as I do.
This morning I successfully compiled and ran the P10 kernel source on my M10. I had to tweak the config a bit. I tested it in TWRP. No problems.
Tomorrow, I'll inject it into the boot.img of the system ROM and see what happens. If it is mostly stable, then we're on the way to LOS for the M10. If it's completely stable, I'll push the source up to github.
I'll continue to use the stock kernel for the released versions of TWRP in this thread, though.
Thanks to @clsA for helping me work out that the M10 kernel is a subset of the P10 kernel.
@Yahoo Mike
thx for the twrp
succesfully flashed on my X605L
"Stock recovery image (recovery_stockROM.img) from TB-X605F_USR_S200065_1905280020_Q00332_ROW - just in case something goes wrong & you need to restore stock recovery. Only use this image on a TB-X605F. If you need it for any other variant, just ask in this thread and we'll track it down for you."
do you have the stock recovery for the X605L ?
how can i backup "DATA" inside twrp ?
will this help ?
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
OSIRIS2010 said:
...
do you have the stock recovery for the X605L ?
Click to expand...
Click to collapse
Now I think of it, you don't need it. If TWRP fails to flash, then stock recovery will still be there. If stock recovery is still not loading, just boot into the system and shutdown. When you shutdown, the system will re-flash stock recovery for you.
OSIRIS2010 said:
...
how can i backup "DATA" inside twrp ?
Click to expand...
Click to collapse
Have a look at the second post.
TL;DR...the dm-verity-forceencrypt tool will do it. But it will break the next OTA. The unencrypted P10 guys are having problems at the moment with this.
I've tried to get TWRP to unencrypt the data partition, but I can't get KeyMaster to initialise successfully. Maybe the next version of TWRP will be able to do it.
Yooo. Sorry I took so long works been crazy. I cant get it to reboot into twrp recovery. Its flashes the 605 recovery then I follow the next steps in the guide but I can only get it to reboot to the stock recovery screen. Run the reboot recovery command then immediately hold the volume + - down along with power. I tried a lot I let reboot twice then let off, and nothing then I tried several more times. Reflashing then the next step. I must not be holding my mouth...err I mean pushing the buttons right or the recovery just isn't gonna work. Add I'm very newbie at rooting and customizing. I've I've rooted one phone. A 70$ moto g5 plus I got off Ebay that was basically brand new. Installed twrp recovery and magisk. I bought that cause I have SD note 9 I cant root and have this need to play YouTube videos in my truck lol. Let me know if you have any suggestions I can try. Or ideas that might make it work. I pretty much fubard the tab and (at a different time) before I tried this recovery and was able to reflash stock img though odin.
11mackey11 said:
Yooo. Sorry I took so long works been crazy. I cant get it to reboot into twrp recovery. Its flashes the 605 recovery then I follow the next steps in the guide but I can only get it to reboot to the stock recovery screen. Run the reboot recovery command then immediately hold the volume + - down along with power. I tried a lot I let reboot twice then let off, and nothing then I tried several more times. Reflashing then the next step. I must not be holding my mouth...err I mean pushing the buttons right or the recovery just isn't gonna work. Add I'm very newbie at rooting and customizing. ...
Click to expand...
Click to collapse
Don't be too hard on yourself...you've done well to get this far.
I just had a quick look at the kernel for the X505F. It's very different from the X605F. So this TWRP definitely won't work for you. Sorry.
If you want me to build a TWRP for the X505F, PM me and we'll work something out.
How do you remove twrp I think that or magisk is giving me the booting issues. Half the time I reboot for things it gets stuck. Not sure if it's root or twrp but I can't seem to remove either.
cbomb1337 said:
How do you remove twrp I think that or magisk is giving me the booting issues. Half the time I reboot for things it gets stuck. Not sure if it's root or twrp but I can't seem to remove either.
Click to expand...
Click to collapse
If you uninstall Magisk, then the system will overwrite TWRP with stock recovery the next time you reboot. Just tap "uninstall" in the Magisk Manager app. You can also remove Magisk from TWRP following these instructions.
What kind of boot issues are you having? Are you using a TB-X605F with SDA450? Or is it something similar?
I am using Tb 605f it seems to be booting fine now after removing this riru module and edxposed. I'll just leave that and stick with just viper 4 Android lol
Do you know if them modules for increasing speed work? I think one of them was called fde and there the doze one.
cbomb1337 said:
I am using Tb 605f it seems to be booting fine now after removing this riru module and edxposed. I'll just leave that and stick with just viper 4 Android lol
Do you know if them modules for increasing speed work? I think one of them was called fde and there the doze one.
Click to expand...
Click to collapse
Good to hear it's all working again.
Sorry, I haven't tried any of those tweaks.
Lenovo have updated the stock ROM they serve for the TB-X605F through LMSA rescue. It's now at TB-X605F_USR_S210126_1910290024_Q00332_ROW. This is the latest update. There are no OTAs to apply. The M10 is due for a security OTA pretty soon, though. The P10 has already received it.
Unfortunately, it's no longer possible to post a direct link to Lenovo's website for this ROM. You'll have to use LMSA to get it.
FYI. Lenovo have changed how they serve the stock ROM. The ROM is now kept at rsdsecure-cloud.motorola.com. LMSA seems to generate (or request and receive) a one-off time-limited credentialed ticket for the download. You can't download the zip files without the credentials attached to the URL.
If you really want to, you can still intercept the URL in download_resources.json in the LMSA download folder.
is there anything new in the update. i might hold of because i dont want to lose root.
cbomb1337 said:
is there anything new in the update. i might hold of because i dont want to lose root.
Click to expand...
Click to collapse
No, there's nothing new. This isn't really an update, it just seems to be a consolidation of the old stock ROM and incremental OTAs.
This is only for M10 wifi (TB-X605F) with SDA450.
The latest OTA for TB-X605F has just landed. It's available on your tablet, or directly from: TB-X605F_USR_S210126_191029_Q00332_ROW_TO_TB-X605F_USR_S210152_200120_Q00332_ROW_WCE26E2CD5.zip.
The update takes the M10 to:
Code:
build: TB-X605F_USR_S210152_200120_ROW
security patch: 1 January 2020
kernel: 3.18.120-perf-gd60e12b6-dirty
If you have TWRP and root, you'll need to:
select "uninstall" in the Magisk Manager app
install the OTA (from SD card) in recovery and reboot
re-flash TWRP
re-install Magisk
only if you unencrypted the data partition
If you have unencrypted your data partition, it will be re-encrypted during this process. Make sure you back it up before you start the OTA. You might also need to restore the TWRP backup you made of the vendor partition, before the OTA will run. Once the OTA, TWRP and Magisk are installed, you can re-run the dm-verity tool.