[Q] [GT-P7100] partition layout problem? - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Hello everyone!
I have Samsung Galaxy Tab 10.1v (GT-P7100, Hungarian Vodafone).
I rooted unlocked it. Last day I tried to push the latest version of (beta) Ice Cream Sandwich (Galaxy Tab) rom from XDA-developers.
This went wrong. I scrwed up my Tablet. It is frozen on the opening screen.
I tought, no problem, I can push the older ROM. But I can't.
It seems to be the partition layout changed and I can't push any rom into the Tab.
I tried everything. What function can use on the Tablet?
I can use the Tablet in download mode with Odin3 v1.85.
I tried many older ROM install to my tablet with Odin.
Apparently finished Odin with success, but the boot process failed. (Frozen Galaxy Tab logo)
At least I tried to use correct PIT file with the ROM, but the same.
I can boot via fastboot, and I can boot the Tab with clockworkmod recovery image (4.0.0.4 or 5.0.2.3) but I can't use the "mount USB" function. -> "E:Unable to open ums lunfile (No such file or directory)"
After clockworkmod factory reset -> Frozen Galaxy Tab logo.
I tought, no problem, I can use the adb to push my older image to my Tab.
I did it, I found the uploaded ZIP file in Clockworkmod recovery (install zip from card). The install process started, and finished with this error: E: failed to mount /efs (invalid argument)
I use adb shell to check my system.
This is what I say after the boot:
Code:
#df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 362.1M 32.0K 362.1M 0% /dev
/dev/block/mmcblk0p5 189.0M 4.2M 184.7M 2% /cache
Code:
# mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p5 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1,
data=ordered)
Code:
# cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p5 /cache ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p4 /system ext4 rw
I can mount /data partition manualy.
Code:
~ # mount /data
mount /data
~ # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 362.1M 32.0K 362.1M 0% /dev
/dev/block/mmcblk0p5 189.0M 4.2M 184.7M 2% /cache
/dev/block/mmcblk0p8 14.1G 463.1M 13.7G 3% /data
~ #
So, I think the main problem is, that my partition layout is wrong.
What is the correct layout of Galaxy Tab 10.1?
It is possible to create the correct layout with a simple shell script?
Or maybe any other idea?

---

Basically I love how you have attempted everything, makes it easier for me to deal with this
The lunfile error is common only because it was not properly fixed, All CWM has this issue as this is a port over for the GTab.
Odin usually does the repartitioning automatically, so you don't need to worry about it, as per the frozen logo how long does it stay? as the initial first boot per flashed firmware takes about 2-3minutes as the dalvik cache is being generated. when it's done, you will feel a vibration that's when you know it's alright.
What you should do is, flash a stock firmware, 3.2, Then wait for it to boot up, if it loops, then you flash CWM, then go to CWM recovery, factory reset followed by fix permissions.
It should boot from there

---

Dear Misledz,
thank you your quick reply.
I found the latest rom in samfirmware.com.
It has only old ROMs for this Galaxy version.
Code:
GT-P7100 P7100BUKE2 ## 3.0.1. 2011 May
GT-P7100 P7100BUKDC ## 3.0.1. 2011 April
GT-P7100 P7100BUKDF ## 3.0.1. 2011 April
GT-P7100 P7100BUKC8 ## 3.0.1. 2011 March
I used thw P7500 series ROMs already (last good ROM was also P7500) so I downloaded from samfirmware.com this:
GT-P7500 P7500XWLA1 3.2 2012 January Hungary
I booted into download mode the tab. (Odin3 Download Mode (Protocol v2)
Put the file in Odin3 v1.85 into PDA section (P7500XWLA1_P7500OXXLA1_P7500XXKL4_HOME.tar.md5)
The flash process failed, here is the log from Odin.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7500XWLA1_P7500OXXLA1_P7500XXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.img
<ID:0/012> NAND Write Start!!
<ID:0/012> bootloader.bin
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The screen on the tablet in red border:
Invalid binary signature.
Now I try to download the old 3.0.1 P7100BUKE2 rom and reply again.
Thanks +1!
Misledz said:
Basically I love how you have attempted everything, makes it easier for me to deal with this
The lunfile error is common only because it was not properly fixed, All CWM has this issue as this is a port over for the GTab.
Odin usually does the repartitioning automatically, so you don't need to worry about it, as per the frozen logo how long does it stay? as the initial first boot per flashed firmware takes about 2-3minutes as the dalvik cache is being generated. when it's done, you will feel a vibration that's when you know it's alright.
What you should do is, flash a stock firmware, 3.2, Then wait for it to boot up, if it loops, then you flash CWM, then go to CWM recovery, factory reset followed by fix permissions.
It should boot from there
Click to expand...
Click to collapse

---

Well yes because you cannot flash a 7500 ROM on a 7100 that would obviously fail because the RAM disks are different and careful it may cause a brick, brother.
7500 and 7100 are different models, please don't mix them up.

---

Hi,
I tried to install the latest official Samsung GT-P7100 ROM (3.01.).
I downloaded this file from samfirmware ->
GT-P7100 P7100BUKE2 ## 3.0.1. 2011 May.
This Zip file contains 3 files.
I put this 3 files in Odin. (see screenshot 1 name: odin.jpg)
It was success process, here is the Odin log:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_P7100BUKC8.tar.md5 is valid.
<OSM> PDA_SIGNED_HRI83_BUKE2.tar.md5 is valid.
<OSM> MODEM_HRI83_BUKDF_REV_03.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> bootloader.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> boot.img
<ID:0/012> system.img
<ID:0/012> recovery.img
<ID:0/012> modem.bin
<ID:0/012> Transmission Complete..
<ID:0/012> Now Writing.. Please wait about 2 minutes
<ID:0/012> Receive Response form LOKE
<ID:0/012> RQT_CLOSE !!
<ID:0/012> RES OK !!
<ID:0/012> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/012> Removed!!
After this, the Tablet started to reboot.
During the reboot I saw an android robot and above an exclamation mark.
I made photo with my phone. (screenshot 2: exclamation.jpg)
When this exclamation mark dissapiered the Tablet started to reboot.
Shown the Galaxy logo, then the blue LED indicator next to the front camera illuminated on the top.
The inticator LED switched off, but the logo remained.
Waited cc 20 mins, but nothing else. (screenshot 3: logo.jpg)
I didn't feel the little vibration as you mentioned.
After that I booted into ClockworkMod Recovery v4.0.0.4,
then made factory reset, and fix permition. (screenshot 4: clockwork.jpg)
At least I rebooted. Unfortunately the same, no boot after the Samsung logo.
At the end, I made recovery log with Clockwork.
I put here. (Only deleted my serial number.)
No more idea... (But I saw in the log, that the partition table is okay in the fstab)
Just for sure, I made pics from my USB mode and Download mode screen maybe you can see anything. (screenshot 5: usbmode.jpg, screenshot 6: downloadmode.jpg)
Recovery log: (I cange the http link in the log, because the forum doesn't allowed to send it.)
Code:
/data/media/clockworkmod # cat recovery.log
cat recovery.log
Starting recovery on Fri Mar 29 12:26:07 2019
framebuffer: fd 4 (1280 x 800)
ClockworkMod Recovery v4.0.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /efs ext4 /dev/block/mmcblk0p1 (null)
2 /boot emmc /dev/block/mmcblk0p3 (null)
3 /cache ext4 /dev/block/mmcblk0p5 (null)
4 /data auto /dev/block/mmcblk0p8 (null)
5 /misc emmc /dev/block/mmcblk0p6 (null)
6 /recovery emmc /dev/block/mmcblk0p2 (null)
7 /system ext4 /dev/block/mmcblk0p4 (null)
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.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=HRI83
ro.build.display.id=HRI83.313
ro.build.version.incremental=eng.root.20110616.175603
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Thu Jun 16 17:56:22 EDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=root
ro.build.host=pershoot-ubuntu
ro.build.tags=test-keys
ro.product.model=p7510
ro.product.brand=samsung
ro.product.name=p7510
ro.product.device=p7510
ro.product.board=p7100
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=p7510
ro.build.description=GT-P7510-user 3.0.1 HRI83 313 release-keys
ro.build.fingerprint=samsung/GT-P7510/GT-P7510:3.0.1/HRI83/313:user/release-keys
ro.cwm.prefer_tar=true
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rommanager.developerid=cyanogenmod
ro.url.legal= *removed google link*
ro.url.legal.android_privacy=*removed google link*
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.modversion=CyanogenMod-7.1.0-RC0-Harmony-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=*************************************
ro.bootmode=unknown
ro.baseband=%s
ro.carrier=unknown
ro.bootloader=P7100BUKB7
ro.hardware=p7100
ro.revision=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:using /data/media, no /sdcard found.
/data/media/clockworkmod #
ps.: If you see in the log the Tab says from itself:
ro.product.model=p7510
ro.product.brand=samsung
ro.product.name=p7510
ro.product.device=p7510
ro.product.board=p7100
So I tought it is almost the same machine, and I used the 7500 ROM already...

---

Just a little more bad experience:
I tried upload every "factory" stock ROM for GT-P7100 via Odin3 but still nothing changed. This make me mad slowly.
This were the tried ROMs.
Code:
GT-P7100 P7100BUKE2 ## 3.0.1. 2011 May
GT-P7100 P7100BUKDC ## 3.0.1. 2011 April
GT-P7100 P7100BUKDF ## 3.0.1. 2011 April
GT-P7100 P7100BUKC8 ## 3.0.1. 2011 March

---

Why not flash a 3.2 rom directly? 3.1 is very buggy
Sent from my GT - I9003 in the bathroom

---

Unfortunately no 3.2 original (or stock) ROM for GT-P7100...
Only that ROMs...
What information can I provide to you to get closer to the un-brick...?

---

Holy crap, I just realized it's 7100 and not 7510
Yes 3.1 is the only firmware for it, Sorry was mistaken for another series.
When you say nothing has changed, what exactly do you mean?
The flash is completed but freezes? Or the flash fails? Let's tackle it down 1 by 1 I'm willing to help you see this through.
Fitz.

---

First of all: thank you your patient and help!!!
Before bricked my Tablet, I used this custom ROM from XDA-developers:
[ROM][4 Dec][HC32] isi-galaxy 1.2.5v with pershoot's kernel
(http://forum.xda-developers.com/showthread.php?t=1372432)
Because my Tablet is unusable, I tought put this isi-ram back on my P7100.
I did the install steps that wrote in the isi-galaxy article. (As I mentioned, I did already once and was everything fine.)
But now something went wrong.
The installation process was successful (seemingly) but when I began to reboot my tab, this error message welcome me (no galaxy tab logo).
See the attached file.

---

Basically you don't have a normalboot.img either your bootsector was written to another partition or you may need to repartition it again.
Have you attempted flashing the pit file and the firmware file together? That should reformat and recreate into one partition only.

---

Yes, I tried it already.
The only PIT file what the Odin accept with the ROM file is this: android_fastboot_emmc_full_p4_16G_32G.pit
But the problem remain the same.
I have two question:
1. If an another Tablet user make from his device a NANROID backup and send me
the backup file can I restore my device from this backup?
2. how can I check which partiton contains the bootimage?

---

You may be able to do that, you may need a CWM backup image from someone, but I wouldn't suggest it as it also contains the efs and it will overwrite your IMEI too with his. Which is a bad idea as whatever he downloads in the Market, will be downloaded to your's too, or so I've heard. Since CWM backs up the EFS partition too.
I think that should be in the normalboot.img, you can try to open up the firmware with 7zip or WinRar, you'll find it in there. I wouldn't mess around with it too much though, then again, have you tried Kies? what has kies detected about your tablet?
On another note, if you have an efs backup on your device you can always copy that and paste it into that guy's nandroid backup and replace it, so the data that get's replaced is with your IMEI instead. That's one workaround, but efs gets generated on first boot, which you seem to be unable to do right now.
Best bet would be to flash CWM Recovery and do a complete wipe with internal aswell. Something else is conflicting with it.

---

Finally I went to Samsung official service. They replaced the motherboard of my Tablet. Easy!

---

hi! I can confirm is bootloader problem , exactly same problems to me , but my tab had no root nor openbootloader, it just happened flashing with odin from 3.0.1 to 3.2.1 official smsung firm...
I have no posibility to purchase samsung sat so a bit of help may be thankfull... my tab is dead and useless.
Can´t find a repartition file, all ops found for 7500 model and 7510, can pit file may be fit for p7100???????
thx!!!!!!!!!!

---

I know that this is an old post, but I have exactly the same problem and find no easy solution ..
But I have not even Clockwork.
Has anyone perhaps now figured out how to fix it?

---

seems the problem is partitioning with p7500. got a tabled damaged like this as well. there is no pit file for p7100 thus no chance to recover original partitioning.. i guess?
anyway, cannot mount all needed paths, while /dev/block/mmc**** exist, mke2fs outputs "invalid block size". probably because of the 7500 pit.
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
maybe it is worth trying installing a rom for non-3g tab? would it skip /efs checking?

---

Can someone create a pit file for p7100 (10.1v)? I guess the program is called Pit Magic, that extracts partition table settings..
Please help save a bricked device ?
Sent from my GT-N7000 using xda app-developers app

---

So can someone create pit file for P7100 or not? I got same device as others with damaged partitions (green robot with exclamation)

---

Wizard(LV) said:
So can someone create pit file for P7100 or not? I got same device as others with damaged partitions (green robot with exclamation)
Click to expand...
Click to collapse
Damn, I have the same problem.
Tried to repartion and now it only boots on ODIN3 download mode...
Guess it's just an expensive mirror now?