Hi, I need incease partitions of Userdata. I found some tutorials and for me it looks fine this: http://forum.xda-developers.com/showthread.php?t=2710480.
Unfortunatelly I can't go over step about remove partitions because according to log are being used. I tried a lot of possibility with parted and fdisk but somehere I do mistakes. Can me help with this. See attachment with my steps. Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found solution after many experiments. The biggest problem it was unmount partitions and then these partitions remove. These things were possible do in OMNI ROM 4.4.4 over ADB. I found this solution here: http://forum.xda-developers.com/showthread.php?t=2712253&page=11
My steps:
0 - You download scripts fs-utils from here - http://forum.xda-developers.com/showthread.php?t=2712253 and copy to MicroSDCard
1 - Install OMNIROM 4.4.4
2 - I was fighting with connection of ADB. I can't run ADB Sideload because I can't connect. I was only freely in recovery menu. I used following commands:
adb shell (this command connect command line to phone and in prompt I had something this ~ # 6 --> don't worry ... try to command ls and if will be listed folder from mobile so thats OK)
adb kill-server
adb start-server
adb devices
You have to try so long until will not correct adb shell .
3 - Now I had the biggest problem. At any cost you have to run unmount(command UMOUNT) and remove(command RM) partitions.
umount /sdcard
umount /data
parted /dev/block/mmcblk0
rm 14
rm 15
mkpartfs logical ext2 1621 5865
name 14 Userdata
mkpartfs logical ext2 5865 7818
name 15 SDCard
quit
These commands must be done. If not something is wrong and you have to fix it some way.
Then it's easy. Run following commands
cd /ext_card/fs-utils
tune2fs -j /dev/block/mmcblk0p14
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p14
e2fsck -fpDC0 /dev/block/mmcblk0p14
tune2fs -j /dev/block/mmcblk0p15
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p15
e2fsck -fpDC0 /dev/block/mmcblk0p15
chown -R 2800:2800 /sdcard
After all steps I didn't have mounted internal SDCard. This is very small problem. In new recovery I formated as vfat and then I formated as ext4 and after restart it was mounted. Resize internal sdcard for apps DONE.
Related
Hi all,
after i resize my SD with MiniTool Partition Wizard and create a Linux Swap partition my swap on mobile wan't work. also when i want to create a ext4 for data2sd, it also wan't work -.-
don't have any idea..
Use GingerDX v21 + Alfs v06
safix8 said:
Hi all,
after i resize my SD with MiniTool Partition Wizard and create a Linux Swap partition my swap on mobile wan't work. also when i want to create a ext4 for data2sd, it also wan't work -.-
don't have any idea..
Use GingerDX v21 + Alfs v06
Click to expand...
Click to collapse
hi try this FAT32/EXT2/LINUX SWAP for now
testing only then if work upgrade to ext4
use minitools partition then download userinit.txt
go to this thread
xpraken said:
do this
1) download userinit.txt below to root of sdcard
2) boot into CWM recovery
3)mount /sdcard, /sd-ext (if you have ext partition) and /system
4) run: adb shell
5) move userinit.sh to /sd-ext ->
mv /sdcard/userinit.txt /sd-ext/userinit.sh
6) then,
chmod 755 /sd-ext/userinit.sh
7) reboot
this step will activate the swap without using app like swapper2
Click to expand...
Click to collapse
9) run sdparted: for the differents options see the original thread
This is for my configuration -> sdparted -es 1024M -ss 128M -efs ext3
also when i create partitions with minitool partition?
Swap using terminal emulator:
bash
cd /sdcard
dd if=/dev/zero of=[swap filename] bs=1024k count=[Size in MB]
# E.g. dd if=/dev/zero of=swapfile.swp bs=1024k count=32
# Creates a 32mb empty file called swapfile.swp on sdcard
mkswap [swap filename]
# Formats swap file
[wait at least 30 secs after doing this then]
swapon [swap filename]
# This enables the swap file (NOT swap using Partition)
# [swapoff [swap filename]] (Disable Swap. Be Patient while swap contents are emptied)
----
or if you were looking for partitions...
swapon [Linux swap partition] (/dev/****)
after i successfully parted my sd, moved the userinit tu sd-ext, the Recovery can mount sd-ext.
when i want to boot to rom, it will stuck on Alfs Kernel Boot logo.
i have create an fat32/ext2/swap partition
What do i wrong
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i'm wondering about people who gets ext and swap work fine.
i work over an week to get swap and ext partition to work -.-
could be the sd card itself be the problem?
safix8 said:
could be the sd card itself be the problem?
Click to expand...
Click to collapse
Safix8 it'a not your fault..it's a problem of kernel..i and few people have this problem..the solution for me is remove the ext partition and for swap partition look here. so, swap work for me..
safix8 said:
9) run sdparted: for the differents options see the original thread
This is for my configuration -> sdparted -es 1024M -ss 128M -efs ext3
also when i create partitions with minitool partition?
Click to expand...
Click to collapse
men this how i work with ext2 and swap (linux swap)
use minitools to partition fat32/ext2/linuxswap
i download the userinit.txt and edit the swappiness to 200 bcoz my linux swap is 257mb
then
poweroff ur phone
boot to cwm or xrecovery
mount /sd-ext and /sdcard
first to know if ur phone is connected
type adb devices
if on the list the phone is connected
next
run adb shell
type this
mv /sdcard/userinit.txt /sd-ext/userinit.sh
and
chmod 755 /sd-ext/userinit.sh
at last reboot
to know the swap is working
goto terminal
type FREE
if swap is 0
is not working
xpraken said:
do this
1) download userinit.txt below to root of sdcard
2) boot into CWM recovery
3)mount /sdcard, /sd-ext (if you have ext partition) and /system
4) run: adb shell
5) move userinit.sh to /sd-ext ->
mv /sdcard/userinit.txt /sd-ext/userinit.sh
6) then,
chmod 755 /sd-ext/userinit.sh
7) reboot
this step will activate the swap without using app like swapper2
Click to expand...
Click to collapse
Sweet! Now I'm able to swap without swapper2. Thanks!
adb shell?where
hajiborojobo said:
adb shell?where
Click to expand...
Click to collapse
read this it may help
ADB
Manage swap over app
Try app resetSwap
"https://market.android.com/details?id=com.guille.resetSwap#?t=W251bGwsMSwxLDIxMiwiY29tLmd1aWxsZS5yZXNldFN3YXAiXQ.." for manage your swap (enable, disable, reset, info..)
it's cool , needn't restart
CM App Installer will pull the latest versions of the apps available that CyanogenMod exclusively develop, and give you the option to install them to your system either rooted or non-rooted. I cannot guarantee success with this, I don't develop the application, my job is simply to make it easier for you guys to get your favourite CyanogenMod apps on your own ROMs!
Use carefully! As ever, I do not take responsibilty for any damage done to your device as a result of this! The root features use the code specified in "code" in the options menu, or it's listed below. If you're paranoid, please give it a read
I have to emphasise, please try the non-root method first!. The root method is designed as a last ditch attempt to get it working, it does backup and restore your old versions but errors do happen, expect this as a possibility if you're rooted!
The list of apps available in the application are:
Apollo
Calculator
CM File Manager
Torch
Messaging
DSP Manager
Voice+
News and Weather Widget
Trebuchet Launcher
cLock Widget
Movie Studio
CM Wallpapers
Let me know if you have any more suggestions to add!
Code
This information is also available from within the application.
There are a number of commands that this application uses, it executes certain processes through the code to copy apps to the system directory.
These commands are ran as if they were ran inside the terminal emulator, and always consist of
process, remount to read-write, transfer/copy/rename, remount to read-only, close. (In this order).
I use a Process to get a SU Runtime instance
Code:
Process p = Runtime.getRuntime().exec("su");
And then I use a PrintStream to issue the commands listed below to it.
Remount the system partition as read-write
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Rename an app (use move command to move with a different extension - Creating backups)
Code:
mv /system/app/AppOfChoice.apk /system/app/AppOfChoice.bak
Copy an app from SD card to System directory
Code:
cat /sdcard/CMApps/AppOfChoice.apk > /system/app/AppOfChoice.apk
Remove an app from system partition
Code:
rm -r /system/app/AppOfChoice.apk
For permissions, I use chmod
Code:
chmod 644 /system/app/AppOfChoice.apk
Remount the system partition as read-only
Code:
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
And that is it. The process commands get pushed over the course of about two seconds, and should work. Again, I can't promise everything.
Credit also goes to the Reddit member /u/wchill, his code helped with the system code (shown in the Code section above)
Similarly, I do not take any responsibility if this app causes your phone to be bricked, corrupted, broken, or to encounter an unfortunate case of spontaneous combustion. Use at your own risk.
In the mean time, enjoy!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Source:
See this xda thread
So I've been out of a baseband for a few days now and I've come across this:
~ # ←[6ncat /proc/emmc
cat /proc/emmc
dev: size erasesize name
...(cut by me)
mmcblk0p35: 01000000 00000200 "boot"
mmcblk0p37: 73fffc00 00000200 "system"
...(cut)
~ # ←[6n/sbin/e2fsck -n -f /dev/block/mmcblk0p35
/sbin/e2fsck -n -f /dev/block/mmcblk0p35
e2fsck 1.41.11 (14-Mar-2010)
/sbin/e2fsck: Superblock invalid, trying backup blocks...
/sbin/e2fsck: Bad magic number in super-block while trying to open /dev/block/mm
cblk0p35
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n/sbin/e2fsck -n -f /dev/block/mmcblk0p37
/sbin/e2fsck -n -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p37: 2530/118800 files (1.3% non-contiguous), 434660/475135 bl
ocks
~ # ←[6n
So, the question is this: IS my boot partition an actual ext2 filesystem or am I trying to read it with the wrong "reader?" I don't want to jump the gun and format it into the wrong type if it's not corrupt, ya know?
Oh, I also get that same failure message checking my radio partition, too, so, need to know if THAT's ext2 as well...
ATDavis said:
So I've been out of a baseband for a few days now and I've come across this:
~ # ←[6ncat /proc/emmc
cat /proc/emmc
dev: size erasesize name
...(cut by me)
mmcblk0p35: 01000000 00000200 "boot"
mmcblk0p37: 73fffc00 00000200 "system"
...(cut)
~ # ←[6n/sbin/e2fsck -n -f /dev/block/mmcblk0p35
/sbin/e2fsck -n -f /dev/block/mmcblk0p35
e2fsck 1.41.11 (14-Mar-2010)
/sbin/e2fsck: Superblock invalid, trying backup blocks...
/sbin/e2fsck: Bad magic number in super-block while trying to open /dev/block/mm
cblk0p35
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n/sbin/e2fsck -n -f /dev/block/mmcblk0p37
/sbin/e2fsck -n -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p37: 2530/118800 files (1.3% non-contiguous), 434660/475135 bl
ocks
~ # ←[6n
So, the question is this: IS my boot partition an actual ext2 filesystem or am I trying to read it with the wrong "reader?" I don't want to jump the gun and format it into the wrong type if it's not corrupt, ya know?
Oh, I also get that same failure message checking my radio partition, too, so, need to know if THAT's ext2 as well...
Click to expand...
Click to collapse
looks like you have a Sprint phone (different partition table than GSM phones)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but to answer your question, NO, the only EXT4 partitions are /system /cache and /data, all the others are RAW partitions
if you're missing baseband, you probably flashed something for a GSM phone, so you need to reflash Sprint RUU... check the Sprint section on how to unbrick/fix this, there are several guides
That would have been a kernel... I'm still s-on, so I couldn't have destroyed too many of those fifty Partitions.
Thanks for the tip, I saw a guide on that somewhere over there. I guess I'll go dig it up since it's what may be my issue.
Hi.
I have problem with my m7.
Can't use RUU (error 120), can't mount phone storge for paste rom.zip.
I using adb fastboot and command "adb fastboot sideload rom.zip" and "error: close"
I have installed recovery TWRP and unlock bl, try used THIS tutorial but i have error
C:\Users\Mati>cd /d c:\mini-sdk
c:\mini-SDK>adb push mkfs.ext4 /tmp
adb server is out of date. killing...
* daemon started successfully *
2669 KB/s (3537143 bytes in 1.294s)
c:\mini-SDK>adb shell
~ # ←[6nchmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # ←[6n/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,
^extra_isize -m 0 /dev/block/mmcblk0p37
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p37
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p37 is mounted; will not make a filesystem here!
~ # ←[6nmount /data
mount /data
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
~ # ←[6nmkdir -p /data/media/0
mkdir -p /data/media/0
mkdir: can't create directory '/data/media/': Read-only file system
~ # ←[6nexit
Click to expand...
Click to collapse
Any ideas?
Sorry for my english..
Thanks!
Sony156 said:
Hi.
I have problem with my m7.
Can't use RUU (error 120), can't mount phone storge for paste rom.zip.
I using adb fastboot and command "adb fastboot sideload rom.zip" and "error: close"
I have installed recovery TWRP and unlock bl, try used THIS tutorial but i have error
Any ideas?
Sorry for my english..
Thanks!
Click to expand...
Click to collapse
the command is adb sideload rom.zip
and the phone must be in TWRP / Advanced / Sideload / Swipe to sideload
The link you posted has nothing to do with sideloading a Rom
Thanks for reply.
I know, i have running sideload in TWRP.
But adb don't see my m7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
C:\adb>adb sideload rom.zip
loading: 'rom.zip'
* failed to write data 'protocol fault (no status)' *
Click to expand...
Click to collapse
Sony156 said:
Thanks for reply.
I know, i have running sideload in TWRP.
But adb don't see my m7
Click to expand...
Click to collapse
update your adb and reinstall your pc drivers
I try different version adb and drivers for htc.
I too install fresh windows 7 on my imac and this same..
Using this: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2232799
Sony156 said:
I try different version adb and drivers for htc.
I too install fresh windows 7 on my imac and this same..
Using this: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2232799
Click to expand...
Click to collapse
Here use my ADB / Fastboot
does fastboot devices return the phones serial number in the bootloader ?
same with adb devices in TWRP ... you should see the phones serial number
i use this adb and my computer don't see htc in fastboot.
In recovery adb see phone
hboot 1.44
in bl is serial number, imei
Sony156 said:
i use this adb and my computer don't see htc in fastboot.
In recovery adb see phone
hboot 1.44
in bl is serial number, imei
Click to expand...
Click to collapse
adb doesn't work in the bootloader (fastboot does)
adb works in recovery and when the phone is booted up
in bootloader -> fastboot devices
Problem solved.
Phone had errors in the partition.
Thanks for all.
Today i got an issue for my N960F after flashing a custom ROM. I'm not sure till now what've gone wrong, but after rebooting my device i faced an issue that my SIM card can not register on network.
Cellular network signal is full, but can not make any calls and can not connect to data.
Tried to restore through TWRP with a nand backup, but always fails as EFS partition can not be mounted. Eventually I managed to restore my EFS partition after following the hereunder steps.
I'll just leave it here if anyone faced the same in the future.
Disclaimer: You are doing this at your own risk. I shall not be held liable for any losses or bricked devices ( They already are )
Pre requisites:
- ADB on your PC, latest SDK is preferred.
- Custom recovery ( with ADB enabled )
- Better to have a previous EFS backup
Steps:
- Reboot into recovery and enable ADB ( in TWRP, ADB is enabled by default )
- Attach your device to your PC. and open your terminal or command prompt as an admin.
- Type the following commands:
- Navigate to your ADB folder ( in my case it is C:/ADB )
cd C:/ADB
- Ensure that your phone is readable in ADB mode
c:\ADB>adb devices[ATTACH type="full"]5610649[/ATTACH]
c:\ADB>adb shell
Your terminal handle should change into root ~ #
~ # cd /dev/block
/dev/block # ls
you should get an output like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/dev/block # cd by-name
/dev/block/by-name # ls -la
you should see device partitions listed as this .. EFS partition is highlighted in yellow and is on sda3 as below
/dev/block/by-name # mke2fs /dev/block/sda3
and you should be prompted by a message to proceed or not. Press y then enter
Finally,
/dev/block/by-name # mount -w -t ext4 /dev/block/sda3
We successfully formatted and mounted EFS partition and now either to restore your old EFS backup or flash stock firmware through ODIN.
Resources: