Related
I am not responsible for any damage your nook suffers.
Officially supported by The Nooter Project for Nook Simple Touch
http://code.google.com/p/nooter/
Touch-Formatter
(Tool to return to stock)
Information:
What it does:
Formats: /data, /cache, /system
Installs 1.1 /system.
Regenerates /data automatically.
Bugs:
CWM may not refresh the screen correctly when booted, move the cursor with the right keys so it refreshes the screen.
If CWM hangs while rebooting, dont worry, force shutdown, and start your nook again, nothing bad happens.
Future updates: (In order of priority).
Update to 1.1.2
Be compatible with NSTG (Nook Simple Touch Glowlight)
Differentiate between the NST and NSTG (Nook Simple Touch Glowlight) so to make only one zip.
Backup /factory + Wipe the complete NST + Recreate the whole NST partition table + Restore /factory
User manual:
Things you will need:
CWM
Thread: http://forum.xda-developers.com/showthread.php?t=1360994
Direct download links:
http://forum.xda-developers.com/attachment.php?attachmentid=806435&d=1323121399
http://forum.xda-developers.com/attachment.php?attachmentid=806434&d=1323121315
Download it and burn it to an sd-card, (windows users use this to burn the image https://launchpad.net/win32-image-writer/+download)
You must have an external microSDCard reader to burn CWM, not the NST.
The button layout of CWM:
Both Buttons on the left: BACK
Upper button on the right: UP
Lower button on the right: DOWN
n button: SELECT
Power button: TOGGLE DISPLAY
Zips:
Download http://nooter.googlecode.com/files/Alpha-FormatTouch-2.zip
Old:
Download http://nooter.googlecode.com/files/Alpha-FormatTouch.zip and copy it on the sd card burnt with CWM
Instructions:
Copy the zip onto the root directory of the sdcard you burned the CWM.(Don't extract them)
Insert the sdcard on your nook, and boot it.
On CWM select install zip from sdcard
Then select choose zip from sdcard
Select Alpha-FormatTouch-2.zip, click yes and wait till the process finishes.
Go back, eject the sd card, and click reboot.
On future updates I'll try: automatically make a backup of /factroy, recreate the whole nook partition table so that people that screw hard can breathe new life into their NST easily.
Index
Automatic Methods:
[NST]MinimalTouch 1.1beta5
[NST]Touch-Formatter
Manual Tutos:
Skip registration (OOBE)
Making the manual process LESS PAINFULL
Setting up adb manually on the nook touch
Setting up root access on NST through adb and installing busybox
Improve battery life(testing)
Backup bookmarks and annotations(testing)
Enable non market app installs
Installing XorZone's B&N button modifier
Change the powered off screen image
Blocking OTA updates
Installing new fonts for your nook (testing)
Installing Gapps (+launcher, etc)
Totally uninstall Gapps (my repack), unrooting, erasing and restoring
Interesting or useful specific apps or hacks for Nook Simple Touch
nook 1.1 update
Thanks to:
ros87 for n2T-Recovery (http://forum.xda-developers.com/showthread.php?t=1289233)
mali100 for the correct command for the /data restoration and for CWM (http://forum.xda-developers.com/showthread.php?t=1360994)
bisbal for trying it out and giving ideas.
meghd00t for pointing out factory.zip is common across more than one NST and researching how to Resize Nook STR Partitions (http://forum.xda-developers.com/showthread.php?t=1225196)
dobbing for the copy of the 1.1 update.
Thanks eded333. Seems Nook touch developers are back on track. Glad to see all the busy posts. Cheer up.
eded333 said:
As some people where having trouble returning to stock after rooting, this is a semi automatic method, easy to follow, that will leave your nook stock (if you havent erased the unique data, flashing Noogie into the NST, which isnt recoverable ¬¬).
Click to expand...
Click to collapse
eded333,
Could you tell where unique data kept (what files)?
Hopefully, it’s small enough and easy to backup / zip
If Touch-Formatter can read the file from SD, it can restore unique data easily, right?
ApokrifX said:
eded333,
Could you tell where unique data kept (what files)?
Hopefully, it’s small enough and easy to backup / zip
If Touch-Formatter can read the file from SD, it can restore unique data easily, right?
Click to expand...
Click to collapse
If i'm not wrong /rom and /factory both hold unique info for every nook, as mac, etc.
If you root your device, the only partitions which are touched are /data and /system, so dont worry for that.
Yes, it should be easy to, for example, to create a Backup.zip which did a backup of those files, partitions, or anything you want and then add to this or another zip a way to restore them from the SD.
Anyway there is allready a tuto for something like that, which creates a full backup of your Nook and it should be the first step before playing with it:
http://forum.xda-developers.com/showthread.php?t=1142983
Edit:
The backup done by CWM dosn't backup /rom and /factory.
So do I have to register again after using this? Or does it stay registered? (I haven't had to wipe my Nook in a while. I'm so proud of myself! xD)
Googie2149 said:
So do I have to register again after using this? Or does it stay registered? (I haven't had to wipe my Nook in a while. I'm so proud of myself! xD)
Click to expand...
Click to collapse
This completely erases /data /cache and /system.
So... yes , you will need to register again, after using this.
eded333 said:
If i'm not wrong /rom and /factory both hold unique info for every nook, as mac, etc.
If you root your device, the only partitions which are touched are /data and /system, so dont worry for that.
Yes, it should be easy to, for example, to create a Backup.zip which did a backup of those files, partitions, or anything you want and then add to this or another zip a way to restore them from the SD.
Anyway there is allready a tuto for something like that, which creates a full backup of your Nook and it should be the first step before playing with it:
http://forum.xda-developers.com/showthread.php?t=1142983
Or you can use the latest CWM: http://forum.xda-developers.com/showthread.php?t=1360994
Click to expand...
Click to collapse
That’s exactly what I want to avoid – to create full 1.8GB backup.
Isn’t it nice to have tiny backup, email to self, just in case?
There is /rom folder, but no /factory one.
/rom “zipped” is 32KB only
Searched both threads you mentioned – cannot find anything related to /factory folder.
Does /rom/devconf backup sufficient?
ApokrifX said:
That’s exactly what I want to avoid – to create full 1.8GB backup.
Isn’t it nice to have tiny backup, email to self, just in case?
There is /rom folder, but no /factory one.
/rom “zipped” is 32KB only
Searched both threads you mentioned – cannot find anything related to /factory folder.
Does /rom/devconf backup sufficient?
Click to expand...
Click to collapse
While your idea with just backing up the unique data (which resides in both the rom partition and the factory one) might seem a good one, what happens when you screw up your NST the way that 99% of the users that asks me for help does?
If you delete/corrupt/overwrite boot, rom, factory or data, then your tiny rom backup won't help you much unless you can get a copy of the other partitions from someone else.
And then there's the problem with alignment of the data partition, which is part of an extended partition.. The first thing people usually kills is the partition table , and simply restoring it from another NST will (in 70% of the cases) not bring back the extended partitions
My vote would be a little yes and mostly no
ros87 said:
While your idea with just backing up the unique data (which resides in both the rom partition and the factory one) might seem a good one, what happens when you screw up your NST the way that 99% of the users that asks me for help does?
If you delete/corrupt/overwrite boot, rom, factory or data, then your tiny rom backup won't help you much unless you can get a copy of the other partitions from someone else.
And then there's the problem with alignment of the data partition, which is part of an extended partition.. The first thing people usually kills is the partition table , and simply restoring it from another NST will (in 70% of the cases) not bring back the extended partitions
My vote would be a little yes and mostly no
Click to expand...
Click to collapse
I think a backup of ROM itself should be a yes. Because if you have that and somehow completely absolutely destroy your partition, you will be able to with a little work and kindness from others eventually completely restore your device, in fact you could create a generic copy of the partitions blank or otherwise then use that to restore a device, have a script take the rom insert it write /boot /system etc for you and you're good to go.
However this shouldn't be used in place of a proper backup.
ros87 said:
While your idea with just backing up the unique data (which resides in both the rom partition and the factory one) might seem a good one, what happens when you screw up your NST the way that 99% of the users that asks me for help does?
If you delete/corrupt/overwrite boot, rom, factory or data, then your tiny rom backup won't help you much unless you can get a copy of the other partitions from someone else.
Click to expand...
Click to collapse
That’s where you Touch-Formatter helps me.
It’ll restore generic copy, my tiny backup makes it “personal” than.
That’s how B&N does it on factory, right?
---------- Post added at 03:43 AM ---------- Previous post was at 03:39 AM ----------
BTW: Where is factory partition?
Code:
#df
/dev: 116512K total, 0K used, 116512K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16116K total, 217K used, 15899K available (block size 512)
/system: 285583K total, 196911K used, 88672K available (block size 1024)
/data: 808292K total, 313252K used, 495040K available (block size 4096)
/cache: 237987K total, 8344K used, 229643K available (block size 1024)
/sdcard: 7774208K total, 113824K used, 7660384K available (block size 32768)
/media: 241947K total, 759K used, 241187K available (block size 512)
---------- Post added at 03:51 AM ---------- Previous post was at 03:43 AM ----------
GabrialDestruir said:
...in fact you could create a generic copy of the partitions blank or otherwise then use that to restore a device, have a script take the rom insert it write /boot /system etc for you and you're good to go.
Click to expand...
Click to collapse
Gabrial,
Do you think it’ll be possible to connect via adb and push back /rom partition content to restored generic image.
Providing we replaced uRamdisk and can use adb connect via USB.
Would it be sufficient?
ApokrifX said:
That’s where you Touch-Formatter helps me.
It’ll restore generic copy, my tiny backup makes it “personal” than.
That’s how B&N does it on factory, right?
---------- Post added at 03:43 AM ---------- Previous post was at 03:39 AM ----------
BTW: Where is factory partition?
Code:
#df
/dev: 116512K total, 0K used, 116512K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16116K total, 217K used, 15899K available (block size 512)
/system: 285583K total, 196911K used, 88672K available (block size 1024)
/data: 808292K total, 313252K used, 495040K available (block size 4096)
/cache: 237987K total, 8344K used, 229643K available (block size 1024)
/sdcard: 7774208K total, 113824K used, 7660384K available (block size 32768)
/media: 241947K total, 759K used, 241187K available (block size 512)
---------- Post added at 03:51 AM ---------- Previous post was at 03:43 AM ----------
Gabrial,
Do you think it’ll be possible to connect via adb and push back /rom partition content to restored generic image.
Providing we replaced uRamdisk and can use adb connect via USB.
Would it be sufficient?
Click to expand...
Click to collapse
It only gets mounted when running restores, not while the system is in use. But yes assuming your generic image had adb access you could push it back to /rom the issue however is that Touch-Formatter while great for returning devices to stock wouldn't fix partition issues, so if you screw up your partitions you'll need more than just this to fix it.
I will work on (when I have some time) making a blank image with just a generic /boot, with all the partitions correctly done of the NST, but empty.
This image, compressed, shouldnt occupy more than a few megabytes, then make a zip which backups the sensitive data, /rom, /factory and create another zip, which should destroy all the data on the NST, burn this empty image, restore /rom and /factory, then trigger automatically reset/restore to end up with a 100% clean nook, even if you screw it hard.
Is this what you were asking for ApokrifX? Or did I get it wrong?
Is there really unique data on /factory ? I thougt there is only some duplicate data from the rom partition.
eded333 said:
Anyway there is allready a tuto for something like that, which creates a full backup of your Nook and it should be the first step before playing with it:
http://forum.xda-developers.com/showthread.php?t=1142983
Or you can use the latest CWM: http://forum.xda-developers.com/showthread.php?t=1360994
Click to expand...
Click to collapse
Making a normal backup with CWM doesn't include the /rom and /factory partition.
mali100 said:
Making a normal backup with CWM doesn't include the /rom and /factory partition.
Click to expand...
Click to collapse
Mmmm, I thought it did a full rom backup, I'll change the advice on the previous post, thanks.
mali100 said:
Is there really unique data on /factory ? I thougt there is only some duplicate data from the rom partition.
Click to expand...
Click to collapse
Yep, factory contains a copy of the rom data which gets extracted to rom when you do a factory restore.
eded333 said:
I will work on (when I have some time) making a blank image with just a generic /boot, with all the partitions correctly done of the NST, but empty.
This image, compressed, shouldnt occupy more than a few megabytes, then make a zip which backups the sensitive data, /rom, /factory and create another zip, which should destroy all the data on the NST, burn this empty image, restore /rom and /factory, then trigger automatically reset/restore to end up with a 100% clean nook, even if you screw it hard.
Is this what you were asking for ApokrifX? Or did I get it wrong?
Click to expand...
Click to collapse
eded333,
That’s exactly what I meant!
---------- Post added at 04:01 AM ---------- Previous post was at 03:01 AM ----------
ros87 said:
Yep, factory contains a copy of the rom data which gets extracted to rom when you do a factory restore.
Click to expand...
Click to collapse
That’s all?
Anyway, where is it (factory partition)?
I.e. what is # in /dev/block/mmcblk0p#
“fdisk -l” shows nothing...
Factory, should be, if i'm not wrong /dev/block/mmcblk0p3
ApokrifX said:
That’s all?
Anyway, where is it (factory partition)?
Click to expand...
Click to collapse
No that's not all
And it's located where eded said it is.
Guys,
Need a little help here:
http://forum.xda-developers.com/showthread.php?p=22214127#post22214127
Basically, how do we change NST MAC?
Sorry, don’t know where else to ask…
Hey guys,
recently i recognized that my GNex was missing some storage space.
As you can see in the pictures it says, only 3GB available whereas apprx. only 5GB are displayed as used. But there should be much more free space.
So i used the App DiskUsage and saw, that 'system data' is taking up 6GB, wich is way too much, right?
Any Ideas how i can fix that?
I'm using TWRP 2.4.3.0.
FuelFlo said:
Hey guys,
recently i recognized that my GNex was missing some storage space.
As you can see in the pictures it says, only 3GB available whereas apprx. only 5GB are displayed as used. But there should be much more free space.
So i used the App DiskUsage and saw, that 'system data' is taking up 6GB, wich is way too much, right?
Any Ideas how i can fix that?
I'm using TWRP 2.4.3.0.
Click to expand...
Click to collapse
no idea how to fix it without a wipe but just for comparison, mine says 2153 MB for System Data
do you have old backups in /data/media/<TWRP or Clockworkmod>
have you updated your recovery?
i, too, had that problem before i realize it was the nandriod backups i had with CWM.
Try deleting your oldest backup and you should see a decrease in your "system data"
Okay, i checked and i should have no backups left.
I already deleted them some days ago. Yesterday somehow i discovered 2 backups in the 'lost+found' folder and have no idea, what they were doing in this spot. So i deleted the, too.
(i did all the deleting with a file explorer[root browser lite] an not with TWRP)
Yea and i updated from TWRP 2.4.1 to 2.4.3 recently.
So whats the way to shrink 'system data'. Isn't it a partition? So i would have to repartition it?
no, 'system data' is not a partition. its a part of the /data partition naming convention aside.
you should verify that your backups are actually deleted, because if you dont do it from the right directory, they will still be there. i had this exact issue with CWM backups on my device, after I had switched over to TWRP, and had to delete the backups from /mnt/shell/emulated/clockworkmod (i think that was the exact path)
Pirateghost said:
no, 'system data' is not a partition. its a part of the /data partition naming convention aside.
you should verify that your backups are actually deleted, because if you dont do it from the right directory, they will still be there. i had this exact issue with CWM backups on my device, after I had switched over to TWRP, and had to delete the backups from /mnt/shell/emulated/clockworkmod (i think that was the exact path)
Click to expand...
Click to collapse
All right, thanks. Found no Backups but i discovered that 'lost+found' had a huge size of 5.5 GB.
So i deleted it via TWRP file manager...and android created a fresh one on the next boot.
It seems that 'Root Browser lite' wich I was using didn't delete all the files (including old backups)l properly and so they endet up in lost+found.
Thanks again for your help!
Pirateghost said:
no, 'system data' is not a partition. its a part of the /data partition naming convention aside.
you should verify that your backups are actually deleted, because if you dont do it from the right directory, they will still be there. i had this exact issue with CWM backups on my device, after I had switched over to TWRP, and had to delete the backups from /mnt/shell/emulated/clockworkmod (i think that was the exact path)
Click to expand...
Click to collapse
This has actually come as a big surprise for me too!!!
I always had in excess of 3GB space hence never bothered checking what was occupying my used memory.
Reading this post I decided to analyze it finally, and CWM is using 2.9GB space in the /mnt/shell/emulated/clockworkmod path!!
Thanks to all who contributed in this post. :good: This is going to help many people. :highfive:
Another surprise:
The disk usage app shows 2.9GB in the above folder, but using ES file explorer, I cannot see anything there.
Will try another file explorer and try.
tgeery said:
no idea how to fix it without a wipe but just for comparison, mine says 2153 MB for System Data
Click to expand...
Click to collapse
I deleted the backups using ROM toolbox Pro!
Now my system data is a measly 1040MB!!! (Down from 3.9GB) And my system is super smooth now.
I am using AOSPA 3.1.
Is such small usage normal?
Hi All,
Hopefully this should be a very quick question. I'm loading CM onto my phone, and this is the first ROM I've ever used. I've loaded CWM, made a backup, and I'm about ready to go and load CW on. I've noticed though that out of the 5 or so gig the phone comes with for internal memory, about 4gb is used up. Is this just the system and the back up and apps?? It seems quite a lot. Will CM fill this up further? Will I encounter any issues?
I hope thats all clear, but excuse me for being a beginner.
EDIT: This is now even more relevant now CM is flashed. I've just looked in the file viewer, and there's still all the folders etc from the old samsung, and amazonmp3 etc etc. I thought the "wipe data/factory reset" in CWM would have cleared all this.....
Many thanks for looking.
floateruk said:
Hi All,
Hopefully this should be a very quick question. I'm loading CM onto my phone, and this is the first ROM I've ever used. I've loaded CWM, made a backup, and I'm about ready to go and load CW on. I've noticed though that out of the 5 or so gig the phone comes with for internal memory, about 4gb is used up. Is this just the system and the back up and apps?? It seems quite a lot. Will CM fill this up further? Will I encounter any issues?
I hope thats all clear, but excuse me for being a beginner.
EDIT: This is now even more relevant now CM is flashed. I've just looked in the file viewer, and there's still all the folders etc from the old samsung, and amazonmp3 etc etc. I thought the "wipe data/factory reset" in CWM would have cleared all this.....
Many thanks for looking.
Click to expand...
Click to collapse
Factory reset only wipes the data partition. For the first time installing a custom ROM, and especially going from stock to cm for the first time, you should wipe the system partition which can be done from cwm.
Sent from the dark side of the moon.
Want to know how to boost your devices performance and battery life? See my thread here: http://forum.xda-developers.com/showthread.php?t=2495269
iKlutz said:
Factory reset only wipes the data partition. For the first time installing a custom ROM, and especially going from stock to cm for the first time, you should wipe the system partition which can be done from cwm.
Sent from the dark side of the moon.
Want to know how to boost your devices performance and battery life? See my thread here: http://forum.xda-developers.com/showthread.php?t=2495269
Click to expand...
Click to collapse
Hi again.
So I finally got round to trying to get this sorted.... and I'm failing. I've booted into CWM, rerun the "wipe/data factory reset", rerun the "wipe cache" then went into "mounts and storage" and did a format of the system partition, but it still hasn't cleared any of the data.
Am I doing something incorrectly? I didn't want to play around with it too much, in case i bork it all. Any help would be massively appreciated.
Also, I'm a bit concerned about what formatting the system partition will do. Does it just clear the rom already on there, and I can then flash Cyanogenmod back on from my sd card?
Thanks
floateruk said:
Hi again.
So I finally got round to trying to get this sorted.... and I'm failing. I've booted into CWM, rerun the "wipe/data factory reset", rerun the "wipe cache" then went into "mounts and storage" and did a format of the system partition, but it still hasn't cleared any of the data.
Am I doing something incorrectly? I didn't want to play around with it too much, in case i bork it all. Any help would be massively appreciated.
Also, I'm a bit concerned about what formatting the system partition will do. Does it just clear the rom already on there, and I can then flash Cyanogenmod back on from my sd card?
Thanks
Click to expand...
Click to collapse
Formatting system partition wipes the currently installed rom / system apps.
How do you know that it is not wiping the data? If you do a system format and your rom still boots then it isn't working properly.
It could be a problem with the version of recovery (cwm / twrp) that you're using. It can't hurt to update it, which could be the case here.
Good luck. Let me know how it goes.
Sent from the dark side of the moon.
iKlutz said:
Formatting system partition wipes the currently installed rom / system apps.
How do you know that it is not wiping the data? If you do a system format and your rom still boots then it isn't working properly.
It could be a problem with the version of recovery (cwm / twrp) that you're using. It can't hurt to update it, which could be the case here.
Good luck. Let me know how it goes.
Sent from the dark side of the moon.
Click to expand...
Click to collapse
Thanks for coming back so quickly!
So if you see the attached, this is what I'm looking at. The phone has 5.5gb internal memory, of which, looking at the below, I'm using about 1.5gb, BUT I only have 1gb left to use, and I get warnings about lack of memory.... So there's 3gb being used for.... I don't know.
When I first put cyanogen on, I noticed that the file structure from stock was still there (i.e. all the folder my old apps made). I expected when I put CM on that it would wipe everything, including all of those folders.
You can try an app called es file explorer, it has a feature that fully scans the contents of the internal SD card.
It should show a list of all the folders from the old stock data folders. You can multi select and delete what you want.
Another option which is more efficient, is to make a full backup of all the internal data in your PC. Then fully format the internal SD card via cwm and transfer which contents you need back from the PC such as photos and music. Asides from photos, music and other media items, most of those internal SD contents aren't needed as Android uses these folders for app data etc.
Always make back ups.
Your welcome.
Sent from the dark side of the moon.
iKlutz said:
You can try an app called es file explorer, it has a feature that fully scans the contents of the internal SD card.
It should show a list of all the folders from the old stock data folders. You can multi select and delete what you want.
Another option which is more efficient, is to make a full backup of all the internal data in your PC. Then fully format the internal SD card via cwm and transfer which contents you need back from the PC such as photos and music. Asides from photos, music and other media items, most of those internal SD contents aren't needed as Android uses these folders for app data etc.
Always make back ups.
Your welcome.
Sent from the dark side of the moon.
Click to expand...
Click to collapse
Yeah, I have got ES File explorer. I couldn't find a "scan" but I've gone through all the folder on my device and I can see the following:
/storage - 3.83gb
/mnt - 2.11gb
/sdcard - 893mb
A lot of this seems to be duplicated though.... The stuff on mnt seems to be a shortcut to whats in sdcard, and all that in storage seems to be in the other two. I don't technically think it's all duplicated, but different ways to get to the same stuff, which makes me very nervous about deleting any of it....
Just got a liitle program to give a break down. See attached.
Surely my system data shouldn't be that big?
I recommend you make a full back up in your PC and format the SD card and transfer the contents of your current SD folder back. I've done it before on different devices, I do it on first root / cm install coming from stock because of all the old obsolete data. Apps like clean master won't removing it because it's marked as important for stock users. It shouldn't be a problem.
Note:
Having different links to the data partition is normal. It's purpose is compatibility.
Sent from the dark side of the moon.
---------- Post added at 12:01 PM ---------- Previous post was at 11:54 AM ----------
It's possible that's reserved for the system. Mine is similar. You can still use it if you convert user apps into system ones.
Sent from the dark side of the moon.
iKlutz said:
I recommend you make a full back up in your PC and format the SD card and transfer the contents of your current SD folder back. I've done it before on different devices, I do it on first root / cm install coming from stock because of all the old obsolete data. Apps like clean master won't removing it because it's marked as important for stock users. It shouldn't be a problem.
Note:
Having different links to the data partition is normal. It's purpose is compatibility.
Sent from the dark side of the moon.
---------- Post added at 12:01 PM ---------- Previous post was at 11:54 AM ----------
It's possible that's reserved for the system. Mine is similar. You can still use it if you convert user apps into system ones.
Sent from the dark side of the moon.
Click to expand...
Click to collapse
Just found this: http://forum.xda-developers.com/showthread.php?t=2083107
It's something to do with backups. I'm gonna read through that thread and see if I can find out what I can/can't delete without bricking the phone.
Massively appreciate your time and repsonses on this iKlutz. Just out of interest, did you do a backup when you installed a rom? Have you found that the backup is this big??
Use ES file explorer or other file manager with root explorer capabilities.
Go to /data/media
You should see:
0
clockworkmod
legacy
obb
In clockworkmod folder I've found a backup (2.0GB) that was made by mistake to internal sotrage, since I allways do backup in CWM Recovery to external SD.
Deleted and 2.0GB were gained.
luisbraz said:
Use ES file explorer or other file manager with root explorer capabilities.
Go to /data/media
You should see:
0
clockworkmod
legacy
obb
In clockworkmod folder I've found a backup (2.0GB) that was made by mistake to internal sotrage, since I allways do backup in CWM Recovery to external SD.
Deleted and 2.0GB were gained.
Click to expand...
Click to collapse
Hmmm. Data/Media is empty.... I might delete the back up from CWM. If the worst happens, I can always flash from the external SD card can't i? Do I "need" that back up of the device when it was stock?
floateruk said:
Hmmm. Data/Media is empty.... I might delete the back up from CWM. If the worst happens, I can always flash from the external SD card can't i? Do I "need" that back up of the device when it was stock?
Click to expand...
Click to collapse
Do not delete.
Copy the folder(s) that you have in the "backup" to the external SD card to the "backup" folder in the "clockworkmod" folder.
Then, you can delete the backup folder located in "data/media/clockworkmod/".
I allways save the backup of the stock ROM's.
To restore in CWM recovery, simply choose "restore from external SD card". And to backup, choose "backup to external SD card", or it will backup to the internal memory.
floateruk said:
Hmmm. Data/Media is empty.... I might delete the back up from CWM. If the worst happens, I can always flash from the external SD card can't i? Do I "need" that back up of the device when it was stock?
Click to expand...
Click to collapse
Did you solve the issue?
luisbraz said:
Did you solve the issue?
Click to expand...
Click to collapse
No.... I don't really know what to do with it.
I've got an s3 mini with Cyanogen and CWM and the system data portion is only 54mb.
I might go into CWM and start deleting things. If I delete the backup I made of my stock phone when I first rooted and added CWM, I can't see too many issues.... I can always flash a stock ROM again can't I?
floateruk said:
No.... I don't really know what to do with it.
I've got an s3 mini with Cyanogen and CWM and the system data portion is only 54mb.
I might go into CWM and start deleting things. If I delete the backup I made of my stock phone when I first rooted and added CWM, I can't see too many issues.... I can always flash a stock ROM again can't I?
Click to expand...
Click to collapse
Yes, using Odin you can flash stock ROM again.
Next time do the backups in CWM to the external SD card!
I have been using TWRP for a while and have been saving backups regularly on the external SD-card. I have restored many times after testing some custom ROM.
Today I tried to restore my most recent backup and after it was done, it throws me back into the boot screen.
I can see a long list of previous backups but when I select them I observe the following, which I had not paid attention to before:
1) the most recent backup involves the partitions System and Data
2) the three next backups show no partitions and TWRP refuses to restore them (and I could swear I had restored from them in the past)
3) a very old backup shows System, Data and Boot
4) an older custom ROM backup also shows System, Data and Boot
Can someone please tell me what you think the problem is here? I cannot go back to my most recent backup.
Make sure you've not somehow ended up with 2 twrp folders with different id's as twrp will only recognize the current Id.
If that's the case copy the backups into that folder.
There is only one TWRP folder. It seems some backups contain "Boot" "Data" and "System" and some backups contain only "System" and "Data" and are missing "Boot".
As I only followed the "defaults" when I did the backups, I need to understand why in some cases it did not save "Boot".
Would you know why?
Zilliman said:
There is only one TWRP folder. It seems some backups contain "Boot" "Data" and "System" and some backups contain only "System" and "Data" and are missing "Boot".
As I only followed the "defaults" when I did the backups, I need to understand why in some cases it did not save "Boot".
Would you know why?
Click to expand...
Click to collapse
I've no idea, never come across it, unless you accidentally unchecked those partitions?
In any case none are full backups.
You should make a backup of EFS and modem too.
ashyx said:
I've no idea, never come across it, unless you accidentally unchecked those partitions?
In any case none are full backups.
You should make a backup of EFS and modem too.
Click to expand...
Click to collapse
I have managed to restore an older backup which had Boot, Data and System partitions. I then restored the latest backup which only had Data and System. It now seems to work. I started it up and it all appears to be in place.
I then booted into TWRP and selected to do a backup and it had automatically selected the Data, System and Boot partitions. Why did it leave Boot out of the previous backups I do not understand but will keep an eye on it from now on.
Regarding the EFS partition: Originally I installed the stock ROM using ODIN. Does this mean that all the partitions were created during that initial installation? Or was the EFS partition present beforehand?
EFS partition is not part of the firmware, so is extremely important to back up, probably the most important of all to backup as it contains a lot of information that could render your device useless if it gets corrupted.
OK, thanks, will do it now.
ashyx said:
EFS partition is not part of the firmware, so is extremely important to back up, probably the most important of all to backup as it contains a lot of information that could render your device useless if it gets corrupted.
Click to expand...
Click to collapse
Can we make EFS checked by default? I had no idea that it's that important..
alexeyp said:
Can we make EFS checked by default? I had no idea that it's that important..
Click to expand...
Click to collapse
"Important" - is there anything other than the IMEI to worry about? On my other, dual-SIM Chinese phones, I used to change the IMEI as I liked.
Yes. And it's ONLY 20MB, compared to the other partitions which are many GB in length.
And Restore should be made to have the partition unchecked by default.
Zilliman said:
"Important" - is there anything other than the IMEI to worry about? On my other, dual-SIM Chinese phones, I used to change the IMEI as I liked.
Yes. And it's ONLY 20MB, compared to the other partitions which are many GB in length.
And Restore should be made to have the partition unchecked by default.
Click to expand...
Click to collapse
Check it and it should stay checked.
And yes it contains a lot of important stuff related to imei, wifi, network, Bluetooth.
Lose it and you could be in trouble.
Search Google for more info.
Im on OOS and made a nandroid backup via TWRP (official)/ Backup size was 5 GB... So i thought this is regard to OOS. Then yesterday i flashed CM ROM and made a nandroid backup.Back up size was 5 GB.. What the hell. Then i looked in to both of OOS and CM TWRP backup folders. I've notice that those commom files on both backups are massive.."system_image_emmc" is 2.4 GB and "system.ext4" is 1GB .. What is this?Why this much of capacity? Is this normal for OP3 or am i doing something wrong?
In twrp, when in the backup section you can go to settings I believe and enable compression.
crazykas said:
Im on OOS and made a nandroid backup via TWRP (official)/ Backup size was 5 GB... So i thought this is regard to OOS. Then yesterday i flashed CM ROM and made a nandroid backup.Back up size was 5 GB.. What the hell. Then i looked in to both of OOS and CM TWRP backup folders. I've notice that those commom files on both backups are massive.."system_image_emmc" is 2.4 GB and "system.ext4" is 1GB .. What is this?Why this much of capacity? Is this normal for OP3 or am i doing something wrong?
Click to expand...
Click to collapse
untick the system image option in twrp when making a backup of anything that doesn't need OTA compatibility. A system image backup will always be the same size because it's taking a backup of the entire /system so it basically makes the empty space take up space in the backup.
Mine is 7.08GB even without system image ?
StykerB said:
untick the system image option in twrp when making a backup of anything that doesn't need OTA compatibility. A system image backup will always be the same size because it's taking a backup of the entire /system so it basically makes the empty space take up space in the backup.
Click to expand...
Click to collapse
Should be system images of OOS vs CM be different capacities? Anyway, if i untick system image emmc, would be a problem when i restoring that backup?
crazykas said:
Should be system images of OOS vs CM be different capacities? Anyway, if i untick system image emmc, would be a problem when i restoring that backup?
Click to expand...
Click to collapse
a system image takes a copy of the entire /system so even the empty space in /system will take up space in the image because the image needs to represent bit for bit the entire /system. A regular system backup intelligently stores the files from /system so it takes up less space but you lose compatibility with anything that requires bit for bit exact /system (basically only OTA's right now) but for any sorta custom rom use it's 100% fine.
You basically only cannot use an incremental OTA from Oneplus if you use a regular system backup.