yashsingh1/xdaforums huggingface dataset:
[Captivate General] 41LY45:
Used the samsung's Task Manager to kill active Apps on FF 2.7
[Captivate General] nickm50:
The built in task killer works just fine.
[Captivate General] jamezz23:
Where do I find the lockscreens or themes at?
[Captivate General] KonaZXIII:
The lock screens should already be there. Take a look at Settings> Display> Unlock Screen.

For themes go to Captivate Themes and Apps and look for themes that say "Compatible with (or tested on) Cog 4.x".

This should get you started- http://xdaforums.com/showthread.php?t=921920
[Captivate General] xThe Enforcer:
Welcome to the addiction.
[Captivate General] kangi26:
I strictly use SystemPanel Lite. Haven't used anything else since going to 2.2(LONG time ago)

Welcome to this group of flashers
[Captivate General] jamezz23:
Ah sweet thanks. When everything looks the same as before sometimes its hard to picks out what settings they added
[Captivate General] mike29892:
cog 4.3 is a great rom to start, its not far off of stock. 4.3 seems to be running great for me too compared to earlier versions.
[Captivate General] studacris:
Well nice to see my help and recommendation of rom worked out for you. Now just read, read, read, and when you think you've got a question, read some more. I started flashing my phone day 2 of having it this is my first smartphone, didn't post until 3 months later and that was to start helping other people. Have fun and be careful font do anything unless you know what it is, and make sure you know how to recover from a blunder.
[Captivate General] tkjeeper:
Ha, congrats, I too flashed Serendipity, my first, a week ago and since have flashed a nice juicy paragon kernel. It's amazing the speed! I've tried a few launchers but none did I like as much as the stock one. Until I found W7 launcher on the market. But I cross back and forth btw the stock and W7, thats what I like about it is it's easy to get rid of if I like. Great work on the flash, great people here, helped me out immensely too.

I do have one question tho, that hasn't been explained to me and may help you also. Harveythedog mentioned a nandroid back up and I've searched but cant find out what this means and how to do it? Can someone explain this?

I've backed up with titbu, and backed up my apn's, and my efs folder to ext sd, but I'm not positive I've done a nandroid backup.

What is REALLY needed is a sticky here with a step by step on what to do once you've flashed a rom. There's plenty on HOW to do it and what steps to take prior, but I haven't found anything on exactly what should be done after. I think it would be really useful for noobs like me.

great work
[Captivate General] 1tontomato:
Stop encouraging him "haha" just kidding welcome to the party.
[Captivate General] studacris:
A nandroid back up is done in clockwork recovery under backup and restore, it makes a back up of your system so if you were to do something that breaks the os you can restore a working rom from the backup.
[Captivate General] mastergrillo:
Good job on the flash no matter how many roms.i.try i keep going back to cog its the best one out there lovin the.battery life and speed
[Captivate General] tkjeeper:
Ok, so I've done that. Good news. Does it get backed up on the internal sd or ext sd? If int, should I move it to ext? And home comp? Thanks Studacris.
[Captivate General] studacris:
It puts it on the internal sdcard. /sdcard/clockworkmod/backup to be more precise. Flashing doesn't wipe the sdcard partition only master clear does that, but you should be backing up the entire sdcard on your computer before flashing anyway, so that will be in there, but a good rule of thumb in computers in general: if its important to you back it up, and back up the backup. Data redundancy is an amazing thing ;)

make sure you dont rename it ever clockwork has an issue with restoring if you do, even if you change it back to what it was, so just dont rename. the nandroid itself is just named by the date you created it I believe.
[Captivate General] bigdaddydo:
serendipity forevaaaaa :)
[Captivate General] thresherhorn:
3 days into my first Rom flash as well - Serendipity (literally spent weeks researching, reading and understanding everything).

Gotta say no matter how much i messed with lagfixes... Kernels... Modems..... I could never get the cappy as smooth as this Rom. Kudos to the creators. And grats on your first (and in all likelihood by no means your last)
[Captivate General] KonaZXIII:
This should be on the first page of every ROM post. :cool:
[Captivate General] 1tontomato:
Nandroids make an image of your complete rom system, not the kernel or modem. The things you are going to use your nandroids for are when you are going to flash a theme but you don't know if it's compatible. Make a nandroid and flash the theme if you get a boot loop, boot back into recovery and restore your nandroid.

Another use would be like if now your on Serindipty and some one says hey Cognition is da bomb, make a nandroid and flash Cognition. If you decide you like Serindipty better you can go back. Here is the catch you MUST FLASH SERINDIPTY THE WHOLE ROM BEFORE YOU RESTORE THE NANDROID. You will be right back where you left off with all your settings the way they were. It makes trying stuff out a little easier.

The BIGGEST mistake you can make with a nandroid is TRYING TO FLASH BACK TO STOCK WITH A NANDROID DOES NOT WORK. When you need to use odin, you need to use odin. Hope this was helpful.

Samsung SGH I897 Andromeda3 powered, fueled with win
[Captivate General] jackjack078:
Wow, learn something every useful today. I'm in a process of changing from totally noob to not so noob day after day, lol... Thank you.
[Captivate General] jamezz23:
My wifi stopped working after 2 days of working fine. Not sure why, has anyone else had this problem with cognition 4.3? I had this problem with stock rom to but I was always able to fix that with a wifi fixer app from the market, but its not working this time. Have any ideas? Sucks because 3g hasn't expanded to my area like they've been telling me they would for the past year or so.
[Captivate General] waslost1:
Welcome to the flashers club. I started with Cog 3.x series. Really stable and great if you loke the stock look that actually works. After building confidence with Cog I started flashing others and found the whole experience of changing ROMs to be fun and addictive. There really is no turning back. Currently on Firefly whick I love but now find myself experimenting with kernels. You see, you are just getting your feet wet. We are all here to share our addiction. It's hard to say we are "helping" one another with a straight face. Happy flashing!
[Captivate General] milkytron:
I remember that feeling haha congratz!

I would recommend Cyanogenmod7 or MIUI because they run on gingerbread and make it pretty easy to find and install new themes
[Captivate General] james.arroyo:
feels gooooood!

I just flashed my first ROM and Kernel as well. Running Serendipity ROM with Onix kernel and it feels great!

I feel so PRO and ready to do more on this phone.
[Captivate General] xThe Enforcer:
Try Firefly people, it's outstanding. Welcome to the addiction!
[Captivate General] h0ckey10:
+1

Not to mention even w/o themes they are by far the most customizable roms and in very different ways, IMO
[Captivate General] xThe Enforcer:
Yeah, but it's harder since it's not installed via CWM :(

Too much work for my lazy ass!
[Captivate General] jamezz23:
Haha, in my last comment I was crying about not having 3g in my area and my wifi not working. I woke up the other day and liked at my phone and I had 3g lmao. No more slow ass edge network!!!
[Captivate General] fluidd:
Good job bud! You're not gonna stop now.. its like CRACK..

Flash FireFly when you get a chance and most likely you won't ever convert.. haha
[Captivate General] tkjeeper:
Yeah, I was Serendipity for weeks, till I tried FF. Love it. Very customizable and smooth. I was with the stock kernel...for a half hour, lol. Then I flashed my fave that I've had great luck with, a paragon kernel oc'd to 1400. Hasn't let me down yet.
[Captivate General] jamezz23:
I wanna flash firefly soon. What kernel would you get? Because on that rom don't you have to flash your own kernel?
[Captivate General] studacris:
Every rom has a kernel in it. Firefly has onix.
[GT540 Optimus General] qazxsw1234:
Hi

I updated CM 1.8 . Allow moving application is checked. If i try to move apps to sd system is restarting.

I upgraded with -w option by fastboot. Why this could be ?

Thank you.
[GT540 Optimus General] mimm.m:
you have anroid version 2.3.3 and cyanogenmod 7 thats right ?

not CyanogenMod 1.8 .....

have you recovery on your phone ... ?
[GT540 Optimus General] Quinny899:
Have you tried reflashing?
[GT540 Optimus General] qazxsw1234:
i used cm 7 android 2.3.3 sorry for miss information.

i reflashed now, but nothing changed. What would it be ?

Thank you.
[GT540 Optimus General] qazxsw1234:
by the way,

i use link2sd and first partition is ext2. link2sd is working fine. but app2sd is not working. And it is not important to work but some apps try to install to sd by self. So they makes phone restart.
[G Tablet Q&A, Help & Troubleshooting] sam0433450:
Hey guys,

My gTab got into a boot loop randomly (I hadn't even tried flashing) so I had a look on the forums here for a solution. I first tried booting into recovery from an SD card but had no luck, then tried booting clockworkmod but no luck and I finally tried nvflash.

I followed the great instructions from the sticky on this site and managed to re-flash the device. It copies the files across and gets to the reboot stage but the boot loop happens again! It loops a few times and then the tablet turns off and I can't turn it back on. I can reflash the device but it just goes through the same process.

I plugged the tablet into my PC and I can see the detected hardware icon come up. When I hold the power button this icon goes so it looks like the device is reading the power on/power off command but the screen doesn't turn on.

I have looked around everywhere but can't seem to find a solution....

Any help will be greatly greatly appreciated!

Thanks in advance,

Sam
[G Tablet Q&A, Help & Troubleshooting] Mantara:
So you were running stock rom? What happened when the boot loop started?
[G Tablet Q&A, Help & Troubleshooting] sam0433450:
Yeah I was just running a stock ROM. I just turned it on one day and it got to the Tap n Tap screen and then the screen goes blank and then the tap n tap screen comes back up. This goes on about 5 times and then just stops.

I tried doing recovery as per Google's suggestion but had no luck at all. After a nvflash I can't get the screen to come on! When I re-flash it it loads up but does the exact same loop and turns off and wont come back on until I reflash.

I'm guessing I need to repartition the device. I have put the clockwordmod recovery image into the flash (as per another posts suggestion) but I can't boot!

Any thoughts?
[G Tablet Q&A, Help & Troubleshooting] jhreid1969:
You could try and use the format utitilty at http://xdaforums.com/showthread.php?t=974422 and afterwards, go to http://xdaforums.com/showpost.php?p=9603803&postcount=1 which gives great detail about how to use nvflash to restore your Gtablet back to a stock image, which there is a download link for 3588 also.

I usually do it this way if things get out of hand and I want to restart from the beginning with a fresh start. It has not failed me yet. For some, the terms may confuse people, but in all, the people here give good instructions to where most can understand it.

I hope this may help you.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
If you put the CWM recovery image into the nvflash configuration then you don't have to boot all the way. Shut it down then start it up while holding the Volume Up key and it should go into CWM recovery. Then try clearing data and caches. If that doesn't cure your problem then go back in and repartition.
[G Tablet Q&A, Help & Troubleshooting] sam0433450:
Hey guys thanks for the responses but still no luck.

I can't boot into CWM. Once the NVFlash is complete the tablet restarts, goes into a boot loop and then turns off and I can't get it going again.

I've been googling for hours but can't find anything...
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Have you tried holding down the volume + key when it reboots at the end of the nvflash? That should intercept the boot process and drop you into recovery before it can loop.
[G Tablet Q&A, Help & Troubleshooting] sam0433450:
Yeah tried that... Doesn't come up with the "recovery key detected" just goes through to the boot loop
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Interesting... Which image were you nvflashing? What version of CWM did you insert?

Also... please post the output from the nvflash.
[G Tablet Q&A, Help & Troubleshooting] sam0433450:
well I used the nvflash_gtablet_2010110500.zip and not sure what version of CWN i'm using...

At one stage I used the nvflash_gtablet_2010110500.zip to see if it made a difference but same thing again.

C:\Documents and Settings\crolls\Desktop\NVFlash\nvflash_gtablet>"nvflash.exe" -

-bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create

--go

Nvflash started

rcm version 0X20001

System Information:

chip name: t20

chip id: 0x20 major: 1 minor: 3

chip sku: 0x8

chip uid: 0x17141188437fa0d7

macrovision: disabled

hdcp: enabled

sbk burned: false

dk burned: false

boot device: nand

operating mode: 3

device config strap: 0

device config fuse: 0

sdram config strap: 0

sending file: gtablet.bct

- 4080/4080 bytes sent

gtablet.bct sent successfully

downloading bootloader -- load address: 0x108000 entry point: 0x108000

sending file: bootloader.bin

| 928945/928945 bytes sent

bootloader.bin sent successfully

waiting for bootloader to initialize

bootloader downloaded successfully

setting device: 1 0

creating partition: BCT

creating partition: PT

creating partition: EBT

creating partition: MBT

creating partition: BLO

creating partition: MSC

creating partition: OGO

creating partition: SOS

creating partition: LNX

creating partition: APP

creating partition: CAC

Formatting partition 2 BCT please wait.. done!

Formatting partition 3 PT please wait.. done!

Formatting partition 4 EBT please wait.. done!

Formatting partition 5 MBT please wait.. done!

Formatting partition 6 BLO please wait.. done!

Formatting partition 7 MSC please wait.. done!

Formatting partition 8 OGO please wait.. done!

Formatting partition 9 SOS please wait.. done!

Formatting partition 10 LNX please wait.. done!

Formatting partition 11 APP please wait.. done!

Formatting partition 12 CAC please wait.. done!

done!

sending file: part4.img

/ 2097152/2097152 bytes sent

part4.img sent successfully

sending file: part5.img

\ 131072/131072 bytes sent

part5.img sent successfully

sending file: part6.img

/ 4194304/4194304 bytes sent

part6.img sent successfully

sending file: part7.img

/ 16777216/16777216 bytes sent

part7.img sent successfully

sending file: part8.img

/ 33554432/33554432 bytes sent

part8.img sent successfully

sending file: recovery.img

| 3862528/3862528 bytes sent

recovery.img sent successfully

sending file: part10.img

/ 16777216/16777216 bytes sent

part10.img sent successfully

sending file: system.img

\ 117292032/117292032 bytes sent

system.img sent successfully

Press enter to continue:
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
That's the good one. Would be nice to know which CWM but if it isn't recognizing the recovery key that isn't likely the problem anyway. I'll assume you didn't mess with the BCT and bootloader files... weird one.

Would you happen to have access to a linux machine you could try this from? I wouldn't think it would make any difference but you never know.
[G Tablet Q&A, Help & Troubleshooting] sam0433450:
nah I don't but if there is absolutely no solution I can build a linux box up.

Fml just my luck.
[G Tablet Q&A, Help & Troubleshooting] sam0433450:
Hey I just tried another format.

i get the Magic Value mismatch and critical falure:unable to load kernal which is all normal but I then get a unrecoverable bootloader error.

It then turns off and I can't get the errors or anythign to come back up

Is that normal?

Is the bootloader the function that actually turns the tablet on? Could this be corrupt somehow? Any way to maybe fix it?
[G Tablet Q&A, Help & Troubleshooting] dodgeman762:
Been watching this thread waiting for a miracle as I have a similar problem. Except in my case any power down results in not being able to restart except to go into APX and do the instructions in this post. However, if I power down I can't get it to boot except into APX.

Here a few interesting observations that may help:

Attempting to boot normally does cause my computer to at least recognize that a USB device is attached. However, can't actually connect to it.

Reflashing following the above post does result in a "normal" reboot. However, even though it says USB Debugging is enabled cannot connect using ADB (which would be great as then I could wipe).

Now here's a really goofy thought - if we had a flash image that did nothing but go into CWM we would be able to do the necessary housekeeping. Once done we could then try to reflash the full recovery and see if that clears the problem.
[G Tablet Q&A, Help & Troubleshooting] sam0433450:
Pretty interesting thoughts and at one stage i was thinking along the sames lines as the CWM only image. I'm not too familiar with CWM but I would imagine that the way it has been coded is that it must recognise recovery mode (power +) to load even if it is the only image on the device... Hopefully I'm wrong...
[G Tablet Q&A, Help & Troubleshooting] dodgeman762:
So here I sit staring at the output from running nvflash.sh and I see that, although it creates the partitions:

Formatting partition 2 BCT please wait.. done!

Formatting partition 3 PT please wait.. done!

Formatting partition 4 EBT please wait.. done!

Formatting partition 5 MBT please wait.. done!

Formatting partition 6 MSC please wait.. done!

Formatting partition 7 BLO please wait.. done!

Formatting partition 8 OGO please wait.. done!

Formatting partition 9 SOS please wait.. done!

Formatting partition 10 LNX please wait.. done!

Formatting partition 11 APP please wait.. done!

Formatting partition 12 CAC please wait.. done!

It seems it doesn't send them all (clockworkmod is in place of 09_SOS.img)

04_EBT.img sent successfully

05_MBT.img sent successfully

06_MSC.img sent successfully

07_BLO.img sent successfully

08_OGO.img sent successfully

clockworkmod_recovery_bekit-0.8.img sent successfully

10_LNX.img sent successfully

11_APP.img sent successfully

So it seems partitions 2, and 3 are not sent.

Looking in gtablet.cfg they are configured:

[partition]

name=BCT

id=2

type=boot_config_table

allocation_policy=sequential

filesystem_type=basic

size=3145728

file_system_attribute=0

partition_attribute=0

allocation_attribute=8

percent_reserved=0

filename=02_BCT.img

[partition]

name=PT

id=3

type=partition_table

allocation_policy=sequential

filesystem_type=basic

size=131072

file_system_attribute=0

partition_attribute=0

allocation_attribute=8

percent_reserved=0

filename=03_PT.img

And the files exist:

02_BCT.img

03_PT.img

So, am I onto something or did I just waste a lot of screen real estate?

Thanks in advance, as always!

Edit - Same result in Windows, too.
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Partitions 2 & 3 are BCT and Bootloader (which actually contains a copy of the BCT if I remember properly. They aren't sent the same way as the other images. There should be a block of text before the partitioning that shows them being sent. Not sure why it doesn't show them being written but it is normal behavior.

Sheer guesswork but it feels like some kind of bootloader problem to me. You could try a different bootloader file. I have seen this more when using windows than linux but that could be anecdotal.
[G Tablet Q&A, Help & Troubleshooting] dodgeman762:
Sorry, omitted the top part not realizing it's relevance.

lashing G Tablet with base images...

Nvflash started

rcm version 0X20001

System Information:

chip name: t20

chip id: 0x20 major: 1 minor: 3

chip sku: 0x8

chip uid: 0x1714118840dfe297

macrovision: disabled

hdcp: enabled

sbk burned: false

dk burned: false

boot device: nand

operating mode: 3

device config strap: 0

device config fuse: 0

sdram config strap: 0

sending file: gtablet.bct

- 4080/4080 bytes sent

gtablet.bct sent successfully

downloading bootloader -- load address: 0x108000 entry point: 0x108000

sending file: bootloader.bin

| 928945/928945 bytes sent

bootloader.bin sent successfully

waiting for bootloader to initialize

bootloader downloaded successfully

setting device: 1 0
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Sorry I didn't see this earlier. I've been successful using Linux based nvflash with LiveCD's and in virtual environments (VirtualBox) so no need to build a box if you can try one of those options. Up to you if you think it's worth a shot.
[G Tablet Q&A, Help & Troubleshooting] sam0433450:
Yeah I have a linux VBox set up which i forgot about so I'll try that tonight.

How do you use nvflash with LiveCDs? I was just going to go off the instructions from http://xdaforums.com/show...03&postcount=1
[G Tablet Q&A, Help & Troubleshooting] K J Rad:
Boot up the CD... mount a drive... install and run the software... It's a little more complicated than the average install but it's easier than building a computer ;-)
[G Tablet Q&A, Help & Troubleshooting] RJLadd:
I'm having more or less the same problem. I unboxed the GTab; charged the battery; turned it on. It wanted to OTA update to 3588; I let it.

I then started following the nvflash process in http://xdaforums.com/showthread.php?t=861950, figuring that just in case anything went wrong with a ROM install, I'd know how to get back to a working state.

The host is a Win7 Ultimate x64 with the Android SDK already installed, with drivers for a different device. Removed those and installed the recommended drivers for GTab.

nvflash_gtablet.bat appeared to complete ok, but the tablet went into a boot loop.

Tried formatting (http://xdaforums.com/showthread.php?t=974422). It looked like that bricked it, but running the either the original thread's nvflash or the format thread's nvflash_gtablet.bat still got an "Entering nvflash recovery mode / Nv3p Server" message on the GTab.

Unfortunately, that always seems to be followed by a "Magic value mismatch" message. Sometime the GTab then quickly clears the screen; sometimes it boot loops, and sometimes it just continues to display that message. There's usually some more text after the message - sometimes it appears to make sense, and sometimes it's obviously not really text.
[G Tablet Q&A, Help & Troubleshooting] dodgeman762:
After following this thread http://xdaforums.com/showthread.php?t=861950 I have come to the conclusion that there is something in the nvflash process that is causing this problem. In particular, it would seem that there is something specific to either each individual gTag (not so likely) or at least to slightly different hardware/firmware combinations. The process to either clean erase or flash a "generic" image overwrites this specific data. Re-attempting the process using different computers and operating systems is not going to solve the problem if the flash image is the problem,

My gut instinct is that the problem is gtablet.bct.

Hopefully, someone will discover where exactly the bomb is located and prevent this from happening to others. And maybe those of us caught up in this will get normal boot functionality back.

There is a work-around to the issue. As with most work-arounds it doesn't fix the problem but at least gets your gTab back to being somewhat functional.

http://xdaforums.com/showpost.php?p=11031898&postcount=40