Related
USE AT YOUR OWN RISK. You are responsible if you mess up your tablet.
NOTE: ONLY MESS WITH Partitions 10 & 11 (media and userdata)
This Wipe Data error E: format_volume: make_extf4fs failed on /dev/block/mmcblk1p2 is normal we all have it and it doesn't harm your device
Repartitioning your Nook Tablet requires (you must have):
* ADB drivers working on your PC
* CWM installed either to Internal (EMMC) or SDCARD
BEFORE START:
Watch the whole video and read the post first, once done you are now ready to start!
Click to expand...
Click to collapse
Big Thanks to @meghd00t
1. BACKUP INTERNAL SDCARD AND ROM
* To backup your Internal SDcard a.k.a: /media partiton, MyNook, /emmc:
Connect your Nook Tablet to your PC via USB, Turn on USB storage and copy all your files from MyNook to a folder in your PC.
* To backup your current ROM:
Boot into CWM, then go to backup & restore >> backup (external SDcard) so you can restore your /data later on.
Please NOTE that if you don't have a larger sdcard you will have to backup your current ROM to Internal SDcard, in which case you must use the method above to copy the clockworkmod folder to your PC.
2.0 PREPARATION:
IF YOU COME FROM THE OLD REPARTITION METHOD...
Code:
> cd path-to-adb-drivers
[B]> adb shell[/B]
# parted /dev/block/mmcblk0
(parted) toggle 10 lvm
# quit
2.1 REPARTITION:
Code:
# sgdisk -e /dev/block/platform/mmci-omap-hs.1/mmcblk0
This will write the secondary gpt label and remove the parted prompt found error fix?
Code:
# sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -d 11 -d 10
This will delete partition 10 & 11 media and userdata
Code:
# sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -n 0:0:+12G -n 0:0:0
# sgdisk /dev/block/platform/mmci-omap-hs.1/mmcblk0 -c 10:media -c 11:userdata
This will re-create both media (change +12G to whatever you need) and userdata will use the rest, then it'll set the name of the partitions
3. REBOOT YOUR DEVICE INTO CWM:
Code:
Ctrl+c to exit shell mode
> adb reboot recovery
This will exit from shell mode and reboot into recovery again. If adb reboot recovery doesn't work for you then do it manually.
4. FORMAT PARTITIONS:
Code:
> adb shell
# mkdosfs -F32 -n MyNook /dev/block/mmcblk0p10
# make_ext4fs -L userdata /dev/block/mmcblk0p11
Ctrl+c to exit shell mode
> adb reboot
> adb kill-server
This will start adb shell mode, format partition 10 to FAT32, format partition 11 to EXT4, exit shell mode, reboot your device to system and stop adb server from keep running.
5. RESTORE YOUR DATA
Reboot back into CWM recovery
CWM >> backup and restore >> Advanced restore >> /data
Click on this link to see the Old Method
~ Veronica
This ought to be stickied. I assume this will also work for the 8GB NT, although of course numbers need to change to reflect the fact that it's only 8GB.
Old Method
Hello, i decided to create this thread as the OP in this one hasn't been Updated with the solution for Repartiton your 16GB Nook Tablet and i see there is still people asking about how to do this and i've had to give the link of the "hidden" post over and over again.
Big Thanks to @tselling for put in risk his NT and post instructions for this, please go here and Thank him!
Repartitioning your Nook Tablet requires (you must have):
* ADB drivers working on your PC
* CWM installed either to Internal (EMMC) or SDCARD
* Tools: parted, tune2fs, e2fsck << Download this ONLY if you need them: parted is not found,etc
Boot into CWM, then go to backup & restore >> backup or backup to internal so you can restore /data after the repartitioning process since we are going to delete and recreate it.
IT DOESN'T MATTER WHAT ROM YOU HAVE INSTALLED, THE PROCESS IS MADE WHILE IN CWM SO MEDIA AND DATA PARTITIONS ARE NOT BEING USED
THIS PROCEDURE IS NOT REVERSIBLE UNLESS YOU RUN THE RIGHT COMMANDS TO REVERT THE PARTITIONS BACK TO DEFAULT SIZE
Here is a quick summary: Start parted on mmcblk0 from adb shell. Fix the errors. Delete partition 11 (userdata). Resize partition 10 (media) to make it larger... use the original start position and change the end position to make it the size you want. Recreate partition 11... use the end position from partition 10 as the new start position and use the original end position. Name partition 11 "userdata". Print the partition table along the way to make sure that its what you want. Exit parted. Use tune2fs and e2fsck to convert the ext2 partition back to an ext4 partition. Reboot back into CWM, restore your data partition and then reboot.
Click to expand...
Click to collapse
HOW DO I REVERT THIS PROCESS BACK TO STOCK???
"The bold text is the prompt and commands. The non-bold parts are screen output"
Remember that userdata is where most apps install. If you install alot of games you don't want to reduce it too far, 2.5GB - 2GB is probably ok for most people.
~ $ cd path-to-adb-drivers
ONLY IF YOU GET parted: not found: * You should had downloaded NT_repartition_files.zip uncompressed it and placed the files where adb is located already *~ $ adb push parted /system/bin * tune2fs and e2fsck may or may not be needed *~ $ adb push tune2fs /system/bin
~ $ adb push e2fsck /system/bin
Click to expand...
Click to collapse
~ $ adb shell
* daemon not running. starting it now on port xxxx *
* daemon started succesfully *
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? f
f
f
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 569312 blocks) or
continue with the current setting?
Fix/Ignore? f
f
f
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 2684MB 1074MB fat32 media
11 2684MB 15.6GB 12.9GB ext4 userdata
(parted) rm 11 * This will remove partition #11 *rm 11
rm 11
(parted) resize * You're entering to resize mode *resize
resize
Partition number? 10 * Partition #10 will be resized *10
10
Start? [1611MB]? * <---| enter *
End? [2684MB]? 11.6GB * Give a value between 11.6 and 13.6 that will leave you with>> 11.6GB: 4GB for /userdata | 13.6: 2GB for /userdata *11.6GB
11.6GB
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
(parted) mkpartfs primary ext2 * This will re-create partition #11 in the empty space and format it to ext2 *mkpartfs primary ext2
mkpartfs primary ext2
Start? 11.6GB * This value must concide with what you set in End? [2684MB]? 11.6GB before *11.6GB
11.6GB
End? 15.6GB * This value can't be changed. Must be 15.6GB *15.6GB
15.6GB
(parted)
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext2
(parted) name 11 userdata * This will name partition #11 "userdata" *name 11 userdata
name 11 userdata
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext2 userdata
(parted) quit
quit
quit
Information: You may need to update /etc/fstab.
~ # tune2fs -j /dev/block/mmcblk0p11 * From here the convertion process of partition #11 to ext4 has started *tune2fs -j /dev/block/mmcblk0p11
tune2fs 1.41.6 (30-May-2009)
Creating journal inode: done
This filesystem will be automatically checked every 30 mounts or
0 days, whichever comes first. Use tune2fs -c or -i to override.
~ # e2fsck -fDp /dev/block/mmcblk0p11
e2fsck -fDp /dev/block/mmcblk0p11
/dev/block/mmcblk0p11: 11/529056 files (0.0% non-contiguous), 49429/1056092 blks
~ # tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p11
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p11
tune2fs 1.41.6 (30-May-2009)
Please run e2fsck on the filesystem.
~ # e2fsck -fDp /dev/block/mmcblk0p11
e2fsck -fDp /dev/block/mmcblk0p11
/dev/block/mmcblk0p11: Group descriptor 0 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 1 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 2 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 3 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 4 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 5 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 6 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 7 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 8 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 9 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 10 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 11 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 12 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 13 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 14 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 15 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 16 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 17 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 18 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 19 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 20 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 21 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 22 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 23 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 24 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 25 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 26 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 27 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 28 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 29 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 30 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 31 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Group descriptor 32 checksum is invalid. FIXED.
/dev/block/mmcblk0p11: Adding dirhash hint to filesystem.
/dev/block/mmcblk0p11: 11/529056 files (0.0% non-contiguous), 49429/1056092 bl
ks
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext4 userdata
(parted) quit
quit
quit
Ctrl+c to exit shell mode
~ $ adb kill-server
Now reboot back into recovery (advanced option).
Go to backup & restore>> Advanced restore>> data to restore your data (apps), make sure you pick the correct folder of your latest backup, once done reboot system. ENJOY!
BONUS: Manage all your books including B&N downloads in calibre
Thanks to @roustabout
Also, once you've done this you can also shell in and
Code:
$ adb shell
# cd /data/media/B&N Downloads
# rm -r *
# cd ..
# rmdir B&N Downloads
# ln -s "/media/B&N Downloads" "B&N Downloads"
Ctrl+c to exit shell mode
$ adb kill-server
This points your B&N library to your /media folder for downloading, helpful if you want to manage all your books in Calibre.
~ Veronica
I am sorry for noob question, but is this a tutorial on how to expand that miserable 1gb user data space and steal more space from 12gb locked internal memory?
schtuka said:
I am sorry for noob question, but is this a tutorial on how to expand that miserable 1gb user data space and steal more space from 12gb locked internal memory?
Click to expand...
Click to collapse
lol yes Mr.
~ Veronica
too much text. someone make a youtube video. tks.
xdahgary said:
too much text. someone make a youtube video. tks.
Click to expand...
Click to collapse
strictlyrude27 said:
For ****'s sake. It's a bunch of commands you enter on the command line. OF COURSE THERE'S A LOT OF TEXT.
Click to expand...
Click to collapse
Actually the commands are few...
"The bold text is the prompt and commands. The non-bold parts are screen output".
I did it in less than 10 minutes and reading the tutorial twice.
~ Veronica
Like a charm. So happy. F bn
In the guys defense, not having ever used adb before, it took me about 30 minutes to do it last night. I had a hard time figuring out how to make the computer see the Nook while in CWR. Once I got that figured out, it went pretty fast.
Ok, I am trying to follow the instructions before actually doing it ... bear with me..
So I boot in CWM Recovery.
Do the backup.
Then what? Open cmd on my computer and go to shell?
I am familiar with ADB, but I am confused about at what point in the script you change the size of media 10 and data 11...... I see that 2GB of user data 11 will be enough for me. What size the media 10 should be? I remember from GParted that you have to divide equally the space....
Also, it says in the end of summary to reboot back to CWM. I thought we are in CWM doing the script the whole time. When did we reboot?
Thanks.
For noob like me, I actually wish to have some briefing about the commands. For example, in case I want to have less then 12GB of media data, 10GB may be, which number that I should change?
--------------
Edit: I guess
End? [2684MB]? 11.6GB
11.6GB
11.6GB
(parted) p
to
End? [2684MB]? 10GB
10GB
10GB
(parted) p
Correct me if I'm wrong. My NT is still on the way to my house
schtuka said:
Ok, I am trying to follow the instructions before actually doing it ... bear with me..
So I boot in CWM Recovery.
Do the backup.
Then what? Open cmd on my computer and go to shell?
I am familiar with ADB, but I am confused about at what point in the script you change the size of media 10 and data 11...... I see that 2GB of user data 11 will be enough for me. What size the media 10 should be? I remember from GParted that you have to divide equally the space....
Also, it says in the end of summary to reboot back to CWM. I thought we are in CWM doing the script the whole time. When did we reboot?
Thanks.
Click to expand...
Click to collapse
After the backup you plug your NT to your computer (you must have adb working already) open the cmd on windows and "cd" to the path of adb files then "adb shell" as explained in the tutorial.
You first resize/extend media partition (10) because that is the one mounts in your PC ("MyNOOK")
The part that the size is changed for /media is here:
(parted) resize
resize
resize
Partition number? 10
10
10
Start? [1611MB]?
End? [2684MB]? 11.6GB >> in this part 11.6GB is set to leave 4gb for userdata, i personally set it to 13.6GB so that leave 2GB for userdata as i don't install heavy apps and games like crazy.
11.6GB
11.6GB
The userdata partition is recreated after with what is left:
Start? 11.6GB >> as you can see its the same value that was set before in End? [2684MB]? 11.6GB of the /media partition
11.6GB
11.6GB
End? 15.6GB
15.6GB
15.6GB
As stated in the tutorial this is made while in CWM , you reboot back into it just to restore your data,nothing else. Let's put it this way when the windows updates install in your PC it ask you to reboot right? Sometimes reboots are required why? don't ask just do it is easy and it won't harm your device gee
~ Veronica
camapghe said:
For noob like me, I actually wish to have some briefing about the commands. For example, in case I want to have less then 12GB of media data, 10GB may be, which number that I should change?
--------------
Edit: I guess
End? [2684MB]? 11.6GB
11.6GB
11.6GB
(parted) p
to
End? [2684MB]? 10GB
10GB
10GB
(parted) p
Correct me if I'm wrong. My NT is still on the way to my house
Click to expand...
Click to collapse
hMM I THINK YOU'RE CONFUSED this is for users that want their /media partition bigger not /userdata (we are shortening userdata) why would you want this? simple because you can copy all your media: music, videos, movies, books, etc. to /media (which mounts to your PC as MyNOOK) so you don't use your sdcard to host them all.
Userdata is where apps install when you download them so think first of a size that works for you, and what partition you think you will give it more use.
~ Veronica
@Veronica: I'm confused indeed. I usually install tons of games + apps on my phone. That's why I don't want the partition where device stores those things internally small.
I guess I just follow exactly (and blindly) to the tut. Professional guys here must be right.
xdahgary said:
too much text. someone make a youtube video. tks.
Click to expand...
Click to collapse
FYI, if you ever unlock bootloader, install CWM, root and install custom ROM for a HTC Wildfire S from scratch, I swear you will just bang the phone up
Just out of curiosity, as I have not done this before, but can you string commands together with ampersands as you can in a Linux Bash terminal? If so, it could be one (albeit very long) command...
Thank you Veronica. I will try it at work right now. 6LV26081EP701653Y
So I did everything according to OP. Within CWM went to Advanced/Reboot to recovery/restore
Trying to restore my backup and I am getting:
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Error while formatting /data
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
....... help?....
I still have your ROM on sdcard. Should I try to install it instead of backup?
Tried to install your ROM from sdcard. Rebooted and now just sitting on white NOOK screen.
Am I FUBARed? I can't get to CWM.
schtuka said:
Thank you Veronica. I will try it at work right now. 6LV26081EP701653Y
So I did everything according to OP. Within CWM went to Advanced/Reboot to recovery/restore
Trying to restore my backup and I am getting:
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Error while formatting /data
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
....... help?....
I still have your ROM on sdcard. Should I try to install it instead of backup?
Tried to install your ROM from sdcard. Rebooted and now just sitting on white NOOK screen.
Am I FUBARed? I can't get to CWM.
Click to expand...
Click to collapse
Something you did wrong while using the commands can you tell me the values that you gave to /media and /userdata please.
Turn off your device, turn it on by long pressing power and "N" button for 5 seconds (let me know if you get the white screen with the box), then let go power and N buttons and it ishould boot into CWM after that box.
Other alternative if you cant boot internally to CWM is to prepare an sdcard and boot into CWM from there.
You need to get into CWM.
I used same numbers as in OP. I mean just copy and paste from OP.
Yeah. I got to CWM what should I do now?
Thanks
schtuka said:
I used same numbers as in OP. I mean just copy and paste from OP.
Yeah. I got to CWM what should I do now?
Thanks
Click to expand...
Click to collapse
wipe cache and advanced> dalvik cache.
Restore only data this way:
* Go to Backup&restore> Advanced restore> data
* wipe cache and dalvik again just in case (i always do that when restoring).
~ Veronica
Same error:
Restoring data...
E:format_volume: make_extf4fs failed on /dev/block/platform/mmci-omap-hs.1/by-name/userdata
Error while formatting /data
I think I made a mistake. Perhaps the usb drivers I used to format were not Nook Tablet specific. I have same computers at work and at home and once I got into ADB shell I thought it was good to go. Now I am looking at device manager and it is just says
-Android phone
Android composite ADB interface
Also looking through USBviewer I see too many Android devices. Including Nook Tablet USB Composite device connected and Nook Tablet ADB Interface not connected.
Hello all,
I have a question regarding the manner in which my galaxy player (YP-G70) is bricked. I have bricked it before and have been able to get out of it but on this one i cannot. I tried flashing multiple kernels and os's but none seem to work. The problem i am having is i cant get into cwm but when i can i get error messages saying that it cant mount and/or find files. If i try to format it says cant mount then a block error. I can get into download mode. Another weird thing is that when the samsung logo comes up it does not flash it stays a solid white then straight to cwm even though i flashed the stock factory image. Any help would be greatly appreciated.
Thanks.
Flash stock firmware through Odin, then wipe data and cache in recovery
Sent from my YP-G70 using xda app-developers app
Well i reflashed the stock firmware and this is what i get: youtube.com/watch?v=xBQi4tbbsI0&feature=youtu.be
Flash this in Odin
http://forum.xda-developers.com/showthread.php?t=1389873
Sent from my YP-G70 using xda app-developers app
For some reason i am still getting the same errors. Any other ideas?
Update: i was fiddling around with it while it was in recovery through adb and when i typed "mount sdcard" in adb shell i get the error:
~ # mount sdcard
mount sdcard
mount: can't read '/etc/fstab': No such file or directory
UPDATE2:
Sorry for all the updates
i just ran
cat /proc/partitions
major minor #blocks name
179 0 7757824 mmcblk0
179 1 1 mmcblk0p1
179 5 256 mmcblk0p5
179 8 15558144 mmcblk1
179 9 15557120 mmcblk1p1
this is not even close to how many there normally are. Any ideas?
UPDATE3:
This isnt looking good, ran parted on the partitions and this is what i got:
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 7757824 mmcblk0
179 1 1 mmcblk0p1
179 5 256 mmcblk0p5
179 8 15558144 mmcblk1
179 9 15557120 mmcblk1p1
~ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Error: Invalid partition table on /dev/block/mmcblk0 -- wrong signature feb7.
Ignore/Cancel? i
i
i
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.8kB 7944MB 7944MB extended
5 65.5kB 328kB 262kB logical
~ # parted /dev/block/mmcblk0p1 print
parted /dev/block/mmcblk0p1 print
Error: Can't have a partition outside the disk!
~ # parted /dev/block/mmcblk0p5 print
parted /dev/block/mmcblk0p5 print
Error: /dev/block/mmcblk0p5: unrecognised disk label
~ # parted /dev/block/mmcblk1 print
parted /dev/block/mmcblk1 print
Model: SD SU16G (sd/mmc)
Disk /dev/block/mmcblk1: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 15.9GB 15.9GB primary fat32 boot, lba
~ # parted /dev/block/mmcblk1p1 print
parted /dev/block/mmcblk1p1 print
Model: Unknown (unknown)
Disk /dev/block/mmcblk1p1: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
Not So Pro said:
Update: i was fiddling around with it while it was in recovery through adb and when i typed "mount sdcard" in adb shell i get the error:
~ # mount sdcard
mount sdcard
mount: can't read '/etc/fstab': No such file or directory
UPDATE2:
Sorry for all the updates
i just ran
cat /proc/partitions
major minor #blocks name
179 0 7757824 mmcblk0
179 1 1 mmcblk0p1
179 5 256 mmcblk0p5
179 8 15558144 mmcblk1
179 9 15557120 mmcblk1p1
this is not even close to how many there normally are. Any ideas?
UPDATE3:
This isnt looking good, ran parted on the partitions and this is what i got:
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 7757824 mmcblk0
179 1 1 mmcblk0p1
179 5 256 mmcblk0p5
179 8 15558144 mmcblk1
179 9 15557120 mmcblk1p1
~ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Error: Invalid partition table on /dev/block/mmcblk0 -- wrong signature feb7.
Ignore/Cancel? i
i
i
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.8kB 7944MB 7944MB extended
5 65.5kB 328kB 262kB logical
~ # parted /dev/block/mmcblk0p1 print
parted /dev/block/mmcblk0p1 print
Error: Can't have a partition outside the disk!
~ # parted /dev/block/mmcblk0p5 print
parted /dev/block/mmcblk0p5 print
Error: /dev/block/mmcblk0p5: unrecognised disk label
~ # parted /dev/block/mmcblk1 print
parted /dev/block/mmcblk1 print
Model: SD SU16G (sd/mmc)
Disk /dev/block/mmcblk1: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 15.9GB 15.9GB primary fat32 boot, lba
~ # parted /dev/block/mmcblk1p1 print
parted /dev/block/mmcblk1p1 print
Model: Unknown (unknown)
Disk /dev/block/mmcblk1p1: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------
Easy! you destroyed the memory partitioing thanks to a wrong kernel flashing.
Solution here, starting from post 39:
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
Good lick and welcome to the club
:
Thanks so much, i figured out what cause it and it was [Kernel][JB][YP-G70] Mercurius v5 the USA fixed version. Anyways thanks again!
Not So Pro said:
Thanks so much, i figured out what cause it and it was [Kernel][JB][YP-G70] Mercurius v5 the USA fixed version. Anyways thanks again!
Click to expand...
Click to collapse
PLEASE tell me what you did! I have the exact same problem, and it came after trying to restore an apparently corrupted backup of the same ROM ^
After I restored, it booted into cwm and was trying to do some update or installation... it was going too fast to read, but it said FAILED, and then would go on a boot loop doing the same thing.
I tried all the things I know could help in Odin. I was a able to boot into a rom one time, but the capacitive buttons didn't work.
As of yet, I am able to get into download mode, and then flash entropy's kernel, which then allows me to reboot into recovery, but only if it's rebooted automatically by odin. Once in recovery, I tried wiping everything and installing roms, but when I reboot nothing happens, and I can't get back into recovery, only download mode. >.<
Refer to post #7. If you cannot figure it out still then post what player you have and its capacity.
Thanks to @munjeni for tipping me off in the right direction and to @judas1977 + @Tesla-MADAL93 for having done this on the Ace 2 I come from ~~
Everything else in this post applies to Gingerbread, scroll down to the 5th message for a more clear guide centered around a 4.1.2 ROM.
This is my annotated diary about the last 2 hours, I'm sorry if the story feels a little bit Dadaist but I don't want to encourage people who don't feel ready to try it, so please read all of it first and if anything is unclear ask instead of doing!!
I installed Busybox 1.22.1 (iirc) and replaced the default shell with bash (install Bash-X from market, copy /S/xbin/bash over /S/bin/sh, remove app if you like to). All of this was done with Gingerbread .188 and CWM 5.5.0.4 from Supercharged kernel.
Original partition table, with names added:
[email protected]:~$ adb shell
Code:
sh-4.2# fdisk -u -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders, total 15515648 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 2047 1023+ 0 Empty #### TA ("Trim Area") IMEI, BL UNLOCK, SIMLOCK ETC -- DO NOT TOUCH
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 2304 3327 512 f0 Linux/PA-RISC boot #### SBL? Mem-init? Power management? PARAM?
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 2048 2303 128 f0 Linux/PA-RISC boot #### unknown, as above
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 3328 15269887 7633280 5 Extended #### GROUPS ALL FOLLOWING PARTITIONS FOR THEM TO FIT INTO THE 4-PARTS MBR SCHEME
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 4096 20479 8192 4a Unknown #### another of the 4 unclear partitions
/dev/block/mmcblk0p6 20480 26623 3072 83 Linux #### MODEMFS (Samsung's "EFS") RADIO CALIBRATION
/dev/block/mmcblk0p7 26624 36863 5120 70 Unknown #### no idea either
/dev/block/mmcblk0p8 36864 53247 8192 83 Linux #### IDD (apparently related to usage stats reporting)
/dev/block/mmcblk0p9 53248 86015 16384 48 Unknown #### KERNEL
/dev/block/mmcblk0p10 118784 2215935 1048576 83 Linux #### SYSTEM
/dev/block/mmcblk0p11 2727936 6922239 2097152 83 Linux #### DATAFS
/dev/block/mmcblk0p12 2215936 2727935 256000 83 Linux #### CACHEFS
/dev/block/mmcblk0p13 86016 118783 16384 48 Unknown #### FOTAKERNEL?
/dev/block/mmcblk0p14 6922240 15269887 4173824 c Win95 FAT32 (LBA) #### SDCARD/EMMC/UMS
Partition table entries are not in disk order
so let's rearrange this list for easier thinking & reading
Code:
/dev/block/mmcblk0p1 1 2047 1023+ TA
/dev/block/mmcblk0p3 2048 2303 128 ?
/dev/block/mmcblk0p2 2304 3327 512 ?
/dev/block/mmcblk0p5 4096 20479 8192 ?
/dev/block/mmcblk0p6 20480 26623 3072 MODEMFS
/dev/block/mmcblk0p7 26624 36863 5120 ?
/dev/block/mmcblk0p8 36864 53247 8192 IDD
/dev/block/mmcblk0p9 53248 86015 16384 KERNEL
/dev/block/mmcblk0p13 86016 118783 16384 FOTAKERNEL?
/dev/block/mmcblk0p10 118784 2215935 1048576 SYSTEM
/dev/block/mmcblk0p12 2215936 2727935 256000 CACHEFS
/dev/block/mmcblk0p11 2727936 6922239 2097152 DATAFS
/dev/block/mmcblk0p14 6922240 15269887 4173824 SDCARD
great, the important (for us) stuff is contiguous so we can delete those partitions and recreate them
(if fdisk works like parted we must do that in numerical order, so system>data>cache>ums)
we must delete and recreate partition 13 with the same sizes
OTOH fdisk lets us experiment without saving in real time (!!!) but let's do this in recovery mode
Let's research the sizes we want first -- I find Link2SD's graphical df the best way to do this (see photo 1)
so 540 MB for /system should be enough (I have 454M used, account a safety margin as I integrate updates + FS overhead + 1000 vs 1024 units)
4,14 MB used on /cache... 7,8 MB should be more than enough (same size I used on my Ace 2 which had about 5 MB used there)
this large size is for dalvik cache on ROMs that store it there (vm.dalvik.dexopt-data-only=0 and vm.dalvik.dexopt-cache-only=1 or something)
494 MB on /data, but I'd probably want to change apps and stuff... let's try with 1,25 GB
but if we remove /system we'll have to reflash the rom from a zip, which I'd need to make...
let's leave that partition alone for this first time
reboot now
Click to expand...
Click to collapse
Launching fdisk:
#### SONY
#### SONY (red green blue lightbar)
#### + button
#### CWM-based recovery v5.5.0.4
[email protected]:~$ adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
#### No shell in ramdisk? Very lame...
#### [Mounts and storage]
#### [Mount /system, unmount everything else]
[email protected]:~$ adb shell
sh-4.2# fdisk -u /dev/block/mmcblk0
Command (m for help):
What I did in fdisk:
u #### change units to sectors
d #### delete
14
d
13
d
12
d
11
c #### disable cylinder rounding
n #### new
l #### logical partition
First sector (3334-15269887, default 3334): 2215936
Sector 2215936 is already allocated #### Apparently this version of fdisk makes you waste a sector...
First sector (2215937-15269887, default 2215937): Using default value 2215937
Last sector or +size or +sizeM or +sizeK (2215937-15269887, default 15269887): +1600M
#### CACHEFS:
n
l
First sector (3334-15269887, default 3334): 5340938
Sector 5340938 is already allocated
First sector (5340939-15269887, default 5340939): Using default value 5340939
Last sector or +size or +sizeM or +sizeK (5340939-15269887, default 15269887): +8M
#### FOTAKERNEL
n
l
First sector (3334-15269887, default 3334): 86016
Sector 86016 is already allocated
First sector (86017-15269887, default 86017): Using default value 86017
Last sector or +size or +sizeM or +sizeK (86017-118783, default 118783): Using default value 118783
t
Partition number (1-14): 13
Hex code (type L to list codes): 48
Changed system type of partition 13 to 48 (Unknown)
#### USB STORAGE
n
l
First sector (3334-15269887, default 3334): 5356564
Sector 5356564 is already allocated
First sector (5356566-15269887, default 5356566): Using default value 5356566
Last sector or +size or +sizeM or +sizeK (5356566-15269887, default 15269887): Using default value 15269887
c
Partition number (1-14): 14
Hex code (type L to list codes): c
Changed system type of partition 14 to c (W95 FAT32 LBA)
w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
sh-4.2# reboot
Now enter CWM again and factory reset -- you'll get an error as it can't delete /sdcard/.android_secure as it's unformatted
(and for that matter this CWM can't format /sdcard either...)
No problem apart from skipped heartbeats, boot into Android and format it from the settings! (see photo 2)
Well, the last screenshot speaks for itself... but I'll repeat, don't try this at home! (Have a friend try it so you'll have someone to blame if it gets bricked)
Very interesting... It causes problems?
Inviato dal mio ST25i utilizzando Tapatalk
ale467 said:
Very interesting... It causes problems?
Click to expand...
Click to collapse
Unlike my example, you must have over 50M free on /cache (at least in Gingerbread) or cheat by bind-mounting it somewhere else... or give up on directly installing stuff from the market
I tried bind mounting /cache to /data/local/tmp/cache but Google Play is still broken, so I guess you'll want a 57M partition there...
Also, you can always return to stock layout by flashing a full ROM in green light download mode, then wiping /sdcard from settings
I'm going to update this for 4.1, it's even somewhat easier and more predictable
----------------
1: think of the rough partition sizes
Code:
system (350M)
data (1,5G)
cache (280M) ## keep in mind whether ROM uses this for dalvik-cache and at least in 2.x Google Play downloads there
sdcard (remaining space)
2: make sure you have some files ready
→ROM in recovery zip format
→Backup of everything you want
→Kernel with fdisk in ramdisk
→ADB known working in recovery and normal mode
→Fixed busybox (http://forum.xda-developers.com/attachment.php?attachmentid=1057725&d=1336884034)
3: enter recovery and dump partition table (adb shell, fdisk /dev/block/mmcblk0, p)
Unlike my previous experiment, I'll calculate sizes in cylinders -- harder but fdisk appears to work better that way
Code:
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
[...]
/dev/block/mmcblk0p10 1857 34624 1048576 83 Linux #SYSTEM
/dev/block/mmcblk0p11 42625 108160 2097152 83 Linux #DATAFS
/dev/block/mmcblk0p12 34625 42624 256000 83 Linux #CACHEFS
/dev/block/mmcblk0p13 1345 1856 16384 48 Unknown #FOTAKERNEL, move this on another line if it helps you think better but put it back there after calculations
/dev/block/mmcblk0p14 108161 238592 4173824 c Win95 FAT32 #UMS
so our work area starts at cylinder 1857 and ends at 238592!
4: calculate partition sizes (I'll only list start & end cylinders for clarity)
Code:
/dev/block/mmcblk0p10 1857 12538 << 1857 + (350000000÷32768)
/dev/block/mmcblk0p11 12538+1 >> 12539 58315 << 12539+(1500000000÷32768)
/dev/block/mmcblk0p12 58315+1 >> 58316 66861 << 58316 +(280000000÷32768)
/dev/block/mmcblk0p13 1345 1856
/dev/block/mmcblk0p14 66861+1 >> 66862 238592
5: remove partitions (d, 14, d, 13, ..., 10)
6: create partitions (n, l, 1857, 12538, repeat for next row)
7: retype partitions (t, 13, 48, t, 14, c)
8: save changes (w, reboot) - enter recovery again, you should get 5 "E: Can't {mount|open} /cache/[...]" lines
9: go to mounts and storage and run all 4 formats, sdcard will probably fail -- if it doesn't skip to step 13
10: install fixed busybox (adb push '/home/riki/Desktop/busybox' /cache/)
11: enter adb shell, make it executable (chmod +x /cache/busybox)
12: format media partition (/cache/busybox mkfs.vfat /dev/block/mmcblk0p14)
13: quit shell, mount /sdcard in CWM
14: adb push your ROM to /sdcard, install it and reboot!
This is so interesting, I've being doing this on a Samsung Galaxy SCL to fix it as its internal storage and /data partition were totally corrupted. I used parted instead of fdisk to repartition the external SD and edit then kernel's RAM disk to make it mount /data in one of the new partitions. Because of this that I've been doing lately, I'm thinking of using fdisk in my Xperia U too to have more available space in internal SD, that would be great, as I use dual boot feature.
I think I'll do this when I'm be fed up of Jelly Bean being the main ROM and KitKat just the secondary one.
By the way, I think it can be possible to leave enough free space before mmcblk0p14 to create my secondary ROM's partitions there (mmcblk0p15 for /system, mmcblk0p16 for /data and mmcblk0p17 for /cache) instead of creating system.ext4, data.ext4 and cache.ext4 inside my internal SD and mounting them in loop devices... What do you think? Could I brick my phone doing that? I've asked here too just in case.
The only thing I'd have to do is to format my mmcblk0p15 using mke2fs to set the same UUID as in mmcblk0p10 just if my secondary ROM doesn't boot (but I think this wouldn't be necessary):
Code:
mke2fs -T ext4 -O has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize -U [COLOR="Silver"][mmcblk0p10's UUID][/COLOR] -I 256 /dev/block/mmcblk0p15
You've explained this how-to so well, @Ryccardo! Thanks for this tutorial.
Many, many thanks to you, sir!
Thanks to you i was able to increase data partition on my P (similar partition scheme to U).
Other tutorials weren't so useful than yours and i was searching quite a lot. Thank you, live in wealth!
What many refer to as the "internal SD Card" is actually a partition of the internal memory module that is formatted FAT32 for cross-platform use, and dedicated to user storage (usb transfer, downloads, photos & videos, etc). Other partitions of the internal memory module use file system formats that are more specific to the linux-based operations of Android, kernels, bootloaders, etc.
The total size of the internal memory module of the SGH-i777 is 15.8 GB, and it is partitioned as shown in the table below.
Booted into Android: Settings > Storage, you should see reports for:
- "INTERNAL STORAGE" ~2GB
- "INTERNAL STORAGE" ~11.5GB
- IF you have an SD Card installed, you should see a third report named "SD CARD"
(Using the partition table as reference)
The first "internal storage", displays the status of the /data partition. This partition is populated by user-installed apps & data, as well as the user-specific data for /system apps.
The second "internal storage", displays the status of the user-storage partition.
Stock I777 Partition Table:
Code:
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 317MB 262MB ext4 CACHE
8 317MB 333MB 16.8MB MODEM
9 333MB 870MB 537MB ext4 FACTORYFS
10 870MB 3018MB 2147MB ext4 DATAFS
11 3018MB 15.2GB 12.2GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
The path to user-storage (both internal and external) may vary from Android when booted into recovery.
Booted into Android
internal & external user-storage are located at /storage/sdcard0 & /storage/sdcard1
Code:
mount
/dev/block/vold/179:9 /mnt/media_rw/sdcard1 vfat rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/259:3 /mnt/media_rw/sdcard0 vfat rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/block/vold/259:3 /mnt/secure/asec vfat rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Booted into CWMR
internal & external user-storage are located at /storage/sdcard0 & /storage/sdcard1
Code:
mount
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/block/vold/179:9 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096)
Booted into TWRP
internal & external user-storage are located at /emmc & /sdcard
These path names more appropriately represent the type of memory used. eMMC = embedded Multimedia Card
http://en.wikipedia.org/wiki/MultiMediaCard#eMMC
http://www.pcmag.com/encyclopedia/term/64404/emmc
The inconsistency with android's naming system can be an issue for apps that write OpenRecoveryScripts while booted into android, to be performed in recovery.
Code:
mount
/dev/block/mmcblk0p11 on /emmc type vfat (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)
/dev/block/mmcblk0p11 on /and-sec type vfat (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)
Code:
TWRP CWMR & AOSP Device Label FileSys size (MB)
mmcblk0 179:0
mmcblk0p /efs /efs 179:1 EFS ext4 20
mmcblk0p2 179:2 SBL1 1.2
mmcblk0p3 179:3 SBL2 1.2
mmcblk0p4 179:4 PARAM 8
mmcblk0p5 /boot /boot 179:5 KERNEL 8
mmcblk0p6 /recovery /recovery 179:6 RECOVERY 8
mmcblk0p7 /cache /cache 179:7 CACHE ext4 246
mmcblk0p8 259:0 MODEM 16
mmcblk0p9 /system /system 259:1 FACTORYFS ext4 504
mmcblk0p10 /data /data 259:2 DATAFS ext4 2016
mmcblk0p11 /emmc /storage/sdcard0 259:3 UMS FAT32 11634
mmcblk0p12 /preload /preload 259:4 HIDDEN ext4 504
mmcblk1 179:8
mmcblk1p1 /sdcard /storage/sdcard1 179:9 {whatevr} FAT32 {as purchased}
This information above was helpful for me recently, and although these devices are well aged, I hope that the info. can be useful for someone else.
We have @SteveMurphy and @razen_kain to thank for encouraging me to compile and post this stuff.
From an ADB shell, or within a terminal emulator, "mount" will give you a report of the currently mounted devices, and their mount points, permissions and more.
The original partition table posted is reported from gparted, within an ADB shell
adb devices
^if it returns your device serial, then ADB can see your device
adb shell
^starts a shell session on the device
parted /dev/block/mmcblk0
^starts a gparted session on disk "mmcblk0", the internal memory module
print
^displays the partition table
If I have any of this information incorrect, or if there's more information that should be included, please let me know.
There's an entire world of fstab, device mapping, and volume daemons that I am NOT savvy with, so I chose not to run down that rabbit hole.
This is fantastic stuff! I know you put a lot of work into it, so thanks for all the research you've accumulated and shared.
cyril279,
Very helpful info. Nice job on compiling and posting the info. Thanks for taking the time to do it and for continuing to help in this forum.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Great work man! We really appreciate you putting your time and effort into this. I am curious though what the 959g looks like. I know the recovery is on a different partition but that is the only difference Im aware of.
We would only know for sure if we analyze a 959 phone, but I'm going to guess that the partition table would be exactly the same. Notice that mmcblk0p6 is Recovery, and on the I777 that partition is not used.
so I wanted to try this but my android says:
Code:
C:\Users\Allan Romero>adb shell
[email protected]:/ $ parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
/system/bin/sh: parted: not found
127|[email protected]:/ $
is there a way to fix this, I wanted to compare the partition tables of my SGH-S959G to the SGH-I777, reason being was that when I go to download mode it says model S959G and I wanted to see if it can be changed to show the i777 under model.
micallan_17 said:
so I wanted to try this but my android says:
Code:
C:\Users\Allan Romero>adb shell
[email protected]:/ $ parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
/system/bin/sh: parted: not found
127|[email protected]:/ $
is there a way to fix this, I wanted to compare the partition tables of my SGH-S959G to the SGH-I777, reason being was that when I go to download mode it says model S959G and I wanted to see if it can be changed to show the i777 under model.
Click to expand...
Click to collapse
Did you boot into recovery before you ran adb shell? First boot into recovery, next type adb shell and you will get a ~ # prompt, then type parted /dev/block/mmcblk0 followed by print.
creepyncrawly said:
Did you boot into recovery before you ran adb shell? First boot into recovery, next type adb shell and you will get a ~ # prompt, then type parted /dev/block/mmcblk0 followed by print.
Click to expand...
Click to collapse
Oh I see, your tip fixed it, so I got this:
Code:
C:\Users\Allan Romero>adb shell
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 317MB 262MB ext4 CACHE
8 317MB 333MB 16.8MB MODEM
9 333MB 870MB 537MB ext4 FACTORYFS
10 870MB 3018MB 2147MB ext4 DATAFS
11 3018MB 15.2GB 12.2GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
(parted)
someone with more inside knowledge can let us know if there are any differences perhaps?
so based on comparison by looks:
code from cyril279:
Code:
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 317MB 262MB ext4 CACHE
8 317MB 333MB 16.8MB MODEM
9 333MB 870MB 537MB ext4 FACTORYFS
10 870MB 3018MB 2147MB ext4 DATAFS
11 3018MB 15.2GB 12.2GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
code from mines:
Code:
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 317MB 262MB ext4 CACHE
8 317MB 333MB 16.8MB MODEM
9 333MB 870MB 537MB ext4 FACTORYFS
10 870MB 3018MB 2147MB ext4 DATAFS
11 3018MB 15.2GB 12.2GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
is it safe to say that flashing the i777 bootloader (odin screen one) to the SGH-S959G would basically convert it to an i777?
micallan_17 said:
is it safe to say that flashing the i777 bootloader (odin screen one) to the SGH-S959G would basically convert it to an i777?
Click to expand...
Click to collapse
I suppose, but what I don't get is why it matters? The devices are practically identical, excepting the 959 having the separate partition which is a great thing and something the i777/i9100 lacks.
So what I'm asking is because our two phones are almost the same and can flash the same roms/kernels/recovery, what does it matter if it says '959' or 'i777'?
SteveMurphy said:
I suppose, but what I don't get is why it matters? The devices are practically identical, excepting the 959 having the separate partition which is a great thing and something the i777/i9100 lacks.
So what I'm asking is because our two phones are almost the same and can flash the same roms/kernels/recovery, what does it matter if it says '959' or 'i777'?
Click to expand...
Click to collapse
oh, I see I didn't know about the separate partition, I guess it doesn't really matter what it says on it, thanks for the reply
Cheers
Great info. Thanks fellas.
anyone fhave a new pit file for the s959g to increase system partition been searching for hours or would the one for the i777 work fine. I don't want to loose my separate recovery partition. I want to be able in install full slim gaaps
Created one don't need now.
Hi, I noticed there are about two similar threads but focusing on slightly different things so I am starting a new one.
I have ZLR F9006 (aka. ALPS F9006 or STAR F9006). It's a MT6582 cheap nobrand phone.
It has 4GB internal memory divided into several partitions. Since I have a 32 GB sdcard in it,
I find the existance of 1GB internal sd partition very annoying and I would like to merge that space
to /data instead, completely vanishing the internal_sd.
I have installed CWM Touch and booted into it. Here is df in recovery via adb:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 497520 48 497472 0% /dev
/[email protected] 127044 4208 122836 3% /cache
/dev/block/mmcblk1 31159328 6732768 24426560 22% /sdcard
/[email protected] 1029872 47888 981984 5% /emmc
/[email protected] 1828400 1133596 694804 62% /data
/[email protected] 706392 488788 217604 69% /system
/sbin # cd /emc
(usrdata=/data, emmc=internal storage)
I installed parted but I get this error:
Code:
~ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Error: Can't have a partition outside the disk!
I know this is the internal memory because mmcblk1 is the SD card (and opening it in parted works).
I have these block devices:
Code:
/dev/block # ls
ls
loop0 loop4 mmcblk0 mmcblk0p2 mmcblk0p6 platform
loop1 loop5 mmcblk0boot0 mmcblk0p3 mmcblk0p7 zram0
loop2 loop6 mmcblk0boot1 mmcblk0p4 mmcblk0p8
loop3 loop7 mmcblk0p1 mmcblk0p5 mmcblk1
As you can see, there are 8 partitions on the internal block device, with the p7 being the /data partition:
Code:
/dev/block # parted /dev/block/mmcblk0p7 print
parted /dev/block/mmcblk0p7 print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p7: 1900MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 1900MB 1900MB ext4
And the p8 being the internal SD i want to get rid of:
Code:
/dev/block # parted /dev/block/mmcblk0p8 print all
parted /dev/block/mmcblk0p8 print all
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/block/mmcblk0p8: 1055MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
(Strangely enough, you can't see the filesystem on those, but the msdos partition table and size fits.)
I was hoping I would simply delete that p8 and then expand the p7 to the remaining size, all that
should be perfectly doable with parted without even losing data (apart from few empty dirs on the p8).
But I highly doubt I can do it by directly calling parted on that specific partitions, I think that I need to make
it work calling it for the whole /dev/block/mmcblk0 (could someone confirm this?).
If yes, how can I make that happen?
You're likely to brick your phone if you do it that way. Take a look here on how to repartition your internal memory. It's for MT6577, but I think it could be of relevance to your situation.
Thanks, this is very relevant. This is how my block table looks like (attached). I was right about the partitions being the last (but i am not sure about the bmtpool at the end).