yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Q&A, Help & Troubleshooting] Moester:
I've successfully rooted my P1000 Gingerbread yesterday (I used d00mlord's way)

My primary reason for rooting is to freeze bloatware and consequently to free RAM, which I have already done.

I'm quite happy with my Tab as is, so I'm wondering whether I should go ahead and flash a custom ROM? I don't think I would need it and I'm a bit intimidated when I read some of the posts here. The increase in speed is very appealing though.

:)
[Galaxy Tab Q&A, Help & Troubleshooting] blcpl:
You could try installing an Ice Cream Sandwich based rom, if you wanted to try; it works a lot better in general for a tablet (definitely more suited to it than gingerbread), it lets you access newer version of some apps (like a better kindle client and Chrome as a web browser) and works pretty much fine.

It's also not as hard as it may seem, as long as you have everything ready beforehand you could get it ready in a couple hours.

You can always make a full backup of your current working setup, so if worst comes to worst, you can get back to it :)
[Galaxy Tab Q&A, Help & Troubleshooting] achaa:
help me

Help me. http://xdaforums.com/showthread.php?t=1296330 When i done 12th step tablet don't power up.I tried to charge 4 hours but nothing.It doesnt charge and stops line rolling in big battery icon. It doesn't go to download mode,recovery mod. HELP ME. What should i do.sorry for my bad english and tell me grammar mistakes in post.(I must give TOEFL test). and what should i do with my tab.
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
I saw at least 6 places you posted regarding your issue.

It is not going to help.

And, if there are 6 answers all telling you different things to do, I wish you your very best.
[Galaxy Tab Q&A, Help & Troubleshooting] mg09charis:
galaxy tab

sir question. . .i would like to ask about galaxy . .. can i install the CCNA 4.0 exploration in it?
[Galaxy Tab Q&A, Help & Troubleshooting] ChrisCTX:
Anybody got experience dealing with the Encryption Unsuccessful bug on this particular device (CDMA).
[Galaxy Tab Q&A, Help & Troubleshooting] xhowardtheduckx:
today i really messed up and i need some advice

i have a p1000 that i was running 2.3.6 on and i tried to root it using cf root with odin. odin said the root was succesful, however when the device rebooted the touchscreen portion no longer works the only buttons that work are the power and volume up and down modes.

i then tried to flash the original rom from the samsung firmware site the flash is a success but the touchscreen still does not work. the two firmwares i tried to flash was 2.2 froyo and 2.3.4 gingerbread. any suggestions would be greatly appreciated because i am currently at a loss. :highfive:
[Galaxy Tab Q&A, Help & Troubleshooting] TheATHEiST:
Re-stock with overcome.
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
Are you sure you have P1000, not P1000L or P1000N ?
[Galaxy Tab Q&A, Help & Troubleshooting] swooshman:
response awaited- ad hoc wi fi

Hi need help in connecting gt p 3113 to ad hoc wifi, can't find any solutions, kind of desperate,

Thanks in advance...
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
so, be desperate in your own device forum

http://xdaforums.com/forumdisplay.php?f=1596

This one you posted in is only for Galaxy Tab 7" original
[Galaxy Tab Q&A, Help & Troubleshooting] Stjom:
Hi, Coming from official GB, I installed CM-9 RC1 in my P1000. But I noticed that some of my games that ran on the previous ROM (Official GB) do not run on CM9 build. I'm wondering if it's a kernel problem or what. Do you have any idea on why this problem occurs?

Thanks!
[Galaxy Tab Q&A, Help & Troubleshooting] dorsumsallae:
Have same problem using cm10
[Galaxy Tab Q&A, Help & Troubleshooting] Barhoom-P1000:
Help

Hi guys I need some help

I tried to update my Galaxy tab P-1000 from (GB)2.3.3 to aokp galaxytab build25 /rom build on cm9/ unfortunately rom stock on bootscreen.

So I entered again recovery mode (I'm using CWM) , preformed a complete wipe /without formatting sd/

After that, I tried to flash an other rom, suddenly recovery crashed weirdly, and I'm unable to access sd or doing anything else (unmount anything)

PC doesn't recognize my tab either on ODIN or even normally, I reinstalled Kies, and nothing happened......

So now I'm stock on bootscreen ie on a broken recovery mode

Can anyone help me, Please

Thank you
[Galaxy Tab Q&A, Help & Troubleshooting] RiderG:
P1000 GSM - which ROM

I gambled and lost... I had rooted my GSM tab using zerg-Rush and all was well. Decided to try to get the latest Cyanogen working and did not restore to stock first. Followed the Cyanogen wiki meaning I installed cwm5 recovery zImage using heimdall flash which appeared to work fine.

Now it is soft bricked - it sits on the Galaxy Tab boot screen.

If I hit power and voldown it will boot into what looks like clockwork recovery but I can't work out how to pick any of the menu items. I can move up and down the menu with the vol up/down buttons but no button seems to select anything. The bottom half of that screen says it can't find anything in /cache

I don't have a windows box, only linux or mac. So I can use heimdall but not odin.

I have a full Titanium Backup, but I did not write down the info about my device, so I don't know which stock firmware from samfire I should use. The tab was bought from Expansys GB, but appears to have started life somewhere in Eastern Europe even though it was all in English. It's running Gingerbread. Is there info in the Titanium Backup somewhere I can use? Even if I have to run strings on a file somewhere?

I don't have odin, so can I install GB-Stock-safe with heimdall? Is GB-Stock-Safe-v5.zip the right one?

Ideally I'd like to get my tablet back to absolute stock, then try again. Else at least get it working with something! Seems to me finding the right firmware on samfire would be a good start... But how?
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
Edit: maybe it is just your CWM that isn't working properly? have you tried using the soft button to select the items?

You can flash CWM again, maybe Overcome kernel (see my signature for new overcome link)

heimdall flash --kernel ./zImage

or even CM9 one (unpack the boot.img)

heimdall flash --kernel boot.img

Otherwise, restock using heimdall like below:

===================

I use Linux to restock all the time:

Use the same GB-stock-safe-v5 (see my signature for new overcome link)

but you need to unpack the rom to its individual file,

heimdall:

1) unpack the GB_Stock_Safe_v5.tar

2) go to download mode

3) heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage --modem ./modem.bin

4) at this point you can reboot to the stock rom.

(but I don't, I just go to download mode again)

when done,

5)unpack the overcome kernel 4.0 tar and you get another zImage

6) go to download mode

7) Flash that zImage

heimdall flash --kernel ./zImage

tab will reboot

- ignore the robotic voice, just force the tab to off

8) Boot into recovery and flash your latest CM.

9) then flash gapps

10) reboot and be greeted with the setup wizard
[Galaxy Tab Q&A, Help & Troubleshooting] RiderG:
Thanks heaps for the detailed information. It failed because I didn't have a modem.bin in the directory - should have read the command line more carefully.

Alas when I tried again with the JPZ one - which seems to be the one i want as far as I can tell from google I got the soft brick screen... that is the one with the outline of a phone and a PC and a ! between them.

I can't get it into download mode now. Just that screen. I've tried power on and vol up I've tried power on and vol down, with or without screen connection.

But then I decided... what if it will work anyway? That's what the various how to unbrick things say. Even if it doesn't say "downloading" maybe it will do so.

And it did!

at the end, it seemed to boot into clockwork recovery, and gave errors:

failed to mount /dbdata invalid argument

discard filesystem for rfs can;t mount /dbdata

cache wipe failed

can't open directory /preload/app no such file or directory

copy application failed

Installing multi-csc

can;t acccess to /system/csc/MKO/system

successfully appl;ied multi-csc

then it jsutr sat. I tried powering off, it got back into soemthignn like clockwork recovery saying "OK key to reboot"

Alas it's a tab, there is no OK key!

next step, try overcome.
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
for me I would do it in one go without booting into the OS at all.

heimdall flash the gb-stock-safe.

Finished, force off, force to download mode

heimdall flash overcome kernel.

Finished, force off (without waiting for the ROM to come up), force to CWM recovery

Flash ICS, flash gapps, reboot to ICS.

I have been doing these steps so many times.
[Galaxy Tab Q&A, Help & Troubleshooting] RiderG:
How are you flashing your ICS?

The instructions on the cynagenmod wiki assume you have the ability to put it on the root partition or are running rom manager.

So I get the cmw recovery and can't work out what to do next.

And now I can't get the recovery.... I can get download but once I've done the GB install then overcome flash only straight power on and poweron/voldown work, can't seem to force cwm recovery.
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
Put the files in sd card and choose to install from sd card. That is how I install mine.

Recovery from complete power off : hold volume up + power. Keep holding until Samsung logo appear, let go power only, keep holding volume up, until recovery appear then let go.
[Galaxy Tab Q&A, Help & Troubleshooting] RiderG:
Your patience is impressive and very welcome. I do appreciate you taking the time to help.

I downloaded cm-9.1.0-p1.zip via the cyanogen mod wiki page which seems to be the latest stable. MD5 sum correct both when downloaded and when copied to sd card.

I seem to have a black thumb for this thing.

I started again from scratch, so GB stock safe then overcome from 002001-Overcome_Kernel_v4.0.0.tar

I still can't get into recovery mode.

If I have a cable attached I just get a grey battery icon once I force power off then on after flashing overcome.

If I don't have a cable attached then when I boot from power off with volume up held on, if I take my finger off power when the logo appears I get the robotic voice and eventually an unusable recovery screen, where the vol up/down buttons work but the power button doesn't select. If I don't take my finger off power, it just powers off again.

If I let the robot voice go then eventually it boots to a screen saying android which then does nothing. If I use power and volume up, I get the unusable recovery screen not the proper one.

I once got a working recovery screen, but when I tried to install the cm zip from the external card it printed a couple of lines on the screen got a bit over a cm of brown progress line then rebooted right back into the recovery mode again except this time did not have the option to install from external card. And would not boot into anything else, just the recovery.

I tried reflashing GB and overcome, but the same sequence happens.

So it seems that maybe clockwork is trashed. So I reflash clockwork, then GB and overcome, but same sequence happens, can't get a good recovery screen.

If I reflash clockwork but don't do GB and overcome again I can get the recovery but the install from sd card fails with

installing update

assert failed getprop("ro.product,device) == "galaxytab" || getprop("ro.build,product") =="galaxytab" || getprop("ro.product,device") -== "GT-P1000" || getprop("ro.build,product") = "GT-P1000"

Now that all looks like I don't have the right cm for my device (a 3G box bought from Expansys UK) but various property files from titanium backup say

sys_ro.build.description=GT-P1000-user 2.3.3 GINGERBREAD XWJPE release-keys

and

sys_ro.product.model=GT-P1000

so the cm file is right. but it isn't finding the properties for some reason. Is that because this is a clockwork kernel flashed without me flashing the GB and overcome after it?

samfirmware.com doesn't have the XWJPE firmware but does have P1000XWJPJ_P1000OPSJP6_OPS.zip which is an Australian one, hopefully not locked to the carrier with its name on!

Is it worth trying to reset with that, then go through all this again?
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
OK, I think I tried to rush you.

Take one step at a time.

now, just GB stock safe and make sure the tab boots to GB ROM.

Post back, does that work fine.

Late here, check back with you tomorrow.
[Galaxy Tab Q&A, Help & Troubleshooting] RiderG:
Once more into the breach!

Gave it a few hours on the charger, then flashed GB and let it reboot, removing the cable as soon as flash done.

heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage --modem ./modem.bin

modem.bin used was from JPZ

Boots into a screen labelled Android system recovery <3e> which "doesn't work" meaning I can move between menu items with vol up/down but not select with power.

deleting /system/csc

successfully installed package.

updating filesystem

failed to mount /dbdata (Invalid argument)

discard filesystem for rfs can't mount /dbdata

wiping cache

formatting /cache

cache wipe failed

updating application

failed to mount /data (Invalid argument)

install application for customer Can't mount /data

your storage not prepared yet. Please use UI menu for format and reboot actions

copy application failed

appling Multi CSC

Installing Multi CSC

can't access to /system/csc/MKO/system/

successfully applied multi-CSC

Power off, power on, same screen but now it says MANUAL MODE and gives the same /dbdata, storage not prepared, and Multi-CSC errors as above.
[Galaxy Tab Q&A, Help & Troubleshooting] AndroidOS.FTW:
Soft Bricked T-Mobile Tab (Original) SGH-T849

Yeah, you read the model name right. That's a T849 or at least, that's what's printed on the back. This is a first release T-Mobile Tab. It was actually running the GB-Stock-Safe-v5 ROM for months and then just one day after a reboot, it kept looping and wouldn't recover. I popped it on the PC, fired up ODIN and performed the same ODIN flash process I've done dozens and dozens of times between various Vibrants, Tabs and SGS2s but, it never would recover.

I still have and tried flashing the Stock Safe v1 as well as the v5 TARs and PITs with no joy. If anyone out there has any ideas and preferably, working links to any suggested ODIN or other flash files (this device is so old that many links to files no longer work), I'm all ears (eyes).

Update: I've restructured the image placement and added a capture of the ODIN flashing, just so you could see, the flash seems to take just fine with no errors but, I still end up right back at the same Android system recovery <3e> screen, with the same error.

Here's a pic of the results from the latest attempt to flash back to the GB-Stock-Safe-v5 ROM. I'd really love to get this Tab back in play so, again, if anyone has suggestions.

Interestingly, I can perform a "wipe data/factory reset" from this menu and it appears successful, returning the following.

-- Wiping data...

Formatting /data...

Formatting /dbdata...

Formatting /cache...

Data wipe complete.

How can the formatting of /data succeed (no error indicated) if /data didn't mount as suggested by the error displayed? Just on a lark, I decided to give ODIN another shoot but, switch things up by using the Overcome Kernel vice the GB Stock Safe one. Everything was looking good, load went smooth and first reboot began the conversion process (I've loved hearing that sexy female robot voice since my first taste of TeamWhiskey) but, I was disappointed to hear her tell me "Convert data partition... Not enough space on partition"

That got me thinking and lead me to try something else. Heading back to ODIN I decided to try flashing just the GB Stock Safe PIT to see about resetting the partitions. PIT flashed fine, I immediately booted into CMW recovery and did a data/factory reset. That's when I saw this.

--Wiping data...

Formatting /data...

Error mounting /data!

Skipping format...

Formatting /cache...

Formatting /dbdata...

Formatting /sdcard/.android_secure...

Formatting /sdcard/android...

All User Data Wiped.

So, that leads me to think the internal storage is hosed in some way. Is it possible that ODIN isn't actually initiating a true format/repartition of the internal store even though no errors during the flash are indicated? Or is this an indication that the internal storage is simply corrupt? If corrupt, is there any way to recover?

My thanks to all who take the time to read these posts and offer their experience and knowledge to the community in an attempt to help those in need.
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
I actually own a T849 myself.

Maybe the NAND chip is failing as you said it just happen one day.

Anyway, this thread mentioned about flashing dbdata.rfs.tar using Odin

http://xdaforums.com/showthread.php?p=23348040#post23348040

try flashing the dbdata.rfs with heimdall

heimdall flash --dbdata ./dbdata.rfs

and see how it goes.

EDIT: Really sorry, I am looking into the heimdall parameters again

there should be a --dbdata and --hidden supported and GB-stock-safe has both

can you try: (with GB-stock-safe)

heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./dbdata.rfs --hidden ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage --modem ./modem.bin

EDIT2: Dont have to do that I tried to do the same mistake in my tab, I can confirm the same error, but then I ignore it.

I will just flash overcome kernel (untar to get zImage)

heimdall flash --kernel ./zImage

then boot yourself to recovery (Overcome CWM and flash ICS)

BTW, 3e recovery OK button is not POWER button, it is capacitive HOME button, but you won't use that recovery anyway.
[Galaxy Tab Q&A, Help & Troubleshooting] RiderG:
Same error as I had... and the command line I was using had the same problem so I tried adding dbdata.rfs and --hidden but this is what happened:

# heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./dbdata.rfs --hidden ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage --modem ./modem.bin

Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna

http://www.glassechidna.com.au

This software is provided free of charge. Copying and redistribution is

encouraged.

If you appreciate this software and you would like to support future

development please consider donating:

http://www.glassechidna.com.au/donate/

Initialising connection...

Detecting device...

Claiming interface...

Attempt failed. Detaching driver...

Claiming interface again...

Setting up interface...

Checking if protocol is initialised...

Protocol is not initialised.

Initialising protocol...

Handshaking with Loke...

Beginning session...

Session begun with device of type: 0

Uploading PIT

PIT upload successful

Uploading HIDDEN

100%

ERROR: Failed to confirm end of file transfer sequence!

HIDDEN upload failed!

Ending session...

Rebooting device...

Re-attaching kernel driver...

The hidden came from the GB_Stock_Safe_v5.tar file which is the same as the one in your sig link according to diff and md5sum.

But just to be sure... I unzipped the one from your link in another dir, untarred, copied the JPZ modem.bin to the untar directory ran it again. Same error.
[Galaxy Tab Q&A, Help & Troubleshooting] RiderG:
OK, so being a horribly impatient sort and realising Things Are Stuffed, I tried to flash the firmware from samfirmware.

It has the same stuff as the GB, except no dbdata. So I tried the same command line, removing the dbdata and changing file names as appropriate:

$ heimdall flash --repartition --pit ./P1_add_hidden.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --hidden ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage --modem ./modem.bin

Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna

http://www.glassechidna.com.au

This software is provided free of charge. Copying and redistribution is

encouraged.

If you appreciate this software and you would like to support future

development please consider donating:

http://www.glassechidna.com.au/donate/

Initialising connection...

Detecting device...

Claiming interface...

Attempt failed. Detaching driver...

Claiming interface again...

Setting up interface...

Checking if protocol is initialised...

Protocol is not initialised.

Initialising protocol...

Handshaking with Loke...

Beginning session...

Session begun with device of type: 0

Uploading PIT

PIT upload successful

Uploading HIDDEN

22%

ERROR: Failed to confirm end of file transfer sequence!

HIDDEN upload failed!

Ending session...

Rebooting device...

Re-attaching kernel driver...

Only got to 22% this time! Then booted to the Android System Recovery <3e> screen showing Manual Mode.

Maybe my copy of heimdall no good?

So off to the mac.

using a fresh GB safe zip, and the heimdall command line, same problem as tryng to do GB on the linux box. 100% hidden then the complaint about the end of transfer sequence.
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
Hi RiderG.

That was a bug in heimdall that keep resurfacing.

I now have the same error.

But read my message.

It doesn't matter that you get the error.

Now unpack the overcome kernel tar until you get a image.

Flash that using heimdall --kernel

Then boot into that cwm 5.x

Use that to flash the latest cm9/cm10 or aokp

Need to do it twice because of mtd conversion.

Then flash gapps immediately then reboot.

I just did it before I post my last edit.

Go try that.
[Galaxy Tab Q&A, Help & Troubleshooting] RiderG:
Aha! Did that, and once I realised that the 2nd time you pick "flash from internal SD card" even though it is the external SD card....

then the install worked.

I was scared it hadn't for a bit as the splash screen was up for a while but I managed to keep my fingers off the power button for long enough,

And it works!

Once again thanks heaps. It's people like you who make the world go around.
[Galaxy Tab Q&A, Help & Troubleshooting] AndroidOS.FTW:
Heimdall... isn't that a blimp that blew up? :P j/k

Post deleted. Comments merged with original post.
[Galaxy Tab Q&A, Help & Troubleshooting] priyana:
Don't like the way you "ninja" your post since you are the not the OP, it is not easy to find the original post.

But yeah, it does sounds a bit like hosed memory. the failed movinand and all.

One shot you get is by accessing CWM and flash CM9 for example.

It has different partition scheme, maybe it will somehow get around the bad block, but I am a bit sceptical about that too.

After that, of course there is the "Fix Damaged Internal SD" thread and the "External SD only thread"

for the brave hearts.