[Galaxy Tab  Android Development] Jarmezrocks:
Hi everyone,

I wouldn't really call myself a developer, but I am part of a team of developers (well was - we have all got so busy in life at the moment so Android developments have slowed down a fair bit) anyway I am not currently employed so I have been doing a fair amount of phone work for a local Phone repair shop here on the Gold Coast. I met the guy when I went in to my friends computer store to get PC parts and this guy's phone store conjoins. Anyway I made mention that I can fix software on Android devices. He said that he didn't do software, my reaction was "So what you just let all that business walk out the door then?" he laughed "I suppose so". Anyway one thing lead to another and i had a phone I needed to try unlock. I wasn't actually successful with that one, but I did manage to revive the corrupt IMEI and he seemed pretty impressed by that. I got a call saying he had a Galaxy Tab for me to try get working again. So here I am :)

Initially I DID get it running (only for a while) on stock Gingerbread from the Restock Overcome ROM thread here, so a big thanks to @AdamOutler, @priyana, @Alterbridge86 and @ApriliaM3 for their ongoing efforts to date with supporting the P1000 TAB.

So why am I uploading a new Re-Stock? What's all this about?

Tell tell you the truth plain and simply the well known and famous "GB_Stock_Safe_v5.tar" did not work for me. I was not satisfied that this was a hardware fault either, something was telling me there was some underlying issue that had not been dealt with. Most other people, simply flash gt-p1000_mr.pit, GB_Stock_Safe_v5.tar, and JK3 Modem and they are good to go. For me I had the most unstable device I had ever worked with. Random reboots. Constant bootloops, in among every 10 reboots occasionally I reached the homescreen :victory: if I was lucky I could maybe open an app or two and apply some settings but soon as the screen locked or I left the tab for any length of time I came back to a revolving boot screen :rolleyes: If you want to know if this is you and if what I went through is what you are experiencing then read more here >>> Tab reboots before BML/MTD can even get started. Then no recovery

There is a solution!

Download

GB_Stock_AUST_Jarmezrocks+P1.pit.zip

Mirror

GB_Stock_AUST_Jarmezrocks+P1.pit.zip

Contains the following:

GB_Stock_AUST_Jarmezrocks.tar

P1_add_hidden.pit

P1_add_hidden.pit came from the stock Australian Optus Firmware P1000XWJU6_P1000OPSJU3_P1000XXJR2_HOME.tar.md5

Oddly enough this firmware DID NOT work on this Tab? The Restock base was as close as I got and it was ridiculous and unusable.

Each time I flashed this firmware ^^^ with Odin the Tab would switch off as it was applying cache or hidden and then was Bricked. Luckly Adam developed Heimdall OneClick Unbrick. I would say in the last week I have easily bricked this Tab maybe 30 or 40 times, I was determined to not let this beat me. There had to be an answer?

I pulled apart the firmwares and pretty much went with my gut instincts. Here is the run down:

The PIT

The difference between P1_add_hidden.pit and gt-p1000_mr.pit have hidden and cache partitions switched as far as I can see? Naturally in the Optus firmware the Hidden partition is just oversized and most likely full of bloat/cr@p in other words. I included the P1 pit in the firmware build because it was in the original. I am not sure of this does anything extra, but figured it can't hurt anyway (even though people are freaked out about pit files) seeming we re-partition when Re-stocking GB anyway.

dbdata

I knew that dbdata is important especially if we have oblitorated the data partition and made a fair mess of everything. I think this is the most importance file besides the pit when we need to return to stock.

movinand

Movinand was included because when I inspected the P1 pit it had an allocation for it. There was maybe a chance that when not all partitions in the structure are written to I could provide a weekness or void for data to "overflow" so to speak. I think of partitions like dividers in fishtanks as an analogy.I bred fish and I know what happens to the structure of large tanks with partitions if adjacent tanks are filled and one left empty; it creates weakness. Anyway I decided to fill it, at least for the flashing part where data and structure are being formed by bytes of information.

cache

cache I decided to go with the larger stock firmware mainly because I think part of the issue with the Tab its self is a lack of cache (causing the instability first noted).

hidden

Need I say more? Look at the size of the stock Aust firmware

modem.bin, ZImage, boot.bin, factory.rfs

I spose I chose to stick with stock so that if that was where the tablet was staying that it looked as though it had matching firmware when looking in 'About divice' and the modem for connection specific to the carrier and region, nothing more than that really.

param.lfs

Now this part I wasn't sure about? Maybe I should have gone with the smaller one? I don't know.....they were not worlds apart in difference anyway, and really by that stage I just wanted to flash the darn thing and see if it worked! :laugh:

Result. 100% smooth boot. Device rebuilt dalvik in a reasonable time (I weigh it up close to the specs on my Galaxy S1); a few force closes when reaching the home screen but they are kind of expected considering the device age and specs. Within about 15 min and 1 reboot into recovery to "re-fix permissions" (which seemed to stabilise it for some reason?) and then no more force closes, device operated perfectly! Smooth, no glitches no random reboots. Man I was sooooo happy!!!:victory:

As per the instructions I went on to faultlessly perform the upgrade to Overcome Kernel, CM9 (BML/MTD), it rebooted once as expected to change kernel and recovery, then continued all the way through to completion. I then remounted the partitions (wow this seems to be a really big issue with the P1000 doesn't it? Why is it that nearly every boot into recovery leads to half or more partitions left unmounted? - Note it doesn't boot unless you mount the damn things!) anyway I cleared caches(note clearing caches happened far too fast so that is how I noticed the partitions were not mounted), factory reset and reset permissions! (THIS PART IS IMPORTANT ON THE P1000!!!)

I rebooted; it took several reboots and rebuilding of the dalvik caches before it would reach the home screen. I think something like 28 apps got split up into about 3 or 4 reboots (which did it's self) and I was worried again that I had another unstable device, but figured it was a bit uneasy on her feet in GB, and maybe JB was similar....so I rebooted, fixed permissions again and rebooted. Sure enough perfect!! Device is still running faultlessly. I will proceed to theme it, and add a few "nice touches" before it is returned to the owner tomorrow.

To fill in the blanks of the story when I got given the Tab I could see someone had messed with it already. When I told the guy initially the next day that I got it working albeit rather unstable though his reaction was priceless! He goes "You what? You got it going? How the f#*% did you manage that? Man 5 different phone shops have looked at that and probably at least another 5 other tech geeks that all know a fair bit about phones & tablets. None of them got it to work!" he continued "Do you know that thing has not been touched for at least a year and half!"

So it was a big test really. I didn't know this till about an hour ago when he saw that I had it all running:laugh::laugh::laugh: Guess I passed then eh?:cool:

XDA:DevDB Information

*NEW* GB Re-Stock Safe for Australian P1000 Tabs where GB_Stock, ROM for the Samsung Galaxy Note 10.1

Contributors

Jarmezrocks

ROM Firmware Required: For Bricked Devices

Based On: GB_Safe_Stock_v5

Version Information

Status: Stable

Current Stable Version: v1.0

Stable Release Date: 2014-05-22

Created 2014-05-22

Last Updated 2014-07-09