Database Info

New here, E4GT Need some help

Hey guys, ok so I am coming from two HTC Heros (CMDA Sprint)
Was running cyanogenmod on both (me and the wife) loved it.
Now that I have the E4GT, I went ahead last week and used ODIN to install LoStKernel.
Now it did give me root and I have used apps like rom toolbox and setcpu.
My main problem is it seems these samsung devices are a lot trickier to tinker with.
Basically I am looking to get Clockworkmod so I can flash roms and make nandroid backups.
From what I have read, I need a kernel that supports and/or has CWM in it.
I tried flashing CWM with rom manager, and it installed - but I have no option to backup/restore I can only flash a zip or clear cache.
There are SO MANY things posted in the development section and I do not know which kernels are the latest, best etc.
I need:
a) CWM/busybox
b) overclocking support
c) FULL stock functionality (no loss of wifi or something stupid like that)
From what I am understanding the kernel is included with a rom. But I can't flash a rom without CWM. So I am rooted but stuck with stock rom and it's kernel.
Confused, lol!
Can someone point me to a proper thread to get me CWM and a well supported ROM to install? Can I get CWM working fully on the stock kernel/rom?
If someone can point me to the right direction, maybe I can find a developer to donate to lol!

No love?
At this point I'm just trying to get cwm. Seems I may have already had it just didn't know it came with lostkernel and now I botched it using rom manager.
Sent from my SPH-D710 using XDA App

You can actually flash a new kernel with CWM in odin
Thats the easiest method
There are several, as for the best I dont know yet
Im still tinkering with my setup

I guess that's my main issue - I can't find one that has CWM, everything I am seeing is a ROM that needs CWM to install.
If I had CWM I'd be all set because then I can backup my setup and try new things without worry, but I don't want to use ODIN to try a kernel that CWM won't take, or isn't there, and then lose what I have ya know?

All set, seems I flashed a kernel that wasn't what it was supposed to be. I apparently flashed his earlier version (pre-LoStKernel) that did not have CWM5 it it.
Just used ODIN last night to drop in LoStKernel and kept root, but also have CWM5 now. After clearing my SD Card, made my first backup. 1.5GB, jesus! lol. Nearly my whole SD card... yes, it's from my old Hero, so, time to get a 32GB.

cwm 6.0.0.x on the infuse 4g

i see that the guys working on the jellybean port for the infuse are using cwm 6.0.0.5 or so -- how can i get this installed on my infuse without installing the new jellybean rom (yet) ?
just want to stick with aokp 40 until jellybean is done, but want to play with the cool new touch recovery too...

Some one would have to compile the recovery into the ics kernel....
Sent from my HTC PH39100 using Tapatalk 2

What's so new about it?...........

May want to read this before pulling the trigger.. http://forum.xda-developers.com/showpost.php?p=29037114&postcount=275

hazard66 said:
i see that the guys working on the jellybean port for the infuse are using cwm 6.0.0.5 or so -- how can i get this installed on my infuse without installing the new jellybean rom (yet) ?
just want to stick with aokp 40 until jellybean is done, but want to play with the cool new touch recovery too...
Click to expand...
Click to collapse
I can personally tell you that cwm 6 is not touch...I used it on my vivid and there was no touch...at least the vivid has no touch...ill flash the vivid cwm 6 again just to be sure...
Even better...can someone who has flashed jb say wether or not the cwm has touch?
EDIT: Cwm 6.0.0.5 does not have touch for the HTC vivid...not sure about the infuse though...for the vivid it works just like the old cwm...use volume to navigate, power to choose
Sent from my HTC PH39100 using Tapatalk 2

whether or not cwm has touch enabled or not does not have to do with its version.

The Jack of Clubs said:
whether or not cwm has touch enabled or not does not have to do with its version.
Click to expand...
Click to collapse
yes, i know that as ive seen others with touch...thats why i said not sure about the infuse, the vivid one is built from official cm source so i don't think CWM 6 naturally supports touch...as in touch is enabled by some sort of add on/code edit-i could be wrong as i didn't build it nor have i looked at the source or anything so this is all based off of my observations of the vivid cwm 6
-jack if you've used the cwm from scotts cm10 build can you let us know if it has touch...i would pm scott but hes busy and knowing whether or not a recovery has touch isn't really necessary.
either way...doesn't effect me, im not a fan of CWM any longer and likely will not use it again for flashing roms

enabling touch isnt that hard to do in cwm. if you used the aroma installer on something like aokp on the infuse, youve used touch in cwm on the infuse. i know however its not enabled in the cwm6 thats with the jb rom. its just not a priority to fix right now. but im sure after getting more things working, itll be added one day.

The Jack of Clubs said:
enabling touch isnt that hard to do in cwm. if you used the aroma installer on something like aokp on the infuse, youve used touch in cwm on the infuse. i know however its not enabled in the cwm6 thats with the jb rom. its just not a priority to fix right now. but im sure after getting more things working, itll be added one day.
Click to expand...
Click to collapse
thanks for the reply, yeah...im sure once everything is as stable as ics some one may look into adding touch, ive used aroma before so i know what your talking about there...im buying an infuse in a few hours so i will be able to actually test things out before i reply
as for aroma...i love it and i hate it...its cool that you get to customize your flash some what...but the size of the download can be so huge! especially if its an aroma built for the vivid...stock vivid is 600mb unzipped...zipped and compressed its 400mb add another few hundred megabytes in there for aroma add ons and your looking at one or two roms per gig lol

mg2195 said:
thanks for the reply, yeah...im sure once everything is as stable as ics some one may look into adding touch, ive used aroma before so i know what your talking about there...im buying an infuse in a few hours so i will be able to actually test things out before i reply
as for aroma...i love it and i hate it...its cool that you get to customize your flash some what...but the size of the download can be so huge! especially if its an aroma built for the vivid...stock vivid is 600mb unzipped...zipped and compressed its 400mb add another few hundred megabytes in there for aroma add ons and your looking at one or two roms per gig lol
Click to expand...
Click to collapse
love the touch CWM for the GNote...
http://forum.xda-developers.com/showthread.php?t=1584576
stock Gnote i downloaded was a one click oding 1gig the virgin stock...
Odexed & Stock Rooted, Zipaligned, Deodexed & CRT 600-700mg
most of the GNote custom ROM 600-650...there is work to use the aroma with the GNote again...for the add-ons....its gonna be a whooper...

So is the new CWM suppose to be touched based???
Sent from my SAMSUNG-SGH-I997 using xda premium

slicingtaco said:
So is the new CWM suppose to be touched based???
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Could be wrong...but just based off only official cm source I don't think its touch based...i think the touched based ones have some sort of modification to the cm source
Sent from my HTC PH39100 using Tapatalk 2

http://www.clockworkmod.com/rommanager <- both touch and nontouch recovery are both by clockworkmod. and again, version means nothing towards it. to get touch working in cwm, you just need to load touchscreen modules. theyre just not in any of the infuse versions yet.

Somehow i have cwm 6 while running ics paranoid android. I didn't do it on purpose

MattSoRaven said:
Somehow i have cwm 6 while running ics paranoid android. I didn't do it on purpose
Click to expand...
Click to collapse
With most non-samsung phones recovery is not built into the kernel(actually HTC are the only phones I know like this), its in its on little partion which means you can change kernels without changing recoveries
For the infuse the recovery seems to have always been tied into the kernel so when you flash a kernel you flash a recovery...
Now by you saying that you still have cwm6, that leads to believe that possibly Scott has somehow removed the recovery from the kernel...if that was the case though you'd think there would be problems with the recovery inside the ics kernel...so I'm thinking somehow your still running he jb kernel which somehow can still run ics??? Lol I'm kinda at a lost...that was just me typing my thoughts/thinking outloud/rambling on about recoveries
Makes me curious tho...
Sent from my HTC PH39100 using Tapatalk 2

I think you're right that the recovery was partitioned somewhere and didn't go away. I was on an ics kernel. I believe this based on the build.prop info saying it was a 6/20 kernel, everything worked fine including Wi-Fi, torch, etc.
I was on JB and used Zen's toolkit to "complete wipe" then used the toolkit to restore to PA.
Edit: I flashed the latest yuma kernel because i needed to change this thing asap. I also just noticed multiple kernels have 6/20 as a date. The yuma kernel is signed differently with an "aaron" in the name that the previous kernel didn't have and is has a 6/30. I would have grabbed a screen shot, but i have ppl coming over soon and need to charge it so i can answer calls.

Well matt...here's what Scott had to say, the recovery is not in the kernel...its in recovery (assuming that means in its a seperate partion) so I guess as soon as you get cwm 6 your stuck with it unless you Odin/heimdal back to stock...
Now you wanna hear something interesting/cool? If the recovery is in its own partion then this opens the door for more types of custom recoveries! I was already planing on building an ics kernel with twrp recovery baked in when I get an infuse to work with...the problem with that though is as soon as you flash a Rom you would lose my kernel/twrp...but if Scott has it in its own partion then as soon as there's a twrp for jb I would be able to compile it and not have to worry about it getting erased from flashes..
Here's a video of twrp in action...http://www.youtube.com/watch?v=D2VlpVKj1eI&feature=youtube_gdata_player twrp is my favorite recovery...its fully touch based recovery and you can also theme the recovery as the UI is built with xml codes...really cool-I have it on my vivid...its also based off cwm source...so its just as stable as cwm
EDIT...i like your profile pic/avatar...nothing like some $5 Hot N' Ready large pizzas lol
Sent from my HTC PH39100 using Tapatalk 2

it isnt in the kernel, it is a partition. you cant boot to something inside of a kernel file, that doesnt make sense. you do however need a kernel capable of running whichever version of recovery you want to use. since fastboot is not on this device and many other samsung devices, there is a sort of failsafe in which recovery is written onto the device during system boot. which is why when you flash from a touchwiz rom to aosp rom, you have to let it boot up and freeze, then go back into recovery and flash again. you can look up partition information in recovery.fstab.

The Jack of Clubs said:
it isnt in the kernel, it is a partition. you cant boot to something inside of a kernel file, that doesnt make sense. you do however need a kernel capable of running whichever version of recovery you want to use. since fastboot is not on this device and many other samsung devices, there is a sort of failsafe in which recovery is written onto the device during system boot. which is why when you flash from a touchwiz rom to aosp rom, you have to let it boot up and freeze, then go back into recovery and flash again. you can look up partition information in recovery.fstab.
Click to expand...
Click to collapse
Actually...recoveries are built into the kernel...why else would you get red cam by flashing entropies gb kernel zimage
And as you can see in the picture (twrp Samsung github) they even state that most Samsung's must have recovery built into kernel..
Now it may be different with aosp Roms...but for normal stock Roms and stuff, i know for a fact that kernels contain the recovery...
Sent from my HTC PH39100 using Tapatalk 2

hrm. maybe its some kind of uimage. dunno, doesnt really apply to the infuse though.

New to Android and been reading.

Hello everyone. I received my Verizon SG3 shortly after it came out. I have been doing reading as I am very new to android. This is my first android phone. Previously I had an EnV Touch. Hated that thing, but it did the job. So any who I now have this awesome kick butt phone and it has all the Verizon crap on it I cannot get rid of. I have rooted and the bootloader is unlocked. I used a windows program to gain root and then used EZ unlocker to unlock the bootloader. I have been looking and looking to figure out what rom I want to start with, I want JB, but don't want a lot of bugs ATM as i don't have all that much time to play with flashing and being still so new I don't want to end up with a brick. I tried my harderst to figure this out by reading, but the info seams so spread out, I kinda want to try the CM10 9-6 as I have read it is stable and not many bugs. My main question is about kernels. Am I correct in thinking they will get flashed just like my rom will in ROM manager? Or do I need to flash through CWMR? How do I know what Kernel to use? I have been reading the CM10 takes a different kernel than say synergy or stock. Or will the stock kernel work till I load the proper kernel. If I knew about the kernel and how vital it was to go with the ROM maybe I wouldn't be so paranoid. I have a friend with a GS2 and he told me the kernel has to go with the ROM and if the two don't mach then you could brick. I can't afford a brick my first time around.
If you could give me some advice or point me in the direction of some more reading that would be great.
Thanks
JB

All ROMs come with a kernel in them. Typically you just stay with it unless you want some extra features or what not. There are aosp kernels and kernels based on the stock firmware. If you use a touchwiz based rom you need to use a touchwiz kernel.
I don't think it will brick it if you interchange them. It will just boot loop
Edit: you flash kernels in recovery just like a rom. if you change kernels without changing roms you need to wipe cache and dalvik cache through recovery also.
Sent from my Nexus S 4G using xda premium

Back up your IMEI before flashing anything, alot of horror stories floating around. Development has some fantastic guides. After that, most of the "big gun" rom's here have kernels, and are for the most part consistently the same flash method through recovery. Cwm recovery is solid and reliable, start with that until you feel comfortable enough to venture off. Make sure it's version 6.0.1.2 (regular or touch) for any jelly bean based rom.
Sent from my SCH-I535 using xda premium

I backed up the IMEI with the terminal emulator. So if the error occurred it would restore with the proper IMEI. Should I back it up any other way too?
Also I'm planning on using the Rom manager to flash the Rom. Do you not recommend that or should I do it manually with CWRM?
Thanks for the replies. I'm still getting my feet wet and know all about searching before asking. Used to program dish.
Sent from my Galaxy S3 using Tapatalk.

Your call, depends how paranoid you are! I would flash manually, it's a control thing for me, I know what/how/when all was done. Using 6.0.1.2 touch is awesome, speeds flashing up considerably.
Sent from my SCH-I535 using xda premium

I might have to try the touch. I have standard 6 on there. The one you listed. Rom manager gives me the option to load touch too. Friend uses Rom manager on his s2. Looks to just automate things a little.
What I don't know is if it wipes the appropriate areas first for a clean install or if it's doing it dirty.
Sent from my Galaxy S3 using Tapatalk.

Use the Synergy backup. If you lose your IMEI you just flash it again and it's back. Just make Nandroid backups and flash away. This is my first Android phone too and now I get why people become flash addicts, it's amazing what you can do. It's easy to relock and unroot if need be. Everything is easy if you take it smart and slow.
Sent from my SCH-I535 using Tapatalk 2

Here here!
Sent from my SCH-I535 using xda premium

Just stick to a couple rules and you will be fine. First is backup, backup and backup before flashing. Always stay within the Verizon SGS3 section, Sounds simple but others have made the grave mistake. When flashing kernels, stick to the software, ie flash a JB kernel to a JB rom, flash a ICS kernel to an ICS rom. You should not have any problems but if you do you always have a backup. There are many roms, just flash an try them, make sure to read through the threads to identify any issues that have been discussed. JB roms there are a couple, a TW based JB rom from a T-mobile leak that was ported to VZW SGS3 that works well, there are official and unofficial JB vanilla roms, ie CynogenMod. Stick to those rules, keep a back up, i usually will transfer a copy of my original backup to my pc just in case, and always backup to external sd card. Good luck and have fun.

You can also flash kernels via Odin I believe.

[Q] Can't install roms anymore

I have noticed a couple of similar threads, but they're older. Pl let me know if a thread is available for my issue: I have flashed multiple roms on my VGS3 for months. Now I can't install a custom rom. I've flashed the stock root update, I've tried CWM, CWM Touch and TWRP, and I am unable to flash a rom that I want. I have tried six different ones, all newer roms updated within the last 30 days. It starts to read the update then it just stops and says "failed" or sometimes I get the unable to install system 7 prompt. Either way it's driving me crazy. I'm used to having the rom of my choice on my phone (this is your guys' fault LOL) and I'm stuck with the stock rom. I have checked, I'm rooted. I can use EZ Recovery and EZ Bootloader with no problems, I can flash different recoveries. I've heard there are other recoveries but I'm not familiar with them. Thanks y'all.

I would Odin back to stock and then root and flash clean. I have never had any problems like you are having. Had some issues flashing with twrp once but I flashed cwm and never had an issue since.
Sent from my SCH-I535 using xda premium

bbqsfire said:
I would Odin back to stock and then root and flash clean. I have never had any problems like you are having. Had some issues flashing with twrp once but I flashed cwm and never had an issue since.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I actually just did that this morning. Could it be an SD card thing? Should I maybe reformat? I'm looking at older threads and that come up a time or two.
Thanks tho, appreciate it. Like I said, never had any problems until two weeks ago.

[Q] CWM on One XL

Is it still a big "no no" to use CWM on the XL? I remember when I first got this phone we were not supposed to use it? From what I can tell all the ROM's still say flash in TWRP. The thing is I prefer using ROM Manager especially considering ive paid for it. GooManager is a just a bit lacking to me. If i do have to use TWRP it's not such a big deal, but since I'm getting a replacement phone it might be the perfect time to switch back.
I'm looking at using this one (http://forum.xda-developers.com/showthread.php?t=2240660).
Thanks guys.

kyleallen5000 said:
Is it still a big "no no" to use CWM on the XL? I remember when I first got this phone we were not supposed to use it? From what I can tell all the ROM's still say flash in TWRP. The thing is I prefer using ROM Manager especially considering ive paid for it. GooManager is a just a bit lacking to me. If i do have to use TWRP it's not such a big deal, but since I'm getting a replacement phone it might be the perfect time to switch back.
I'm looking at using this one (http://forum.xda-developers.com/showthread.php?t=2240660).
Thanks guys.
Click to expand...
Click to collapse
Using software flashers isn't a great idea. (IE not flashing directly from within recovery)
TWRP seems to have more working features than CWM.

You can use it if you want, but beware that it may not work as well as TWRP. I'd use TWRP unless you absolutely can't. It works a lot better on this phone anyways.
Sent from my evita

That version of CWM is very stable, at least it was when I was using it. The only negative was that Viper ROM wouldn't flash with it because it terminates the install if TWRP isn't installed, unless it's been changed. Other than that I had no problems with Phil's CWM whatsoever. It's not your typical CWM. The way the touch interface works is different than TWRP and kinda cool. It will also restore TWRP backups, which is a nice feature. I only switched back to TWRP because it was the only recovery image I had on my computer after I ran the 3.18 RUU and I was too lazy to download it again, lol.
Sent from my One X using Tapatalk 2

I've been using the "official" CWM, ever since TWRP 2.4 and 2.5 were having so many problems: http://forum.xda-developers.com/showthread.php?t=2148909
Everything on this CWM release seems to work fine for me. I know everything on TWP 2.6 is working fine, I just haven't bothered to go back to it.
Notions that CWM is a "big no no" is based on very outdated info. This dates from back when CWM was not an official release, just a hacked port that caused some serious (and difficult to resolve) issues for some folks.

I use cwm also since twrp was giving me dramas.
I find cwm is more compatible with things.

I've never used CWM personally, I never saw a point as everything has worked for me with TWRP (provided I stuck with 2.3.3.1 until 2.6 came out). I guess it's just personal preference. I've only gone by other's posts in terms of things people have said, not being able to mount or wipe SD card or not being able to charge in recovery. But there certainly is a bug going from certain versions of CWM to TWRP causing FC on Dialer.

The only problem I've found with TWRP 2.6 so far is that it was far too easy for me to wipe my sd card accidentally today. Using advanced wipe and moving a little too fast. No backup either. Whoops.
Sent from my Evita