Related
This should help anyone who keeps having flashing issues.
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON SDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)(OR WHATEVER YOU USE)
apps.zip not included. Create your own.
Flashing the rom:
1. Backup current rom (to the sdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues
[FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR SYSTEM]
3. Flash the rom
4. [TW roms this step is not needed] Flash gapps for aosp roms if applicable.
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
TIPS:
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
Reserved
You may want to add that if you're flashing a 4.2.2 barred rom, you will need to upgrade to the latest bootloader (MD4)
Also, what do you mean "both recoveries are compatible with each other"? Some may take that to mean that the same backups can be restored on either one, which is not true.
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
Agreed
TheAxman said:
2. Complete wipe, (I do complete, some people do not) Complete = No Issues
Click to expand...
Click to collapse
You may want to really define what you mean by " Complete Wipe " . At least in the way you mean it. For me a " FULL Wipe " means : System - Data - Dalvik Cache - Cache - Factory Reset - Internal SD. For others it may mean something different.
prboy1969 said:
You may want to really define what you mean by " Complete Wipe " . At least in the way you mean it. For me a " FULL Wipe " means : System - Data - Dalvik Cache - Cache - Factory Reset - Internal SD. For others it may mean something different.
Click to expand...
Click to collapse
Will do, thanks.
EDIT: How about now, I actually wrote this for the G4, but saw it useful in the G3, because I still own one. Missed a few items.
TheAxman said:
Will do, thanks.
EDIT: How about now, I actually wrote this for the G4, but saw it useful in the G3, because I still own one. Missed a few items.
Click to expand...
Click to collapse
You accidentally put "clear data" instead of "clear system"
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
[updated: 07-12-2013]
Well simply, can it be done ?
I'm currently running 3.2.8 with root & twrp with partitions encrypted.
I want to upgrade to 4.0.1, convert to F2FS, keep root & twrp and still be encrypted.
I've read that a new version "blu spark" of the recovery has been released, is this the key to what i want to do ?
If you could provide a foolprof how to, this would be amazing.
Vitriol_Drinker said:
Well simply, can it be done ?
I'm currently running 3.2.8 with root & twrp with partitions encrypted.
I want to upgrade to 4.0.1, convert to F2FS, keep root & twrp and still be encrypted.
I've read that a new version "blu spark" of the recovery has been released, is this the key to what i want to do ?
If you could provide a foolprof how to, this would be amazing.
Click to expand...
Click to collapse
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
AlkaliV2 said:
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
Click to expand...
Click to collapse
I also want to flash OOS 4.0 based on Nougat, but I want to do a clean flash and change the file system to f2fs (I come from OOS 3.2.7 rooted with official TWRP 3.0.2-1).
So, what I have to do is:
1. make backups of files and apps (I will move files and backup apps with Titanium Backup on my PC or a USB stick) and nandroid backup for evenience (move also it on PC)
2. wipe all (with TWRP or adb?)
3. flash OOS 4.0 Nougat (adb?)
4. flash last stable version of Supersu
5. flash latest TWRP by @eng.stk (with adb?)
Is it correct? The only thing that I can't understand is if I have to use adb or TWRP for flashing, I heard that when you flash the full update the recovery will be replaced with the stock one...
Please help me, I'm looking for trying Nougat
let92 said:
I also want to flash OOS 4.0 based on Nougat, but I want to do a clean flash and change the file system to f2fs (I come from OOS 3.2.7 rooted with official TWRP 3.0.2-1).
So, what I have to do is:
1. make backups of files and apps (I will move files and backup apps with Titanium Backup on my PC or a USB stick) and nandroid backup for evenience (move also it on PC)
2. wipe all (with TWRP or adb?)
3. flash OOS 4.0 Nougat (adb?)
4. flash last stable version of Supersu
5. flash latest TWRP by @eng.stk (with adb?)
Is it correct? The only thing that I can't understand is if I have to use adb or TWRP for flashing, I heard that when you flash the full update the recovery will be replaced with the stock one...
Please help me, I'm looking for trying Nougat
Click to expand...
Click to collapse
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
Or... unroot your phone, flash the stock recovery (fastboot mode) and update through the official OTA Then flash the recovery and root your device again :good:
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
All right, I'll try this weekend and will post here the result
Viper The Ripper said:
Or... unroot your phone, flash the stock recovery and update through the official OTA Then flash the recovery and root again :good:
Click to expand...
Click to collapse
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
let92 said:
All right, I'll try this weekend and will post here the result
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
Click to expand...
Click to collapse
Flash stock recovery from OP site and flash rom. Don't relock the bootloader. then flash twrp using fastboot and flash supersu. Will require backing up too tho. I tired the method I gave you and it worked well. F2FS is really worth the effort.
hiredantispammer said:
Flash stock recovery from OP site and flash rom. Don't relock the bootloader. then flash twrp using fastboot and flash supersu. Will require backing up too tho. I tired the method I gave you and it worked well. F2FS is really worth the effort.
Click to expand...
Click to collapse
It seems more simple the @Viper The Ripper's method: in that way I only need to flash the stock recovery, boot the phone (I think the phone will boot on OOS 3.2.7, my actual version), then download OTA (using a VPN to Germany because the update hasn't begun in Italy ), factory reset (will the phone keep Nougat or come back to manufacturer Marshmallow version?), flash recovery by @eng.stk and root phone.
Correct?
AlkaliV2 said:
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
Click to expand...
Click to collapse
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Viper The Ripper said:
Or... unroot your phone, flash the stock recovery (fastboot mode) and update through the official OTA Then flash the recovery and root your device again :good:
Click to expand...
Click to collapse
Will this work for me ? Applying the OTA won't relock bootloader will it ?
titanium backup that I took on 3.2.8 isn't restoring on 4.0.1. because F2FS maybe? any solution?
sahed01 said:
titanium backup that I took on 3.2.8 isn't restoring on 4.0.1. because F2FS maybe? any solution?
Click to expand...
Click to collapse
What do you mean? Titanium give you an error when you try to restore some apps? Or you don't find the backups on your phone?
let92 said:
What do you mean? Titanium give you an error when you try to restore some apps? Or you don't find the backups on your phone?
Click to expand...
Click to collapse
.
no nothing like that. it's just when I'm restoring any app, it's like titanium backup freezes. *restoring app* for like hours. but nothing actually happens.
Only suggestion that i will give is what worked for me. So here is what i did and successfully upgraded from 3.2.8 to 4.0.1 OOS without losing data and keeping encryption on ext4 /data.
1. Keep full OTA zip, and SuperSU latest in the folder or Stable, whatever you want, and the latest recovery by eng.stk v11.
2. Remove security from your phone (pin/password/fingerprint), and Go to recovery flash v11 recovery by eng and reboot to recovery.
3. Wipe system, cache, and dalvik.
4. Flash full OTA, flash TWRP recovery img again. If on rebooting, you find stock recovery, just flash v11 from fastboot again.
5. Don't reboot into system, reboot into recovery again, flash SuperSU zip and make sure SuperSU flashes properly. You need to read the installation process and determine that it flashed properly.
6. Reboot to system, you will have all of your data safe and the way it was in MM.
7. Be careful, the moment you assign pin/pattern/fingerprint security to your device, TWRP would ask for a pattern in recovery and it won't decrypt your data. (Works fine if you are on f2fs). If you are like me and don't flash zips that oftenly, it's good to go.
I hope this method helps. Be sure to remove security from phone before flashing and rebooting as recovery won't work if you have security applied. It's a cheap workaround but it works nevertheless.
sahed01 said:
.
no nothing like that. it's just when I'm restoring any app, it's like titanium backup freezes. *restoring app* for like hours. but nothing actually happens.
Click to expand...
Click to collapse
Maybe Titanium wants the storage permission even if it doesn't ask for it
Try to give it, delete app cache and restart the phone.
Then try to restore one app.
let92 said:
All right, I'll try this weekend and will post here the result
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
Click to expand...
Click to collapse
Go to Supersu apk and choose the option in settings to unroot completly your phone
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
Vitriol_Drinker said:
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Will this work for me ? Applying the OTA won't relock bootloader will it ?
Click to expand...
Click to collapse
If you apply the official OTA you won't lose nothig from your current rom
Yes it'll work and nope, applying the OTA won't relock your bootloader :good:
Vitriol_Drinker said:
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Click to expand...
Click to collapse
People that want F2FS will lose their data converting their filesystems unless they back it up; no method listed in this thread gets around this. All the options listed keeps the users on ext4 because the official OTA does not convert your /data partition to F2FS as shown in the updater script code below from official 4.0.1 full firmware and update file.
Code:
getprop("ro.display.series") == "OnePlus 3" || abort("E3004: This package is for \"OnePlus 3\" devices; this is a \"" + getprop("ro.display.series") + "\".");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.050000, 10);
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
ui_print("Writing static_nvbk image...");
package_extract_file("RADIO/static_nvbk.bin", "/dev/block/bootdevice/by-name/oem_stanvbk");
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64bak");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfgbak");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak");
), "");
msm.boot_update("finalize");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("firmware-update/adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
set_progress(1.000000);
You can see that all it does it overwrite the system partition with the new changes, writes the radio file, and flashes the extra firmware to bring you up to speed with nougat. If you want to do this right and be on F2FS you have to do it manually.
Viper The Ripper said:
Go to Supersu apk and choose the option in settings to unroot completly your phone
Click to expand...
Click to collapse
Thank you! I'll try your method so!
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
Sounds like good plan, but I have one question. Do you need to disable security (fingerprint, patern or code) on forehand to make sure the data can be decrypted?
I've managed to do all this and end up wit 4.0.1 with F2FS and no encryption. If I encrypt the phone, it changes the format of the data partition and TWRP won't decrypt it. If I understand this thread, this is to be expected. There is no way to end up with encrypted F2FS that TWRP can decrypt?
Revolised123 said:
Sounds like good plan, but I have one question. Do you need to disable security (fingerprint, patern or code) on forehand to make sure the data can be decrypted?
Click to expand...
Click to collapse
I didn't. Just boot back to recovery after flashing everything. With this TWRP data can be decrypted.
Hi,
I have i747 that has a clockworkmod recovery. How do I erase as much as possible of everything so that my phone is as clean as possible before I install a new ROM on galaxy s3?
I tried to factory reset phone, did all the 'delete/erase' options within clockworkmod recovery (except advanced section) and yet I see some residual folders from the previous installation. is there a way to completely erase wipe out everything without bricking the phone?
Thanks!
user-747 said:
Hi,
I have i747 that has a clockworkmod recovery. How do I erase as much as possible of everything so that my phone is as clean as possible before I install a new ROM on galaxy s3?
I tried to factory reset phone, did all the 'delete/erase' options within clockworkmod recovery (except advanced section) and yet I see some residual folders from the previous installation. is there a way to completely erase wipe out everything without bricking the phone?
Thanks!
Click to expand...
Click to collapse
You should really flash TWRP recovery before proceeding. CWM hasn't been maintained or updated in a long time. It is likely to give you problems flashing anything new.
To completely blank a phone in TWRP I use Wipe -> Advanced Wipe -> Dalvik, Cache, System, Data. Followed by Wipe -> Format Data then type "yes" to confirm; always a good idea if you're switching between Touchwiz and AOSP in particular. That will leave you with totally blank internal storage. You'll have to flash a ROM from an external SD, or load a ROM zip over USB while booted in recovery because internal storage will be wiped clean.
It might be a good idea to look into what bootloader and modem you're running too. If you're still using CWM, you might be on pretty old firmware that isn't going to work right with newer roms. Just don't start flashing bootloaders/modems willy-nilly. Samsung made this phone kind of easy to hard brick on the newer firmwares. There's a right way to update it, if you find you have to.
jason2678 said:
You should really flash TWRP recovery before proceeding. CWM hasn't been maintained or updated in a long time. It is likely to give you problems flashing anything new.
To completely blank a phone in TWRP I use Wipe -> Advanced Wipe -> Dalvik, Cache, System, Data. Followed by Wipe -> Format Data then type "yes" to confirm; always a good idea if you're switching between Touchwiz and AOSP in particular. That will leave you with totally blank internal storage. You'll have to flash a ROM from an external SD, or load a ROM zip over USB while booted in recovery because internal storage will be wiped clean.
It might be a good idea to look into what bootloader and modem you're running too. If you're still using CWM, you might be on pretty old firmware that isn't going to work right with newer roms. Just don't start flashing bootloaders/modems willy-nilly. Samsung made this phone kind of easy to hard brick on the newer firmwares. There's a right way to update it, if you find you have to.
Click to expand...
Click to collapse
Thanks so much for providing such a detailed answer!! You make many very good points!!
Just to reflect on those...
1) Yes, CWM recovery has not been updated for about 2-3 years. I have 6.0.4.7 version. Where do I check how stale it really is? I tried googling for CWM recovery and saw tons of links with everyone talking about CWM but ZERO sites with actual CWM .zip or .img file
2) I did 'adb bugreport' and was able to find information on my bootloader and a modem:
Bootloader: I747UCUEMJB
Radio: I747UCUEMJB
I am not too sure for what I would need to use this information for though
3) when completely blanking the phone (doing all those wipe/erase actions you mentioned), would that erase the recovery as well or is recovery is kept on a some other partition that never gets touched
4) When installing TWRP over CWM, would TWRP override CWM or install side to side along with CWM?
Thanks!
The will need to run an updated bootloader and modem before installing the latest custom roms.
user-747 said:
2) I did 'adb bugreport' and was able to find information on my bootloader and a modem:
Bootloader: I747UCUEMJB
Radio: I747UCUEMJB
I am not too sure for what I would need to use this information for though
3) when completely blanking the phone (doing all those wipe/erase actions you mentioned), would that erase the recovery as well or is recovery is kept on a some other partition that never gets touched
4) When installing TWRP over CWM, would TWRP override CWM or install side to side along with CWM?
Thanks!
Click to expand...
Click to collapse
3 - Those wipes will just blank /system, /data and other partitions that would affect a rom. More critical areas like bootloader, modem, and recovery will remain untouched and intact.
4 - TWRP will overwrite CWM in the /recovery partition. They can't coexist.
2 - If you're comfortable with Odin, this thread might be the easiest and safest way to get updated. The Odin tar will get you up to NE4 firmware that should work with all the newest roms. Before modding, you could check for updates a few times in that stock rom. There should be two, one from NE4 to NJ1, and one NJ1 to NJ2. NJ2 is the newest and almost certainly last update for the i747.
If you don't like using Odin, there are recovery flashable zips to update the firmware for i747 too. You just have to be very careful how you go about it or you can brick the phone.
audit13 said:
The will need to run an updated bootloader and modem before installing the latest custom roms.
Click to expand...
Click to collapse
I was able to install the most recent octos just a few days ago with my stale configuration: old bootloader and old cwm recovery. My phone i747 currently has nougat.
When you speak of 'latest roms' what exactly do you have in mind?
jason2678 said:
3 - Those wipes will just blank /system, /data and other partitions that would affect a rom. More critical areas like bootloader, modem, and recovery will remain untouched and intact.
4 - TWRP will overwrite CWM in the /recovery partition. They can't coexist.
2 - If you're comfortable with Odin, this thread might be the easiest and safest way to get updated. The Odin tar will get you up to NE4 firmware that should work with all the newest roms. Before modding, you could check for updates a few times in that stock rom. There should be two, one from NE4 to NJ1, and one NJ1 to NJ2. NJ2 is the newest and almost certainly last update for the i747.
If you don't like using Odin, there are recovery flashable zips to update the firmware for i747 too. You just have to be very careful how you go about it or you can brick the phone.
Click to expand...
Click to collapse
I am actually quite familiar with Odin. I used to root i747 with it. Then I wanted to update to the latest official rom and ironically soft-bricked the phone to the point where it was dead...nothing worked at all. If I remember correctly I wrote i9305 Rom to i747 phone. Then I found out that during boot the phone internally still scans through sd card and was able to take advantage of that to install recovery and consequently cyanogenmod os. I remember tons of Adb done. Since then the phone regained all functionality and now works very smooth with freshly installed octos. However, I see I am missing some hard drive space ie unusually large usage by octos. This makes me wonder if the 'bad original partition + bootloader +modem' are still in there but not invoked for some reason and the explanation behind my what appears to be successful installs is working os, etc are written to a separate partition which is now invoked. Is this hypothesis legit or not real? Is it at all possible that my cwm somehow is installed on a partition that is delete-able or that cannot be a possibility and all recovery goes into write-protected space?
And while we are in this topic, what are the obvious advantages of a newer boot loader if I can still install whatever custom roms?
user-747 said:
I was able to install the most recent octos just a few days ago with my stale configuration: old bootloader and old cwm recovery. My phone i747 currently has nougat.
When you speak of 'latest roms' what exactly do you have in mind?
Click to expand...
Click to collapse
Sometimes, a phone will not display the correct imei with the latest custom ROM unless the phone is running the most recent bootloader and modem for the particular phone.
audit13 said:
Sometimes, a phone will not display the correct imei with the latest custom ROM unless the phone is running the most recent bootloader and modem for the particular phone.
Click to expand...
Click to collapse
Thanks! Good to know.
I think this phone only has a 12 GB data partition. About 1.5 GB is reserved for /system, another 1 GB for /cache, and there are a host of other partitions. That's some of your used space. The rest could be cruft from old installs left over in userdata that a standard wipe of /data didn't get unless you format internal storage.
If what you have is working for you, then I wouldn't touch bootloader and modem.
jason2678 said:
You should really flash TWRP recovery before proceeding. CWM hasn't been maintained or updated in a long time. It is likely to give you problems flashing anything new.
To completely blank a phone in TWRP I use Wipe -> Advanced Wipe -> Dalvik, Cache, System, Data. Followed by Wipe -> Format Data then type "yes" to confirm; always a good idea if you're switching between Touchwiz and AOSP in particular. That will leave you with totally blank internal storage. You'll have to flash a ROM from an external SD, or load a ROM zip over USB while booted in recovery because internal storage will be wiped clean.
It might be a good idea to look into what bootloader and modem you're running too. If you're still using CWM, you might be on pretty old firmware that isn't going to work right with newer roms. Just don't start flashing bootloaders/modems willy-nilly. Samsung made this phone kind of easy to hard brick on the newer firmwares. There's a right way to update it, if you find you have to.
Click to expand...
Click to collapse
jason2678 said:
I think this phone only has a 12 GB data partition. About 1.5 GB is reserved for /system, another 1 GB for /cache, and there are a host of other partitions. That's some of your used space. The rest could be cruft from old installs left over in userdata that a standard wipe of /data didn't get unless you format internal storage.
If what you have is working for you, then I wouldn't touch bootloader and modem.
Click to expand...
Click to collapse
Thanks for the insight!
I went ahead and updated by recovery to TWRP via Odin just a few minutes ago...
I see Under Advanced Wipe another option for Wipe -> Advanced Wipe -> Internal Storage. Should I also wipe out internal storage? What is it for anyway? Whats the difference between 'internal storage' and 'system'?
user-747 said:
Thanks for the insight!
I went ahead and updated by recovery to TWRP via Odin just a few minutes ago...
I see Under Advanced Wipe another option for Wipe -> Advanced Wipe -> Internal Storage. Should I also wipe out internal storage? What is it for anyway? Whats the difference between 'internal storage' and 'system'?
Click to expand...
Click to collapse
Honestly I'm not 100% sure what the Internal Storage wipe does under Advanced Wipe, and I don't feel like making then restoring a backup right now just to test it . I never use it. If I had to guess, I bet it wipes /data and possibly a few other partitions without preserving user files in /data/media/0, see below, but don't know that. It certainly won't blank the whole internal storage; some areas like recovery, modem, and aboot are far too important and won't be touched.
Here's what I can tell you. Doing Wipe -> Advanced Wipe -> system, data, cache, dalvik is typically good enough for flashing a new rom (switching from Touchwiz to AOSP can require some additional care), some would even say overkill the way rom installers are scripted today, but old habits die hard. However, Advanced Wipe -> Data will wipe /data without wiping /data/media. Since android got multi-user support, files reported to be in /sdcard are actually stored in /data/media/0 for the primary user, so that means that downloads, pictures, user app files and things like that can be left behind by just wiping data since /data/media is left untouched. It is useful if you don't want to shuffle your files off then back on the device to flash something new or if you're using a device without an external SD and have a rom zip stored on device in /sdcard, but it leaves stuff behind if you're looking for a clean start.
To completely blank /data pick Wipe -> Format Data and TWRP will format /data and leave nothing behind, not even /data/media like the normal Advanced Wipe -> Data preserves. Just make sure you're prepared for the phone storage to be blank. You'll have to flash from external SD or push files from a computer over usb. TWRP does automatically start up mtp and adb shortly after booting if you need to push files over usb.
/system is a partition of special reserved space just for the rom and system apps and not user files. It is usually mounted read only when booted up normally to keep us from messing anything important up. I hope this helps and doesn't just muddy the waters more.
jason2678 said:
Honestly I'm not 100% sure what the Internal Storage wipe does under Advanced Wipe, and I don't feel like making then restoring a backup right now just to test it . I never use it. If I had to guess, I bet it wipes /data and possibly a few other partitions without preserving user files in /data/media/0, see below, but don't know that. It certainly won't blank the whole internal storage; some areas like recovery, modem, and aboot are far too important and won't be touched.
Here's what I can tell you. Doing Wipe -> Advanced Wipe -> system, data, cache, dalvik is typically good enough for flashing a new rom (switching from Touchwiz to AOSP can require some additional care), some would even say overkill the way rom installers are scripted today, but old habits die hard. However, Advanced Wipe -> Data will wipe /data without wiping /data/media. Since android got multi-user support, files reported to be in /sdcard are actually stored in /data/media/0 for the primary user, so that means that downloads, pictures, user app files and things like that can be left behind by just wiping data since /data/media is left untouched. It is useful if you don't want to shuffle your files off then back on the device to flash something new or if you're using a device without an external SD and have a rom zip stored on device in /sdcard, but it leaves stuff behind if you're looking for a clean start.
To completely blank /data pick Wipe -> Format Data and TWRP will format /data and leave nothing behind, not even /data/media like the normal Advanced Wipe -> Data preserves. Just make sure you're prepared for the phone storage to be blank. You'll have to flash from external SD or push files from a computer over usb. TWRP does automatically start up mtp and adb shortly after booting if you need to push files over usb.
/system is a partition of special reserved space just for the rom and system apps and not user files. It is usually mounted read only when booted up normally to keep us from messing anything important up. I hope this helps and doesn't just muddy the waters more.
Click to expand...
Click to collapse
Thanks!
I will try to do wipe and reinstall Rom tonight and will update this thread. While we are in this topic, when flashing twrp via Odin in phone's download mode, I noticed that it says: Qualcomm secureboot: enabled. Does this mean my bootloader is locked?
user-747 said:
Thanks!
I will try to do wipe and reinstall Rom tonight and will update this thread. While we are in this topic, when flashing twrp via Odin in phone's download mode, I noticed that it says: Qualcomm secureboot: enabled. Does this mean my bootloader is locked?
Click to expand...
Click to collapse
No, the i747 never had a locked bootloader. You couldn't boot unsigned stuff like CWM, TWRP, or octos if it did.
jason2678 said:
No, the i747 never had a locked bootloader. You couldn't boot unsigned stuff like CWM, TWRP, or octos if it did.
Click to expand...
Click to collapse
Thanks!
user-747 said:
Thanks!
I will try to do wipe and reinstall Rom tonight and will update this thread. While we are in this topic, when flashing twrp via Odin in phone's download mode, I noticed that it says: Qualcomm secureboot: enabled. Does this mean my bootloader is locked?
Click to expand...
Click to collapse
I went ahead and did all the wipes and formats you recommend and all worked like a charm. OctOs installed like a charm, my disk space is regained, gapps are working, IMEI is good. so far I cannt find anyting that does not work. Thank you @jason2678 for your valuable feedback on my questions!!
Hello, I rooted almost 20 days ago and I want to change my rom and I have some questions,
Because I don't want to lose ANY data or delete my OS like the last time I tried rooting
so this is what I'm gonna do:
1. take nandroid backup
2. backup all user apps and data using titanium backup
3. move backups to somewhere safe you can get back to (SD card)
4. Download the following files:
LineageOS - Gapps - SU
Of course latest versions
5. go to Recovery and do the following:
1. Wipe (System, Data, Cache)
2. Flash (LineageOS then Gapps then SU)
3. Wipe (dalvik cache, cache)
to make sure everything goes smooth
Reboot system
6. If you fail:
restore from last backup and do it again
7. If you success:
Congratulations.
8. Restore apps and data using titanium backup
So, that's all?
now to the question part.
1. which partition should I backup in twrp for a nandroid backup?
I'm still not sure, I'm guessing all of them
2. does magisk work instead of the LineageOS su add on?
3. what does data partition include if I wipe it?
(I want to know what data Id lose)
4. do I need no Verity opt encrypt or not?
(I used to flash it alongside the SU file)
Please answer the questions, and if you know that something is wrong with the steps I'm gonna do help
Additional information:
Device: Galaxy S7 (herolte)
ROM: LineageOS 14.1
Mo10 said:
Hello, I rooted almost 20 days ago and I want to change my rom and I have some questions Because I don't want to lose ANY data or delete my OS like the last time I tried rooting...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3529197
If all else fails, try posting your question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3341138
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Mo10 this is not device specific. You have a good plan. The nandroid backup default settings in twrp is OK for your purpose. I'm not convinced about titanium backup. Maybe you have to restore some apps manually. It's always a good idea to have login names, passwords, contacts etc stored in a safe place.
2 magisk works, but it's to much trouble. Can be necessary for Pokémon or banking or some sound mods.
3 data is all your apps and the app data. If an app asks for memory access, it can write outside of data
I was attempting to install the Begonia Recovery Project for Miui 12.5 (android 11) using the fastboot method. But when I reboot into this new recovery and look inisde the "install" tab, all my folders from my main storage are made up of random letters and numbers.
I assume that this means that my files are still encrypted but I am not sure how to decrypt them.
I am running MIUI 12.5.3 Global edition on android 11 and the Begonia Recovery Project version I downloaded and installed was from this website : https://www.pling.com/p/1556862/
Furthermore, I have a unlock pattern on my phone but when I boot into the custom recovery, it doesn't ask me for my unlock pattern. Could this be the reason all my files are named with random letters and numbers?
It won't let me boot back into my operating system and when I try, I get an warning saying "No OS Installed! Are you sure you wish to reboot?". Rebooting leads me right back into the custom recovery, with all files still named with random characters.
I would prefer to be able to boot back into my system without having to lose any of my personal files on my phone (if that is possible).
Any help is greatly appreciated and I thank you in advance
Sqorpz said:
I was attempting to install the Begonia Recovery Project for Miui 12.5 (android 11) using the fastboot method. But when I reboot into this new recovery and look inisde the "install" tab, all my folders from my main storage are made up of random letters and numbers.
I assume that this means that my files are still encrypted but I am not sure how to decrypt them.
I am running MIUI 12.5.3 Global edition on android 11 and the Begonia Recovery Project version I downloaded and installed was from this website : https://www.pling.com/p/1556862/
Furthermore, I have a unlock pattern on my phone but when I boot into the custom recovery, it doesn't ask me for my unlock pattern. Could this be the reason all my files are named with random letters and numbers?
It won't let me boot back into my operating system and when I try, I get an warning saying "No OS Installed! Are you sure you wish to reboot?". Rebooting leads me right back into the custom recovery, with all files still named with random characters.
I would prefer to be able to boot back into my system without having to lose any of my personal files on my phone (if that is possible).
Any help is greatly appreciated and I thank you in advance
Click to expand...
Click to collapse
This is the reason why everyone recommends taking a backup of your files and resetting your device prior to such attempts. Unfortunately, most likely you will lose part, if not all of your files.
That No OS Installed error is normal since MIUI is a system on root OS and TWRP isn't able to detect them.
That random named folders is your internal storage but it's encrypted. You'll need to enter your passcode every time you boot to TWRP. If it doesn't ask you go to Mount and select Decrypt Data
To disable encryption you'll need to format data and install Disable ForceEncrypt. Doing this will erase EVERYTGHING. (except Find Device,IMEI's etc)
I would recommend you to install this TWRP to decrypt them.
If your device boots back to TWRP, it might be triggering Rescue Party. (click the 3rd button on the bottom of the screen to view the logs)
Fytdyh said:
This is the reason why everyone recommends taking a backup of your files and resetting your device prior to such attempts. Unfortunately, most likely you will lose part, if not all of your files.
Click to expand...
Click to collapse
I had installed twrp like this before and never had this type of error. But yes, the smart thing would definately be to always have backups. Lesson learned for next time!
Canny1913 said:
That No OS Installed error is normal since MIUI is a system on root OS and TWRP isn't able to detect them.
That random named folders is your internal storage but it's encrypted. You'll need to enter your passcode every time you boot to TWRP. If it doesn't ask you go to Mount and select Decrypt Data
To disable encryption you'll need to format data and install Disable ForceEncrypt. Doing this will erase EVERYTGHING. (except Find Device,IMEI's etc)
I would recommend you to install this TWRP to decrypt them.
Click to expand...
Click to collapse
Thank you for the fast reply.
I installed the twrp that you recommended. TWRP still isn't asking for my passcode and I can't find a "Decrypt Data" option in the Mount section. The only checked options in Mount are "Data", "Cache", and "Micro SD Card".
Is Disable ForceEncrypt needed in order to be able to boot back into my operating system? Is there any way to boot back into my OS without this?
Thanks again for the fast reply!
Sqorpz said:
Thank you for the fast reply.
I installed the twrp that you recommended. TWRP still isn't asking for my passcode and I can't find a "Decrypt Data" option in the Mount section. The only checked options in Mount are "Data", "Cache", and "Micro SD Card".
Is Disable ForceEncrypt needed in order to be able to boot back into my operating system? Is there any way to boot back into my OS without this?
Thanks again for the fast reply!
Click to expand...
Click to collapse
That zip can only be used if your data is formatted. If you flash it without formatting data you'll be making the situation even worse because it won't allow you to decrypt anymore. (it makes the phone think data isnt encrypted tho it clearly is encrypted)
Also did you check the logs as i suggested to determine the reason why the phone is not booting?
Canny1913 said:
That zip can only be used if your data is formatted. If you flash it without formatting data you'll be making the situation even worse because it won't allow you to decrypt anymore. (it makes the phone think data isnt encrypted tho it clearly is encrypted)
Also did you check the logs as i suggested to determine the reason why the phone is not booting?
Click to expand...
Click to collapse
Whoops, I used the twrp you recommended without formatting the data. Does this mean my data is forever undecryptable?
I checked the logs and indeed it is triggering the Android Rescue Party.
It suggests possible solutions that are
wipe caches, and/or
Format data, and/or
Clean-flash your ROM.
The reported problem is :
'--reason=enablefilecrypto_failed'
Sqorpz said:
Whoops, I used the twrp you recommended without formatting the data. Does this mean my data is forever undecryptable?
I checked the logs and indeed it is triggering the Android Rescue Party.
It suggests possible solutions that are
wipe caches, and/or
Format data, and/or
Clean-flash your ROM.
The reported problem is :
'--reason=enablefilecrypto_failed'
Click to expand...
Click to collapse
No i didnt meant that, i said the Disable ForceEncrypt zip needs data to be formatted.
The reported problem unfortunately means your phone cannot setup encryption. (thats why twrp won't decrypt it)
The only solution is to format data to make the phone usable again.
(you might as well flash the disable encryption zip after formatting the data since encryption on android is a pain in the ass and it makes the phone a bit faster)
By the way, do not wipe data, just click Format Data and format it since it doesn't get rid of the encryption properly.
T
Canny1913 said:
No i didnt meant that, i said the Disable ForceEncrypt zip needs data to be formatted.
The reported problem unfortunately means your phone cannot setup encryption. (thats why twrp won't decrypt it)
The only solution is to format data to make the phone usable again.
(you might as well flash the disable encryption zip after formatting the data since encryption on android is a pain in the ass and it makes the phone a bit faster)
By the way, do not wipe data, just click Format Data and format it since it doesn't get rid of the encryption properly.
Click to expand...
Click to collapse
Thank you so much for your informative responses.
Apologies, I thought you meant that flashing different twrp would lead to undecryptable files.
By formatting data do you mean the parition on my phone called "data"?. I forgot to add that files in my "data" folder have sensible names and don't look encrypted. Is it normal for it to just encrypt my internal storage?
By the sounds of it, I think I will proceed with your suggestion of formatting the data. Just to clarify, will this method also remove everything in my internal storage, eg pictures, music, videos?. Is there a way to continue with this method without having to lose those?
I appreciate your help greatly.
Sqorpz said:
Thank you so much for your informative responses.
Apologies, I thought you meant that flashing different twrp would lead to undecryptable files.
By formatting data do you mean the parition on my phone called "data"?. I forgot to add that files in my "data" folder have sensible names and don't look encrypted. Is it normal for it to just encrypt my internal storage?
By the sounds of it, I think I will proceed with your suggestion of formatting the data. Just to clarify, will this method also remove everything in my internal storage, eg pictures, music, videos?. Is there a way to continue with this method without having to lose those?
I appreciate your help greatly.
Click to expand...
Click to collapse
They actually encrypted the whole partition till Android 10. This required you to enter a password before the phone boots up but now they only encrypt the internal storage,apps and app data so you don't have to enter a password anymore before the phone boots-up.
Yes formatting the data will erase everything on your device including the internal storage.
Because they are encrypted just like the other part of data there's no way to save them.
Canny1913 said:
They actually encrypted the whole partition till Android 10. This required you to enter a password before the phone boots up but now they only encrypt the internal storage,apps and app data so you don't have to enter a password anymore before the phone boots-up.
Yes formatting the data will erase everything on your device including the internal storage.
Because they are encrypted just like the other part of data there's no way to save them.
Click to expand...
Click to collapse
I see. So could this have been avoided if I had flashed the twrp after disabling my password? Is it a smart practice to disable your password before doing stuff like flashing a custom recovery?
Obviously losing all my data and internal storage is definately a kick in the nuts. But it is also my fault for not backing up my data before experimenting like this.
Could you please send me an oultine of the steps I need to follow in order to proceed with your method of getting my phone working again. Frankly, I have little experience in this area and I'm afraid i'll make a mistake in the process. I also trust in your expertise and experience far greater than mine.
Thank you again!
Sqorpz said:
I see. So could this have been avoided if I had flashed the twrp after disabling my password? Is it a smart practice to disable your password before doing stuff like flashing a custom recovery?
Obviously losing all my data and internal storage is definately a kick in the nuts. But it is also my fault for not backing up my data before experimenting like this.
Could you please send me an oultine of the steps I need to follow in order to proceed with your method of getting my phone working again. Frankly, I have little experience in this area and I'm afraid i'll make a mistake in the process. I also trust in your expertise and experience far greater than mine.
Thank you again!
Click to expand...
Click to collapse
Simple, enter TWRP, go to Wipe, click Format Data, type yes then hit enter. Your data will be wiped. reboot the phone in Recovery mode (not to the normal OS or else the phone will encrypt again) again so the internal storage gets created.
Plug your phone into a PC, download this:https://zackptg5.com/downloads/archive/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
copy it to your phone and install it. If you want to use Magisk, install Magisk first then this zip file. The encryption will be completely disabled.
To answer your first question, It wasn't your fault because i have no idea why your storage got corrupted in the first place but you should definitely disable the password (or disable the encryption if you want to use a password) before doing anything.
Canny1913 said:
Simple, enter TWRP, go to Wipe, click Format Data, type yes then hit enter. Your data will be wiped. reboot the phone in Recovery mode (not to the normal OS or else the phone will encrypt again) again so the internal storage gets created.
Plug your phone into a PC, download this:https://zackptg5.com/downloads/archive/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
copy it to your phone and install it. If you want to use Magisk, install Magisk first then this zip file. The encryption will be completely disabled.
To answer your first question, It wasn't your fault because i have no idea why your storage got corrupted in the first place but you should definitely disable the password (or disable the encryption if you want to use a password) before doing anything.
Click to expand...
Click to collapse
Since I am reseting my phone to its factory settings, I researched into some ROMs that I may use instead of MIUI. I came across the Pixel Experience ROM and I'm considering installing it.
I read somewhere that flashing a ROM involves having to disable encryption every time you flash a new ROM or something along those lines. Will installing the Disable ForceEncrypt disable encryption permanently or will I have to considering installing it again if I want to flash the Pixel Experience ROM?
Sqorpz said:
Since I am reseting my phone to its factory settings, I researched into some ROMs that I may use instead of MIUI. I came across the Pixel Experience ROM and I'm considering installing it.
I read somewhere that flashing a ROM involves having to disable encryption every time you flash a new ROM or something along those lines. Will installing the Disable ForceEncrypt disable encryption permanently or will I have to considering installing it again if I want to flash the Pixel Experience ROM?
Click to expand...
Click to collapse
You will have to install it again if you install a new ROM or kernel since it modifies both of them (they both get wiped if you install or update the ROM.
I recommend you follow their install guide since a lot of people get confused when they see errors.
Flashing PE A12
1. Flash latest Firmware. 2. Flash latest Dynamic TWRP. 3. Reboot to Dynamic TWRP. 4. Flash latest PE rom zip and then format data. 5. Reboot and enjoy. Links Here: Dynamic TWRP: TWRP For A12 Note: If you see any red line errors on twrp just ignore them and continue flashing. Also before...
telegra.ph
Canny1913 said:
You will have to install it again if you install a new ROM or kernel since it modifies both of them (they both get wiped if you install or update the ROM.
I recommend you follow their install guide since a lot of people get confused when they see errors.
Flashing PE A12
1. Flash latest Firmware. 2. Flash latest Dynamic TWRP. 3. Reboot to Dynamic TWRP. 4. Flash latest PE rom zip and then format data. 5. Reboot and enjoy. Links Here: Dynamic TWRP: TWRP For A12 Note: If you see any red line errors on twrp just ignore them and continue flashing. Also before...
telegra.ph
Click to expand...
Click to collapse
Thank you for all your help. It was probably simple and easy for you but for me, I had no idea what I was doing and would never have done the steps that you suggested so thank you. I really appreciate all the help you've given me.
I just have one last request that is : do you know any good backup services for android? I know about services like google photos for backing up photos and videos, but I was wondering if there were any that backed up the android as a whole, including app data/progress, photos, videos, notes etc.
Thank you again for all your support and making this process very simple and easy and wish you all the best.
Sqorpz said:
Thank you for all your help. It was probably simple and easy for you but for me, I had no idea what I was doing and would never have done the steps that you suggested so thank you. I really appreciate all the help you've given me.
I just have one last request that is : do you know any good backup services for android? I know about services like google photos for backing up photos and videos, but I was wondering if there were any that backed up the android as a whole, including app data/progress, photos, videos, notes etc.
Thank you again for all your support and making this process very simple and easy and wish you all the best.
Click to expand...
Click to collapse
Google One app can backup photos,SMS, phone call history and redownloads all of the apps (except apps that were installed from an apk file)
Pixel Experience actually bypasses the Google Photos storage limit so you can backup your entire gallery without problems.
For notes just use Google Keep, it syncs the notes to your Google account.
App data can be backed up by Titanium Backup or Migrate. (i suggest you test them before backing up your entire app data as suggested by Migrate developer)
I don't exactly recommend backing up Data as a whole since your only option is TWRP and TWRP loves to complain when it comes to backing up and restoring.
Thanks for the best wishes and i wish you all the best too. Have a good one.