Keep a stable stock rom, Keep your recovery, and run a custom built rom like CM9!
First, credit to all the peoples threads I'm linking to, especially bbelos, mkasick, rothnic and CVPCS, invisiblek and Beanstown106.
Neyenlives for inspiring me to do this with his cm9 install post http://forum.xda-developers.com/showthread.php?t=1774408
I take no credit, and thats why I'm not just linking a fixed up rom. This is just my preferred way to run these
I didn't want to give up my stock (or beans) rom for a buggy cm9.
Before you start, if you haven't already, BACK UP YOUR IMEI!!!!
http://forum.xda-developers.com/showthread.php?t=1791291
just to be safe
You can dual boot using Cyanogen Mods Team Epic dual boot method (FakeCWM) which will install on the EMMC:
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
The link tends to break, so if it doesn't work just go to their blog (maybe even donate to them!)
I am using the the CWR that rothnic put together with mkasick's kexec kernel
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
Rothnic pointed me in the right direction to "add one line to Invisiblek's updater-script that "flashes" the boot.img to the bootloader partition in the multi boot folder."
so take cm9 rom:
invisblek's http://goo.im/devs/invisiblek/i535/roms
Beans build of CVPCS': http://goo.im/devs/B...ICIAL-d2vzw.zip
and unzip it, and open the file
\META-INF\com\google\android\updater-script
with notepad++ on windows http://notepad-plus-plus.org/
or text wrangler for mac http://www.barebones.com/products/textwrangler/ (thanks usatf1290)
add in this line
package_extract_file("boot.img", "/dev/block/mmcblk0p7");
so that it is 3rd to last in the script
make sure you have the unix EOLs flags as mentioned here
http://boardreader.com/thread/update_zip_error_status_6_677jjXi0hq.html
And then add a cm9 boot.img into the root
invisiblek's , http://goo.im/devs/invisiblek/i535/roms/boot.img
Bean's http://goo.im/devs/B...zw/cm9/boot.img
zip up your system and META-INF folders and your boot.img and
flash it in place of the CM9 nightly build.zip mentioned in the team epic instructions
also get gapps from here http://goo.im/gapps and
flash in fake cwr after flashing cm9
Hopefully invisiblek and others will start packaging their original roms in this format so we can just dual boot them.
Thanks again everyone for your hard work.
So, you'd just do a reboot to get back to the Stock Rom?
And if you want to go back to CM9 from stock, you'd have to reflash the cm9 correct? and would that start the rom from scratch again?
Once in cm9, if you reboot, it will put you into recovery again. From there you either reboot system and that takes you back into stock, or, you install zip, install from internal sdcard, go to multi boot/cm9/boot_cm9.zip and that will take you back to cm9, just as you left it, not from fresh install.
Keep stock, keep recovery , keep custom kernel rom!
If the reboot options are eventually set up properly in the cm9 (or any custom rom) rebooting from cm9 can put you right back in cm9, I think.
Sent from my SCH-I535 using Tapatalk 2
silasrye said:
Once in cm9, if you reboot, it will put you into recovery again. From there you either reboot system and that takes you back into stock, or, you install zip, install from internal sdcard, go to multi boot/cm9/boot_cm9.zip and that will take you back to cm9, just as you left it, not from fresh install.
Keep stock, keep recovery , keep custom kernel rom!
If the reboot options are eventually set up properly in the cm9 (or any custom rom) rebooting from cm9 can put you right back in cm9, I think.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot! Will try this now!
---------- Post added at 06:00 PM ---------- Previous post was at 05:38 PM ----------
Good stuff!
Thanks for the information.
I think i might make a video guide on this. Im excited. Haha:laugh:
You should, it's very exciting, I wanted to make one, but the only camera I've got is on my phone.
I still would love to see the bootloader unlocked, but really, dual booting with a stable rom as backup is pretty sweet. At this point I'm looking forward to the ril fix more than the bootloader cracking.
Sent from my SCH-I535 using Tapatalk 2
silasrye said:
You should, it's very exciting, I wanted to make one, but the only camera I've got is on my phone.
I still would love to see the bootloader unlocked, but really, dual booting with a stable rom as backup is pretty sweet. At this point I'm looking forward to the ril fix more than the bootloader cracking.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I will tomorrow, when nobody is home. But I'd have to record it with my Bionic.
If you wanted to reverse this, all you would have to do is delete the multiboot folder, correct?
I'm not sure about that, it might be better to try and ask team epic
Sent from my SCH-I535 using Tapatalk 2
NightxFall said:
If you wanted to reverse this, all you would have to do is delete the multiboot folder, correct?
Click to expand...
Click to collapse
Yes that is correct. It is all consolidated in that folder. It creates separate images to be used for boot, system, and data that can be deleted easily.
Will do this when CM9 gets data Thank you!
Installed this last night, including the kexec CWM. Works great except for the data, as expected.
Wicked fast; can't wait for the RIL to be taken care of. Like someone else said, I'd rather see that happen now than bootloader unlock.
---------- Post added at 11:05 AM ---------- Previous post was at 10:49 AM ----------
Question-
Since we're using the Sprint SGS3's CM9 nightlies, will data ever work?
I mean, is team Epic working on the VZW RIL, or is someone else, or are they the same (spr/vzw)?
I'm a little confused by this bit.
If you followed the guide completely you should be using invisiblek 's cm9 for i535, Verizon. I don't really know what's the difference, but we aren't just using the sprint nightlys so I believe the goal is to achieve data at some point and that there are folks working on it.
Now I'm going to stray just a bit and mention that I believe it was dhacker that got data running on the Motorola devices,
Edit: he is working on the vzw sgs3,
Check @dhacker29 on twitter
Sent from my SCH-I535 using Tapatalk 2
silasrye said:
If you followed the guide completely you should be using invisiblek 's cm9 for i535, Verizon. I don't really know what's the difference, but we aren't just using the sprint nightlys so I believe the goal is to achieve data at some point and that there are folks working on it.
Now I'm going to stray just a bit and mention that I believe it was dhacker that got data running on the Motorola devices, I had a bionic when he was working on it. He may have some advice for figuring out a verizon lte ril.
http://droidmodderx.com/2012/02/10/ics-for-the-bionic-now-has-4g-lte-5-5-902/
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
cvpcs is heading up the effort to fix RIL. He updated IRC last night that he ruled a lot of issues out and had some plans to try a few approaches.
One difference with the VZW S3 is that I believe it is their first phone to have the LTE radio on the SOC instead as a separate package. I did notice that he has a hijack solution to automatically kexec a custom (CM) boot.img without having to go through recovery.
Basically, he is using the hijack used for the DroidX to interupt the normal initialization process. Then instead of killing all processes and substituting the custom init, he is killing all processes then kexec'ing the completely separate CM boot.img. This gives us a clean boot solution, and severability from the stock boot.img. Now that he has this working(meaning he can easily try out different builds without dealing with less clean hacks), he is putting his efforts into RIL.
So, once RIL is fixed, we should have no reason not to have a fully working CM9 and possibly CM10 build (it appears he is applying these patches to a jellybean branch).
silasrye said:
If you followed the guide completely you should be using invisiblek 's cm9 for i535, Verizon.
Click to expand...
Click to collapse
You're right, and I did.
confused myself on that one, lol...
I can't get this to work for the life of me i have tried with the touch recovery flashed manuelly and through ezrecovery app. My script editing and repackaging went off with out a hitch. once I go to fakecwm and flash boot-cm9.zip it completes the install and nothing happens so i click reboot phone and it boots into beans rom. I know my recovery is kexec compatible because I have already loaded invisibleks kernel via kexec method. Any ideas ?
Sent from my SCH-I535 using Tapatalk 2
rendering the video atm . then uplaoding to youtube
Did you remember to put boot.img into your zip?
If so I guess wait for the video. It looks like this will soon be obsolete however
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I535 using Tapatalk 2
Here's the video.
http://www.youtube.com/watch?v=emDdQmNXLi8
Sent from my locked Verizon Samsung Galaxy S III
I think this is what you meant
https://plus.google.com/105844328547178759011/posts/NaZUCL6oe1q
Yes, problem is, if there is a way to share or even copy the url of a google+ post from the Google+ app, I don't know how. Do you?
Sent from my SCH-I535 using Tapatalk 2
Related
Team Epic announces a proof-of-concept source-built kernel for the Verizon SGS3, complete with kexec hardboot support. This kernel serves two purposes:
1. To be included in custom recovery images, as it proves the capability of booting-via-kexec custom kernels from recovery.
2. To serve as a proof-of-concept boot kernel, to demonstrate that custom kernels are capable of running on the Verizon SGS3 in its present form.
Please see our blog post, Kexec, and a Proof-of-Concept Source-Built Kernel for the Verizon SGS3, for full details and source links.
CyanogenMod's Team Epic specializes in Sprint's flagship Android phones on Sprint.
If you appreciate our work, please consider supporting us with a tiny contribution. Thanks!
Awesome! Thank you so much for your guys efforts
Sent from my HTC Rezound via Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MyColorScreen
Good luck guys.
☞ sent from my GS3
Just to confirm, the kexec hardboot approach used here is a bit different from the typical kexec. The main difference is that we actually perform a hardware reboot, reinvoking the bootloader just prior to booting the kexec'd kernel.
The advantage to this approach is that it maintains a high-degree of compatibility and minimizes buggy behavior. The disadvantage is that it requires that the bootloader is capable of booting custom recoveries, which the present Verizon SGS3 bootloader is capable of doing.
Thus, it's very important that folks do not apply any over-the-air (OTA) update, until it is confirmed that custom recovery booting remains intact.
If it eventually arises that booting from a stock kernel/recovery is necessary, then it's likely a bunch of kernel bugs will have to be fixed, and it might still have compatibility issues observed in previous kexec attempts. It's linked in the blog post, but there's a bit more of a technical description of the hardboot approach in this old thread.
Thanks to invisiblek and captjtkirk for testing.
you guys are awesome xda has the best devs ever! I worship you guys!
Wow! Thanks for taking the time to do this even though you guys aren't vzw owners. Great example of how great this community is.
Sent from my DROIDX using xda app-developers app
Unbelievable...you guys are awesome.
Jelly Bean here we come!
mkasick said:
Thus, it's very important that folks do not apply any over-the-air (OTA) update, until it is confirmed that custom recovery booting remains intact.
Click to expand...
Click to collapse
Forgive my paranoia, but does Verizon have the ability to force an OTA without us pressing an "OK" button?
Thanks to all who worked on this, you're awesome!
jh120 said:
Forgive my paranoia, but does Verizon have the ability to force an OTA without us pressing an "OK" button?
Thanks to all who worked on this, you're awesome!
Click to expand...
Click to collapse
nope. you have to accept the OTA
Just a question does the kexec allow the sgsiii to use both cores. I have heard that kexec on both the droid razr and droid 3 doesn't allow for dual core yet. Any such issues with sgsiii or is it too soon to tell?
Sent from my DROID X2 using xda app-developers app
Neverendingxsin said:
nope. you have to accept the OTA
Click to expand...
Click to collapse
Depends. My rezound didn't ask. I would wake up with my phone in recovery. It would fail to install the update because the stock recovery wasn't there but it never gave me a choice to install or refuse
Sent from my ADR6425LVW using Tapatalk 2
Say we needed to return to stock, can we just use Odin, flash back the ROM or would their be a bit more to it?
And THANKS! You are just missing the raised finger picture to Verizon over this.
densetsu86 said:
Just a question does the kexec allow the sgsiii to use both cores. I have heard that kexec on both the droid razr and droid 3 doesn't allow for dual core yet. Any such issues with sgsiii or is it too soon to tell?
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
I know this was an issue back in April(?) I haven't read anywhere that this has changed and I am curious to know this as well.
skennelly said:
I know this was an issue back in April(?) I haven't read anywhere that this has changed and I am curious to know this as well.
Click to expand...
Click to collapse
According to Noobnl in the IRC channel, the dual core thing isnt an issue since its a hard reboot so it reloads the bootloader; "this is a more advanced form kexec."
Glad to see some love from familiar faces. This is one if those times when i nuts being on sprint. From the galaxy tab, to the og epic, to the touch, sprint has allowed great things to happen on their devices. Now in big red, it's great to see we can use/reuse stuff across networks.
Big thanks!
Sent from my DROID RAZR using Xparent ICS Tapatalk 2
ceo.mtcl said:
Good luck guys.
☞ sent from my GS3
Click to expand...
Click to collapse
+1
densetsu86 said:
Just a question does the kexec allow the sgsiii to use both cores.
Click to expand...
Click to collapse
In short, yes.
Longer answer:
Traditionally kexec works by having one instance of the kernel boot a second instance directly, that is, by avoiding the bootloader. For this to work, every kernel driver has to shutdown in such a way that the same driver (in the kexec'd kernel) can revive and restart the hardware it controls.
The problem is that some, maybe many, drivers aren't actually capable of doing that. For the most part, it's a feature only needed by kexec, so unless the device manufactuer is specifically targetting kexec support, usually one or more drivers will put some part of the hardware in a confused state. That's the main source of compatibility bugs with kexec.
Now, what we do in the kexec hardboot approach is use the Linux kexec infrastructure to load and stage a new kernel in memory. Then we perform a hardware-level reboot, reinvoke the bootloader, and then at the very beginning of the recovery kernel code, we check to see if there's a kexec'd kernel out there in memory and if so, jump to that instead.
The advantage with this technique is that once the kexec'd kernel is booted, the environment is the exact same as if it was a kernel flashed to the device--there shouldn't be any hardware compatibility issues.
As it turns out, the one compatibility thing we have seen, which is unusual reboot behavior, isn't actually an artifact of kexec. The same thing would happen if you flashed a "boot kernel" to the recovery partition and booted it directly.
---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------
ErylFlynn said:
Say we needed to return to stock, can we just use Odin, flash back the ROM or would their be a bit more to it?
Click to expand...
Click to collapse
This is a temporary mechanism. To return back to the stock kernel, simply reboot the device.
To remove the custom recovery and fully flash back to stock, yes, you would use Odin.
Great work guys. You guys are awesome.
Amazing news!
So when you say you just reboot to get back to the stock kernel, is it a certain way of rebooting?
As in, if you were running soap and a kexec aosp kernel and rebooted and it forced you to the stock Samsung kernel, the phone wouldn't boot right?
Sent from my ADR6425LVW using xda app-developers app
Clockwork Mod Touch for the Epic 4G!!!!!!!!!!!!!!!!!!!!!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Everything I used to create the Zip is in here: http://d-h.st/zIL
I used unpack-bootimg.pl (I forget where that came from) to unpack an existing CWM Touch recovery.img from the Nexus S 4G
Then, I unpacked an existing boot.img from our device using zman0900s tools here: http://forum.xda-developers.com/showthread.php?t=1405284
Then, I added the etc/recovery.fstab and the default.prop from the epic to the nexus s 4g's recovery img.
Then, I repacked using a modified tool I made based on nubecoder's boot.img repack tools: https://github.com/nubecoder/create_boot.img
Then, I added the newly made ramdisk-recovery.img to Dees_Troy's TWRP zip.
Instructions:
Just flash this zip in any MTD recovery: http://d-h.st/Wfq and enjoy the new recovery after you go to advanced>reboot recovery
Unfortunately, due to the way our boot.imgs are packed, this recovery will be replaced when you install a new kernel or ROM, but the recovery replacement does not occur until you reboot recovery, so all you have to do is flash whatever you were flashing, then flash the CWM Touch zip and then recovery will stay.
On stock touchwiz ROMs, flash this modified version of Shadow Kernel that includes the recovery
http://forum.xda-developers.com/attachment.php?attachmentid=1419586&d=1350836408
There are probably other ways to build the recovery, but none of them worked for me... not Koush's Builder and not building from source
Anyone can add this recovery to their kernel by extracting a boot.img using zman0900s tool, then adding my initramfs_cwm folder in the build script zip at the beginning of my post, then repack using nubecoder's tool.
Thanks to Koush for CWM
Thanks to our CM team for the device specific files I pulled to make this possible
Thanks to Dees_Troy for his TWRP zip I based this on
Thanks to nubecoder for his create boot image zip
Thanks to zman0900 for his extract boot image zip
First. About to try now. Thanks for this.
Sent from my SPH-D700 using xda premium on cm10 nightly
Second. Been waiting for this for a long time. Thanks Xbox
Sent from my SPH-D700 using xda app-developers app
softbricked
...
Successfully worked on my phone.
Sent from my SPH-D700 using xda app-developers app
Weird that it softbricked you. It worked fine for me. I wouldn't have posted it otherwise. Try again after you odin stock.
Thanks a million for this xbox! Been waiting a long time to see a touch cwm!
Sent from my Epic4G using xda developers premium[HD] app
No problem guys.
*Ahem* I'd like to file a complaint if you will. I flashed this and my phone stole my little sister, and obviously since you put no disclaimer in this thread I'd like to formally blame you.
Can't wait to get the new epic... an awesome ex epic owner may be sending me his for free... I know what recovery I will be using! Thanks Xbox!
AproSamurai said:
*Ahem* I'd like to file a complaint if you will. I flashed this and my phone stole my little sister, and obviously since you put no disclaimer in this thread I'd like to formally blame you.
Click to expand...
Click to collapse
Still better than your sister stealing your phone...
xboxfanj said:
Still better than your sister stealing your phone...
Click to expand...
Click to collapse
I would like to officially 2nd this statement!
Heh, good work Jake. I'm sure people will greatly enjoy this.
Great job Jake..Didn't think we would ever see this. So where this is based off of twrp, would it be possible to create an inject.cwm file like twrp has so there is an option to re inject after a flash?
Sent from my SPH-D700 using Xparent SkyBlue Tapatalk 2
Thank you xbox, good works
no soft brick issue in here and works fine
Sent from my SPH-D700 using xda premium
Took an hour to redo my phone. At theater to see paranormal activity 4. Will re flash when I get home. I don't know why it soft bricked. I really want cwm touch. All I did was flah the zip. No rom update or anything else. But all the positive comments from everyone else gives me hope. But just in case I will re download in case it was a bad dl.
Sent from my SPH-D700 using xda premium
Jmax0420 said:
Took an hour to redo my phone. At theater to see paranormal activity 4. Will re flash when I get home. I don't know why it soft bricked. I really want cwm touch. All I did was flah the zip. No rom update or anything else. But all the positive comments from everyone else gives me hope. But just in case I will re download in case it was a bad dl.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
So want to see that movie... im jealous... and ya I would have to say it was probably a bad download seens how nobody else has had a problem... anyways goodluck and enjoy the movie!
Uhhhhhhhhhhh... I was waiting too long for this "touch", then I hopped onto TWRP days ago AND deleted ALL but one CWM backup... and here's the long-awaited touch but aww... Since TWRP everything's a hell lot easier but lost that sense of geek...
PLUS: Would like to report that TWRP does not work with "Stock FC09 Prerooted MTD", stuck at the Samsung logo too. If same phenomenon here, I guess it's that InjectTWRP won't work with stock kernels (CM and other kernels based on CM are all fine) ... @xboxfanj interested in the issue?
Sent from Nokia N900 w/ Android 2.3.7
Jmax0420 said:
Took an hour to redo my phone. At theater to see paranormal activity 4. Will re flash when I get home. I don't know why it soft bricked. I really want cwm touch. All I did was flah the zip. No rom update or anything else. But all the positive comments from everyone else gives me hope. But just in case I will re download in case it was a bad dl.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yeah thats the problem. You need to be on an mtd rom. So, Odin stock then cwm, then flash any cm rom, then flash this cwm.
Sent from my GT-P7510 using Tapatalk 2
xboxfanj said:
Yeah thats the problem. You need to be on an mtd rom. So, Odin stock then cwm, then flash any cm rom, then flash this cwm.
Sent from my GT-P7510 using Tapatalk 2
Click to expand...
Click to collapse
"God damn it, Gump! You're a god damn genius! This is the most outstanding answer I have ever heard. You must have a goddamn I.Q. of 160. You are goddamn gifted, Private Gump!"
Substitute "Xbox" for "Gump" and you've got it. Jake, your genius is truly amazing and inspirational.Thank you...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We Are Proud To Introduce Our Latest Efforts
AoCP
CP 4.6
Jelly Bean
~
Its a new source that we have put together based from CM10 and AOKP.
~
It is Android Open Collective Project.
~
Many thanks goes to:
Google for the base
-> Cyanogen-mod and AOKP<-
for all the time, and efforts into showing us the way.
And lets not forget the work on the lovely mods included here.
With out you, our eyes would still be closed.
This Is Jellybean 4.1.2
This is compiled from source.
It is for i997
It is...
Rooted
Deodexed
Zipaligned
It has....
OTA
Lots of customizations
toggles
weather
Custom apps
New Features
Wallpapers
Themes
[Changelog]
4.2.1
Build script adjustments
Minor fixes
4.4
Added autohide for quick toggles
Added clickable clock and date in notification panel
Various bug fixes and updates
4.6
Added AOKP torch toggle
Enable/disable QuietTime
Added a couple of themes
Fixed toggle/weather alternate hide
Some performance updates
***Make sure you are on gingerbread bootloaders before flashing this rom***
HOW TO INSTALL
1. Factory Data reset
2. Wipe Dalvik
3. Format System
4. Install Zip from Sdcard
5. Boot up
6.Install GApps
7. Enter google info
(If you are coming from a cm9, cm10 or AOKP based ROM, it is recommended flashing to stock first)
(May have to remove external sdcard if coming from gingerbread)
(Do not flash gapps for ics, or you will lose your camera)
Download
AoCP CP 4.6
Credits
Cyanogen-mod
Team Kang
Team Hacksung
TheCollective Team
Johnsondr80
Robm1911
DMAN3285
Mortem Tuam
Ruger94
Fezzy102
ee23hd2
flappjaxx
joedv
LiquidSmooth
(For the propmodder source)
scott.hart.bti
(For kernel source and infuse4g build script references)
&
Special thanks to 3/75th Ranger for all the bootloops
As Always, We are not responsible if it messes up your phone
got mine
Downloading now, thanks for the new release!
First
Sent from my ADR6425LVW using xda premium
OK just some questions, very nice looking rom excited to try!
Is this MTD based, or if we are on a MTD based JB rom do we need to maybe Odin back to GB?
Again just curious, is this based off scott's kernel, if so which one?
thanks for new rom...congrats sir..
hazard66 said:
OK just some questions, very nice looking rom excited to try!
Is this MTD based, or if we are on a MTD based JB rom do we need to maybe Odin back to GB?
Again just curious, is this based off scott's kernel, if so which one?
Click to expand...
Click to collapse
It is based on teamhacksungs kernel via Dman, and yes it is MTD based. As far as I know, I'm not sure if you will have to Odin back to stock, I guess we will find out soon enough...
crt60 said:
It is based on teamhacksungs kernel via Dman, Some of the code is based off of Yuma, and yes it is MTD based. As far as I know, I'm not sure if you will have to Odin back to stock, I guess we will find out soon enough...
Click to expand...
Click to collapse
I flashed this coming from scotts 2.50 paranoid rom. I went to reboot and it hung on the samsung screen for about 15 min. Did a battery pull went to boot recovery, and wasnt able to do that, so I returned to stock.
I am going to play with the ROM though, so Im gonna start back over from scratch and hopefully get to use it before I get too sleepy. Family guy is on so Im good for now, lol. ROM sounds and looks pretty cool and im always game to try and test out new things, so im gonna try it. Thank you for bringing a new toy to the Infuse forums. Thanks for you and your team's hard work. :good:
Downloading, Thank crt60 for the new rom. :good:
Very excited to try this. I am on Scott’s CM10, can anyone confirm if I can flash from CM10(after wiping and formatting of course)? I won’t be near my home PC until late tonight and didn’t want to risk going through my whole day with a bricked phone
lazerus06 said:
Very excited to try this. I am on Scott’s CM10, can anyone confirm if I can flash from CM10(after wiping and formatting of course)? I won’t be near my home PC until late tonight and didn’t want to risk going through my whole day with a bricked phone
Click to expand...
Click to collapse
If that's the case I would hold off till your at a pc. There has been one report of hanging at the boot screen a couple posts up.
Confucius and The Collective say good things come to those who wait...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Great work CRT
This is MTP by default, however once your booted you should be able to go to settings>storage>hardmenukey> and change your preferred USB connection type.
Just saying. Check it out.
There has been problems with people realizing this on other devices lately.
Hope everyone enjoys and don't hesitate to spank a thanks button if your enjoying our work or if we've help you in anyway.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
lazerus06 said:
Very excited to try this. I am on Scott’s CM10, can anyone confirm if I can flash from CM10(after wiping and formatting of course)? I won’t be near my home PC until late tonight and didn’t want to risk going through my whole day with a bricked phone
Click to expand...
Click to collapse
On some of the other devices, when people are having problems getting it flashed most users recommend coming from cm10
I would suggest creating a nandroid back up of your current ROM and should you run into a problem, you could restore it and be back to a use able phone.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I got it to boot just fine after returning to stock. Running it now, and so far so good. Very smooth. I love the orange theme. Never really been a fan of the color but it looks good in this.
Sent from my SGH-I997 using xda app-developers app
hellorenauldo said:
I flashed this coming from scotts 2.50 paranoid rom. I went to reboot and it hung on the samsung screen for about 15 min. Did a battery pull went to boot recovery, and wasnt able to do that, so I returned to stock.
I am going to play with the ROM though, so Im gonna start back over from scratch and hopefully get to use it before I get too sleepy. Family guy is on so Im good for now, lol. ROM sounds and looks pretty cool and im always game to try and test out new things, so im gonna try it. Thank you for bringing a new toy to the Infuse forums. Thanks for you and your team's hard work. :good:
Click to expand...
Click to collapse
I just flashed from 10/22 CM10 build, by simply following 3 cleanups - format /system flash this ROM
absolutely no problems, first time boots up.. I am loving the themes, on top of already existing JB butter smooth.
Awesome job
IMEI issue, I install from GB rom.
My fixed, return to stock GB rom to ICS rom and to AOCP (JB) rom.
CR..... Thanks for looping credit. I couldn't have done without your help.
Sent from my SGH-i997 using Tapatalk
Nice to see this got out! was beta testing this for dman at one point till he joined cm10. He had everything working perfectally but the camera if i remember right i'll try this version
paluinfusion said:
I just flashed from 10/22 CM10 build, by simply following 3 cleanups - format /system flash this ROM
absolutely no problems, first time boots up.. I am loving the themes, on top of already existing JB butter smooth.
Awesome job
Click to expand...
Click to collapse
Same here no problems booting up, standard 3 wipes
Sent from my SGH-I997 using Xparent SkyBlue Tapatalk 2
PARTY ROCK IS IN THE HOUSE TONIGHT!!! GANGNAM STYLE! :Excitement:
After a bunch of work, I present to you WORKING CLOCKWORKMOD!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*Big thanks to those of you who worked on the d2att, that code was invaluable for getting a working graphics driver and some unknowns I could not see.*
Confirmed on:
- SGH-i497 (ATT)
- SGH-T779 (T-Mobile)
You can also use this to get ROOT!
Requirements:
- Windows Computer with Samsung Drivers installed
- Odin if on Windows/Heimdall on Linux
- sdcard in the /sdcard slot
1. Download my Odin package here:
https://dl.dropbox.com/u/58849669/espresso10att/cwm_recovery_espresso10att_childofthehorn.tar.md5
2. Download SuperSu from Chainfire and copy to your sdcard:
http://forum.xda-developers.com/showthread.php?t=1538053
3. Open Odin (as administrator) and hit the "PDA" button, remember to uncheck the reset
4. Mount Device into Download Mode (PWR, Vol) and Hit go on Odin once it appears.
5. Once Finished, Reboot into Recovery
6. Backup your existing image
7. Flash SuperSu from SDcard
8. WInning.
TO RETURN TO STOCK RECOVERY USE THIS ODIN FLASHABLE:
https://dl.dropbox.com/u/58849669/espresso10att/espresso10_stock_childofthehorn.tar.md5
****In the process of doing this, I had to bust my /system in order to get the files required.
I would strongly appreciate if anyone can send me a copy of their boot.img and either a copy of their system.img or system.tar.ext4 made by clockworkmod. ****
Part of doing this was integrating everything with the d2-variant build chains in CM9 and CM10. Say thanks in the Thread if you like this or promote this thread so it makes it to the main page.
GITHUB: https://github.com/childofthehorn/espresso10att
Thanks Guys!
AWESOME!!!
Sweet, thanks so much, worked amazing on my T-Mobile Tab 2, got root awaiting a CM9 ROM. No rush, just happy to have my root on my plaything. Keep up the amazing work.
FINALLY! You just made my evening! Incoming Donation.
Confirmation number: 75052748C2563800A
---------- Post added at 09:43 PM ---------- Previous post was at 09:30 PM ----------
I have the ATT device as well, running a full stock rooted backup as we speak. I will get it uploaded when completed. Please hold...
Glad to hear it guys!
Very happy to know it works just as well on the T-mobile one.
I can get some custom ROMs going if I can get a copy of someone's /system and boot.img .
First goal is CM9 and then a migration to CM10.1 once that is pretty stabile.
Luckily for us, we have two amazingly complete CM sources with the d2att ( and nice d2 kernel chain!) and p5100 which cover most of our requirements as far as setup and drivers/libs.
Thank You for the support. If you like this, check out my site, say thanks, and/or vote this up onto the main site for a post so it is more visible.
I will be posting the original stock recovery.IMG in Odin flash able later tonight.
Sent from my Galaxy Nexus using Tapatalk 2
Childofthehorn said:
Glad to hear it guys!
Very happy to know it works just as well on the T-mobile one.
I can get some custom ROMs going if I can get a copy of someone's /system and boot.img .
First goal is CM9 and then a migration to CM10.1 once that is pretty stabile.
Luckily for us, we have two amazingly complete CM sources with the d2att ( and nice d2 kernel chain!) and p5100 which cover most of our requirements as far as setup and drivers/libs.
Thank You for the support. If you like this, check out my site, say thanks, and/or vote this up onto the main site for a post so it is more visible.
I will be posting the original stock recovery.IMG in Odin flash able later tonight.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
If I was home I could help with my T-Mobile tab 2. Currently out stealing cars legally tho. Just glad for root and I'll help if I can in anyway.
Sent from my ThunderBolt using xda app-developers app
Amazing work! Thank you.
Will this wipe my current apps and data?
dmunjal said:
Amazing work! Thank you.
Will this wipe my current apps and data?
Click to expand...
Click to collapse
Not at all. You are merely flashing Root over your existing install. I also suggest that you make a backup prior to installing SuperSU. All of your non-native apps and contacts, etc are on /data and SuperSU does not touch /data at all.
Just posted up the Original Stock Recovery in an Odin Flashable if you want to return to stock.
Thanks for figuring this out. If you still need boot img or anything from the t-mobile version let me know. Also is it possible to add the t-mobile model number (SGH-T779) to the thread title, it would help others to find it.
Thanks again
Edit: I just saw that you added the model to the OP. Thanks again
Yeah I can extract system images from the CWM blobs if that is all you have. However a simple tar ball of /system and your boot.img would be helpful.
No more help at this time, however that might change with CM9 integration for T-Mobile.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks a lot !, I had waiting a long time for this.
I have a GT-P5113 and I have the latest jellybean update (4.1.1). Do you know if this method works for my tablet, and if it doesn't, do you know a method for this model?
Sent from my GT-P5113 Galaxy Tab 2 10.1, the ipad pwning monster
Jooni said:
I have a GT-P5113 and I have the latest jellybean update (4.1.1). Do you know if this method works for my tablet, and if it doesn't, do you know a method for this model?
Sent from my GT-P5113 Galaxy Tab 2 10.1, the ipad pwning monster
Click to expand...
Click to collapse
^ This is covered elsewhere:
http://forum.xda-developers.com/showthread.php?t=1657056
BTW - The SGH-i497 has been added to CF-Autoroot by Chainfire. Now get rootness the easy way.
http://autoroot.chainfire.eu/
The T779 is in there as well.
For the T mobile users I will be putting together a Device tree for you guys as well. Let me know if there is anyone who wants to head up the CM9 port for the T779.
Childofthehorn
will this root work with the SCH-I915 Verizon ?
warlord002 said:
Childofthehorn
will this root work with the SCH-I915 Verizon ?
Click to expand...
Click to collapse
I honestly have no idea! That Model Number did not appear in the code, however the hardware is the same and considering the partition table is almost exactly like the D2 it just might.
IF YOU DO SO, YOU DO IT AT YOUR OWN RISK. I am not responsible!
Worst Case scenario, you will not be able to "wipe" your device in case of a failure easily until you perform a Manual update using Kies (usually the Samsung firmware has the recovery.img in it, but no guarantees!).
Get me a Copy of the Recovery.img or Full Odin Image for that device and I can probably make it work. The same would be true of the new SPH-P500 for Sprint. I do not have a Verzion version so I cannot test it. If you are a willing volunteer, let me know.
The Gtab2 10.1 LTE is Basically a Blown up Galaxy S3. However I am quickly finding that the AOSP D2 Kernel source doesnt like me much... erg.
Im out of town now but if no one shares their system I will dump mine when I get back sat morning.
Sent from my SGH-T779 using Tapatalk HD
Childofthehorn;
Get me a Copy of the Recovery.img or Full Odin Image for that device and I can probably make it work. The same would be true of the new SPH-P500 for Sprint. I do not have a Verzion version so I cannot test it. If you are a willing volunteer said:
I don;t know how to get that img or Odin image for you from my verizon tab 2 . but if you tell me how to do so i will surely try to make one ,
thanks
Click to expand...
Click to collapse
All the rooting steps are the same as the other gtab 2 10.1???
Yes. Basically.
These are the standard root steps for all Samsung devices with unlocked boot loaders.
Its the software and images that you are putting on your device which are different.
Sent from my Galaxy Nexus using Tapatalk 2
GUMMY
As of October 9, 2014 Team Gummy has disbanded. The final M4 release can be found here:
M4 Final Release
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gummy ROM is made for speed, stability and to stay as closely in line with AOSP as possible while still supporting a large amount of devices and giving you all of the features you love. It isn’t slowed down by features you’ll never use nor is it so slim as to be just another AOSP build.*
Features:
* New base built from AOSP
* Status Bar Mods
* Hardware Key Mod
* Many Wallpapers
* Performance Control
* Application Permission Controls
* Carrier Label Options
* Lock clock widget
* QuickSettings
* Theme Manager
Device Specific:
Whats not working...
* what else (you tell us)
ChangLOG:
Please review out Gerrit instance to keep up with changes daily...
Instructions for installations:
1. Download ROM
2. Download Gapps
3. Push to sdcard
4. Reboot Recovery
5. Wipe Data and Cache
6. Install ROM
7. Install Gapps
8. Reboot System
Contributions:
- Thank you to Cyanogenmod for device and hardware repositories. Without this, porting * * Gummy to QCOM devices would have been nearly impossible.
- Thank you to Google for the best source code.
- Androidfilehost.com for hosting our file servers!
Team Members: In alphabetical order
Primary Developers:
Cphelps76, Kejar31, DHacker29
Developers and Device Maintainers:
apascual89, Bkjolly, Buckmarble, BytecodeMe, Hashcode, hedwig34, Papi92, TDM
Artwork direction and development
Cphelps76, Kejar31
Github- https://github.com/TEAM-Gummy
Gerrit- http://review.gummyrom.com/#/q/status:open,n,z
Twitter- @gummyRom
GAPPS - we now recommend PA-Gapps
As of 2/19 the build is know know as d2lte. You can download it here:
Gummy ROM
BOOM! I was hoping for a pure AOSP and/or Gummy.
I've heard some good things about Gummy. Can't wait to try it out. But before I go through the trouble of flashing and such, is there circle battery w/ percentage on this? That's ultimately the deal breaker for me so far on KitKat
DubleJayJ said:
I've heard some good things about Gummy. Can't wait to try it out. But before I go through the trouble of flashing and such, is there circle battery w/ percentage on this? That's ultimately the deal breaker for me so far on KitKat
Click to expand...
Click to collapse
Yes, circle battery w/ percentage is included. Using it myself right now.
Sent from my SCH-I535 using Tapatalk 2
Everybody make sure you are using the latest recovery . twrp 2.6.3.1 works for kit Kat previous versions do not.
Sent from my SCH-I535 using Tapatalk 2
Have you tested any of the custom kernels? I assume BMS and KT work, as they work with all the CM11 builds out there, but I thought I'd ask.
My deal breaker would be with Tap-to-Pay. Will this work with Google Wallet's TTP?
Downloading now. Really hoping this one doesn't have the FC and random reboot issues like some of the others.
chad783 said:
My deal breaker would be with Tap-to-Pay. Will this work with Google Wallet's TTP?
Click to expand...
Click to collapse
No Verizon phone will, due to the ongoing disagreement VZ has with the Google payment method. Don't expect ANY rom to come out with functioning tap-to-pay until Verizon works out their beef with Google. You can try some of the hacks people have posted for 4.3 roms, but I haven't seen anyone report that it worked on a 4.4 rom; make sure you use one of the older Wallet versions, because all newer versions for VZ devices have that functionality broken.
beepea206 said:
No Verizon phone will, due to the ongoing disagreement VZ has with the Google payment method. Don't expect ANY rom to come out with functioning tap-to-pay until Verizon works out their beef with Google. You can try some of the hacks people have posted for 4.3 roms, but I haven't seen anyone report that it worked on a 4.4 rom; make sure you use one of the older Wallet versions, because all newer versions for VZ devices have that functionality broken.
Click to expand...
Click to collapse
Other roms have got TTP to work.
Also, does FB sync with the contacts?
chad783 said:
Other roms have got TTP to work.
Click to expand...
Click to collapse
Yes, other 4.3 roms got it to work, through using the hack and an older version of Wallet.... which I already said was the case. No one has successfully had T2P work with Wallet on a 4.4 rom on a VZ Samsung device yet... at least not that's being reported on xda. You will not find T2P working on a flashable rom until Verizon and Google settle their dispute; devs are not going to incorporate the hack because it works for some and not for others.
If you need T2P, try the 4.3 hack and report back to us if it worked... otherwise, stick with a hacked 4.3 rom if you need the functionality.
---------- Post added at 01:07 PM ---------- Previous post was at 12:45 PM ----------
FYI... just flashed and didn't get a data connection. Tried the usual techniques to get it to work, but no dice. :/
On it an loving it. Great work. Only other thing I need on this ROM is RAM Usage Bar on Recents and a notification status bar toggles.
beepea206 said:
Have you tested any of the custom kernels? I assume BMS and KT work, as they work with all the CM11 builds out there, but I thought I'd ask.
Click to expand...
Click to collapse
I have not but I see no reason why they wouldn't work. Let us know how it goes
beepea206 said:
FYI... just flashed and didn't get a data connection. Tried the usual techniques to get it to work, but no dice. :/
Click to expand...
Click to collapse
Data has been working well for me. Sometime it takes a few minutes to hook up but has always come on eventually. Check under status your IMEI and see if you didn't lose it.
thanks running nice havent ran into any problems :good:
hedwig34 said:
Data has been working well for me. Sometime it takes a few minutes to hook up but has always come on eventually. Check under status your IMEI and see if you didn't lose it.
Click to expand...
Click to collapse
Ahh good call. I believe my IMEI was there (I glanced really fast), but it might not have been. Does a firmware flash remedy that? I've never had that issue before.
No a firmware flash won't do it. Best to flash to a backup where it was there. Then make backup of the IMEI. There is a script I think on xda that will do it. I keep a copy of the back on my PC too just in case.
Sent from my SCH-I535 using Tapatalk 2
beepea206 said:
Ahh good call. I believe my IMEI was there (I glanced really fast), but it might not have been. Does a firmware flash remedy that? I've never had that issue before.
Click to expand...
Click to collapse
hedwig34 said:
No a firmware flash won't do it. Best to flash to a backup where it was there. Then make backup of the IMEI. There is a script I think on xda that will do it. I keep a copy of the back on my PC too just in case.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Here's the link you were looking for - http://forum.xda-developers.com/showthread.php?t=1852255
I did method A and B just to be safe
Nice work. Just an FYI Nightly is spelled wrong in the title. Keep up the good work!
Sent from my SCH-I535 using xda app-developers app
DubleJayJ said:
Here's the link you were looking for - http://forum.xda-developers.com/showthread.php?t=1852255
I did method A and B just to be safe
Click to expand...
Click to collapse
Perfect. Thx! I didn't know I could do this from a terminal, so now I'm set!