Database Develop

Rom

Seen an alpha 3 ICS rom. Can I just download that and flash it over my current rom or does it habecto be done certain way. I've flashed before on my evo but this seems a little bit more complicated
Sent from my SPH-P100 using XDA App

I'd rather go the full procedure they describe within their thread - imho especially you have needs for clockworkmod. Found that to be a quite safe way for me.

I would I just don't have access to a pc. Does ICS run fine on your tablet. Is it worth it
Sent from my SPH-P100 using XDA App

Once you have CWM Recovery installed, getting the ICS Alpha on your tab is not difficult if it's listed as supported in the thread.
Only thing: This is an ALPHA build. That means many things are not functional. The build is aimed at developers/testers.
Having given a shot at it, this build is surely not a daily driver for someone who needs its tab to be functional and reliable. Many of those problems have work arounds however but since the tablet is not mostly used by myself, I did not take the risk of having it be unreliable...
In short: it should work and not eat your hamster... But it is not a fully functional rom yet, be prepared for some trouble... Be sure you know how to go back in case of trouble... and read instructions carefully

If you want a good ICS rom here ya go. FYI!!! THIS IS FOR CDMA TABS!!!
Get rooted and CWM'd via Rodderick's thread in our Development section.
From there do the following (all credit to JT from here on out)
Download http://k.22aaf3.com/jt1134/vzwtab/cwm-recovery-5.0.2.7.tar
Extract the contents. You will have two files zImage and recovery.bin
Odin these two files to your tab while your tab is plugged in to the PC and in Download mode. This will bring your clockworkmod up to 5.0.2.7 which is a must to install the rom I'm about to link.
Next go to this thread
http://rootzwiki.com/topic/11697-rom-cdma-aosp-ics-cm9-build-31-0104-x-2/
At the bottom of the first post download the 3.1 ROM the 3.1 Patch and the gapps files.
Once those are downloaded boot your tab up to normal operations and plug it into your PC again. Now transfer those three files to your tab.
Boot up into clockwork recovery wipe the cache, dalvik, and do a factory data reset. Then flash the 3.1 file first, then flash the 3.1 Patch, then flash the gapps files.
If everything says it installed correctly the only things that won't be working are camera (which it does work in panorama mode) and possibly 3G. (Never tested 3G as I only use wifi).

Can you please post pictures and how can I check which cwm I already have? If I already have 5.0 can I just go ahead and flash? One more thing is this a whole new ICS or the ones going around. Thank you much

So I checked and I got 4.0 cwm. With that said. I don't have access to a pc. Is there any other way to upgrade to 5.0 cwm? PLEASE someone reply with yes. I'm getting bored with this andcwpuld like to try ICS. Thanks

rjumawan said:
So I checked and I got 4.0 cwm. With that said. I don't have access to a pc. Is there any other way to upgrade to 5.0 cwm? PLEASE someone reply with yes. I'm getting bored with this andcwpuld like to try ICS. Thanks
Click to expand...
Click to collapse
Without access to a PC I think you are making life very difficult for yourself.
You do not state what Tab you have; below I linked to the install for the P1010 only...I did this for reference because you will see it required Odin to flash it i.e. access to a PC.
http://forum.xda-developers.com/showpost.php?p=20195348&postcount=1

Thank for the reply. Yeah I know it makes it, harder just seeing if there was a way around it. I'm playing with the sprint galaxy tab. Not much to play with out there for it.

Really need help please. From 2.3.4 to Slim ICS

Thought I wasnt such a noob but appearantly I am.
Went from stock 2.1 on Captivate to Serendipity 5.x then later to 6.0, 6.1, 6.2, 6.3, 6.4 No hickups, havn't messed with it since. Finally decided to upgrade to slim ICS.
after a ton of hickups, finally got CM7 on the phone just to get stuck in a bootloop. Tried wipes (Dalvik, system, cache) as recommended on forums and got stuck on splashscreen. After trying tons of stuff ended up with stock 2.3.4. , which is now rooted. and after scouring the forums have no idea where to go from here.
I tried Rom Manager & RM Premium (I selected i9000 as I am guessing that is the corrrect one for captivate) to get CWM but the CWM flash install failed, so I just refunded it
Where am I now?
Rooted stock 2.3.4.
Kernel ver.- 2.6.35.7-I987UCKH3-CL461307
Build Number- Gingerbread.UCKH3
Odin won't see my phone
I have no CWM Recovery (looks like stock samsung recovery)
Where should I go from here?

bimbim18 said:
Thought I wasnt such a noob but appearantly I am.
Went from stock 2.1 on Captivate to Serendipity 5.x then later to 6.0, 6.1, 6.2, 6.3, 6.4 No hickups, havn't messed with it since. Finally decided to upgrade to slim ICS.
after a ton of hickups, finally got CM7 on the phone just to get stuck in a bootloop. Tried wipes (Dalvik, system, cache) as recommended on forums and got stuck on splashscreen. After trying tons of stuff ended up with stock 2.3.4. , which is now rooted. and after scouring the forums have no idea where to go from here.
I tried Rom Manager & RM Premium (I selected i9000 as I am guessing that is the corrrect one for captivate) to get CWM but the CWM flash install failed, so I just refunded it
Where am I now?
Rooted stock 2.3.4.
Kernel ver.- 2.6.35.7-I987UCKH3-CL461307
Build Number- Gingerbread.UCKH3
Odin won't see my phone
I have no CWM Recovery (looks like stock samsung recovery)
Where should I go from here?
Click to expand...
Click to collapse
try to install drivers again and first open odin after that connect device then odin will recognize the device

Im about to try ICS on my cappy. Im on GB 2.3.5. I will try slim or Turk's V5. However, if I dont like it, would a simple one click ODIN bring me back to GB easily? or is there more to it (because of kernals, or do a double flashing, etc etc)
Thanks

dhlalit11 said:
try to install drivers again and first open odin after that connect device then odin will recognize the device
Click to expand...
Click to collapse
I'll try that, to get CWM , just a flash of Boog's KH3 should work correct?

bimbim18 said:
Odin won't see my phone
I have no CWM Recovery (looks like stock samsung recovery)
Where should I go from here?
Click to expand...
Click to collapse
Depending on how you ended up at 2.3.4, you may need different drivers in order for Odin to see your phone.
I used Heimdall after an unsuccessful update from Slim 2.7 to 2.8 and had to use Heimdall to get out of a similar bootloop. It left me without CWM and a computer that cannot detect my phone.
Since Heimdall worked but I knew I needed CWM, I found a Heimdall package from Apex that contained CWM (post #3, http://forum.xda-developers.com/showthread.php?t=1300843).
Not sure this address your needs but hopefully it will help

captican said:
Depending on how you ended up at 2.3.4, you may need different drivers in order for Odin to see your phone.
I used Heimdall after an unsuccessful update from Slim 2.7 to 2.8 and had to use Heimdall to get out of a similar bootloop. It left me without CWM and a computer that cannot detect my phone.
Since Heimdall worked but I knew I needed CWM, I found a Heimdall package from Apex that contained CWM (post #3, http://forum.xda-developers.com/showthread.php?t=1300843).
Not sure this address your needs but hopefully it will help
Click to expand...
Click to collapse
actually I think Heimdall was what actually got my phone working again, I'll go with that. thanks. what driver did you end up using if you remember? I probably need the same one

bimbim18 said:
actually I think Heimdall was what actually got my phone working again, I'll go with that. thanks. what driver did you end up using if you remember? I probably need the same one
Click to expand...
Click to collapse
This is where I found it:http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
Once you open the package, it flashes the ROM the first time through and then gives you the option of flashing gingerbread bootloaders on a second flash. I did not flash bootloaders since I was already on gb. The ROM itself, Apex 12.4, is actually pretty good.
Based on my experiences recently, ending the bootloop, solving a softbrick, and upgrading to CWM (thanks AdamOutler!, I actually am less nervous about using Heimdall than I am Odin but it just does not seem to be as popular as Odin. The major drawback of Heimdall is the different drivers.
Good luck.

OMG i got the biggest scare, after attempting to flash the kernel it got stuck in the 'establishing connection' stage. After 30 mins I pulled the plug to make another attempt. I got a screen I have never seen before:
had a computer and a phone pic with big yellow letters:
"Upgrade attempt Failed. Try recovery mode"
no problem. Hold volume buttons, power on.... same screen. 3 times same thing. OK no problem lets try download mode, same thing. After some googling I finally found a similar poster that basically said the screen actually serves AS a download mode, and that he tried 6 times before the flash took. I got mine after 3 more attempts.
Tried to flash slimICS from there, failed and aborted..
So, from here I guess it is mandatory to flash CM7? or do i have to go to 2.3.5 first?

bimbim18 said:
OMG i got the biggest scare, after attempting to flash the kernel it got stuck in the 'establishing connection' stage. After 30 mins I pulled the plug to make another attempt. I got a screen I have never seen before:
had a computer and a phone pic with big yellow letters:
"Upgrade attempt Failed. Try recovery mode"
no problem. Hold volume buttons, power on.... same screen. 3 times same thing. OK no problem lets try download mode, same thing. After some googling I finally found a similar poster that basically said the screen actually serves AS a download mode, and that he tried 6 times before the flash took. I got mine after 3 more attempts.
Tried to flash slimICS from there, failed and aborted..
So, from here I guess it is mandatory to flash CM7? or do i have to go to 2.3.5 first?
Click to expand...
Click to collapse
I cannot answer that question about needing CM7 or 2.3.5.
I know that I went to Slim ICS from Fusion ICS without any problems. The procedure for Fusion seemed tailored to their ROM (http://forum.xda-developers.com/showthread.php?t=1233979). I remember being a little nervous about "pull battery at android and triangle screen..." but it worked out fine.
I have to decide whether or not to go the Fusion route or this way (http://forum.xda-developers.com/showpost.php?p=22335637&postcount=10).

OK, I finally got it installed, OMG it's amazing ^^
To answer my own questions for anyone else it may help.
No, you don't need to go to 2.3.5. I just went to CM7 (build 16) and that gave me the rest of the updates I needed to jump to slim ICS 2.8
Thank you for all your help !
..now to spend the next week going through settings lol

bimbim18 said:
OK, I finally got it installed, OMG it's amazing ^^
To answer my own questions for anyone else it may help.
No, you don't need to go to 2.3.5. I just went to CM7 (build 16) and that gave me the rest of the updates I needed to jump to slim ICS 2.8
Thank you for all your help !
..now to spend the next week going through settings lol
Click to expand...
Click to collapse
Just wait until you discover the addiction of trying a new ROM. Because it "might"be better, or faster, or have cool options or themes... ...... ..... aaaaahhhhh I needed help!!
Sent from my GT-I897 using xda premium

shaker2k said:
Just wait until you discover the addiction of trying a new ROM. Because it "might"be better, or faster, or have cool options or themes... ...... ..... aaaaahhhhh I needed help!!
Sent from my GT-I897 using xda premium
Click to expand...
Click to collapse
I am not the one who has a problem with this. My wife, on the other hand...

bimbim18 said:
OK, I finally got it installed, OMG it's amazing ^^
To answer my own questions for anyone else it may help.
No, you don't need to go to 2.3.5. I just went to CM7 (build 16) and that gave me the rest of the updates I needed to jump to slim ICS 2.8
Thank you for all your help !
..now to spend the next week going through settings lol
Click to expand...
Click to collapse
If you had read my instructions, would hav e been simpler. It said, coming from GB rom, flash TeamHacksung build 16, then mine. done.

[Q] Installing ICS from CM7.2?

Hi,
Sorry if this seems like a dumb question - A bit confused from reading up all the info on upgrading to ICS on the p990.
Im running a volk custom kernel, and CM 7.2 - OS Version 2.3.7.
Whats the "best" way to upgrade to the new ICS? I tried running the LG software update but it doesnt go too well, fails after it tries to detect phone - even though it detects it initially.
Can I get the release that LG released with my setup?
Please advise.
Thanks!

Same situation here. I'm on official cm7.2 and would like to upgrade to ics. But don't think that useing official lg update tool is so good idea - it might brick your phone. It won't update to ics because you aren't running the official GB rom so lg update tool won't upgrade (correct me if i'm wrong).
Maybe the AIO tool would do the trick.
Anyways, people we need your advice!

LOL, use NVflash ICS rom like TG.

for me the best way is using the toolkit to install new partition, new bootloader and recovery
than boot into recovery and flash the room as usual

Thanks Wakata.
Much appreciated. I have tried downloading the toolkit but its always corrupt.. ill download the 7 zip format.
I take it that I will need to back everything up and wipe everything, install new partition, boot loadder and recovery(CWM??), then flash with the new rom and kernel?

I've also used the All-In-One P990-Toolkit to upgrade to ICS.
You can use 1. to backup your internal SD in case you need it later.
Then hit 4. to change the partition layout and after that 8. to flash the new unlocked bootloader. That's all.

Thanks again
Slight problem - I downloaded the 7z file, and extracted them, but cant seem to run the .cmd file? What am i doing wrong here?

scratch that last question.. for some reason the files are corrupt when i download them.. grrrr.

So I followed the instructions, and suprise suprise, I get an error -
Nvflash started
nvflash configuration file error: file not found
An error occured. Read above lines for details
Help please

Nevermind, I had a fiddle and flashed ics 6.0.xxx.. lets see how it goes. Hopefully I havent bricked it lol

Sorry, problem.
I first tried option 1, then 4, then 8.. after its all done, no errors - I boot the phone, and its stuck on the red LG logo.. I've left it there for around 10-15 mins with no luck? Help!

Haha, actually I figured it out. I did realise I didnt have a ROM! Doh! lol rookie mistake.
I downloaded this rom and kernel(1.4ghz OC) and its running pretty well, no bugs so far(touch wood)

Issues With Touchpad

Hello, I have had a touchpad for some time and but CM9 and CWM on it some time ago, but it started having some issues recently. So I figured I should try and reinstall a newer version of CM and start from scratch.
I went to this post http://forum.xda-developers.com/showthread.php?t=2026692 and downloaded both the skz+tenderloin-1.10.zip and the gapps zip.
I then placed those into the Download folder on the touchpad.
This is where things took a turn. I rebooted to get into CWM, upon selecting it from the boot menu it kept restarting back to the boot menu. After a few tries it got into CWM. I then wiped the data and did a factory reset, wiped the cache, and then wiped the dalvik like the post said to do. I then went to install zip from sdcard. Found the skz+tenderloin zip and chose to install that. CWM says it starts to install but then before the progress bar fills up at all...it resets back to the bootloader.
At this point I am at a loss with what to do and I would really appreciate any help I can get with this.
UPDATE: I figured starting from scratch would be the best bet, so I have uninstalled CM9 and CWM using ACMEUninstall. Now I am wondering if it is worth using CM10 as my default Android or should I stick with the best CM9.
Either way, if I should use CM9 or 10 can someone either help me or point me in the right direction for the best tutorial on doing this properly?

Restore a backup then DL an updated version of CM9 to flash or upgrade to ACMEInstaller3 to give you a larger system partition along with the latest version of CWM in order to install a CM10 rom apart from oats which does not require the extra space .
There are numerous guides and you should probably read up on a little bit before just flashing a rom to avoid the problems you are having .

sstar said:
Restore a backup then DL an updated version of CM9 to flash or upgrade to ACMEInstaller3 to give you a larger system partition along with the latest version of CWM in order to install a CM10 rom apart from oats which does not require the extra space .
There are numerous guides and you should probably read up on a little bit before just flashing a rom to avoid the problems you are having .
Click to expand...
Click to collapse
The issue I am encountering is there is a ton of info out there, some outdated some not. I restored back to stock webOS with nothing else. I have ACMEInstaller 3 in the Palm directory, so I am ready to install the most stable/best CM9 currently out there, I just don't know which tutorial is the best one to follow. Could you perhaps just link me to one you recommend?

http://rootzwiki.com/topic/31548-ho...-with-sound-camera-microphone-updated-232013/

Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.

Saix_XIII said:
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Click to expand...
Click to collapse
I installed CM9 based on the link above with the AIO package. It worked flawlessly, hopefully my freezing/restarting issues happen less often now. Thanks to all who offered help.

Saix_XIII said:
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Click to expand...
Click to collapse
I can tell you that I use my Schizoid as my daily driver, and it's not a preview.

Tab reboots before BML/MTD can even get started. Then no recovery

Ok guys,
I am not new to Android but this is really really starting to give me the sh!ts. I have no f#*%ing idea how many times I have gone and restocked this POS tab.
I follow the guide to a T for Overcome etc etc. I know all that.
I can flash CM10 through recovery from there and it completes oddly enough. However it does not boot at all. I have done this maybe 10 times. No boot. Just constant re-install of the kernel and Cyangen Bootanimation. I also have no recovery as soon as that happens and then I have to start ALL OVER AGAIN!!!!
Ok so I decide to try CM 9.1.0 stable. Surely this will allow something. Guess what? It doesn't even install. YES I have removed the lines from the updater script. I mean how stupid. If you don't even have a system for a getprop to querey of course it is going to fail.
Remove the lines, gets to BML/MTP and starts to process for maybe about 10-15 seconds and then reboots and becomes a brick
What in gods name am I missing here that isn't in the million and 1 guides I have already read and the conflicting opinions of people say 'flash CM10 straight after Overccome kernel' and 'No no no you need to be onn CM9 first' and I have even read 'No you need to flash CM7 first then from there you can flash CM10'
Like WTF?
Cant there just be a 100% true guide. For starters Overcome ROM guide only gets you to there, nothing more. There is no steps in between. There are only guides that assume that you have done the steps to get to Overcome ROM.
I am about to scour the internet now and see if I can find CM7 cause I am sick to death of restocking and starting from scratch on this stupid POS. I mean FFS I thought that this would be straight forward like when I updated my i9000 Galaxy S to ICS, but noooooooo nothing I have done gets the results of what people claim in the guides.

These are my steps
Odin
PIT = gt-p1000_mr.pit
PDA = GB_Stock_Safe_v5.tar
Modem = modem.bin (JK3 as per the guide)
reboot download - it does boot otherwise
Odin
PDA = CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
reboots into Gingerbread
reboot download again
Odin
PDA = Overcome_Kernel_v4.0.0.tar
Sexy voice does her sh!t (I thought that this was where we did BML to MTD but it's not its rfs to ext4 - thought I'd add that for anyone that has in the past like me had experience with doing this stuff before and needs a refresher).
Reboot into recovery and from here is anybodys guess?
I need the EXACT EXPLICIT DETAILS FROM THIS POINT!
Everything I try from here completely messes the P1000 and I have to start again.
CM10 - Flashes but doesn't boot - recovery updates but flashing anything else obviously kills it and I start again
Overcome ROM wipe - Flashes but exists the script before completing
CM9.1.0 - Flashes, gets to BML/MTD and quits - note Recovery is completely screwed after this point
CM7 - Yes I am about to try this. Please tell me why this is wrong and explain and I will listen. Please also advise all the other people out there with guides that are wrong to update them and include the important details that they have overlooked for people like myself.
Thanks

Overcome kernel converts rfs to ext4 but still in BML.
When you flash cm9 or cm10, flash it 3 times.
That is by selecting the zip. Flash it, it reboots to recovery (a new recovery, no longer overcome).
Flash zip again. Now it converts to MTD. It then reboots to recovery. (Many people think it is bootlooping. )
At this point flash zip again. Now it does the longer install.
Screen says a lot of thing about /system and stuff.
Let it finish and reboot to cm.
The weakness of most guides is that they never say 3 times.
The noobs thinks it is a bootloop without reading what the recovery is doing.
Sent from my GT-N7100 using xda app-developers app

priyana said:
Overcome kernel converts rfs to ext4 but still in BML.
When you flash cm9 or cm10, flash it 3 times.
That is by selecting the zip. Flash it, it reboots to recovery (a new recovery, no longer overcome).
Flash zip again. Now it converts to MTD. It then reboots to recovery. (Many people think it is bootlooping. )
At this point flash zip again. Now it does the longer install.
Screen says a lot of thing about /system and stuff.
Let it finish and reboot to cm.
The weakness of most guides is that they never say 3 times.
The noobs thinks it is a bootloop without reading what the recovery is doing.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
You may have missed the point where Recovery becomes unreachable the minute I flash CM9 the first time. After that I can no longer get recovery and device becomes a brick.
Jarmezrocks said:
CM9.1.0 - Flashes, gets to BML/MTD and quits - note Recovery is completely screwed after this point
Click to expand...
Click to collapse
If you can provide a link to a known 100% certain to work version of CM9 or any CM I would be greatly appreciated! I believe there is much confusion (and to be honest I got lost with so many different opinions about changes made to CM in their thread) as to what version is best to flash. I personally tried the latest CM of version 9.1.0 and the stable (to which there were two and I tried one but not the other?) and did not have any luck with either.
Look forward to hearing from you
Thanks for your reply mate :good:

Not sure why your cm9 gone bad.
Make sure you download the p1 variant and check the md5 sum of the file.
It has always been on with me.
Restock. Overcome kernel. Then flash cm 3 times.
Unless there is a hardware issue?
Sent from my GT-N7100 using xda app-developers app

priyana said:
Not sure why your cm9 gone bad.
Make sure you download the p1 variant and check the md5 sum of the file.
It has always been on with me.
Restock. Overcome kernel. Then flash cm 3 times.
Unless there is a hardware issue?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thats the thing though, I believe that CM 9 has changed several times since the beginning. Both the latest and stable didn't work. There is another stable version but really got put off the whole ordeal because I was reading so many posts of people confused as to which version they should be flashing and which one they made the stable version in the end.
Something else also thrown in was that some guys where flashing Overcome and not allowing conversion to ext4 and then upgrading to CM10?
Should flashing Overcome kernel over the top of standard Gingerbread allow the device to boot and run stock GB with ext4? How would this be different to running stock and using OCLF4 on stock kernel with CWM Recovery? Say CF root Recovery?
Sorry for all the questions but the device isn't mine and I am now looking for the simplest solution to making it run normal and stable. Seems like normal GB is so unstable its not funny! Is it normal to get random reboots on stock Gingerbread?

It is not normal for GB to reboot by itself. There must be something not right.
About overcome kernel on top of normal GB with ext4, yes that is possible to run it that way.
About allowing overcome kernel to convert to ext4, or not to allow that, it doesn't matter.
CM kernel will repartition the internal storage and everything will dissappear once a new partition scheme is in.
My suggestion is usually for people to not wait for overcome kernel to convert since it is not needed.
Sent from my GT-N7100 using xda app-developers app

Hey I got some good news!:good:
And....I will need you @priyana to update your OP for the Overcome ROM thread too, this will apply to all Australian P1000 Tabs I guess...well at least the Optus ones anyway.
Essentially the GB_Stock_Safe_v5.tar and gt-p1000_mr.pit are NOT safe like we are lead to believe....well not for the tablet I have just repaired. It is now running CM10 no problems!
I have created a new firmware package that incorporates a new PIT and various combos of files from the old GB_Stock_Safe_v5.tar and the standard firmware package.
What I found was flashing the completely stock firmware the device would not boot or function what so ever, which is really strange as most people would expect that standard firmware would at least be stable enough to use. Not even with the stock PIT or the gt-p1000_mr.pit.
You can down load the files here >>> GB_Stock_AUST_Jarmezrocks+P1.pit
This will have a firmware package and pit file combination that is suited to Australian P1000 TABS
Containing
GB_Stock_AUST_Jarmezrocks.tar
P1_add_hidden.pit
These are the ONLY files that will allow the Tab to boot, run and function normally. Before the thing was just so unstable you could barely do anything with it.
So from here Australian user who are having issues/problems with the Overcome ROM guide and getting continual reboots or bootloops should flash this package.
I will start a new thread in the dev section where it will be seen by others who are wanting to salvage their device.

That is good to hear.
BTW, the new overcome thread is sos_sifou's, not mine ?
Regarding the stock ROM, I remember that Stimpz0r, one of the great devs here, used to own a P1000 from optus and have no issue with overcome GB stock safe v5.
Makes me wonder if there are different variant of optus P1000.
Sent from my GT-P1000 using XDA Free mobile app

priyana said:
That is good to hear.
BTW, the new overcome thread is sos_sifou's, not mine ?
Regarding the stock ROM, I remember that Stimpz0r, one of the great devs here, used to own a P1000 from optus and have no issue with overcome GB stock safe v5.
Makes me wonder if there are different variant of optus P1000.
Sent from my GT-P1000 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry yeah you are right, you're just the heavy promoter of it (with good reason too eh?)
I will PM him and see if he can include it in the OP?
All I know is that without a doubt there was no way that package was saving this Tab, and that the one I posted most certainly did....so it would suggest to me that there is a difference between some models...I mean why else would they create a different firmware with a different .pit file? It makes no sense to do it without reason when really it is much easier to maintain the status-quo...don't you think?
Thanks for your valuable input too by the way. I really appreciate it :good:

can you re-upload ? i cannot download it