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.

[Q] Sorry folks - this is probably a dumb question

Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick

nickpb said:
Firmware: 2.2
Click to expand...
Click to collapse
It would be simpler just to connect it to KIES and let it update your ROM according to its specs without any worries, If it fails than you can chose latest ROM from here its based on region, so chose latest for your region
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3

nickpb said:
Hi there,
I have just 'inherited' a Galaxy S GT-I9000 from my daughter. It has the original FROYO ROM:
Firmware: 2.2
Baseband version: I9000XXJPP
Kernal version: 2.6.32.9
Build number: FROYO.XXJPO
I'd quite like to update it to something more 'modern', but I'm a bit cautious because it's not clear (to me at least) if I can select any of the suggested ROMs, or whether I need a special one for the XXJPP version.
Sorry if this is a dumb question, but I struggle to keep up with the changes in technology and code nowadays (I am 62 after all).
I did update my previous phone (Orange San Francisco), so I'm not completely Ga-Ga (yet), but could really do with some guidance regarding this particular baseband version.
Thanks in anticipation.
Nick
Click to expand...
Click to collapse
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess

AlwaysDroid said:
You should look unto cyanogenmod 10. It is unbelievably smooth, and everything works perfect. Also totally stable. To safely do so, update to gingerbread with kies, then flash a custom kernel such as Devil through Odin. Now your ROM will not boot, dont worry. Boot into recovery and flash the CM10 Zip. It may stop halfway. This is okay, and if it happens simply boot into recovery again and flash again. Sucess
Click to expand...
Click to collapse
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2

Hi.
I think if u be in GB ROMs , it's better , then go to new bases like ICS or JB slowly.

Hey I recommend you just to update it via Kies. You will probably get 2.3.6 GB Value Pack. Its pretty good, and stable, atleast for me. If you are not satisfied with preformace that you get with it, you can install custom kernel, such as semaphore, so it would get better,
If you lived with froyo till now, you wont need anything more than GB. And you can be sure about stability, good signal, no restarts and so on, that you can get on some custom ICS and JB roms...

snapper.fishes said:
It doesn't work perfectly. Cyanogen mod is usable, but there are still quite a few issues that you would not find on a stock rom. If the rom is perfect we would already have a stable release. Just take a look at all of the bug reports.
Flashing a custom rom is a large commitment. You are giving up the warranty (thought it's probably over by now), agreeing to withstand any inconvenience that might arise as a result of the custom rom (e.g. Random reboots, bad phone signal, lag, and all sorts of weird problems), and accepting the risk that the roms might break your phone completely (But this is a very rare occurrence. Most bricked phones can still be saved, the only real exceptions being those early I9000M models that has a tendency to fry the internal memory)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Sent from my GT-I9000 using xda premium

AlwaysDroid said:
I totally and kindly disagree with you. Cm10 has almost no bugs for me at all. No random reboots. Nothing. Its almost perfect.
Click to expand...
Click to collapse
Please don't be misleading. CM10 is certainly good in it's own right, but there are quite a few things that are not working.
For instance, Google+ instant upload is completely non-functional because of an incomplete implementation in both the camera and gallery apps. This is clearly a rom problem.
The gallery app also has no settings. There is a menu option to access settings, and one would expect to see a settings screen similar to the one in CM9 when that settings menu is clicked. Instead the user is greeted with a blank screen.
Users need to be fully aware of what they are getting when choosing a rom and making statements like "it is almost perfect" is subjective and can be misleading.
Finally you say that CM10 has "almost no bugs" and then follow it with "... nothing" which is an obvious contradiction. Which is it, almost none, or absolutely none?

[Q] tab 8.9 upgrade problem. Please advise.

I need a bit of urgent advice if possible. Having waited patiently for Samsung to release ICS for the P7310 which has never appeared in the UK, I'm trying to flash to JB (latest AOSP version) from the stock 3.2.
I've installed CWMOD 5.5.0.4 ok, and copied the update rom and gapps to the root of the tab. I've gone into CWMOD recover mode, wipe/reset and then selected the rom to install. It starts the install, then fails with the system error 7 message (seems to be fairly common). It obviously started the install but now I don't seem to be able to boot the tab into 3.2 anymore, it just sits at the boot logo and doesn't get any further. I'm happy to try another ROM (maybe CM10), but I need to transfer it to the device first, and ofcourse I can't do this within windows at the moment. Odin still runs and can talk to the tab, but I'm a bit lost at the moment.
I'm a bit new to all this, so could really do with some help.

Flash the stock Rom.with Odin. You can find it at sammobile.com. it'll bring you back to stock.and.you can start over again. You're soft bricked right now.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

Cool. Thanks for that. I guess I just select the PDA option in Odin, and let it do its thing.
Any idea why this happens? I'd read a couple of threads about going from HC to ICS first, then to JB. Is this a requirement, or optional?

I'ver had similar problems finding a Rom that works on my i957. Never did find an ics that worked. I'm running jb from nrvate, but I think its specific to the i957. And, yes, flash just like you did the cm recovery.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

Really appreciate the replies. I've managed to get the tab back working under 3.2 (stock rom downloaded from SamFirmware), so that's a start. I still want to upgrade to JB if possible (or ICS if not). Am I likely to experience the same problem again? Is it worth going to ICS first? I've downloaded the stock US ICS rom, which i can flash using Odin. I can't see why this wouldn't work on a UK spec 8.9 wifi, but can anyone confirm if it does?
So, I'm back at square one, but really want to try and get this sorted.

Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
Did you do a clean install when you tried to flash the jb Rom? I.e. factory reset, format/clear system and data. If not that probably is the problem. There should not be any benefit of flashing ics before jb. The one difference between the two is you most likely will have to flash a gapps (Google apps) package after the the jb flash. Not sure where you got the Rom, but the developer should have the gapp they recommend and instruction on how to do the flash. Every jb to Rom I've flashed has the gapps package flashed after the Rom and before rebooting.
I'd stick with a Rom specific for your device. I hard bricked my phone with the wrong Rom once. The US Rom probably does not have the correct radio for.you in the UK. I only use WiFi so don't care too much if I have the right radio or.not.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?

You might try to flash a different version of cwm I don't remember now how I found this link, but here is a link for Overcome_CWM_Recovery_v5.1.2.6_P73xx.tar
http://www.sendspace.com/file/507gjv
just flash in Odin, like the ROM itself (in PDA section)
I use twrp but don't know where to find a version for your p7310.
Have you tried a different Rom
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
tman24 said:
I've just tried again, and have hit the same problem, and have tried the AOSP rom and the CM10 rom this time. I did a wipe/factory reset beforehand, but the installer starts then just aborts with 'symlink: some symlinks failed' E:Error in /sdcard/<rom file name> (Status 7). Obviously the tab 8.9 doesn't have an sd card slot, but I thought the rom must be aware of this.
Where am I going wrong?
Click to expand...
Click to collapse

harry_fine said:
You have a /sdcard directory despite the fact you have no physical external sdcard.
I had the same problem. Found this solution:
http://forum.xda-developers.com/showthread.php?t=1973712
Click to expand...
Click to collapse
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error

Ok, silly question time, but does the tab need to be rooted to install these new roms successfully?

You don't need to be rooted, just the recovery installed. Not sure why you're having problems now other than I had a hell of a time getting a Rom installed too. I'd try a different Rom. I tried some yesterday and didn't get any of them to work well. At least you've learned how to recover from a soft brick. I've learned that lesson too, to many times!
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

I'd try to download CM10 again. As i see in the error message there is a problem with the zip, maybe caused by error in downloading?

tman24 said:
If reading that reply right, one specific stock rom does what's necessary, trouble is, that's a US stock rom, and I'm in the UK. Already had it confirmed that it wouldn't be good to install a US rom on a UK tab. Loads of people has flashed their tabs, so it can't be that difficult! I've just tried Overcome CwM v5.2.1.6 with the same AOSP and CM10 roms, but same error
Click to expand...
Click to collapse
Hi, dont know if this will help, but I have flashed the US ICS rom on my Swiss Tab 8.9, with no problems. There should be no issue with worrying about the wrong radio as stated previously, as the 7310 is the WIFI only model, so there should be no issue with 3G. The only thing which causes some issues is the screen flicker issue. If you flash the US gingerbread first, then the ICS, it seems to solve the issue. For mor info check out this thread http://forum.xda-developers.com/showthread.php?t=1573548&page=50
Good luck!

Aaarrgggh! Frustrating, now I'm just getting 'hardware id not found' when I connect the tab to the PC!!! I can browse the device in Windows, but of course, Odin won't connect. How difficult can this really be!
I've already uninstalled and re-installed the Samsung USB drivers, tried a different USB port etc, but same result.
As it stands, the tab is working, but on that horrible v3.2.

I might be getting somewhere, but nothing's easy! I have moved everything over to a laptop we have, and have gone through the whole process again. I installed CwM ok using Odin, copied over the AOSP beta13 for the 7310, and this time when I installed the ZIP, it said completed ok. Good so far.
I then rebooted, and while I see the Samsung logo, the screen then goes black and stays that way. I've left it ages, but it doesn't seem to get anywhere. I can still reboot it and get into download/recovery, so that's ok. Am I doing anything wrong? I did the wipe/reset beforehand, so It's not obvious why this is not working.

Quick update. I can get ICS running (CM9 works), so that's good. It does look like any JB rom (AOSP/CM10) just cause a blank screen on reboot, which is wierd. I've re-downloaded the ROM's just in case, but no dice. Install completes ok, and gapps reports no problems.

I often don't get a boot animation, just the black screen. Every once in awhile the animation comes back. Seems totally random. I'm using nravates jb Rom on the i957. Other than that it runs great.
Sent from my SGH-I727 using xda app-developers app

[Q] Android jellybean 4.1 / 4.2?

Hello developers from XDA!
I have three questions that I was hoping you guys could answer.
First off, I own a Samsung Galaxy S GT i9000 and I'm currently running on 2.3.6 gingerbread XXJVU rooted.
I have been searching EVERYWHERE for a stable jellybean 4.1.2 ROM for my phone, but there are so many and the instructions are very complicated, resulting me into not really understanding how to flash it..
I have earlier tried to flash and ICS ROM which hugely failed. Flashing the stock rom & rooting it went succesfully, but after trying to install the rom from the recovery menu it didn't work. The result was that it was taking nearly up to an hour to start up. I had taken the battery out the phone and restarted before I waited so long. (Yes, believe it, or not. I have seriously waited an hour for it to start up. It just didn't want to.)
So my questions:
Do any of you from XDA developers know a STABLE jellybean rom which has most of the features available? For instance; calling, SMS, Wi-Fi, 3G, Play Store, USB acces etc.
I've heard that "Cyanogenmod 10" was a good one..
Second question is: IF any of you could provide me with a link to a rom (hopefully as I mentioned before Cyanogenmod 10) can you please provide a link with instruction on how to flash it? I really don't want to spend around 30 minutes to find out what I must do.
Also, I've heard that it's not a good idea to go from 2.3.6 to 4.1.2 instantly. I actually want to take the chances and go to Jellybean instead of first flashing and ICS rom.
And as for my last question: I will of course do a nandroid backup in recovery. But, if the jellybean rom fails to flash will I still be able to use that backup? As I mentioned before, I failed flashing an ICS rom. But when I did my recovery menu changed? It went from ClockWorkMod to a different one with a different colour. I haven't really looked at the backup files in the new recovery menu, but if I flash the jellybean mod I assume my recovery menu will change from CWM to CM, and resulting (I think) removing the backup files?..
If neccessary I'll post my entire device information:
Device information:
Model number: GT-I9000
Android version: GINGERBREAD_MR1 2.3.6 (SDK 10)
Kernel version: 2.6.35.7-i9000XXJVU-CL851880
Buildnumber: GINGERBREAD.XXJVU
I hope these questions could be answered!
Thanks in advance.
P.S.: Sorry if I posted this in the wrong section.

Hey,
so first of all I'd recommend Mackay ROM 1.5.9 which is based on CyanogenMod 10 but tries to stay as close as possible to stock Jelly Bean. You can find it in the development section.
To your second point: Go on CM9 first (twice!) then flash a clean CM10 and afterwards finally Mackay. If you got questions regarding that, you can ask me ofc But to be honest you have to read and try a bit to get into these things. I can explain a lot but you have to think yourself before doing something
Best regards
Sent from my Gameboy Color

inMindAndroid said:
I really don't want to spend around 30 minutes to find out what I must do.
Click to expand...
Click to collapse
:thumbdown:

BlueFlame4 said:
To your second point: Go on CM9 first (twice!) then flash a clean CM10 and afterwards finally Mackay.
Click to expand...
Click to collapse
Alternatively you could just do a factory reset and flash CM10 Fishears since it uses the same partition layout as stock, avoiding the need to flash middlemen and format drives.

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