yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mroscar:
Thanks guys, definitely at&t bootloaders.

thanks for the suggestion, unfortunately that didn't fix the problem. I wish it'd been that easy though:)
[Captivate Android Development] Doobysnacks:
Is the battery the only thing that can be changed through the kitchen? Or can I use all the available mods?
[Captivate Android Development] sjc807:
Flashing now. I've been a fan of Apex since 5.3 and I'm really looking forward to this rom. Just wondering, what kernel do you recommend that has good performance and good battery life?
[Captivate Android Development] mrhaley30705:
Only one available, boog's.
[Captivate Android Development] sjc807:
Alright and thanks for the quick reply :).
[Captivate Android Development] watsa:
you can use whatever mod is present in it
[Captivate Android Development] Ptrout:
Am I retarded ? What am I missing

Having trouble even booting into rom.

DL'ed install package

DL mode, flash ODIN ATT bootloader (says 2.3.3)

Then flash boog.tar

Clockwork (sometimes it shows as 3.xxx and installs Pinnacle....boot loops

or

and sometimes as 4.xxxx)

it cant see the ext SD.

Been at it for 4 hours

any help is much appriciated
[Captivate Android Development] watsa:
1. Calm down :)

2. Once you have at&t bootloaders, flash kernel which is present in pinnacle flasher kit. That kernel is Xcal's

3. Are you coming from stock KH3?
[Captivate Android Development] mattern1974:
Actually there might be a customized version of the boog kernel used for Fusion V.
[Captivate Android Development] Ptrout:
No I was going from APEX 9.2 withTalon Kernel.

I can flash the att bootloader with ODIN, on boot it shows ATT logo

tried both "boog.tar" and included "I9000 re-oriented vG2.1_no_voo"

Both boots to CWM 4.0.1.5 with these of errors...

E:can't mount /cache/recovery/log

E:can't open /cache/recovery/log

E:can't mount /cache/recovery/last log

E:can't open /cache/recovery/last log

Thank you for helping me out
[Captivate Android Development] watsa:
If you were on Apex you already had CWM recovery. You just had to convert to RFS (disable voodoo lagfix) and then flash pinnacle. Did u disable voodoo? Now try flashing talon from ODIN again, and from CWM --> voodoo --> disable it... then flash pinnacle
[Captivate Android Development] Ptrout:
Oh i was told since I was on APEX and it wasnt an "ATT boot loader" I had to flash ATT bootloader first.....

I didn't undo lagfix, so its probably still in ext4, i thought flashing botoloaders, would have wiped the phone clean.

Now its just stuck in bootloop, and somewhat broken CWM, is there any way out ?

Again thanks so much
[Captivate Android Development] watsa:
yep you needed AT&T BL but you didnt need a custom kernel flash. Anyways thats what I am saying flash Talon again from CWM --> Reboot into recovery --> Try disabling lagfix(this is mentioned in OP) --> Once lagfix is disabled flash pinnacle again...

If all this fails then I am afraid you may have to start from stock KH3 --> Flash a custom kernel to get CWM --> Flash Pinnacle
[Captivate Android Development] Ptrout:
Ok thank you, since CWM is shot, (it doesnt even show option to disable lagfix.)

I can still access DL mode, so I can do stock kernel and rom ?

Thanks, hopefully ill have working Pinnacle by end of the night :)
[Captivate Android Development] watsa:
Open ODIN present in pinnacle flasher inside kernel folder. Put Talon.tar in PDA, connect your phone in download mode and flash kernel... This should give you voodoo options back in recovery and then you can try disabling lagfix... then you can try flashing pinnacle... If this fails then yes stock KH3, then boog' latest kernel (or XCal no voodoo) to get CWM and then pinnacle
[Captivate Android Development] oriveradel:
Hey watsa.. I got home today and did a full ROM install, odin the new Boogs kernel and I got rid of the reboots.. will keep reporting on that..
[Captivate Android Development] Ptrout:
Is the "I9000_reoriented_vG.2.1_novoo" in the bootloader package on page 1, the talon.tar you are refering to ? if not link ?

You are the best
[Captivate Android Development] watsa:
No thats XCal and its a non voodoo kernel. Talon.tar can be found in OP of talon
[Captivate Android Development] eep2378:
Flashed boogs latest kernel a little while ago, so far so good. Will report any issues:)
[Captivate Android Development] blacura:
Rom is great but when i get a call screen stays black and will not come out of lock mode. when it finally does i missed the call. I tried going through the thread but i did not see anything helpful.

and the phone restarts randomly for no reason or when i try to do any task that may be too hard for it
[Captivate Android Development] Johnsondr80:
Yup. Its got a purple "Fusion" recovery.

Perr-tee.

sign up for dropbox using this link to get 250mb free and help fusion at the same time.

http://db.tt/cCn3zrY

presented by Xdapremium app
[Captivate Android Development] apparition:
for issue#1, wave your hand in front of the proximity sensor or press the power button to turn on the screen.

#2, i had that. i had to exchange my phone with my cell provider.
[Captivate Android Development] Hunt3r.j2:
I managed to somehow get it to "reboot in recovery" via Captivate AIO's .bat file for rebooting in recovery, but now it's just plain stuck at the Samsung Galaxy S screen.

I'll try Boog's kernel to see how things go.

EDIT: Boog's kernel got me into Recovery, can I still flash the ROM and be in good shape?
[Captivate Android Development] watsa:
So u have flashed the rom?
[Captivate Android Development] mrhaley30705:
May be easier for you to start over from one of the stock roms.
[Captivate Android Development] Hunt3r.j2:
Right now I'm sitting in recovery via Boog's ODIN flashable kernel, can I still flash the ROM?

I was on JF6, just flashed the Galaxy S international kernel that wouldn't get into CWM, but I flashed Boog's updated Odin kernel w/ CWM and managed to get into recovery straight away. Do I start over or not?
[Captivate Android Development] watsa:
As long as u see recovery the kernel doesnt matter
[Captivate Android Development] mrhaley30705:
@watsa

Any way to oc (thinking Tegrak)?
[Captivate Android Development] watsa:
Yea only tegrak since it allows OCing stock kernels
[Captivate Android Development] xpakage:
Make sure you hold the volume rocker (both up and down vol) and the power button. Release all when you see anything on the screen. It should be the AT&T World Screen. Then it will boot into recovery. With Froyo bootloaders you had to hold keys until you were in recovery but not GB bootloaders.
[Captivate Android Development] mrhaley30705:
Tegrak works perfectly for me. All I want is 1200mhz, and I don't UV.
[Captivate Android Development] xpakage:
That is not a very good reason not to try this. If you think it will improve speed, this ROM is fast now.
[Captivate Android Development] xpakage:
GPS

I have not tried the GPS in a vehicle yet, but here is GPS Test from the back yard.
[Captivate Android Development] watsa:
I was waiting for this. so what do u think my "fix" is included or not?
[Captivate Android Development] shopealope:
hmmm... I guess I'll give it a shot then and see how it goes. I'm currently on apex 9.2

Sent from my Captivate :D
[Captivate Android Development] Danielk425:
Ok noob thing to say probably, but, I am very appreciative of all your hard work Watsa! Your threads are awesome and so is your work i'm in love with apex 9.2 and I mean in love "boing yoing yoing yoing"lol. I gotta try this now though. I've been on the captivate for what two years now and I like everyone else waited impatiently for updates from att, samsung, and then I waited some more. wait no F-ING more people Watsa is shredding this crap up! Thanks a million! A dedicated noob.
[Captivate Android Development] watsa:
I keep switching between pinnacle and apex. no need to flash any bootloaders etc. Just ensure that lagfix is disabled while flashing pinnacle from apex
[Captivate Android Development] shopealope:
**** yes. Couldn't have said it better.

Sent from my Captivate :D
[Captivate Android Development] shopealope:
Gotcha. I'll let you know how it goes, downloading right now.

Sent from my Captivate :D
[Captivate Android Development] xpakage:
Well, it locked on to 10 sats with 15 ft accuracy, like ApeX. BUT only one was going over 40 (would not stay) and ApeX for me would have 3 or 4 go over 40 and stay there.

So I am going to say definitely they are included, I think, maybe :D
[Captivate Android Development] watsa:
lol not included. and last time you said no when all files were same :p:p:p
[Captivate Android Development] smully1:
Any batt % mod?
[Captivate Android Development] blacura:
The proximity sensor is on the top left right? it basically is the light sensor also right?..

#2 i am going to really hope i can get the new galaxy s II
[Captivate Android Development] killer_raj:
thanx for the re direction...

yes..it was just a lil miscommunication....watsa will sort it out in the next release...

as for now..if anyone can send me the systemui.apk from pinnacle 1.2 then i can modify to solve the problem and upload it back here...coz i m still using 1.1 and dont wanna download the whole rom for just one file...

and watsa if u r readin this..then GTALK....need to talk...
[Captivate Android Development] watsa:
you have an update package for 1.2 you dont need full rom
[Captivate Android Development] RashaMatt:
Yes I changed them first to 7276/supl.google.com, but that made no difference for me... So them I installed H3llstorm's fix, which made all the difference :)

____________________________________________________________

AT&T Captivate SGS I897, Pinnacle 1.2 KH3
[Captivate Android Development] watsa:
ok back on pinnacle after a day on JVS :rolleyes:
[Captivate Android Development] mroscar:
thanks so far for the help guys. any other ideas for my problem? Been searching and haven't found anything that has worked
[Captivate Android Development] yobbei:
How do you like jvs? Same old same old or has potential?
[Captivate Android Development] diabolik711:
Status Bar colors

right now only battery icon is green, signal strength and wifi are white. actually it toggles between green and greyish is there a fix?
[Captivate Android Development] watsa:
It is supposed to be that way. They turn green when connected to google servers, else they are white
[Captivate Android Development] killer_raj:
simple explaination..to all users again ....when u r connected to google sever.then ur wifi icon and signal icon will turn green....but in the case of pinnacle if sometime ur network signal is changin to gray from green(indifferent to wifi or mobile data) even when u r connected to google server..then its a small glitch..which i already sloved...

just download the file copy it in system/app folder using root explorer and viola...ur problem will be solved...

and dont worry in pinnachle 2.0.. u will not face the problem regardin that..this is already included..

the file which i attached earlier was for 1.1 or 1.1.1,,,,but if u guys use that..then u will loose 9 toggles and other mods..which watsa added in 1.2...

thats why made new one..specially for 1.2....
[Captivate Android Development] killer_raj:
OMG!!!!!

u just started the 100th page of pinnacle thread...and u just started this thread on 4th september...

congrats!!!!

and congrats for reachin 1000th page in apex thread....(day before yeterday)

:cool::cool::cool::cool:
[Captivate Android Development] Boldizzle:
Wow, my phone really hated this patched UI. Phone restarts all the time now... :(
[Captivate Android Development] dalewest:
Originally Posted by 96dogpound

With the update to 1.2 I've lost Noise Suppression. It it because of the different phone.apk and will it return in future updates?

​

I noticed that the Call End Tone in the Call Status Tones settings section came back in 1.2, which I like since I get dropped calls as I cross dead zones. Assuming that it came back because of the JVR phone.apk, does that also mean that the Audience chip is not being used in 1.2?

FWIW, if I had to choose one over the other, I'd choose Audience support, since that is the only reason I stick with Cappy ROMs.

Just my 2¢. :D

P.S. I've had no issues on this ROM. None. Nada. Kind of shocking, actually... but in a good way. Thanks Watsa!
[Captivate Android Development] watsa:
No audience support should still be there, just that because of my stupidity for fixing phone FC you cannot see it :( Wait for 1.3
[Captivate Android Development] watsa:
works fine for me :confused:
[Captivate Android Development] Ruddy64:
Yes, same here. Works fine.
[Captivate Android Development] dan_maran:
Random sleep death after plugging head phones. Will see if happens again.
[Captivate Android Development] xpakage:
What do you mean by random sleep death? You sleep like the dead with headphones in? :p
[Captivate Android Development] dalewest:
To those having stability issues

Not trolling at all... just hoping to help.... Have you followed watsa's instructions in the OP?

Installation Instructions: You need to be on AT&T bootloaders, CWM 3+ and RFS before flashing this. If you are on Ext4(lagfix enabled) then disable it first then flash from CWM

For people who are not on AT&T GB bootloaders:

1. Flash back to JF6

2. Follow instructions in readme file from http://www.mediafire.com/?tx56ypyw8wx4c8n

​

Your phone should not be plugged into a PC while flashing, just in case. Might want to avoid being plugged into a charger as well while flashing.

Also, if you restore apps from Titanium Backup, do you also restore data? You might try to only restore apps and not data (if possible/practical). You also might use TiBu's Move feature to make sure all of your apps are installed in internal memory instead of the SD card.

And never use TiBu restore system data.

FWIW, I've had no issues whatsoever on this ROM.
[Captivate Android Development] Gromlakh:
My quickie review

Installed Pinnacle 1.2 on Sunday, coming over from Cognition 5 V2. My quick 'n dirty observations.

GPS:

I can get a 10m accuracy lock from multiple satellites in less than 10 seconds from home. Work...not so much, but I'm also buried deep within a government building in an office with no windows. Something tells me the failure to lock at work isn't b/c of Pinnacle. :D

Stability:

Zero random crashes/reboots so far. The only force close I've had was due to a faulty TiBu restore of Google Reader. Uninstalling/reinstalling from the Market fixed the problem.

Speed:

I don't do benchmarks, so I'm going more on the highly scientifically accurate "feel." Cog5 has ext4 support, Pinnacle doesn't. Pinnacle feels snappier than stock KH3, but not quite as snappy as Cog5. The slight speed difference b/w Cog5 and Pinnacle isn't enough to matter much to me, but ext4 support would be awesome.

Battery:

I've been on battery for a day and a half without charging at all. That includes:

- Wifi or 3g on the whole time

- Several GPS tests

- 2-3 hours of playing music

- Several games

- Market downloads

- 4 voice calls (total of about 45 minutes)

- Hours and hours of checking email, Facebook, XDA, etc.

I'm still sitting at 30% charge right now. ;)

LUV!
[Captivate Android Development] ctrclckws:
I have also decided to move from Cognition 5V2. Still setting up so no reports on usage.

Initial install was only slightly painful. (getting into download/recovery is sometimes tricky on my phone)

Installed Stock KH3 no bootloaders with Odin.

Completed normal boot

Installed Boog Kernel with CWM

Completed normal boot.

Copied Pinnacle 1.2 to Phone

Rebooted recovery, got CWM (tricky from stock, with my phone)

Wiped data/cache/battery stats.

Applied Pinnacle Zip with CWM

Rebooted.

Currently downloading Titanium Backup.

Later will try to change to the JazzK type battery indicator
[Captivate Android Development] petrichor8:
coming from cog v5, soft brick hell

Damn, I wanted so badly to try this rom out, here's the saga that was my night.

I'm coming from Cognition 5 v2, trying to go to pinnacle, and while I love the cog5 rom, i can't leave well enough alone. Anyone who has any advice, suggestions, "oh crap, you can't do that", please chime in!

I backed most everything up, then sat down to the football game, and my own personal hell commenced.

I 1-click odin back to uckf1 stock, no problems, to get back to RFS. I then tried to figure out the best way to get CWM on the phone, so I could flash pinnacle. My approach was to attempt to use the fugu root method, and then flash the cog5 kernel (thus getting cwm), then use that to flash pinnacle.

I flashed the fugu root, when the odin failed, and I got the dreaded phone-!-pc, which I've never gotten whilst flashing any one of a several roms over the last year or so. I tried everything to get the phone back, battery pulls, usb jigs, throwing it :D, but nothing worked. I finally stepped away, then went back & just plugged it back into the pc & reclicked odin out of desperation (after an hour wasted with searching forums), and it flashed the fugu root! Alright, I'm back in business...or so I thought. The kernel flash did the same thing to me, but I finally got it all installed, and used cwm to flash pinnacle.

Boy, does it look good, and smooooooth! My issue, NOTHING would download/install from the market. I mean nothing. I tried clearing market data, fixing permission using cwm, reflashing the entire process, nothing worked.

I noticed that in cwm, that it couldn't read e:/cache, and the stock flash could download/install from market, so it's something that odin was doing. I even tried using adb to make /cache read/write, and thought I fixed it, but nothing.

I finally flashed back to stock, used odin to install the cog5 kernel, and reflashed cog5, and I seem to be running a viable install again.

Does anyone have any advice, or comments, or suggestions as to why for the first time ever, odin would fail every time, and seemed to corrupt something the first go-round? This is the first time I've ever had issues flashing, and I'm flashed cognition, perception, andromeda, serendipity, GW, numerous modems/kernels, so I'd like to think I'm not a complete idiot when it comes to some of this, but I'm stumped.

I'm clueless, having spent 6+ hrs flashing/reflashing, reading forums, and trying everything I could think of. Is something in the phone bad? I know I have the GB bootloaders, cause I had to install them earlier (for serendipity 7 or GW, i think).

I would have thought a few 1-click stock flashes would fix anything, but maybe I need to go all the way back to JF6 (and will that even restore the correct bootloaders)?

Thanks in advance!
[Captivate Android Development] nyydynasty:
why didnt you just flash back to stock JF6? flashing from that point is easy-peasy
[Captivate Android Development] Gromlakh:
My journey from Cog5 was as follows:

1. Using Heimdall, flashed back to KH3 stock (not KF1, this may not be 100% important but Pinnacle's base is KH3).

2. Let it reboot once so it got through the "cache/db formatting" process.

3. When that finished and it rebooted again, I did a battery pull, then went back to DL mode.

4. Flashed the Pinnacle starter kernel (that's the re-oriented i9000 one from the original post). This gave me CWM recovery.

5. Battery pull.

6. Reboot into CWM recovery.

7. Flashed Pinnacle 1.2 from CWM, which I had already placed on my SD card.

8. Reboot when complete.

9. Life is good.

Some observations about your path, and possible problems:

1. No need for Fuguroot. Don't bother with it.

2. Cog starter kernel has ext4 support and will format things into ext4 when it boots up the first time. High likelihood this was a part of your problem.

3. Odin probably messed up because it sucks. Use Heimdall.

4. I can't imagine any benefit to flashing all the way back to JF6. If you're reformatting/repartitioning/whatever the entire phone, there's no reason to backtrack all the way to JF6. Use the latest stock firmware, which would be KH3. Then follow the rest of my post and see if that gets you anywhere.
[Captivate Android Development] 96dogpound:
Any reason that the stock Samsung Captivate roms don't include the Voice Dialer app? I kind of miss it having come from Apex to Pinnacle. I can't figure out which library files are associated with the app or if the files from the i9000 rom will even work.
[Captivate Android Development] orb_526:
I came from Cog 5v2 and posted my procedure previously. I can only say that it worked for me. I like to follow whatever instructions as close to the OP as possible. I did not go all the way back to JF6 as I was already on Cog and therefore AT&T boot loaders but I did follow the full "Pinnacle Flasher" steps to be safe. Good Luck!
[Captivate Android Development] petrichor8:
you rock, i'm gonna try it again :D

any way you could hook me up with links to the kh3stock/kernel/heimdal links, so I can use the ones you did so I don't grab the wrong ones?
[Captivate Android Development] Gromlakh:
I'm at work right now, so not at the moment. "Suffer" through Cog5 for the rest of the day and I'll post more detailed instructions tonight. I use Heimdall from the command line, so if you're not used to doing that the instructions may be a bit unusual for you. Personally, I think it's better that way, and I want to wait to post until I get home because I have a text file with my Heimdall flash command saved on my laptop.

Expect something from me around 10pm-ish (it's 11am my time right now).
[Captivate Android Development] dan_maran:
Nope sometimes I wish though.

This morning before I left I copied some music to my external SD, unmounted and left it for 5 minutes picked it up on the way out the door stuck my headphones in pocketed it. On the subway tried to unlock the screen for some tunes but it wouldn't wake up. I unplugged the head phones and tried to wake it up with no change, when I plugged in the head phones again they were in my ear and I could hear the crackle so I know the unit was on just couldn't get a response until a battery pull.
[Captivate Android Development] axeman007:
watsa, I'm on Apex 9.3 and wanna switch over to Pinnacle. Do I have to install bootloaders again? (i'm using the default bootloader for apex)
[Captivate Android Development] tallsilver:
Voice Dialer is in mine! There's no icon in the settings but if you look ad the system apps.............it's there.

Works fine for me. :D
[Captivate Android Development] watsa:
Do you see white AT&T bootscreen? If yes then you are on correct BL, else if you see I9000 screen first after powering on then you are on I9000 BL. You need AT&T BL although people have reported it to be working with I9000 BL too
[Captivate Android Development] 96dogpound:
Thanks. I've seen it in the system app folder in the installation zip but I don't know how to "run" the program or hold to display the icon in the app drawer.
[Captivate Android Development] watsa:
lol somebody really hates my roms. All the ROMs have a tag called 'sucks' :cool:
[Captivate Android Development] RTBee:
It's from all the 'other' ROM developers ;)
[Captivate Android Development] xpakage:
I bet he is using Swype and tried to spell "rocks" :D:D
[Captivate Android Development] ri3tn:
This always happens to me, I've been reflashing and wiping and going back to stock and trying to flash again, but nothing works.
[Captivate Android Development] xpakage:
Not sure how to help. Never heard of that issue before. Can you format the card, put your music back on and see if it does it again?
[Captivate Android Development] bobmanfred:
Just for clarity's sake. How do I go about getting CWM3+?
[Captivate Android Development] watsa:
what is your curent setup?
[Captivate Android Development] mrhaley30705:
So it's a tie then. Pinnacle and apex are both the "worst ROM in the world". :)
[Captivate Android Development] bobmanfred:
Im currently on Continuum 4.1 running Froyo 2.2.1 with Froyo bootloaders.
[Captivate Android Development] Gromlakh:
Now Pinnacle also has a "watsa is my hero" tag, so it's all good. ;)
[Captivate Android Development] dalewest:
Wait, he's my hero too!!!