{
"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"
}
This is only for Huawei P9 (EVA)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-eva.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_huawei_eva/releases/download/3.1.1-1/twrp-3.1.1-1-eva.img"][U]download twrp-3.1.1-1-eva.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which P9 models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Huawei P9
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin
Version Information
Status: Stable
Created 2017-03-01
Last Updated 2017-06-11
Changelog
Code:
[B]TWRP 3.1.1-0[/B]
* bump up TWRP version to 3.1.1
* fix backup of /version
* use device specific and updated prebuilts (+kernel)
* remove the ability to flash images to ext4 mounted partitions
[B]TWRP 3.1.0-3[/B]
* kernel updated for proper loop support
* magisk can now be installed and is supported by every rom running b380+ kernel (tested on b383)
* native_package.xml has been changed to device specific version
[B]TWRP 3.1.0-2[/B]
* Add support for NTFS formatted MicroSD cards or OTG drives
* Enabled direct image flashing to special partitions
(be careful when using it - one wrong klick means brick in a second!)
* TWRP is now compatible with AOSP based ROMS (LineageOS)
and decrypted Stock ROMS, transition from Stock to LOS is possible.
* Correct versioning - Device version is now comming from the common base.
* 3650-common: introduce init.recovery.hi3650.power.rc for better power handling
[B]TWRP 3.1.0-1[/B]
* proper handling of decryption (improves booting time by ~10 seconds)
* do not wipe /data/hw_init during /data wipe or factory reset to prevent system errors
* cleanup ramdisk, reduced image size by 10mb
[B]TWRP 3.1.0-0[/B]
* add the ability to format oem specific partitions
* add back f2fs support so we can format /data as f2fs
* bump up twrp version to 3.1.0
I have a p9 with b378 rooted and a working version of twrp (no data encryption), is it possible to install this thru my twrp?
frenzissi said:
I have a p9 with b378 rooted and a working version of twrp (no data encryption), is it possible to install this thru my twrp?
Click to expand...
Click to collapse
Yes, should be fine
Atarii said:
Yes, should be fine
Click to expand...
Click to collapse
I can confirm this works fine
Thanks
<<<by scaniathe>>>
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
LE: I flashed @Atarii B378 img and now I am rooted. AdAway is working as expected. Thank you!
mihairimia said:
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
Click to expand...
Click to collapse
You will still need to use my pre-rooted boot images, that's separate from TWRP. L19 is work in progress
mihairimia said:
Thank you for your effort. It installed flawless on my L19C432 with B378.
I tried to root it but it failed. Chainfire's latest zip rebooted my phone and phh's ended with error 1.
Click to expand...
Click to collapse
i will look into it today, could you link me the zip files you used for rooting? especially phhs version (supersu is not supported, thats why we removed it from the entire recovery ecosystem)
Regards
OldDroid said:
i will look into it today, could you link me the zip files you used for rooting? especially phhs version (supersu is not supported, thats why we removed it from the entire recovery ecosystem)
Regards
Click to expand...
Click to collapse
The one from here https://forum.xda-developers.com/p9/how-to/twrp-3-0-2-0-n-t3506947. Dont waste your time. Its working if B378 img from Atarii is flashed.
Atarii said:
You will still need to use my pre-rooted boot images, that's separate from TWRP. L19 is work in progress
Click to expand...
Click to collapse
L09 B378 img is ok for now. Still need to test if system apps uninstall. But I am happy Adaway is working!
Is somebody here to explain me (quick explain) what is encryption/decryption support?
And I never know... When I launch TWRP for the 1st time, we have to choose if we want to let the system untouched.
Must I let the system in "Read Only mode" or not? I don't understand what it can change (I didn't have to choose that on my previous (HTC) devices)...
Thanks.
Perfect!
Thanks
cbgti said:
Is somebody here to explain me (quick explain) what is encryption/decryption support?
And I never know... When I launch TWRP for the 1st time, we have to choose if we want to let the system untouched.
Must I let the system in "Read Only mode" or not? I don't understand what it can change (I didn't have to choose that on my previous (HTC) devices)...
Thanks.
Click to expand...
Click to collapse
Encryption/decryption support is related to the /data partition (where your user files are stored). The encryption scheme changed for Nougat, so this is the first TWRP that supports being able to read/write to that encrypted /data partition.
Read-only system mode (aka systemless mode) - some people do not touch the system partition, so they can later apply OTAs easier (as they perform a diff on system files)
good job OpenKirin team, thx a lot
So supersu from chainfire isn't working even on this, right?
@Atarii : Thanks!
After flashing ARISE Sound System dolby atmos (doesn't run) and viper (can't install driver) don't work Any solutions?
maliniaka said:
After flashing ARISE Sound System dolby atmos (doesn't run) and viper (can't install driver) don't work Any solutions?
Click to expand...
Click to collapse
Propably the script wont work on huawei, but we work on it.
will this TWRP work for the Honor 6x Nougat Beta too?
sassmann said:
will this TWRP work for the Honor 6x Nougat Beta too?
Click to expand...
Click to collapse
what does the title say, whats the name of the forum where this has been posted?
Hope this answers everything!
PS: Its comming soon for H6X.
Related
Team Win Recovery Project 3.0.4-1 (unreleased)
Notice #1: Please don't wipe your data partition if TWRP cannot decrypt it. Instead, make an effort to gather logs to help solve the issue!
Notice #2: Themes from 3.0.0 to 3.0.3 are incompatible with 3.0.4. Sorry! (small theme engine changes regarding backlight control)
This is a unified build for both the OnePlus 3 and the OnePlus 3T!
WARNING: The OnePlus 3 & 3T stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/oneplusthree.html
Use 3.0.4-1 for now, rather than the builds on twrp.me until an official release happens. You will have problems with 3.0.3 on Nougat!
For now, please download the build from:
https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-1-oneplus3.img
Officially 3.0.4 has not been released yet, but it has critical fixes for this device on Nougat, so please be patient.
There is a download link there, as well as instructions on how to flash it.
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Extract/install adb & fastboot to your computer.
{
"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"
}
Download TWRP for OnePlus 3 & 3T (oneplus3).
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.0.4-1 (build.nethunter.com) - Fix crash when trying to reboot that resulted in TWRP restarting, CAF kernel updates
v3.0.4-0 (build.nethunter.com) - Capability restoration for Nougat, F2FS backport support, EXT4 decryption support
v3.0.3-0 (twrp.me) - Same as 3.0.3-1-rc2. In sync with the OnePlus 3T device tree (3.0.3-1).
v3.0.3-1-rc2 (build.nethunter.com) - Redo the device tree for OOS 4.0, including dynamic encryption support (pull libs from ROM)
FEATURES
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Allows OnePlus full OTA flashing
KNOWN ISSUES
F2FS takes a long time to boot, see below.
If your device is taking more than 10 minutes to boot, you probably have a misc flag enabled that disables passing cmdline, see below.
Reboot buttons don't work in TWRP (restarts TWRP) - disable Ask to install TWRP App on settings page, fix on the way. - fixed in 3.0.4-1
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Personally, I'd have tried this after 15 minutes.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
WHY WON'T MY DATA DECRYPT / WHY IS MY PASSWORD INVALID IN TWRP?
In order for encryption to work in TWRP, it must pull the encryption libraries from your current ROM. It does this during TWRP boot logo. If you have no ROM installed, then it will fall back to the default OxygenOS 4.0.2 encryption libraries included in the TWRP image.
The crypto daemon in recovery will not be able to decrypt unless the version of the encryption key matches the version of the libraries. This is an unusual restriction that was added by OnePlus.
You can usually fix this by simply booting into your ROM and changing your boot up password. You can change it back or remove it if you want immediately after. This will generate a new crypto key which should be compatible when you next enter TWRP.
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-7.1)
Device tree: https://github.com/TeamWin/android_device_oneplus_oneplus3 (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_oneplus_msm8996 (twrp-7.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project for the OnePlus 3 & 3T, Tool/Utility for the OnePlus 3
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3
Version Information
Status: Stable
Current Stable Version: 3.0.4-1
Stable Release Date: 2017-01-21
Created 2017-01-23
Last Updated 2017-02-07
Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
For the OnePlus 3 only:
OxygenOS 3.2.8: http://s3.amazonaws.com/oxygenos.on...6_OTA_017_all_1611182000_fbe1471194d64b3e.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...n_16_OTA_037_all_1701041839_aa64b084a40a4.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...16_OTA_039_all_1701140133_89fcc9baba94e4c.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
For the OnePlus 3T only:
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
OxygenOS 4.0.3: http://otafsc.h2os.com/patch/amazon...3TOxygen_28_OTA_041_all_1702081824_e3a712.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
jcadduono said:
Team Win Recovery Project 3.0.4-0 (unreleased)
Click to expand...
Click to collapse
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
peshellas said:
Nice mate as always.
Pm: you might need yo check the format of the first post, everything is written 3 times. :laugh:
Click to expand...
Click to collapse
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
RohanAJoshi said:
Never quote full op, this is spamming.
For 3 times same content, open xda in browser, it's xda app bug.
Click to expand...
Click to collapse
You re Right mate, i know, i have been here since the very old days, I thought i had deleted ot, and continued, apparently not. Thanks for the tip, didn't know about the bug.
ext4 decrypted fine on OnePlus 3 OOS 4.0.2.
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
fbf2201 said:
Is flashing twrp-data-fstype-swap-x.x.zip still necessary when switching between f2fs and ext4?
The instructions and the link are not stated in OP anymore.
Click to expand...
Click to collapse
Both EXT4 and F2FS should work out of the box now.
No flashing needed.
Hello and thanx for the hard job.
I wanted to try a clean install starting from stock, hoping to correct my issue with twrp black screen.
I need your help. Here is what I've done :
- Restore stock with the unbrick tool
- Update to Nougat 7.0 and OOS4.0.2 via oneplus update
- Unlock bootloader
- Flash twrp 3.0.4-0 via fastboot
- Flash no-verity-opt-encrypt-5.0
- Flash RR rom
- Wipe data and Dalvik
- Reboot.
This is the first time it made it to me. It ask me a password when it boot. I saw a lot of post about that, but I can't understand how to solve it.
Can someone help me please ? My phone is OP3T
Hello, thanks for the super-useful tool. TWRP has been my goto recovery for as long as I have been rooting (days of htc-hd2). I am experiencing the following issues with v3.0.2-1 (all my checkpoint backups are in that version).
* Device = op3
* If it helps, this was a OOS 4.0.1 backup. I was trying to restore it because of a 4.0.2 upgrade failure attempt
* restore hangs at 100% after the backup is complete.
* After waiting for nearly 15 mins, I used the power down to restart the phone - i had lost recovery
* tried to re-install recovery. but when twrp boots - it doesn't get to main menu
* Oddly enough op recovery installs and boots into fine. Which is what I am on.
I am currently on stock recovery without root unable to restore backup ups in twrp and in titanium backup
any thoughts?
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
Its a unified version
ScratMan38 said:
Is the 3.0.4 version from this link https://build.nethunter.com/twrp/oneplus/twrp-3.0.4-0-oneplus3.img a unified 3/3T version ? or 3 only ?
Click to expand...
Click to collapse
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
cultofluna said:
I've also download it...But I'm afraid to install because it's not really clear...My device IS OP3T.
Click to expand...
Click to collapse
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Thanks your reply was really helpful:laugh:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Renosh said:
Why don't your read the OP? It clearly says it is so either you can't read or you should stick to stock OOS and never flash anything
Click to expand...
Click to collapse
Abaddon said:
it's unified. even if it says op3 it will work for the 3t. read the op. a lot of 3t stuff baked in. works fine. only issue now is the black screen with LED light when booting into recovery. at least for me
Click to expand...
Click to collapse
There was two links in the OP, one for 3.0.3-1 mentioning "unified", and one for 3.0.4 with only "oneplus3".
As I knew the dev was working on both version and still supplies 3.0.3-1 test releases in Op3T thread that were newer than the 3.0.4 he built ; and as the changelog did not mention the unification for 3.0.4, for sure, OP was not clear at all.
Is this 3.0.3.x or 3.0.4.0 backward compatible with Marshmallow ROMs?
chancex said:
the 3.0.4.0 is recommend version or have some problem must need? for now i'm use 3.0.3.1 is good with f2fs data partition, OS version is RR-N-v5.8.0-20170117-oneplus3t-Official, i want to dirty flash update to RR-N-v5.8.0-20170122-oneplus3t-Official, i need update TWRP to 3.0.4.0 first? or i can keep use 3.0.3.1?
Click to expand...
Click to collapse
You want to update a custom rom which by definition has no issue with dm-integrity (only present in stock boot image), so if you don't have any issue keep your recovery.
It seems though that latest version has a minimized risk of issues with f2fs so why not updating it?
cultofluna said:
Thanks your reply was really helpful[emoji23]
Click to expand...
Click to collapse
He was right, the thread's title says clearly 3 and 3T.
{
"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"
}
This is only for Honor 8 (FRD)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x with decryption support.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Code:
[COLOR="red"][B]WARNING:[/B] since 3.1.0-2 update we've enabled image flashing to special partitions -
not just /recovery or /boot partition.
That means your device could be bricked in a few seconds if you do not pay attention
or don't know what you're doing. (Noobs please stay away out of this section!)[/COLOR]
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-frd.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official SuperSU (not just 2.82+)[/U][/B]
1. Ensure you are running stock kernel from b380+
2. Tick the option "Keep vendor partition mounted" inside OpenKirin Settings
3. download and install [URL="www.supersu.com/download"]official SuperSU[/URL]
4. Enjoy!
[B][U]2. Custom SuperSU[/U][/B]
1. Make sure the device running stock EMUI 5.x boot.img
2. flash this modded SuperSU 2.79: [URL="https://drive.google.com/open?id=0BxWP2gF_0Bd_UmQ2Zm9ZRGxBTUE"]download here[/URL]
3. enjoy root :)
[COLOR="red"][B]NOTE:[/B][/COLOR] this is for every device (except kirin 960 based) running emui 5.x without loop support.
[B][U]3. Magisk[/U][/B]
1. ensure you are running a kernel from b380 or later
2. flash magisk
3. enjoy root & safetynet (read note)
[B][COLOR="red"]NOTE:[/COLOR][/B] Magisk Hide is a known problem on Huawei/Honor devices.
Make sure you are not rebooting/turning off your device with Magisk Hide enabled!
You may face a broken fingerprint scanner, do not worry,
simply disable magisk hide and reboot - fps works again!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_honor_frd/releases/download/3.1.1-1/twrp-3.1.1-1-frd.img"][U]download twrp-3.1.1-1-frd.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which H8 models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
yes, you can! (have a look at the instructions in FAQ)
Q: Can i install LOS or AOSP based roms with this TWRP?
yes, you can! (please follow the installing procedure in the corresponding rom thread)
Q: Can i install Magisk?
A: Every ROM based upon b380+ kernel should now include proper loop support.
Since 3.1.0-3 you are able to flash Magisk through TWRP (recovery kernel has been updated)
Q: Does official SuperSU work?
A: Yes, even though chainfire included a fix in his upcomming version,
you can use every version of it, just check the "Rooting Instructions" section.
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with forceencrypt disabled
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=4960686"]OldDroid[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Honor 8
Contributors
surdu_petru, XePeleato, OldDroid
Source Code: https://github.com/OpenKirin
Version Information
Status: Stable
Created 2017-03-03
Last Updated 2017-06-26
Changelog
Changelog
Code:
[B]TWRP 3.1.0-2[/B]
* Add support for NTFS formatted MicroSD crads or OTG drives
* Enabled direct image flashing to special partitions
([B][I][COLOR="Red"]be careful when using it - one wrong klick means brick in a second![/COLOR][/I][/B])
* TWRP is now compatible with AOSP based ROMS (LineageOS)
and decrypted Stock ROMS, transition from Stock to LOS is possible.
* Correct versioning - Device version is now comming from the common base.
* 3650-common: introduce init.recovery.hi3650.power.rc for better power handling
*** reserved ***
surdu_petru said:
*** reserved ***
Click to expand...
Click to collapse
Thanks for putting the effort into making and sharing this TWRP with us.
The download link isn't working for me.
I'm using the mobile XDA labs
Thanks
John
Sent from my Honor 8 using XDA Labs
johnhux7 said:
Thanks for putting the effort into making and sharing this TWRP with us.
The download link isn't working for me.
I'm using the mobile XDA labs
Thanks
John
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Yes, it's working ... just checked right now ! You should try one of the alternate mirror links./ Or use a PC for download !
surdu_petru said:
Yes, it's working ... just checked right now ! You should try one of the alternate mirror links./ Or use a PC for download !
Click to expand...
Click to collapse
OK.
I will try in a PC when I can.
On a mobile the hyperlink doesn't show so there is nothing to click on
Got it to download.
Just had to open the page in a browser.
Thanks buddy
Sent from my Honor 8 using XDA Labs
Has anyone managed to root EMUI 5 using this recovery?
Thnak you so much surdu_petru
surdu_petru said:
Yes, it's working ... just checked right now ! You should try one of the alternate mirror links./ Or use a PC for download !
Click to expand...
Click to collapse
The link is working.
Great work @surdu_petru!!!!! once again!
Regarding this. I already have previous nougat twrp + root (although no access to data partition) Can I just flash this one on top? Do I need to format or reinstall something afterwards?
[EDIT]
Just replace previous 3.0.2 for nougat and everything is working: root and access to data & system partition! Enormous work!!!!
Another thing, you mention a "modded boot image with disabled dm-verity" can you explain what's this and for what is it used for?
Thanks once again!
@surdu_petru : Thanks for the great work. I'm curious if you used the 7.x.x kernel from the OP git here https://github.com/OpenKirin/android_kernel_huawei_frd/tree/7.x ? If so, did you use recommended-config? (with loop-dev == y)?.
Many thanks.
Wow. Just wow.
@surdu_petru Thanks for your work, but i´m not able to mount data partition
flashed over twrp 3.0.2.0 for Nougat
4rch0 said:
@surdu_petru Thanks for your work, but i´m not able to mount data partition
flashed over twrp 3.0.2.0 for Nougat
Click to expand...
Click to collapse
Happened to me too. Maybe we need to reflash to full stock again to bring back encryption, then flash this TWRP. I don't wanna run the whole process again. Guess I'll just have to wait for LOS14.1 to be stable.
thank you so much!! now i can root (may be)..
4rch0 said:
@surdu_petru Thanks for your work, but i´m not able to mount data partition
flashed over twrp 3.0.2.0 for Nougat
Click to expand...
Click to collapse
Depends on if you formated partition before it might cause issues
Sent from my ALE-L21 using Tapatalk
LastStandingDroid said:
Depends on if you formated partition before it might cause issues
Sent from my ALE-L21 using Tapatalk
Click to expand...
Click to collapse
no didn´t format it , with the other twrp , i dont have any issues
I have flashed twrp 3.0.3 FRD at my Mate 8. I able to enter twrp but in 5 seconds my phone automatic restart. If I quickly check my internal storage. It's decrypted. So means it's working.
Is there any chance to support mate 8 too? Been using Twrp 3.0.2 FRD from beginning and has no issue.
Thanks in advance.
dexz said:
I have flashed twrp 3.0.3 FRD at my Mate 8. I able to enter twrp but in 5 seconds my phone automatic restart. If I quickly check my internal storage. It's decrypted. So means it's working.
Is there any chance to support mate 8 too? Been using Twrp 3.0.2 FRD from beginning and has no issue.
Thanks in advance.
Click to expand...
Click to collapse
If u have any chance a log would be needed. And if u can Unmount data before reboot it might help to prevent recovery from being killed
Also there might be some issues due to different devices loading recovery faster? I can't answer on this. You'll have to wait or participate in helping out testing builds from devs
Sent from my CUBOT_MANITO using Tapatalk
---------- Post added at 08:32 PM ---------- Previous post was at 08:27 PM ----------
4rch0 said:
no didn´t format it , with the other twrp , i dont have any issues
Click to expand...
Click to collapse
Where you able to use data partition in twrp earlier versions means u wiped data partition so it's decrypted. This mounts data to dm-0 if decrypted. Which the other version never did
Sent from my CUBOT_MANITO using Tapatalk
dexz said:
I have flashed twrp 3.0.3 FRD at my Mate 8. I able to enter twrp but in 5 seconds my phone automatic restart. If I quickly check my internal storage. It's decrypted. So means it's working.
Is there any chance to support mate 8 too? Been using Twrp 3.0.2 FRD from beginning and has no issue.
Thanks in advance.
Click to expand...
Click to collapse
your device isnt supported, its for honor 8!
Regards,
OD
TWRP installed. Data encrypted. But flashing EMUI5 root with the package found here did not give any success (root not detected)
morpheus302 said:
TWRP installed. Data encrypted. But flashing EMUI5 root with the package found here did not give any success (root not detected)
Click to expand...
Click to collapse
Yes I can confirm that. @LastStandingDroid could you upload your old TWRP?
Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
{
"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"
}
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: beta
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
NOTE:
This may be a dead duck in the water before it even installs due to the fact Samsung currently seem to be locking bootloaders on all recent devices even devices with previously unlocked bootloaders.
BEFORE attempting to install this software please ensure you have the stock firmware available (this can be found on updato.com) and that you are able to flash it with Odin.
.
1.1k views, 120 downloads and not one report or tap of a thanks.
XDA truly is about community spirit.
Cheers guys.
If you do one for the the a530f i would be glad to test it ! (if there's no risk of complete brick of course)
tibey said:
If you do one for the the a530f i would be glad to test it ! (if there's no risk of complete brick of course)
Click to expand...
Click to collapse
No risk as long as you've got the firmware handy.
ashyx said:
1.1k views, 120 downloads and not one report or tap of a thanks.
XDA truly is about community spirit.
Cheers guys.
Click to expand...
Click to collapse
It's amazing.
I would very much like to know if this is locked from factory, but no one reports if it can be flashed or not :/
Guide on TWRP recovery for A8
ashyx said:
Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: Testing stage
NOTE: THIS IS AS YET UNTESTED. IF YOU DECIDE TO TRY THIS OUT PLEASE REPORT ANY ISSUES WITH DETAILS. POSTS LIKE 'NOT WORKING' WILL BE IGNORED
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Hello @ashyx, I have made a guide based on your thread: http://techbeasts.com/install-twrp-recovery-root-galaxy-a8-plus-2018/
Just wanted to notify.
Sucks that no one is reporting anything, but tbh in europe it seems that only the A8 (A530f) has been released so far.
Do you think it would be easy to port for that model ? I think there's a couple of us waiting for this port, would be much appreciated and would test it asap.
tibey said:
Sucks that no one is reporting anything, but tbh in europe it seems that only the A8 (A530f) has been released so far.
Do you think it would be easy to port for that model ? I think there's a couple of us waiting for this port, would be much appreciated and would test it asap.
Click to expand...
Click to collapse
It will be ready at some point today.
@tibey
Here you go, good luck: https://androidfilehost.com/?fid=746010030569951180
.
ashyx said:
@tibey
Here you go, good luck: https://androidfilehost.com/?fid=746010030569951180
.
Click to expand...
Click to collapse
Seems to work great on a530f ! Just followed the instructions (had just a minor issur with MTP not working in TWRP)
Thanks a lot :good:
Edit : Guess you should post it there : https://forum.xda-developers.com/ga...18-roms-kernels-recoveries--other-development (damn that forum is invisible in search)
tibey said:
Seems to work great on a530f ! Just followed the instructions (had just a minor issur with MTP not working in TWRP)
Thanks a lot :good:
Edit : Guess you should post it there : https://forum.xda-developers.com/ga...18-roms-kernels-recoveries--other-development (damn that forum is invisible in search)
Click to expand...
Click to collapse
Yep it seems Samsung are forcing the use of their own MTP driver in the kernel as I couldn't disable it.
And it continues, now 2.2k views and 199 downloads and still not one downloader could be bothered to post.
ashyx said:
And it continues, now 2.2k views and 199 downloads and still not one downloader could be bothered to post.
Click to expand...
Click to collapse
Well samsung mtp isn't in a8+ defconfig i just looked. So post your device tree and the partition layout and fstab from stock kernel and I will see if I can help.
travis82 said:
Well samsung mtp isn't in a8+ defconfig i just looked. So post your device tree and the partition layout and fstab from stock kernel and I will see if I can help.
Click to expand...
Click to collapse
I know it isn't which is why it isn't included.
Seems like they are forcing their own driver.
There is probably a way to fix it by modifying the make files, but I won't spend any more time on it until people can be bothered to take the time to respond.
Not working
ashyx said:
Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: Testing stage
NOTE: THIS IS AS YET UNTESTED. IF YOU DECIDE TO TRY THIS OUT PLEASE REPORT ANY ISSUES WITH DETAILS. POSTS LIKE 'NOT WORKING' WILL BE IGNORED
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Not Working Properly its give bootloop
i try according to this method but not working it restart after the first logo of the phone.
odin show passed message but phone get bootloops
akshaygpt2 said:
Not Working Properly its give bootloop
i try according to this method but not working it restart after the first logo of the phone.
odin show passed message but phone get bootloops
Click to expand...
Click to collapse
.
What are your phone specs and build number?
ashyx said:
.
What are your phone specs and build number?
Click to expand...
Click to collapse
Android 7.1.1
Galaxy A8 plus
Sent from my SM-A730F using Tapatalk
akshaygpt2 said:
Android 7.1.1
Galaxy A8 plus
Click to expand...
Click to collapse
I need your firmware build.
ashyx said:
I need your firmware build.
Click to expand...
Click to collapse
Build Firmware -
NMF26X.A730FXXU1ARAC
Sent from my SM-A730F using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/[/COLOR]
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3 Compact
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Install ROM.
Install 10.0 Gapps for ARM. **
* recommended TWRP: Post #2
** optional, opengapps
Downloads
Download the ROM
Over the Air Updates
To use OTA updates please read Post #2
Sources
DEVICE:
https://github.com/LineageOS/android_device_sony_z3c
https://github.com/LineageOS/android_device_sony_msm8974-common
https://github.com/LineageOS/android_device_sony_shinano-common
KERNEL:
https://github.com/LineageOS/android_kernel_sony_msm8974
Addons
OpenGapps
Magisk
Thanks
Whole LineageOS Team for this amazing ROM
@koron393
@SpiritCroc
@Myself5
@nailyk
@drakonizer
@rcstar6696
@tomascus
I hope I haven't forgot anyone
Bugs
Current hardware support state: Gist
WHAT'S BROKEN
You tell me.
XDA:DevDB Information
LineageOS 17.1 for z3c, ROM for the Sony Xperia Z3 Compact
Contributors
NeoArian
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 23.5.A.1.291
Based On: AOSP
Version Information
Status: Beta
Created 2019-10-02
Last Updated 2020-01-04
OTA and TWRP recovery
Over the Air Updates
My upload script automatically pushed OTA updates to my GitHub.
If you want to make them visible through the Updater you can flash the attached magisk module LineageOS-17.1_z3c-OTA-v1.zip or add the line
Code:
lineage.updater.uri=https://raw.githubusercontent.com/ArianK16a/OTA/lineage-17.1/z3c.json
manually to your build.prop. You should use the recommended TWRP so that the updates flash fine.
TWRP recovery
TWRP 3.3.1 for our z3c with Android 10!
The TWRP for Android 10 is attached to this post.
Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-10.0
Changelog for twrp-3.3.1-1-z3c-20191212-sar.img
Improved System as root support, /system is a symlink to /system_root/system now
Changelog for twrp-3.3.1-1-A10.0-z3c.img
Added Bootlogo, booting from offline state will display the original sony logo now instead of nothing
Fixed fastboot boot
Updated kernel cmdline from 23.5.A.1.291
How to install this build:
Reboot to fastboot by holding volume up while connecting your device to your computer
Open a terminal and move to the directory with TWRP in it
Rename the downloaded image to twrp.img
Type
Code:
fastboot flash recovery twrp.img
Boot into TWRP while the device is powered off press the power and volume down button
Feel free to ask questions or give feedback about TWRP here .
Have a nice day!
Additional information about the recovery on this device:
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse
The new build is up!
Get it from here: https://sourceforge.net/projects/ep...age-17.0-20191002-UNOFFICIAL-z3c.zip/download
Make sure to use the new TWRP from Post #2 because Android 10 introduces System-as-Root which can lead to weird behaviour in the old TWRP.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected, yet unlisted bugs.
MY personal hardware support list can be found here: https://gist.github.com/ArianK16a/1e46c463a5c910efb322d9cf0e16c3c0 but as always, i can't guarantee you anything!
Happy flashing!
I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/
hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out
NIce, thank you
hhpl said:
hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out
Click to expand...
Click to collapse
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
hhpl said:
I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/
Click to expand...
Click to collapse
There are GApps: https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/
NeoArian said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
Click to expand...
Click to collapse
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/
hhpl said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/
Click to expand...
Click to collapse
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.
NeoArian said:
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.
Click to expand...
Click to collapse
ok done, once again nothing new, still same situation
Can this ROM be installed on top of LineageOS 16 without wape?
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...
NeoArian said:
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...
Click to expand...
Click to collapse
No, I found a beta version on Google.
Gotta check again with the one you provided, I'll edit this post in a while
Edit: buttons don't work again
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy
hhpl said:
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy
Click to expand...
Click to collapse
The same basic steps you'll find in the OP
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
I've experienced the same issue after installing gapps - only back button works. Gesture navigation is working fine.
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)
Barciej33 said:
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)
Click to expand...
Click to collapse
You must read 1st to 3rd post.
LOS17 is just getting started.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected
Click to expand...
Click to collapse
@NeoArian Any chance for a screen recording of how it runs?
JamesMars said:
@NeoArian Any chance for a screen recording of how it runs?
Click to expand...
Click to collapse
No? If you are interested you can test it yourself.
I have my holidays now anyway.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're 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.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: excalibur
Maintainer/Authors build: @TheMalachite
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/TheMalachite/android_device_xiaomi_excalibur
Kernel: Prebuilt kernel from MIUI V11.0.2.0.QJXINXM
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by fastboot flash recovery.img
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Device Changelog
Code:
2020-07-30
- Initial unofficial release
PBRP Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Downloads
Flashable zip
https://drive.google.com/file/d/18MzNCTExOWLiu9ZUD3A7SXlD4QY2grrZ/view?usp=drivesdk
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the Redmi Note 9 Pro Max
Contributors
TheMalachite, Reza Adi, Shovon, Manjot Sidhu, Mohd Faraz, Sagar
Version Information
Status: Stable
Current Stable Version: 3.0.0
Stable Release Date: 2020-07-30
Created 2020-07-30
Last Updated 2020-07-30
Bugs: You tell me
Reserved #2
thank you sir..... for providing this recovery and opportunity to test your initial relese
Good but when other custom rom for redmi note 9 pro max
[email protected]@ said:
Good but when other custom rom for redmi note 9 pro max
Click to expand...
Click to collapse
When their will be dev who wanna build custom rom for it
Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...
Vijo123 said:
Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...
Click to expand...
Click to collapse
I am waiting for my bootloader time 133 hours provided by MI. I will flash and provide feedback on 13 August.
kannss said:
I am waiting for my bootloader time 133 hours provided by MI. I will flash and provide feedback on 13 August.
Click to expand...
Click to collapse
Ok. Never go back to 'Mi Unlock Status' under Developer Options to add ur device again...
I did that mistake and my wait time got reset to give me new wait time.
Also don't log out of Mi account or play with 'Find Device' settings.
U may know already. But im just saying..
If u face any driver related issues, then in the Mi Unlock Tool itself, they have provided a way to install it, if u check their settings...
Good Luck
Vijo123 said:
Flashed it via fastboot from Platform Tools folder. Rebooted into recovery mode. And Pitch Black was installed successfully. Then transferred the pitchblack zip folder to sd card. And installed it through pitchblack. Rebooted to system.
After the system reboot, again switched off phone and entered recovery mode, only to find that the pitchblack was overwritten by system recovery.
tried wiping data second time, after installing pitchblack. Again it was overwritten by system recovery.
Do I need to do any additional steps within pitchblack, before rebooting to system?
Or install any ROM?
My final aim is to install LineageOS, which currently isn't available for this devise..
Any help is greatly appreciated...
Click to expand...
Click to collapse
Enable DM VERITY
MaheshTechnicals said:
Enable DM VERITY
Click to expand...
Click to collapse
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?
I'm on rooted (magisk), device with xposed installed and working BUT stock recovery. waiting for you to successfully stick the tarp and I'll follow. Kindly keep updating results and steps tried by you.
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
Vijo123 said:
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?
Click to expand...
Click to collapse
I'm on rooted (magisk), device with xposed installed and working BUT stock recovery. waiting for you to successfully stick the tarp and I'll follow. Kindly keep updating results and steps tried by you.
I'm currently using SD Maid app (Pro version) to remove all unnecessary bloatwares. Works like a charm.
And IMO, also works better than Termux or any other debloater. Although debloating is just one of the function of termux, but if u r using it just to debloat, then better go for SD Maid ?
UPDATE : i installed as per instructions for installation from PC, first recovery.img and then flashed whole zip. Worked great. after rebooting device twice manually,, recovery sticks,, and its a great one. excellent work done.
just one question, what does magisk manager installation in recovery do ? (Specials>tools>magisk manager)
coolvipcandy said:
UPDATE : i installed as per instructions for installation from PC, first recovery.img and then flashed whole zip. Worked great. after rebooting device twice manually,, recovery sticks,, and its a great one. excellent work done.
just one question, what does magisk manager installation in recovery do ? (Specials>tools>magisk manager)
Click to expand...
Click to collapse
Did u wipe data or dalvik etc. Because mine got overwritten by system recovery.
Can u please tell how did u do, STEP BY STEP?
Maybe my adb fastboot tools were outdated??
Vijo123 said:
Will it keep PB Recovery form overwritten?
Because, ppl try to disable DM verity, so im asking.
Also, I managed to root my Pro Max using Magisk manager. But a lack of custom recovery always hurts.
So how do i Enable DM verity now?
Click to expand...
Click to collapse
Vijo123 said:
Did u wipe data or dalvik etc. Because mine got overwritten by system recovery.
Can u please tell how did u do, STEP BY STEP?
Maybe my adb fastboot tools were outdated??
Click to expand...
Click to collapse
i did as mentioned in first post,, as i was already root, i first flashed recovery.img and then from recovery, flashed the whole zip archive. thats all.
then.booted to system,, again booted manually to recovery and it was there,, and checked twice again, recovery was there.
---------- Post added at 05:25 AM ---------- Previous post was at 05:24 AM ----------
i didnt mess with dm verity,,
Working fine in my device. Successfully rooted and installed Edxposed. Everything working fine.
how to wipe "system" partition, there's no option for that ??
wipe > Advance > ???
Format data option
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
Do not install inbuilt magisk from this recovery. It gives bootloop, download from github or xda and flash zip manually
Stuck on fastboot mode
PLEASE HELP
i installed twrp recovery in my redmi note 9 pro max and install magisk , now my device is stuck on fastboot.
---------- Post added at 05:22 AM ---------- Previous post was at 05:18 AM ----------
kannss said:
Working fine in my device. Successfully rooted and installed Edxposed. Everything working fine.
Click to expand...
Click to collapse
bro when i installed i got stuck in fastboot
what should i do now ...? should i install custom rom or not