Help! Super soft-bricked!! - Samsung Galaxy Player 4.0, 5.0
SOLVED!
See post #3
So.. I was playing around with building a kernel for my SGP 5.0 US. Everything was going ok and I built a few successful ones until I stupidly decided to play around with voodoo lagfix, which in hindsight was a terrible idea.
My player right now is floating between no download mode and being able to access CWM. I've tried flashing everything I can possibly find for it - recovery images, PIT files (with repartitioning), new ROMs, absolutely nothing will work. I've tried flashing files individually, on multiple computers, multiple USB ports, etc. Most of the time flashing something to it just puts it back in no download mode and I have to recover it with the unbrickable app (which usually takes half a dozen or so tries to bring it back).
/system, /data, /datadata, /cache and /emc will not mount or format. It almost seems like they're permastuck in EXT4 from when I attempted to flash a lagfix kernel on there. In ADB I can see the contents of what's on the player, but I can't format through the shell or remount in RW.
Here's my PIT file pulled from Heimdall -
Code:
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 14
Unknown 1: 15718400
Unknown 2: 1
Unknown 3: 0
Unknown 4: 0
Unknown 5: 7703
Unknown 6: 237
Unknown 7: 62704
Unknown 8: 18
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: IBL+PBL
Filename: boot.bin
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: YPG70_8G-0304.pit
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL
Filename: Sbl.bin
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 5
Unknown 2: 6226025
Unknown 3: 7143533
Partition Name: SBL2
Filename: Sbl.bin
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 40
Unknown 2: 39021280
Unknown 3: 7143533
Partition Name: EFS
Filename: efs.rfs
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 36662408
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 30
Unknown 2: 6684793
Unknown 3: 3014771
Partition Name: RECOVERY
Filename: zImage
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 1160
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.rfs
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 536
Unknown 2: 6684780
Unknown 3: 115
Partition Name: DBDATAFS
Filename: dbdata.rfs
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 256
Unknown 2: 115
Unknown 3: 115
Partition Name: CACHE
Filename: cache.rfs
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 7696
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: datafs.rfs
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 256
Partition Block Count: 20516
Unknown 2: 0
Unknown 3: 0
Partition Name: USERFS
Filename: userfs_8G.rfs
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: inand_8G.bin
Ending session...
No matter WHAT I do, they all stay EXT4.
Going in through ADB shows /dev/block/mmcblk0p1-mmcblk0p11, but not the rest.
Here's the recovery.log too -
Code:
Starting recovery on Sat Jan 1 05:49:42 2005
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /efs rfs /dev/block/mmcblk0p10 (null)
2 /system ext4 /dev/block/mmcblk0p13 (null)
3 /datadata ext4 /dev/block/mmcblk0p14 (null)
4 /cache ext4 /dev/block/mmcblk0p15 (null)
5 /data ext4 /dev/block/mmcblk0p16 (null)
6 /emmc vfat /dev/block/mmcblk0p17 (null)
7 /sdcard vfat /dev/block/mmcblk1p1 (null)
8 /boot emmc /dev/block/mmcblk0p11 (null)
9 /recovery emmc /dev/block/mmcblk0p12 (null)
touch: /etc/mtab: No such file or directory
W:Unable to create /etc/fstab!
I:Processing arguments.
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=c0890810938bfbe
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdkc110
ro.revision=0
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
ro.build.product=herring
ro.product.device=herring
ro.radio.noril=yes
ro.bt.bdaddr_path=/efs/bluetooth/bt_addr
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
ro.telephony.call_ring.multiple=0
ro.nfc.port=I2C
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
W:Can't unlink /cache/recovery/command
-- Installing: /sdcard/DD_01232012.zip
Finding update package...
I:Update location: /sdcard/DD_01232012.zip
Opening update package...
Installing update...
Entropy's Daily Driver
01/23/2012 Release
Flashing Kernel
Thank designgears of Cognition X2 for the CWM kernel flashing example for eMMC devicesscript result was [No more redbend_ua makes Entropy happy.]
No more redbend_ua makes Entropy happy.
Install from sdcard complete.
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
W:Can't unlink /cache/recovery/command
-- Wiping cache...
Formatting /cache...
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Cache wipe complete.
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
W:Can't unlink /cache/recovery/command
Checking MD5 sums...
boot.img: OK
cache.ext4.tar: OK
data.rfs.tar: OK
datadata.rfs.tar: OK
recovery.img: OK
system.rfs.tar: OK
.android_secure.vfat.tar: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2012-01-23.08.40.56//system.rfs.tar
Restoring system...
10+0 records in
10+0 records out
40960 bytes (40.0KB) copied, 0.000273 seconds, 143.1MB/s
Volume size(40960) is too small to format the volume to FAT32
Retry to format after enlarge the volume size to larger than reserved area(32) * sector size(4096)
create_pbr[456]: failed to calc_fat_sectors!
make_tables[743]: Cannot create PBR!
fat_format[964]: Failed to make table!
Fail to format
failure while running fat.format
E:format_volume: format_rfs_device failed on /dev/block/mmcblk0p13
Error while formatting /system!
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
W:Can't unlink /cache/recovery/command
I was wondering initially if the flash could be screwed up or locked, but through flashing different boot images I can change the recovery between CWM and stock recovery.
I'm really at a loss here, I've spent probably 20+ hours in the past two days trying to revive this thing and I'm out of ideas. I've gotten absolutely nowhere. Can anyone help please??
I'm pretty proficient with linux and have Virtualbox w/ Windows XP running on Debian.. I just really need a hand
I've never run in to this before and the other guys might have a better idea but it sounds like you need to repartition. There is a check box in Odin to do it. I don't think that you need the pit file unless that is hosed too... It looks OK from your Heimdall output. I would try going through AdamOutler's unbrickable mod post and when you get to the Odin flash check the repartition box in odin...
Or have you tryed that?
Ok, I got in this situation few times. The problem comes when you compile a kernel with wrong vermagic and init tries to load samsung propietary modules. Sometimes when it happens, the partition table of your internnal storage gets corrupt. Repartition with Odin using a PIT file won't help.
You need to manually repartition your internal storage. To do this:
1. Make sure you can enter to a shell with adb shell command. If not, try Entropy512 kernel. The device will stay with Samsung logo, but you should be able to get in a console.
2. Ask someone with a working device to give you a working partition table. To do this, you need to do:
Code:
fdisk /dev/block/mmcblk0
Then, press u, enter, press p, enter. This should give you a output like this:
Code:
# partition table of /dev/mmcblk0
unit: sectors
/dev/mmcblk0p1 : start= 64, size= 15515584, Id= 5
/dev/mmcblk0p2 : start= 0, size= 0, Id= 0
/dev/mmcblk0p3 : start= 0, size= 0, Id= 0
/dev/mmcblk0p4 : start= 0, size= 0, Id= 0
/dev/mmcblk0p5 : start= 128, size= 512, Id=83
/dev/mmcblk0p6 : start= 704, size= 512, Id=83
/dev/mmcblk0p7 : start= 1280, size= 2560, Id=83
/dev/mmcblk0p8 : start= 3904, size= 2560, Id=83
/dev/mmcblk0p9 : start= 6528, size= 10240, Id=83
/dev/mmcblk0p10: start= 16832, size= 20480, Id=83
/dev/mmcblk0p11: start= 37376, size= 15360, Id=83
/dev/mmcblk0p12: start= 52800, size= 15360, Id=83
/dev/mmcblk0p13: start= 68224, size= 593920, Id=83
/dev/mmcblk0p14: start= 662208, size= 274432, Id=83
/dev/mmcblk0p15: start= 936704, size= 131072, Id=83
/dev/mmcblk0p16: start= 1067840, size= 3940352, Id=83
/dev/mmcblk0p17: start= 5008256, size= 10504192, Id=83
This output is from my YP-G70 international 8G. Don't know if it's exactly the same for US version.
3. Then:
Code:
adb shell
fdisk /dev/block/mmcblk0
Press u, enter, press p, enter. This should print your faulty partition table. My guess is the last partition will have incorrect size. Delete that one with d. Then, create the rest of partitions with n. Make sure you enter the right starting sector, and the right size (ex. for mmcblk0p12, enter "52800" and "+15360").
Finally, write the partition table with w.
Now, enter in download mode and flash a kernel that you know is working (you can also dump it to the right partition (dd if=<unpacked zImage> of=/dev/block/mmcblk0p11). If the device doesn't reboot, you should reflash a stock kernel and do a factory reset in stock android recovery.
rumirand said:
Ok, I got in this situation few times. The problem comes when you compile a kernel with wrong vermagic and init tries to load samsung propietary modules. Sometimes when it happens, the partition table of your internnal storage gets corrupt. Repartition with Odin using a PIT file won't help.
You need to manually repartition your internal storage. To do this:
1. Make sure you can enter to a shell with adb shell command. If not, try Entropy512 kernel. The device will stay with Samsung logo, but you should be able to get in a console.
2. Ask someone with a working device to give you a working partition table. To do this, you need to do:
Code:
fdisk /dev/block/mmcblk0
Then, press u, enter, press p, enter. This should give you a output like this:
Code:
# partition table of /dev/mmcblk0
unit: sectors
/dev/mmcblk0p1 : start= 64, size= 15515584, Id= 5
/dev/mmcblk0p2 : start= 0, size= 0, Id= 0
/dev/mmcblk0p3 : start= 0, size= 0, Id= 0
/dev/mmcblk0p4 : start= 0, size= 0, Id= 0
/dev/mmcblk0p5 : start= 128, size= 512, Id=83
/dev/mmcblk0p6 : start= 704, size= 512, Id=83
/dev/mmcblk0p7 : start= 1280, size= 2560, Id=83
/dev/mmcblk0p8 : start= 3904, size= 2560, Id=83
/dev/mmcblk0p9 : start= 6528, size= 10240, Id=83
/dev/mmcblk0p10: start= 16832, size= 20480, Id=83
/dev/mmcblk0p11: start= 37376, size= 15360, Id=83
/dev/mmcblk0p12: start= 52800, size= 15360, Id=83
/dev/mmcblk0p13: start= 68224, size= 593920, Id=83
/dev/mmcblk0p14: start= 662208, size= 274432, Id=83
/dev/mmcblk0p15: start= 936704, size= 131072, Id=83
/dev/mmcblk0p16: start= 1067840, size= 3940352, Id=83
/dev/mmcblk0p17: start= 5008256, size= 10504192, Id=83
This output is from my YP-G70 international 8G. Don't know if it's exactly the same for US version.
3. Then:
Code:
adb shell
fdisk /dev/block/mmcblk0
Press u, enter, press p, enter. This should print your faulty partition table. My guess is the last partition will have incorrect size. Delete that one with d. Then, create the rest of partitions with n. Make sure you enter the right starting sector, and the right size (ex. for mmcblk0p12, enter "52800" and "+15360").
Finally, write the partition table with w.
Now, enter in download mode and flash a kernel that you know is working (you can also dump it to the right partition (dd if=<unpacked zImage> of=/dev/block/mmcblk0p11). If the device doesn't reboot, you should reflash a stock kernel and do a factory reset in stock android recovery.
Click to expand...
Click to collapse
Thanks, that might be really helpful!! I'll give it a go. Meticulus, I've already tried alllll that like 20 times already.
I can still ADB in with no problem whatsoever, manual partitioning seems like the only thing I haven't tried so far. I also have a feeling that the partition tables for US/INTL are different.. I really borked it eh?
Anyone with a US 5.0 wanna post the output of
fdisk /dev/block/mmcblk0 please?
*Warning you are doing this on your own behalf I am not responsible if something goes wrong with your device or anything when you are going through this process*
THIS PROCESS WORKED FOR ME
You are going to have to do a factory restore * I kept all of my device data and sd data i just had to re-install the apks*
hmm
have you tried doing the unbrickable mod on a unbuntu i was on a hard brick state in which the device hadn't turned on at all but i got it to work.
Maybe this can help
http://forum.xda-developers.com/showthread.php?t=1386669
I followed the first steps before creating the virtual machine
make sure you have unbuntu on windows if you have windows of course, then try installing java for linux on unbutu so you can open up the unbrickable mod, make sure you have device plugged in and it should say spc110 detected or at least something like that then start the unbricking you should see a downloading sign. Note: if you don't see a downloading sign on the galaxy player and computer you should unplug the galaxy player and restart the unbrickable mod don't plug the galaxy player in immediately, plug the galaxy player in when you are ready and as soon as you see spc110 detected quickly click unbrick button and it should say downloading *this must be done quickly in order to get a downloading reading* wait 5 min and then shut down unbuntu and open up windows i did this and the galaxy player stayed in download mode. unzip the bootloaders attachment from the link above. Make sure you have kies installed on windows with all of the proper samsung drivers. Next open up odin and click pit select galaxyplayerpart.pit from the bootloaders folder, click bootloader afterwards and select galaxyplayerdownloadmodeonly.tar from the bootloaders folder and click start on odin. wait until it is complete it should say something like pass. Re-open odin and click bootloader open up galaxyplayerbootloaders.tar from the bootloaders folder and click start on odin. your device should restart and go into recovery mode now this is important you have to do wipe data and wipe/clear cache options then do factory reset and select the reboot device option and there you go. your galaxy should reboot and you will have to go through set up again and you will have to reinstall your apks your data should still be there though.
Thanks AdamOutler and all of the members on this page http://forum.xda-developers.com/showthread.php?t=1386669
dgk164cpehs1 said:
*Warning you are doing this on your own behalf I am not responsible if something goes wrong with your device or anything when you are going through this process*
THIS PROCESS WORKED FOR ME
You are going to have to do a factory restore * I kept all of my device data and sd data i just had to re-install the apks*
hmm
have you tried doing the unbrickable mod on a unbuntu i was on a hard brick state in which the device hadn't turned on at all but i got it to work.
Maybe this can help
http://forum.xda-developers.com/showthread.php?t=1386669
I followed the first steps before creating the virtual machine
make sure you have unbuntu on windows if you have windows of course, then try installing java for linux on unbutu so you can open up the unbrickable mod, make sure you have device plugged in and it should say spc110 detected or at least something like that then start the unbricking you should see a downloading sign. Note: if you don't see a downloading sign on the galaxy player and computer you should unplug the galaxy player and restart the unbrickable mod don't plug the galaxy player in immediately, plug the galaxy player in when you are ready and as soon as you see spc110 detected quickly click unbrick button and it should say downloading *this must be done quickly in order to get a downloading reading* wait 5 min and then shut down unbuntu and open up windows i did this and the galaxy player stayed in download mode. unzip the bootloaders attachment from the link above. Make sure you have kies installed on windows with all of the proper samsung drivers. Next open up odin and click pit select galaxyplayerpart.pit from the bootloaders folder, click bootloader afterwards and select galaxyplayerdownloadmodeonly.tar from the bootloaders folder and click start on odin. wait until it is complete it should say something like pass. Re-open odin and click bootloader open up galaxyplayerbootloaders.tar from the bootloaders folder and click start on odin. your device should restart and go into recovery mode now this is important you have to do wipe data and wipe/clear cache options then do factory reset and select the reboot device option and there you go. your galaxy should reboot and you will have to go through set up again and you will have to reinstall your apks your data should still be there though.
Thanks AdamOutler and all of the members on this page http://forum.xda-developers.com/showthread.php?t=1386669
Click to expand...
Click to collapse
Thanks, but I tried all that already to no avail.. flashing the new PIT file makes no difference. I will say though, I did find myself using the Unbrickable Mod and it's turned out to be a lifesaver!
What version of the SGP do you have, btw?
There is another method, but use it only if the method above doesn't work:
Get a full dd dump of another US device, that was the method I used to get back to life my player: take a look here.
AWESOME!!
Just manually repartitioned it and I'm back in business. Thanks so much! Turns out the international partition table is pretty close to the US one. The last partition was indeed really screwed up. Fixed that, flashed a new bootloader and ROM and it finally let me restore my nandroid backup!
Just share the partition table and mark it as solved, please.
exodus454 said:
Thanks, but I tried all that already to no avail.. flashing the new PIT file makes no difference. I will say though, I did find myself using the Unbrickable Mod and it's turned out to be a lifesaver!
What version of the SGP do you have, btw?
Click to expand...
Click to collapse
yea i have galaxy player 5.0 us version
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 64 15515647 7757792 5 Extended
/dev/block/mmcblk0p5 128 639 256 83 Linux
/dev/block/mmcblk0p6 704 1215 256 83 Linux
/dev/block/mmcblk0p7 1280 3839 1280 83 Linux
/dev/block/mmcblk0p8 3904 6463 1280 83 Linux
/dev/block/mmcblk0p9 6528 16767 5120 83 Linux
/dev/block/mmcblk0p10 16832 37311 10240 83 Linux
/dev/block/mmcblk0p11 37376 52735 7680 83 Linux
/dev/block/mmcblk0p12 52800 68160 7680+ 83 Linux
/dev/block/mmcblk0p13 68224 662144 296960+ 83 Linux
/dev/block/mmcblk0p14 662208 936640 137216+ 83 Linux
/dev/block/mmcblk0p15 936704 1067776 65536+ 83 Linux
/dev/block/mmcblk0p16 1067840 5008192 1970176+ 83 Linux
/dev/block/mmcblk0p17 5008256 15512448 5252096+ 83 Linux
There's my partition table.. no idea if it's spot-on for what the stock table was but it works without issue. I didn't recreate the missing zeroed partitions (2-4) either.
1) Heimdall's dump-pit will report partitions as EXT4 even when they are RFS
2) Heimdall tends not to like flashing US 5.0s - gotta use Odin
Out put from mine
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 969728 7757792 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p5 9 40 256 83 Linux
/dev/block/mmcblk0p6 45 76 256 83 Linux
/dev/block/mmcblk0p7 81 240 1280 83 Linux
/dev/block/mmcblk0p8 245 404 1280 83 Linux
/dev/block/mmcblk0p9 409 1048 5120 83 Linux
/dev/block/mmcblk0p10 1053 2332 10240 83 Linux
/dev/block/mmcblk0p11 2337 3296 7680 83 Linux
/dev/block/mmcblk0p12 3301 4260 7680 83 Linux
/dev/block/mmcblk0p13 4265 41384 296960 83 Linux
/dev/block/mmcblk0p14 41389 58540 137216 83 Linux
/dev/block/mmcblk0p15 58545 66736 65536 83 Linux
/dev/block/mmcblk0p16 66741 313012 1970176 83 Linux
/dev/block/mmcblk0p17 313017 969528 5252096 83 Linux
Removed started my own topic!
Bumping this to ask if anyone has the partition table output for the 4.0 USA 8G. I am in a similar bind and I cant seem to find the 4.0's table anywhere...
Bump, need this too.
zaphod666 said:
Bumping this to ask if anyone has the partition table output for the 4.0 USA 8G. I am in a similar bind and I cant seem to find the 4.0's table anywhere...
Click to expand...
Click to collapse
Hi. i have softbricked device too but mine is YP-G1 4.0 INTL and i cant find partition table for mine to repair my player. i have done all with odin pit file and full restore tar.md5 and i have no luck. i can acces download mode and stock recovery. can some help me with this?
t0m4s_g1l said:
Hi. i have softbricked device too but mine is YP-G1 4.0 INTL and i cant find partition table for mine to repair my player. i have done all with odin pit file and full restore tar.md5 and i have no luck. i can acces download mode and stock recovery. can some help me with this?
Click to expand...
Click to collapse
try looking here: http://forum.xda-developers.com/showthread.php?t=1531850
goldflame09 said:
try looking here: http://forum.xda-developers.com/showthread.php?t=1531850
Click to expand...
Click to collapse
Thanks but i did all that and doesnt work.... as i said when it boot up all apps fail and nothing work sorry my english u can look my post and see what is happening. i think i need to do repair partitions with adb like man in this post.
http://forum.xda-developers.com/showthread.php?p=42010368#post42010368
Thanks for help
exodus454 said:
Thanks, that might be really helpful!! I'll give it a go. Meticulus, I've already tried alllll that like 20 times already.
I can still ADB in with no problem whatsoever, manual partitioning seems like the only thing I haven't tried so far. I also have a feeling that the partition tables for US/INTL are different.. I really borked it eh?
Anyone with a US 5.0 wanna post the output of
fdisk /dev/block/mmcblk0 please?
Click to expand...
Click to collapse
Could you shed a little more light on this...I have done so much already so this looks like rocket science to me!
Related
[Q] Partition help w/possible need Froyo pit/bootloader for Int'l 5.0
Alrighty, I took the NOOB video to heart and have spent a pantsload of time trying to unbrick my Galaxy S WiFi 5.0 that I got from woot.com that I mucked up with some bad files/bad settings on Odin, I don't really remember what I did anymore. I love the video, very well done. My sgp has the physical home button but unlike all the other releases, it started out with Froyo. The box it came in says it's a YP-G70CW/TTT though there is some dispute where these were destined and I've seen conflicting info on the TTT. Probably doesn't matter. The fact is it started out with Froyo and I think everybody else started with Gingerbread. Using various Adam Outler threads, I was able to get it out of hard brick using Unbrickable, then I got the Samsung logo back with the bootloader, and back into recovery/normal download mode using the G70-GalaxyPlayer5.0-8gig-Inter_model_2.3.5.pit But then I'm stuck at a bunch of mount errors. Here's a screenshot I took with Droid Explorer: i42.tinypic.com/34g0ehc.jpg (sorry, can't post full links) Applying the ROM from Eryigit-GB-2.3.6 G70ZCKPA release 3 gets me a nice little CWM recovery, the error list is shorter unless I look at the log. If I plug in a USB when the device is off, I get the "working" star with no animation and shortly after the empty battery icon appears and the player reboots, repeating the same routine. Unplugged it boots into CWM recovery. i39.tinypic.com/i2lnnl.jpg Here is a somewhat cleaned up formatting of the log I got off the player. Code: Starting recovery on Wed Mar 7 13:32:21 2012 framebuffer: fd 4 (480 x 800) CWM-based Recovery v5.0.2.7 recovery filesystem table ========================= 0 /tmp ramdisk (null) (null) 1 /efs rfs /dev/block/mmcblk0p10 (null) 2 /system ext4 /dev/block/mmcblk0p13 (null) 3 /cache ext4 /dev/block/mmcblk0p15 (null) 4 /data ext4 /dev/block/mmcblk0p16 (null) 5 /datadata ext4 /dev/block/mmcblk0p14 (null) 6 /emmc vfat /dev/block/mmcblk0p17 (null) 7 /sdcard vfat /dev/block/mmcblk1p1 (null) 8 /boot emmc /dev/block/mmcblk0p11 (null) 9 /recovery emmc /dev/block/mmcblk0p12 (null) W:Unable to get recovery.fstab info for /sd-ext during fstab generation! I:Completed outputting fstab. I:Processing arguments. W:failed to mount /dev/block/mmcblk0p15 (No such file or directory) mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory W:failed to mount /dev/block/mmcblk0p15 (No such file or directory) E:Can't mount /cache/recovery/command I:Checking arguments. I:device_recovery_start() Command: "/sbin/recovery" ro.secure=0 ro.allow.mock.location=0 ro.debuggable=1 persist.service.adb.enable=1 ro.factorytest=0 ro.serialno=c0890801ac378bd ro.bootmode=unknown ro.baseband=unknown ro.carrier=unknown ro.bootloader=unknown ro.hardware=smdkc110 ro.revision=0 init.svc.recovery=running init.svc.adbd=running ro.build.product=herring ro.product.device=herring ro.radio.noril=yes ro.bt.bdaddr_path=/efs/bluetooth/bt_addr status.battery.state=Slow status.battery.level=5 status.battery.level_raw=50 status.battery.level_scale=9 ro.telephony.call_ring.multiple=0 ro.nfc.port=I2C I:Checking for extendedcommand... I:Skipping execution of extendedcommand, file not found... W:failed to mount /dev/block/mmcblk0p15 (No such file or directory) mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory W:failed to mount /dev/block/mmcblk0p15 (No such file or directory) E:Can't mount /cache/recovery/log E:Can't open /cache/recovery/log W:failed to mount /dev/block/mmcblk0p15 (No such file or directory) mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory W:failed to mount /dev/block/mmcblk0p15 (No such file or directory) E:Can't mount /cache/recovery/last_log E:Can't open /cache/recovery/last_log W:failed to mount /dev/block/mmcblk0p15 (No such file or directory) mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory W:failed to mount /dev/block/mmcblk0p15 (No such file or directory) W:Can't unlink /cache/recovery/command And this is what things looked like with Adroid Commander: i41.tinypic.com/14aga2r.jpg I'm not sure if the lack of device info nor space used is due to the program not having access or just a better look at what the log is saying that there is squat there. I'm not sure, but it seems like I am not able to browse into those problematic folders. At one point in one program (I think it was Adroid Commander) the cache, data, sdcard, etc had a different icon and from some more reading, seemed to be the behavior of the program not having root access to those folders (or are they really partitions?). But I should be especially with that cwm ROM. I'm not really clear what is going on here. So I have been learning and poking around with adb and dbparted since I was trying to see if there were problems with the partitions though I couldn't get print to cooperate. I think the data from the log and those other programs were what I needed. What I've seen in tons of reading on some of those "can't mount /cache" errors is the advice to restore to factory as the cure. I don't think I've seen anything specific of what the problem is that causes this but I don't think anyone has put up the original pit/boatloader/rom I would need to get to my factory setup. Or I'm doing something wrong getting to a base Gingerbread with the 2.3.5 pit and the roms I tried. It seems my partitions are messed up but I'm not quite sure what they should be for me to modify them with sdparted. There seems to a variety going on with the partition types. Still getting nowhere though I figured out how to make Heimdall download the pit from my player once I got past the lib error. Code: Initialising connection... Detecting device... Claiming interface... Setting up interface... Checking if protocol is initialised... Protocol is initialised. Beginning session... Session begun with device of type: 0 Downloading device's PIT file... PIT file download sucessful Entry Count: 14 Unknown 1: 15718400 Unknown 2: 1 Unknown 3: 0 Unknown 4: 0 Unknown 5: 7703 Unknown 6: 237 Unknown 7: 62704 Unknown 8: 18 --- Entry #0 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 1 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 1 Unknown 2: 0 Unknown 3: 0 Partition Name: IBL+PBL Filename: boot.bin --- Entry #1 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 2 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 1 Unknown 2: 0 Unknown 3: 0 Partition Name: PIT Filename: YPG70_8G-0304.pit --- Entry #2 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 3 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 5 Unknown 2: 0 Unknown 3: 0 Partition Name: SBL Filename: Sbl.bin --- Entry #3 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 4 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 5 Unknown 2: 6226025 Unknown 3: 7143533 Partition Name: SBL2 Filename: Sbl.bin --- Entry #4 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 5 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 20 Unknown 2: 0 Unknown 3: 0 Partition Name: PARAM Filename: param.lfs --- Entry #5 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 6 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 40 Unknown 2: 39021280 Unknown 3: 7143533 Partition Name: EFS Filename: efs.rfs --- Entry #6 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 7 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 30 Unknown 2: 36662408 Unknown 3: 0 Partition Name: KERNEL Filename: zImage --- Entry #7 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 8 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 30 Unknown 2: 6684793 Unknown 3: 3014771 Partition Name: RECOVERY Filename: zImage --- Entry #8 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 9 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 1160 Unknown 2: 0 Unknown 3: 0 Partition Name: FACTORYFS Filename: factoryfs.rfs --- Entry #9 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 10 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 536 Unknown 2: 6684780 Unknown 3: 115 Partition Name: DBDATAFS Filename: dbdata.rfs --- Entry #10 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 11 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 256 Unknown 2: 115 Unknown 3: 115 Partition Name: CACHE Filename: cache.rfs --- Entry #11 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 12 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 7696 Unknown 2: 0 Unknown 3: 0 Partition Name: DATAFS Filename: datafs.rfs --- Entry #12 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 13 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 256 Partition Block Count: 20516 Unknown 2: 0 Unknown 3: 0 Partition Name: USERFS Filename: userfs_8G.rfs --- Entry #13 --- Unused: No Partition Type: 2 (EXT4) Partition Identifier: 0 Partition Flags: 1 (R) Unknown 1: 0 Partition Block Size: 0 Partition Block Count: 0 Unknown 2: 0 Unknown 3: 0 Partition Name: GANG Filename: inand_8G.bin I threw different 5.0 pit files from different sgp's at it to see the result. It still booted into recovery with the same can't mount errors no matter if it was the Korean one with the larger memory or the US pit. Everything got messed up again when I tried the 4.0 pits out. Adroid Commander and Droid Explorer also don't seem happy with the stock recovery mode, I can't see anything on the player. With the cwm recovery, both are browsable in those programs except for some partitions. I get fewer boot errors with the cwm/eryigit rom. It seems like the bootloaders don't have permission to get at the important partition folders during boot. Is that the problem.? How is that fixed if so?
There is a full recovery for the yp-G70 intl here: http://forum.xda-developers.com/showthread.php?p=21653631 It includes all the partitions. Sent using Tapatalk
klin1344 said: There is a full recovery for the yp-G70 intl here: http://forum.xda-developers.com/showthread.php?p=21653631 It includes all the partitions. Sent using Tapatalk Click to expand... Click to collapse That ROM was shut down due to too much traffic. I found it elsewhere last week but when I unrar it, the sucker is like 8gigs. What's the deal with that? I also became a bit suspicious of that file due to the cloned articles all over the place with the same instructions. The instructions are a bit off on the articles as they tell you to use the rar in Odin at first and if that doesn't work, to extract it. I didn't think Odin could ever use a rar but maybe so. Some of other cloned articles provide a link to the Samsung USB drivers twice instead of a link to the ROM. They say it's the ROM link but it isn't. And then there is the issue of the missing bootloader file for Odin. The top result in Google has a bunch of replies that they bricked their units following those instructions. The instructions say to check the bootloader in Odin but only has links for the pit and the rom. I know I tried those two files without success though I don't remember the outcome. I got suspicious of some files once I found Heimdall could check the tar even if I couldn't use Heimdall. That rom, along with a few others kicked out errors though they may be less of a problem than I had thought. I'll download it again and poke around to see if it includes a bootloader. I always thought those were separate. Followup: I can't find the file at all now, I can't post to that thread if that person has it, I've overwritten the file on my thumb drive and Recuva keeps crashing in my virtual machine on deep scan. I seem to have a good collection of roms dating back to the froyo 2.2.2 now that I've organized and labeled all my files with their various KP8, KPF, KPA ending codes. Are the partitions changed at all from Froyo to Gingerbread? I've read there are some partition type changes on the custom roms. I'm not sure where I stand on original vs. customs. The last time I ran a pit file it was the international 2.3.5 one. I don't have anything for the original 2.2.2 and since most of the threads are phones, I don't think I could use those if I found one. I'm mostly picking through the info on creating or fixing partitions and matching it up with those outputs on the Recovery ROM thread in post 2.
TiMthisIS said: That ROM was shut down due to too much traffic. I found it elsewhere last week but when I unrar it, the sucker is like 8gigs. What's the deal with that? I also became a bit suspicious of that file due to the cloned articles all over the place with the same instructions. The instructions are a bit off on the articles as they tell you to use the rar in Odin at first and if that doesn't work, to extract it. I didn't think Odin could ever use a rar but maybe so. Some of other cloned articles provide a link to the Samsung USB drivers twice instead of a link to the ROM. They say it's the ROM link but it isn't. And then there is the issue of the missing bootloader file for Odin. The top result in Google has a bunch of replies that they bricked their units following those instructions. The instructions say to check the bootloader in Odin but only has links for the pit and the rom. I know I tried those two files without success though I don't remember the outcome. I got suspicious of some files once I found Heimdall could check the tar even if I couldn't use Heimdall. That rom, along with a few others kicked out errors though they may be less of a problem than I had thought. I'll download it again and poke around to see if it includes a bootloader. I always thought those were separate. Followup: I can't find the file at all now, I can't post to that thread if that person has it, I've overwritten the file on my thumb drive and Recuva keeps crashing in my virtual machine on deep scan. I seem to have a good collection of roms dating back to the froyo 2.2.2 now that I've organized and labeled all my files with their various KP8, KPF, KPA ending codes. Are the partitions changed at all from Froyo to Gingerbread? I've read there are some partition type changes on the custom roms. I'm not sure where I stand on original vs. customs. The last time I ran a pit file it was the international 2.3.5 one. I don't have anything for the original 2.2.2 and since most of the threads are phones, I don't think I could use those if I found one. I'm mostly picking through the info on creating or fixing partitions and matching it up with those outputs on the Recovery ROM thread in post 2. Click to expand... Click to collapse I was able to download it without any problems. It is still stored in his dropbox, so I don't know what you mean by there's too much traffic and it got shut down. The bootloaders are included in the ROM, thats why you have to check phone bootloader update. Also, what "cloned articles" are you talking about?? Links?
klin1344 said: I was able to download it without any problems. It is still stored in his dropbox, so I don't know what you mean by there's too much traffic and it got shut down. The bootloaders are included in the ROM, thats why you have to check phone bootloader update. Also, what "cloned articles" are you talking about?? Links? Click to expand... Click to collapse Sorry if my postings are getting wordy, lack of sleep and constant testing and figuring things out are to blame. I kept getting an error that the download was temporarily restricted due to too much traffic by that user for most of the last week. It just started working again, thanks. When I searched elsewhere by putting the file name into Google a bunch of help guides kept popping up. They are often the same text and offer the same bad links that promise a rom but link to usb drivers. One of the top ones actually had the dropbox link but the high traffic restriction kept dead ending me on that file. They seem to have varying intros and generic pictures but the instructions seems to be copied among them, hence the bad links. Sometimes there are unrelated device videos as part of the walk through. They all begin with "www" if they don't work. I'm link restricted. bestandroidblog.com/android-hacks/how-to-unbrick-your-galaxy-player-5/ androidauthority.com/unbrick-samsung-galaxy-player-5-48449/ This Italian one has the same bad links too: androider.it/3289/guida-come-fare-ad-eseguire-lunbrick-sul-samsung-galaxy-player-5/ They seem to be churned out possibly based on that XDA info that was the first source. I've gotten confused over the bootloaders and partition options at times since some instructions say check the box, others say no. I didn't realize some had bootloaders or pits inside those tars. Especially since there are boxes especially for those right in Odin. Why is that tar so big when unrar-ed? Is it an uncompressed image? I found another image on an xda topic for an international unit. It was gz compressed and was slightly under 8 gigs too when uncompressed but had no file extension. So I'm trying to hunt that source down again and see what/how I am supposed to use that. One interesting find over in the Nexus threads over a user with the same /cache errors with cwm. User cjward23 posted "It sound very similar to an issue a range of HTC devices had that contained a Samsung EMMC. What was happening is that EMMC would not allow certain partitions of the device to written to." That makes sense to me too since the log also shows all those mmc block errors. My thinking now is that the pit and bootloaders I'm using are fine but I have a sort of partial root block even with the cwm either by that EMMC or something else. That would make sense of why the stock restores work if the device is trying to match operations up with stock. CWM's mount and format page can't do much. It won't mount and obviously can't format without the mount. Only the external SD card mounts and the USB mode can then activated. Playing around with Doomlord or SuperOneClick to see about the root status got me nothing. None would connect. I think early on with this device I tried a rooting app but I don't think the test was successful after it claimed it had rooted. But I was too nervous about problems and lack of knowledge of roms kept me away until recently. Problem I have now is getting back to FROYO stock and the 2.2.2 partition. I will be trying that next with the boxes checked on the rom I do have. I may have been mixing that with a GB pit file. G70-recovery.tar is the base GB 2.3.5 Int'l right? That isn't quite stock for me if there is some sort of hardware block that is causing this trouble. Or maybe a locked bootloader but now I just tossing more in since I've just started to consume info on where the rooting mojo happens to see if it matches with what's happened. Update: There's a few files in the G70XXKD6 rar. One seems a bit more for a "light" flash that keeps the customer's old data. The second one I had a bad hash. I found a new one but it fails out if I select repartition <ID:0/004> Can't open the specified file. (Line: 1876) That would be nice to work since I believe my partitions are in the wrong format or that I should definitely repartition when going back to FROYO. What were the change between the two releases? I seem to remember some talk about rfs though right now mine show ext4. I suppose I need to go back to adb and see what I can do with sdparted or fdisk once I figure out which ones need to be manually fixed. I can't quite follow the official instructions that look like their from Samsumg to flash, if not working, to wipe date/factory reset and flash again since I have a soft brick and can't get to recovery until I toss the bootloader back on it. But then I'll the refusals to mount to format again if I do get there.
mine got froyo 2.2.2 maybe i can help may sgp 5.0 has a 2.2.2 i got it over the weekend and mine says yp-g70cb/mea if you have any instructions on how to dump those files from mine so i can upload it somewhere edit i can do a full back up and you can restore it into your player i might have to restore to factory and wipe all data before doing that
To TIMthisIS How did you solve this issue? If fixed. Interesting to know for further help or support.
any solutions? Got anyone a solution to this problem? Uwe
uwemd said: Got anyone a solution to this problem? Uwe Click to expand... Click to collapse This is very old Thread that was never really answered! (common behavior when people they found their solution, they forget to close the request) You have better to open a new one stating your own issue, we will be able to direct you to a possible fix. If you have partionning problem (reading or mounting /dev/block/mmcblk0p14 or upper) we have solution available. This device is very robust...
Thanks! Solved it already bei creating the partition table with fdisk manually.
[Q] File system and partitions
Can some confirm if I understand correctly As I understand internal GS2 memory is divided into several partitions: /dev/block/mmcblk0p9 on /system type ext4 /dev/block/mmcblk0p7 on /cache type ext4 /dev/block/mmcblk0p1 on /efs type ext4 nil on /sys/kernel/debug type debugfs /dev/block/mmcblk0p10 on /data type ext4 /dev/block/mmcblk0p4 on /mnt/.lfs type j4fs /dev/block/vold/179:11 on /mnt/sdcard type vfat So as I understand in CWM recovery: format data formats dev/block/mmcblk0p10 on /data type ext4 format system formats /dev/block/mmcblk0p9 on /system type ext4 format cache formats /dev/block/mmcblk0p7 on /cache type ext4 wipe data / factory reset - on stock deletes everything from dir /data or just some files from dir /data wipe cash - deletes all files from from /cache or just some files from dir /cache wipe dalvik- deletes all files from from /data/dalvik-cache or just some files from dir /data/dalvik-cache format /sdcard formats /dev/block/vold/179:11 on /mnt/sdcard type vfat ???? format /emmc formats what???? In what partition is bootloader? In what partition is kernel? In what partition is CWM recovery? Where are located download mode (home+down+power) system/files? From recent experience I understood that nandroid is not doing backup of all partitions. EFS partition is not backed up. What else is not backed up and what partitions are backed up? What partition is backed up in nandroid boot.img file?
Don't mess with them until you really know what you are doing if bootloader gets messed up then its a brick
I really don't want to have problem and that's why I'm asking. When you know simple basics it much safer to change ROM's
Well, if you'd search before asking questions, you'd have the information already. Basically: Code: 0 '/tmp' 'ramdisk' '(null)' '(null)' 0 1 '/efs' 'ext4' '/dev/block/mmcblk0p1' '(null)' 0 2 '/boot' 'emmc' '/dev/block/mmcblk0p2' '(null)' 0 3 '/recovery' 'emmc' '/dev/block/mmcblk0p6' '(null)' 0 4 '/cache' 'ext4' '/dev/block/mmcblk0p7' '(null)' 0 5 '/system' 'ext4' '/dev/block/mmcblk0p9' '(null)' 0 6 '/data' 'ext4' '/dev/block/mmcblk0p10' '(null)' -16384 7 '/preload' 'ext4' '/dev/block/mmcblk0p12' '(null)' 0 ' 0 '/sdcard' 'vfat' '/dev/block/mmcblk1p1' '/dev/block/mmcblk1 9 '/sdcard1' 'vfat' '/dev/block/mmcblk0p11' '(null)' 0 Bootloader is in p2 and p3. Kernel is in p5. Recovery is inside the kernel. Download mode (home+down+power) system/files is in initramfs (also kernel, basically). Boot.img file contains the kernel if I remember correctly. If you're concerned about partitions, back them all up with dd. However, be careful goes without saying
Sure I was looking, but short and simple answer couldn't find Thanx And additional questions: So if /system (/dev/block/mmcblk0p9) is deleted, then phone still should be able to boot into download or recovery mode? (because Bootloader is in p2 and p3; Kernel is in p5.) Can it be that in boot.img is packed p2, p3, p5 partitions?
/system comes with the ROM, so yes - you can delete it and still have recovery. Why don't you extract the boot.img and see what's in it?
Sure I've tried to extract but.. In phone "Nandroid browser" can't open In windows "unyaffs" says "broken image file" In windows "DiskInternals Linux Reader" also not working
If you search you will find the post that shows how to extract on SGS2 and tools required . jje
limmes said: In what partition is bootloader? In what partition is kernel? In what partition is CWM recovery?boot.img file? Click to expand... Click to collapse i always formats system and boot in cwm 4.x.x but since 5.x.x only system is present, meaning formating boot is good but is more dangerous for all users to access. formating system solves many issues.
[Q] CWM problem formatting /data
I flashed CWM 5.5.0.4 a couple weeks ago because I wanted to flash the latest CM9 KANG. I have been having freezing and reboot issues with all the builds I've flashed from Coffeebeans and Pershoot. I noticed the other day in CWM that when it was formatting /data it would do it really quickly but not give me an error. It took longer to format /cache. I found a recovery.log from 3/28 when I flashed Task's v14 ROM. I went through the log and it looks like it's not formatting /data. Here is some of the log: Starting recovery on Thu Mar 28 23:47:28 2019 framebuffer: fd 4 (1280 x 800) CWM-based Recovery v5.5.0.4 recovery filesystem table ========================= 0 /tmp ramdisk (null) (null) 0 1 /efs ext4 /dev/block/mmcblk0p1 (null) 0 2 /recovery emmc /dev/block/mmcblk0p2 (null) 0 3 /boot emmc /dev/block/mmcblk0p3 (null) 0 4 /system ext4 /dev/block/mmcblk0p4 (null) 0 5 /cache ext4 /dev/block/mmcblk0p5 (null) 0 6 /data ext4 /dev/block/mmcblk0p8 (null) 0 7 /preload ext4 /dev/block/mmcblk0p10 (null) 0 W:Unable to get recovery.fstab info for /datadata during fstab generation! W:Unable to get recovery.fstab info for /emmc during fstab generation! W:Unable to get recovery.fstab info for /sdcard during fstab generation! W:Unable to get recovery.fstab info for /sd-ext during fstab generation! I:Completed outputting fstab. -- Wiping data... Formatting /data... I:Formatting unknown device. rm: can't remove '.' or '..' rm: can't remove '.' or '..' Formatting /cache... Creating filesystem with parameters: Size: 469762048 Block size: 4096 Blocks per group: 32768 Inodes per group: 7168 Inode size: 256 Journal blocks: 1792 Label: Blocks: 114688 Block groups: 4 Reserved block group size: 31 Created filesystem with 11/28672 inodes and 3694/114688 blocks warning: wipe_block_device: Discard failed -- Installing: /sdcard/GalaxyTask_14_Slim.zip Finding update package... I:Update location: /sdcard/GalaxyTask_14_Slim.zip I:using /data/media, no /sdcard found. Opening update package... Installing update... minzip: Extracted file "/tmp/boot.img" ~~~~~~~~~~~~~~ <== Galaxy Task 14 ==>about to run program [/sbin/busybox] with 3 args mount: mounting /dev/block/mmcblk0p8 on /data failed: Device or resource busy After that it finishes installing the ROM without any issues, but I'm worried about why it's not formatting /data. I'm not sure if this has anything to do with it but when I flashed CMW 5.5.0.4 through Odin I accidentally put it in the bootloader section instead of PDA. Does anyone have any ideas on this? Should I just Odin back to stock and start over? Thanks.
[help] clockwork mod recovery not working
I:Loaded font:/res/font.datcan't open /dev/tty0: No such file or directorypredefine pixel_format is 4framebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentLoaded (event0): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event2): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event1): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)CWM-based Recovery v6.0.3.0I: using hack for MTK ext4 [email protected]:[MTK]Get size of ext4 device /cache[/dev/block/mmcblk0p7] from fseek =0x7e00000.I:[MTK]Get size of ext4 device /data[/dev/block/mmcblk0p8] from fseek=0x40000000.I:[MTK]Get size of ext4 device /system[/dev/block/mmcblk0p5] from fseek =0x600000.I:[MTK]Get size of ext4 device /cust[/dev/block/mmcblk0p6] from fseek=0x2bc00000.recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /boot emmc /dev/bootimg (null) 02 /cache ext4 /dev/block/mmcblk0p7 (null) 1319895043 /data ext4 /dev/block/mmcblk0p8 (null) 10736107524 /misc emmc /dev/misc (null) 05 /pro_info emmc pro_info (null) 06 /recovery emmc /dev/recovery (null) 07 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 08 /system ext4 /dev/block/mmcblk0p5 (null) 61603849 /cust ext4 /dev/block/mmcblk0p6 (null) 733872128W:Unable to get recovery.fstab info for /datadata during fstab generation!W:Unable to get recovery.fstab info for /emmc during fstab generation!W:Unable to get recovery.fstab info for /sd-ext during fstab generation!W:Unable to get recovery.fstab info for /external_sd during fstab generation!I:Completed outputting fstab.Irocessing arguments.I:Got arguments from /cache/recovery/commandI:Checking arguments.Warning: No file_contextsI:device_recovery_start()移动叔叔专版www.ydss.cn技术支持: 银狐(yyjdelete)Apr 15 2013 23:19:27Command: "/sbin/recovery""--update_package=CACHE:update.zip"(replacing path "CACHE:update.zip" with"/cache/update.zip")ro.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=running正在查找刷机包...I:Update location: /cache/update.zip正在打开刷机包...I:read key e=3I:read key e=3I:2 key(s) loaded from /res/keys正在验证刷机包...I:comment is 1738 bytes; signature 1720bytes from endI:whole-file signature verified against key 0I:verify_file returned 0正在安装刷机包...Replacing stock recovery with ClockworkMod recovery...about to run program [/sbin/busybox] with 4 argsrm: /etc: is a directoryabout to run program [/sbin/busybox] with 4 argssh: invalid number 'root'sh: can't kill pid 3468: No such processsh: invalid number 'S'sh: invalid number '/sbin/adbd'sh: invalid number 'recovery'sh: can't kill pid 106: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/adbd'sh: invalid number 'root'sh: can't kill pid 14980: No such processsh: invalid number 'S'sh: invalid number '/sbin/recovery'sh: can't kill pid 109: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/recovery'run_program: child exited with status 1script result was [256]Starting recovery on Wed Sep 25 01:18:52 2013can't open /dev/tty0: No such file or directoryframebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentioctl(): blank: Invalid argumentClockworkMod Recovery v5.5.0.4recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /system ext4 /dev/block/mmcblk0p1 (null) 02 /cache ext4 /dev/block/mmcblk0p2 (null) 03 /misc emmc /dev/block/mmcblk0p3 (null) 04 /staging ext3 /dev/block/mmcblk0p4 (null) 05 /data ext4 /dev/block/mmcblk0p8 (null) 0W:Unable to get recovery.fstab info for /datadata during fstab generation!W:Unable to get recovery.fstab info for /emmc during fstab generation!W:Unable to get recovery.fstab info for /sdcard during fstab generation!W:Unable to get recovery.fstab info for /sd-ext during fstab generation!I:Completed outputting fstab.Irocessing arguments.I:Checking arguments.I:device_recovery_start()Command: "/sbin/recovery"ro.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=runningI:Checking for extendedcommand...I:Skipping execution of extendedcommand, file not found...-- Installing: /sdcard/update.zipFinding update package...I:Update location: /sdcard/update.zipI:using /data/media, no /sdcard found.Opening update package...E:Can't open /sdcard/update.zip(No such file or directory Card to mount (20s)SDCard mounted..../tmp/recovery.logwas copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
abhilaab said: I:Loaded font:/res/font.datcan't open /dev/tty0: No such file or directorypredefine pixel_format is 4framebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentLoaded (event0): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event2): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)Loaded (event1): (ev_bits: 0xbedadc94, key_bits: 0xbedadc98)CWM-based Recovery v6.0.3.0I: using hack for MTK ext4 [email protected]:[MTK]Get size of ext4 device /cache[/dev/block/mmcblk0p7] from fseek =0x7e00000.I:[MTK]Get size of ext4 device /data[/dev/block/mmcblk0p8] from fseek=0x40000000.I:[MTK]Get size of ext4 device /system[/dev/block/mmcblk0p5] from fseek =0x600000.I:[MTK]Get size of ext4 device /cust[/dev/block/mmcblk0p6] from fseek=0x2bc00000.recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /boot emmc /dev/bootimg (null) 02 /cache ext4 /dev/block/mmcblk0p7 (null) 1319895043 /data ext4 /dev/block/mmcblk0p8 (null) 10736107524 /misc emmc /dev/misc (null) 05 /pro_info emmc pro_info (null) 06 /recovery emmc /dev/recovery (null) 07 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 08 /system ext4 /dev/block/mmcblk0p5 (null) 61603849 /cust ext4 /dev/block/mmcblk0p6 (null) 733872128W:Unable to get recovery.fstab info for /datadata during fstab generation!W:Unable to get recovery.fstab info for /emmc during fstab generation!W:Unable to get recovery.fstab info for /sd-ext during fstab generation!W:Unable to get recovery.fstab info for /external_sd during fstab generation!I:Completed outputting fstab.Irocessing arguments.I:Got arguments from /cache/recovery/commandI:Checking arguments.Warning: No file_contextsI:device_recovery_start()移动叔叔专版www.ydss.cn技术支持: 银狐(yyjdelete)Apr 15 2013 23:19:27Command: "/sbin/recovery""--update_package=CACHE:update.zip"(replacing path "CACHE:update.zip" with"/cache/update.zip")ro.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=running正在查找刷机包...I:Update location: /cache/update.zip正在打开刷机包...I:read key e=3I:read key e=3I:2 key(s) loaded from /res/keys正在验证刷机包...I:comment is 1738 bytes; signature 1720bytes from endI:whole-file signature verified against key 0I:verify_file returned 0正在安装刷机包...Replacing stock recovery with ClockworkMod recovery...about to run program [/sbin/busybox] with 4 argsrm: /etc: is a directoryabout to run program [/sbin/busybox] with 4 argssh: invalid number 'root'sh: can't kill pid 3468: No such processsh: invalid number 'S'sh: invalid number '/sbin/adbd'sh: invalid number 'recovery'sh: can't kill pid 106: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/adbd'sh: invalid number 'root'sh: can't kill pid 14980: No such processsh: invalid number 'S'sh: invalid number '/sbin/recovery'sh: can't kill pid 109: No such processsh: invalid number 'root'sh: can't kill pid 1844: No such processsh: invalid number 'S'sh: invalid number 'grep'sh: invalid number '/sbin/recovery'run_program: child exited with status 1script result was [256]Starting recovery on Wed Sep 25 01:18:52 2013can't open /dev/tty0: No such file or directoryframebuffer: fd 3 (540 x 960)ioctl(): blank: Invalid argumentioctl(): blank: Invalid argumentClockworkMod Recovery v5.5.0.4recovery filesystem table=========================0 /tmp ramdisk (null) (null) 01 /system ext4 /dev/block/mmcblk0p1 (null) 02 /cache ext4 /dev/block/mmcblk0p2 (null) 03 /misc emmc /dev/block/mmcblk0p3 (null) 04 /staging ext3 /dev/block/mmcblk0p4 (null) 05 /data ext4 /dev/block/mmcblk0p8 (null) 0W:Unable to get recovery.fstab info for /datadata during fstab generation!W:Unable to get recovery.fstab info for /emmc during fstab generation!W:Unable to get recovery.fstab info for /sdcard during fstab generation!W:Unable to get recovery.fstab info for /sd-ext during fstab generation!I:Completed outputting fstab.Irocessing arguments.I:Checking arguments.I:device_recovery_start()Command: "/sbin/recovery"ro.boot.serialno=U4YSYLAQS8R4SG9Dro.serialno=U4YSYLAQS8R4SG9Dro.bootmode=unknownro.baseband=unknownro.bootloader=unknownro.hardware=mt6589ro.revision=0ro.factorytest=0ro.secure=0ro.allow.mock.location=1persist.mtk.aee.aed=onro.debuggable=1persist.sys.usb.config=mass_storage,adbpersist.service.acm.enable=0ro.mount.fs=EXT4ro.mtprof.disable=1init.svc.ueventd=runningro.sf.lcd_density=240init.svc.recovery=runninginit.svc.adbd=runningI:Checking for extendedcommand...I:Skipping execution of extendedcommand, file not found...-- Installing: /sdcard/update.zipFinding update package...I:Update location: /sdcard/update.zipI:using /data/media, no /sdcard found.Opening update package...E:Can't open /sdcard/update.zip(No such file or directory)Installation aborted.I:using /data/media, no /sdcard found Click to expand... Click to collapse as it says no sd card is found .. so is your sd card is working fine or not and in cwm check the mounts and storage that the sd card is mounted or not
Arc 7 Root and Recovery and MT8125 chipset info
Hope this is the right place to post, I've been lurking around the forums since I got my first smart phone a few years ago but never posted as I've usually found what I'm looking for through googling and rtfm'ing, only reason I came out of the shadows was to get my Kobo Arc 7 rooted. No way I could live without it, I had been watching this thread http://forum.xda-developers.com/showthread.php?t=2507886, checking it every few days to see if there was any development when I saw development was pretty much abandoned on the Arc 7. So this all started with a pm that made me try getting root myself with a little help from dazza9075. Basically was told to trade in the arc 7 for an arc 7hd, barring that I could try the new cydiaimpactor update and see if it worked. It went something like this. I followed the instructions for the 7hd: Root Fully setup device Download impactor on PC from http://www.cydiaimpactor.com/ Download android SDK on PC, from http://developer.android.com/sdk/index.html Run SDK manager and acquire the google USB drivers Enable dev mode on device by going to settings, about kobo, and tap build number 7 times Enable USB debug mode in developer options Enable unknown sources in security options Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error. Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface Run the impactor program downloaded earlier, once loaded, click on start Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference) Go to the market place and download SU by Chainfire Credit to http://www.cydiaimpactor.com/ for the rooting tool Chainfire for SU Click to expand... Click to collapse Everything went fine until plugging in the device to let it install a USB composite device. As expected it did fail on the third but when trying to install Google USB drivers it couldn't find any for the device. Just for kicks I opened up Impactor and pressed "Start" it did nothing, I then clicked "USB Scan" and let it complete, then pushed "Start" again. Quick popup on the screen, so I swiped the screen and ran Root Checker Basic and voila I had root. Since then I've pretty much been badgering dazza9075 through pm to see about getting a recovery for it, I'm an old school linux guy, but never spent much time doing any development, so trying to figure things out myself is usually not an issue but this is new to me. I've been utilizing my google fu to try getting a recovery image made and had some success. Basically started with the instructions for dumping the partition info via dazza's instructions. Turned out to be a little more frustrating than anything, all the commands were turning up nothing, then finally I checked chipset specific stuff, it's running an MTK8125 so after getting nowhere with: cat /proc/mounts Code: [email protected]:/ # cat /proc/mounts cat /proc/mounts rootfs / rootfs ro,relatime 0 0 tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 none /acct cgroup rw,relatime,cpuacct 0 0 tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0 tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0 none /dev/cpuctl cgroup rw,relatime,cpu 0 0 tmpfs /storage/emulated tmpfs rw,relatime,mode=705,uid=1023,gid=1023 0 0 /[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0 /[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=or dered 0 0 /dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0 /[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all oc,commit=1,data=ordered 0 0 /[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all oc,commit=1,data=ordered 0 0 /dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i d=1023,default_permissions,allow_other 0 0 /dev/block/vold/179:97 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,rela time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 cat /proc/partitions Code: [email protected]:/ # cat /proc/partitions cat /proc/partitions major minor #blocks name 7 0 1254 loop0 179 0 7523456 mmcblk0 179 1 1 mmcblk0p1 179 2 10240 mmcblk0p2 179 3 10240 mmcblk0p3 179 4 6144 mmcblk0p4 179 5 786432 mmcblk0p5 179 6 524288 mmcblk0p6 179 7 6145664 mmcblk0p7 179 64 2048 mmcblk0boot1 179 32 2048 mmcblk0boot0 179 96 15637504 mmcblk1 179 97 15633408 mmcblk1p1 So trying to find the ls -al /dev/block/platform/dw_mmc/by-name was the first hurdle as there was no "by-name" Code: ls -al /dev/block/platform/dw_mmc/by-name ls -al /dev/block/platform drwxr-xr-x root root 2014-01-29 20:33 mtk-msdc.0 drwxr-xr-x root root 2014-01-29 20:33 mtk-msdc.1 ls -al /dev/block/platform/mtk-msdc.0 drwxr-xr-x root root 2014-01-29 20:33 by-num lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0 -> /dev/block/mmcblk0 lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0boot0 -> /dev/block/mmcblk0boot0 lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0boot1 -> /dev/block/mmcblk0boot1 lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p1 -> /dev/block/mmcblk0p1 lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p2 -> /dev/block/mmcblk0p2 lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p3 -> /dev/block/mmcblk0p3 lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p4 -> /dev/block/mmcblk0p4 lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p5 -> /dev/block/mmcblk0p5 lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p6 -> /dev/block/mmcblk0p6 lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p7 -> /dev/block/mmcblk0p7 ls -al /dev/block/platform/mtk-msdc.1 drwxr-xr-x root root 2014-01-29 20:33 by-num lrwxrwxrwx root root 2014-01-29 20:33 mmcblk1 -> /dev/block/mmcblk1 lrwxrwxrwx root root 2014-01-29 20:33 mmcblk1p1 -> /dev/block/mmcblk1p1 but an ls -l revealed: Code: [email protected]:/ # ls -l ls -l drwxr-xr-x root root 2014-01-31 08:16 acct -rw-r--r-- root root 16927 1969-12-31 18:00 advanced_meta_init.rc drwxrwx--- system cache 2014-01-28 19:01 cache dr-x------ root root 2014-01-31 08:16 config -rw-r--r-- root root 4 1969-12-31 18:00 custom_build_verno lrwxrwxrwx root root 2014-01-31 08:16 d -> /sys/kernel/debug drwxrwx--x system system 2014-01-31 08:17 data -rw-r--r-- root root 185 1969-12-31 18:00 default.prop drwxr-xr-x root root 2014-01-31 08:16 dev lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p5 lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p6 lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p1 lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_f -> /dev/block/mmcblk0p2 lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_s -> /dev/block/mmcblk0p3 lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_ro -> /dev/block/mmcblk0p4 lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p7 So I focused on googling emmc partition tables and stumbled upon this thread http://forum.xda-developers.com/showthread.php?t=2450045 which again I followed with little success. I had already tried way 1 and way 2 and way 3 couldn't read the partition table. So I followed the comments and #3 mentioned "cat /proc/emmc", so: Code: [email protected]:/ # cat /proc/emmc cat /proc/emmc partno: start_sect nr_sects partition_name emmc_p1: 00000400 00000002 "ebr1" emmc_p2: 00006800 00005000 "protect_f" emmc_p3: 0000b800 00005000 "protect_s" emmc_p4: 00016c00 00003000 "sec_ro" emmc_p5: 00020c00 00180000 "android" emmc_p6: 001a0c00 00100000 "cache" emmc_p7: 002a0c00 00bb8d00 "usrdata" Still not giving me a good picture of the partition table so I followed that thread till the end which took me to this thread, http://forum.xda-developers.com/showthread.php?t=1959445. So in fashion I started following that. So Using fdisk: Code: [email protected]:/ # fdisk -l /dev/block/mmcblk0 fdisk -l /dev/block/mmcblk0 Warning: ignoring extra data in partition table 5 Warning: ignoring extra data in partition table 5 Disk /dev/block/mmcblk0: 7704 MB, 7704018944 bytes 1 heads, 16 sectors/track, 940432 cylinders Units = cylinders of 16 * 512 = 8192 bytes Device Boot Start End Blocks Id System /dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended Partition 1 does not end on cylinder boundary /dev/block/mmcblk0p2 1665 2944 10240 83 Linux Partition 2 does not end on cylinder boundary /dev/block/mmcblk0p3 2945 4224 10240 83 Linux Partition 3 does not end on cylinder boundary /dev/block/mmcblk0p4 5825 6592 6144 83 Linux Partition 4 does not end on cylinder boundary /dev/block/mmcblk0p5 8385 106688 786432 83 Linux parted: Code: [email protected]:/ # 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 Error: Can't have a partition outside the disk! gdisk: Code: [email protected]:/ # gdisk -l /dev/block/mmcblk0 gdisk -l /dev/block/mmcblk0 GPT fdisk (gdisk) version 0.8.4 EBR signature for logical partition invalid; read 0x0000, but should be 0xAA55 Error reading logical partitions! List may be truncated! Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format. *************************************************************** Disk /dev/block/mmcblk0: 15046912 sectors, 7.2 GiB Logical sector size: 512 bytes Disk identifier (GUID): E01B69E6-D822-467F-B1D2-97C0B7BA9ABA Partition table holds up to 128 entries First usable sector is 34, last usable sector is 15046878 Partitions will be aligned on 1024-sector boundaries Total free space is 13420733 sectors (6.4 GiB) Number Start (sector) End (sector) Size Code Name 2 26624 47103 10.0 MiB 8300 Linux filesystem 3 47104 67583 10.0 MiB 8300 Linux filesystem 4 93184 105471 6.0 MiB 8300 Linux filesystem 5 134144 1707007 768.0 MiB 8300 Linux filesystem Still no love. So I read on to the emmc section of that thread and understand nothing, more google fu gets me here: https://github.com/ameer1234567890/OnlineNandroid/wiki/How-To-Gather-Information-About-Partition-Layouts. So now I'm looking at the emmc stuff thinking this really doesn't help me, but remembering I'm running an mtk chip I was pretty happy when I got: Code: [email protected]:/ # cat /proc/dumchar_info cat /proc/dumchar_info Part_Name Size StartAddr Type MapTo preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0 ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1 pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0 pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0 nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0 protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2 protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3 seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0 uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0 bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0 recovery 0x0000000000600000 0x0000000002780000 2 /dev/block/mmcblk0 sec_ro 0x0000000000600000 0x0000000002d80000 2 /dev/block/mmcblk0p4 misc 0x0000000000080000 0x0000000003380000 2 /dev/block/mmcblk0 resv 0x0000000000080000 0x0000000003400000 2 /dev/block/mmcblk0 logo 0x0000000000300000 0x0000000003480000 2 /dev/block/mmcblk0 expdb 0x0000000000a00000 0x0000000003780000 2 /dev/block/mmcblk0 android 0x0000000030000000 0x0000000004180000 2 /dev/block/mmcblk0p5 cache 0x0000000020000000 0x0000000034180000 2 /dev/block/mmcblk0p6 usrdata 0x00000001771a0000 0x0000000054180000 2 /dev/block/mmcblk0p7 bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0 Part_Name:Partition name you should open; Size:size of partition StartAddr:Start Address of partition; Type:Type of partition(MTD=1,EMMC=2) MapTo:actual device you operate Bingo, so finally, root, partition info, next recovery. Again I'm green here so I searched and searched and searched until finally I found the lenovo has the same chip that someone else had managed to get a recovery installed. So I've spent most of my day with this page, trying to get a recovery installed http://forum.xda-developers.com/newthread.php?do=postthread&f=613. So I managed to get everything done, booted into CWM recovery, finished up all excited, then started testing CWM first reboot and I'm back to the stock android recovery. So I ended up finding the recovery.img that was created through the steps in the above link and did: Code: adb shell mount -o remount,rw /system mv /system/recovery-from-boot.p /system/recovery-from-boot.p-orig mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh-orig As this was apparently a known problem with some samsung devices. Then: Code: fastboot flash recovery "path to recovery" Which I cut and pasted the path, then rebooted the Arc 7 into fastboot by holding down the Volume up and power slider for aproximately 30 seconds. Fastboot was successful but hung after installing the recovery.img so I hard rebooted and got back into the arc. So I've tested it a few times and now it's booting into CWM recovery, I had two backups made during the image creation process and have been able to restore from both backups, tried creating a backup which completed with an error, can't remember what it is at this point though I will try again later. Only thing I'm noticing is when I boot into recovery it throws the following errors. Code: CWM automade 03.02.2014 11:23:02 E:Can't mount /cache/recovery/command E:Can't mount /cache/recovery/log E:Can't open /cache/recovery/log E:Can't mount /cache/recovery/last-log E:Can't open /cache/recovery/last_log At this point I'm not sure if this is a problem or not as so far everything seems to be working, I will continue testing this recovery out then hopefully post it to dazza9075's original thread. At this point I really don't know what to do from here and any input would be greatly appreciated, dazza has been a great help but I'm at the mercy of being in different countries and timezones, so the pm process is always a little hurry up and wait. Apologies again if this is the wrong place to post, and thanks to all the people in the other posts above for all the hard work they have put in. Hopefully having some of this information in one place will help others with Microtek Chips.
Good work mate! Have you tried creating a backup yet? and can you post the contents of your FSTAB? The important one for you is probably to get the SD card mounted, with the internal storage quite low backups will be tricky, so we need to be able to mount an external SD card and use that for the backup. I wouldn't be to worried about the other partitions that haven't mounted yet, lets concentrate on the important ones, /system /cache /recovery /boot once we can confirm that you can back then restore we can tidy up the other issues. Good work mate!
Here is my fstab: Code: # Android fstab file. #<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags> # The filesystem that contains the filesystem checker binary (typically /system) cannot # specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK /[email protected] /system ext4 ro,noatime wait /[email protected] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait /[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer It appears that my external sdcard is getting mounted for backups anyways as my backups are all being found in /storage/sdcard1/clockworkmod/backup/. Here is the output from CWM during the backup: Code: E:Can't mount /cache/recovery/log E:Can't open /cache/recovery/log E:Can't mount /cache/recovery/last_log E:Can't open /cache/recovery/last_log SD Card space free: 7225MB Backing up boot image... Backing up recovery image... Backing up system... Backing up data... No /sdcard/.android_secure found. Skipping backup of applications on external storage. Backing up cache... Can't mount /cache! E:Can't mount /cache/recovery/log E:Can't open /cache/recovery/log E:Can't mount /cache/recovery/last_log E:Can't open /cache/recovery/last_log Checking the new backup folder created only yields boot.img, data.ext4.tar, recovery.img and system.ext4.tar Pretty much looks like we just need to get the /cache mounting properly then it should go off without a hitch. Correction, just tried wiping the cache from CWM rebooted to delete the failed backups off the device, booted back into recovery and was greeted by the stock android recovery.
Okay so after getting the stock android recovery after wiping the cache 3 times I decided to start fresh. Factory reset Selected english Forced to update Rooted with impactor Installed SU Installed rom toolbox fastboot flash recovery "path-to"\recovery.img power down the volume up powerslider til menu pops up select fastboot image flashes and says complete, hold power slider to power down and rebooted into cwm (volume up and power slider till menu pops up then restore) and this is what I got: Code: rua1 autoCWM v5.5.0.4 for arc 7 -reboot system now -install zip from sdcard -wipe data/factory reset -wipe cache partition -backup and restore -mounts and storage -advanced CWM automade 03.02.2014 11:23:02 SD Card space free: 7852MB Backing up boot image... Backing up recovery image... Backing up system... Backing up data... No sd-ext found. Skipping backup of applications on external storage. Backing up cache... No sd-ext found. Skipping backup of sd-ext. Generating md5 sum... Backup complete! Rebooted From rom toobox "Rom Management" selected custom cwmr swiped to backups selected backup I just made and rebooted into cwm from rom toolbox Code: CWM automade 03.02.2014 11:23:02 Waiting for SD Card to mount (20s) SD Card mounted... Verifying SD Card marker... ############################# # ROM Toolbox Lite v. 5.9.8 # # Feb 04, 2014 # ############################# E:unknown volume for path [/storage/sdcard1/clockworkmod/backup/2014-02-04.17.00.21] Can't mount backup path /tmp/recovery.log was copied to /sdcard/clockworkmod/revoery.log. Please open ROM Manager to report the issue. So for kicks I tried to restore the backup manually from /storage/sdcard1/clockworkmod/backup/* Code: Checking MD5 sums... Erasing boot before restore... Restoring boot image... Restoring system... Restoring data... .android_secure.img not found. Skipping restore of /sdcard/.android_secure. Restoring cache... sd-ext.img not found. Skipping restore of /sd-ext. Restore complete! rebooted kobo, everything seems to be in place. Boot back into recovery to make sure it's cwm not stock android. Rom Toolbox Lite -> Rebooter -> Reboot Recovery. Bam, back into CWM. So it is backing up to the external sdcard and can restore from there it just can't do it automagically!? Regardless aside from not finding ext-sd everything seemed to work.
Have you disabled the auto recovery repair thing? I'm away from my computer at mo but if you kook at the arc recovery rom process there is a file you need too delete, that stops custom recovery getting replaced at boot Sent from my GT-I8750 using XDA Windows Phone 7 App
I renamed those files as I had read they were causing similar issues on Samsung devices. Now they are renamed and moved to another folder. I'm flashing http://forum.xda-developers.com/showthread.php?t=1916098 right now. it backed up okay, but couldn't find the file. The zip was saved to /sdcard/downloads but its reading my sdcard which is /storage/sdcard1 as /sdcard. I did a wipe to flash that and when it couldn't find it it rebooted to factory. I'm back in CWM doing a system restore from the backup it just made. So it is working, just seems to be issues with paths. I am able to flash manually once in CWM though.
howlinwolf430 said: I renamed those files as I had read they were causing similar issues on Samsung devices. Now they are renamed and moved to another folder. I'm flashing http://forum.xda-developers.com/showthread.php?t=1916098 right now. it backed up okay, but couldn't find the file. The zip was saved to /sdcard/downloads but its reading my sdcard which is /storage/sdcard1 as /sdcard. I did a wipe to flash that and when it couldn't find it it rebooted to factory. I'm back in CWM doing a system restore from the backup it just made. So it is working, just seems to be issues with paths. I am able to flash manually once in CWM though. Click to expand... Click to collapse your Fstab is very odd looking, it does look exactly like what you find within android but the recovery ones I have been using are a little different here is mind Code: /system ext4 /dev/block/mmcblk0p3 /sdcard datamedia /dev/block/mmcblk0p8 /dev/block/platform/mmcblk0 /cache ext4 /dev/block/mmcblk0p4 /data ext4 /dev/block/mmcblk0p8 /recovery emmc /dev/block/mmcblk0p1 /boot emmc /dev/block/mmcblk0p2 /misc emmc /dev/block/mmcblk0p5 /staging emmc /dev/block/mmcblk0p6 /metadata emmc /dev/block/mmcblk0p7 That is for the 10HD, /SDcard in this case is an internal chip, there is no external chip, I have to have it set at "data media" but on the original Arc I have it set to "vfat". For the 10HD I cant manually mount /SDCARD, but it does do it itself when backing up and restoring but on the Arc it works fine, I can manually mount and unmount. Im a little unsure why its not working on the 10HD, a chap was going to have a look for me but hasn't yet got back to me. format is /mount_point Mount_type /location below is the fstab of Astrali, his been a good help with mine Code: # mount point fstype device [device2] /boot emmc /dev/block/mmcblk0p16 /cache ext4 /dev/block/mmcblk0p18 /data ext4 /dev/block/mmcblk0p21 length=-16384 /recovery emmc /dev/block/mmcblk0p13 /misc emmc /dev/block/mmcblk0p11 [B]/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1[/B] /system ext4 /dev/block/mmcblk0p17 /sys_boot vfat /dev/block/mmcblk0p3 /FOTA emmc /dev/block/mmcblk0p19 [B]/sdcard1 vfat /dev/block/mmcblk0p20[/B] [B]/sd-ext auto /dev/block/mmcblk1p2[/B] #added sd-ext support by Astrali [B]/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1[/B] #added for rom manager support Here we can see /external_SD and /sdcard are actually the same thing (?) mounted from blk1p1 (likely an external Sdcard) I don't know why there is two mounts, perhaps different software looking for the same thing but in different places? /SDcard1 is mounted from blk0p20 so probably internal storage, /sd-ext however is mounted from blk1p2, likely a second partition on an external card
/boot mtd boot /cache yaffs2 cache /data yaffs2 userdata /misc mtd misc /recovery mtd recovery /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 /system yaffs2 system /sd-ext ext4 /dev/block/mmcblk0p2 keep this in mind, im just building a recovery img just now based on this...
Can you please upload kobo arc 7 stock rom or system.img