THIS FIRMWARE IS A TOY. IT HAS MAJOR ISSUES.
eortizr said:
ICS for i777 is not coming any time soon,,, the so called 'devs' are not smart enough to figure it out...
Click to expand...
Click to collapse
(more quotes to come boys and girls!)
Since apparently, if there isn't a crappy bugridden barely usable ICS firmware somewhere in the development forum, development is "stopped" and "dead" - I figured I'd put up something for the little babies with their sense of being entitled to everything in the world a little firmware to suck on so maybe they'll shut up.
So here is Baby Pacifier - A minimally usable (but at least safe to flash) ICS firmware based from the I9100 XXLPH leak, using most (but not all of) my Sh1tROM tutorial guide to deodex, debloat, and partially Hellraise (CSC only - no modem/audio/kernel)
It contains Chainfire's CF-root initramfs-repacked kernel, so includes functional CWM. Note that internal and external SD cards are swapped compared to normal Samsung CWMs. (This is actually the Android standard going forward and I'll likely change DD soon to reflect this.)
It also includes the softkey workaround akira02rex pointed out in his thread in General (link later...) Note that this workaround is easier said than done, I'll be writing a short guide about my experiences with this later.
http://dev-host.org/HM2 - The usual - Nandroid your current firmware, wipe data in CWM, flash this in CWM.
The softkey hack makes twlauncher look like ass - LauncherPro seems to be nicer in this regard.
HARDWARE TOUCHKEYS DO NOT WORK. CALL AUDIO IS TOTALLY BROKEN IN THE FIRMWARE, AND ONLY PARTIALLY FUNCTIONAL (you need to disable Samsung Noise Reduction on every call) WITH THE ATTACHED KERNEL. THIS WILL NOT CHANGE BEFORE I9100 ICS KERNEL SOURCE IS RELEASED. DON'T ASK FOR FIXES - THESE CAN'T BE FIXED BEFORE THEN.
Data seems to work however with any I777 Gingerbread modem (I'm using UCKH7). This does not flash a new modem.
For some reason, since implementing the CSC hack, no ringtones or notification tones show up for selection on first boot. They do afterwards.
I'll add a few more details later (probably tonight)
When you're done playing, enter CWM and Nandroid back to a usable firmware.
I've attached a hex-edited variant of CF-Root that fixes some of the call audio issues (I can hear my voicemail now, and mic works if you disable Samsung Noise Reduction during a call). However expect some audio issues to remain. See http://forum.xda-developers.com/showpost.php?p=22889718&postcount=26 for more details on how this got haxxed.
I reuploaded the kernel with a fixed updater-script so that it flashes properly now.
For a high-level overview of the hexedit hack - see http://forum.xda-developers.com/showpost.php?p=23005998&postcount=204 - You'll need a Linux box and the ability to read and understand a bash shell script.
First! I might as well play with it for a little.
Sent from my SGH-I777 using xda premium
But entropy when will the kernel source drop? Im just kidding. Gonna flash for ****s and giggles.
Lol love the name...
sent from interspace on my hacked telly...
Entropy I knew you were a great dev. But your patience and dedication make u a good person. Thanks for all u do. May try this when I get home.
Sent from my GT-I9100 using Tapatalk
My touchkeys and audio don't work!
J/K, thanks for this might give it a try just for giggles later on.
I like playthings.
LOL @ Baby Pacifier name.
Been using this for almost 2 hours. It's pretty functional minus the things that are not functioning .
Not sure if I'm digging the touchwiz integration, but this is obviously not polished.
Surprised this thread doesn't have 300 replies and that the dev host servers haven't crashed yet.
Thanks for sharing.
Entropy512 said:
THIS FIRMWARE IS A TOY. IT IS NOT USABLE AS ANYTHING OTHER THAN A PLAYTHING.
(more quotes to come boys and girls!)
Since apparently, if there isn't a crappy bugridden barely usable ICS firmware somewhere in the development forum, development is "stopped" and "dead" - I figured I'd put up something for the little babies with their sense of being entitled to everything in the world a little firmware to suck on so maybe they'll shut up.
So here is Baby Pacifier - A minimally usable (but at least safe to flash) ICS firmware based from the I9100 XXLPH leak, using most (but not all of) my Sh1tROM tutorial guide to deodex, debloat, and partially Hellraise (CSC only - no modem/audio/kernel)
It contains Chainfire's CF-root initramfs-repacked kernel, so includes functional CWM. Note that internal and external SD cards are swapped compared to normal Samsung CWMs. (This is actually the Android standard going forward and I'll likely change DD soon to reflect this.)
It also includes the softkey workaround akira02rex pointed out in his thread in General (link later...) Note that this workaround is easier said than done, I'll be writing a short guide about my experiences with this later.
http://dev-host.org/HM2 - The usual - Nandroid your current firmware, wipe data in CWM, flash this in CWM.
The softkey hack makes twlauncher look like ass - LauncherPro seems to be nicer in this regard.
CALL AUDIO AND HARDWARE TOUCHKEYS DO NOT WORK. THIS WILL NOT CHANGE BEFORE I9100 ICS KERNEL SOURCE IS RELEASED. DON'T ASK FOR FIXES - THESE CAN'T BE FIXED BEFORE THEN.
Data seems to work however with any I777 Gingerbread modem (I'm using UCKH7). This does not flash a new modem.
For some reason, since implementing the CSC hack, no ringtones or notification tones show up for selection on first boot. They do afterwards.
I'll add a few more details later (probably tonight)
When you're done playing, enter CWM and Nandroid back to a usable firmware.
Click to expand...
Click to collapse
I likey the toys
Galaxy S II
I still hope the whiny babies keep making whiny threads to whine about. I like seeing them get trashed.
Jk. I know it drives you crazy. Thanks for your continued hard work.
Sent from my SGH-I777 using Tapatalk
I LOL'd when i saw that quote in the OP. Haha i so remember that being said- glad somebody hung on to that ridiculous statement
sent from my Galaxy SII
Is the link down?
Sent from my SGH-I777 using Tapatalk
Pure win.
We love you, Entropy.
oh man....this rules.
Haha love the name, gonna play with it tonight when the day is over. I still would love to know why the audio routing is so different between us and the i9100. I wonder if sammy planned this all along.
whoops
I'm late i guess! lol. i can download it but its like 1/2MB or something. can't wait to fiddle with it later when the link is working again! thanks
Hmm, I'll check the link tonight... Including checking the MD5sum against what I uploaded.
As to the call audio - I think AT&T seems to really like using some weird call audio processing chip (Audience) that isn't in international devices - I know that was the case on the I9000 vs Captivate - however I'm not sure if we even have that chip in the I777.
To be honest, I haven't paid too much attention to it. It hasn't been a major issue on Gingerbread.
There is just enough audio-specific stuff in the kernel that is different between I9100 and I777 that I'm not going to mess with it until I've got kernel source.
See https://github.com/Entropy512/linux_kernel_sgh-i777/blob/master/sound/soc/codecs/mc1n2/mc1n2_cfg.h vs https://github.com/Entropy512/linux...master/sound/soc/codecs/mc1n2/mc1n2_cfg_gsm.h
If DIO port 1 is related to call audio (maybe it is maybe it isn't) - then we absolutely need kernel source to even start working call audio.
Which leads me to - there are Gingerbread experiments I can play with.
According to this, which points to this, says the GSII has it.
Good call, I figured we still had that pesky audience chip. I remember on my captivate which I still have whenever we ran a i9000 rom with i9000 modem it would bypass the audience chip. Wish that was possible on the I777. Still can't see any improvements from that chip on either phone. I wish AT&T would keep there paws off the damn devices.
Also Entropy, any good place I can start reading up on kernel development or at least some place to read up about what is being accomplished in those drivers?
Related
I've not seen a specfic thread dedicated to ROMS that people are using that appear to be flawless. I did do a search on here, but honestly, I'm new to Android and don't know exactly what to search for other than maybe CM7.1, UnNamed, and ROMs. of which you get way too many threads to sort through. figured I'd start this and people can add things. I'll keep it updated on this first post with updates as people post them. This may help others who are new find what they need to. If you know of a safe rom, post up. If you also know of a walkthrough of how to install it, post that up as well since other newbs may want help walking through their first flash. Thanks!
considering tomween1 already spent the time to create a thread with all the info you need (here) i think this thread is redundant. just my opinion, though.
nothing is "safe" if you dont know what you're doing or dont do homework, first. On the flip side, most roms are relatively safe if you know what to do. All the info you need to flash, root, whatever ... is usually stickied to the top of the section.
If it isn't from netchip, and you take care to READ all directions and instructions and warnings before flashing - everything here is safe.
(Only thing "unsafe" really is bootloaders - which is why I make sure any bootloader thread has plenty of warnings.)
I think he meant "safe" is the ROM has no error which all the cook ROMs have. Even the Stock ROm sometimes has a bug.
re: Errors
sweetboy02125 said:
I think he meant "safe" is the ROM has no error which all the cook ROMs have. Even the Stock ROm sometimes has a bug.
Click to expand...
Click to collapse
NOTICE:
If anyone wants a custom rom without any bugs or errors please look elsewhere!
(xda is not the right place for you.)
if anyone is looking for:
1) something safe to flash
and
2) doesnt want to read and gain the proper knowledge prior to touching their phone
then they should leave their phone as it is right out of the box. There are a lot of people on this forum that are more than willing to help someone out but dont expect them to do all the work. You need to meet them half way and have some prior knowledge of what you are doing.
I respect this post and would love to see it turn into a rom known bugs thread. For ex unnamed is a battery hog. P8 has Bluetooth issues and cm7 has sub par cam.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
zgr8jakez said:
I respect this post and would love to see it turn into a rom known bugs thread. For ex unnamed is a battery hog. P8 has Bluetooth issues and cm7 has sub par cam.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
The problem is, if everyone posted bugs in this thread, you'd have to sift through pages and pages of posts to see if you have a similar problem. Even then, the problem may not be the rom but a bad flash or incompatibility with a app. This would be so cluttered, you wouldn't be able to get anything out of it. What if there was a bug and the dev fixed it in a update? A newb would read the thread and think there's a issue that hasn't been resolved. Bugs are best left to their dev thread where they can be announced and addressed. If you want to see what rom A has to offer, take the time to READ.
zgr8jakez said:
I respect this post and would love to see it turn into a rom known bugs thread. For ex unnamed is a battery hog. P8 has Bluetooth issues and cm7 has sub par cam.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Hmmm.... these "bugs" look more like opinions or might possibly be user error. For me UnNamed is a battery genius and I probably got over 2 days of use on one charge. I'm using Bluetooth just fine on Serendipity right now. And cam on cm7 works better for some then it might work for you bro.
im on uname rom myself but look to make the change to {ROM} MIUI 1.10.21 {Updated on 10-25-11} cuz i love miui so, unmae is a very good fast rom i just miss miui.
task650 said:
Hmmm.... these "bugs" look more like opinions or might possibly be user error. For me UnNamed is a battery genius and I probably got over 2 days of use on one charge. I'm using Bluetooth just fine on Serendipity right now. And cam on cm7 works better for some then it might work for you bro.
Click to expand...
Click to collapse
My thoughts exactly. (Except I never tried CM7)
Sent from my Galaxy S II (i777)
Yup. I've never had battery problems with gtg's ROM. Yes, S8 is slightly better on battery due to being more aggressively debloated, but it's not THAT much better.
Usually, anyone who encounters severe drain has encountered an app bug.
Slight exception: Any ROM that doesn't include my 10/20 kernel is susceptible to the fuel_alerted wakelock bug. Easy enough to flash my kernel over any ROM that hasn't been updated with the 10/20 kernel.
At this point, any user who claims a ROM is a battery drainer is usually at fault themselves. Especially if they haven't posted debugging info collected as documented in my Known Battery Drainers thread.
Most of the issues people have with roms are user errors.
Sent from my SAMSUNG-SGH-I777 using XDA App
One thing I forgot: The UCKJ2 leak that is distributed as a .exe file is an "Odin One-Click" flash package which will flash crippled bootloaders. I would suggest avoiding it.
re: One-Click
Entropy512 said:
One thing I forgot: The UCKJ2 leak that is distributed as a .exe file is an "Odin One-Click" flash package which will flash crippled bootloaders. I would suggest avoiding it.
Click to expand...
Click to collapse
What I am looking for is a complete stock 4 part odin flash rom like
this below but one which is for the SGS2 i777 phone and not the i9100.
OR an Odin One-Click flash for i777.
PIT select u1_02_20110310_emmc_EXT4.pit
PDA select CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5
PHONE select MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5
CSC select GT-I9100-CSC-MULTI-OXAKI3.tar.md5
So far I could not find a 100% stock package for the i777 here in XDA.
Designgears had a very good odin one-click for the old captivate I used to have.
Either one would be good, one-click or just the complete 4 part odin flash.
Glad I could get the convo going! I'm very conservative when it comes to testing rom's and am a battery nazi as far as processes go. Cm7 is fine with still shots but unless they fixed it lately the fps on it was not perfect. I know I'm alone on the Bluetooth issue with s8 but had just gone from a fresh wipe to clean install
.. there have been allot of mms issues with that rom though..
UnNamed has more bloat so of course it will use more power after I froze the bloat it was where s8 was. The devs are amazing not knocking any at all just putting my 2 cents in. Btw the way I found the easiest way to play around with rom's was to back up in both cwm and titanium, flash one for a week and repeat indefinitely that way you can get the best of all worlds.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
CSC and cache get integrated into the system image on first boot - so you will never see a return-to-stock that includes csc and cache for UCKH7, since the return-to-stock was generated from a dumped phone, and since it's the initial stock firmware, H7 doesn't exist as Odin upgrade leaks anywhere.
Same exact deal as gtg's Ultimate Unbricks for the Infuse - the D5 unbrick (and I think the E3 unbrick too, will check tonight) were created from system dumps, so do not include a separate CSC or Cache file, as those get integrated into the system image on first boot.
Notice: Saurom RCV users, there is a fix so that you can flash other kernels. The problem was caused by an incompatible library being flashed over Saurom's RTL modded library. In the future, my kernels will ship without modified libraries, and a cwm zip containing only the libraries will be offered (for those who need them).
For your pleasure, here is a new kernel for the ATT Galaxy Note. This kernel is forked from Da_G's Overclock kernel, so you are still getting all the features of that excellent piece of code.
For those a bit confused as to what 'Ghost thouch' is, and why it is removed:
Samsung added a bit of code to the touchscreen driver on the non-intl version of the note to detect 'ghost' touch input events, similar to the raindrop detection on the original Motorola Atrix (and others). While a nice idea on paper, this had un-intended consequences when trying to perform multi-touch input that continues longer than around 5 seconds; such as playing some games. It is now disabled in this kernel.
Edit: There also seems to be a pleasant side effect that I hadn't noticed... keyboard input is improved. Makes sense I suppose, since now there isn't this constant check for false touches slowing things down. Let me know if you see this on your device.
Please READ:
1. I have only tested this kernel on the ATT Galaxy Note running stock rom
2. This kernel has no option to turn ghost touch detection on and off (I am considering this for version 0.2)
3. I will likely not fix the issues where more than 6 fingers are not reliably detected.... why do you need that many fingers on the screen??
4. As always, you are flashing something on to your expensive phone and it very well could kill you, burn [more] holes in the ozone layer, intoxicate innocent kittens, etc. (oh, and break your phone). You always flash at your own risk.
5. The only change at the moment over Da_G's 0.2 kernel is the touchscreen stated above. As such, all the other good or bad remains the same.
Have fun, Let me know what you think.
Heard from:
Saurom RC4 -- Works fine
Saurom RC5 -- holoNote kernel is bundled already, but if you want to flash a different kernel you must apply a cwm zip containing a RTL modded lib
TPC V2 -- Works fine
Rogers -- Works fine
Kallsyms version of my Kernel is now up (file ending with suffix 'k'). Please confirm that it is working for you guys that use that feature (I do not).
Per request: Version without su/busybox (and install script) is now up. Please NOTE: this kernel does not remove root, just no longer installs root.
An oversight of mine has resulted in android reporting kernel version unavailable. Apps such as cpuspy report correct kernel name/ version.
https://github.com/hololight/sgh-i717-kernel
When you flashed this was it on top of a custom rom or stock? Just trying to decide if I want to flash on top of saurom.
Flashed on Saurom RC4 and it booted fine. It seems I don't have anymore keyboard problems with this kernel either. I can finally type fast again!
Sent from my SGH-I717R using xda premium
As stated above, I have only tested this on stock att rom. That said, as Da_G's kernel works with Saurom, I can not see how this would cause any problems.
As people confirm it works in 'X' situation, I will update the op.
hololight said:
For your pleasure, here is a new kernel for the ATT Galaxy Note. This kernel is forked from Da_G's Overclock kernel, so you are still getting all the features of that excellent piece of code.
For those a bit confused as to what 'Ghost thouch' is, and why it is removed:
Samsung added a bit of code to the touchscreen driver on the non-intl version of the note to detect 'ghost' touch input events, similar to the raindrop detection on the original Motorola Atrix (and others). While a nice idea on paper, this had un-intended consequences when trying to perform multi-touch input that continues longer than around 5 seconds; such as playing some games. It is now disabled in this kernel.
Please READ:
1. I have only tested this kernel on the ATT Galaxy Note running stock rom
2. This kernel has no option to turn ghost touch detection on and off (I am considering this for version 0.2)
3. I will likely not fix the issues where more than 6 fingers are not reliably detected.... why do you need that many fingers on the screen??
4. As always, you are flashing something on to your expensive phone and it very well could kill you, burn [more] holes in the ozone layer, intoxicate innocent kittens, etc. (oh, and break your phone). You always flash at your own risk.
5. The only change at the moment over Da_G's 0.2 kernel is the touchscreen stated above. As such, all the other good or bad remains the same.
Have fun, Let me know what you think.
Any chance of getting this with the kallsysms function that DA_G implemented in one version of his kernel 0.2? Thanks it would allow us more screen improvement with the touchscreentune app available (which works well to re-calibrate the pens offsets btw)?
Heard from:
Saurom RC4 -- Works fine
https://github.com/hololight/sgh-i717-kernel
Click to expand...
Click to collapse
Please hit THANKS button if I help you, I have very low self esteem, and I crave validation! Sent from my Team EOS ICS Xoom
Quick question. Which of the three versions of Da_G's kernel is this from. I'm using his one with the kalysms (so?)
Sent from my SAMSUNG-SGH-I717 using xda premium
I hope to have a version with kallsyms up later today.
Sent from my SAMSUNG-SGH-I717 using XDA
hololight said:
For your pleasure, here is a new kernel for the ATT Galaxy Note. This kernel is forked from Da_G's Overclock kernel, so you are still getting all the features of that excellent piece of code.
For those a bit confused as to what 'Ghost thouch' is, and why it is removed:
Samsung added a bit of code to the touchscreen driver on the non-intl version of the note to detect 'ghost' touch input events, similar to the raindrop detection on the original Motorola Atrix (and others). While a nice idea on paper, this had un-intended consequences when trying to perform multi-touch input that continues longer than around 5 seconds; such as playing some games. It is now disabled in this kernel.
Please READ:
1. I have only tested this kernel on the ATT Galaxy Note running stock rom
2. This kernel has no option to turn ghost touch detection on and off (I am considering this for version 0.2)
3. I will likely not fix the issues where more than 6 fingers are not reliably detected.... why do you need that many fingers on the screen??
4. As always, you are flashing something on to your expensive phone and it very well could kill you, burn [more] holes in the ozone layer, intoxicate innocent kittens, etc. (oh, and break your phone). You always flash at your own risk.
5. The only change at the moment over Da_G's 0.2 kernel is the touchscreen stated above. As such, all the other good or bad remains the same.
Have fun, Let me know what you think.
Heard from:
Saurom RC4 -- Works fine
Kallsyms comming soon.
https://github.com/hololight/sgh-i717-kernel
Click to expand...
Click to collapse
OMG, yesterday i was trying to analyze why my keyboard is missing keypresses when i type quickly and i came to the conclusion that it must be some sort of an accidental touch algorithm that works in the background!
I'm going to check this out!
Thanks!
Op updated with kallsyms support kernel... enjoy.
gonna flash and report back its nice to see another dev here
What's Kallsyms?
lowspeed said:
What's Kallsyms?
Click to expand...
Click to collapse
Da_G has a build of the kernel with this:
Version 0.2 CWM Zip (with KALLSYMS + KALLSYMS_ALL for debugging)
The original request came from someone who wanted to use an app to help fix the spen issues which required this I believe.
hololight said:
Op updated with kallsyms support kernel... enjoy.
Click to expand...
Click to collapse
Thank you! Amazing!
My phone will eat your Apple!
Not discounting your work here - and this is just my opinion.
It might've been better to work with DaG and get him to integrate this into his kernels. do you plan to re-release every time he makes changes to his kernels?
Can i use this on my rogers galaxy note? Will i loose lte on rogers or nfc? Thanks
Sent from my SGH-I717R using Tapatalk
Hrmm... should ignore it? Yeah... ill ignore it.
Sent from my SAMSUNG-SGH-I717 using XDA
Turilo: only tested on att stock. But as nfc and lte are android and modem respectivly, I would guess you should be fine? Let me know how it goes.
Sent from my SAMSUNG-SGH-I717 using XDA
OK tested it out. I don't think it helped.
hololight said:
Hrmm... should ignore it? Yeah... ill ignore it.
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
I wasn't trying to start anything, it was a serious question though. Are you going to release a new one after DaG does changes to his kernel?
hololight said:
Turilo: only tested on att stock. But as nfc and lte are android and modem respectivly, I would guess you should be fine? Let me know how it goes.
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
Ok so far seems fine on my rogers note but when checking kernel in about phone i get unavailable? Grat work by the way
Sent from my SGH-I717R using Tapatalk
All ICS kernel updates can go here. This is for Entropy, LipShitz, Task and any other who is actually working on the ICS kernel.
If you post here, it will be deleted on the spot so just fair warning...
First!
These are always my latest *unsupported* builds:
i9100 Touchwiz Based Roms: http://www.cheatersedge.org/android/i777/TWzImage.tar
AOSP Based Roms: http://www.cheatersedge.org/android/i777/AOKPzImage.tar
Red5 said:
If you post here, it will be deleted on the spot so just fair warning...
Click to expand...
Click to collapse
Come at me bro!
j/k..
Seriously guys.. No fooling around!
Fenny maybe I missed it but do you have a thread to discuss this tw kernel. So far so good. I had already converted OmegaRom 5.1 with everything and was just waiting on a kernel. So far so good. I am gonna look through my notes on how/where to fix the home haptic feedback but other than that all 4 buttons seem to working perfectly. I have sent a pm to the des of OmegaRom to see if they wanted it ported (help porting it to our phones) but i have heard back from them so far. Will continue playing with it with your kernel and test it out. I have run the OmegaRom for about three days already and have had any issues so testing with your kernel is now upon me. Thanks for your work on this. Rich
Fixed: All keys and home haptic working now, though home haptic seems lighter than the other keys.
Sent from my SGH-I777 using xda premium
Until things are cleaned up better, there aren't going to be threads. There's enough to be done and enough things are still not working right that new threads aren't justified yet.
https://github.com/Entropy512/initramfs_galaxys2_ics
https://github.com/Entropy512/kernel_galaxys2_ics
used to build the attached zImage. If you don't know what to do with a raw zImage, this isn't ready for you yet. Simple as that - there is a lot of things missing (like, don't set any profiles in SetCPU with reduced clock frequencies, bad things will happen) - I still haven't tested flashing zips in CWM. nandroid backup/restore seems to work but no guarantees.
You still need to disable Samsung Noise Reduction or use a hacked Phone.apk along with a hacked /system/usr/keylayout/sec_touchkey.kl (see Hellraiser on github) for it to work in a reasonable way. There's probably a large pile of **** still broken. Don't pester me with bug reports - there's a pile of stuff I KNOW I still need to address.
When I tried the attached patch yesterday, it made the screen wake problem significantly worse. Progress in the wrong direction is still progress, as it gives you an idea where to look. I'm going to investigate this further tonight.
It was an attempt to add the missing GPIO definitions that are in the Gingerbread source tree into the ICS kernel.
Entropy, not stating a fact and you KNOW a heck a lot more than I so take this with a grain of salt. I have been playing with lots of different files on a ported/converted i9100 ICS Rom (Omega Rom 5.1) and used these for the usr files and have seen the screen wake issue. http://db.tt/DUe4afdh Maybe it has nothing to do with these though. I have changed many other things like csc folder, csc other files, many other things also. Also I am using the kernel posted by Fenny if that matters or is much different than yours a I have tested it out yet. I only replied here because one of the files I removed was the gpio file completely as other files inside seemed to have the same configurations. Maybe I am WAY off base here. If you want to try the Rom i converted already to see if anything helps let me know and I will send a link to you. Thanks for all your hard work.
Sent From My KickAss ATT SGS2 SPORTING my CobraRom
Sorry.... went to bed and woke up to 50 more pages on other thread.What company shares network with att that has ICS??
Tap-Tap Talking
You know... if this thread is no posting allowed, and not stickied, it is just going to get BURIED.
Sent from my GT-I9100 using XDA
Better off doing how its being done... if use another developers ... you just mirror same issues...if build yourself you know whats what.
Tap-Tap Talking
Entropy512 said:
When I tried the attached patch yesterday, it made the screen wake problem significantly worse. Progress in the wrong direction is still progress, as it gives you an idea where to look. I'm going to investigate this further tonight.
It was an attempt to add the missing GPIO definitions that are in the Gingerbread source tree into the ICS kernel.
Click to expand...
Click to collapse
Isn't 4.0 a total new build from Sammy? Honestly.... from what I'm looking at...I don't see ginger GPIO being compatible..but should be if all they used was duct-tape and staples to parse another kernal together.I'm buying a laptop. You guys use sdk? Entropy..what program are you using for kernal popping? Give me area you want help....will do
Tap-Tap Talking
LipShitz said:
Sorry.... went to bed and woke up to 50 more pages on other thread.What company shares network with att that has ICS??
Tap-Tap Talking
Click to expand...
Click to collapse
AT&T does not share its network with anyone - unless you're thinking of the MVNOs that use their network, which are almost exclusively using low-end prepaid devices.
The I777 is AT&T-unique - no other carrier uses it. Everyone else uses I9100 variants. (Except the Korean carriers, which have the M250S/K/L, and NTT DoCoMo, which has an I9100 variant branded as SC-02 I believe.)
Entropy512 said:
AT&T does not share its network with anyone - unless you're thinking of the MVNOs that use their network, which are almost exclusively using low-end prepaid devices.
The I777 is AT&T-unique - no other carrier uses it. Everyone else uses I9100 variants. (Except the Korean carriers, which have the M250S/K/L, and NTT DoCoMo, which has an I9100 variant branded as SC-02 I believe.)
Click to expand...
Click to collapse
Sc-02-i9100....this is what we have source? I want to run another of att dual core. I made a call to my work for that persons contact info. If I get..(I will) it will help in big way. If you read my first 2 pm's from other day...you know what I mean.
Tap-Tap Talking
Fenny said:
You know... if this thread is no posting allowed, and not stickied, it is just going to get BURIED.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Ill make sure it stays at the top.
LipShitz said:
Sc-02-i9100....this is what we have source? I want to run another of att dual core. I made a call to my work for that persons contact info. If I get..(I will) it will help in big way. If you read my first 2 pm's from other day...you know what I mean.
Tap-Tap Talking
Click to expand...
Click to collapse
I'll catch up on your PMs soon.
I think I've found the screen wake bug: I misread the #ifdefs in the Gingerbread kernel, and realized they unmap the HOME key GPIO.
There was no such unmapping in the ICS kernel - so the GPIO was left mapped to HOME but left floating, which explains both random wakes and spurious HOME presses. It's also why the patch I posted this morning caused guaranteed screen wakes on resume - GPX3(5) is the HOME GPIO and was set to pulldown by that patch - it's an active-low GPIO.
Attached is a test kernel zImage and two patches - if these solve screen wake for those experiencing it, I'll push the patches to github and probably release the first Daily Driver ICS tonight even though I still haven't fixed SetCPU hangs.
This kernel is for Touchwizz firmwares only - if it solves the problem for everyone I'll work with the CM9 maintainers on integrating the attached patches, which apply to the current state of my github repo.
Let me know when you get to test point. Shoot it over if you want.
I have started writing a new program that will enable you to do parcing of 2 total diff Kernals,full factory and custom ROMs., yank out APK's and cook me dinner. What It will prob be 2gig in size..will streamline it. But when done--- WE WILL RULE THE WORLD!.. yea ok.
Tap-Tap Talking
Here is a kernel I compiled to work with MIUIv4 for this weeks update 2.3.23:
http://www.mediafire.com/?5bm1l4t1bmbd8bm
All good... little laggy(prob CPU hang) 200-1200 CPU set? No wake issue yet. I'm on 1.5 hours.
Tap-Tap Talking
I restarted phone and stuck on startup logo(samsung bla bla bla) i need to hook it up to laptop and flash it. Will not go into cwm with power and both volume. Im on my infuse.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Sorry Double Post
RE: [RoM]UCLD3 Official ATT "Leak" !CLOSED!
I just wanted to say TY to the developers of this ROM, especially task. I got burned, but I knew what I was getting into. I'm within 30 days, plus have 1 yr warranty, plus insurance. I got my new phone and I'm happy.
Thanks again guys for trying to bring us something new and exciting.
Just a question: were all of the AT&T leaks affected by this, or just UCLD3?
The general consensus is that LD3 was the culprit, however it is possible that all leaks are affected.
The culprit was the CWM injected kernel in the version task posted. All other leaks and the one-click version of LD3 were unaffected.
nbell13 said:
The culprit was the CWM injected kernel in the version task posted. All other leaks and the one-click version of LD3 was unaffected.
Click to expand...
Click to collapse
And you know this how? Without facts, this statement is useless bro. One thing I do know is the bricking only happened to a few people. Far less then people who didn't have issues. Just like entropy said, without reproducing it would be hard to figure out. But either way. Leaks are just that. Leaks. They are pretty much worthless considering everything else we already have. So really, to figure out exactly the cause we would have to go through the process of brick, then replace/fix the device and so on.
task650 said:
And you know this how? Without facts, this statement is useless bro. One thing I do know is the bricking only happened to a few people. Far less then people who didn't have issues. Just like entropy said, without reproducing it would be hard to figure out. But either way. Leaks are just that. Leaks. They are pretty much worthless considering everything else we already have. So really, to figure out exactly the cause we would have to go through the process of brick, then replace/fix the device and so on.
Click to expand...
Click to collapse
I thought that's what you had said yourself in your thread (haven't read it in a while)
Task
I have flashed this rom many times and no issues with my phone. Although I have been lurking in these threads as a NOOB, it is apparent to me that you have to:
follow instructions in OP before flashing
Read all the of the thread before flashing
Make sure that you have the entire zip file downloaded before flashing...
Not sure what is the problem, but it is not anything with zip I down loaded.. I did both.The other files such as Shomans or AOKP as they are better than any stock rom...
Thank you for all that you do...
nbell13 said:
I thought that's what you had said yourself in your thread (haven't read it in a while)
Click to expand...
Click to collapse
i think i may have said something about it, but just wasn't sure what was happening. there were too many "it could be this" and "it could be that" stuff being mentioned. but i did however make an attempt for 2 days trying to replicate the brick. i have no qualms about buying a new phone so i wasn't worried at all about bricking. i tried every way that anyone mentioned plus more but i still couldn't get it to brick. so i'm still iffy about the whole thing. i just said screw and took down the thread. considering A TON of people don't like to read OP's and follow directions i thought it would be the best thing to do.
task650 said:
i think i may have said something about it, but just wasn't sure what was happening. there were too many "it could be this" and "it could be that" stuff being mentioned. but i did however make an attempt for 2 days trying to replicate the brick. i have no qualms about buying a new phone so i wasn't worried at all about bricking. i tried every way that anyone mentioned plus more but i still couldn't get it to brick. so i'm still iffy about the whole thing. i just said screw and took down the thread. considering A TON of people don't like to read OP's and follow directions i thought it would be the best thing to do.
Click to expand...
Click to collapse
Thanks for the hard work on it anyway Task. I read the OP. I read every post in the thread and then I read the OP again. I have flashed and reflashed it several times. Flashed several kernels and still running great.
The original OEM battery and earpiece failed within a day of each other so I am back to using my Atrix until I can get a warranty replacement on the i777.
Thanks again Task...it was fun while it lasted.
task650 said:
i think i may have said something about it, but just wasn't sure what was happening. there were too many "it could be this" and "it could be that" stuff being mentioned. but i did however make an attempt for 2 days trying to replicate the brick. i have no qualms about buying a new phone so i wasn't worried at all about bricking. i tried every way that anyone mentioned plus more but i still couldn't get it to brick. so i'm still iffy about the whole thing. i just said screw and took down the thread. considering A TON of people don't like to read OP's and follow directions i thought it would be the best thing to do.
Click to expand...
Click to collapse
Lol, I just bought the GNex from Google Play myself... Gonna need to switch back to T-Mobile in the fall when I move back to my hometown... AT&T has **** for signal there That, and I'm finally sick of touchwiz.
nbell13 said:
I'm finally sick of touchwiz.
Click to expand...
Click to collapse
Yeah that's why I use AOKP I can't stand touchwiz ics
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Lol. I installed nova to take care of that. Do want some of the other stuff so have to leave tw in some way but at least I don't have to look at it.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
nbell13 said:
The culprit was the CWM injected kernel in the version task posted. All other leaks and the one-click version of LD3 were unaffected.
Click to expand...
Click to collapse
No - even after the re-repack I believe a few more bricks happened.
Looks like the UCLD3 leak (and maybe all leaks) have the same bug that is in all of the Epic 4G Touch leaks and all Chinese Galaxy Note ICS leaks, along with the SHW-M250S/K/L official ICS releases and source code - it's a nasty one that can cause severe hardbricks if you wipe in recovery.
When I say "severe hardbrick" - I mean that the eMMC chip actually gets damaged to the point where not even JTAG recovery services like mobiletechvideos.com are able to recover the device.
It's looking like UCLD3 has the same issues that SiyahKernel 3.1rc6 had (which was rebased on SHW-M250L sources).
This is probably like some of the xbox360 and ps3 bricking updates -- an update changes something in the way the device operates. In those update -- spinning the media faster or turning on gpu acceleration of the UI, etc.. some devices can't take the change in the baseline for which they were certified and die.
Perhaps they changed voltages, media parameters, etc -- without source, we won't know for sure.
othermark said:
This is probably like some of the xbox360 and ps3 bricking updates -- an update changes something in the way the device operates. In those update -- spinning the media faster or turning on gpu acceleration of the UI, etc.. some devices can't take the change in the baseline for which they were certified and die.
Perhaps they changed voltages, media parameters, etc -- without source, we won't know for sure.
Click to expand...
Click to collapse
Sweet.... I want one of them Xbox with ICS
Yea this is one of those oddities. On mine I did do a wipe using the ld3 leaked kernel (trying to get ld3 installed) and although it wouldn't boot it also didn't hard brick. I ended up wiping using Odin and starting over.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Entropy512 said:
No - even after the re-repack I believe a few more bricks happened.
Looks like the UCLD3 leak (and maybe all leaks) have the same bug that is in all of the Epic 4G Touch leaks and all Chinese Galaxy Note ICS leaks, along with the SHW-M250S/K/L official ICS releases and source code - it's a nasty one that can cause severe hardbricks if you wipe in recovery.
When I say "severe hardbrick" - I mean that the eMMC chip actually gets damaged to the point where not even JTAG recovery services like mobiletechvideos.com are able to recover the device.
It's looking like UCLD3 has the same issues that SiyahKernel 3.1rc6 had (which was rebased on SHW-M250L sources).
Click to expand...
Click to collapse
Thank you for your insights, while I understand very little in the way of repacks and source code, I can grasp (beginning to) smart, safe flashing practices. When you share your thoughts on these subjects, the non-dev community is so much the better for it (though there will never be a silver bullet to the spreading of BS through the grapevine).
And it looks like I'm still the only one who wants Samsung stock roms.
raduque said:
And it looks like I'm still the only one who wants Samsung stock roms.
Click to expand...
Click to collapse
There are still plenty of great TW GB ROMs around. Unfortunately, people who want a stable, safe stock ICS ROM will have to wait until Samsung gives you one. Without the developers we wouldn't have ICS on our phone AT ALL, so complaining is without merit (unless you are complaining to Samsung).
raduque said:
And it looks like I'm still the only one who wants Samsung stock roms.
Click to expand...
Click to collapse
Naw I want a Samsung stock rom built for the ATT version also
Sent from my SGH-I777 using XDA Premium App
First of all I would like to apologize if you have heard these questions a thousand times before, but I have done a fair amount of reading and haven't gotten enough concrete answers to be confident enough to continue.
I just got up the courage to root my Fascinate after over a year of having it by following droidstyle's excellent guide. It was very painless and worked first shot, so no worries there. Now I'm at the point of what to do next... I have already frozen the bloatware and looked into some 'root-friendly' apps but I'm not sure where to go from here. I think I've decided I want to get the most out of this thing as I'm not due for an upgrade for (what seems like) a long time. I'm under the impression that installing a good ICS rom is the way to go but I just have a few noob questions before I continue.
1) From what I have been reading Glitched AOKP ICS is the best rom to use currently on the Fascinate, correct? Also quick question, regarding the link to download it... is the current version the build 34 one or the milestone 5 one at the top?
2) Rooting my phone initially didn't erase any of my apps or data. What will installing an ICS rom erase, if anything? I will make backups of course, but I'm just wondering what to expect. Will the 'bloatware' apps still be there or will installing ICS install new system apps?
3) What market apps should I consider 'must haves' to tweak stuff? I already bought setcpu but haven't invested in anything else yet.
4) I plan to follow section 4 of droidstyle's guide but need clarification... even though I have rooted stock 2.3, I should still follow all steps right?
Thank you for listening to my noob questions and thanks to anyone who can offer advice. I have been building and working on computers for years but this cell phone hacking stuff is all new to me (obviously).
Crawshayi said:
First of all I would like to apologize if you have heard these questions a thousand times before, but I have done a fair amount of reading and haven't gotten enough concrete answers to be confident enough to continue.
I just got up the courage to root my Fascinate after over a year of having it by following droidstyle's excellent guide. It was very painless and worked first shot, so no worries there. Now I'm at the point of what to do next... I have already frozen the bloatware and looked into some 'root-friendly' apps but I'm not sure where to go from here. I think I've decided I want to get the most out of this thing as I'm not due for an upgrade for (what seems like) a long time. I'm under the impression that installing a good ICS rom is the way to go but I just have a few noob questions before I continue.
1) From what I have been reading Glitched AOKP ICS is the best rom to use currently on the Fascinate, correct? Also quick question, regarding the link to download it... is the current version the build 34 one or the milestone 5 one at the top?
2) Rooting my phone initially didn't erase any of my apps or data. What will installing an ICS rom erase, if anything? I will make backups of course, but I'm just wondering what to expect. Will the 'bloatware' apps still be there or will installing ICS install new system apps?
3) What market apps should I consider 'must haves' to tweak stuff? I already bought setcpu but haven't invested in anything else yet.
4) I plan to follow section 4 of droidstyle's guide but need clarification... even though I have rooted stock 2.3, I should still follow all steps right?
Thank you for listening to my noob questions and thanks to anyone who can offer advice. I have been building and working on computers for years but this cell phone hacking stuff is all new to me (obviously).
Click to expand...
Click to collapse
1) M5 is newest. Get glitched build off of the exynos server.
2) Complete wipe. A desktop equivalent would be formatting your hard drive with Windows Vista installed and doing a fresh install of windows 7.
Backup all data and contacts locally or on the cloud. Do NOT use Verizon to backup your contact data. Use Google or a local backup instead.
No bloatware will be present since custom roms do not come from the carrier.
3) NSTools. Maybe Root Explorer or wi-fi tether for google
4) Just follow the guide. Rooting doesn't have much to do with recovery and intalling ics and such.
Not to knock ICS, because I love AOKP, but you could also consider working your way there over time. I had a lot of fun playing with different Touchwiz ROMs like SC3 and TSM Res. You may even find one along the way that you want to stick with for a while. At the very least, you'll learn to get where a complete data wipe doesn't even slow you down.
There's so much good stuff still available for this phone. My phone is sheer perfections right now, but I still have plans to try out GeeWiz and MIUI.
Everyone knows the current destination is Glitched AOKP, but the fun is in the journey.
I agree. I would download everything rom,kernel, and app you can find for the phone between here and rootzwiki, just in case links go dead. Tsm res and awesome sauce are two very good roms that I had a ton of fun with. They are more forgiving to the new user as far as making mistakes goes. Couple of things to know before you continue are that you can use the three finger method to get into recovery on touchwiz roms but not the ics roms(must enter recovery through power off menu). You also cant just flash back and forth from touchwiz roms and cm7 or ics roms, as you have to follow certain steps
Sent from my SCH-I500 using Tapatalk
Well I was planning on jumping right into ICS as it looks amazing and I don't think I want to wait... however I wouldn't be opposed to the idea of trying different roms later on down the road. Is it going to be a pain to go backwards from ICS, or just flash like usual? Also, to those that have tried most of the 'good' roms, what would you consider your top 3 non-ICS?
Also on the subject of backing up my apps... I have been using Mybackup as it seems the most simplistic to use and reliable. Will my apps be exactly as they were when I backed them up (after switching to ICS) or is it just better to re-download what I need and configure them again?
I hate to spam some more questions but I figure since I already am... just a few more...
I haven't really messed with Setcpu that much, but is it bad to have it at 100/1000 or should I keep the max lower than that? And last one... what's the best wifi tether to use so Verizon won't send their goons after me? Is the USB tether from clockwork mod any good?
Thanks to all of you for your input. I think I'll be attempting to flash to ICS tomorrow night and hopefully all goes well.
You can go from touchwiz roms to isc roms by flashing but you need to do a lot more using the computer to go backwards. It will make more sense once you have a better understanding. Use titanium backup to backup your apps. If you really dont have any then just redownload them. If you are on the touchwiz roms you can use setcpu, but for ics roms you are going to be using an app called nstools or from control (built into settings section of rom). Again, more of this will make sense later down the road that is why I figured it would be better to start on a from like tsm Res or awesome sauslce
Sent from my SCH-I500 using Tapatalk
Well I'm still on the fence here on what to do. I really want to run ICS but with all the little glitches I've read about I think maybe I'll try some of the better GB roms first... I think TSM Res looks top for me with the features, but I might try more than just 1. I've heard not to restore data backups when going ICS... does this apply to GB roms as well? Should I also switch the radio or is what I have the same as the GB one? Thanks
Crawshayi said:
Well I'm still on the fence here on what to do. I really want to run ICS but with all the little glitches I've read about I think maybe I'll try some of the better GB roms first... I think TSM Res looks top for me with the features, but I might try more than just 1. I've heard not to restore data backups when going ICS... does this apply to GB roms as well? Should I also switch the radio or is what I have the same as the GB one? Thanks
Click to expand...
Click to collapse
AOKP milestone 5. You WILL thank me for it. Make sure its Steve's glitchy (the kernel of course) build.
Sent from my SCH-I500 using xda premium
mezster said:
AOKP milestone 5. You WILL thank me for it. Make sure its Steve's glitchy (the kernel of course) build.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
You don't like the one they just released a few days ago?
Crawshayi said:
You don't like the one they just released a few days ago?
Click to expand...
Click to collapse
That is a nightly and has a minor bug where apps on SD card force close. No biggie for more experienced users who know its a nightly and can deal. Nightlies are bleeding edge releases and as such can contain a bug or two. Milestones are stable releases to be used as a reliable daily driver if one is needed (some do). I recommend the m5 release since it is a milestone and you are new to this. I also want to see you have the best experience possible.
Sent from my SCH-I500 using xda premium
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
I'm in a similar spot. I put CM7 on my wife's phone a while ago, but she has downloaded so much crap on it it's running like garbage and crashing.
Does the AOKP M5 have any bugs I should be aware of? As long as it's working well and everything is working (WiFi, Camera, MMS, etc), she'll be fine with it as a daily driver.
Two other questions I have.
Where can I get the correct glitchy Kernel?
Do I just need to download the ROM and kernel, wipe data/cache, then flash the ROM then kernel, then gapps (in that order) in Clockwork Recovery? Anything else?
She really likes the ICS stuff I've been showing her on my Rezound, especially the speech to text typing.
Thanks for your feedback.
EDIT
Added Information:
Just to make sure my i's are dotted and my t's are crossed--
Build for Verizon Fascinate:
http://forum.aokp.co/page/releases/_/milestone-5-r20
fascinatemtd Samsung Fascinate
Glitch Kernel:
http://forum.xda-developers.com/showthread.php?t=1459475
Are those right?
EDIT 2
Should I update radios as well? (Assuming yes since going to AOKP from CM7). Which ones should I do? Again, is this a simple flash in CWR? What's the install sequence?
Thanks.
EtherBoo said:
I'm in a similar spot. I put CM7 on my wife's phone a while ago, but she has downloaded so much crap on it it's running like garbage and crashing.
Does the AOKP M5 have any bugs I should be aware of? As long as it's working well and everything is working (WiFi, Camera, MMS, etc), she'll be fine with it as a daily driver.
Two other questions I have.
Where can I get the correct glitchy Kernel?
Do I just need to download the ROM and kernel, wipe data/cache, then flash the ROM then kernel, then gapps (in that order) in Clockwork Recovery? Anything else?
She really likes the ICS stuff I've been showing her on my Rezound, especially the speech to text typing.
Thanks for your feedback.
EDIT
Added Information:
Just to make sure my i's are dotted and my t's are crossed--
Build for Verizon Fascinate:
http://forum.aokp.co/page/releases/_/milestone-5-r20
fascinatemtd Samsung Fascinate
Glitch Kernel:
http://forum.xda-developers.com/showthread.php?t=1459475
Are those right?
EDIT 2
Should I update radios as well? (Assuming yes since going to AOKP from CM7). Which ones should I do? Again, is this a simple flash in CWR? What's the install sequence?
Thanks.
Click to expand...
Click to collapse
Get the Milestone 5 Glitched build found HERE
It includes the Glitch kernel, so no need to flash separately, and also has a few extra cherry picks thrown in. This is a Milestone build, so no real bugs, should run smooth as silk.
I'm not sure of the recommended radio for fascinate on ICS.
jbreakfield said:
Get the Milestone 5 Glitched build found HERE
It includes the Glitch kernel, so no need to flash separately, and also has a few extra cherry picks thrown in. This is a Milestone build, so no real bugs, should run smooth as silk.
I'm not sure of the recommended radio for fascinate on ICS.
Click to expand...
Click to collapse
Might sound like a cheesy question, but what radios are you running?
Thanks for your help.
jbreakfield said:
Get the Milestone 5 Glitched build found HERE
It includes the Glitch kernel, so no need to flash separately, and also has a few extra cherry picks thrown in. This is a Milestone build, so no real bugs, should run smooth as silk.
I'm not sure of the recommended radio for fascinate on ICS.
Click to expand...
Click to collapse
QFT.
Get the Glitched build as it has fixes, extra available RAM, and much more not available in the AOKP official build.
Wifi, cam, and MMS all work fine. I can't honestly think of anything not working off the top of my head. NovaLauncher (Regular is free, Prime is $4 and well worth it for gestures) is recommended at this point since Apex has gotten a little slow.
Radio is recommended to be EH03 though I think ec09 and anything newer than eh03 work fine. I am running EH03 and no complaints.
I think I remember reading something about torch not working in ICS... is that the type of app that turns on the LED? Believe it or not I use that a lot and it would be a pain if it didn't work when I switch.
Also, is there any way to check what radio you're currently using before flashing? Tried looking that up but couldn't find it
Ah yes...torch doesn't work but you can use the tiny flashlight app to turn on the flash and achieve the same functionality.
Sent from my SCH-I500 using xda premium
bobloblaw1 said:
Ah yes...torch doesn't work but you can use the tiny flashlight app to turn on the flash and achieve the same functionality.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
The Tiny Flashlight + LED app? That's actually what I'm using now and if that works then I'm all set... I thought when people said 'torch' they just meant any app that turns on the LED
I flashed and ran into 1 problem. I had to flash Team Hacksungs Build 2 ROM first. Flashing glitched put me in an endless boot. Then I couldn't boot to recovery. I really was flipping out.
I had to Odin a new recovery in, wipe, then flash Team Hacksungs Build 2 ROM. For some reason, it booted into AOKP (?) then. I went back to recovery, wiped, reflashed AOKP and got it working.
I haven't searched yet, but anyone know where I can change the boot screen? It's really not a "wife friendly" boot screen.
As I understand it, torch refers to the built in flashlight feature in aokp called torch. Tiny flashlight plus the widget give similar functionality.
Sent from my SCH-I500 using xda premium