[RECOVERY][ROOT]TWRP 3.1.0-1 - Galaxy J2 Grand prime plus SM-G532F/G/M
- Thread starter ashyx
- Start date
Hello @ashyx
By no means do I want to be rude or disrespectful, I kinda wanted to contact you about the possibility to porting TWRP to a new Samsung Mediatek device. The Galaxy A10s.
Or if possible point me to the right direction to attempt to port it myself, which will probably give me nightmares
Thanks for your attention and sorry about ummmm the post on an unrelated device n.n"
By no means do I want to be rude or disrespectful, I kinda wanted to contact you about the possibility to porting TWRP to a new Samsung Mediatek device. The Galaxy A10s.
Or if possible point me to the right direction to attempt to port it myself, which will probably give me nightmares
Thanks for your attention and sorry about ummmm the post on an unrelated device n.n"
I found a link for the file "no-verity-no-encrypt_Ashyx for those who need it
http://www.mediafire.com/file/guzbin48sh6cwpt/no-verity-no-encrypt_ashyx.zip/file
http://www.mediafire.com/file/guzbin48sh6cwpt/no-verity-no-encrypt_ashyx.zip/file
I followed this method to install a custom recovery method and all worked well, until one day I installed a Magisk module (Detach) and the phone went haywire. It went into boot-loop.
In TWRP, it could not mount /system read-write, showing /system is not in proc/mount. TWRP shows 0 mb /system. partition size. Wiping /system /data and /cache fails with I/O error or something like that. My first guess was that TWRP erred, so I pushed different TWRP images to /tmp with adb (because /sdcard is read-only), and installed them over recovery partition. All show no error during flashing, but after rebooting my recovery did not change.
I did further check, and I found that su binaries are missing, but I can go to adb shell as root (whoami returns root). Doing adb remount does not actually mount /system read-write although it returns as successful.
So I returned to Odin, and flashed combination, to no avail. Odin could not complete the operation with (Write) fail. I flashed 4 file firmware to no avail as well. Tried with different cables, with same result.
It is a nice paperweight now. But I am wondering if the phone can still be brought to life without using direct flashing methods like UFI/ISP. Thank you in advance for any suggestion or direction you all can give.
In TWRP, it could not mount /system read-write, showing /system is not in proc/mount. TWRP shows 0 mb /system. partition size. Wiping /system /data and /cache fails with I/O error or something like that. My first guess was that TWRP erred, so I pushed different TWRP images to /tmp with adb (because /sdcard is read-only), and installed them over recovery partition. All show no error during flashing, but after rebooting my recovery did not change.
I did further check, and I found that su binaries are missing, but I can go to adb shell as root (whoami returns root). Doing adb remount does not actually mount /system read-write although it returns as successful.
So I returned to Odin, and flashed combination, to no avail. Odin could not complete the operation with (Write) fail. I flashed 4 file firmware to no avail as well. Tried with different cables, with same result.
It is a nice paperweight now. But I am wondering if the phone can still be brought to life without using direct flashing methods like UFI/ISP. Thank you in advance for any suggestion or direction you all can give.
Well, are you sure you are flashing the correct firmware? Hopefully you're not flashing anything with a lower bootloader version perhaps. What errors are you getting on your phone when flashing with Odin that Odin fails?
Yes, I am flashing correct firmware (i.e., the one that the phone was running before it stopped working correctly,G532GDXU1ASA5_XID). The log:
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G532GDXU1ASA5_CL15222057_QB21594701_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_G532GDXU1ARC3_CL13269178_QB17586474_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OLE_G532GOLE1ASA5_CL15222057_QB21594701_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_G532GDXU1ASA5_CL15222057_QB21594701_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> preloader.img
<ID:0/011> NAND Write Start!!
<ID:0/011> lk.bin
<ID:0/011> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Odin logs don't necessarily give me useful information. Are there any red messages popping up on your phone?
No there are not. The only red text is ODIN MODE (HIGH SPEED. In fact, there is nothing is happening on phone display. No progress bar and such.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
63Unofficial release -TWRP recovery for the Samsung Galaxy J2 Grand prime plus SM-G532F/G/M/DS - 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-backup-using-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/apps/supersu/2014-09-02-supersu-v2-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
.6
I know it's off topic, but i'm working on lineageos for g532g, f, m and mt. Wait and see if a lineageos unofficial thread appears here eventually.
Please don't discuss it in this thread5
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.4
Seeing as there has been nearly 200 downloads since posting and only 2 yes 2 people have bothered clicking the Thanks button in the OP with no reports of any issues, I have changed the status to stable for your benefit.3Here 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.
.
