yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Blaze 4G] taodan:
Just restore from backup. Making sure you wipe before restore.

Sent from my Galaxy S Blaze 4 G
[Samsung Galaxy S Blaze 4G] MrPapito429:
Thanks it worked perfect
[Samsung Galaxy S Blaze 4G] MrPapito429:
Is it confirmed that the kernel will work on provision
[Samsung Galaxy S Blaze 4G] thomas.raines:
You can either restore your backup or install mini miui fresh... miui kernels are funny... they usually require particular and specific mods
[Samsung Galaxy S Blaze 4G] Jserrano56:
I've tried just about every ics/jb rom there is for this phone and they've all worked with lz except MIUI
[Samsung Galaxy S Blaze 4G] MrPapito429:
Is LZ the same as lightning, sorry I'm still learning as I go with this new phone, pardon if I seem like a noob
[Samsung Galaxy S Blaze 4G] Jserrano56:
Yes lz kernel is lightning zap kernel
[Samsung Galaxy S Blaze 4G] MrPapito429:
And for sure it works with provision, sorry for all the questions i just don't want to go through another restore
[Samsung Galaxy S Blaze 4G] Jserrano56:
It did for me
[Samsung Galaxy S Blaze 4G] HectorRDZ:
I flashed the kernel and my phone ended up in a boot loop

. What do I do?

Sent from my SAMSUNG-SGH-T769 running CyanogenMod 10 ;D
[Samsung Galaxy S Blaze 4G] goingcrazy614:
Re-flash old ROM. Wipe everything and you should be good to go.
[Samsung Galaxy S Blaze 4G] HectorRDZ:
Reflash cm10?

Sent from my SAMSUNG-SGH-T769 running CyanogenMod 10 ;D
[Samsung Galaxy S Blaze 4G] Jserrano56:
Which ROM?
[Samsung Galaxy S Blaze 4G] HectorRDZ:
Cyanogenmod 10

Sent from my SAMSUNG-SGH-T769 running CyanogenMod 10 ;D
[Samsung Galaxy S Blaze 4G] Jserrano56:
Wow didn't read your signature... Umm I haven't tried lightning zap kernel on CyanogenMod 10...Maybe someone else could help you.
[Samsung Galaxy S Blaze 4G] HectorRDZ:
When i flashed it everythig was going well and then a screen saying enjoy the lighting zap kernel by thomas.raines and then the lightning appeared and then it rebooted again and again

Sent from my SAMSUNG-SGH-T769 running CyanogenMod 10 ;D
[Samsung Galaxy S Blaze 4G] Jserrano56:
Have you tried wiping cache and dalvik cache and then rebooting or maybe re-flashing the kernel
[Samsung Galaxy S Blaze 4G] daboross:
I seem to have no /sys/devices/system/cpu/cpufreq/ondemand/ folder, only a /sys/devices/system/cpu/cpufreq/Lionheart/ folder? The script gives me an error that it doesn't exist and I checked it and the ondemand doesn't exist.
[Samsung Galaxy S Blaze 4G] thomas.raines:
That's because Lionheart is set as the default governor. If you want ondemand, you need to set it as the governor, then you can make changes/adjustments to that particular governor.
[Samsung Galaxy S Blaze 4G] njstein:
Hey Thomas, I realize you called EOL on this, but wondering is you've put any thought to adding pegasusq governor in your bad@ss kernel? I've read that it's designed specifically for dual core. Just curious is all.

Love this kernel by the way, makes my Paranoid Blaze fly!

Sent from a Paranoid Blaze
[Samsung Galaxy S Blaze 4G] goingcrazy614:
Voltage Control makes it easy for us dumb dumbs. Lol
[Samsung Galaxy S Blaze 4G] Beast6875:
Umm noob question... What's a governor and please no sarcastic answers please.

Sent From My Samsung Galaxy S Blaze 4G Running CM 10.
[Samsung Galaxy S Blaze 4G] thomas.raines:
Think of it like this, your phone is your car, the cpu is the engine, the governor is the accelerator. So if your cpu needs more power, the governor opens up and gives more power to the cpu. The when you don't need the power, the governor lightens up and let's the cpu wind down. The governor also regulated how fast the cpu ramps up and ramps down...
[Samsung Galaxy S Blaze 4G] njstein:
Here's a link to a thread that goes over different governors and schedulers. Great information!

http://xdaforums.com/showthread.php?t=2222345

Sent from a Paranoid Blaze
[Samsung Galaxy S Blaze 4G] LiveFaster:
Is there still an issue with alarm clock? Should I be worried and set another alarm clock?

Sent from my SAMSUNG-SGH-T769
[Samsung Galaxy S Blaze 4G] taodan:
No issue, alarm clock works fine.

Sent from my Galaxy S Blaze 4 G
[Samsung Galaxy S Blaze 4G] HectorRDZ:
Yes I have and it still goes in a boot loop

Sent from my SAMSUNG-SGH-T769 running CyanogenMod 10 ;D
[Samsung Galaxy S Blaze 4G] ktempleton:
Try not wiping the cashe after u run the ROM on a regular kernel
[Samsung Galaxy S Blaze 4G] Jserrano56:
I'm running CM 10 RIGHT NOW with LZ...
[Samsung Galaxy S Blaze 4G] HectorRDZ:
Then what am I doing wrong?

Sent from my SAMSUNG-SGH-T769 running CyanogenMod 10 ;D
[Samsung Galaxy S Blaze 4G] Jserrano56:
Why not try a different rom?
[Samsung Galaxy S Blaze 4G] HectorRDZ:
What other roms are out the? Besides paranoid

Sent from my SAMSUNG-SGH-T769 running CyanogenMod 10 ;D
[Samsung Galaxy S Blaze 4G] njstein:
AOKP, Liquidsmooth, Provision, and a few others. Check Development, if it says ROM in front, give it a go! Personally, Paranoid is my favorite.

Sent from a Paranoid Blaze
[Samsung Galaxy S Blaze 4G] thomas.raines:
Mine too...who woulda thunk it? Lol
[Samsung Galaxy S Blaze 4G] itsLYNDZ:
Its probably not something youre doing wrong. This kernel doesnt work for some people.
[Samsung Galaxy S Blaze 4G] Jserrano56:
Which CyanogenMod 10 are you running? I'm running the nightly's from 6/30/2013
[Samsung Galaxy S Blaze 4G] HectorRDZ:
This is what I'm running

Sent from my SAMSUNG-SGH-T769 running CyanogenMod 10 ;D
[Samsung Galaxy S Blaze 4G] xWolf13:
Your running the "stable" version. Nightlys run better than stable. Plus, its not really stable.
[Samsung Galaxy S Blaze 4G] HectorRDZ:
So I need to flash a nightly and then maybe the kernel will work for me?
[Samsung Galaxy S Blaze 4G] xWolf13:
It should be able to work. Im using the latest nightly with LZ and it works..
[Samsung Galaxy S Blaze 4G] HectorRDZ:
I just checked the cm website and there is a new nightly from 7/21/2013 should I get that one?
[Samsung Galaxy S Blaze 4G] xWolf13:
Get the latest one. If that is the latest one. Get it.
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
So, I downloaded the zip (3.7) everything went fine, did a backup using CWM (REALLY glad I did), flashed kernel ...

BOOT 1:

1. Samsung Logo

2. LZ Logo

3. Boot animation

4. "Android is Upgrading"

- it upgrades all the apps, says starting apps the freezes, reboots

BOOT 2:

1. Samsung Logo

2. LZ Logo

3. Boot animation

4. It boots to the lockscreen, then after like 10 seconds it freezes, then reboots

BOOT 3:

1. Samsung Logo

2. LZ Logo

3. Boot animation, freezes, reboots

Then it's just a constant boot loop, I wiped Cache and Dalvik Cache, rebooted, nothing. I reflashed, nothing. I finally just gave up and restored my backup.

I'm running Cyanogenmod 10 Nightlies (AUG42013)

Am I doing something wrong?
[Samsung Galaxy S Blaze 4G] jparnell8839:
Try running a nightly from August? Lol jk jk. Seriously though, if you're freezing during boot, a logcat would help.

On your next attempt, try this:

1. Nandroid

2. Wipe cache, data, dalvik

3. Flash LZ

4. See if the freezing still occurs. If it does, problem with either the download, the kernel itself, or (very unlikely but possible) hardware issue. If it doesn't, restore nandroid, wipe cache and dalvik, flash LZ, and see if the freezing still happens. If it does, reboot and post a logcat
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
Oh my goodness, that was supposed to be AUG42013, I'm so stupid lolol :p

Considering I have no idea what a logcat is it seems I have some homework to do!

I'll try and let you know!

- - E D I T - -

Did all of it still freezing .. I'm thinking it's a bad download ..
[Samsung Galaxy S Blaze 4G] jparnell8839:
To logcat, you must have ADB on your PC. Connect your phone to your pc with the USB cable. Go to the directory ADB is located in Terminal or Command Prompt. Reflash LV on your phone. DO NOT REBOOT YET. Run this command:

adb devices

If it shows your device is there, run this command:

adb logcat > logcat.log

Then on your phone, reboot it. It'll start pulling the logcat once the ADB daemon on your phone is started, hopefully before it crashes
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
Okay, I followed you all the way until you said don't reboot, after one flashes LZ it reboots automatically . . So what should I do?

Secondly, if my computer doesn't have ADB I have to download Android SDK or something like that right?
[Samsung Galaxy S Blaze 4G] Romman0:
You could download SDK, or just use this minimal adb tool.

http://xdaforums.com/showthread.php?p=42407269
[Samsung Galaxy S Blaze 4G] jparnell8839:
Eh, just pull battery, restart the logcat, put the battery back in and boot as normal.

Something i forgot to mention, when you start the logcat, ADB will say "waiting for device" or something along those lines. That message won't disappear once the phone connects to the PC on boot, just trust that it is indeed logcatting
[Samsung Galaxy S Blaze 4G] thomas.raines:
you'll have to edit the updater-script in the zip...
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
To stop it from automatically rebooting?.
[Samsung Galaxy S Blaze 4G] thomas.raines:
Yes...
[Samsung Galaxy S Blaze 4G] crossking:
This is a great kernal, thanks for all your work. I just had a question. I want to use directinject with this kernal and both seem to have a "90userinit" file in the init.d folder. Do I keep both or just one? Thanks.
[Samsung Galaxy S Blaze 4G] thomas.raines:
Just one... they are the same file...
[Samsung Galaxy S Blaze 4G] Nirvanagar:
Hmmm,

I saw that someone else had an issue with this latest version, 3.7. I'm having issues as well. This is what I did and what I got:

1) Backup

2) Wipe Cache 3 times

3) Wipe Delvik Cache 3 times

4) Install kernel file from SD card

5) The phone restarts itself, then the LZ logo pops up. Then the screen goes completely blank. Boot animation never comes up

I'll try and get a log soon, but just thought I'd post this in case these symptoms might be familiar.
[Samsung Galaxy S Blaze 4G] RonnieTheBear:
I'm having just about the exact same problem as FroBread, first time flashing install hung at "starting apps", retried after wiping dalvik & cache & data, was able to get into system for a couple of minutes before it crashed again, and now i'm stuck in a boot loop where sometimes it crashes on the loading screen lightning animation, sometimes at the lock screen. Will try and take a log cat tonight, but i'm not sure how much luck i'll have if I can't get into the settings to enable usb debugging.

EDIT: I wiped data back to stock again and tried to reflash. Now it's freezing at the google account setup page.
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
I feel so popular! Lol, I'm going to tell you guys the same thing he told me, logcat or it didn't happen :)

Sent from a Blaze that only knows how to speak the language of: CyanogenMod 10.2.
[Samsung Galaxy S Blaze 4G] RonnieTheBear:
Actually the more I think about it, I might just stick with stock CM10 (just reflashed it and it's working fine). I was only trying out Ligntning Zap as a suggestion made by [MENTION=4145127]thomas.raines[/MENTION] in another thread to solve an issue I was having with my car dock, but that issue is so minor compared to the headaches LZ was giving me this afternoon!

I'm not really an overclocking kind of guy, Whether PC or phone, the results have always been extremely unstable for me. :eek:
[Samsung Galaxy S Blaze 4G] FroBreadCreamJellyPie:
Sorry things didn't work for you :/

Sent from a Blaze that only knows how to speak the language of: CyanogenMod 10.2.
[Samsung Galaxy S Blaze 4G] thomas.raines:
CM-10.2 update... see the changelog
[Samsung Galaxy S Blaze 4G] njstein:
Oh really?! Flashing now, loved the LZ!

---------- Post added at 03:13 PM ---------- Previous post was at 02:24 PM ----------

So, I'm running 4.3 PAC. I downloaded to phone, moved to ext sd card. Recovery, flash zip. It didn't reboot on its own. So I hit reboot. Did not boot. So I went back into recovery, wiped cache and Dalvik, reboot; same, no boot. So I went back to recovery, wiped cache/dalvik, flashed zip, wiped cache/dalvik,reboot. No boot. I'm restoring my nandroid at the moment and unfortunately I don't have a logcat for you (this is my bad, sorry Thomas). But looking at the steps, did I do something completely bonehead?
[Samsung Galaxy S Blaze 4G] thomas.raines:
Apparently there is an issue between LZ kernel and PAC rom. I don't know much about PAC so I need a log. I tested on Beanstalk and had no issues, other than 1 random reboot on Lionheart gov
[Samsung Galaxy S Blaze 4G] njstein:
When I get a little free time, I'll post you one!

Sent from a Blazing PACMAN devouring ALL...
[Samsung Galaxy S Blaze 4G] thomas.raines:
Added Exhilarate download links to 3rd post... Make sure you download and flash the right one!
[Samsung Galaxy S Blaze 4G] goingcrazy614:
I had the same issue so I switched to Beanstalk. Runs great so far.
[Samsung Galaxy S Blaze 4G] tommyboy8125:
Working great so far on cm 10.2 :thumbup:
[Samsung Galaxy S Blaze 4G] tazzbr60:
could someone post a good link for download--I have a galaxy s blaze 4g--the link says the server is down
[Samsung Galaxy S Blaze 4G] thomas.raines:
Goo servers have been going in and out today...just keep trying...
[Samsung Galaxy S Blaze 4G] 7r00t:
So far so good on DU v3.9!

Sent from a Dirty Blazed Unicorn Riding the Lightning Zap via XDA Developers Premium App

---------- Post added at 09:03 PM ---------- Previous post was at 08:59 PM ----------

Can't wait for oc/uv implementation. Great work as always!

Sent from a Dirty Blazed Unicorn Riding the Lightning Zap via XDA Developers Premium App
[Samsung Galaxy S Blaze 4G] njstein:
Alright my man. This is five minutes worth of logcat from my phone. I started with my phone being turned off, then turned phone on. My process was wipe cache, wipe dalvik, flash. Then powered off phone, then got adb going with phone plugged in, turned phone on. Let me know what you think and what you see!

Actually I couldn't post the entire five minutes. I looked and tried to find where it repeated and cut it off there. If you need more let me know! Thanks, Thomas!

This is from my Blaze running the 10/18 nightly of PACMAN ROM.
[Samsung Galaxy S Blaze 4G] thomas.raines:
Looks like surfaceflinger is dying... I'll look into it a little deeper later... 515 am comes early on mondays...lol

I would suggest going back to the last stable build and not a nightly...especially anything after 10/15... we have found some issues with cm code...
[Samsung Galaxy S Blaze 4G] thomas.raines:
On another note:

Update available for Blaze!

Check the changelog... you'll like this one...

Hold tight exhilarate users, we are working on your p_4...
[Samsung Galaxy S Blaze 4G] xCMxkarnage:
I have BLAZE 4g, will Blaze_p4-CM-10.2.zip work with my CM10.2? flashed in recovery?>!?!? pleases respond:
[Samsung Galaxy S Blaze 4G] njstein:
It should flash nicely.

Sent from a Blazing PACMAN devouring ALL...
[Samsung Galaxy S Blaze 4G] xCMxkarnage:
so after i flash it what will happen, i proceesed with a normal boot?
[Samsung Galaxy S Blaze 4G] njstein:
Yep. Knowing Thomas and his work, it'll be butter my man. If you don't like it, just redo the whole process but without the kernel.

Sent from a Blazing PACMAN devouring ALL...

---------- Post added at 10:05 PM ---------- Previous post was at 10:03 PM ----------

That sounds super ominous. When you say issues, do you mean something that could hurt my phone? If so, I'm heading back to Beanstalk!

Sent from a Blazing PACMAN devouring ALL...
[Samsung Galaxy S Blaze 4G] thomas.raines:
No... it's on the dev side...looks like some commits were added to display that cause errors during compiling... looks to me like they should have an ifdef out ifconfig before them because it's with mdpi and or phone doesn't use mdpi...but if ink was able to get past them, Idk what to expect. But it won't break your phone. Either way, try an older version because display and surfaceflinger go hand in hand. I just reverted back to before to commits and compiled with no issues...

**EDIT** So, for you guys running PACROM, I got thru njstein's logcat, thanks btw, and it looks like it's a combination of things causing the bootloop.

/system/lib/libdvm.so
/system/lib/libnativehelper.so
/system/lib/libmedia_jni.so
/system/lib/libc.so

With these libraries failing to load properly, it will cause surfaceflinger to crash and result in a bootloop.

Not exactly sure why they are failing, but my suggestion is to talk to inkslinger and see f he can compile PAC with LZ kernel. There's about a 75% chance that will work. But it results in differences in code. I'm not sure what is different in the code between cm-10.2 and PAC, but it's enough of a difference to cause issues...

@inkslinger420, if you have any input on the code diffs, please let me know and I'll try to incorporate it...
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I'm gonna dig this morning and see what is up...we also have an issue over there with cm shifting display caf around and now all 8660 devices are failing builds..:what: Somcom also told me I could pick slims repo as they still use the same layout but cm is twisting up all kinds of issues with us as well...I need to look deeper into this..with report back..

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----

---------- Post added at 11:04 AM ---------- Previous post was at 10:49 AM ----------

Ok,...Im gonna run a test build with LZ built in..We'll see what happens...Thanks Thomas..
[Samsung Galaxy S Blaze 4G] thomas.raines:
Cm updated the kernel this morning to match display-caf...unfortunately it breaks display... everything is out of focus and colors are funky to say the least... you can use my display-caf on my t769 repo on github... it's updated to just before it got broken

**EDIT**

@inkslinger420, don't forget to add vendor/lz-kernel to your manifest and build...
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I added all that I believe I was supposed to and get 2 minutes in and throws fail..I stepped out so I don't have it in front of me, but I rolled back to stock PAC and am running a test build so I can see if its my repo that got all twisted or not..(and I had the lz-kernel in manifest when I tried it.just FYI):D

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----

---------- Post added at 02:09 PM ---------- Previous post was at 01:34 PM ----------

Ok, I may have borked adding it to manifest...what would be the best way in your opinion..?
[Samsung Galaxy S Blaze 4G] thomas.raines:
add these lines you your manifest

<remote fetch="https://github.com" name="LZkernel" />
<project name="TeamFahQ/vendor_lz-kernel" path="vendor/lz-kernel" remote="LZkernel" revision="cm-10" />
<project name="TeamFahQ/msm8660-common_lz_kernel" path="kernel/samsung/msm8660-common" remote="github" revision="cm-10.2" />
<project name="t769/android_hardware_qcom_display-caf" path="hardware/qcom/display-caf" remote="github" revision="cm-10.2" />
<project name="TeamFahQ/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-10.2" />

Note that you might need to remove android_device_samsung_qcom-common from your mainfest since you are probably on different sources (or just replace the source name, i.e. CyanogenMod, with TeamFahQ. The device_qcom-common already has the call for lz vendor files for building...

I would recommend

Before you sync, delete or rename your current device/samsung/qcom-common and kernel/samsung/msm8660-common files in .repo/projects and in working tree. That way you get a clean sync
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Alright..Thats EXACTLY what I did...Just making sure it was right..resyncing work tree and gonna attempt another build now..
[Samsung Galaxy S Blaze 4G] InkSlinger420:
A little info

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----
[Samsung Galaxy S Blaze 4G] thomas.raines:
There's the problem...lol

Now, what do I have to do to meet there mods is the question at hand... Maybe you building natively will correct this issue???
[Samsung Galaxy S Blaze 4G] InkSlinger420:
I hit a make rule error with the scripts..I guess I didn't drop them in first..so retrying now..glad I could help get the reason for the issues answered for you though..we'll see what the build does..

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----

---------- Post added at 03:23 PM ---------- Previous post was at 03:09 PM ----------

Not trying to jinx, but I have it compiling without error (for now:p)..

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Ahhhh...Christ almighty...:confused: Always fun...:screwy:

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----
[Samsung Galaxy S Blaze 4G] goingcrazy614:
I am running latest Beanstalk with latest LZ (no mods or scripts) and the voice calls is pulling huge battery. Any ideas?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Disregard...got it to copy and almost finished compiling...

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----
[Samsung Galaxy S Blaze 4G] thomas.raines:
Not bad... I was going to talk crap because that's about 7% an hour (roughly), and I'm at 2 hours and still 100%... but you do have screen on and voice calls that's draining your battery... I on the other hand have cell stand by and screen on as my highest battery consumers...

Actually, it looks like the kernel is working out swimmingly... Hope everyone else is enjoying it... don't forget to post your results, hit the thanks button and remember, times are hard for us army folks...lol
[Samsung Galaxy S Blaze 4G] ktempleton:
I577 p3
[Samsung Galaxy S Blaze 4G] ktempleton:
Screen on
[Samsung Galaxy S Blaze 4G] thomas.raines:
Where's that last_kmsg.log at?
[Samsung Galaxy S Blaze 4G] InkSlinger420:
OK.PAC compiled successfully..GONNA LET NJSTEIN TEST BEFORE I DROP IT..:cool:

(Stupid caplock)

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----

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

So Thomas, I had a few errors ( that I got it past all if em) and I saw it inject all your scripts...is there anything else to know or look for if god help me it boots?

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----
[Samsung Galaxy S Blaze 4G] thomas.raines:
Just hope it boots...lol

Thanks a bunch man...
[Samsung Galaxy S Blaze 4G] InkSlinger420:
Will know in 5 minutes..and no problem..fingers crossed...

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----

---------- Post added at 07:19 PM ---------- Previous post was at 07:05 PM ----------

Kinda scared the tester is taking so long to get back to me..:confused:

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----

---------- Post added at 07:40 PM ---------- Previous post was at 07:19 PM ----------

OK..we have boot..issue arises on startup com.android.phone has stopped...said to reboot to recovery,wipe dalvic and cache again and cross fingers...but we do have boot none the less...!!!!!

----sent from a PAC 4.3 infested i577----

----Official PAC Maintainer for i577 ( exhilarate ) and the t769 ( blaze 4g )----
[Samsung Galaxy S Blaze 4G] BlazinDroid5280:
Running great on DU 3.9. No issues on install. TY
[Samsung Galaxy S Blaze 4G] thomas.raines:
That's great! Thanks so much man! Are you going to start using LZ kernel in PAC now?