FORUMS
Remove All Ads from XDA
Honor View 10

[RECOVERY][ROOT]TWRP 3.1.0-1 - Galaxy J2 Grand prime plus SM-G532F/G/M

10,949 posts
Thanks Meter: 7,243
 
By ashyx, Recognized Contributor on 3rd June 2017, 11:00 PM
Post Reply Email Thread
Unofficial release -TWRP recovery for the Samsung Galaxy J2 Grand prime plus SM-G532F/G/M - Mediatek MT6737T



TWRP 3.1.0-0 Released
Mar 10, 2017

TWRP 3.1.0-0 is out now for all currently supported devices.

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
Mar 11, 2017

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 TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb...twrp-v3-1-0-0/


Current status: STABLE

Features:

MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
system Image backup and flashing support
NTFS support
F2FS support >> To be added
Twrp app support




WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!




Instructions:
(Note: failure to follow these instructions implicitly will cause TWRP to be replaced by stock recovery at boot!)


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.


Download:
twrp_3.1.0-1_sm-g532_5617b


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 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 or the boot patch needs flashing below to disable dm-verity.





To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/app...2-05-t2868133/



This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:

(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 patcher
no-verity-no-encrypt_ashyx




DEVICE TREE: soon


PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST













Credits: Me, Teamwin, my tester @ShaDisNX255
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



.
The Following 28 Users Say Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
 
 
Amanullah
4th June 2017, 01:30 PM |#2  
Guest
Thanks Meter: 0
 
More
Is the lineage 14.1 will come for this device or devs working on this?
4th June 2017, 06:11 PM |#3  
I'm testing this out from the very beginning (it's not a huge sacrifice, this is my work's phone so I don't have many things stored on this phone)
Trying right now, will feedback after I'm finished.

---------- Post added at 11:11 AM ---------- Previous post was at 10:46 AM ----------


I assume that by wiping DATA is wiping my phone clean, the OS gets erased clean. Am I supposed to re-flash stock and re-root, re-flash recovery?
Edit: Never mind, fixed it.
The Following User Says Thank You to ShaDisNX255 For This Useful Post: [ View ] Gift ShaDisNX255 Ad-Free
4th June 2017, 07:46 PM |#4  
Quote:
Originally Posted by ashyx


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 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 or the boot patch needs flashing below to disable dm-verity.


.

Ok so every time I boot in to TWRP, I am going to have to flash the "no-verity-no-encrypt_ashyx" file? Or is it every time the phone reboots, I am going to have to flash this file?
Because so far I've booted into recovery twice and both times I've had this message (the one that asks if I should keep read only or allow modifications to system)?

Also, backup was a success after the flashing of the no-verity file but I failed to make a successful restore

I'm uploading the recovery to mediafire since it's about 2 MB long and I didn't want you to miss any detail.
Recovery Log
4th June 2017, 07:54 PM |#5  
ashyx's Avatar
OP Recognized Contributor
Thanks Meter: 7,243
 
Donate to Me
More
Quote:
Originally Posted by ShaDisNX255

Ok so every time I boot in to TWRP, I am going to have to flash the "no-verity-no-encrypt_ashyx" file? Or is it every time the phone reboots, I am going to have to flash this file?
Because so far I've booted into recovery twice and both times I've had this message (the one that asks if I should keep read only or allow modifications to system)?

Also, backup was a success after the flashing of the no-verity file but I failed to make a successful restore

I'm uploading the recovery to mediafire since it's about 2 MB long and I didn't want you to miss any detail.
Recovery Log

OK you need to flash the boot patcher to disable encryption. This is the only way you can make a data backup or restore.
You only need do this once unless you upgrade or replace the boot image.
The Following 5 Users Say Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
4th June 2017, 08:31 PM |#6  
Quote:
Originally Posted by ashyx

OK you need to flash the boot patcher to disable encryption. This is the only way you can make a data backup or restore.
You only need do this once unless you upgrade or replace the boot image.

Got it. Yeah for some reason after 2 reboots in to TWRP I got the message twice so I flashed the no-verity file twice.
Anyway, I still couldn't do a "Full restore", it fails when it gets to something called vram?
Idk, I'm trying another backup and restore, but this time I'll wipe (factory reset) before restoring.
Be right back with feedback

---------- Post added at 01:24 PM ---------- Previous post was at 01:06 PM ----------

Quote:
Originally Posted by ShaDisNX255

Got it. Yeah for some reason after 2 reboots in to TWRP I got the message twice so I flashed the no-verity file twice.
Anyway, I still couldn't do a "Full restore", it fails when it gets to something called vram?
Idk, I'm trying another backup and restore, but this time I'll wipe (factory reset) before restoring.
Be right back with feedback

Yeah, it gets stuck on something called "nvram"
I am trying another "restore" with this particular box ticked off and see if everything else restores nicely
I really don't know what that is.

---------- Post added at 01:31 PM ---------- Previous post was at 01:24 PM ----------

Quote:
Originally Posted by ShaDisNX255

Got it. Yeah for some reason after 2 reboots in to TWRP I got the message twice so I flashed the no-verity file twice.
Anyway, I still couldn't do a "Full restore", it fails when it gets to something called vram?
Idk, I'm trying another backup and restore, but this time I'll wipe (factory reset) before restoring.
Be right back with feedback

---------- Post added at 01:24 PM ---------- Previous post was at 01:06 PM ----------



Yeah, it gets stuck on something called "nvram"
I am trying another "restore" with this particular box ticked off and see if everything else restores nicely
I really don't know what that is.

Unticking "nvram" and it gets a successful restore.
The phone works fine

I think TWRP is good to go for the G532
The Following User Says Thank You to ShaDisNX255 For This Useful Post: [ View ] Gift ShaDisNX255 Ad-Free
4th June 2017, 08:43 PM |#7  
ashyx's Avatar
OP Recognized Contributor
Thanks Meter: 7,243
 
Donate to Me
More
Quote:
Originally Posted by ShaDisNX255

Got it. Yeah for some reason after 2 reboots in to TWRP I got the message twice so I flashed the no-verity file twice.
Anyway, I still couldn't do a "Full restore", it fails when it gets to something called vram?
Idk, I'm trying another backup and restore, but this time I'll wipe (factory reset) before restoring.
Be right back with feedback

---------- Post added at 01:24 PM ---------- Previous post was at 01:06 PM ----------



Yeah, it gets stuck on something called "nvram"
I am trying another "restore" with this particular box ticked off and see if everything else restores nicely
I really don't know what that is.

---------- Post added at 01:31 PM ---------- Previous post was at 01:24 PM ----------



Unticking "nvram" and it gets a successful restore.
The phone works fine

I think TWRP is good to go for the G532

I'll look at that partition, it may just be protected so not able to be backed up. If not I'll just remove it from backup.
Can you give me a screen shot of the on screen log?
The Following 3 Users Say Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
4th June 2017, 09:14 PM |#8  
Quote:
Originally Posted by ashyx

I'll look at that partition, it may just be protected so not able to be backed up. If not I'll just remove it from backup.
Can you give me a screen shot of the on screen log?

Here you go
Attached Thumbnails
Click image for larger version

Name:	20170604_140759.jpg
Views:	914
Size:	262.1 KB
ID:	4171403  
The Following User Says Thank You to ShaDisNX255 For This Useful Post: [ View ] Gift ShaDisNX255 Ad-Free
4th June 2017, 09:49 PM |#9  
ashyx's Avatar
OP Recognized Contributor
Thanks Meter: 7,243
 
Donate to Me
More
Quote:
Originally Posted by ShaDisNX255

Here you go

Ok I've found the issue with /nvram and will be uploading the fixed version shortly.
Just for info you can take screen shots directly in TWRP by holding POWER+VOL DOWN. Note where it saves the screenshot.

However there seems to be an issue with the EFS backup being empty, so I need to check if there are sub partitions I need to include.
Can you do the following in ADB or a terminal:

For ADB, enable USB debugging and do:

adb shell
su
ls -laR dev/block > sdcard/block.txt


For terminal do:
su
ls -laR dev/block > sdcard/block.txt


You can also use TWRP terminal:
ls -laR dev/block > sdcard/block.txt

Then find block.txt in /sdcard and post up.

.
The Following 2 Users Say Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
4th June 2017, 10:20 PM |#10  
Quote:
Originally Posted by ashyx

Ok I've found the issue with /nvram and will be uploading the fixed version shortly.
Just for info you can take screen shots directly in TWRP by holding POWER+VOL DOWN. Note where it saves the screenshot.

However there seems to be an issue with the EFS backup being empty, so I need to check if there are sub partitions I need to include.
Can you do the following in ADB or a terminal:

For ADB, enable USB debugging and do:

adb shell
su
ls -laR dev/block > sdcard/block.txt

For terminal do:
su
ls -laR dev/block > sdcard/block.txt

You can also use TWRP terminal:
ls -laR dev/block > sdcard/block.txt

Then find block.txt in /sdcard and post up.

.

Attaching requested file, also attaching screenshot of the message I got after typing the command
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2017-06-04-15-16-13.png
Views:	612
Size:	43.0 KB
ID:	4171456  
Attached Files
File Type: txt block.txt - [Click for QR Code] (12.7 KB, 142 views)
The Following User Says Thank You to ShaDisNX255 For This Useful Post: [ View ] Gift ShaDisNX255 Ad-Free
4th June 2017, 10:29 PM |#11  
Sub_Zero2's Avatar
Senior Member
Thanks Meter: 323
 
More
Good work, guys
The Following 2 Users Say Thank You to Sub_Zero2 For This Useful Post: [ View ] Gift Sub_Zero2 Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes