Database Users

fix_permissions

how do I run fix_permissions on myTouch ?

First off your sig needs an update lol
Extended menu :
* Reboot system now :: reboot your phone
* USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
* Backup/Restore (recovery partition not included!)
o Nand backup :: Make a Nand backup
o Nand + ext backup :: Make a Nand + ext backup
o Nand restore :: Restore a Nand backup
o BART backup :: Make a BART backup (Nand + ext)
o BART restore :: Restore latest BART backup
* Flash zip from sdcard :: Flash a zip update file from your sdcard
* Wipe
o Wipe data/factory reset :: Wipe /data and /cache
o Wipe Dalvik-cache :: Wipe Dalvik-cache both on /data and ext
o Wipe SD:ext partition : Wipe the ext partition on your sdcard
o Wipe battery stats : Wipe the battery stats in /data
o Wipe rotate settings : Wipe the sensor settings in /data
* Partition sdcard
o Partition SD :: Interactive SD partitioning
o Repair SD:ext :: Repair the ext partition
o SD:ext2 to ext3 :: Convert ext2 to ext3
o SD:ext3 to ext4 :: Convert ext3 to ext4
* Other
o Fix apk uid mismatches :: Does extacly that
o Move apps+dalv to SD :: Moves all apps and Dalvik-cache to sdcard (This will NOT enable apps2sd!)
o Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
Click to expand...
Click to collapse

Mikey1022 said:
First off your sig needs an update lol
Click to expand...
Click to collapse
sig updated ,thank you

[GUIDE]How to format your phone properly

How to format your phone properly
Guide updated on 14/05/15
Disclaimer:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this tool
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
This process will wipe all of your data off your phone. This includes all of your apps and system storage. Make sure to backup all of your apps and data to the cloud or onto a computer
Make a backup!! Why am I saying this again? Because there is always a few careless people who do this process and complain how they lost all of their data.
All users of android 4.0.x are warned that factory resetting your phone will hard brick your device. To check if you have brickbug, follow this link: brickbug check Also, a custom recovery is not a custom kernel! Brickbug occurs at kernel level. If you are affected, you will need to install a custom kernel like siyah kernel
Here are some of the ways you can format your phone:
- Manually via recovery
- Using a pit file
- Using hawker's scripts
Formatting manually via recovery:
If you don't have a custom recovery already, flash Philz recovery using odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9100/philz_touch_6.48.4-i9100.zip.md5
Reboot your phone to recovery. If your current ROM doesn't have the option to do this, you can use the app quick boot or you can shut down your phone then use the button combinations to get into recovery (volume up + home + power). Note: Root is need to run the app.
Once in recovery, select and confirm factory reset
Select and confirm wipe cache partition
In mounts and storage, select and confirm format /system and /preload (wiping preload is necessary when switching between stock and custom roms).
Go back to the main menu and go to advanced menu. You will now have to select and confirm to wipe dalvik(or art) cache.
Once all of these has been done, you can install a rom normally.
If you are on TWRP recovery, follow these steps:
Reboot your phone to recovery.
Once in recovery, go to wipe
Tick: Data, system, cache and dalvik cache
Swipe the bar to confirm to wipe
Go back to the main menu
You can now install a rom normally.
If you get errors when formatting the preload partition, you will have to flash this first then you will be able to format the preload partition: http://bit.ly/13ojAEh
Formatting via pit file:
This process will wipe all of your data off your phone. This includes all of your apps, system storage and internal sd card. It doesn't wipe your external sd card. Make sure to backup all of your apps and data to the cloud or onto a computer
Make a nandroid backup onto your external sd card or PC (VERY IMPORTANT!!! All backups in internal sd card will be deleted so move them!)
Download the system pit files (attached in OP)
Extract the zip file
Open ODIN (Attached in the OP, JOdin for linux and OS X)
Connect your phone to your PC via USB while in download mode (make sure your phone is detected on ODIN, it should say COM:{number})
Click on the PIT button and locate and select your desired pit file
Click on PDA or AP and select your kernel .tar file (look at this thread if you don't have one: http://forum.xda-developers.com/galaxy-s2/development-derivatives/convert-kernel-zip-to-tar-t2994381)
Make sure that re-partition has been ticked then click start. If your phone successfully flashes, move onto the next step. If not, try changing usb ports, changing ODIN version, changing pit files or seeing if your device has a corrupt nand (or broken). If your nand is corrupt or broken, you won't be able to flash with ODIN (and you will need to buy a new motherboard). If you are still unsure what to do, look at the screenshot in the attachments.
While your phone reboots, you need to perform the button combination to get into recovery (home button + power button + volume up)
If you have CWM recovery, go to mounts and storage then select format /sd card0 or /internal sd card. Select default and your internal sd card should successfully format. If not, try ext4 format. If you have TWRP recovery, you will need to go to wipe>advanced and select format /sd card then swipe to confirm . If you can successfully format your phone here, skip steps 11, 12, 13, 14.
----IF FORMATTING FAILS IN RECOVERY----
If formatting sd card in recovery fails, connect your phone to your PC. While still in recovery (CWM), go to mounts and storage and select mount mass storage. If you have TWRP recovery, go to mount and select mount sd card. It should prompt you that the storage isn't ready yet and you need to format. If your PC still doesn't detect your phone, check if the proper drivers are installed (in attachments). Also, if your phone doesn't get detected and you've done everything in this step, try changing usb ports, computers and even usb cables.
Click format
You can leave all of the settings to default, I personally like to change the allocation size to 4KB (4KB is good if you want to make the most out of your phone's storage while having enough speed)
Click format.
----AFTER SUCCESSFULLY FORMATTING----
Go back to your phone. You can choose to restore from your backup or install a new rom. If you choose to restore from a backup, skip all of the remaining steps. (Note: DorimanX kernel recoveries can not format /data partition more than 2gb, use an alternative first when restoring a backup then flash back if needed)
In mounts and storage, choose format /data, /cache and /system (Note: DorimanX kernel recoveries can not format /data partition more than 2gb, use an alternative first then flash back if needed)
Now you can flash a ROM as you normally would
Formatting via hawker's script:
Copy HawkerCoreV???.zip onto your device. I have included the zip in the attachments.
Reboot into Recovery
Install zip from SD card>Run HawkerCoreV???.zip
When you are at a stage whereby you want to flash a new CUSTOM ROM and want to do a FULL WIPE before doing so (which I would ALWAYS recommend) the steps are as follows:
If you have not previously done so, download and install the core zip HawkerCoreV???.zip. This will create a folder called /sdcard/HawkerCore
A nandroid backup is recommended beforehand
Install zip from SD card>Run /sdcard/HawkerCore/Scripts/ROMNuke
Install zip from SD card>Flash your new ROM
Reboot
If you are installing a new STOCK ROM and want to do a Nuke then:
A nandroid backup is recommended beforehand
Install zip from SD card>Run /sdcard/HawkerCore/Scripts/ROMNuke
Reboot into Download mode using the button combinations (volume down + home + power button)
Install your stock ROM via Odin
Huge thanks to hawkerpaul for his awesome scripts. Also huge thanks to ElGamal for providing the modified pit files and metalgearhathaway for providing the stock pit file.

Although I know all this already, I find your continued support of our prehistoric S2 to be very helpful to others. I can vouch that these methods are the best way to ensure a full wipe and avoid issues with flashing whatever ROM suits your needs. I personally use a mix of all 3 methods to ensure a fully functional phone. Many thanks for your continual posts throughout the S2 forum here on XDA!

error 1 when try to f2fs data .. any help

cache f2fs works on most tpwr but im not able to convert data to f2fs
always error 1
any working f2fs tpwr link?
iwant both data and cache to f2fs
i think is a problem with mkfs.f2fs.. simply if one is able to fix is really appreciate

Here your are, this is what I'm using:
https://forum.xda-developers.com/le-pro3/development/twrp-multirom-vanilla-mod-t3571543

yes, this twrp works but first you must do a backup, copy the backup to your pc or otg drive, convert the data partition to f2fs and after that tick use -rm instead format in options and restore your data backup.

What to backup with TWRP?

Can I know if I should backup system or system_image, and vendor or vendor_image?
And is there any value to backing up other partitions, or should I just do these ones?

"A full backup/restore of MIUI should consist of no more than:
* Boot
* Data
* System_Image (or System_root)
* Vendor_image"
Took this info from the OrangeFox recovery thread. Personally, I would also back up the /system partition

DATA partition is on F2FS by default?

I've unlocked my new MI9T to install xiaomi.eu rom.
First of all, after unlock, i've installed the official TWRP and i've formatted (not wiped) the DATA partition.
I've noticed that TWRP logged that it was formatting the DATA partition with mkfs.f2fs ...... really strange...
So, i've rebooted to TWRP and changed the DATA partition type to EXT4 and formatted it... after a reboot i've tried to format it again and it was formatted again in F2FS (like F2FS was the default selection).
So i've tried to switch to OrangeFox recovery (i suspected a bug in TWRP)... but the same behaviour...seems that F2FS is the default partition type for my DATA partition.
I've installed the xiaomi.eu (the kernel in this rom is the official one, and i dont think that it supports F2FS) and the rom boot ok, without problems.
I've tried also to force ext4 on DATA, but with this partition type the rom never boot (it remains on the android bootanimation).
So right now, i see a f2fs partition type on my data partition, with original kernel.
I've tried also to change the cache partition to f2fs (by default this partition is formatted in ext4) but in this way, the rom boots, but i can't see the cache partition, seems that effectively the kernel can't mount the cache partition.
so i've unpacked the official miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM_5001481fbb_10.0 rom, and i've found that in the vendor partition, under (vendor)/etc/fstab.qcom there is this entry for DATA partition:
Code:
/dev/block/bootdevice/by-name/userdata /data [B]f2fs [/B]noatime,nosuid,nodev,nodiscard,fsync_mode=nobarrier,reserve_root=32768,resgid=1065 wait,check,fileencryption=ice,wrappedkey,quota,reservedsize=128M,latemount
So, this phone uses by default a F2FS partition type for DATA????

gulp79 said:
...so i've unpacked the official miui_DAVINCIEEAGlobal_V11.0.4.0.QFJEUXM_5001481fbb_10.0 rom, and i've found that in the vendor partition, under (vendor)/etc/fstab.qcom there is this entry for DATA partition:
So, this phone uses by default a F2FS partition type for DATA????
Click to expand...
Click to collapse
Yes - stock QFJEUXM 11.0.4, never formatted (or wiped) Data, see screenshot from /vendor/etc/fstab.qcom