Disclaimer: I cannot guarantee that this process will work for you as it did for me. If something goes wrong I will do everything I can to help you, but you are responsible. This is a guide for the I9300 international version.
This is an updated version of my original thread for the I9000, It is still a work in progress but please feel free to highlight things that are wrong or could be better.
What you need:
A downloaded firmware (such as these stock firmwares)
Odin. Usually contained in the firmware. (Here otherwise)
USB Cable
Backups
>65% Battery
Start this download now so that by the time backups are complete, the download should be too.
Section 1: Modes
In this guide you will have to put the phone into various modes. This is done through button combinations.
Download Mode: power + volume down + home button. Hold this combination until the phone reboots, once the galaxy s III logo comes up, you can release the buttons.
Recovery Mode: power + volume up + home button. Hold this combination until the phone reboots, once the galaxy s III logo comes up, you can release the buttons.
Section 2: Rooting
First things first, in order to properly backup your phone, it needs to be rooted.
In the backups section there is a method for those that do not wish to have a rooted handset. However, backups using programs with root privileges are much more reliable and effective.
What you need:
CF Root (Here)
Odin
Place the phone into download mode using the button combination.
Start Odin and confirm that the phone has connected:
{
"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"
}
Extract the CF-Root .zip so that it is in the form of a .tar
Hit the PDA button on odin, browse to where you saved the CF-Root.tar and select open:
Make sure the options section on Odin looks like this:
Hit Start and wait for the flashing process to complete.
Your phone should now be rooted.
Section 3: Backups
A nandroid backup is a full backup of the system, made in recovery mode. This is used to restore the system in the event that something goes wrong and the system will not boot. By default, this backup will be saved to the external SD card if present.
To make a nandroid backup:
Boot the phone into recovery mode.
Use volume buttons to navigate and power button to select.
Select "backup and restore" -> "backup".
Wait for this to finish, then select "Go Back", then "reboot system now".
A backup made with titanium backup can be used to restore all previous apps, settings and content (messages, call logs etc) back onto the phone after new firmware has been flashed.
To make a titanium backup:
Download Titanium Backup from the market.
Go into the phone Settings -> System -> Developer options -> USB debugging. Titanium backup needs this to work.
Run titanium backup and you should get a message about superuser permissions, grant the app permissions. This means it can backup system data, settings etc.
In the top right corner there should a square icon with a tick. Tocuh this to go into batch options.
Run "backup all user apps + system data".
Wait for it to finish
You are now ready to flash new firmware.
If you wish to backup without rooting, I suggest using an array of programs to achieve this, Go Backup, APN Backup, AppMonster. By using these in combination you can most likely achieve a total backup, but it is probably more trouble than rooting, backing up, flashing, restoring then unrooting.
Section 3: Flashing the firmware
Extract Odin and run it. It should look like this:
All the settings above are the settings you need.
In some cases a firmware file will be split into three seperate files (Modem/Phone, CSC and PDA/Code). However, often they will be arranged into one single file.
If the firmware is in one file then select PDA and open the .tar file you extracted from the firmware.zip.
If it is split into more than one file then:
Press the PDA button and select the CODE file.
Press the PHONE button and select the MODEM file.
Press the CSC button and select the CSC file.
Once the firmware is loaded into Odin:
Place phone into download mode.
Connect phone to PC.
Wait for phone to connect to odin.
Flash firmware by pressing start.
Wait for flash to finish.
Once the firmware is installed, you should root your phone so that you can restore backups (refer to section 2).
Once this is done, it is a good idea to do a wipe of the caches so that the install is as clean and smooth as possible.
To do so:
Download super wipe onto your phone from this thread.
Boot into Recovery Mode
Select "install zip from sdcard"
select "choose zip from sdcard" or from "internal sdcard".
navigate to the location of the script, select it, then select "yes".
This will run the wipe script. Once this has run, reboot the phone if it doesn't automatically.
Section 4: Restore
4.1 Start up
Once the phone starts up it should run you through the setup wizard. Go through this process and add gmail account etc.
4.3 Restoring
Restore using titanium backup:
Go to the market and download titanium backup.
As before, make sure USB debugging is enabled.
Touch the icon in the top right corner to go into batch mode.
Navigate to the restore section and choose "restore all apps with data"
Before you start the batch restore, you may wish to remove certain items from your resotre, such as stock apps that will have been updated in the new firmware.
Run the restoration.
If something went wrong and you want to get back to your old firmware then restore using the nandroid backup we made earlier:
Boot into recovery.
Select "backup and restore".
Select "restore"
Choose the appropriate backup to begin the process.
For those that wish to have a non rooted handset, you can follow this procedure to unroot your phone.
Related
hi! all. how can i backup the current stock rom that is installed on my rooted tablet so that if i wish to install custom rom to try & if i don't like it i can still flash back the stock rom.
Obtain a MicroSD card, format and install in your A500 microSD slot. Install Acer Recovery from the Market. In the app, install the new recovery. Say "yes" to backup the existing recovery. Once that finishes, chose the option to reboot into recovery. Once in recovery, chose the "restore and backup" menu, then "backup". The backup will take 5 minutes or so to complete. Chose option to "reboot system". Once Android comes back up, use a file manager app to go to your /mnt/external_sd/clockworkmod/backup and look for a file named "2011-08-08-03.58.40". This translates to the date and time you just did your backup. That's proof that you have a backup file. I would also use Titanium Backup to backup all apps and system files to make getting your new ROM functional easier once you get it flashed.
Once you have this backup, you can flash other ROMS to experiment. If you want to go back to stock, then boot back into recovery as above, or hold down on the volume- button, then push and hold the power button. Release both buttons when script appears in the upper left corner of the "Acer" boot screen. This should bring up the Acer Recovery menu you installed earlier (when you flash a new ROM be sure to reinstall this app). Again, chose the "restore and backup" menu, but this time chose restore. It should bring up your microSD directory and you should see the "2011-08-08-03.58.40" (or whatever date you did your backup). using the volume rocker, chose that file, press the power button, and restore that backup. That should take you back to your stock configuration. You'll probably have to reinstall your widgets though.
jyams said:
Obtain a MicroSD card, format and install in your A500 microSD slot. Install Acer Recovery from the Market. In the app, install the new recovery. Say "yes" to backup the existing recovery. Once that finishes, chose the option to reboot into recovery. Once in recovery, chose the "restore and backup" menu, then "backup". The backup will take 5 minutes or so to complete. Chose option to "reboot system". Once Android comes back up, use a file manager app to go to your /mnt/external_sd/clockworkmod/backup and look for a file named "2011-08-08-03.58.40". This translates to the date and time you just did your backup. That's proof that you have a backup file. I would also use Titanium Backup to backup all apps and system files to make getting your new ROM functional easier once you get it flashed.
Once you have this backup, you can flash other ROMS to experiment. If you want to go back to stock, then boot back into recovery as above, or hold down on the volume- button, then push and hold the power button. Release both buttons when script appears in the upper left corner of the "Acer" boot screen. This should bring up the Acer Recovery menu you installed earlier (when you flash a new ROM be sure to reinstall this app). Again, chose the "restore and backup" menu, but this time chose restore. It should bring up your microSD directory and you should see the "2011-08-08-03.58.40" (or whatever date you did your backup). using the volume rocker, chose that file, press the power button, and restore that backup. That should take you back to your stock configuration. You'll probably have to reinstall your widgets though.
Click to expand...
Click to collapse
when using Titanium Backup, will it backup my games save data?
As the title says, I gets notifications almost daily that I have limited space left on my internal storage, and it seems to be getting worse, no matter how many apps I delete or photos I get rid of. I have a GT-I9505 running the 5.0.1 GPE ROM. Does anyone know how I can fix this? I cant move the apps to my SD card either. This is from my phone.
{
"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"
}
What recovery are you using?
Philz Touch I believe.
There's your problem. Philz and Clockworkmod both write protect the portion of internal storage where the nandroid images are stored due to the fact those two recoveries make incremental backups. To resolve the issue, do the following.
1. Download TWRP 2.8.7.2 from the Optimized CM12.1 thread in I9505 Original Android Development and place it in your internal storage.
1. Go into Philz and delete all nandroid backups. Philz nandroid backups aren't compatible with TWRP.
2. Go into the nandroid menu and free all unused space. This will restore the missing storage space.
4. Flash the recovery you downloaded in step 1.
5. Reboot into TWRP.
6. Make a new nandroid backup.
The reason I mention switching to TWRP is that TWRP doesn't make incremental backups like Philz and Clockwork mod, and therefore doesn't need to write protect the nandroid backup storage space. Also, some ROMs will not install with Philz or Clockworkmod installed, so switching to TWRP is a good idea.
Strephon Alkhalikoi said:
There's your problem. Philz and Clockworkmod both write protect the portion of internal storage where the nandroid images are stored due to the fact those two recoveries make incremental backups. To resolve the issue, do the following.
1. Download TWRP 2.8.7.2 from the Optimized CM12.1 thread in I9505 Original Android Development and place it in your internal storage.
1. Go into Philz and delete all nandroid backups. Philz nandroid backups aren't compatible with TWRP.
2. Go into the nandroid menu and free all unused space. This will restore the missing storage space.
4. Flash the recovery you downloaded in step 1.
5. Reboot into TWRP.
6. Make a new nandroid backup.
The reason I mention switching to TWRP is that TWRP doesn't make incremental backups like Philz and Clockwork mod, and therefore doesn't need to write protect the nandroid backup storage space. Also, some ROMs will not install with Philz or Clockworkmod installed, so switching to TWRP is a good idea.
Click to expand...
Click to collapse
When you say go into the nandroid menu and free all unused space, is this still on philz? I used that option on philz and flashed the recovery, hopefully that works!
Edit: Having trouble flashing TWRP on using Odin. I downloaded TWRP from where you said, but it cant load onto Odin as it doesnt have the right file type?
The copy of TWRP is a flashable zip. Flash it using Philz, or extract the image file from the zip and flash it through Odin. And yes, freeing all unused space applies to both Philz and Clockworkmod.
Strephon Alkhalikoi said:
The copy of TWRP is a flashable zip. Flash it using Philz, or extract the image file from the zip and flash it through Odin. And yes, freeing all unused space applies to both Philz and Clockworkmod.
Click to expand...
Click to collapse
That did the trick, I think! Thanks a lot. I ended up wiping cache, Dalvik and internal storage for a complete new build. will make a backup once I have everything back to normal.
Team RejectZ
How to Nandroid Back up and Restore as well as flash zips with TWRP on the Galaxy J700t1 (Metro PCS variant)
Hello , TimmetaL6669 here from Team Rejectz... It feels so good to be back.. So we have been having this little problem with the TWRP when it comes to doing a back up or flash anything because of, "system can't mount -data , failed" "system can't mount external sd card " .. or something along those lines... So after playing with it for awhile I finally figured out what the problem is... We are used to the old file system before Marshmallow... Before Marshmallow and before SE Linux Enforced the system would write directly to data or the sd card by mounting it directly... but with the new security the system writes through the system.. not by mounting thus avoiding potential malware attacks... so if the system can write to itself... so can we... This fix is more simple than I originally thought... there is no need to mount data unless you are flashing a ROM in which case we can use odin....or TWRP... you just have to know from where...So without further adue,
Pre-Requisites:
You must be Rooted usisng Mese2050's ported TWRP recovery and flashing SU binaries or by using Paco's Method.
You must have a micro SD card with at least 4 GB on it for your zips and backups
WARNINGS: DO NOT WIPE DATA OR CASHE OR DALVIK CASHE FOR ANY REASON YOU WILL END UP IN A BOOT LOOP OR AT THE RESTORE SCREEN
There isn't any reason to change cashe or data unless you are doing a full ROM change ..... Odin does this anyway when you odin so unless you just made an entire ROM with kernel and recovery included with STOCK cashe then DON'T WIPE CASHE OR DATA on marshmallow.. New security.. They did away with us messing with DATA or CASHE.... No need anyway for a back up or restore or to flash zips.... a good updater script for zips for marshmallow will mount the System anyway.
To Nandroid Back UP:
1. Boot into TWRP and click BACK UP. You're gonna need to switch your storage.... Switch your storage to Micro SDCard STORAGE .. because thats where we are going to be making our backup to..Then Swipe to Back up. Wait for your backup to be complete
{
"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"
}
To Nandroid RESTORE:
Boot into TWRP. Click RESTORE. This time though we have been running into the "can't mount storage/ can't mount data" issue ...So..... Instead of switching to your Micro SDCard storage, STAY IN INTERNAL STORAGE. click "go up a level". Click external SD. Find your back up and swipe to Restore.
To Flash zip Files
Again just like with the restore option we are going to stay in the internal storage and click "go up a level" click external sd card and find the zip file you want to flash from your sd card. Click install Image
Thats it. Click thanks if I helped you, Feel free to ask questions if you get stuck. Make sure that you are completely rooted first with SU and Busybox binaries in /system/bin , /system/xbin and root/sbin before you try to use TWRP. Before attempting a back up, or to use TWRP make sure you follow the instructions carefully in Mese2050's TWRP thread.
" Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery]."
Also ensure that you have "unknown sources" checked in Settings/Security tab. and also in "Developer Options" you wanna have USB debugging and OEM unlock checked too.
This will keep root, Xposed, etc upon restore?
Sent from my SM-J700T1 using XDA-Developers mobile app
needmuchohelp said:
This will keep root, Xposed, etc upon restore?
Sent from my SM-J700T1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes.. hut keep a copy of the su zip file on your sd card anyway just in case
needmuchohelp said:
This will keep root, Xposed, etc upon restore?
Sent from my SM-J700T1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes.. hut keep a copy of the su zip file on your sd card anyway just in case
Yeah, i do. My sd files look almost exact to bottom screenshot
Sent from my SM-J700T1 using XDA-Developers mobile app
---------- Post added 10-08-2016 at 12:04 AM ---------- Previous post was 09-08-2016 at 11:59 PM ----------
I think I had done this prior to reading this post, but I did smart install of busybox at same time, when I restarted it wasn't reading sd properly and I formatted thinking it would solve issue. Lost data on sd and still didn't fix issue. Did full clean install, normal busy box, everything golden now
Sent from my SM-J700T1 using XDA-Developers mobile app
I am a little confused. I have the SM J700T. I thought I was following Messi2050's instructions. Here's where I am so far. I have a 32gb micro sd card which I did not have installed when I setup Kies3. Kies3 was installed in the PC to install the phone drivers. Correct? I saw the drivers install when I connected the phone having Odin3 running at the same time. After the drivers installed the phone connected to Odin. Then I launched Odin 3 in order to flash a kernel which turned out to be incompatible with the J700T and got the "Kernel is not Seandroid Enforcing" error. I found a recovery image which was supposed to take me back to stock, and it seemed to work in that I could then install the Messi2050 kernel "odin-permissive-kernel-j700t-t1". The install went ok. Then I flashed the TWRP "odintwrp-3.0.2-0-j700t" which seemed to go ok, but when I disconnected the phone from the PC and rebooted into TWRP I was seeing the Enforcing error on the screen until TWRP fully booted. Anyway, I put the Micro SD card in with the SuperSU zip on it and used TWRP to install "UPDATE-SuperSU-v2.46.zip" , which kinda hung on the install until I sorta cancelled it and immediately the install finished. I rebooted and checked for root with Root Checker and after a while I got a successful report. So then I tried to do a backup of the phone as explained above in this thread.. I selected the MicroSD card to back up to and selected all the selectable partitions, but ended up with lots of can't mount data errors. Eventually I selected only system to backup and it succeeded. So now when I boot up the phone I am still seeing the Enforcing error on the initial black boot screen, but it boots normally and I have been able to use rooted tools and apps. I do not have Busybox installed yet as I believe I have to start over to clear the Enforcing error. I also did not follow Messi2050's instruction to MTP the SU file onto the phone while I am in TWRP. (Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.) I assume that means you have to have the phone connected to the PC. So how do I fully clear the Enforcing error? Here, in this thread, it says, "WARNINGS: DO NOT WIPE DATA OR CASHE OR DALVIK CASHE FOR ANY REASON YOU WILL END UP IN A BOOT LOOP OR AT THE RESTORE SCREEN ", so there must be something I am missing when Messi2050 says, "-if you want internal storage or data to work in TWRP: Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone! Go to [Reboot] -> [Recovery]. So somewhere in here I need to get oriented correctly. I think I have to reset the phone but I tried a factory reset but it didn't clear the Enforcing error. I would appreciate a considered response from the members who know what to do!! Thanks
@bromerrill
Messi2050's directions for format data would be from the beginning as in right after you flash kernel and twrp and before you backup using this threads method for backup.
After a backup/restore using this method in this thread, do not wipe anything.
-sent from this device using this app....
OriginalShinken1 said:
@bromerrill
Messi2050's directions for format data would be from the beginning as in right after you flash kernel and twrp and before you backup using this threads method for backup. After a backup/restore using this method in this thread, do not wipe anything.
So, first you use Odin to flash Messi2050's kernel, which, when you reboot gives the Enforcing warning message; then you Odin the TWRP, and then EXACTLY what do you wipe and why and how??
Does this or another step resolve the inability to do a backup of data and the other partitions? I followed the instructions in this thread, but it didn't work.
Perhaps it has to do with the first wipe? Perhaps you could explain why these errors are happening; something to do with the Marshmallo file system? How to resolve it?
Click to expand...
Click to collapse
@bromerrill
Click format data. Type yes (you'll see)
Make sure you have supersu zip on sd card just in case. Then go back to "install" and flash supersu.
Sorry pics are turned.
-sent from this device using this app....
Well it seems we still do not have a handle on this rooting process. After following the instructions and getting root twice, each time upon a reboot after a while the phone gets soft bricked. Getting the Custom binary blocked by FRP error. It could be related to turning off the developer options subsequent to getting root. If that is the case those who know need to advise those who don't not to turn off developer options! As far as this thread is concerned I don't see a clear explanation of the backup / restore procedure. There has to be something you do before using TWRP to do a backup, otherwise you get errors that you can't back up the data, etc. I appreciate the skewed pictures but that doesn't explain anything because there is no procedure explained. I wrote, "then EXACTLY what do you wipe and why and how??" which is not yet answered. How hard is it to do a step by step so all the users can get a clear understanding of the procedure??
Unofficial release -TWRP recovery for the Samsung Galaxy J2 Grand prime plus SM-G532F/G/M/DS - Mediatek MT6737T
{
"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.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
.
Is the lineage 14.1 will come for this device or devs working on this?
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.
ashyx said:
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.
.
Click to expand...
Click to collapse
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
ShaDisNX255 said:
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
Click to expand...
Click to collapse
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.
ashyx said:
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.
Click to expand...
Click to collapse
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 ----------
ShaDisNX255 said:
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
Click to expand...
Click to collapse
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 ----------
ShaDisNX255 said:
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.
Click to expand...
Click to collapse
Unticking "nvram" and it gets a successful restore.
The phone works fine
:good:
I think TWRP is good to go for the G532
ShaDisNX255 said:
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
:good:
I think TWRP is good to go for the G532
Click to expand...
Click to collapse
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?
ashyx said:
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?
Click to expand...
Click to collapse
Here you go
ShaDisNX255 said:
Here you go
Click to expand...
Click to collapse
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.
.
ashyx said:
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.
.
Click to expand...
Click to collapse
Attaching requested file, also attaching screenshot of the message I got after typing the command
Good work, guys
ShaDisNX255 said:
Attaching requested file, also attaching screenshot of the message I got after typing the command
Click to expand...
Click to collapse
This should fix the nvram backup error. I have also reduced the amount of partitions available for backup. Some were just unecessary.
Can you post me the recovery log after installing this version and if possible after backup/restore please?
https://www.androidfilehost.com/?fid=961840155545571164
.
ashyx said:
This should fix the nvram backup error. I have also reduced the amount of partitions available for backup. Some were just unecessary.
Can you post me the recovery log after installing this version and if possible after backup/restore please?
https://www.androidfilehost.com/?fid=961840155545571164
.
Click to expand...
Click to collapse
Some weird red messages appeared during the back up
I am going to attach both logs of TWRP (the new version) being recently installed and the log of when I performed a backup.
I don't know if you want me to go ahead and try a Restore as is.
The log after the backup is uploaded to mediafire Check Link [Here} since it's about 2 MB big.
Pastebin doesn't let me host it there either.
The log after recently installing TWRP is attached.
ShaDisNX255 said:
Some weird red messages appeared during the back up
I am going to attach both logs of TWRP (the new version) being recently installed and the log of when I performed a backup.
I don't know if you want me to go ahead and try a Restore as is.
The log after the backup is uploaded to mediafire Check Link [Here} since it's about 2 MB big.
Pastebin doesn't let me host it there either.
The log after recently installing TWRP is attached.
Click to expand...
Click to collapse
Just needs a tweak to the fstab layout. Will update tomorrow.
ashyx said:
Just needs a tweak to the fstab layout. Will update tomorrow.
Click to expand...
Click to collapse
Yeah sounds good. Will test tomorrow
I'm trying to root my J2 Prime (SM-G532G/DS build G532GDXU1AQC1) but I want to do it through TWRP, will this method work? It's a new phone and I don't want to brick it within just 3 days of purchase.
ShaDisNX255 said:
Yeah sounds good. Will test tomorrow
Click to expand...
Click to collapse
Ok, this should fix all issues. :fingers-crossed:
Please note if you have made any previous backups then I suggest you delete these as they will no longer be relevant and will cause errors if you try to restore.
If you could try a backup then restore with this version and then post the recovery log so I can check it over?
I have added the update to the OP.
https://www.androidfilehost.com/?fid=673368273298960951
.
ashyx said:
Ok, this should fix all issues. :fingers-crossed:
Please note if you have made any previous backups then I suggest you delete these as they will no longer be relevant and will cause errors if you try to restore.
If you could try a backup then restore with this version and then post the recovery log so I can check it over?
I have added the update to the OP.
https://www.androidfilehost.com/?fid=673368273298960951
.
Click to expand...
Click to collapse
Similar red text to previous build
Uploaded recovery log to Mediafire
ShaDisNX255 said:
Similar red text to previous build
Uploaded recovery log to Mediafire
Click to expand...
Click to collapse
I'm assuming these are the errors you are referring to?:
Unable to locate '/proinfo' partition for backup calculations.
Unable to locate '/preload' partition for backup calculations.
Unable to locate '/secro' partition for backup calculations.
These aren't even included in the fstab or backup as I removed them, so no idea why TWRP is referencing these partitions.
Anyway hopefully this will resolve the issue: https://www.androidfilehost.com/?fid=817550096634775525
By the way, you don't need to back up /cache or /system_image. /cache is only temporary data and should always be empty after reboot. /system_image is the same as /system except it creates a raw backup of the system partition..
.
ashyx said:
Ok, this should fix all issues. :fingers-crossed:
Please note if you have made any previous backups then I suggest you delete these as they will no longer be relevant and will cause errors if you try to restore.
If you could try a backup then restore with this version and then post the recovery log so I can check it over?
I have added the update to the OP.
https://www.androidfilehost.com/?fid=673368273298960951
.
Click to expand...
Click to collapse
Link not working 404 error seemes like url not does not exist
Sent from my SM-G532F using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This guide is for your twrp to recognize your internal memory and the available memory that is in it since we all face this problem that presents twrp in internal storage.
Warning: This procedure will erase all the data of your device such as google accounts, messages, root, that is to say it will remain factory mode, so you will need to reconfigure the device, I add images of the steps so that it is as comprehensible as possible to understand.
When you install twrp and start it for the first time we will get the following information we just need to confirm the action Swipe to Allow Modifications.
So we visualize the following menu with the options offered by twrp, we will only focus on the option Wipe.
We choose the option Advanced Wipe.
Check the Data box and we choose the option Repair or Change File System
We choose the option Change File System
We choose the option EXT4
We choose the option Swipe to Change, When confirming the action your device will erase all your data stored in the internal storage
Twrp will recognize your internal storage and capacity
Warning: You must re-flash Drm-fix.zip. magisk.zip to be root on your device
Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.
omaison said:
Hello,
Thank you for your guide.
I have follow it and it was working, I had the possibility to flash my new ROM.
But as soon I restart again in TWRP, the data partition is again crypted and TWRP can't mount it.
We have to format it again.
Is there a way to decrypt it definitively, so to have the possibility to update a ROM without erase the data partition?
Thank you in advance for your help.
Click to expand...
Click to collapse
No you have do it again after fresh installation
Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.
omaison said:
Thanks for your reply.
OK. So with a ROM like OmniRom for example, on which a new version is released each week, there no way to update our device each week without loosing our data?
If it is the case, I hope that a new version a TRWP will fix this issue soon.
Click to expand...
Click to collapse
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.
awadnisar said:
How to u update the ROM?, by flashing zip?
Idk because I am using stock ROM.
Click to expand...
Click to collapse
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]
omaison said:
On the Omni ROM, you have an update tool which download the zip file of the ROM, and allow to restart directly in TWRP and launch the flash of the zip file.
But the process is blocked due to this encryption issue.
The only way I have found, is to restart manually on TWRP, format the data partition and then flash manually the zip file to do the update.
But it will say that at each update I loose my data... [emoji17]
Click to expand...
Click to collapse
Means updating OmniROM is wiping data partition?
awadnisar said:
Means updating OmniROM is wiping data partition?
Click to expand...
Click to collapse
Not automatically. But it seems that I don't have the choice to format it manually to have the possibility to flash the new version of the ROM.
Otherwise TWRP generate an error with saying that the data partition is encrypted.
I will try again on the next week when the new version of the OmniIROM is released.
redundant