Dual/Multi Boot On the OnePlus 3T - OnePlus 3T Guides, News, & Discussion

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have looked around and haven't seen anyone mention this so I thought I would post about it. I hope others find this useful. I've used this tool on my Galaxy Note 4 to have two different OS's running (mostly due to bluetooth problems on CM, but I digress). This allows the user to dual boot and maintain safetynet with Magisk. I've used this a lot and was really excited to see that it is compatible with this amazing phone!
The thread that caught my interest on the subject (for Note 4): http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
The original thread quoted by @aukhan (for S4, but most of the discussion is here too): http://forum.xda-developers.com/showthread.php?t=2447534
All credit goes to the original developers for this tool, I had nothing to do with its development. This thread is made to troubleshoot our specific device without clogging up their threads for other devices.
Thanks to @aukhan, @rlorange, @chenxiaolong , and other contributors.
Download the Dual Boot Patcher snapshot apk from here. That is the only app that you should need to complete the process. Click on the latest build link and then click on the android file that ends in "snapshot.apk". The snapshots are the recommended version at the moment.
I made a video walkthrough of this process for the Note 4. A lot of it is similar, but I will try to get a new video up for the OP3T when I have time.
Basically you patch all of the .zip files that you would have flashed normally and then you flash them to a new ROM slot. If there are more questions that the video and my more specific instructions below don't answer I'll be happy to answer them or post a better walkthrough if needed.
It should be noted that to switch back and forth you'll need to install the Dual Boot Patcher apk on both ROMs. This does not affect TWRP Recovery.
So far I've only done this once on the 3T and I haven't had any issues. Obviously the 5 second delay is a little annoying when booting between ROMs, but I can get over that. I currently have RR Official installed as my primary with Open Beta 6 as my secondary. Normally the stock ROM is recommended for the primary boot slot, but this seems to work fine.
More Specific Instructions for recommended Data Slot:
1) Download all .zip files that you would flash if you were going to flash the ROM normally (ex. LOS, Gapps, SuperSu, XPosed, kernels, etc)
2) Download the Dual Boot Patcher apk: https://snapshots.noobdev.io/, install it on your phone, set the kernel, and update the ramdisk (ROMs page, three dots on Primary, scroll to bottom)
3) Open Dual Boot Patcher app and tap the three lines in the upper left then select "Patch Zip File"
4) Tap the plus button and find each of the .zip files that you will be flashing. After selecting one make sure to change "Partition Configuration" to "Data slot" and enter a number (be consistent with each file). Push continue.
5) A file browser will now open. Navigate to the place you'd like to save the file and select the location.
6) You may now repeat steps 4 and 5 to add the rest of the zip files
7) Tap the check mark in the upper right to "Patch" all of the .zip files
8) Tap the three lines in the upper left again and select ROMs
-Installation
--Option 1
9) Tap the phone icon in the lower right and push okay
10) Tap the plus button in the lower right and navigate to where you saved your patched files. Select the main ROM (the ROM you want to dual boot to) and tap "keep location" (this will put all data in the location it specified ie /data/multiboot/data-slot-1 for this case)
11) Repeat step 10 until all zips are added in the order you want them flashed (the order is important so get your ROM before your Gapps etc). If you mess up swipe the one that's in the wrong order to the right to remove it from the list
12) Tap the check mark in the upper right. A console should appear and it should virtually flash the ROM as you would expect in TWRP
13) Once it says "x/x completed" in cyan text and it has stopped you can just tap the back arrow in the upper left
14) If you go back to the ROMs page there should now be a "Secondary" ROM. To test it out you'll need to select it and then reboot the phone.
15) Once it has booted and you are past the setup you'll need to enable "unknown sources" in the menu and install Dual Boot Patcher. Once it's installed, open it. It should find the two ROMs and you'll be able to select Primary from the ROMs menu and reboot back
--Option 2 (best if your ROM doesn't report your device name like RR)
9) After patching the files reboot into TWRP
10) Flash the patched files like you would normally flash a ROM (order is important so flash the ROM before Gapps, su, etc)
11) Once the process has completed reboot into system
12) Since you haven't selected the secondary ROM at this point it should boot to your primary ROM (although I can't remember at the moment). Open Dual Boot Patcher, select the ROMs page, select the secondary ROM, and reboot your phone
13) It should reboot to your newly installed ROM where you can set it up and install DBP to boot back between ROMs.
This process can be done using any of the partition configurations listed when patching a Zip file. Secondary and Multi Slots go to the System partition and data slot goes to internal storage. I recommend not using the Multi Slots since more than two ROMs is a lot on the system partition. I would recommend the data slots.
If you have problems make sure to set the kernel and update the ramdisk before flashing
In the event of a bootloop you can recover your primary ROM by entering TWRP, tapping install, selecting image in the bottom right corner, navigating to the /sdcard/MultiBoot/primary folder, and selecting the "boot.img" file. This will return your phone back to the primary ROM.
There is a multiboot.log file that is very useful for debugging. Please post it if you have issues (found in the /sdcard folder)
If you later want to flash anything to the ROM that you're "dual booting" into then all you have to do is patch the zip files and flash them like before except you're flashing to a slot that already has a ROM now.
Tasker Integration
I've been using RR as my daily driver, but the BT doesn't work in my car. I did a lot of research to enable ROM switching in Tasker so that I could easily switch over ROMs when I get into my car. I use my android watch to trigger the task into my OOS ROM and then when BT disconnects I have it trigger a task to switch back to RR. Here it is:
Add action>system>send intent
Under "Action" enter
Code:
com.github.chenxiaolong.dualbootpatcher.SWITCH_ROM
Under "Cat": Default
Under the first "Extra" enter
Code:
rom_id:primary
(change primary to dual or whatever your other slot name is)
Under the second "Extra" enter
Code:
reboot:true
(this tells the app to reboot right after switching the ROM to the desired one)
Under "Target": Activity
I have found that the intent will trigger if the phone is locked, but won't do anything until the phone is unlocked. With swipe or smart lock enabled you can use secure settings to wake the screen and then run a shell with root to swipe up on the lock screen (Command: "input swipe X1 Y1 X2 Y2" replace the X's and Y's with numbers for your screen. Use developer settings to figure out where the start and stop should be.)
All of this allows me to trigger a ROM switch and reboot from my watch without taking my phone out of my pocket (i.e. while driving).
Backup/Restore/Move ROMs from/to specified slots
chenxiaolong said:
Wow, a lot has happened since my midterms started Once midterms are over, I'll start replying to posts here again (starting from around page 731 when I last posted).
I haven't been doing absolutely nothing over the past couple weeks though! We now have a very basic backup and restore implementation. This is still very much a work-in-progress and currently has no UI (nor does it work outside of recovery mode). But anyway, I figured some people who love bleeding edge stuff will want to give this a try. (And yes, backing up one slot and restoring to another already works!)
Like the installer, DualBootUtilities, and pretty much everything multiboot-related, backup and restore is handled by mbtool. I've compiled debug versions here with the new backup & restore features: https://snapshots.noobdev.io/misc/mbtool/mbtool_recovery_8.0.0.r1855.gfeb767e_DEBUG.tar.xz EDIT: Extract "mbtool_recovery" from the PC zip (easier) or from assets/data-8.0.0-rVERSION.tar.xz in the apk.
To give this a try, you'll want make sure your adb command is set up properly and reboot into recovery. Then you'll need to copy the appropriate mbtool_recovery binary to /tmp/:
Code:
# For 32-bit ARM devices
adb push armeabi-v7a/mbtool_recovery /tmp/
# For 64-bit ARM devices
adb push arm64-v8a/mbtool_recovery /tmp/
# For x86/x86_64 Intel devices, you guys probably already know what you're doing
Then, make sure /system is mounted because TWRP does not mount it by default.
Code:
adb shell mount /system
Now, to backup a ROM, run, for example (to backup extsd-slot-cm to a backup named "my_backup_name"):
EDIT: One thing to note because the tool doesn't detect this yet. If you want to backup the primary ROM, make sure to do a ramdisk update from the app first. Otherwise, the kernel will not have any multiboot code and won't boot if you decide to restore it to another slot.
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup -r extsd-slot-cm -n my_backup_name
To restore a ROM, run, for example (to restore "my_backup_name" to multi-slot-1):
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery restore -r multi-slot-1 -n my_backup_name
If you want to do partial backups (say, backing up the data and kernel only), you can add "-t data,boot" to the command. For more command arguments, see:
Code:
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery backup --help
adb shell MBTOOL_NO_MULTICALL=true /tmp/mbtool_recovery restore --help
I expect there to be a lot of bugs, so feel free to blame me or yell at me for whatever issues you run into
Click to expand...
Click to collapse
Edit: Turns out I didn't look hard enough. There is a thread that has already been created to discuss this tool on this wonderful phone and it fixes an issue where some ROMs with 3/3T support won't flash in dual-boot.

I erroneously did the upgrade ramdisk on my 3t with OxygenOS and now phone is not booting anymore (5 vibration and then recovery)... Someone can help me in understanding what I can do to solve it?

mar.ste said:
I erroneously did the upgrade ramdisk on my 3t with OxygenOS and now phone is not booting anymore (5 vibration and then recovery)... Someone can help me in understanding what I can do to solve it?
Click to expand...
Click to collapse
It has been awhile since I've played with DBP, but I seem to recall that it stores a copy of the boot image before the ramdisk update that you can flash

Related

[n80xx] CyanogenMod 10.2 Dual Boot

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For anyone interested, below are the steps for getting your device dual-booting with CyanogenMod 10.2.
Why?
I don't want to erase native firmware and want to give a try to CyanogenMod
I want to have both native and CM, because I like native Samsung S-Pen apps, but want to have more fresh Android too
I like experimenting - it's cool!
The Idea
Our Android device has 2 boot partitions - for normal boot, and to boot into recovery. If I want to boot CyanogenMod, I need to place its boot image instead one of those boot partitions. E.g. if I want to have both native firmware and cyanogen - then obviously I need to replace recovery partition. However I can do the backup of recovery and restore it later if needed.
But, I also need to place cyanogen system and data partitions somewhere. Putting it on the external sdcard makes CM working really slow, repartitioning internal memory might be good idea, but it is not so easy and is not necessary for experimenting. Thus I've created 2 image files and put it to native data partition (mmcblk0p12) to media folder, e.g. into internal sdcard, then changed cyanogen boot image to mount those image files on boot as system and data partitions.
Prerequisites:
Rooted Samsung Galaxy Note 10.1 2012 Edition
2GB of free disk space at internal sdcard
Recovery partition backup, because we are going to replace it with CyanogenMod boot image
Clear understanding of what you are doing, because you potentially can break your device
Downloads:
CM 10.2 boot image
CM 10.2 data partition image
CM 10.2 system partition image
Steps
This manual suggests that you are going to do the recovery backup to external sdcard and has native firmware which means that recovery partition is mmcblk0p6, data partition is mmcblk0p12 and internal sdcard is /mnt/sdcard folder (otherwise you need to change the commands appropriately and might need to fix cyanogen boot image too).
Download 3 files by the links above and upload to internal sdcard of your device. Connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to external sdcard to create recovery backup
cd /mnt/extSdCard
dd if=/dev/block/mmcblk0p6 of=./recovery.img
# go to internal sdcard folder
cd /mnt/sdcard
# unpack partition images - each is 1Gb of disk space
gunzip ./system.img.gz
gunzip ./data.img.gz
# write CM boot image to recovery partition
dd if=./cyanogen.img of=/dev/block/mmcblk0p6
# finish
exit
exit
Now you can reboot your device into recovery mode and see CyanogenMod booting.
Restoring native recovery:
If you got tired from CyanogenMod and/or would like to take back your recovery, please use the backup you've done before. Lets say it is placed on your external sdcard, then connect to your device via ADB and run ADB shell, or type the next commands in terminal emulator:
Code:
# become root
su -
# go to the folder with recovery backup
cd /mnt/extSdCard
# write recovery image over recovery partition
dd if=./recovery.img of=/dev/block/mmcblk0p6
Please let me know If I missed anything in my steps.
P.S. What I've changed in Cyanogen boot.img to make it using img files instead of partitions in form of patch: View attachment cyanogen_boot_img.patch. It is also necessary to create /host folder in initrd folder tree.
wow!!
it's really hard to be done xD
i thought it will be as easy as it was on my old Galaxy S2
all what i needed to do is to restart the phone and press home to boot to second Rom
i hope it's going to be easier soon
and thank you for you efforts toward our device Development
MoNsTeRmUk said:
wow!!
it's really hard to be done xD
Click to expand...
Click to collapse
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
X-Stranger said:
Well, it is not as hard as it probably seems Download 3 files and overwrite recovery partition.
Probably I need to compose something like zip file for CWM or TWRP when I have free time... But if would be really nice if someone get it working too following current steps
Click to expand...
Click to collapse
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
MoNsTeRmUk said:
I really Appreciate your work here brother And as it seems our device is not getting much of the attention unlike other devices
And what i meant by hard is it's possible to be done without any mistakes , but i take sometime to do so and you need a computer every time you want to change the Rom so it's not a solution for every time use .
I wish you good luck and Thank you for your support
Click to expand...
Click to collapse
Thanks for kind words Actually you don't need to have the computer to change ROM, you can type commands from terminal emulator directly from Android. I'm also thinking about creating small Android app which can be installed to each ROM and will be able to switch boot partition within one click.
Thanks for this superb work. Can't download last file ?
Please if can make someone flashable zip it would be great I am a noob but I want try this thanks again
Sent from my GT-N8000 using Tapatalk HD
other roms
Can I do this this with another rom
maro_X said:
Can I do this this with another rom
Click to expand...
Click to collapse
It is possible, but your another rom must be specially modified for this.
What rom are you talking about exactly?
Multi-boot solution
I've tired of writing images to boot partition every time I want to switch between native firmware and Cyanogen, so decided to compose a little program that I was talking before. So let me introduce you N8xx Boot Manager!
The idea:
You put your boot images files to some folder on your sdcard, lets say to /mnt/extSdCard/images/boot
And recovery boot images to /mnt/extSdCard/images/recovery
Now you run Boot Manager and select what you want to boot as normal boot or as recovery
As soon as you selected it, the application asks you if you would like to write this image to the appropriate partition (boot or recovery)
After successful writing it will ask you for booting from that partition, e.g. propose to reboot into your another rom or recovery
For sure all the settings like path where to keep images and boot/recovery partition names can be fixed appropriately to your device at the Settings tab
For sure the application requires root permissions, e.g. your device must be rooted. You can also check this from Settings tab
The application file: View attachment bootmanager-1.0.apk - feel free to install it to your device and use posting me bug reports
P.S. The only thing I've forgotten - the button to create native boot image file backup You still need to do it manually, sorry Hopefully in next release, if there be people interested in N8xx Boot Manager
P.P.S. Generally this program can be used for any device - just put correct images and correct boot partition names
P.P.P.S. Why N8xx and not N8xxx or N80xx? Because I've missed one symbol when typed application name in Android Studio and was too lazy to change that later :laugh:
N80xx Boot Manager
Updated version of N80xx Boot Manager: View attachment bootmanager-1.1.apk
Changelog:
Fixed application name
Fixed images path detection when no settings were changes
Added "Backup boot partiton" and "Backup recovery partition" buttons
Thus, now to install CM 10.2 as dual boot you don't need to go to ADB or terminal - just upload 3 img files to your device proper locations, installl boot manager apk, create stock boot/recovery partitions backup, then select what you want to boot and boot to that rom!
P.S. Going to update first post of this thread with steps based on Boot Manager, just would be nice if someone confirm that it works.
swamimahesh said:
Can't download last file
Click to expand...
Click to collapse
Re-uploaded.
I love u man
Finally alittle love for our device :crying:
Do I have to reinstall apps when booting to cm?
edit: I dont really understand the first step when you extract data and system.img. Can you explain more clearly the procedure?
edit2: did anyone do this dualboot successfully?
data.img.gz
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
netj said:
Hi,
Thanks for this post !
The unpack data.img.gz don't work for me, an error occurs (with several softwares).
The md5 is ok.
Could you repost this file ?
TY.
:angel:
Click to expand...
Click to collapse
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment data.img.gz and let me know if it works for you.
muop_92 said:
I can not use the n80xx boot manager app. It was failed to back up recovery or boot img. And it can not detect backup folders also. I am using revolution hd9 on n8000
Sent from my GT-N8000 using Tapatalk
Click to expand...
Click to collapse
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
X-Stranger said:
I'm using the same Revolution HD 9.0 by mike1986 and it works for me. The backup might fail if backup folder is not available. By default it is trying to use external sdcard for backups, it is looking for /mnt/extSdCard/images/boot and /mnt/extSdCard/images/recovery paths for the purpose. Please create those folders if you don't have it, or change boot manager settings according to your thought where the backups should be. The boot and recovery folders should exist anyway, e.g. it is up to you to create them.
Click to expand...
Click to collapse
Where is /mnt ? I saw in my device only /storage/extSdCard
Sent from my GT-I8160 using Tapatalk 2
muop_92 said:
Where is /mnt ? I saw in my device only /storage/extSdCard
Click to expand...
Click to collapse
It's the same. External sdcard is available on both these paths as far as I know. You can change it otherwise in application settings tab.
Ok !
X-Stranger said:
Looks like file hosting has disk issues thus my files become broken. System.img re-uploaded already. Now please try that View attachment 2519204 and let me know if it works for you.
Click to expand...
Click to collapse
Hi,
It's Ok !
Thanks !
I have just modify the paths :
dd if=/dev/mmcblk0p6 of=./recovery.img --> dd if=/dev/block/mmcblk0p6 of=./recovery.img
dd if=./cyanogen.img of=/dev/mmcblk0p6 --> dd if=./cyanogen.img of=/dev/block/mmcblk0p6
:good:

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://docs.google.com/uc?id=0B5c3gpyMBJusXzRfRWg4TXhZdVE&export=download
aromafm_cooper.zip (v1.91)
http://www.upload.ee/files/3959191/aromafm_cooper.zip
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ Touch Recovery for Galaxy Ace, Tool/Utility for the Samsung Galaxy Ace S5830
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-07
:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.
NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary
commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
Very nice... will try it soon... :good:
Wow this should be great
I tried the recovery and it works. Installation is quick and simple and works just as described. Installing, wiping, backups, touch (up and down) and everything else works just as said. Kudos to you OP!
The last thing I wanna know:
After installing/restoring anything, can you successfully reboot to system?
You should also try Aroma File manager, it's the best part of this recovery.
Gonna Try...
@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and then boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk
nizar.nasani said:
@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and the boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk
Click to expand...
Click to collapse
Expect a fix soon!
I was understanding the problem for last few days (because same happens to other two devices also) and finally got the solution and I'll be re-compiling recovery as soon as I get some time.
UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.
Am I dreaming? Thanks for revive my old Ace
Sent from my Nexus 5 using XDA Premium 4 mobile app
Bhargav97 said:
UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.
Click to expand...
Click to collapse
swipe left and right dont work for me ????
Rhievaldo said:
swipe left and right dont work for me ????
Click to expand...
Click to collapse
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.
Bhargav97 said:
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.
Click to expand...
Click to collapse
always read it,, but forgot about that. Sorry... cause read it at 23 march, and try at 30 march..
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing
everything seems to be working for me
---------- Post added at 06:43 PM ---------- Previous post was at 06:34 PM ----------
actually, all features work butkeeps rebooting into recovery,, not sure if its a problem restoring a back up ill try installing a new rom
edit,, yes it reboots into recovery no matter what,, damn,, nearly close to perfect
Bhargav97 said:
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing
Click to expand...
Click to collapse
yes right when i reboot to system it reboot to recovery, the same as the previous time.
There was a little bug which caused issue for rebooting to system. I just fixed it and asked @chraso to compile. So, now finally it's done! Updated first, second and third posts.
Report back for the download link put up on first post.
i've test almost everything and i can say this is the best recovery ever made for ace ✌
thanks for bring it to our ace
sent from my kitkat ACE

[EOL] MultiROM v33(e) for OP3/3T [UNIFIED]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is one-of-a-kind multi-boot mod for Oneplus 3. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is encrypted).
MultiROM has 2 parts you need to install:
Modified recovery - You cand download the unified IMG file here, or specific for OP3 from second post and use fastboot or TWRP or Flashify app to flash it.
MultiROM - download the unified ZIP file here, or specific for OP3 from second post and flash it in recovery.
Go into TWRP MultiRom settings and check "Enable No-KEXEC Workaround"
Your current rom will not be erased by the installation.
Download links for specific OP3 version are in the second post.​
WORKAROUND for FCs
If you get FC's in your secondary, edit build.prop in that secondary's /system dir and set:
Code:
#ro.sys.sdcardfs=true
...to comment the line (don't delete, don't set to false).
Don't boot before editing this line (flash secondary, edit and then boot).
You can edit in your primary if you are rooted, looking into:
Code:
/sdcard/multirom/roms/<your_sec_rom>/system/build.prop
*You can also try using multiromfix.zip, available in this post, thx to @Startrek852 (to disable sdcardfs support in that secondary).
​
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/MR-op3/multirom
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery
MultiROM device tree - https://github.com/MR-op3/device_oneplus_oneplus3​
Thanks a lot to Tasssadar for creating this awesome utility.
And to @nkk71 for the No-KEXEC workaround
MultiROM, Tool/Utility for the OnePlus 3
XDA:DevDB Information
MultiROM OP3/3T, Tool/Utility for the OnePlus 3
Contributors
martinusbe, BitOBSessiOn
Version Information
Status: Alpha
Current Beta Version: 3.0.3-2
Beta Release Date: 2017-02-12
Created 2016-07-10
Last Updated 2019-09-10
Reserved
Downloads
IT WILL NOT WORK WHEN ENCRYPTED
How-To by @bihariel
MultiRom for oneplus3
Recovery 08/03 Fixed usb-otg
multirom-20160814-v33b-UNOFFICIAL-oneplus3.zip
uninstaller
Update 11/26
Recovery 11/26
multirom-20161126-v33e-UNOFFICIAL-oneplus3.zip
Update 02/05/2017 op3
for new firmware 4.0.+, so older roms/kernels will not work on this!
AFH folder here
Update 02/20 by @BitOBSessiOn Unified
In post #1183
Update 03/10 Unified By BitOBSessiOn
recovery https://www.androidfilehost.com/?fid=745425885120713897
mr zip https://www.androidfilehost.com/?fid=817550096634752067
Update 08/07 by BitOBSessiOn
Post #1950
Flashable zip to fix your locksettings can be found here
MR Manager TBO 2016/08/17
Multirom Manager apk with oneplus support
Changelog:
- Darkened UI by @daveyannihilation #WhiteUImustDie
- Added icons for OOS, Tipsy, Tesla, Validus, Slim (needs the new zip flashed)
- Supports all Oneplus devices, Redmi2, Lux unoffically (to use the icons, the MR maintainer will need to update his MR zip)
MR Manager TBO 2017/04/21
Multirom Manager apk with added oneplus3T support
Flash recovery
Flash multirom zip
Enable kexec workaround in TWRP mr settings
Enjoy!
Reserved
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
*Updated MultiROM Manager APK available here.
*FCs in secondaries should have been fixed in latest TWRP-MROM versions.
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Hello, MultiRom does not recognize the recovery amends
bihariel said:
Thank you,
Hope someone can add support for Oxygen OS and a kernel with kexec support.
Click to expand...
Click to collapse
Its a first build, give me a minute, i have a family
jejemc said:
Hello, MultiRom does not recognize the recovery amends
Click to expand...
Click to collapse
i know
Great work bro :beer: :good:
Unreal work bro much alohas
And here we are!! Thanks a lot @martinusbe, working like a charm!
Superfast! Many thx! Can´t wait to get my oneplus3
Dope. Nice way to use cm13 if I need dash boot into oxygen OS awesome!!
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
cunc-cam said:
Hey, booted into a secondary ROM and now Oxygen is throwing an "incorrect pattern" error. I remember there were some files to delete to fix this, but I can't remember which ones. (Maybe add it to the OP to prevent confusion?) Thanks for your time!
Click to expand...
Click to collapse
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
bihariel said:
I am unable to boot OxygenOs, what process did you folowed?
And for the incorrect patern just go to twrp- file manager, navigate into /data/system and delete the files:
password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
Click to expand...
Click to collapse
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
cunc-cam said:
Thanks so much! By not being able to boot oxygen, do you mean as secondary or as primary? It must be unencrypted. Beyond that I don't know. It might be harder as secondary, I don't know if it would encrypt itself again.
I can boot into oxygen when it's the primary os through the given method, but it does take a few seconds of black before the boot animation shows.
Click to expand...
Click to collapse
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
bihariel said:
My phone is decrypted and oxygen as primary. But i cant boot secondary roms, it always shows me the boot menu over and over.. when i select secondaries to boot.
I was able to boot only one time a sacondary rom. Must be there something am doing wrong.
Click to expand...
Click to collapse
Huh. Be sure you checked the custom recovery setting related to kexec, I don't think that is supported on our device. Other than that, I'm as clueless as you
Its checked kexec warkaround. Injected sector boot. When i select secondary to boot, the phone reboots but it always goes back to boot menu... Will investigate a bit more...
touchscreen does not work on boot menu
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
bud77 said:
Huge thanks for this port @martinusbe
FYI, I've tried all these roms as secondary, using the K-exec workaround. All are working very fine (device decrypted)
Beanstalk
ResurrectionRemix
Slim
Tipsy
Bliss
Thank you !
Edit : Just tried the MM apk, and it does not see the MM recovery, even tho it's already installed
Have you been in touch with Tassadar to have it official ?
Click to expand...
Click to collapse
does touchscreen working for you?

[GUIDE] Lenovo Yoga Tab 3 8 / YT3-850F - How to unlock and root

Hello there!
After searching the internet up and down for a guide how to root this device and having found nothing, i decided to do it by myself - with success.
Here i want to share my way of unlocking this device for others:
Warning: Backup all your data first, as the unlocking of the device will reset it to factory defaults!
This is a guide for people who are aware of the risks of flashing, it lies completely in your own responsibility!
Before doing anything at all, read this post carefuly!
Requirements:
Lenovo Yoga Tab 3 8 / YT3-850F (obviously)
Having ADB and fastboot installed.
Getting a proper twrp version & Chainfires SuperSU
Links:
15 seconds ADB Installer v1.4.3: https://forum.xda-developers.com/showthread.php?t=2588979
Fitting twrp: http://www.htcmania.com/showthread.php?t=1291696
The thread's in spanish, i used google translate.
Chainfires SuperSU: https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
This one worked for me, first i flashed an older version and got stuck within a bootloop. Reflashing this newer version and wiping all caches within twrp helped.
Step by step:
1. First you want to unlock the "developer options" in your settings.
To do this go into settings -> about this device and tap on "BuildNumber" 7 times.
After two taps, a small pop up notification should appear saying "you are now X steps away from being a developer" with a number that counts down with every additional tap.
unlocked developer options.
2. Now you can go into the developer options and activate both "USB debugging" and "OEM Unlock".
Both are needed for beeing able to flash anything onto your device in the first place.
3. Install Lenovos USB drivers & the 15 seconds ADB Installer v1.4.3
4. Boot your device into Recovery Mode. To do this, turn it on while holding both the On-Button as well as Volume-Up.
Inside the Recovery console select "boot into bootloader" with the volume keys and confirm with the on button.
See: https://forum.xda-developers.com/wiki/Lenovo_Yoga_Tab_3_-_8"-_YT3-850F
5. Connect your Tablet to your PC via USB.
Now open a console prompt on your PC and Type "fastboot oem unlock" (without the quotes of course).
This should unlock the bootloader for flashing.
6. Flash the twrp image supplied in the links section.
For Android 6 extract the "TWRP 3.0.2.7 (a)" folder from the downloaded archive, for Android 5 the "TWRP 2.8.7.7" folder.
Inside this folder, there should be a folder called "img", enter it.
Inside the img folder open a new console by “Shift + Right click” on any empty white space inside the folder and then select “Open command window here” from the context menu.
Now type "fastboot twrp.img", this should install twrp onto your device.
Now type "fastboot reboot" to reboot your device.
See: http://rootmygalaxy.net/install-twrp-recovery-via-fastboot/
Note: I have done this step on Android 6, so noe guarantee for Android 5.
7. You can enter twrp the same way now like the original recovery menu.
It will boot up in russian language, but you can change it to english or some other choices:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. It is advisable that you do a backup of your system files now with twrp, in case something goes wrong with SuperSU.
9. Copy the zip of Chainfires SuperSU onto your Device.
Within twrp you can now install SuperSU, which will root your device.
10. Done! Enjoy your newly rootet device!
Final words: To the moderators: Feel free to edit this thread for better understandability.
Hi, would you know if this method also works for model Lenovo Yoga Tab 3 10.1 / YT3-X50F? Thanks in advance.
ale_aas said:
Hi, would you know if this method also works for model Lenovo Yoga Tab 3 10.1 / YT3-X50F? Thanks in advance.
Click to expand...
Click to collapse
I have the same model, did it work for you?
fede01_8 said:
I have the same model, did it work for you?
Click to expand...
Click to collapse
Hi, please, feel free to follow the steps in this post: https://forum.xda-developers.com/th...e-yoga-tab-3-10-1-yt3-x50f-twrp-root-t3695297
I just uploaded it, and work fine for me.
Thanks so much!
Thanks So much, yYour guide worked successfully, but I was not very clear how to install the TWRP recovery, so I had to install it manually using the guide on this page:
http://www.techmoviles.com/instalar-twrp-recovery-en-depositivos-android-mediante-fastboot/
In this guide is more detailed, it can serve any other also
regards! very thankful.
PD: My YogaTab3 is of model YT3-850F, in case someone has doubts
drwakey said:
Hello there!
After searching the internet up and down for a guide how to root this device and having found nothing, i decided to do it by myself - with success.
Here i want to share my way of unlocking this device for others:
Warning: Backup all your data first, as the unlocking of the device will reset it to factory defaults!
This is a guide for people who are aware of the risks of flashing, it lies completely in your own responsibility!
Before doing anything at all, read this post carefuly!
Requirements:
Lenovo Yoga Tab 3 8 / YT3-850F (obviously)
Having ADB and fastboot installed.
Getting a proper twrp version & Chainfires SuperSU
Links:
15 seconds ADB Installer v1.4.3: https://forum.xda-developers.com/showthread.php?t=2588979
Fitting twrp: http://www.htcmania.com/showthread.php?t=1291696
The thread's in spanish, i used google translate.
Chainfires SuperSU: https://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
This one worked for me, first i flashed an older version and got stuck within a bootloop. Reflashing this newer version and wiping all caches within twrp helped.
Step by step:
1. First you want to unlock the "developer options" in your settings.
To do this go into settings -> about this device and tap on "BuildNumber" 7 times.
After two taps, a small pop up notification should appear saying "you are now X steps away from being a developer" with a number that counts down with every additional tap.
unlocked developer options.
2. Now you can go into the developer options and activate both "USB debugging" and "OEM Unlock".
Both are needed for beeing able to flash anything onto your device in the first place.
3. Install Lenovos USB drivers & the 15 seconds ADB Installer v1.4.3
4. Boot your device into Recovery Mode. To do this, turn it on while holding both the On-Button as well as Volume-Up.
Inside the Recovery console select "boot into bootloader" with the volume keys and confirm with the on button.
See: https://forum.xda-developers.com/wiki/Lenovo_Yoga_Tab_3_-_8"-_YT3-850F
5. Connect your Tablet to your PC via USB.
Now open a console prompt on your PC and Type "fastboot oem unlock" (without the quotes of course).
This should unlock the bootloader for flashing.
6. Flash the twrp image supplied in the links section.
For Android 6 extract the "TWRP 3.0.2.7 (a)" folder from the downloaded archive, for Android 5 the "TWRP 2.8.7.7" folder.
Inside this folder, there should be a folder called "img", enter it.
Inside the img folder open a new console by “Shift + Right click” on any empty white space inside the folder and then select “Open command window here” from the context menu.
Now type "fastboot twrp.img", this should install twrp onto your device.
Now type "fastboot reboot" to reboot your device.
See: http://rootmygalaxy.net/install-twrp-recovery-via-fastboot/
Note: I have done this step on Android 6, so noe guarantee for Android 5.
7. You can enter twrp the same way now like the original recovery menu.
It will boot up in russian language, but you can change it to english or some other choices:
8. It is advisable that you do a backup of your system files now with twrp, in case something goes wrong with SuperSU.
9. Copy the zip of Chainfires SuperSU onto your Device.
Within twrp you can now install SuperSU, which will root your device.
10. Done! Enjoy your newly rootet device!
Final words: To the moderators: Feel free to edit this thread for better understandability.
Click to expand...
Click to collapse
what about yt3-850m, anyone tried this on it?
thank you for this guide, but before we delve in, is there any custom rom we could flash?
my device is at 6.0.1 from telco, so unless there are nougat/oreo/pie roms out there, having a rooted device has little benefit?
ewong3 said:
thank you for this guide, but before we delve in, is there any custom rom we could flash?
my device is at 6.0.1 from telco, so unless there are nougat/oreo/pie roms out there, having a rooted device has little benefit?
Click to expand...
Click to collapse
It would facilitate the installation of Magisk though which in many ways is better than custom rom installation :good:
I did this same thing, but replaced supersu with magisk. Similar process, but rather than flashing supersu from twrp, just download magisk.apk from github, rename to magisk.zip, and flash with twrp.
Upon reboot I still had to install the magisk apk manually, as the magisk app didn't show up. Once installed, I had to go through one more step in the magisk app to reflash it properly, using the direct install method.
Instructions to install twrp (google translated from the thread linked above):
Original post (Translated)​
A month ago I bought this tablet and these are the things I did to it and that can help you
Before that, thanks to:
lenovo-forums.ru - Where I got everything from
SevenMaxs - User of that forum, who made the TWRP
baikal0912 and Steaven - From that forum too, for posting the Roms for the tablet (5.1 and 6.0 respectively)
Note 1 from OP: If you already updated to the latest version without touching anything, you only need to do the first 2 points (if you want to)
Note 2: In case you have touched and cannot update, continue from the point that you have not done (bootloader, twrp or update)
1. Unlock Bootloader​
Activate developer options
For this you have to go to "Settings -> About the tablet". Once here, you have to touch several times on "Compilation number", until it says "You are already a programmer"
Enable debugging and unlock permissions
Go to "Developer Options" and check the boxes for "OEM Unlocking" and "USB debugging"
Connect tablet to your computer
Download file and unzip it
01. Bootloader
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Run Unlock_Bootloader.bat
Note from Gramdalf: I was on linux, but was still able to do this - just look at the `.bat` file and enter the fastboot/adb commands as they are.
Review the tablet, as a code will appear and ask for permission to activate debugging, select 'Remember this computer's RSA key'
2. Install TWRP​
Connect tablet to PC
download file
02. TWRP
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Install
-If it comes with Android 5 from the factory, apply TWRP 2.8.7.7.
-If it comes with Android 6, install TWRP 3.0.2.7 (a)
You only have to open the .bat that is in each folder.
Note from Gramdalf: Same thing, just enter the commands as they are in the .bat script, making sure that you are in the correct directory. The only difference with this is that with the `tools\fastboot -i 0x17ef flash recovery img\twrp.img` command, `-i` wasn't an available option - I was able to run it just fine without it. The recovery flashed correctly, but just keep in mind that I'm not sure if there are any lasting side effects that I am unaware of.
-If you have Android 5 and then update to Android 6, you have to install TWRP 2.8.7.7 and then you can flash 3.0.2.7 which is in the "TWRP 3.0.2.7 (b)" folder from the same TWRP (it's a zip )
Note from OP: TWRP says 850M, but it is compatible with it. There is a version from someone on XDA who tweaked a few things for the 850F, but I haven't tested it.
Note from Gramdalf: I didn't do the following part in my case, but it's there just in case you want it
3. Firmware​
Android 5.1
YT3-850F_USR_S000025_1510160911_Q1241_ROW_factory_update
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Android 6
YT3-850F_000109_161226_ROW_otafull
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Just go into TWRP and flash.
Note from OP: When upgrading from 5 to 6, the bootloader is locked again and TWRP is removed, you need to do step 1 and 2 again.
Root and Xposed
Enter TWRP
Flash SuperSU
Restart
Check that it is rooted
Enter TWRP
Flash Xposed
Restart
Install the Xposed APK
Verify that it has been installed correctly
04. Programas
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

[Guide] Tired of EMUI ? Here's a full guide on how to install a Treble Rom

So I was tired of EMUI, the UI design isn't really that bad but it really clashed with Android's Material Design, so since our Mate 9 is Treble compatible, I decided to try a few Treble ROMs. After many fails and factory resets, I finally settled on Havoc-OS. Here I made a guide on how to switch to a Treble Rom.
So a few things to note :
There's no (fully) compatible TWRP recovery for Kirin devices. Either they work but cannot flash OpenGApps or they simply don't work with Treble ROMs.
Huawei's eRecovery seems to work. For me at least, it didn't work before. So as usual, BACKUP ALL OF YOUR DATA(Titanium Backup or HiSuite for apps if needed). You can also use TWRP with stock EMUI if you want to backup your partitions in case something goes really bad.
Make sure you're using stock kernel, ramdisk and recovery_ramdisk before starting anything.
A Micro SD card is optional but useful for restoring things or if you don't want to transfer all of your backup data to your PC
USB Debugging isn't really needed.
-------------------Requirements-------------------
- Your phone, obviously. Has to be a Mate 9 (Pro) updated to Android 8.0 Oreo.
- An unlocked bootloader (Since Huawei stopped giving unlock codes, I can't help you on that one. Sorry boys)
- A PC and a USB Type-C cable.
-------------------A. First things first-------------------
Enable OEM Unlocking
An easy thing to do, otherwise you won't be able to flash anything on your phone (FRP will be "Lock" on bootloader screen). You may think that this is kind of a mandatory thing to do since you've unlocked your bootloader, but you can get it back to disabled and greyed out anytime, so here's a reminder.
1. Enable developer options by going to Settings > System > About Phone and taping multiple times on Build Number
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Once that's done, go to Developer Options and enable OEM Unlocking.
-------------------B. Downloads-------------------
1. Download and install Minimal ADB
Click here to download Minimal ADB
2. Download your ROM, right now there are two fully compatible ROMs :
- OpenKirin Builds : https://openkirin.net/download/
- Havoc-OS : https://forum.xda-developers.com/mate-9/development/rom-havoc-os-t3826470
You'll get an img file that you must put inside where you installed Minimal ADB.
3a. For later : Download Huawei Firmware Finder and Huawei Update Extractor
- Huawei Firmware Finder
- Huawei Update Extractor > If you're not running Windows (Mac, Linux) (Thanks to irony_delerium)
- Also download Magisk Manager (This is an APK)
--- OR ---
3b. Download this patched Ramdisk with Magisk included so that you don't have to download all of the above. CREATED WITH BUILD NUMBER MHA-L29 8.0.0.370(C432). USE AT YOUR OWN RISK IF IT DOESN'T EXACTLY MATCH YOUR PHONE BUILD.
Here (name is patched_boot.img)
-------------------C. Installation-------------------
Now that you've got your Rom img and Minimal ADB, we can start installing it.
1. Turn off your phone.
2. Plug your phone into your PC AND hold down the volume down button until you get a (terrible) white screen saying you're in fastboot&rescue mode.
3a. Open a command prompt (with admin rights if possible) on your PC and get to your Minimal ADB directory. By default, it should look like this :
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
3b. If you installed Minimal ADB on a different drive, then type this :
Code:
cd /d {DRIVELETTER}:/{MINIMAL ADB DIRECTORY/}
4. Make sure your phone is detected by typing :
Code:
fastboot devices
This should show up.
5. Now you can start flashing your ROM by typing :
Code:
fastboot flash system {IMGFILE}.img
Your ROM should start flashing with the message 'target reported max download size of 494927872 bytes'
It should take a minute.
Once you see 'finished. total time: times', that means your ROM has been flashed.
Don't reboot just yet. Things won't work
6. Reboot to recovery by turning off your phone (hold down power button for ~5 seconds) and holding volume up.
7. Now that you are in EMUI recovery, do the following :
- Wipe cache
- Wipe data/factory reset
You MUSTdo this otherwise you will have multiple issues.
8. You're done for the installation. Now reboot to system and start your phone first config (again).
-------------------D. Root-------------------
Your Treble Rom isn't rooted by default. But the Treble Rom itself triggers the SafetyNet flag, which means even if your phone is super clean, it is not certified. So it is obviously completely optional, by it is extremely recommended to install Magisk.
If you downloaded the patched_boot.img file in the attachment
The install process will be extremely easy. It will install Magisk 16.7 (only Beta works with Treble right now). So all you have to do is :
Get to fastboot mode by turning off your phone, plugging it to your PC while holding volume down button. Then, type the following command in the same command prompt window :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and download Magisk Manager. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
If you're not using the attachment
1. Check your phone Android version and build number. It is in Settings > About phone. Write it down, you'll need it.
2. (Install and) Open Huawei Firmware Finder. Get in the 'Common Base' tab and type in your phone build number.
3. Find the matching build number in the list. Make sure its type is 'FullOTA-MF' and its size is 2Go+. Then click on the blue link in the 'Filelist' column. Copy paste the first (ending with 'update.zip') in your browser to download the zip file. It should take some time.
4. Once it's downloaded, open it with 7Zip/WinRar and extract the file named 'UPDATE.APP'.
5. Open Huawei Update Extractor, go to the Settings tab and untick everything.
6. Now, go to the Extract tab and click on the dots on the right and select your extracted 'UPDATE.APP'. A ton of files should appear.
7. Right click on 'RAMDISK', and 'Extract selected'. Put it somewhere on your PC, you'll need it.
8. Plug your phone on your computer and put your RAMDISK.IMG in a folder on your phone.
9. On your phone, download and install Magisk Manager. If it prompts you to do so, do not install it. Then go to Settings tab and change 'Update Channel' to 'Beta'.
10. Now go back and tap 'Install', then choose 'Patch Boot Image File' and select your RAMDISK.IMG that you transferred to your phone. Then let Magisk do its thing.
11. Once it's done, on your PC, go to Your Phone/Internal Store/MagiskManager, and transfer the file 'patched_boot.img' to your Minimal ADB folder.
12. Turn off your phone and get to fastboot mode. You know how to do it now, don't you ?
13. In the same command prompt on your PC, type :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and BAM, you're rooted. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
-------------------E. SafetyNet-------------------
Magisk may be installed, but with a Treble Rom, SafetyNet should trigger anyway. So you'll have to do a few things.
1. In Magisk Manager, go to the Downloads tab and search for 'MagiskHide Props Config'. Install it, then reboot your phone.
2a. Once your phone is rebooted, download Terminal Emulator on the Play Store
--- OR ---
2b. Go to developer options and enable 'Local Terminal'.
3. Open your terminal, then type :
Code:
su
(Accept root request)
Code:
props
Things should appear. Woah.
4. Type 1 (Edit device fingerprint), then f, then choose a vendor and a model by typing the right number, then press y. Don't reboot yet (press n)
5. Type 6 (Script settings), then 1, then y. Now you can reboot (press y). Once it's done, make sure that 'boot stage' is 'currently post-fs-data'. Otherwise SafetyNet will still trigger.
THERE YOU GO ! Your phone should pass SafetyNet. You can check this by trying to search for the Netflix app on the Play Store or going into the Play Store settings and making sure your device is Certified'.
If you have any question/bug, do ask/report all of dem to me.
I haven't rooted or done anything with this device since I've bought it coming from all Samsung devices previously. This guide is awesome! Nice work!
About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".
i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages
irony_delerium said:
About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".
Click to expand...
Click to collapse
Yup, I'm aware of the Play Store app, but IMO, having everything directly on your PC is more convenient. Also what you said is useful for people not running Windows, so kudos to you for that.
aureliomilitao said:
i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages
Click to expand...
Click to collapse
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.
Deytron said:
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.
Click to expand...
Click to collapse
i extract system.img in update.app ...and lost Brazil language
aureliomilitao said:
i extract system.img in update.app ...and lost Brazil language
Click to expand...
Click to collapse
Well... I'm sorry, but I can't help you on that one. It just doesn't make sense. You can't "lose" a language. As I said, try to use Huawei eRecovery to completely restore your phone.
Solved

Categories

Resources