How do I erase everything on galaxy s3 i747 - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

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!!

Related

[Q] how to upgrade to 4.4 from 4.3 a and backup TA

What are all the steps involved from 4.3 bootloader locked to cm11?
Some threads are saying you can brick your internal partition if you don't unlock properly. I used to be a sammy owner( see signature). I'm new to the xperia world. I understand that root is required for TA backup and latest CM need 4.3 baseband. But 4.3 no root with locked bl?
Also, will flashtool flash device with locked bootloader to go from 4.3 > 4.1?
theperson333 said:
What are all the steps involved from 4.3 bootloader locked to cm11?
Some threads are saying you can brick your internal partition if you don't unlock properly. I used to be a sammy owner( see signature). I'm new to the xperia world. I understand that root is required for TA backup and latest CM need 4.3 baseband. But 4.3 no root with locked bl?
Also, will flashtool flash device with locked bootloader to go from 4.3 > 4.1?
Click to expand...
Click to collapse
Also, What is your recommended method of unlocking the bootloader and why?
Please post any answers in a separate thread and link to it, so it can be made a sticky.
I am not responsible if anything goes wrong.
Go to http://xperiafirmware.com/8-firmware/40-sony-xperia-m-c1905, and follow the steps under "Upgrade to latest 4.1.2". This works on locked bootloaders too, and it even works if it is a downgrade, not upgrade.
Stock 4.1.2 is rootable with Framaroot's Gandalf exploit (search for it on XDA), root it. Then you can back up the TA partition, either with the flashtool you have downloaded earlier, or in some manual way. Make absolutely sure it went well before proceeding! I think you have read plenty of warnings if you have asked this question.
Then proceed as usual. Go ask Sony for an unlock key, unlock your phone with fastboot. Download the 4.4 ROM you wish to use, then flash the boot.img of it by
Code:
fastboot flash boot boot.img
. Then boot the phone into recovery mode using
Code:
fastboot reboot
and when it begins to boot, bash the volume up key a few times. Then install your new ROM from recovery.
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
Also, this is from experience, I have a C1905, which I prior upgraded with SEUS to 4.3. The procedure I wrote worked on it nevertheless.
Another thing that happened to me is that in the process my /data partition got corrupted. The "internal sdcard" lives at /data/media, and recoveries want to preserve this folder, so when they can't mount it and rescue files from it, they skip it, and the new ROM won't boot because it can't mount the /data partition either. So if you get a bootloop after installing the new ROM, try formatting /data AND the internal storage, there's an option in the recovery to do this.
When did your /data/ get corrupt? I read on xda that after boot loader unlock, you must boot a stock firmware to format /data/ properly, is this true? I'll post link to that topic when I have access to computer.(new user of xda app)
Sent from my C1905 using XDA Free mobile app
theperson333 said:
When did your /data/ get corrupt? I read on xda that after boot loader unlock, you must boot a stock firmware to format /data/ properly, is this true? I'll post link to that topic when I have access to computer.(new user of xda app)
Sent from my C1905 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know. All I know is that I did these:
Reflash 4.1.2 from flashtool
Boot it, root it, push a busybox on the thing
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img
Pull TA.img from the internal storage to the computer
On phone: busybox md5sum /dev/block/platform/msm_sdcc.1/by-name/TA, on computer: md5sum TA.img, ONLY PROCEED IF CHECKSUMS MATCH! (They matched the first time for me. As a precaution I put them on my Google Drive along with the checksum, they'll be safe there, you should also find a safe place for your own backup in case you want to restore it later.)
Put the phone in fastboot mode, unlock it using the official method, then flash boot.
[*]Start recovery (bashing vol+), flash full ROM from the SD card, then flash Gapps too.
[*]Boot the phone, watch it being stuck on bootanimation.
[*]Pull the battery, start recovery again, wipe /system, flash ROM
[*]Boot phone, watch another 10 minutes of the boot animation
[*]Pull battery, start recovery, wipe everything, notice that /data won't wipe because it won't mount (WTF?)
[*]Do a bit of Googling, realize that recovery is afraid to wipe /data, because the internal storage (/data/media) is inside it, and precious things can be on it (for example the Nandroid backups, the ROM you were about to flash, family photos etc.)
[*]Use "wipe /data and /data/media" in recovery, this really formats the /data partition.
Flash ROM, flash Gapps, reboot phone, be happy with it.
I marked the steps with lime colour in which I am absolutely sure my /data was corrupted, and dark green when I only suspect it.
On second thought, it may have something to do with unlocking the bootloader in the official way. As far as I know, unlocking the bootloader destroys all user data on the phone as a security measure (say your stock ROM has a password you set but an attacker could flash an alternate ROM with no password to access all of your precious data. To prevent this you can't flash an alternate firmware without unlocking the bootloader and destroying sensitive data in the process). And as fastboot is a pretty simple and dumb piece of code (all it has to do is write the internal flash), I wouldn't be surprised if it didn't bother creating a filesystem on the /data partition, but instead just zeroed it all out. Their philosopy seems to be "if you know how to unlock the bootloader, you are a developer, and developers know how to format the /data partition". So, if my train of thought here is correct, my /data was "corrupted" in the steps marked with any shade of green, only this doesn't really mean "corrupted", it means "zeroed out with no filesystem".
The recovery's "wipe /data" command means: mount /data, and delete everything except the /media folder inside, because the internal storage lives at this folder, which most people don't expect to lose when wiping /data, for idiotic historical reasons.
So all zeroes -> no filesystem -> recovery can't mount it -> recovery pees its pants in horror and doesn't touch it, because it thinks "Oh my Glob, this partition does not contain a valid filesystem, but it may have a corrupted filesystem or one that I don't recognise, and formatting it could destroy my owner's data, which could be inside this hypothetical filesystem's /media directory. Which my owner wouldn't expect and then they would think I am a bad recovery."
------
I just re-read your question. I didn't use any stock software after unlocking, my recovery formatted my /data perfectly for me.
thermate said:
I don't know. All I know is that I did these:
Reflash 4.1.2 from flashtool
Boot it, root it, push a busybox on the thing
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img
Pull TA.img from the internal storage to the computer
On phone: busybox md5sum /dev/block/platform/msm_sdcc.1/by-name/TA, on computer: md5sum TA.img, ONLY PROCEED IF CHECKSUMS MATCH! (They matched the first time for me. As a precaution I put them on my Google Drive along with the checksum, they'll be safe there, you should also find a safe place for your own backup in case you want to restore it later.)
Put the phone in fastboot mode, unlock it using the official method, then flash boot.
[*]Start recovery (bashing vol+), flash full ROM from the SD card, then flash Gapps too.
[*]Boot the phone, watch it being stuck on bootanimation.
[*]Pull the battery, start recovery again, wipe /system, flash ROM
[*]Boot phone, watch another 10 minutes of the boot animation
[*]Pull battery, start recovery, wipe everything, notice that /data won't wipe because it won't mount (WTF?)
[*]Do a bit of Googling, realize that recovery is afraid to wipe /data, because the internal storage (/data/media) is inside it, and precious things can be on it (for example the Nandroid backups, the ROM you were about to flash, family photos etc.)
[*]Use "wipe /data and /data/media" in recovery, this really formats the /data partition.
Flash ROM, flash Gapps, reboot phone, be happy with it.
I marked the steps with lime colour in which I am absolutely sure my /data was corrupted, and dark green when I only suspect it.
On second thought, it may have something to do with unlocking the bootloader in the official way. As far as I know, unlocking the bootloader destroys all user data on the phone as a security measure (say your stock ROM has a password you set but an attacker could flash an alternate ROM with no password to access all of your precious data. To prevent this you can't flash an alternate firmware without unlocking the bootloader and destroying sensitive data in the process). And as fastboot is a pretty simple and dumb piece of code (all it has to do is write the internal flash), I wouldn't be surprised if it didn't bother creating a filesystem on the /data partition, but instead just zeroed it all out. Their philosopy seems to be "if you know how to unlock the bootloader, you are a developer, and developers know how to format the /data partition". So, if my train of thought here is correct, my /data was "corrupted" in the steps marked with any shade of green, only this doesn't really mean "corrupted", it means "zeroed out with no filesystem".
The recovery's "wipe /data" command means: mount /data, and delete everything except the /media folder inside, because the internal storage lives at this folder, which most people don't expect to lose when wiping /data, for idiotic historical reasons.
So all zeroes -> no filesystem -> recovery can't mount it -> recovery pees its pants in horror and doesn't touch it, because it thinks "Oh my Glob, this partition does not contain a valid filesystem, but it may have a corrupted filesystem or one that I don't recognise, and formatting it could destroy my owner's data, which could be inside this hypothetical filesystem's /media directory. Which my owner wouldn't expect and then they would think I am a bad recovery."
------
I just re-read your question. I didn't use any stock software after unlocking, my recovery formatted my /data perfectly for me.
Click to expand...
Click to collapse
Is it better to unlock bootloader with flashtool in this case? IS it possible to recreate partition with ADB?
theperson333 said:
Is it better to unlock bootloader with flashtool in this case? IS it possible to recreate partition with ADB?
Click to expand...
Click to collapse
As far as I know, flashtool is just a GUI over fastboot when it comes to unlocking the bootloader, so it does exactly the same thing you would do with fastboot. It makes no difference.
What do you mean by "recreating partition with ADB"?
Are there any adb tools or shell tools accessible from adb to recreate partitions?
Sent from my C1905 using XDA Free mobile app

[Q] Is it possible to wipe system partition before installing a ROM

This is regarding a recently bought tablet Note 8. The current usage of /system partition is at above 75%. I have been trying to wipe/delete all system data in an attempt to have a 'fresh' OS once I install new stock ROM. In CWM recovery, I have even tried to format system partition (in addition to normal data reset, cache wipe and delvek cache wipe).
I installed the new stock ROM 4.4.2 in Download mode. Afterwards I checked and my system partition was still above 75% full. I do understand that system partition is normally read only. I am trying to work out if there is there any way where I can flash the stock ROM whilst completely removing the current system files.
Please offer any guidance or advice regarding this matter. Thanks!
Possible? Yes. Necessary? No.
The installation script for a ROM will almost always format the system partition before setting it up with the new ROM files, unless the developer is doing some special testing and you would know if that is the case.
ramjet73
Yes I think most custom ROMs would wipe system partition too. Though I want to install the stock ROM of Android 4.4.2. I have flashed the ROM about four times now, everytime trying different settings such as wipe/format system drive.
But I always end up with /system drive same size as before.
Thanks for the reply ramjet73.
S2 user said:
Yes I think most custom ROMs would wipe system partition too. Though I want to install the stock ROM of Android 4.4.2. I have flashed the ROM about four times now, everytime trying different settings such as wipe/format system drive.
But I always end up with /system drive same size as before.
Thanks for the reply ramjet73.
Click to expand...
Click to collapse
Depending on how you flash the stock ROM, Odin will flash a .img file to the system partition and completely replace its contents or an updater-script in a stock ROM zip file will format it and then copy all the included /system files to the empty partition.
In either case you cannot control what goes into the initial configuration of the system partition, only delete things that you don't need after it is flashed, unless you flash from a stock ROM zip file and delete items from that before you flash it.
There are scripting tools that can help with ROM "slimming" but I don't know if any are available for the Note 8.0 or not.
ramjet73

Clean Flash Custom Rom

I know I saw this process in a recent thread but I've misplaced it. If anyone can point me to it, I would be grateful.
I want to clean flash CM 13 on my OP3.
From what I remember, I'm supposed to store the CM 13 zip file and gapps file in the SD Card folder. Is that truly correct? The OP3 doesn't have an SD Card though I did find a folder.
If I do a factory reset and wipe everything, won't that folder also get wiped? Then how would I install the ROM from the phone?
Sorry, I know this is a straightforward process for many of you, and dirty flashing is easy. But I think a clean flash is better and I'd rather not guess and end up with a bricked phone I have to fuss with.
Again, I know this exact process is in a thread somewhere but I can't find it.
the phone storage is /sdcard/
u can use something like ES File Explorer and create a folder called CM13 or whatever u want
u do have ur bootloader unlocked and twrp installed, correct?
yes u will just the get cm zip file and put it in a folder (ex. /sdcard/CM13/)
i put the gapps in the same folder
create a nandroid backup
wipe/advance wipe - wipe caches/data/system !!!!Do NOT WIPE - INTERNAL STORAGE OR OTG!!!
then flash cm zip and gapps
Hi, thank you. Yes, bootloader unlocked, twrp installed and I've done it in the past on a different phone but couldn't sort out clean flashing from dirty flashing. I've done it correctly in the past, and it's also gone very wrong for me. I think I mistakenly wiped internal storage once and that was a disaster.
Somewhere I've also read about a factory reset through trwp.
I don't need to do that, or wiping caches/data/system is the same thing?
.
digger16309 said:
Hi, thank you. Yes, bootloader unlocked, twrp installed and I've done it in the past on a different phone but couldn't sort out clean flashing from dirty flashing. I've done it correctly in the past, and it's also gone very wrong for me. I think I mistakenly wiped internal storage once and that was a disaster.
Somewhere I've also read about a factory reset through trwp.
I don't need to do that, or wiping caches/data/system is the same thing?
.
Click to expand...
Click to collapse
If you wipe internal storage, you will lose the zips for your ROM and GAPPS. You can connect your device and have it recognized on your PC from within TWRP if you do accidentally wipe your internal storage.
Factory reset doesn't wipe the system partition as that would remove your OS. Most Roms will wipe your system partition before it installs itself so generally you don't have to wipe the system partition manually, but it's good practice.
Clean flash = wipe dalvik, cache, data; then install ROM (which will wipe system before it installs, or manually wipe system before the ROM install for good measure).
Dirty flash = flash ROM, then wipe dalvik and cache. The only time you should do this if the ROM you're looking to flash says it can be done (ie. CM nightlies).

wipse system in TWRP

I accidentally wiped the system in TRWP and the phone won't boot, it just shows white screen with HTC logo and the red text down.
Did I just wiped my android from the phone?
I can get into bootloader and recovery. But I dont have rom in my internal storage. (because I deleted everything) How can I put rom.zip into my storage again and do the flash?
PLEASE HELP!
delete please have found an answer
JernejB2 said:
delete please have found an answer
Click to expand...
Click to collapse
Threads typically aren't deleted on XDA. If you found a solution, post it for the benefit of others that may have the same/similar issue.
In the future, you shouldn't be wiping anything, if you have no idea what it is, or what the outcome will be. It says right on the TWRP Wipe section, that the default wipe is the only one you need most of the time. And it says that for a reason. And the remaining options are also called "Advanced" for good reason.
Yes, "system" is the Android Operating System. By wiping it, you wiped the whole OS.
Recovering from this is typically done by putting a ROM on removable SD, or alternately using adb push to put a ROM on the phone. Then boot into TWRP and install the ROM.
You should also typically have TWRP backup of your current ROM, for easy recovery. Basic good practice to always have a TWRP "nandroid" backup whenever messing with the phone (root, ROMs, other mods). And there is usually not a good reason to wipe "everything" (all at the same time) and therefore also wipe your backups wherever they may be (internal storage or SD card).

[SOLVED] How to completely wipe literally EVERYTHING

I looked through many threads, posts, websites, and tutorials, but none of them say how to literally wipe my device completely (it could be that it's not possible), what I want to do is completely remove literally everything so that it's like a brand new hard drive without even any files in it.
'Factory Reset' doesn't remove everything because android still boots after a factory reset and android wouldn't be able to boot if there were no files on the device. TWRP doesn't remove everything either because how is twrp running, and I can still see the androids root directories in twrps file manager (TWRP does tell me that there's no OS installed, but then why is there still a functioning file system with actual files in them).
I want to completely wipe everything so that any future roms I download will have no way to be affected by any old kernels/roms/apps that I have installed in the past. I want to clean install android on top of a literally empty phone hard drive. If this isn't possible then what's the closest to that that I can get? Cuz I tried various roms and I had bugs that persisted between multiple roms even though other people said that they didn't have these issues.
In case you're wondering: I'm currently running LineageOS 15.1, oreo 8.1
Your best bet it to wipe using stock image. Reinstall TWRP and wipe system, cache and data before installing new ROM
I agree with the advice given by Vanschtezla.
Also, if you would completely wipe all data on the phone's storage then that would also wipe the partition table. The storage area is divided into partitions which are mounted to for example /system /data and /cache when your phone boots.
Also there is no real need to "wipe everything" as you say as that could brick your phone. If you just boot TWRP and wipe using "Factory reset" and additionally: System then everything should be clean enough to install a new ROM. Depending on the ROM it will wipe the System partition anyway.
Kernels reside in the system partition so when you wipe System, any Kernel is gone
Pre installed (system) Apps sit in the System partition so wipe System and they are gone
User Apps sit in the data partition so wipe data (that is included in the Factory reset) and they're gone
All in all I think you're expecting issues that simply do not exist. Especially if you just follow the instructions of the (custom) ROM you want to install.
THANK YOU!
peterpv said:
I agree with the advice given by Vanschtezla.
Kernels reside in the system partition so when you wipe System, any Kernel is gone
Pre installed (system) Apps sit in the System partition so wipe System and they are gone
User Apps sit in the data partition so wipe data (that is included in the Factory reset) and they're gone
Click to expand...
Click to collapse
This is exactly what I was looking for! Why don't any "How to wipe your phone" guides say these things (even the ones that get more technical don't mention what exactly gets deleted for each wipe option, which is why from your perspective it was probably very weird to read my question).

Categories

Resources