Unofficial release -TWRP recovery for the Galaxy J7- SM-J700T/T1, Exynos7580
{
"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"
}
Update 20/11/2017
TWRP 3.1.1-1 NN build released.
Update 20/2/2017
TWRP 3.0.3-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
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 3.10.7 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 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.
NOUGAT DOWNLOAD:
twrp_3.1.1-0_sm-j700t_201117
MARSHMALLOW DOWNLOAD:
twrp_3.0.3-1_sm-j700t_23217
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
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
Credits: Me, @slipk487, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.
Bootlooped on my j700t1
slipk487 said:
Bootlooped on my j700t1
Click to expand...
Click to collapse
Is your firmware up to date, the kernel is built using the latest sources?
i believe im fully updated
slipk487 said:
i believe im fully updated
Click to expand...
Click to collapse
Seems so, would you be willing to be contacted via PM?
I'm fairly sure this is a kernel issue and would like to PM you links to test builds.
ye no problem. that was the stock kerenrl i have yet to try it on mira kernel.
slipk487 said:
ye no problem. that was the stock kerenrl i have yet to try it on mira kernel.
Click to expand...
Click to collapse
Shouldn't really matter which boot kernel is being used. P.M sent
Thank you for this! Can't wait for the working build.
vekenti said:
Thank you for this! Can't wait for the working build.
Click to expand...
Click to collapse
We have it working, hopefully there will be an update at some point today.
Thanks for being involved in this. I hope to donate soon.
Just updated to this phone on metropcs prepaid 4 days ago..from a Samsung galaxy s4..
I like it, but I'm noticing some things I still need.
I'll message you soon ash, just to let you know I've donated via paypal
I'll test for you ash.
Metabolic12 said:
I'll test for you ash.
Click to expand...
Click to collapse
I will also test. J700T.
Metabolic12 said:
I'll test for you ash.
Click to expand...
Click to collapse
Dustinsk22 said:
I will also test. J700T.
Click to expand...
Click to collapse
Fixed build up: https://forum.xda-developers.com/ga...y-galaxy-j7-sm-j700t-t1-t3560342/post71151450
.
ashyx said:
Fixed build up: https://forum.xda-developers.com/ga...y-galaxy-j7-sm-j700t-t1-t3560342/post71151450
.
Click to expand...
Click to collapse
Darn in have to wait until I'm home to flash. Unless flashfire will work? If I had my other phone I would just do it.
Dustinsk22 said:
Darn in have to wait until I'm home to flash. Unless flashfire will work? If I had my other phone I would just do it.
Click to expand...
Click to collapse
You can extract the recovery.img from the tar archive and flash with twrp or flash the tar archive with flashfire.
ashyx said:
You can extract the recovery.img from the tar archive and flash with twrp or flash the tar archive with flashfire.
Click to expand...
Click to collapse
I'm booting to recovery now. If I'm not back in 10 or less, assume this J7 turned into a radioactive tornado and wiped Indiana off the planet.
Metabolic12 said:
I'm booting to recovery now. If I'm not back in 10 or less, assume this J7 turned into a radioactive tornado and wiped Indiana off the planet.
Click to expand...
Click to collapse
Oh gee, looks like Indiana got wiped
ashyx said:
Oh gee, looks like Indiana got wiped
Click to expand...
Click to collapse
If only it was that easy, I even put my full body suit on :cyclops:
Full boot running on bootloader APK6. TWRP boots and mounts all available partitions. I'll test USB in a little bit when I get home. Congrats brother and thank you.
We have twrp and good boot. Thnx for this again and again.
I dont suppose someone could post a recovery log from TWRP so I can look it over?
ADVANCED>SAVE RECOVERY LOG
Related
If someone wants to make mirrors or a flashable zip, feel free to contact me and I will update thread
I've got my new OP3 today and what I've noticed that it runs with Oxygen OS 3.2.5. So I have looked around and saw that nobody backed up their 3.2.5 und uploaded it so I decided to do it.
Here is the download link: https://mega.nz/#!PJhzRDyL!wX12zmq9ptiu8gNbtfQfypB2Q6wGdu3IfNFFwi9acQk
The only requirement is an unlocked bootloader as fastboot doesn't allow to flash on locked devices
How to install:
via twrp:
- boot into twrp recovery
- press "install"
- press "install image" on the bottom right
- select the image and confirm on which partition it should flash
(not recommended) via fastboot:
- boot into fastboot
- use these commands to flash it:
ignore the little warning message and pe patient because it can take a while till you get a response from cmd because fastboot splits the image into 6 parts
Code:
fastboot flash boot boot.img
fastboot flash system system.img
Note: if your phone isn't booting, flash supersu and it should boot.
screenshots:
{
"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"
}
Fastboot flashing is not working.
Can you comment on the LTE reception and performance? It was the only issue i had with 3.2.4
Anyone tried looks tempting
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
TWRP is working, fastboot not.
Im on 3.2.5 now so yes its working, but only with TWRP
*Extracted fine with newest winrar*
Error on my end, sorry, thank you!
Chronzy said:
@hellcat50 zip is corrupt, "unexpected end of archive" when I tried to extract the img's. Downloaded it twice. Don't recommend wiping and trying to install at this time.
Would love to have this though, would you mind repacking?
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
you were able to extract the imgs? I downloaded it twice and got corrupt zip both times.
Click to expand...
Click to collapse
It did extract without any issues on my end.
I downloaded and extracted the file on my PC with the latest winrar.
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!
So, I will not lose my data, right?
No, but you should still do a backup in TWRP.
AcmE85 said:
No, but you should still do a backup in TWRP.
Click to expand...
Click to collapse
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)
Andrea224 said:
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)
Click to expand...
Click to collapse
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.
AcmE85 said:
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.
Click to expand...
Click to collapse
Mmh...ok, thanks anyway.
So basically you should have unlocked bootloader, supersued, and TWRP'ed
Reconfigured said:
So basically you should have unlocked bootloader, supersued, and TWRP'ed
Click to expand...
Click to collapse
SuperSU is not needed, why should it be? With this you overwrite the whole System partition, thus removing all mods including SuperSU and Xposed.
waiting for someone to confirm the LTE issue resolution.. if it's resolved, I'll flash this ASAP..
AcmE85 said:
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!
Click to expand...
Click to collapse
Pick your brain for a moment if you don't mind...
Still having issues with both methods... in TWRP, at the install image screen i'm only getting boot and recovery partition options, supposed to have system too right?
Fastboot it hangs for a moment at an error of something about invalid sparsing but continues to flash, apparently successfully, but when i reboot system it just boots back to recovery.
Chronzy said:
Pick your brain for a moment if you don't mind...
Click to expand...
Click to collapse
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
Can we directly flash it over 3.2.4 in twrp ?
Any differences with the previous version guys?3.2.4....Tnx!!
AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
I was on an older recovery, should have known... that did it, Thanks! :good:
{
"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"
}
Enjoy Your Asus Zenwatch 3-Swift-AND-FEEL THE SPEED
Please read the instructions and notes before flashing anything.
Code:
###Disclaimer###
I am not responsible if your phone will be damaged, broken, boot looping. YOU are choosing to make these modification.
WARNING:
IMPROPER FLASHING MAY POTENTIALLY BRICK YOUR DEVICE. SO PLEASE PROCEED AT YOUR OWN RISK. ME OR ANY OTHER DEVELOPER MENTIONED IN THIS POST WILL ASSUME NO RESPONSIBILITY FOR THIS.
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF WHISKY
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE ME HERE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
Requirements
- An unlocked bootloader
- adb and fastboot drivers
- TWRP recovery
You can download adb and fastboot package from here. https://developer.android.com/studio/releases/platform-tools.html#download
--------------------
HOW TO FLASH THE ROM
0- Attach your devices to your PC and enable USB Debugging
1- Boot your device with TWRP from
Custom-TWRP-thanks to @Maxr1998
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot boot name-of-the-twrp.img
Or
fastboot flash recovery name-of-the-twrp.img
2- Now move the build/ROM to your watch
3- Make a backup - there's always 1% chance something goes wrong.
4- Full wipe is recommended....Wipe data/Factory reset
5- Flash the ROM
6- Reboot
7- Setup your initial settings
8- GO TO MY KERNEL THREAD AND DOWNLOAD THE LATEST VERSION AND FLASH THAT.
9- Done
--------------------
HOW TO ACHIEVE ROOT
- Reboot into TWRP
- Copy the root-wear.zip (ROOT AND BUSYBOX_1.5_AND_2.0) package inside your device
- Flash the root-wear. zip and reboot
- Open busybox and install
- Done
--------------------
HOW TO ACHIEVE ROOT AFTER FLASHING THE NEW BOOT IMAGES
- DOWNLOAD THE LATEST VERSION FROM (KERNEL THREAD)
- Reboot into TWRP
- Flash the new kernel and reboot
- Complete your device setup
- Reboot into TWRP again
- Flash root-wear.zip (ROOT AND BUSYBOX_1.5_AND_2.0) package
- Reboot
- Open busybox and install
- Done
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
PLEASE LOOK MY KERNEL/BOOT IMAGES THREAD FOR LATEST KERNEL
KERNEL/BOOT IAMGES FOR LATEST UPDATE
-NOTE: YOU NEED TO FLASH THE ROM FIRST (Setup your initial settings) AND THEN FLASH THE LATEST KERNEL FROM KERNEL THREAD
ROMs-ANDROID_WEAR_2.0 [DEODEXED][ODEXED] [LATEST]
Short changelog-[DEODEXED] [27/8/2018]
- Based on latest release NWD1.170623.001- June_1_2017 security patch
- Kernel is compiled with LINARO GCC: 4.9.4-Optimized/based on latest available source 3.18.24 Kernel
- All *apk system/data, system/app, Framework & priv-app zipalign & optimized for better RAM utilization
- Can be root - Flash the following Root/BusyBox if you want to achieve root access.
- dm-verity disabled
- forced-encryption disabled
- SELinux permissive
- init.d script support
- Tweaked for Best Performance
- adb is enabled by default
- Update script
- Tweaks to achieve better battery life
- Clean
------------------------------------------------------------
Download-Link [LATEST-27/8/2018]
BUILD_WEAR_2.0 [DEODEXED] /ROM
MD5:0ceb5c2c3261cb0026b1365940efc839
------------------------------------------------------------
BUILD_WEAR_2.0 [ODEXED] /ROM
MD5:131ab240ec04f8a5ecbf7acb6d42ad51
------------------------------------------------------------
Download-Link
ROOT AND BUSYBOX_1.5_AND_2.0
------------------------------------------------------------
------------------------------------------------------------
ROMs-MWG68_ANDROID_WEAR_1.5
Download-Link
Deodexed/ROM
MD5:3913568ed1d59d90340962b24a3a46b7
Odexed/ROM
MD5:ee3dbf24fcc19a713ddcf819e24c43bb
----------------------
Kernel Source
https://github.com/toffyjan/Asus-zenwatch-3-kernel
----------------------
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN BUY ME A SHOT OF COFFEE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE ME HERE
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
DONATE-HEREhttps://www.paypal.me/JANJANXDA
paypal.me/JANJANXDA
----------------------
Special thanks to:
If you can, donate and respect all the devs and enjoy
@Chainfire for great work in android
@Maxr1998 thanks for script and twrp recovery
@superR for the kitchen
@Captain_Throwback
@SuperThomasLab for great tools
-Take a look here. And support the dev.
@Xmaster24 for system-less root-
Willi Ye for his great app
-Take a look here. And buy the donate version to support the dev.
Please always support devs and others (soon).
Thanks! What's the decryption key? Apparently I need that to download.
ups gonna fix it soon.
go gO
You meant to flash this with TWRP, right? I did that and did a wiped it (factory reset in TWRP). Seems to hang at the ASUS IN SEARCH OF INCREDIBLE loading screen. Could just be my watch of course.
jobarr said:
You meant to flash this with TWRP, right? I did that and did a wiped it (factory reset in TWRP). Seems to hang at the ASUS IN SEARCH OF INCREDIBLE loading screen. Could just be my watch of course.
Click to expand...
Click to collapse
Offcourse flashing with TWRP..You need to wipe your data too. And fast boot takes some time. 5-10 minutes. I tested on two watches and it works. Be patient
I removed boot animation so that is why see only Google with capital letters. It make the boot process a bit faster.
@janjan Nice one!
Will try it out asap. Just a small tip, could you rebase your kernel onto the swift branch of the kernel-msm repo on android.googlesource.com? That way, the commit history isn't lost and we can see all the changes you made (and improve on them as well). Precondition of course is that the repo already contains the latest MWF76 sources, I didn't check that yet. But if yes, you could just clone it, and drop the .git folder into your kernel folder, verify all is fine and commit the changes.
janjan said:
I removed boot animation so that is why see only Google with capital letters. It make the boot process a bit faster.
Click to expand...
Click to collapse
You mean splash, don't you? Did you just wipe it with zeroes or how did you do it?
After 10 minutes I still only see "ASUS IN SEARCH OF INCREDIBLE". It never even shows "Google".
jobarr said:
After 10 minutes I still only see "ASUS IN SEARCH OF INCREDIBLE". It never even shows "Google".
Click to expand...
Click to collapse
Tell me what you did. You procedure please.
Booted TWRP via "fastboot boot recovery.img"
Flashed your zip
Wiped Dalvik/cache/data
Rebooted
jobarr said:
Booted TWRP via "fastboot boot recovery.img"
Flashed your zip
Wiped Dalvik/cache/data
Rebooted
Click to expand...
Click to collapse
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.
Maxr1998 said:
@janjan Nice one!
Will try it out asap. Just a small tip, could you rebase your kernel onto the swift branch of the kernel-msm repo on android.googlesource.com? That way, the commit history isn't lost and we can see all the changes you made (and improve on them as well). Precondition of course is that the repo already contains the latest MWF76 sources, I didn't check that yet. But if yes, you could just clone it, and drop the .git folder into your kernel folder, verify all is fine and commit the changes.
You mean splash, don't you? Did you just wipe it with zeroes or how did you do it?
Click to expand...
Click to collapse
I will check it out. need to prepare my self for my exam ..I try to
janjan said:
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.
Click to expand...
Click to collapse
Yes. Ahhh....ok, lemme try that.
janjan said:
I will check it out. need to prepare my self for my exam ..I try to
Click to expand...
Click to collapse
Sure, school's always first. Good luck in your exam!
Maxr1998 said:
Sure, school's always first. Good luck in your exam!
Click to expand...
Click to collapse
Thank you. I didn't add too much right now. But we will do that. My last exam in wireless communication.
janjan said:
And you are bootloader unlocked right?
You have to wipe first and then flash the zip.
Click to expand...
Click to collapse
It still won't leave the ASUS screen after 5 minutes. :/
jobarr said:
It still won't leave the ASUS screen after 5 minutes. :/
Click to expand...
Click to collapse
Try to flash the kernel after flash the build. Or
Flash the root after flashing the build or
Wipe everything also your system and then flash the ROM. You have to wipe everything.
I just test again and it seems working without and issue
I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.
jobarr said:
I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.
Click to expand...
Click to collapse
Sounds like the best idea to me actually.. @janjan, didn't you also flash my extracted boot image with fastboot before?
jobarr said:
I wasn't bothering with rooting at the moment. Just trying to get my charging problem fixed.
You mean flash boot.img again manually (with fastboot) after flashing the zip? I tried that. No change. Tried wiping system before flashing everything, no change. I'm wondering if something really is wrong with my watch. I think I'll just load the stock stuff back on it and send it back to Amazon and get a new one I think.
Click to expand...
Click to collapse
jobarr said:
Thanks! What's the decryption key? Apparently I need that to download.
Click to expand...
Click to collapse
Maxr1998 said:
Sounds like the best idea to me actually.. @janjan, didn't you also flash my extracted boot image with fastboot before?
Click to expand...
Click to collapse
Yes I did. But actually It could be a good idea for @jobarr to try it out. I will suggest him to flash your extracted boot image and your system.img and then flash my kernel or my build.
It seems any modification or even by booting into twrp and allow modification causes boot loop and rebooting every 30 seconds. It is due to dm-verity stock kernel feature which provides integrity checking of block devices Or STATE CHECKING. I had the same issue with boot loop and then fixed the issue by flashing my build + kernel.
janjan said:
Yes I did. But actually It could be a good idea for @jobarr to try it out. I will suggest him to flash your extracted boot image and your system.img and then flash my kernel or my build.
It seems any modification or even by booting into twrp and allow modification causes boot loop and rebooting every 30 seconds. It is due to dm-verity stock kernel feature which provides integrity checking of block devices Or STATE CHECKING. I had the same issue with boot loop and then fixed the issue by flashing my build + kernel.
Click to expand...
Click to collapse
Yeah, dm-verity is a pain.. Shouldn't SuperSu also patch dm-verity? Might be worth a try as well.
Unofficial release -TWRP recovery for the Galaxy A7 2018 - SM-A750F 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.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Update 25/12/2018
Beta build released.
Current status - (Tested working)
Treble supported
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.
NOTE: ON ANDROID 5.1.1> 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.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
2. Load the file below into the AP slot, uncheck AUTO-REBOOT and hit start.
twrp_3.2.3-1_a750_251218
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
5. Reboot to TWRP (Do not boot to the OS yet)
*****OREO ROOT INSTRUCTIONS:*****
NOTE: To mount data it is necessary to first *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
Continue with the instructions below to prevent the data partition becoming re-encrypted.
1. To root I suggest downloading and installing the latest Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Copy the Magisk zip to a Micro sd card then install with TWRP.
3. Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @BlackMesa123 for RMM bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
158 views, 20 downloads and not one reply.
Smashing guys. :good:
4. перепрограммируйте обходной zip- архив rmm.можно поподробнее?
Mod edit: English please!
Google translation:
4. reprogram the rmm bypass zip archive. can you be more specific?
Odin shows Failed !! Tried 3 Times ? Had to Flash the Firmare Again.
Help !!
notoriouschyld said:
Odin shows Failed !! Tried 3 Times Had to Flash the Firmare Again.
Help !!
Click to expand...
Click to collapse
Sorry about that, build error on my end. Fixed now.
It will not work on SM-A750FNXXU1ARIC?
Sfuj24 said:
It will not work on SM-A750FNXXU1ARIC?
Click to expand...
Click to collapse
Is that a statement or question?
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
powermen27 said:
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
Click to expand...
Click to collapse
No matter how complete an instruction is, if you don't bother reading it in the first place it's not going to make any difference.
As clearly posted in the OP:
NOTE: ON ANDROID 5.1.1> 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.
Click to expand...
Click to collapse
sorry
ashyx said:
Sorry about that, build error on my end. Fixed now.
Click to expand...
Click to collapse
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
notoriouschyld said:
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
Click to expand...
Click to collapse
Can you tell me which firmware build number you are running and if possible a screen shot of your device screen while booted to download mode?
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
A7whatever said:
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
Click to expand...
Click to collapse
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
https://androidfilehost.com/?fid=11410963190603874542
ashyx said:
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
Click to expand...
Click to collapse
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
A7whatever said:
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
Click to expand...
Click to collapse
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
ashyx said:
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
Click to expand...
Click to collapse
Flashed the old sboot.bin however got the same bootloop
A7whatever said:
Flashed the old sboot.bin however got the same bootloop
Click to expand...
Click to collapse
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
ashyx said:
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
Click to expand...
Click to collapse
Yes
A7whatever said:
Yes
Click to expand...
Click to collapse
Hmm looks like I'll have to take another look at the twrp config or kernel build.
If I pack the kernel into a boot image would you be willing to test if it boots?
Disclaimer: No guarantees. Follow at your own risk. I am not responsible for bricked phones.
Credits to 4PDA
Prerequisites:
Knowledge of OEM unlocking from Developer options, adb, and fastboot
Knowledge of QPST in case you encounter bootloop, so you can revert to a reliable stock ROM
Unlocked bootloader (from here)
1) Get your bootloader unlocked, if you haven't already.
- Visit https://www.zui.com/iunlock
- Enter the IMEI1 (Second number when you call *#06# with the phone)
- Enter the Device ID from the Bootloader/Fastboot (Hold VOL- and Power, while device is off)
- Enter your email and captcha and set the checkmark to acknowledge voiding your warranty.
- If you get an error saying that your IMEI1 is wrong, put in a sim card and wait a few hours. If it still doesn't work, write an email to [email protected]
- In the developer settings in android, enable usb debugging and oem unlock.
- Flash the sn.img file you receive with fastboot (again, hold vol- and power while the device is off). Command is 'fastboot flash unlock sn.img'. You need compatible usb drivers, qualcom drivers and adb/fastboot to do that. Use google or write me a PM if you have trouble with that.
- execute 'fastboot oem unlock-go'
- This allows you to use fastboot to flash custom system/boot/vendor/vbmeta images
Click to expand...
Click to collapse
@wzsx150's recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img MEGA Google Drive
@wzsx150's TWRP for Android 10 TWRP-3.3.2B-0508-LENOVO_Z5S-10.0-CN-wzsx150-fastboot.7z (extract the IMG file and flash using fastboot)
3) Now you can flash TWRP.
- Download ...
- Flash it from the Bootloader with 'fastboot flash recovery recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img'
- Press VOL UP / VOL DOWN to navigate to recovery.
Click to expand...
Click to collapse
11.3.169: L78071_11.3.169_DEV_FullOTA.zip
11.5.096 Update: ZUI_11.3.169_DEV_TO_ZUI_11.5.096_ST.zip
11.5.111 Update: ZUI_11.5.096_TO_ZUI_11.5.111_ST.zip
Other files, use at your own risk
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Official TWRP for jd2019
In recovery, Format data, then wipe Dalvik/ART Cache, Cache, Data
Reboot to recovery
Install in order, without rebooting, 11.3.169 -> 11.5.096 Update -> 11.5.111 Update.
Install Magisk 20.4
Install TWRP for Android 10 (above) using fastboot if the update replaces stock recovery after rebooting
Edited out from original
Wipe Data and flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
In order not to encrypt Data in the future, install Official TWRP immediately after installing updates. Install > Install Image > twrp-3.3.1-0-jd2019.img
Install GApps
Note: I do not know if the 11.5 update relocks the bootloader. It doesn't lock the bootloader.
I had bootloop from OpenGApps. 4PDA post advises to use BiTGApps. You can install Google Play Store from the built-in Lenovo App Center and that's what I did.
Haven't tried disabling dm-verity and forceencrypt.
Good job, my man, I'll check it out tonight and prepare ourselves an updateable package for people coming from any rom to avoid the hassle of going through all of that. As soon as I get it working will release a new TWRP for Android 10.
{
"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"
}
carlshark said:
View attachment 5036881
Click to expand...
Click to collapse
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
jacoghi said:
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
Click to expand...
Click to collapse
I've been using the phone on 11.5.111 for a couple of days now.
I flashed both the 3.3.2 TWRP of @wzsx150 and the official TWRP and they seem to be working. I didn't turn off encryption so it seems to work well.
Happy to have helped in a small way. Thank you for your hard work!
links not works
vesdan said:
links not works
Click to expand...
Click to collapse
Thanks for the heads up, apparently the original poster removed the links. Will be uploading the ones I used.
Reuploading done.
Thank you very much
Thanks for the rom my friend.
Can you please upload the latest update cause i am rooted and it cannot be installed via the system.
Also guys ,does anyone knows if i can put the latest android 10 with multilanguage rom ?Thank you for everything ,i appreciate.
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
galardo_2 said:
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
Click to expand...
Click to collapse
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
vesdan said:
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
Click to expand...
Click to collapse
but the qpst app need an aditional content.xml file, where can i get one
Install global via fastboot, all is included or in qfil ROM is all in zip file
vesdan said:
Install global via fastboot, all is included or in qfil ROM is all in zip file
Click to expand...
Click to collapse
I tried and failed again
i tired and failed again
galardo_2 said:
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
Click to expand...
Click to collapse
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
carlshark said:
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
Click to expand...
Click to collapse
after a few atempts (3-4 days) the imei number got accepted, but now i have another problem as you can see, i flashed the gapps and now i have the bootloop and i dont have a clue how to undone it
hello friends I have all the updates installed, but it tells me that there is a new one, where can I download it?
On the other hand, what difference is there between installing by twrp and qfill?
galardo_2 said:
i tired and failed again
Click to expand...
Click to collapse
This is problem with program, drivers sahara. Try fastboot
{
"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 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy A71 SM-A715F, SM-A715U, SM-A715U1, SM-A715V and SM-A715W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download A71: a71.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
Link
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Changelog:
GitHub History
after unlock bootloader and root, fingerprint doesnt work.
how to fix it ?
thank you in advance
kevin mitnick said:
after unlock bootloader and root, fingerprint doesnt work.
how to fix it ?
thank you in advance
Click to expand...
Click to collapse
Dont use Ian multidisabler.
afaneh92 said:
Dont use Ian multidisabler.
Click to expand...
Click to collapse
I reflashing rom and reflashing twrp and not used ian multidisabler. but fingerprint still not fixed. please help
kevin mitnick said:
I reflashing rom and reflashing twrp and not used ian multidisabler. but fingerprint still not fixed. please help
Click to expand...
Click to collapse
Try this vbmeta disabler https://drive.google.com/file/d/1-4K--sTHhGY9ekmKd_oiaP0eoGrD4vAf/view?usp=drivesdk
afaneh92 said:
Try this vbmeta disabler https://drive.google.com/file/d/1-4K--sTHhGY9ekmKd_oiaP0eoGrD4vAf/view?usp=drivesdk
Click to expand...
Click to collapse
thank you sir..
I flashed this file, but still ask calibration for finger print and not fixed.
kevin mitnick said:
thank you sir..
I flashed this file, but still ask calibration for finger print and not fixed.
Click to expand...
Click to collapse
So other twrp recoveries are ok?
afaneh92 said:
So other twrp recoveries are ok?
Click to expand...
Click to collapse
I tried your twrp and ian recovery..still same..
Flashing The Twrp on Odin is ok. But when i flash using twrp with zip or img. Always showing in Red error.. reading flashin error..
alpher17 said:
Flashing The Twrp on Odin is ok. But when i flash using twrp with zip or img. Always showing in Red error.. reading flashin error..
Click to expand...
Click to collapse
post recovery log
kevin mitnick said:
I tried your twrp and ian recovery..still same..
Click to expand...
Click to collapse
still working on a fix
Sorry i forgoten my firm version is A715FXXS6BUI1 . Is not supported?
alpher17 said:
Sorry i forgoten my firm version is A715FXXS6BUI1 . Is not supported?
Click to expand...
Click to collapse
should be ok
afaneh92 said:
still working on a fix
Click to expand...
Click to collapse
I bought another a71 mainboard and the problem is still same. finger print need calibration. is that software or hardware problem ? finger print work well before unlock bootloader
kevin mitnick said:
I bought another a71 mainboard and the problem is still same. finger print need calibration. is that software or hardware problem ? finger print work well before unlock bootloader
Click to expand...
Click to collapse
I think disabling encryption broke it. This doesn't effect US devices only international variants on specific models.
afaneh92 said:
I think disabling encryption broke it. This doesn't effect US devices only international variants on specific models.
Click to expand...
Click to collapse
my device is a715fxx.
so, how to fix it ?
please help
kevin mitnick said:
my device is a715fxx.
so, how to fix it ?
please help
Click to expand...
Click to collapse
I cant help you now, as I said above still working on it. dont spam the thread.
@afneh92
afaneh92 said:
I cant help you now, as I said above still working on it. dont spam the thread.
Click to expand...
Click to collapse
Can you help me with something?
I have the TWRP 3.5.1 [ianmacd] recovery installed and a custom Samsung ROM (NcX 3.1.2).
I want to flash the stock firmware via odin to keep the ROM up to date (though without losing data, by flashing the HOME_CSC file).
I'll need to flash TWRP again to install Magisk and Root later via Odin as even though it wont format my data, it will flash on top of my current TWRP.
To install yours, what steps should i follow after i flash the Stock ROM again? (Remember that i wont lose data/need to encrypt the phone again)?
Pupet_Master said:
@afneh92
Can you help me with something?
I have the TWRP 3.5.1 [ianmacd] recovery installed and a custom Samsung ROM (NcX 3.1.2).
I want to flash the stock firmware via odin to keep the ROM up to date (though without losing data, by flashing the HOME_CSC file).
I'll need to flash TWRP again to install Magisk and Root later via Odin as even though it wont format my data, it will flash on top of my current TWRP.
To install yours, what steps should i follow after i flash the Stock ROM again? (Remember that i wont lose data/need to encrypt the phone again)?
Click to expand...
Click to collapse
There is 90% chance to lose data, make data backup move it to PC then try.
Note1: changing vbmeta will lose data so must flash same file.
Note2: if you disabled encryption need to do again.
Ignoring note 1&2 then rebooting to system will lose data