[ROM][p6800/p6810/i815] (17/1/2014 BeanStalk link) Jellybean Custom ROMs

[daniel_hk]

Here is a colloction of all the available Jellybean custom roms for GalaxyTab 7.7.


17/1/2014
Add the new JB build: BeanStalk link.

7/10/2013
After studying the source of fstrim, I manage to get it work on our CM kernels. Thanks to UpInTheAir's tips! :good:
The update kernels are good for all the ROMs I posted. LagFix/Fstrim is working now. Cheers!
　History

22/7/2013
The Samsung blobs are really outdated. It's getting harder and harder to port our tab to new codes. Need you guys to show more patrience to test and report on the new builds.
Flash this patch View attachment p6800-TelephonyPatch.zip will fix the Telephony and kernel issue of p6800 in 16/7 cm10.1. Not work for PAC. Good luck!

20/7/2013
A bug in the new CM source cause i815 not boot. The fixed version 20130720 is uploading now. Salute to Lt.col.johncross and other i815 owners for helping me test. Cheers!

16/7/2013
A tiny bug (a missing flag) in the device tree cause the new SystemUI crash! My repo was corrupted after repeatly reverting the commits. It took me a whole week to recover! I really need to complete my uploads to github!
In this new build, I switch to the 4412 kernel source (3.0.64) with new sensor blobs. Native NTFS support is finally there. For those who want to change their external sd to NTFS, please noted that recoveries can't read NTFS. Testing and rebuilding now. Will upload in an hours. Cheers!

24/6/2013
It's been a while for cm10.1 update. The new cm10.1 is uploading now. Cheers!

9/6/2013
It was a busy week. The most important thing in early June is the momerial of the "Democracy movement of June 4" in 1989. The whole world was beneficial from it but not the origin China... :crying:
I upgrade the power management and a few kernel drivers of the CM kernel. Which fixed the charging loop issue but the tab will reboot to system after charging for a few mintues. Don't know if it is normal yet?. Gpu max. freq. is 400Mhz and update to the new blobs now. I also merge the two wifi driver to give a more stable driver. The firmware of wifi chip is updated to version 4. Hoping the kernel is done and I can move on...:fingers-crossed:

3/6/2013
It's really great that Espen96 has setup a host at his server for me! :good:
http://3djanos.com/daniel_hk/index.php?dir=rom/pa3
It is a pure download page without any ad. and delay. Also works great for downloading in the tab.

1/6/2013:
After two weeks of sweaty work on the wifi driver, I finally manager to finish TWO workable drivers. One base on Atheros latest driver on 3.9 kernel. The other one derived from the stock JB source. All the wifi and power management related drivers are modified. Both drivers work quite well in power consumption and connectivity. I use the Atheros driver as standard and will release the other drivers in a seperate kernel shortly.
CM has change a lot in the pass two weeks. Sadly, pie seems not working yet, or I don't know how... Box has limits in download so decided to remove it from pre-release. I'm open to any suggestion on new hosts. The new builds are uploading now. Cheers!

17/5/2013:
The latest cm10.1 is uploading to pre-release now. Base on the test kernel, full multi cast and vif supports are added. I have test it with Torrent download for a few hours. Hoping the wifi p2p wakelock (sleep drain) issue is fixed.

16/5/2013:
Sadly, the new wifi driver from p6800 JB source is not working on 4.2.x. Tab will reset after system start. However, I found another bug in our wifi driver's wakelock. Since cm10, the kerenl has not handle mulitple vif (which p2p always use). It just quit at the wow_suspend when detected more than one vif. In cm10, the driver will behave like sod on wifi. In cm10.1, infinite wow_suspend requests are issue which heat up and drain battery. I rewrite the whole wow_suspend and wow_resume in cfg80211. BT dowload will not cause the tab hang at sleep now. Hoping the issue is fixed. The test kernel for p6800 is uploading to pre-release. This kernel also work for PA3.50. Please test and report.

13/5/2013:
I'm adding one more release area goo.im. All the previous roms are uploading to goo.im now. OTA with GooManager will be supported shortly. Since goo.im may not be available in some region. I will continue to keep other locations.

7/5/2013:
The new build is uploading to pre-release now. Found a bug in power management of wifi driver. The wakelock duration was set to a very short period. When at sleep, the tab may not have enough time to handle the incoming wifi packets before wakelock time out. Thus infinite number of wakelock is generated. If the packet can be handled eventually, battery is drained. If not, hanging may occurs. Hoping the drain issue is gone now.

29/4/2013:
I have connect my tab to adb logcat for a day. The issue just don't come out! I change the network driver and some of the hardware settings. Don't know if the drain is fixed or not... Need you guys to do a real time test...
Testing kernels with some updates are uploading to pre-release. Support both CM10.1 and PA3.
- Touch screen params. revert to stock values.
- Compass direction fixed
- NTFS_RW enabled
- IP multicast is enabled
- lpm support, hoping to fix autoboot when charger/usb connected in PA3
- improve preview quality of streaming video in rear camera.

20/4/2013:
The Bluetooth headset is fixed!:highfive: That was the last piece of puzzle for bluetooth! It was a tiny bug in the opensource tinyalsa driver cause that. Making a clean build now. Will upload to pre-release after a brief test in a few hours. Latest CWM 6.0.3.1 too. (md5 generation in backup cause reboot, pending to next release)

12/4/2013:
The new heart need another bypass to remove the clot. I rebuild all the three model with the new supercharge kernel. By default, no O/C & U/V are applied. The GPU is boost to 300Mhz. A safe and smooth value. Hoping the laggings are gone. Uploading to pre-release to replace the 8/4 version.
Revise the tested U/V values in FAQ to adapt the new GPU freq.

10/4/2013:
Add the tested U/V values in FAQ.

7/4/2013:
Take a break to build the PA for GT-Plus. Learn more about the device tree & kernel now! Come back with a little bit refreshing. I finally figure out how to overclock the kernel.:highfive: With some degree of undervoltage, add a little bit performance without sacrifying power consumption. Thanks for the Ezykernel from Ezynow. A very good reference for O/C & U/V. With Pimp my rom, I finally got an Antutu value over 10K. :highfive:
Before starting upload, I found quite a few updates from CM. Rebuild again and will upload to pre-release in a few hours.

3/4/2013:
The first phone working p6800 build is uploading to pre-release now. Phone is working fine now! :highfive:
The new tinyalsa in 4.2 is not quite comatible with my Bluetooth. The headset's input pin is not initialize. Need to find a way to fix it. I have enabled the output pin but no way to test it. Anyone has bluetooth speakers, please report.

2/4/2013:
Kernel changes only cover p6800. Rebuilds p6810 & i815 and will upload ASAP.

1/4/2013:
Burying myself into the kernel source for the whole week end, I finally fixed the tinyalsa support in the kernel. :highfive: It was just a tiny change that cause the whole audio input fail! Nearly all apks using audio input, voice search, recorder,etc. are working now. Sadly, the phone.apk issue is not caused by that! For p6810 & i815, I could say all major issues are gone now, please enjoy. For p6800, I have to carry on...
Almost everything is tested. This time no need to put in pre-release.

26/3/2013:
Please forget about the 20130325bt build. I found the last piece of pizzle and fixed the buletooth headset service. Rebuilding all 3 models now. Will upload to pre-release ASAP. :highfive:
The last major issue is Phone.apk which requires another major operation. Please be patient...

25/3/2013:
Working on bluetooth for a whole week. Got stuck! I can scan, pairing and trasfer files but I can't bind it to the Headset service. Upload to the pre-release area to see if anyone has any idea... Sorry, p6800 only for the time being. Don't have enough time to build other models. My antique PC need 3 hrs to complete a build! Really need to upgrade it...
Please report the outcome of other bluetooth devices...
Phone.apk not fix yet. Please don't border to test it. Seems the audio driver for input not working. Searching for manual from ALSA & YAMAHA now...
Someone report transfer limits in Box. Add one more location for pre-release.

22/3/2013:
CWM 6.0.3.0 & CM10.1 10/3/2013 builds released to make room for the coming pre-release.
Further progress in bluetooth, file transfer is OK now. Audio input most likely cause phone FC. Phone apk need serious change or rewritten to work on our Tab...

11/3/2013:
10/3/2013 builds are uploading to pre-release areas..Box may take longer to upload.
There is no significant change in CWM 6.0.2.9 so pending for newer release.

8/3/2013:
My tab is fixed! Yeah!
Ater dumping the first few MB from my tab via the JTAG port. I know what cause my problem now...
It was the dd command I issued earlier to flash the recovery. I must had enter the wrong partition in of=.. I write the data to mmcblk0 instead of mmcblk0p6! I recover those data from my friend's tab. I lost all the data inside but I'm grateful to have it back. This is really the price I have to pay...
This command is extremely dangerous! I should have put it in a script to avoid typing errors. I did it in the terminal apps which is even more dangerous since the software keyboard easily cause typing error... I must had touch the Enter key when I type the letter p. I have done lots of times so I didn't bother to check the terminal window (my second mistake). This is a very good lesson to me... Thanks for those concern and for those teasing (I deserve it!). Really grateful to have you guys around! :good:

5/3/2013:
Working on the kernel for the whole weekend. Hoping to identify the problem of bluetooth and Telephony. Stuck in the latest kernel source! It fail to boot and required a lot of changes. With my friend's tab in hand, I finally managered to correct all the errors and build it out but waste the whole weekend! The lastest cm10.1 builds with the new kernel and other updates from CM is uploaded to the pre-release area. Please test and report.

17/2/2013:
No changes can be made before getting my Tab back... But still want to make myself useful. This is the CM10.1 4.2.2r1 build. Thanks gazjglusk for testing the build for me...
PS. I was told that the software keyboard is hidden by default as pa3.0b1

10/2/2013::crying:My Tab fail to boot this morning, I think my bootloader is corrupted. Not even the Samsung logo and battery icon while charging. I have to send it to the dealer for repairing...Hoping won't put an end to my works

My works:

CyanogenMod 10.2 (4.3.1r1):
http://forum.xda-developers.com/showthread.php?t=2501402

TWRP & CWM Recoveries
http://forum.xda-developers.com/showthread.php?t=2352967

PAC-Man Rom v23.0.0(4.2.2.r1.2):
http://forum.xda-developers.com/showthread.php?t=2330651

ParanoidAndroid 3.68(4.2.2.r1.2):
http://forum.xda-developers.com/showthread.php?t=2139747

CyanogenMod 10.1 (4.2.2r1.2):
　● change log:

　　[COLOR=Blue]16/7/2013[/COLOR]
　　- latest source from Official n7000 16/7/2016 build
　　- 4412 kernel source with s wifi driver
　　- new ligtht sensor driver with new blobs. lower margin and one more step
　　- new power driver to fix charging loop at power off
　　- native NTFS support
　　[COLOR=Blue]24/6/2013[/COLOR]
　　- latest source from Official n7000 23/6/2013 build
　　- Settings update
　　- kernel-s with some minor bug fixes.
　　[COLOR=Blue]1/6/2013[/COLOR]
　　- latest source from Official n7000 30/5/2013 build
　　- completely new wifi driver and wakelock routines
　　- wifi data transfer in deepsleep
　　- better 5G wifi support
　　- fix a bug in gpu avs voltage table
　　[COLOR=Blue]17/5/2013[/COLOR]
　　- latest source from Official n7000 16/5/2013 build
　　- new wakelock routines for kernel wifi driver
　　- better support for 5G wifi
　　- better support for multicast
　　- lower the wifi power at deepsleep
　　[COLOR=Blue]7/5/2013[/COLOR]
　　- latest source from Official n7000 4/5/2013 build
　　- bug fix in kernel wifi driver
　　- Touch screen params. revert to stock values.
　　- Compass direction fixed
　　- NTFS_RW enabled
　　- IP multicast is enabled
　　- improve preview quality of streaming video in rear camera.
　　- move bluez patches from system core to device tree
　　[COLOR=Blue]20/4/2013[/COLOR]
　　- latest source from Official n7000 16/4/2013 build
　　- bluetooth headset audio fixed
　　- some debug stuff removed and clean up of kernel see if they cause drain
　　[COLOR=Blue]12/4/2013[/COLOR]
　　- kernel fixed release
　　[COLOR=Blue]7/4/2013 pre-release[/COLOR]
　　- latest CM10.1 source from Official n7000 7/4/2013 build
　　- O/C & U/V kernel upto 1.6G (1.8 not stable).
　　- new io scheduler & pagasusq gov.
　　- cup entries enabled in performance settings (3rd party setCUP not required)
　　[COLOR=Blue]3/4/2013[/COLOR]
　　- latest CM10.1 source from Official n7000 2/4/2013 build
　　- quite a lot updates from CM's source.
　　- fix the phone in p6800
　　[COLOR=Blue]1/4/2013[/COLOR]
　　- latest CM10.1 source from Official n7000 30/3/2013 build
　　- new Mali driver in kernel
　　- fix tinyalsa audio support in kernel
　　- change on-demand cupfreq.
　　[COLOR=Blue]25/3/2013 pre-release[/COLOR]
　　- latest CM10.1 source from Official n7000 21/3/2013 build
　　- Changes in bluetooth stack
　　- new SuperUser settings
　　- New green 3D chaging animation
　　[COLOR=Blue]10/3/2013[/COLOR]
　　- latest CM10.1 source from Official n7000 10/3/2013 build
　　- New su and Superuser.apk
　　- include Fuse and obb public mount points
　　- fix Brightness control in Quick Settings
　　- changes in kernel, try to reduce power consumption.
　　[COLOR=Blue]3/3/2013[/COLOR]
　　- latest source from CM's Offical n7000 2/3/2013 build
　　- lots of changes in kernel
　　- enabled the performance settings under developer options
　　[COLOR=Blue]17/2/2013[/COLOR]
　　- latest source from CM's Offical n7000 16/2/2013 build
　　- CM10.1 is now 4.2.2r1 
　　[COLOR=Blue]8/2/2013[/COLOR]
　　- latest source from CM's Offical n7000 build
　　- lower minium valuse for Brightness, increase autoBrightness steps
　　- fixes on Contacts.apk and Settings.apk from pa2.55

　● know issues:
　　- all CM10.1 issues
　　- VoiceDialer not working on bluetooth headset yet.

ParanoidAndroid 2.55cm (4.1.2):

[COLOR="DarkRed"]　● [B][I] change log:[/I][/B][/COLOR]
　　[COLOR=Blue] 14/1/2013[/COLOR]
　　- CM nightly build updates
　　- increase autoBrightness steps
　　- fix button misalignment in portrait view
[COLOR="DarkRed"]　● [I][B] know issues:[/B][/I]
　　- wifi sleep of death. mostly when signal is poor
　　- built-in wifi tethering doesn't work, may use paTether.apk
[/COLOR]

Downloads

[COLOR=Green][B][SIZE="4"]
Goo.im:[/SIZE][/B][/COLOR][url]http://goo.im/devs/daniel_hk/rom[/url]
[COLOR="Green"][B][SIZE="4"]Miror:[/SIZE][/B][/COLOR][url]http://www.kuaipan.cn/file/id_39173572073096195.htm#kp|39173572073096197|0[/url]
[COLOR=Green][B][SIZE="4"]Kernels:[/SIZE][/B][/COLOR][url]http://goo.im/devs/daniel_hk/rom/kernel/GT-7.7[/url]

[SIZE=4][COLOR=Green][B]CM10.1 Downloads:[/B][/COLOR][/SIZE]
　● [COLOR=Red]24/6/2013:[/COLOR]
　　p6800: [url]http://d-h.st/7aV[/url]
　　p6810: [url]http://d-h.st/w19[/url]
　　i815: [url]http://d-h.st/kQt[/url]
　● [COLOR=Blue]1/6/2013:[/COLOR]
　　p6800: [url]http://d-h.st/yZe[/url]
　　p6810: [url]http://d-h.st/24D[/url]
　　i815: [url]http://d-h.st/xR5[/url]
　● [COLOR=Blue]17/5/2013:[/COLOR]
　　p6800: [url]http://d-h.st/hJF[/url]
　　p6810: [url]http://d-h.st/Ey1[/url]
　　i815: [url]http://d-h.st/MV8[/url]
　● [COLOR=Blue]7/5/2013:[/COLOR]
　　p6800: [url]http://d-h.st/W6z[/url]
　　p6810: [url]http://d-h.st/9hQ[/url]
　　i815: [url]http://d-h.st/NOt[/url]
　● [COLOR=Blue]20/4/2013:[/COLOR]
　　p6800: [url]http://d-h.st/njb[/url]
　　p6810: [url]http://d-h.st/jDS[/url]
　　i815: [url]http://d-h.st/w7r[/url]
　● [COLOR=Blue]12/4/2013:[/COLOR]
　　p6800: [URL]http://d-h.st/AsV[/URL]
　　p6810: [URL]http://d-h.st/VpX[/URL]
　　i815: [URL]http://d-h.st/GpI[/URL]
　● [COLOR=Blue]3/4/2013:[/COLOR]
　　p6800: [URL]http://d-h.st/mJZ[/URL]
　● [COLOR=Blue]1/4/2013:[/COLOR]
　　p6800: [URL]http://d-h.st/iFX[/URL]
　　p6810: [URL]http://d-h.st/ywd[/URL]
　　i815: [URL]http://d-h.st/PH8[/URL]
　● [COLOR=Blue]10/3/2013:[/COLOR]
　　p6800: [URL]http://d-h.st/siT[/URL]
　　p6810: [URL]http://d-h.st/oa0[/URL]
　　i815: [URL]http://d-h.st/DYt[/URL]
　● [COLOR=Blue]3/3/2013:[/COLOR]
　　p6800: [URL]https://mega.co.nz/#!ZJxRjBCI!QFP7Jz_hVwxn7xNHTE2vGmBdUIVV8_epA9m6C1iDHMo[/URL]
　　p6810: [URL]https://mega.co.nz/#!9UZH0ASZ!G85RzUABwhIELdxxcU6iKX8NsHENdQXNdJWw-3mUCPQ[/URL]
　　i815: [URL]https://mega.co.nz/#!9Jh2HJaa!UNG4gVvkZ7h-CbLO3x37vCW0jrUVEywJJG3YY_dKq94[/URL]
　● [COLOR=Blue]17/2/2013:[/COLOR]
　　p6800: [URL]http://d-h.st/1Kn[/URL]
　　p6810: [URL]http://d-h.st/4RA[/URL]
　　i815: [URL]http://d-h.st/cQZ[/URL]
　● [COLOR=Blue]7/2/2013[/COLOR]
　　p6800: [URL]http://d-h.st/Zdt[/URL]
　　p6810: [URL]http://d-h.st/rfJ[/URL]
　　i815: [URL]http://d-h.st/QYi[/URL]

[COLOR=Green] [SIZE=4][B]PA2.55cm Downloads[/B][/SIZE][/COLOR]
　● [COLOR=Red] 14/1/2013:[/COLOR]
　　p6800: [URL]http://d-h.st/nFa[/URL]
　　p6800AROMA: [URL]http://d-h.st/BfR[/URL]
　　p6810: [URL]http://d-h.st/2XX[/URL]
　　p6810AROMA: [URL]http://d-h.st/omh[/URL]
　　i815: [URL]http://d-h.st/M0Z[/URL]
　● [COLOR=Blue] 27/12/2012:[/COLOR]
　　p6800: [URL]http://d-h.st/mrT[/URL]
　　p6800AROMA: [URL]http://d-h.st/Wxa[/URL]
　　p6810: [URL]http://d-h.st/oh3[/URL]
　● [COLOR=Blue] 7/12/2012:[/COLOR]
　　p6800: [URL]http://d-h.st/hMG[/URL]
　　p6800AROMA: [URL]http://d-h.st/CLQ[/URL]
　　p6810: [URL]http://d-h.st/oen[/URL]

[COLOR=Green] [SIZE=4][B] Support files:[/B][/SIZE][/COLOR]
　● PA_Trebuchet.zip: [URL]http://d-h.st/oQX[/URL]
　　[I]- to activate PA settings for 14/1 non-AROMA version[/I]
　● paTether.apk: [URL]http://d-h.st/6ph[/URL]
　　[I]- to provide basic wifi tethering support for pa2.55[/I]

[I]**AROMA version (gapps included), current versions in [COLOR=Red]RED[/COLOR][/I]

Pre-release ROMs:
**The latest builds for testing. Some may not boot.. Please report after testing
site1:http://pan.baidu.com/share/link?shareid=296833&uk=1512265283#dir/path=/JB ROM
site2:https://mega.co.nz/#F!xRYlwZbY!LZM83QAU4OM8cz7jW0jG5Q

Gapps:
　● 20121011 for (4.1.2) pa2.55,cm10: http://d-h.st/06e
　● 20130812 for (4.2.2) pa3.x,cm10.1: http://goo.im/gapps//gapps-jb-20130812-signed.zip
　● pa_gapps: http://goo.im/devs/paranoidandroid/roms/gapps

Other developers:

• BeanStalk
  Thanks vaka2
  BeanStalk: http://forum.xda-developers.com/showthread.php?t=2599392
• CyanogenMod
  Thanks locerra & alanorth
  CM10.1:http://forum.xda-developers.com/showthread.php?t=2053415
  CM10: http://forum.xda-developers.com/showthread.php?t=1816859
• ParanoidAndroid
  Thanks Androguide.fr
  PA2.53: http://forum.xda-developers.com/showthread.php?t=1838391

Source:
kernel & device trees
gitub: https://github.com/danielhk/

Credits:

• The Cyanogenmod Team who keep many devices alive!
• The ParanoidAndroid Team
• locerra & ohanar for his great work on 7.7 devices trees
• Androguide.fr for his work on PA for our device
• All those who help and donate

Donations:
　　

 

[daniel_hk]

FAQ

Q: Where is the developer options settings
A: the "developer options" is hidden in 4.2.1 (cm10.1, pa3.0)
　to show it in settings:
　in:
　　settings > about
　hit the "build number" 7 times (hints will be shown after the 3rd time)

Q: How to avoid the emmc brick bug when flashing
A: if coming from stock ics. Here is one of the easier way:

1. flash the rom (and gapps) in recovery. don't do any factory rest and wiping!
   **AROMA version: disable wipe caches option!
2. reset to recovery again.
3. do factory reset or wipe data
4. reset and enjoy!

Q: What are the safe U/V values?
A: The margin of voltage tolerance is vary.
　I recommend using Pimp my rom (Androguide.fr:good
　at Pimp my CPU under the TOOLS:
　　select VOLTAGE CONTROL
　The tested values are from ezykernl :good:. Value lower than that not garantee working.

• Freq　　　　stock　　　tested　　　safe
• 1600MHz　no value 　 1300mV　　1325mV
• 1400MHz　1300mV　　1275mV　　1300mV
• 1200MHz　1225mV　　1200mV　　1225mV
• 1000MHz　1125mV　　1100mV　　1125mV
• 800MHz 　 1050mV　　1000mV　　1025mV
• 500MHz 　　950mV 　　 925mV 　　 925mV
• 200MHz 　　950mV 　　 900mV 　　 925mV

 

[sbalu]

Greetings, great welcome for the new topic!

 

[Pirmas]

Re: [ROM][p6800/p6810/i815] Jellybean Custom ROMs (9/2/2013))

Thanks a lot.

Sent from my GT-P6800 using XDA Premium HD app

 

[ATking]

Thx a lot!! A Gift for the Year of Snake!!!!

Thx a lot for the great work!!

I have a question about the USB OTG! I tried the OTG cable with usb stick which is working quite well, But once I try the cable with the card reader, the device off after a few second respond.

I did try to use the same cable with the same card reader to the Tab 10.1 with CM 10.1, that is working.

Does it because of the Voltage of 7.7 is lower than 10.1? is there anyway to increase that?

Thanks a lot for your great work!

 

[daniel_hk]

Thx a lot for the great work!!

I have a question about the USB OTG! I tried the OTG cable with usb stick which is working quite well, But once I try the cable with the card reader, the device off after a few second respond.

I did try to use the same cable with the same card reader to the Tab 10.1 with CM 10.1, that is working.

Does it because of the Voltage of 7.7 is lower than 10.1? is there anyway to increase that?

Thanks a lot for your great work!

I think so, there may not be enough current to drive your card reader...

 

[Gilbot]

Re: [ROM][p6800/p6810/i815] Jellybean Custom ROMs (9/2/2013))

New CM10.1 builds?!?!?!!!

Sent from my SCH-I535 using xda premium

 

[golfinggino]

Re: [ROM][p6800/p6810/i815] Jellybean Custom ROMs (9/2/2013))

So long with no updates for this tablet and now 2 paranoind and 1 cm 10.1 updates which to flash???
Thank you for the updates !!!

Sent from my GT-P6800 using xda app-developers app

 

[carlo67]

hi
I would like to know the wifi\3g\bt working on the PA2.55cm ?

---------- Post added at 01:00 PM ---------- Previous post was at 12:56 PM ----------

and
I would like to know how to flash the PA2.55cm? Odin or?

 

[daniel_hk]

hi
I would like to know the wifi\3g\bt working on the PA2.55cm ?

---------- Post added at 01:00 PM ---------- Previous post was at 12:56 PM ----------

and
I would like to know how to flash the PA2.55cm? Odin or?

It's a zip, you have to flash it in recovery.

If you are now in stock ICS, beware of the eMMC bug for bricking. You must replace the kernel before doing a factory reset or wipe.

Goodluck !

 

[carlo67]

It's a zip, you have to flash it in recovery.

If you are now in stock ICS, beware of the eMMC bug for bricking. You must replace the kernel before doing a factory reset or wipe.

Goodluck !

ok
I have cm9 on the tablet now. Will I doing a factory reset or wipe.?

 

[sbalu]

It's a zip, you have to flash it in recovery.

If you are now in stock ICS, beware of the eMMC bug for bricking. You must replace the kernel before doing a factory reset or wipe.

Goodluck !

Sorry to see that your tab went wrong!I hope it will comes to life soon.
What is this eMMC bug exactly? I never change any kernel when I change from stock ICS to PA.Just root and put the new CW and flash up PA.

 

[daniel_hk]

ok
I have cm9 on the tablet now. Will I doing a factory reset or wipe.?

cm9 is ok. you can do a factory reset.

Goodluck !

 

[daniel_hk]

Sorry to see that your tab went wrong!I hope it will comes to life soon.
What is this eMMC bug exactly? I never change any kernel when I change from stock ICS to PA.Just root and put the new CW and flash up PA.

There are many posts on this subject.

In short:
Some of the Samsung devices (including or 7.7) have bad memory chips inside. The sock ICS kernel include a flag something like EMMC_CAP_ERASE, bad chips will lock or burnt during format (wipe). Androguide and I were also the victims of this bug. I was lucky. The dealer replace the motherboard for me within warranty period.

This time the warranty period was expired...

 

[carlo67]

cm9 is ok. you can do a factory reset.

Goodluck !

ok what about google apps ? will I need them?

---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------

There are many posts on this subject.

In short:
Some of the Samsung devices (including or 7.7) have bad memory chips inside. The sock ICS kernel include a flag something like EMMC_CAP_ERASE, bad chips will lock or burnt during format (wipe). Androguide and I were also the victims of this bug. I was lucky. The dealer replace the motherboard for me within warranty period.

This time the warranty period was expired...

am I will be safe come from cm9 ?

---------- Post added at 06:41 PM ---------- Previous post was at 06:29 PM ----------

I have a question
which rom is better for p6800 [PA2.55 or PA3] ?

 

[sbalu]

There are many posts on this subject.

In short:
Some of the Samsung devices (including or 7.7) have bad memory chips inside. The sock ICS kernel include a flag something like EMMC_CAP_ERASE, bad chips will lock or burnt during format (wipe). Androguide and I were also the victims of this bug. I was lucky. The dealer replace the motherboard for me within warranty period.

This time the warranty period was expired...

Than is this the right method to avoid brick: "IF COMING FROM STOCK : Do NOT wipe anything, Flash the this rom directly, reboot recovery, then wipe data (factory reset), cache and dalvik, and then Re-Flash this Rom again.This will get you safe from brick."?First time when I flashed to PA I done so, but after that I forgot about it.Fortunately there was no problem so far.Only sometimes (fortunately rarely)PA unknown way go to bootloop when restart it and than only way to get rid of it, to start from stock rom for me.When in bootloop it does not do factory reset even.Thats why I have to flash back to ICS stock to do a factory reset and after that I can do it from the beginning.And what about kernel changes you mentioned?
I wish to avoid motherboard replacement this time for your tab!I curious about it, report please!

 

[daniel_hk]

ok what about google apps ? will I need them?

---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------



am I will be safe come from cm9 ?

---------- Post added at 06:41 PM ---------- Previous post was at 06:29 PM ----------

I have a question
which rom is better for p6800 [PA2.55 or PA3] ?

Yes, you also need gapps to have those basic apps like Play.

The kernel of cm9 has no brick issue. Other custom ICS kernels like EzyICS & Dedrak's are also OK. With them, you can factory reset and flash rom/gapps directly

The easier way is download the AROMA version which has gapps included. You don't have to download it separately.

Goodluck !

 

[daniel_hk]

Than is this the right method to avoid brick: "IF COMING FROM STOCK : Do NOT wipe anything, Flash the this rom directly, reboot recovery, then wipe data (factory reset), cache and dalvik, and then Re-Flash this Rom again.This will get you safe from brick."?First time when I flashed to PA I done so, but after that I forgot about it.Fortunately there was no problem so far.Only sometimes (fortunately rarely)PA unknown way go to bootloop when restart it and than only way to get rid of it, to start from stock rom for me.When in bootloop it does not do factory reset even.Thats why I have to flash back to ICS stock to do a factory reset and after that I can do it from the beginning.And what about kernel changes you mentioned?
I wish to avoid motherboard replacement this time for your tab!I curious about it, report please!

The first step is to replace the faulty stock ICS kernel.

If you are not in stock ICS or you have already installed a custom kernel, you don't have to flash twice.

I don't know which stock ICS is good or bad. Just don't want to risk.

Factory reset usually wipe /data & /cache
PA or CM rom will write to /system & /boot

stock rom will write to /modem & other partitions too.
standard stock rom is in .tar.md5 format. and each partition is an image which will replace the whole partitions.

if you are in boot loop and can't be fixed by factory reset. There may be something wrong with other partiition(s). By installing stock rom will probably reset it.

As I mentioned before, pa & cm (and most of other custom roms) only touch /system & /boot. When to do factory reset, wiping caches doesn't matter. You may also redo it after rom boot and no need to re-flash rom/gapps.

Although this is not a good pratice, I sometime don't do factory reset when flash new rom. If something goes wrong, I can redo it. When I go from CM10.1 to PA2.99, I didn't do a factory reset. Found out that everything is preserved.

If you don't know what you are doing, play by the book is always the secure way.

A backup in recovery is a MUST if you flash alot.

 

[carlo67]

Yes, you also need gapps to have those basic apps like Play.

The kernel of cm9 has no brick issue. Other custom ICS kernels like EzyICS & Dedrak's are also OK. With them, you can factory reset and flash rom/gapps directly

The easier way is download the AROMA version which has gapps included. You don't have to download it separately.

Goodluck !

thanks , so the p6800AROMA: http://d-h.st/BfR is correct one?

 

[sbalu]

The first step is to replace the faulty stock ICS kernel.

If you are not in stock ICS or you have already installed a custom kernel, you don't have to flash twice.

I don't know which stock ICS is good or bad. Just don't want to risk.

Factory reset usually wipe /data & /cache
PA or CM rom will write to /system & /boot

stock rom will write to /modem & other partitions too.
standard stock rom is in .tar.md5 format. and each partition is an image which will replace the whole partitions.

if you are in boot loop and can't be fixed with factory reset. There may be something wrong with other partiition(s). By installing stock rom will probably reset it.

As I mentioned before, pa & cm (and most of other custom roms) only touch /system & /boot. When to do factory reset, wiping caches doesn't matter. You may also redo it after rom boot and no need to re-flash rom/gapps.

Although this is not a good pratice, I sometime don't do factory reset when flash new rom. If something goes wrong, I can redo it. When I go from CM10.1 to PA2.99, I didn't do a factory reset. Found out that everything is preserved.

If you don't know what you are doing, play by the book is always the secure way.

A backup in recovery is a MUST if you flash alot.

Where can we find birck safe ICS kernel?My stock ICS is P6810XXLPM_P6810OXXLP1_AUT.zip, that I use to flash.Its from samfirmware.com.May be its kernel is safe, because there was no problem with it, so far.I am an average user, thats why I try to keep what it is in written.Whether what cause bootloops in PA roms?I made TWRP backup, other method was not sucessfully as we discussed it before.I just hope it will work for restore when I need it.
It is worrisome that even such an expert like you can make brick.Sure accidents everytime happen.Do you know already what was led to brick for your tab?