1. KarlsenMk's Avatar
    Hello everyone.
    I have a Galaxy Tab GT-P1000. It's worked perfect until this morning.
    When i woke up, i heard the sound of it turning itself on and off again, so i plugged it in the charger and left for work.
    Came home from work, and its still doing it. The battery is now fully charged.

    It starts up. The Galaxy Tab logo shows for about 5 seconds, and then it turns itself off again, before it automatically turns itself back on. Endless circle, that i can not stop.
    When i try to do a soft reboot, nothing happens, and it keeps turning itself on and off again.
    When i try to do a hard reboot, it shows the hard reboot screen for about 1 second, then turns itself on and off again.

    Kinda lost for ideas here. Please help.
    10-24-2013 05:42 PM
  2. keifusrahn's Avatar
    Is it rooted and have you flashed a custom rom? the only reason im asking is It sounds like a classic case of bootloop.
    10-24-2013 07:11 PM
  3. KarlsenMk's Avatar
    It has not been tampered with whatsoever. Everything is factory. Charger is factory too. Yes, you are spot on about the bootloop
    10-24-2013 07:35 PM
  4. keifusrahn's Avatar
    You can try my guide Guide For [BOOTLOOP RECOVERY] Noob Friendly - xda-developers And see if you can get it back going but sence it hasn't been tampered with and is still under warranty I would go that route Samsung. If its not under warrinty you can try my guide or try this.

    The main pointer to an Internal SDCard Failure is the inability to flash hidden.rfs and movinand.mst
    You should be able to confirm this to be the case by running dmesg on the device using adb from the command prompt of your computer

    If you were luckly enough to have left USB Debbugging on than you should be able the run the following command
    while the device is booting loop otherwise run it ) while you are in recovery
    adb shell "dmesg | grep mmc0"

    My output contained the following line:
    <3>[ 4.802004] mmc0: error -110 whilst initialising MMC card

    Another way to check is to use adb to view the devices file system.
    adb shell "ls /dev/block"

    Do this WITHOUT an external sdcard.
    Any Reference to mmcblk will be missing.

    Normally you should be able to RMA this as it is an hardware failure.
    However as warranties expire or you just can't be bothered to wait here is an alternative solution

    The Solution is fairly straight forward, However It's not a repair and it is not possible to recover any data from the Internal memory.
    So You've lost your Angry Birds Hi-Score forever.

    That's the bad news. The Good News is, You've still got what will soon be a working Tablet again and a chance to get an even higher score.

    Note: The Following description maybe considered by some as a little heavy on Technical Details.
    Unfortunately. we are taking advantage of how the Linux Kernel Interacts with hardware ports and how the linux sysfs Virtual filesystem works, It's the nature of the beast I'm afraid

    The Solution

    In one sentence. We will use the external SD Card to store and load The Android OS.

    How Do You Plan to pull that trick off?
    This is made possible because of how the Linux kernel manages and addresses devices of the same type. Linux gives each device a number which increments by 1 each time.
    The Hardware can control what Linux Sees. I.E the Internal Memory is always loaded first and given and index of 0 [ remember computers : Start Countong a zero ]
    After trying and failing to access from the internal sdcard the Kernel quite sensibly looks for the first functioning SDCard on the System and creates it in the /dev tree with a index of zero for that Class of device. It just so happends that the first (and only) Sdcard on the System is now physically located in the external SDCard Slot.

    So What Now?
    Now we have to play nice with whatever rom is on the device. which means providing the number of partitions that the rom expects. In my case It was 3.
    So go ahead ad format and parition your SDCard.
    There is nothing to stop you having more than the base amount with what ever file systems you please as long as the Kernel Can provide a mount point to the device than You're laughing.

    This Partition Below table was suitabke for UK Roms. The Fat32 Partition is what will appear when the device is connected to Windows as a disk drive.
    From what I recall that is the only reason for having a fat filesystem on the Card. So If you're a Linux Junkie then You should be able to pick what Filesystem is good for you. Format the external sdcard with 3 parititions (you can probably get away with 2) I used a 32 GB card with the follwing

    Partition 1: 28 GB Fat 32 (sdcard partition)
    Partition 2: 4 GB ext4 (data partition)
    Partition 3: 100MB Fat 32 (preload partition)
    I Used Heimdall for this and I flashed everything. Odin should do the Job as long you remove hidden.rfs and movinand.mst from the tar balls

    heimdall flash --repartition --pit gt-p1000_mr.pit --primary-boot boot.bin \
    --cache cache.rfs \
    --factoryfs factoryfs.rfs --modem modem.bin \
    --param param.lfs \
    --secondary-boot Sbl.bin \
    --kernel zImage --recovery zImage
    After That I Flash a custom kernel which If memory serves enabled the CWM Recovery. The Kernel I used was
    one from Team Overcome Kernel 4 which can be downloaded from the teamovercome download page
    The choice of kernel isn't any endorsement........ Actully I will say. Use Team Overcome Kernel. It Works!
    Seriously any custom kernel should do the trick and In Theory even a stock kernel could be make to work [See Notes]

    Boot To Recovery ( You should now see Clockwork Recovery Mod )
    edit /system/etc/vold.fstab on the device to look like the following. You can use the adb pull command if you are unsure how to get at the file.

    Linux and Windows use different newline characters. If you are editing the file on windows make sure you are using an editor suitable for the task (i.e UltraEdit or Notepad++)

    # internal sdcard

    ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
    asec = disable
    discard = disable
    format_option = -r 1558
    dev_mount sdcard /mnt/sdcard 1 /devices/platform/s3c-sdhci.2/mmc_host/mmc1

    # externel sdcard
    ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
    asec = enable
    dev_mount sdcard /mnt/sdcard/external_sd auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2 /devices/platform/s3c-sdhci.2/mmc_host/mmc1
    One final Reboot should make your Still broken but functioning tablet a little less a bitter pill to swallow (see what I did there)

    Note: First boot takes a while. if you are worried or think it is boot looping, you can watch the output using adb logcat
    You should now have a working galaxy with the added bonus of a re-sizable data partition.

    Tool List:
    A Micro SD Card - The Bigger The Better , Size and Speed are everrything as this is where you everything pm your tablet will live. I would definitely pitch for a 32GB Class 10.
    A Method of formatting and Partitioning the SDCard. - If your a windows user than you need a method of formatting ext4 partitions. I 'm unsure of the current state if the art regarding that.
    A Custom Recovery Image. Clockwork Recovery Mod or something similiar. You can use fasboot from the android sdk to flash it to you device
    A Custom Kernel Image. with support for the Ext 4and Fat32 Filesystems.
    The Next Step Is To Flash A Rom to the devoce . You Should be able to flash any rom to it as long as Your sdcard Is formatted correctly
    I Flash Latest Stock Rom at the time and

    [Advanced User and Mashoist's]

    You Can use you own custom recovery and kernel if you are so Inclined.

    For Extra "Going To Try This Because It's There! an I can" Points
    Retain A full Stock Experience. When Booting From SD.

    It Should be Possible, If can find a way to format the sdcard partitions to Samsung Proprietary RFS File System.
    This was also the reason a custom kernel was used ;
    10-26-2013 12:00 PM
  5. Gerlongs's Avatar
    Hi! I have my Samsung Galaxy Tab P1000... It is still running on android FROYO 2.2. How can I upgrade it to the latest version, Jellybean? and by the way, my tablet is not rooted... hoping for reply...
    11-22-2013 12:51 PM
  6. Kaushik Pathak's Avatar
    me 2ooo...I am also willing to give you money to get this updated. the device itself is outdated and now there is no question about the warranty.... so guys please help me out...
    i have also heard that if swap memory is increased the device performance extends to great!! so also please do mention steps properly...

    I have also tried to follow the steps that are provided all over the internet and ended in a huge flop... went to samsung store and they upgraded my device to 2.3 thats it... not even jelly bean!! took 800 buks.... I am willing to take risk again if and only if a reliable source help me out!
    11-24-2013 02:54 AM
  7. Sumeet Saini's Avatar

    follow this to upgrade

    its the best so far
    12-29-2013 09:34 AM

Similar Threads

  1. Samsung Galaxy S3 hardly holds a charge?
    By JakeTheGiratina1 in forum Sprint Galaxy S III
    Replies: 6
    Last Post: 06-09-2015, 05:53 PM
  2. Android File Transfer doesn't work on Mac Mavericks
    By Arelunde in forum Droid RAZR MAXX HD
    Replies: 24
    Last Post: 06-10-2014, 06:26 AM
  3. Cabdy crush crashes on exit.
    By phatdonkey in forum Samsung Galaxy Note 3
    Replies: 5
    Last Post: 11-01-2013, 12:34 AM
  4. Will tab 3 8.0 update to 4.3.3 and above????
    By Nychotxxx in forum Samsung Galaxy Tab 3
    Replies: 4
    Last Post: 10-31-2013, 04:36 PM
  5. Anyone get MailDroid notifications to show up on the Gear?
    By rishman1 in forum Samsung Galaxy Gear
    Replies: 0
    Last Post: 10-24-2013, 04:32 PM