{
"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"
}
Requirements:
Unlocked Honor 7x : See this [But don't flash twrp from anywhere else before backing up your device. Use twrpimgmount_ramdisk for backing it up first.]
Download:
TWRP Complete Backup
TWRP Img mount not tested yet
Instructions:
Flash twrpimgmount_ramdisk.img through fastboot
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
Press and hole both volume + power on to boot to erecovery OR volume up + power on to boot to twrp (i don't know which combination is of which one) i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Backup/restore and flash image functions are tested for system/vendor/product/version/cust/oeminfo/recovery/recovery2/boot rest of them are not tested by me but should work.
Note: It is suggested to make a complete backup in memory card before rooting your Honor 7x.
After backing up, flash TWRP Complete Backup Ramdisk
Join Telegram group if you are willing to test latest stuff
Credits:
Ported form Honor 6x : OP
Follow next:
1. Flash Magisk 16.0+ to root
XDA:DevDB Information
[OREO]TWRP COMPLETE BACKUP, Tool/Utility for the Honor 7X
Contributors
Sudeep Duhoon, Pretoriano80, zxz0O0
Version Information
Status: Testing
Created 2018-03-17
Last Updated 2018-04-07
For Nougat : Go Here
Reserved
TWRP on my OREO Beta Not Detecting My Phone on Pc no Response Please Check Ur Recovery
Can I do this with the Bnd-L24 model that has the bootloader unlocked with TWRP installed?
Great bhai
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Sudeep Duhoon said:
Computer doesn't see phone via USB - Known bug
TWRP reports "no OS installed" - Intentional, it has to work like this.
TWRP cannot read /sdcard (internal storage) - Your internal sd is encrypted and this twrp has no decryption support
Click to expand...
Click to collapse
one further note, using the "complete_twrp_ramdisk.img" TWRP was able to see the installed OS, and offered to install the TWRP app.
Sudeep Duhoon said:
i suggest you to flash twrp to erecovery_ramdisk partition using twrp too.
Click to expand...
Click to collapse
What does this mean?
---------- Post added at 10:08 AM ---------- Previous post was at 09:36 AM ----------
I couldn't get it to backup. It always fails at data or system (If I don't select data).
Tried both images.
how can i flash the stock recovery? i was able to brick my device
Edit: nvm i fixed it
topnomi said:
I was able to get twrp booted, but had issues backing up system & data
its mentioned elsewhere, but i didn't see mentioned here. this twrp is unable to read the /sdcard partition (internal storage), so you have to use a microsd card (external_sdcard).
My Process: (BND-L24 USA Honor 7x Oreo)
in bootloader:
Code:
fastboot flash recovery_ramdisk twrpimgmount_ramdisk.img
then reboot phone into recovery by holding both volume buttens + power
(i guess the ramdisk is loaded instead of the stock recovery)
once in twrp, i backed up the MANY partitions to my microsd card.
the backup failed for 2 partitions:
1) Data
Code:
createTarFork() process ended with ERROR: 255
2) System
failed at 87%, no error in the backup log, however the log was speckled with
Code:
unable to find partition for path '/system'
UPDATE: i was able to backup system using the file "complete_twrp_ramdisk.img" attached to this thread.
Other notes regarding this TWRP:
Computer doesn't see phone via USB
TWRP reports "no OS installed"
TWRP cannot read /sdcard (internal storage)
I look forward to trying future versions, and would be happy to help test things on my device if devs don't have this specific model.
Click to expand...
Click to collapse
Hi, I'm glad to report that although the first recovery that is twrpimgmount_ramdisk.img failed to backup system as I got the same error message as above but I was able to flash some other partitions like kernel, recovery etc... I actually selected a bunch of them.
Anyway most importantly after flashing the complete_twrp_ramdisk.img, I was able to backup system successfully. I'm using the Indian variant BND AL10 MODEL. I hope this helps some one out there.
I have a dumb question: Now, that the system is backed up with twrp, if I mess up my phone ever, can I simply restore this system img and be able to boot back into the os? Do I need to install any other partitions? I don't care about data. Please let me know.
Hi, I flashed this complete_twrp_ramdisk.img and now I want to go back to stock recovery of oreo which is bnd_recovery_nocheck.img from the other post. I tried using adb and it fails. I tried using the this twrp but it shows a lot of partitions to choose from and I'm confused example: ramdisk recovery, recovery_vendor, recovery_ramdisk etc... there are sooooooo many. I tried recovery_vendor and also ramdisk but it doesn't work. Can you please tell me how to install the stock recovery?
Does anybody have a BND-L21 backup of the system partition?
Edit: nvm i found it
Can someone tell me how to install stock recovery after installing the above complete_twrp_ramdisk.img as I'm unable to flash using adb. I tried "fastboot flash recovery recovery.img" and also "fastboot flash recovery_ramdisk recovery.img" I tried flashing the BND_recovery_nocheck.img from the other post which is a stock one.
I also tried flashing it using this twrp to the partition recovery_ramdisk and gives the error saying "the size is larger than the device" Please someone help.
I have tried couple times to install new release
twrp_ramdisk_oreo_7-4-18.img
Click to expand...
Click to collapse
But I can only get to twrp splash screen.
OP change-log has no information about this new release, so maybe is still not ready.
telegram group has mention of this , but did not help Yet.
**EDIT**
It was suggested by DEV in telegram to just be patient and try again. This third time installed 4-7-2018 released version it loaded right into recovery, without any delay.
Don't know if it is coincidence or not but before I was on RRos ROM. and now I am back on EMUI 8
Well, the mess here you have gentlemen, nichrome you do not understand where the root for 7ku, where to 8ku, what tvrp to put for 8ki for everyday needs.
---------- Post added at 03:56 PM ---------- Previous post was at 03:52 PM ----------
Which TWRP can I put in order to flush the root on the 8th oreo?
What TWRP should I be using on RROS Room? In order to install Magisk?
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
darkmage1991 said:
what are the 2 images with dates for? twrp_ramdisk_oreo_19-4-18.img and twrp_ramdisk_oreo_7-4-18.img?
i tried flashing both in twrp after using fastboot to flash the inistial ramdisk and neither one boot into recovery they get stuck at the twrp splash screen but the image labeled complete_twrp_ramdisk.img boots fine.
Click to expand...
Click to collapse
Afaik they are test builds (ports) of data decryption enabled twrp.
I had them working when on the Oreo beta but cannot get to work on RR or the new official Oreo.
Related
{
"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"
}
Bismillahi Alrahmani Alraheem
(in the name of God the most gracious, the most merciful)
Finally Unoffoicial TWRP 3.0.2 is here for Dual sim version of XPERIA Z3 (D6633)!!
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
And much more...
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit Instance - http://gerrit.omnirom.org
Notes About Sony Devices:
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility. The source for this utility is here:
https://github.com/Dees-Troy/extract_elf_ramdisk
This utility is designed to work in conjunction with the current methods that most AOSP ROMs use for the ramdisk and can also be used on stock kernels. This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. Most AOSP based ROMs like OmniROM or CyanogenMod will support this method. Some stock kernels may also support the FOTAKernel method.
What does all this mean? It means that TWRP may not work on your device unless you install other custom software as well. Check with your ROM developer to see what they support.
DOWNLOAD:
Please notice that it won't work in stock based roms, only custom roms will run it
20160907 (img)
20160907 (zip)
Installation methods
TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/recovery-twrp-302-z3dual.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Fastboot method:
you should have fastboot in your pc (either downloaded separately or with android SDK)
fire up Terminal (Linux and OS X) or CMD window (MS Windows) in the folder you have the image on it and it is preferred to copy the image to the folder of fastboot so the following command work then type:
Code:
fastboot flash FOTAKernel recovery-twrp-302-z3dual.img
don't forget to put ./ before 'fastboot' if you are using OS X or linux (./fastboot)
ZIP method:
flash the zip using any recovery
Themes and colors:
HERE
(Read Post #2 in the link if you want to customize, I'll be making pre-made themes later on inshaaAllah (God willing) )
NOTE: You are free to repack it and even sharing it without taking my permission
Please Donate If you want me to support Z3 dual more and more, it is back to you
XDA:DevDB Information
TWRP 3.0.2 for Z3 Dual D6633, Tool/Utility for the Sony Xperia Z3
Contributors
Muhammad Ashraf
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Testing
Created 2016-06-25
Last Updated 2016-09-07
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
sorry for the late reply, I am not sure why does it act like that
i'll try to make a zip file for that issue
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Oh, I am SOOOOOOOO Sorry, You have noticed me, By mistake I have uploaded Cyanogenmod Recovery instead of twrp
figuring that out now
I am sorry all of you
thanks man
EDIT: DONE
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Unlocked or Locked bootloader?
(Does this require an unlocked bootloader?)
I cannot get to recovery mode using DD or fastboot
Command will go through but adb reboot or h/w combos wont get me recovery. How do I install recovery ? . I have a ROM that can only be installed via recovery pl help
I cannot get to recovery mode using DD or fastboot
FAILED (remote: Command not allowed)
it always says "FAILED (remote: Command not allowed)"
should the bootloader be unlocked ?!
what is the problem here?!
Hi, i flashed the .img using my twrp, the only option on "select partition" was kernel, i know i shouldn't have done it, but i did. Now the phone doesn't boot, it keeps on a black screen. I think i need to flash a new kernel, can someone help me? Thanks
edit
Locked bl
Excellent WORK +++++
Bismillahi Alrahmani Alraheem YOU are my god!
Well done. You are the man. Exellent work with this TWRP for my D6633 (z3 dual)
it saved my life!
bryantshurley said:
I cannot get to recovery mode using DD or fastboot
Click to expand...
Click to collapse
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
"fastboot flash boot recovery-twrp-302-z3dual.img" got me to a new recovery screen and can no longer boot the system.
rzepek2pl said:
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
Click to expand...
Click to collapse
That was a bad advice. Now I only have TWRP on my phone. Only boots into this!
Can it be saved? How?
Your 20160907.zip based on TWRP 3.0.2 was put into root & flashed with TWRP v2.8.7.0 which did not update, when re-launching recovery I was still on v2.8.7.0
{
"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 Mate 8 (NXT)
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-next.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_next/releases/download/3.1.1-1/twrp-3.1.1-1-next.img"][U]download twrp-3.1.1-1-next.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 10. June 2017
Q: which Mate 8 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][3.1.1-0][MATE 8][DECRYPTION SUPPORT], Tool/Utility for the Huawei Mate 8
Contributors
OldDroid, XePeleato, surdu_petru
Source Code: http://ttps://github.com/OpenKirin
Version Information
Status: Stable
Created 2017-04-08
Last Updated 2017-06-11
Reserved
TWRP 3.1.0-1 next for encrypted/ decrypted data
This post has been deplaced here. I'll remove it when the TWRP above will work for encrypted/ decrypted data.
Thanks for comprehension!
I'm glad, that we can help the Mate 8 community
Thanks for distribution ...
The themes are here now.
Thanks!
Thak you very much.
I have your "Boot_Insecure_B560_Fix-adb_dm-verity.img" installed. Do you recomend to go back to stock boot and use this TWRP for any flashing? Or shoud i stay in a insecure boot?
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Us there 2 differnt versions of this twrp 1 for decripted data and 1 for formated data ??
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
We can see what we can do with the both. A merger is perhaps possible?!
Edit:
Already it works with untouched boot.
With no formatted datas, it seems to me.
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
franzyroy said:
We can see what we can do with the both. A merger is perhaps possible?!
Edit:
Already it works with untouched boot.
With no formatted datas, it seems to me.
Click to expand...
Click to collapse
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads : twrp-3.1.0-next-v2.img md5 : 7ee1833ea51bf3835efc23851ad9a011
surdu_petru said:
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads :twrp-3.1.0-next-v2.imgmd5 : 7ee1833ea51bf3835efc23851ad9a011
Click to expand...
Click to collapse
It seemed to me that dexz had tested it like that.
If I can test it, I'll do it. In the week, it's not really possible for me. @dexz should can do it.
jac10000 said:
Sorry but this twrp have not decryption support.
Have you test it on Mate 8 with no formated datas ? and boot with no disabled encryption ? with untouched boot ?
On my mate 8 with encrypt datas it don't work
I don't see my internal sdcard
But I take this twrp and I changed some parameters and it work fine for me .
TWRP-3.1.0-0_Decrypt_Mate-8.img
But it must be used on really encrypt datas, not formated .
I flash suspersu on an untouched boot and system and I'm root .
Click to expand...
Click to collapse
With the TWRP here, the root works too.
surdu_petru said:
Thank you very much for your test
As I can see it's working for decrypt unmodified /data if mount point to /dm-0 ...
I make a new TWRP, but should be tested in the same conditions like @jac10000 !
Also, please @jac10000, if you can test my new release to see if it decrypt /data , thanks !
EDIT :
Please, @franzyroy - you should test TWRP with unmodified data, so if your data was modified by wipe or format, you should restore device to Stock Huawei Firmware N by /dload/UPDATE.APP method . Thanks !
Downloads :twrp-3.1.0-next-v2.imgmd5 : 7ee1833ea51bf3835efc23851ad9a011
Click to expand...
Click to collapse
The one I tested and working yesterday was with /dm-0 before you posted another version.
Anyway twrp-3.1.0-next-v2.img is working fine and decrypted. Using adb shell mount. it show /data is on /dev/block/dm-5 the same with the one I have tested before.
Edit : I got force reboot using twrp-3.1.0-next-v2 after 5 seconds
Edit2 : It's only stop force reboot when I got the "Unmodified System Partition" screen.
Edit3 : I see force reboot stop if there's no changes on twrp setting (example time zone, language & etc)
@surdu_petru
Yes I just test it this twrp-3.1.0-next-v2.img and like @dezx I have force reboot when I use TWRP File Manager
dexz said:
The one I tested and working yesterday was with /dm-0 before you posted another version.
Anyway twrp-3.1.0-next-v2.img is working fine and decrypted. Using adb shell mount. it show /data is on /dev/block/dm-5 the same with the one I have tested before.
Edit : I got force reboot using twrp-3.1.0-next-v2 after 5 seconds
Edit2 : It's only stop force reboot when I got the "Unmodified System Partition" screen.
Edit3 : I see force reboot stop if there's no changes on twrp setting (example time zone, language & etc)
Click to expand...
Click to collapse
jac10000 said:
@surdu_petru
Yes I just test it this twrp-3.1.0-next-v2.img and like @dezx I have force reboot when I use TWRP File Manager
Click to expand...
Click to collapse
Perhaps you should make that and send the console.recovery.log to @surdu_petru or @OldDroid because if they have made the TWRP with mine, it's perhaps the cause.
@surdu_petru
---->logs
Thanks guys for feedback
I'll upload a new version very soon, hope will fix reboot issues !
I say that because :
I have no issues with a prerooted boot
It's also with Decrypted data boot
I can install a zip without to see an error
I see the internal storage
I can also see the size, not 0 MB
Only thing which doesn't work fine, when I mount the data, it's unmounted in the 5 seconds.
surdu_petru said:
Thanks guys for feedback
I'll upload a new version very soon, hope will fix reboot issues !
Click to expand...
Click to collapse
Thank you. Looking forward to it.
Sorry I'm out of like bullet :laugh:
New Test Version 3 !
Downloads : twrp-3.1.0-next-v3.img md5 : d969789ee06d3d323a98d9f028e6f475
Thank you for the feedback
TWRP RECOVERY FOR GALAXY J7 PRIME
{
"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"
}
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.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR BRICKS. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Instructions:
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
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 + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP 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.
DOWNLOADS:
twrp3.1.0-0
Use Odin to flash.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot to if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery. If you choose to 'Allow' then SuperSU needs to be flashed to disable dm-verity.
To Root:
Flash the latest SuperSU:
http://www.supersu.com/download#zip
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
(Note this MUST be flashed before 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 modded kernel from below.
5. Reboot
Modded Kernel:
https://mega.nz/#!tJ5XVa4I!_kMCzV7kOMvEdvJwB3ZUDPZjGUNIuuzK6RSLHMiZG4M (Thanks to maxx35000)
NOTE: NO NEED TO FLASH MODDED KERNEL IF YOU ARE USING ANY CUSTOM ROM
HIT THANKS IF I HELPED YOU:good:
is this oficial ?
Mounting internal is working?
Not work on last update from samsung, with update AQC4 recovery not incompatible
Janeslejade said:
Mounting internal is working?
Click to expand...
Click to collapse
Yes. Read the thread on how to do this.
hoangphuc057 said:
Not work on last update from samsung, with update AQC4 recovery not incompatible
Click to expand...
Click to collapse
It's working. I'm on AQC4
Not working on G610Y.
---------- Post added at 09:23 AM ---------- Previous post was at 09:11 AM ----------
Guys, i want to go back to stock recovery, questions.... Is it safe to flash this stock recovery??
SM-G610F/M_stock_recovery
My unit is G610Y.
Up... Please help, i need the SM-G610Y_stock_recovery... Please someone help or advise if SM-G610F/M_stock_recovery is okay to flash on G610Y??
Help guys! I tried to root my phone but no success. It says need adb 1.3 or newer. What should i do?
External sd mounting?
Thanks for the update, working on G610M
4. Install modded kernel from below.
Click to expand...
Click to collapse
how to do this?
Ephesis said:
how to do this?
Click to expand...
Click to collapse
Flash through odin in AP
Siddhant NAik said:
Flash through odin in AP
Click to expand...
Click to collapse
how about rooting? flash via odin too?
---------- Post added at 09:52 AM ---------- Previous post was at 09:40 AM ----------
Flash through odin in AP
Click to expand...
Click to collapse
Odin wont read it since its a zip file not a tor file.
inamie said:
External sd mounting?
Click to expand...
Click to collapse
This is the essential question!
thank
trinaldi said:
This is the essential question!
Click to expand...
Click to collapse
not working.
Anyone tried this on G6100 ?
Please update aqc4 mod kernel
Thank you bro. Haha :d :d
{
"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"
}
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.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR ANY DAMAGE CAUSED. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
FULL STEPS TO INSTALL TWRP
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
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 + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP 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.
FEATURES
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
ADB Sideload
Full SELinux support
Built in android 6.0 tree
Mount Ext Sd Card
To root with SuperSU:
Download the latest SuperSU by Chainfire.
Flash it through TWRP. If you can't mount internal storage, use ADB SIDELOAD or OTG instead.
Go to [Reboot] -> [System].
To mount Internal Storage
Download the Modded Kernel from the link below.
Flash through Odin in AP.
Boot into TWRP and FORMAT /data.
Downloads
SuperSu
TWRP-3.1.1
Modded Kernel
Bugs
MTP
Device Tree: https://github.com/Siddhant-Naik/android_device_samsung_on5xelte
HIT THANKS IF I HELPED YOU
Siddhant NAik said:
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.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR ANY DAMAGE CAUSED. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
FULL STEPS TO INSTALL TWRP
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
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 + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTEN 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.
FEATURES
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
ADB Sideload
Full SELinux support
Built in android 6.0 tree
Mount Ext Sd Card
To root with SuperSU:
Download the latest SuperSU by Chainfire.
Flash it through TWRP. If you can't mount internal storage, use ADB SIDELOAD or OTG instead.
Go to [Reboot] -> [System].
To mount Internal Storage
Download the Modded Kernel from the link below.
Flash through Odin in AP.
Boot into TWRP and FORMAT /data.
Downloads
SuperSu
TWRP-3.1-0
Modded Kernel
Bugs
MTP
Device Tree: https://github.com/Siddhant-Naik/android_device_samsung_on5xelte
HIT THANKS IF I HELPED YOU
Click to expand...
Click to collapse
Did you build it from source?
Siddhant NAik said:
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.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR ANY DAMAGE CAUSED. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
FULL STEPS TO INSTALL TWRP
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
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 + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP 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.
FEATURES
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
ADB Sideload
Full SELinux support
Built in android 6.0 tree
Mount Ext Sd Card
To root with SuperSU:
Download the latest SuperSU by Chainfire.
Flash it through TWRP. If you can't mount internal storage, use ADB SIDELOAD or OTG instead.
Go to [Reboot] -> [System].
To mount Internal Storage
Download the Modded Kernel from the link below.
Flash through Odin in AP.
Boot into TWRP and FORMAT /data.
Downloads
SuperSu
TWRP-3.1.1
Modded Kernel
Bugs
MTP
Device Tree: https://github.com/Siddhant-Naik/android_device_samsung_on5xelte
HIT THANKS IF I HELPED YOU
Click to expand...
Click to collapse
thanks sir, work in my j5 prime
Sent from my SM-G570Y using Tapatalk
---------- Post added at 11:11 AM ---------- Previous post was at 10:50 AM ----------
i already install,
but, i cant install from internal..
& i try to backup my rom, but failed..
please sir, fix this...
thanks before
Sent from my SM-G570Y using Tapatalk
fahri01 said:
thanks sir, work in my j5 prime
Sent from my SM-G570Y using Tapatalk
---------- Post added at 11:11 AM ---------- Previous post was at 10:50 AM ----------
i already install,
but, i cant install from internal..
& i try to backup my rom, but failed..
please sir, fix this...
thanks before
Sent from my SM-G570Y using Tapatalk
Click to expand...
Click to collapse
Flash the modded kernel
Any grace ux rom
Gautham Asir said:
Any grace ux rom
Click to expand...
Click to collapse
not yet, does my injustice rom flash with new TWRP??
I will try to flash
Unable to flash since it failed
Who knows if Recovery worked?
Screenshot
Twrp is working fine except data and mtp
It does not receive the machine memory and resets it when it is not set
Is normal that the custon kernel take too much time to install? odin freezes in:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
Please revise any flash files to reboot
Dont flash kernel
use advance wipe
select data partion
click on repair
th format it using ext 2 or other
boom data will be mounted
thanks :3
Very good work. No problems on SM-G570M
Nothing else MTP and data
Thanks for making it possible I've been waiting for TWRP for some time.
TheFlash said:
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.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR ANY DAMAGE CAUSED. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
FULL STEPS TO INSTALL TWRP
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
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 + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP 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.
FEATURES
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
ADB Sideload
Full SELinux support
Built in android 6.0 tree
Mount Ext Sd Card
To root with SuperSU:
Download the latest SuperSU by Chainfire.
Flash it through TWRP. If you can't mount internal storage, use ADB SIDELOAD or OTG instead.
Go to [Reboot] -> [System].
To mount Internal Storage
Download the Modded Kernel from the link below.
Flash through Odin in AP.
Boot into TWRP and FORMAT /data.
Downloads
SuperSu
TWRP-3.1.1
Modded Kernel
Bugs
MTP
Device Tree: https://github.com/Siddhant-Naik/android_device_samsung_on5xelte
HIT THANKS IF I HELPED YOU
Click to expand...
Click to collapse
hi
how to flash modded kernel by odin or twrp ?
Cannot flash modded kernel
Wait for some GraceUX ROM
andro_harsh said:
cannot flash modded kernel
Click to expand...
Click to collapse
extract it and flash the img from twrp and format data
boom internel will be mounted
{
"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"
}
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: twrp-montana-3.2.3.0.img
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (14542 KB)...
OKAY [ 0.460s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.270s]
finished. total time: 0.730s
Select recovery using the volume keys and power button to select.
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Code:
./ fastboot flash recovery recovery.img
Source Code:
Github
Contributors
@teamwin @sohamlad7 @GoldeneyeS2 @lohanbarth
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.3-0
Stable Release Date: 2018-10-08
Created 2018-07-05
Last Updated 2018-10-08
I think i have found a error. Cant decrypt files. TWRP from Squid a could do that. Your TWRP gives failed password error with correct password.
lohanbarth said:
Requirements
Unlocked bootloader
Fastboot drivers installed on PC
Instructions:
Download the TWRP image here: LINK
Rename the downloaded img file recovery.img
Put phone into fastboot mode (hold vol down + power button).
Connect phone to PC.
Open a command prompt where you have fastboot and the TWRP image file located.
Type the following in command prompt (recovery.img is the name of your twrp img you downloaded & renamed).
Code:
fastboot flash recovery recovery.img
Normal output:
Note for Windows 10 users who use the powershell and not cmd
The command will become:
Source Code:
Github
Contributors
@[email protected]@[email protected]
Version Information
Status: Stable
Current Stable Version: TWRP 3.2.2-0
Stable Release Date: 2018-07-05
Created 2018-07-05
Last Updated 2018-07-05
Click to expand...
Click to collapse
Support on Arm64 rom's?
Adamask said:
I think i have found a error. Cant decrypt files. TWRP from Squid a could do that. Your TWRP gives failed password error with correct password.
Click to expand...
Click to collapse
go to wipes and click on data format.
rssxda said:
Support on Arm64 rom's?
Click to expand...
Click to collapse
Yes
twrp 3.2.3 in op.
after wipe data and reboot the phone twrp is not there
Cesarcami53 said:
after wipe data and reboot the phone twrp is not there
Click to expand...
Click to collapse
it's normal you have to flash a .zip file so that it stays
Where is the twrp zip..??
Hello ! guys ... I'm without pc can I flash it for this app?
zanduo said:
Hello ! guys ... I'm without pc can I flash it for this app?
Click to expand...
Click to collapse
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
lohanbarth said:
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
Click to expand...
Click to collapse
I have root and twrp and bootloader .... the problem and that I am without pc ...
---------- Post added at 03:50 PM ---------- Previous post was at 03:27 PM ----------
lohanbarth said:
if the twrp application does not work, used flasify, you have to be root and have the bootloader unlock
Click to expand...
Click to collapse
Thanks man i use flasify And Works! Thanks ! Now i waiting for 64 roms
I have another problem. I managed to flash the recovery.img sucessfully (as described) and I can start TWRP. It functions properly, however every time I do a backup (not recovery!) after reboot the TWRP is gone.
How is that possible? Why the recovery partition gets overwriten or damaged by a simple backup?
How do I permanently flash the recovery partition with TWRP without need to reflash it every time?
RuKlowd said:
I have another problem. I managed to flash the recovery.img sucessfully (as described) and I can start TWRP. It functions properly, however every time I do a backup (not recovery!) after reboot the TWRP is gone.
How is that possible? Why the recovery partition gets overwriten or damaged by a simple backup?
How do I permanently flash the recovery partition with TWRP without need to reflash it every time?
Click to expand...
Click to collapse
flash a .zip file (magisk or a custom rom) to fix it
ur backup gets the original recovery of stock rom.. then, if u recovery u lost the twrp, but, if u recovery and reinstall twrp from twrp for .img, u dont lose him..
lohanbarth said:
flash a .zip file (magisk or a custom rom) to fix it
Click to expand...
Click to collapse
Thanks, it worked! So the recovery partition won't really (permanently) flash unless you root the device, right? Do I always need to root to permanently flash any other partition, too?
ilovepanda said:
ur backup gets the original recovery of stock rom.. then, if u recovery u lost the twrp, but, if u recovery and reinstall twrp from twrp for .img, u dont lose him..
Click to expand...
Click to collapse
Sorry, I had difficulties to understand you :/
if you make a backup, the backup will also add the recovery stock, so when restoring, it will also restore the backup of the recovery stock, it would be better to install the stock and before the first boot, install the twrp via .img
is this recovery only fot the xt1792, or can i also use it for the xt1794 ?
PhoenixGamer said:
is this recovery only fot the xt1792, or can i also use it for the xt1794 ?
Click to expand...
Click to collapse
You can