samsung 8.9 tab

[member33]

some additional questions: 2) PDA, PHONE AND CSC. - mean what?

Sometimes you just need to flash PDA without PHONE AND CSC but other times you'll need to flash all 3 - PDA, PHONE AND CSC together.

some additional questions: as per your instruction, default is PDA. when do i know to use PHONE and CSC?

It depends on how many files (.tar OR tar.md5) you get after you've extracted the firmware zip file.

If it contains only 1 file, always feed to - PDA.

But if it contains multiple files then you'll have to feed to all 3 - PDA, PHONE AND CSC (see image below).

Important Note: leave PIT and BOOTLOADER alone, DO NOT feed files to them as they're meant for repairing purposes or only when advised by developers on the installation of their ROMs. As of this flashing guide on updating of official incremental firmware, there's no need to flash them, SO LEAVE THEM EMPTY.

____________________________________________________________
http://forums.hardwarezone.com.sg/g...new-box-sealed-sets-4043305.html#post76203060

 

[member33]

some additional questions:3) The .tar.md5 files for PDA may contain words like - PDA and/or CODE and/or HOME.

After I've extracted the zip file, it contains multiple .tar.md5 files.

So.....


Which file should I feed to Odin-PDA?

Normally the PDA .tar.md5 file contains words like - PDA and/or CODE and/or HOME.

Eg: xxxxxxxxxxxPDAxxxxxxxxx.tar.md5
Eg: xxxxHOMExxxxxxxxxxxxxxx.tar.md5
Eg: xxxxxxxxxxCODExxxxxxxxxx.tar.md5
Eg: PDAxxxxCODExxxxxxxxxxxx.tar.md5
Eg: HOMExxxxCODExxxxxxxPDA.tar.md5


Which file should I feed to Odin-PHONE?

Normally the Odin-PHONE .tar.md5 file contains the word - MODEM.

Eg: xxxxxxxxxxxMODEMxxxxxxxxx.tar.md5
Eg: xxxxxxxxxxxxxxxxxxxxMODEM.tar.md5


Which file should I feed to Odin-CSC?

Normally the Odin-CSC .tar.md5 file contains words like - CSC and/or MULTI_CSC.

Eg: xxxxxxxxxxxCSCxxxxxxxxx.tar.md5
Eg: MULTI_CSCxxxxxxxxxxxxx.tar.md5
Eg: xxxMULTI_CSCxxxxxxCSC.tar.md5

Note: placing of the words is not important.

some additional questions: - you mind showing me the website for the firmware again? at least i could bookmark it..

You can search your device firmwares (zip files) at Sammobile website.

It doesn't matter where you download, just check that you've downloaded the correct device model and firmware version.
____________________________________________________________
http://forums.hardwarezone.com.sg/g...new-box-sealed-sets-4043305.html#post76203060

 

[kurt_629]

Chim.... I guess for now, it's OK.. until then...

I thank you sincerely

 

[blue00]

Turn on USB debugging refers to Tab 8.9 device settings.


How to get there?

On device go to - Settings> Developer Options> USB Debugging.

Please note that because I'm using custom Themes and lcon layouts, so yours may look different to the screenshot above.
____________________________________________________________
http://forums.hardwarezone.com.sg/g...new-box-sealed-sets-4043305.html#post76203060

this part u mention is workable if devise is able to boot into android.

if lets say i flash a custom rom for my tab7.7 and got stuck at boot up, what to do then?

 

[member33]

this part u mention is workable if devise is able to boot into android.

if lets say i flash a custom rom for my tab7.7 and got stuck at boot up, what to do then?

For bootloop issue (stuck at boot/logo), you'd need to boot into recovery and do the wipe - select wipe cache partition and select wipe data/factory reset (actually this is required everytime you change to a new ROM but not necessary for incremental firmware/version updates). Normally this should solve bootloop but if it didn't work out, try to flash back a full stock ROM and then flash the custom ROM again (and do the wipe). But if it didn't work out still, then most probably you've corrupted partition and if that happens you'd have to flash a .pit file.

Normally bootloop happens after flashing a custom ROM from stock or vice versa. If you didn't do wipe after changing ROMs, DalvikVM still reads from the old Dalvik Cache which causes bootloop because most of the applications (.apk) and frameworks from the new ROM have changed. So you've to wipe the old cache so it can update accordingly (and build a new tree of dependencies) and this is the reason why it takes such a long time to boot on the first time after installing a new ROM.
________________________________________________________
http://forums.hardwarezone.com.sg/g...new-box-sealed-sets-4043305.html#post76203060

 

[blue00]

For bootloop issue (stuck at boot/logo), you'd need to boot into recovery and do the wipe - select wipe cache partition and select wipe data/factory reset (actually this is required everytime you change to a new ROM but not necessary for incremental firmware/version updates). Normally this should solve bootloop but if it didn't work out, try to flash back a full stock ROM and then flash the custom ROM again (and do the wipe). But if it didn't work out still, then most probably you've corrupted partition and if that happens you'd have to flash a .pit file.

Normally bootloop happens after flashing a custom ROM from stock or vice versa. If you didn't do wipe after changing ROMs, DalvikVM still reads from the old Dalvik Cache which causes bootloop because most of the applications (.apk) and frameworks from the new ROM have changed. So you've to wipe the old cache so it can update accordingly (and build a new tree of dependencies) and this is the reason why it takes such a long time to boot on the first time after installing a new ROM.
________________________________________________________
http://forums.hardwarezone.com.sg/g...new-box-sealed-sets-4043305.html#post76203060

thks for details


but where to get a .pit file? for tab 7.7

 

[member33]

Just to be clear that before you proceed to flash a .pit file -
1. you did the wipe AFTER installing a ROM but still stuck/hang at logo.
2. It still stuck/hang at logo after you have flash back a full stock ROM.

You can download P6800 .pit file here. You get 2 folders.
*Use the .pit file in the 'pits-stock folder' and feed it to Odin-PIT. Do Not use any files in 'pits-patched folder' as they're meant for repairing bad sectors in eMMC.

*You need to flash .pit file together with official firmware (download at Sammobile - JB preferred, avoid ICS). Feed them according to Odin-PDA/PHONE/CSC. Tick F. Reset Time and Tick Re-partition. DO NOT tick Auto Reboot.

*Start flashing > successful when you see a Pass (device doesn't reboot itself, no worries because Auto Reboot is uncheck) > unplug cable and wait for 5 mins > boot to recovery and do the wipe > reboot > done (it may takes few mins to boot).



Side note: If your device is running ICS with stock Kernel, DO NOT use recovery to do the wipe prior to installing ROMs because it will trigger eMMC brick (bad sectors).
________________________________________________________
http://forums.hardwarezone.com.sg/g...new-box-sealed-sets-4043305.html#post76203060

 

[blue00]

Just to be clear that before you proceed to flash a .pit file -
1. you did the wipe AFTER installing a ROM but still stuck/hang at logo.
2. It still stuck/hang at logo after you have flash back a full stock ROM.

You can download P6800 .pit file here. You get 2 folders.
*Use the .pit file in the 'pits-stock folder' and feed it to Odin-PIT. Do Not use any files in 'pits-patched folder' as they're meant for repairing bad sectors in eMMC.

*You need to flash .pit file together with official firmware (download at Sammobile - JB preferred, avoid ICS). Feed them according to Odin-PDA/PHONE/CSC. Tick F. Reset Time and Tick Re-partition. DO NOT tick Auto Reboot.

*Start flashing > successful when you see a Pass (device doesn't reboot itself, no worries because Auto Reboot is uncheck) > unplug cable and wait for 5 mins > boot to recovery and do the wipe > reboot > done (it may takes few mins to boot).



Side note: If your device is running ICS with stock Kernel, DO NOT use recovery to do the wipe prior to installing ROMs because it will trigger eMMC brick (bad sectors).
________________________________________________________
http://forums.hardwarezone.com.sg/g...new-box-sealed-sets-4043305.html#post76203060

thks !!! will try it when 4.2 is out.

the default 4.1 is so so .... n some funny features...