Sorry - My bad behind the battery it says SGH-I777
when it boots up it says SGH-I9100 on the splash screen..
[Kernel] TRIM: Fast and Stable CyanogenMod 11 on the Galaxy S2 AT&T i777
- Thread starter Lanchon
- Start date
-
- Tags
- development
when it boots up it says SGH-I9100 on the splash screen..
so which is it? behind the battery there should be a sticker with model, IMEI, etc.
i9100 has an actual/physical/clicky HOME button below the screen, plus a tactile button on each side of HOME.
i777 has 4 tactile buttons and no clicky.
UPDATE: new CM 12.1 kernels are up... TRIM + FreezeFix + TWRP !
all-in-one kernels with TWRP are finally here, now including the official version of zeitferne's freezefix.
going forward, both TWRP and CM recovery versions of new CM 12.1 kernels will be produced.
this was possible on the i777 thanks to the work of @dimoochka who ported TWRP to this platform and of @cyril279 who built and shared a working version. thank you guys! as always, all my i777 stuff is untested.
enjoy TWRPing!
all-in-one kernels with TWRP are finally here, now including the official version of zeitferne's freezefix.
going forward, both TWRP and CM recovery versions of new CM 12.1 kernels will be produced.
this was possible on the i777 thanks to the work of @dimoochka who ported TWRP to this platform and of @cyril279 who built and shared a working version. thank you guys! as always, all my i777 stuff is untested.
enjoy TWRPing!
UPDATE: new CM 12.1 kernels are up... TRIM + FreezeFix + IsoRec !
TWRP kernels were nice enough... for a day.
now they are obsolete! meet IsoRec, the isolated recovery solution that finally lets you choose your preferred recovery.
the new IsoRec-compatible TRIM kernels can be found here.
going forward, only the IsoRec-compatible flavor of CM 12.1 kernels will be produced.
enjoy TWRPing; or whatever you like best!
TWRP kernels were nice enough... for a day.
now they are obsolete! meet IsoRec, the isolated recovery solution that finally lets you choose your preferred recovery.
the new IsoRec-compatible TRIM kernels can be found here.
going forward, only the IsoRec-compatible flavor of CM 12.1 kernels will be produced.
enjoy TWRPing; or whatever you like best!
Last edited:
REQUEST
someone running CM 12.1 on the i777 please test IsoRec:
-flash IsoRec kernel: should recovery-boot to CM recovery.
-flash IsoRec TWRP: should recovery-boot to TWRP.
-flash IsoRec disabler: should recovery-boot back to CM recovery.
then please report here.
testing is necessary before merging IsoRec into official CM.
thank you!
someone running CM 12.1 on the i777 please test IsoRec:
-flash IsoRec kernel: should recovery-boot to CM recovery.
-flash IsoRec TWRP: should recovery-boot to TWRP.
-flash IsoRec disabler: should recovery-boot back to CM recovery.
then please report here.
testing is necessary before merging IsoRec into official CM.
thank you!
behind the battery says SGH-I777 and has 4 buttons on the front also has ATT on the front top
How can I complete erase this phone and allow it to use CM on it and the wifi works?
thank you that would be great! i have held off my own change at gerrit pending someone testing on the i777, so much appreciated.
Worked perfectly!
Was able to flash latest nightly via the ota updater with no issue.
Sent from my SAMSUNG-SM-G890A using Tapatalk
Last edited:
thanks so much! updating gerrit right now
UPDATE: new CM 12.1 kernels are up... and CM 13.0 kernels too !!!
unfortunately still no fix for PegasusQ, so refrain from using that governor.
WARNING: the CM 13.0 kernels are completely untested. please report.
enjoy!
unfortunately still no fix for PegasusQ, so refrain from using that governor.
WARNING: the CM 13.0 kernels are completely untested. please report.
enjoy!
UPDATE: new CM 13.0 kernels are up !!!
F2FS support included.
enjoy!
F2FS support included.
enjoy!
UPDATE: VICTORY !!!
2016-03-02: after two years of tests and discussions, folklore, FUD and evidence, Lysergic Acid finally took the plunge and merged! TRIM is now part of the official CM 12.1 and CM 13.0 kernels, and this project can at last be retired, yoohoo!!! CM 13 users now enjoy TRIM out of the box, but users of CM 12.1 builds older than Match 2016 as well as CM 11.0 users continue to require a separate TRIM kernel.
this thread is dedicated to Entropy and the brave users who risked their devices to run the very first TRIM tests.
2016-03-02: after two years of tests and discussions, folklore, FUD and evidence, Lysergic Acid finally took the plunge and merged! TRIM is now part of the official CM 12.1 and CM 13.0 kernels, and this project can at last be retired, yoohoo!!! CM 13 users now enjoy TRIM out of the box, but users of CM 12.1 builds older than Match 2016 as well as CM 11.0 users continue to require a separate TRIM kernel.
this thread is dedicated to Entropy and the brave users who risked their devices to run the very first TRIM tests.
Been a while I updated the ROM. Been totally out of touch - please pardon my newbie question. I currently have Android 4.4.4, Carbon ROM version August 28,2014. Kernel 3.0.64-CMg8245168. To install the CM-13 ROM all I do is Cook's ROM wipe and and install from the Kernel-Lanchon-TRIM-isorec.....zip?
@Lanchon ...well I guess I concede trim is safe in your (samsungs) implementation after rereading entropys saga again and the commits. But if my **** bricks I'm blaming you! JOKING! You deserve much credit.
Relevant:
With a clean wipe flashing the i9100 04 zip, gapps and your cm13 kernel works fine, better than LP. The sec_touchkey.kl has to be placed manually as it's not the i777 config it's still i9100 layout, but works after that.
Doing the same with any rom past 04 results in a bootloop even with clean wipe. It gets through "optimizing apps" and "finishing boot" then loops at the cm splash.
I'm guessing kernel seeing the commits in the i9100 changelog.
No obligation or anything I just wanted to say there are still some i777 users that can benefit from the surprisingly good dev on the i9100 side. We don't have 13 yet (ever). And I think all i777 users thank you.
Relevant:
With a clean wipe flashing the i9100 04 zip, gapps and your cm13 kernel works fine, better than LP. The sec_touchkey.kl has to be placed manually as it's not the i777 config it's still i9100 layout, but works after that.
Doing the same with any rom past 04 results in a bootloop even with clean wipe. It gets through "optimizing apps" and "finishing boot" then loops at the cm splash.
I'm guessing kernel seeing the commits in the i9100 changelog.
No obligation or anything I just wanted to say there are still some i777 users that can benefit from the surprisingly good dev on the i9100 side. We don't have 13 yet (ever). And I think all i777 users thank you.
so i gues you are asking for an updated kenel?
of course it'd be better if i777 cm moved to 13. but before asking for the change to LA, it'd be ideal to have REPIT working on the device beforehand, to handle the small /system issue.
i can make a port for the i777 if you help me:
-install TWRP isorec.
-clone this:
https://github.com/Lanchon/REPIT/tree/master/device-dump
-reboot to recovery.
-male sure you see the recovery from the PC by issuing: adb devices
-on the PC, run the run-dump[.bat] script.
-go here and create a new porting issue:
https://github.com/Lanchon/REPIT/issues
-post the generated dump-out.txt on the issue thread.
Well this was interesting. I'm posting here because I didn't get anything.
From cyrils (good working) isorec twrp I pushed the dump.sh and ran the .bat and got this in the output:
After that the previously working isorec twrp is mostly broken, the bottom middle log button thing is filled with red "E: Invalid Block Device" errors on most partitions. Rebooting to system gives the "No OS Installed" prompt, I rebooted anyway and sure enough it boots into cm13 as normal.
Back in still broken twrp adb works and I can see the /tmp directory but not much else, can't format anything, so after pushing cyrils omni kernel it flashed surprisingly (so it can write to a partition but the recovery won't detect it now?). I rebooted into that and it worked as expected, so the partitions are fine, then I flashed you cm13 kernel getting a working system back, but still with the broken isorec twrp. I tried this with a cwm.tar and that also worked fine.
No amount of disabling, flashing non-isorec twrp kernels, reflashing twrp isorec, then your cm13, no combo gets isorec twrp working right again.
Really strange thing is that after trying the cwm isorec it works fine!? So ONLY the twrp isorec now won't work after running the dump.sh. That makes no sense to me.
So all's good here I didn't lose anything just on cwm now instead of twrp. And the phone works better than ever on the 04 rom with your kernel so I'm happy with it.
I'm not looking for a fix just posting my experience. Is that really weird or what? Maybe formating the recovery partition could clear something up? Full repit? I'll try at some point.
From cyrils (good working) isorec twrp I pushed the dump.sh and ran the .bat and got this in the output:
Back in still broken twrp adb works and I can see the /tmp directory but not much else, can't format anything, so after pushing cyrils omni kernel it flashed surprisingly (so it can write to a partition but the recovery won't detect it now?). I rebooted into that and it worked as expected, so the partitions are fine, then I flashed you cm13 kernel getting a working system back, but still with the broken isorec twrp. I tried this with a cwm.tar and that also worked fine.
No amount of disabling, flashing non-isorec twrp kernels, reflashing twrp isorec, then your cm13, no combo gets isorec twrp working right again.
Really strange thing is that after trying the cwm isorec it works fine!? So ONLY the twrp isorec now won't work after running the dump.sh. That makes no sense to me.
So all's good here I didn't lose anything just on cwm now instead of twrp. And the phone works better than ever on the 04 rom with your kernel so I'm happy with it.
I'm not looking for a fix just posting my experience. Is that really weird or what? Maybe formating the recovery partition could clear something up? Full repit? I'll try at some point.
Last edited:
this is extremely weird.
> I pushed the dump.sh and ran the .bat and got this in the output
what does that mean? you only needed to run the bat on the PC, not push anything. what exactly did you do? and the output, was it on the screen of the PC or in the 'dump-out.txt' file on the PC?
as you can see in the script:
https://github.com/Lanchon/REPIT/blob/master/device-dump/dump.sh
there is nothing in lines 2, 7, 13... so your error messages are strange as hell. what exactly did you do?
New posts
-
Xiaomi.EU Android 11 Latest Weekly Release- Latest: DeathStroke47
-
-
[r64] arter97 kernel for OnePlus 7 series
- Latest: Ayan Chakraborty
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone